yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] CharlierPvP:
Okay... I'am so confused when i tried one of the "Screen fix apps" some of them didnt even show the watermark down right corner... By the way it was the root that i used it was "S4 mini rootkit" or something like that.. Is that a screen problem or do i have to fix it physically like removeing the screen and then putting it back on (but it might be risky)..
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] IronRoo:
now I'm confused! Ha! Ha! So some of the screen test apps show the screen is working fine will others don't?

Well at least if some app show all colours/tests screens with no "ghost" icon that means at least it's not a hardware issue stuck pixel etc. That might suggest it's an app causing it. (I am assuming you got your kernal and rom from a trustworthy source and not some random download site!) Boot into safe mode so 3rd party apps don't work, do you still see the strange icon like marks?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] CharlierPvP:
I did get rom from a yt vid,but the issue didn't show up for him, and the safemode still shows the icons.. is there a samsung stock kernel somewhere, when i put my device to odin mode it show :Samsung Official System: Official
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] IronRoo:
Well I'm at a loss. Nothing I can think of seems to match all the symptoms you say and the shapes. If it's not in the software then I would guess it's some damage to screen but you say it doesn't appear on old ROM. It's not 3rd party apps so must be the rom/kernal, but still seems strange. And those shapes make stuck pixels seem unlikely ......

If it was me I'd flash another ROM, if not fixed, flash another kernal, if still not fixed then flash the stock ROM to start with a clean phone and then flash another ROM.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] CharlierPvP:
U know... i tried Cm13 still there im at loss aswell
[Huawei P9 Lite Questions & Answers] kriminel87:
need help for my p9 lite L31 lost os after traing to root i wiped out all !!and i tray the update.app always stop on 5% cause not the good firmware (VNS-L31C432B130FULL and VNS-L31_C636B100_Firmware_Southern-East Asia_Channel-Others_Andriod 6.0_EMUI 4.0_05013RUM)

need some help
[Huawei P9 Lite Questions & Answers] RonPo:
Your bootloader starts? Yes

Maybe this steps (in german) helping

Extract files from your ROM.

http://www.android-hilfe.de/thema/huawei-mate-s-anleitung-falls-nur-mehr-der-bootloader-startet.769966/

Ron
[Huawei P9 Lite Questions & Answers] Loruski053:
This happened to me too, trying to install xposed.

I fixed downloading the update.zip of the update to b151, it fixed me everything, my question is have you twrp installed?:confused: If not you must install the update.zip trough bootloader with adb.
[Huawei P9 Lite Questions & Answers] dalexlomas:
I had same issue with update stuck at 5% I solved this by doing the update with USB cable unplugged and did the update from SD card and all went well, after flushing stock rom might be necessary to wipe/data reset do this by powering the device whilst holding volume up then selecting from the menu
[HTC Desire 526] BigCountry907:
I have seen reports of getting Temp-Root.

Please share how you are getting Temp Root.

Enable OEM-UNLOCKING ---->>> Without the switch in the Developer Options.

The OEM-UNLOCKING switch simply sets the last byte of the FRP partition to 01 or 00.

00 means the boot loader can not be unlocked.

01 means it can.

Steps

1 ) Enable developer options on the device and turn on usb debugging.

2 ) Get the Temp Root Access ( We need to use the adb shell )

3 ) Copy the FRP partition to a image file. (execute the below command in adb shell)

dd if=/dev/block/bootdevice/by-name/frp of=/sdcard/frp.img

3 ) Copy the FRP image file to a computer . (execute the below command in command window)

adb pull /sdcard/frp.img

4 ) Open the frp.img in a hex editor like HXD.

change the last byte from 00 to 01. See pics below.

[IMG="OEM UNLOCKIN = OFF"]http://i1376.photobucket.com/albums/ah40/Big-Country907/Locked%20FRP_zpsmacpx7cx.jpg[/IMG]

