Related
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.
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
Yes I am new to rooting droids, but I am not illiterate in this subject. However, I am pregnant, and over emotional and possibly losing my mind because I can't get my phone to work. (Sounds like a noob issue right?!)
I have a droid 2, latest update, blahblah.
I rooted it, no problem, got good instructions from here, downloaded ROM manager, and Bootstrap. I downloaded Liquid Dream ROM. Flashed Clockwork, and rebooted. ROM seemed to download onto the device fine, finished rebooting and now it plays the Liquid Dream animation on start up over and over. Currently I am in reboot mode but I am stuck, I don't know where to go from here (because I am a noob, I know). So I'm hope full that someone with a lot more knowledge on this can help me out, so I don't totally lose my mind. Thanks for your time future person who helps me! (I hope)
did you wipe all the data/cache and davlik prior to installing a new rom. When ever changing roms, you need to clear out the old data.
go into fastboot, clear data/cache and under advance clear dalvik.
try that.
ChelseaLynn__ said:
Yes I am new to rooting droids, but I am not illiterate in this subject. However, I am pregnant, and over emotional and possibly losing my mind because I can't get my phone to work. (Sounds like a noob issue right?!)
I have a droid 2, latest update, blahblah.
I rooted it, no problem, got good instructions from here, downloaded ROM manager, and Bootstrap. I downloaded Liquid Dream ROM. Flashed Clockwork, and rebooted. ROM seemed to download onto the device fine, finished rebooting and now it plays the Liquid Dream animation on start up over and over. Currently I am in reboot mode but I am stuck, I don't know where to go from here (because I am a noob, I know). So I'm hope full that someone with a lot more knowledge on this can help me out, so I don't totally lose my mind. Thanks for your time future person who helps me! (I hope)
Click to expand...
Click to collapse
Well, something probably didn´t upload ok. So, what you have to do know is: make sure the .zip file in the sdcard is not corrupted. In order to make sure of that, you can try to download it again (you will need an sdcard reader). Then, when you have already the .zip file in the sdcard, boot into recovery. From boot loop the best way is to boot the phone pressing power + volumen down, then choose recovery from the hboot menu. Once you are in the CWM recovery menu, do a wipe data / factory reset. wipe cache partion and format system.
When that is done, you are able to flash the zip file from install .zip from sdcard choice. That should work and get your cell back to life.
It might be Clockwork. There have been some issues with it. If none of the above suggestions work, try getting Amon Ra.
If ClockWorkMod does not work you can try flashing the 4EXT recovery...works smoothly at least in my Inspire 4G.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
I browsed through the general q&a and i am not finding exactly what i am looking for, so please hold the yelling if i missed it. but i am not against being told where to go....
background info....I purchased a DNA off of EBay and i turned it on, and got it going. The SW version is current, stock rooted and the phone is S-Off. The phone still had some of the guys pictures on it, so i jumped in to recovery (CWM touch recovery) and wiped the phone, cache, and restarted. When i did the phone hung, and never booted, so i held the power button down, it then rebooted, checked the apps and all was good. his pics are still on the phone.....going through the phone and wiping (backup and reset) and it's the same thing....
So my question is, what can i do to get the phone back to square one, fully clean but still keep the root and s-off? the reason i am asking is when i wiped it wouldnt boot properly. should i reflash a stock rooted rom? whats the best way to wipe the internal memory? i have rooted and rom'd going back to the original droid, but the HTC's always intimidate me. So please any suggestions they would be welcome. I want to get it stock, then make a perfect good backup, then start trying some roms.....
Thanks in advance!
So I read up a little more, and decided that the best thing to do was Format the SD card. After i did that, i wiped everything again and after it boots, it still just hangs. Then i hold power down and it restarts and i get the "android is upgrading screen" then i am fine. So i am still concerned that it never boots properly. So my question still stands..... should i download another stock rom, or is there something else i should do?
mooseknuckles said:
So I read up a little more, and decided that the best thing to do was Format the SD card. After i did that, i wiped everything again and after it boots, it still just hangs. Then i hold power down and it restarts and i get the "android is upgrading screen" then i am fine. So i am still concerned that it never boots properly. So my question still stands..... should i download another stock rom, or is there something else i should do?
Click to expand...
Click to collapse
if you wipe the phone in recovery ( im assuming /data, /cache, /dalvik, and/or /system) you would have to flash a new ROM on top of that, because you are wiping the entire thing. i dont think you can do a regular wipe in CWM and expect it to boot after that. but, yes, for what you want, formatting /sdcard would probably suffice.
[indiferenc] said:
if you wipe the phone in recovery ( im assuming /data, /cache, /dalvik, and/or /system) you would have to flash a new ROM on top of that, because you are wiping the entire thing. i dont think you can do a regular wipe in CWM and expect it to boot after that. but, yes, for what you want, formatting /sdcard would probably suffice.
Click to expand...
Click to collapse
I don't think cwm wipes the rom by selecting factory reset in it.
Sent from my HTC6435LVW using xda premium
It doesn't, and if he had wiped system it never ever ever would have booted even after resetting it 9001 times.
Wiping data, factory reset, same thing different terms for different versions of recoveries, technically wiping data would delete sdcard with /data/media but usually doesn't. Format SD and a factory reset/data wipe would be what he's looking for, but it not booting afterwards is an issue pointing to something else.
I'd suggest looking at your current ROM version then getting a rooted version and flashing it then seeing if it persists. Any ROM will do, really, I just said that way if you want to stay on that version of sense.
Tapatalked from my HTC DNA - ReVolt