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.
Related
Ok, so when I turn on the phone, it gets stuck on the HTC screen logo forever. With the volume down and power button, I'm able to get into hboot/hboot usb plug when connected to the computer. The recovery, factory reset, image crc options don't work. In my linux computer, when I type fastboot devices, I'm able to get serial number of the phone. The picture links below summarize my current state
{
"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"
}
The commands that I've tried are below.
(command): /fastboot devices [output] SH******** fastboot -- (note: here I did get my serial number but I know better than to post it here.
(command): ./fastboot oem rebootRUU [output]... FAILED (status malformed (1 bytes))
(command): ./fastboot flash zip PD15IMG.zip [output]: sending 'zip' (322693 KB)... FAILED (status malformed (1 bytes))
Tools in hand: android-sdk-linux, linux mint, PD15IMG.zip and phone
note: I also tried all of the above commands on windows 7 home premium 64 bit with adb installed and got the same error messages from fastboot. I tried the official htc bootloader unlocker but kept getting that error: 120 battery less than 30%.. although my battery is fully charged and that stopped the tool from unlocking the boot loader.
I read somewhere If i find the orginal stock recovery image, I might get out of this but I cannot find it anywhere yet.
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
RUU?
gesange said:
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
Click to expand...
Click to collapse
Yeah I tried RUU and it gets stuck all the time at Rebooting bootloader or waiting for bootloader
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
hi guys, i unlocked my oneplus6 phone after that i used autoroot in toolAllinOne..all good, i instaled magisk apk and tryed to install but it says always failled. But that is not the problem, the problem is now when the phone is opened the program recognize abd device and model but when i go in bootloader it recognize abd device but model not anymore. the drivers i thing are installed well because abd is detected. Anyone know why model is not detected? I cannot install .img file for twrp.
P.S. the phone works well and it have stock software.
{
"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"
}
This driver appear just in bootloader mode, when phone is opened it doesnt appear.
solved.
StyL3sX said:
solved.
Click to expand...
Click to collapse
How?
I could not even find my device when i use fastboot devices command in fast boot mode. Because of this i could not flash twrp also.
I installed drivers and connected the phone in all sorts of modes (usb debugged, usb undebugged, fastboot, system on, switch off mode).
When the phone is connected in switch off mode, i could see something like "usb device not found" message in pc. Tried changing desktop. But it's the same result.
I'm unlocked and on stock open beta 4 pie.
StyL3sX said:
hi guys, i unlocked my oneplus6 phone after that i used autoroot in toolAllinOne..all good, i instaled magisk apk and tryed to install but it says always failled. But that is not the problem, the problem is now when the phone is opened the program recognize abd device and model but when i go in bootloader it recognize abd device but model not anymore. the drivers i thing are installed well because abd is detected. Anyone know why model is not detected? I cannot install .img file for twrp.
P.S. the phone works well and it have stock software.
This driver appear just in bootloader mode, when phone is opened it doesnt appear.
Click to expand...
Click to collapse
Please see my post in this thread: https://forum.xda-developers.com/showpost.php?p=77823085&postcount=2
my zenfone 4 problem:
it is charging but i am stuck at asus logo with rotating circle and whenever i am trying to get into droid boot it is showing an android with yellow helmet
{
"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"
}
As long as a phone powers on it's NOT hardbricked, but softbricked if Android doesn't get properly started.
even if it is soft bricked i am not able to get into recovery mode this was showing:
Re-flash phone's STOCK ROM.
damn, i am not able to get into fastboot dude that's what it is all about if i would be able to get into fastboot i would have flashed my phone long time ago.when i ty to get into fastboot android sign with yellow helmet appears.
My zenfone 4 problems:
access to droidboot or recovery (stuck at android icon with a yellow helmet), so i cant flash a rom or firmware.
Tried different combo keys, but always stuck with that android icon.
You typically re-flash a STOCK ROM by means of ADB Sideload method.
ook so for using adb sideload method u need to get into droid boot what i am saying it i am not able to get into droid boot mode and everytime i try an android sign with yellow helmet appears.
You are absolutely WRONG.
What you have to do is running ADB commands as follow
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_FILE_ON_PC_HERE>
i am noob please can u tell me the steps elaborately OKAY,
NOW I HAVE GOT IT BUT IS NOT SOWING ANY DEVIICES I HAVE CONNECTED MY MOBILE SEE:
Then you obviously never have enabled USB Debugging on phone what is prerequisite to run ADB commands.
jwoegerbauer said:
Then you obviously never have enabled USB Debugging on phone what is prerequisite to run ADB comso
Click to expand...
Click to collapse
so,now what should i do?
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.