About phone: Huawei P9 lite VNS-L21C432B161 (central Europe)
First modifications
A long time ago i unlocked bootloader and successfully rooted the phone. I turned off OEM unlock option in settings after rooting, because someone said i should do so for security. Then came EMUI 5 OTA. It somehow updated itself without me agreeing. Android nougat detected, that the bootloader was unlocked and so it assumed that OEM unlock option was also ENABLED when it really wasn't, making me unable to re-enable the option.
So i used the https://forum.xda-developers.com/huawei-p9lite/how-to/tutorial-rollback-n-to-mm-c432-devices-t3563955432-devices-t3563955" <-- official rollback package and installed stock ROM through dload.
Here is the part where i messed up horribly
Now i wanted to update to android 7 again, but updater wasn't giving it to me and i was unable to flash it through TWRP. I installed the rollback package again through download mode as it said it allows any ROM to be installed, hoping i could then install android 7 through Download mode, which would in turn allowed me to install newer version of TWRP to then install a nougat based custom ROM.
Current situation
Now i am stuck at the 'Your device has been unlocked and can't be trusted. TWRP 3.0.1 should be installed but it never boots. Can't access bootloader, phone doesn't seem to be detecting the Power+Volume down combination. Recovery gets stuck at the shorter warning screen during boot, erecovery gets stuck as well. This has been like this even before i tried this, no idea what caused it. I can't even access download mode, which gets stuck at the shorter warning screen as well.
What i hope to achieve now
At best: To make it work again.
At worst: To at least be able to turn it off somehow so the text doesn't get burnt into the screen in case i ever manage to fix it.
Thanks in advance
Related
Hello,
I own a Huawei P8 L09, bootloader unlocked, rooted and with TWRP recovery.
I tried this morning to flash a new rom using TWRP recovery.
Problem is that I do believe I wiped to many partitions and I ended up with a bootloop.
I could at first access 3 times the emui erecovery (btw, Wifi recovery failed) but not anymore (is it related to the battery level ? I don't know how much I still have)
Following a lot of threads here and on some other forums (I've been searching now for approx. 7 hours...) :
I downloaded a update stock ROM (B170 something), I extracted Boot, System, Recovery and Cust
I entered bootloader mode (it's the only mode I can go to; recovery No, Download mode neither)
and on my computer I typed in the cmd "fastboot flash recovery recovery.img" same with system, cust and boot.
All of them said "Okay" but the bootloop is still there and I can't acess any other mode or shut the device off.
Also, my bootloader indicate that i'm "unlocked" but when I try to do something as :
"fastboot erase cache" it says "remote: not allowed" or something like that.
I tried the SD card flash method but I can't even acess the 3-button mode (doesn't work - bootloop again).
Finally, I've got 2 questions :
1) Is there a solution ? Is there/was there anybody in the same situation ?
2) Does the battery level influence wether I may or not enter any mode ? like b.e. under 30% I can't access recovery or something like that ?
Thanks in advance for your help and sorry for my bad english.
Greetings from Belgium !
Jules
Hi!
I have the same situation as you do, All i know is that you can access the eRecovery only if you're plugged in.
But it's completely useless. Have you found any solutions yet?
Edit:
i struggled and i'm still struggling but i figured out that I need the recovery and boot img of the version i was on previously. In my case that is B350.
The main mirror is down but i managed to find another one: https://mega.nz/#!NAcgQY7Y!I4eRfkaq62J31csv_wZ8_nTzmUbWPX71JUicDysjus8
after flashing them i was able to partially flash (using vol+-&pwr) B170 (it only went up to 90% with my USB attached, fails without USB)
At my surprise it booted B170 even if it didn't complete, however right now it keeps rebooting every minute. I'll update if i manage to fix this
I have the same problem as you both. To flash boot.img and other files by fastboot we need to unlock bootloader. To unlock bootloader we need to have Imei, Product Id and SN, but I can't read it because phone won't turn on.
Anyone know how to get this info?
you can read these info from the packaging box!
I managed to fix my issues (i believe) by continuously flashing and flashing versions. I never really managed to fully OTA update to 100% due to some "CUST error" but from B350 i managed to "update" to B170, then to B200, then to B321a.
Now i just installed TWRP and rooted it and on the process of installing xposed (if possible).
I wasted a good 6-7 hours on everything already
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
TukAliveFra said:
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
Click to expand...
Click to collapse
you gonna pay for the repair..
Hi there! I have this question which I'd love to have answered because I've been on this issue for around 2 days straight.
Long story short:
Tried to flash custom recovery using fastboot, didn't work because bootloader locked
Kept on trying the unlocker apps, none of them even installed fully (THIS WAS WHEN I WAS STILL ON LOLLIPOP)
Somehow, at some point, I just randomly rebooted and BOOM THERE WAS TWRP (Sorry, I don't remember how exactly I managed that. As far as I remember, I was only using fastboot and nothing else)
Flashed CM 14.1 unofficial, device gave an error message regarding boot.img (something like "could not load boot.img"
Used stock ROM to flash OTA Android 6.1
Now the Asus unlocker app downloads but on reboot it says "error: unlock fail !!!"
Obviously, fastboot is unable to flash a recovery right now. I tried ignoring the error message and rebooting to recovery to stop the device from loading the stock recovery again but the device still loads the stock recovery.
I'm really tired
P.S: NO, there is no Enable OEM option in my Developer Options menu and YES, I have all the drivers necessary.
Did you get anywhere with this? I have a similar problem except that I couldn't flash Android 6.1 because the vendor had flashed WW 5.0.2 on a CN phone without also updating the CN recovery to WW. So the update failed its consistency check.
I've got TWRP on there now, but can't unlock the bootloader in 5.0.2 - I think this is why TWRP can't flash anything. It can't see the update files, won't switch to external SD, etc. .
I also found and tried flashing a WW recovery but that didn't work either. I'm wondering now if I got the 615 software by mistake.
so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
FISBANREGNER said:
so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
Click to expand...
Click to collapse
any help with this would be great im looking for the latest firmware for the sm-g550t1 the rev00 doesnt work because of version mismatch
FISBANREGNER said:
so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
Click to expand...
Click to collapse
ok so i was having an issue where i bricked my metropcs sm-g550t1 (galaxy on5) when i downloaded the stock rom for my phone i would get a sw mismatch D2 B1 error. the reason for this error is the update that came out in the beginning of 2017 changed the firmware version from PF1 to PL1. so if you are also having this problem when trying to unbrick your phone use the firmware for phone SM-G550T2 then use your twrp backup to unbrick but remember to turn the oem unlock on or you will brick your phone again
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Kj1594 said:
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Click to expand...
Click to collapse
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Himanshu.Shukla said:
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Click to expand...
Click to collapse
I did try to install codeworkx twrp recovery, for the Oreo build but it was giving me a hard brick, ie. A black screen and a blue LED when trying to boot to recovery. But as I said, using Unbrick tool v4.0.8 I was able to restore to Oxygen Os 5.1.7 and then everything worked fine.
I am just unsure why it didn't work with Oxygen Os 4.5.8
I mean, with a locked bootloader and a freshly installed OS, you should be able to get OTA updates, right? But the system update was failing. So maybe there was something wrong with the partitions? I don't know. The bootloader in the older Unbrick tool was different than stock. Maybe that was a fault, well, I'll never know. But all I'm saying is, newer Unbrick Tool worked wonders for me.
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
just download the Full OTA update in the thread section.
must downgrade first ur recovery to nougat then install update via recovery.
You can use TA-1021.
If you want Nougat Ver. then use Nokia OST.
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
my Nokia 6 phone is also bricked. Please share if you find a solution.
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
First flash stock recovery, then boot into stock recovery and flash latest OTA
Link for latest OTA got from Telegram (TA-1025 ) : https://android.googleapis.com/packages/ota-api/package/5d91fc596557fecf1ba49b9321b446c64e3acd06.zip
Note :Your bootloader will be remained unlocked. don't worry
Sharashchandra said:
First flash stock recovery, then boot into stock recovery and flash latest OTA
Link for latest OTA got from Telegram (TA-1025 ) : https://android.googleapis.com/packages/ota-api/package/5d91fc596557fecf1ba49b9321b446c64e3acd06.zip
Note :Your bootloader will be remained unlocked. don't worry
Click to expand...
Click to collapse
I'm stuck in EDL mode now, any fixes or tips on how to flash/patch? QFIL is saying 'Failed to switch to EDL Mode'
Dantheman221 said:
I'm stuck in EDL mode now, any fixes or tips on how to flash/patch? QFIL is saying 'Failed to switch to EDL Mode'
Click to expand...
Click to collapse
Is phone is totally dead?? what you are getting when you insert charger? how pc is detecting your device (go to device manager)?
Sharashchandra said:
Is phone is totally dead?? what you are getting when you insert charger? how pc is detecting your device (go to device manager)?
Click to expand...
Click to collapse
It shows up as a QualComm COMM port device. But before you get your hopes up, every time I have tried to flash it, it says "Failed to switch to EDL mode" :-/.