first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
perch_44 said:
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
Click to expand...
Click to collapse
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
flumpster said:
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
Click to expand...
Click to collapse
If that fails, I had the same issue with cwm, I installed twrp via fastboot and haven't had the problem of the file not showing up after adb push. Fustrating I know.... I tired everything I could think of in cwm multiple reboots different usb ports... on an on......
Please HELP CWM Roocovery Loop!!!
perch_44 said:
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
Click to expand...
Click to collapse
I am having the same exact problem. It started when I tried to restore my stock backup that I made using CWM 5.8.2.0 coming from the CM rom. I am stuck in the CWM recovery screen and cant get ADB to see the TF Prime. I just get error: device not found. How did you manage to push a zip if ADB wasn't seeing your device? I have been looking for a fix for the last week now.
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Danny80y said:
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Click to expand...
Click to collapse
How do I flash TWRP when Im stuck CWM?
hellshavoc said:
How do I flash TWRP when Im stuck CWM?
Click to expand...
Click to collapse
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Striatum_bdr said:
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Click to expand...
Click to collapse
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
hellshavoc said:
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
Click to expand...
Click to collapse
you hold the volume down until the screen starts, then you let go and wait
whycali said:
you hold the volume down until the screen starts, then you let go and wait
Click to expand...
Click to collapse
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
hellshavoc said:
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
Click to expand...
Click to collapse
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
It is confusing but just keep trying till you get it!! Once there go to the TWRP site they have the file and the fastboot commands all set in a guide.
I have exactly the same problem than you.
I had the fastboot/adb connection (I used to push the rom by adb), but i tried to install a wrong version on gapps. Since then, I'm stock in the recovery mode without adb/fastboot connection.
If you find a solution for that, pleaze post it !!
Striatum_bdr said:
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
Click to expand...
Click to collapse
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
slide mon said:
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
Click to expand...
Click to collapse
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
haxin said:
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
Click to expand...
Click to collapse
I was trying to downgrade the phone to ICS using the factory image from google. I picked the wrong image from the google site (picked soju, needed sojus) and flashed it using fastboot. As soon as I flashed the wrong bootloader the USB connection stopped working so I didn't flash the radio or os. I no longer can connect to the phone using fastboot or adb, usb debugging stopped working. The USB debugging option is set in developer options. So, trying to get the phone working now without USB. Hope that makes sense now. :good:
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
Ok, so I attempted to root a Nabi 2 so I could use the SD card to hold apps since the onboard memory is terrible and I bricked the dang thing. I unlocked root supposedly using a one click app method, then I was able to attempt to update using the updater already on the Nabi. During the reboot, thats when it bricked. It is stuck in a constant boot loop mode that eventually ends up on a dead android screen.
My main problem is I know there has got to be a way to restore a stock rom/os on it, but every how to guide out there assumes that I already know what the hell they are talking about. SDK, ADB, HIV, STD, its irritating. Also, I tried TWRP, ADB, etc. but since the Nabi is in a constant boot loop and dead android screen, I can't get my PC to recognize it for more than 5 seconds. Is there a step by step guide to what I need to do for a novice? Like step 1. "since your PC can't recognize the device in the first place this is where you start". Step 2, use "this program, then this, and this is why".
Can anyone out there help me get pointed in the right direction? I am tech savvy but the existing guides assume too much, have broken links, and don't say anything about what to do when you can't even get your device to be recognized.
Thanks
Aaron
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Higher-Primate said:
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Click to expand...
Click to collapse
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
aicjofs said:
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
Click to expand...
Click to collapse
I want to say it was running 4.1 or 4.2 but I'm not positive. Stupid me should have written it down. Is it possible to load any of the versions now that I have wiped it? I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen. From there I did a - and + and got an option to side load recovery or boot to ADB I think it was. So since I can at least get there, is there anything I can do? Other than that, TWRP won't recognize it and says no drivers are loaded. I'm assuming because I can't get the Nabi to stay stable long enough to actually load anything on to it? The device recognizes for a few seconds then disappears.
Higher-Primate said:
I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen.
Click to expand...
Click to collapse
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
aicjofs said:
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
Click to expand...
Click to collapse
Ok, I tried fastboot, but it doesn't really do anything. Once I go into fastboot, I have more options. Bootloader, continue, reboot bootloader, reboot, and power off. None of the options allows the Nabi to show up as a device in device manager. Everything just takes me to the dead android unfortunately.
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Higher-Primate said:
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Click to expand...
Click to collapse
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
aicjofs said:
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
Click to expand...
Click to collapse
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Higher-Primate said:
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Click to expand...
Click to collapse
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
aicjofs said:
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
Click to expand...
Click to collapse
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Higher-Primate said:
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Click to expand...
Click to collapse
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
aicjofs said:
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
Click to expand...
Click to collapse
No problem at all. Ok, that seemed to have done something. I put in the exact one you just changed above, and I rebooted normally, now I have a TWRP screen on the Nabi display. Now, what instructions do I need to follow? Do I still use NabiLab2015, if so the Disney/Nick or NV7A - US? Both now say "TWRP +mount:mounting /system on ext4 failed: no such file or directory.
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Higher-Primate said:
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Click to expand...
Click to collapse
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
aicjofs said:
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
Click to expand...
Click to collapse
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Higher-Primate said:
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Click to expand...
Click to collapse
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
aicjofs said:
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
Click to expand...
Click to collapse
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Higher-Primate said:
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Click to expand...
Click to collapse
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-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 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- 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 3013stock.zip file 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 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- 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 on the external SD card 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 KK3013bootloader.zip you downloaded and install it.
- Reboot
aicjofs said:
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-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 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- 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 3013stock.zip file 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 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- 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 on the external SD card 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 KK3013bootloader.zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
What happens if it won't let me create the backup folder? It errors out and says it can't create one.
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.