I had a problem a few days ago that i was having problems after rooting my phone so i brought it back to stock using RSD Lite and then tried to flash a new rom on the phone and it said my phone was not unlocked so i downloaded The Myth Tools and unlocked it that way but I am wondering if i messed it up because i did not really know what i was doing i just tried to see if i could figure it out and it seemed like it worked until today. I flashed Touchwiz on there a couple days ago and it worked fine i made a backup wiped the cache,dalvik cache and system now today it randomly freezes and is now stuck on the bootloader unlocked screen. I can hold down power and volume up and boot into recovery which is ClockworkMod Recovery v6.0.3.6 touch and it also says under that in the bottom right of the screen Warning No file_contexts now i dont know if it has always said that since i flashed this recovery or just started. I also once again tried wiping the cache and dalvik cache because i read it on another post of someone stuck on this screen so i tried that and rebooted it still the same result stuck on bootloader screen. At this point i have no idea what to do. If i have to start over from stock because i messed up unlocking it or completely wipe it again and reflash touchwiz or another rom. I have had nothing but problems since rooting this phone I have gone through atleast 6 to 8 roms because every single one of them gives me a problem somehow. The most common is when i make a call or recieve one and i put the phone up to my ear I know the sensor turns off the screen but when i take it away to end it or do something its completely off or apps force closing all the time still after i did the stock reflash. I am starting to wonder if its just my phone because everyone else i read about has no problems with there phones mine nothing but problems. Please if someone could help me or walk me through this process it would be greatly appreciated I love the things it can do with custom roms but i just wish it would run smooth.
bpc87 said:
I had a problem a few days ago that i was having problems after rooting my phone so i brought it back to stock using RSD Lite and then tried to flash a new rom on the phone and it said my phone was not unlocked so i downloaded The Myth Tools and unlocked it that way but I am wondering if i messed it up because i did not really know what i was doing i just tried to see if i could figure it out and it seemed like it worked until today. I flashed Touchwiz on there a couple days ago and it worked fine i made a backup wiped the cache,dalvik cache and system now today it randomly freezes and is now stuck on the bootloader unlocked screen. I can hold down power and volume up and boot into recovery which is ClockworkMod Recovery v6.0.3.6 touch and it also says under that in the bottom right of the screen Warning No file_contexts now i dont know if it has always said that since i flashed this recovery or just started. I also once again tried wiping the cache and dalvik cache because i read it on another post of someone stuck on this screen so i tried that and rebooted it still the same result stuck on bootloader screen. At this point i have no idea what to do. If i have to start over from stock because i messed up unlocking it or completely wipe it again and reflash touchwiz or another rom. I have had nothing but problems since rooting this phone I have gone through atleast 6 to 8 roms because every single one of them gives me a problem somehow. The most common is when i make a call or recieve one and i put the phone up to my ear I know the sensor turns off the screen but when i take it away to end it or do something its completely off or apps force closing all the time still after i did the stock reflash. I am starting to wonder if its just my phone because everyone else i read about has no problems with there phones mine nothing but problems. Please if someone could help me or walk me through this process it would be greatly appreciated I love the things it can do with custom roms but i just wish it would run smooth.
Click to expand...
Click to collapse
You can enter Recovery, right? What happens if you install a .zip? Right now your phone is stuck in the Motorola logo?
it wouldnt even go to the motorola symbol it just stayed in the first screen where it said your bootloader was unlocked. It would go into recovery and i tried to reboot it and it gave me the same screen. So i wiped it completely cache, dalvik cache and system and shut it off. Last night i plugged it into my comp to put it back to stock and it started up like normal and booted into a rom like i just installed one where you have to fill in all that info and setup wifi if you choose too which was weird because it wouldnt do anything before. Anyways i used RSD Lite and put it back to stock and thats where it is now. I am reading the Atrix HD Beginners Guide written by skeevydude right now and I am thinking about trying to root it again with the help of that article and maybe I will have better luck doing it that way hopefully haha maybe I can finally get a rom to run the way everyone else says they run smooth and fast. Any input though to help me would be much appreciated i am definitely new at this and want to learn its something that interests me alot ever since a friend rooted my phone the first time i cant stop playing with it I was trying to make it as fast as I can I had ProBam on there i think its called ive had touchwiz, motoblur, carbon, liquidsmooth, MIUI, and a couple others I cant remember also had a custom kernel i flashed on there and Pure performance so as you can see I have been trying everything.
bpc87 said:
it wouldnt even go to the motorola symbol it just stayed in the first screen where it said your bootloader was unlocked. It would go into recovery and i tried to reboot it and it gave me the same screen. So i wiped it completely cache, dalvik cache and system and shut it off. Last night i plugged it into my comp to put it back to stock and it started up like normal and booted into a rom like i just installed one where you have to fill in all that info and setup wifi if you choose too which was weird because it wouldnt do anything before. Anyways i used RSD Lite and put it back to stock and thats where it is now. I am reading the Atrix HD Beginners Guide written by skeevydude right now and I am thinking about trying to root it again with the help of that article and maybe I will have better luck doing it that way hopefully haha maybe I can finally get a rom to run the way everyone else says they run smooth and fast. Any input though to help me would be much appreciated i am definitely new at this and want to learn its something that interests me alot ever since a friend rooted my phone the first time i cant stop playing with it I was trying to make it as fast as I can I had ProBam on there i think its called ive had touchwiz, motoblur, carbon, liquidsmooth, MIUI, and a couple others I cant remember also had a custom kernel i flashed on there and Pure performance so as you can see I have been trying everything.
Click to expand...
Click to collapse
Good to know that is working now. I would recommend you to take it easy. Don't flash it everyday, use and know a ROM, then you can decice which one is better for you. Be sure to have a backup if something fails, also save a .zip (ROM) in the SD card. Just FYI, I haven't come across a ROM that is 100% smooth (Not even HoloBlur). They are very good, but maybe not the smooth level that you think.
Hey bpc87, I was wondering if you were able to get a custom ROM up & running after all that & if so, how?
I've had the same issue whenever I tried installing a ROM. It would install & boot okay the first time, but when rebooting, it would get stuck at the "bootloader unlocked" warning screen. I went back to stock using Myth Tools & now, after installing a ROM, a reboot leaves me stuck at the "Motorola Dual Core" screen.
Any help from you & the community would be awesome!
bsmitty said:
Hey bpc87, I was wondering if you were able to get a custom ROM up & running after all that & if so, how?
I've had the same issue whenever I tried installing a ROM. It would install & boot okay the first time, but when rebooting, it would get stuck at the "bootloader unlocked" warning screen. I went back to stock using Myth Tools & now, after installing a ROM, a reboot leaves me stuck at the "Motorola Dual Core" screen.
Any help from you & the community would be awesome!
Click to expand...
Click to collapse
dude i havent even tried to since i flashed it back to stock because i dont want the same thing to happen. The last time I just went to turn on bluetooth and it just rebooted on its own. Not too mention the other problems I had I am not going to mess with it again until I read more on how to root it because it is either that or my phone.
Yeah, I understand. Hopefully then some other users who run into the same problem will investigate & figure out what's goin on. I've seen several other threads of people who've encountered the same thing but unfortunately no answer. For me, this is the determining factor as to whether I end up keeping the AHD or not.
Thanks
I have the same problem. Everytime in moto logo after rebooting, but with stock firmware all ok. Is there any solution for this problem?
Related
Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.
Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.
Gave my old LG Revo to a buddy, things POS, but its all he has at the moment. Anyways, I had a version of Ginger-volt rom on there, and it was acting up, so I was just gonna update everything and put the last version that came out on it, or go with whatever the newest most stable rom is....So I booted into CWM and did a nandroid back up, then wiped everything, cache, dalvik, etc etc, booted up fine, went through some stuff, then i went back to restore the back up i just made cause he forgot to tell me about some game data he wanted backed up.....
So anyways, i restored it, wiped the cache, then rebooted, and yea, then it went into boot loop, at first it was between the LG Logo and the Boot Animation, but now it just suts at the LG Logo for quite awhile, like 10min, and then restarts, and does it over and over. And I try and hold down Power and Vol-Down, but it doesn't work, can't get into recovery. So Need some help here. I've tried all the old tricks I remember from my LG Revo days, but nothing has worked thus far. Is there a way to like boot into something like ODIN and just flash the Stock Firmware. Like RSD-Lite maybe ? Can't remember if that was Moto only....Think it may have been lol
remembered about the exitrecover.zip thing did that, put sdcard back in phone, booted, holding down power and vol-dwn, and it worked, flashed the .zip and then rebooted, now its doing it once again. WTF. I want this thing back to Stock, and then I am gonna root it and flash a new rom. but before that obviously i need to fix this first. Can someone help me at all. I know there isn't a lot of people left on this forum.
BackSeatSuicide said:
Gave my old LG Revo to a buddy, things POS, but its all he has at the moment. Anyways, I had a version of Ginger-volt rom on there, and it was acting up, so I was just gonna update everything and put the last version that came out on it, or go with whatever the newest most stable rom is....So I booted into CWM and did a nandroid back up, then wiped everything, cache, dalvik, etc etc, booted up fine, went through some stuff, then i went back to restore the back up i just made cause he forgot to tell me about some game data he wanted backed up.....
So anyways, i restored it, wiped the cache, then rebooted, and yea, then it went into boot loop, at first it was between the LG Logo and the Boot Animation, but now it just suts at the LG Logo for quite awhile, like 10min, and then restarts, and does it over and over. And I try and hold down Power and Vol-Down, but it doesn't work, can't get into recovery. So Need some help here. I've tried all the old tricks I remember from my LG Revo days, but nothing has worked thus far. Is there a way to like boot into something like ODIN and just flash the Stock Firmware. Like RSD-Lite maybe ? Can't remember if that was Moto only....Think it may have been lol
Click to expand...
Click to collapse
Try the LG restore tool i think its LGPSNT or something like that, but you need a .TOT, and the you can reroot, flash a recovery, and install an updated ROM, gingervolt is OLD
betatest3 said:
Try the LG restore tool i think its LGPSNT or something like that, but you need a .TOT, and the you can reroot, flash a recovery, and install an updated ROM, gingervolt is OLD
Click to expand...
Click to collapse
well i fixed that stuff on my own, couldn't get anyone to respond so I just went based on what I remember, like i said, it's been awhile since i used that phone
BUT NOW ! I got a whole other issue, and its a lot more F'd up, and I have never dealt with this before, so I am just wingin it on what i've tried so far. But i've hit a wall. So after restoring everything and getting Broke-Out rom back on there and everything, I noticed after a lil bit that it had the No Sim-Card icon in the status bar, and couldn't make a call. Then it hit me, and i didnt wnna say it outloud just in case i was wrong, so looked at About Phone>Status, and yep, Completely zero'd out, IMEI/MEID etc etc. I have no idea what to do. I tried following that guide on here but that program DFS or whatever, I entered my IMEI number in this program and hit "Write" and now its in my phone, so i know its communicating with my phone, but that still didnt fix it, I am missing the HEX number, and where it is located on the phone behind the battery, has been complketely rubbed away, so i cant read it. I don't know if Verizon will tell me what the number is, and I didnt wanna call them cause what am I supposed to tell them, not that we care about the warranty on this phone cause its pretty much on its last legs anyways, but i dont wanna cause any problems on my account, cause I know verizon is pretty anti-custom development,
So any ideas on what to do ?
Anyone ? Any suggestion on how to go about fixing this ?
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
raynefr said:
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Click to expand...
Click to collapse
Do you still have the memory issue? If so, try running a RUU, and see if that fixes your problem.
If not, just use adb sideload to sideload a ROM. Then wipe everything except internal storage and install the ROM normally.
EDIT: Looks like @BD619 ninja'd me XD
BTW sideload very rarely works when you wipe your sdcard.
BD619 said:
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
Click to expand...
Click to collapse
hey thanks for the reply. i followed the guide and after some effort, everything seemed good, but when i was trying to load 5.03 sense 6 rom, i got to the htc start up, then it defaulted back to the bootloader..i went with the deodex version of the download, should i try the odex? or a different version all together?
and now it doesnt want to boot into recovery mode either! going to try redoing the steps, but i just cant figure out what the problem is
**edit* i cant fix twrp. the title loads, but thats it. endless loop
ok i got it to seemingly work. restoring content now. sat in fron of my pc for 15 hours...not even sure where imat or if i got any closer to rooting..smh..thank you everyone who helped. if anyone comes across this
to get out of the endless cycle of recover/loading screen.. delete your twrp, or whatevs your using. even if you have the latest, just redownload it. worked for me. i guess there is a huge difference between the odex and the deodex.i had figured deodex was a more refined version, but maybe it had more complicated software. in any case, if you are at a point where you dont have a base os, and you make it this far, go with odex, it worked for me. htc is big on back up, so i was more worried about having to scrap my phone then i was regaining data, especially with most of my stuff backed up to google drive. hopefully you guys are careful.
now...about this backup issue i had in the first place. how can i fix the storage issue? i have a 32 gb phone minus partition leaves me with over 24gb..why is it going based off the separate phonememory slot? why cant i change it?
Okay im not quite sure whats happening here my friend has given me his phone which he bought with this mod as a back up phone.
It is currently loading up to the android bit after the logo then restarting or rebooting and constantly does this while on the android screen you have to power the phone off quickly before the restart. In any case i tried to get the stock rom and installed it... after the update it still does this.
What i have done is gone into the TWRP menu and installed this rom
http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743 through the sd card. Its the first link.
Anyhow i dont really have much knowledge with this so any help is appreciated and i can not seem to find a factory reset. Im not sure how to find what version i am using or anything like that.
badman112 said:
Okay im not quite sure whats happening here my friend has given me his phone which he bought with this mod as a back up phone.
It is currently loading up to the android bit after the logo then restarting or rebooting and constantly does this while on the android screen you have to power the phone off quickly before the restart. In any case i tried to get the stock rom and installed it... after the update it still does this.
What i have done is gone into the TWRP menu and installed this rom
http://forum.xda-developers.com/one...one-mini-2-t3250020/post63859743#post63859743 through the sd card. Its the first link.
Anyhow i dont really have much knowledge with this so any help is appreciated and i can not seem to find a factory reset. Im not sure how to find what version i am using or anything like that.
Click to expand...
Click to collapse
Even though the user as done a great job creating an RUU its still not official.
I would try and use this one instead and see how it goes.
Just go to TWRP and create a backup
Replace the backup with this one
in TWRP restore phone.
Remove USB and reboot.
lets us know! G.Luck