Hi all,
Thanks in advance for your help.
I've bricked--like totally bricked--my Nabi 2. On startup, it goes to the Nabi logo, flashes black for a moment and returns to the logo, and is unresponsive. I've tried starting up holding vol+, but nothing happens; no bootloader gets loaded.
How can I restore my device? I have installed nabilabs on my PC, but the Nabi device isn't recognized. I have installed both 32/64 bit drivers. I've also installed pdanet.
Thanks for your responses.
DB
dbbergen said:
Hi all,
Thanks in advance for your help.
I've bricked--like totally bricked--my Nabi 2. On startup, it goes to the Nabi logo, flashes black for a moment and returns to the logo, and is unresponsive. I've tried starting up holding vol+, but nothing happens; no bootloader gets loaded.
How can I restore my device? I have installed nabilabs on my PC, but the Nabi device isn't recognized. I have installed both 32/64 bit drivers. I've also installed pdanet.
Thanks for your responses.
DB
Click to expand...
Click to collapse
I have a similar situation. Major difference is that TWRP (v2.8.4.0) is installed and running, but there's no OS on it otherwise. I have tried various downloads (such as "246stock.zip", and TWRP says there was an error installing on ALL zip files I have tried. It can't be a bad download, since I have re-downloaded the files,. on different machines, and I get the same error each time. NabiLab and NabiLabGUI don't seem to work if there is not already a working OS on the tablet.
Seems like what I need is something like the microSD-based flash/install I used for my Nook Tablet (acclaim) to put CM11 on it. Is there, in fact, a way to outright flash a .IMG file of some sort onto this? Or have I already ruined this already worthless P.o.S.? At this point I'd be just as happy to run something like CyanogenMod on it, and forget the disaster that is the Nabi2 interface and bloatware (then hunt down some other utility for time and access controls).
Images tried, all of which gave me "Error flashing zip"
1937stock.zip
205stock.zip
2127stock.zip
246stock.zip
jelabarre59 said:
I have a similar situation. Major difference is that TWRP (v2.8.4.0) is installed and running, but there's no OS on it otherwise. I have tried various downloads (such as "246stock.zip", and TWRP says there was an error installing on ALL zip files I have tried. It can't be a bad download, since I have re-downloaded the files,. on different machines, and I get the same error each time. NabiLab and NabiLabGUI don't seem to work if there is not already a working OS on the tablet.
Seems like what I need is something like the microSD-based flash/install I used for my Nook Tablet (acclaim) to put CM11 on it. Is there, in fact, a way to outright flash a .IMG file of some sort onto this? Or have I already ruined this already worthless P.o.S.? At this point I'd be just as happy to run something like CyanogenMod on it, and forget the disaster that is the Nabi2 interface and bloatware (then hunt down some other utility for time and access controls).
Images tried, all of which gave me "Error flashing zip"
1937stock.zip
205stock.zip
2127stock.zip
246stock.zip
Click to expand...
Click to collapse
Those zips aren't flashable. You have to extract and restore them.
Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 2.4.6 ROM and bootloader.
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 246stock.zip files you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.4.6 ROM.
- Download this http://forum.xda-developers.com/showpost.php?p=50349692&postcount=89
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
- Reboot
Alternatively you can "restore" the new kitkat for Nabi. Just replace the instructions for 2.4.6 files above with these below.
3.0.13 stock zip
https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
3.0.13 bootloader
https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing
Not sure how bad your situation was but you may have to do a factory reset in TWRP as well. Try that if it doesn't boot after successfully doing the above.
aicjofs said:
Those zips aren't flashable. You have to extract and restore them.
Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 2.4.6 ROM and bootloader.
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 246stock.zip files you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.4.6 ROM.
- Download this http://forum.xda-developers.com/showpost.php?p=50349692&postcount=89
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
- Reboot
Alternatively you can "restore" the new kitkat for Nabi. Just replace the instructions for 2.4.6 files above with these below.
3.0.13 stock zip
https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
3.0.13 bootloader
https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing
Not sure how bad your situation was but you may have to do a factory reset in TWRP as well. Try that if it doesn't boot after successfully doing the above.
Click to expand...
Click to collapse
Just an update, I managed to get a warranty replacement, because it decided it didn't want to charge anymore. Got one of the newer units as a replacement, which has the much better power connector, and am running it as-is for the time being (their updated firmware isn't *as* bad, will have to see what happens with the Mattel ownership).
I am having the same type of issue. I currently have TWRP v2.3.3.0 (Nabi 1.9.3.7) installed, but it shows no OS installed. I attempted to restore to the 30.0.13 stock at got the following message:
E:Unable to wipe '/system'.
and got the Failed on the screen. I also attempted to use the wipe function on the system and got E: Unable to mount for /data, /data, /system, /cache, /data, /addon.
Any help would be greatly appreciated.
biglerad said:
I am having the same type of issue. I currently have TWRP v2.3.3.0 (Nabi 1.9.3.7) installed, but it shows no OS installed. I attempted to restore to the 30.0.13 stock at got the following message:
E:Unable to wipe '/system'.
and got the Failed on the screen. I also attempted to use the wipe function on the system and got E: Unable to mount for /data, /data, /system, /cache, /data, /addon.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You don't have the right TWRP version probably. That's the ICS version. Try the JB or KK version. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
OK, I had managed to repair the Nabi2s which was bricked before (the trick to "backup" the core files of the specific system, then extract files from 2_0_141107stock.zip), and restore. But for some reason it lost WiFi completely, so I figured I'd try re-flashing again. Now I have no TWRP, and cannot even make the device visible to boot to TWRP. Is it time to take out the sledgehammer, then send the pieces back to the founders at what used to be Fuhu?
I have gone round ans round on the site, tries to find which threads I had followed before, and I seriously think I NEVER want to buy another device where I can't wipe the HDD with a dd command, and boot an installer with a USB or DVD ever again.
jelabarre59 said:
OK, I had managed to repair the Nabi2s which was bricked before (the trick to "backup" the core files of the specific system, then extract files from 2_0_141107stock.zip), and restore. But for some reason it lost WiFi completely, so I figured I'd try re-flashing again. Now I have no TWRP, and cannot even make the device visible to boot to TWRP. Is it time to take out the sledgehammer, then send the pieces back to the founders at what used to be Fuhu?
I have gone round ans round on the site, tries to find which threads I had followed before, and I seriously think I NEVER want to buy another device where I can't wipe the HDD with a dd command, and boot an installer with a USB or DVD ever again.
Click to expand...
Click to collapse
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Did that tablet ever receive an update past KitKat?
No Wifi is usually one of two things.
1) Kernel(boot partition) doesn't match kernel modules(system partition). Fix: Restore both boot and system in TWRP.
2) The wifi conf is bad. Fix: Factory reset/wipe data partition Note: loses all personal data.
3) I suppose if there was an update past kitkat, maybe the bootloader or the misc partition got an update. Don't go down that route yet.
Here is the general flow for restoring things, should have everythin you need if you can get fastboot to come up:
https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
My original(and only) notes on Nabi2s
https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
https://forum.xda-developers.com/showpost.php?p=58623597&postcount=2507
aicjofs said:
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Click to expand...
Click to collapse
There's the problem. At this point the tablet only gets as far as the initial Nabi logo. Trying the "<Vol+><power>" option gives me the "Booting Android recovery..." followed shortl by the dead android. That's all the tablet will do.
Is there no way to make a microSD boot? That was what I would do with my Nook Tablet ("acclaim"). Seriously, whomever thought Android should be automatically locked out from the very people who bought/paid for/own the devices should be smacked by each and every Android user out there.
Thanks very much for the info. Took me 2 days to find this.
aicjofs said:
If you can get to the bootloader screen you should be able to bring up fastboot and get TWRP back on tablet(or just boot to TWRP temporarily)
Here is the general flow for restoring things, should have everythin you need if you can get fastboot to come up:
https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
My original(and only) notes on Nabi2s
https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
https://forum.xda-developers.com/showpost.php?p=58623597&postcount=2507
Click to expand...
Click to collapse
All these instructions presume I can get to a "recovery/bootloader" screen, which this tablet will NOT do. It gets the initial Nabi logo, and that's as far as it will ever go. You could leave it there for 5 hours and that's all it will do (happened to do that once letting it charge, and the Nabi likes to boot as soon as it gets power).
I would try your "nvflash", but it's a MSWin executable, and I'm running Linux.
I'm just wondering; if I had the appropriate image file, is there a way to do a raw dump/write to the USB port, forcing the data to a particular device? If I tail /var/log/syslog, then plug in the Nabi2s, I get these messages in the syslog (and nothing else from the tablet after that):
Code:
kernel: [ 5973.824134] usb 2-1: new high-speed USB device number 4 using ehci-pci
kernel: [ 5973.986609] ehci-pci 0000:00:1d.7: port 1 reset error -110
kernel: [ 5975.192071] usb 2-1: new high-speed USB device number 5 using ehci-pci
kernel: [ 5975.346686] ehci-pci 0000:00:1d.7: port 1 reset error -110
In theory there should be a raw device there somewhere (lsusb doesn't see it)
jelabarre59 said:
All these instructions presume I can get to a "recovery/bootloader" screen, which this tablet will NOT do. It gets the initial Nabi logo, and that's as far as it will ever go. You could leave it there for 5 hours and that's all it will do (happened to do that once letting it charge, and the Nabi likes to boot as soon as it gets power).
I would try your "nvflash", but it's a MSWin executable, and I'm running Linux.
I'm just wondering; if I had the appropriate image file, is there a way to do a raw dump/write to the USB port, forcing the data to a particular device? If I tail /var/log/syslog, then plug in the Nabi2s, I get these messages in the syslog (and nothing else from the tablet after that):
Code:
kernel: [ 5973.824134] usb 2-1: new high-speed USB device number 4 using ehci-pci
kernel: [ 5973.986609] ehci-pci 0000:00:1d.7: port 1 reset error -110
kernel: [ 5975.192071] usb 2-1: new high-speed USB device number 5 using ehci-pci
kernel: [ 5975.346686] ehci-pci 0000:00:1d.7: port 1 reset error -110
In theory there should be a raw device there somewhere (lsusb doesn't see it)
Click to expand...
Click to collapse
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2) See this: https://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701 If you can short the solder joints, I would assume the 2S has them too. That will start the 3pserver on the tegra itself, and bring up a USB interface. I don't think you need the APX driver for linux but you might check. There are plenty of linux nvflash binaries out there. Here is one that should work for tegra3 for sure: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ or search github and compile your own. That would allow what you want, however... I'm not sure where the bootloader partition is. In the notes I linked above I listed a cat /proc/partitions which I will markup below
179 0 15269888 mmcblk0
179 1 8192 mmcblk0p1 <---likely recovery partition but maybe boot
179 2 8192 mmcblk0p2 <---likely boot partition but maybe recovery
179 3 2048 mmcblk0p3 <---if like a Nabi 2 the EKS with crypto key
179 4 2048 mmcblk0p4 <---if like a Nabi 2 the linux backup partition table.
179 5 2097152 mmcblk0p5 <--- preload aka addon partition with all the Nabi apps and media
179 6 1572864 mmcblk0p6 <--- system partition
179 7 2097152 mmcblk0p7 <--- cache partition
179 8 2048 mmcblk0p8 <--- not sure
179 9 32768 mmcblk0p9 <---if like a Nabi 2 the USP or staging partition for placing blob files for flashing
179 10 2048 mmcblk0p10 <---Not sure
179 11 9435136 mmcblk0p11 <--- data partition
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
The problem here is the Nabi 2 had a 6MB partition that was clearly the bootloader. A 2MB that was the Nvidia/Tegra partition table(different structure then a linux PT), and a 4MB partition for the device parameters. Those are "nvidia partitions" and don't show up in the linux partition table. For the Nabi 2 the bootloader was nvidia partition 4
I would go about it like this:
Tear open the Nabi and see if it has the pins to force tegra to 3pserver
Get nvflash binary or compile one
Get the bootloader.bin from here(note the name is bootloader2S.bin and the commands below I have bootloader.bin so rename it: https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
Force the tablet to 3pserver with the pins
Check to see if it's there with lusb
Use the commands(if you are a linux guy I assume you know you may need sudo, or ./nvflash, etc, etc)
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
^^^examine the partitiontable.txt and see if it clarifies where the bootloader might be. They like to call it EBT in tegra. I would tell you how to flash the botloader but I just don't know where it is. The bootloader tries to load the boot.img from the boot partition, and has some sort of watchdog where if it doesn't load boot.img in such and such amount of time, it will try and load recovery.img. If that doesn't happen it just sits there staring at you. You could try and flash boot and recovery and maybe that brings you back to something more familiar. Examine the partition table text and find out which is boot and recovery. Boot is usually LNX, and recovery SOS.
If you are still in nvflash mode after all of this and havent shut down the tablet use commands below. If you have to restart you need have a first command of "nvflash --bl bootloader.bin <some command>" then all subsequent commands just need "nvflash --resume <some command>"
If it's exactly like a Nabi 2 then this would be the flow. So if your partitiontable.txt shows EBT as 4, SOS as 7, and LNX as 8
nvflash --resume --rawdeviceread 0 3072 nabibricksafe.img
nvflash --resume --read 4 04_EBT_raw.img
nvflash --resume --read 7 07_SOS_raw.img
nvflash --resume --read 8 08_LNX_raw.img
<optional>
nvflash --resume --download 4 bootloader.bin
nvflash --resume --download 7 twrp.img
nvflash --resume --download 8 twrp.img
nvflash --resume --go
^^^I have no idea about the 3072. That gets the first 3 "nvidia partitions" on a Nabi2 but that may not be long enough for a 2S, you can make it a larger read to be on the safe side(maybe 6000). You are basically reading the critical part of the tablet, backing up the current partition 4, 7, and 8, before reloading 7,8 with TWRP. Then tablet should restart. Remember if you have to restart the tablet the "resume" won't work, you will need to issue something with -bl bootloader.bin after a fresh boot as the first command of the session. You could add
nvflash --resume --download 4 bootloader.bin
in the above if the partition table confirms its the bootloader partition(EBT). In fact that may actually be the ONLY command you need to bring back the bootloader text, I'm just being cautious since it's not my tablet and taking a conservative approach.
That will put TWRP in both boot and recovery partitions so that hopefully you can boot TWRP somehow. If we can, then we can go back and fix things in TWRP. This may be all you need.
Side note: I never used nvflash on a 2S so who even knows if all this typing means anything, and maybe the emmc is just bad and none of this matters. I'm just try to give you all the major things I can think of to save you time. Good luck!
jelabarre59 said:
Just an update, I managed to get a warranty replacement, because it decided it didn't want to charge anymore. Got one of the newer units as a replacement, which has the much better power connector, and am running it as-is for the time being (their updated firmware isn't *as* bad, will have to see what happens with the Mattel ownership).
Click to expand...
Click to collapse
Thank you very much you saved my day
---------- Post added at 08:10 AM ---------- Previous post was at 08:08 AM ----------
aicjofs said:
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2) See this: https://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701 If you can short the solder joints, I would assume the 2S has them too. That will start the 3pserver on the tegra itself, and bring up a USB interface. I don't think you need the APX driver for linux but you might check. There are plenty of linux nvflash binaries out there. Here is one that should work for tegra3 for sure: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ or search github and compile your own. That would allow what you want, however... I'm not sure where the bootloader partition is. In the notes I linked above I listed a cat /proc/partitions which I will markup below
179 0 15269888 mmcblk0
179 1 8192 mmcblk0p1 <---likely recovery partition but maybe boot
179 2 8192 mmcblk0p2 <---likely boot partition but maybe recovery
179 3 2048 mmcblk0p3 <---if like a Nabi 2 the EKS with crypto key
179 4 2048 mmcblk0p4 <---if like a Nabi 2 the linux backup partition table.
179 5 2097152 mmcblk0p5 <--- preload aka addon partition with all the Nabi apps and media
179 6 1572864 mmcblk0p6 <--- system partition
179 7 2097152 mmcblk0p7 <--- cache partition
179 8 2048 mmcblk0p8 <--- not sure
179 9 32768 mmcblk0p9 <---if like a Nabi 2 the USP or staging partition for placing blob files for flashing
179 10 2048 mmcblk0p10 <---Not sure
179 11 9435136 mmcblk0p11 <--- data partition
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
The problem here is the Nabi 2 had a 6MB partition that was clearly the bootloader. A 2MB that was the Nvidia/Tegra partition table(different structure then a linux PT), and a 4MB partition for the device parameters. Those are "nvidia partitions" and don't show up in the linux partition table. For the Nabi 2 the bootloader was nvidia partition 4
I would go about it like this:
Tear open the Nabi and see if it has the pins to force tegra to 3pserver
Get nvflash binary or compile one
Get the bootloader.bin from here(note the name is bootloader2S.bin and the commands below I have bootloader.bin so rename it: https://forum.xda-developers.com/showpost.php?p=58603231&postcount=2504
Force the tablet to 3pserver with the pins
Check to see if it's there with lusb
Use the commands(if you are a linux guy I assume you know you may need sudo, or ./nvflash, etc, etc)
nvflash --bl bootloader.bin --getpartitiontable partitiontable.txt
^^^examine the partitiontable.txt and see if it clarifies where the bootloader might be. They like to call it EBT in tegra. I would tell you how to flash the botloader but I just don't know where it is. The bootloader tries to load the boot.img from the boot partition, and has some sort of watchdog where if it doesn't load boot.img in such and such amount of time, it will try and load recovery.img. If that doesn't happen it just sits there staring at you. You could try and flash boot and recovery and maybe that brings you back to something more familiar. Examine the partition table text and find out which is boot and recovery. Boot is usually LNX, and recovery SOS.
If you are still in nvflash mode after all of this and havent shut down the tablet use commands below. If you have to restart you need have a first command of "nvflash --bl bootloader.bin <some command>" then all subsequent commands just need "nvflash --resume <some command>"
If it's exactly like a Nabi 2 then this would be the flow. So if your partitiontable.txt shows EBT as 4, SOS as 7, and LNX as 8
nvflash --resume --rawdeviceread 0 3072 nabibricksafe.img
nvflash --resume --read 4 04_EBT_raw.img
nvflash --resume --read 7 07_SOS_raw.img
nvflash --resume --read 8 08_LNX_raw.img
<optional>
nvflash --resume --download 4 bootloader.bin
nvflash --resume --download 7 twrp.img
nvflash --resume --download 8 twrp.img
nvflash --resume --go
^^^I have no idea about the 3072. That gets the first 3 "nvidia partitions" on a Nabi2 but that may not be long enough for a 2S, you can make it a larger read to be on the safe side(maybe 6000). You are basically reading the critical part of the tablet, backing up the current partition 4, 7, and 8, before reloading 7,8 with TWRP. Then tablet should restart. Remember if you have to restart the tablet the "resume" won't work, you will need to issue something with -bl bootloader.bin after a fresh boot as the first command of the session. You could add
nvflash --resume --download 4 bootloader.bin
in the above if the partition table confirms its the bootloader partition(EBT). In fact that may actually be the ONLY command you need to bring back the bootloader text, I'm just being cautious since it's not my tablet and taking a conservative approach.
That will put TWRP in both boot and recovery partitions so that hopefully you can boot TWRP somehow. If we can, then we can go back and fix things in TWRP. This may be all you need.
Side note: I never used nvflash on a 2S so who even knows if all this typing means anything, and maybe the emmc is just bad and none of this matters. I'm just try to give you all the major things I can think of to save you time. Good luck!
Click to expand...
Click to collapse
Thank you guys keep up the good work
Hello i have a serious problem with nabi jr tab of my friend's , the model no. is SNBJR-MT5C , my friend was using busybox and adb , when he tried to add .bak file for fuhu in system/apps ,because he wanted to get rid of the password each time device starts, this resulted in a bootloop , because there was no twrp installed , as this device was running kitkat , he tried using a backup from here somewhere in xda but without scatter and files.md5 , so he manually make files.md5 and generated scatter from mtk droid tools from firmware.info , but when he tried flash from sp flash tool , it did not accept that scatter, because pre-loader and mbr has start address 0 , because scatter version was wrong, mtk droid tools generated MT6582_sctter.txt, but it was MT8127 SoC , MT6582 - v111, MT8127 - v112 , so he got v112 from somewhere , and then retried and it got DA(Download Agent) error , so he made a mistake and changed DA and it bricked it completely , now its black screen and it wont turn on , even wont go in fastboot/recovery mode by holding power button and volume + or - buttons , also not showing anything in pc device manager , its totally dead , does anyone had the same experience ? or can anyone guide me about anything? Thanks
aicjofs said:
Keep in mind I had the Nabi 2S for all of a day, so what I am about to say only applies to the Nabi 2 not 2S. If you see no menu then there is a non functioning bootloader, or at least it doesn't load all the way. It won't front any USB port, and you won't see it with lusb. There is a way to manually start "forced recovery" though(or there was on the Nabi2)
Click to expand...
Click to collapse
I managed to get all the pieces of my daughter's Nabi 2S in one place (well, except for the bumper, I had multiples so I must have one still available. But did find the right charger cable). Since she has a different tablet to use for now (I was given 4 XO tablets; one, maybe two actually work) I could send this to a developer who wants to dabble with the hardware. Mind you, it's bricked, so it powers up but can't get to recovery menus, etc. The Nabi 2S doesn't appear to have the solder joints to do a forced recovery, but there is something that looks like it might be a button to do the same thing.
It's April 2018, if there's a developer who wants to try out other experiments on a Nabi2s that's otherwise bricked, you can still contact me. The Nabi is sitting in a box in the closet, it's not doing anything, and my daughter is now using an OLPC OX tablet instead (hey, got 4 of them for free, 2 actually power up).
(yeah, want to re-flash that second one someday as well, just to get it to a clean, stripped-down base to start from).
Hello bro I have a different situation here I have a nabi 2 nv7a I installed twrp on it and deleted the previous ROM to install new one but unfortunately when I try to install any ROM it shows error e\ unable to mount storage then I figured that the solution for it is to change the type of internal storage but the twrp I installed doesn't have any option of changing the type I went to wipe internal storage there was only one option that swipes and when I wipes then it also shows e/unable to mount and there is no option of changing type and I'm unable to change my twrp because I have no is plssss someone help
Related
Long missive below, so fair warning – I have put in as much detail as I can remember to help out troubleshooting and I have read every thread on APX mode I can find both on this board and others.
I’ve gone and done it now, my GTab formerly running VEGAn-Tab 5.1.1 is stuck booting only to APX mode. So what did I do, and what have I tried?
* Immediately after purchase, I loaded ClockworkMod .8, then VEGAn 5.1.1. Absolutely no issues.
* Started looking into the various kernels, decided to try Clemsyn’s since it seemed to support VPN’s without any hassle (I don’t have any Linux experience, so to me moving module files around is a hassle). It worked great, my VPN to home worked. I successfully upgraded several times to his Version5 without any problems.
* Loaded a ton of apps, the vast majority worked just fine. I loaded App2SD, and moved most of the larger apps to the SD card. I also I think moved LauncherPro to the SD Card, which caused minor problems later.
* Inserted a 512MB USB stick. It worked. However when the GTab rebooted with it in, I received a ton of FC’s for apps loaded to the SD Card that load on startup, including LauncherPro. I can’t remember what exactly I did to fix that, I remember somehow getting the regular launcher to load, then uninstalling LauncherPro and a ton of other apps. Reloaded those but didn’t move them to the SD Card. Everything back to normal.
* Decided I wanted a boot screen other than the birds, so I made one following the instructions in that thread. Like everyone else, my graphic failed on partition 6 but worked on partition 7. No problems after that.
* Yesterday I inserted a 4GB USB stick. It didn’t work. Rather stupidly based on my earlier experience with the 512, but confident I could fix anything that broke, I rebooted the machine with the stick still inserted. As expected, a ton of FC’s, this time though the apps were not loaded on the SD Card. Not good. I also could not get into the regular launcher to uninstall things. No problem, I was planning to switch to the Gingerbread edition of VEGAn anyway. I force rebooted (held the power button down about 10 seconds).
* The GTab came back to life in APX mode. Not good, but not fatal either. I downloaded NVFlash and the Win7 x64 drivers, I had no problem connecting the GTab and my laptop. Now feeling a little better, but still annoyed.
* Read the “[STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions)” thread on recovery backward and forwards twice to make sure I understood what I was doing. Came to the conclusion that all I needed to do at this point is unzip the two files (one with NVFlash, the other with the stock images) into one subdirectory, and run the .bat file. I did that, watched NVFlash create and format about 10 subdirectories, then load the images to them. NVFlash reported success, and my GTab rebooted into stock TnT. The usual FC’s on bootup, after chasing those away, I enabled WIfi, and let it download the latest firmware – 3588. It asked to install, I said yes. It asked to reboot I said yes. It rebooted into APX mode.
* Now I am really annoyed, this isn’t supposed to happen, though I did find I think 2 guys that are stuck in APX mode, looks like one returned his, the other leaves it on a dock and does not touch it. I don’t have the dock, I don’t like the stock TnT, and since I ordered the custom carbon fiber backing sticker and the “android eating the apple” sticker and they look great on the back I am not in favor of returning it at this time.
* So I spent another couple of hours on the web reading. I read the “[UTILITY] G-Tablet Format” thread on formatting the device, I downloaded that zip file, it looks much like the regular NVFlash recovery process. Actually exactly the same, but it looks like the .img files are different and the NVFlash file is different. It ran, and said it was successful. The GTab rebooted, and said I think “Magic number mismatch”. I rebooted again, expecting to see a magic number error, which would give me the greenlight to go into NVFlash Recovery mode, but failure - right back into APX mode. I wanted to do try the format and then restore to stock process back to back, but it seems that the machine has to reboot after any NVFlash action. Right back to APX mode, NVFlash to stock worked the same as before, loaded then APX mode on reboot.
* I tried using NVFlash to stock but adding CWM .8 on partition 9. No difference, right back to APX mode, no chance to get CWM to load. I read that using a single command to push only CWM to partition 9, then while holding down the plus sign pushing the image. That actually worked, it rebooted into CWM. Everything seemed to work as expected, I could mount the system and data directories, format them, reformat the SDCard, change it’s size to 2048/0. I tried wiping the DELVIK cache, it returned an error saying a file existed but then said it was successful. I don’t remember what it said when I did that the very first time when loading VEGAn 5.1.1, so that might be the expected behavior. Either way, I rebooted and right back to APX mode.
* I read somewhere that flashing CWM to partition 10 worked. I swapped around .img files so that it was pushed to 10 instead of 9. Upon reboot, it went straight to CWM. I had the same experience as before, upon reboot after that it went to APX mode instead of back to CWM.
* I popped the back off and tried booting while shorting out the 4 pins, no change, though I could get to APX mode anyway so I wasn’t expecting a miracle. The button next to those 4 pins didn’t make a difference either.
* I tried booting while holding down the vol- button, and again with both the vol- and + being held down. Neither worked.
* I downloaded the SDK to try ADB mode. It made me download the Java DK, no problem. The SDK does not see the JDK, but I didn’t reboot the laptop, since I was still in #Tegratab (thanks BadFrog for your help). I will do that when I get home and get ADB to work, but I don’t know what to do when I get that done. ADB works, I needed to load the 32 bit version of the JDK, even though I have an x64 machine. ADB works, so I am happy. Now to see if that helps the overall problem.
* I did after booting into CWM load VEGAn Gingerbread and Clemsyn’s GB Beta 2 kernel. After next rebooting into APX mode, I pushed CWM to partition 9, and it tried booting into GB but never got past the animated GB screen. I will try that again later today with 5.1.1 and the Ver5 kernel and see if it makes any difference. I can probably live with it booting into APX mode if I can push CWM to Par9 and get it to boot back into 5.1.1 when needed. z4root didn't help either.
* So in conclusion, I am stuck in APX mode no matter what I tried. I think it is partition related, because of the problems after inserting the USB sticks, and since it will reboot after NVFlash into whatever seems to be in partition 10. In the DOS world that is easy to fix, especially when doing a system wipe and rebuild. I tried using NVFlash to say partition 10 is the boot partition, that didn’t work, NVFlash actually didn’t seem to do anything and I had to do a CTRL-C to end it.
Any suggestions, other than peel my stickers off and mail it back to Amazon.com?
* 1239CET 25 Mar 11 - Edited, I tried z4root, it didn't help my problem.
* 1345CET 25 Mar 11 - ADB now working. Win7x64 Ult.
* 1725CET 26 Mar 11 - Unit RMA'd to Amazon - I was on day 30 so off it went, the replacement just shipped so they will cross in the mail.
Bump for more visibility
Very nice detailed post - you certainly did your homework. With that in mind I don't think I have much to add.
Yes, I remember one user who would reboot into APX mode all the time. I think there was one other person who would reboot into Fastboot all the time. And I don't think those problems were ever resolved.
Question: What is the model # on your device? I want to make sure it's it's not a 320, as at least one user on this board got a 320 and not a 300 (he got it from SEARS online). A 320 is a 1GB "v2" Malata device and those nvflash files might not work with them.
Here's another suggestion before you give up. Since nvflash seems to be the problem, maybe try another nvflash such as the Adam. The Adam nvflash DOES work on the GTAB. Maybe it will "jump-start" something for you.
Adam nvflash (Windows): http://api.notionink.com/fix/windows/LCD.zip
Adam nvflash (Linux): http://api.notionink.com/fix/linux/LCD.zip
Normally I wouldn't suggest this, but you are ready to return so there's not much to lose. You can always re-flash back to 1105 bekit, before you return it. These files will alter the booloader to that of an Adam, but again you can undo with the GTAB nvflash if needed.
Yep, mine is stuck in APX mode and the only way to "boot" it is to nvflash it.
I've set it up with VEGAn 5.1.1 and another kernel and my wife uses it. It sits on the dock (charging) when she's not using it and is never turned off/rebooted. If it does go off, I just nvflash it to boot (using the --format_partition 2 command) and once it boots the bootloader and formats partition 2 it proceeds to run.
I gave up (and also since my wife is using it I can't test other methods to make it work) and will later probably get myself one of the newer tablets (Samsung or Motorola or Toshiba...who knows) and pass my fully functional Gtablet to my wife.
roebeet said:
Here's another suggestion before you give up. Since nvflash seems to be the problem, maybe try another nvflash such as the Adam. The Adam nvflash DOES work on the GTAB. Maybe it will "jump-start" something for you.
Adam nvflash (Windows): http://api.notionink.com/fix/windows/LCD.zip
Adam nvflash (Linux): http://api.notionink.com/fix/linux/LCD.zip
Normally I wouldn't suggest this, but you are ready to return so there's not much to lose. You can always re-flash back to 1105 bekit, before you return it. These files will alter the booloader to that of an Adam, but again you can undo with the GTAB nvflash if needed.
Click to expand...
Click to collapse
Good sugestion, but unfortunately the nvflash in the adam recovery rom is the same as the one in the FORMAT images (151K), it seem to be better under windows since it list partition in text, the other when asked for a list of partition output a binary files.
As for the bekit1105 I usually do (when trying other rom or tnt5) NVFLASH FORMAT IMG, THEN NVFLASH the 1105 with the partition #9 replacing the clockwork .8 alway worked for me.
If it was me I would try to re-partition under windows the flash section, I am not sure how to do it with adb but if possible I would do it there.
I also notived the unit seem to be making sure the flash is partitioned in 2 section (2GB/16GB) inside system/etc/inandop.sh maybe that would be a couple of command to run by hand in adb, I know partition of flash can be tricky at time and it may be the reason the unit is falling to apx..
Would be a good idea to extract the partition list to confirm all their size a legit too.. either way don't give up I am quite sure someone will figure out a way of those half bricked unit...
michaeljwestii said:
*
Decided I wanted a boot screen other than the birds, so I made one following the instructions in that thread. Like everyone else, my graphic failed on partition 6 but worked on partition 7. No problems after that.
Any suggestions, other than peel my stickers off and mail it back to Amazon.com?
* 1239CET 25 Mar 11 - Edited, I tried z4root, it didn't help my problem.
* 1345CET 25 Mar 11 - ADB now working. Win7x64 Ult.
Click to expand...
Click to collapse
I really think something is wrong there, the correct partition for the bmp is definitely #6 in my tablet,
however in the other recovery (nvflash_gtablet_46_2010112600.zip) in roebeet's dropbox the #6 and #7 are inverted... 16MB vs 4MB but their .cfg is correct
So if you flashed the bird on 7 it's a surprise for me that it worked...
also I am wondering did you change the size if the partition in the .cfg files prior to flashing ??? or did you simply swapped the files? I noticed a few post where people where changing the recovery partition without adjusting the size in the .cfg file...
I would really like to see the list of your partition...
sound like the geek way to ask a girl for a show
read this... http://forum.xda-developers.com/showthread.php?t=934023
your boot configuration table may be bad... so maybe another rom like roebeet suggested would help...
Actually it's bekit's dropbox.
Some of the newer gTAB's have partitions 6 and 7 reversed:
Code:
[partition]
name=BLO
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part6.img
[partition]
name=MSC
id=7
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=16777216
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=part7.img
My first gTAB (the one I currently own) was setup this way, but one dev unit I got in December had them reversed, and bekit had one that was reversed as well. I actually flashed the 1105 bekit image and it had worked for me, at the time.
I do not think the image can be the cause of this problem (as long as the size in the cfg is correct), however I think something is wrong in the early boot process in his case...
The guy in this toshiba forum are playing quite a lot with their partition with nvflash...
http://tosh-ac100.wetpaint.com/page/Repartition+Internal+Storage
Interestingly, reading my partition 11 on my tab end with an error...
Z:\>nvflash -r --read 11 part-11.img
Nvflash started
[resume mode]
receiving file: part-11.img, expected size: 209715200 bytes
/ 209584128/209715200 bytes receiveddata receive failure NvError 0x120000
command failure: read failed
like if the partition was not the correct size by a few bytes...
Roebeet...
I was looking at the ADAM recovery and I think it may explain why some tablet are boot looping or bricked...
the file name they use for the .bct files tell us something...
LCD\harmony_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct
They specify their FLASH (HY27UF084G2B) number in their boot config, this is probably due to the fact that they change their IC from time to time (flash are often on high allocation so manufacture often have more than one supplier) and those change seem to be important enough that they use it as their boot config... (bct probably need to match the memory... or even configure memory speed etc)
This mean that flashing with a BCT that is not specific to the type of memory installed may be bad... but there's no proof that viewsonic had unit with different memory, unless it's one of the difference between the 300 and 320 unit you where mentioning..
Interesting. One thing about the Adam and the VEGA that I always liked is that we have at least on vendor-based nvflash config from them. Even the Viewpad10s has one. But we never got an official one for the gTablet - bekit's version is fantastic and still the defacto standard, but it's not the vendor's.
I keep wondering if the latest holdout on their stock release is because they want to deploy an nvflash version. It's not in the realm of impossibility, given that the Viewpad10s already has one. And it would certainly be a good way to give users a backout in case the update.zip fails (Viewsonic, you reading this?). A vendor-based nvflash config would be a wonderful thing, if they offered it. Well, we can hope....
michael...
Did you try in nvflash to set the boot partition ?
--setboot N
sets the boot partition to partition N
roebeet said:
Interesting. One thing about the Adam and the VEGA that I always liked is that we have at least on vendor-based nvflash config from them. Even the Viewpad10s has one. But we never got an official one for the gTablet - bekit's version is fantastic and still the defacto standard, but it's not the vendor's.
I keep wondering if the latest holdout on their stock release is because they want to deploy an nvflash version. It's not in the realm of impossibility, given that the Viewpad10s already has one. And it would certainly be a good way to give users a backout in case the update.zip fails (Viewsonic, you reading this?). A vendor-based nvflash config would be a wonderful thing, if they offered it. Well, we can hope....
Click to expand...
Click to collapse
I think it would better and safer if people would do a capture of their unit rom instead of using a generic one as a backup.
Would be nice to see one from Viewsonic as well, I hope they hear you!
P00r said:
I think it would better and safer if people would do a capture of their unit rom instead of using a generic one as a backup.
Would be nice to see one from Viewsonic as well, I hope they hear you!
I tried to locate that viewpad recovery with no sucess, ca you point me in the right direction ? tnx
Click to expand...
Click to collapse
Well, it WAS here:
http://ap.viewsonic.com/in/downloads/
But now it seems to have been pulled. Weird. Maybe check back in a day or two. I already looked at their firmware and it's very similar to the Advent Vega 1.0.9 firmware (sister devices).
I have downloaded the VEGA image restore, they left inside the utility used to create the .BCT files
the help for this utility confirm the bct is linked to the flash chips
as well as to the image (not sure which...)
Usage: buildbct [options] Configfile ImageFilename ChipName
options:
-h, --help, -? Display this message.
-d, --debug Output debugging information.
Configfile File with configuration information
ImageFilename Output image Filename
ChipName Name of the chip, currently valid --ap15
This mean using a generic bct may be risky if viewsonic have more than 1 type of hardware tablet with the same name...
Makes a lot of sense, to me. I honestly think we've been very lucky so far (most of us). Bekit and I must have the same device as his backup has never failed me. And, as you can imagine, I have flashed my device a LOT.
We don't know the hardware differences - why are some of the newer devices shipped with switched partitions? Why is it that at least one XDA user got a 320, when they paid for a 300? And if those Woot devices really are new, who's to say that the hardware inside isn't slightly different. Maybe our mods won't work on them regardless of what we do.
The other problems are that 1) Viewsonic isn't telling us and 2) we aren't keeping any metrics on this. We had this issue with the Pandigital Novel, but it was only two boards - eventually we could find ways to distinguish between the two (we called them "v1" and "v2" boards. I even opened them up and could tell that way. But, so far, we don't know if this is the case with the GTablet.
This 320 series will be interesting to watch
I do not think the order of the partition should have any impact, looking at other device they are all organised diferently, only their descriptor and file system seem to matter (YAFFS for the user accesible section) but it does show they played with it
Thanks for the comments and help
Thanks everyone for the comments and help. I checked Amazon and since I was on day 30, I did an online RMA and sent it back, so I didn't try the Adam idea. I did confirm it is not a model 320 though.
P00r - I did try the Setboot N command, pointing it at partition 10, since when I put the CWM image there it booted to it. NVFlash hung and I CTRL-C'd it after about 3 minutes.
When I swapped partition 6 & 7, I did swap the config info also, so the partition size and file system were correct per the cfg file normally.
The bad GTab and new replacement will cross in the mail, hopefully Gojimi's GB is out of experimental and into Beta by then
The whole BCT is still a mystery (to me at least). I've posted about that, and if I recall, responded to official viewsonic suggesting they provide info on that plus partition table, etc. I have yet to find any info on what the BCT actually is, but have seen from posts on wetpaint that messing with it or changing it can bork your device.
That's one of the reasons I'm still stock. Don't want to get into a situation where nvflash is the only resort.
The other reason I haven't tried to flash using nvflash is the bad blocks I mentioned awhile ago, and not being able to nvflash/read all my partitions. Figured that if it can't read all partitions, it probably won't be able to write them either .
Just ordered a 2nd Gtab from the woot deal, so I'm curious if that'll show bad blocks in dmesg, and if I'll be able to read all partitions w nvfash w the new one...
Jim
When the new tablet comes in, I'll pull the partition list and post it. Is there any other info from a bone-stock machine anyone would think is useful?
michaeljwestii said:
When the new tablet comes in, I'll pull the partition list and post it. Is there any other info from a bone-stock machine anyone would think is useful?
Click to expand...
Click to collapse
Happy to hear you cane exchange it!
Can you try extracting all the partition, I got an error on my partition 11, and I think Jim is right about the bct also used to map bad block in the flash...
I am just curious to see if this error is there on a virgin unit!
I can send you a batch files for the command
Hi all,
i am hoping one of you can help me with my Gtab T2.
2 weeks ago my tablet was acting very strange, so i decided to install a new rom.
This went terribly wrong, and the tablet is completely bricked.
I cannot get passed the bird screen.
For my feeling i have tried everything, i have downloaded several versions of NVFlash, even with CWM baked in, didn't work. I have downloaded the format version of NVFlash, and that did work, but.....
i get 2 types of messages, the magical mismatch, and an error message which says there is a critical error with the boot loader. But they are replacing eachother after a new format, so 1 time the magical error, the next time the critical error.
When installing with using NVFlash(doesn't matter which version), the tablet is reacting, gives also the message Entering NVFlash Recovery mode / nv3p server, but the tablet does not start up again by itself. When start up again with the volume + button, i receive the following message; "Detect a recovery key pressed", then "Booting recovery kernel image". There it stops!! Nothing happens.
I also renamed the clockworkmod image to part9 image, and you can guess the result........
Please note i have used the manuals found over here and somewhere else on the web. Most of them are copies from Roebeet's his manual. I also found a site called NVFlash for dummies, did everything as mentioned in the manuals, but again, nothing helped.
To go in APX mode is not a problem at all, btw.
I also tried to format my external SD from FAT to FAT32 to NTFS, no chance at all to get passed the bird screen.(should be FAT32)
I even tried the manual to to open the damn tablet, uncharge the battery, , but i didn't do anything with the copper wire, as mentioned in the manual.
Also i have found the youtube manual to install NVFlash(perhaps i forget a step) but even that didn't help me out.
Also a search on the internet to recover the kernel and the bootloader, didn't give me a solution.
At this point i have format the tablet, the error message says magical mismatch, and this should be ok. I have tried severall times to install it again, but the tablet doesn't go further than the birdscreen.
Is there anyone with a possible solution? Please help!
please see also attached the latest attempt to get the tablet to work
C:\Users\brom\Desktop\gtab.nvflash.1.1.branch.20110422 with cwmv8>"nvflash.exe"
--bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create
--go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x170061834200f5d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928940/928940 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33292288/33292288 bytes sent
part8.img sent successfully
sending file: recovery.img
| 3862528/3862528 bytes sent
recovery.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
| 116840064/116840064 bytes sent
system.img sent successfully
Press enter to continue:
thanks in advance for your help!
Have you tried bekits origonal stock restore image?
yes i did, (1st thing i tried)but nothing seems to work. Is there another possibility to remove all data from the tablet, and install it again?
Maybe it is a hw issue, the nand going bad? Call Viewsonic and get a replacment.
what i see in the install script is the following,
- 4080/4080 bytes sent
isn't there apossibilty to change this, because in the CWM bootloader you need to change a setting with values like this to i believe 2040.
could be ,but the tablet starts up, but doesn't go further.
Here are a couple links that may help get your tablet restore:
Viewsonic GTablet For Dummies
Guide - Restore G Tablet after a Failed Recovery Mode "update.zip"
Hope this helps.
djab67
(if this helps, please consider clicking the "Thanks" button)
sounds like you are using a version of cwm that is not compatible with your bl version.
the 1st one i used, the 2nd is unknown by me, let's try.
And thanks for the info.
i know, but which one to use??
Which one did you use? When you use the wrong cwm for your bl version, you will stay stuck at 'booting kernel recovery image' until you run a format nvfflash then flash the stock 1.1 or 1.2 Rom.
please see attached what i have tried until sofar.
update-smb_a1002-3389-user
update-smb_a1002-3053-user
update-smb_a1002-3316-user
update-smb_a1002-2967-user
G_Harmony_Gingebreadv2.6(BL1.1)
nvflash_windows_20100500 (1)
gtab.nvflash.1.2.branch.20110617
gtab.cwm.3028.1.2.branch.rev5
gtab.nvflash.1.1.branch.20110422
cwmod_microsd
CWM3028.1.2external
cwmod08.1.1external
nvflash_gtablet_46_2010112600
gtab-cwm-v08
gtab.nvflash.1.2.branch.20110508 with cwmv3028 (1)
gtab.nvflash.1.2.branch.20110508 with cwmv3028
nvflash 1.1
nvflash_gtablet_46_2010112600
4349_Downgrade
I also have a format nvflash, to remove everything from the tablet.
note i constantly run a format when a flash do not work. perhaps it's me, but i'm lost.
Magic value mismatch.
Among the files that u tried to flash, I noticed that there is one file that yo didn't try
FORMAT.zip
http://www.mediafire.com/?a8sptd6u556qr2j
1.) Go to this website http://viewsonic-gtablet-for-dummies.webs.com/
2.) Go to code detox
3.) Use the "special nvflash" known as "format nvflash.zip files"
This Nvflash removes every single image and setting you flashed on your gtab. After the format.zip nvflash done its job, it will show up "magic value mismatch"
Using format.zip, any damage you done on your tablet shud be wiped clean. (the format.zip removes everything, even the bootloader and etc).
After u do ur format.zip nvflash, you need to determine what kind of bootloader your gtab is. (BL 1.1 or BL 1.2). It will help if you remember what kind of rom you used previously to determine the bootloader.
After that, run the nvflash with cwm (1.1 or 1.2), then it shud be ok.....
(at least this is how i do)
Hope it helps
maestro2702,
If you can connect to your g tablet in APX mode, then I think steps I documented in a guide should work for you. If you follow the steps in the guide exactly (including the listed downloads), your tablet will be on bootloader 1.2 when finished. It should not matter what bootloader you had originally.
Couple notes for when the tablet is working again:
Follow roebeet's Mountain Laurel instructions to switch over from stock to clockworkmod recovery.
Once clockworkmod recovery is flashed, go ahead and try any bootloader 1.2 rom you want.
Link to the guide:
Guide - Restore G Tablet after a Failed Recovery Mode "update.zip"
Hope this helps.
djab67
(if this helps, please consider clicking the "Thanks" button)
Hi Fury7, tried this one this morning, and unfortunally, i get stuck on the birdscreen again. Earlier in this topic someone suggested it could be a memory(NAND) issue, and i am starting to believe it is.
djab67
i'm reading your instructions now, quit some text, but i will let you know if it worked out.
thanks anyway.
Just a question. You know which bootloader are you using?
@fury7
At this point there is no bootloader on my tablet, i cant get one to install.
When i link it to my PC, the only thing i see that it is visible as an external disk, which cannot be accessed. When i try to install a bootloader, i need to use the SD Card, and that is not working either. At this point it is not possible to get further than the 1st screen, the bootloader doesn't come up when installed. tried severall versions. ADP i cannot get to work with the tablet, because it is only visible as an external disk which cannot be accessed by the W7 PC.
So i am starting to believe there is something wrong with the hardware.
I believe I narrowed down my problem to needing to format the different mmcblk’s so I can get one of the different recoveries to restore the image. As to what I have tried and have not keep reading.
So one day decided to try cm7 via SD Card, and it looked impressive. However It said something about issues with the sd card. I had no Idea what it would do to the nook ( I should've read the the instructions more thoroughly)
So I reboot only to find the nook looping back to cwm recovery (it was rooted).
After some searching I try the Ubuntu restore. It got stuck at the MLO part, I decided maybe it takes a while and i guess it Zeroed out mmcblk5 (I guess i'm not sure of anything at this point). The only issue later I find is that Ubuntu doesn't do any formatting, it just blanks out the partition and reloads it. After that failed attempt CWM just freezes at the cardboard box
I gave this a try
http://forum.xda-developers.com/showthread.php?t=1663836
but it spends a while with 1 red x and then reboots into locked recovery.
Giving it another try, I start apply the method described in:
http://forum.xda-developers.com/showthread.php?t=1605664
but “scripts” zip file gives a 404 error at Drop box.... the other files worked like a charm. It did get me pretty close and gave me this state (3 drives formatted in ext, I just need the others to format and restore). Thanks meghd00t!
List of devices attached
0000000000000000 recovery
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB bootdata
7 134MB 522MB 388MB factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 14.5GB 12.9GB media
11 14.5GB 15.6GB 1139MB ext4 userdata
So now I am trying
http://forum.xda-developers.com/showthread.php?t=1545766
See post#2. However I am no linux guru and I am stuck at the step that says
Copy device and vendor folder from Nook-Tablet to ~/android/system/
I followed the instructions on
http://forum.xda-developers.com/showthread.php?t=1570022
To setup ubuntu on the vm box. I can connect to the nook via adb on windows 7 but it refuses to work from Ubuntu, it just wont show (I added the adb_usb.ini and launched adb via sudo). I tried to pull from windows but it doesn't look right and think it would be best if I pull it from Ubuntu.
P.S.
Oh also, since I reason that my partitions are pretty much gone I tried to pull it from the cm7 sd image. unless someone knows how for me to mount the mmcblk’s and extract the needed files from there.
Fixed Somewhat ...
Well I found the missing files to get this method to work.
http://forum.xda-developers.com/showthread.php?t=1605664
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/showthread.php?t=1470910
However the nook just boots then it says: Please restart your device and try again, and powers down...
For some reason I cant get the acclaim_update.zip to work. Can anyone please help or send me in a new direction?
Please restart...
Riddler9884 said:
Well I found the missing files to get this method to work.
http://forum.xda-developers.com/showthread.php?t=1605664
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/showthread.php?t=1470910
However the nook just boots then it says: Please restart your device and try again, and powers down...
For some reason I cant get the acclaim_update.zip to work. Can anyone please help or send me in a new direction?
Click to expand...
Click to collapse
That is the notice that the Nook is trying to load Recovery but there is not a recovery.img
I note in the op that you tried Megd00t's repart. It is absolutely solid in my opinion. I even intentionally bricked my nt8 to film the video that shows how to make it work.
If you try it again, you should be able to use an SDCard version of Clockworkmod to flash any *.zip to the device. See my series of videos here: http://www.youtube.com/playlist?list=PL676779C4F7BE8FEB&feature=mh_lolz
PM me if you have questions. I have not yet finished the accompanying articles describing the processes.
I am stumped
I performed this again
http://forum.xda-developers.com/show....php?t=1605664
with the added lines from the DD recovery
for blocks 7, 8 and 9
No go - It boot loops the stock recovery
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/show....php?t=1470910
Same result - It boot loops the stock recovery
by what I read both of these are supposed usually do the trick but it still doesn't do it. I followed the advice that cwm should be able to apply any zip
but the stock bn update zip doesnt work
acclaim update fails
heck the ribbon rom fails
it gave a status one. What am I overlooking?
Would there be a way to make a disk image of the entire nook with all the sub partitions defined?
It would have blocks 1-9 with their stock info and the rest of the partitions zeroed out. So they loaded with info when you boot to recovery?
Stock cannot be flashed without mod
Riddler9884 said:
I followed the advice that cwm should be able to apply any zip
but the stock bn update zip doesnt work
acclaim update fails
heck the ribbon rom fails
it gave a status one. What am I overlooking?
Click to expand...
Click to collapse
My error. (Sorry) The B&N update file (the BN acclaim update is the same) cannot be flashed without modification. Meghd00t posted a "howto" I believe but I don't have a link right now.
However, you SHOULD be able to flash the Ribbon Root and other custom ROMs using CWM. I don't know where you should go now...
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
Riddler9884 said:
Would there be a way to make a disk image of the entire nook with all the sub partitions defined?
It would have blocks 1-9 with their stock info and the rest of the partitions zeroed out. So they loaded with info when you boot to recovery?
Click to expand...
Click to collapse
I believe that is Albert Wertz's process. You might want to check it out. His file is a CWM "Backup" image that you should be able to "Restore" (with CWM). Might be worth a try...
Well I am not sure but I believe what fixed it was:
repartitioning the Nook using: http://forum.xda-developers.com/showthread.php?t=1605664
Then Using: SD_R3NT16or8gbV4_7
http://forum.xda-developers.com/showthread.php?t=1528625
I flashed flash-restore-stock.zip from:
http://forum.xda-developers.com/showthread.php?t=1545766
followed up by using the restore feature in SD_R3NT16or8gbV4_7
to complete the missing info
I almost got my nook back. Now I just need to work out how to get my sn back.
Riddler9884 said:
Well I am not sure but I believe what fixed it was:
repartitioning the Nook using: http://forum.xda-developers.com/showthread.php?t=1605664
Then Using: SD_R3NT16or8gbV4_7
http://forum.xda-developers.com/showthread.php?t=1528625
I flashed flash-restore-stock.zip from:
http://forum.xda-developers.com/showthread.php?t=1545766
followed up by using the restore feature in SD_R3NT16or8gbV4_7
to complete the missing info
I almost got my nook back. Now I just need to work out how to get my sn back.
Click to expand...
Click to collapse
Hey sounds like you are almost there.
The sn is under the SDCard door. I saw a post somewhere on XDA about a process for manually putting it back in the device memory. Search here and Google.
Sent from my NookTablet using XDA
I tried
http://forum.xda-developers.com/showthread.php?t=1610069
I guess it works depending on how much you have cleared from the nooks internal memory in the process of restoring the nook.
I kind of put this together based on what I saw here
http://nookdevs.com/NookColor_Fix_Boot_Loops
Look at the section that says
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
i did a little research
Their method didn't work form me, but it gave me insight. I worked out the chmod by what was said here
http://forum.xda-developers.com/showthread.php?t=1586281
~ # echo -n -e "20201700########" > /rom/devconf/SerialNumber
~ # echo -n -e "20201700########" > /rom/devconf/DeviceID
~ #echo -n -e "5867########" > /rom/devconf/MACAddress
~ # cd /rom/devconf
/rom/devconf # chmod 440 MACAddress
/rom/devconf # chmod 440 DeviceID
/rom/devconf # chmod 440 SerialNumber
Update - It Couldn't Register but I did find this out by chance:
When I originally got my tablet and rooted the google play store saw this under My Devices:
(From a pc, Log in, all the way at the bottom, My Devices tab)
Maker-> Barnes&Noble
Model-> BNTV250
I went back in recently after restoring and got this:
Maker-> Bn
Model-> Nook Tablet
Maybe one of the restores was messing with changing the name for Compatibility? I used so many things I cant tell where the above came from.
repart.img
Riddler9884 said:
Maybe one of the restores was messing with changing the name for Compatibility? I used so many things I cant tell where the above came from.
Click to expand...
Click to collapse
What is the ID that is displayed when you connect with ADB? In all of my (3 months) trial of being "bricked", I did not stop getting my serial number as the id when I connected with adb. But, nothing else on the internal memory worked. The only way I could use the Nook was with an external SD-based ROM (I used CM7a).
What I suggest is (repeat this after each different attempt to fix your issues): Try Meghd00t's repart.img again. Let it clear everything and restore back to stock. You might be pleasantly surprised! I sure was.
Here is a link to my step-by-step guide. http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Nope no more, re-imaging the nook for this test. My wife will kill me if I keep ignoring her to tinker with the nook, Especially since it was for her to read her novels.
After loading albertwertz image and having access to android market and the amazon store has her happy.
Registering the B&N would just be a plus.... I need a tablet I will just get a Samsung 7 inch tablet.
Restore serial number on Nook
Riddler9884 said:
Nope no more, re-imaging the nook for this test. My wife will kill me if I keep ignoring her to tinker with the nook, Especially since it was for her to read her novels.
After loading albertwertz image and having access to android market and the amazon store has her happy.
Registering the B&N would just be a plus.... I need a tablet I will just get a Samsung 7 inch tablet.
Click to expand...
Click to collapse
I found this on one of Succulent's posts:
- To get your serial number back, you need to perform factory restore (8 failed boot method)
- The one that prompt,
Clearing data…
A reset is being performed.
This may take a few minutes
Click to expand...
Click to collapse
Here is a link to the thread: http://forum.xda-developers.com/showthread.php?t=1545766
*late edit*
I think after all this posting I might be close to what is going on. When I boot, it looks like /system isn't mounting. I will paste the output of the recovery log at the end of this post, for someone to confirm. Maybe my fstab was changed at some point? If anyone can post a current fstab file that would be great too.
Okay, I'll try to be succinct. I had a working CM10, but could never really get flash to work without crashing on me. So I decided to go with Androwook. I went through the nvflash, everything went according to the tutorial. I have all my backup .imgs, etc. I still have full access to the device via fastboot, nvflash, and TWRP. I can't recall the entire series of events, but at some point when I tried to install the WW_epaduser_10_4_2_9_UpdateLauncher.zip, it halfway installed, tried to format the internal storage (which later I found it had) and then rebooted with the droid on his back, red exclamation point. Uh oh. So I was able to get recovery reflashed, and since then, no matter what rom I install, nothing will boot! Last thing I have tried was the Prime Full Wipe, adb pushed a couple of roms to internal storage and flashed and no love.
Can anyone please guide me in the right direction here? Right now, my boot still says "AndroidRoot 9.4.2.28r01" which tells me its still the .mobi loader right? Will that affect the rom image loading up?
I tried playing with the nvflash, but not really quite sure what I am doing. I can "wheelie -b blob.bin" from the blob I pulled during the nvflash procedure. After that, I can successfully "nvflash --resume --rawdevicewrite 0 2944 bricksafe.img" This doesn't give any win, however. I have the other files but the documentation on how to MAKE nvflash backups is all over. How to USE them doesn't seem to be. Any and all help is greatly appreciated.
Oh no...
wolfeyes30 said:
Oh no...
Click to expand...
Click to collapse
Originally Posted by rayman View Post
No, no guide yet.
We purposedly left out the procedure for doing a full restore until it is explicitly required.
Our experience is that if we give the instructions for this, people will do it for every little brick that could easily be fixed in other ways and it's just not a good idea
For 99% of cases, you can restore by simply flashing the partitions that have been broken, e.g.
Bootloader having issues => nvflash -r --download 4 bootloader.bin
Broken or stock recovery => nvflash -r --download 5 recovery.img
Broken or stock boot partition => nvflash -r --download 6 boot.img
Broken system partition => nvflash -r --download 10 system.img
stock system.img, boot.img etc can be retrieving by using the blobunpack tool on the blob file (different blob ) inside official ASUS images (downloaded from support.asus.com). When unpacked, blob.APP => system, blob.LNX => boot.img, blob.SOS => blob.LNX.
There are very few cases where you will brick further than this and when/if that happens, we'll be happy to help people through it, assuming they have ALL the backups we mention on androidroot.mobi! In everyday usage, you won't need those backups, but when/if something really bad happens, they could mean the difference between a brick and a recoverable tablet.
Click to expand...
Click to collapse
I think this is where I need to be. Of course i just broke it worse, now I can *only* access the device via nvflash. In my inifinite wisdom, I renamed "bootloader.ebt" to "bootloader.bin" and flashed it. I then tried to flash "bricksafe.img" and that did not fix anything. I can see that there's a way to blob-extract what I need from the above post, but I don't see the bootloader.img conversion listed in there. Maybe it's named as it should be on extration.
I am tempted to try doing a wheelie using the "ebtblob.bin" instead of the "blob.bin" since these other images I recovered have the .ebt extension. But there's extreme lack of documentation, and I don't want to make it worse. Anyone?
I tried doing this:
Try the following:
1) Download *externallinknotallowed*/androidroot.mobi/download/rec_bootloader.bin
2) Boot device into nvflash with Wheelie
3) nvflash -r –download 4 rec_bootloader.bin
4) nvflash -r –go, shutdown regularly and see if it boots again normally.
Click to expand...
Click to collapse
and got what looks like a syntax issue
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
[email protected]:~/Downloads/tf201_nvflashpack$ ./nvflash -r –download 4 rec_bootloader.bin
Nvflash v1.5.66719 started
[resume mode]
unknown command: –download
[email protected]:~/Downloads/tf201_nvflashpack$
Click to expand...
Click to collapse
I looked through the nvflash manpage and don't see anything regarding a -download flag.
jrodder said:
I think this is where I need to be. Of course i just broke it worse, now I can *only* access the device via nvflash. In my inifinite wisdom, I renamed "bootloader.ebt" to "bootloader.bin" and flashed it. I then tried to flash "bricksafe.img" and that did not fix anything. I can see that there's a way to blob-extract what I need from the above post, but I don't see the bootloader.img conversion listed in there. Maybe it's named as it should be on extration.
I am tempted to try doing a wheelie using the "ebtblob.bin" instead of the "blob.bin" since these other images I recovered have the .ebt extension. But there's extreme lack of documentation, and I don't want to make it worse. Anyone?
I tried doing this:
and got what looks like a syntax issue
I looked through the nvflash manpage and don't see anything regarding a -download flag.
Click to expand...
Click to collapse
Okay.
[email protected]:~/Downloads/tf201_nvflashpack$ ./nvflash --resume --download 4 rec_bootloader.bin
Nvflash v1.5.66719 started
[resume mode]
sending file: rec_bootloader.bin
/ 1021997/1021997 bytes sent
rec_bootloader.bin sent successfully
So it was a syntax thing, I read a bit closer. I now have bootloader again, roms still won't load up. I might take a rest for tonight. I am sure this is fixable, just checking to see if there's any guru out there that can help a brother out.
jrodder said:
Okay.
[email protected]:~/Downloads/tf201_nvflashpack$ ./nvflash --resume --download 4 rec_bootloader.bin
Nvflash v1.5.66719 started
[resume mode]
sending file: rec_bootloader.bin
/ 1021997/1021997 bytes sent
rec_bootloader.bin sent successfully
So it was a syntax thing, I read a bit closer. I now have bootloader again, roms still won't load up. I might take a rest for tonight. I am sure this is fixable, just checking to see if there's any guru out there that can help a brother out.
Click to expand...
Click to collapse
I can't seem to mount /DATA from within TWRP, it also started asking me for a password. I just reinstalled it again (I think) via adb, and it's still asking me for a password? I can cancel by it, but it's nothing I set and have never seen before.
jrodder said:
.........I have all my backup .imgs, etc. I still have full access to the device via fastboot, nvflash, and TWRP. I can't recall the entire series of events, but at some point when I tried to install the WW_epaduser_10_4_2_9_UpdateLauncher.zip, ....
Click to expand...
Click to collapse
I did this exact same thing going through the steps for the AndroWook HairyBean instructions.
I now have a new bootloader (doesn't say AndroidRoot) and I can't seem to do anything.
I'm actually lost when it comes to finding out whether or not I'm able to boot to APX mode.
How can I tell if I'm in APX mode?
If I get into APX mode, do you know how to restore the bootloader?
ANY help would be greatly appreciated.
--Charlie
ecatsab said:
I did this exact same thing going through the steps for the AndroWook HairyBean instructions.
I now have a new bootloader (doesn't say AndroidRoot) and I can't seem to do anything.
I'm actually lost when it comes to finding out whether or not I'm able to boot to APX mode.
How can I tell if I'm in APX mode?
If I get into APX mode, do you know how to restore the bootloader?
ANY help would be greatly appreciated.
--Charlie
Click to expand...
Click to collapse
Well this is the blind leading the blind but... you know you are in APX mode when you hold up on the volume, press and hold power and it vibrates. Screen should stay totally black. On windows a device will show up. For me at home on linux, I just have to test it by trying to do a wheelie, and it works. Glad to know I'm not the only soul screwed after this androwook flashing attempt. I am certain it is recoverable, but can't for the life of me make it happen. Restoring the bootloader would be done as I outlined above in one of my replies. Grab the recovery image and flash it. if you google the command I used, you should find the url. XDA won't let me post links...
Hope that helps.
jrodder said:
Well this is the blind leading the blind but... you know you are in APX mode when you hold up on the volume, press and hold power and it vibrates. Screen should stay totally black. On windows a device will show up. For me at home on linux, I just have to test it by trying to do a wheelie, and it works. Glad to know I'm not the only soul screwed after this androwook flashing attempt. I am certain it is recoverable, but can't for the life of me make it happen. Restoring the bootloader would be done as I outlined above in one of my replies. Grab the recovery image and flash it. if you google the command I used, you should find the url. XDA won't let me post links...
Hope that helps.
Click to expand...
Click to collapse
I am starting to think my whole issue is with something wonky that happened with the partitioning of the internal storage. I unpacked the stock ASUS blob, so try and push the system data via nvflash.
[!] Done - your device should now be ready for nvflash
[email protected]:~/Downloads/tf201_nvflashpack$ ./nvflash -r --download 10 system.img
Nvflash v1.5.66719 started
[resume mode]
system.img is too large for partition
command failure: partition download failed
[email protected]:~/Downloads/tf201_nvflashpack$
Click to expand...
Click to collapse
That's not the first time I had seen that, as I get that same error trying to push the 700mb blob file for the Androwook Hairybean 1.2.
Here is the listing of file structure from adb shell:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 491.3M 48.0K 491.3M 0% /dev
/dev/block/mmcblk0p2 421.3M 16.5M 404.8M 4% /cache
/dev/block/mmcblk0p8 27.2G 431.5M 26.7G 2% /data
/dev/block/mmcblk0p8 27.2G 431.5M 26.7G 2% /sdcard
~ #
Click to expand...
Click to collapse
Is that what it's supposed to be? I read about a staging partition, which is where the blob has to sit when being sent. Is that an actual partition that is supposed to exist separate from what is listed?
I did find this from another post where a user had blown up his partitions:
Note the error on /data. Could not format /data either using the CWM mounts and storage menu. I named the partitions I knew about and formatted /data (mmcblk0p8) from adb shell:
Number Start End Size File system Name Flags
1 38.3MB 575MB 537MB ext4 system
2 575MB 1024MB 449MB ext4 cache
3 1024MB 1026MB 2097kB misc
4 1026MB 1585MB 559MB ext3 staging
5 1585MB 1591MB 5243kB fat32 btmac
...
8 1596MB 63.6GB 62.0GB ext4 data
Click to expand...
Click to collapse
I will continue to try and find out how, but if ANYONE can tell me how I can automagically format the internal storage to its proper config, I'd be grateful. I tried everything via TWRP 2.2.2, but it doesn't seem to be working. I don't have another tablet to test with for sanity purposes, but if it matters I cannot ever mount the "sdcard" from the mount menu, with internal storage selected. I've gone through and tried all the wipe and format options many times.
**still trying***
More reading, I understand now that my only option is figuring out nvflash, as it supercedes fastboot after it has been installed. So, I grabbed my current partition structure, seems awfully high but without someone to help me sanity check that I don't know if its correct or not. I see an option that looks like it would be great, but appears to need a config file that I don't have.
--format_all
formats all existing partitions on the target device using the config file,
including partitions and the bct
Click to expand...
Click to collapse
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=768
BytesPerSector=4096
PartitionId=3
Name=PT
DeviceId=18
StartSector=768
NumSectors=128
BytesPerSector=4096
PartitionId=4
Name=EBT
DeviceId=18
StartSector=896
NumSectors=2048
BytesPerSector=4096
PartitionId=5
Name=SOS
DeviceId=18
StartSector=2944
NumSectors=2048
BytesPerSector=4096
PartitionId=6
Name=LNX
DeviceId=18
StartSector=4992
NumSectors=2048
BytesPerSector=4096
PartitionId=7
Name=CER
DeviceId=18
StartSector=7040
NumSectors=2048
BytesPerSector=4096
PartitionId=8
Name=IMG
DeviceId=18
StartSector=9088
NumSectors=2048
BytesPerSector=4096
PartitionId=9
Name=GP1
DeviceId=18
StartSector=11136
NumSectors=256
BytesPerSector=4096
PartitionId=10
Name=APP
DeviceId=18
StartSector=11392
NumSectors=131072
BytesPerSector=4096
PartitionId=11
Name=CAC
DeviceId=18
StartSector=142464
NumSectors=109568
BytesPerSector=4096
PartitionId=12
Name=MSC
DeviceId=18
StartSector=252032
NumSectors=512
BytesPerSector=4096
PartitionId=13
Name=USP
DeviceId=18
StartSector=252544
NumSectors=136576
BytesPerSector=4096
PartitionId=14
Name=PER
DeviceId=18
StartSector=389120
NumSectors=1280
BytesPerSector=4096
PartitionId=15
Name=YTU
DeviceId=18
StartSector=390400
NumSectors=128
BytesPerSector=4096
PartitionId=16
Name=CRA
DeviceId=18
StartSector=390528
NumSectors=1280
BytesPerSector=4096
PartitionId=17
Name=UDA
DeviceId=18
StartSector=391808
NumSectors=7368960
BytesPerSector=4096
PartitionId=18
Name=GPT
DeviceId=18
StartSector=7760768
NumSectors=128
BytesPerSector=4096
Click to expand...
Click to collapse
Sorry to hear you also have this issue. I broke mine in a very similar way and have been struggling to repair it too. Do you have a compiled version of the blob unpack tool? I can only find the source and I was hoping to avoid having to setup the tools for compiling that and hoped there was a validated Windows exe available somewhere?
Was annoying to have spent ages on the NVFlash backup procedure to now have that being (at the moment!) zero help whatsoever...
rtg2 said:
Sorry to hear you also have this issue. I broke mine in a very similar way and have been struggling to repair it too. Do you have a compiled version of the blob unpack tool? I can only find the source and I was hoping to avoid having to setup the tools for compiling that and hoped there was a validated Windows exe available somewhere?
Was annoying to have spent ages on the NVFlash backup procedure to now have that being (at the moment!) zero help whatsoever...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1890912
rtg2 said:
Sorry to hear you also have this issue. I broke mine in a very similar way and have been struggling to repair it too. Do you have a compiled version of the blob unpack tool? I can only find the source and I was hoping to avoid having to setup the tools for compiling that and hoped there was a validated Windows exe available somewhere?
Was annoying to have spent ages on the NVFlash backup procedure to now have that being (at the moment!) zero help whatsoever...
Click to expand...
Click to collapse
After about two days of messing with it, I did finally get success. I didn't bother updating this post, mainly because I wasn't entirely sure what I had done that made the difference. In retrospect, I was quite close most of the time. Reformatting /data to ext3 helped, as well as using my nvflash with bricksafe.img. I also wonder if I might have had a bad download, considering the chain of events. I *swear* I did all the things that needed to be done many times, but in the final round after a night of sleep I used fresh downloaded images of the TWRP recovery and CM10. Bottom line is, as long as you have done the nvflash tutorial properly, and backed up all the items as instructed, you should always be able to recover.
OK I'm not a total n00b but I am a novice. I've been searching for an answer for this problem for a couple days now.
Device is a Nabi 2 that was rooted and had gapps installed on it using the Victoria tutorial on youtube. Everything was great until i tried to do the OTA update to 2.1. Obviously it wouldn't update because TWRP was installed so I downloaded Nabi Lab 2 to take it back to the stock ROM and bootloader. And now the problem starts...
After flashing the stock rom and installing the stock loader I rebooted. Now I'm stuck at the NABI loading screen with no animation. If I hold the Volume + key and power it will boot up to the screen with the options "boot normally, Fastboot Protect, Recovery Kernal, and Forced Recovery." However I am not able to navigate to any of the options or select anything. Also when the Nabi is connected to my PC Nabi Lab no longer sees it, nor does ADB (using "adb.exe devices" at the command prompt). It's also not detected by Device Manager. The only thing Device Manager sees is a MTP USB Device that it can not install a driver for.
So, PLEASE HELP! Before my daughter misses this stupid thing and I have to buy another.
dwelch77 said:
OK I'm not a total n00b but I am a novice. I've been searching for an answer for this problem for a couple days now.
Device is a Nabi 2 that was rooted and had gapps installed on it using the Victoria tutorial on youtube. Everything was great until i tried to do the OTA update to 2.1. Obviously it wouldn't update because TWRP was installed so I downloaded Nabi Lab 2 to take it back to the stock ROM and bootloader. And now the problem starts...
After flashing the stock rom and installing the stock loader I rebooted. Now I'm stuck at the NABI loading screen with no animation. If I hold the Volume + key and power it will boot up to the screen with the options "boot normally, Fastboot Protect, Recovery Kernal, and Forced Recovery." However I am not able to navigate to any of the options or select anything. Also when the Nabi is connected to my PC Nabi Lab no longer sees it, nor does ADB (using "adb.exe devices" at the command prompt). It's also not detected by Device Manager. The only thing Device Manager sees is a MTP USB Device that it can not install a driver for.
So, PLEASE HELP! Before my daughter misses this stupid thing and I have to buy another.
Click to expand...
Click to collapse
So you can't navigate the bootloader screen at all? If you click the vol- button it doesn't highlight the next menu item just nothing happens?
aicjofs said:
So you can't navigate the bootloader screen at all? If you click the vol- button it doesn't highlight the next menu item just nothing happens?
Click to expand...
Click to collapse
Exactly. I can not navigate the options at all. Volume - doesn't do anything, Volume + doesn't do anything.
OK scratch all of that. So while I was messing around with it this morning I accidentally dropped the tablet. After "impact calibration" the keys worked and I was able to get into TWRP. And Nabi Lab recognized it was plugged in. I was able to get it set all the back to factory with the factory boot recovery in place as well. As of right now update 2.1 is downloading and I'm keeping my fingers crossed that it will work.
The only thing I can think of is something on the board might have a broken solder connection, so as of right now I'm touching it as little as possible until the updates are done. I'll post back here when I have more information.
Nabi 2 Bricked ?
Hi,
I hope someone can help me with a Nabi 2 problem.
Basically I have 2 x Nabis. Rebuilt the first ok after a couple of days so that it now has Jelly Bean and Google Play (which is a big improvement). Then took it upon myself to start the 2nd one. I realised that something wasn't quite right and wiped in anticipation of rebuild again...what a mistake
So after installing the adb and fastboot drivers (pdanet) and TWRP 2.6.0 I can still get into TWRP BUT can no longer wipe "data", "cache", "system", "internal storage" etc as it says : "E:Unable to mount '/data' ....or system, or cache, addon, internal storage etc. Now i'm no expert on fastboot commands or terminal but can anyone please point me in the right direction as im completely clueless on this ?
I wouldn't know where to start
Thanks in advance
Dow
Dowmole said:
Hi,
I hope someone can help me with a Nabi 2 problem.
Basically I have 2 x Nabis. Rebuilt the first ok after a couple of days so that it now has Jelly Bean and Google Play (which is a big improvement). Then took it upon myself to start the 2nd one. I realised that something wasn't quite right and wiped in anticipation of rebuild again...what a mistake
So after installing the adb and fastboot drivers (pdanet) and TWRP 2.6.0 I can still get into TWRP BUT can no longer wipe "data", "cache", "system", "internal storage" etc as it says : "E:Unable to mount '/data' ....or system, or cache, addon, internal storage etc. Now i'm no expert on fastboot commands or terminal but can anyone please point me in the right direction as im completely clueless on this ?
I wouldn't know where to start
Thanks in advance
Dow
Click to expand...
Click to collapse
You are using wrong version(Jellybean vs ICS) of TWRP is my guess.
aicjofs said:
You are using wrong version(Jellybean vs ICS) of TWRP is my guess.
Click to expand...
Click to collapse
No matter what I do I cannot mount the internal storage (it shows 0MB under "Restore" and cannot mount the Micro SDcard either). All of the folders on the Nabi 2 are now empty and I would like to try to re-format and rebuild it. I have tried ICS and Jellybean TWRP but neither allow me to mount any folders (data, system,cache etc).
Is there anything I'm not doing or could try ?
Thanks
Dow
Dowmole said:
No matter what I do I cannot mount the internal storage (it shows 0MB under "Restore" and cannot mount the Micro SDcard either). All of the folders on the Nabi 2 are now empty and I would like to try to re-format and rebuild it. I have tried ICS and Jellybean TWRP but neither allow me to mount any folders (data, system,cache etc).
Is there anything I'm not doing or could try ?
Thanks
Dow
Click to expand...
Click to collapse
So what exactly did you do again? It was an original Nabi2 on ICS, and you "wiped" it. What exactly did you wipe? All the partitions not showing up is usually I sign of the wrong TWRP build but you said you tried both. Plus I have never seen where you can't mount the MicroSD
In the terminal app in TWRP(both versions) what does it say if you type
cat /proc/partitions
does it look like this:
major minor #blocks name
179 0 7766016 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 823296 mmcblk0p3
179 4 481280 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 32768 mmcblk0p6
179 7 1536000 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 65536 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 4485120 mmcblk0p11
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
or more like this
major minor #blocks name
179 0 7766016 mmcblk0
179 48 31166976 mmcblk1
179 49 31162880 mmcblk1p1
Thanks for your help on this aicjofs I really appreciate it
It shows :-
179 0 31166976 mmcblk0
179 1 1 mmckblk0p1
179 5 31164416 mmcblk0p5
The whole "short" story was....When I received the Nabi 2 just over a year ago I had to somehow get Google Play Store on it. As we know that wasn't possible until recently so I followed the guide by Victoria (I think from memory) on Youtube. This then did not allow me to do further Nabi updates. I managed to get this back to stock from your guide and then update bit by bit to the latest update (wit Jellybean). All was great until I realised that the wrong one of my children had been setup on it. I removed the user (from the parent portal on the Nabi website). This then stopped me using the external SD card (media errors stopping it)
So stupidly (in hindsight) I took it upon myself to wipe the Nabi from within Jellybean and re-boot, thinking that it would be a straightforward re-setup. But it wasn't. It seemed to have un-mounted everything. So now within TWRP I cannot mount data, system, cache, external sd card. and therefore cannot wipe those folders and start again (from TWRP that is). I have tried to mount those folders from terminal but am getting nowhere
Thanks
Dowmole
Ok I've now managed to mount all folders except external sd card.
I can push the system.ext4.win file to sdcard/twrp/backups/device name/oem/system.ext4.win ...but it does not show up in restore (can only see it in file manager). So therefore cannot restore.
Anyone have any ideas ?
Dowmole said:
Ok I've now managed to mount all folders except external sd card.
I can push the system.ext4.win file to sdcard/twrp/backups/device name/oem/system.ext4.win ...but it does not show up in restore (can only see it in file manager). So therefore cannot restore.
Anyone have any ideas ?
Click to expand...
Click to collapse
Hello Dowmole, I have the same problem as you because in my infinite wisdom I wiped and updated using the built in system as well.Would you mind telling me how you managed to mount your internal storage?Apparently now, it seems, our problems are inverted because I can ONLY mount my External SD.The tablet works fine but I can't reroot it or flash anything because TWRP is unable to mount /data etc...
also when I type cat /proc/partitions this is the result:
179 0 30892032 mmcblk0
179 1 30887936 mmcblk0p1
Is my internal sd corrupt or something should I format it?
Radmatazz said:
Hello Dowmole, I have the same problem as you because in my infinite wisdom I wiped and updated using the built in system as well.Would you mind telling me how you managed to mount your internal storage?Apparently now, it seems, our problems are inverted because I can ONLY mount my External SD.The tablet works fine but I can't reroot it or flash anything because TWRP is unable to mount /data etc...
also when I type cat /proc/partitions this is the result:
179 0 30892032 mmcblk0
179 1 30887936 mmcblk0p1
Is my internal sd corrupt or something should I format it?
Click to expand...
Click to collapse
I had a similar issue -- 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.
Your solution was awesome!
2girlzdad said:
I had a similar issue -- 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.
Click to expand...
Click to collapse
-----> My issue was EXACTLY the same, I used your solution and viola, it is fixed, it even auto asked me to install root before I rebooted! THANK YOU... as a rank amateur, I feel I should share the finer details of my solution to help anyone else out that also has this problem.
I did a couple things different from this, that I should share so that all will benefit.
I use NabiLabGUI. The TWRP that comes with it does NOT work with my build. I searched for the TWRP that comes with it,
Found at my 'C:\Users\Spam\AppData\Local\Apps\2.0\7J1BHCKA.8HM\5YTQ71XH.YAP\ then 2 sub directories,
nabi...exe_3432fd94fe885e67_0001.0002_none_141f851fecdb6e30 and
nabi..tion_3432fd94fe885e67_0001.0002_f75a67d47ecb93e2
since I have a nabi 2 NV7A, for my daughter, I opened the subdirectory '2' in each replacing the 2\recovery\new\recovery.img with the one from twrp-recovery-JBNV7AUS-263.zip (note you must rename it to 'recovery.img')
I then ran nabilabgui, simply selecting the recovery installer, to easily load the recovery image, booted into the now version 2.6.3 TWRP, and loaded the 'twrp-recovery-JBNV7AUS-263.zip'
No boot/softbrick
I am unable boot beyond the bootloader screen. I cannot gain access via Nabi Lab GUI with ADB but I can via Fastboot. So my issue is how do I fix my Nabi 2 via Fastboot? I need commands and where and what files to get back to stock.
Thank you,
Niles
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Doozeman said:
Hi there I think I have softbricked my Nabi 2. I tried to update the software from ICS to JB using files from the XDA Nabi 2 Wiki but have come to a massive problem. I can't boot back into TWRP because all I get is an Android laying down with an ! on his chest. I can't re-install TWRP because my Windows 8 PC can no longer see the device!! I can get into the tablet options menu with fastboot, forced recover etc. I think the biggest problem is getting the PC to see the device.
If I try selecting different options in the tablet boot menu then Windows will see the device as Android ADB Device or MTP USB Device.
Can anyone help me get over this problem? I'm not used to using shell commands but fear I will have to install the Android environment to use ADB to get things working.
Please help if you can as this tablet belongs to a nephew of mine and he is missing his YouTube. I am close to tears trying to find the solution. I have read and re-read XDA posts in case I missed something.
Many Thanks In Advance.
Doozeman
Click to expand...
Click to collapse
Android lying down is stock recovery, need to put TWRP back on it.
Since you can get to the tablet menu you need to select fastboot protocol. It will not do anything unless 2 conditions are met. You need to have USB plugged in to your computer and the fastboot driver installed. The fastboot driver might be the hardest part, most of the time people use PDAnet installer. Once you have that you can then put TWRP back on it with
fastboot flash recovery recovery.img or with Nabilab GUI
Where you might run in to problems is where your upgrade failed, hard to tell if you now have the JB bootloader or the ICS bootloader. Try TWRP's for both versions until you figure it out.
aicjofs said:
Android lying down is stock recovery, need to put TWRP back on it.
Since you can get to the tablet menu you need to select fastboot protocol. It will not do anything unless 2 conditions are met. You need to have USB plugged in to your computer and the fastboot driver installed. The fastboot driver might be the hardest part, most of the time people use PDAnet installer. Once you have that you can then put TWRP back on it with
fastboot flash recovery recovery.img or with Nabilab GUI
Where you might run in to problems is where your upgrade failed, hard to tell if you now have the JB bootloader or the ICS bootloader. Try TWRP's for both versions until you figure it out.
Click to expand...
Click to collapse
Thanks very much for the reply. I did have PDANet installed and my computer couldn't see the tablet. I will try again soon later. I think my problem has arisen since i followed a procedure from this link http://forum.xda-developers.com/showpost.php?p=50431606&postcount=98 and I may have messed up flashing this file http://forum.xda-developers.com/showpost.php?p=50356162&postcount=91 too early!. Ultimately I wish to have this file http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85 on the tablet and it being up and running with no problems.
First things first though I need to get the tablet seen by the computer.
Do I need to uninstall my Nexus 7 and Samsung Galaxy S III drivers first before installing PDANet? Once installed how do I get fastboot installed?
Many Thanks in Advance,
Doozeman
Okay I now have found how I can install TWRP via your command but I'm still unable to install an OS on the tablet. NabiLabs refuses to see the tablet and I am now stuck. Tell you what like this is a steep learning curve for me! Why can't this tablet be as easy as the Nexus 7 to flash or recover?
Have you any more suggestions as to how I can proceed? Is there another way I can push installation files? I have tried copying stock restore files (as supplied by Nabilabs) to a micro sd card using the following layout TWRP/BACKUPS/"My Device Number"/restore but no matter the version of TWRP installed there are no files shown to restore.
*Update* I have tried to install the latest TWRP via flashable zip but it won't install because of the missing folders as there is no OS installed. I get an error status 6. Unable to mount /data, /system, /cache etc.
I'm beginning to fear that I have killed this tablet
I'm tearing my hair out here!!
Many Thanks in Advance
Completely and totally stumped
This started yesterday. Never rooted this tablet, no custom roms, totally stock (it's my daughters); I decided to check for updates. All there was was a 'Google security update' or something like that. I was on JB already. So I installed the update and the tablet decided it had to restart and since then it had just gone into a bootloop (constant Nabi splash screen)... So I've follow instruction to get the TWRP recovery (2.6.3.0) on here via fastboot flash and I can boot into there just fine. I cannot mount anything on internal storage. I have 2127 & 2311 stock backups set up on an ext flash drive in the TWRP backup folder and can see it when I go to restore in TWRP, but they both fail because they 'cannot find partition size for boot'. No matter what I do I cannot mount anything from internal storage. I'm at the point where I think internal is corrupt. There's no OS. It shows Internal Storage (0MB) as well.
Anyone have any ideas at what I might be up against here or what I can do?
sandrewmorrison said:
This started yesterday. Never rooted this tablet, no custom roms, totally stock (it's my daughters); I decided to check for updates. All there was was a 'Google security update' or something like that. I was on JB already. So I installed the update and the tablet decided it had to restart and since then it had just gone into a bootloop (constant Nabi splash screen)... So I've follow instruction to get the TWRP recovery (2.6.3.0) on here via fastboot flash and I can boot into there just fine. I cannot mount anything on internal storage. I have 2127 & 2311 stock backups set up on an ext flash drive in the TWRP backup folder and can see it when I go to restore in TWRP, but they both fail because they 'cannot find partition size for boot'. No matter what I do I cannot mount anything from internal storage. I'm at the point where I think internal is corrupt. There's no OS. It shows Internal Storage (0MB) as well.
Anyone have any ideas at what I might be up against here or what I can do?
Click to expand...
Click to collapse
Usually a sign u flashed ICS TWRP instead of JB.
aicjofs said:
Usually a sign u flashed ICS TWRP instead of JB.
Click to expand...
Click to collapse
Can you tell me the version numbers of each version? I believe I have tried both. Both have told me I have no OS installed, cannot mount any internal anything, can't format it, and doesn't show any internal storage space. It comes up as 0mb.