In a long and painful process I've lost most of my trust in being able to revive my good old PH-1 to life.
When updates stopped, I moved to the Pixel 4 and gave the essential to my son, with the (unofficial) lineageos and TWRP installed. I surely changed to January back-to-stock, otherwise TWRP would not be installed. That's what happend next (summary):
- lineageos stopped working, system wasnt't booting any more
- Junior went into twrp, could not decrypt phone, wiped system, changed boot slot, for what he told me.
- downloaded Carbon Rom 5 and tried to flash it via twrp
- ignored the warning (no system installed)
- reboot to recovery leads to carbon rom recovery (errors showing up at the bottom). No adb connection can be established. Rebooting via hardware leads back to TWRP, obviously on the other slot.
- My decision: Back to Stock again! -> Reboot to bootloader. fastboot devices is showing my device.
[email protected]:~/devices/essential/QQ1A.200105.007_Jan2020-NOVENDOR$ ./flashallnowipe.sh
target didn't report max-download-size
sending 'abl_a' (780 KB)...
- phone keeps hanging there, no response.
Now there is no recovery any more. Pushing a new recovery does not succeed:
[email protected]:~/devices/essential/QQ1A.200105.007_Jan2020-NOVENDOR$ fastboot devices
PM1Lxxxxxxxx fastboot
[email protected]:~/devices/essential$ fastboot flash boot__a lineage-17.1-20201116-recovery-mata.img
target didn't report max-download-size
sending 'boot__a' (25737 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
Now: any hope? Where to start?
well, it has been quite while, but since I got through about the same you may be having here, let me give you a few hints that worked for me to resolve a soft-brick of my mata device.
Make sure you have the latest platformtools from from a reliable source.
Restart your computer and also your phone after any error message.
Best is to go back to stock, but after LOS you may need to flash the boot.img with the following command:
fastboot flash:raw boot_a|b [stock_boot.img]
Was in the same situation and this helped me to sort out the flash recovery problem:
fastboot flash:raw boot_a recovery.img
Just enter correct value - boot_a or boot_b and the right name of your recovery instead of rcovery.img
Btw. if you have problem to use flashall, then you can always flash manually - each part by yourself. They are listed in flashall file. You can read it by any text viewer
(I use a Linux Ubuntu based machine for works on phones. Even live distro booted with just on fly installed fastboot and adb works fine)
I was getting all sorts of fastboot errors, despite the device accepting ADB commands. The solution was to use a different USB cable on a different USB port. This Essential mata has a stubborn USB port. It only works with the correct cable, port combo. Some people say you must use USB3 other say they used USB2. I've seen the same thing with VR headsets only working on certain USB controllers. So keep trying different things.
Related
Hello,
I have the MZ601 (Xoom UK 3G) and had EOS Everest JB stable on it.
Now I wanted to go back to stock. I downloaded the original firmware from Motorola, flashed the img files with adb and everything was fine (I did not relock the bootloader). The first OTA went fine too, now I am on Android 3.0.1 (H.6.1.-38-1).
It now detects the next OTA (about 44 MB, 63.5.25.en.EU), downloads it, tries to install it but at about 1/3 of progress the green bot of ! appears. I reflashed the stock firmware several times now, same result.
Then I googled, flashed Tiamat CWM recovery, rooted the device and then did:
adb remount (got message: succeeded)
adb shell rm /system/recovery-from-boot.p (message: no such file or directory)
adb shell rm /system/etc/install-recovery.sh (no message, so guess it worked)
Now I have no idea what else to try. I'd like to get back to stock ICS.
edit: reflashed back to stock once more. This time I entered recovery mode before I applied the very first OTA and the green bot of ! already appears, what's wrong here?
Hi,
It looks like your problem is not big deal. Just try flashing again all the files and principally DON'T FORGET TO FLASH RECOVERY! And I don't see why wouldn't you lock bootloader , if you really wants it unlocked and go to stock ICS I'd recommend you to flash stock, lock bootloader and then you update, after you get to the version you want unlock again :thumbup:
Wish you the best luck
Any problems please give me an up!
Thanks for your reply!
I think I flashed recovery with the specific adb command (see below), not sure, not really an expert. :/ I even wiped dalvik cache and factory reset in cwm recovery before flashing back to stock.
Here's what I did in detail when reverting to stock:
I downloaded MZ601_H.6.1-38-1_Retail_Europe.zip from the official Motorola website, extracted all files and used these commands in adb:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Also, I noticed the green bot of ! appears after reboot when I enter recovery mode even before I flash the very first OTA (so just after flashing the stock files and reboot). Looks like recovery is somewhat broken or so?
I didn't want to relock the bootloader simply because I might want to root the device once I am back on stock ICS. Basically, I just wanted to get away from a custom ROM (Team EOS).
Would locking the bootloader make a difference for my success? According to google it doesn't but I am no expert to judge it right.
Yea, it looks like something is going wrong there...
Try downloading the files again, and then flash recovery. If you have no success try locking your BL, maybe it can works. The two times I went back to Stock I relocked my BL and had no problems to update via OTA. Then you relock your BL and use LordAIOTool to root again, which can easy your work...
Also you should try erasing system, recovery, cache and data before flashing, but it looks like what you did is fine.
Good luck
Thanks! I will give that a shot and post the result here.
By the way, that is one thing I read about and didn't dare to try yet: formatting system.
From what I read, after formatting /system the tablet will no longer be able to boot into android. In that case, how can I perform adb commands still? Afaik USB debugging has to be on but I will not be able to get into settings (due to lack of boot) and turn it on (and it will be off after reflashing afaik).
When you format system you can't boot in Android, but you can still flash things via fastboot, which uses a different protocol from adb. There was one time I had to format system to fix a cellphone, but if you don't want to try that, no worries , it may turn out without risking
I believe in order to upgrade you need to lock the BL. Once you update you can unlock it again.
Okay, downloaded the image again, this time via XDA. Suprisingly, all files were flashed in less than a min each (sometimes flasing system.img took half an hour or longer). Same result though. Since I forgot to lock the bootloader I flashed everything again after reboot:
Code:
>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 49.293s]
writing 'boot'... OKAY [ 2.155s]
finished. total time: 51.477s
>fastboot flash system system.img
sending 'system' (262144 KB)... FAILED (remote: (00120003))
finished. total time: 1196.176s
Not sure why it failed here, worked dozens of times. So I simply decided to reflash system.img once more in the same run:
Code:
>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.391s]
writing 'system'... OKAY [ 14.744s]
finished. total time: 40.136s
Worked fine apparently, then continued from there as normal:
Code:
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All went well this time, no error messages on the latest full reflash or locking bootloader. Then rebooted, and now it is stuck at the Motorola boot screen:
Code:
Failed to boot LNX 0x0004
Starting RSD mode 2
(charger information bla bla here)
Not sure why this happened and what this actually means? It won't boot up and since the bootloader is locked I can't enter recovery or anything. What do I need to do now?
Man... You forgot to flash the kernel (boot.img)!!! And it's probably appearing because of this small mistake!!! Now that you're on RSD Mode 2 you have to fix it another way... I never went to it (only went twice to mode 3), so sorry, I can't help you this time , I will search a little and see what I can do for you.
My mistake on posting, I did flash boot.img before that, corrected my previous posting.
Now I am stranded. And I can't even turn off the device on boot screen.
edit: rescued it, thanks to this posting:
Pushed power + vol up for reboot, waited 5 sec, then held vol down until fastboot appeared (kept pressing the button for about 17 sec until fastboot showed up).
Once there, I unlocked bootloader successfully again to flash all stock files. Xoom booted up bravely afterwards, phew.
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
Landorin said:
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
Click to expand...
Click to collapse
Glad you made it
Congrats!!
Hey I just got a tf300 for cheap and decided to put a rom on it. I got twrp installed and got root access. The version of twrp was too old and when I updated it and got into twrp I was prompted for a password. I figured something was wrong with the version of twrp I installed and I could go go back to the previous version of twrp by using fastboot but I am unable to get into fast boot.
I hold power and volume down but it boots right into twrp. I'm not able to get it to boot normally either it just boots into twrp. Has anybody run into this or have any ideas why I can't get power + volume down to bring up the recovery menu?
EDIT: Oh and adb doesn't see any devices either.
EDIT #2: It seems that my pc kind of recognizes that something is installed. It shows up on Device Manager as "Transformer" with the yellow exclamation point. I haven't been able to find any drivers that work with it. Anyone have a link?
EDIT #3: Ok I forced the universal naked drivers to install and adb devices now shows tf300 in recovery. When I put in adb reboot bootloader it comes up with the rck android and wipe data. I used fastboot to load my original twrp blob that was working fine. I get:
I:\tf300>fastboot -i 0x0b05 f
sending 'recovery' (6448 KB).
OKAY [ 1.895s]
writing 'recovery'...
OKAY [ 2.862s]
finished. total time: 4.757s
But when I go into recovery its still the version of twrp that was causing issues and it still asks for a password.
I figured i'd do a fastboot erase of boot, cache, recovery, system, userdata and then fastboot the original twrp blob but I get:
I:\tf300>fastboot erase boot
< waiting for device >
EDIT #4: It seems that adb recognizes by device but fastboot does not. Entering fastboot devices returns blank. Anyone know if this is an issue with the driver?
Anyone?
Ok after a couple of hours of hair pulling I figured it out.
Fastboot was definitely not working witht tf300 due to drivers. Since I couldn't find any drivers for windows. I booted up my trusty linux server, installed android-tools-fastboot and voila sudo fastboot devices shows the tf300t.
Reloading twrp did not work so I tried formatting the partitions by doing the following:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc (The first couple of times I did this, I missed this one which caused bootloader to hang when installing twrp)
fastboot erase cache
I then installed the working version of twrp I had originally by:
fastboot –i 0x0b05 flash recovery twrp.blob
I then rebooted into recovery and twrp works great without any password prompt or errors that it could not access the partitions.
I user twrp to flash 2.7.01 version of twrp and rebooted, I then used twrp to flash CM11 snapshot M7 and gapps, cleared cache and davlik and then rebooted.
The CM spinning animation took a while but then it booted into CM.
The topics I got all this info from are too numerous to mention. I hope this helps anyone that has ran into the same situation.
Hi, so I got this phone about a month ago, with stock rom and filled up with bloat and unnessecary crap. So being the fundamentalist I am, I rooted this phone too (5th android phone I've had), and started playing with it.
By default, the bootloader is locked, so I unlocked it using Huawei's website unlock helper and fastboot.
I have no memory card to go with this phone, so I've had to try out the fastboot/adb way of doing this, and so far it's been a hit and miss.
I've been testing with SlimStock KK, and with Ascend G6 Mod, and I'm able to flash the boot and recovery successfully, but when it comes to flashing the system, it fails. Here's the output of that:
Code:
Karls-MBP% fastboot devices
90587873 fastboot
Karls-MBP% fastboot flash system /Volumes/ODIN/karleirik/Downloads/Firefox/Huawei_Ascend_G6-L11_Modded_B370_ROM/SYSTEM.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.039s]
sending 'system' (1048576 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (Undefined error: 0))
finished. total time: 26.000s
So right now my device is softbricked. Does anyone know how to get around this problem ? Or have another approach to flashing it?
Edit: I might add that I've tried different system images, and different hardware USB ports on my laptop to no avail. I have also tried the flashall, which fails due to no product ID and adb sideload <zip> fails because of a timeout:
Code:
* failed to write data 'protocol fault (couldn't read status length): Connection reset by peer' *
- Phossk
Phossk said:
Hi, so I got this phone about a month ago, with stock rom and filled up with bloat and unnessecary crap. So being the fundamentalist I am, I rooted this phone too (5th android phone I've had), and started playing with it.
By default, the bootloader is locked, so I unlocked it using Huawei's website unlock helper and fastboot.
I have no memory card to go with this phone, so I've had to try out the fastboot/adb way of doing this, and so far it's been a hit and miss.
I've been testing with SlimStock KK, and with Ascend G6 Mod, and I'm able to flash the boot and recovery successfully, but when it comes to flashing the system, it fails. Here's the output of that:
So right now my device is softbricked. Does anyone know how to get around this problem ? Or have another approach to flashing it?
Edit: I might add that I've tried different system images, and different hardware USB ports on my laptop to no avail. I have also tried the flashall, which fails due to no product ID and adb sideload <zip> fails because of a timeout:
- Phossk
Click to expand...
Click to collapse
Try putting the .zip file inside your adb and fastboot files and just type the .zip file name when flashing instead of the whole path to the .zip
Hope this will solve your problem.
Hi,
I'm tring to flash this twrp https://twrp.me/oneplus/oneplus6.html after unlocked the bootloader on my new OP6 but this is what I get from ADB:
D:\Trash\ADB>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.578s
Any hints??
Thx in advance!
Edit: First time I got in fastboot mode (to unlock bootloader), when I sent command "ADB devices" I saw the usual serial. Now after unlocked the bootloader, once I go in fastbode mode, there's no more devices listed.
What went wrong??
zappomax said:
Hi,
I'm tring to flash this twrp https://twrp.me/oneplus/oneplus6.html after unlocked the bootloader on my new OP6 but this is what I get from ADB:
D:\Trash\ADB>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.578s
Any hints??
Thx in advance!
Edit: First time I got in fastboot mode (to unlock bootloader), when I sent command "ADB devices" I saw the usual serial. Now after unlocked the bootloader, once I go in fastbode mode, there's no more devices listed.
What went wrong??
Click to expand...
Click to collapse
I don't get it. The TWRP site you posted said to fastboot into TWRP image, then flash recovery from TWRP itself. It seems like you tried to flash the image directly. As the TWRP site you posted explains, this is not how it works anymore.
Just follow the instructions from the site.
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
Click to expand...
Click to collapse
Command is "fastboot boot recovery.img" and when you're in twrp flash twrp zip
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
After unlocking the bootloader (and subsequent factory reset) did you reenable the developer menu and the USB debugging? Does your device asks for debugging permission?
akxak said:
After unlocking the bootloader (and subsequent factory reset) did you reenable the developer menu and the USB debugging? Does your device asks for debugging permission?
Click to expand...
Click to collapse
Sure
zappomax said:
Sure
Click to expand...
Click to collapse
Sounds like your usb drivers are faulty. Try a different computer. Happened to me before with a Pixel XL.
Sometimes it helps just to reconnect the phone.
Sorry to all...
I just needed to read the instructions carefully on TWRP site...
So stupid and hasty
There's no recovery on this device, it's included in the boot partition. So fastboot boot the image, and then flash the installer zip.
I have a similar problem.
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen is ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could all adb commands on this devices even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason?
Now, after trying different drivers from Google, samsung and oneplus, I am sure that the problem is from phone's end because in all cases my oneplus1 and oneplus7 are detected in adb devices without fail. Request you to read carefully before replying, since i am out of options now, tried almost all remedies available elsewhere.
ashish_jha said:
I have a similar problem.
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen is ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could all adb commands on this devices even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason?
Now, after trying different drivers from Google, samsung and oneplus, I am sure that the problem is from phone's end because in all cases my oneplus1 and oneplus7 are detected in adb devices without fail. Request you to read carefully before replying, since i am out of options now, tried almost all remedies available elsewhere.
Click to expand...
Click to collapse
ADB Driver Installer v6.0 for Windows 10 64 Bit (2023)
ADB Driver Installer v6.0 Latest for Windows 10> It helps you to connect Android Smartphones and Tablets to Windows 7/ 8/ 10/ XP/Vista x64/ x86
www.driversforum.net
I'm trying to downgrade my Pixel back to 9. Few reasons - unimportant.
I have the latest platform tools, adb and fastboot both find the phone fine.
I've downloaded the latest stock image from the Google site.
But I get a very odd error
Sending 'bootloader' (8493 KB) OKAY [ 0.199s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Everything is in the same folder, I've tried using the full path and not relative paths. Tried different cables and even different stock images. I've also got older versions of platform tools so tried earlier versions of fastboot.
I'm lost. What else is there to try/do?!
teapea said:
I'm trying to downgrade my Pixel back to 9. Few reasons - unimportant.
I have the latest platform tools, adb and fastboot both find the phone fine.
I've downloaded the latest stock image from the Google site.
But I get a very odd error
Sending 'bootloader' (8493 KB) OKAY [ 0.199s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Everything is in the same folder, I've tried using the full path and not relative paths. Tried different cables and even different stock images. I've also got older versions of platform tools so tried earlier versions of fastboot.
I'm lost. What else is there to try/do?!
Click to expand...
Click to collapse
Out of curiosity, which variant is this? Vzw? Google? Have you done updates in this way before? Or maybe only OTA updates?
cheers
Google stock image, using Google drivers, platform tools from full SDK. Done many many flashes this way - although never "downgraded" before. I stupidly hit update on my Pie stock image and it went to 10 so trying to go back.
I did read it needed have no "pending installs" in order to flash - but that doesn't make much sense, but currently OTAing to latest 11 version.
I did have Magisk root on my original 9, and the OTA to 10 obviously killed this.
Happy to kill all data and start again, I just need 9 back on this phone!
Only thing I've not tried is a different computer - will need to wait until I get back from the office to try another one though, but I've used my own laptop many times before which is why it's so confusing!
And to confirm - another laptop, totally fresh image - same problem...
teapea said:
And to confirm - another laptop, totally fresh image - same problem...
Click to expand...
Click to collapse
I know it seems simple but bootloader is unlocked and usb debugging is enabled? Also, are file extensions visible? That could cause problems too
Here's how I downgrade once in fastboot:
fastboot --slot=all flash bootloader bootloader.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=all flash radio radio.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(current slot) --skip-reboot update image.zip(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(other slot) --skip-reboot update image.zip(or drag and drop to cmd window)
Then you enter recovery and wipe/format data and reboot to system after
Yeah - well I found the problem.
I was launching fastboot via "adb reboot fastboot" - which then put the phone in a screen which said "fastbootd" in red at the top. I'd never seen it before, but said fastboot so thought it was OK.
As soon as I remembered to reboot into fastboot with the volume down key - we're all good!
Never seen the fastbootd screen before - no idea what that was all about - I assume after installing Android 10/11 this was the new fastboot screen but clearly not!
Either way - I'm back on 9 and getting things back to normal. Systemless hosts is causing my grief with adblocker at the moment, but not investigated that too much.
So I guess the error message wasn't the right one, but just a generic one based on me not being in the right fastboot mode!
Thanks all for looking and offering advice, appreciate it - but I guess you'd never guess the issue with that error message!
the adb command is adb reboot bootloader. There may be others not sure, but that's the one I've used if the phone was on and booted.