[HELP] Bricked phone while trying to install custom rom - Essential Phone Questions & Answers

[HELP] Bricked phone while trying to install custom rom - Essential Phone Questions & Answers

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

Related

Can't Flash TWRP

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

writing 'vender'... FAILED (remote: Permission denied!)

I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.

Hey, no problem bro! It's called vendor, not vender, and the command is: fastboot flash vendor etc. This should solve your problem (Sorry for my english)

NHagney said:
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Click to expand...
Click to collapse
I'm a Linux guy so you may wish to take this with a grain of salt. I have a vague memory of the same error and it was a case of a misspelled and/or miscapitalized command. I am assuming 2 things -
1) everything has worked up to this point
2)the code presented is exactly what you typed on your computer
Your error may simply be that your misspelled vendor after "fastboot flash"

Thats what i get for being hung over. I'm over here trying to run this as admin all kinds of nonsense. Wondering why this went so smooth last night now running into this. I still don't have a working device. After restarting the device I don't get the OS only the initial google screen. Edit: nevermind. It just posted. TY guys. On to Android 'N' maybe Nuttybar?

Unbricking Progress - Stuck in ADB/ADB composite/Fastboot/QH-USB

I will update my unbricking process with every attempt
Attempt 1:
Tried to flash grossoshop fastboot rom 17s by manually erasing boot, system, userdata, cache and recovery. Phone doesn't wake up with any. Still responds to ADB and Fastboot commands with no errors
If browsed through adb, system partition only shows two directories lib and lib64
Attempt 2:
Trying to manually flash mbn files present in the official 20s rom of x720. QPST is not recognizing my phone. I have to somehow put the phone into 9008 mode rather than 9025 mode (which is diagnostic)
There are no QPST compatible files around for Le Pro 3. Guess I finally put my 240$ to the trashcan....
Attempt 3:
I tried to flash the mbn, elf and bin files to their corresponding partitions via fastboot, everything went okay with the flashing. Then I flashed the boot.img, stock recovery and splash..... Went okay.
Rebooted my phone into recovery and its still dead. I can only see ADB interface in device manager and device is recognized correctly in adb.
If I power off my phone by pressing both volume buttons + power and then just insert USB cable, I end up in QDLoader 9008 mode. There is still hope if LeEco ever releases service rom for Le Pro 3 just like it released earlier for Le1, Le2, Le Max 2 etc. Leeco.re has all the firmwares except Le Pro 3.
Flagship my ass, LeEco ripped us off with its amazing chinese U-turn yet again. There is no hope in unbricking the phone unless I get QFill factory service rom meant to be compatible with QPST flasher.
Attempt 4:
Finally found the unbrick service rom which is to be flashed with FlashOne program but turns out the file is incomplete.
Ref Thread: http://www.leeco.re/topic/1906-helpx720-bricked/#comment-33155
I charged my x720 last night (just 10 hrs ago), drove to office with battery last known at 87% just 30 minutes ago.
I took it out of my pocket, sent a couple of text msgs, put it on my office table. Now all of a sudden phone is black, no display, no sign of life except short two vibrations everytime I try to turn it on. I have no idea what has just happened. Still got 6 hrs to stay at office then to home where I might try to charge/put phone to PC and check....
I literally have no idea what just happened.
I'm on CM13 by Team Superluminal and never had any problems like this in the past....
I'll update what was the problem once I get home and thoroughly check my phone :/
Click to expand...
Click to collapse

leave power button and vol down pressed for some time........ it's not the normal waiting time....... just leave it pressed until you get into download mode......
it happened to me with a past custom rom.......... your boot-loader may be locked again......
TURBO

TURBO2012 said:
leave power button and vol down pressed for some time........ it's not the normal waiting time....... just leave it pressed until you get into download mode......
it happened to me with a past custom rom.......... your boot-loader may be locked again......
TURBO
Click to expand...
Click to collapse
Phone vibrates very momentarily after about 10 seconds of holding power button and then vibrates like that every 10 seconds if I keep power button pressed.
I connected it to my Computer and it shows up as QUSB_BULK in device manager. Looks like my device is bricked until LeEco releases QFIL files for Le Pro3. I already have installed Qualcomm QDLoader 9008 drivers.
I am leaving this phone on charger overnight and will check if Battery really was depleted this fast in-case phone lives up. Otherwise its a sad story until LeEco releases QFIL files.

