Hello Guys,
Just registered her at XDA and I hope I have not posted this thread in the wrong place. I will get right in to it without having to type the extra BS.
I have my TF201 which I have modded many times over to install a new ROM and firmware. About a year ago I had just flashed TEAMWIN recovery and got myself the absolutely SICK AndroWok 2.31 ROM. just a couple a months ago I wanted to upgrade my Android version to the latest because I was running 4.2.1. So I downloaded the upgraded Bootlader ZIP for the TF201 and thought while I'm at it I will update my recovery to TWRP 2.6.3.0... Big mistake... When I first go into recovery, it kept asking for a password... tried many times over and disabled my main OS password as I thought in some retarded way it was connected.... So for a little while I can easily reboot to AndroWok from the recovery and it would boot up fine... up until I hit the 5th attempt... From there on in, it keeps booting into recovery.... without a sign of change.... I TRIED everything.... NVFLASH, adb and fastboot the crap out recovery so I can flash the previous edition... it wont work... first off the files transfer way too quick and through all the transfer methods you can think of, I the blue fill up bar would never show... so I knew the flashing protocol was not complete although you would get the ok in command prompt. I even tried tried to flash the stock firmware thats about 112MB... it finished that in 10 seconds which is not possible... basicaly.. im stuck loopin into this retarded TWRP2.6.30... non of my flash or transfer methods work.. i cleared cache, i rebuilt the partition all of that.. im just not getting anything... and one more thing... when i would fastboot something out of command prompt, the selectable option on the tablet... where you usualy see the android logo, clear cache and rck.. (fastboot)... it would get stuck... as soon I flash wut ever file for recovery, bootloader, etc.... please help... i know i can get around this....
DeltaAden said:
Hello Guys,
Just registered her at XDA and I hope I have not posted this thread in the wrong place. I will get right in to it without having to type the extra BS.
I have my TF201 which I have modded many times over to install a new ROM and firmware. About a year ago I had just flashed TEAMWIN recovery and got myself the absolutely SICK AndroWok 2.31 ROM. just a couple a months ago I wanted to upgrade my Android version to the latest because I was running 4.2.1. So I downloaded the upgraded Bootlader ZIP for the TF201 and thought while I'm at it I will update my recovery to TWRP 2.6.3.0... Big mistake... When I first go into recovery, it kept asking for a password... tried many times over and disabled my main OS password as I thought in some retarded way it was connected.... So for a little while I can easily reboot to AndroWok from the recovery and it would boot up fine... up until I hit the 5th attempt... From there on in, it keeps booting into recovery.... without a sign of change.... I TRIED everything.... NVFLASH, adb and fastboot the crap out recovery so I can flash the previous edition... it wont work... first off the files transfer way too quick and through all the transfer methods you can think of, I the blue fill up bar would never show... so I knew the flashing protocol was not complete although you would get the ok in command prompt. I even tried tried to flash the stock firmware thats about 112MB... it finished that in 10 seconds which is not possible... basicaly.. im stuck loopin into this retarded TWRP2.6.30... non of my flash or transfer methods work.. i cleared cache, i rebuilt the partition all of that.. im just not getting anything... and one more thing... when i would fastboot something out of command prompt, the selectable option on the tablet... where you usualy see the android logo, clear cache and rck.. (fastboot)... it would get stuck... as soon I flash wut ever file for recovery, bootloader, etc.... please help... i know i can get around this....
Click to expand...
Click to collapse
So what I understand is, that you can at least boot into fastboot mode, is that so?
Have you tried.the erase command?
Code:
fastboot -i 0x0b05 erase recovery
Advice: One should never, repeat: never!, flash TWRP 2.6.3.0. Too many bricks are reportet. I had to buy new logic board for my tf201 because of this.
Second question: You talked of 'nvflash', you tried. So you have your nvflash blobs? If yes - you are safe!
Post the version of your bootloader.
das chaos said:
So what I understand is, that you can at least boot into fastboot mode, is that so?
Have you tried.the erase command?
Code:
fastboot -i 0x0b05 erase recovery
Advice: One should never, repeat: never!, flash TWRP 2.6.3.0. Too many bricks are reportet. I had to buy new logic board for my tf201 because of this.
Second question: You talked of 'nvflash', you tried. So you have your nvflash blobs? If yes - you are safe!
Post the version of your bootloader.
Click to expand...
Click to collapse
Thanks for the reply... Yes I guess it was a terrible mistake to get 2.6.3.0... In terms of the blobs, I only have the firmware from Asus stock.. I havent extracted or backed anything up previously... and about the command you gave me; yes, I also tried that and no luck. Is there any other way? Something is telling me that partition is off... because basically im unable to flash and write anything.. all flash attempts are failed so nothing is getting written...
DeltaAden said:
Thanks for the reply... Yes I guess it was a terrible mistake to get 2.6.3.0... In terms of the blobs, I only have the firmware from Asus stock.. I havent extracted or backed anything up previously... and about the command you gave me; yes, I also tried that and no luck. Is there any other way? Something is telling me that partition is off... because basically im unable to flash and write anything.. all flash attempts are failed so nothing is getting written...
Click to expand...
Click to collapse
Also... i forgot to mention.... when i erase the recovery and try to flash the new one... command prompt would hang up with <waiting for device> ... that would stay there for ever.
DeltaAden said:
Also... i forgot to mention.... when i erase the recovery and try to flash the new one... command prompt would hang up with <waiting for device> ... that would stay there for ever.
Click to expand...
Click to collapse
Looks bad!
1. Have you got the right USB drivers for Windows (Naked Drivers)?
2. Have you tried another USB port?
3. Have you tried another USB cable?
4. How many icons do you find on BL menue? Do you really know, how to enter fastboot mode (NOI)?
If nothing helps, buy another logic board. It's cheap on ebay.
das chaos said:
Looks bad!
1. Have you got the right USB drivers for Windows (Naked Drivers)?
2. Have you tried another USB port?
3. Have you tried another USB cable?
4. How many icons do you find on BL menue? Do you really know, how to enter fastboot mode (NOI)?
If nothing helps, buy another logic board. It's cheap on ebay.
Click to expand...
Click to collapse
Yes I have the naked drivers... and I beleive it is fuctional because theres clearly a response from my tablet... i usualy start by entering the shel first which sometimes takes a couple of attempts. when its successful, i know a session is now active with my table to i simply exit again... then from there its easy because i know the tablet has a session with my pc so i "adb reboot bootloader" which automaticaly restarts the tablet into fastboot and icon hovering over RCK.... from there I run my commands and command prompts confirms it by the 'ok' displayed along with the time it took in seconds.... clearly theres something wrong there.... i should try it at another pc.... or maybe the issue is a bit more complex... the real question remains, why can i not flash another recovery besides the 2.6.3.0??. still any other suggestions.? i will try another pc and have a go
DeltaAden said:
Yes I have the naked drivers... and I beleive it is fuctional because theres clearly a response from my tablet... i usualy start by entering the shel first which sometimes takes a couple of attempts. when its successful, i know a session is now active with my table to i simply exit again... then from there its easy because i know the tablet has a session with my pc so i "adb reboot bootloader" which automaticaly restarts the tablet into fastboot and icon hovering over RCK.... from there I run my commands and command prompts confirms it by the 'ok' displayed along with the time it took in seconds.... clearly theres something wrong there.... i should try it at another pc.... or maybe the issue is a bit more complex... the real question remains, why can i not flash another recovery besides the 2.6.3.0??. still any other suggestions.? i will try another pc and have a go
Click to expand...
Click to collapse
On second thought:
Are you logged in as an admin in Windows or do you sudo before fasboot in Linux?
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
Hello guys, I'm here because my TF201 seems to be bricked ...
I know, there is a lot of threads about this kind of problems, but I can't succeed to solve mine by reading hundred of threads.
I explain what's happened :
My TF201 has an unlocked bootloader (by asus method), root, and has a CWM (CWM-based Recovery v5.5.0.4). I was on the lattest ICS build (9.4.2.15). Since october, i know that JB was on TF201, but not mine. So I decide to download the lattest Stock JB version from Asus website and to place it into my SDcard. I reboot my TF201 in recovery (holding down the volume button, then up), I've done a backup. After this backup, I've done a factory reset and I install the new ROM from my SDcard. Maybe I should not do this ... But now, my tablet stay on the bootscreen (Asus EEE pad logo). I can always access to the recovery, so I tried to factory reset and restore my previous backup ... But it didn't work, my tablet still bricked.
So, I went to google, i've read lots of threads for trying to understand whats happened to my TF201. I've read some thread on XDA forum too.
I've tried every solutions proposed, and anyone work.
I've read some articles about ADB. I installed it, but the problems is that my TF201 can't be detected by my computer (Running Win8 64). I installed drivers from here : http://forum.xda-developers.com/showthread.php?t=1379875
But, still nothing, impossible to show my device when I write "adb devices" or "fastboot devices" in windows cmd.
I'm a little bit desesperate, so i came here for writting this thread, hopping that someone could help me to unbrick my TF201 without send it back to Asus (wich cost me hundreds of euros).
I'm going in front of some questions that i've read in other thread :
No i've not TWRP recovery installed.
I haven't got a nvFlash.
Thanks for reading this thread and for your help !
Sincerelly,
Thrakka.
PS : I'm really sorry for my bad english, don't blame me ^^
You can access recovery?
Then you are not bricked.
Why not flash a custom rom?
Garret said:
You can access recovery?
Then you are not bricked.
Why not flash a custom rom?
Click to expand...
Click to collapse
Primarily because he has cwm recovery and jellybean bootloader. He does not know how to set up his drivers on his computer for fastboot to install the correct recovery for his bootloader.
to the OP, go here http://forum.xda-developers.com/showthread.php?t=1615990 and figure out how to get twrp for jellybean on your prime. TWRP supports flashing roms from the microsd slot so you dont need to push one to your sd. also if you need help getting the naked drivers to work on your prime go the link http://forum.xda-developers.com/showthread.php?t=1426502 that pertains to others putting it on the prime. they will be more help than the galaxy naked drivers users. FORGET ABOUT CWM!!! IT IS NOT SUPPORTED ON PRIME FOR JELLYBEAN
@ Garret
Yes I can access to recovery, but for flashing a new rom, I need to access my internal SDcard ... But infortunatelly, now I can't.
A thing that I don't understand is when I restore my ICS backup, it doesn't work ...
@ Whycali
I'm gonna try your advice this afternoon.
But how can I install TWRP on my prime without access ... I'm will try with your links ... Hoping succeed ...
I'll give you the results in the evening.
Sincerely,
Thrakka.
I can access to the fastboot mode, but impossible to flash anything ...
I've taken all driver for the prime on my computer, install them.
the command "fastboot devices" work, i can see my prime : 00000 fastboot
but when I try the command "fastboot -i 0x0b05 flash recovery twrp.blob" from www{dot}teamw.in/project/twrp2/93, the result : error: cannot load 'twrp.blob' : No error.
I can't understand.
The directory "/platform-tools" from the ADT is in the PATH variable, and the file "twrp.blob" is in the same directory. Two ways for the fastboot command to find it, but it can't succeed ...
Same problem when I want to create my own nvflash blob file (tuto from androidroot.mobi/t3_nvflash/) with the command "fastboot -i 0x0b05 flash staging ebtblob.bin", the result is the same : error: cannot load 'ebtblob.bin' : No error.
I can't see my mistake ... Could you help me ?
Sincerely,
Thrakka.
PS : as i'm a new member, I can't post direct link to other site where I found tutos, sorry ...
Thrakka said:
I can access to the fastboot mode, but impossible to flash anything ...
I've taken all driver for the prime on my computer, install them.
the command "fastboot devices" work, i can see my prime : 00000 fastboot
but when I try the command "fastboot -i 0x0b05 flash recovery twrp.blob" from www{dot}teamw.in/project/twrp2/93, the result : error: cannot load 'twrp.blob' : No error.
I can't understand.
The directory "/platform-tools" from the ADT is in the PATH variable, and the file "twrp.blob" is in the same directory. Two ways for the fastboot command to find it, but it can't succeed ...
Same problem when I want to create my own nvflash blob file (tuto from androidroot.mobi/t3_nvflash/) with the command "fastboot -i 0x0b05 flash staging ebtblob.bin", the result is the same : error: cannot load 'ebtblob.bin' : No error.
I can't see my mistake ... Could you help me ?
Sincerely,
Thrakka.
PS : as i'm a new member, I can't post direct link to other site where I found tutos, sorry ...
Click to expand...
Click to collapse
on your pc you need to run the command from the same directory that contains the file you wish to transfer. easiest way to do this is to place the blob in the folder where your fastboot application is then hold shift and right click inside the folder. from the menu that opens choose open command window here. from there run your fastboot commands.
---------- Post added at 12:37 PM ---------- Previous post was at 12:02 PM ----------
hey, hold up and check your pm. Do not install TWRP for jb if you are still on the ICS bootloader.
you can check which bootloader version of twrp to install by where the nvidia logo is on the bootscreen. bottom center needs ics twrp. bottom right needs Jellybean twrp. By all means if you are still with ics finish the nvflash backups first.
867-810 Eecuri
Little update for the post :
I succeed all this steps, I've TWRP for ics now.
I'm looking for an ICS Rom for install it.
What could I do if I want to have a JB ROM ?
Thrakka said:
Little update for the post :
I succeed all this steps, I've TWRP for ics now.
I'm looking for an ICS Rom for install it.
What could I do if I want to have a JB ROM ?
Click to expand...
Click to collapse
Follow the instructions fully in the second post of the androwook thread for upgrading from ics.
All problem are solved !
Thanks Whycali for your precious help !
I've installed the AndroWook ROM, and it's a real pleasure !
Good Job man, I was travelling, just saw you made it
Thank you Garret ;D
It was not as bad as i was thinking before posting this thread !
Just compatilibity problem between a JB rom with ICS bootloader and ICS recovery ^^
senior member, can you help me with this problem ?
http://forum.xda-developers.com/showthread.php?t=2263137
Help with tf201
Hey all,
To start I have a bricked tf201. i was following a Youtube tutorial to update my twrp. i followed the instruction diligently. I was running CM 10.1 on the tf201. After the Install I rebooted and now it boot loops. if i hold vol down + pwr button it looks for revovery kernel and then fails. if i hold Vol up + pwr button it vibrates and black screen assuming this is apx mode. i followed ever tutorial on apx and i can't get anything to work. is there any hope for this tablet? Thanks in advance!
bricked tf201 too
bucknerspc said:
Hey all,
To start I have a bricked tf201. i was following a Youtube tutorial to update my twrp. i followed the instruction diligently. I was running CM 10.1 on the tf201. After the Install I rebooted and now it boot loops. if i hold vol down + pwr button it looks for revovery kernel and then fails. if i hold Vol up + pwr button it vibrates and black screen assuming this is apx mode. i followed ever tutorial on apx and i can't get anything to work. is there any hope for this tablet? Thanks in advance!
Click to expand...
Click to collapse
I have the same issue. Only a black screen on VolUP+Power or The Device is unlocked on VolDown+Power. I can't do anything, the usb driver is not reconize and fastboot or adb shows anything. Please any help to recovery?
Thanks in advance
Another Bricked tf201
Aduniel said:
I have the same issue. Only a black screen on VolUP+Power or The Device is unlocked on VolDown+Power. I can't do anything, the usb driver is not reconize and fastboot or adb shows anything. Please any help to recovery?
Thanks in advance
Click to expand...
Click to collapse
Hello Aduniel: I have essentially the same issue with my tf201. It seems to be hard bricked? (My guess.) If I reboot with Volume Down and Power button, I get a message "This device is Unlocked" in upper left of screen. Also large lettering in center of the screen, "ASUS" and "nNidea Tegra 3" in the lower right.
If I boot with Volume Up and Power button, I get a blank, black screen. (APX mode).
I have set up ADB and naked drivers on a notebook running Windows 7. When I try to connect via fastboot, I get a message <waiting for device>. But it does not connect.
I was wondering if you managed to get your tablet working since Nov. 2013? If so, what did you have to do? I need to know if there is any hope, or have I shot myself in the foot, as they say.
Cheers man,
Jim
Hard Brick TF201
JRKirkey said:
Hello Aduniel: I have essentially the same issue with my tf201. It seems to be hard bricked? (My guess.) If I reboot with Volume Down and Power button, I get a message "This device is Unlocked" in upper left of screen. Also large lettering in center of the screen, "ASUS" and "nNidea Tegra 3" in the lower right.
If I boot with Volume Up and Power button, I get a blank, black screen. (APX mode).
I have set up ADB and naked drivers on a notebook running Windows 7. When I try to connect via fastboot, I get a message <waiting for device>. But it does not connect.
I was wondering if you managed to get your tablet working since Nov. 2013? If so, what did you have to do? I need to know if there is any hope, or have I shot myself in the foot, as they say.
Cheers man,
Jim
Click to expand...
Click to collapse
Hello Jim,
I have the same problem.
I kan also do APX mode but nothing wil work.
If i type apd devices: there is nothing displayed.
Also when I try to flash, it says: waiting for device.
I only once had connection with easyflasher and it saw the TF201: Chipuid: 0x98243044050469391, but later one nothing happend.
I waited for 45 minutes and stil, nothing was done.
I hve been disperate, so can anyone help us, Plaese.
Th TF201 is now dead since oktober 2013, ppfffffffffffffffffffff
Thanks. greetings 5079
Hello everyone, been a lurker for some time, but have never needed to post before until today. I'm accustomed to rooting and installing custom roms but I've never had anywhere close to as much difficulty as Im having with this tf201. Heres the situation:
Not sure if you'd call this bricked, as I have total access to fastboot, adb, and CWM Recovery (version 5.8.3.4 touch btw). However my most recent attempt ended with totally wiping from the volume down+power menu (whatever its called). I can not turn the tablet off, as it automatically boots to the asus splash screen (and goes no further, naturally). It is unlocked, and my drivers do work (both fastboot and adb recognize the device), but I can not flash or push anything to the sdcard (with adb its a protocol failure, with fastboot I get "sending zip....OKAY writing zip....FAILED [remote : [FileOperationFailed]]) Don't know if it needs to be said, but I also can't simply drop the file on the sd card as if it were a media storage device as "my computer" does not recognize that it is connected (Oh I am using the naked universal drivers from http://forum.xda-developers.com/showthread.php?t=1998650 )
So yeah, Im at a loss as it seems like no one has had this particular problem before (also my connector cable works fine, so its not that). Any help would, of course, be greatly appreciated.
EDIT: On the tablet after trying to flash with fastboot it returns "Failed to process command flash:zip error (0x30003)"
Really? Not a single person has any idea? Could really use some help here...
GrimAgent said:
Really? Not a single person has any idea? Could really use some help here...
Click to expand...
Click to collapse
You do not flash zips with fastboot.
First of all tell me where your "NVIDIA" logo is when you first power on, bottom center or bottom right?
The nvidia logo is in the bottom center of the "EEE PC Splash"
This is going to sound stupid, but did you verify the MD5 before you tried to flash it?
GrimAgent said:
The nvidia logo is in the bottom center of the "EEE PC Splash"
Click to expand...
Click to collapse
You are still on the ICS bootloader if NVIDIA is bottom center.
Go here http://www.teamw.in/project/twrp2/93 and follow the instructions for "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)"
You will need to get the ICS blob file. Never flash the wrong recovery for what bootloader you are on or you can brick your device.
If you get it working and you want to upgrade to Jellybean bootloader there is instructions in post 2 of the Hairybean Rom thread. "Upgrade instructions for ICS"
edit.. to make it a bit easier for you.
Get this file http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.4.4.0-tf201-ICS.blob
Rename it to twrp.blob
Place the twrp.blob in the same folder as your fastboot exe
Go into fastboot and type
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for it to finish and then type
fastboot -i 0x0B05 reboot
see if that works.
Damn, I had a feeling it was the bootloader issue that I messed up. I went searching all over for how to find out which one I had once I realized my potential mistake. Gonna give these steps a try
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
GrimAgent said:
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
Click to expand...
Click to collapse
If you now have twrp on there you dont need to push a file. Place the file on an external SD card on the root and plug it in before starting prime.
When going into TWRP go into install and select external SD. Pick your rom and then flash it.
Thanks a lot flumpster, everything's good now and Ive got cyanogen up and running smoothly. You've brought my tablet back to life and Ive learned a valuable lesson
I have a blind N10 on bootloader that is it doesnt show anything on fastboot mode but it does go there. I researched and found other people with similar problem http://rootzwiki.com/topic/37629-bootloader-fastboot-weirdness/ . However they managed to unlock the device by clicking the vol+ once and then power key as I also saw on youtube videos. IT WORKED. and then it went downhill. it got stuck on bootloop. SO i tried to go into fastboot again and it went and then pressed vol+ twice to go into recovery and there was a android with "!" red sign on middle.
and of course it won't boot. So I tried to use the Wugs toolkit, put it on back to stock with bootloop option. and it started to do its work, but got stuck at the sending bootloader (1280KB) sign for more than 10-15 mins. I pressed the power button and it failed that step saying too many links and wugs kit continued the process got stuck again and then completed and my device still goes to fastboot, but cant go into recovery anymore I think as it shows blank screen. Please mind that I am still blind on the screen and nothing comes. my only way of knowing it goes to fastboot is through cmd line. PLEASE HELP, dont wanna brick this.
Is there any way to ODIN it. I cant find online any ODIN insturctions? help help
I cant even turn it off now! Its always going to fastboot. Please help
mustafansu said:
I cant even turn it off now! Its always going to fastboot. Please help
Click to expand...
Click to collapse
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
ricco333 said:
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
Click to expand...
Click to collapse
Hi ricco333
thanks for the reply. I have updated the SDK and tried to run the command as you mentioned. However it is the same thing. Its getting stuck at sending bootloader. I am attaching a screenshot here. it stays there until i press ctrl+c. then it tries to continue and gets stuck again at sending boot. which is the second screenshot.
Is there any other way to restore factory image. i thought samsung devices had ODIN system. Thanks again for the reply.
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Also try re downloading the stock images...
Maybe you have a corrupted file.
Have you tried using the Nexus 10 Toolkit?
http://forum.xda-developers.com/showthread.php?t=2001868
IT WORKED!!
ricco333 said:
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Click to expand...
Click to collapse
Thanks so much guys.After trying 2 different cables and a new computer, a fresh installation of ADB and samsung drivers it finally worked. Thanks again. HUGE SIGH of RELIEF
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.