Hello XDADevs,
I had previously experienced boot issues after installing the ARHD 21 ROM on my wife's phone, only to find out that I was flashing the wrong ROM. I switched to ARHD 11.2 and was making better progress, when I started getting errors after hitting the 'HTC One Powered by Android' splash screen. The errors being "Unfortunately, the process com.android.systemui has stopped" popping up every time I tapped OK. The screen would then go blank and would not turn on again, though I could tell the phone was running when I pressed the volume buttons.
Using CWM recovery, I cleared all the caches I could find and re-installed the ROM. This time, phone boots to a blank screen, no responses. Was told by @Captain_Throwback that I needed to be using the TWRP recovery image, so while in CWM(because that was the only way I could interact with my phone via adb) I loaded the TWRP image.
Now, I cannot open Recovery, and cannot interact with my phone. Tried different methods of trying to connect, with no positive results.
C:\Minimal ADB and Fastboot>adb kill-server
C:\Minimal ADB and Fastboot>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Minimal ADB and Fastboot>
This was my first time unlocking, rooting, and flashing a ROM on any device. I used SunShine to unlock and S-Off, loaded SuperSU(everything was fine), then after that I tried loading ARHD 21, which is when all the trouble started.
All I wanted to do was to make my wife's phone work better after porting this phone from Verizon to T-Mobile by changing the band frequencies from CDMA to GSM.
So now that my recovery is not working, how can I connect my phone to the computer again to get this to work?
Surreel said:
Hello XDADevs,
I had previously experienced boot issues after installing the ARHD 21 ROM on my wife's phone, only to find out that I was flashing the wrong ROM. I switched to ARHD 11.2 and was making better progress, when I started getting errors after hitting the 'HTC One Powered by Android' splash screen. The errors being "Unfortunately, the process com.android.systemui has stopped" popping up every time I tapped OK. The screen would then go blank and would not turn on again, though I could tell the phone was running when I pressed the volume buttons.
Using CWM recovery, I cleared all the caches I could find and re-installed the ROM. This time, phone boots to a blank screen, no responses. Was told by @Captain_Throwback that I needed to be using the TWRP recovery image, so while in CWM(because that was the only way I could interact with my phone via adb) I loaded the TWRP image.
Now, I cannot open Recovery, and cannot interact with my phone. Tried different methods of trying to connect, with no positive results.
C:\Minimal ADB and Fastboot>adb kill-server
C:\Minimal ADB and Fastboot>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Minimal ADB and Fastboot>
This was my first time unlocking, rooting, and flashing a ROM on any device. I used SunShine to unlock and S-Off, loaded SuperSU(everything was fine), then after that I tried loading ARHD 21, which is when all the trouble started.
All I wanted to do was to make my wife's phone work better after porting this phone from Verizon to T-Mobile by changing the band frequencies from CDMA to GSM.
So now that my recovery is not working, how can I connect my phone to the computer again to get this to work?
Click to expand...
Click to collapse
I'm not sure how you loaded TWRP from CWM, but you should be flashing TWRP through the bootloader, using fastboot flash recovery nameofTWRP.img. I'm not clear on what exactly you did. You will always be able to get to the bootloader, which is good, because that's where you need to be to flash recovery. Do you know how to get to the bootloader and can you fastboot flash the recovery image? And what TWRP file, exactly, are you flashing?
EDIT: You should've posted this in the Q&A forum for your device. Those are the people that would most be able to help you. I'm not sure why you posted it here. Ask a mod to move it.
I flashed the recovery the only way I knew how, which was through adb running fastboot flash recovery openrecovery-twrp-2.8.0.2-m7.img
My phone will not connect to the computer anymore. since running that command.
Surreel said:
I flashed the recovery the only way I knew how, which was through adb running fastboot flash recovery openrecovery-twrp-2.8.0.2-m7.img
My phone will not connect to the computer anymore. since running that command.
Click to expand...
Click to collapse
You realize that file is for M7, right? Start by downloading the proper recovery for your device. That's why I asked where you got it.
And you didn't use adb, you used fastboot. The two aren't synonymous. Fastboot is for bootloader operations and adb is when the device is booted up or in recovery. If you just get back to fastboot mode, you can flash a proper recovery.
Captain_Throwback said:
You realize that file is for M7, right? Start by downloading the proper recovery for your device. That's why I asked where you got it.
And you didn't use adb, you used fastboot. The two aren't synonymous. Fastboot is for bootloader operations and adb is when the device is booted up or in recovery. If you just get back to fastboot mode, you can flash a proper recovery.
Click to expand...
Click to collapse
I figured that out earlier today. Flashed the correct recovery and am now looking into getting a different ROM loaded because the ARHD 11.2 isn't working.
Related
Hi again
I'm still in processing with flashing a recovery on my XOOM 3G MZ601.
I unlocked fastboot successfully after 2-3 try (1&2 nothing appeared on the tab).
Now I'm on flashing recovery, but it is f****** stuck on "sending 'recovery' <3998 KB>..."
I tried everything possible I can think of, so I'm turning back on you guys.
When >fastboot devices, I got my devices.
But when >fastboot flash recovery recovery.img, got stuck on message above "..".
Answered on my own.
Good news, I succeed to flash recovery.
For information of future question about this, so it can be on the record, even if my device appeared when adb devices and fastboot devices, I got a driver called controller SM didn't right.
I install the last chipset drivers of my MB, rebooted PC, then do the adb command again, and tada, it worked.
I'm glad. Now, next step, root & custom.
After rootting my moto G around a month ago, the KitKat update has came out, I tried to update on my phone and there was an error, then I tried updating it from the PC, again another error. Then when I would turn my phone on it would turn off after around 1 minute after turning on, So I found a thread to install the update manually, then I had errors flashing partitions as said in the steps on this other website. I uplugged the phone as I kept getting errors, now when I try to turn it on it just gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. Even when I hold down the power button to turn it off, it just turns the screen black, vibrates, turns back on with the warning screen. I cannot enter fastboot with holding down power and the volume key. I am stuck here any tips or anyone know what is going on/ causing the error?
Did u got the phone completlely off? If not - try it and try to Boot in fastboot then.
Sent from my Moto G using xda app-developers app
pspuser97 said:
Did u got the phone completlely off? If not - try it and try to Boot in fastboot then.
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
I have managed to get it into fastboot just now by holding down the power and both volume buttons.But I still can't seem to get it working.
Luke1275 said:
After rootting my moto G around a month ago, the KitKat update has came out, I tried to update on my phone and there was an error, then I tried updating it from the PC, again another error. Then when I would turn my phone on it would turn off after around 1 minute after turning on, So I found a thread to install the update manually, then I had errors flashing partitions as said in the steps on this other website. I uplugged the phone as I kept getting errors, now when I try to turn it on it just gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. Even when I hold down the power button to turn it off, it just turns the screen black, vibrates, turns back on with the warning screen. I cannot enter fastboot with holding down power and the volume key. I am stuck here any tips or anyone know what is going on/ causing the error?
Click to expand...
Click to collapse
what model???
yiu have the usb drivers intalled??
alonsoch said:
what model???
yiu have the usb drivers intalled??
Click to expand...
Click to collapse
Its the vodafone UK moto G, yes I have the drivers installed.
fastboot oem fb_mode_clear
Try fastboot oem fb_mode_clear
i have same problem
I am also having same problem. did anyone found solution for this?
There can be many reasons for this: broken ROM, incorrect kernel etc. Unless you know specifically the last thing you changed; you are better off doing a factory reset and installing a new ROM in Recovery or flashing a firmware image via fastboot.
I am having this exact same issue. the phone is stuck on the unlocked bootloader screen. It is still responsive, I can get into the fastboot and even clockwork recovery mod but nothing i do will escapt the bootloop. I even tried a factory reset in Fastboot and Clockwork and the RSD lite method but it didnt work.
Go to the 'Restore Stock Firmware' thread and re-flash your firmware again. I've had bootloops before.
Sent from my Moto G on MoKee, using XDA app.
mej0248 said:
Go to the 'Restore Stock Firmware' thread and re-flash your firmware again. I've had bootloops before.
Sent from my Moto G on MoKee, using XDA app.
Click to expand...
Click to collapse
I did, I tried that method but when I get to step 3B I cannot get mboot or whatever to work. First it throws an error and asks for an obscure Adb.dll that i hunted down and put in its folder but then i click it to open and it flashes up for a second then closes. Excuse me while I go cry in a corner for a bit. :crying:
Deadboy90 said:
I did, I tried that method but when I get to step 3B I cannot get mboot or whatever to work. First it throws an error and asks for an obscure Adb.dll that i hunted down and put in its folder but then i click it to open and it flashes up for a second then closes. Excuse me while I go cry in a corner for a bit. :crying:
Click to expand...
Click to collapse
Bootloader screen is a boot animation http://forum.xda-developers.com/moto-g/general/guide-how-to-stuck-boot-animation-t2794208
And for restore stock firmware try inputting these commands manually
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
If all else fails check out my guide : http://forum.xda-developers.com/moto-g/general/unbrick-method-t2794271
NEED URGENT HELP
I accidentally wiped the internal storage of my Moto G XT1033 (dual sim variant), since the OS is lost now my phone is stuck at bootloader warning. I can access TWRP recovery. In device manager I can see Google Nexus ADB Interface. And in taskbar (safely remove hardware and eject media) phone is recognized as Eject XT1032. But in file explorer/My computer I can't see the phone. My phone drivers are installed.
I've tried adb shell command and I am getting this error:
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
and with adb devices command following error:
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
(this line/area is blank)
C:\Minimal ADB and Fastboot>
Now how can I fix ADB or this problem? Please help
Juste300 said:
NEED URGENT HELP
I accidentally wiped the internal storage of my Moto G XT1033 (dual sim variant), since the OS is lost now my phone is stuck at bootloader warning. I can access TWRP recovery. In device manager I can see Google Nexus ADB Interface. And in taskbar (safely remove hardware and eject media) phone is recognized as Eject XT1032. But in file explorer/My computer I can't see the phone. My phone drivers are installed.
I've tried adb shell command and I am getting this error:
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
and with adb devices command following error:
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
(this line/area is blank)
C:\Minimal ADB and Fastboot>
Now how can I fix ADB or this problem? Please help
Click to expand...
Click to collapse
If you have access to TWRP, then are you able to go into the Advanced menu and use the ADB Sideload feature to flash over a ROM from your PC? I had a problem while working with my phone the other day during its initial unlocking and flashing where I'd broken the system install but still had access to TWRP, and by swiping and enabling ADB Sideload, I was able to flash in a new ROM with my phone connected to my computer by running: adb sideload /path/to/rom.zip
Alternatively, you may be able to use the stock firmware restoration procedure detailed elsewhere in this forum to restore your stock firmware via fastboot.
Pardon me if I haven't fully grasped your issue. Hope this helps!
a_gert said:
If you have access to TWRP, then are you able to go into the Advanced menu and use the ADB Sideload feature to flash over a ROM from your PC? I had a problem while working with my phone the other day during its initial unlocking and flashing where I'd broken the system install but still had access to TWRP, and by swiping and enabling ADB Sideload, I was able to flash in a new ROM with my phone connected to my computer by running: adb sideload /path/to/rom.zip
Alternatively, you may be able to use the stock firmware restoration procedure detailed elsewhere in this forum to restore your stock firmware via fastboot.
Pardon me if I haven't fully grasped your issue. Hope this helps!
Click to expand...
Click to collapse
Thanks for the help. I tried ADB Sideload feature in twrp as well the adb sideload /path/to/rom.zip this command/feature was not working from the pc.
Anyways, I tried USB OTG method, copied CM nightly into my flash-drive then attached flash-drive + OTG cable with phone, at first OTG was not working don't know why it could not mount, I restarted phone, went into recovery and then I could installed rom from flashdrive. Finally my phone is working now
I am totally new to android and this rom rooting stuff. Moto G is my first android smartphone coming directly from iPhone 5 so I was scared like hell
If anyone failed with ADB Sideload method please try USB OTG method and your phone will work again. Hope this help others
same issue
Juste300 said:
Thanks for the help. I tried ADB Sideload feature in twrp as well the adb sideload /path/to/rom.zip this command/feature was not working from the pc.
Anyways, I tried USB OTG method, copied CM nightly into my flash-drive then attached flash-drive + OTG cable with phone, at first OTG was not working don't know why it could not mount, I restarted phone, went into recovery and then I could installed rom from flashdrive. Finally my phone is working now
I am totally new to android and this rom rooting stuff. Moto G is my first android smartphone coming directly from iPhone 5 so I was scared like hell
If anyone failed with ADB Sideload method please try USB OTG method and your phone will work again. Hope this help others
Click to expand...
Click to collapse
same issue but i dont know how to flash rom though pendrive i didnt find the files that i were in my pendrive in twrp menu
:crying:
shivamtyagi said:
same issue but i dont know how to flash rom though pendrive i didnt find the files that i were in my pendrive in twrp menu
:crying:
Click to expand...
Click to collapse
You first have to select the usb storage in TWRP because TWRP detected internal storage. U can even mount usb otg from TWRP options. after selecting usb then u can see the files in ur usb drive.
I'm stuck on the same Warning screen, it is not a bootloop since the phone just seems to freeze but after a minute I get the windows sound as if you conected something via USB, but the warning screen stays, I've let it for hours and I've flashed stock roms. Even when you flash a no warning boot logo.bin the screen shows again even when mfastboot shows as succesful flash. Out of ideas now, please help
Code:
Model XT1068
Thanks
Thanks
Solution for MotoG locked in bootloader,
I think you must have tried to install another kernel version or so. If you have installed cyanogen try resinsallting the lasted update by going into custom recovery and flashing the latest update in the cmupdater file. Worked for me ! Lets hope that it works for you too. All the best !
I am new to this (clearly heh) and wanted to put CM12 on my OPO, as it just arrived today and CM11 is a bit dated.
So after 101 issues I got TWRP installed, great!
However I messed it up by wiping my OS off the phone, leaving me with just access to TWRP and nothing else.
I was reading about ADB, but I cannot get the ADB sideload to start on my phone (it just hangs...).
ADB also does not detect my phone when I do an ADB push.
Any help is appreciated :'(
Acrylicus said:
I am new to this (clearly heh) and wanted to put CM12 on my OPO, as it just arrived today and CM11 is a bit dated.
So after 101 issues I got TWRP installed, great!
However I messed it up by wiping my OS off the phone, leaving me with just access to TWRP and nothing else.
I was reading about ADB, but I cannot get the ADB sideload to start on my phone (it just hangs...).
ADB also does not detect my phone when I do an ADB push.
Any help is appreciated :'(
Click to expand...
Click to collapse
If you are able to get into TWRP then this link http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 will surely help you
- Install your device drivers first (If they are installed properly, then only skip this)
- Once adb and fastboot files are loaded on your computer, open command prompt and type command "fastboot devices". If you see your device serial number on the prompt, you are good to proceed ahead with flashing procedure.
- I recommend you to flash fastboot images of CMOS12 using that link.
I just tried rooting my phone. The phone is cycling back and forth between the bootloader is unlocked screen and the Motorola splash screen.
To repeat some steps from a prior post.
My phone had QPR30.80-58-3 .
I downloaded that ROM and extracted the boot.img file.
I downloaded the latest Magisk Manager and installed it on my phone.
I ran through the patching process for boot.img.
I requested an unlock code from Motorola and unlocked the bootloader.
I flashed the patched boot image which patched partition b.
I flashed the patched boot image to partition a.
I rebooted which began the cycle.
I tried holding down the power button but it returns to the cycle.
I can get back to the bootloader with the Volume Down and Power buttons.
Any suggestions on what could get me back to a functioning phone, rooted or not rooted?
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
dafunk60 said:
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
Click to expand...
Click to collapse
I checked that the image I patched was from the QPR30.80-58-3 ROM which matched the level after the phone was updated.
I flashed that original boot image which flashed partition a and then rebooted. I did not flash partition b.
It first came up with the unlock warning screen. It sat on the Motorola splash screen for a noticeable amount of time followed by a yellow screen with a circle around the Motorola symbol. Finally it ended up on a blue Hello there screen with a yellow start button.
This screen was unresponsive. Eventually through various cyclings through all this I ended up on a screen that said Android could not boot and gave me an option of a factory reset. I did that but it did not help getting past the Hi there screen.
I went back and flashed the QPR30.80_58 image on both partitions a and b. This got me back to setting up the phone again. The phone is at QPR30.80_58. I am considering just rooting at this level.
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
DougPeterson said:
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
Click to expand...
Click to collapse
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
dafunk60 said:
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
Click to expand...
Click to collapse
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If you want to get into recovery, boot into the bootloader than do
Code:
fastboot reboot fastboot
That'll boot you into fastbootd which has an option to go to the real recovery
DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If adb isn't showing any devices connected that would explain why the rescue software cannot find your phone. Perhaps you don't have the correct driver installed. Windows Device Manager shows the phone as a Motorola ADB Device on my PC.
View attachment 5061327
Another possibility is that you have multiple versions of adb on your PC. Older versions won't work but the adb.exe in "C:\Program Files (x86)\Rescue and Smart Assistant" works for sure. With your phone booted into android & unlocked, plug it into your PC. Do you see the "USB debugging connected" on the phone? If you don't I would re-check that USB debugging is enabled. If you do see the debugging notification, on your PC, open a command prompt and navigate to "C:\Program Files (x86)\Rescue and Smart Assistant". Run
Code:
adb devices
Does adb find your phone?
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
jwoegerbauer said:
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
Click to expand...
Click to collapse
As it turns out, I had already stumbled upon your your "ADB-FASTBOOT-Installer" during a trip down one of the many rabbit holes trying to get this tablet working again.
adb devices returns:
List of devices attached0123456789ABCDEF recovery
adb reboot restarts the tablet, which I assume means the ASUS tablet driver is working.
I can't seem to do anything else with adb, however, such as push a new TWRP version, etc. This may be a key point, as it seems likely the version I have of TWRP may be too old to support upgrade using something like Chrombi-KK.
Is this a likely theory?
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
NotTheLips said:
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
Click to expand...
Click to collapse
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
jwoegerbauer said:
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
Click to expand...
Click to collapse
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
[email protected] said:
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
Click to expand...
Click to collapse
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
NotTheLips said:
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
Click to expand...
Click to collapse
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
NotTheLips said:
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
Click to expand...
Click to collapse
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
jwoegerbauer said:
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
Click to expand...
Click to collapse
As I mentioned before, "2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine."
[email protected] said:
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
Click to expand...
Click to collapse
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
NotTheLips said:
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
Click to expand...
Click to collapse
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
[email protected] said:
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
Click to expand...
Click to collapse
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
the problem is your pc does not have adb and fastboot properly installed
try this one https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
also, use this official driver https://www.asus.com/SupportOnly/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
if your pc is 64 bit use win764bit version
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
This "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in Fastboot mode, so you can easily have permission to it in ADB but not in Fastboot.
Each manufacturer implements Fastboot differently. So, if not already done yet, download and install the suitable "Android USB Driver" provided by ASUS. Then Fastboot should work.
BTW: Your device actually stucks in recovery mode.
Is OEM Unlock got enabled in Android settings? If not, Fastboot never will work.