[IMG="OEM-Unlock ENABLED"]http://i1376.photobucket.com/albums/ah40/Big-Country907/Unlocked-FRP_zpsrnyv3oxz.jpg[/IMG]

5) First copy the edited frp.img to the sdcard.

adb push frp.img /sdcard/

6) Flash the edited frp.img to the device

dd if=/sdcard/frp.img of=/dev/block/bootdevice/by-name/frp

Now boot the device into download mode

7) Get the unlock token for the htc dev site.

fastboot oem get identifier token

Go to HTC-DEV site and finish unlocking the Boot-Loader.

To Get Perm Root

1) After unlocking the boot loader flash TWRP recovery.

fastboot flash recovery twrprecovery.img

I can build the TWRP recovery ( Possibly even use Desire 626s TWRP Recovery )

2) Install supersu using TWRP.

3) Enjoy the Rooted Desire 526 ( VERIZON Model)

Can someone please share with us how you are obtaining temp root
[HTC Desire 526] BigCountry907:
So I guess No One is getting temp root ???

A thought on how to get root.

I'm not an app guy but what I suggest is.......

On a HTC Desire 626s toggle the OEM_UNLOCKING switch on and off.

Capture the command the switch uses to set the last byte of the FRP partition.

Create a app or command that is the same to run on the desire 526.

If we can set the last byte to 01 instead of 00 then we can unlock the bootloader with the normal HTC DEV.

If you tell me how to caputre / log that command I can do it on my desire 626s.
[HTC Desire 526] Darcliet:
Work around

Are you saying you need a screenshot of the oem token for the 626? I have both the Verizon 526 and cricket 626. If necessary, I can get it. Really hoping you find a workaround.
[HTC Desire 526] BigCountry907:
[MENTION=5474906]Darcliet[/MENTION]

No thats bot what i'm saying.

This is a way to get the needed OEM Unlock Token from the desire 526.

If we can set the last byte of the FRP partition to 01 then FASTBOOT OEM_UNLOCK will generate the TOKEN.

So what we need to accomplish is

Either:

A) find a way to get temp root so we can dd flash the frp partition.

B) Replicate the command that is executed on the android system to set the byte.

My reference to the Desire 626s is that the 626s has the Enable OEM Unlocking in the Developer Options.

So if we turn on and off the oem unlocking switch and then logcat the command that is executed we can use the logged command to set the FRP on the 526.

If someone tells me how to get temp root, or how to log the command from the 626s. We can give it a try.
[HTC Desire 526] BigCountry907:
Logcat of the switch

So I toggled on and off my Oem-Unlocking Switch in Developer Options ( Desire 626s)

This is the output I believe for that switch.

[COLOR="SeaGreen"]V/WindowManager( 911): not Base app: Adding window Window{52eef4 u0 com.android.settings/com.android.settings.SubSettings} at 4 of 10
I/PhoneStatusBar( 4325): setSystemUiNavVisibility(swipe=false hasFocus=false hasPolicy=false shadeState=true)
I/PhoneStatusBar( 4325): hiding the MENU button mLongPressHomeMenu = false
D/FindExtension(15804): FindExtension: before mHardwareRenderer.initialize, mSurface.isValid() = true
I/ThreadedRenderer(15804): Defer allocateBuffers to drawing time
W/Settings(15804): Setting adb_blocked has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/Settings(15804): Setting bugreport_in_power_menu has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
I/PhoneStatusBar( 4325): setSystemUiNavVisibility(swipe=false hasFocus=false hasPolicy=false shadeState=true)
I/PhoneStatusBar( 4325): hiding the MENU button mLongPressHomeMenu = false
W/InputMethodManagerService( 911): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@2cd6461d attribute=null, token = android.os.BinderProxy@2a1d8103, client pid=15804, inputType=0x(null)[/COLOR]

So someone who knows more about how this works, maybe they can come up with a way to replicate those commands.

