I rooted using ioroot12 and tried installing recovery using both play store CWM installer for D800 as well as a manual install using the method shown in a thread in the D800 development forum. Both methods appear to install successfully but when I reboot to recovery I get a black screen (can tell black light is lit though) and nothing else. Holding the power eventually reboots phone back into the stock os. When in the broken recovery status and connected to computer via USB I get a slew of drive letters all prompting to format.
I'm guessing those are all the directories on the phone which are formatted android fs?
Any ideas what is happening? ioroot12 contains some changes to be compatible with the latest OTA, maybe the stock recovery file structure changed a little after the OTA?
arie001 said:
I rooted using ioroot12 and tried installing recovery using both play store CWM installer for D800 as well as a manual install using the method shown in a thread in the D800 development forum. Both methods appear to install successfully but when I reboot to recovery I get a black screen (can tell black light is lit though) and nothing else. Holding the power eventually reboots phone back into the stock os. When in the broken recovery status and connected to computer via USB I get a slew of drive letters all prompting to format.
I'm guessing those are all the directories on the phone which are formatted android fs?
Any ideas what is happening? ioroot12 contains some changes to be compatible with the latest OTA, maybe the stock recovery file structure changed a little after the OTA?
Click to expand...
Click to collapse
i repeatedly tried over and over after the ota.... it wont work you have to go back to stock reset. root then install twrp or cwm. twrp worked for me and cwm messed up my device causing a complete wipe of everything including logos and everything just a black screen that wouldnt power on. 30 minutes later it booted back up??? be careful.
Thanks
podagee said:
i repeatedly tried over and over after the ota.... it wont work you have to go back to stock reset. root then install twrp or cwm. twrp worked for me and cwm messed up my device causing a complete wipe of everything including logos and everything just a black screen that wouldnt power on. 30 minutes later it booted back up??? be careful.
Click to expand...
Click to collapse
Thanks, probably saved my phone from certain destruction. I followed the steps to go back to stock and successfully rooted and was able to install custom recovery finally.
I seem to recall the OTA taking a long time for being so small, I wonder if they played with partition sizing or something on the "o" firmware.
arie001 said:
Thanks, probably saved my phone from certain destruction. I followed the steps to go back to stock and successfully rooted and was able to install custom recovery finally.
I seem to recall the OTA taking a long time for being so small, I wonder if they played with partition sizing or something on the "o" firmware.
Click to expand...
Click to collapse
i only seen that the att apps were updated after the update as well as a security update tightening up their security for their bootloader.as far as partitioning uncertain on that.
glad it worked for you.
I spent a few hrs last night into the am trying to root and flash a working recovery. Just realized my phone auto updated to the OTA and, think I need to go back to the pre-ota. For whatever reason, I can't get twrp to update, no matter how I try to flash it.
Sent from my LG-D800 using Xparent Red Tapatalk 2
bzmotoninja83 said:
I spent a few hrs last night into the am trying to root and flash a working recovery. Just realized my phone auto updated to the OTA and, think I need to go back to the pre-ota. For whatever reason, I can't get twrp to update, no matter how I try to flash it.
Sent from my LG-D800 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I got mine to root using ioroot 12. I got twrp by usint freegee app. The only thing is my recovery is 2.6.3.0. Trying to figure 9ut how to get a newer version of recovery now.
Sent from my LG-D800 using XDA Premium 4 mobile app
Check with the guys on the webchat If you get stuck. I gotta flash pre-OTA personally. Something that I flashed stuck and won't let twrp update.
Sent from my LG-D800 using Xparent Red Tapatalk 2
bzmotoninja83 said:
Check with the guys on the webchat If you get stuck. I gotta flash pre-OTA personally. Something that I flashed stuck and won't let twrp update.
Sent from my LG-D800 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
If you're on 10o now, try using FreeGee from the Play Store, as mentioned, to get twrp installed.
heres what youre failing to realize..... with 2.6.3.0 I cant flash anything other than, nothing. Everything fails..... I cannot upgrade to the later versions of twrp, any way shape form or fashion. thanks tho
btm fdr said:
If you're on 10o now, try using FreeGee from the Play Store, as mentioned, to get twrp installed.
Click to expand...
Click to collapse
I couldn't get the 10o OTA to install but I used FreeGee to install TWRP and it was incredibly easy/simple. I've seen a few people now that have said they were also able to flash TWRP after upgrading to 10o using FreeGee as well.
fountain79 said:
I got mine to root using ioroot 12. I got twrp by usint freegee app. The only thing is my recovery is 2.6.3.0. Trying to figure 9ut how to get a newer version of recovery now.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have TWRP installed already you can just boot into recovery, flash a new TWRP or CWM recovery zip and then go to the "Advanced" menu and select Reboot>Recovery to boot into recovery again and you'll be in the new recovery you just flashed.
I tried that like 30 times over the last 2 days. I finally got flashtool to go back pre ota and now I'm running PA and have 2.6.3.3 for twrp. My reason for things not working is, I think that when I flashed something, it stuck making the code all jacked. Please next time, don't ASSume that because its supposed to work that it always will. There will always be human error.
Sent from my LG G2 using Xparent Red Tapatalk 2
Related
hi im new to the whole nexus 7 scene just got it today and its also my first nexus device. came from a highly locked down dx2 then to htc and now im trying this. i used the nexus root toolkit v1.5.5 to unlock and root and flash custom recovery. but when i hold power down+volume down i get into the boot loader and i choose recovery then GOOGLE splash screen comes up and it does absolutly nothing while no usb chord plugged in. with usb chord it stays at the google splash screen for but a moment then just boots into android.
i tried the advance utilities and flash the cwm that way but same results. im still on 4.1.0 jrn84d. what am i doing wrong? i don't fully understand adb so if there is quite litteraly a step by step please give me a link or write it down if no such link exists. my last hdd that had adb all setup and ready crashed so its not setup and i was talking to someone who helped me get it going. all i know is i need to use command prompt but getting it into adb and then using it to push and get into cwm i have no clue.
i would love to make a nandroid and then install a kernal to gget the full power out of this thing. it is unlocked and rooted already.
They using ROM Manager app to install CWM and also boot into recovery. Will work for sure as long as you're rooted.
Sent from my SPH-L710 using xda app-developers app
dante32278 said:
They using ROM Manager app to install CWM and also boot into recovery. Will work for sure as long as you're rooted.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you follow the steps correctly, it should have a custom recovery installed. check if your rom is actually rooted.
EDIT: What the hell are you doing on 4.1.0? I thought factory stock was 4.1.1.
Use this:
http://forum.xda-developers.com/showthread.php?t=1809195
Get GooManager from the play store. It can download and install TWRP recovery which I prefer. GooManager will let you reboot into recovery too.
Sent from my Paranoid Nexus 7 using XDA Premium
cakessi said:
EDIT: What the hell are you doing on 4.1.0? I thought factory stock was 4.1.1.
Use this:
http://forum.xda-developers.com/showthread.php?t=1809195
Get GooManager from the play store. It can download and install TWRP recovery which I prefer. GooManager will let you reboot into recovery too.
Sent from my Paranoid Nexus 7 using XDA Premium
Click to expand...
Click to collapse
lol i dunno just came with it. its the 16gb version dunno why it came with 4.1.0 but it did. and when i installed rom manager i flashed cwm with that then choose to boot into recover that way and it worked. i am unlocked and rooted and now have a nandroid. have yet to try going to cwm with power+volume down being pressed i will give it a shot later on and make another nandroid before i accept the update im being propted for.
ty guys for the help.
There was a bug that required the N7 to be connected to a PC-USB connection before it would work. They didn't fix the bug until 4.1.2.
Your best bet, if you can boot into Android, is to download a Reboot-to-Recovery app or use CWM or GooManager to reset into recovery. If you are boot looping, throw a USB connection into the mix when trying to do it. I believe it is VolDown+Power+USB connection. Drivers may also be a factor.
Thanks for the reply. I finally updated it. Had to do three updates though. First to 4.1.1 then to 4.1.2 and then to 4.2. I have a nandroid at 4.1.0 so if I need to do anything I'm just going back. I used ota root keeper and the cwm that's from rom manager allows you to choose to protect your custom recovery as well as root. But I don't know if that was working in tandem with ota root keeper since I made sure to back it up first before I did anything.
Sent from my Nexus 7 using xda app-developers app
I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.
Anyone figure out how to root the new OTA? It wont allow root with the old flash way since its new OTA
timenewton said:
Anyone figure out how to root the new OTA? It wont allow root with the old flash way since its new OTA
Click to expand...
Click to collapse
Yes use the new IOROOT15 to root the device. But I have been unsuccessful in flashing any roms, however I did get twrp to work with FreeGee app in the android market.
I appreciate your help very much, thank you
jea508 said:
Yes use the new IOROOT15 to root the device. But I have been unsuccessful in flashing any roms, however I did get twrp to work with FreeGee app in the android market.
Click to expand...
Click to collapse
What version of twrp? Sounds like you may need to update.
Sent from my LG-D800
btm fdr said:
What version of twrp? Sounds like you may need to update.
Sent from my LG-D800
Click to expand...
Click to collapse
Im still using the twrp that was flashed with freegee. i'm a newb to all this. Maybe i should flash new version of twrp and try. I was trying to install the mal 4.2.2 rom and just got lg screen, then black.
jea508 said:
Im still using the twrp that was flashed with freegee. i'm a newb to all this. Maybe i should flash new version of twrp and try. I was trying to install the mal 4.2.2 rom and just got lg screen, then black.
Click to expand...
Click to collapse
I've been unsuccessful in getting any roms to work. I tried 4.2.2 rom and got lg screen then black, had to restore nand backup from twrp recovery but it was hellish to get into, had to do the hold vol+pwr precisely, almost gave up. So, reverted to a backup just fine.
Next tried to loki_flash recovery 2.6.3.1 (then was going to do them in order-2.6.3.2>2.6.3.3 [have not tried going directly to 2.6.3.3) and was hit with an unsupported aboot error (device mismatch).
So now i'm going to try and use flash tool to revert back to 11A, root, install twrp (I hope this is possible and I don't brick my phone [i'm new to all of this])
Anyone tell me if this is an acceptable option to proceed? Thank's in advance.
Acceptable. KDZ to 11A.
Just wanted to post I was successful using lg flash tool to revert to 11A, rooted, freegee twrp, flashed 2.6.3.3, flashed OSE ROM. Everything is well ATM!
Sent from my LG-VS980 using Tapatalk
Long story short: I want cm on the S4 after using it on the HD+, but CWM isn't booting up.
I've seen problems regarding simply accessing the recovery mode like needing to use the buttons twice after powering on, but the thing is that after getting to do this, for whatever reason, the phone boots up with the default recovery option (Android system recovery <3e>).
Some background on the phone would be that it is rooted, about one year ago when I bought it. I fear that I might have flashed something back then, but I don't have any of the files. To add, I sadly don't remember the method, but I can give some device info:
View attachment 2870784
The next and last thing would be that ROM manager says I have CWM installed and even with the reboot option of the app, it takes me to the default recovery.
View attachment 2870785
Any similar experiences on how to deal with this? I'd at least have a means to access CWM.
Are you sure you're still rooted? If you're not sure I would re-flash root using motochopper
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you sure you're still rooted? If you're not sure I would re-flash root using motochopper
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, yes. I do have things like tethering and su on the phone, plus root checking apps from the store say its rooted.
ROM Manager is crap. It says I have CWM 6.0.4.7 installed but when I boot into recovery it says 6.0.4.4.
I've been looking for a way to manually install the latest Touch version of CWM but so far I've come up with nothing. Maybe if you flash TWRP (via Goo Manager app) you'll then be able to flash CWM back over it. Sometimes it takes 2 or 3 tries for Goo Manager to successfully flash the recovery.
Even better, I figured out how to flash CWM touch. The loki_tool downloaded here can patch any compatible img file and then flash your recovery directly.
https://github.com/djrbliss/loki
The readme was very helpful.
snakecharmer23 said:
Even better, I figured out how to flash CWM touch. The loki_tool downloaded here can patch any compatible img file and then flash your recovery directly.
The readme was very helpful.
Click to expand...
Click to collapse
Thanks for the link! It was really easy to follow.
Okay so i have a few questions here its been a while since i have placed a Rom onto my device the last one was a Sprint model of the G2 and i was able to successfully install CM12 nightly onto it.
With my T-Mobile G2 i had used the once click root application to do so and used auto rec from the app store to install TWRP recovery hopefully i didn't do anything wrong at this point. So now i try to boot into recovery using the power and the down key at the same time but when i did this i was prompted with do you want to reset all data or not and i of course i chose no and booted back home.
Yes i have Super Su with granting access so to solve this minor problem. I had the quick boot application here to boot into recovery but another problem persisted. I cant flash anything over it fails every time and i am trying to flash 5.1.1 cm 12 i think with gapps with 5.1 i believe but in doing so still failed it matched up and everything. I thought that maybe i was trying to flash something that's really not compatible with my phone so i tried to use the same rom but different carriers.
It was cm-12-20150406-NIGHTLY-D801.zip and gapps-lp-20150222-signed but still failed to install the rom? is there something im doing wrong? May i have a tutorial step by step on what to do to successfully flash? and why cant i boot into recovery with the button configuration did i do something wrong with that i just want to so that if theirs a boot load epidermic and i need to use that to restore and see what the problem is? just need help please
Tensaz said:
Okay so i have a few questions here its been a while since i have placed a Rom onto my device the last one was a Sprint model of the G2 and i was able to successfully install CM12 nightly onto it.
With my T-Mobile G2 i had used the once click root application to do so and used auto rec from the app store to install TWRP recovery hopefully i didn't do anything wrong at this point so now i try to boot into recovery using the power and the down key at the same time but when i did this i was prompted with do you want to reset all data or not and i of course i chose no and booted back home and yes i have Super Su with granting access so to solve this minor problem i had the quick boot application here to boot into recovery but another problem persisted i cant flash anything over it fails every time and i am trying to flash 5.1.1 cm 12 i think with gapps with 5.1 i believe but in doing so still failed it matched up and everything. I thought that maybe i was trying to flash something that's really not compatible with my phone so i tried to use the same rom but different carriers cm-12-20150406-NIGHTLY-D801.zip and gapps-lp-20150222-signed but still failed to install the rom? is there something im doing wrong? May i have a tutorial step by step on what to do to successfully flash? and why cant i boot into recovery with the button configuration did i do something wrong with that i just want to so that if theirs a boot load epidermic and i need to use that to restore and see what the problem is? just need help please
Click to expand...
Click to collapse
There's no way anyone can read that without any punctuation marks or any paragraph order.
Basically, the data reset function doesn't work when you have a custom recovery, that's how you enter it. But the TWRP version installed is usually old, somewhat like 2.7.0.0, so you need to update it before installing any roms.
If you really do have recovery installed when you get to the screen about erasing data just choose yes and yes and it will just take you to recovery. If that's too scary for you then just boot into recovery using an app like rebooter from the play store.
As far as flashing it sounds like you may have downloaded bad files. If you're using your phone to download the roms maybe try using a pc then transferring to your phone. And DON'T flash roms for a different carrier, you're just asking for trouble.
Sent from my LG-D801
Choristav said:
There's no way anyone can read that without any punctuation marks or any paragraph order.
Basically, the data reset function doesn't work when you have a custom recovery, that's how you enter it. But the TWRP version installed is usually old, somewhat like 2.7.0.0, so you need to update it before installing any roms.
Click to expand...
Click to collapse
I Have version 2.8.6.1
rick09 said:
If you really do have recovery installed when you get to the screen about erasing data just choose yes and yes and it will just take you to recovery. If that's too scary for you then just boot into recovery using an app like rebooter from the play store.
As far as flashing it sounds like you may have downloaded bad files. If you're using your phone to download the roms maybe try using a pc then transferring to your phone. And DON'T flash roms for a different carrier, you're just asking for trouble.
Sent from my LG-D801
Click to expand...
Click to collapse
I used my computer to download the files all together and the problem still persisted.
And that i do know to not flash with different Carrier did it with a s4 without thinking.
Tensaz said:
I used my computer to download the files all together and the problem still persisted.
And that i do know to not flash with different Carrier did it with a s4 without thinking.
Click to expand...
Click to collapse
The problem might be that you are on the wrong bootloader so v30 lollipop. As loki and bump don't work on it it will result into an failed flash. What you can do is flash the right bootloader or easily downgrade bootloader and bootstack with autorec for your phone. Read carefully which one you need for your tmobile d801. If there is an loki error then just flash the jellybean bootloader what you easily can do with autorec.
Sent from my LG-D802 using Tapatalk
wulsic said:
The problem might be that you are on the wrong bootloader so v30 lollipop. As loki and bump don't work on it it will result into an failed flash. What you can do is flash the right bootloader or easily downgrade bootloader and bootstack with autorec for your phone. Read carefully which one you need for your tmobile d801. If there is an loki error then just flash the jellybean bootloader what you easily can do with autorec.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Still a bit noobish how do i do that boot loader thing?
Tensaz said:
Still a bit noobish how do i do that boot loader thing?
Click to expand...
Click to collapse
Well you download the right version for your d801
https://www.androidfilehost.com/?w=files&flid=13763
Then you need to install it
Click on the lollipop and let it do its job. If it asks for root then allow it.
It will probably reboot and you are done. Only need to flash then a newer recovery. Also search bender_007 on xda and leave him a thanks perhaps for his app
Sent from my LG-D802 using Tapatalk
wulsic said:
Well you download the right version for your d801
Then you need to install it
Click on the lollipop and let it do its job. If it asks for root then allow it.
It will probably reboot and you are done. Only need to flash then a newer recovery. Also search bender_007 on xda and leave him a thanks perhaps for his app
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
my god i can flash now awesome thank you now i have one last question if you dont mind telling me since i downgraded my boot loader to kk i think using the auto rec do i need to flash my current 30b boot-stack first before i use my stock restore? or is there an easier way to do so (tried to go into stock but was met with a black screen after lg logo)
Tensaz said:
my god i can flash now awesome thank you now i have one last question if you dont mind telling me since i downgraded my boot loader to kk i think using the auto rec do i need to flash my current 30b boot-stack first before i use my stock restore? or is there an easier way to do so (tried to go into stock but was met with a black screen after lg logo)
Click to expand...
Click to collapse
Well, as far as I know autorec downgrades to jb bootloader, to boot into stock you could find d801 lp modem and d801 lp bootstack/bootloader as it might need kk bootloader
Sent from my LG-D802 using Tapatalk
wulsic said:
Well, as far as I know autorec downgrades to jb bootloader, to boot into stock you could find d801 lp modem and d801 lp bootstack/bootloader as it might need kk bootloader
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thank you for your help i now have a boot loader for stock that i found and im using auto rec for every time i reboot to cm12 getting the hang of this flashing thing i just want to know if theres any problems with the network service for cm12 at all?
Tensaz said:
thank you for your help i now have a boot loader for stock that i found and im using auto rec for every time i reboot to cm12 getting the hang of this flashing thing i just want to know if theres any problems with the network service for cm12 at all?
Click to expand...
Click to collapse
With cm12 I am not sure but the cause could be perhaps the wrong modem, and or bootloader. I also suggest to check out newer custom roms the only cyanogenmod as some custom roms are already running on lollipop modem and caf. CAF is code aurora forum so kinda it will also have changes specifically for qualcomm devices.
Sent from my LG-D802 using Tapatalk