Hi,
this is my first post on xda and first Android device well actually it's a present for my daughter. First i'd like to say that you guys doing a great work here! Thank you!
Last couple of days (and nights) I spend reading and reading and reading.. http://forum.xda-developers.com/showthread.php?t=1905674 - now 101 pages! I am not in UK or US or any other country where nabi app shop is working, the only option for me is G play store. So rooting and installing gapps is the way for me. Unfortunately jmztaylor's method not working for me. Not only for me on page 26 (http://forum.xda-developers.com/showthread.php?t=1905674&page=26) mr_tris reported of having the same problem, but never got a solution for it and I see that MikeDVH (http://forum.xda-developers.com/showpost.php?p=35985909&postcount=1020) just reported the same issue:
failed to mount data (invalid argument)
-- Could not mount :/sdcard
-- Aborting
Backup failed!
I am getting the same error. There is plenty of free space (3+GB) and 2GB SD card. No apps on tablet, just configured Nabi mode.
The only explanation I can come up with that it's something different in UK model of Nabi2. The model reads: NABI2-NV7A-UK
My Nabi2 came with 1.9.29 and before attempting to root I upgraded to 1.9.37
I am thinking to trying http://forum.xda-developers.com/showthread.php?t=2041224 flash with his supplied stock version 1.9.37, but don't wanna mess something. I can supply any additional information or images needed, but to be honest will need some guidance in doing that as not very familiar with all this flashing thing, but not afraid of CLI
I can not post in that thread, but maybe it will be good to have thread dedicated to UK version of Nabi 2. Any other Nabi2-UK owners having problems/success?
regards
p.
petras_m said:
Hi,
this is my first post on xda and first Android device well actually it's a present for my daughter. First i'd like to say that you guys doing a great work here! Thank you!
Last couple of days (and nights) I spend reading and reading and reading.. http://forum.xda-developers.com/showthread.php?t=1905674 - now 101 pages! I am not in UK or US or any other country where nabi app shop is working, the only option for me is G play store. So rooting and installing gapps is the way for me. Unfortunately jmztaylor's method not working for me. Not only for me on page 26 (http://forum.xda-developers.com/showthread.php?t=1905674&page=26) mr_tris reported of having the same problem, but never got a solution for it and I see that MikeDVH (http://forum.xda-developers.com/showpost.php?p=35985909&postcount=1020) just reported the same issue:
failed to mount data (invalid argument)
-- Could not mount :/sdcard
-- Aborting
Backup failed!
I am getting the same error. There is plenty of free space (3+GB) and 2GB SD card. No apps on tablet, just configured Nabi mode.
The only explanation I can come up with that it's something different in UK model of Nabi2. The model reads: NABI2-NV7A-UK
My Nabi2 came with 1.9.29 and before attempting to root I upgraded to 1.9.37
I am thinking to trying http://forum.xda-developers.com/showthread.php?t=2041224 flash with his supplied stock version 1.9.37, but don't wanna mess something. I can supply any additional information or images needed, but to be honest will need some guidance in doing that as not very familiar with all this flashing thing, but not afraid of CLI
I can not post in that thread, but maybe it will be good to have thread dedicated to UK version of Nabi 2. Any other Nabi2-UK owners having problems/success?
regards
p.
Click to expand...
Click to collapse
i get the same error! any help would be great
Nabi 2 - UK Root and Gapps Install
After some more tries I finally rooted my nabi2-UK and successfully installed gapps!
Original files and credit go to jmztaylor from this thread: http://forum.xda-developers.com/showthread.php?t=1905674
New gapps and credit (no "Android Upgrading" message every reboot) go to t499user: http://forum.xda-developers.com/showthread.php?p=35888524 and manual recovery and flash http://forum.xda-developers.com/showthread.php?t=2016463
I’ve done “semi manual/automatic” if you can say that. So the steps were:
1. From http://junefabrics.com/android/ installed PdaNet for Android to have all proper drivers. My system win 7 64
2. set everything according http://forum.xda-developers.com/showthread.php?t=1590800
3. ran jmztaylor insatall.bat and selected option 2
4. in the background watching http://www.youtube.com/watch?v=HcAIsePNYVE – found some very useful notices – Thanks!
5. followed till the end, with the error: failed to mount data (invalid argument) and -- Could not mount :/sdcard
6. in TWRP selected Backup and done backup to external SD card
7. nabi being still in TWRP on pc opened command prompt and run:
Code:
adb push root.zip /sdcard/root.zip
and
Code:
adb push gapps.zip /sdcard/gapps.zip
8. In TWRP selected Install, navigated to /sdcard and selected root.zip after it was installed, the same done for gapps.zip
9. rebooted, run superSU, google play was installed, downloaded root checker – Congratulations! This device has root access!
Rebooted several times – everything ok.
I believe that this can be done in a better way, but this is just my experience and maybe it will help someone.
Sorry if some may sound in proper – English is not my native language
Happy New Year!
THANKYOU
petras_m said:
After some more tries I finally rooted my nabi2-UK and successfully installed gapps!
Original files and credit go to jmztaylor from this thread: http://forum.xda-developers.com/showthread.php?t=1905674
New gapps and credit (no "Android Upgrading" message every reboot) go to t499user: http://forum.xda-developers.com/showthread.php?p=35888524 and manual recovery and flash http://forum.xda-developers.com/showthread.php?t=2016463
I’ve done “semi manual/automatic” if you can say that. So the steps were:
1. From http://junefabrics.com/android/ installed PdaNet for Android to have all proper drivers. My system win 7 64
2. set everything according http://forum.xda-developers.com/showthread.php?t=1590800
3. ran jmztaylor insatall.bat and selected option 2
4. in the background watching http://www.youtube.com/watch?v=HcAIsePNYVE – found some very useful notices – Thanks!
5. followed till the end, with the error: failed to mount data (invalid argument) and -- Could not mount :/sdcard
6. in TWRP selected Backup and done backup to external SD card
7. nabi being still in TWRP on pc opened command prompt and run:
Code:
adb push root.zip /sdcard/root.zip
and
Code:
adb push gapps.zip /sdcard/gapps.zip
8. In TWRP selected Install, navigated to /sdcard and selected root.zip after it was installed, the same done for gapps.zip
9. rebooted, run superSU, google play was installed, downloaded root checker – Congratulations! This device has root access!
Rebooted several times – everything ok.
I believe that this can be done in a better way, but this is just my experience and maybe it will help someone.
Sorry if some may sound in proper – English is not my native language
Happy New Year!
Click to expand...
Click to collapse
Just wanted to say thanks to you and everyone on this site! i had a bit of trouble rooting my daughters nabi 2, but thanks to you i got it sorted!
Happy new year!!
:laugh::laugh:
easytiger1978 said:
Just wanted to say thanks to you and everyone on this site! i had a bit of trouble rooting my daughters nabi 2, but thanks to you i got it sorted!
Happy new year!!
:laugh::laugh:
Click to expand...
Click to collapse
Glad to hear that it worked for you. There is an updated recovery with various fixes so all that still have, in first post mentioned error, might wanna try http://forum.xda-developers.com/showthread.php?p=36083895#post36083895
Just replace recovery.img and gapps.zip in jmztaylor Files directory with new ones and try.
petras_m said:
Glad to hear that it worked for you. There is an updated recovery with various fixes so all that still have, in first post mentioned error, might wanna try http://forum.xda-developers.com/show....php?t=2074501
Just replace recovery.img and gapps.zip in jmztaylor Files directory with new ones and try.
Click to expand...
Click to collapse
I think that link is broken?
easytiger1978 said:
I think that link is broken?
Click to expand...
Click to collapse
updated link
failed to install / invalid argument whilst pushing root and Gapps on Nabi 2
A huge thank you for the 'how to' and files to help me root my nieces Nabi 2! ;0) I successfully rooted and installed Google apps, although I did it differently to the above methods.
(I'm using windows 8 and the Nabi 2 was already on 1.9.37. The device shows as NABI2-NV&A-UK under my computer)
I kept stalling at the point after the files were being pushed to the SD card. I also had the 'invalid argument / failed transfer' message flash up on the Nabi for a split second, and then hanging as the Nabi was disconnected from my laptop, until a reboot was done; but then it was not in developer mode. After going round in circles and reading for about an hour and a half (and watching the helpful video on youtube), and then coming here to see the above post, I tried the command prompt push method but still no joy! When I tried that method the files being pushed would show up on the Nabi screen but they would not install, there was also an error message after each attempt (I cannot remember exactly what it said now, sorry).
Two hours later and still no luck. Then I thought 'what if I did it this way' > ... I rebooted the Nabi 2, with a 2gb SD card in it. I opened 'my computer' and formatted the SD card. I dragged and dropped the Root.zip and Gapps.zip files to the root of SD card. I ran the adb driver app, via the command prompt (which in windows 8 can be accessed by pushing the windows key and X, then choosing 'command prompt' as there's no link for it in accessories) and then I ran the jmzrootpack 'install.bat' file to get the Nabi into developer mode. Then I entered install via the menu and the files were there! I installed the root and gapps files as in the youtube video, rebooted and everything was installed and worked as it should. Job done!
Once again thank you to the developers who made this possible ;0)
Related
Hello everyone. Let's see if anybody can help me, because I'm pretty stuck with this.
Note: I've already searched high and low for solutions to the "Signature verification failed", but they either don't work or don't apply here.
I've tried to install the following ROM from xda-developers in a Sanei N10:
Unofficial CyanogenMod 10 for many AllWinner A10 tablets
I've installed it following the usual procedure:
- Press Vol+ and Power to get the Recovery menu
- Select Wipe data/factory reset
- Select Wipe cache
- Install the three ZIP files: "cm10_a10_20120913.zip", "gapps-jb-20120726-signed.zip" & "n10_compatibility_1.2.1.zip"
The problem is, even though the first ZIP with the ROM installs successfully, the second one (the one with Google's apps) refuses to install, showing instead the message "signature verification failed". The same happens with the third ZIP (N10 compatibility).
So the installation doesn't actually finish. If I reboot the tablet, it runs Cyanogenmod 10, but the touchscreen doesn't work (I have to plug a USB mouse to interact with the operating system).
So what do I do to avoid the dreaded "signature verification failed" message? Just in case if it's of any help to identify the problem, I'll mention that I can see the Android bot laying down with a red triangle with an exclamation when entering the Recovery menu.
I've tried to use the ROM Manager which is preinstalled with Cyanogenmod 10, but when choosing "Flash ClockworkMod Recovery" it says that "The SD Card needs to be mounted to use ROM Manager". Of course my MicroSD is properly mounted (I can see its files in the card from console, from the "Terminal Emulator"). I think this happens because the MicroSD is mounted in /storage/sdcard1 instead of in /storage/sdcard0, but I can't change that. I can't download APKs from the browser, either, because it also says something similar about not being able to access the SD (even though it's correctly mounted and can see it mounted from Settings > Storage).
I've also tried the CyanogenMod A10 ROM available in this page, which is more recent (October instead of September):
http://www.slatedroid.com/topic/3870...mod-10-tweaks/
But the same happens.
I've even tried installing the CWM Recovery ROM, but it doesn't let me installing that from the Recovery either (same message about the "signature"), and with Odin3 it doesn't work either because I don't know how to reach the "download mode", which is needed for Odin3. Pressing Vol+ and Power I get the Recovery, but not the Download mode. Does anyone know how do I get to the download mode in the Sanei N10?
Any idea about how to solve this? Right now I have a tablet with no touchscreen and not even Google applications (so I don't even have the Play Store), so it's practically worthless (at least the WiFi works). How can I get this tablet back to being usable?
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
benny6812 said:
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
Click to expand...
Click to collapse
No, unfortunately I still couldn't fix it
There's nobody here in xda-developers who can help me? Surely somebody must know enough to help me find a solution.
I've tried creating a symbolic link from /storage/sdcard1 to /storage/sdcard (it doesn't exist right now), but it just says "link failed Read-only file system" (I was root, by typing "su" and clicking "Allow" in the Superuser window). So, I can't create symbolic links even while being root user? I need this link so ROM Manager can detect my SD Card (it says it's not mounted but it really is, but in "/storage/sdcard1").
Also, the gapps package linked in the ROM page above seems not to be properly signed, even though it has that "-signed" suffix in its name. I always get that "signature verification failed" error message. But now I've tried downloading a more recent gapps package (gapps-jb-20121011-signed.zip) and that package finally worked! BUT, even though it apparently installed successfully, I still can't see any Play Store icon, nor any other Google app (Gmail, etc.). Why? Those icons should appear after installing gapps, shouldn't they? Maybe this newer "gapps" package is somehow incompatible with this tablet? (is this even possible?).
Also, even though I can now install the newer "gapps" package, I still can't install the "n10_compatibility_1.2.1.zip" file (I still get "signature verification failed" for that ZIP), which, I guess, contains the drivers needed for the N10 so the touchscreen works (currently it doesn't, and I have to use a USB mouse to use Android in this tablet). Any ideas? I'm getting tired of trying 9485738489754935627 things with no good result . I guess Android is showing here its Linux roots...
I think the key here is managing to install a new Recovery ROM that doesn't care about signing, but how do I do that? I can't install through ROM Manager because I get that error about the SDCard needing to be mounted to use it (and it's really mounted), and then I can't create the /storage/sdcard symbolic link because I get that "link failed Read-only file system" error. Also, I can't use Odin3 because I can't manage to put this tablet in Download Mode. Aaaargh! There's no good solution
Any ideas?
Bump!
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Yojimbojpr said:
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Click to expand...
Click to collapse
Thanks for replying. If we could find some way to install a new Recovery, then we'd probably by able to get the N10 Compatibility file working. This can't be that hard to do, but I've tried lots of things, and none of them worked...
Anyone?
Please, someone help!
Bump!
No ideas?
Please, I'm getting desperate
sanei
OMA2k said:
No ideas?
Click to expand...
Click to collapse
same problem here....
jamjamjan said:
same problem here....
Click to expand...
Click to collapse
Please let me know if you find a solution to this. Thanks!
I'm having the same issue with [ROM][CM10/10.1][21 Dec] Codename Lungo
Well, at last I could finally solve the problem thanks to chris5s from this forum.
These are the steps that worked for me:
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/showthread.php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!
I hope this helps somebody else!
hey i just registered because i have been having the same exact problem i read that you fixed it but how can i get in to the tablet if im not able to do any movements after it boots ???
please any help would be appreciated
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Thatgrass said:
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
i did i just dont know how to get in to the terminal app
ok so im in the terminal app but what do you mean by modify the install sh file ???
Hello "lesanei"
I just noticed your posts. Let's see if I can help you...
The touchscreen doesn't work because the appropriate drivers were not installed (because of the "signature verification failed" issue). So you need to connect a USB mouse (and preferably a keyboard too) to the tablet. The Sanei N10 should come with a USB to micro-USB adapter. If you don't have it, you can buy it for cheap here.
Since there is only the one USB input in the tablet, you can't connect two USB devices at the same time. What I did use is a wireless mouse+keyboard combo which only needed one USB dongle for reception. If you don't have that, you can just connect a USB mouse and type with the on-screen-keyboard using the mouse. It's annoying, but it works
When I say "modify the install-recovery.sh file", I mean the file inside "cwm_recovery_6.0.1.2_a10.zip". You can modify it from your PC if you prefer. You don't have to do it in the tablet if you don't know how to use the "vi" editor (command line editor). Just open the "install-recovery.sh" file in Wordpad (do not use the Notepad, because it doesn't support Unix line endings so it shows the file incorrectly) and replace all instances of "/sdcard" with "/mnt/extsd". So the file contents should look like this:
#!/system/bin/sh
if busybox test ! -f /mnt/extsd/recovery.img; then
echo no /mnt/extsd/recovery.img
exit 1
fi
cat /mnt/extsd/recovery.img > /dev/block/nandg
sync; sync; sync
echo done
Click to expand...
Click to collapse
Then place all three files ("recovery.img", "install-recovery.sh" and "reboot-recovery.sh") into your MicroSD card. Then safely extract it from your PC, insert it in the tablet and type this from the Terminal:
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
Click to expand...
Click to collapse
Then follow the regular steps to install Cyanogenmod and this time all files should install sucessfully, so when rebooting, touchscreen and everything else will work.
Let me know if it works for you.
I purchased a NT from a guy on Craigslist who said it was bricked. Since I have installed CM10 on a number of NC and NT I thought I would take a chance and buy it. When you turn it on, after the N is displayed, it momenteriarly displays what looks like the opening the Reading Forever page. Then is goes to a Red exclamation point that says to restart your device and try again.
I have tried booting from a CWM boot disk. It says it can't find E: when I try a data/factory reset, I suspect the partitions are meesed up. What is my best course of action at this point?
Bonnie_Raitt said:
I purchased a NT from a guy on Craigslist who said it was bricked. Since I have installed CM10 on a number of NC and NT I thought I would take a chance and buy it. When you turn it on, after the N is displayed, it momenteriarly displays what looks like the opening the Reading Forever page. Then is goes to a Red exclamation point that says to restart your device and try again.
I have tried booting from a CWM boot disk. It says it can't find E: when I try a data/factory reset, I suspect the partitions are meesed up. What is my best course of action at this point?
Click to expand...
Click to collapse
Bad choice on your part because the device information may be gone. But there is a guide to rebuilding the internal partitions here.
Try it out and see if it works. I've never tested any unbricking methods because, well, I've never been bricked. Important to read instructions carefully before doing anything and make sure you're knowledgeable on what you're doing.
It appears that I need to know whether I have an 8 or 16 Gb model. Is there a way to tell if I can't boot it?. TIA
Bonnie_Raitt said:
It appears that I need to know whether I have an 8 or 16 Gb model. Is there a way to tell if I can't boot it?. TIA
Click to expand...
Click to collapse
Ask the guy from craigslist or open up the back and look at the hardrive and see what it says.
No way to contact CL guy. Is opening up the device the only way to find out?
Bonnie_Raitt said:
No way to contact CL guy. Is opening up the device the only way to find out?
Click to expand...
Click to collapse
You'll have to open it up then. Only difference is the "hard drive" is 16 GB and the ram is 1 GB instead of half a gig.
I was able to contact seller. He says it's a 16 GB model. I'm off to try the fix listed above
I downloaded flash_restore_16gb_partitions_1-4&6.zip, put it on my CWM boot card, and chose it from "install zip from sdcard.. Here's what is says:
Installing flash_restore_16gb_partitions_1-4&6.zip
E: Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package
Opening update package
Installed update...
Extract xloaded
extract U-boot
extract recovery
extract Boot
Extract Bootdata
Install from sdcard complete
I then powered down NT.
Took a 4 GB SD card that had a single partition marked active with EASEUS Partiton manager. Copied nooktablet_1_4_2_update.zip to it. Inserted it in NT and rebooted
It flashes momentarily to reading fowever screen, then goes to updating software screen. Very quickly a red exclamation point appears asking me to restart to try to install software again. Restarting gives same results.
Should I move on to the ADB process or is there something else I can do at this point
Bonnie_Raitt said:
I downloaded flash_restore_16gb_partitions_1-4&6.zip, put it on my CWM boot card, and chose it from "install zip from sdcard.. Here's what is says:
Installing flash_restore_16gb_partitions_1-4&6.zip
E: Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package
Opening update package
Installed update...
Extract xloaded
extract U-boot
extract recovery
extract Boot
Extract Bootdata
Install from sdcard complete
I then powered down NT.
Took a 4 GB SD card that had a single partition marked active with EASEUS Partiton manager. Copied nooktablet_1_4_2_update.zip to it. Inserted it in NT and rebooted
It flashes momentarily to reading fowever screen, then goes to updating software screen. Very quickly a red exclamation point appears asking me to restart to try to install software again. Restarting gives same results.
Should I move on to the ADB process or is there something else I can do at this point
Click to expand...
Click to collapse
Have you tried the repart.img?
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
If you get the red x during that process you can try adb process.
Sent from my NookTablet using xda app-developers app
datallboy said:
Have you tried the repart.img?
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
If you get the red x during that process you can try adb process.
Sent from my NookTablet using xda app-developers app
Click to expand...
Click to collapse
Yes,that's actually what I tried at first. It doesn't work.
At this point I'm trying to load the ADB tools and drivers,
In [FAQ] NT Reference Thread | Tips&Tricks | How to's | Videos | NEW USER? PLEASE READ!
it references a link [HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial .
The video for windows doesn't work any more. I went ahead and downloaded the referenced
ADB + Fastboot + Drivers.zip
I made an attempt to load the uSB drivers. I'm not certain if I did it correctly or not. When I run the adb devices command is get nothing returned.
Can someone point me to a current reference for installing the drivers or offer more advice on where to go from here. Thanks
Bonnie_Raitt said:
Yes,that's actually what I tried at first. It doesn't work.
At this point I'm trying to load the ADB tools and drivers,
In [FAQ] NT Reference Thread | Tips&Tricks | How to's | Videos | NEW USER? PLEASE READ!
it references a link [HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial .
The video for windows doesn't work any more. I went ahead and downloaded the referenced
ADB + Fastboot + Drivers.zip
I made an attempt to load the uSB drivers. I'm not certain if I did it correctly or not. When I run the adb devices command is get nothing returned.
Can someone point me to a current reference for installing the drivers or offer more advice on where to go from here. Thanks
Click to expand...
Click to collapse
I have no idea how to set up ADB, never done it. So I won't be able to help you there. Sorry.
But since it is a 16GB version you may want to attempt the Adam Outler Ubuntu ReFlash Method. It uses ubuntu to recover your partitions on your device. Since you have nothing to lose with it, give it a try.
If someone else doesn't pipe in, I'll try it this afternoon
OK. I downloaded ADB stuff from
HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - TutorialLike Tweet +1
I placed everything i c:\adb. I followed instructions and now have an "Othe device" called Barnes and Noble Nook Tablet". It has an exclamation point. I have uninstalled and reinstalled several times to no avail. I am running Windows 7 SP1 64 bit intel.
I'm at a dead end here. Can anyone assist?
Just finished reading
[UnBrick]TOTAL WIPE and reflash back to 1.4.0 via Ubuntu Recovery --Now Easier!!!!
It looks like something I could do, but I'd like some feed back from the experts before I bork my NT worse than It already is. Any thoughts?
Bonnie_Raitt said:
Just finished reading
[UnBrick]TOTAL WIPE and reflash back to 1.4.0 via Ubuntu Recovery --Now Easier!!!!
It looks like something I could do, but I'd like some feed back from the experts before I bork my NT worse than It already is. Any thoughts?
Click to expand...
Click to collapse
Well your nook is already borked up. You bought it with the internal partitions deleted most likely. This method writes zeros and rebuild the partitions itself.
Bonnie_Raitt said:
OK. I downloaded ADB stuff from
HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - TutorialLike Tweet +1
I placed everything i c:\adb. I followed instructions and now have an "Othe device" called Barnes and Noble Nook Tablet". It has an exclamation point. I have uninstalled and reinstalled several times to no avail. I am running Windows 7 SP1 64 bit intel.
I'm at a dead end here. Can anyone assist?
Click to expand...
Click to collapse
You might find some helpful info/pointers re: setup for ADB access over USB at http://forum.xda-developers.com/showpost.php?p=35971559&postcount=13.
I got ADB drivers loaded and started at looking at trying to find out which partition is borked and how to fix. I started with http://forum.xda-developers.com/showthread.php?t=1531120,
When I tried somto delete and recreate partitons 10 and 11 I got a number of errors messages. I'm still looking for a "how to" when dealing with partitions. If anyone wants to hold my hand I would be grateful.
BTW, I tried the Ubuntu boot disk but could never get it to boot.
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!
Hi all,
to make it plain and short: I messed up.
I have a GT-S5830i which I unrooted according to the Sticky Note in the forum, installed CWM Recovery and then 'installed from ZIP' a CM9_cooperve_Beta_05.zip that I found in one of the posts in the forum. The installation went on without error message but since then the phone does not make it beyond the initial screen "Samsung Galaxy Ace GT-S5830i". I can start recovery mode and Download mode. In reovery mode I can format cache, data, sdcard, sd-ext but *not* system. Error Message: "E: format_volume: make_ext4fs failed on /dev/block/st19"
I have tried already several methods according to the forum, e.g.
1) 'install from ZIP' older Cyanogenmod
2) the tool ext4_formatter.zip
3) re-flash with ODIN with several tar-ROMs, all failed. Odin finds the phone (since I start Odin as Admin now), but after I hit 'start' it tries to establish a connection to the phone and ends after a while with 'Failed'
I'm basically lost now, don't know what else to do. Any advise is appreciated (it's my mom's phone, she is getting impatient )
Thx, cheers!
Xala
Hi @xalarsk , So you can't format your /system partition , which is required for installation of your rom ,, you need to try this method from here mate . Follow my instruction from the line @post#4 :"1. Download one of the newest ,,," to the end of the post and please do not use CM9 beta , because it is unstable and will wreak havoc with your system eventually . ( either cm7 or cm11 is the place you should go for CyanogenMod experience for cooperVe device ).
If you fail at any level please give us your logcat ( error massage ) for better support for your Odin process you mentioned .
Cygwin not working
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
xalarsk said:
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
Click to expand...
Click to collapse
Cygwin was meant for windows platform to get the native Linux environment/command line you already got there . You can create a virtual instance of the windows 7 inside virtualbox or any kind of apps you are preferring such as Vmware/Parallel etc etc to get the job done .
Splitfus2 only supports windows platform as far as i know mate,,, either vitalization as i said or the pre-made zip package ( which is clearly not .exe file ,, push the download now and get yourself a descent downland manager,, tested and zip packaged delivered ) from here is the feasible approach for your problem .
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
xalarsk said:
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
Click to expand...
Click to collapse
Another fellow had similar issue with my attachment that was corrected here @ post#27
Unbricked, SD card not recognized
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
xalarsk said:
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
Click to expand...
Click to collapse
Mostly this happened because of the bug inside CM9 beta you used . Study this topic mate i troubleshooted while ago for a sample of the symptoms external SD card would show after unstable ICS usage .
Also as an alternative to the method i instructed there , you can format/Re-partition your SD card by putting it inside card reader and using app such as free MiniTool Partition Wizard "Gparted" tool for Linux users Or "iPartiton" for Mac users etc etc ,, to get the job done . You can find several tutorials inside XDA for this matter mate.
Phone works with CM7.2, can I upgrade to CM9?
Hi again,
first of all, props to @ehsanotaku, I will hit the 'Thanks' buttons.
Now, this is a bit beyond the topic, but I'd like to ask anyway for recommendations of CM9 roms. The one I picked from a post inside this forum bricked my phone and made me start this thread, I don't want to go down this road again. So I'd be glad for any recommendation of a stable ROM that will put my phone beyond Android 4.0.
Cheers again,
Xala
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
hojnikb said:
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
Click to expand...
Click to collapse
ok not going to excruciating details of symptoms and explaining all of your errors for now just please read my advice @ post2 of this topic and follow the procedures accordingly and finished it with formatter tools and cm7 instructions you will find there ., after that you can install Kitkat Smart R2 like you are coming from another CM7 build instruction . btw some problem regarding super user privileges and play store 492-498 infamous bug was reported for this fairly new development .
Hello everybody, I'm just new here. I need your wise help with a Lenovo S820e.
First of all, the story: Got a Lenovo S820e from a chinese guy. Received a smartphone with lots of chinese garbage on the rom including pornography and things like that, so I decided to look for some guides to reinstall an official ROM for this Lenovo. Honestly I'm a beginner with these things and took me a while after realizing how to do all the proccess.
After reading some basics and check some youtube videos, I went to NeedROM website and looked for this ROM:
***can I post a link?***
Realized that this is the only ROM version (some updates here) but finally the only one that I've found on the internet.
I followed the steps (took me some days, lol) to update via sdcard posted on that ROM link (here the steps):
Install ROM:
Need a memory card, create folder sdfuse and copy to install on this ROM (QSB tailed).
a) normal phone boot into Android OS, use a USB cable to connect PC, the pop-up screen, select USB mass storage devices, and turn on USB storage device;
b) New sdfuse folder, unzip the downloaded firmware, and copied file QSB to the phone sdfuse directory;
Note: Make sure before upgrading phone there is a certain amount of power
2. T card upgrade process
Long press VOLUP + POWER_KEY enter droidboot, a menu appears and select the fourth SDUPDATE, the bottom of the screen you can see the progress and status upgrade
See "SDCARD UPDATE SUCCESS!!!" Indicates a successful upgrade
After some tries, realized how to enter that droidboot (Volume down + power button... after seeing the lenovo logo release the power button). :good:
To shorten this story I finally got a "Lenovo S820e android 4.1.2" with an official ROM, rooted (to get rid of these chinese apps, no offense intended) and without google apps. Here is the part where I spent another few days to install gapps because didn't accomplish with adb loader, cwm recovery, etc.
So I found this guide (russian site, translated with google help) on how to install google apps without CWM, a something like a manual installing:
****????****
Installed the root explorer and copy-pasted the system files to the internal storage, permissions and rebooted the device.
But after boot I got a look-a-like, useless "Assistive touch-thing-app" ( I don't know exactly what is ) that I cannot find how to uninstall it. Note that this was after (at last) installing gapps (20121011 signed, hard to find the correct version for this Lenovo S820e )
Video: https: //youtu.be/ yhIwf3OHAUU
Can I post a youtube video please? I have uploaded a video with my problem. Help me please. Got denied access because I'm a NEW member here.
I need help, if someone have seen something like this "assistive touch-thing" and know how to uninstall / deactivate it will be great and I will pray for you :fingers-crossed:
I don't know i I'm too newbie.
Sorry if I have grammar errors or bad english. I'm not native.
Thank you in advance.
Best Regards.