So we could execute them on the 526.

It looks like this is setting the byte maybe???

Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@2cd6461d attribute=null, token = android.os.BinderProxy@2a1d8103, client pid=15804, inputType=0x

I'm not sure, this is a little out of my realm of expertise.

One thing I do know is if we can set the last bit of FRP to 01 then we can get the oem unlock token from fastboot.
[HTC Desire 526] Gators850:
flashed new frp with 0 changed to 1...

but when proceeding to htcdev website to enter my device identifier token i get the following error

"We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.

Error Code: 170.

Error Reason: CID Not Allowed."
[HTC Desire 526] BigCountry907:
Ok so at least your getting the unlock token now

We can try to edit the misc.img the same way.

Pull it off your phone and open in hex editor.

You will find the CID in there.

Change it to the cid for metro pcs.

We might need to edit the board_info.img the same way too.

Then try again.

Im trying to get my temp root back.

I had it and had to factory reset my phone.

now kingo is not working again.

Took me like 20 times before.
[HTC Desire 526] Gators850:
is the highlighted section what im looking for??

[IMG="misc.img"]https://s11.postimg.org/x1x0xaenn/Screenshot_2.png[/IMG]
[HTC Desire 526] BigCountry907:
No that's not it.

Got to look at build.prop

# begin build properties

# autogenerated by buildinfo.sh

htc.build.stage=2

ro.aa.customizationid=3026008

ro.aa.project=A13_WL_L51_DESIRE_SENSE70_VZW

ro.prot=true

ro.aa.maincid=VZW__003

ro.aa.cidlist=VZW__003

ro.aa.rid=205

ro.aa.modelid=0PM310000

ro.aa.report=com

ro.aa.skulist=603

ro.aa.taskid=448911

ro.aa.mainsku=603

ro.aa.romver=1.07.603.5

ro.onecid=1

ro.cwkey=VZW__003

ro.build.id=LMY47O

ro.build.display.id=LMY47O release-keys

ro.build.version.incremental=564390.5

ro.build.version.sdk=22

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=5.1

This is the CID:

ro.aa.maincid=VZW__003

This is the MAINVER:

ro.aa.romver=1.07.603.5

If you search for 1.07.603.5

you will see the CID right by it.

You might only find.

0PM310000

We should change that too.

I'm kinda thinking there is more in the frp.img thats causing the problem.

I want to drop the FRP.img from my desire 626s and give it a try.

Be careful could end up bricking.
[HTC Desire 526] BigCountry907:
If I can get this thing to root again im going to try and push my misc.img and frp.img from my desire 626s to the 526.

they are both msm8909 chipsets so should be compatible.

Crossing things up like that could cause a brick.

But ill take the chance. only paid $35 for the thing.
[HTC Desire 526] BigCountry907:
Heres the info for the 626s

# begin build properties

# autogenerated by buildinfo.sh

htc.build.stage=2

ro.aa.customizationid=3031505

ro.aa.project=A32E_UL_L51_DESIRE_SENSE70

ro.prot=true

ro.aa.maincid=METRO001

ro.aa.modelid=0PM911000

ro.aa.rid=427

ro.aa.taskid=455088

ro.aa.cidlist=METRO001

ro.aa.report=com

ro.aa.skulist=1550

ro.aa.mainsku=1550

ro.aa.romver=1.23.1550.3

ro.onecid=1

ro.cwkey=METRO001

ro.build.id=LMY47O

ro.build.display.id=LMY47O release-keys

ro.build.version.incremental=637541.3

ro.build.version.sdk=22

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=5.1

use the CID and Mainver And device model from here.

If you are changing your misc.img.

mainver = 1.23.1550.3

cid = METRO001

mid= 0PM911000

change mainver to 1.00.0000.0
[HTC Desire 526] BigCountry907:
Theese are the files from my 626s.

You can try to dd them over.

