Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Your command is wrong, The command to use is: fastboot flash recovery twrp.the name of your file.img
Just like @jawmail said, you're flashing twrp on the bootloader """slot""
-fastboot flash recovery ***TWPR***.img
-fastboot reboot-bootloader
When your phone reboots, using your volume keys, search for "recovery" and using the power button, confirm it.
PROFIT
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Haha. Thanks. Yeah I am really lucky. My phone is working now thanks. Just coming from the S6 Edge. Very different rooting method from that, so yeah I should be way more careful. Thanks for the awesome guide, btw Heisenberg. Running PureNexus with ExperimentalX kernel. Such an amazing combo.
Heisenberg said:
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Click to expand...
Click to collapse
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Puck24 said:
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Click to expand...
Click to collapse
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Heisenberg said:
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Click to expand...
Click to collapse
guess it's a corrupted file?
Actually, I just tried flashing it one more time, rebooted to the bootloader with the phone, not with the command. Then I also used the phone to enter into recovery, not by issuing commands. And it works
Sent from my Nexus 6P using XDA Free mobile app
First post here at XDA - before I start with my problem, I should say thanks to everyone who posts here. I've come across this site so often when looking for information and always found it to be very helpful.
I was taking a Photo Sphere photo a few weeks ago, and after the photo had been taken, and during the processing/rendering stage, I looked away from my phone while holding it to let it work. I looked down to see the finished result about 30 seconds later and saw the Google startup screen. It appears that somehow, taking a Photo Sphere photo may have soft bricked my 6P, but I have no idea how. The phone itself was working perfectly normally prior to that.
I kept manually restarting it, powering it off, booting to recovery and restarting to see if I could get it back to normal with no success. It would occasionally, maybe one in twenty times, get to the Android boot animation, but would freeze after around 5 seconds on that, then restart again. Eventually, I thought to clear the cache partition via TWRP, so I did so and it then booted and loaded Android as normal. However, one of the first things I did was go to Settings to reset the time as it was wrong, and, as soon as it displayed the Settings screen, the phone restarted again, and no amount of cache clearing has resolved the issue since.
It's a 64GB 6P running Marshmallow 6.0.1, unlocked and rooted via Heisenberg's excellent guide and running TWRP 3.0.2.0, which was the latest available when I rooted. Right now, upon starting, it shows the "Your device software can't be checked for corruption. Please lock the bootloader." message as normal, then the Google logo, then it restarts and does the same again. I can access recovery mode as normal.
Does anyone have any ideas what steps I need to take to get my 6P operable again? Given that it booted after I wiped the cache then rebooted when I went to settings, my relatively uneducated presumption is that the root has somehow gotten messed up, but I don't know enough about troubleshooting Android to resolve it myself. I'd obviously prefer to avoid wiping it and losing data if possible. Although I'm a computer geek, I'm not 100% sure about Android ADB/fastboot commands and what to run to resolve this issue, so I thought I should defer to the experts here. I was considering flashing the factory image (part 11 of Heisenberg's guide) to see if that helped, but wasn't sure if that's the best first step to try at this point so thought it best to seek some advice rather than turn a soft brick into a hard one.
Thanks for any and all assistance!
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-VN1
Device is UNLOCKED.
Qfuse Status: ENABLED.
Well, maybe the above is a bit too much to read...my bad habit of being verbose. Here's a tl;dr version;
Unlocked and rooted 64GB 6P running Marshmallow is boot-looping at the bootloader unlocked screen
Wiping cache only temporarily resolved
Can access recovery and fastboot as normal
Any ideas?
Well, mine appears to have done the same exact thing, but I wasn't using photosphere. Before I continue, here's my story...
I'm on vacation from Sept 1st to Sept 5th, and on the 4th(yesterday), I was browsing using Chrome before it froze and shut off on me, which then turned into a bootloop with the Google screen. Next, I did what I normally do when I have a problem, I head to recovery(depending on what I was last doing, I'd delete a file that I know caused it), but instead, I couldn't get into recovery. I tried maybe about 10 times and got into recovery twice. I removed all overlays that had to do with Substratum and deleted my cache/dalvik cache, rebooted and I got to the Android updating screen. It went through the process, froze and rebooted again. Now, I'm at the point where it's just the Google screen. I can get into the Bootloader, but nothing else. I'm thinking I'm having hardware failure or something. I attempted to do a factory image restore twice now, doing the third one as I type this before I contact Google, but yeah... I can't get into recovery or past the Google screen. Only the bootloader is accessible.
Now... As for your situation, download Wugfresh Nexus Toolkit, or follow later on in Heisenberg's guide to restore the factory image without deleting the userdata partition. There may still be a chance for you to get your data back, but for me... nah. Good luck.
Hey Curiousn00b, thanks for sharing your story. It seems really weird that they're just dying so suddenly and so fatally with no hardware failures. I'm wondering if this is part of a larger issue.
I just tried flashing the factory images for MHC19I as per part 11 of Heisenberg's guide and, alas, no luck. The images flashed fine, but it's still doing the same thing as before.
Is there anything else I can do to get it to a usable state again without completely wiping it? Should I try another factory image, maybe an earlier one? And, if I do have to wipe it, can I re-flash TWRP recovery and take a backup first?
Here's my log output for confirmation. Thanks again, I appreciate your reply.
Code:
C:\SDK\platform-tools>fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.237s]
finished. total time: 0.345s
C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
C:\SDK\platform-tools>fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.202s]
writing 'radio'...
OKAY [ 2.855s]
finished. total time: 4.060s
C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\SDK\platform-tools>fastboot flash boot c:\angler\images\boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12045 KB)...
OKAY [ 0.287s]
writing 'boot'...
OKAY [ 0.387s]
finished. total time: 0.676s
C:\SDK\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\SDK\platform-tools>fastboot flash cache C:\angler\images\cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.018s]
sending 'cache' (5752 KB)...
OKAY [ 0.161s]
writing 'cache'...
OKAY [ 0.226s]
finished. total time: 0.409s
C:\SDK\platform-tools>fastboot flash recovery C:\angler\images\recovery.img
target reported max download size of 494927872 bytes
sending 'recovery' (12977 KB)...
OKAY [ 0.337s]
writing 'recovery'...
OKAY [ 0.406s]
finished. total time: 0.747s
C:\SDK\platform-tools>fastboot flash system C:\angler\images\system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.561s]
sending sparse 'system' (478066 KB)...
OKAY [ 12.529s]
writing 'system'...
OKAY [ 6.772s]
sending sparse 'system' (483054 KB)...
OKAY [ 12.458s]
writing 'system'...
OKAY [ 7.038s]
sending sparse 'system' (480089 KB)...
OKAY [ 12.603s]
writing 'system'...
OKAY [ 14.026s]
sending sparse 'system' (469850 KB)...
OKAY [ 12.264s]
writing 'system'...
OKAY [ 22.259s]
sending sparse 'system' (55828 KB)...
OKAY [ 1.530s]
writing 'system'...
OKAY [ 2.856s]
finished. total time: 104.912s
C:\SDK\platform-tools>fastboot flash vendor C:\angler\images\vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185185 KB)...
OKAY [ 4.567s]
writing 'vendor'...
OKAY [ 15.101s]
finished. total time: 19.670s
C:\SDK\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.008s
C:\SDK\platform-tools>
Seems like it's possible for you to be in the same exact situation as me, unless you can boot into recovery. I can't do that.
If you can boot into recovery, just take your files off the device and go for a full wipe. I think my device hard bricked itself somehow... You may be soft-bricked, but in the worst case, hard bricked. :c
Yep, I can't boot into recovery either right now because I flashed the factory image. I'll try to re-flash the TWRP recovery and see how it goes.
I can't believe a software issue can get to the stage of hard-bricking your phone while doing nothing other than unlocking and rooting it, and even putting it back to factory and doing a full wipe doesn't resolve it. I really hope I don't get to that stage, although it's disappointing to hear that you've had that experience. Thanks again for your feedback, I'll update once I've attempted to re-flash.
So I finally got around to flashing the TWRP 3.0.2.0 recovery again and still no dice, so I made a start on the backup process.
One thing I wanted to check before I do the full wipe and reinstall stock, though - my partitions in TWRP showed this from the Backup screen;
Code:
Boot (32MB)
System (1850MB)
System Image (3072MB)
Vendor (173MB)
Vendor Image (200MB)
Data (0MB)
Cache (0MB)
Recovery (32MB)
EFS (8MB)
This may just be paranoia, but which of those is the user data (apps, files, photos etc.) stored in? I get that the Data partition is wiped when doing the stock image install, so that's fine, but I presume System would be the OS itself - and I'm pretty sure I have more than 2-3GBs of data on my 6P, but the largest there is 3GB.
Also, using Backup from the TWRP main menu, how do I restore the user data once I've got it back up and running again without killing the OS again? Can I selectively choose what to restore?
I've copied the TWRP backup folder to my laptop using adb pull, so that's safely stored there for now. Just wanted to check before I totally wipe everything and start clean.
Thanks.
MarkB16 said:
So I finally got around to flashing the TWRP 3.0.2.0 recovery again and still no dice, so I made a start on the backup process.
One thing I wanted to check before I do the full wipe and reinstall stock, though - my partitions in TWRP showed this from the Backup screen;
This may just be paranoia, but which of those is the user data (apps, files, photos etc.) stored in? I get that the Data partition is wiped when doing the stock image install, so that's fine, but I presume System would be the OS itself - and I'm pretty sure I have more than 2-3GBs of data on my 6P, but the largest there is 3GB.
Also, using Backup from the TWRP main menu, how do I restore the user data once I've got it back up and running again without killing the OS again? Can I selectively choose what to restore?
I've copied the TWRP backup folder to my laptop using adb pull, so that's safely stored there for now. Just wanted to check before I totally wipe everything and start clean.
Thanks.
Click to expand...
Click to collapse
Did you verify any contents in TWRP that you pulled to ur PC? . In TWRP go to advanced and then file explorer, you should see your data.
Edit: Data would be where the user data is stored (pictures, downloads, etc.)
I terms of restoring data, I've always gone with Titanium Backup but in this case not sure you'd be able to as it sound like u can't boot into the OS and see ur apps?
spunks3 said:
Did you verify any contents in TWRP that you pulled to ur PC? . In TWRP go to advanced and then file explorer, you should see your data.
Edit: Data would be where the user data is stored (pictures, downloads, etc.)
I terms of restoring data, I've always gone with Titanium Backup but in this case not sure you'd be able to as it sound like u can't boot into the OS and see ur apps?
Click to expand...
Click to collapse
Yep, if I go to TWRP, I can view the backups in the \sdcard\TWRP\backups\[serial number] folder, and now that I've done adb pull, they're on my hard drive, too.
Exactly, yeah, it's still boot-looping, so I can't get into the OS to run Titanium Backup or migrate any data. It's still looping at the "Device can't be checked for corruption" screen. I followed Heisenberg's guide to re-flash the stock images and didn't flash userdata. Why would the data partition show as being empty in TWRP unless the partition has been royally messed up when the phone had it's original heart attack?
And, if the data partition is where userdata is stored, I presume that means the data on the phone is already gone? Dumb question, I think I know the answer already, but don't understand how it could have happened when I didn't wipe it myself.
MarkB16 said:
Yep, if I go to TWRP, I can view the backups in the \sdcard\TWRP\backups[serial number] folder, and now that I've done adb pull, they're on my hard drive, too.
Exactly, yeah, it's still boot-looping, so I can't get into the OS to run Titanium Backup or migrate any data. It's still looping at the "Device can't be checked for corruption" screen. I followed Heisenberg's guide to re-flash the stock images and didn't flash userdata. Why would the data partition show as being empty in TWRP unless the partition has been royally messed up when the phone had it's original heart attack?
And, if the data partition is where userdata is stored, I presume that means the data on the phone is already gone? Dumb question, I think I know the answer already, but don't understand how it could have happened when I didn't wipe it myself.
Click to expand...
Click to collapse
You should be able to confirm if the data is really there or not by going into TWRP > Advanced > File Manager.
You should also check to see if data and cache are mounted in TWRP.
I haven't gone over Heisenberg's steps yet but, since you've already attempted to flash userdata, whatever you had is most likey gone.
Try the following via fastboot for erasing everything and starting from scratch.
NOTE: THE FOLLOWING COMMANDS WILL ERASE EVERYTHING ON YOUR PHONE.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader [name of your file].img
fastboot reboot-bootloader
fastboot flash radio [name of your file].img
fastboot reboot-bootloader
fastboot flash recovery [name of recovery file].img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot format userdata
fastboot format cache
That's what I'm saying - at no point have I ever entered the command fastboot erase userdata - I specifically wanted to keep the data and do a backup, and the phrase userdata would be a big red flag to me, so I wouldn't enter it unless I knew for sure the data was already gone. I'm wary of even touching the data partition, so I've been sure to follow all of the commands very carefully. I've been in I.T. for a while, I know the danger of running the wrong command.
I can see that there are data files in the backups, however the data.ext4.win file is only 6KB, so I guess there's no data there.
I don't know how to mount the data and cache partitions in TWRP - I can see the option to do it, but have no idea what it does.
Thanks again.
Mine was the Camera app doing the HDR processing. For the first few times it happened, it was random - the crash and bootloop will happen after taking 2-3 photos. Today, it finally hung while processing HDR and it never recovered. Sigh, seems like I need to send my phone to Huawei. I have tried all sorts of flashing to no avail.
kurtisnet said:
Mine was the Camera app doing the HDR processing. For the first few times it happened, it was random - the crash and bootloop will happen after taking 2-3 photos. Today, it finally hung while processing HDR and it never recovered. Sigh, seems like I need to send my phone to Huawei. I have tried all sorts of flashing to no avail.
Click to expand...
Click to collapse
So my phone isn't the only one with an aversion to taking photos? I don't understand how just taking a photo could cause this unless there's a massive software bug somewhere that requires a very specific set of conditions to brick your device. Would you mind letting me know what Huawei say to your issue? I'm curious as to what they think could cause a failure of this degree.
MarkB16 said:
That's what I'm saying - at no point have I ever entered the command fastboot erase userdata - I specifically wanted to keep the data and do a backup, and the phrase userdata would be a big red flag to me, so I wouldn't enter it unless I knew for sure the data was already gone. I'm wary of even touching the data partition, so I've been sure to follow all of the commands very carefully. I've been in I.T. for a while, I know the danger of running the wrong command.
I can see that there are data files in the backups, however the data.ext4.win file is only 6KB, so I guess there's no data there.
I don't know how to mount the data and cache partitions in TWRP - I can see the option to do it, but have no idea what it does.
Thanks again.
Click to expand...
Click to collapse
If at anytime you did 'fastboot flash userdata userdata.img' you've overwritten the data partition and lost the data :-/ wish I could help more...
MarkB16 said:
So my phone isn't the only one with an aversion to taking photos? I don't understand how just taking a photo could cause this unless there's a massive software bug somewhere that requires a very specific set of conditions to brick your device. Would you mind letting me know what Huawei say to your issue? I'm curious as to what they think could cause a failure of this degree.
Click to expand...
Click to collapse
I've just collected my phone again from Huawei. They replaced the motherboard (new imei number). Sent in at 11.30am today and is ready by 4pm. Applaud Singapore Huawei service center for their super fast turnaround time. Totally was expecting at least a week of repair lol.
Mine was bricked completely - internal storage was accessible from twrp but that was about it. Flashing new roms with everything wiped didn't help. Flashing pure nexus also will sometimes hang and reboot. Sometimes it'll be successful.
spunks3 said:
If at anytime you did 'fastboot flash userdata userdata.img' you've overwritten the data partition and lost the data :-/ wish I could help more...
Click to expand...
Click to collapse
But I didn't, that's what I mean - it's like the data partition has been wiped for no reason at all, or it was part of the initial failure. I haven't run any commands which should touch that partition.
Am I right in thinking that, at this stage, the my data is unrecoverable, and the best bet is just to try to get the phone back up and running again? Are there any other checks I could try to confirm the data is already gone?
Thanks, I do appreciate your input.
kurtisnet said:
I've just collected my phone again from Huawei. They replaced the motherboard (new imei number). Sent in at 11.30am today and is ready by 4pm. Applaud Singapore Huawei service center for their super fast turnaround time. Totally was expecting at least a week of repair lol.
Mine was bricked completely - internal storage was accessible from twrp but that was about it. Flashing new roms with everything wiped didn't help. Flashing pure nexus also will sometimes hang and reboot. Sometimes it'll be successful.
Click to expand...
Click to collapse
Nice, glad they got it sorted so quickly for you. Hoping I can get mine running again, but I'll contact them if I can't.
MarkB16 said:
But I didn't, that's what I mean - it's like the data partition has been wiped for no reason at all, or it was part of the initial failure. I haven't run any commands which should touch that partition.
Am I right in thinking that, at this stage, the my data is unrecoverable, and the best bet is just to try to get the phone back up and running again? Are there any other checks I could try to confirm the data is already gone?
Thanks, I do appreciate your input.
Nice, glad they got it sorted so quickly for you. Hoping I can get mine running again, but I'll contact them if I can't.
Click to expand...
Click to collapse
Hmmmmm... The only other thing that comes to mind is trying something like a fastboot pull command
I've done a full adb pull for all the partitions already, and the data partition file was only 6KB.
One thing I clearly forgot about - I can use File Manager to confirm if the data is there. I've checked there, and all of the files and folders on my device still appear to be shown as normal - if I check /sdcard/DCIM/Camera, I can see my photos, if I check /sdcard/Downloads, I can see stuff I've downloaded, etc. However, when I go to the TWRP menu and choose Backup, the Data partition is 0MB. Tapping Refresh Sizes doesn't change anything.
So if the userdata is stored on the Data partition and I can confirm the files are still on the phone, how is the Data partition showing as 0MB in the Backup screen? What on earth is going on?
The data partition that you backed up isn't userdata, it's the installed apps partition. There is a separate partition for userdata. When installing a new rom, wiping /data in twrp is always a good idea but it won't touch your userdata.
You should be able to mount your phone to your PC while in twrp and copy all your data over, then proceed w a full factory flash to try and correct your problem. When you mount it, it will show up on PC just like a thumb drive.
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
seabro01 said:
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
Click to expand...
Click to collapse
uhh no I did not see that in the tutorial.
I tried: ./fastboot flashing unlock_critical
and looks like it freezes after that command...
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
yenkoPR said:
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
Click to expand...
Click to collapse
no not rooted
now im trying to flash back to stock, but when I run flash-all.sh error keeps popping up:
remote: Error flashing partition.
FAILED (remote: Error flashing partition.)
finished. total time: 2.025s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.735s]
writing 'boot_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.782s
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (512 KB)...
OKAY [ 0.103s]
writing 'cmnlib_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.169s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (512 KB)...
OKAY [ 0.101s]
writing 'cmnlib_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.188s
...
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
What do you mean by can't boot up? Do you see boot animation and have you tried to go back to fast boot or recovery?
Sent from my ONEPLUS 3T using Tapatalk
Try different USB ports and cables. When 8.1 came out I had to swap my cable and change the port I was using on my desktop, for some reason the cable I had been using and the port I had been using since I got the phone was no longer adequate. There were a number of other people having the same issue. Some commands would look to complete properly, but following up with the same command (something un-damaging like fastboot --set-active=a | fastboot --set-active=b) would either error again or show that the 'completed' command hadn't actually done anything. I switched cables/ports around (ended up with an Antek USB-A to USB-C cable in a USB3.1 port) and everything worked properly.
If you're trying to flash a stock build image from Essential, you will probably need critical unlocked because those images do contain a bootloader that gets flashed, and that is secured behind critical.
ytlei said:
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
Click to expand...
Click to collapse
What cable are you using?
Do not use the cable that came with the phone!!!!!
We are screwed mate, I am on the same boat with you. Essential took no responsibility and offered a 200$ replacement device. The phone doesn't power on anymore and no light indicators are working, so hard bricked.
I had a Asoip screw up(did not disable password) and was only able to get fastboot. Had to see what slot was active and flashed to that slot that was active boot.img,twrp,Asoip and was back up and running. My bootloader was unlocked. I read through all the posts and peoples screw ups and was able to get it up and running again in a day. I never posted as I wanted to learn it on my own. Good luck.........
ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
What cable did you use while connecting to your computer?
And what is the status now? Are you able to turn it on at all by volume and power key combination?
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
ytlei said:
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
Click to expand...
Click to collapse
and pressing the volume down key + power key at the same time doesn't work?.. what happens when you plug your phone into the charger? does it vibrate?
ive had fastboot command problems previously myself with this device and found that the usb port can play a pretty large factor. Swapping usb ports and reattempting to run the commands (as others recommended may be useful) make sure you are using latest version of adb/fastboot and have up to date drivers installed for the phone.
Look at the rooting tutorial there is information in there about swapping active slots (the essential has both a and b paritions) if you set the other slot as the active slot you may be able to regain some communication within fastboot (i would suggest you verify with fastboot devices prior to attempting to flash to partitions).
Additionally you should be able to still recover back to stock without custom recovery using the default recovery partition. I would think that if you are able to access the bootloader you should be able to access the default essential recovery partition. If you can access the standard recovery you should be able to factory reset the phone and sideload a new rom (id suggest the default factory image from essential until you can get back to square one)
I'm in the same boat. Tried to flash twrp after upgrading to 8.1 and got the same Error flashing partition, and now I'm stuck on the bootloader.
I've found that if I lock/unlock and lock/unlock critical it will let me flash the stock 8.1 boot and every other partition except for system and vendor, but gives a flash write error for those. I'm still unable to get past the bootloader.
Essential basically said I'm SOL. $200 out of warranty replacement assuming I live in the US, which I don't.
Mine was doing this too, but it was only a few days old so I returned it. I'm pretty sure it's defective flash memory.
My phone was doing this exact thing. Botched factory installs rendered my phone hardbricked.
Tried a thousand+ things to get it to turn on to no avail. LUCKILY I bought it second hand and have no warranty D:
I want to cry
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>adb reboot bootloader
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.017s]
writing 'vbmeta'...
OKAY [ 0.036s]
finished. total time: 0.073s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot erase system
erasing 'system'...
OKAY [ 37.155s]
finished. total time: 37.169s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash system system.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 13.484s]
writing 'system' 1/4...
OKAY [ 4.426s]
sending sparse 'system' 2/4 (456612 KB)...
OKAY [ 14.049s]
writing 'system' 2/4...
OKAY [ 3.476s]
sending sparse 'system' 3/4 (460796 KB)...
OKAY [ 13.959s]
writing 'system' 3/4...
OKAY [ 3.582s]
sending sparse 'system' 4/4 (173628 KB)...
OKAY [ 5.140s]
writing 'system' 4/4...
OKAY [ 1.580s]
finished. total time: 59.786s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.711s]
finished. total time: 1.719s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot reboot
rebooting...
finished. total time: 0.043s
Click to expand...
Click to collapse
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Traijan said:
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Click to expand...
Click to collapse
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Supplement...the Part with the vbmeta is not necessary as far as i know.
solong
speedson
speedson said:
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Click to expand...
Click to collapse
Hey, I used the default rom installed on my huawei p10 lite.
I did a complete clean install yet.
Before that I used twrp to install it (because I thought it worked with .img) and after that I startet from a clean install of the default rom again and did the linked tutorial.
I'm not root on this device, I just have a unlocked bootloader.
I also didn't encrypted my internal storage. Do I have to do it?
What you mean with not reboot to bootloader? I did the commands in the link on fastboot (holding vol - and connect to pc)
Do you have an idea what I can do? I really would like to test android 12.
A good place to start when figuring out why no rom install's in my system-as-root...
Back to stock it is...