Related
This is my first experience trying to mod a device but everything I read said it was easy so I bought the Gtab and spent 4 hours yesterday trying to flash VEGAn-TAB GingerEdition STABLE RC1 but it won't boot.
The first thing I did was root the device following instructions from driod pirate (before I found XDA). I now know I didn't need to do that step.
After rooting it, I found this post with great step by step instructions for installing clockworkmod and flashing a rom. I followed the instructions to install ClockwordMod and the VEGAn-TAB GingerEdition rom. After trying to boot, it stuck on the ViewSonic splash screen.
I did some more research and thought I might need to downgrade the bootloader/tnt version so I followed these instructions and was able to successfully load the stock rom. I then followed the same steps above to install clockworkmod and flash the vegan rom. Again, when trying to boot, it just sticks on the ViewSonic splash screen.
Any ideas what I might be doing wrong?
Do I need to do a nvflash and try the process from the beginning again?
dw21 said:
This is my first experience trying to mod a device but everything I read said it was easy so I bought the Gtab and spent 4 hours yesterday trying to flash VEGAn-TAB GingerEdition STABLE RC1 but it won't boot.
The first thing I did was root the device following instructions from driod pirate (before I found XDA). I now know I didn't need to do that step.
After rooting it, I found this post with great step by step instructions for installing clockworkmod and flashing a rom. I followed the instructions to install ClockwordMod and the VEGAn-TAB GingerEdition rom. After trying to boot, it stuck on the ViewSonic splash screen.
I did some more research and thought I might need to downgrade the bootloader/tnt version so I followed these instructions and was able to successfully load the stock rom. I then followed the same steps above to install clockworkmod and flash the vegan rom. Again, when trying to boot, it just sticks on the ViewSonic splash screen.
Any ideas what I might be doing wrong?
Do I need to do a nvflash and try the process from the beginning again?
Click to expand...
Click to collapse
You need to follow the nvflash instructions on the developer page. Your partitions need to be fixed before gb roms will work
I suggest the first thing you do is setup nvFlash. I can assure you that you will need to use this utility at some point. It is very usefull and powerfully utility and is very easy to setup and use. http://forum.xda-developers.com/showthread.php?t=861950
once you set that up..i suggest you start from scratch.
So this is what I would do if i was in your shoes.
1. Install nvFlash and go back to stock.
2. Update to 3588 using OTA
3. Install cwm .8 on your tablet
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
6. Mount your tablet using cwm .8 and upload the rom you want to install
7. Install the rom you want and you should be good to go
(dont forget to reboot your device after that first boot.)
What is the risk involved with NVFlash? I've read a few complaints that their devices were bricked after nvflash. How do I make sure I avoid that happening?
dw21 said:
What is the risk involved with NVFlash? I've read a few complaints that their devices were bricked after nvflash. How do I make sure I avoid that happening?
Click to expand...
Click to collapse
Anytime you brick it, you can use nvFlash to un-brick it. Its just a matter of knowing what you are doing and reflashing it with the correct files. From what I have experienced, its pretty much impossible to brick these tablets once you have nvFlash setup. No matter how bad that situation is, I have always been able to recover using nvFlash(and I have been in very terrible situtations where I got a blank screen when i booted...turns out I was stuck in apx mode when i booted)
rbansal2 said:
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
Click to expand...
Click to collapse
Can you go into more details on these two steps? I know it's done with cwm but I want to make sure I do it exactly right.
worked for me
Thanks guys this worked great! For some reason I couldn't upgrade to 3588 it would FC at 50% but it works now!
clayvikings said:
Thanks guys this worked great! For some reason I couldn't upgrade to 3588 it would FC at 50% but it works now!
Click to expand...
Click to collapse
Awesome, that's great news! Welcome to the club!
rbansal2 said:
I suggest the first thing you do is setup nvFlash. I can assure you that you will need to use this utility at some point. It is very usefull and powerfully utility and is very easy to setup and use. http://forum.xda-developers.com/showthread.php?t=861950
once you set that up..i suggest you start from scratch.
So this is what I would do if i was in your shoes.
1. Install nvFlash and go back to stock.
2. Update to 3588 using OTA
3. Install cwm .8 on your tablet
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
6. Mount your tablet using cwm .8 and upload the rom you want to install
7. Install the rom you want and you should be good to go
(dont forget to reboot your device after that first boot.)
Click to expand...
Click to collapse
I did exactly this (minus step 1. as it was already a stock device) and I had exactly the same problem - gtab stuck at viewsonic splash screen. My unit was fresh outta the box and fully charged, and this was the firstht hing I tried to do with it. CWM installed without a hitch (yes, 0.8) and I repartitioned without fear (I had no data on it anyway). Did the wipes, mounted the tab and copied over the rom... all instructions I found on XDA for doing it. It still sticks at the splash screen.
So, to get a working tablet again, I used nvflash to go back to stock (though I have a superuser app now, which is odd for 'stock'), did the ota update to 3588, loaded Spark+ on it for a launcher and add the amazon marketplace app (looking for more free apps).
I still want to get VEGAn installed though, just wish I new why it was freezing up/not booting/not correctly installing or whatever the problem is.
If you have run nvflash you can now install Gingerbread roms as it fixed your partitioning. When you got stuck on the vs birds it meant your partitioning was wrong and you needed to nflash. If you did then your fine now.
The nvflash provided does not bring you to complete stock. If you want complete stock just flash the 3588 update.
I did the exact same thing you did, with the same result. Then I nvflashed and walked through the rest of the steps and I was quickly able to flash VEGAn-TAB.
dw21 said:
I did the exact same thing you did, with the same result. Then I nvflashed and walked through the rest of the steps and I was quickly able to flash VEGAn-TAB.
Click to expand...
Click to collapse
I've been watching the VEGAn-TAB logo flash and pulse at me for the past hour. Think I'm going to try to flash the ROM again...
EDIT:
Scratch that. restarted into cwm, cleared user data again, booted right into V. Going through setup screens now. Question though... If this was writtne for the G-Tab, then why does it still have the phone stuff in it?
was working but now it isn't?
++++i had to use nvflash for my gtab and it worked. I loaded vegan-tab 7.0 GE and it took "literally HOURS" to boot to the tablet setup page, after that it was working great until I rebooted it after 1 day of use and now i can't get past the "powered by g-tabdevs" boot page?????? any thoughts?++++
UPDATE: I repartitioned the sd card 2048/0 and that didn't work, then i cleared the dalvik (?) cache and the other cache and it booted up successfully (warning to newbs like me, this did clear all my data so back up everything)
SIDE NOTE: I love this website!!!
Two things I always do before I decide to try a new ROM, backup anything I don't want to lose, then go do a factory reset. When you install a new ROM, it doesn't automatically wipes all the partitions, especially the user data and settings. By leaving that there, you are allowing the ROM have access to that information which in turn, can cause problems because not every ROM setups the same. I have seen many people run into problems because they don't do a data wipe. If you do this, you will see a lot less problems in the future and if you do get a new install running but seeing FCs with a lot of apps, do a factory reset.
VEGAn-TAB GingerEdition STABLE RC1 Still In Boot Loop
Hi, I've tried doing as per what the instructions said about clearing the cashes and partition SD card sizing. I've load VEGAn-Tab 6 times already and everytime I still end up with a boot loop error. I just decided to use tntlite instead, but I really want to get this working. I noticed one thing as I was loading tntlite and the stock rom that when I go back to ClockworkMod v08 to mount “/system” and “/data”.
I see the following:
“unmount/system”
and,
“unmount/data”
which is right, but when after I load VEGAn-Tab
I see the following:
“mount/system”
and,
“unmount/data”
From what I've been reading this should not be the case. I'm not sure it this is related to my problem with the boot loop or not.
Please help!
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.
Just got my gtab for $270 as a toy and have been reading all the material I could find about flashing a new ROM waiting for it to arrive.
Of course, I got ahead of myself and may have screwed up right out of the box.
I forgot to see which boot loader I have (like I said...I was excited).
I downloaded CWM...installed it per the 'dummies' web page...all good.
Downloaded BL1.2 CM7.0.3 and transferred it per the dummies page...and hit install from zip file. It then dumped back to CWM where I installed GAPPS while still in CWM.
Then hit system reboot, and it got to the CM7 android screen with the looping arrow in a circle. Problem seems to be that it's been sitting on that screen with a looping arrow for about 20 minutes now. I read that it takes a while for the first boot to load everything, but am pretty sure 20 minutes is more than generous?!
Is there a way to see what BL I've got from CWM having already wiped out the method to find out (going into setting in android OS) by virtue of starting the CM7 ROM load?
Should I give up on this install of CM7, turn off the gtab, go back into CWM and try the install again AND reboot before installing GAPPS?
Having forgotten to look at the BL version, does it makes sense that I would have likely got BL1.2 being that this gtab is brand brand new?
Any help would be appreciated.
Thanks,
Joe
San Antonio TX
joseph.fox said:
Just got my gtab for $270 as a toy and have been reading all the material I could find about flashing a new ROM waiting for it to arrive.
Of course, I got ahead of myself and may have screwed up right out of the box.
I forgot to see which boot loader I have (like I said...I was excited).
I downloaded CWM...installed it per the 'dummies' web page...all good.
Downloaded BL1.2 CM7.0.3 and transferred it per the dummies page...and hit install from zip file. It then dumped back to CWM where I installed GAPPS while still in CWM.
Then hit system reboot, and it got to the CM7 android screen with the looping arrow in a circle. Problem seems to be that it's been sitting on that screen with a looping arrow for about 20 minutes now. I read that it takes a while for the first boot to load everything, but am pretty sure 20 minutes is more than generous?!
Is there a way to see what BL I've got from CWM having already wiped out the method to find out (going into setting in android OS) by virtue of starting the CM7 ROM load?
Should I give up on this install of CM7, turn off the gtab, go back into CWM and try the install again AND reboot before installing GAPPS?
Having forgotten to look at the BL version, does it makes sense that I would have likely got BL1.2 being that this gtab is brand brand new?
Any help would be appreciated.
Thanks,
Joe
San Antonio TX
Click to expand...
Click to collapse
Yes, you can temrinate your install if it hasn't finishws. Congrats on your first brick. Sometimes it just happens even when you use the correct files.
If it's a new tab you most likely you were on 1.2. If you boot back to CWM (PWR & Vol+) it will give you the CWM version. If you loaded the 1.2 CWM version it will say V3.0.2.8. In CWM try a wipe data/factory reset, wipe cache, wipe dalvik cache & fix permissions and then reflash the rom & gapps. If it loops again, go to dummies and run code red (use the version of nvflash with cwm). Follow the instructions step by step & download everything via his links since his instruction are written with them in mind. If you have problems just post back.
Al
Thanks for the advice! I did load CWM-BL1.2, and I guess by virtue of the fact that CWM-1.2 didn't crash my system, that I had BL1.2 on the gtab.
Went back and tried to load CM7 7.0.3 again, but no luck; then revisited the catch-all GB ROM thread and downloaded CM7 7.1RC, and it loaded.....so I'm up and running!
Now just got to learn more about the market....numerous favorite programs don't show up in the market.
Thanks again!
Ok, so I have rooted my x10 mini pro, and installed CWM recovery. I now have a ROM that I have decided on, but would like some clarification on something. According to install instructions, I just need to factory reset full wipe. However some devs tell you to also do a dalvik cache wipe and/or a cache partition wipe as well. Is it a rule of thumb that all 3 are done, or do you just settle for a factory reset full wipe, as per the dev's instructions? I really don't want to make a mess of my first attempt and get stuck in a boot loop or something even more disastrous. I currently have 2.1 stock, that I will be upgrading from. Thanks for any help.
cleggs said:
Ok, so I have rooted my x10 mini pro, and installed CWM recovery. I now have a ROM that I have decided on, but would like some clarification on something. According to install instructions, I just need to factory reset full wipe. However some devs tell you to also do a dalvik cache wipe and/or a cache partition wipe as well. Is it a rule of thumb that all 3 are done, or do you just settle for a factory reset full wipe, as per the dev's instructions? I really don't want to make a mess of my first attempt and get stuck in a boot loop or something even more disastrous. I currently have 2.1 stock, that I will be upgrading from. Thanks for any help.
Click to expand...
Click to collapse
I would make the three wipes to avoid any issue, but the most important is to make the backup from CWM before wiping anything.
KuSkUS_68 said:
I would make the three wipes to avoid any issue, but the most important is to make the backup from CWM before wiping anything.
Click to expand...
Click to collapse
Thank you for the reply. Yes, I'm aware about backing up my data. I probably will make 3 wipes, just to cover myself. I am a little concerned about things going badly, and not being able to start CWM to revert back to stock, if things don't turn out well, but that's just my nature to worry about such matters. lol. I will make a backup and then do the 3 wipes discussed, and then flash the new ROM. I will keep everything crossed, just in case. Thank you for taking the time to reply, much appreciated.
Don't worry too much
Got a x10 mini pro myself which I messed up real bad, a little tweaking here and some tweaking there and I got it running again. As long as you don't mess up the hardware, which is relatively not likely, you shouldn't having too much problems restoring it to working state
Well, that was very painless really. I did a factory reset, cache partition and dalvik cache wipes before and after applying the new Rom, and everything went very smoothly. Expecting a long first boot, as seems to be normal for this process, it booted so quickly, I thought I must have done something wrong lol. See! There's nothing to worry about after all....I told you so.
cleggs said:
Well, that was very painless really. I did a factory reset, cache partition and dalvik cache wipes before and after applying the new Rom, and everything went very smoothly. Expecting a long first boot, as seems to be normal for this process, it booted so quickly, I thought I must have done something wrong lol. See! There's nothing to worry about after all....I told you so.
Click to expand...
Click to collapse
Glad to know. You were absolutely right....
BTW which ROM have you tried?
KuSkUS_68 said:
Glad to know. You were absolutely right....
BTW which ROM have you tried?
Click to expand...
Click to collapse
I went for this one http://forum.xda-developers.com/showthread.php?t=1151499 I'm still playing around with it, but it seems very stable. Very nice work by paul-xxx
cleggs said:
I went for this one http://forum.xda-developers.com/showthread.php?t=1151499 I'm still playing around with it, but it seems very stable. Very nice work by paul-xxx
Click to expand...
Click to collapse
Mmmm... I installed the other ROM made by paul-xxx, MiniCM7Pro http://forum.xda-developers.com/showthread.php?t=1201116
It also works fine for me (although latest releases are showing some bugs), but I like that "Sony style". Probably I'll give it a try
KuSkUS_68 said:
Mmmm... I installed the other ROM made by paul-xxx, MiniCM7Pro http://forum.xda-developers.com/showthread.php?t=1201116
It also works fine for me (although latest releases are showing some bugs), but I like that "Sony style". Probably I'll give it a try
Click to expand...
Click to collapse
Only annoying thing I have found so far, is my virtual keyboard. When hitting the backspace or space keys, sometimes it's unresponsive which can be a little irritable. This is using the touchpal keyboard, but I did notice similar on the stock keyboard too. But everything else is very stable. Wifi works no problems at all, as does bluetooth (well, it starts up on demand, but I haven't actually used it yet lol) Notifications for new sms works well too (this can sometimes be temperamental on some phones) I've yet to test GPS but I know it starts well enough. And I've yet to have any FC's. It would be interesting to hear your comparison of the two versions, if you do decide to give it a try.
EDIT: oh, and radio works well too lol :-D
I remember my first ROM install... d*mn it went as wrong as anything could. Somehow i managed to install a ROM for the X10 on my X10 mini pro.
It froze at the bootanimation.
PC Companion fixed it.
Since then I have bricked my phone many times, experimenting with custom kernals and home-modding, PC Companion never failed me
[TUT] un-brick for n00bs
Emperor.dk said:
I remember my first ROM install... d*mn it went as wrong as anything could. Somehow i managed to install a ROM for the X10 on my X10 mini pro.
It froze at the bootanimation.
PC Companion fixed it.
Since then I have bricked my phone many times, experimenting with custom kernals and home-modding, PC Companion never failed me
[TUT] un-brick for n00bs
Click to expand...
Click to collapse
I must have had beginners luck.
I do like your tutorials, always concise and the screen shots are always very helpful for noobs like myself. Thank you Emperor.dk
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....