dd if=/sdcard/frp.img of=/dev/block/bootdevice/by-name/frp

dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc

dd if=/sdcard/board_info.img of=/dev/block/bootdevice/by-name/board_info

It Could cause you not to boot.

I would do frp.img and try unlock

then if dont work add misc.img

then if dont work add board_info

Backup your original files first so if it goes wrong there might be a chance to put them back.
[HTC Desire 526] Gators850:
flashed the files you provided,again once proceeding to the htcdev website to enter the token i get same error as before
[HTC Desire 526] BigCountry907:
Well that makes things much more complicated.

Chances are it's probably coded in the boot-loader itself.

If you don't mind I want to have you pull all the firmware files off the phone.

All of them.

I'll write you a script. (I still never got my temp root back).

I would like to take a look at the recovery and the kernel in the boot.img.

Like I said the Desire 626s and the Desire 530 both are msm8909 chipsets. This also includes the newer Desire 526 as well. This means that the actual firmware running the chips is the same. My initial Idea was to build my own firmware for the 626s and test flash it on the 526. If that works then theoretically we could take the boot-loader and radio images from a S-off device and flash it to a non s-off and have s-off.

Yes I know there is no way to write to those partitions without s-off ( By normal means anyway ).

Now if you intentionally cause the right kind of brick by removing the right firmware and not removing the wrong firmware to force the device into Emergency Download Mode then provided that we have the other files we need for QPST and or QFIL ( for msm8909 chips ) we can take the firmware files from the RUU for the 626s and push it to the 526.

Pretty crazy I know. For sure not easy. And also after such a flash the 526 would actually be a 626s.

If you want to know how we could do this then go here and download the whole Qualcomm Tech Folder.

https://github.com/dante198406/Qual...0-NR964-4_C_MSM8909_LA_SW_User_Manual_SPD.pdf

Learn the QPST - QFIL stuff and away we go.

Not sure what my issue is getting root now.

Kingo keeps getting stuck at lime 52% till I reboot and then stuck at 65% till reboot then stuck at 77% till fail root.

Any Ideas?
[HTC Desire 526] BigCountry907:
Heres a Link To the process in general.

http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
[HTC Desire 526] BigCountry907:
Ya im frustrated now.

I spent a whole day trying to get temp root back.

No luck.

It Seems to be an issue with the kingo link app on the phone.

When i did get root it wasnt poping up now it keeps popping up.
[HTC Desire 526] Gators850:
cmd

Would this be the correct code I'd go about to back up Img?

adb shell

su

dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646

New to this so do apologize
[HTC Desire 526] BigCountry907:
Almost but not quite.

If you ran that command go to your sdcard1 folder and delete the backup.img.

Otherwise your phone memory is more than full.

The htc devices seem to use sdcard2 as the external sd card.

So first you will need a 32gb sd card.

The image size will be like 16gb.

then the command I would use is.

adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard2/backup.img

then

exit
exit

so that you are at the regular command window.

then

adb pull /sdcard2/backup.img

To get it to the computer.

That is 1 of the backups we need.

But we need each partition individually too.

Give me a little wile and Ill post the commands.

And Please don't try to intentionally brick your phone.

It might not be so easy to use qfil or qpst to fix it.

There are other files we need to get for qpst first.
[HTC Desire 526] Gators850:
so this code gave me a file or directory does not exsit:

adb shell

su

dd if=/dev/block/mmcblk0 of=/storage/sdcard2/backup.img

So I Changed It To The Following:

adb shell

su

dd if=/dev/block/mmcblk0 of=/storage/ext_sd/backup.img
[HTC Desire 526] BigCountry907:
Ok as long as the file goes to the external sdcard your good to go.

I found the kingoroot issue. The root works fine but the kingosuperuser app is not giving me the prompt to grant root permission. They need to fix kingosuperuser. Get it out to them and if they fix it many more people will easily get temp root. After you have it working the 1st time. Like actually working with adb shell

