Yes, I know.. Many posts like this one, but there seem to be many variations also, so I'm concerned if I'm following the right advise or will make things worked. Also, while I copied the external SD Contents, I made the fatal flaw of not doing the propper backup (Stimpy.. you idiot!)
I tried following this approach:
The initial image with CWM 5.x worked fine, and the Nook rooted fine. I installed ES File Explorer, launched the Nook recovery Flash.apk, fine
Installed CWM 6.2.7 fine.
Final Step - Went to install the last stable release of CyanogenMod (cm-10.2.1-acclaim) and the screen flashed several times, then went off).
I powered it on and it stuck int the "Read Forever" white screen.
I can get it to go into Recovery mode by booting off the micro SD Card image I first created, and can even get it to CWM 6.2.7. But that's it. I can't get it beyond recovery mode, or rebooting into the "Read Forever" screen.
As a last resort (and maybe not a bright one?) I tried restoring back to factory defaults..... To no avail. No change in behavior.
After downloading some earlier mod versions (i.e. 10.1.3, 10.2.0, etc) I did manage to get the Cyanogemod bootloader to install. However, I could not get past the initial boot screen (where the Arrow circles the face).
I tried installing different versions of the Mod (even successfully installing 10.2.3 which I initially had problems with). I tried wiping the cache, and the Dalvik cache and rebooted, as well as trying wiping them, installing another cyanogenmod and restarting, and to no avail.
So, I can get to recovery screen, and I can get to the bootloader screen, but no further.
And all this, because Netflix stopped working on the original 1.4.3 B&N firmware (sigh).
Really appreciate some help here.
Thanks
See http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 and http://forum.xda-developers.com/showpost.php?p=48612997&postcount=1 for info and pointers on potential steps for recovery and re-flashing.
Related
So...I can't install either of the two CM based ROM's I've downloaded. However, on the first try, I installed VEGan, and then tonight TNT Lite, with no issues. Any CM ROM I try to install just sits on the loading screen, regardless of how long I wait. Is there something special that needs to be done to install them, different than what I do for other ROM's? (Clear data/cache, flash the ROM, clear data/cache again, reboot.)
sfreemanoh said:
So...I can't install either of the two CM based ROM's I've downloaded. However, on the first try, I installed VEGan, and then tonight TNT Lite, with no issues. Any CM ROM I try to install just sits on the loading screen, regardless of how long I wait. Is there something special that needs to be done to install them, different than what I do for other ROM's? (Clear data/cache, flash the ROM, clear data/cache again, reboot.)
Click to expand...
Click to collapse
I believe you have ClockworkMod 0.8 recovery, since you were able to flash Vegan Rom.
In general, before you flash the different rom
1. Back up your current rom
2. wipe data (factory reset)
3. wipe cache
4. flash the rom
5, flash gapps
6. reboot
Hope this helps
There have also been some reports of G-Tablets coming out of the box with incorrect partitions.
Using NVFlash has cured those issues. You should then be able to flash CM7 Roms through CWM like everyone else.
I repartitioned with 2048/0, shouldn't that rule out any partitioning problems?
I'm trying it again right now with flashing the rom then gapps.zip, waiting for it to boot...or just stay on the boot screen.
Format system and data, then follow those steps again. I ran in to similar issues when I hadn't formatted.
Also, do the three wipes again after installing the ROM and gapps.
Holy crap! I see the CM boot screen now! Thanks for the help guys. Now, do I still need to do the market fix (http://forum.xda-developers.com/showthread.php?t=865245)? It looks like from their changelogs that the latest version of Flash is cooked into the ROM so I shouldn't have to do that part from the guide, but I'm wondering about the market.
Well, the market seems to have everything, including an app (power control plus) that none of the other rom's let me see, so I seem to be good to go! Thanks again guys!
Thanks for the suggestion - and I'll readily admit I'm WAY out of my comfort zone with Android.
When I format the /system /data do I have to mount first?
What order do the steps run in? Do I partition and then format /system /data?
cannot install cm based roms
I was trying to reset from factory rest but failed when my gtablet stucked and apparently did something wrong along the way. Now when I turn it on, I get the 3 birds screen, followed by G-Tabdevs screen, then dead. I do have clockwork mod installed on it.
1 when I clicked factory rest, it just return to the manue and said cannot find the file.
2 when I did a back up, it went through boot image,recovery image,system and then taskbar stopped in the half at settings.apk and then dead.
3 when I tried to followed this link http://forum.xda-developers.com/showthread.php?t=865245
to use the external tf card to flash, Gtablet doesnot recogonize the external card, while I can read all the files in gtablet. I can copya single small file but cannot paste a recovery and update.zip on gtablet. Each time I copied a file from gtablet, then it is dead. I have to return on by pressing power and volume+.
4 I tried adb to push update.zip to gatblet,also failed. I feel my gtablet can only allows me to read it and refuse me to do anything on it.
Any ways to reboot my gatblet brick?
Please help! I've been reading forums all weeks trying to figure out how to fix it and am not having any luck!
Appreciate any suggestions
Hello all,
I need some advice. I originally followed this page http://wiki.cyanogenmod.com/wiki/Sam...l_Update_Guide to flash and everything was fine for 3 or 4 days and then the fc's came. So i odin'd to stock and when getting ready to reflash i see that you need to be on 2.2 to use his guide. So another member kwkslvr (who has been very helpful and patient btw) told me his method for flashing CM7 so i attempted to straight from 2.1 with no root to the following...
(kwkslvr's method) You definitely don't need to be on Froyo. You don't need root either. What has worked best for me is to Odin to 2.1, reboot into stock recovery and flash update.zip. Since you've flashed before, update.zip will probably already be in your internal sdcard unless you removed it. You'll have to flash it twice in a row without rebooting and that will load ClockworkMod Recovery.
Once you're in CMW Recovery (probably green recovery), wipe data/factory reset then format/system. These two steps are CRUCIAL! Flash your CM7 Nightly twice. The first time you flash it, it installs blue recovery. The second time it installs CM7. After that, again without rebooting, install gapps.
From that point, wipe data/factory reset again and reboot into the OS.
So i tried that and got to where the phone restarts after the flash and it has galaxy and cyanogen below it for a few seconds and then immediately script with font like from recovery mode races down the screen for a few seconds, then back to galaxy/cyanogen in a loop. So i odin'd again and as of now am stock 2.1 with the options of kies n it to 2.2 and then follow cyan page again or trying kwkslvr's method again. I did notice he mentioned nightlies but i am attempting to flash the stable on page 1 of this thread but don't think that would make much difference. I love the way this ROM looks and performed before it went off the tracks. Any suggestions are welcomed. Thanks alot
EDIT: At the boot loop sequence i 3 buttoned to recovery and reflashed and it seems to have worked. I notice the battery gauge no longer has the # %. And the horizontal line next to it is gone too. On my market page under "not installed" i have adobe flash showcase (Reads this item is not available at top), google search which just has a open tab (Already is installed), magic 8 ball by dennis bond (Reads this not available in your country?? it was the first time i installed it) Any ideas on how to get these 3 items off the not installed section. It's mainly a minor annoyance. I have cleared cache in market with no luck. Thanks.
So I hate starting a new thread, but after searching for a day I have not been able to fix this issue.
I was running UnNamed v2.1.1 and wanted to update to the newest version. Following the instructions, I booted into CWM, wiped data/factory reset, installed the zip from my sd and rebooted. It worked fine, but I lost all my contacts which were on my SIM card (I was dumb and didn't back them up).
When I had previously updated I still had my contacts so I figured they should still be there. In an effort to find them I booted into CWM mode again and installed CM9 Nightly from my zip card. Again it booted fine, but still no contacts. I decided to go back again to UnNamed (wasn't a fan of CM9) and then I ran into issues.
My phone got stuck in the boot animation screen. I waited 20 min and nothing. Then I followed creepyncrawly's guide for returning to stock. My computer said "PASS" but when it rebooted it said "failed to mount /data (Unknown error: 0)". I turned off the phone and tried again and it seemed to work, but now my phone is still stuck in boot animation screen.
Any ideas how to fix this?
Reflash stock rom through Odin. But I would flash a cwm kernel through Odin, boot into recovery, and flash a rom.
Sent from my SGH-I777 using xda premium
supertwinkey said:
So I hate starting a new thread, but after searching for a day I have not been able to fix this issue.
I was running UnNamed v2.1.1 and wanted to update to the newest version. Following the instructions, I booted into CWM, wiped data/factory reset, installed the zip from my sd and rebooted. It worked fine, but I lost all my contacts which were on my SIM card (I was dumb and didn't back them up).
When I had previously updated I still had my contacts so I figured they should still be there. In an effort to find them I booted into CWM mode again and installed CM9 Nightly from my zip card. Again it booted fine, but still no contacts. I decided to go back again to UnNamed (wasn't a fan of CM9) and then I ran into issues.
My phone got stuck in the boot animation screen. I waited 20 min and nothing. Then I followed creepyncrawly's guide for returning to stock. My computer said "PASS" but when it rebooted it said "failed to mount /data (Unknown error: 0)". I turned off the phone and tried again and it seemed to work, but now my phone is still stuck in boot animation screen.
Any ideas how to fix this?
Click to expand...
Click to collapse
Don't know what is installed with cm9, or if flashing cm9 repartitions, but you can find bootloaders, param.lfs and PIT and complete stock UCKH7 packages in the Download Repository linked in my signature.
Troubleshooting without enough information is only a shot in the dark. I often see problems with param.lfs associated with boot loop. Your error message not being able to mount /data partition suggests PIT. Just some thoughts to start you on the way.
Finally fixed, thanks for the suggestions. After flashing the stock rom in Odin it still wasn't working. I was wiping factory/data before flashing, but for some reason when I wiped after flashing it worked fine.
I've had Android on my Touchpad 32G for quite some time now, both CM7 and the latest CM9 alpha.
Recently I wanted to upgrade to the official nightly, so I downloaded that, Gapps, Rohans tweak and various other small things and was ready to go.
I did a wipe/factory reset, wiped cache and dalvik as I usually do.
Then I tried to update to the nightly, however it just rebooted my Touchpad.
When it starts to install it shows the usual "finding package...", "opening package..." and "installing package..." but when it gets to the "installing package..." part it freezes for a second and then reboots everytime I try it.
I have both CWM and TWRP, and TWRP now refuses to run. I can select the option in moboot and it is actually trying to run, and even go as far as showing the splash that is supposed to "roll up", but then it reboots just like when I try to flash a rom.
CWM works perfectly as well as the original webOS 3.0.5 installation.
I have tried clearing the uiImages from /boot (using webOS and classicnerds cleaner) which doesn't solve my flashing problem.
Now, upon flashing any new rom, it always reboots as per the description above.
Any solution to this? Help would be much appreciated.
I have created a 4GB partition for Ubuntu chroot that can be started from within webOS.
Does creating that partition break the ability to flash?
It was created using Tailor from the webos-internals testing feed.
I actually had this issue myself yesterday, in that I couldn't flash anything. What I ended up doing was deleting ALL the partitions, doing a factory reset to 3.0.0, then upgraded to 3.0.5, then reinstalled using ACMEInstaller. There's a guide here on how to reflash back to factory (which removes everything - Android, WebOS, all the partitions and data of everything), which I followed, then I reinstalled the latest nightly (20120402) with ACMEInstaller.
That's what I would suggest. Yes, wipe-everything-and-reinstall is kind of annoying, plus you lose everything from WebOS, but this way you're sure to have it working again, like I did.
Then, as a suggestion, when you flash the ROM, flash JUST the ROM, and the GApps zips first. Boot up and make sure they work. Then flash Rohan's tweak, reboot, make sure it works. Then reboot, do a backup, and flash the other stuff one at a time, so you can try and troubleshoot where the problem lies.
That seemed to work, thank you.
Before I did that I tried repairing the partitions using Tailor, however it didn't work.
I know there are several threads regarding the Wifi issues on the Nabi 2, and I have followed them and have tried to resolve by restoring a stock image with limited success.
I was able to Install TWRP, backup to SD, and go through the recovery process for several stock images but the only one that will boot for me is 2.3.11.
I have recovered them all 1.9.12, 1.9.37, 2.05, and 2.1.27, none of them would boot after the restore, they would just hang on the white Nabi icon with the spinning ring around it. Most of them would overwrite the recovery partition, which I had to restore via fastboot.
I copied each image to my sd card, and the process I followed was:
Boot to recovery (TWRP)
Restore
Reboot
A couple times I tried doing a factory reset via the hidden recovery menu, but that did not make a difference.
I can get 2.3.11 to restore with no problem, and it boot fine. I am wondering if this is because I am on the Jelly Bean bootloader (I ran the addonfix) and that the older images need the ICS bootloader? However, I could not find any separate downloads for an ICS bootloader.
The other thing I thought is that maybe the version of Nabi I have (listed in the title) was the problem.
Any ideas?
rnabi99 said:
I know there are several threads regarding the Wifi issues on the Nabi 2, and I have followed them and have tried to resolve by restoring a stock image with limited success.
I was able to Install TWRP, backup to SD, and go through the recovery process for several stock images but the only one that will boot for me is 2.3.11.
I have recovered them all 1.9.12, 1.9.37, 2.05, and 2.1.27, none of them would boot after the restore, they would just hang on the white Nabi icon with the spinning ring around it. Most of them would overwrite the recovery partition, which I had to restore via fastboot.
I copied each image to my sd card, and the process I followed was:
Boot to recovery (TWRP)
Restore
Reboot
A couple times I tried doing a factory reset via the hidden recovery menu, but that did not make a difference.
I can get 2.3.11 to restore with no problem, and it boot fine. I am wondering if this is because I am on the Jelly Bean bootloader (I ran the addonfix) and that the older images need the ICS bootloader? However, I could not find any separate downloads for an ICS bootloader.
The other thing I thought is that maybe the version of Nabi I have (listed in the title) was the problem.
Any ideas?
Click to expand...
Click to collapse
Yes there are ones that will not boot because you have the JB bootloader. The only ones that will boot are 2.3.11, and 2.4.6 unless you reinstall the ICS bootloader. There is a way with APX/nvflash but I'm not sure that going back is going to help wifi. That is usually fixed by factory reset, or just clearing the wifi conf file.
aicjofs said:
Yes there are ones that will not boot because you have the JB bootloader. The only ones that will boot are 2.3.11, and 2.4.6 unless you reinstall the ICS bootloader. There is a way with APX/nvflash but I'm not sure that going back is going to help wifi. That is usually fixed by factory reset, or just clearing the wifi conf file.
Click to expand...
Click to collapse
I have tried factory reset several times and I just tried deleting the conf file, neither fixed it. This is for my nephew with Autism and he has been very upset that his Nabi is not working so I have been trying for days to get this working for him, but I'm about ready to give up.
Any other ideas? Does anyone think it is worth it to try the APX/nvflash route to go to an older image? I am starting to think maybe there is an actual hardware issue with wifi. :crying:
My granddaughter has autism and her Nabi will not connect to WiFi I’ve tried everything and still not working. I build computers so I know how to do most things but this is way to much