Thanks to everyones help I was able to get 320 updated, then OTA 321 came without issue. Now I am trying to re-root and having no luck. (And please let me know if this is the wrong section, but I see all the rooting questions in this one.)
Followed the steps someone posted in the thread "How does one get root again once upgraded to 5.1?":
• Phone was still unlocked but I went through the steps and clicked ‘ROOT’ in the software tool anyways (and got no errors).
• Downloaded and renamed and moved the TWRP Recovery from the link in those steps (and later tried with twrp-2.8.7.0, to the same end).
• Found my phone listed in the “adb devices” list in command prompt, unplugged, ran ‘fastboot flash recovery TWRP.img’ from that folder, booted into recovery, plugged it back in and it successfully finished on the computer screen (nothing showed up on the phone).
• Rebooted into TWRP (Up and power) right from that recovery screen, and it boots to the EMUI screen asking me to navigate with up and down through “Reboot system now”, “Wipe data/factory reset”, etc.
All drivers are the same as when I rooted my phone on this same computer 2-3 months ago and again 2-3 weeks ago before I upgraded to 5.1, but just to be sure, I rechecked my ADB drivers, fastboot files, and confirmed it sees this as a fastboot device when in recovery… it just wont boot into TWRP so I can put supersu on.
Not sure if I am doing something wrong, if something is different in B321, or if I should try some of the alternate rooting methods (Shuame or whatnot… I’ve never tried them). It's the last step, and I can be happy and get back to where I was.
I have tried flashing that TWRP file a dozen times… and it works every time, but then it boots to the stock EMUI every time. I heard someone once say that the phone could be overwriting it? But I am booting into it, or trying to, right from the recovery screen. Of course I tried rebooting into the phone normally a few times as well, then restarting and going into ‘Up + Power’, every time the same thing.
Appreciate your suggestions.
try rename a file detailed here:
http://forum.xda-developers.com/showthread.php?p=62380255
xordos said:
try rename a file detailed here:
http://forum.xda-developers.com/showthread.php?p=62380255
Click to expand...
Click to collapse
That looks almost like my issue. However, I don't believe I understand your post entirely.
So you were unable to get TWRP to stick? I am unable to even get there once.
1. I don't understand how to rename that file.
2. Your steps say I have to get into TWRP, then "install SU.zip inside twrp". Since I cannot get into TWRP, I cannot get to step 2, and I cannot get to step 3, renaming the file.
Beggars can't be choosers, but could you dumb it down for me just a smidge? Can I get into any place on the phone or from my Windows PC to change this file name to make it work?
save the SU.zip from that post to your sdcard.
then run this cmd after goto bootloader:
fastboot boot twrp.img
Note is cmd is different from the regular flash cmd.
this will boot into twrp, then install the SU.zip you just downloaded.
This way, when you boot into OS, you will have full supersu completely installed. Now your phone is rooted, and you can use root browser or anything you like to rename the file.
xordos said:
save the SU.zip from that post to your sdcard.
then run this cmd after goto bootloader:
fastboot boot twrp.img
Note is cmd is different from the regular flash cmd.
this will boot into twrp, then install the SU.zip you just downloaded.
This way, when you boot into OS, you will have full supersu completely installed. Now your phone is rooted, and you can use root browser or anything you like to rename the file.
Click to expand...
Click to collapse
So perfect; so simple. Thanks!
Now rooted... I'll go rename that now.
I went to /firmware/image/update, and renamed update.app to updatex.appx. Rebooted with Up+Power, and TWRP is there by default.
Related
Hi everyone
I am having this weird issue with my T-Mobile G2... I am still on clockworkmod recovery 2.5.1.3 I don't know why and it is preventing me from doing everything! In the beginning I didn't notice I was on this version because in Rom Manager it appears to be in 3.0.? but when I reboot in CWM recovery I still have the green letters and the older version... The thing is that I am using right now CM7 and I am having problems with file formats, mounting system, etc. I have tried to S-Off my phone with a tut here with no luck.
About the root method, I don't even remember which one I used to root my phone because I was new when I did it and I just followed tuts around the web. Only thing I remember is that I used the first perma root method available by the time and it wasn't S-Off or carrier unlock.
The point is, I need to update to clockworkmod 3.0 or 5.0 in order to solve all the issues with my phone! I can't even do a nand at the moment because of this. What do you recommend?
Appreciate any help.
Solution in a post below.
If your having trouble getting ROM Manager to flash your recovery, this is how to do it manually through ADB.
1. Download this file here.
2. Rename the file to recovery.img
3. open a command prompt/terminal window and navigate to the location that you saved the file to. c:\path\to\recovery.img
4. type adb reboot bootloader
5. once booted into fast boot, back in the cmd prompt/terminal type fastboot flash recovery recovery.img
when its done reboot and then back in cmd prompt/terminal type fastboot reboot.
after reboot type adb reboot recovery and you should boot into clockwork. Make a nandroid and go find a custom rom.
I followed step by step but still showing version 2.5.1.3 and still having green letters.
Ok got it solved. Here is what I did:
The problem was that I had the wrong hboot installed which left my cellphone with S-ON and furthermore blocked me from doing anything. What you have to do if you have the same issue is to follow first this tutorial http://forum.xda-developers.com/showthread.php?t=1178912 to downgrade to stock rom, and then you have to re root the system following this tutorial http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
That's it! Good luck
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app
Here is a simple, easy guide to install a custom recovery and root your device after achieving S-Off using the RevOne method.
**Moonshine installs all the SU/busybox binaries needed for root. So if you merely want a custom recovery you can follow this guide up to Step 7.**
Takes less than 5 minutes and is really easy. First, go to one of these threads and download either classic or touch CWM CWM Recovery or TWRP if you so prefer TWRP Recovery
Step 1. Rename recovery file recovery.img *Note: If using Win7 or 8 it hides known file extensions by default. Take care to not rename the file to "recovery.img.img"*
Step 2. Move file to your folder containing fastboot.exe on your computer
Step 3. Make sure phone is plugged in to USB port and USB debugging is turned on.
Step 4. Open a command prompt and type in: adb devices
Step 5. If device is listed type: adb reboot bootloader
Step 6. Using the command prompt, cd to the directory that has your fastboot.exe and recovery file *example: cd C:\sdk\
Step 7. Once in the bootloader type: fastboot flash recovery recovery.img
Step 8. If everything goes as it should, the recovery should be installed. On the bootloader screen you are currently on navigate to and select the BOOTLOADER option. Once it takes you to the new screen, navigate to and select RECOVERY
Step 9. Once it boots into recovery, select reboot now. It will prompt you to root the device. Select Yes.
Step 10. Phone will reboot. You now have a custom recovery and are rooted. Go to the play store and download either SuperUser or SuperSU. I prefer SuperSU, but it is entirely up to you.
Click to expand...
Click to collapse
Enjoy!!
Really nice guide. Thanks for writing this. It's also exactly the same steps one would use for TWRP, if someone is wondering about that. Just use the TWRP file and rename to recovery.img.
Sent from my HTC6435LVW using Tapatalk 4 Beta
I've done this a 100 times but for some reason I'm getting the error "error: cannot load 'recovery.img'".
What's going on?
I did the RevOne method yesterday.
Edit, it happened with both CWM and TWRP.
After the RevOne method, my phone says **UNLOCKED** and S-Off, however is it possible that I'm not Unlocked?
Edit 2, what's really weird is that last night, I used the "All-in-one Toolkit" to flash the TWRP recovery and it worked just fine. I'm actually in the TWRP recovery right now. And then once I rebooted from recovery, it did NOT ask me to root/install SU.
arozer said:
I've done this a 100 times but for some reason I'm getting the error "error: cannot load 'recovery.img'".
What's going on?
I did the RevOne method yesterday.
Edit, it happened with both CWM and TWRP.
After the RevOne method, my phone says **UNLOCKED** and S-Off, however is it possible that I'm not Unlocked?
Edit 2, what's really weird is that last night, I used the "All-in-one Toolkit" to flash the TWRP recovery and it worked just fine. I'm actually in the TWRP recovery right now. And then once I rebooted from recovery, it did NOT ask me to root/install SU.
Click to expand...
Click to collapse
Do you use Win7 or 8? By default it hides known file extensions. So if you renamed it to "recovery.img" it might actually be "recovery.img.img".
Also I believe the all in one kit installs the SU binaries for you... I wouldn't know as I don't use one clicks or kits.
Phaded said:
Do you use Win7 or 8? By default it hides known file extensions. So if you renamed it to "recovery.img" it might actually be "recovery.img.img".
Also I believe the all in one kit installs the SU binaries for you... I wouldn't know as I don't use one clicks or kits.
Click to expand...
Click to collapse
Wow!
Why didn't I think of this? (I guess the frustration from last night trying to figure out why RevOne wasn't working.)
Thank you. This worked!
Fixed broken link.
Does this method erase all data? Sorry, just got my DNA yesterday
It erases nothing
Phaded said:
It erases nothing
Click to expand...
Click to collapse
Thanks, I'm dumb. Didn't realise it needed S-Off first (of course) which (at least the methods i've found) require a wipe.
Recovery Worked Great!
Worked Great!
Thank you
Use Runrummer for s off does not wipe
miggy_2602 said:
Worked Great!
Thank you
Click to expand...
Click to collapse
nice write up, extremely useful for noob:laugh:
Ok I type in fastboot flash recovery recovery.img and it just says "waiting for device" Looking at my phone it says Tampered/Unlocked S-OFF. Am I missing something?
when I flash recovery through
fastboot flash recovery recovery.img
I get the attached error. Is something wrong ????
also attached bootloader screenshot
thanks
You're not s-off or unlocked...
Ok... This is my 4th android phone.. And I love this phone... And only had it for a week.... and just now got it bricked.... here's what happen... Today I tried to flash a sense 4.1 rom, but im so new at this, and I'm half way done, and I went in a rush because I was nervous, and I accidentally press "install and keep data" and that was my mistake. I factory reset it b4 so I tried to flash it... So I thought it wouldn't be a problem. So I waited till the phone finish flashing. And when I rebooted the phone.... Nothing happened, just stuck on the white screen.... vibrating and etc... And I tried to restore all my data in clockworkmod recovery like I never even tried flashed it.. and it kept saying "won't mount sd card" and I tried to clear my cache/dalvik-cache, and like it still wont fix the issue. I even tried to restore wat I backup b4 I tried to flash it... and It was gone!!! Even my windows 8 laptop won't even detect my resound nor my sd card(unless its on a different android). But How can I fix my Rezound?!? plzzzz How can I fix this soft bricked issue? pllzzzzzzz help!!!
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
xkjonathanxk said:
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
Click to expand...
Click to collapse
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
@acejavelin
acejavelin said:
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
Click to expand...
Click to collapse
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Multidex24 said:
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Click to expand...
Click to collapse
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Dont know how to work ubuntu.. help again
acejavelin said:
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Multidex24 said:
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Click to expand...
Click to collapse
For the things you need to do, its not much different than Windows. Download and install adb, copy images to same places, and the commands are pretty much the same. If you can dualboot you obviously have some knowledge of such things.
If this is all do difficult, just grab a thumb drive, put mini-adb, recovery.img, and your ROM on it and go to a buddies computer with Win7 for 20 minutes and get it done that way.
I know this seems like a huge, potentially fatal problem, but it is minor...
Another thought I had... Download TWRP, go into CWM recovery and copy the TWRP file and ROM to the sd card, and FLASH TWRP recovery ZIP with CWM recovery, reboot into recovery and you will then be on TWRP and you can use TWRP's HTC Dumlock to flash the ROM and the boot.img without a PC at all... In theory, it should work.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.