Ok so after getting 4.5.141 to load via motos update I attempted to root the phone. Which by all accounts looked like it worked however....
My phone does not appear to still be BL unlocked, and there are no apps in the list under superuser. I downloaded CWM and tried flashing then going into recovery and that fails even through prompted for SU by the apps it says it work etc.
Now I cannot even get into recovery via any method. Via CWM it errors with a message cannot boot 2 error then loads rsd mode. Via power on/vol dwn it just gives the android dude with ! in the triangle.
Ok so how do I fix this? I need to be able to root, unlock the BL (if even possible) and fix my recovery partition. (any command used from fastboot fails I suspect its still a permissions root issue)
Any help is appreciated.
NVM I fixed it.
I re-ran the unlock process what was funny is when I flashed the sbf to unlock the BL the screen immediately showed the "unlocked" in the upper left hand corner. When I went to do the fastboot oem unlock part it said already unlocked. (I tried this earlier and it kept failing I think cause I forgot the sbf.
I then went through the steps to re-root it, then re-flashed the newer CWM and now I am able to get into recovery etc.
Related
i have been searching these forums for the past few days and have come up dry.. i have an htc rezound and I want the OTA BUT i have perm rooted it and removed most (if not all) the bloat... how do i go about rebloat and relocking my phone? i have tried using cleantool and it keeps waiting for the phone or it just fails all over itself repeatedly
edit: i have it set to charge only, sync is off and closed, and it is in fastboot mode. I have also tried something I found on here which seems like it is very similar to cleantools with less functionality and it just says <waiting for device> indefinitely
twich12 said:
i have been searching these forums for the past few days and have come up dry.. i have an htc rezound and I want the OTA BUT i have perm rooted it and removed most (if not all) the bloat... how do i go about rebloat and relocking my phone? i have tried using cleantool and it keeps waiting for the phone or it just fails all over itself repeatedly
edit: i have it set to charge only, sync is off and closed, and it is in fastboot mode. I have also tried something I found on here which seems like it is very similar to cleantools with less functionality and it just says <waiting for device> indefinitely
Click to expand...
Click to collapse
There are a few different ways to do it. Easiest way I did it to make it foolproof, is flash stock recovery if your on a custom recovery and relock phone and run the RUU. It will put you back to stock and you can just download the OTA and update it, then Unlock and flash Amon Ra recovery and from the developer menu install SU and superuser to reroot.
If you need more instructions , just ask otherwise to me that was the easiest way.
P.S. Just be aware the internal SD card gets wiped after you unlock again so move anything off the internal SD to the external SD that you want to save prior to unlocking again.
I didnt take the ota, I used cons ota rom.. this was my steps for that
1) download rom from here http://forum.xda-developers.com/showthread.php?t=1467329
2) boot into recovery, flash rom....
here you can go two ways, if you dont want the new baseband, it will flash the ph98img and not do anything, if you want the new radios I will tell you how I did it, then tell you where you need to start if you wont want them.
3)perform nandroid
4)via adb (thing you used to unlock originally) fastboot oem lock YOU ARE NOW LOCKED.
5)boot into hboot it will flash the ph98img
6) Unlock bootloader (find the email with the unlock.bin code and follow those instructions)
7)Reboot phone
8)connect to pc, charge only usb debugging enabled
9)run one click root
Proceed with this if you get the mainver error ONLY otherwise if having wifi issues, proceed to step 13
10) after rooted follow this post http://forum.xda-developers.com/showthread.php?t=1467099 NOTE, op in the thread supplied his miscnew.img USE IT!
11)Read this thread http://forum.xda-developers.com/showthread.php?t=1459347&highlight=mainver it will explain how to get the ph98s to work.
11a) do the ph98 file thing to the ph98 img in amon ra to get it to flash in bootloader
12) after amon ra is restored, perform restore nandroid.
If wifi is not working, even if you dont have mainver issues do step 13
13) If having wifi issues as in not working go to this thread http://forum.xda-developers.com/showthread.php?t=1467793 and follow instructions EXACTLY!!!
Now you should be running new radios, hb2.11, the 2.6 kernel etc.
You will have to follow the post in step 11 to get any ph to work from now on.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, BURN YOUR HOUSE DOWN OR ABDUCTED BY ALIENS BY FOLLOWING THE ABOVE INSTRUCTIONS.
im having some trouble getting into recovery because clockworkmod says it does not have an officially supported recovery... how do i manually install one?
Assuming you installed a recovery, just boot to Hboot. Pull the battery, then hold the power button and volume down button. Once in Hboot you can choose Recovery.
twich12 said:
im having some trouble getting into recovery because clockworkmod says it does not have an officially supported recovery... how do i manually install one?
Click to expand...
Click to collapse
To flash a recovery do the above steps to get into hboot (power down, pull battery, hold volume down and power buttons) and once you are in hboot, choose fastboot. Then connect to your pc and in the pc cmd prompt type:
fastboot flash recovery nameofrecovery.img (name of stock recovery you need to download, trying to find a link for you...)
That will put the stock recovery on the phone, then you can run RUU to get the rest back to stock and you can then accept the OTA.
feralicious said:
To flash a recovery do the above steps to get into hboot (power down, pull battery, hold volume down and power buttons) and once you are in hboot, choose fastboot. Then connect to your pc and in the pc cmd prompt type:
fastboot flash recovery nameofrecovery.img (name of stock recovery you need to download, trying to find a link for you...)
That will put the stock recovery on the phone, then you can run RUU to get the rest back to stock and you can then accept the OTA.
Click to expand...
Click to collapse
got it! OTA and everything.. debating on rerooting for a bit thanks a lot everyone! +rep
All you have to do to reroot now is flash Amon Ra and then install su from within that. So it's super easy at this point.
su seems to have remained installed.... no root but su is definitely still installed! the only reason i am going to wait on rerooting is so i can learn more about it before i flash or anything
Yeah, it will show up in your apps but it doesn't work properly until you reinstall. I thought I had remained rooted but when I went to use Titanium Backup it couldn't get root access, then after I reinstalled su it worked fine.
But yeah, if you don't need it yet don't worry about it. The only good reason to do it is to use TiBU to save all your settings and if you have Amon Ra you can make a nandroid of your phone so that if something happens you have a backup image of everything and can restore it very easily via Amon Ra. You can still stay on stock ROM etc... the only thing you would need to flash is the Amon Ra recovery.
ya i see what you mean... I also want to get rid of this unbelievable amount of bloat... geez their are a ton of useless verizon apps never mind the stupid games
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.
So I am a first time rooter, so I'll try my best to use the proper terms and whatnot.
Anyways, I have an unlocked HTC One X+ that I am trying to root. I was using the AIO kit by Hasoon2000. I had my bootloader successfully unlocked, and so I proceeded to continue with rooting. I thought I pushed the SuperSU.zip to the device, because the cmd line said it was successful. So I booted into recovery mode, made a backup, and then when to flash the SuperSU.zip file. However, I could not find it in the file explorer in recovery mode.. so I went to push the file to the phone again, but now it says device not found. The only thing I can think that's happened is my USB debugging got turned off... which is bad. So is SuperSU.zip in my phone somewhere, or am I stuck with a phone that can only go into recovery mode?
Thanks for any help!
I have now similar problem too...
actually I had rooted successfully, but after many failed CM11 installation attempts, I decided to relock the bootloader, in order to update the Firmware. But it didn't work too and I came the way back again, in which I unlocked the bootloader with Unlock Token etc. again. Now the bootloader is unlocked but apparently not rooted!?! I can't push superuser via adb because **Device is not found** and I can only go to TWRP Recovery and bootloader...
COULD SOMEONE HELP??!
PS: when i press the reboot in TWRP, it says that "the phone seems not to be rooted, do you want to install the SuperUser? and when I accept it... it reboots only and nothing does change!
well... im not sure what I did differently but it finally recignized the device!! And now I managed to get everything installed... weird!
I got an evo lte. I unlocked, flashed recovery and rooted. I don't think the recovery or the root worked right. I was on 4.1, root checker showed rooted, but busybox wouldn't install and I couldn't flash ROMs.... Kept getting an unable to execute binary error. I relocked, flashed stock 4.3 sense 5 with ruu. Had no service, flashed again, phone works now with no noticeable issue. I went to unlock so I could flash recovery and root. But there's no boot loader menu, it only says "press power to reboot". Not sure what to do, maybe relock and run the ruu again?
Thanks
stupid
I had a pj75img file or whatever the exact name is. i felt stupid when I realized why.
Hi All,
I have unlocked my HTC M8 eye with the help of HTCDev site and installed TWRP from playstore. I restarted the phone and went into Fastboot mode and using adb installed TWRP image file for this phone (v2.8.0.3), before it I have saved SuperSU zip file on my local storage. From TWRP in recovery mode I installed SuperSU everything goes good and its shows Success. When I reboot I shows "Your device does not seems to be rooted? Install SuperSu now?" When I gave install now it shows error msg "Failed to copy su binary in to /system/bin/". I tried re-flashing it and tried to install some other versions of SuperSU but none worked. After this phone goes re-booting and stuck in HTC logo screen till I use shortcut keys to enter recovery mode. In Fastboot mode my laptop was able to detect my phone from command prompt and also my internal storage.
I believe I can get back my phone on working. Please help me, I really need my phone back .
If you can still get into recovery, then you can install a custom rom and go that route. Keep in mind, if you are just HTCdev unlocked and you flash a custom rom, you will have to use fastboot to flash the boot.img.
If that doesn't work, then you should be able to find the RUU for your phone and restore it to stock and redo the custom recovery and root. For future reference, just flash the SuperSU zip. TWRP doesn't normally detect that correctly and trying it's method often makes things worse, as you experienced.