To get my OPO back to stock to sell it, I decided to flash the factory image through fastboot, since after seeing the options I had, it was what I was most familiar with having owned a Nexus device in the past. I'm on a Macbook Pro, using only the fastboot and ADB files I need, which I have done in the past and it worked perfectly. Everything from the latest factory image has flashed, except the system.img file, which comes back saying this:
sending 'system' (844889 KB)...
FAILED (remote: data too large)
finished. total time: 0.003s
What can I do to fix this without bricking my device? I'm freaking out right now and don't know what to do. I don't want to unplug or exit fastboot mode in fear of bricking or doing damage to the device.
That usually means your adb/fastboot is outdated, how did you install it?
Transmitted via Bacon
I had the same problem, updating sdk helps, but if you don't want to download the large size, I'd suggest downloading Minimal fastboot and adb which works fine
Aditya Srinidhi said:
I had the same problem, updating sdk helps, but if you don't want to download the large size, I'd suggest downloading Minimal fastboot and adb which works fine
Click to expand...
Click to collapse
Minimal Fastboot and ADB should fix your problem.
Related
I'm on ICS and never upgraded to JB. I've just unlocked my bootloader so I can do NVFlash Backup and start flashing ROM's.
I unlocked without any problems. I've rebooted into bootloader and selected the USB icon. My computer found the drivers and correctly identified as 'ASUS Android Bootloader Interface'.
From the guide http://androidroot.mobi/pages/tegra3-guide-nvflash/
I ran the command
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
I got the following output from my Windows console
Code:
sending 'staging' (1002KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 7.935s
On my tablet appears
Code:
Failed to process command download:000fa98d error(0x120003)
Also the device now appears in my windows device manager with the following error
Code:
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I've not rebooted my tablet for fear of this question...
Have I bricked my tablet?
P.S. At this point I haven't attempted to reboot my device because I'm worried it might never come back.
So I've been crawling around the internet for anyone else who's had this problem and the only person with a similar issue is
http://forum.xda-developers.com/showpost.php?p=32222050&postcount=110
So since my OP, I've removed the USB cable from my laptop, plugged it back in and I can see my TF300.
When I run
Code:
fastboot devices
I get
Code:
00000 fastboot
Which I assume means my computer can see it?
At the moment I've still not rebooted. From what I've read Staging partition is applied at boot, which I assume means no changes have been made yet?
Because my transfer failed, will anything be applied from Staging on next reboot? Or should I run a command now to prevent any changes?
Thanks
Any help on this will be much appreciated.
Just to clarify, I've still not rebooted my device since I attempted the flash and seem to have access to Fastboot. I don't want to reboot unless I know it's safe to do so.
Thanks!
I thought this morning I'd try and change my drivers and run the command again.
I thought first I'd use Universal Naked Drivers, when I select the INF 'android_winusb.inf' file I get two options both called 'Asus Fastboot Interface'.
If I select either of these I get the following error
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tempered with.
The other option I do seem to have is under manufacturer 'Google, Inc.' I've got 'Android Bootloader Interface'. Is that any better?
So I eventually got the Universal Naked Drivers to work (after disabling Driver signature enforce from Windows boot options) and I could see my device in device manager and from 'fastboot devices'.
So I re-ran
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
And this time it also failed with another message. In my console showed
Code:
sending 'staging' (1002 KB)...
FAILED (remote: (AccessDenied))
finished. total time: 0.014s
And my TF300 displayed the line
Code:
Failed to process command download:000fa98d error(0x30010)
But this time, I can no longer see my device from device manager or 'bootloader devices'. Windows doesn't even make the 'device inserted' sound when I plug it in.
So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks
psjw12 said:
So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks
Click to expand...
Click to collapse
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.
daws said:
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.
Click to expand...
Click to collapse
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.
psjw12 said:
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.
Click to expand...
Click to collapse
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan
Claudii said:
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan
Click to expand...
Click to collapse
That's odd, it's like Fastboot says image was deployed but then it doesn't apply the change. Thank goodness there's a staging partition on Asus! I also had the problem of the device disconnecting whilst trying to flash and then not showing up.
How does the tablet show up in your device manager? As 'Asus Fastboot' or 'Android Fastboot'? Mine was ASUS and I was thinking of trying the Android driver instead.
I've not tried to flash mine again since trying, I'm going to wait for an appropriate time for me to have a heart attack if it all goes wrong
Edit: The next command it wants to issue is
Code:
fastboot -i 0x0b05 reboot
I wonder if that what makes it commit the changes? Hopefully someone can answer that for me.
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
There are How-to's on this site. It's probably unlocked now. Try flashing a custum recovery in fastboot.
aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
ken_alpha24 said:
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
Click to expand...
Click to collapse
I bought that off of eBay. I have tried to flash a custom recovery but it doesn't seem to get installed as well. After I do it, I only see the stock recovery but when I run the command fastboot flash recovery recovery.img it gives me the following message.
target reported max download size of 536870912 bytes
sending 'recovery' (8134 KB)...
OKAY [ 0.264s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.445s
But when I go to recovery, I only see the stock recovery. It seems like even-though the command are executed successfully on the computer, they are not applied to the phone. Any ideas?
Any ideas guys?
aroshlakshan said:
Any ideas guys?
Click to expand...
Click to collapse
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
zephiK said:
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
Click to expand...
Click to collapse
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
aroshlakshan said:
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
Click to expand...
Click to collapse
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
zephiK said:
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I got it working. I flashed TWRP on my phone and wiped the phone. Downloaded http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip , extracted the contents and flashed it with fastboot using the following commands.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
Hope this helps a newcomer like me. Thanks guys.
I figured that since the Motorola web site doesn't have the firmware for this yet I would post a link to my Dropbox so others have access to the firmware. This is for us cellular Moto g4 play xt1607 not sure if it will work for devices on a different carrier. If someone could make a backup of their current rom and test it out to let us all know if it does that would be great. Please hit the thanks button if this helps anyone. https://www.dropbox.com/s/i6jsafelq...y-DEFAULT_regulatory-DEFAULT_CFC.xml.zip?dl=0
This must be flashed with fastboot. If you do not know how to flash with fastboot there are tons of how to videos if you google it.
BACKUP YOUR DEVICE TO SD CARD OR PC BEFORE DOING ANYTHING!!!!!
DISCLAIMER: FLASHING ANYTHING TO YOUR PHONE HAS RISKS. IF YOU DO NOT KNOW WHAT YOU ARE DOING AND YOU HAVE JUST PURCHASED YOUR PHONE AND HAVE NOT UNLOCKED THE BOOTLOADER STOP!!!!! DO NOT CONTINUE. IM NOT SURE WHAT THE EFFECTS WILL BE IF YOU TRY FLASHING WITH A LOCKED BOOTLOADER, IT COULD BRICK YOUR DEVICE!!!!! I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY FLASHING THIS FIRMWARE. IF YOU DID SOMETHING WRONG AND DONT FOLLOW INSTRUCTIONS THAN THATS YOUR OWN T.S.
Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then download firmware, unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img sparsechunk.0
fastboot flash system system.img sparsechunk.1
fastboot flash system system.img sparsechunk.2
fastboot flash system system.img sparsechunk.3
fastboot flash system system.img sparsechunk.4
fastboot flash system system.img sparsechunk.5
fastboot flash system system.img sparsechunk.6
fastboot flash system system.img sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
DanHutchins said:
Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img sparsechunk.0
fastboot flash system system.img sparsechunk.1
fastboot flash system system.img sparsechunk.2
fastboot flash system system.img sparsechunk.3
fastboot flash system system.img sparsechunk.4
fastboot flash system system.img sparsechunk.5
fastboot flash system system.img sparsechunk.6
fastboot flash system system.img sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.
Click to expand...
Click to collapse
jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Is the bootloader unlocked?
jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What command gives the error?
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
DanHutchins said:
Is the bootloader unlocked?
Click to expand...
Click to collapse
jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Not sure. Did you make sure USB debugging is active for file transfer?
jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
jestyr8 said:
II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
Click to expand...
Click to collapse
That's because if you unplug the phone from the PC then plug it back in it defaults the USB debugging to charge only. If you get into twrp you can still put a custom ROM in root of phone to flash in twrp. I would try that then try to install the stock again. Be sure to have debugging set to file transfer.
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Please do as of now that's the best I can do. Everything worked fine for me. I have flashed the same file many times on my g4 play
jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Were you able to get back to stock?
DanHutchins said:
Were you able to get back to stock?
Click to expand...
Click to collapse
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.
jestyr8 said:
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.
Click to expand...
Click to collapse
I like cm13 there just aren't any real good themes for free. I don't mind donating to a dev. but if I can't test it out to see if I like it or not I don't want to pay.
I'm using the material glass theme along with stealth icons, i like it a lot
jestyr8 said:
I'm using the material glass theme along with stealth icons, i like it a lot
Click to expand...
Click to collapse
Looks cool.
DanHutchins said:
Looks cool.
Click to expand...
Click to collapse
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.
jestyr8 said:
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.
Click to expand...
Click to collapse
No problem, ask around for anyone able to make it flash able with twrp I'm sure someone can or at least give you instructions on how to do it.
USB debugging to file transfer
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
Where/how to "change debugging to file transfer" on Win-7?
Thanks!
Until now, my only experience was flashing a recovery image to Moto E2 with command:
Code:
fastboot flash recovery twrp.img
Neither I have to change "USB debugging to file transfer", nor I needed to use command
Code:
fastboot oem fb_mode_set
Is that something new and specific to Moto G Play 4th Gen?
Edit:
I have just unlocked the bootloader of my new Moto G4 Play and flashed a new logo file with command:
Code:
fastboot flash logo logo.bin
Still puzzled by "change debugging to file transfer"
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.
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.