Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?
Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device is now back in a fastboot loop with no access to any options but power off & restart.
Your phone is broken
Buy a new phone and don't try to mess with it next time
Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.
Related
Hi all,
Well my adventure started last night when I went to return my Nexus S to stock. I did so and it worked well. Then I tried to re-root the device.
After doing so, it now will not boot past the google boot screen (with the unlock icon). It just sits there, even after battery pulls and additional attempts to start up. I can reboot into recovery (fastboot) as shown on the attached images. After hours of reading, it seems I need to flash CWM recovery.img to get the phone to boot. Ok, not a problem. So I installed the android sdk, google and samsung phone drivers and my phone is recognized in device manager.
When I go to flash the recovery.img via fastboot, it just sits there on "waiting on device" and ever goes anywhere. I also have a message on the bottom of the Nexus screen that says "FASTBOOT STATUS - FAILInvalid Command"
I'm at a point where googling is doing no good. Please help.
How can I get my phone to boot? How can I successfully flash the recovery image so I can go forward with root and be done with it?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
albundy2010 said:
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
Click to expand...
Click to collapse
Ok, how does one go about doing this on Win7x64?
Quides are on the forum? No idea what that means.
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
albundy2010 said:
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
Click to expand...
Click to collapse
Believe me, I've done that. Hours and hours worth.
Anyone care to help since apparently this information is so easy to locate? Fastboot simply isn't communicating with my phone and it will not boot past the google boot screen.
After many hours of trying, I figured it out. It had to do with the PDA net drivers. Basically, my phone would not boot up, preventing me from finishing the PDA net install. It kept hanging on "Installing PDA net to your phone" because, well, it couldn't install to my phone (since it was in fast boot mode).
I kept clicking on OK on the dialogue box and it would roll back, uninstalling the PDA net drivers. This was why fast boot could not communicate via cmd.
How I worked around this was by NOT clicking ok, hence not uninstalling the drivers.
It was an epiphany. And a pain in the arse.
So, if you have a similar issue, don't click ok on the dialogue. Leave it in limbo and work your command line magic!
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK
Hello guys, last week I installed the unofficial port of MM from here http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541 and everything was going well until yesterday the screen got frozen. I tried to reboot the tablet but It got frozen in the nvidia boot logo, so I tried to reinstall the ROM through fastboot. This step is when I realized that I cant write sometimes through fastboot. I can go into this mode but sometimes the writing failed until now everytime it fail. This is the error reported on the screen:
writing 'boot' ...
FAILED (remote: (FileWriteFailed)
This is a screen capture of the command window:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that I have broken the bootloader but I cant find the bootloader img for the tablet. Any help will be thanked!
If fastboot is working you still have a working bootloader. You are in fact in the bootloader. I'm not sure why fastboot write would fail. Perhaps the Windows fastboot driver should be reinstalled.
The bootloader is flashed by a "blob" file and is included with restoration images. If the bootloader does get damaged somehow, you can only boot to APX mode and only Nvidia can repair that.
Try do download and use minimal ADB.
Also reinstall the fastboot driver on your PC (deleting tablet from control panel/system/.... and connecting it again and istall again the driver you download from nvidia site or here on XDA)
best thing you can do if fastboot commadn don't work (happen to me) is download a recovery imagere (again nvidia developer site or here on XDA) and use the flashall.bat.
Magic done for me
and u can use it when u have only Apx? .... i cant find driver for it ... i have only black screen alltime
helllo ..! but still the above case wil work for the deactivated shield's..? my sheilds are now in apx mode..
Sent from my SHIELD Tablet using xda premium
If you can only boot APX mode you are stuck. There's no driver for APX mode so you can't do anything with it. Only NVidia can repair it at that point.
I don't know if this may be important but two days before this happened I encrypted the tablet. this may be affect the bootloader? The tablet is still unusable since I can't flash anything thought fastboot starts.
Hello everyone, I have a big problem with my device, it happens that the system started to fail and after that it turned off, when I turned on it stayed in a bootloop and I can only access the fastboot, the question is that my device does not have the OEM and I never did any modifications so it doesn't have recovery either.
So far I have tried to install for fastboot the boot.img and system.img from the original firmware but I get the error "remote: not allowed in locked state" because the bootloader is locked
Any recommendation?
Reflash original Stock ROM by means of ADB Sideload method
jwoegerbauer said:
Reflash original Stock ROM by means of ADB Sideload method
Click to expand...
Click to collapse
but I can't use recovery and it doesn't have TWRP installed either.
The truth is that I am quite new to this subject but it would help me a lot if you guide me through that process.
In addition, the stock rom offered by ulefone is in .tar.gz format
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
jwoegerbauer said:
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
Click to expand...
Click to collapse
How about, I was trying to access with ADB, however when I put adb devices, the device does not appear, perhaps because I did not have the USB debugging before the bootloop, I was trying with different commands and nothing happens, but it does appear in the device manager. I'm sure I have the correct drivers because I tried another device with USB debugging enabled and it works fine.
Attached image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should be obvious to you that ADB can't work as expected if USB debug option isn't got enabled on Android.
how can the bootloop be solved if only fastboot is available?
And the manufacturer flashing tool doesn't recognize the phone?
I cannot reflash the phone.
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Au123456 said:
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication View attachment 5479285
Click to expand...
Click to collapse
Do you want to be able to modify your system partition(including rooting the device) at some point in the future? If so, check the box beside the "never show this screen during boot again" then just swipe the slider at the bottom to allow modifications in the future.
Or
If you do not plan to modify your system partition in any kind of way, tap the "keep read only" button.
This happened to me multiple times, for me it was an error with flashing Treble GSI from google, tho i fixed it by going in fastboot mode/bootloader and on my PC to flash boot, lk, lk2, recovery (official one) and then reboot my phone, but you will delete the TWRP Recovery just so you know.
_________________________________________________________________________________________________________________________
NOTE: I don't know if this will work for you and might brick your device if you don't use correct ROM files...
_________________________________________________________________________________________________________________________
Also if it then boots into Fastboot mode than you can try flashing all files (It will factory reset your phone)
You have to install adb and fastboot on your PC
Commands:
cd *the path to adb and fastboot*
fastboot devices
fastboot flash *what you wanna flash* *filename of the file that you wanna flash*
For Example if you wanna flash boot it will be like ( fastboot flash boot boot.img ) if the filename is with .bin wich most new devices use it will be fastboot flash boot boot.bin
Hope that this helps