Update # 2
I managed to connect my phone stable with Computer without any stupid black rebooting.
I'm able to see my device in ADB under recovery, and ADB under composite interface and even I can issue ADB Reboot Bootloader command to take it to fastboot.
If I just flash TWRP, it flashes successfully but stays black. Even if I boot recovery image, it reboots into composite interface instead.
Next stop: Grossoshop fastboot rom. Im downloading it right now from https://mega.nz/#!VEM1QIYL!HwT9hk7-GA6KZBTRMv0IQ9kleYaG-el63UF21S6P0us
I REALLY REALLY REALLY HOPE IT WORKS. Phone died on me while on nearly full battery so if it stayed on during whole day it still would have half the juice left to be flashed in fastboot. I don't know if the phone is recharging on adapter or not.
Code:
D:\ADB>adb devices
List of devices attached
50a2127e recovery
D:\ADB>adb reboot bootloader
D:\ADB>adb devices
List of devices attached
D:\ADB>fastboot devices
50a2127e fastboot
D:\ADB>fastboot flash recovery lepro3_twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (47052 KB)...
OKAY [ 1.313s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 1.641s
D:\ADB>fastboot boot lepro3_twrp.img
downloading 'boot.img'...
OKAY [ 1.331s]
booting...
OKAY [ 0.344s]
finished. total time: 1.675s
D:\ADB>adb reboot -p
D:\ADB>adb devices
List of devices attached
50a2127e device
D:\ADB>adb reboot recovery
D:\ADB>adb reboot bootloader
D:\ADB>fastboot devices
50a2127e fastboot
D:\ADB>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.078s]
finished. total time: 0.078s
D:\ADB>

Update # 3 Phone is still in coma after flashing Grossoshop 17s rom via fastboot
Incomplete log since the batch file window can't be maximized or scrolled
Code:
*****
**********************************************************************
***** FLASH SYSTEM *****
**********************************************************************
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.000s]
sending sparse 'system' (487311 KB)...
OKAY [ 14.516s]
writing 'system'...
OKAY [ 9.544s]
sending sparse 'system' (518775 KB)...
OKAY [ 14.934s]
writing 'system'...
OKAY [ 7.324s]
sending sparse 'system' (524287 KB)...
OKAY [ 15.657s]
writing 'system'...
OKAY [ 5.031s]
sending sparse 'system' (524284 KB)...
OKAY [ 15.755s]
writing 'system'...
OKAY [ 4.486s]
sending sparse 'system' (500922 KB)...
OKAY [ 15.109s]
writing 'system'...
OKAY [ 7.818s]
sending sparse 'system' (484095 KB)...
OKAY [ 14.501s]
writing 'system'...
OKAY [ 89.072s]
finished. total time: 213.780s
**********************************************************************
***** FLASH KERNEL *****
**********************************************************************
target reported max download size of 536870912 bytes
sending 'boot' (35764 KB)...
OKAY [ 1.016s]
writing 'boot'...
OKAY [ 0.234s]
finished. total time: 1.266s
**********************************************************************
***** FLASH TWRP *****
**********************************************************************
target reported max download size of 536870912 bytes
sending 'recovery' (48272 KB)...
OKAY [ 1.344s]
writing 'recovery'...
OKAY [ 0.344s]
finished. total time: 1.687s
**********************************************************************
***** REBOOT RECOVERY *****
**********************************************************************
-- If process was OKAY.....
-- Press any Key to start Recovery then.....
1. Wipe DATA, CACHE and DALVIK CACHE for new rom installation.....
2. Wipe CACHE and DALVIK CACHE if you are updating BB72 rom.....
3. Restart at the end of the process.....
-- First boot takes long.....
D:\ADB\GSLEPRO3\18S>

Update # 4:
Phone is still dead, only recognizeable through ADB, Fastboot, QDLoader 9008. Screen never comes alive, only the vibrator gives the sign of life if not for the device Manager.
I managed to flash the mbn, elf and bin files to corresponding parittions with no errors, then I flashed official boot.img, splash.img and stock recovery but upon reboot, phone is still dead.

Dang it man. I in the same boat. I can get to the fastboot and that is it. If i try to boot recovery it flashes the recovery screen and then goes back... im so dumb for even trying to unlock and flash a rom on this thing...