su

after reboot run kingoroot again and temp root comes right back.

I cant get past the su part again.
[HTC Desire 526] Gators850:
last night i was having a issue with kingo as well after doing a factory reset...every time id click on kingo root on my pc it would run awhile then disconnect my wifi on my phone causing the root process to fail due to the fact the phone needs wifi...

what i did which idk if it helped or not is as following...

restarted phone a few times,downloaded supersu and king root not kingo on my phone (not pc) and started the root process....

once it started the root process i then click home screen to let it run in background for a min or so..

then would open supersu then close it and reopen king root...

eventually once king root got to like 25% supersu would prompt me to update binary when id open it..

i clicked continue normal update of binary,supersu will fail of course but once i gained temp root that way i reconnected my phone to pc and reran kingo and it worked...

i have successfully pulled the backup.img from phone and it is a total of 7.28 GB
[HTC Desire 526] BigCountry907:
Cool

I will try what you did.

I was messing around with supersu and kingroot too when I finally got kingoroot to work the first time.

Yes your backup size sounds about right. Our device is 8gb.

You still need to backup each individual partition.

Let me shoot you the commands real quick.

give me 30 minuets
[HTC Desire 526] BigCountry907:
Theese are all the partitions you need to backup.

Pull the other backup image from your sd first so you have space.

Unless you have enough space. another 8gb

1|shell@htc_a13wlpp:/ $ cat /proc/emmc

dev: size erasesize name

mmcblk0p1: 00004000 00000200 "board_info"

mmcblk0p2: 00400000 00000200 "pg1fs"

mmcblk0p3: 00100000 00000200 "sbl1"

mmcblk0p4: 01af7c00 00000200 "reserve_1"

mmcblk0p5: 00040000 00000200 "mfg"

mmcblk0p6: 017afc00 00000200 "pg2fs"

mmcblk0p7: 00040000 00000200 "rpm"

mmcblk0p8: 00200000 00000200 "tz"

mmcblk0p9: 00400000 00000200 "aboot"

mmcblk0p10: 00a00000 00000200 "sp1"

mmcblk0p11: 00008000 00000200 "ddr"

mmcblk0p12: 00100000 00000200 "rfg_0"

mmcblk0p13: 00100000 00000200 "rfg_1"

mmcblk0p14: 00100000 00000200 "rfg_2"

mmcblk0p15: 00100000 00000200 "rfg_3"

mmcblk0p16: 00100000 00000200 "rfg_4"

mmcblk0p17: 00100000 00000200 "rfg_5"

mmcblk0p18: 00100000 00000200 "rfg_6"

mmcblk0p19: 00100000 00000200 "rfg_7"

mmcblk0p20: 00180000 00000200 "fsg"

mmcblk0p21: 03b00400 00000200 "radio"

mmcblk0p22: 00a00000 00000200 "tool_diag"

mmcblk0p23: 00500000 00000200 "wcnss"

mmcblk0p24: 00000400 00000200 "limits"

mmcblk0p25: 00447c00 00000200 "reserve_2"

mmcblk0p26: 00100000 00000200 "misc"

mmcblk0p27: 00001000 00000200 "debug_config"

mmcblk0p28: 00180000 00000200 "modem_st1"

mmcblk0p29: 00180000 00000200 "modem_st2"

mmcblk0p30: 00040000 00000200 "pdata"

mmcblk0p31: 01600000 00000200 "persist"

mmcblk0p32: 00004000 00000200 "sec"

mmcblk0p33: 00100000 00000200 "cdma_record"

mmcblk0p34: 00000400 00000200 "fsc"

mmcblk0p35: 00002000 00000200 "ssd"

mmcblk0p36: 00020000 00000200 "rfg_8"

mmcblk0p37: 00020000 00000200 "rfg_9"

mmcblk0p38: 00020000 00000200 "rfg_10"

