After I successfully flashed (MOD)(BL1.2ROM-CM-10)SmOoTher_BeAn_4.1.2(G-tablet)(Updated 02/01/13) I attempted to install the Google Now launcher plus some other apps from the Play Store which resulted in the tablet becoming non-responsive and lagged. I tried rebooting into recovery and clearing Data, Cache & Dalvik then rebooted but the tablet will only boot back into recovery. I've tried flashing the ROM again but no change. I'm starting to think that I might need to restore to factory using Bekit and NVflash but those files are no longer available.
BL 1.2
ClockworkMod Recovery v3.0.2.8
I've got a MediaFire folder of GTab recovery stuff here. Hopefully you find what you need there.
...Oh, I thought this post was from September of 2017. Well, maybe this will help anyone else with similar problems in the future. Good luck.
Related
I have tried several different Rom Managers without a problem on my G Tablet. Have been using TNT lite. Recently I switched to Vegan Gingerbread edition, but when I went to backup my old Rom (TNT Lite) the backup hangs on backing up the cache. I tried wiping the cache and formatting the cache, but it always hangs indefinitely.
I installed Vegan Gingerbread anyway and it appears to work perfectly, yet I still cannot backup the rom with Clockworkmod (always hangs on the cache). If I try to look at the cache partition in filemanager, it shows empty, though I am not sure it is actually recognized. I can't seem to do anything with the cache at all.
I am, by no means an expert, but have had no problems with this before. Backup did work before the recent problem.
Since everything is working with my G Tablet now, I am not sure there is an actual problem with the cache, except that I can't backup the Rom without it hanging on the cache. This may limit my ability to load other Roms in the future.
Please help.
I have the exact same problem. I've had no issues backing up and restoring ROMs myself, but now I'm having issues with my tablet not being able to format or restore cache. I can install a ROM, but it takes a long time to actually load up - it can sit on the first splash screen for easily 5 minutes before it boots into the ROM, wher as before it took around 1 minute or less. Are you having this slow boot problem as well, or are your problems strictly with the cache? I'm going to continue to look into it (currently looking into using nvflash to do a restore and see if that irons things out), so I'll let you know if I come across any solutions. And please, let me know if you do as well.
hey guys i had the exact same problem before but nvflash fix what ever the problem was and the newly installed cwm work as it should. are you getting "ANDROID" screen right before it goes into cwm?
I am not getting the Android screen before ClockworkMod, but I generally boot with the power/vol + combo. I also have not changed Rom's recently, so I am not sure if this would be a problem or not. I do not have any boot problems that I am aware of, nor can I see and performance problems resulting from my inability to format the cache. The only problem is I can't wipe the cache, backup the rom, or format the cache as it stops on formatting cache partition and therefore can't continue the backup process. Other than incomplete backups I am not sure what problems this actually causes. Do you know.
I haven't used NVFlash yet, but I guess I will have to give it a try. Am I simply restoring the ROM to factory state and starting over or is there some other process I am looking for? Unfortunately, I did not get a proper backup of my original factory rom, so I will have to rely on downloads. Any tips on NVFlash would be greatly appreciated.
It's Fixed! Thanks for the tips.
Here is how I did it:
Ran NVFLASH - it was much easier that expected. It fully restored the original stock Rom, but I still had trouble with clockworkmod. Mostly it would not boot into recover mode. I then re-rooted the tablet using the Update.zip method, Then everything worked fine including backup and cache format.
I continued to restore my tablet and tried the backup each step of they way.
I installed Vegan Gingerbread - Worked flawlessly
I reinstalled MyBackupsPro and all my apps and Data - Also, worked flawlessly
I reinstalled Rom Manager - also worked flawlessly.
I used Rom Manager to upgrade ClockworkMod to 2.5.1.8 - then the backup/ format cache problem reappeared.
I then ran Rom Manager again and selected flash alternate ClockworkMod. It restored version 2.5.1.1. Then the backup and format cache worked again.
It appears that my Gtab does not work properly with Clockworkmod ver 2.5.1.8 and that was the entire problem.
Since Version 2.5.1.1 works great, I see no reason to upgrade this again and consider my problem fixed. I hope this info helps others
I have flashed a few different roms trying to find one I like and have not had any issues until I flashed GTabComb.
I am not stuck in ClockworkMod (v3.0.2.8) (GTab 1.2). I can reboot the system but it just puts me back in recovery. I have tried flashing a rom that worked before, and wiping every partition, cache and factory reset. I have tried to reflash cwm but it fails.
I had a friend who is rather experienced in this stuff (hokansoc) suggest to me that it could be the flag is stuck that causes the bios to select recovery and that and adb reboot device might work. However I am having a very hard time getting the tegra drivers to work (if anyone has a good guide to that it would be appreciated).
As always, any help is appreciated. Thanks
Was able to apx->NVFlash->clockwork and reflash rom. Mods, feel free to close.
So, I was able to successfully unlock my bootloader, got TWRP 2.6 on it, and put a few different ROMs on my machine; however, I have yet been able to install a ROM and get it to move past the boot animation.
I have tried the latest nightly ROMs for CyanogenMod 10.1 and 10.2 for my TF201, both of which get stuck in CM's boot animation. I just tried the same with the newest Baked ROM, only to be stuck in its boot animation as well.
I'm trying to figure out if there was something I forgot to do. I have been able to revert to a backup of my stock Jellybean 4.1.1 that I stored using TWRP, but haven't been able to use anything else.
Are there any thoughts on this? Have I missed something? I was able to use the unlocker utility and each boot offers the confirmation in the top-left that my bootloader is unlocked. I am able to enter TWRP from the recovery mode. Shouldn't it be as simple as selecting a ROM's zip archive and installing it from TWRP?
Have you done a full wipe before installing, including cache and dalvik cache partitions?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Try installing twrp 2.5. AS I just read in another thread there are problems with 2.6..
Sent from my MB526 using xda app-developers app
Factory reset
After flashing CM 10.1 nightly last night i had the same issue. I booted into my recovery console (flatline cwm) and performed a factory reset. This seemed to clear whatever issue was bothering the tablet. Still sat there for about five minutes on the animation after the reset but then progressed into setup.
Doubt if it makes a difference but mine was connected to the dock too.
If you're still stuck the method that worked for me yesterday was:
Used Flatline CWM as the recovery, installed using fastboot
Used an external memory card to copy the relevant zip files to my sdcard, recovery couldnt find them otherwise using adb push
Installed from zip using Flatline CWM
Installed gapps using Flatline CWM
Booted, got the issue you had
Booted into recovery, performed a factory reset
Told recovery to restart the machine
Booted into setup screen after loading for a few minutes
I'm sorry to post another yet another boot-loop post, however I have found the suggestions from other threads were to no avail.
I rather naively attempted to root and flash a custom ROM earlier today due to growing frustration over TouchWiz and its associated apps. So I rooted my phone using Chainfire's CF-AutoRoot and Odin.v3 which seemed to work perfectly and my phone booted fine afterwards. I then went into the Play store and downloaded ClockworkMod Recovery and created a recovery image of my phone. Then using the download and install ROM feature of ClockworkMod I downloaded Cyanogenmod and downloaded the most recent stable release (cm-10.1.3?). However when I tried to flash and restart it warned me that my storage was too low so I stupidly transferred the backup I had made from my s3 to my computer. When I tried to flash the second time the install appeared to work and my phone rebooted, however it is now stuck on the Cyanogenmod boot screen.
I can access Odin on the phone as well as the recovery mode, but I am at a loss as what to do next.
Thank you.
AlexFrancis said:
I'm sorry to post another yet another boot-loop post, however I have found the suggestions from other threads were to no avail.
I rather naively attempted to root and flash a custom ROM earlier today due to growing frustration over TouchWiz and its associated apps. So I rooted my phone using Chainfire's CF-AutoRoot and Odin.v3 which seemed to work perfectly and my phone booted fine afterwards. I then went into the Play store and downloaded ClockworkMod Recovery and created a recovery image of my phone. Then using the download and install ROM feature of ClockworkMod I downloaded Cyanogenmod and downloaded the most recent stable release (cm-10.1.3?). However when I tried to flash and restart it warned me that my storage was too low so I stupidly transferred the backup I had made from my s3 to my computer. When I tried to flash the second time the install appeared to work and my phone rebooted, however it is now stuck on the Cyanogenmod boot screen.
I can access Odin on the phone as well as the recovery mode, but I am at a loss as what to do next.
Thank you.
Click to expand...
Click to collapse
Choose Wipe data.Factory Reset from recovery
Then, Wipe Cache and, go to Advanced and choose Wipe Dalvik Cache reboot if that not work read this and learn all the basics of flashing roms especially backing up efs folder...
Read this http://forum.xda-developers.com/showthread.php?t=1931790
. I then went into the Play store and downloaded ClockworkMod Recovery and created a recovery image of my phone. Then using the download and install ROM feature of ClockworkMod I downloaded Cyanogenmod and downloaded the most recent stable release (cm-10.1.3?
Suggest you use the standard method as posted not this one .
Fixed
tallman43 said:
Choose Wipe data.Factory Reset from recovery
Then, Wipe Cache and, go to Advanced and choose Wipe Dalvik Cache reboot if that not work read this and learn all the basics of flashing roms especially backing up efs folder...
Read this http://forum.xda-developers.com/showthread.php?t=1931790
Click to expand...
Click to collapse
Thank you very much for your help. I had already tried this a few times to no avail, but after you posted I figured it would be worth giving it one more try, and lo and behold it worked! Thanks again
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