Same here - qdload 9008 mode and no qfil compatible rom pack from LeEco. Relying blindly on them releasing the files sometime in the future seems like a lost cause to me.

coolmaster121 said:
Dang it man. I in the same boat. I can get to the fastboot and that is it. If i try to boot recovery it flashes the recovery screen and then goes back... im so dumb for even trying to unlock and flash a rom on this thing...
Click to expand...
Click to collapse
I am out and have OmniRom installed atm. Thank your XDA!
In case this helps you guys fix it:
https://forum.xda-developers.com/showpost.php?p=71704244&postcount=595

coolmaster121 said:
I am out and have OmniRom installed atm. Thank your XDA!
In case this helps you guys fix it:
https://forum.xda-developers.com/showpost.php?p=71704244&postcount=595
Click to expand...
Click to collapse
Your case was different. At least ur phone showed signs of life by momentarily showing u the recovery screen. My phone doesn't live up at all not even. LED notification light or screen. Just fastboot or ADB or QDLoader.....

Had a similar effect yet from different reason. I dropped my phone in salty water (I thought it would survive as it did in fresh water for a minute LoL) and it won't turn off but just in a boot loop to Recovery.
Then the screen died, won't turn on at all, phone vibrates once or twice every restart infinitely. The battery drained out and I put the phone in a bucket of rice for a day and voila it turned on again. I was able to relock the bootloader and sent it back for repair (with fingers crossed hoping they won't dismantle the phone and find water traces inside =D). They replaced it with new one and so I am happy camper again. =D

Joms_US said:
Had a similar effect yet from different reason. I dropped my phone in salty water (I thought it would survive as it did in fresh water for a minute LoL) and it won't turn off but just in a boot loop to Recovery.
Then the screen died, won't turn on at all, phone vibrates once or twice every restart infinitely. The battery drained out and I put the phone in a bucket of rice for a day and voila it turned on again. I was able to relock the bootloader and sent it back for repair (with fingers crossed hoping they won't dismantle the phone and find water traces inside =D). They replaced it with new one and so I am happy camper again. =D
Click to expand...
Click to collapse
I just happened to buy the phone and get it shipped to wrong country where Leeco support doesn't exist neigther the country supports such repair correspondance. Customs here will charge me around 150$ when I will recieve my phone after repair, moreover my Leeco warranty isnt covered because I didnt buy from their official store (rather a chinese store through a friend and get it shipped to me). So Im left out in the dark waiting for the on-shelf recovery measures.

Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things

benjmiester said:
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
Click to expand...
Click to collapse
Do you have twrp installed? And an OTG?

benjmiester said:
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
Click to expand...
Click to collapse
You can try "adb sideload" in twrp usually it bypasses "unauthorized" status and flashes away directly.

ivangotoy said:
You can try "adb sideload" in twrp usually it bypasses "unauthorized" status and flashes away directly.
Click to expand...
Click to collapse
That actually did the trick, thanks! I'd be really screwed without TWRP booting.

We, in the qh-usb boat, are rly screwed right now

benjmiester said:
That actually did the trick, thanks! I'd be really screwed without TWRP booting.
Click to expand...
Click to collapse
I am screwed. Can yu explain how this adb sideload worked?

zman123 said:
I am screwed. Can yu explain how this adb sideload worked?
Click to expand...
Click to collapse
Sorry I didn't see this earlier. I was lucky in that my phone would still work in fastboot mode with my computer even though adb push would not so I couldn't push files to flash.
If you can get to twrp, or fastboot (volume DOWN + power, hold until it boots to fastboot screen) then you can open fastboot command window on PC, type fastboot devices and make sure it shows a device is attached and recognized. If so, flash twrp with command fastboot flash boot twrp.zip (or whatever you name it). Once in twrp, you can go to sideload option, have to toggle it on in twrp and it will say ready (waiting to accept zip over adb). Then have rom zip and gapps zip in adb/fastboot folder on pc.
Use command adb sideload rom.zip then same for gapps.zip. It will show progress on the phone if working.

