Related
Alot of the guides floating around showing how to flash back to stock rom is incomplete ( missing a few steps ) and will result in boot loop most of the time. the correct procedure is :
Part 1 : Setting up Fastboot.
1. Make sure you have java installed, if not get it from here : http://java.com/ and install it.
2. Download the Android SDK manager from here : http://developer.android.com/sdk/index.html ( get the exe download )
3. Install SDK manager, then run the android SDK manager.
4. Once launched it will show you available updates, choose ONLY these two "Android SDK Platform Tools and Android SDK Tools" and update them.
5. After update is complete close the sdk manager and go to the SDK manager platform-tools folder, normal path is : ( C:\Program Files\Android\android-sdk\platform-tools )
6. Copy the following 3 files from this folder : "adb.exe" , "AdbWinApi.dll" and "fastboot.exe"
7. go to your c drive ( c:\ ) and make a new directory called "fastboottools"
8. copy the 3 files above into your fastboottools folder.
9. so now your should have a folder like this : "c:\Fastboottools" with the following 3 files in it "adb.exe" , "AdbWinApi.dll" and "fastboot.exe".
Click to expand...
Click to collapse
That is it, Fastboot tools is setup. Proceed to next guide.
Part 2 : Flashing guide.
1. download the ROM from here:
ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35. 3033h_7.51.35.19_release_228383_signed.zip
or here ( mirror link ) : ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35.3033h_7.51.35.19_release_228383_signed.zip
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.
Click to expand...
Click to collapse
after trying EVERYTHING else, this is the method that worked for me, i tried to cover every step possible ( alot of the other guides skipped few steps and that is where i got problems ).
hope this helps.
( PLEASE BE AWARE : This will remove recovery and root. if you flash back to stock rom using this method you will have to root your phone again. It will still be unlocked, just recovery and root will be removed. to re add recovery and root check part 3 below. )
Part 3 : Add recovery and root access back after installing stock rom.
1. Download the following 2 files, you will need them :
PH06IMG.zip
su-2.3.6.1-ef-signed.zip
2. Extract PH06img.zip to your "c:\fastboottools" directory. it will add the "recovery.img" file to fastboot.
3. Copy the file su-2.3.6.1-ef-signed.zip to your phones SD card, dont change the name, keep it standard, just put it in the root directory of your SD card.
4. go to the settings on your phone "Settings -> Power -> and Uncheck Fast boot" ( This is important, make sure fastboot is unchecked.
5. Take out your battery, put battery back in and boot into bootloader ( hold down volumedown + power )
6. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
7. Go to the Fastboottools directory "c:\fastboottools", Hold CTRL+Shift and right click in that Folder and open Command Prompt.
8. type inside command prompt : "fastboot flash recovery recovery.img" and let it finnish, takes less than a minute.
9. reboot your phone, but reboot it back into bootloader ( hold down volumedown + power )
10. Now using volume keys choose "recovery" and press "enter" ( not power button, rather use enter button in recovery else you sometimes get a "hat like" picture on the screen )you should now see the recovery options.
11. find the "install zipd from sd card" option and press enter, then choose su-2.3.6.1-ef-signed.zip and confirm to flash it.
12. once flashed reboot the phone and you will now have recovery and root access back again.
Click to expand...
Click to collapse
it is recommended you update superuser to newer version and also install busybox.
Now that you have recovery installed you can also flash custom roms again.
I STRONLGY recommend once you reach this step that you make a backup of your rom via the bootloader recovery menu, that way you dont have to go through all this pain again next time.
The End !!!
feel free to post any problems you encounter below.
stuck on bootloop at step 10
I've attempted the recovery and get as far as step 10, but unfortunately
"still suffer the bootloop.
what am I supposed to do in the recovery step to get it working fine!
do i load the update.zip?
please reply if availale... am stuck on bootloop
ty
bootloop ussualy happens when you dont clear your cache properly before flashing.
Make sure to clear ALL cache, and also make sure to follow the steps exactly as they are posted, even if it looks like you can skip a step DON'T. do each step as posted, and clear all cache when you are told to. then you wont get boot loops.
Hi,
I bought HTC chacha locally at a online retailer. Its not tied to any sim/operator. However I am stuck at android version 2.3.3. (firmware version 1.20.720.1). If I try to run the (ota)software update, the phone says no updates available.
I really need to unlock the boot loader. However if I try the htcdev.com, the RUU utility says that the please update to 1.57.XX and then try unlocking the bootloader. I am really stuck here.
My question is can I try the steps mentioned above in this post to get the firmware update, with a locked bootloader?
Any other suggestions to update my firmware to the latest 1.57.XX?
--Thanks in Advance..
htc status restore factory 2.3.3
No, I didn't make a real backup! I thought titanium backup would cover that, it didn't, so I have no backup of the stock stuff.
I have a HTC Status (aka chacha) US ver with att. I unlocked the boot loader by htc's site, worked fine. Then I rooted it with cmw, worked great.
Recently the ota 2.3.5 update (48mb) became available. I downloaded it and tried to install it, it failed with checksum. I know it is the cmw mod. How can I get the stock load 2.3.3 back onto my htc status? The above directions mention the "asia" load. Are the files mentioned generic for all phones with the exception of the cid?
p.s. It would be great if someone out there had the stock 2.3.3 recovery file for the status! That would be easier to load than the sdk stuff.
update : both ruu files listed above show to be corrupt when unzipping.
Update: I installed a newer zip utility than the stock win xp one and it unzipped without any trouble. Moving on to the next step.
Update: all went well, except the "english" option, I chose english singapore. Installed cwm and rooted again. updated to 2.3.5. Thanks for the info above.
thank you!
raymerjacque said:
Alot of the guides floating around showing how to flash back to stock rom is incomplete ( missing a few steps ) and will result in boot loop most of the time. the correct procedure is :
Part 1 : Setting up Fastboot.
That is it, Fastboot tools is setup. Proceed to next guide.
Part 2 : Flashing guide.
after trying EVERYTHING else, this is the method that worked for me, i tried to cover every step possible ( alot of the other guides skipped few steps and that is where i got problems ).
hope this helps.
( PLEASE BE AWARE : This will remove recovery and root. if you flash back to stock rom using this method you will have to root your phone again. It will still be unlocked, just recovery and root will be removed. to re add recovery and root check part 3 below. )
Part 3 : Add recovery and root access back after installing stock rom.
it is recommended you update superuser to newer version and also install busybox.
Now that you have recovery installed you can also flash custom roms again.
I STRONLGY recommend once you reach this step that you make a backup of your rom via the bootloader recovery menu, that way you dont have to go through all this pain again next time.
The End !!!
feel free to post any problems you encounter below.
Click to expand...
Click to collapse
thank ! but dont update rom to 1.57.707.3,why?
Does the phone need an unlocked bootloader?
Can the be a way to debrand the firmware? Is the firmware attached the latest generic one?
Thanks
can't flash new htc status att rom 2.14.502.2 ruu security fail
Goatman5467 said:
No, I didn't make a real backup! I thought titanium backup would cover that, it didn't, so I have no backup of the stock stuff.
I have a HTC Status (aka chacha) US ver with att. I unlocked the boot loader by htc's site, worked fine. Then I rooted it with cmw, worked great.
Recently the ota 2.3.5 update (48mb) became available. I downloaded it and tried to install it, it failed with checksum. I know it is the cmw mod. How can I get the stock load 2.3.3 back onto my htc status? The above directions mention the "asia" load. Are the files mentioned generic for all phones with the exception of the cid?
p.s. It would be great if someone out there had the stock 2.3.3 recovery file for the status! That would be easier to load than the sdk stuff.
update : both ruu files listed above show to be corrupt when unzipping.
Update: I installed a newer zip utility than the stock win xp one and it unzipped without any trouble. Moving on to the next step.
Update: all went well, except the "english" option, I chose english singapore. Installed cwm and rooted again. updated to 2.3.5. Thanks for the info above.
Click to expand...
Click to collapse
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Thanks man
Tried and made it
Work very fine except I cannot update sofware to newer version... Stuck on 1.54.401.2
Goatman5467 said:
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Click to expand...
Click to collapse
I'm having the same issue.
You need the stock rom for the update to work. But frankly, I did not see any improvement. Battery life sucks.
I'm back to CM9
Goatman5467 said:
A new ota update was available (1.57.707.3) but it won't install, it says the current rom seems to be altered and it refuses to install. So I went to htc.com/support and found the status page and downloaded the latest installer for 2.14.502.2 rom image. It fails with "security fail" under ruu in the phones bootloader screen.
The installer on the pc say's I must get the correct rom installer for my phone. I think it might have something to do with the asia chacha system and boot.img 2.3.3 stuff I installed.
Current software is android 2.3.5 and software 1.57.707.2
Is there anyway to get rid of cwm or force the new rom to install over the old?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1752473
good lesson
Hi everyone.
I want to take my htc cha cha for warranty service by HTC. It means that I need to un-root the phone and take it back to official rom by HTC.
My phone is in Asia area, anyone has this stock/ official rom? Plzz share to me.
Thanks so much.
...
Hi ..
i have a problem with coming back to the stock arabic rom
the wizard stops and gives 2 errors !!
Signature check fails
Is there a way to switch off or bypass signature checking?
>fastboot flash system system.img
sending 'system' (254104 KB)...
OKAY [ 57.650s]
writing 'system'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 293.043s
>fastboot flash boot boot.img
sending 'boot' (2584 KB)...
OKAY [ 2.340s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 4.633s
thanks!, it worked for me
Link doesn't work
Dear, thank you for the super thread. But I have 2 problems (as I'm a newbie to HTC Chacha).
1. The download links for the files PH06IMG.zip & su-2.3.6.1-ef-signed.zip does not work. and 2. I cannot get the code from HTCDev website.
Please Help.
Thanks in advance.
Hello Everyone
Currently my ChaCha is running on GB 2.3.5 with version 1.57.720.1 (ASIA)
i want to the stock rom of this verison may be upgraded also
The links mentioned for the stock rom in this thread is not working
can i get the working links
P.S if i flash my ChaCha with CyanogenMod9 can i switch back to my stock verison without any issues (sorry if my question is annoying)
Thank you
I have been trying to unbrick my phone for 2 days now. So right now when I boot it goes through the boot screens then it goes black and just says
"process system ins't responding" , so if i press wait that error will just pop up again. Otherwise all I get is a black screen and have to force reboot.
So here is what I have done so far:
When bought phone I did S-OFF and have it unlocked "I believe it was with firewater, but that was months ago",
Installed CWM 6.0.4.8 <--im pretty sure thats the one.
Created nandroid
Then I installed SKYFALL and used that ever since.
Decided I wanted ViperOne.
Read many post and here is where the fun started.
Restored my origional nandroid.
fastboot flashed stock recovery then erase cache
booted nandroid. and installed downloaded 4.4.3 OTA
phone rebooted just fine.
fastboot flashed twrp recovery (openrecovery-twrp-2.8.0.3-m8_wlv.img) then erase cache
booted recovery and installed ViperOne.
then error process system isn't responding.
Since then I have repeated those steps. I have also tried CleanRom and RKDN and those get stuck in loading loops. I have tried the RUU options, and tried RUU and fastboot to get back to the 1.55.605.2 completely stock as it can be with a stock image or the nandroid and nothing seems to work. Just get the same errors. Now I am stuck and unsure what to do or how to go about fixing this....
Not sure if you've already tried this, but might help.
Load the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
After that, go into the stock recovery and do a factory reset.
dab1414 said:
I have been trying to unbrick my phone for 2 days now. So right now when I boot it goes through the boot screens then it goes black and just says
"process system ins't responding" , so if i press wait that error will just pop up again. Otherwise all I get is a black screen and have to force reboot.
So here is what I have done so far:
When bought phone I did S-OFF and have it unlocked "I believe it was with firewater, but that was months ago",
Installed CWM 6.0.4.8 <--im pretty sure thats the one.
Created nandroid
Then I installed SKYFALL and used that ever since.
Decided I wanted ViperOne.
Read many post and here is where the fun started.
Restored my origional nandroid.
fastboot flashed stock recovery then erase cache
booted nandroid. and installed downloaded 4.4.3 OTA
phone rebooted just fine.
fastboot flashed twrp recovery (openrecovery-twrp-2.8.0.3-m8_wlv.img) then erase cache
booted recovery and installed ViperOne.
then error process system isn't responding.
Since then I have repeated those steps. I have also tried CleanRom and RKDN and those get stuck in loading loops. I have tried the RUU options, and tried RUU and fastboot to get back to the 1.55.605.2 completely stock as it can be with a stock image or the nandroid and nothing seems to work. Just get the same errors. Now I am stuck and unsure what to do or how to go about fixing this....
Click to expand...
Click to collapse
I can team viewer with you and checkout what's up. What error do you get on RUU flashing?
jsaxon2 said:
Not sure if you've already tried this, but might help.
Load the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
After that, go into the stock recovery and do a factory reset.
Click to expand...
Click to collapse
I had this ruu already, and the MD5 matched up. So I downloaded a new copy anyways, However I am unable to flash it. On another note I did try other non 443 rru's that did flash but factory reset did not work.
dottat said:
I can team viewer with you and checkout what's up. What error do you get on RUU flashing?
Click to expand...
Click to collapse
when trying to flash
Code:
C:\Users\balddav\My Documents\M8\ruu\443>fastboot oem rebootRUU
C:\Users\balddav\My Documents\M8\ruu\443>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
error: cannot load '0P6BIMG.zip'
Then I push file to root of external sd card:
once boot to HBOOT
Loading...[0P6BIMG.zip]
and after 1 hour still loading. then I tried to load 442 ruu and this:
Code:
C:\Users\balddav\My Documents\M8\ruu\442>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (825739 KB)...
OKAY [ 35.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 36.033s
I can ruu the 443 firmware from this post http://forum.xda-developers.com/showthread.php?t=2723159with no issues.
dab1414 said:
I had this ruu already, and the MD5 matched up. So I downloaded a new copy anyways, However I am unable to flash it. On another note I did try other non 443 rru's that did flash but factory reset did not work.
when trying to flash
Code:
C:\Users\balddav\My Documents\M8\ruu\443>fastboot oem rebootRUU
C:\Users\balddav\My Documents\M8\ruu\443>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
error: cannot load '0P6BIMG.zip'
Then I push file to root of external sd card:
once boot to HBOOT
Loading...[0P6BIMG.zip]
and after 1 hour still loading. then I tried to load 442 ruu and this:
Code:
C:\Users\balddav\My Documents\M8\ruu\442>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (825739 KB)...
OKAY [ 35.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 36.033s
I can ruu the 443 firmware from this post http://forum.xda-developers.com/showthread.php?t=2723159with no issues.
Click to expand...
Click to collapse
Flash the firmware and then go right to RUU flashing via sd.
dottat said:
Flash the firmware and then go right to RUU flashing via sd.
Click to expand...
Click to collapse
I have tried that and it hangs on loading. But I will try it again.
When I woke up I noticed my phone actually booted up normally. I think what I did different was reformat external drive. Copy the 442 RUU to it. I flashed the 442 firmware, then reboot to hboot it loaded the RUU, went to sleep and it worked.
So when I get a chance today I will make sure I have a good copy of the 443 firmware and try it the same way I just did 442, and post my steps.
Thanks for your help so far.
removed
So I was just trying something out and downloaded the OTA update and installed it. Everything looked like it updated fine so I just rebooted and the error process system isn't responding came back when rebooting. So I am trying the 443 firmware and RUU.
One thing I noticed from this post http://forum.xda-developers.com/showthread.php?t=2723159 is there is no boot or recovery, so after flashing the 443 firmware, I flashed the boot and recovery images found on the same thread. then I inserted the sd card with the RUU from here http://forum.xda-developers.com/verizon-htc-one-m8/development/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144 and this time HBOOT loaded the file and installed with no errors.
Now on booting up it still says Process system isn't responding.
dab1414 said:
So I was just trying something out and downloaded the OTA update and installed it. Everything looked like it updated fine so I just rebooted and the error process system isn't responding came back when rebooting. So I am trying the 443 firmware and RUU.
One thing I noticed from this post http://forum.xda-developers.com/showthread.php?t=2723159 is there is no boot or recovery, so after flashing the 443 firmware, I flashed the boot and recovery images found on the same thread. then I inserted the sd card with the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144 and this time HBOOT loaded the file and installed with no errors.
Now on booting up it still says Process system isn't responding.
Click to expand...
Click to collapse
You did not need to flash boot and recovery. In fact, the ruu will do that automatically for you.
Did your phone calm down? Sometimes on boot if blinkfeed and other apps try to update it can crash. . Reboot once more after that and see what happens.
dottat said:
You did not need to flash boot and recovery. In fact, the ruu will do that automatically for you.
Click to expand...
Click to collapse
I realized that shortly after I typed it, I looked in the zip files.
dottat said:
Did your phone calm down? Sometimes on boot if blinkfeed and other apps try to update it can crash. . Reboot once more after that and see what happens.
Click to expand...
Click to collapse
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo%20Oct%2016%2C%2023%2039%2048.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video%20Oct%2016%2C%2023%2042%2033.mov?dl=0
I have tried rebooting several times with the same results.
dab1414 said:
I realized that shortly after I typed it, I looked in the zip files.
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo Oct 16, 23 39 48.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video Oct 16, 23 42 33.mov?dl=0
I have tried rebooting several times with the same results.
Click to expand...
Click to collapse
I'm at a loss, the only other thing I could tell you to try would be to remove the sdcard and try rebooting.
I have a few comments. Go back and flash the 4.4.3 RUU from fastboot. Make sure your SDK is up to date with the latest and greatest. Your firmware is ok. In looking through your log from the fastboot attempt, you got error - Failed (remote: 32 header error). This means the zip couldn’t be read and unzipped properly. Something is borked. Make sure you have lots of room on your internal SD card too.
dab1414 said:
I realized that shortly after I typed it, I looked in the zip files.
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo Oct 16, 23 39 48.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video Oct 16, 23 42 33.mov?dl=0
I have tried rebooting several times with the same results.
Click to expand...
Click to collapse
You could have hosed partitions. I can team viewer and try a couple things to see if we can get it fixed.
jsaxon2 said:
I'm at a loss, the only other thing I could tell you to try would be to remove the sdcard and try rebooting.
Click to expand...
Click to collapse
Irieone said:
I have a few comments. Go back and flash the 4.4.3 RUU from fastboot. Make sure your SDK is up to date with the latest and greatest. Your firmware is ok. In looking through your log from the fastboot attempt, you got error - Failed (remote: 32 header error). This means the zip couldn’t be read and unzipped properly. Something is borked. Make sure you have lots of room on your internal SD card too.
Click to expand...
Click to collapse
dottat said:
You could have hosed partitions. I can team viewer and try a couple things to see if we can get it fixed.
Click to expand...
Click to collapse
Finally!!! Thank you all for the help.
So I removed my sdcard, then installed twrp, then went and advanced wipe and selected every box ( all i did before was factory resets). Then flashed firmware through ruu mode. Then reinserted sdcard with the 0P6BIMG file. rebooted to bootloader selected hboot, then when done rebooted and it was working fine. then reinstalled twrp and installed viperone, and rolling through just fine. Guess there was something floating around the factory reset didnt wipe.
Again thank you all for your time and help to resolve my screwup!!
dab1414 said:
Finally!!! Thank you all for the help.
So I removed my sdcard, then installed twrp, then went and advanced wipe and selected every box ( all i did before was factory resets). Then flashed firmware through ruu mode. Then reinserted sdcard with the 0P6BIMG file. rebooted to bootloader selected hboot, then when done rebooted and it was working fine. then reinstalled twrp and installed viperone, and rolling through just fine. Guess there was something floating around the factory reset didnt wipe.
Again thank you all for your time and help to resolve my screwup!!
Click to expand...
Click to collapse
Yeah....I think your partition was wonked. Twrp even has a repair option built in now for ext4 partitions under advanced wipe.
so im having a issue attemping to root my verizion variant google pixel. ive been successful in getting the device a unlocked boot loader but now the issue i am running into in the recovery. Secondly when i go to reboot the phone after flashing the recovery as failed the loading screen goes on for hours with no change. This is what im running currently.\
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (9434 KB)...
OKAY [ 0.330s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 0.435s
That is what i get as a responce. any help would be a great help. Those that can assist me in the matter im willing to sent some BTC your way. Thanks in advance. ive also tried to go the boot-to-root method and i get the same effect of the phone being stuck at the loading screen.
Why are you not reading in the other section where this is posted. Mods, roms, etc. It is known that recovery partition is gone, it's part of boot. There is TWRP alpha2 thread that works on Pixel and instructions. SuperSU 2.78 SR4 works as well.
I suggest you do reading first to understand how the new partitions work before you start moding. Pixel has 2 system, 2 boot partitions.
milan187 said:
Why are you not reading in the other section where this is posted. Mods, roms, etc. It is known that recovery partition is gone, it's part of boot. There is TWRP alpha2 thread that works on Pixel and instructions. SuperSU 2.78 SR4 works as well.
I suggest you do reading first to understand how the new partitions work before you start moding. Pixel has 2 system, 2 boot partitions.
Click to expand...
Click to collapse
is there any link that you can reference? thanks in advance.
http://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page10
First thing you're doing wrong is flashing the boot image you're supposed to be booting the boot image.
jayfried said:
http://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page10
First thing you're doing wrong is flashing the boot image you're supposed to be booting the boot image.
Click to expand...
Click to collapse
i have isolated what i think is the root of the issue.
First, i can't do a normal boot up on the phone is stays at the google load screen with the four dots that shift left and right.
Second i try and use adb push and i can't get the files on the phone and I'm stuck in fast boot. (adb devices shows nothing and fast boot devices shows the phone)
my theory is that i need the zip on the phone and it would have what it needs to run.
Any help on the matter would be of great help.
There are 2 files for twrp, an image file which you put with your adb and fastboot tools and a zip file that goes on your phone which you can put on there one you fastboot "BOOT" the image file. fastboot boot of the twrp.img file will boot the phone to recover but it doesn't install the recovery you have to at this point install the zip file which can be put on the phone as it's file system should be mounted and installed From twrp. As you are not able to boot the phone right now I recommend starting over with a fresh install of Google factory image.
This is the first thing you should do if you haven't already: http://forum.xda-developers.com/showthread.php?t=2588979&page=93
Make sure to install it system wide so you can run the adb and fastboot from any directory on your computer. Then this:
https://developers.google.com/android/images
1.Download and unzip the correct file which would probably be in NDE63V
2. Put phone in bootloader mode and run the flash all batch file, boot it and set up phone
3. Put the zip files on the phone for twrp and root and enable USB debug
4. Back to bootloader and fastboot boot the twrp image
5. Once booted in twrp install the zip for twrp and reboot to recovery from the reboot tab
6. Once back in the recover which is now installed install the zip for root then reboot system and rejoice
---------- Post added at 09:14 PM ---------- Previous post was at 08:56 PM ----------
Sorry for all the edits
jstorms1991 said:
i have isolated what i think is the root of the issue.
First, i can't do a normal boot up on the phone is stays at the google load screen with the four dots that shift left and right.
Second i try and use adb push and i can't get the files on the phone and I'm stuck in fast boot. (adb devices shows nothing and fast boot devices shows the phone)
my theory is that i need the zip on the phone and it would have what it needs to run.
Any help on the matter would be of great help.
Click to expand...
Click to collapse
Did you enable adb debugging? Honestly, just following the instructions works great. No theories needed.
Use flashall from Google of you are stuck to go back to stock, then start over.
Also look here, it's from XL but applies.
Do your research before messing around.
https://r.tapatalk.com/shareLink?ur...share_tid=3494478&share_fid=3793&share_type=t
[GUIDE] Restore to stock after soft bricking. Then install TWRP, Root & Custom Kernel
As the TRWP heroes are'nt ready with a fully working recovery version and keep their thread clean for developement I'll start
here with a self answered question.
One way which finally helped me out to get the phone rooted was this one, witch @devsk kindly posted:
1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!
Note the model number in that ZIP URL. If it does not match your phone, do not use it. I have compiled a list of stock recovery and boot at: https://forum.xda-developers.com/htc-u11/development/stock-recovery-taiwan-version-1-10-709-t3719599
I will keep adding as we see more models.
Will we loose fingerprint security after root?
Example story = HTC one MAX, lost fingerprint security after unlock bootloader. Early birds whom managed to unlock then also got S-off then remove the "tampered" mark as well as modify the unlock to show "locked" as if the entire thing is virgin in order to get fingerprint security back.
After a couple of months of official updates, it cannot be S-off by old exploits and must pay Sunshine S-off then can remove the "tampered" and modify to virgin "lock" to get fingerprint security.
Will U11+ go through the same story?
cx5 said:
Will we loose fingerprint security after root?
Example story = HTC one MAX, lost fingerprint security after unlock bootloader. Early birds whom managed to unlock then also got S-off then remove the "tampered" mark as well as modify the unlock to show "locked" as if the entire thing is virgin in order to get fingerprint security back.
After a couple of months of official updates, it cannot be S-off by old exploits and must pay Sunshine S-off then can remove the "tampered" and modify to virgin "lock" to get fingerprint security.
Will U11+ go through the same story?
Click to expand...
Click to collapse
Didn't happen on the U11 so can't see why it would on the +
For some reason I am unable to flash the boot image .. patched or otherwise .. can't even flash the test TWRP recovery image.
Below is what I get whenever I try to flash any .img file.. Anyone have any clue what's wrong or can help???
Code:
fastboot flash boot patched_boot.img
target reported max download size of 2399200000 bytes
sending 'boot' (37409 KB)...
FAILED (data write failure (Too many links))
finished. total time: 1.006s
E:\Temp
I have 2 HK U11+'s and both are unable to flash the boot or recovery images.
I am presently on 2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_India_SEA_1.24.400.2_Radio_8998-002772-1712011153_release_519104_signed_2_4
Problem solved ... Tried it again after reboot and on a different USB port and it worked .. odd ..
I have a Honor 8/FRD-L14 (US model) which I purchased a couple months back. I decided I wanted to root it, so I unlocked the bootloader, installed TWRP (version 3.1.1-1 for FRD-L14) and magisk. To cut to the chase, a lot of my apps didn't work after restoring my backup so I thought I would start over from scratch.
So I had the brilliant idea to wipe all my partitions in TWRP, thinking it would be easy to restore from a blank slate. Nope.
I have obtained a copy of B389 (FRD-L14C567B389b) firmware, both update.zip and update_full_FRD-L14_hw_usa.zip. The first is about 1.3 GB, and the latter is 683 MB..
Here's what I can do:
1. I can unlock and "oem relock" the phone, using TWRP or stock recovery as appropriate.
2. I can boot into Huawei eRecovery, but it always reports "Getting package info failed". It's done this all along.
3. I can boot into TWRP, and attempt to sideload. If I try to sideload the larger "update.zip", it fails immediately. If I try to sideload the smaller "update_full_FRD-L14_hw_usa.zip", it fails at 50%. In both cases the display shows the following:
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Verifying current userdata...
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching userdata files...
Removing empty directories...
Unpacking data new files...
add link type file...
write radio image...
check_write_data_to_partition,write data error
[COLOR="red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from zip failed
[COLOR="Red"]Updater process ended with ERROR: 7[/COLOR]
4. I can "fastboot flash" system SYSTEM.img, boot BOOT.img, cust CUST.img, and recovery RECOVERY.img extracted from the UPDATE.APPs mentioned earlier.
5. HiSuite restore reports that my device is not supported, whether locked or relocked.
6. I have a 128 GB SDXC, and I have attempted to load the two UPDATE.APP files from the aforementioned zip files. Either UPDATE.app, whether placed at root level or in a directory called "dload", gives the same error when trying the 3-button flash function: "Software install failed!", always at 5%.
At no point have I been able to actually boot the OS. If I do not select one of the various recovery modes, the phone never progresses past the unlocked warning message with orange text. (If the phone is locked, it warns that it has "failed verification" with red text, but still won't proceed.)
It really seems like I must simply be doing something wrong here. Apparently I have all the tools I should need available and functional. And yet, I cannot restore the phone to stock firmware.
* Does anyone know what I'm doing wrong? And, does anyone know anything about whether I should be using some particular firmware version for this, and if so which one?
* Is the problem the /data directory? How do I repair/restore that?
marshaul said:
I have a Honor 8/FRD-L14 (US model) which I purchased a couple months back. I decided I wanted to root it, so I unlocked the bootloader, installed TWRP (version 3.1.1-1 for FRD-L14) and magisk. To cut to the chase, a lot of my apps didn't work after restoring my backup so I thought I would start over from scratch.
So I had the brilliant idea to wipe all my partitions in TWRP, thinking it would be easy to restore from a blank slate. Nope.
I have obtained a copy of B389 (FRD-L14C567B389b) firmware, both update.zip and update_full_FRD-L14_hw_usa.zip. The first is about 1.3 GB, and the latter is 683 MB..
Here's what I can do:
1. I can unlock and "oem relock" the phone, using TWRP or stock recovery as appropriate.
2. I can boot into Huawei eRecovery, but it always reports "Getting package info failed". It's done this all along.
3. I can boot into TWRP, and attempt to sideload. If I try to sideload the larger "update.zip", it fails immediately. If I try to sideload the smaller "update_full_FRD-L14_hw_usa.zip", it fails at 50%. In both cases the display shows the following:
4. I can "fastboot flash" system SYSTEM.img, boot BOOT.img, cust CUST.img, and recovery RECOVERY.img extracted from the UPDATE.APPs mentioned earlier.
5. HiSuite restore reports that my device is not supported, whether locked or relocked.
6. I have a 128 GB SDXC, and I have attempted to load the two UPDATE.APP files from the aforementioned zip files. Either UPDATE.app, whether placed at root level or in a directory called "dload", gives the same error when trying the 3-button flash function: "Software install failed!", always at 5%.
At no point have I been able to actually boot the OS. If I do not select one of the various recovery modes, the phone never progresses past the unlocked warning message with orange text. (If the phone is locked, it warns that it has "failed verification" with red text, but still won't proceed.)
It really seems like I must simply be doing something wrong here. Apparently I have all the tools I should need available and functional. And yet, I cannot restore the phone to stock firmware.
* Does anyone know what I'm doing wrong? And, does anyone know anything about whether I should be using some particular firmware version for this, and if so which one?
* Is the problem the /data directory? How do I repair/restore that?
Click to expand...
Click to collapse
I had written this guide a long time back. It didn't recieve any attention but holds true for your device. If you restore by rollback you can relock the bootloader with the "LOCKED" status rather than the "RELOCKED" which means your warranty won't be void.
Here's the guide:
https://forum.xda-developers.com/honor-8/how-to/restoring-relocking-bricked-frd-l04-t3666360
The only difference is download the rollback packages from this thread:
https://forum.xda-developers.com/ho...users-how-to-restore-downgrade-t3537433/page1
Sent from my Honor 8 using XDA Labs
Thanks for the response.
Is there any reason I should rollback to the version you discuss?
I looked at the backup I made before unlocking, and it was FRD-L14C567B391. So I downloaded this and have been attempting to use it.
Flashing the recovery.img and attempting to 3-button install UPDATE.app doesn't work. It does the same thing it's done all along: immediately stops at 5%.
If I attempt to sideload this I do get a new error (I'll share it when I get home).
BTW, is every android phone so fussy about this stuff? I will never consider this platform again after how unwilling it seems to do basic restore procedures -- not sure if that's just Huawei or all androids. Either way there's really no excuse -- just flash the damn software and try to run it.
marshaul said:
Thanks for the response.
Is there any reason I should rollback to the version you discuss?
I looked at the backup I made before unlocking, and it was FRD-L14C567B391. So I downloaded this and have been attempting to use it.
Flashing the recovery.img and attempting to 3-button install UPDATE.app doesn't work. It does the same thing it's done all along: immediately stops at 5%.
If I attempt to sideload this I do get a new error (I'll share it when I get home).
BTW, is every android phone so fussy about this stuff? I will never consider this platform again after how unwilling it seems to do basic restore procedures -- not sure if that's just Huawei or all androids. Either way there's really no excuse -- just flash the damn software and try to run it.
Click to expand...
Click to collapse
Nope this is only on Huawei phones. The reason I recommend the rollback process is because it helps you restore your phone to the state you bought it (Including a "LOCKED" not "RELOCKED" bootloader). A TWRP flash will get you on the stock ROM but future OTAs might be a pain and safetynet will not pass without Magisk. Using this method you will be on the right recovery and latest firmware with everything official. Also if you have warranty this method restores it.
On phones from Google, Samsung, etc restoring is insanely simple. Huawei doesn't encourage third party development.
Sent from my Honor 8 using XDA Labs