removed for lack of interest in subject matter
also found result of similar work; removed overlap
found flashable zip using different technique to cause full restore but it didn't flash stock recovery; unable to find creator of zip but felt it was not in any ones best interest to leave my files and info posted and may offend the creator of the zip even though my technique is completely my own work!
good luck
OK, I've missed some part of this. I used the 1.1 file on an SD card and I'm guessing without some sort of image for factory software it's not going to work. I get a menu to completely reformat and restore to factory or skip the steps. I choose to restore, it went through some operations, then booted up through Cyanoboot and into my CM7 rom.
From what I have seen it looks like the problem is that I don't have a stock recovery on the device, so it's probably just re-writing the CWM or Cyanoboot.
Any ideas?
zeropants said:
OK, I've missed some part of this. I used the 1.1 file on an SD card and I'm guessing without some sort of image for factory software it's not going to work. I get a menu to completely reformat and restore to factory or skip the steps. I choose to restore, it went through some operations, then booted up through Cyanoboot and into my CM7 rom.
From what I have seen it looks like the problem is that I don't have a stock recovery on the device, so it's probably just re-writing the CWM or Cyanoboot.
Any ideas?
Click to expand...
Click to collapse
I am working on a new version that prints errors to the screen. The first thing this does in flash stock recovery to the proper partition, then flashes the described file and unmounts everything. In other words it flashes stock recovery, obviously that failed so it couldn't mount the recovery partition.
I have yet to find a proper method of displaying errors such as this. (sorry I should have said that cwm is flashed to the recovery partition so only stock or cwm can exist in that partition at a time). You may need to look at your partitions for errors.
I'll post a new version as soon as possible. I was working on that problem(error reporting) when I received your reply.
Note: it will not fix partition problems(only what is written to the partitions), only flash stock recovery and use that to rewrite everything from there and your rom. It does not write rom either as that contains your serial number, mac address, etc.
Good Luck!
zeropants said:
OK, I've missed some part of this. I used the 1.1 file on an SD card and I'm guessing without some sort of image for factory software it's not going to work. I get a menu to completely reformat and restore to factory or skip the steps. I choose to restore, it went through some operations, then booted up through Cyanoboot and into my CM7 rom.
From what I have seen it looks like the problem is that I don't have a stock recovery on the device, so it's probably just re-writing the CWM or Cyanoboot.
Any ideas?
Click to expand...
Click to collapse
I was running cm9 with cwm internal. Downloaded file with Nook, reboot recovery, flashed zip, reboot. Full factory restore! Back to B&N video screen and everything clear and clean. I did this after my previous post to ensure everything is ok. In looking I see many posts in the last three or four days about cm7 and partition problems. celticwebsolutions has a thread about it.
Give the link a try! celticwebsolutions is the op for cm7 and seems to be a very nice guy!
http://forum.xda-developers.com/showthread.php?t=1513583
Good Luck!
zeropants said:
OK, I've missed some part of this. I used the 1.1 file on an SD card and I'm guessing without some sort of image for factory software it's not going to work. I get a menu to completely reformat and restore to factory or skip the steps. I choose to restore, it went through some operations, then booted up through Cyanoboot and into my CM7 rom.
From what I have seen it looks like the problem is that I don't have a stock recovery on the device, so it's probably just re-writing the CWM or Cyanoboot.
Any ideas?
Click to expand...
Click to collapse
corrected incorrect link in previous post!
Related
So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.
FLASHABLE ZIP, (1)RESTORING NC TO STOCK/FACTORY OR (2)CWR REMOVAL ONLY
What you will find here: files to restore to stock (v. 1.0.0 or 1.0.1) and files to remove CWR and thus restore stock recovery (8 failed boots and factory reset [power+n]).
______________CAVEAT________________
Keep in mind that the Nook is really hard to brick. By that, I mean almost impossible. The reason is simple: it has a boot priority on uSD, which means you can always boot your NC from the uSD with, for example, Nookie Froyo (see thread in Dev section). From there you can install Clockwork recovery and other applications (ibid) and repair almost anything. So please, don't panic.
If you ask for help, explain yourself exhaustively on what you have done to require attention. Thank you.
All the usual warnings apply. I cannot guarantee that the following won't have side effects, although I'm pretty sure it won't. Please read complete thread before attempting anything.
Do not attempt flashing files unless you really need to or absolutely know what you are doing.
____________________________
______________UPDATE-01/23/2011_______________
There is another method to restore to stock. If you know your way around ADB, please read this thread: click here, as it will guarantee a clean restoring of your partition. The below files only copy files, but cannot "recreate" your partitions. Both methods can work, but the one linked above (shad0wf0x's thread) will work without exception. Only requirement is that you can use ADB. Thank you.
_______________________________________________
I know a few people out there are struggling after having messed up their Nook's partitions (boot, system, etc.). Hope this will help.
Requirements:
- Rom manager / Clockwork Recovery. This can be easily installed through Nookie Froyo booted from uSD, or through rooted NC. See Clockwork Recovery thread for more information.- A uSD with enough free space (at least 175 MB). Make sure uSD is mounted (see mounts option in Clockwork Recovery). If it doesn't read your uSD, format from an Android device (Memory settings, unmount-> format).
Files to restore NC to stock (1):
If AND ONLY if you choose to restore completely your NC, /data and /system partitions must be formatted before flashing. See mounts and storage option in CWR.
LINKS ARE DOWN: please refer to the following post: http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148
BEWARE: These files will reset you Nook Color to stock and remove Clockwork Recovery, by replacing /boot, /system, and /media with stock
If you choose to flash one of the two files above, formating /data and /system is required BEFORE flashing the file (see mounts and storage in CWR) ! After flashing, resets (8 failed and power+n) shouldn't be necessary, everything should work straight "out of the box" after flashing the file.
Or,
File to remove CWR and restore stock recovery (2):
If you simply wish to remove CW Recovery, use this file, which restores /boot only:
EDIT: files are not available anymore. Sorry for the inconvenience.
Size: 6.1MB, md5sum: 6d00a461a221e69195440355f6706104
Note that this last file will affect your rooting of the NC.
If you should choose to keep your NC rooted, try this:
EDIT: files are not available anymore. Sorry for the inconvenience.
Keep in mind this last file has not been tested on my NC. It's necessarily less dangerous than the other files (which already aren't very dangerous). But still, please give me some feedback on whether it works or not. Cheers.
5. As a last attempt to fixing your NC, if your nook never gets passed the "Touch the future screen" or simply doesn't boot, try this file:
EDIT: files are not available anymore. Sorry for the inconvenience.
________________________________
Comments are welcome.
Sam
Very handy - Thanks for your effort
dude this is just what i needed after my little nook color break down. Thanks!!! a ton!!! also its 11:56 eastern and the downloads are available yet...
Jamdat33 said:
dude this is just what i needed after my little nook color break down. Thanks!!! a ton!!! also its 11:56 eastern and the downloads are available yet...
Click to expand...
Click to collapse
File is now available.
quick question, if we removed cwrecovery then will the 8 boot reset work again?
Yes, it will. That's the point.
beautiful! Thats just what i wanted, thanks alot man
Thank you. I was worried that I wouldn't be able to check out the B & N 2.2 update coming out soon. It worked great. After flashing I had to factory reset the data (three finger salute) and everything worked out great. Now I'm in the process of installing the 1.0.1 update and then will probably go back to where I was before (autonooter with clockwork recovery). I have a nandroid backup and titanium backup of everything so won't take long. Thanks again. Great job!
Tried out method 2. Looks like i have a corrupted recovery now It wont go past the "Touch the future of reading" and when i do the 2 button salute it brings me to a screen that says the install failed
EDIT: Nvm. just magically worked again.
Edit 2: I used the 2nd method and it wasn't smooth sailing. I'm gonna relate what happened and what I did so that samuelhaff can help others if they have the same problem:
I originally auto-nookered the device and then installed CWR. I foolishly tried to do the 8 hard resets and was met with the recovery screen. I also foolishly wiped the data and cache hoping that would do the trick and alas it just left me with a "touch the android" homescreen that didn't work.
At this point I used the second method after I tried froyo and when I reset the nook the nook it would get stuck at the the "Touch the future of reading." So to fix it i tried to get into recovery by holding the N button and the power button and it showed me a screen that said the install failed and then the nook started booting normally again. Not smooth sailing but it worked so thanks a lot!
you're awesome. Wish I had this last week. haha
tytdfn said:
Tried out method 2. Looks like i have a corrupted recovery now It wont go past the "Touch the future of reading" and when i do the 2 button salute it brings me to a screen that says the install failed
EDIT: Nvm. just magically worked again.
Edit 2: I used the 2nd method and it wasn't smooth sailing. I'm gonna relate what happened and what I did so that samuelhaff can help others if they have the same problem:
I originally auto-nookered the device and then installed CWR. I foolishly tried to do the 8 hard resets and was met with the recovery screen. I also foolishly wiped the data and cache hoping that would do the trick and alas it just left me with a "touch the android" homescreen that didn't work.
At this point I used the second method after I tried froyo and when I reset the nook the nook it would get stuck at the the "Touch the future of reading." So to fix it i tried to get into recovery by holding the N button and the power button and it showed me a screen that said the install failed and then the nook started booting normally again. Not smooth sailing but it worked so thanks a lot!
Click to expand...
Click to collapse
Thank you for your contribution.
I don't understand why your NC wouldn't boot pass the splash. Will have to see if that happens again.
But on the other hand, I have noticed that the first boot after restoring may show up an "install failed" notice. Which, again I don't understand just yet. But everything should work if you boot a second time.
Anyway, I'll look into it. In the mean time, both files should help quite a few hot-headed nookers, like myself.
If I new you better, I would fall in love with you. Maybe we should take this slowly.
Is it possible to make a 1.0.1 version
This is a huge step forward. Thanks for posting this. It makes experimentation much more possible.
I'm so happy. I think I'm going to be able to stop crying now.
Good job, sir...
If i can stop screwing up all of my technical endevours, i'm going to start trying to make a rom kitchen, now that there is a streamlined way back...
Nevermind, I can't seem to do anything correctly this weekend...
Sent from my LogicPD Zoom2 using XDA App
straby187 said:
Is it possible to make a 1.0.1 version
Click to expand...
Click to collapse
Most certainly.
Sent from my HTC Desire using XDA App
Ok... I have absolutely no clue what happened... All went well... Flash went through without a hickup... Booted up fine... And then... No wi-fi... I absolutely can not enable wifi now...
ourprisonplanet said:
Ok... I have absolutely no clue what happened... All went well... Flash went through without a hickup... Booted up fine... And then... No wi-fi... I absolutely can not enable wifi now...
Click to expand...
Click to collapse
Ok. Which method did you use? (1) or (2)? Before flashing, were you using v. 1.0.0 ou 1.0.1? Try updating to 1.0.1. See if Wifi is working. If not, try method (1) (again?). Do both resets (8 failed and power+n).
samuelhalff said:
Ok. Which method did you use? (1) or (2)? Before flashing, were you using v. 1.0.0 ou 1.0.1? Try updating to 1.0.1.
Try method (1) (again?). Do both resets (8 failed and power+n).
Click to expand...
Click to collapse
OH THANK GOD :-D I did the power+n and it brought it back... Thank you SOOOO much for such a quick response... I have no clue what the heck caused that... that was weird...
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
I would get nvflash set up with bekit's images and flash that to get yourself back to a working stock image. Follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=861950
After that, put Clockworkmod ( v .8, get it from development forum) on it and repartition your sdcard to 2048 and 0 then you should be ready to flash.
Then get a ROM from the development forum here, there are some based off cm7 (gingerbread builds).
I was hoping not to have to use NVflash cuz people report problems with the boot loop, however I havent found any other option so far so I guess i'm trying that. Thanks for the link.
Xxlgeek,
Every time I hear boot loop I think re-partition -- because most of the time that
seems to fix the problem.
I agree you should NVFlash to get a stock version working. Then install CWM so
you can partition -- and the do the Fix Permissions, Wipe Dalvik Cache, Wipe
Cache, Wipe Factory Data.
With that I would try to wind up with a stock machine and let it OTA up to 3588.
I wouldn't load another Alternate Rom until I knew my tablet is working good and
until I know a lot more about the roms and how to work with the G-Tablet.
IMHO.
Rev
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Xxlgeek,
If it didn't work, I would erase the Cyanogenmod 7 file -- and I would go back to a stock rom until I could make sure all the hardware is working right and the system
is stable.
When you know the tablet is good and stable, you can always download and re-do.
Rev
Xxlgeek said:
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1021978
you are not alone...
it may have to do with the boot loader .... further investigation needed. CW does not replace this but the stock does I have been running the old one since december on my personal tab. but most of these woot pads are updated .... hmmmmmm
Xxlgeek said:
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Click to expand...
Click to collapse
Which version of CM7 are you running?
jivy26 said:
Which version of CM7 are you running?
Click to expand...
Click to collapse
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Just throwing this out there. I bought 2 from Woot myself. On my first G-Tab I had the same issue with every single ROM I tried. I finally used NVFlash to go back to stock and everything was good again. I then flashed to the G-Harmony Gingerbread ROM and it worked and still runs like a CHAMP. Now, I finally get the other G-Tab out and start to go through the same routine as the first and it's been a no go repeatedly. I have mostly been trying with the Cyanogen 7 Final ROM to no avail and even with the G-Harmony. Going to try NVFlash on number 2 tab and see what the result is and will post back in a bit with updates.
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
tunez23 said:
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
Click to expand...
Click to collapse
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Did you extract both archives to the same directory on your computer?
akodoreign said:
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Click to expand...
Click to collapse
2 partitions are reversed and Gingerbread roms don't like it. Using bekits original nvflash files will fix the partitioning permanently as far as flashing between froyo and gingerbread.
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Edit.....This is not all tablets. I'm guessing around 30% or so have the 2 reversed partitions but it seems 50% of the woot tabs. Helped fix many of these on irc in the last 2 weeks
KrazyOne7 said:
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Click to expand...
Click to collapse
Having the same problem too!! Any help would be much appreciated.
Tried wiping everything with FORMAT.zip from another thread, and get and error for unknown device when running that *.bat file.
This newbie needs some serious help!
Locked bootloader??!
thebadfrog said:
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Click to expand...
Click to collapse
I think I must have the locked bootloader, but tried both Gojimis's fix and nvflash fix and get the error as mentioned above.
So I am getting nowhere, won't go past the "booting..." splash screen to install any of the update.zip files from the microSD card.
Help!
K J Rad said:
Did you extract both archives to the same directory on your computer?
Click to expand...
Click to collapse
Yes, I extracted both the gtablet and the windows zip files.
KrazyOne7 said:
Yes, I extracted both the gtablet and the windows zip files.
Click to expand...
Click to collapse
Me too, and still getting the error "nvflash configuration file error: file not found Press enter to continue:"
Are they in the same directory. If they are not then nvflash can not find the files to flash. Both zips have to be unzipped in the same directory and the driver has to work. You must be able to see the tablet from the computer when you boot into apx mode. APX mode is power/vol- NOT power/vol+
I tried to install a custom boot animation and wound up having to use CWM recovery to get out of weird looping behavior. I'm not sure exactly what the restore function wipes (for instance, my Vegan ROM was still installed).
Since that episode I've been seeing more Forced Closures than before. I wonder if I need to repartition again. What values should I see if am or am not partitioned 2048/0 and where would I look for those? Thanks.
Surely someone can tell me what to look for as an indicator.
I promise to stop calling you "Shirley."
Rick,
I don't think it's personal -- there just is not a place you can look and see your
partitioning.
If you were boot looping, used CWM to stop it, repartitioned 2048/0 and are running
smoothly now I wouldn't worry about it.
Rev
EDIT: On further thought, I think if I were having glitches (like the FCs), I would
reflash back to stock, install CWM and clean up and reset as needed, and make
darn sure everything was working and exactly right -- and then go my way from
there. But that's just the way I work.
Thanks, Rev.
Thing is, I did not repartition (or, rather, re-repartition) after recovery. Have I necessarily reverted, due to CWM recovery, to the unreliable stock partition (bearing in mind that the device wasn't totally wiped; the Vegan ROM was still in place)?
EDIT: I understand that reflashing to stock and starting over will address any issue. I'm just trying to learn.
Rick,
If you boot into recovery using power/volume + and you get CWM you are still in
ClockWorkMod and have not reverted to stock recovery.
I understand you are trying to learn. I just don't like "flaky" anything so I "make sure"!
Rev
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
tabbott01 said:
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
Click to expand...
Click to collapse
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
phone_noobie said:
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
Click to expand...
Click to collapse
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
mattb3 said:
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
Click to expand...
Click to collapse
yes it is good because i can see all the videos, pics i have saved in it. Also i put the new ROM on my internal sd card and its there so sd card is def good. What could be causing the problem?
To the op, I would use Odin, no real worries there.
To the other guy with sdcard issue, try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
mattb3 said:
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
Click to expand...
Click to collapse
Thanks...that's exactly what I did, except the backup would never quite "take." It completely loaded and cycled through the boot process, but I ended up on a boot-restore loop. So now I've Odin-ed back to stock with the closest build I could find to my stock (which I don't think is out there yet - FROYO.UVJL6.ULTIMOBILE - do you know anywhere to find it?), rooted, and am searching for a good, stable, battery-friendly mod once again.
s15274n said:
try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
Click to expand...
Click to collapse
i did try formatting, then moving all the stuff back and am still getting that same error message
^ what rom are you on, if one?
You could always ODIN, and use my option b cwr in the noob guide. I just tested making a backup using trigger 8/22 and know there are no issues. Not really sure whats up on your end. I will say though, I've emailed koush several times that there is an issue with cwr on the vibrant from rom manager, for some it won't even flash.
phone_noobie said:
i did try formatting, then moving all the stuff back and am still getting that same error message
Click to expand...
Click to collapse
try different sd card..or reinstall CWM...