So I decided to go ahead and flash Lollipop to my Nexus 7 once I saw the factory image was out. All was going well, bootloader unlocked, and initiated the flash-all script, but then disaster. My cable moved ever so slightly and my tablet became disconnected after the flash process had wiped the previous version and the recovery. I get the bootloader just fine, fastboot communicates just fine for device check (fastboot devices returns a serial number), but adb does not. To make matters worse, I can't boot into recovery.
I've tried just about everything seemingly. Neither toolkit or manual command line work has worked so far. Both return:
FAILED (command write failed (invalid argument)))
then tries to send the bootloader, same response
then:
Rebooting into bootloader...
FAILED (command write failed (unknown error)))
sending 'boot' (5146 KB)
FAILED (command write failed (no such device or address)))
And now I'm at a loss. What did I do to goof this badly?
Update:
Rebooted PC, changed cable (desperate measures), tried flash-all after fastboot devices listed the serial number. Got as far as sending bootloader and then I got:
FAILED (data transfer failure (too many links)))
rebooting into bootloader...
FAILED (command write failed (Unknown error)))
Archive does not contain 'boot.sig'
error: memory full
HELP!
Every solution seems to involve the ADB in some way.. I just want to mention with the lack of functioning OS on the tablet, I have no adb capabilities which had led me to wonder what exactly happened...
WRX97 said:
Every solution seems to involve the ADB in some way.. I just want to mention with the lack of functioning OS on the tablet, I have no adb capabilities which had led me to wonder what exactly happened...
Click to expand...
Click to collapse
You're obviously not looking at any revelant guides. adb does not work except in custom recoveries or booted into the OS. It does not and never will work while in bootloader/fastboot mode. You should just skip the flash-all and run the commands in bootloader manually.
I've tried flashing individually to no avail. When I try anything, whether it be flashing new stuff on, erasing anything, its all met command write errors either for invalid arguments or unknown errors
Is my tablet a write off at this point? No one seems to have any advice...
WRX97 said:
Is my tablet a write off at this point? No one seems to have any advice...
Click to expand...
Click to collapse
Well without knowing what commands you are using and the errors you are receiving, it's hard to give more advice.
{
"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 comes from attempting a flash
No one has any suggestions for the above error messages?
Seems like maybe the fastboot drivers aren't working? Can you do fastboot devices and get a response?
Fastboot devices gets a response
Fastboot devices returns the device serial number, which makes me wonder what the true problem is.. Corrupted boot loader?
Related
So I have a HTC One Max that I've been trying to root and get s-off on.
There is some physical damage to the flex cable. (how I bought the phone) SD Card and camera do not work. I can make calls and hear music fine.
{
"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"
}
When trying to flash a custom recovery this is the error I get:
When using rumrunner it runs for about 4 minutes until it gets to this and errors out:
When using firewater and weaksauce this is all i get:
What im wondering if because it is ripped on the flex cable is it causing it not to flash.
I've tried different cables, usb ports, probably each above method 3+ times. reinstalling drivers.
colaicee said:
So I have a HTC One Max that I've been trying to root and get s-off on.
There is some physical damage to the flex cable. (how I bought the phone) SD Card and camera do not work. I can make calls and hear music fine.
What im wondering if because it is ripped on the flex cable is it causing it not to flash.
I've tried different cables, usb ports, probably each above method 3+ times. reinstalling drivers.
Click to expand...
Click to collapse
So whatever that rom you are currently on... factory reset the phone. Then push/run firewater again.
dottat said:
So whatever that rom you are currently on... factory reset the phone. Then push/run firewater again.
Click to expand...
Click to collapse
Im currently on stock rom. When i go to fashboot to flash recovery i get the error:
<bootloader> signature checking...
FAILED <remote: signature verify fail>
colaicee said:
Im currently on stock rom. When i go to fashboot to flash recovery i get the error:
<bootloader> signature checking...
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
No need to flash recovery. You are stock right? Boot to boot loader and chose factory reset from the prompt. Then reattempt Firewater etc.
Hey guys, i was trying to unlock bootloader with flashtool. Something went wrong, and phone restarted. oem lock and usb debugging was opened while unlocking bootloader. Now here is a screenshot to check drm keys. i dont have a backup of my drm keys. i couldnt unlock bootloader and couldnt root. snapchat's camera is scratchy but trackID works well.
what should i do? (sorry for bad english)
{
"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"
}
Blobs: generic error!
HUK: generic error!
FIDO_KEYS : Not provisioned ,SUNTORY error
I have bad news for you... your DRM keys are lost forever.
You're supposed to unlock the bootloader using official Sony method, don't understand why you attempted to do so using flashtool.
Try again using the link above. Then patch your kernel using this tool, specifically enable DRM-fix.
@mceyhan4
the keys are lost, but honestly its related to software side of some sony apps / camera. you can always use modified kernel which stimulates DRM keys (even if/when there arent any)
re build you stock modified kernel using http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
download supersu and put it in sdcard
- flash the modified kernel
- boot, goto twrp, flash SUPERSU from sdcard.
Reboot.
DONE
in the fastboot mode, ' adb device' command is not showing my device. i dont have time to make a backup and reset. dont have any other phone. and camera is not working well on whatsapp, snapchat or any other apps
i do regret too much.
mceyhan4 said:
in the fastboot mode, ' adb device' command is not showing my device. i dont have time to make a backup and reset. dont have any other phone. and camera is not working well on whatsapp, snapchat or any other apps
i do regret too much.
Click to expand...
Click to collapse
Obviously adb devices doesn't work in fastboot mode. You have to use fastboot devices
cant even install twrp
C:\Users\xxx\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
CB5A29LSMH fastboot
C:\Users\xxx\AppData\Local\Android\android-sdk\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.798s
C:\Users\xxx\AppData\Local\Android\android-sdk\platform-tools>fastboot flash boot twrp.img
target reported max download size of 536870912 bytes
sending 'boot' (20046 KB)...
OKAY [ 0.681s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.702s
C:\Users\xxx\AppData\Local\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
mceyhan4 said:
in the fastboot mode, ' adb device' command is not showing my device. i dont have time to make a backup and reset. dont have any other phone. and camera is not working well on whatsapp, snapchat or any other apps
i do regret too much.
Click to expand...
Click to collapse
always always use FLASHTOOL for xperia devices! works like a charm
am i supposed to downgrade first?
i cant unlock the bootloader without having a sim lock. front camera's screen flash is not working btw.
First time poster, hi to all and thanks in advance for any help you can provide.
My LG G5 H850 is some what in a bricked state, after a bad kdz update, my fault of course. It seems to have wiped all partitions.
The phone will only boot to fastboot, there is no recovery or download mode. Using the vol – and power, vol + and inserting the cable still sends me to fast boot.
I have the kdz, extracted that, extracted the dz. The bootloader is in an unlocked state.
When trying to flash the laf with fastboot flash laf laf.img the message I get is
Sending 'laf' (33448 KB) OKAY [ 0.819s]
Writing 'laf' FAILED (remote: 'cannot flash this partition in unlocked state')
fastboot: error: Command failed
Locking the bootloader gives a message FAILED (remote: 'device is locked. Cannot flash images')
adb commands don’t work error: no devices/emulators found
LGUP can’t see the device, there is no handset connected, please connect a handset(s).
I’ve looked at every post I can find regarding this be it about the LG or other devices and can’t get anything working.
Is there anything else I could try or some way to flash this partition to get to download mode?
As you can tell I’m a noob on this.
{
"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"
}
You're not a noob, at least when it comes to troubleshooting, so kudos for that.
Have you tried following this guide?
totalnoob34 said:
You're not a noob, at least when it comes to troubleshooting, so kudos for that.
Have you tried following this guide?
Click to expand...
Click to collapse
Thanks for the reply, I have looked at this but unfortunately, I can’t get the phone into download mode for the pc to detect it.
When I “Hold Vol+ and connect to PC while it was powered off” download mode flashes for a split second then straight back into fastboot.
I’m thinking if I can get the laf to flash I might be able to get into this, I have seen on other posts about “Shorting JTAG Pins” but most of those are for older LG models, can’t find anything about this regarding the G5.
Drewlandsupri said:
Thanks for the reply, I have looked at this but unfortunately, I can’t get the phone into download mode for the pc to detect it.
When I “Hold Vol+ and connect to PC while it was powered off” download mode flashes for a split second then straight back into fastboot.
I’m thinking if I can get the laf to flash I might be able to get into this, I have seen on other posts about “Shorting JTAG Pins” but most of those are for older LG models, can’t find anything about this regarding the G5.
Click to expand...
Click to collapse
Hmm, that may work, but I have no first hand experience on it unfortunately. JTAG pins usually exist on any model, but they may not be accessible to the user.
So I have been trying to get TWRP onto my Moto G Power 2020 phone to prep it for a custom rom but am completely stuck.
To start, I am on Ubuntu 21.10 but have had luck using ADB to install Lineage on a tablet so I am a bit beside myself.
I have been following these instructions https://www.getdroidtips.com/twrp-recovery-moto-g-power/
The steps I have done are:
Unlocked developer mode and turned on OEM Unlocking and USB Debugging.
Turned off the phone, held the Volume Down and Power Button down until to switches to Fast Boot Flash Mode (For some reason the Volume UP+ Power doesn't do anything but turn the phone on).
Opened Terminal in folder I have the TWRP file and ran "fastboot devices". The phone shows up.
BUT when I open terminal in the folder that the twrp file is in and run "fastboot flash recovery twrp-3.5.0-0-rav-sofia.img" it starts and then errors out with:
FAILED (Write to device failed (No such device))
fastboot: error: Command failed
I even tried running "fastboot boot twrp-3.5.0-0-rav-sofia.img" but it does the exact same thing but the error is:
FAILED (Status read failed (No such device))
fastboot: error: Command failed
I would love any assistance because I'm not seeing anything out there that reflects the issue that I am having. I know there are A/B partitions but I'm not sure if there is some additional step that I am missing.
{
"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"
}
One thing that I do notice is when I am looking at the phone screen when it is in Fast Boot Mode, it does say oem_locked at the bottom but I have OEM unlocking turned on.
Edit: I also saw that one issue might be that I need some OEM unlock code but the OEM code prompt is still giving that same error of No Such Device
Hey I'm new to this forum and Android Tablets in general. I have received a Vodafone Smart Tab 4G, which doesn't boot up. It's an old Tablet and it hasn't been used in a couple years. I want to see if I can make it boot up and test whether it's still usable for minor tasks. I thought I'd try to install an update using an SD card, but it's surprisingly impossible to find anything from an official source. The service menu does say "KTU84P release-keys" which seems to suggest that it has Android 4.4.4 installed.
What I've tried so far:
1: Go into the service menu and do a factory reset.
2. Try to find an update file to install through SD card method (to no avail)
3. Put some alleged stock roms onto an SD card and try to use the update function (fails on the verification step)
4. Installed ADB & Unsigned Mediatek Vcom Drivers on Windows 10. ADB has no connection to the Tablet.
5. Downloaded and tried SmartTab4G_Recovery_KK_benjaminwan to no avail. It gets stuck at "waiting for device".
6. Downloaded SP Flash tool, but failed to find a ROM for the Smart Tab 4G with a scatter file.
7. Out of desperation I tried to flash it with a Smart Tab 3G Rom which had a scatter file, but when I press download nothing happens.
My current understanding is that the standard service menu isn't meant to be used to flash the firmware. If I had an official update file I might have had some success, but I couldn't find one. All the other attempts involving a connection to my Windows 10 PC failed, which seems to indicate that I might be using bad drivers. I'm honestly at my wits' end and I don't understand why this is any more complicated than going to the manufacturers website, finding my device, downloading the most recent system software and flashing it through the service menu. Hope someone can help me out with this one.
Update: Tried a different computer. Partial success. Device manager actually recognized an Android device this time. I installed the usb driver and the recovery batch actually didn't get stuck on "waiting for device" this time. That's great news, although I didn't get much further. Here's what I got:
{
"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"
}
Thread can be closed. I got it after all with the help of the available information. Turns out the recovery.bat was a dead end. Not sure why it didn't work for me with the batch. I tried the approach explained here with cmd and it worked fine.
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
Once I was in the cwm everything went smoothly since verification was disabled and I could install a custom rom. This probably took me way longer than it should've, but at least it's working now.