Related
so I have the latest software, used the HTC unlock method, was rooted and had the TWRP recovery working just fine, I'm an idiot and flashed the CM recovery through RM and of course it didn't work, so I've tried every which way I can find to re-flash the TWRP and even tried flashing AMON but it will not go into recovery with any of them after it says it successfully wrote the recovery.
TWRP and CM just wait for a minute then reboot normal, AMON reboots then sits at the HTC screen... forever and i have to pull the battery.
I tried uninstalling RM to see if it was F'ing with it, didn't matter.
not sure what to try next to get a working recovery back onto the phone, I'm still rooted just running the stock ROM, I had loaded an alternate ROM successfully last week, just didn't like it. So I know all is 'working' as expected I just F'd up the recovery part now
any help??
afaik if you used the HTC unlock you need to fastboot flash it, or maybe hboot zip it? What have you tried so far?
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
morellox said:
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
Click to expand...
Click to collapse
*my opinion*
delete rom manager
boot into recovery using adb
"adb reboot recovery"
or terminal emulator
"reboot recovery"
or the app "quickboot"
does that work?
I've tried all those except Quickboot... *trying now......*
annnnnd
same thing with the app...
I'm thinking at this point I almost need to just write everything over again? use a flashable zip in the bootloader and just have it write everything over again, I was going to do a new rom anyways bored with the stock again.
so I need to find that I guess? re-write everything go back to fresh and start over
1. Make sure u r not flashing CDMA recovery over a GSM device, or vice versa.
2. How did u get ur device rooted in the first place?
3. Last resort, relock ur device and apply the correct RUU, then unlock and root again.
Sent from my HTC EVO 3D X515m using XDA App
1) good there
2) I followed a tutuorial where I pushed the recovery and the SU file after doing the HTC official unlock method, worked great at first, I'm the idiot that pushed the CM recovery over top of it and now I can't get a working recovery back on.
3) do I really have to relock first, I've seen the simple tutorial on doing so, I was hoping maybe I could find an all in one flashable ROM that would at least get me back to operational on all partitions and then re-work that one with a new ROM later or something, not possible?
This is of no help to you but - I had the same error. TWRP v1.0.3. I tried everything in the book to get it to work... but got stuck at the HTC splash screen like you. And I tried installing the 1.13 PG86IMG and then my device turned off while installing the PG86IMG (it was fully charged during flashing, I checked). Be careful with what you do.
I was unlocked with AlphaRev's tool, running my own ROM.
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
morellox said:
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
Click to expand...
Click to collapse
htc unlock method has proven to be a bit shady for the community in that it doesnt allow all the features/functions the revolutionary (and prior unrevoked) unlock method does.
most developers unlocked with revolutionary and haven't performed the htc unlock method so it has been hard to gather technical details on the htc unlock method.
one item we can eliminate in the effort to narrow down your issue: there is no working Amon RA recovery for the EVO 3D. not sure where you obtained Amon RA recovery. TWRP was created to pick up the torch from the Amon RA recovery as he retired from developing his recovery to support emmc devices.
stick to either flashing the twrp or cwm recovery images. there are only a handful of ways to load a custom recovery and only a handful of ways to boot the device into recovery mode.
i'd follow a logical pattern and work your way through the avaiable options. by following the available options one step at a time you should be able to narrow down which methods work and don't work. sorry it has been difficult as this htc unlock method is newer to the community we aren't as familiar with it as we are the revolutionary method.
ways to flash a custom recovery:
1) fastboot - fastboot flash recovery c:\downloads\recovery.img
2) bootloader - PG86IMG.zip file containing recovery.img and android-info.txt
3) flash_image - while in normal android mode (my app Flash Image GUI works well for this)
ways to boot into recovery mode:
1) turn device completely off and unplug USB. vol down + pwr loads bootloader. select recovery from the menu
2) from android mode: adb shell reboot recovery
3) from android mode: use a 3rd party app like quick boot.
this is all off the top of my head so it might not be an *exhaustive* list but it should cover all the common approaches. hope that helps and keep us updated! good luck!
damn...
I really appreciate everyone's help here I've been a part of various forums for a REALLY REALLY long time... from the days of Nextel, then I was a Palm Lover for a few years and now Android.
this obviously isn't urgent as my phone is working just fine, I just can't flash a new ROM since I can't get any recoveries working.
unfortunately I'm pretty sure I've tried all the methods listed above, I'm going to probably sit down sometime this weekend and systematically go through each method one more time just to be sure. TWRP worked for me just fine in the beginning, I flashed a ROM more than once, reverted back to my old ROM, made back ups, cleared cache's all the stuff I'd need to do.
thanks everyone, I'll keep trying
and no one knows of a flashable 'rom' that would have all the different partitions included in a zip or something like that? like.... what is in place of recovery in a stock phone? I can always unroot and start over but I did use the HTC unlock method so I hope that even works
got one to work! followed this method
http://forum.xda-developers.com/showthread.php?t=1239455
I’m extremely new to the Android community and I did do a lot of reading on how to unlock, install a recovery, and install ICS on my HTC Rezound. The problem I’m having is that I found an ICS ROM to install. I downloaded it, renamed it PH98IMG.zip, installed it onto my SD card through Clockworkmod Recovery, I then tried rebooting into the bootloader to get the zip file installed, but this is what happens in bootloader:
SD Checking…
Loading…[PH98DIAG.zip]
No image!
Loading…[ph98diag.nbh]
No image or wrong image!
Loading…[ph98img.zip]
And there’s a vertical progress bar on the right side of the screen that fills up, but then nothing happens after that. It goes back into the bootloader screen. Now my phone won’t startup at all, I get stuck at the HTC white startup screen. I can get into bootloader and Clockworkmod recovery, but nothing else works.
If anybody can please help me with step by step instructions I would really really really appreciate it. Thanks.
I should also mention that I followed a YouTube video on how to install ICS on my Rezound (I can't post a link of the video b/c XDA website won't let me).
The video had me unlock the bootloader, install CWM recovery, and install something called Ineffabilis-Deus-v1.0.1-Odex.zip. Everything up to this point worked just like the video (which is point 3:30 on the video). After that, nothing else worked.
I've ended up formatting the SD card from CWM recovery so now there's nothing on the SD card. Not even the PH98IMG.zip file. PLEASE PLEASE HELP!
If you still have ADB set up after you unlocked, here's whatchya do.
1. Unzip the P98 file.
2. Move the boot.img into your ADB directory.
3. Plug your phone into your computer.
4. Run CMD as administrator and type in the following commands
adb reboot bootloader
fastboot flash boot boot.img
Should work just fine after that. :good:
And I really hope you are at least using the modded CWM recovery from this post and elsewhere, you'll have issues if your phone fully drains otherwise:
http://forum.xda-developers.com/showthread.php?p=27517554
Worry about reflashing recovery on its own after you get the ROM up and running, just be sure you keep the phone charged. And consider AmonRa or TWRP recovery.
Chyrux said:
If you still have ADB set up after you unlocked, here's whatchya do.
1. Unzip the P98 file.
2. Move the boot.img into your ADB directory.
3. Plug your phone into your computer.
4. Run CMD as administrator and type in the following commands
adb reboot bootloader
fastboot flash boot boot.img
Should work just fine after that. :good:
Click to expand...
Click to collapse
YES! It worked! THANK YOU SO MUCH! Now to figure out how to get Amon Ra installed and uninstall CWM Recovery.
You can download Amon Ra from this post
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
rename img file to recovery.img and flash using fastboot as below
fastboot flash recovery recovery.img
fasheezy said:
YES! It worked! THANK YOU SO MUCH! Now to figure out how to get Amon Ra installed and uninstall CWM Recovery.
Click to expand...
Click to collapse
Dowload this: http://www.mediafire.com/?5yemc20dcnbr91c
Rename to PH98IMG and install via boot loader.
fasheezy said:
I’m extremely new to the Android community and I did do a lot of reading on how to unlock, install a recovery, and install ICS on my HTC Rezound. The problem I’m having is that I found an ICS ROM to install. I downloaded it, renamed it PH98IMG.zip, installed it onto my SD card through Clockworkmod Recovery, I then tried rebooting into the bootloader to get the zip file installed, but this is what happens in bootloader:
SD Checking…
Loading…[PH98DIAG.zip]
No image!
Loading…[ph98diag.nbh]
No image or wrong image!
Loading…[ph98img.zip]
And there’s a vertical progress bar on the right side of the screen that fills up, but then nothing happens after that. It goes back into the bootloader screen. Now my phone won’t startup at all, I get stuck at the HTC white startup screen. I can get into bootloader and Clockworkmod recovery, but nothing else works.
If anybody can please help me with step by step instructions I would really really really appreciate it. Thanks.
Click to expand...
Click to collapse
My Rezound has the exact same screen when going to the bootloader. I tried so very hard to avoid this but it must be done, I have to ask for help. I have no idea how to fix this phone. When trying to boot it gets all the way to the 4GLTE screen and stops, forever.
This phone is rooted with an unlocked bootloader, S-On, using Hasoon2000's AIO. It was working fine up until I did something stupid and loaded Motioncoding's Beats audio installer. (In case you're wondering I did this in an attempt to have the Beat's audio function while using Pandora, unfortunately this stopped the stock music player from functioning with headphones, I'm and idiot, I know...)
The problem occurred once I tried to uninstall the beat's audio installer using Root Browser Lite and deleting the system files they specified in the instructions. Apparently I deleted one to many and upon restart this is where I ended up. I have tried numerous fixes but the problem I keep running into is I cannot get access to Android via a USB connection on my PC. I still have access to the bootloader and to Clockworkmod Recovery but that is it. If someone can explain to me how to fix this it would really make me feel better and I promise I will never try to do something this stupid again. Thanks.
Board
Did you create a nandroid backup as recommended before trying any new mods? If not, reflash your rom in recovery/boot.img in fastboot, with only a system wipe. If so, restore your nandroid, if you don't boot then reflash a proper boot.img in fastboot.
Yeap snuzzo is spot on. I just wanted to add that it's not a big problem at all, not even something to stress about. We will help you get it fixed up. If you have the vertical loading var, there's a PH98IMG.zip file on the external sd card that you need to delete.
Since it was mentioned in the quote, make sure you aren't running the official clockwork mod recovery. Either run amon ra or fly halfs custom clockwork mod
Sent from my ADR6425LVW using xda premium
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...
I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.
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.