mmcblk0p39: 00020000 00000200 "rfg_11"

mmcblk0p40: 00020000 00000200 "rfg_12"

mmcblk0p41: 00020000 00000200 "rfg_13"

mmcblk0p42: 00020000 00000200 "rfg_14"

mmcblk0p43: 00020000 00000200 "rfg_15"

mmcblk0p44: 00004000 00000200 "control"

mmcblk0p45: 00010000 00000200 "extra"

mmcblk0p46: 00140400 00000200 "local"

mmcblk0p47: 00040000 00000200 "skylink"

mmcblk0p48: 02800000 00000200 "carrier"

mmcblk0p49: 00080000 00000200 "frp"

mmcblk0p50: 01000000 00000200 "vzw_quality"

mmcblk0p51: 01000000 00000200 "vzw_logger"

mmcblk0p52: 01400000 00000200 "fataldevlog"

mmcblk0p53: 01e00000 00000200 "devlog"

mmcblk0p54: 00a00000 00000200 "ramdump"

mmcblk0p55: 00a00000 00000200 "battery"

mmcblk0p56: 01000000 00000200 "absolute"

mmcblk0p57: 003a4800 00000200 "reserve"

mmcblk0p58: 03000000 00000200 "hosd"

mmcblk0p59: 02000000 00000200 "boot"

mmcblk0p60: 02000000 00000200 "recovery"

mmcblk0p61: 18000000 00000200 "cache"

mmcblk0p62: a0000000 00000200 "system"

mmcblk0p63: 00500000 00000200 "cota"

mmcblk0p64: 00500000 00000200 "apppreload"

mmcblk0p65: f8000000 00000200 "userdata"
[HTC Desire 526] BigCountry907:
By the way.

Did you ever get the promp to allow root access to apps / adb ???
[HTC Desire 526] Gators850:
yes i am getting promp to allow root....this could be a dumb question but if i was to take the backup.img and extract it with 7zip could i pull the img files from within that are needed from the list of backups you need cause ive noticed they are within the backup.img file?
[HTC Desire 526] BigCountry907:
IDK. I have never seen windowz ever read a backup file like that.

You are correct though. They are all in there.

But that 1 individual backup has never really prooved to be useful to me.

So I do both.

1 so i have a maybe unbrick image.

and the rest so I have each partition.

So when I mess around and hex edit something like the misc.img and screw it up.

I have a good image to put back.

I'm working mostly in linux. I only run windoze when i have no choice.

Some of the backups we can actullaly mount and open and read in linux.

The only way to be safe is to do it both ways.

Were really playing with fire here.

The other images I gave you were off my 626s.

But it didnt brick you.

So when I get root again.

Im gonna see what othere 626s images I can push.

Most likley I will brick it until I can do the qpst / qfil thing.

But the reason i bought this phone is cause it's $35.00 and makes a great toy to learn with.

My 626s and the new 530 are about the same at this device. Hopefully I got it right. the 626s the 526 and the 530.

To me really there the same.

Same hardware different software.

But none the less all compatible.
[HTC Desire 526] BigCountry907:
Im good to go again.

Temp root ok.

Time to get busy.

Must be the team effort.

SU / King / Kingo
[HTC Desire 526] Gators850:
hell yeah im glad to hear your up and running...im pulling the last of the img files now...

i do have another dumb question lol..

i noticed on this code you put in a " after the rfg_1

for example:

dd if=/dev/block/bootdevice/by-name/rfg_1" of=/storage/ext_sd/rfg_1.img

but then in this code below you left out the "

dd if=/dev/block/bootdevice/by-name/rfg_8 of=/storage/ext_sd/rfg_8.img

so my question is this do i need to include the " or leave it out....
[HTC Desire 526] BigCountry907:
Oops Leave out the "
[HTC Desire 526] Gators850:
Google Drive

Currently uploading files to google drive....later on this evening after work I'll post the current download links to files