First.. I want to say hello and that i've been reading around these forums for quite a while since I got my Droid about a year ago. I haven't posted anything till now.. but that's only because everyone else usually get's the answers typed faster than me. lol
On to the problem... I think I screwed up. I JUST bought this thing today. I got a little too excited about getting this tablet rooted and might have jumped the gun a little. I used the apk that has been around to root. No problems there. I got ROM Manager loaded... and I ended up flashing the newest recovery from there before realizing that everyone else says to use something else.
So... at this point, i'm unable to reboot into recovery at all. It starts up, acts like it's about to, and then just reboots again into the OS instead. Is there a way to fix this and get it on the correct recovery image or have I totally screwed myself over? Maybe through ADB? I can only tolerate this horrid TnT OS for so long. Took me 20 minutes to get it to update without a FC... Browser, weather, calendar, and a bunch of other stuff FC on me when I tried starting.. Fortunately, those issues are less frequent with the update, but still not working keeping.
I need some "stock(CyanogenMod)" Froyo goodness.. lol I can't have my year and a half old phone outclass this tablet for too long. If anyone can offer any help on this, I would greatly appreciate it.
The good news is you are still booting into the OS, so I doubt you've screwed anything up too bad. Most likely Clockwork Mod just never flashed so you are still running with the gimpy stock recovery and it's puking on the update.zip file you have on your internal sd card for some reason.
First suggestion is get a copy of Clockwork Mod 0.8 and try installing it. The instructions here are geared toward installing from an external from an external MicroSD card: http://forum.xda-developers.com/showthread.php?t=865245 I am not certain why they say that's the only way to do it, since I never did it that way.
I just downloaded this: http://www.mediafire.com/?dvleg4oatkfxm7w and stuck the update.zip and recovery folder into my /sdcard directory, then turned my tablet off, then held down Vol+ and turned it back on. Clockwork Mod should install itself and boots into Clockwork Mod, and that was that.
I never used ROM Manager at all on my G Tablet, so I can't speak to doing anything that way, but I would stick with the tried and true methods at least until you have Clockwork Mod running.
If that fails and you really can't get any recovery working, maybe something did get botched and you might need to use nvflash to fix it, but I doubt it.
Once you get Clockwork Mod running properly, just copy over the update.zip for TNT Lite or Vegan ROM, flash, and wipe data, then you should be good to go.
Worked perfectly and entirely from the tablet! I installed CM6.1 and I'm a bit upset at the lack way it looks, but then, its packed for smaller screens, so I understand. Thank you for the quick reply. I'm off to try TnT Lite now.
Related
I'm not expert enough to say this is the answer to a lot of people's problem -- but I'm going to throw it out anyway and hopefully some of the "really expert" people will jump in.
Several times when I have had major problems, I have found that the file structure/files/etc. on my tablet were messed up. Before I could reinstall, I had to re-partition, wipe caches, etc.
I read a lot of posts about people having major lockups or loops and then just trying to reload and reload software assuming that is the only problem -- and not getting good results.
It seems to me that if there is a serious enough malfunction to have to nvflash or do a major recovery -- it would be good to re-partition, wipe caches, etc. in case there is corruption or other structure problems.
What I think we need is for one of the gurus to make us a procedure for "Rebuilding the /sdcard File Structure" (or something like that. Repartition to 2048 and 0 --- and then what else? Which things need to be wiped, formatted, etc.
I'm pretty good a discerning what's wrong -- and I think some of these rebuilds are failing because of this problem.
Right? Wrong? Other ideas? Procedure?
Rev
P. S. -- Enough folks are having these problems right now that this could be an important help for them if I am right......
I PM'd, but the short version for the forum.
I've obviously seen a lot of issues with the TNT Lite 5.0.0, and I've whittled it down to two major problems. First off, not everyone reads instructions. This was fine pre-TNTL 5.0.0 as the instructions really were the same for every version preceding it. But 5.0.0 changed the playing field drastically. Which leads me to the my second point....
I think that some of us have been using mods for so long now that stock was no longer an option without an nvflash. Viewsonic, for example, had a bootloader update in December and I believe a recovery change with 3588. But since a lot of us have been using mods for months, we never got those updates. So, when the time came to revert back to stock, there were problems.
In some ways, TNT Lite 5.0.0 is almost like a tablet cleanup - it's the first update I've had where a stock pre-req was required, and the first one in a very long time where I added a stock bootloader and recovery.
nvflash and tnt 5.0
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Charles77 said:
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Click to expand...
Click to collapse
Not sure -- sounds like you did it correctly. nvflash to 2967, OTA to 3588 and then TNTL 5.00. You didn't install clockworkmod, correct? You need 3588 recovery for this to work.
oops yes I did. ok
Charles77 said:
oops yes I did. ok
Click to expand...
Click to collapse
That would do it. The reason why 3588 recovery is needed is because it updates the bootloader, whereas I believe clockwormod does not.
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
darthbubba said:
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
Click to expand...
Click to collapse
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Deleted dupe
FIXED IT!
jimcpl said:
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Click to expand...
Click to collapse
I FOUND A FIX!!!!
Link here: http://forum.xda-developers.com/showpost.php?p=12030351&postcount=14
I got my wish, now I'm back to status quo ante...
I sent tcrews a PM with this link, hopefully it'll fix his too...
darthbubba et all,
The files from otreblada that are in this download are the same files roebeet and others have provided -- just packaged together in one set.
To nvflash you have to have:
1. the files for the program nvflash
2. the .img, boot, etc. files
3. the USB driver files.
All of these are referenced and available in several places.
I am glad, however, that this might be a solution for some of you who seem to
have recurring problems.
Rev
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
I got a little bit of a weird question.
I rooted my Tablet originally Cyangenmod's Root Guide:
http://wiki.cyanogenmod.org/w/Install_CM_for_tf101
Every single time I enter Clockworkmod Recovery, I get stuck in a boot loop until I rock between the newest version of Clockwork Recovery (v6.0.1.3) and back to the newest version of Clockwork Recovery Touch (v5.8.3.4.t) (rock as in move back and forth, not 'jam').
Clockwork Recovery Touch is the only version I've found that properly recognizes the sdcard while in recovery mode, so that always ends up being the version I keep on the tablet.
While I am always ultimately able to get the tablet back to functional AND install the rom, this remains something of a nuisance. As rarely as I update the tablet, I almost always forget about this quirk till I am knee deep into trying to update the ROM.
I wanted to see if anyone else has this problem and if there are any work arounds. I would like to not have to fight with this issue everytime and realistically, I'm nearing the point where I am going to upgrade to a new tablet and who I pass it on to will likely not be tech swavy enough to know how to deal with the problem.
Any thoughts?
Flash TWRP recovery - CWM is ancient and bricks the TF101 if you install JB and above ROMs
Easyflasher can do it
http://forum.xda-developers.com/showthread.php?t=1688012
So can Goo Manager from the Play Store
I'll give it a shot. Clockwork DOES do the job, its just, as I said, every single time I ENTER Clockwork, I have to rock the recoveries to make the tablet boot into Android again >.>
Based on the comments on the page TWRP, it seems to be similar problems there too, but at least I know how to get around it if it blows up!
LighthammerX said:
I'll give it a shot. Clockwork DOES do the job, its just, as I said, every single time I ENTER Clockwork, I have to rock the recoveries to make the tablet boot into Android again >.>
Based on the comments on the page TWRP, it seems to be similar problems there too, but at least I know how to get around it if it blows up!
Click to expand...
Click to collapse
TWRP (at least my builds) are working just fine with the tf101. My vfat formatted external microsd is recognized perfectly and the internal sdcard works perfect, too. Plus, you'll be able to flash newer ROMs. You could have an issue if your tab is already in some weird state, but otherwise TWRP should work fine unless you're using some other formatting besides what is standard for Android.
See here for download links and instructions:
http://forum.xda-developers.com/showthread.php?t=2434422
I just went through the update to ne5 getting wifi calling and such, then rerooted since I lost it.
Everything was working fine, so I put in philz recovery since I lost that after the update also. I think it booted once after that, then now it is stuck on the spark screen when it boots.
Any way to go into Odin and change it, or reflash a stock rom of it? open to ideas since my new phone is pretty useless now, lol
Cowboyup65 said:
I just went through the update to ne5 getting wifi calling and such, then rerooted since I lost it.
Everything was working fine, so I put in philz recovery since I lost that after the update also. I think it booted once after that, then now it is stuck on the spark screen when it boots.
Any way to go into Odin and change it, or reflash a stock rom of it? open to ideas since my new phone is pretty useless now, lol
Click to expand...
Click to collapse
Ok, I fixed it through my engineering problem solving.
Since I could not boot the phone past the spark screen and I had only zip files to load on the phone, I had to pull my sd card, load it into my laptop, transfer a couple of file of stock roms http://cnexus.co/downloads/getdownload.php?file=SM-G900P/NE5/NE5_ROOTED_ODEXED.zip
this one being the one I used.
Then I was able to boot into Philz recovery, flash the zip file and get my phone back.
Of course the last couple weeks of tweaks and changes were gone and all the bloatware came back in a hurry, but I deleted it as expected.
Just updating this in case someone else runs into the same problem in the future.
Bummer Odin doesn't push .zip files, would have made it a little easier, but through mistakes and failure we learn and tonight I learned a few things about my phone, cool!.