Related
Okay guys here's the dealio-
I recently got my transformer prime and I *loved* it. It came pre-loaded with the .21 version of ICS, which can't be rooted as of now so I downgraded to stock .15 with a modified ViperMod and then rooted and installed CWM. Next, I installed the Gummy custom ROM onto my prime (still .15). Well, I started to experience some weird -probably ROM related- issues and I ended up deciding to flash back to stock. ...BIG MISTAKE on my part I found out! I used the modified ViperMod to flash back to the stock .15 and it ran through the process but stopped at the ASUS boot logo with the little loading circle going around and around and around. First I let it sit for a VERY long time-stuck on boot. Then, I tried turning it off and back on-stuck on boot. Next, I tried pushing down the little recovery button-stuck on boot. I tried booting into CWM, but obviously, since I flashed back to the stock .15, all I get is the android guy laying in his side with the red triangle.
I am really really hoping that this is not a hard brick because the error that people are describing is the tablet stuck in the screen with "EeePad" in the middle and then getting something about an "unrecoverable bootloader error". My tablet boots past the EeePad screen and there is no error message-just the endless loading circle.
I am hoping that one of you smart guys could have a clue on how to revive my tablet. Any help would be greatly appreciated, and maybe I can buy you a beer if you bring my baby back to life
Here is a picture of what it looks like (circle is still spinning):
http://img838.imageshack.us/img838/276/img20120322182429.jpg
so you can get into recovery? I saw you said you tried to flash cm9 again. if you caught in a bootloop, jemaine made a zip file you can flash to get you out of it. you have to search for it though in developement section. does your computer still recognize your prime when you hook it up to your computer? you may need to adb commands into prime.
good luck getting it back running.
demandarin said:
so you can get into recovery? I saw you said you tried to flash cm9 again. if you caught in a bootloop, jemaine made a zip file you can flash to get you out of it. you have to search for it though in developement section. does your computer still recognize your prime when you hook it up to your computer? you may need to adb commands into prime.
good luck getting it back running.
Click to expand...
Click to collapse
I no longer have cwm installed, it is just the stock recovery so I cannot install any .zip's. Also, when I plug the tablet in wile its on the Asus loading screen, the computer DOES recognize it. Maybe there is some way to get into it and reflash?
Any suggestions guys?
seanyuan62 said:
Any suggestions guys?
Click to expand...
Click to collapse
When you say your pc can see the prime can you see it with adb? If not go here:
http://forum.xda-developers.com/showthread.php?t=1426502
Once you have adb figured out you should be able to reflash recovery. See this thread:
http://forum.xda-developers.com/showthread.php?t=1576937
I used method 2. You will need to push the blob file to your prime using adb. Hope that helps.
Won't turn off and stuck on Boot screen PANIC!!!!
I'm running CM9 nightlies on my 64gb TF201 and have had no issues with it. I'm using GooManger and Teamwin for recovery and have not had any issues in that department either. Until now.
So 2 days ago a nightly was released that I flashed with out issues. The updated ROM however wanted to open the virtual keyboard when I started typing so I decided to revert back. I did this by just flashing an earlier released nightly. It went through the process and then restarted. The boot screen came on and then never left. If I try and turn it off it just restarts. I can't get it into recovery but I can get into fastboot. However I don't have a little Android symbol just the wipe data and USB. I don't have a backup on my computer that I can push through. I flashed CWM recovery through fastboot in hopes of then being able to get into recovery but with no luck. I used transformerprimerecovery.zip followed all the instructions got an "OK" and "finished" on CMD. At the same time the little progress bar on the TF showed that it did something but no change with my condition.
When I'm connected with fastboot it doesn't show up on my computer as I found to be expected. In device manager Android Phone is listed and when I click on it ASUS Android Bootloader Interface shows up stating device is working properly. If I open CMD and type "cd" it just replies C:\users\Josh>. I tried to wipe data to see if it would and it said it did but still no change. I've been reading for the past two days and haven't found the same set of problems yet. I've found similar issues but not all together.
Please if anybody has a suggestion for me I would be most Thankful. I've not had any luck with my searches
Thanks
Lifewithsuzy, try this, it's what I did when I screwed up my tablet, and it's helped a few others.
geo.z said:
Lifewithsuzy, try this, it's what I did when I screwed up my tablet, and it's helped a few others.
Click to expand...
Click to collapse
I haven't been able to try this yet for I seem to be having ADB issues. SDK is updated and current and I have the latest universal driver setup. I show up in device manager but not in the CMD prompt.
---------- Post added at 08:10 AM ---------- Previous post was at 07:44 AM ----------
I seem to be falling further down the rabbit hole. I mentioned above that I was able to flash CWM recovery via fastboot was not able to access it. I tried the same process with TeamWin recovery. It just stated that the specified path could not be found. So I'm losing features now.
lifewithsuzy said:
I haven't been able to try this yet for I seem to be having ADB issues. SDK is updated and current and I have the latest universal driver setup. I show up in device manager but not in the CMD prompt.
---------- Post added at 08:10 AM ---------- Previous post was at 07:44 AM ----------
I seem to be falling further down the rabbit hole. I mentioned above that I was able to flash CWM recovery via fastboot was not able to access it. I tried the same process with TeamWin recovery. It just stated that the specified path could not be found. So I'm losing features now.
Click to expand...
Click to collapse
When you are trying to flash anything in adb or in fastboot, put the file in the same folder as those .exe files. Manytimes it is a typing mistake on the path that kills you. Also remember to add the.zip at the end of the file name if applicable.
Gage_Hero said:
When you are trying to flash anything in adb or in fastboot, put the file in the same folder as those .exe files. Manytimes it is a typing mistake on the path that kills you. Also remember to add the.zip at the end of the file name if applicable.
Click to expand...
Click to collapse
No luck. I've tried rearranging all the files associated with adb and fastboot I can think of. I've opened the CMD window from about every file as well as from the start menu and I can't get CMD prompt to recognize the tablet. The tablet allows me to get to the point where it states that it is "starting fastboot USB download protocol". Device manager shows Android Phone > ASUS Android Bootloader Interface. And when I remove the device it shows it listed as "fastboot device". I'm stumped on getting into CMD and can't do anything until I do. It just stays on the boot screen until I force it off. And if I'm not holding down the volume up button when I do it, it just recycles on. I've found post regarding the boot screen locked on but everybody has been able to fix it through a properly functioning fastboot/ADB.
lifewithsuzy said:
No luck. I've tried rearranging all the files associated with adb and fastboot I can think of. I've opened the CMD window from about every file as well as from the start menu and I can't get CMD prompt to recognize the tablet. The tablet allows me to get to the point where it states that it is "starting fastboot USB download protocol". Device manager shows Android Phone > ASUS Android Bootloader Interface. And when I remove the device it shows it listed as "fastboot device". I'm stumped on getting into CMD and can't do anything until I do. It just stays on the boot screen until I force it off. And if I'm not holding down the volume up button when I do it, it just recycles on. I've found post regarding the boot screen locked on but everybody has been able to fix it through a properly functioning fastboot/ADB.
Click to expand...
Click to collapse
The command window should be opened from the same window (folder) you have adb.exe or fastboot.exe in otherwise it isn't going to work unless you have the exact path which is easy to kame a mistake on. I would try the following:
If your not on twrp I would fastboot install it first.
Install universal naked driver
Download and unzip nvflash file
In the folder window where adb.exe is, press and hold shift, and right click and select open command prompt here.
Now do adb devices
You should see you device
put you rom in the same folder and push it to the table
reboot to recovery and install
I tried to root my me302kl by following the first post described in this thread, but it seems I've bricked my tablet
http://forum.xda-developers.com/showthread.php?t=2601837
I have the LTE version, unlocked the bootloader using the apk from Asus, and followed the fastboot method in the first post, and now I'm stuck at the Asus logo on startup. I'm trying to factory reset by using the update download from the Asus website, but when i try
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
it fails with this:
writing 'update'...
FAILED (remote: partition table doesn't exist)
Then I tried following perpe's advice but both methods did not work
Download the update zip for your device and sku from ASUS. Unpack it once, there should be a second zip, try to flash it with
fastboot update name-of-your.zip
if this doesn't wotk, then copy the update zip to an external sd card. Your sd card should be formated in far32. Place the card into the tablets sd card. Press Volume UP + Power to boot it into the bootloader, it should flash it automatically, if not look if yor bootloader has a menu entry "sd download..." select it with the volume keys and power.
Click to expand...
Click to collapse
When booting into recovery mode, I get the dead android robot icon, regardless of whether the .zip file is on the SD card or not. I've also tried making a system.img file out of the system folder from the extracted zip file and flashing that with fastboot flash system system.img and fastboot flash boot boot.img, but that didn't work either.
Any kind soul have advice on how to make use of the official Asus OTA .zip file, or perhaps be able to supply some .img backups for me to make use of?
EDIT
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Lenino83 said:
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Click to expand...
Click to collapse
download the OTA zip from the asus website
unzip once, you should have another zip
power on the tablet while holding volume up to boot into recovery mode
after the android robot shows up, hold volume up and press the power button to get the recovery menu to show
install the zip using adb sideload
using adb sideload will differ depending on what OS you're using. you can google to find out more specific instructions for that because it's a little more work to get it for windows. for OSX if you have homebrew, you can just 'brew install android' and it will install all the android tools for you.
once you have adb installed, in the terminal type 'adb sideload pathname_of_zip.zip' and it will restore your device to factory settings
I had the same problem and your trick saved me from sending it back. I am not sure if i would have send it back as I have yet to brick something since I am playing with android back in the days of Viewsonic gtablet. We are stuck with 4.2.
Sent from my T0LTE using Tapatalk
help
tkuichooseyou said:
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Click to expand...
Click to collapse
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
ionratiu2000 said:
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
Click to expand...
Click to collapse
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
back
rob_z11 said:
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
Click to expand...
Click to collapse
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
ionratiu2000 said:
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
Click to expand...
Click to collapse
You can download king's root or something which is a window app, and it does give your tablet root. I am not exactly sure about the name, but would let you know once I have access to my laptop.
Sent from my T0LTE using Tapatalk
ASUS MEMO PAD FHD10 ME302KL frozen logo screen
I have problem with my asus memo pad 10. It just shows asus logo startup screen and nothing more and it have no reaction with anything I do.
Please help!
I can't boot into recovery mode, but there is no problem to boot into fastboot mode!
Could anyone provide stock recovery file or link? Then I can flash recovery and do the adb sideload.
Thanks!!
Hello. I just got a HTC ONE X+ yesterday as my first smart phone, iv been using a basic nokia for around 20years lol I choose the HTC mainly because I saw a review of one using the Viper+ rom and love to customise my computers so thought this was right up my street.
I sat down today watched a couple of youtube videos & read a few tutorials, I unlocked the phone through the cmd and did the reset, all went smoothly as far as i was aware, I then went into settings and there was no developers options to select, I dumped the rom onto the storage, and went into the fastboot again since im following a step by step guide, I did the backup, wiped Wipe Cache, Dalvik, then when I went to Factory Reset it said failed, I thought ok ill try again after system, did that went back to FR again said failed. hhmm ok, went ahead with installing Viper and it started installing and said fail. so I went to reboot but told me their is no OP any more, so I tried to do a restore but it shows an empty folder, so now it only boots into the white HTC logo screen and sits there. I can get into the fastboot menu still, but when connected to a laptop it doesn't show up as a device so I cant view any folders or anything.
does anyone know where it went wrong and a way to correct this? it would be a big help to me, thank you
-Marc
you didn't say what recovery you got I suggest you to install TWRP 2.7.1.0 from here:
http://techerrata.com/file/twrp2/enrc2b/openrecovery-twrp-2.7.1.0-enrc2b.img
when you download that .img file install this toolkit, that you will download from here:
https://mega.co.nz/#!ZExEEBJL!jKoitltieeOIb8JV-cjqw9i4ldV1yXFUAf-q1W8-UUE
It's easy very easy to install you have option to install "Your own recovery" select that and press flash and select your .img that you download up, it will say in cmd 2 times Okay.
But before you flash, when you unzip this toolkit from .rar put it in "C:\" not in "C:\something\something & other things" becouse toolkit won't found .img.
After that you download 2.1.1 rom from here:
http://uploaded.net/file/tqmae0zd
and when you download the rom he will be named like ViperX_2.1.1 or something like that you rename it to just viperx.
When you did all that go into recovery wipe all, connect your phone to a PC go to device manager to portable devices and disable HTC One X+ if you don't do that adb won't recognized the phone. Then in recovery go to Advacned - Adb sideloade press that button and on PC through toolkit in section Extras select first option adb sideload press run, and select viperx.zip rom in toolkit folder or in "C:\" where you put it. Sideload will begin counting to 100% when it finish, rom will run automatically, rest is easy just next next pick what you want.
P.S
Don't forget to install latest htc drivers, and latest drivers for usb to avoid some conflicts becouse when sideloading adb won't recognized sometimes, that happends.
Thanks for the reply, I would of liked to have given this ago but now the tool kit keeps saying enable USB debugging first, which I cant do....anyway to do this without the original OS installed?
First of all there is THANKS button in left corner under avatar, so you can click on it instead of saying Thanks.
Second you don't need usb debugging mode in recovery go into recovery wipe all like I write in my first reply, install drivers first for HTC and do everything like i told you up there.
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.
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"