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
Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
Reason for this guide:
I have tried to go back to RUU and doing this with the RUU applications didn't work, the installation always failed. Because of that I was a bit afraid never to be able to get back to stock / RUU again
steps I did - i'm not sure if step 2 and 3 are necessary, but for me it worked like this
!!!DO NOT RELOCK the bootloader before Step 4 - this will brick your phone!!!
1. download RUU for your device here (check your radio at top the bootloader menu)
2. extract the RUU rom from RUU application
start the ruu application, even if it fails. also start the flashing process, nothing will happen here. search for the ruu logs, for me at c:\ruu_log. in the log (for me in line 191) is the path to the rom.zip that should get flashed. something in temp folder... for me the line looks like this:
"<T093343><DEBUG><CMD>fastboot -s HT1BMVMXYZ flash zip C:\users\raangu\AppData\Local\Temp\{1235}\{12345}\rom.zip</CMD></DEBUG></T093343>"
3. flash the needed images
in the rom.zip you will find a boot_signed.img, a system.img and a recovery_signed.img. flash all these images with fastboot.
In command line:
fastboot flash system system.img
fastboot flash boot boot_signed.img
fastboot flash recovery recovery_signed.img
4. relock the bootloader
In command line:
fastboot oem lock
5. install with RUU application
now run the RUU application again and follow the instructions.
You are back on RUU now!
Thankyou
"3. flash the needed images
in the rom.zip you will find a boot_signed.img, a system.img and a recovery_signed.img. flash all these images with fastboot.
In command line:
fastboot flash system system.img
fastboot flash boot boot_signed.img
fastboot flash recovery recovery_signed.img"
can u explain better this part...?? what does it mean "flash all these images with fastboot..??
P.S: i don't have any ROM.ZP file in my local\temp\ directory......only an empty directory....
What is your DeviceID?
I've the vodafone brand and the DevideID is "VODAP034".
I tried this guide to change ID but not work:
htcsensationforum.com/htc-sensation-rooting/general-changing-cid/
Any ideas?
THX Jaggy and Raangu
Thank you Raangu and jaggyjags for doing awesome job here.
I've questions regarding to RUU, if I want to flash RUU other then my device's Radio version or flash older RUU then my device's stock Rom,
will these brick my phone?
agv983 said:
"3. flash the needed images
in the rom.zip you will find a boot_signed.img, a system.img and a recovery_signed.img. flash all these images with fastboot.
In command line:
fastboot flash system system.img
fastboot flash boot boot_signed.img
fastboot flash recovery recovery_signed.img"
can u explain better this part...?? what does it mean "flash all these images with fastboot..??
P.S: i don't have any ROM.ZP file in my local\temp\ directory......only an empty directory....
Click to expand...
Click to collapse
Hi agv983,
with "flash all these images with fastboot" I mean the lines below:
fastboot flash system system.img
fastboot flash boot boot_signed.img
fastboot flash recovery recovery_signed.img
so you dont flash these things with cwm or something else. you do it with fastboot in command line.
did you take a look in the ruu_log? the path is written there.
PaXGeN said:
What is your DeviceID?
I've the vodafone brand and the DevideID is "VODAP034".
I tried this guide to change ID but not work:
htcsensationforum.com/htc-sensation-rooting/general-changing-cid/
Any ideas?
THX Jaggy and Raangu
Click to expand...
Click to collapse
Hi PaXGeN,
I'm not sure if this changes your Device ID
Maybe only for sensation?
mmtrt said:
Thank you Raangu and jaggyjags for doing awesome job here.
I've questions regarding to RUU, if I want to flash RUU other then my device's Radio version or flash older RUU then my device's stock Rom,
will these brick my phone?
Click to expand...
Click to collapse
Hi mmtrt,
I can't tell if it bricks your phone, but there are several RUUs for different Radio versions available. thought for each Radio there is also a RUU...
HI can u tell step by step how to install RUU i tried it but its failed
?????????
i did everything just the way you said but even after doing that i cant flash ma phone using RUU file "RUU_Pico_HTC_Europe_1.28.401.1_Radio_10.35d.80.09H_1.11.82.17_release_230964_signed" !!!!....
Ma bootloader details are :
"*** UNLOCKED ***
PICO PVT SHIP S-ON RL
HBOOT-1.03.0000
RADIO-1.11.82.17
Nov 29 2011,17:10:06 "
and yes i seriously wanna remove that "*** UNLOCKED ***" So that ma warranty doesnt go !!!!!! will this flashing remove that tooo??!!!!
And ma software no. is 1.31.720.3
can u post a link to RUU of above specification? !!
please reply soon!!!!
hussainali5005 said:
Hello there raangu,
i followed the steps in installing RUU , now i can not start my phone it is looping and i did everything and i can not get into recovery mode in my htc phone there is a phone icon and a red exclamation mark , please help me fix this i have no money to buy another phone please help me you are only expert in htc explorer and my only hope. please please
Click to expand...
Click to collapse
lol, dont worry, reflash the recovery as you did in the tutorial when rooting and install another rom
thanks raangu and jaggyjags for all the stuff u have been providing.....just wanted to ask some questions...
1)can i flash recovery_signed.img of other software version to my current version i.e. can i flash 1.10.720.2 recovery_signed.img to 1.13.720.3 to remove the chinese custom recovery which i have flashed....(i have not flashed any custom rom)
2)and when flashing as per the 1st post do i have to do a factory reset before the process to write the image file...please help....
3) does nandroid backup include the stock recovery file....please reply
thank you
@raangu i found the version of ruu required for me,i got the info in settings-->about phone-->software version.
please help....thank you...
I'm getting the log file but there isn't any zip.rom in the log file.
Any ideas?
cined said:
I'm getting the log file but there isn't any zip.rom in the log file.
Any ideas?
Click to expand...
Click to collapse
try this instead
1. Download the RUU.
2. Open the RUU exe file, and proceed until you get to the page which says 'View Readme'. At that point, stop.
3. Go to your TEMP folder (on Windows 7 it'll be something like : C:\Users\USERNAME\AppData\Local\Temp
4. Look for folders that have lots of characters in that format: "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}". One of the folders will contain two files, and another folder with the same "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" format. Open that folder.
5. In there, you will see either rom.zip or firmware.zip (depending on the device).
It says when trying to flash system.img,, date length too large
help me please
help me please
i don't understand this step
---- 2. extract the RUU rom from RUU application----
where i can find the RUU application??
PS: my phone is: HTC EXPLORER with jaggyrom, and i'd return to my stock rom.
i've downloaded my stock rom following this discussion--- http://forum.xda-developers.com/showthread.php?t=1569430
because your download link page wasn't running to me, but i think that roms are the same.
thnx
A total successful unrooting and reverting to stock
Warning dont flash any other rom before this step in order to retain factory status you have to maintain the default rom on which rooting was done
for those who want to revert to stock from jaggy or any other make a clockwork backup of your stock rom even if it is rooted
Step 1 : if you have messed up in previous posts by our friend dont be alarmed
make sure you have clockwork mod of your original rom backed up in sd card or in the computer copied from sd card
to do this go to the recovery option choose backup and restore in this select restore and select the backup you did with your stock rom
Step 2 : download these files ( also noted in my system the android sdk was in c drive root as c:\Android else make a fresh installation of the android sdk ) GIVEN BELOW AT THE END OF POST
Step 3 : on c drive paste these files in c:\Android ( if file not there in pc install sdk in this folder ) now open cmd from start menu
Step 4 : Execute commands
cd c:\Android
fastboot flash boot boot_signed.img
fastboot flash recovery recovery_signed.img
(fastbooting system .img mentioned in previous post is not required as it will conflict with the hboot and it too tiresome to get the sock back)
Final step : now with the stock boot and recovery of htc default signed just restart your cell phone and got to settings > storage >factory reset
Ta da your phone is unrooted now for the grand finale lock the HBOOT
execute command : fastboot oem lock
to lock the boot loader
now it will show relocked now at this stage if you got your factory default ruu matched with the software version of your phone in my case it was
V1.31.728.1
then flash that ruu and vola your phone is crystal clear no hboot relocked or no rooting ever shown.
Try it and press thanks if liked
I dont get this, sorry...
I have stock scandinavian rom on my Explorer, and I want to flash an european rom instead.
Ive go the European RUU, but for gods sake I cant get it installed...
I dont want to brick my girlfriends phone, its 1 month old, and I dont want to fiddle with too much.
Is there any way to simply flash the RUU with the bootloader?
prateek.maac said:
Warning dont flash any other rom before this step in order to retain factory status you have to maintain the default rom on which rooting was done
for those who want to revert to stock from jaggy or any other make a clockwork backup of your stock rom even if it is rooted
Step 1 : if you have messed up in previous posts by our friend dont be alarmed
make sure you have clockwork mod of your original rom backed up in sd card or in the computer copied from sd card
to do this go to the recovery option choose backup and restore in this select restore and select the backup you did with your stock rom
Step 2 : download these files ( also noted in my system the android sdk was in c drive root as c:\Android else make a fresh installation of the android sdk ) GIVEN BELOW AT THE END OF POST
Step 3 : on c drive paste these files in c:\Android ( if file not there in pc install sdk in this folder ) now open cmd from start menu
Step 4 : Execute commands
cd c:\Android
fastboot flash boot boot_signed.img
fastboot flash recovery recovery_signed.img
(fastbooting system .img mentioned in previous post is not required as it will conflict with the hboot and it too tiresome to get the sock back)
Final step : now with the stock boot and recovery of htc default signed just restart your cell phone and got to settings > storage >factory reset
Ta da your phone is unrooted now for the grand finale lock the HBOOT
execute command : fastboot oem lock
to lock the boot loader
now it will show relocked now at this stage if you got your factory default ruu matched with the software version of your phone in my case it was
V1.31.728.1
then flash that ruu and vola your phone is crystal clear no hboot relocked or no rooting ever shown.
Try it and press thanks if liked
Click to expand...
Click to collapse
could you direct me to the link. where you found the ruu v1.31.728.1
Dear Developers
I have successfully unlock & rooted my phone through htcdev..m having some bugs in my custom rom,i had recently update my rom from htc service centre before root it.sometime its restarts again n again so i need stock rom & guide to flash it so i can get back to my orignal rom...
plz do the needful
Custom ROM? You have SuperOSR or CyanogenMod?
You said something about "i had recently update my rom from htc service centre "..
What ROM do you have?
dear alex
i have stock rom andrid 2.3.5
software version-1.57.720.1
Then you don't have a custom ROM, lol
It's stock ROM, just reset your phone to factory data from Settings.
i know dat if i do factory reset then i got the stock rom....
i will get all application back those i had deleted like facebook system applications & All
munishjoshi said:
Dear Developers
I have successfully unlock & rooted my phone through htcdev..m having some bugs in my custom rom,i had recently update my rom from htc service centre before root it.sometime its restarts again n again so i need stock rom & guide to flash it so i can get back to my orignal rom...
plz do the needful
Click to expand...
Click to collapse
http://www.4shared.com/file/eJD86RlV/ruu_chacha_htc_asia_wwe_157707.html
there you go.. enjoy
how we cam flash it....i have S-ON
munishjoshi said:
how we cam flash it....i have S-ON
Click to expand...
Click to collapse
I'll try to help:
1. download the ROM from here:
http[:][doubleslash]alex.swtesting.ro[slash]downloads[slash]ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35.3033h_7.51.35.19_release_228383_signed[dot]zip
2. extract and copy the system.img to the same directory as your fastboot tools
3. enter the fastboot mode by pressing volume down + power button after the device has been turned off.
4. choose fastboot by pressing power button, and then connect your phone to your PC
5. using fastboot tools, run this command on cmd: "fastboot flash system system.img"
6. run factory reset on your phone fastboot menu...
wait until reboot, and in my case: voila, it brings all the apps back
does this support arabic? oh and can you identify which apk is responsible for the world countries when you try choose a location for worldwide clock? cause i deleted that it seems and have no idea which one it was. and if you know which one it is, if there's a link for it or if the link above, contains it.thanks
hararilmi said:
I'll try to help:
1. download the ROM from here:
http[:][doubleslash]alex.swtesting.ro[slash]downloads[slash]ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35.3033h_7.51.35.19_release_228383_signed[dot]zip
2. extract and copy the system.img to the same directory as your fastboot tools
3. enter the fastboot mode by pressing volume down + power button after the device has been turned off.
4. choose fastboot by pressing power button, and then connect your phone to your PC
5. using fastboot tools, run this command on cmd: "fastboot flash system system.img"
6. run factory reset on your phone fastboot menu...
wait until reboot, and in my case: voila, it brings all the apps back
Click to expand...
Click to collapse
I tried it.. but it is giving me Signature verification error. Need some help
hrishikol said:
I tried it.. but it is giving me Signature verification error. Need some help
Click to expand...
Click to collapse
does your boot loader have the tag **unlocked** ? only if it has unlocked tag you can install using fastboot else you get the error. unlock your bootloader, flash the zip/image, once done relock the bootloader if you need.
to unlock the bootloader using htcdev.. i need to update the software to 1.57.. and i am getting signature error ehile doing so using the patch provided earlier in the thread
hrishikol said:
to unlock the bootloader using htcdev.. i need to update the software to 1.57.. and i am getting signature error ehile doing so using the patch provided earlier in the thread
Click to expand...
Click to collapse
Yes you need to update your boot loader. Download the RUU from HTCDev. run the ruu and check for the rom.zip file in temp folder. rename the rom.zip to PH06IMG.zip and update the zip file through bootloader(power + volume key method). Then your bootloader will be updated. Revert if any errors.
Dont use the patch, try the official version. It will work.
Hi hrishikol ,
i did a deodex to my phone app and now the chacha is stuck at the HTC logo,
can you please give me ideas on how to solve this problem?
i have installed CWM,in order to flush a ROM ,
but it is not functioning properly
The Guides above are 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.
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
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.
still was getting bootloop ... then i cleared cache, full wipe and cleared davlik ... then it magically booted
thanks all
raymerjacque said:
The Guides above are 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.
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.
Click to expand...
Click to collapse
I have S-OFF but it seems like every Clockwork Recovery that I download doesn't work. If I do it through the PC on Fastboot, it says "Can't load IMG." and if I try to load it through through the Bootloader on the Phone, it says "Wrong image". Plus there are so many recovery images floating around, I have no idea which is the right one.
Try following instructions. Works every time for me.
Kevc44485 said:
Try following instructions. Works every time for me.
Click to expand...
Click to collapse
Thanks but I would have liked some real help. Anyone else please?
trufan1 said:
I have S-OFF but it seems like every Clockwork Recovery that I download doesn't work. If I do it through the PC on Fastboot, it says "Can't load IMG." and if I try to load it through through the Bootloader on the Phone, it says "Wrong image". Plus there are so many recovery images floating around, I have no idea which is the right one.
Click to expand...
Click to collapse
You could try EXT instead. Part I to install the recovery. Part I & Part II to install EXT & 3.32 firmware.
PART I: Flashing 4EXT recovery touch
To dowload and install the newest version of 4ext recovery TOUCH (v1.0.0.5 RC3). Use one of the following methods provided:
Third method: Download this file, check the MD5 of the zip and install it following the steps 4 and 5 from post#1 in this thread.
NOTE: File used in third method WILL NOT install the needed 3.32 firmware in any way, only contains the recovery.img to flash 4ext recovery touch.
PART II: Updating the firmware
This step is MANDATORY otherwise your ROM will not boot.
After updating the firmware you will have the 3.32 firmware with unlocked bootloader. Which basically means that you can use advanced fastboot commands, such as: flash new radios and splashscreens
Download compatible firmware from here.
Copy the PG58IMG.zip file you've downloaded to the root of the sdcard. Root of the sd card mean that you can't put the file inside any folder. Also, you can't rename the file. Please keep the PG58IMG otherwise the bootloader won't recognize it.
Power off your phone or remove the batt and put it back again.
Hold volume-down + power button to boot into the bootloader
Wait for the firmware package to be found and confirm to update as prompted
Once it completed successfully and prompted you to reboot, pull the battery out.
Connect your SD card to the PC and remove the PG58IMG.zip file.
Quoted from here
.
Click to expand...
Click to collapse
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
prestonmcafee said:
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
Click to expand...
Click to collapse
By a generic system image, you are referring to wanting to install an aosp image (treble ROM), correct?
Yes.
prestonmcafee said:
Yes.
Click to expand...
Click to collapse
And obviously you still have your bootloader unlock code?
Also what Mate 9 version do you have and what exact firmware is it running?
I can help ya out no problem. Just obviously want to make sure you avoid going through that again
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Sorry, MHA-L29 8.0.0.360 (C567)
prestonmcafee said:
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Click to expand...
Click to collapse
Oh...You're already bootloader unlocked that makes it even easier.
I'm using the system.IMG form the thread below this paragraph. Tried a few different aosp ROMs and it seems to be the best so far. Aside from a couple things of course. And the honor 8 Pro is the same CPU, GPU found in the mate 9.
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564.
In the main post of that thread, just follow step 2 and 3 and you'll be good to go for having an aosp ROM.
As for magisk/root... You can follow my guide below that I posted the other day. Just let the aosp ROM boot up once first. Also I can extract the ramdisk.IMG you'll need if you can't once you check it over.
https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Basically in a nutshell to get setup on an aosp ROM is as follows
1 Download the ROM from the first thread i posted
2 Extract the system.img to where your adb folder is
3 Run command prompt from there
4 With your phone powered off. Hold the volume up button and connect it to your computer (fastboot screen)
5 Run command fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset
8 Reboot the phone and should be good to go
Need to do first boot on its own before rooting
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
prestonmcafee said:
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
Click to expand...
Click to collapse
Yeah, fairly happy about it. A few bugs though but nothing major. Get better standby drain and about the same SOT time as EMUI. The only thing that is lacking is the camera in aosp doesn't use both cameras.
There is the stock camera port (works with magisk) but it's lacking a few things like video recording doesn't work... And umm not sure what else.
I needed to install an update, enable developer options and enable OEM unlocking (which was greyed out) before it would install. Here is my earlier post:
Dang, didn't work. Here is what I did.
-reset phone, but did not enable developer options.
-extracted and placed system.img in the minimal fastboot and adb folder. Ran a command prompt with administrative rights (win 10)
-shut off and connected Huawei mate 9 by USB, holding vol up
-vol up brought the EMUI restore screen. Shut off and tried again, same outcome. So shut off and tried vol down, and that brought up the fastboot screen. It reported phone unlocked but FRP locked.
-ran command "fastboot flash system system.img" and get:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 11.167s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 11.183s
I suspect this is due to the FRP locked condition.
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
prestonmcafee said:
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
Click to expand...
Click to collapse
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
OK, now that I have it up and running, here is the procedure I used, fixing what are either typos or variations because my system was slightly different. I unlocked the bootloader using instructions from:
http://www.teamandroid.com/2017/04/08/huawei-mate-9-unlock-bootloader/
I used Minimal ADB and Fastboot from
https://forum.xda-developers.com/showthread.php?t=2317790
I downloaded and extracted the system image from the link Wirmpolter provided:
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564
Here is a slightly edited set of instructions that worked for me:
a. unlock bootloader
b. reset phone
c. enable developer mode (settings/system/about phone tap on build number until developer mode is enabled), enable OEM unlock and USB debugging
d. check that FRP unlock and bootloader unlock worked by booting into fastboot screen (for me, hold VOL DOWN while booting)
1 Download the ROM from the thread above
2 Extract the system.img to where your adb folder is
3 Run command prompt from there (or use MA&F's desktop icon, which does the same thing)
4 With your phone powered off. Hold the volume DOWN button and connect it to your computer (fastboot screen)
5 Run command: fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset [eRecovery didn't have this option, so I rebooted a couple of times while holding vol up and it eventually gave me the option to factory reset]
8 Reboot the phone and should be good to go
Up and Running!
Wirmpolter said:
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
Click to expand...
Click to collapse
I'm up and running. Thanks! So far, the only glitches are:
While Android can see and format the SD card (a Samsung 64GB), the SD card is invisible over a USB connection and Google Maps and my music player can't see it. File explorer and copy files to the SD card, so the SD card works.
The camera is terrible, but you have a fix for that.
I'm quite lost about how to install Magisk and a camera module
At the risk of asking too much, I have another request. I'm looking at how to install the stock camera on my Mate 9 with the AOSP, and here is my pathetic understanding of the steps.
First, I looked at your (Wirmpolter) instructions:
1. Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/app...mless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
2. If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
3. Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Here are some questions:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager -- this is an android app? Do I sideload it?
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Finally, the camera image is here:
https://forum.xda-developers.com/showpost.php?p=75848917&postcount=2
It isn't clear to me how to flash using Magisk, but perhaps that will be obvious once I have magisk operating.
prestonmcafee said:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
Click to expand...
Click to collapse
Firmware Finder (they have Windows desktop and Android apps for it, and there's also http://pro-teammt.ru/firmware-database/ which does the job just as well, though it's all in Russian.)
Find the FullOTA-MF firmware that corresponds to your model, download the 'update.zip' that goes with it - on the website, it's under the link 'update' in the same row. If you do it on your phone in the Firmware Finder app, hit "Download" on the relevant detail screen and it'll prompt you for which files you want.
Once you've got the update.zip, extract it, you'll find a file UPDATE.APP, which is what the extractor wants. If it throws up an error, disable CRC checking of the extracted content. (I don't recall what the label for it is and I don't have it installed on the machine in front of me...); and yes, you'll want RAMDISK.img from it.
prestonmcafee said:
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Click to expand...
Click to collapse
Magisk Manager wants to create a patched ramdisk image. When it updates, it'll want to update the ramdisk image on your device (which it'll be able to do since it's running with root privileges itself anyway), but for the first pass, it needs that image provided and for you to manually flash it.
Thanks!
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
prestonmcafee said:
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
Click to expand...
Click to collapse
The magisk manager app apk you just run on your phone to install it, no side loading required.
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
That worked
prestonmcafee said:
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
Click to expand...
Click to collapse
That seems to have worked.