I read and read - did not see an answer to my question - if so I did not understand.
I have ran the NvFlash and it appeared to go okay - but now my Gpad does is rotate back and forth between the Viewsonic and Gtablet screen.
I am stuck on what to do next.
Thanks very much for your help!
Same exact thing happened to me Friday night. I fixed it by partitioning to 2048 0 using CWM via NVFlash.
How do you do that?
Sorry to be so thick!!!!
I found the downloads for cwm - how do you access that with NvFlash?
You can flash the stock recovery images and swap in teh part9.img with the CWM recovery file taken from the cwm zip.
Basically, you need to extract the CWM recovery zip and get the recovery.img file. You rename this to part9.img and replace the part9.img file in the nvflash_stock 1105 directory wherever you have it.
Alternativly, you can put CWM recovery on the microsd card, the instructions are in the CWM recovery thread.
Finally, I had issues failing to boot when I was using a different nvflash.exe. You should use the 140KB nvflash file for the process outlined int eh stock recovery thread.
CWM and nvflash are 2 different things. Install cwm and repartition as suggested.
tgatlinjr said:
How do you do that?
Sorry to be so thick!!!!
I found the downloads for cwm - how do you access that with NvFlash?
Click to expand...
Click to collapse
Here's a step-by-step tutorial:
http://forum.xda-developers.com/showthread.php?t=1030042
Once you're into CWM just go to advanced and then partition to change to 2048 & 0.
Btw, since you're going to be changing two files in your NVFlash folder (part9.img & nvflash_gtablet.bat) you may want to copy them somewhere else on your pc so you can put them back after you're done.
I did manage to get it to boot and download the 3588 update but when it reboots and tries to apply the update it fails.
Any ideas?
tgatlinjr said:
I did manage to get it to boot and download the 3588 update but when it reboots and tries to apply the update it fails.
Any ideas?
Click to expand...
Click to collapse
One way is to get the 3588 zip from the forum here & download it to the root of the G Tablet. Rename it to update.zip & install with CWM. I'd also wide data/factory reset & wipe cache partition too.
I have installed CWM now with no problem.
The Gpad boots to Viewsonic Tap UI version1.0-2638
It then informs me that there is an update to 3588
It proceeds to download the update - asks me to accept and apply the update
States it will shutdown to apply this update - it does, reboots - and after a few seconds a triangle with an exclimation mark along side the little Android man pops up and will do nothing else.
I, also, downloaded the 3588.zip file as suggested in the previous reply and got the same result.
I wiped the cache and did the data factory reset as well.
Any ideas to where I can go from here as all of this is new to me?
Hi everyone - got it fixed.
I appreciate everyones help.
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 just flashed Calkulin's ROM but when I reboot, I keep getting stuck at the "gtablet" screen.
I followed these exact directions except I did a wipe before and after flashing.
http://forum.xda-developers.com/showthread.php?t=865245
Any help?
Had a similar problem myself. The way i fixed it is by replacing "part 9" with the recovery image from clockwork and renaming it part 9 (then you reflash again). What this does it install clockwork on your tablet again. Once you get back into clockwork you need to partition your SD card to 2mb/0 swap. Once that finishes you should be able to reboot fully.
thanks
tyranie909 said:
Had a similar problem myself. The way i fixed it is by replacing "part 9" with the recovery image from clockwork and renaming it part 9 (then you reflash again). What this does it install clockwork on your tablet again. Once you get back into clockwork you need to partition your SD card to 2mb/0 swap. Once that finishes you should be able to reboot fully.
Click to expand...
Click to collapse
thanks that really worked
I installed CWM and TNT 4.4.0; and was able to boot once(first time). But once I powered down the gTab, It goes in to boot loop. I am able to boot into CWM and able to connect to my pC via USB Mass storage using CWM; please help me correctly install the TNT app.
thanks in advance,
I hope this helps!
Check out this thread and make sure you read the comments because you installed CWM.
http://forum.xda-developers.com/showthread.php?t=842000
Also, if you decide to upgrade to a custom ROM, you don't have to install CWM. You can do it in standard recovery, but there is another thread it in both:
http://forum.xda-developers.com/showthread.php?t=842004
Good luck!
i would try re-flashing the rom. maybe even re-download it to ensure that the file isn't incomplete or corrupt.
can I just install tntlite 4.3 or something that is older and upgrade to 4.4? Since I have the CWM installed already?
At this point I do get the Bootloader and mount error E: can't mount /dev/block/mmcblk3p2
Perhaps a good course of action would be:
1> Boot into CWM then partition the sdcard to 2048/0.
2> Follow direction in the second post to return to stock rom, then re-flash the rom using standard recovery (not with CWM).
If that does not work, then use nvflash method to return to stock and start over again http://forum.xda-developers.com/showthread.php?t=861950. I had to do this several times to get my gtablet functions the way it should.
Hope this helps.
tboneuncw said:
. . .
Also, if you decide to upgrade to a custom ROM, you don't have to install CWM. You can do it in standard recovery, but there is another thread it in both:
http://forum.xda-developers.com/showthread.php?t=842004
Good luck!
Click to expand...
Click to collapse
yes, I preferred the standard recovery method to install rom too. However, I have not been able to search for a method to install latest kernel without the use of CWM. Do you have a method?
mydave1 said:
Perhaps a good course of action would be:
1> Boot into CWM then partition the sdcard to 2048/0.
2> Follow direction in the second post to return to stock rom, then re-flash the rom using standard recovery (not with CWM).
If that does not work, then use nvflash method to return to stock and start over again http://forum.xda-developers.com/showthread.php?t=861950. I had to do this several times to get my gtablet functions the way it should.
Hope this helps.
Click to expand...
Click to collapse
What does partitioning of 2048/0 do?
use4all,
To answer your question, it may fix it.
When I hear boot loop, I think partition problem because partitioning often
does fix it.
1. Flash the tablet back to stock. Use the files in the instructions:
http://forum.xda-developers.com/showthread.php?t=861950
2. Install ClockWorkMod (CWM)
3. Reboot into CWM and go to the Advanced Menu -- Repartition to 2048 and 0, Fix Permissions
and Wipe Dalvik Cache. Return to Main Menu and Wipe Cache
and Wipe Factory Data.
4. Shut down and repeat Step 1.
5. At this point if all has gone well, you should have a "stock" working
tablet with "Bekit 1105" (AKA Stock Version 2638 on it.
6. Set up the wifi and almost immediately you should get an OTA (over the air)
Update notice. Do it and when you finish you should have a Stock 3588
tablet.
From there, you can move carefully to where you want to go and hopefully
won't have any more boot loops. I know this is a long process -- and once
in a while it doesn't work -- but I've done it with folks a pile of times and I
think it is the best procedure for your situation.
Good Luck,
Rev
2048/0 is an SD repartition. Think of it as a troubleshooting task just before having to resort to nvflash. It will wipe both /sdcard and /data, so keep that in mind.
Also, btw, if you have TNT Lite 4.3.0+, you can toggle back and forth between standard and cwm - it's called the "3588 Recovery Pack". Read my first post for details.
Ok, thanks for the help. I got to Stock ROM now.
Before I jump into reinstalling 4.4, let me ask this:
do I just copy the 4.4 into the GTab? and boot? or is there something I need to do before that?
4.4 install is just like the 4.3 install - just read my first post for details.
Thank you all for your help. I am up and running on TNTLite4.4. Love it so far..
I have a rooted TMo Vibrant running 2.1. I want to install a custom ROM and have the paid version of ROM mgr installed. I have downloaded the new ROM and I also have a (separate) zip of a different ROM on the SD card. The beginning steps of the installation go smoothly. But when I get to the point where ROM mgr says "Do you want to go into recovery mode to continue installation?" and I Select YES, the phone reboots into NORMAL mode and the installation ends. Same thing happens if I try to install manually from the SD card. I scroll down and select "install zip ...". Then the next screen that pops up has "reboot", " delete data", "reinstall packages", etc . I have tried all those options. But ultimately I end up back at the point where the only option I haven't chosen is "reboot system now". When I select reboot, the phone reboots in normal mode again. What am I doing wrong?
Not sure if this is your problem, but sounds like you need clockwork mod recovery update.zip on your phone.
Here is the trick though, when you get into normal recovery, sometimes you have to apply the cwm recovery update.zip TWICE to get into cwm recovery.
Boot up phone into stock recovery
apply the cwm recovery update.zip
phone reboots into stock recovery again
apply the cwm recovery update.zip again.
Hope that helps.
I would suggest doing this.
First and foremost make a nandroid backup, you can use cwm to do this. place a copy of the backup on your computer.
Backup your /efs folder which contains your nv_data.bin and imei information. You loose this you are f*cked.
Get the cwm recovery update.zip and put it on your internal sd root. If you have multiple update.zip files, just delete them all, just make sure the cwm recovery update.zip is there.
Also place the zip file of the rom onto your internal sd root also.
Disable voodoo lagfix if you have that installed.
Odin back to stock jfd 2.1. When finished next..
Apply cwm recovery update, apply TWICE to get into cwm recovery.
Then you can go into cwm recovery and select the zip of the rom you want to flash.
Follow all install directions of the ROM developer, they may want you to be on 2.2 first, which would mean odin to stock jfd 2.1, flash stock 2.2, then install whatever rom you are trying to.
That is how I do it.
I have a question about Clockwork recovery and this phone. Above you say that if any .zips are on internal sd to delete them and leave CWR on there only. I have this. Then if we want to go into the CWR we have to apply the update.zip twice. I do this also. Why can't we just replace the stock recovery with the Clockwork one and bypass the having to reinstall the packages twice. Maybe an sh init_hijack or something like that. I have been trying to find where the stock recovery "lives" to no avail. If you know where it is, then I can work on this and post the results.
Seems reasonable that if we replace the stock files with the CWR files and hijack the rocvery at boot it should work to boot right into CWR directly.
Woodrube said:
I have a question about Clockwork recovery and this phone. Above you say that if any .zips are on internal sd to delete them and leave CWR on there only. I have this. Then if we want to go into the CWR we have to apply the update.zip twice. I do this also. Why can't we just replace the stock recovery with the Clockwork one and bypass the having to reinstall the packages twice. Maybe an sh init_hijack or something like that. I have been trying to find where the stock recovery "lives" to no avail. If you know where it is, then I can work on this and post the results.
Seems reasonable that if we replace the stock files with the CWR files and hijack the rocvery at boot it should work to boot right into CWR directly.
Click to expand...
Click to collapse
Well with MiUi and CM it goes directly into clockwork mod recovery. I guess that's the stock recovery on MiUi and CM.
For me, only on 2.1 and 2.2 roms did I have to apply cwm recovery.zip twice.
SamsungVibrant said:
Well with MiUi and CM it goes directly into clockwork mod recovery. I guess that's the stock recovery on MiUi and CM.
For me, only on 2.1 and 2.2 roms did I have to apply cwm recovery.zip twice.
Click to expand...
Click to collapse
I have not used either for this phone but have with other phones and I think that it is b/c they reworked the services and framework.jars into an expanded power menu. I will see it that hack works on this one, so it will be easier on 2.1 and 2.2 for "relative" noobs. I have done it once for another phone and then my computer crashed (not issue related). I'll let you know what I find out this weekend b/c it'll take some time to get the pathways correct.
I appreciate you quick replies and have taken the first part of the advice and tried to backup everything (Which I thought I did using CWM). Just to be safe I have now installed Root Explorer and will back up everything this evening. Can't do more right now. Need to get back to work. Wayne
That did it. I now have my new ROM installed and a back-up of my efs file (which I mistakenly thought was included in my Nandroid back-up). BTW my nandroid, back-up produced by CWM doesn't include a boot image (or at least there is no image called "boot"). I thought there should be a boot image. In any case, I'm finally over the problem I've been trying for days to overcome. Thanks sooooo much. Wayne
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Fulhair said:
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Click to expand...
Click to collapse
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a wall and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
2girlzdad said:
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a well and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
Click to expand...
Click to collapse
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Fulhair said:
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Click to expand...
Click to collapse
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
aicjofs said:
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
Click to expand...
Click to collapse
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Fulhair said:
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Click to expand...
Click to collapse
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
aicjofs said:
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
Click to expand...
Click to collapse
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Fulhair said:
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Click to expand...
Click to collapse
Okay, I abandoned the addon.zip and went back to 2.1.27 rom and OAT over to get to the last update which failed.
Then installed the OAT2.zip via TWRP and bingo! Now working on Jelly Bean with Google Play - okay it's now the US version but it works
I would caution that the zip install had to be installed on the internal SD not the external one.
But otherwise a BIG thank you to all for building the tools to let me do the update and for your support.
Cheers:highfive: