Day 3 after purchasing, I managed to twrp, root and installed RR custom ROM. Went well. Next day, I wanted to try AICP ROM, I flashed it, but it was shutting down often so I moved to LOS 14. After that I saw PARANOID on the list by team Open Kirin, never did use it before so I jumped on it. I got my hands on PA- browser for the 1st time however I missed the flexibility of RR and decided to head back to RR. And that's where I met Mr.Bootloop. I took turns on shifting to LOS, AICP, RR, PA but
nothing worked. so I finally flashed Carbon ( which looped too).
* tried to went back to stock "update.zip +2 more zips" : didn't worked
* wipe data+ cache+vendor +cust + system* reflashed twrp recovery and didn't worked.
I asked few dev, but they seem busy for now. I feel stupid and really need some help.
I know it make no sense flashing n testing all.
If I come could get system, boot, recovery IMG of Duk-L09 (Asia), I think I could flash em with twrp adb sideload.. maybe?
Help this poor fellow please.
I've been using my honor 8 pro 2 months + , 1 month stock and 1 month with RR. i like the RR speed but it just drain too much battery when gaming so i decide to go back to stock b flashing update.app. Everything seems ok and manage to setup the phone to stock. But after i restart the phone here where the problem come, it stuck at error mode and i'm unable to go to fastboot mode nor recovery mode, it just stuck at the error mode screen even when power it off, it will auto power on again. Tried draining the battery and connect the phone to pc while holding vol - method but no success. End up i send my phone to the service centre. They have confirm my phone mobo died and they will replace it with a new 1. Hope your's not the mobo problem.
If you still able to go to fastboot mode with bootloader unlock and frp unlock, i think you're still able to flash your phone back to stock.
Can you boot to erecovery?
Sent from my Honor 8 Pro using XDA Labs
yes, I can boot on erecovery & twrp. flashing any ROM ends me up in bootloop. tried "dload" method with update.zip.
watched a youtuber's method of adb sideload. but still not booting up with the ROMs that worked before.
back on my old phone still looking for better XDA instruction
wyldemdd said:
I've been using my honor 8 pro 2 months + , 1 month stock and 1 month with RR.....
If you still able to go to fastboot mode with bootloader unlock and frp unlock, i think you're still able to flash your phone back to stock.
Click to expand...
Click to collapse
I didn't backed up, I was thinking I would be going back there. stupid me.
xdasith said:
yes, I can boot on erecovery & twrp. flashing any ROM ends me up in bootloop. tried "dload" method with update.zip.
watched a youtuber's method of adb sideload. but still not booting up with the ROMs that worked before.
back on my old phone still looking for better XDA instruction
Click to expand...
Click to collapse
Did you try extracting the update.zip and manually flash boot.img, vendor.img, system.img ? i remember i too have a bootloop when flashing RR the 1st time just because i wipe the vendor in twrp. flashing the vendor.img or zip fix the problem.
wyldemdd said:
Did you try extracting the update.zip and manually flash boot.img, vendor.img, system.img ? i remember i too have a bootloop when flashing RR the 1st time just because i wipe the vendor in twrp. flashing the vendor.img or zip fix the problem.
Click to expand...
Click to collapse
I have extracted "update.app" n tried "dload" folder update method only yet. I try to extract as you said from update.app.
New to huwaii device. to extract boot.IMG/system.img/vendor.IMG from update.app I hope there is a method for that or an app perhaps?
xdasith said:
yes, I can boot on erecovery & twrp. flashing any ROM ends me up in bootloop. tried "dload" method with update.zip.
watched a youtuber's method of adb sideload. but still not booting up with the ROMs that worked before.
back on my old phone still looking for better XDA instruction
Click to expand...
Click to collapse
xdasith said:
I have extracted "update.app" n tried "dload" folder update method only yet. I try to extract as you said from update.app.
New to huwaii device. to extract boot.IMG/system.img/vendor.IMG from update.app I hope there is a method for that or an app perhaps?
Click to expand...
Click to collapse
After extract the update.app from the update.zip, use huawei update extractor to extract system.img , boot.img , vendor.img from the update.app
step how to do that can be found here : https://forum.xda-developers.com/showthread.php?t=2315547
try to flash the vendor.img 1st, boot to twrp wipe data and re-flash your desire custom ROM. reboot to system and see does that fix the problem.
wyldemdd said:
After extract the update.app from the update.zip, use huawei update extractor to extract system.img , boot.img , vendor.img from the update.app
step how to do that can be found here : https://forum.xda-developers.com/showthread.php?t=2315547
try to flash the vendor.img 1st, boot to twrp wipe data and re-flash your desire custom ROM. reboot to system and see does that fix the problem.
Click to expand...
Click to collapse
vendor flashing failed. other than that system recovery boot all were executed fine.
if booted into the system, it say loads an empty screen.
if flashed custom : loops.
xdasith said:
vendor flashing failed. other than that system recovery boot all were executed fine.
if booted into the system, it say loads an empty screen.
if flashed custom : loops.
Click to expand...
Click to collapse
i remember in RROS thread you can download the flashable vendor..zip. try download it and flash thru TWRP and flash RROS.
wyldemdd said:
i remember in RROS thread you can download the flashable vendor..zip. try download it and flash thru TWRP and flash RROS.
Click to expand...
Click to collapse
yeah. I flashed vendor.zip from RR thread. after the failed attempt from flashing Vendor.IMG from update.app( after extraction).
still no good.
wyldemdd said:
i remember in RROS thread you can download the flashable vendor..zip. try download it and flash thru TWRP and flash RROS.
Click to expand...
Click to collapse
I tried that vendor.zip with RROS before. it worked really fine. but since loop with trying to go back after flashing 1 custom after another. I can't go back with any of those .
I replaced vendor zip first with RR too it didn't not seem to work.
I tried with two update.zip (L09 asia) I got from the net. didn't worked yet.
if any of you have gone back to stock n work. please guide me to it.
if I can go back I can go to LOS,again.
the link they shared in a YouTube "Dhananjay way" do stuck at 42%.
"dload" method by DroidTh might do good. but link expired.
The stock link by Morph= has No C6. section. the other update link shared here in XDA tagged " Indian link here" is the one which is giving me vendor.IMG failure.
In order to go back to stock, what I did is I flash the 2 stock recovery which is recovery.img and recovery2.img from extracted update.app. then flash boot.img, system.img, vendor.img. please don't lock bootloader while you don't have a working OS running or else you will stuck with a brick phone.
xdasith said:
I tried that vendor.zip with RROS before. it worked really fine. but since loop with trying to go back after flashing 1 custom after another. I can't go back with any of those .
I replaced vendor zip first with RR too it didn't not seem to work.
I tried with two update.zip (L09 asia) I got from the net. didn't worked yet.
if any of you have gone back to stock n work. please guide me to it.
if I can go back I can go to LOS,again.
the link they shared in a YouTube "Dhananjay way" do stuck at 42%.
"dload" method by DroidTh might do good. but link expired.
The stock link by Morph= has No C6. section. the other update link shared here in XDA tagged " Indian link here" is the one which is giving me vendor.IMG failure.
Click to expand...
Click to collapse
Why Indecisive flashes ? n ultimately landed on unusable brand new device?
(for me), cons+pros with CuSTomOS
i get with RROS/LOS: .
customized the "recent" to" grid view" . ( multi taskin+ ultra Customization)
though default settings drains power +abit more ram comparatively, but if tweak a lil : can optimized.
yet no dual sim disable hotkeys n WiFi hotkey turns on even if u put in no-scan mode.
AICP : is faster boot+ sided LOS addons + micro Gapps.
light, by default it doesn't consume much ram+CPU.
+ browser has "dev chrome dark with adblock + privacy "
Carbon is good too. neat. fast. but Both Carbon+AICP sacrifice some customizations tweaks
PA (non extended) .
it was last flashed till my me n my device parted. worked. n after that it died.
I'm like em all n new on Huwaii Honor, and stupid.
its been a week already. if unfixable I would like to sale it. but I still wanna know the problem. I will try Anything with Oreo/ LOS 15 available device.
wyldemdd said:
In order to go back to stock, what I did is I flash the 2 stock recovery which is recovery.img and recovery2.img from extracted update.app. then flash boot.img, system.img, vendor.img. please don't lock bootloader while you don't have a working OS running or else you will stuck with a brick phone.
Click to expand...
Click to collapse
I'll try this.. this post was more missing earlier. weird.
I haven't get back my phone from huawei service centre. After i've send for motherboard replacement, they broke my display with a burn mark on the screen, took out my screen protector i just bought few days back before the motherboard failed, with the reason my screen protector is a bit scratch. It's been 11 days now i'm without my Honor 8 pro. I end up buying a new phone which is OP5
wyldemdd said:
I haven't get back my phone from huawei service centre. After i've send for motherboard replacement, they broke my display with a burn mark on the screen, took out my screen protector i just bought few days back before the motherboard failed, with the reason my screen protector is a bit scratch. It's been 11 days now i'm without my Honor 8 pro. I end up buying a new phone which is OP5
Click to expand...
Click to collapse
its normally 14 days time they take..hope you get your device back.
wyldemdd said:
I haven't get back my phone from huawei service centre. After i've send for motherboard replacement, they broke my display with a burn mark on the screen, took out my screen protector i just bought few days back before the motherboard failed, with the reason my screen protector is a bit scratch. It's been 11 days now i'm without my Honor 8 pro. I end up buying a new phone which is OP5
Click to expand...
Click to collapse
hey! my device is back on stock and running after tweaked update.app, as divided in two "dloads" , and 1st "dload" without huwaii built in apps & account verification, and 2nd one with proper modules. now as good as new. No SRK tool, no flashing. just dumped modifed payloads in "SDcard/ dload"..1 after another. Il upload those files. after testing a lil more. its now ( after 700:+mb) updation. un-softbricked ! B150 September 5 patched version.
sorry to hear about ur late delivery. asked em to give a Samsung S8 as interest of borrowing n trolling delivery your kustomised H8pro.
xdasith said:
vendor flashing failed. other than that system recovery boot all were executed fine.
if booted into the system, it say loads an empty screen.
if flashed custom : loops.
Click to expand...
Click to collapse
xdasith said:
hey! my device is back on stock and running after tweaked update.app, as divided in two "dloads" , and 1st "dload" without huwaii built in apps & account verification, and 2nd one with proper modules. now as good as new. No SRK tool, no flashing. just dumped modifed payloads in "SDcard/ dload"..1 after another. Il upload those files. after testing a lil more. its now ( after 700:+mb) updation. un-softbricked ! B150 September 5 patched version.
sorry to hear about ur late delivery. asked em to give a Samsung S8 as interest of borrowing n trolling delivery your kustomised H8pro.
Click to expand...
Click to collapse
Good to hear that bro, yeah partial dload method works too, didn't know why i didn't suggest that at the 1st place . Well i'm demanding huawei to make a 1 to 1 exchange since i can't accept a scratch phone which is not there when i send it in. Hopefully i get my exchange soon
wyldemdd said:
Good to hear that bro, yeah partial dload method works too, didn't know why i didn't suggest that at the 1st place . Well i'm demanding huawei to make a 1 to 1 exchange since i can't accept a scratch phone which is not there when i send it in. Hopefully i get my exchange soon
Click to expand...
Click to collapse
I know why u didn't tell at first. You wanted me to miss my phone. Good job. Haha. Anyways, if they give S8 in exchange,u can get 1H8Pro + 256GB SDcard+headstone+another non-explosive MazeAlphaGama device by trading the S8. Btw S8+ battery last for long 3-hr max if used my way.
What's the status?Did They deliver u yet?
Related
Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?
I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...
If recovery, boot or system partition is modified. There's no harm in re locking otherwise..
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.
Hi everybody,
tried to look for soulutions but without any luck...
I wanted to go back to Android 7 from the 8 (because i had the feeling the 8 is much slower).
I couldn't manage to flash the 7 as long as the phone would lock itself everytime while starting the downgrade so i flashed the N2G47Z 4 core image file on top of the Stock 8.1. I know, i should have used a 4CoreOreo....
Result: i'm an idiot with a phone in bootloop. Cannot go into recovery or anything. i manage to see the Google word and the warning that i should lock the bootloader and go to website g.co/ABH
I will wait until the battery drains and try to switch it on again but than what is the right procedure to follow in order to fix it? (if any)
thank you
Pippolinus said:
Hi everybody,
i flashed the N2G47Z 4 core image file on top of the Stock 8.1. I know, i should have used a 4CoreOreo....[/U]
I will wait until the battery drains and try to switch it on again but than what is the right procedure to follow in order to fix it? (if any)
thank you
Click to expand...
Click to collapse
UPDATE
i put the phone in the freezer (couldn' t wait the battery to drain) and i discover that if it is switched off you can enter in fastboot mode for one time (than you go back to bootloop)
I flashed the 4CoreOreo and now i get the same warning and error but after 30 seconds it goes off and it start to load the system.
However it doesn't finish to load it becasue it says Android is corrupted and a full wipe is suggested. I did the full wipe but nothing changed.
So now i'm stuck but in a kind of "light bootloop". I tried to updload Android 7 following the procedure through ADB but it doesn't work.
Try to go to fastboot and flash factory image of 7 from official site, and use the flash_all.sh / flash_all.bat. While you're doing that instead of flashing boot.img from the factory. Use the 4 core for 7 from the https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199 thread. Use the nougat boot.img. That's it. You'll be back on track.
Pippolinus said:
i put the phone in the freezer
Click to expand...
Click to collapse
Literally one of the worst things you could do to a smartphone(or any other type of electronics).
Your phone is probably begging for a motherboard replacement right now...
Danish Fayaz said:
Try to go to fastboot and flash factory image of 7 from official site, and use the flash_all.sh / flash_all.bat. While you're doing that instead of flashing boot.img from the factory. Use the 4 core for 7 from the https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199 thread. Use the nougat boot.img. That's it. You'll be back on track.
Click to expand...
Click to collapse
Hi, thank you for the answer.
I' ll try again changing the boot.img inside the folder ... when i tried yesterday (i tried to flash the 7 and the 8 even with the Nexus toolkit) it was not possible because everytime i unlock it (throught ADB for example) at the first reboot goes back to locked automatically, so the process stops showing some errors.
Changing that .img the problem goes away?
Pippolinus said:
Hi, thank you for the answer.
I' ll try again changing the boot.img inside the folder ... when i tried yesterday (i tried to flash the 7 and the 8 even with the Nexus toolkit) it was not possible because everytime i unlock it (throught ADB for example) at the first reboot goes back to locked automatically, so the process stops showing some errors.
Changing that .img the problem goes away?
Click to expand...
Click to collapse
If your bootloader automatically locks itself, that's a hardware issue. While booted in the bootloader, you should see "No RPMB" along one of the lines. This means that Your motherboard was replaced.
Sent from my Nexus 5X using Tapatalk
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
rahulrk.2303 said:
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
Click to expand...
Click to collapse
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Please take a full back up before you roll back.
mrmazak said:
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Click to expand...
Click to collapse
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
rahulrk.2303 said:
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
Click to expand...
Click to collapse
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
mrmazak said:
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
Click to expand...
Click to collapse
I've already tried the dload method. But holding both volume buttons + power button didn't work. It loads into the error mode screen again. Maybe I'll copy the update.zip into the root of SD card and try again. But i think the phone won't boot into software update mode.
Is it hard bricked or soft bricked?
Should i try taking it to the service center?
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
RSGI said:
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
Click to expand...
Click to collapse
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
There is Oreo downgrade proceedure on Chinese huiwei club website. But your device needs full firmware package available.
There is full downgrade packages for al00 al10 and tl10.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
That's the one i tried.
The BNDAL10 one.
rahulrk.2303 said:
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
Click to expand...
Click to collapse
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Click to expand...
Click to collapse
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
rahulrk.2303 said:
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
Click to expand...
Click to collapse
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
Click to expand...
Click to collapse
but i think the update.zip listed in file list is same , don't really know.
all three are needed for full package.
RSGI said:
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
Click to expand...
Click to collapse
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
The problem is that we can't rollback from oreo to nougat because of different partitions.
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
rahulrk.2303 said:
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
**The problem is that we can't rollback from oreo to nougat because of different partitions.
Click to expand...
Click to collapse
???Well to be true you did not flash a roll-back(did you?) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
Click to expand...
Click to collapse
mrmazak said:
???Well to be true you did not flash a roll-back(did you) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
Click to expand...
Click to collapse
Tbh, i did everything one by one because nothing seems working.
I've tried every single method, trust me.
I'm having trouble getting stock recovery to flash using Fastboot. I've followed the correct method but continue getting an error. Bootloader is unlocked and I am rooted. OEM unlocking is checked in Dev options and so is USB debugging. What is the deal?
Not sure but try typing recovery ramdisk without caps.
christo31 said:
Not sure but try typing recovery ramdisk without caps.
Click to expand...
Click to collapse
That's how the file is named in the folder. I've tried renaming it and no matter how I do it, same results.
That's okay that's the files name but why are you typing the word "recovery_ramdisk" as RECOVERY_RAMDISK
christo31 said:
That's okay that's the files name but why are you typing the word "recovery_ramdisk" as RECOVERY_RAMDISK
Click to expand...
Click to collapse
Typing it that way because that's how the file is named. All caps. Even if I change it to no capital letters it still does it.
Are you in nougat or oreo?
christo31 said:
Are you in nougat or oreo?
Click to expand...
Click to collapse
I was on O but I resolved it. It was as the all caps causing the issue. I was typing exactly as the file was named but I guess it didn't like the all caps
MikeyLee said:
I was on O but I resolved it. It was as the all caps causing the issue. I was typing exactly as the file was named but I guess it didn't like the all caps
Click to expand...
Click to collapse
I got this second hand phone which is honor 7x
And I want to update it to the latest sowtfare but twrp was installed on this phone..
How to get over it??
I'm not familiar on how to and that...
All I want is to have a good performance on my phone
(It's a CHINA ROM) VERSION
I'm currently on android version 7.0 nougat
Emui 5.1
And my question is would it lock my network carrier from where I'm from currently in???
I was fiddling around now for two full days with my 7X. Trying to root the phone which has been upgraded to 9.1.0.162 is a mess. Finally back to stock but still unsatisfied.
There are several lessons learned and findings from those two days:
- Huawei has renamed the partitions from "recovery"/"recovery2" to "recovery_ramdisk"/""erecovery_ramdisk"
- unlocking the bootloader does only let you flash recovery_ramdisk
- if you boot into recovery (Pwr & Vol+), the image from erecovery_ramdisk gets loaded
- To boot into recovery you are able to flash, it requires three buttons to be pressed (Pwr & Vol+ & Vol-)
- To flash erecovery_ramdisk, you have to flash TWRP into recovery_ramdisk and from there you can install an image into erecovery_ramdisk.
Be aware! To go back to stock, do NOT use methods that flash kernel.img from older versions. Since boot.img and kernel.img are related, there might be a great chance to brick the phone.
Lessons learned: Huawei tries to avoid rooting the phone. Since I bought the phone (it is mine!) I am the one who decides what to do with it. Even thought the hardware is still good, I'm done with this messy firmware handling. So now it is time for new hardware from a different company. For the time being I will use it unrooted and accept ads in my news readers, but it will only be a matter of time.
I tried for like 3 hours to find a boot.img and i had root on my phone, but without wifi and sound.
a quick google search showed me that it was because i had a wrong version of the boot.img, afterwards i found another one and now after i have tried installing twrp, booting and flashing using adb (stock and modified versions of boot.img) but it just keeps bootlooping. in twrp i cant wipe, make a backup, see any files in /storage/ and i have no clue what to do next.
What model 7T do you have? HD1907? What was the rom that you were using before you installed TWRP on? OOS12 does not support TWRP. Custom rom A13 does not support TWRP. Only a few custom rom A12 and OOS11 support TWRP.
Idk but I'm just wondering if flashing the last working rom image (dirty flash)? That would eliminate TWRP(?) and eliminate Magisk(?) while hopefully keeping the device from being wiped possibly?
*** Hopefully someone could/would verify this before you attempt... ***
i was on android 11 but i cant remember the version, i have HD1903 (EU ver). i THINK i had the one from the oneplus website(https://service.oneplus.com/us/search/search-detail?id=2096229) but idk anymore
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
MimKA22 said:
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
Click to expand...
Click to collapse
Msmtool back to oos11
can you describe how to use it or send a link to tutorial or smth thx man <3
MimKA22 said:
can you describe how to use it or send a link to tutorial or smth thx man <3
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
i cant find the file for my current version and it doesnt work if i try it with the only version that is android 11
and i cant turn my phone back on
and after i installed the drivers i had to restart my pc and now there is this thing at the bottom right:
testmode
windows 10 pro
...
i waited until my phone had no more battery charge and now im bootlooping again :/
nvm it just booted
im downgrading it now and i dont get the error "smth communication smth" in msmtool anymore
alr it worked my phone is wiped again but i can turn on wifi and sound
but how do i root my phone now? I have an Idea, im gonna write step by step what i think gets me a rooted phone please confirm if that would not break my phone ^^' (bootloader already unlocked)
1. enable usb debugging and allow my pc
2. download and install the latest magisk version from the github
3. download magisk patched boot.img for ver 11.0.5.1BA BUT since i cant find anything on the internet im gonna have to use the zip file from the unbrick tool thing (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/EU_HD65BA/R/) and then patch the boot.img using magisk myself
4. then use platform tools and type following commands: "adb reboot fastboot", "fastboot flash boot {the patched boot image file}"
5. then use magisk to direct install the root thing
i just realisized the unbrick thing that i wanted to use instead of a boot.img doesnt have a boot.img in it... WHERE CAN I FIND A BOOT.IMG brooo androidfilehost.com doesnt have it the unbrick tool doesnt have it
omg i realized i could update my phone to 11.0.9.1 then download the same version from official website and use the dumper to get the boot.img **** meee
wait it sais its 11.0.9.1HD65 AA and not BA **** me
k nvm i just changed the site settings to germany and now its BA
i just went for it and now my phone is rooted thank you very much for your help i would've prob tried to revert back to stock for like 2 weeks and then cry that i cant root my phone thank you so much xd