And it keeps going and going, kinda like the energizer bunny, but I don't want it to keep going, I want it to boot...has anyone had a similar problem? I followed the instructions to the letter, any ideas?
There must be an issue with your ROM install. Try going to ClockworkMod and restoring to factory reset, along with wiping cache and dalvik cache.
If that fails, reflash a newer or different ROM with the above steps done as well.
GL :good:
Related
OK i have to say i m not a noob anymore. And i m pretty confident.
Having said I am coming from Vegan 5.1 and tried many times to download the new Vegan Ginger. But each time I got stuck at the "birds" screen.
And yea I do all the same steps for when i was ROMing to Vegan 5.1
So my questions are: why isn't it working this time?
Do i have to be on Stock Rom for it to work?
Any suggestion?
Thank you
Its always a good idea to start from stock and then going to custom rom. I suggest you use nvFlash to go back to stock, then flash cwm .8 and then try to follow your steps to install it.
enjoy
Best way to flash a new rom is to fully wipe data cache dalvik ect ect do that in cwm then install zip from disk. Works every time and usely it take like ten minites to fully install. If you need help just look around or ask.
Good luck
Awessssoooommmee
You guys are awesome
I just Nvflash and Install the ginger edition easily
Thank youuuuu
I'm having the exact same problem. Even fully wipe data, cache and davik does not help.
I noticed that, when ClockworkMod Recovery showed that it was installing update, the progress bar stayed grey, not changing or moving at all.
Guess I'll have to try nvflash.
Yeah do that
ww9rivers said:
I'm having the exact same problem. Even fully wipe data, cache and davik does not help.
I noticed that, when ClockworkMod Recovery showed that it was installing update, the progress bar stayed grey, not changing or moving at all.
Guess I'll have to try nvflash.
Click to expand...
Click to collapse
Yea do that, cause it looks like this ONLY works on stock rom. And after that just do your usual process, and you should be good.
Everything went so well that my first boot took less than a minute
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
venkavis said:
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
Click to expand...
Click to collapse
Hopefully a guru can answer this question. A guru I am not..
But what I think you did should not be an issue. I typically wipe data and then wipe cache partition when flashing a new ROM. sometimes I wipe cache and data just to get the ROM running from scratch again. But this should not affect booting..
One thing I think might be the problem is that you have a new kernel from one of the newer nightlys. Recently they added perhsoots May kernel. Whenever a new kernel is included in a nightly you usually need to clear dalvik cache. this is in CWM under advanced.
I hope this helps.
Tried clearing dalvik cache. No change.
Going back to stock and see.
Copied the stock ROM file and used the CWM to do the update. Now the g Tablet is gioing into a Boot loop. It Tap n Tap then displays a animated icon and after a minute repeats the same.
Tried the recovery option and its going into an installing loop again. Not sure how to get out of this.
Does anybody have this experience before?
Is this bricked now? Call viewsonic support? I am not sure if they support, They may say its nor under warranty.
Just to remind you, the last effort to resolve this is to NVFLash it...
Have you tried CWM method twice or repartition it and do it again? It's a tablet for you to enjoy your Internet, reading, video but not flashing all day long..etc
To pass it quick, if I were you, I would NVFlash it back to 3588, put back my favorite ROM, reinstall the Apps I like and start Internet browsing, converting movie (so I can watch on the road), reading news...
good luck!
rcjpth
After this I definitely agree. But seems I am stuck again. Hope this is the last time.
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Called Viewsonic support and the tech support person pointed me to below post on XDA
http://forum.xda-developers.com/showthread.php?t=1036956
When I read the article it talks about a locked boot loader. Does is mean if I use this and fix the tablet, I will not be able to do any more rooting?
venkavis said:
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Click to expand...
Click to collapse
So you also tried the alternate file, nvflash_gtablet_46_2010112600.zip? That's what worked for me, but I also have to swap partitions 7 & 8 to get CM7 working again.
Since I'm a glutton for punishment, I wiped my cache from nightly 75 and didn't run into any problem.
Just downloaded the alternate zip and flashed again. Having the same looping issue.
Seems like I Have to send it to viewsonic only. The technician said there is a $75 charge to fix.
(I searched before asking)
So I'm flashing my buddy's Metro Ascend. I got it rooted. Flashed CWM Recovery 2.x.x.x. (The common one, .5.1.8, I think). It hangs if I try to format the cache, period. Hangs during factory reset, wipe cache and format cache. I stupidly flashed anyway and it seemed to work, but after a reboot, the entire system seems broken. Force closes left and right and the Launcher doesn't load. It still received incoming calls at first, but now it doesn't even do that. I'm not too familiar with troubleshooting this particular phone and my friend really needs it fixed. So please, someone help me? (No lectures or flaming please, just advice. I'm not looking for motherly scolding about my irresponsibility )
Sent from parts unknown.
Probably need to wipe the phone clean and flash rom again. If cwm is not working good try Amon Ra.
There's also a system format file floating around that you can flash in recovery to wipe your system clean.
Thanks. Never heard of Amon Ra but I'll look it up. The inability to finish the wipe data/factory reset kills me. I know my way around a Captivate with my eyes closed, but this is all goofy to me.
Still open to suggestions if anyone else has something to add. Easy way back to stock? Suggestions for a good rom/mod to flash? (Currently attempting Icarus 1.0)
Sent from parts unknown.
I followed the directions to root on the LOOK HERE FIRST, so I installed Clockwork, then flashed the root zip, and that's it - I never installed any other ROM. It seems to operate just fine, but then at some point when I reboot it gets stuck at the Samsung logo. I repeatedly restore my NAND backup from before I rooted, flash the root zip again (and I tried redownloading it, in case it was corrupted), and try rebooting and it boots just fine. But then it always breaks itself and boot loops again after a while. I've done this a couple times.
I have the Wifi only tab 10.1 7510 (U.S.).
I suggest following this guide, step by step. It never fails.
This one will get you back to a fresh start.
http://galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-unroot-your-galaxy-tab-10-1/
And this one will get you rooted properly.
http://galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
After that, just make sure to do a nandroid/Titanium Backup before wiping Cache, Dalvik Cache, and then data, all before installing a new ROM.
And after you do the 3x wipe, don't boot up at all. Just install straight from recovery.
kehlan said:
I suggest following this guide, step by step. It never fails.
This one will get you back to a fresh start.
http://galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-unroot-your-galaxy-tab-10-1/
And this one will get you rooted properly.
http://galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-unroot-your-galaxy-tab-10-1/
After that, just make sure to do a nandroid/Titanium Backup before wiping Cache, Dalvik Cache, and then data, all before installing a new ROM.
And after you do the 3x wipe, don't boot up at all. Just install straight from recovery.
Click to expand...
Click to collapse
Those are both the same link, I'm guessing a mistake? I would be interested in the better root tutorial.
This last attempt seems to be working so far. I systematically restored/redid things and tried rebooting to try to rule out possibilities. The one thing I did differently this time is that I installed Busy Box to /bin instead of /xbin (Titanium Backup restore hangs without Busy Box). Go figure.
Earned yourself a thanks by pointing out my mistake.
Updating that post momentarily.
Edit: Updated, best of luck getting everything working.
kehlan said:
Earned yourself a thanks by pointing out my mistake.
Updating that post momentarily.
Edit: Updated, best of luck getting everything working.
Click to expand...
Click to collapse
I think it would be better if you updated the post permanently. Seems silly to just do it momentarily.
I meant I was going to update it momentarily from the point I had noticed it was wrong.
It's been correct since then, hope everything worked out.
Just the other day I had a weird thing happen. I rebooted my phone and when booting I saw Android is updating, followed by optimizing apps and starting apps. I had not run any update of any kind at all. The phone booted fine and ran fine afterwards. Now everytime I reboot the phone, I get the same message Android is updating then it says starting apps and then the phone boots up as normal. Anyone know why this is happening? Is this a problem? I had a similar thing happen on my tablet and when I ran a firmware update afterwards then started getting all kinds of errors.
If this is a problem how do I fix it? And with this happening should I not run any updates?
I am rooted and on stock firmware with no updates installed.
Thanks in advance everyone!
This happens when cache is cleared, anytime you flash a ROM or kernel you are supposed to wipe cache and most packages will do this for you. Your tablet doing this after a firmware upgrade is normal, the errors weren't.
Now if your phone is doing it every reebot it probably means one of two things: 1 your system is wiping cache every shutdown for some reason or 2 your cache partition is corrupted.
If you are unrooted I recommend talking to Verizon (or whomever you purchased it from) about warranty, if its rooted I would try wiping cache and dalvik cache through your recovery (this will cause it to happen one more time but might prevent a second or third) and see if it keeps doing it after three reebots. If that doesn't work wipe everything (cache, dalvik cache, and user data) and reflash your ROM or another ROM. If that doesn't do it either unroot and talk to Verizon about warranty (after resetting the flash counter)
Sent from my SCH-I545 using xda app-developers app
What's the right way to wipe the cache and dalvik then? Should I use titanium backup? Not sure how to do it from recovery on this phone. And will doing this have any side effects?
Thanks again
Also, I haven't flashed any roms or new kernels.
Please, any and all responses and ideas. Im sure the last person that replied knows what he/she is talking about but I just need a lil more info...
Thanks again all!
Sent from my rooted Galaxy S4
Depending on the release, MDk, ME7, MI1, MJ7 you may not be able to wipe the cache manually from the recovery menu.
Whn I was on ME7, no problem. Now that I'm on MI1, I can't do a manual wipe.