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.
I had Vegan Ginger Edition running and it was working great. I decided to Factory Reset the tablet. I used Settings|Privacy|Factory Reset.
But it went into endless reboots, I think. What it was doing is that the screen that says Vegan Tab Ginger Edition comes and it does the animation (shocking and flashing), and it does this like 3 times and then the screen goes blank for a second or so and then the animation starts again, and so on, and it keeps on repeating forever and then it would turn off automatically.
I booted into recovery Clockwork Recovery, and tried to do wipe data/factory reset, wipe cache partition, etc, but nothing helped.
I eventually ended up in doing Wipe Dalvik Cache. Now it does not even get to that Vegan Tab animation. It now gets stuck at "Powered by G-TABDEVS" screen.
Any suggestions? Do I need to re-install? If so I guess I will have to copy the zip to SDCARD and then install it, since I can't boot at all. Is there any other option?
Ya, just reflash vegan ginger.
I reflashed it. It now moves on and does not stop at G-TABDEVS screen, but it is exhibiting the same problem. Repeated VEGAN-TAB GingerEdition screens.
What do I do?
I just flashed CyanogenMod, and even that exhibits the same issue. I even went in and did mounts and storage>format system as well as format data. And then flashed it. But still the same.
More bad news. I nvflashed bekit's original image. It now is showing the original big eliptical g-tablet logo as it boots up, but it continues to cycle between the birds and the gtablet logo.
CWM is also gone. When I try to go into recovery all it displays is the big triangle with exclamation sign for a second or so and then restarts the tablet going back into the endless cycle.
I am now totally stuck. Please help.
have you ever repartitioned your device using Clockworkmod Recovery?
I've seen the tablet just bootloop on the bootanimiation if you have never repartitioned. Mine did it and so did a friends of mine. Tablet working great for weeks, installed different ROMs then one day a reboot and it just loops the bootanimation. Repartitioned in CWM (2048/0) and the problem never returned.
Of course you need to get CWM back on. Read the threads on NVFlash and you should be able to just nvflash the clockwork image to the device to boot in to CWM. Repartition and reinstall your ROM.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
tcrews said:
have you ever repartitioned your device using Clockworkmod Recovery?
I've seen the tablet just bootloop on the bootanimiation if you have never repartitioned. Mine did it and so did a friends of mine. Tablet working great for weeks, installed different ROMs then one day a reboot and it just loops the bootanimation. Repartitioned in CWM (2048/0) and the problem never returned.
Of course you need to get CWM back on. Read the threads on NVFlash and you should be able to just nvflash the clockwork image to the device to boot in to CWM. Repartition and reinstall your ROM.
Click to expand...
Click to collapse
Thank you so much. I got out of this mess. I clearly remember repartitioning 2048/0, but looks like Android Factory Reset corrupted it or something.
For the record, this post helped:
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
shah123 said:
Thank you so much. I got out of this mess. I clearly remember repartitioning 2048/0, but looks like Android Factory Reset corrupted it or something.
For the record, this post helped:
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
Click to expand...
Click to collapse
Hahaaha, and for the record, my start here page code double red takes care of your problem. Not only that, I've also provided nvflash files with cwm pre-installed.
I swear, it's like people don't read the directions properly anymore.
goodintentions said:
Hahaaha, and for the record, my start here page code double red takes care of your problem. Not only that, I've also provided nvflash files with cwm pre-installed.
I swear, it's like people don't read the directions properly anymore.
Click to expand...
Click to collapse
Hey goodintentions, I know you have good intentions , but I have been working with gtablet mods for quite some time now. Usually when you have a bricked gtablet, you are desperately looking for a solution. That's why I hopped from Vegan to Cyanogen to stock etc within an hour or so. And when you have been working on things for some time, you tend to not look at anything that says "start here". Honestly I had never seen your page before, which by the way is pretty good and would have been a life saver if I had known it.
I wonder... what should I name the page as?
I promise you, my instructions work for 99% of the problems people encounter.
goodintentions said:
I promise you, my instructions work for 99% of the problems people encounter.
Click to expand...
Click to collapse
I have no doubt.
Hi all,
I had rooted my nook tablet using snowball mod about a week ago and I loaded CWM on to the emmc using indirect's one-click recovery flash app. It was all working fine.
I wanted to return to stock and so put the 1.4.0 zip on my sdcard and rebooted. But it went straight to CWM. So I remembered i had to restore the stock recovery and rebooted and flashed stock recovery. only this time, I used the updated version of the one-click app (the updated version of 26th Jan) and hit reboot to recovery. This caused my NT to be in a boot loop ever since.
I have tried the 8 failed reboot method to initiate a factory reset but it didn't work. I also tried using the Nook Recovery Fix but i can't get to install the drivers since if I connect the NT to my computer, it keeps rebooting over and over again and I can't get to show for longer than 2 secs in device manager to install the drivers for Windows. (I was using it on Ubuntu till now).
My NT just turns on, the black screen n logo shows (The "With adobe reader" screen) however it doesn't go any farther than that. It just shuts down. The white nook screen does not even show. It's like it's going through multiple failed reboots without me holding down any buttons. Any help from you guys is greatly appreciated. Thanks.
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Data Injures said:
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Click to expand...
Click to collapse
Thanks a lot for your suggestion! I just spent a half hour on the phone with B&N customer service and they agreed to ship out a replacement device. The rep said it was a hardware failure that was causing it to act like that. I was a bit surprised at that. I'm not sure she knew what she was talking about. Anyway I had bought mine off craigslist. And now I'm getting a new device so I guess I can't complain. But I'll try later tonight to restore this one using the bootable CWM you linked to. Thanks again.
Follow Up
Just thought of posting a follow up. The bootable CWM method worked. I was able to fix the recovery. Most certainly not a HW problem like the tech claimed. It's working fine now.
I'm glad to hear that! Now if I have the same problem in the feature I can just follow my own advice. Lol
Sent from my DROIDX using XDA App
So I have basically the same problem. My girlfreinds nook was rooted but the OTA update stopped the root from being effective. I tried the sd card revert to 1.4.0 and I hade the problem with the "n" butting not working. When i tried the 8x reset the nook went into an endless boot loop where I see the back screen and the next white screen flashes for like 2 seconds and then reboots. I tried to make the CWM SD card but it still just reboots. My question is that since i never had the CWM mod installed am I pretty much hosed or am I doing something wrong?
What are you using to make the CWM SD card? I strongly recommend using GParted either from a Linux live image or there is a GParted live image you could use. When it works correctly, the bootable SD card that should stop the boot loop.
But why did the boot loop problem occur in the first place ?
sailerph said:
But why did the boot loop problem occur in the first place ?
Click to expand...
Click to collapse
From what I know of, if you install stock recovery and hit the reboot to recovery button, it initiates the stock recovery which then causes the error. Though I don't know the reason behind nor what's causing the problem, just relaying what I have read around the forums.
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Denmmurray said:
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Click to expand...
Click to collapse
Hm I actually unrooted my nook a couple of times to play with it. I reinstalled the stock recovery from the app on multiple occasions, but instead of clicking reboot to recovery, I ran the one click unroot and never ran into any trouble.
This is what happens when you have too much info with waaaay too little experience.
Bought an unlocked Vibrant from Amazon a year ago after the original tmobile one got stolen. It had issues like freezing up, tons of apps running all of time, etc. I finally tried installing froyo and it made the phone SO MUCH BETTER! Everything ran 1000% faster. I should have stopped there. But, it was pretty addictive I started reading about the new ice cream roms and somewhere, before I even got into it, I messed up the internal sd card. I have been working on this for a week, reading, downloading, flashing, etc. I feel like I have tried everything and have gone around in circles.
I can get into download mode with no problem. The furthest I have gotten after that was getting the "pass" in Odin. The phone does the boot up, then stay on the Galaxy S screen. Now, my computer won't recognize the phone (which has already happened) but now I am soooo confused and frustrated about where to go next. I have used AIO toolbox, Eugene's no brick, installing new drivers, new usb cord, etc.
Sorry so long. Thanks again.
bump...hope someone can help.
Could you give a clearer explanation/timeline of what you did? How did you mess internal sd?
Did you Odin stock jfd?
Sent from my GT-I9000 using XDA App
nolamom said:
bump...hope someone can help.
Click to expand...
Click to collapse
Is Clockworkmod recovery installed? If not, google: Samsung_Vibrant:_Full_Update_Guide and go to the Cyanogenmod wiki entry. Read through the "Installing Clockworkmod recovery" section.
In addition, from Addictivetips, to start recovery mode using the hardware buttons:
"Using hardware button combination on most Android devices:
On most Android devices including ones by HTC, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Sorry, but I'm not allowed to post links yet.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery."
Thanks so much for the help. Ascallop: I tried to run Heimdall suite 1.3.1. The first time the drivers installed but I could not get passed the "run as administrator" on the next step. I have Windows XP professional even though I am on a home computer. It is automatically checked off to do so. When I tried again later that day, my computer again only recognized the vibrant as an unknown device. I just followed your link to Cyanogenmod's wiki and downloaded the older version and the same thing happened with the unknown device. I can't get passed that. Trailblazerz11, I think when I got to clockwork mod recovery, I hit repartition (if I am explaining that right). I was able to get into download mode and use Odin to get to the bootloader loop. I can't get into recovery. I was getting the message about the internal sd error. Now, I am stuck with the unknown device issue. I have tried a couple of different versions of Odin, the AIO toolbox, different usb ports, a new samsung cord, etc. Thanks again for helping this noob.
update: Used heimdall frontloader and installed cmenard overstock. Now I am stuck at the overstock screen. I am searching through different posts to find out more. But if you have any advice or can point me in the right direction, I'd appreciate it. Thanks again.
Have you tried repartition on odin?
sent from the xda app on my android smartphone.
Do you have an external SD card installed? If so, then remove it during the entire recovery process. I had lots of trouble recovering and flashing new kernels/roms while it was installed. Probably should have mentioned this earlier... sry.
No. It was already taken out. I am having trouble still with the vibrant not being recognized. I used the zadig, it recognized the samsung, did the next step, frozen at overstock screen. Now, after unplugging cable, Vibrant pops up as unknown device. Can't do zadig again.
I'm travelling until Friday, when I get back to my home PC, I'll odin my Vibrant back to stock Eclair and will list the steps that I took some months ago to install CWM/CM7. I once was at the same point as you are now, I just can't remember the steps verbatim regarding the recovery process. One question though: have you updated your phone via Kies at any point? If so, was the last update to Froyo?
BTW, I'm currently running (quite happily) ICS Passion V12 on my T-Mobile Vibrant.
The Vibrant is a pretty hard device to truly brick. Don't worry too much, yet.
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
nolamom said:
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Let's get your phone back to Stock first. I just did this to my own Vibrant
I am officially back to stock!!! Thanks so, so much. After all of the reading and researching, you actually jumpstarted my recovery! Thanks again!!!
You're welcome
BTW, I flashed ICS V12r1 with Nelson's new kernel today. I love it. GPS works great for me, although others have reported problems. Same old deep sleep issue for them.
I wonder if flashing back to stock first is the key to fixing the prob. Don't really know though...
After the stock flash, the steps I took were:
copied kernel and rom to the internal sd card
One-click rooted the phone
odin (1.3) the Overstock kernel just to get cwm installed (instructions on the cm7 wiki)
reboot to cwm
wipe data/factory reset
wipe cache/dalvik
flash rom
reboot, let settle
reboot to cwm
flash kernel (I used: ICS_Passion_sunset_with_nova)
reboot, let settle
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
One more thing: I flashed the Gingerbread bootloader as well. After you do this the key combo for cwm is: Vol-up + power. Let go when you see the boot splash.
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
You shouldn't need an external card to root. Try One click root:
http://forum.xda-developers.com/showthread.php?t=1125414
nolamom said:
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
Click to expand...
Click to collapse
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cashmundy said:
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
Click to expand...
Click to collapse
And of course the stock recovery won't work with anything else. Different partitioning, different filesystems.
Okay. I was able to root with the one click root app. Now, I need to figure out what to do next. Ascallop, I was reading about your latest updates. I have to go through it a few times so that I can understand it all. I had froyo before and it blew away stock. I can't imagine what ICS is like Thanks again for all of the help. I HATE being back to stock.
The only reason I'm not running ICS is that I'm waiting for CyanogenMod permissions management to appear in anyone ICS rom. I'm really tempted to try Passion. ICS is markedly better than the best GB in various ways. Just remember to take a nandroid backup before upgrading, and that if something doesn't work and you need to downgrade, you will have to get the downgrade done successfully before you can nandroid-restore. Good luck!
Thanks Cashmundy. I saw the video for the root and install ice cream sandwich by Eddie West (I think that is his name.) He is a dj also. It looks like everything I would need so I may go with that.
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2