Hey, fellas. As you may or may not be aware, I am in dire straits. Recently I had been browsing the XDA forums for the first time in a long time, and lo and behold there was a magnificence I had thought to never see in our own development forum... a Honeycomb alpha! In my haste I tried to follow every instruction to the tee and discovered that I need the stock bootloader/ROM to do this.
Well, coming from cyanogenmod7 and a first time nvFlasher, I followed the instructions from one thread to flash back to stock 3588(I think it was)? So after fiddling with the drivers for about 5-10 minutes, I start flashing and everything is going great, no errors whatsoever. Then the tablet starts to boot up and what happens? A bootloop at the TapNTap screen. So, I tried to boot into recovery thinking it might be fixable with a factory/data reset...and recovery no longer works, it just reboots back int pthe TnT bootloop. And then I came to the this forum, particularly the Q&A, to ask one question...
Is my G-Tablet well and truly forked?
Sincerely, this guy.
[edit]P.S I am also currently trying a bunch of stuff atm to see if I can fix it myself, but just reply if anything I do is futile and I should consider recycling my new hunk of silicone and plastic.
Load cwm .8 via update.zip and repartition your tab. Then try nvflash again.
"Select the advanced option at the bottom of the ClockworkMod menu, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. This erases data on your tablet. Be prepared. "
Or try loading it by nvflash with instructions from this thread
http://forum.xda-developers.com/showthread.php?t=1058649
Here is a thread on how to easily flash to the 1.2 bootloader.
http://forum.xda-developers.com/showthread.php?t=1039000&highlight=guide
Holy heck, thanks man. Do you have a paypal or something so I can send you like 5 dollars?
Nope, just mash the thanks button ;-)
Good luck!
No offense to the OP, but from my observations it seems that NVFlash is more of a breaker than anything. Everybody says to know NVFlash in case you end up with problems...that's fine, people can apparantley use ot to help fix errors that may have happened...
The fact is, most of the "I've bricked my G-Tablet" posts usually contain the line "So I NVflashed..."
I know that the developers use NVFlash for it's ease of use to go between roms, and see what it is that they need to see (I've never used it, so I don't know)
The fact is, the instructions that Mantara posted do not require NVFlash at all. In fact, after flashing 3588, they don't even require CWM.
If I ever softbrick, THEN I'll mess with NVFlash...but until then, it seems that NVFlash might actually cause me to have my first softbrick.
Nvflash is a handy tool to have and yes it can cause errors. Most of the time those errors occur because the partition table on the tablet don't match the partition table for the Rom being flashed. About half the gtabs have different partition tables from what is considered standard. That's why I have been pressing the issue of repartitioning when you first get your gtab and also when you move from 1.1 to 1.2. It helps make sure your tab and the software are on the same page.
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.
So, firstly, big thanks to the devs here. Gt ADB up and running and started the seemingly easy process f flashing ClockworkMod.
However, I'm not getting to ClockworkMod after resetting. If I try booting into recovery, it stays on the birdie splash screen with "Recvery key detected" and "Booting recovery kernel image" in the upper left.
Not finding any options for alternate recoveries or a fix for this.
I bought it used and the original owner had done some stuff to it so perhaps I was not meant to flash Clockwork from here.
Tap UI version is TnT Lite v5.0.0
Kernel version is 2.6.32.9-00001-g0e0c333-dirty
The standard ClockworkMod does not work properly with TnTLite 5.0. You need the one that was specifically compiled for that ROM.
Go here: http://forum.xda-developers.com/showthread.php?t=998663
and scroll down to the bottom of the first post for a link to the compatible version.
I thought that might be the case although I was told I could flash CLockworkmod once 5.0 was on there.
I'm normally a bit better at figuring all this out but starting in the middle of someone else's work has me at an awkward spot.
I've been searching with little luck. Any chance of pointing me in the right direction?
What about a complete factory reset? Would it be advised at this point?
I editted my previous post with a link to TwoTapsX (Experimental) which is identical to TnTLite 5.0. That should get you going but I'm not sure how much damage might be done at this point. I would try just installing the compatible version of CWM and see if that works. If not, we can look at other recovery options.
Just in case... Are you familiar with nvflash? http://forum.xda-developers.com/showthread.php?t=861950
Just started reading about nvFlash and paused to ask the questions before hacking away blindly at my new toy.
I really appreciate you pointing me in the right direction.
I enjoyed the ROM he put on here but, like the poster under me, my data suddenly got deleted and I like to try various ROMs anyway so I set to work.
I rarely leave my tablet running the same ROM for more than 12 hours ;-)
Be aware that switching away from this particular one can be a bit tricky. I find that doing a cache and data wipe before starting helps to boost the success rate. I also try to down grade to stock 1.1-3588 before loading anything else. If that fails it usually results in nvflashing back to factory stock.
Ack! Okay, in what is sure to be yet another Windows 7 issue, I'm having trouble running the .bat file for nvflash.
Are you sure it is the Bat file. Windoz7 64 need a different driver for NVFLASH.
The drivers I used appeared to work. I will try again.
Damn, I'm sorry. I swear I'm usually better at figuring all this crap out for myself. Once I'm back to stock, I can work from the beginning. This is like being dropped into the middle of a David Lynch flick with zero context.
When I run the batch command, it says that nvflash.exe is not recognized as an internal or external command. Weird.
Did you extract both archives to the same directory?
I sure did. I did take it to mean the gtab folder should remain intact within the nvflash folder instead of mixing the contents altogether in one folder. Right?
Everything else seems to be in order.
Putting any recovery zip on the sdcard produces the same results. Thankfully, everything seems to be working aside from the recovery. Maddening!
I think they need to be intermixed. Would have to check the original thread or look at the .bat and .cfg files to be sure... but if I recall properly they do.
All the files from both zips should be in the same folder, otherwise the batch file can't find nvflash and you get that error.
Good luck!
Wow. If that's what it was they need to put a dunce cap on my avi. Thanks for all the help. I shoulda had the guy put it to stock so I could start from scratch.
I'll try that when I get home.
Thanks again!
Sent from my HTC Vision using XDA Premium App
Sleef,
You are in a world of hurt -- and I say that not making any negative comment
toward the advice you already have been given.
TnT Lite 5.0.0 (which is now TwoTapsx) is a second generation ROM Roebeet did
based on the UAT 3991 update posted by VS in a kind of test mode.
The second generation ROM is not compatible in many respects with the original ROMS
up to 3588 -- some of the internals that normally are changed in an update have been modified.
So, as you have been properly warned by others, you cannot run stock CWM. You
also have to be careful downgrading to stock before moving to stock or another ROM.
To get out of 5.0.0 you need to:
1. Read Roebeet's TwoTapsX thread so you know what you are working with:
http://forum.xda-developers.com/showthread.php?t=998663
2. You need to NVFlash back down to stock. Normally we'd tell you to follow
the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Since you already have been working with this, I'd step-by-step make
sure of your setup and that it is right.
My best suggestion would be for you to set up and follow the NVFlash thread above
exactly and see if you can get a good flash. If you do, it will take you down to what
we call bekit 1105, which is stock version 2638. If you get there and boot successfully,
then when you turn on wifi it will soon update you to OTA 3588. Then
you can carefully pretty much do what you want.
If you don't get a successful flash (because the tab has had so many different,
difficult to handle things on it), then all of us will have to help you find a successful
path.
Good luck,
Rev
P. S. -- What the other guys have been telling you is good -- I've just tried to
put it in perspective so you'd understand where you're at and be organized in
your approach.
Quick clarification... I think Rev meant to say "Is NOW TwoTapsX" rather than not which is why that thread is referenced later. The name change was necessary to differentiate the two development paths.
Thanks for popping in Rev. I've been meaning to pop in but I've been... practicing my recovery methods... don't ask...
Yep.
Fumblefingers strikes again. Thanks.
Rev
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
Anybody could post an update.zip stock rom, please?
I got my gtab stuck on apx (like tccrews had it) and I need an stock rom update.zip to apply a fix that I found posted here.
Thanks in advance.
Here you go, there's a link to 3588 in this post:
EDIT: Correct me if I'm wrong but if it's stuck in APX mode wouldn't you have to use NVFLASH to get it back to stock? If so then just follow the directions in the post listed below to NVFLASH your G-Tablet back to stock.
http://forum.xda-developers.com/showthread.php?t=861950.
More specifically here is the exact link to the download:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip.
Just make sure and rename it.
Just because you could have found what you were looking for faster with less threads. Did you try and search for "3389" or "3588" on xda. I do usually every other day to provide the link you were looking for so I know it exists.
Naysses,
I will try to help you, but you are going to have to do a couple of things:
1. Do not post for help in any other threads any more. I think everyone knows you
were upset and desparate -- but it still is bad netiquette and only upsets people and
makes them angry.
2. I have several things for you to do that we have used in the past. It may take us
a day or two of back and forth. But you've got to do them exactly as requested. From
what I have read your PC and tablet must be a mess of software, so I'm going to
start from scratch.
Here's what you need to do:
1. First we've go to make sure you are set up right and have the right software available
and are doing that right. Following is the thread on NVFlashing back to bekit 1105, which
is stock Version 2638. I want you to erase all the NVFlash setup on your PC and then go
in and do this procedure from end to end exactly as it requests. It's
been done a zillion times and will work if your tab is not to messed up to flash right -- and
that's a possibility we will deal with when we get there:
http://forum.xda-developers.com/showthread.php?t=861950
Double check everything as you go and note any exceptions that might happen.
If this does not give us a workable setup, then we will look at NVFlashing CWM to
repartition and clean up your internal drive -- but don't even worry about that until
we see if a repeated, good flash will work.
Good Luck,
Rev
P. S. -- I know I'm being demanding and hard on you, but lots of people I help don't
do what is requested and waste my time and theirs. If your problem is like I think it
is we need to get it right! I'll check this thread early tomorrow to see how you
are doing.
Ur a good man Rev
I got stuck in APX mode before when using the (newer?) 152KB nvflash.exe when trying to reflash the stock image. With the 140KB nvflash.exe I re-ran the nvflash_gtablet.bat and it worked successfully. You do need the 152kb version to pull and back up the BCT, but I use the 140kb one when using the batch file to restore stock (with stock recovery)and haven't had issues getting stuck in APX since that switch.
ramerco,
Thanks for the warning and update.
However, if he will just stick with what I give him I know that works.
A bunch of people have been messed up trying to install the SDK and
ADB and all on top of the original Procedure roebeet wrote. Drivers
get messed up. Makes it tough in times like this.
Rev
Hey, Folks
Let me say that you guys are the best. I have tried to follow most of the things you have done with gtablet, and they are amazing. That said, I have tried every thread I could find and have not found a solution to my problem. I completely bricked my gtab. All I can get now is the bird screen with "booting recovery kernel image". It won't go any farther. I've tried NVFlash, clockworkmod, droidpirate and whatever else I could find. The tablet won't recognize my micro sd card. So do I put the tab on my fishing line and go back to the store for another one? Thanks for you help. Sorry If I'm rehashing an old thread, but I've really tried all I know to do.
Have you tried my website? I'd say you're a code red.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
A Code Red sounds like a good idea, especially since it asks you to use the one that replaces the standard recovery partition in the image with a CWM partition.
The only other thing that comes to mind would be the possibility of a recovery folder (with command) on the root of the internal memory that is telling the tablet it needs to run update.zip... and then something being wrong with an update.zip that's there.
Also, go ahead and take your microSD out if there's some concern about it not recognizing it (just in case the command and update.zip are on that).
Thanks, Ted
But, I'm reasonably sure the problem is with the recovery file on the gtab. I probably erased it when I was trying to install the Honeycomb update. I've tried nvflash. It worked once before and did re-partiton the tablet, but now it won't do the same thing.
Thanks, Gentlemen
I'm going to try goodintentions step by step directions again. Sometimes these things are all just a matter of how you hold your mouth. Maybe after a few dozen times I'll get it right. Thanks to you folks, I really loved my gtab. I had it mod'ed to gingerbread and it was great! I just couldn't leave well enough alone and had to try honeycomb. I promise if I ever get it back to where it was, I won't mess with it again. (Sure I won't)
The thing with honeycomb that I have discovered is that if you don't wipe the data RIGHT AFTER nvflash you will not be able to boot up the new rom you just nvflashed. Nvflash doesn't wipe data. And there's something in the honeycomb data that interrupts the normal boot process of other roms.
So, in the code red procedure, the most important part is wiping the data/factory reset RIGHT AFTER nvflash.
For some reason, people keep ignoring this step even though it's written right there. Like I said at the top of that page, do not skip any step.
goodintentions said:
The thing with honeycomb that I have discovered is that if you don't wipe the data RIGHT AFTER nvflash you will not be able to boot up the new rom you just nvflashed. Nvflash doesn't wipe data. And there's something in the honeycomb data that interrupts the normal boot process of other roms.
So, in the code red procedure, the most important part is wiping the data/factory reset RIGHT AFTER nvflash.
For some reason, people keep ignoring this step even though it's written right there. Like I said at the top of that page, do not skip any step.
Click to expand...
Click to collapse
Good Intentions
You are the GRREAATISt! I followed your instructions, and they worked like a charm! I had already done something similar before to no avail, but I erased everything and followed your guide to the letter. I couldn't figure out how to get back to this message forum, or I would have thanked you sooner. How do I contribute to your beer fund?