Hey, guys,
So here's the deal. My tablet was bricked, and I used nv flash method as found on g tablet for dummies. Worked great. Accessed recovery menu, and installed gtabcomb 3.3--rom was stable and awesome. I reboot, and it gets STUCK AT THE SPLASH SCREEN (three birds). Then it doesn't move. I can't access recovery at this point, either. Only APX mode.
So I did NV Flash again, but whenever I reboot, the same problem happens: Stuck at three birds, with no access to recovery anymore, thereby forcing me to reformat to stock rom.
Any guesses?! There has to be an android wizard out there!
After nvflashing and booting in to clockworkmod recovery, try formatting your sdcard (internal storage, not an external card in the slot).
Format it to 4096/0 then back to 2048/0.
I've seen many Gtablets loop at the birds (or sit at the birds) until this is done.
You'll have to then mount usb in clockworkmod recovery so you can copy the rom.zip from your PC back to the tablet to install.
Same problem ... no workie
I can nvflash CMV5504.
Immediately after nvflash I can boot into TnT.
I can then boot to CWM and install my flavor of ROM (Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8).
I can then reboot from within CWM and it boots correctly.
When I turn it off and reboot it hangs at the birds. Every time.
I tried repartitioning first at 2048/0 and then at the combo of 4096/0 followed by 2048/0. As usual, it boots correctly and then on reboot will hang at the birds.
Pretty confident that I'm on bootloader 1.2 as I've installed Illuminate (Honeycomb) + Clemsyn Combo in the past which requires 1.2
I'm stuck!!!
huckbucket said:
I can nvflash CMV5504.
Immediately after nvflash I can boot into TnT.
I can then boot to CWM and install my flavor of ROM (Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8).
I can then reboot from within CWM and it boots correctly.
When I turn it off and reboot it hangs at the birds. Every time.
I tried repartitioning first at 2048/0 and then at the combo of 4096/0 followed by 2048/0. As usual, it boots correctly and then on reboot will hang at the birds.
Pretty confident that I'm on bootloader 1.2 as I've installed Illuminate (Honeycomb) + Clemsyn Combo in the past which requires 1.2
I'm stuck!!!
Click to expand...
Click to collapse
You need to be using the NVflash program that includes CWM 3028 not the 5504. The NVflash program with CWM 5504 sets different partition tables ment for the ICS build by DRH. To other 1.2 roms I would highly suggest doing your NVflash with the program that includes CWM 3028 instead.
1. NVflash using program that includes CWM3028
2. Boot into CWM immedently after the NVflash process is done.
3. Perform the 3 wipe process, Data/Factory reset, Cache, and Dalvic.
4. In CWM go to Mounts and Mount System then Format System.
5. In CWM go to Advance and Partition SD card 4098/0 then 2048/0.
6. In CWM Fix Permissions, DO NOT SKIP.
7. Mount USB and transfer New Rom, and Gapps if needed.
8. Install and Enjoy.
If for any reason there is a boot loop. Boot back into CWM and perform the 3 Wipe process again and reboot.
huckbucket said:
I can nvflash CMV5504.
Immediately after nvflash I can boot into TnT.
I can then boot to CWM and install my flavor of ROM (Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8).
I can then reboot from within CWM and it boots correctly.
When I turn it off and reboot it hangs at the birds. Every time.
Click to expand...
Click to collapse
Based on your symptoms, I would have to say that you nvflashed one of the older versions of CWM 5504. The version of CWM 5504 from the viewsonic gtablet for dummies site is known to have the "hangs at reboot" problem you describe.
The temporary fix--to allow you to boot--is to format the MSC partition using nvflash. The permanent solution is to install the latest version of CWM 5504: beta15.
To format MSC, run these commands in a CMD.exe window--make sure that you're in the directory which contains both the nvflash program and the bootloader.bin file, then:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable part.txt[/B]
After the command completes, look through the part.txt file for the partition number for the MSC partition. Assuming it is 7 (most commonly it is), format the partition to let you boot the tablet:
Code:
C:\SOME\PATH> [B].\nvflash -r --format_partition [I]7[/I] --go[/B]
---------- Post added at 08:52 PM ---------- Previous post was at 08:47 PM ----------
nobe1976 said:
You need to be using the NVflash program that includes CWM 3028 not the 5504. The NVflash program with CWM 5504 sets different partition tables ment for the ICS build by DRH. To other 1.2 roms I would highly suggest doing your NVflash with the program that includes CWM 3028 instead.
Click to expand...
Click to collapse
No need: You can use CWM 5504 Beta 15 with any ROM, not just ICS.
Thanks guys. Technically, rajeevvp your post helped, but only when I implemented it this way;
http://forum.xda-developers.com/showpost.php?p=23467943&postcount=48
I'm up and running now. Seems pretty stable. Have rebooted 4-5 times and it comes back every time.
huckbucket said:
Thanks guys. Technically, rajeevvp your post helped, but only when I implemented it this way;
http://forum.xda-developers.com/showpost.php?p=23467943&postcount=48
Click to expand...
Click to collapse
Some clarification would help. There are a lot of steps in that link, and most of them don't have any bearing on your problem. The same goes for the steps in nobe1976's post, above.
In both sequences only the 1st full nvflash command changes the MSC partition--and so fixes your problem as a side-effect. All the other steps are basically irrelevant, and more importantly, needlessly wipes the ROM and the user data.
rajeevvp
No need: You can use CWM 5504 Beta 15 with any ROM said:
Granted yes you are correct that you can run any 1.2 ROM with 5504 as your recovery, but the only thing I recommended was to use the NVflash file with CWM 3028 only because it would allow them to install those 1.2 roms also without issues. 5504 is what you posted BETA and with my experience with that recovery is that it can cause SOD just like the ICS rom. Which the only way out is to either let your tablet's drain its power or crack the case and press the internal rest button, which I had to do twice in 5504 not the ROM. If they are testing out DRH ICS then yes you must use the 5504 version as recommended, but to my opinion any other 1.2 base ROMS they should use a more stable CWM recovery like 3028
Click to expand...
Click to collapse
nobe1976 said:
5504 is what you posted BETA and with my experience with that recovery is that it can cause SOD just like the ICS rom.
Click to expand...
Click to collapse
First things first: Recovery mode never goes to sleep, so a Sleep-of-Death (SOD) there is out.
What actually would've happened is most likely this:
Some background first: the recovery program in CWM-5.5.0.4 sets a timeout before waiting for any input. This input timeout is set to 1 hour, and if an hour elapses without any user input, recovery is coded to reboot the system. (There is a bug (actually, two) in the coding which prevents this from actually happening every time, but, that is a matter for the developers.)
So, in your case:
- You were sitting in the main menu, and the input timeout expired after 1 hour of inactivity.
- CWM rebooted the tablet as programmed.
- Tablet booted silently into ROM (most likely ICS).
- USB cable most probably also connected.
- ICS goes to sleep with USB connected.
- ROM SOD.
If they are testing out DRH ICS then yes you must use the 5504 version as recommended, but to my opinion any other 1.2 base ROMS they should use a more stable CWM recovery like 3028
Click to expand...
Click to collapse
As you can see from the above, the SOD happened in the ROM (and not in CWM), and the new timeout behaviour is not likely to trouble most users, so you can, in fact, use CWM-5504 instead of 3028. I currently have 5504 on my 1.1 bootloader and it works pretty much as advertised.
rajeevvp said:
First things first: Recovery mode never goes to sleep, so a Sleep-of-Death (SOD) there is out.
What actually would've happened is most likely this:
Some background first: the recovery program in CWM-5.5.0.4 sets a timeout before waiting for any input. This input timeout is set to 1 hour, and if an hour elapses without any user input, recovery is coded to reboot the system. (There is a bug (actually, two) in the coding which prevents this from actually happening every time, but, that is a matter for the developers.)
So, in your case:
- You were sitting in the main menu, and the input timeout expired after 1 hour of inactivity.
- CWM rebooted the tablet as programmed.
- Tablet booted silently into ROM (most likely ICS).
- USB cable most probably also connected.
- ICS goes to sleep with USB connected.
- ROM SOD.
As you can see from the above, the SOD happened in the ROM (and not in CWM), and the new timeout behaviour is not likely to trouble most users, so you can, in fact, use CWM-5504 instead of 3028. I currently have 5504 on my 1.1 bootloader and it works pretty much as advertised.
Click to expand...
Click to collapse
Actually what happened when my tablet "Timed Out" as you say I was actually setting things in CWM to get it ready for update 1.0. Never did I once let it sit doing nothing. So I selected "Power Off" option so that the tablet can Charge before I flashed the new update and no I already unplugged my usb connection I used for NVflash, I have all my updates, backups and ROMS on a 16gig external SD card so there was no need for the USB connection while in CWM 5504. When I selected the Power Off option it just stayed there saying "Powering Off" for over 15 mins, which uses to just close CWM and power off the Tablet. This time it never booted out of CWM and never Powered off. That was a good reason for me creating my own DRH. The Second time was during a Reboot after flashing a 2.3 based ROM., also no need for the USB since I downloaded and transferred everything needed to my External SD before hand. So with that being said do you really think that CWM 5504 doesn't cause a form of Timing Out or Freeze up that requires the need to either press the rest button to recover.
nobe1976 said:
Actually what happened when my tablet "Timed Out" as you say I was actually setting things in CWM to get it ready for update 1.0. Never did I once let it sit doing nothing. So I selected "Power Off" option so that the tablet can Charge before I flashed the new update and no I already unplugged my usb connection I used for NVflash, I have all my updates, backups and ROMS on a 16gig external SD card so there was no need for the USB connection while in CWM 5504. When I selected the Power Off option it just stayed there saying "Powering Off" for over 15 mins, which uses to just close CWM and power off the Tablet. This time it never booted out of CWM and never Powered off. That was a good reason for me creating my own DRH. The Second time was during a Reboot after flashing a 2.3 based ROM., also no need for the USB since I downloaded and transferred everything needed to my External SD before hand.
Click to expand...
Click to collapse
You said you had a SOD problem, but this isn't Sleep-of-Death at all. Its something completely different: lockups when powering off or rebooting. The cause of that is usually some kind of kernel bug--badly coded device drivers are one possibility. It could also be some kind of transient hardware problem--wonky hardware can cause even well written device drivers to go nuts. And both of those mean that we can, again, exonerate CWM. Specifically:
When you select reboot or power off in CWM, it just calls a (Bionic) C library function which, on the gTab, immediately calls the kernel which starts the reboot/power off sequence. And, if the kernel can't reboot or power off the tablet, then that's where the problem lies. The fact that I've heard this problem report only from you--and that too only on 2 occasions--just makes the case stronger. As a good example of the former (bad kernel code) consider the nVidia/Malata-written mtdblock device driver for the NAND flash. It is known to have problems. Try this simple command in CWM:
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]dd if=/dev/block/mtdblock0 of=/dev/null[/B]
I wouldn't be surprised if the tablet locked up instantly; though it usually takes 2 or 3 tries. You can try this on any CWM version you want. You can even lockup the ROM the same way.
So with that being said do you really think that CWM 5504 doesn't cause a form of Timing Out or Freeze up that requires the need to either press the rest button to recover.
Click to expand...
Click to collapse
See above.
Related
I just got a tablet from the outlet, but it can't boot up. It shows the android logo in small yellow text, then a <!> pops up. Reboots in viewsonic logo, and gets stuck at gtablet logo. I tried holding startup and vol + but that doesn't work. Help please!
EDIT: Thank this guy rcgabriel
rcgabriel said:
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
Gajun said:
I just got a tablet from the outlet, but it can't boot up. It shows the android logo in small yellow text, then a <!> pops up. Reboots in viewsonic logo, and gets stuck at gtablet logo. I tried holding startup and vol + but that doesn't work. Help please!
Click to expand...
Click to collapse
it's not broken - just flash the latest firmware
Try an nvFlash. Mine was stuck at the Viewsonic logo this pas weekend with the recovery (Vol+ and power) not working either. The nvFlash was very easy to do and fixed my Tab.
http://forum.xda-developers.com/showthread.php?t=861950
g1no23 said:
Try an nvFlash. Mine was stuck at the Viewsonic logo this pas weekend with the recovery (Vol+ and power) not working either. The nvFlash was very easy to do and fixed my Tab.
http://forum.xda-developers.com/showthread.php?t=861950
Click to expand...
Click to collapse
thanks for the reply. I tried this, but it didn't help at all. I was able to do all everything but it is still stuck on the gtablet logo. I can go to apx mode fine but I can't go to recovery mode, it reboots back to and gets stuck ;/.
Gajun said:
thanks for the reply. I tried this, but it didn't help at all. I was able to do all everything but it is still stuck on the gtablet logo. I can go to apx mode fine but I can't go to recovery mode, it reboots back to and gets stuck ;/.
Click to expand...
Click to collapse
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Dude! You are the best!!! You are a life saver!! It worked! I got into cwm! Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
EDIT: Just after few minutes of finally getting into CWM, I was able to install VEGAN on it easily. Seriously, I don't know how to thank you enough!
gtab won't boot on its own
ok so i followed the instructions and it worked i was able to boot into the tablet but when i reboot it won't do it i have to use nvflash again to get it to it and once i do and the tablet goes to sleep it wont come back up and once again i have to use nvflash. please help!!
rcgabriel said:
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
I'm stuck in bootloop and I tried you solution and being I'm a noob at this I dont know how to rename the dile under partition 9. I just simply rename the file to recovery.img and i get an error when running the nvflash when it gets to partition 9. Can you please help me .... All help is appreciated.
rcgabriel said:
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
How do you EDIT the gtablet.cfg file in Windows 7? Thanks
Thanks! And a potential pitfall:
Thanks! I was having the same problem all night last night, and repartitioning fixed it.
I'd like to highlight something I had a problem with: I wasted a couple of hours with the WRONG clockworkmod recovery image. I found a similar response from another user who didn't include a link, and I found the clockwork image for g-tablet pointed to by someone else. If you're still having boot loop problems, use the clockworkmod linked to from this thread (v2.5.1.1-bekit-0.8).
Thanks everyone!
Is there a way that a mod can make a Sticky of the "Bricked Solution" fix.
There is no such thing as a bricked Gtablet that I've ever seen. Ive messed mine up a few times now and still works fine no matter how bad it gets.
Same for me, this fixed worked. I was not able to mount /data prior to repartitioning, was able to after. Thus the GTab was able to boot again, I now have a stock GTab, formatted clean, running 3588. Always nice to have a path forward.
emanzi said:
How do you EDIT the gtablet.cfg file in Windows 7? Thanks
Click to expand...
Click to collapse
Use Notepad
Hey i've done as you suggested however I'm stuck at the entering nvflash recovery node / nv3p server print out on my viewsonic gtab.... I still have the device plugged into my computer and it is registered with the usb bus but it won't reboot into the recovery img. I tried to power it down and reboot with "power and volume up" but I get no response. Any suggestions?
One thing I noticed, when people say they try to use nvflash they are using volume +, that is incorrect. You have to do "volume - (the minus sign) with the power button at the same to get the point to be able to use nvflash. See this a lot places in the forums, no wonder there is problems with people trying to use nvflash.
Thank you so much for this. I started getting an error when trying to mount /data so I did an nvflash without reading into it...turned out to be a huge mistake because that caused bootloops and left me without CWM. Turns out I should have just repartitioned but I couldn't get CWM to install from an SD card even though I knew I need to get it back on. Tried dozens of other things - including the full format with no luck but this finally got me into CWM so I could repartition.
Thanks again.
may as well be a brick - in my gut...
Every attempt at customization seems to be a step backwards.
Late nights have been spent over the last week trying to get things back to "normal" and I've had little success. Actually, make that "no success"...
At current, I've been looking ALL DAY (at work) and the last 4 hours at the NVFlash process.
I've got:
USB drivers installed for Windows
Bekit's 1105 files in place (gtablet + windows files)
I can boot to apx with volume.minus and power
PC sees tablet
I can run NVFlash w/o issue
gtablet boots immediately to stock ROM
I power off the gtablet and all I get is APX MODE again.
And again.
I have tried re-running NVFLASH with Roebeet's updated (4/17) files - same thing
I have tried renaming recovery.img from clockwork as "part9.img" and re-running, no success.
I have tweaked the gtablet.cfg and actually adjusted the SIZE for partition 9 to match the clockwork version of what I've named "part9.img" and no luck.
I ran the Format.zip version of nvflash, then ran regular nvflash, no luck.
Every time I run bekit's NVFlash, it loads stock ROM a-ok. Power cycle brings APX mode... I can't get Clockwork to install via the "nvflash switcheroo" nor by dropping "update.zip" and the recovery folder + command file in the root directory.
I feel foolish for spending about $300 on a device like this, and I feel foolish for spending SO MANY LATE NIGHT HOURS trying to fix it, and now I'm essentially going to only be able to use it unless - unless! - someone can come up with something else for me to try.... or if I "boot with NVFlash and hope it doesn't fall asleep on me..."
Any ideas?
Trust me, I've read every thread, seen the same "oh this worked...!" over and over on steps I've tried 3x or more. I think I'm depressed as this is ALL I DID TODAY - research on how to fix my gadget. sigh.
EDIT:
Just thinking here... (scary!) Has anyone ever sideloaded ROM Manager into the stock 3588 ROM? What I'm thinking is that if I can get ROM Manager to install, it loads CWM simultaneously, correct? And from ROM Manager I can reboot into recovery, yes? I would have tried this last night but I didn't come up w/ the idea until past 1:30am.
Also, let me take a step back and explain how I got here:
Installed Cyanogen 7 stable
installed a different keyboard
next day I got keyboard force-closes incessantly
tried to reflash CM7 - boot looped.
I could flash to the stock 3588 ROM w/o issues, and could use Clockwork w/o issues
tried to flash CM7 again, no dice
I suppose what i should have done at this point is re-partition and THEN try to reinstall CM7 - but I was having an issue w/ clockwork not completing the Factory Wipe / Reset - it would get stuck...
so I decided to bring the hammer w/ NVFlash - and I've certainly accomplished that
I can't get clockwork to install despite all I've tried:
paste recovery.img into my NVFLASH folder
change part9.img to recovery.img in the gtablet.cfg file
put clockwork's update.zip in the root folder
put clockwork's update.zip (and change "command" file to SDCARD2
I guess - how do I know if I'm still rooted? When I (nvflash and boot into) the stock ROM, I can connect via usb and navigate the folder structure. I see .android-secure and "data" and other typical folders that I've seen for weeks now...
so tired...
What happens if you do a factory reset immediately after it boots?
@K J Rad - you mean after it boots to the stock ROM, going to settings/security/factory reset (or clear all user data, whatever it says?) - I've tried that twice, and each time it comes back to apx-mode only, and when I nvflash again all my wifi settings are still in place.
if you mean factory wipe / reset from w/in Clockwork - I can't get CW to install.
EDIT - I added more explanation in my earlier post - a "how did I get here" of sorts...
Ok... if you hold down the Volume Up key during the reboot after nvflash does it drop back to APX or enter Recovery? If it goes to recovery... try method I from this: http://forum.xda-developers.com/showthread.php?t=1030915
I had been running BOS 5.4 and I kept getting errors saying that Tablet memory was low and nothing I tried could get that error to go away. I tried uninstalling apps, tried wiping user data, nothing fixed it. Everything would FC constantly.
Long story short, now every time that I boot my GTab it boots straight into recovery without me pushing the volume key. I have tried re-installing BOS but nothing takes. I mount USB through ClockWorkMod and nothing is there except for the BOS zip file that I placed on the memory. Everything else is gone. I tried partitioning the sd card to 2048/0 and then tried re-installing BOS but to no avail. I am all out of idea.
Any ideas??
First off, there is no BoS a5.4 - not sure if you're running BoS or another HC ROM.
Second, did you try and do a factory reset while in the UI, and while cwm was installed? If so, then this is a known issue with cwm. I have instruction on Slatedroid for my ROMs, but to paraphrase here. Use either method:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Again, this is assuming that this is really Bottle of Smoke and not another ROM. If it's not BoS, then the ADB instructions may not work.
roebeet said:
First off, there is no BoS a5.4 - not sure if you're running BoS or another HC ROM.
Second, did you try and do a factory reset while in the UI, and while cwm was installed? If so, then this is a known issue with cwm. I have instruction on Slatedroid for my ROMs, but to paraphrase here. Use either method:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Again, this is assuming that this is really Bottle of Smoke and not another ROM. If it's not BoS, then the ADB instructions may not work.
Click to expand...
Click to collapse
I apologize, it was BOS 5.2. I will try this out and report back, thank you very much for the reply, roebeet. I am LOVING Bottle of Smoke, btw. Thanks for your hard work.
adb method is not working. I can't get it to find my device :/
If the factory restore in the UI was the catalyst, then one of these two options should fix it (if you can get it working). I've had this happen to me with cwm, on my Froyo ROMs.
What happens is that the device wants to wipe the user data, but cwm doesn't understand how to do that the way the device wants it to. So on every reboot it just keeps trying. When standard recovery is added back, the process can complete.
There is potentially one other way, but will take a few steps and I've never tried it myself.... in cwm, mount the device to your PC via the mounts and storage -- USB storage option. Then, grab the 4349 recovery update.zip that I advertise in Slatedroid (sorry, not allowed to give you a link as its against XDA rules - just google "1.2 recovey gtablet 4349"). Take that update.zip and put it somewhere on the mounted drive, unmount, then use cwm to run that update.zip. That should, in theory, get you standard recovery again and might allow the data wipe process to finish.
roebeet said:
If the factory restore in the UI was the catalyst, then one of these two options should fix it (if you can get it working). I've had this happen to me with cwm, on my Froyo ROMs.
What happens is that the device wants to wipe the user data, but cwm doesn't understand how to do that the way the device wants it to. So on every reboot it just keeps trying. When standard recovery is added back, the process can complete.
There is potentially one other way, but will take a few steps and I've never tried it myself.... in cwm, mount the device to your PC via the mounts and storage -- USB storage option. Then, grab the 4349 recovery update.zip that I advertise in Slatedroid (sorry, not allowed to give you a link as its against XDA rules - just google "1.2 recovey gtablet 4349"). Take that update.zip and put it somewhere on the mounted drive, unmount, then use cwm to run that update.zip. That should, in theory, get you standard recovery again and might allow the data wipe process to finish.
Click to expand...
Click to collapse
roebeet, you are my freaking HERO!! I downloaded the 4349 recovery update.zip and BOOM Bottle of Smoke is booting up like a champ. Thank you for taking the time to help me do this!!
http://www.youtube.com/watch?v=0N-SyPEL-pA
fidju said:
roebeet, you are my freaking HERO!! I downloaded the 4349 recovery update.zip and BOOM Bottle of Smoke is booting up like a champ. Thank you for taking the time to help me do this!!
http://www.youtube.com/watch?v=0N-SyPEL-pA
Click to expand...
Click to collapse
Thanks for the update! I might actually need to add those steps to my ROM's cwm caveats in my first posts (might be easier than adb/nvflash for most people).
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Use this thread to install CWM, I'm not a fan of TWRP. http://forum.xda-developers.com/showthread.php?p=25786947 I used this and had no problems updating
Sent from my NOOK Tablet running CM10
deltantor said:
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Click to expand...
Click to collapse
This has been happening to me occasionally. I have found that when I get the black screen, pressing the Power button launches Recovery (CWM in my case). See if that works for you.
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
To the rescue
Ok, I have posted this on a different day. Try this with a blank sd card. Look at the bottom post called "Here is a video"
It a external boot cwm v.5 but you can copy this into your sd then flash and you have cwm v6.0.1.5 internal. Either way you have two ways to do recovery (external and internal):victory:
djd338 said:
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
Click to expand...
Click to collapse
Thanks very much for the reply & link!
I'll do this ASAP when I get back home & report. Thx again!
Sent from my Nexus 7 using Tapatalk 2
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Look pass the fear and go one step at a time, before you know it, your there.
It looks like you have already resolved this from this thread.
Ok, basically I'll go step by step.
1. Download ubuntu iso from ubuntu website (you can donate or put 0$ then download iso) and burn it to cd. 5 minutes
2. Stick the cd into a system that you don't plan to look at the video that is showing you the process and boot it up from a reboot and not from within windows. Select the left square which basically load the ubunbu from cd but does not install anything to your hard drive.3 minutes
3. You can view the whole video but I would skip to the section in video (3:28 watch to 4:43, 6:56 watch to 8:06 ) where I mentioned the setting the two flags in your sd after quick format fat32 and extracting the four files into your sd within ms windows platform from the post . I did this with a normal mini sd card adapter and not the usb stick adapter he used in the video. Since you are doing this to a blank mini sd then there really nothing to worry about since it is blank in the first place. 2 minute
4. If you had your apps backup with titanium backup then it still will be on the main mini sd and not the one that working with for this recovery.
5. I notice you did not mention wipe dalvik cache from your post. You should always wipe dalvik then wipe factory then do a single flash to test boot up.. You can flash gapps after a successful boot up into jellybean. (here's a video showing that I'm using external cwm v.5 even though its recommended to use v.6 .) You can always use cwm v.6 on your next cm10 test rom or use cwm v.6 to reflash to same rom once a successful boot up have been obtained with external cwm v.5. This purpose is to get it running on your nt.
6. Be patient for the first boot. Should not be more than 5 minutes max. It will look black then load. If it boot loops then wipe dalvik then wipe factory and do a single flash to test boot up again.
This will at least get cm 10 flavored rom on to your nt.
djd338 said:
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Click to expand...
Click to collapse
Got it back! Thank you for your help & patience. Also for the timely responses. I now have a bootable "recovery sd card" for curing these type problems. I've labeled it & filed away for any future borks of this kind! And I have cm10 up & running stable.
Thank you!
Sent from my Nexus 7 using Tapatalk 2
Okay my Atrix 4g has unlocked bootloader, Android 2.3.6, and I flashed CWM recovery the other day, and it worked fine except whenever I plugged in my phone to wall charger, it would boot AUTOMATCALLY into that recovery. Followed this guide: LINK
I then installed CWM recovery 5.0.2.3 from here: LINK
Now again when I plug usb into wall to charge, it boots into the first recovery I installed. I can't see the battery charge symbol.
Now I downloaded this ROM - http://forum.xda-developers.com/showthread.php?t=1836674 and tried to boot into recovery from using the volume down button until "Android recovery" but that takes me to the stock 4 option crap.
So I tried to flash the MROM from ROM manager in the os, and it says restarting into recovery, AGAIN that takes me to the triangle exclamation point crap.
SO MY QUESTION is if I do a disk clear, format from the recovery, would my phone still work with T-mobile afterwards, and I can install the CWM again, and flash the new ROM?? I don't care about losing data, I have only few apps.
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
ravilov said:
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
Click to expand...
Click to collapse
Here's a crazier idea - do you mind explaining things in more detail, since I am a noob and this is a help forum.
--
When I install the the recovery, it just says hit yes to continue. Please help, rather than telling me that I am an idiot.
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
ravilov said:
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
Click to expand...
Click to collapse
No problem mate.
Well I guess I could tell you what I did, but I did exactly what the guides said:
downloaded the .zip archive, placed contents anyplace, and started cmd from that folder and entered:
adb install MOTOA4_Bootstrap_0408_1720-signed.apk
Then I opened up that app "System Recovery" and hit Install recovery, then I hit recovery mode from the app, and was told to connect the usb to the wall charger, not pc. And that was it for the first recovery. I then noticed that this specific recovery was missing some functions in the actual recovery so I installed 5.0.2.3 later.
I downloaded the .zip from the site and placed inside phone internal SD, the second link from OP here, turned on phone and went into Android recovery and it opened up the one I installed just a minute ago, and hit install zip from sdcard, I hit internal, and selected the .zip I downloaded from that site. I hit reboot recovery and it booted into that recovery, 5.0.2.3, the real one.
To go to this new one, I insert wall usb to phone and it boots in the first recovery, and I hit, reboot recovery, and it takes me to the new one.
NOW whenever I plug in usb to wall to charge, it boots in the old recovery, and I don't see charge symbol. I have calibrated my battery 3 times, and it is still CRAP (brand new 1800mah battery for mb860).
Anyways, I thought to ask here if I did a wipe data from the new recovery, or old, would it get rid of this whole mess?
Hmm ok.
I told you this before but here goes again. I'd give up on random guides from random sites. Everything you need is right here on this forum.
Not to mention, the recovery in that ZIP is slightly older, there is a newer one available.
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
The ZIP you downloaded seems fine, but it's somewhat likely your boot is also messed up too. If all this goes well, you can try finding the T-Mobile fruitcake (go over to the Atrix Reboot Project thread) and flashing it from the recovery. Be aware though that you might lose all data in doing this.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
ravilov said:
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
Click to expand...
Click to collapse
ALRIGHT thanks for this actual guide.
It installed fine, works fine, AND AGAIN whenever I plug the wall charger in when the phone is off, it boots into the OLD OLD recovery, from the first link.
I still can't see the battery.
Please stop throwing sass at me. :crying:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
ravilov said:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
Click to expand...
Click to collapse
I can only find this: http://forum.xda-developers.com/showthread.php?t=1163009
I downloaded the 2.3.6 ROM from the backup thread. Says nothing about T-mobile.So do I just install this from the new CWM?
Is there just no way of getting rid of CWM recovery so I can install it just once, rather than you keep telling me to install this and that?
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
ravilov said:
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
Click to expand...
Click to collapse
YES!!! Because everytime I connect the damn charger it boots cwm. AND EVERYTIME I hit ANDROID RECOVERY I boot into the OLD OLD OLD OLD Recovery.
why is that hard to understand? I want to uninstall ALL the cwms, and install the one you sent me just to have that one, rather having 3 different cwms I have right now.
Also that thread is just a bunch of people talking about nothing really. HAS ABSOLUTELY nothing to do with T-mobile whatsoever.
I just want to make sure that this AT&T phone will still work with my t mobile sim card after I install ROMs!!!!
---
And for the love of all that is holy, don't reply with: "why won't it?"
BECAUSE THAT IS WHY I AM ASKING. I have never done this, that is why I ASK!!!!!
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
ravilov said:
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
Click to expand...
Click to collapse
SO there is NO WAY to remove CWM recoveries?????
LOL THIS IS FUNNY! Now when I plug charger in, it just boots into OS, and when I hit android recovery with VOL buttons, it shows the white triangle.
Still don't get what that rom did. Installed it, and nothing, except for losing all my data.
This forum made things worse.
Thank you.
EDIT: OKAY NOW it shows the battery when plugged in but still the white triangle crap in the recovery.
You must have SOME recovery. You can install TWRP if you like that better, but you must have SOMETHING. By following the procedure I described you properly installed RomRacer's CWM so that part is fine. Now, why are you still sometimes getting the stock 4-option recovery - only heaven knows.
I don't think there's a way to install the stock Motorola recovery other than installing the full SBF, however SBFs are VERY dangerous and nobody is going to recommend that.
I really can't imagine what you've done with your phone. The mere fact you have multiple recoveries raises a big red flag right there. I tried to help the best way I can, but since obviously it's not doing much good, I'm going to refrain from further comments and let someone else take over. Good luck.
Ravilov has said it all but its pretty spread out trying to figure out what happened so I'm hoping I can tie it all together.
If you attempt to boot into recovery and get the old android recovery but booting normally puts you into CWM Recovery then somehow you have flashed the BOOT partition with CWM image. To fix this just download the correct fruitcake and flash the BOOT.IMG to the BOOT partition using the moto-fastboot tool and reboot. I would recommend erasing the BOOT partition first just in case.
Sent from my Nexus 7 using xda app-developers app
Thanks for your patience and help Ravilov
Sent from my MB860 using xda app-developers app
Hello all. I was successful in rooting my Nook Tablet according to this thread http://forum.xda-developers.com/showthread.php?t=2037368&nocache=1
Unfortunately, when I went to install the CM7 zip, it kept saying, "file not found"
I then read a post about enabling USB Debugging and Unknown Sources. So even though I shouldn't have rebooted, I really didn't have any choice but to reboot and go into settings and enable USB Debugging and Unknown Sources.
Now, I can't get back into recovery to install the .zip despite trying every combination I could think of or find by searching and I've literally been searching for hours.... must be using the wrong keywords because I can't find anything about getting back into recovery that works.
I even went to the Playstore and installed ROM Manager and GOO Manager and tried to reboot in recovery. When the Nook Tablet starts, it just shows and picture of a Nook with a red exclamation mark in the middle of it and says, "Please restart and try again..." or something like that.
Any ideas? Thanks for any response
In terminal emulator : "reboot recovery" or powering off and holding home and power buttons for like 5secs
If you tried booting recovery and it came up with nook recovery then you haven't replaced your internal recovery program to cwm. Instead of cm7 I'll suggest using cm10 because its much more new and essentially is the same thing, just improved.
If you end up not knowing how to internally flash then either read, read, read until you understand or get an SDC image. So many people brick their nooks by not understanding how to internal flash. The SDC image has no risk.
nikufellow said:
In terminal emulator : "reboot recovery" or powering off and holding home and power buttons for like 5secs
Click to expand...
Click to collapse
I tried several times holding the buttons but that didn't work. Terminal Emulator just says, "Operation not permitted." Thanks though.
nikufellow said:
In terminal emulator : "reboot recovery" or powering off and holding home and power buttons for like 5secs
Click to expand...
Click to collapse
datallboy said:
If you tried booting recovery and it came up with nook recovery then you haven't replaced your internal recovery program to cwm. Instead of cm7 I'll suggest using cm10 because its much more new and essentially is the same thing, just improved.
If you end up not knowing how to internally flash then either read, read, read until you understand or get an SDC image. So many people brick their nooks by not understanding how to internal flash. The SDC image has no risk.
Click to expand...
Click to collapse
I was orginally in CWM Recovery when it would let me flash the CM7. The link to the thread in the OP advised that CM7 and the appropriate Gapps needs to be installed first before flashing the CM10 + JB Gapps zips. According to the thread I linked, these ROM's will be flashed to internal. This is the method I've been searching for because I didn't like the SDC image idea... just me.
I wasn't supposed to reboot the NT per instructions but when I forgot to enable USB debugging, it would not let me flash the .zips so I had to reboot the NT to get into settings. Is there a way I haven't read about yet that will enable me to flash the .zips without going through CWM Recovery or is it an absolute must?
Umigobbles said:
I was orginally in CWM Recovery when it would let me flash the CM7. The link to the thread in the OP advised that CM7 and the appropriate Gapps needs to be installed first before flashing the CM10 + JB Gapps zips. According to the thread I linked, these ROM's will be flashed to internal. This is the method I've been searching for because I didn't like the SDC image idea... just me.
I wasn't supposed to reboot the NT per instructions but when I forgot to enable USB debugging, it would not let me flash the .zips so I had to reboot the NT to get into settings. Is there a way I haven't read about yet that will enable me to flash the .zips without going through CWM Recovery or is it an absolute must?
Click to expand...
Click to collapse
You don't need to flash CM7 before CM10. It just replaces it anyways. You just need to replace your current internal recovery with CWM and install the zips. There's no other way to internally flash without using a recovery program.