benjmiester said:
Sorry I didn't see this earlier. I was lucky in that my phone would still work in fastboot mode with my computer even though adb push would not so I couldn't push files to flash.
If you can get to twrp, or fastboot (volume DOWN + power, hold until it boots to fastboot screen) then you can open fastboot command window on PC, type fastboot devices and make sure it shows a device is attached and recognized. If so, flash twrp with command fastboot flash boot twrp.zip (or whatever you name it). Once in twrp, you can go to sideload option, have to toggle it on in twrp and it will say ready (waiting to accept zip over adb). Then have rom zip and gapps zip in adb/fastboot folder on pc.
Use command adb sideload rom.zip then same for gapps.zip. It will show progress on the phone if working.
Click to expand...
Click to collapse
Thank you! I was finally able to get sideload to work. I was using Darkobas recovery and that caused issues. Flashing normal TWRP worked. I was able to get back to stock via recovery so know I am trying to fix the prolem that started this mess... Google play store wont work on cellular..... most annoying problem in the world!

Bootloop PLEASE HELP!!!!!!!!!!!!!!!!!!!!!!

Hey everyone, I've spent the last 5 hours trying to fix my phone and I'm not getting anywhere.
It gets to the second part of the starting up process, where it makes the sound as well and it just keeps glowing over and over.
I'm able to access the recovery mode, I've already tried clearing the partition cache & I've also done a factory reset.
I've tried flashing recovery.img & boot.img from B170 which I read somewhere, I've done that successfully but it doesn't seem to do anything.
I had this before and I fixed it by flashing system.img but for some reason it keeps giving me an error when I try to do it now: "error: cannot load 'system.img'"
Also flashing the bootloader doesn't seem to work:
"C:\Users\Leron\Desktop>fastboot flash bootloader twrp-2.8.7.1-p8.img
target reported max download size of 471859200 bytes
sending 'bootloader' (25880 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
FAILED (remote: partition does not exist)"
I've read something about buying a card adapter but as I said, I have no money...
I tried to root my phone, bad f***ing move because for some reason it's impossible on the Huawei P8, excuse my bad language but im extremely frustrated i should have never done this. any help is welcome
thanks

usleronus said:
Also flashing the bootloader doesn't seem to work:
"C:\Users\Leron\Desktop>fastboot flash bootloader twrp-2.8.7.1-p8.img
target reported max download size of 471859200 bytes
sending 'bootloader' (25880 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
FAILED (remote: partition does not exist)"
Click to expand...
Click to collapse
Big mistake, no wonder it won't flash.
TWRP is NOT a bootloader but is a recovery, so therefore the correct fastboot command is:-
fastboot flash recovery twrp.img
The P8 is quite easily rooted see here:-
https://forum.xda-developers.com/showpost.php?p=74206273&postcount=305
and here:-
https://forum.xda-developers.com/huawei-p8/how-to/rooting-huawei-p8-marshmallow-emui4-0-1-t3431249

Oh my bad haha.
I fixed it using SRKToolHuawei, which is very useful. I'm very new to this so that's why I screwed up so bad lol
Thanks for the help though. I'll check out the links you sent me and try to root again. Hopefully this time I won't break my phone lmao.

stuck at lockscreen, bootloader and frp locked

Hi, I just changed the lcd screen on an old p8lite my girlfriend wasn't using for a year or so. Fact is she can't remember the pin.
Pressing power+vol down I can enter fastboot and rescue mode, but phone was never unlocked so i don't know what commands I can really execute from here, if I press vol up and get into rescue mode I am given the option to download a new recovery, but when downloading it says 'getting package info failed'. In rescue mode I don't have other choices besides rebooting and shutdown.
What can I do to unlock the phone?Can somebody help me?????

UPDATE: on one of many reboots instead of showing me just the options to reboot, shutdown and download recovery, Emui recovery showed the possibility of making a wipe, so i went on wiping, downgrading, rooting, unlocking the bootloader, but i couldn't install twrp - every time I try these are the results:
C:\adb>fastboot flash recovery_ramdisk TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (10816 KB)...
OKAY [ 0.277s]
writing 'recovery_ramdisk'...
FAILED (remote: partition does not exist)
finished. total time: 0.303s
C:\adb>fastboot flash recovery TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img
target reported max download size of 471859200 bytes
sending 'recovery' (10816 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.183s]
finished. total time: 0.484s
But TWRP doesn't get installed, anyway....
I would also like to try to run a datarecovery software to recover photos and stuff my girlfriend left in, but without having the p8 lite mass storage in explorer the results I get with android data recovery softwares are pretty useless, is there a way to make show the storage in explorer? If anyone would be willing to help me with some hints, I'd be very grateful. Thanks

Database Users

welcome