I had been running BOS 5.4 and I kept getting errors saying that Tablet memory was low and nothing I tried could get that error to go away. I tried uninstalling apps, tried wiping user data, nothing fixed it. Everything would FC constantly.
Long story short, now every time that I boot my GTab it boots straight into recovery without me pushing the volume key. I have tried re-installing BOS but nothing takes. I mount USB through ClockWorkMod and nothing is there except for the BOS zip file that I placed on the memory. Everything else is gone. I tried partitioning the sd card to 2048/0 and then tried re-installing BOS but to no avail. I am all out of idea.
Any ideas??
First off, there is no BoS a5.4 - not sure if you're running BoS or another HC ROM.
Second, did you try and do a factory reset while in the UI, and while cwm was installed? If so, then this is a known issue with cwm. I have instruction on Slatedroid for my ROMs, but to paraphrase here. Use either method:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Again, this is assuming that this is really Bottle of Smoke and not another ROM. If it's not BoS, then the ADB instructions may not work.
roebeet said:
First off, there is no BoS a5.4 - not sure if you're running BoS or another HC ROM.
Second, did you try and do a factory reset while in the UI, and while cwm was installed? If so, then this is a known issue with cwm. I have instruction on Slatedroid for my ROMs, but to paraphrase here. Use either method:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Again, this is assuming that this is really Bottle of Smoke and not another ROM. If it's not BoS, then the ADB instructions may not work.
Click to expand...
Click to collapse
I apologize, it was BOS 5.2. I will try this out and report back, thank you very much for the reply, roebeet. I am LOVING Bottle of Smoke, btw. Thanks for your hard work.
adb method is not working. I can't get it to find my device :/
If the factory restore in the UI was the catalyst, then one of these two options should fix it (if you can get it working). I've had this happen to me with cwm, on my Froyo ROMs.
What happens is that the device wants to wipe the user data, but cwm doesn't understand how to do that the way the device wants it to. So on every reboot it just keeps trying. When standard recovery is added back, the process can complete.
There is potentially one other way, but will take a few steps and I've never tried it myself.... in cwm, mount the device to your PC via the mounts and storage -- USB storage option. Then, grab the 4349 recovery update.zip that I advertise in Slatedroid (sorry, not allowed to give you a link as its against XDA rules - just google "1.2 recovey gtablet 4349"). Take that update.zip and put it somewhere on the mounted drive, unmount, then use cwm to run that update.zip. That should, in theory, get you standard recovery again and might allow the data wipe process to finish.
roebeet said:
If the factory restore in the UI was the catalyst, then one of these two options should fix it (if you can get it working). I've had this happen to me with cwm, on my Froyo ROMs.
What happens is that the device wants to wipe the user data, but cwm doesn't understand how to do that the way the device wants it to. So on every reboot it just keeps trying. When standard recovery is added back, the process can complete.
There is potentially one other way, but will take a few steps and I've never tried it myself.... in cwm, mount the device to your PC via the mounts and storage -- USB storage option. Then, grab the 4349 recovery update.zip that I advertise in Slatedroid (sorry, not allowed to give you a link as its against XDA rules - just google "1.2 recovey gtablet 4349"). Take that update.zip and put it somewhere on the mounted drive, unmount, then use cwm to run that update.zip. That should, in theory, get you standard recovery again and might allow the data wipe process to finish.
Click to expand...
Click to collapse
roebeet, you are my freaking HERO!! I downloaded the 4349 recovery update.zip and BOOM Bottle of Smoke is booting up like a champ. Thank you for taking the time to help me do this!!
http://www.youtube.com/watch?v=0N-SyPEL-pA
fidju said:
roebeet, you are my freaking HERO!! I downloaded the 4349 recovery update.zip and BOOM Bottle of Smoke is booting up like a champ. Thank you for taking the time to help me do this!!
http://www.youtube.com/watch?v=0N-SyPEL-pA
Click to expand...
Click to collapse
Thanks for the update! I might actually need to add those steps to my ROM's cwm caveats in my first posts (might be easier than adb/nvflash for most people).
Related
***************SOLVED*******************
Hey, hoping some android gurus can help me out here.
I had the latest version of Obsydian on my phone and have not had any issues. Yesterday, my battery on the phone died, and when it started up again I was getting forcecloses all over the place. Tried reinstalling the rom and go errors, tried a different rom and got errors. So I ODINed the Voodoo RFS fix, followed by stock+Voodoo-Froyo-T959-UVJL5.tar , and didn't get anywhere.
I thought there might have been something wrong with the data on the phone so i tried clearing and formatting everything through Clockwork recovery. Then I tried the partition SD Card through clockwork recovery. I assumed it was the EXT-SD it was formatting so i chose 128mb ext, 32 swap, and left the rest for fat32. However, I'm starting to think it might have been the internal SD card.
I tried ODINing back to stock stock using this guide: http://androidspin.com/2010/08/09/h...droidSPIN+|+Your+No.1+source+for+Android+news.)
I get the phone in ODIN and it flashes, no errors in ODIN, but when the phone leaves download mode and goes to installation it gives a few errors:
Code:
MBR Checksum Error
Movinand Checksum Confirmation Fail
Then it continues installing, and I get another error:
Code:
Wiping data
Formatting Data
[B]Data Wipe Fail[/B]
Formatting Cache
It still acts like it completely finishes the installation, reboots, I get the Tmobile boot and then Galaxy S, and then I get a black screen with all 4 of the lights/buttons on the bottom of the screen on. It can sit like this for 30 minutes, it doesn't do anything.
I still have access to download mode, and I still have access to recovery, however it's no longer ClockworkMod recovery, it's the stock recovery, and it seems to only work for a few moments before going to a triangle with an exclamation point and the android logo.
Any ideas on what I can do to make this phone functional again, or acceptable for a warranty return?
I appreciate any help.
Welcome to the club
Check out my post http://http://forum.xda-developers.com/showthread.php?t=887837
Post #3 it might help if it does let me know so we know for sure if it works
Yes welcome to the club!!! glad you could join us!
Anyways here is what I have learned/done, my only working rom currently is the eugene froyo, can use the phone and data BUT cant download anything or install anything. You can adb push apks into the rom though. Heres the link for it
Use Odin, pit=512, pda=eugene..tar Run this to get semi working rom
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
Once here I have access to my Sd card, this is where I placed the clockwork recovery on as an "update.zip" Link to this is posted below
http://forum.xda-developers.com/showthread.php?t=734164
Boot into recovery, note this will take you to stock recovery. REINSTALL update, may have to do this twice but itll get you to the Clockwork recovery....
After this I tried to install two different roms and both times I get some sort of data error, and installation aborted....hopefully this will help a few people
Yeah a bit more google searching for "vibrant mbr checksum" brought me to the same conclusion, that I needed to ODIN the eugene's froyo - it's flashing right now. Will see where that gets me.
It's my belief that using the SD partition in CWM is what caused the MBR issues and the Data Wipe Fail, as others said they messed with a partition in either CWM or something else prior to this happening
And that's a no go. It just reboots back into the stock recovery every time after odining it, with some new errors.
update media. please wait.
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:copu_dbdata_meda:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
Click to expand...
Click to collapse
I take it back - i did the wrong one apparently.
Had to use the files located on the link you sent, inside of the Eugene_2E_JK2_Froyo.zip file. Apparently there are a few different download files on the first post of that link. This one took longer than all the others I'd tried ODINing, about 5-6 minutes, compared to 2-3 for the others. I had also updated my Odin3 to v1.7, from the v1.3 I was using before.
When it booted up, it gave me an issue with my external SD card, said it was formatted incorrectly, so i formatted it from the phone - it says I have 13gb memory and 1.86 on the ext-SD.
Was able to download and install ROM manager from the market. Attempting to install Nero v3 now.
*** SOLVED ***
I've succesfully installed a rom other than Eugene's froyo, and did not receive any installation errors! Got Nero V3 up and running, very happy.
Note that the MBR checksum error still appeared but did not affect installation at all. Thanks everyone for their help - hopefully this helps the others.
I just got a tablet from the outlet, but it can't boot up. It shows the android logo in small yellow text, then a <!> pops up. Reboots in viewsonic logo, and gets stuck at gtablet logo. I tried holding startup and vol + but that doesn't work. Help please!
EDIT: Thank this guy rcgabriel
rcgabriel said:
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
Gajun said:
I just got a tablet from the outlet, but it can't boot up. It shows the android logo in small yellow text, then a <!> pops up. Reboots in viewsonic logo, and gets stuck at gtablet logo. I tried holding startup and vol + but that doesn't work. Help please!
Click to expand...
Click to collapse
it's not broken - just flash the latest firmware
Try an nvFlash. Mine was stuck at the Viewsonic logo this pas weekend with the recovery (Vol+ and power) not working either. The nvFlash was very easy to do and fixed my Tab.
http://forum.xda-developers.com/showthread.php?t=861950
g1no23 said:
Try an nvFlash. Mine was stuck at the Viewsonic logo this pas weekend with the recovery (Vol+ and power) not working either. The nvFlash was very easy to do and fixed my Tab.
http://forum.xda-developers.com/showthread.php?t=861950
Click to expand...
Click to collapse
thanks for the reply. I tried this, but it didn't help at all. I was able to do all everything but it is still stuck on the gtablet logo. I can go to apx mode fine but I can't go to recovery mode, it reboots back to and gets stuck ;/.
Gajun said:
thanks for the reply. I tried this, but it didn't help at all. I was able to do all everything but it is still stuck on the gtablet logo. I can go to apx mode fine but I can't go to recovery mode, it reboots back to and gets stuck ;/.
Click to expand...
Click to collapse
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Dude! You are the best!!! You are a life saver!! It worked! I got into cwm! Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
EDIT: Just after few minutes of finally getting into CWM, I was able to install VEGAN on it easily. Seriously, I don't know how to thank you enough!
gtab won't boot on its own
ok so i followed the instructions and it worked i was able to boot into the tablet but when i reboot it won't do it i have to use nvflash again to get it to it and once i do and the tablet goes to sleep it wont come back up and once again i have to use nvflash. please help!!
rcgabriel said:
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
I'm stuck in bootloop and I tried you solution and being I'm a noob at this I dont know how to rename the dile under partition 9. I just simply rename the file to recovery.img and i get an error when running the nvflash when it gets to partition 9. Can you please help me .... All help is appreciated.
rcgabriel said:
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
How do you EDIT the gtablet.cfg file in Windows 7? Thanks
Thanks! And a potential pitfall:
Thanks! I was having the same problem all night last night, and repartitioning fixed it.
I'd like to highlight something I had a problem with: I wasted a couple of hours with the WRONG clockworkmod recovery image. I found a similar response from another user who didn't include a link, and I found the clockwork image for g-tablet pointed to by someone else. If you're still having boot loop problems, use the clockworkmod linked to from this thread (v2.5.1.1-bekit-0.8).
Thanks everyone!
Is there a way that a mod can make a Sticky of the "Bricked Solution" fix.
There is no such thing as a bricked Gtablet that I've ever seen. Ive messed mine up a few times now and still works fine no matter how bad it gets.
Same for me, this fixed worked. I was not able to mount /data prior to repartitioning, was able to after. Thus the GTab was able to boot again, I now have a stock GTab, formatted clean, running 3588. Always nice to have a path forward.
emanzi said:
How do you EDIT the gtablet.cfg file in Windows 7? Thanks
Click to expand...
Click to collapse
Use Notepad
Hey i've done as you suggested however I'm stuck at the entering nvflash recovery node / nv3p server print out on my viewsonic gtab.... I still have the device plugged into my computer and it is registered with the usb bus but it won't reboot into the recovery img. I tried to power it down and reboot with "power and volume up" but I get no response. Any suggestions?
One thing I noticed, when people say they try to use nvflash they are using volume +, that is incorrect. You have to do "volume - (the minus sign) with the power button at the same to get the point to be able to use nvflash. See this a lot places in the forums, no wonder there is problems with people trying to use nvflash.
Thank you so much for this. I started getting an error when trying to mount /data so I did an nvflash without reading into it...turned out to be a huge mistake because that caused bootloops and left me without CWM. Turns out I should have just repartitioned but I couldn't get CWM to install from an SD card even though I knew I need to get it back on. Tried dozens of other things - including the full format with no luck but this finally got me into CWM so I could repartition.
Thanks again.
may as well be a brick - in my gut...
Every attempt at customization seems to be a step backwards.
Late nights have been spent over the last week trying to get things back to "normal" and I've had little success. Actually, make that "no success"...
At current, I've been looking ALL DAY (at work) and the last 4 hours at the NVFlash process.
I've got:
USB drivers installed for Windows
Bekit's 1105 files in place (gtablet + windows files)
I can boot to apx with volume.minus and power
PC sees tablet
I can run NVFlash w/o issue
gtablet boots immediately to stock ROM
I power off the gtablet and all I get is APX MODE again.
And again.
I have tried re-running NVFLASH with Roebeet's updated (4/17) files - same thing
I have tried renaming recovery.img from clockwork as "part9.img" and re-running, no success.
I have tweaked the gtablet.cfg and actually adjusted the SIZE for partition 9 to match the clockwork version of what I've named "part9.img" and no luck.
I ran the Format.zip version of nvflash, then ran regular nvflash, no luck.
Every time I run bekit's NVFlash, it loads stock ROM a-ok. Power cycle brings APX mode... I can't get Clockwork to install via the "nvflash switcheroo" nor by dropping "update.zip" and the recovery folder + command file in the root directory.
I feel foolish for spending about $300 on a device like this, and I feel foolish for spending SO MANY LATE NIGHT HOURS trying to fix it, and now I'm essentially going to only be able to use it unless - unless! - someone can come up with something else for me to try.... or if I "boot with NVFlash and hope it doesn't fall asleep on me..."
Any ideas?
Trust me, I've read every thread, seen the same "oh this worked...!" over and over on steps I've tried 3x or more. I think I'm depressed as this is ALL I DID TODAY - research on how to fix my gadget. sigh.
EDIT:
Just thinking here... (scary!) Has anyone ever sideloaded ROM Manager into the stock 3588 ROM? What I'm thinking is that if I can get ROM Manager to install, it loads CWM simultaneously, correct? And from ROM Manager I can reboot into recovery, yes? I would have tried this last night but I didn't come up w/ the idea until past 1:30am.
Also, let me take a step back and explain how I got here:
Installed Cyanogen 7 stable
installed a different keyboard
next day I got keyboard force-closes incessantly
tried to reflash CM7 - boot looped.
I could flash to the stock 3588 ROM w/o issues, and could use Clockwork w/o issues
tried to flash CM7 again, no dice
I suppose what i should have done at this point is re-partition and THEN try to reinstall CM7 - but I was having an issue w/ clockwork not completing the Factory Wipe / Reset - it would get stuck...
so I decided to bring the hammer w/ NVFlash - and I've certainly accomplished that
I can't get clockwork to install despite all I've tried:
paste recovery.img into my NVFLASH folder
change part9.img to recovery.img in the gtablet.cfg file
put clockwork's update.zip in the root folder
put clockwork's update.zip (and change "command" file to SDCARD2
I guess - how do I know if I'm still rooted? When I (nvflash and boot into) the stock ROM, I can connect via usb and navigate the folder structure. I see .android-secure and "data" and other typical folders that I've seen for weeks now...
so tired...
What happens if you do a factory reset immediately after it boots?
@K J Rad - you mean after it boots to the stock ROM, going to settings/security/factory reset (or clear all user data, whatever it says?) - I've tried that twice, and each time it comes back to apx-mode only, and when I nvflash again all my wifi settings are still in place.
if you mean factory wipe / reset from w/in Clockwork - I can't get CW to install.
EDIT - I added more explanation in my earlier post - a "how did I get here" of sorts...
Ok... if you hold down the Volume Up key during the reboot after nvflash does it drop back to APX or enter Recovery? If it goes to recovery... try method I from this: http://forum.xda-developers.com/showthread.php?t=1030915
I installed CWM and TNT 4.4.0; and was able to boot once(first time). But once I powered down the gTab, It goes in to boot loop. I am able to boot into CWM and able to connect to my pC via USB Mass storage using CWM; please help me correctly install the TNT app.
thanks in advance,
I hope this helps!
Check out this thread and make sure you read the comments because you installed CWM.
http://forum.xda-developers.com/showthread.php?t=842000
Also, if you decide to upgrade to a custom ROM, you don't have to install CWM. You can do it in standard recovery, but there is another thread it in both:
http://forum.xda-developers.com/showthread.php?t=842004
Good luck!
i would try re-flashing the rom. maybe even re-download it to ensure that the file isn't incomplete or corrupt.
can I just install tntlite 4.3 or something that is older and upgrade to 4.4? Since I have the CWM installed already?
At this point I do get the Bootloader and mount error E: can't mount /dev/block/mmcblk3p2
Perhaps a good course of action would be:
1> Boot into CWM then partition the sdcard to 2048/0.
2> Follow direction in the second post to return to stock rom, then re-flash the rom using standard recovery (not with CWM).
If that does not work, then use nvflash method to return to stock and start over again http://forum.xda-developers.com/showthread.php?t=861950. I had to do this several times to get my gtablet functions the way it should.
Hope this helps.
tboneuncw said:
. . .
Also, if you decide to upgrade to a custom ROM, you don't have to install CWM. You can do it in standard recovery, but there is another thread it in both:
http://forum.xda-developers.com/showthread.php?t=842004
Good luck!
Click to expand...
Click to collapse
yes, I preferred the standard recovery method to install rom too. However, I have not been able to search for a method to install latest kernel without the use of CWM. Do you have a method?
mydave1 said:
Perhaps a good course of action would be:
1> Boot into CWM then partition the sdcard to 2048/0.
2> Follow direction in the second post to return to stock rom, then re-flash the rom using standard recovery (not with CWM).
If that does not work, then use nvflash method to return to stock and start over again http://forum.xda-developers.com/showthread.php?t=861950. I had to do this several times to get my gtablet functions the way it should.
Hope this helps.
Click to expand...
Click to collapse
What does partitioning of 2048/0 do?
use4all,
To answer your question, it may fix it.
When I hear boot loop, I think partition problem because partitioning often
does fix it.
1. Flash the tablet back to stock. Use the files in the instructions:
http://forum.xda-developers.com/showthread.php?t=861950
2. Install ClockWorkMod (CWM)
3. Reboot into CWM and go to the Advanced Menu -- Repartition to 2048 and 0, Fix Permissions
and Wipe Dalvik Cache. Return to Main Menu and Wipe Cache
and Wipe Factory Data.
4. Shut down and repeat Step 1.
5. At this point if all has gone well, you should have a "stock" working
tablet with "Bekit 1105" (AKA Stock Version 2638 on it.
6. Set up the wifi and almost immediately you should get an OTA (over the air)
Update notice. Do it and when you finish you should have a Stock 3588
tablet.
From there, you can move carefully to where you want to go and hopefully
won't have any more boot loops. I know this is a long process -- and once
in a while it doesn't work -- but I've done it with folks a pile of times and I
think it is the best procedure for your situation.
Good Luck,
Rev
2048/0 is an SD repartition. Think of it as a troubleshooting task just before having to resort to nvflash. It will wipe both /sdcard and /data, so keep that in mind.
Also, btw, if you have TNT Lite 4.3.0+, you can toggle back and forth between standard and cwm - it's called the "3588 Recovery Pack". Read my first post for details.
Ok, thanks for the help. I got to Stock ROM now.
Before I jump into reinstalling 4.4, let me ask this:
do I just copy the 4.4 into the GTab? and boot? or is there something I need to do before that?
4.4 install is just like the 4.3 install - just read my first post for details.
Thank you all for your help. I am up and running on TNTLite4.4. Love it so far..
Hey, guys,
So here's the deal. My tablet was bricked, and I used nv flash method as found on g tablet for dummies. Worked great. Accessed recovery menu, and installed gtabcomb 3.3--rom was stable and awesome. I reboot, and it gets STUCK AT THE SPLASH SCREEN (three birds). Then it doesn't move. I can't access recovery at this point, either. Only APX mode.
So I did NV Flash again, but whenever I reboot, the same problem happens: Stuck at three birds, with no access to recovery anymore, thereby forcing me to reformat to stock rom.
Any guesses?! There has to be an android wizard out there!
After nvflashing and booting in to clockworkmod recovery, try formatting your sdcard (internal storage, not an external card in the slot).
Format it to 4096/0 then back to 2048/0.
I've seen many Gtablets loop at the birds (or sit at the birds) until this is done.
You'll have to then mount usb in clockworkmod recovery so you can copy the rom.zip from your PC back to the tablet to install.
Same problem ... no workie
I can nvflash CMV5504.
Immediately after nvflash I can boot into TnT.
I can then boot to CWM and install my flavor of ROM (Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8).
I can then reboot from within CWM and it boots correctly.
When I turn it off and reboot it hangs at the birds. Every time.
I tried repartitioning first at 2048/0 and then at the combo of 4096/0 followed by 2048/0. As usual, it boots correctly and then on reboot will hang at the birds.
Pretty confident that I'm on bootloader 1.2 as I've installed Illuminate (Honeycomb) + Clemsyn Combo in the past which requires 1.2
I'm stuck!!!
huckbucket said:
I can nvflash CMV5504.
Immediately after nvflash I can boot into TnT.
I can then boot to CWM and install my flavor of ROM (Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8).
I can then reboot from within CWM and it boots correctly.
When I turn it off and reboot it hangs at the birds. Every time.
I tried repartitioning first at 2048/0 and then at the combo of 4096/0 followed by 2048/0. As usual, it boots correctly and then on reboot will hang at the birds.
Pretty confident that I'm on bootloader 1.2 as I've installed Illuminate (Honeycomb) + Clemsyn Combo in the past which requires 1.2
I'm stuck!!!
Click to expand...
Click to collapse
You need to be using the NVflash program that includes CWM 3028 not the 5504. The NVflash program with CWM 5504 sets different partition tables ment for the ICS build by DRH. To other 1.2 roms I would highly suggest doing your NVflash with the program that includes CWM 3028 instead.
1. NVflash using program that includes CWM3028
2. Boot into CWM immedently after the NVflash process is done.
3. Perform the 3 wipe process, Data/Factory reset, Cache, and Dalvic.
4. In CWM go to Mounts and Mount System then Format System.
5. In CWM go to Advance and Partition SD card 4098/0 then 2048/0.
6. In CWM Fix Permissions, DO NOT SKIP.
7. Mount USB and transfer New Rom, and Gapps if needed.
8. Install and Enjoy.
If for any reason there is a boot loop. Boot back into CWM and perform the 3 Wipe process again and reboot.
huckbucket said:
I can nvflash CMV5504.
Immediately after nvflash I can boot into TnT.
I can then boot to CWM and install my flavor of ROM (Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8).
I can then reboot from within CWM and it boots correctly.
When I turn it off and reboot it hangs at the birds. Every time.
Click to expand...
Click to collapse
Based on your symptoms, I would have to say that you nvflashed one of the older versions of CWM 5504. The version of CWM 5504 from the viewsonic gtablet for dummies site is known to have the "hangs at reboot" problem you describe.
The temporary fix--to allow you to boot--is to format the MSC partition using nvflash. The permanent solution is to install the latest version of CWM 5504: beta15.
To format MSC, run these commands in a CMD.exe window--make sure that you're in the directory which contains both the nvflash program and the bootloader.bin file, then:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable part.txt[/B]
After the command completes, look through the part.txt file for the partition number for the MSC partition. Assuming it is 7 (most commonly it is), format the partition to let you boot the tablet:
Code:
C:\SOME\PATH> [B].\nvflash -r --format_partition [I]7[/I] --go[/B]
---------- Post added at 08:52 PM ---------- Previous post was at 08:47 PM ----------
nobe1976 said:
You need to be using the NVflash program that includes CWM 3028 not the 5504. The NVflash program with CWM 5504 sets different partition tables ment for the ICS build by DRH. To other 1.2 roms I would highly suggest doing your NVflash with the program that includes CWM 3028 instead.
Click to expand...
Click to collapse
No need: You can use CWM 5504 Beta 15 with any ROM, not just ICS.
Thanks guys. Technically, rajeevvp your post helped, but only when I implemented it this way;
http://forum.xda-developers.com/showpost.php?p=23467943&postcount=48
I'm up and running now. Seems pretty stable. Have rebooted 4-5 times and it comes back every time.
huckbucket said:
Thanks guys. Technically, rajeevvp your post helped, but only when I implemented it this way;
http://forum.xda-developers.com/showpost.php?p=23467943&postcount=48
Click to expand...
Click to collapse
Some clarification would help. There are a lot of steps in that link, and most of them don't have any bearing on your problem. The same goes for the steps in nobe1976's post, above.
In both sequences only the 1st full nvflash command changes the MSC partition--and so fixes your problem as a side-effect. All the other steps are basically irrelevant, and more importantly, needlessly wipes the ROM and the user data.
rajeevvp
No need: You can use CWM 5504 Beta 15 with any ROM said:
Granted yes you are correct that you can run any 1.2 ROM with 5504 as your recovery, but the only thing I recommended was to use the NVflash file with CWM 3028 only because it would allow them to install those 1.2 roms also without issues. 5504 is what you posted BETA and with my experience with that recovery is that it can cause SOD just like the ICS rom. Which the only way out is to either let your tablet's drain its power or crack the case and press the internal rest button, which I had to do twice in 5504 not the ROM. If they are testing out DRH ICS then yes you must use the 5504 version as recommended, but to my opinion any other 1.2 base ROMS they should use a more stable CWM recovery like 3028
Click to expand...
Click to collapse
nobe1976 said:
5504 is what you posted BETA and with my experience with that recovery is that it can cause SOD just like the ICS rom.
Click to expand...
Click to collapse
First things first: Recovery mode never goes to sleep, so a Sleep-of-Death (SOD) there is out.
What actually would've happened is most likely this:
Some background first: the recovery program in CWM-5.5.0.4 sets a timeout before waiting for any input. This input timeout is set to 1 hour, and if an hour elapses without any user input, recovery is coded to reboot the system. (There is a bug (actually, two) in the coding which prevents this from actually happening every time, but, that is a matter for the developers.)
So, in your case:
- You were sitting in the main menu, and the input timeout expired after 1 hour of inactivity.
- CWM rebooted the tablet as programmed.
- Tablet booted silently into ROM (most likely ICS).
- USB cable most probably also connected.
- ICS goes to sleep with USB connected.
- ROM SOD.
If they are testing out DRH ICS then yes you must use the 5504 version as recommended, but to my opinion any other 1.2 base ROMS they should use a more stable CWM recovery like 3028
Click to expand...
Click to collapse
As you can see from the above, the SOD happened in the ROM (and not in CWM), and the new timeout behaviour is not likely to trouble most users, so you can, in fact, use CWM-5504 instead of 3028. I currently have 5504 on my 1.1 bootloader and it works pretty much as advertised.
rajeevvp said:
First things first: Recovery mode never goes to sleep, so a Sleep-of-Death (SOD) there is out.
What actually would've happened is most likely this:
Some background first: the recovery program in CWM-5.5.0.4 sets a timeout before waiting for any input. This input timeout is set to 1 hour, and if an hour elapses without any user input, recovery is coded to reboot the system. (There is a bug (actually, two) in the coding which prevents this from actually happening every time, but, that is a matter for the developers.)
So, in your case:
- You were sitting in the main menu, and the input timeout expired after 1 hour of inactivity.
- CWM rebooted the tablet as programmed.
- Tablet booted silently into ROM (most likely ICS).
- USB cable most probably also connected.
- ICS goes to sleep with USB connected.
- ROM SOD.
As you can see from the above, the SOD happened in the ROM (and not in CWM), and the new timeout behaviour is not likely to trouble most users, so you can, in fact, use CWM-5504 instead of 3028. I currently have 5504 on my 1.1 bootloader and it works pretty much as advertised.
Click to expand...
Click to collapse
Actually what happened when my tablet "Timed Out" as you say I was actually setting things in CWM to get it ready for update 1.0. Never did I once let it sit doing nothing. So I selected "Power Off" option so that the tablet can Charge before I flashed the new update and no I already unplugged my usb connection I used for NVflash, I have all my updates, backups and ROMS on a 16gig external SD card so there was no need for the USB connection while in CWM 5504. When I selected the Power Off option it just stayed there saying "Powering Off" for over 15 mins, which uses to just close CWM and power off the Tablet. This time it never booted out of CWM and never Powered off. That was a good reason for me creating my own DRH. The Second time was during a Reboot after flashing a 2.3 based ROM., also no need for the USB since I downloaded and transferred everything needed to my External SD before hand. So with that being said do you really think that CWM 5504 doesn't cause a form of Timing Out or Freeze up that requires the need to either press the rest button to recover.
nobe1976 said:
Actually what happened when my tablet "Timed Out" as you say I was actually setting things in CWM to get it ready for update 1.0. Never did I once let it sit doing nothing. So I selected "Power Off" option so that the tablet can Charge before I flashed the new update and no I already unplugged my usb connection I used for NVflash, I have all my updates, backups and ROMS on a 16gig external SD card so there was no need for the USB connection while in CWM 5504. When I selected the Power Off option it just stayed there saying "Powering Off" for over 15 mins, which uses to just close CWM and power off the Tablet. This time it never booted out of CWM and never Powered off. That was a good reason for me creating my own DRH. The Second time was during a Reboot after flashing a 2.3 based ROM., also no need for the USB since I downloaded and transferred everything needed to my External SD before hand.
Click to expand...
Click to collapse
You said you had a SOD problem, but this isn't Sleep-of-Death at all. Its something completely different: lockups when powering off or rebooting. The cause of that is usually some kind of kernel bug--badly coded device drivers are one possibility. It could also be some kind of transient hardware problem--wonky hardware can cause even well written device drivers to go nuts. And both of those mean that we can, again, exonerate CWM. Specifically:
When you select reboot or power off in CWM, it just calls a (Bionic) C library function which, on the gTab, immediately calls the kernel which starts the reboot/power off sequence. And, if the kernel can't reboot or power off the tablet, then that's where the problem lies. The fact that I've heard this problem report only from you--and that too only on 2 occasions--just makes the case stronger. As a good example of the former (bad kernel code) consider the nVidia/Malata-written mtdblock device driver for the NAND flash. It is known to have problems. Try this simple command in CWM:
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]dd if=/dev/block/mtdblock0 of=/dev/null[/B]
I wouldn't be surprised if the tablet locked up instantly; though it usually takes 2 or 3 tries. You can try this on any CWM version you want. You can even lockup the ROM the same way.
So with that being said do you really think that CWM 5504 doesn't cause a form of Timing Out or Freeze up that requires the need to either press the rest button to recover.
Click to expand...
Click to collapse
See above.
I created this thread because I have looked all over and have been unable to find someone with the exact same issue(s).
I said "sort of" in the title because twrp is working. Ok, so before everyone asks if I have nvflash, the answer is no. I did not have the right version of firmware, and did not try to install it originally. Since I was able to install roms, I figured I was fine...oops.
Twrp is not properly installing roms. More on that later. I am getting to the asus splash screen that says my device is unlocked, but it is stuck there.
My last working rom was the deodexed stock JB rom from craig gomez. I installed it with goo and when I installed that, I lost custom recovery and root, so I decided to go back to a more custom rom so Titanium backup would work. When I did that, I tried also tried again to make nvflash work. I got through the first step, it said it was successful, except I never got the little message in the upper left corner that I was supposed to get. I did not think it was a big deal because my prime would still boot like normal.
Then I installed twrp 2.3.1.0 and I have tried flashing previous restore images. I have tried installing the roms on my sdcard. I cannot get past the asus splash screen.
If I try installing a rom with the force md5 check enabled, it does detect an md5 and then quits.
If I try intalling a rom without the force md5 check, i get an error that says E:Unable to mount '/staging'
When I try installing a backup everything seems to work okay, but then I get the same error E:Unable to mount '/staging'
When I try to install roms through fastboot, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I try using adb, I do not see any devices.
I tried putting CWM on the prime to see if I could install from that instead, but it would not load after install.
I tried putting an older version of twrp on the prime, to see if that was the issue because I used to have an older version...I could not get that to load either...so I went back to this version.
Any ideas or suggestions would be awesome guys. I am stuck.
I even went to install the naked drivers again, and when I try to flash a different recovery, I get the <waiting for device> text that never goes away.
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
godlyitem said:
i'm sort of on the same boat. my prime just keeps booting into twrp recovery no matter what i tried. i'm still hoping to find a solution to this problem.
Click to expand...
Click to collapse
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
big time noob said:
For me, I can let it try to boot normally, but I get stuck at the splash screen. This device is unlocked.
If I hold down the volume down button, I can go to fastboot, or RCK for recovery...but it does not work properly.
Click to expand...
Click to collapse
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
godlyitem said:
i just tried to flash cwm in the terminal, it wrote stuff on the memory, but didn't seem to do anything. it booted straight back to twrp. i can't even get it to go to fastboot!!! only if i can go to fastboot, i could save my prime!!!
Click to expand...
Click to collapse
Yeah, I thought that too, but fastboot does not work properly either...argh. I wish one of the gurus would chime in here.
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
Click to expand...
Click to collapse
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
godlyitem said:
EVERYONE i fixed it!!!!!!!!!!!!!!!!!! !!!! it's alive again!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
That doesn't really help us. If possible, can you edit/delete your message so that the guys that might help do actually help? Don't want them to think this is done.
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
mercydia said:
Same Here.. It all happened when i restored my files using titanium backup and when i rebooted im stuck at boot scrren
EDIT: Guys I did a prime fullwipe and flashed stock jb and now prime is restored to its original state..
""I also got some errors like md5 file could not be found and could not find the /staging""..but after the reboot it works perfect
EDIT 1: Now after the prime fullwipe and flashing stock jb i flashed twrp recovery and now it works perfect without a single error even the above mentioned errors were gone
Click to expand...
Click to collapse
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
godlyitem said:
here is what i did. get into twrp recovery. flashed full prime wipe -> right after that flash the stock jb US version directly dled from Asus -> reboot then you will be stuck at the splash screen (that's a good news). Hold down power + volume down until your prime turns off and restart (keep holding those two keys) until the 3 icons appear then flash w/e rom you want in recovery. It's alive!
Click to expand...
Click to collapse
big time noob said:
In twrp I do not see anything that says Full Prime Wipe. I see something that says wipe. Are those the same? I tried doing a wipe from this screen, but it did not work for me as expected.
Click to expand...
Click to collapse
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Thanks. That is what I needed to know.
I will see if I can make this work when I get back from work.
godlyitem said:
no full wipe is a stand alone zip file you have to google and find dl it. put it in your prime then flash it
Click to expand...
Click to collapse
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
big time noob said:
Can you clarify what the Prime fullwipe is and how you got there?
I do not know if it will help me.
I can't even do the wipe command from fastboot.
Just says <waiting for device>
I have tried the wipe command form the boot screen (the one with fastboot and RCK as options), that did not work properly either.
Ryan
Click to expand...
Click to collapse
Download the zip:
http://goo.gl/hiFHB
Goto to Twrp recovery and install the zip..Since it supports microsd u can transfer the zip to microsd.
Goto TWRP -> INSTALL -> CHOOSE EXTERNAL SD -> INSTALL THE ZIP
It will completely wipe the internal storage and then download the official STOCK JB FROM ASUS SITE and follow the same steps to install. Now install the latest twrp recovery using fastboot
big time noob said:
I am pretty sure I am F***ed.
I tried the prime full wipe. It worked the first time, I think. Then went to install a rom.
I had to do both through external SD in twrp because my adb is not working. Also, fastboot only works to install a recovery. The only version of any recovery I can make work is twrp 2.3.1.0
If I try an older version or CWM, it freezes where I try to go into recovery.
Unable to mount data error.
Unable to mount system error.
Same as before.
I tried using unbricker software I found, but since adb does not work properly, the software does not work properly.
I am going to see if I can work my charm and get them to take back my tablet at best buy for an infinity. I have read about other people pulling it off.
I think as we get closer to xmas my odds improve...UNLESS SOMEONE HAS ANOTHER IDEA??? I would love to try something else.
Eyeballer suggested a chat room channel thing, but most of the people are in europe and I would need to do it in the morning...I do not have time for that, but I may try it.
Click to expand...
Click to collapse
When I was doing the fullwipe the same errors happened to me.. But dont mind..I got errors like
1. No md5 file found
2. Mount error
3. Cannot find /staging
Just follow the above the steps ull get it right
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Yeah, I should have said I tried that first. I also tried the stock rom from asus. When that didn't work, I tried the stock rom deodexed I found in goo.
There are a bunch of permission errors going on inside my prime. When I go into the mount area, it will not let me mount the data to move it. Or, when I try to copy it over I get a failed message.
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
godlyitem said:
did you even follow my step by step guide? you can move the stock rom from external SD to your internal SD in advance -> file manager.
Click to expand...
Click to collapse
Fixed?
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
big time noob said:
Okay. I wiped it again, from twrp.
Then it let me move the file from the ext-sdcard to the sdcard.
I used the prime full wipe.
Then I tried to install the stock rom by transferring it in twrp file manager.
I got the file onto the sdcard, but when i tried to install, it said Failed.
That was it.
I even tried installing the ICS version I got from ASUS. Same thing.
Now, I am going to try to access via unbricker...don't know if it will work, but I am out of ideas.
Click to expand...
Click to collapse
big time noob said:
I am alive!
us-tf201-jro03c-10.4.2.15-stock-deodexed.zip
That is the last rom I successfully used.
I used all sorts of different wipes. I was in twrp and noticed my pc installing the transformer adb driver. So I hopped into adb to see if it would see my device with that driver. (it did, but it wasn't before from the fastboot or adb commands with naked driver).
I tried sideloading the above rom from twrp. It worked.
Thought others might want to know.
I do not know if I can install other roms or not. I am a little scared to try just yet.
Click to expand...
Click to collapse
You will have the jelly bean bootloader now so as long as you stick to it you should be fine. The only other thing I would suggest is check you version of twrp, you should be running the jelly bean version of it also. And if I am not mistaken, you need to be on ics to use nvflash (although I haven't checked the op recently so I could be wrong) so definitely stay away from that unless you downgrade.