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...
Related
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.
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+
So I am just about at my wits end. I am fairly computer literate but an absolute noob when it comes to my gtab and flashing it.
I’ll try and give a step by step.
1. Got my Gtab today. I was sooooo excited!
2. Installed CWM and the latest TNT lite ROM.
3. All is well everything worked great.
4. Started up Android market…all hell starts breaking loose with “forced closes”.
5. Ok…so I shut down and restart
6. It starts what I have learned is called a “boot loop” going from the birds to the “G Tablet” screen to black to the birds…
7. I try to reflash TNT…nothin’.
8. I try NVflash, it *says* it completed successfully, but stays in the boot loop.
9. I’ve tried copying the CWM onto the microsd card (yes, command is pointing to the micro card). I then go through the Hold down the plus and start.
10. CWM *seems* to install, then HEY…right back into the boot loop.
11. I try something else and get (in little red text in the top left corner of the screen) something about “Magic” something missing.
Does anybody have any suggestions? I am a smart guy…I can read. The thing is, is that it seems like the mods and the CWM’s are completing successfully, but then I am right back in the flippin’ boot loop. I am afraid I’ve just wasted $300.
Sorry to be the dumb noob.
Pat
Did you change the partition when you installed the new rom? That was what fixed mine.
No...none of the instructions I saw mentioned that. Now I am seeing using CWM to do it but the problem is I can't get CWM to load!
if CWM is installed, you just need to hold V+ and power button when restarting. if not (and this happened to me) you should follow the instructions that were given to me by regalpimpin on this thread http://forum.xda-developers.com/showthread.php?t=1025128 to install CWM, and re partition (you will loose all the data on your internal SD card so be sure to back up) but repartition at 2048 and 0 unless the ROM specifically asks for a different partition.
You need to nvflash if you are getting the magic value mismatch. You could have gotten out of the boot loop originally by repartitioning. Only use bekit 0.8 recovery as any others will bork your tab. Dont use rom manager either.
mocheesehead,
First don't panic. We can fix this. It's REALLY hard to brick
a G-Tablet!
You have done all the right things from what you have written.
As Lisa said the one thing you haven't done is re-partition and
it seems that re-partitioning fixes boot loops most of the time.
Double check. Use your microSD with the CWM update.zip on it.
Since the command file is erased when you use it, you will need
to copy a new copy of the command file edited for /SDCARD2 back
into the recovery folder. Boot into recovery with power/volume +.
When all is finished shut down properly. The reboot as above and
see if you get CWM.
If you don't, you will have to try to load CWM by nvflash. If you
will try the above again, I will see if I can find directions for CWM
by nvflash. I know the process but will have to find the correct
command line.
*************
Just in case CWM loads: I will go ahead put the fix process here:
1. When CWM starts, go to the Advanced Menu and run the
Partition SDCARD, Fix Permissions, and Wipe Dalvik Cache options.
The re-partition takes a few minutes so
don't panic! Then go back to the Main Menu and Wipe Cache
and Wipe/Reset Factory Settings.
2. Once that is done, reboot and hopefully you will be fixed.
3. If not fixed, nvflash back to stock as per the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Makes everything -- especially the files to load -- is correct.
Keep us posted on how you do. Meanwhile I will look for the
other procedure and post it.
Rev
Hi Lisa! Yes! That sounds like my problem. I'll give it a go.
Quick question...is there a preferred format (ie, FAT32, etc) for the micro SD card?
I'll let you know how it turns out!
Thanks...Pat
Pat,
Read this thread. This person had about the same kind of situation
you do and had to nvflash to load CWM.
http://forum.xda-developers.com/showthread.php?t=1026757
Rev
butchconner said:
Pat,
Read this thread. This person had about the same kind of situation
you do and had to nvflash to load CWM.
http://forum.xda-developers.com/showthread.php?t=1026757
Rev
Click to expand...
Click to collapse
Hey cheesehead! Absolutely follow Rev's advise! I was the Guy in the thread he references above. The fix worked like a champ.
You will get it fixed, just as I did. Same issue.
Mark
Thanks to everyone for the kind and informative responses. I probably won't get to a fix til Monday morning I as I have a soccer tourney (kids) all weekend, but I'll report back when I know something!
Thanks again,
Pat
As everybody said, it is almost brick proof, as long as you follow the correct procedures. Some people don't seem to understand missing one step can make things worse. Most of these post give you step by step instructions and by finding the right one to read you can't go wrong. I'm sure you will eventually have it worked out, learning what does what and why you did that will be a big help in the long run.
Ok! So I think I am breathing again! I partitioned the card and got back to the stock UI...man...it does really blow! So, a couple of questions...
1. I flashed TNT lite, and had force close issues. Would you recommend Vegan?
2. Now that I partitioned the card 2048 and 0 like everyone said, do I need to do this again before or after I flash a new rom?
Again, thanks for everyone's kind responses!
Pat
Glad to hear you made back to stock. Here in a bit I will write a step by step how to upgrade to TNTL 4.40 for you if some one doesn't beat me to it.
Thanks JH! I look forward to giving it another go! I appreciate your help!
Pat
Pat,
Remember that the bekit 1105 is about the oldest stock UI that exists!!! Most of us
started with 2967 on our first G-Tablets.
It WAS bad and there was no Flash and no replacement kernal and TnT was at about 2.x and VEGAn was at about .beta 3.
On the other hand, we didn't miss a lot of it because we were trying to keep them
running and find out what they would do and find apps we liked!!!
When I run the latest software I just can't believe how lucky we are.....IMHO.
Rev
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
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!