Related
edit: If you are just looking for the solution, plz click here: http://forum.xda-developers.com/showpost.php?p=68626049&postcount=11
Hey there,
first of all I want to say Thank You for this great community and the work at XDA. Awesome. :good:
I bricked my Honor 6 H60-L02 and I am lost to bring it back to life. :crying:
Where it started:
I was using the official ROM from this thread [OFFICIAL] Honor 6 (L02, L12, L04) Stock ROMs. To be more specific it was the latest Android 6.0 EMUI 4.0 B823 that I installed with all the different OTA-Files starting with the original 5.1 ROM B535. The Honor was rooted and also the bootloader is still unlocked (I already checked the status via Fastboot.).
After I while the Honor 6 started to crash sometimes and the headphone-buttons didn't worked anymore. Then a few days ago the phone crashed and I was not able to boot it again.
And so I tried this:
Using the Rollback-Zip to go back to 5.1. But the 3btn-method didn't worked. The phone didn't want to boot into the recovery. Also the Vol+ and Power-Button didn't work to start the Recovery of the phone. Result: Bootloop.
So I installed ADB and Fastboot (with all necessary drivers) and tried to flash the phone with the 5.1 B535 (as mentioned in Honor 6 H60-L02 Hard Bricked - Only access to fastboot (Vol+ and Usb PC)) because there isn't a 6.0 B823 ROM available. I was able to flash boot, recovery, cust, system, userdata and another one I forgot right now. But the result was the same: Bootloop and no 3-btn or recovery via Vol+ and Power-Button. I also tried to flash it with the HonorTool. Same result.
Then I tried to flash different TWRP versions as recovery. Result: The same as above.
So I tried another official ROM 5.1 B526 because someone had the same problem and was able to recover his phone with this ROM (another thread in the forum). But that didn't worked ether.
Then I tried to flash all the img-files of the 5.1. B535 as crc, ptable and so on because I thought that there could be the problem. But when I tried e.g. to flash crc I get the error FAILED: command not allowed. So I tried to unlock the phones partition via Fastboot and fastboot flashine unlock_critical. But using the command unlock_critical gives me also the Failed error. So I was lost again.
Status right now:
I'm still able to boot into the bootloader via Vol- and Power. But right now the phone was running out of battery. Means I see the red battery symbol when I try to start the phone via the power button (without connecting to the PC or charger) but it isn't booting even into the bootloop. The red battery symbol pops up for a second and the screen went black again.
When I use the charger then the symbol changes to a green battery and stays there, but not the moving one that indicates that the phone is charging. When I use the Power button with usb-charger connected to start the phone I'm trapped in the bootloop again.
You see I already tried a lot of different things I could find on the forum. But nothing worked for me.
I know that it was a fault to try to install 5.1 B535 without the rollback, but I wasn't able to rollback as mentioned under point 1.
Maybe anyone could give me a hint and help me to bring my phone back to life.
Thx a lot! I appreciate that al lot!
If you need anymore informations, plz let me know.
Greets, mike175de
P.S: Sorry for my school english. It is a little bit rusty ;o)
mike175de said:
Hey there,
first of all I want to say Thank You for this great community and the work at XDA. Awesome. :good:
I bricked my Honor 6 H60-L02 and I am lost to bring it back to life. :crying:
Where it started:
I was using the official ROM from this thread [OFFICIAL] Honor 6 (L02, L12, L04) Stock ROMs. To be more specific it was the latest Android 6.0 EMUI 4.0 B823 that I installed with all the different OTA-Files starting with the original 5.1 ROM B535. The Honor was rooted and also the bootloader is still unlocked (I already checked the status via Fastboot.).
After I while the Honor 6 started to crash sometimes and the headphone-buttons didn't worked anymore. Then a few days ago the phone crashed and I was not able to boot it again.
And so I tried this:
Using the Rollback-Zip to go back to 5.1. But the 3btn-method didn't worked. The phone didn't want to boot into the recovery. Also the Vol+ and Power-Button didn't work to start the Recovery of the phone. Result: Bootloop.
So I installed ADB and Fastboot (with all necessary drivers) and tried to flash the phone with the 5.1 B535 (as mentioned in Honor 6 H60-L02 Hard Bricked - Only access to fastboot (Vol+ and Usb PC)) because there isn't a 6.0 B823 ROM available. I was able to flash boot, recovery, cust, system, userdata and another one I forgot right now. But the result was the same: Bootloop and no 3-btn or recovery via Vol+ and Power-Button. I also tried to flash it with the HonorTool. Same result.
Then I tried to flash different TWRP versions as recovery. Result: The same as above.
So I tried another official ROM 5.1 B526 because someone had the same problem and was able to recover his phone with this ROM (another thread in the forum). But that didn't worked ether.
Then I tried to flash all the img-files of the 5.1. B535 as crc, ptable and so on because I thought that there could be the problem. But when I tried e.g. to flash crc I get the error FAILED: command not allowed. So I tried to unlock the phones partition via Fastboot and fastboot flashine unlock_critical. But using the command unlock_critical gives me also the Failed error. So I was lost again.
Status right now:
I'm still able to boot into the bootloader via Vol- and Power. But right now the phone was running out of battery. Means I see the red battery symbol when I try to start the phone via the power button (without connecting to the PC or charger) but it isn't booting even into the bootloop. The red battery symbol pops up for a second and the screen went black again.
When I use the charger then the symbol changes to a green battery and stays there, but not the moving one that indicates that the phone is charging. When I use the Power button with usb-charger connected to start the phone I'm trapped in the bootloop again.
You see I already tried a lot of different things I could find on the forum. But nothing worked for me.
I know that it was a fault to try to install 5.1 B535 without the rollback, but I wasn't able to rollback as mentioned under point 1.
Maybe anyone could give me a hint and help me to bring my phone back to life.
Thx a lot! I appreciate that al lot!
If you need anymore informations, plz let me know.
Greets, mike175de
P.S: Sorry for my school english. It is a little bit rusty ;o)
Click to expand...
Click to collapse
Just flash boot, Cust, recovery and system images and let it boot normally. Don't do any button combo. I have had instances where it works. Give it a try.
With which version?
muradulislam said:
Just flash boot, Cust, recovery and system images and let it boot normally. Don't do any button combo. I have had instances where it works. Give it a try.
Click to expand...
Click to collapse
Thx for your reply.
With which version should I flash? B535 or B526? Should I only flash the three images boot, cust and system? Nothing else?
Thx for a reply!
mike175de said:
Thx for your reply.
With which version should I flash? B535 or B526? Should I only flash the three images boot, cust and system? Nothing else?
Thx for a reply!
Click to expand...
Click to collapse
You can use any firmware but the latest one should be better, and flash four images, boot, Cust, system and boot and let it boot normally.
Then put the dload folder with update.app in sd card and do an update from settings.
Thx. I will give it a try when I'm back from work.
I let you know if it is working.
mike175de said:
Thx. I will give it a try when I'm back from work.
I let you know if it is working.
Click to expand...
Click to collapse
I meant to say flash boot, Cust, recovery and system images.
Wrote boot twice
Nothing changed
Hey muradulislam,
Thx again.
I flashed the images (boot.img twice) but without success. Still the same error (with normal booting aka without any special button combination or with button combination). The honor boots and stays in the bootmode aka bootloop with the led blinkin red. And I still can't boot into recovery via Vol+ and Power..
Any other suggestions?
mike
mike175de said:
Hey muradulislam,
Thx again.
I flashed the images (boot.img twice) but without success. Still the same error (with normal booting aka without any special button combination or with button combination). The honor boots and stays in the bootmode aka bootloop with the led blinkin red. And I still can't boot into recovery via Vol+ and Power..
Any other suggestions?
mike
Click to expand...
Click to collapse
Of all the things you have already tried, the only thing remains to take it to a Huawei service center.
May be someone else can help you here but I have read most of honor 6 and 7 posts and I don't think there is anything there for this problem atm.
Hmm, thx. That is bad...
I bought this phone in China when I was there for work. And I suppose that the german service of Huwaei will not help me at all with this phone.
Does anybody else have any clue how to bring the phone back to life?
Thx a lot.
mike175de said:
Hmm, thx. That is bad...
I bought this phone in China when I was there for work. And I suppose that the german service of Huwaei will not help me at all with this phone.
Does anybody else have any clue how to bring the phone back to life?
Thx a lot.
Click to expand...
Click to collapse
I myself have an H60-L01, bought it from china, bricked and tried everything to revive it but could not, still have to try Huawei customer service in Pakistan, am not sure whether they will be able to help me or not, but will give it a try. I wish you luck buddy. Hope you find a solution.
It's alive ;o)
The phone is working again.
Here are the steps I did for everybody else confrontated with same problem:
1. Download your last working ROM or OTA-File: In my case the OTA-File OTA-EMUI 4.0_H60-L02-L12_B811_B823.zip from this Mega-Link:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!KwhlRKYR
2. Unzip the file and extract recovery.img and boot.img with the Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454).
3. Boot the phone into fastboot mode (connect the USB cable, press the power button to turn off and immediately press the volume down button).
4. Use fastboot to flash the two images of 2. If you need fatsboot you can find it here http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip (Extract adb.zip and copy the extracted files from 2. in the folder adb. In the adb folder run cmd.exe as administrator.)
5. Use this commands for flashing:
fastboot devices => If the device is recognized correctly it is displaying a series of numbers
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot reboot
6. Charge the phone with the Huawei charger, not via USB/PC! (50% is enough.)
7. Download in the meantime the Developer ROM H60_EMUI3.1_Android5.1_6.1.1.zip from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
8. Extract the zip file from 7. and copy UPDATE.app onto your SD-Card into /dload
9. Insert the SD without connecting.
9.1. Disconnect the USB cable from your PC or charger.
9.2. Press the Power button to turn off (maybe that is not necessary.)
9.3. When you feel the vibration press 3btn (Vol+ and Vol- and Power).
9.4. When the Honor logo appears connect your SD-Card (continue to press 3btn for 8 -10 more seconds) => Wait for the recovery process, it should start automatically.
10. After installation Android boots. Skip the first step installation (you should now have the 6.1.1. Developer-Edition installed). Rollback to Android 5.1.1 with the Rollback-File Rollback 591 EMUI3.0.zip from here:
http://www.mediafire.com/download/9qrd8zm9280gy5e/Rollback+591+EMUI3.0.zip
Do do so put the unzipped UPDATE.app from the Rollback-File onto your SD-Card and do a local update via the Update Manager.
11. Boot into Android again (it will still be the 6.1.1 Developer Edition). In my case I want to install the latest Android 5.1.1 B535 from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
I did it via local update again.
12.. After installation and booting => Voila here is your working Android 5.1.1 B535 again. Have fun
13. Brick it again with updating to Android 6.0
I hope I could help somebody with my experience to bring his/her phone back to life.
CU, mike
The same can not restore brick
Hello! In what condition I have a phone? My phone is loaded in error func_boot_kernel.
igorxxl said:
Hello! In what condition I have a phone? My phone is loaded in error func_boot_kernel.
Click to expand...
Click to collapse
Have you unlocked and rooted it?
When does it says that message?
error! no func. func_boot_kernel or _recovery
zinko_pt said:
Have you unlocked and rooted it?
When does it says that message?
Click to expand...
Click to collapse
The bootloader is unlocked. Root is. Phone is loaded into the error! no func. func_boot_kernel. If you try to enter into the recovery, the error! no func. func_boot_recovery.
The error is the same as here club.huawei.com/thread-7962289-1-1.html
I tried to put EMUI4.0, then the phone stopped working. Through ADB stitched, weighting system, boot, recovery, cust.img. It shows all ok. But then the error again. He tried to put different versions of TWRP. On the 3 button also does not work.
Thank you for your attention to my problem.
igorxxl said:
The bootloader is unlocked. Root is. Phone is loaded into the error! no func. func_boot_kernel. If you try to enter into the recovery, the error! no func. func_boot_recovery.
The error is the same as here club.huawei.com/thread-7962289-1-1.html
I tried to put EMUI4.0, then the phone stopped working. Through ADB stitched, weighting system, boot, recovery, cust.img. It shows all ok. But then the error again. He tried to put different versions of TWRP. On the 3 button also does not work.
Thank you for your attention to my problem.
Click to expand...
Click to collapse
You can't use 3 button with custom recovery and root. It wont work.
You need stock recovery in the same version as the rest of files used to flash other partitions.
Flash all stock partitions, then just boot the phone. Check if it works. Forget about TWRP and root for now. One thing at a time.
Nothing helps. I sew different versions via Fastboot. Everywhere all shows OK. However, when you restart the exact same mistake again ..
igorxxl said:
Nothing helps. I sew different versions via Fastboot. Everywhere all shows OK. However, when you restart the exact same mistake again ..
Click to expand...
Click to collapse
You can also try installing custom recovery and restore a twrp backup of ROM.
zinko_pt said:
You can't use 3 button with custom recovery and root. It wont work.
You need stock recovery in the same version as the rest of files used to flash other partitions.
Flash all stock partitions, then just boot the phone. Check if it works. Forget about TWRP and root for now. One thing at a time.
Click to expand...
Click to collapse
goldfinv said:
You can also try installing custom recovery and restore a twrp backup of ROM.
Click to expand...
Click to collapse
i'm in the same situation with my honor 6 plus pe-ul00 i'll try this metod!
mike175de said:
The phone is working again.
Here are the steps I did for everybody else confrontated with same problem:
1. Download your last working ROM or OTA-File: In my case the OTA-File OTA-EMUI 4.0_H60-L02-L12_B811_B823.zip from this Mega-Link:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!KwhlRKYR
2. Unzip the file and extract recovery.img and boot.img with the Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454).
3. Boot the phone into fastboot mode (connect the USB cable, press the power button to turn off and immediately press the volume down button).
4. Use fastboot to flash the two images of 2. If you need fatsboot you can find it here http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip (Extract adb.zip and copy the extracted files from 2. in the folder adb. In the adb folder run cmd.exe as administrator.)
5. Use this commands for flashing:
fastboot devices => If the device is recognized correctly it is displaying a series of numbers
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot reboot
6. Charge the phone with the Huawei charger, not via USB/PC! (50% is enough.)
7. Download in the meantime the Developer ROM H60_EMUI3.1_Android5.1_6.1.1.zip from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
8. Extract the zip file from 7. and copy UPDATE.app onto your SD-Card into /dload
9. Insert the SD without connecting.
9.1. Disconnect the USB cable from your PC or charger.
9.2. Press the Power button to turn off (maybe that is not necessary.)
9.3. When you feel the vibration press 3btn (Vol+ and Vol- and Power).
9.4. When the Honor logo appears connect your SD-Card (continue to press 3btn for 8 -10 more seconds) => Wait for the recovery process, it should start automatically.
10. After installation Android boots. Skip the first step installation (you should now have the 6.1.1. Developer-Edition installed). Rollback to Android 5.1.1 with the Rollback-File Rollback 591 EMUI3.0.zip from here:
http://www.mediafire.com/download/9qrd8zm9280gy5e/Rollback+591+EMUI3.0.zip
Do do so put the unzipped UPDATE.app from the Rollback-File onto your SD-Card and do a local update via the Update Manager.
11. Boot into Android again (it will still be the 6.1.1 Developer Edition). In my case I want to install the latest Android 5.1.1 B535 from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
I did it via local update again.
12.. After installation and booting => Voila here is your working Android 5.1.1 B535 again. Have fun
13. Brick it again with updating to Android 6.0 [emoji14]
I hope I could help somebody with my experience to bring his/her phone back to life.
CU, mike
Click to expand...
Click to collapse
I got a problem at 9.3 or 9.4. The recovery wont start i see only honor logo i used PE_EMUI3.1_Android5.1_6.1.1.zip (as developer edition i.e sdcard/dload/UPDATE.APP) and PE-UL00-V100R001CHNC00B200.zip to extract and flash BOOT.img and RECOVERY.img
any ideas why i can't enter in recovery? =(
EDIT: "fixed with DC-Phoenix tool"
Update 1/2/18 : Removed link until we get a Restore that works across all device's.
This will will help you restore back to a clean OS install using Twrp.
1.Download Files to your computer Unzip and place "Stock Restore 123017" Folder in a folder Named "TWRP".
2.Move TWRP folder you created and place them on your Phone's SD Card or Push them using adb command
Code:
adb push TWRP /TWRP
3. While in Twrp recovery click Restore and navigate to the back up folder.
4. Restore all and reboot. First boot will take a couple of mins so give it time.
This should bring you back up from the dead.
Edit:
If you accidentally flashed Twrp in the wrong slot then only restore boot using this back up.
This should Fix any wifi issues you may be having.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w
Awesome, thanks again! Glad to see your ontop of things in the development of this phone!
@Xshooter726
Can this be used to rebrand the carrier version? Three are still slacking with the second update which I feel is affecting the camera and want to resolve it myself now dees has blessed us with recovery
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
What slot did you restore to? and is the message of corruption in TWRP?
PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
Getting the same thing unfortunately. Might have to wait for the factory images.
CptClubs said:
@Xshooter726
Can this be used to rebrand the carrier version? Three are still slacking with the second update which I feel is affecting the camera and want to resolve it myself now dees has blessed us with recovery
Click to expand...
Click to collapse
Not sure. I don't have a carrier version to test it with.
fivearcosstheeye said:
Getting the same thing unfortunately. Might have to wait for the factory images.
Click to expand...
Click to collapse
Can you run Md5 check sum? I think my upload may have been interrupted.
MD5 Should match this
fe23d7ebb04818e5f3d661e5b67acee0
Xshooter726 said:
Can you run Md5 check sum? I think my upload may have been interrupted.
MD5 Should match this
fe23d7ebb04818e5f3d661e5b67acee0
Click to expand...
Click to collapse
Ran a check and the upload was correct. I've tried restoring the backup to both A & B but neither would work. I'm using a Three branded Razer Phone so it might just be something to do with that?
PupPupG said:
Ran a check and the upload was correct. I've tried restoring the backup to both A & B but neither would work. I'm using a Three branded Razer Phone so it might just be something to do with that?
Click to expand...
Click to collapse
Hmmm that maybe why. I was running the latest update when I did the back up and Three branded phones haven't received the latest update yet. Looks like Three branded phones will have to wait for Official Images. Sorry guys
..Well Unless someone with a clean os installed on a three branded phone does a back up similar to mine then that should work.
PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
Xshooter726 said:
Hmmm that maybe why. I was running the latest update when I did the back up and Three branded phones haven't received the latest update yet. Looks like Three branded phones will have to wait for Official Images. Sorry guys
..Well Unless someone with a clean os installed on a three branded phone does a back up similar to mine then that should work.
Click to expand...
Click to collapse
I don't have a branded carrier version. Going to try a couple more things and if that don't work we'll have to wait for factory images or a custom rom.
When restoring using TWRP, we're supposed to include the 'Vendor' options as well as part of the restoring process? I also restored in both slots.
I have a feeling I just made a very expensive mistake when I tried restoring - left out the 'Vendor' (bottom two) and now it's been on the booting animation for a good 30mins. Can't force shut off by holding the power button or using the vol dwn + pwr to get into download mode. Holding vol up+pwr will get me the 'Razer powered by Android' splash screen and then it just goes back into the animation.
BakaSenpai said:
When restoring using TWRP, we're supposed to include the 'Vendor' options as well as part of the restoring process? I also restored in both slots.
I have a feeling I just made a very expensive mistake when I tried restoring - left out the 'Vendor' (bottom two) and now it's been on the booting animation for a good 30mins. Can't force shut off by holding the power button or using the vol dwn + pwr to get into download mode. Holding vol up+pwr will get me the 'Razer powered by Android' splash screen and then it just goes back into the animation.
Click to expand...
Click to collapse
Hey man, I ran into the same issue as you, so what I did was leave the usb plugged in and held down vol up+power till the phone's screen went black, then immediately held down the vol down button, this brought me into download mode, then I entered:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
into adb and my phone went back into twrp.
Can't help with the getting back into the system, I'm still waiting on that too, but hope this helps
Same for me. device corrupted after the restock restore on a US imported Razer Phone. Cant use it now. Have to get a replacement cheap phone since it is my daily phone lmfao.
My upload is for a full restore but if you have only messed up when flashing boot IMG and it's keeps going straight to Twrp then only restore boot from my back up. Your system should still be intact. I will upload just the boot.img alone.
If you accidentally flashed Twrp in the wrong slot then only restore boot using twrp.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w
Xshooter726 said:
If you accidentally flashed Twrp in the wrong slot then only flash this boot.img using fastboot to get you back to normal.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w
Click to expand...
Click to collapse
Maybe i am wrong but in this zip file is a twrp boot image not a boot.img file ?
Quashhh said:
Hey man, I ran into the same issue as you, so what I did was leave the usb plugged in and held down vol up+power till the phone's screen went black, then immediately held down the vol down button, this brought me into download mode, then I entered:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
into adb and my phone went back into twrp.
Can't help with the getting back into the system, I'm still waiting on that too, but hope this helps
Click to expand...
Click to collapse
Hey, thanks for that suggestion! I was able to get into download mode and I flashed my phones own recovery and I got it to work. Wiped both a & b slot and restored both of them with my recovery.
The only problem (not so sure if it is an issue) is the backup I made is only of the Boot and System Image as per the TWRP instructions. So when I boot into slot a_ I get an error when I boot up 'There's an internal problem with your device. Contact your manufacturer for details.' Switching into slot b, I don't get that error. However, here's the weird thing (I think at least), when I go back into TWRP and switch to slot a, I get a bootloop into TWRP.: So, if I decide to continue on, and flash the TWRP zip file and then subsequently Magisk - I'll lose wifi and etc.
If I end up using Xshooter's full restore img - I'll do the same thing - wipe both slot a&b and restore both slots after. However, I'll get a message after the Razer splash screen say my phone is 'Corrupt' - and this is if I restore with the Vendor options. If I exclude the Vendor options, I'll be stuck in the animation. I lied - I'm stuck on the Corrupt screen now. I can get into TWRP at least...
So, in a bit of a bind here now.
BakaSenpai said:
Hey, thanks for that suggestion! I was able to get into download mode and I flashed my phones own recovery and I got it to work. Wiped both a & b slot and restored both of them with my recovery.
The only problem (not so sure if it is an issue) is the backup I made is only of the Boot and System Image as per the TWRP instructions. So when I boot into slot a_ I get an error when I boot up 'There's an internal problem with your device. Contact your manufacturer for details.' Switching into slot b, I don't get that error. However, here's the weird thing (I think at least), when I go back into TWRP and switch to slot a, I get a bootloop into TWRP.: So, if I decide to continue on, and flash the TWRP zip file and then subsequently Magisk - I'll lose wifi and etc.
If I end up using Xshooter's full restore img - I'll do the same thing - wipe both slot a&b and restore both slots after. However, I'll get a message after the Razer splash screen say my phone is 'Corrupt' - and this is if I restore with the Vendor options. If I exclude the Vendor options, I'll be stuck in the animation.
So, in a bit of a bind here now.
Click to expand...
Click to collapse
No problem, I was just about to give up and settle with a pretty cool paper weight till i tried that out, now i'm gonna try and restore the backup to both slots and try Xshooters method...
Fingers crossed
@BakaSenpai and @Quashhh if you both are able to put your backup on google drive to share it with me so that i can try some options? i have the same issue now. I hope you both get it sorted.
grtz
Steven
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
divvykev said:
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
Click to expand...
Click to collapse
Likely the phone was encrypted
divvykev said:
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Click to expand...
Click to collapse
For me this happened a few times, including when I tried to 'fastboot boot' a wrong image or some latest bluespask Twrps. This is the state when the the phone has hung trying to execute something. The remedy is to hold the power button pressed for something like 10 seconds and the phone will switch off (this is a hardware feature so shlould not fail). After that I go to fastboot normally - press volUp+Power for a few seconds till the fastboot message. Also, make sure that you are not charging, as this seems to have prevented me going to fastboot once.
Today I had a strange issue with my Oneplus 7 pro GM1913 running OOS 9.5.5, device unlocked, twrp and rooted. My device ran out of charge and was turned off. When I plugged into the charger, it boots up and for a few second the oneplus logo and charge the device for some time page came in and then the bootloader unlocked screen came in. I haven't charged the device offline after the battery ran out, it was my first time and i thought it was supposed to be like that. But after some time also it was on the same page. Then i plugged out the device and it was stuck on that page. I tired hard reboot, tried to connect to computer. Nothing was successful. Computer showed unknown device and failed to successfully connect. Not recognised as adb device shown nor fastboot device. Then atleast I tried entering into fastboot mode by pressing power button + volume up. At that time it rebooted into system and then everything was okay. But then i noticed i also lost the twrp recovery. Then i had to flash twrp through magisk manager.
Anyone has any idea what happened? Thanks in advance
You have to flash magisk again after flashing TWRP.
deborok said:
You have to flash magisk again after flashing TWRP.
Click to expand...
Click to collapse
Yeah I did everything and it was working properly for a week amd then this happened
sachinkjohn1 said:
Yeah I did everything and it was working properly for a week amd then this happened
Click to expand...
Click to collapse
flash stock boot. img
zams85 said:
flash stock boot. img
Click to expand...
Click to collapse
It's working now.. But I just want to know whether this happened to anyone else? Or the reason for this?
sachinkjohn1 said:
It's working now.. But I just want to know whether this happened to anyone else? Or the reason for this?
Click to expand...
Click to collapse
I got stuck there once I was trying to flash twrp somehow. Same fix
Stuck at the bootlogo
Hey guys, i hope i get some help from here.. tried to root my one plus 7 pro international version installed twrp everything worked fine... and after that i tried to reboot in system mode.. now im stuck at the bootlogo with the red middle dot and the 2 white ones. i cant even turn it of now.. no command are working... can anybody help me to fix this pls?
Thanks!!!
I had exactly the same problem. System was running fine with just Magisk installed (I boot TWRP with fastboot on a computer).
Then I ran completely out of charge, and the OP7Pro wouldn't boot anymore: at power on, it shows briefly the OnePlus logo, then displays the boot loader unlocked warning for a very long time (a few minutes), then goes to the bootloader menu.
I can boot TWRP and unlock the data partition. I will try flashing the stock boot and see what happens (and report).
Edit: I had to reflash stock boot and system to have the device boot again.
hi guys,please need help;I have just unlock bootloader on my one plus 7 pro and i was fastboot it with twrp img but i didn't install the twrp recovery one my phone so now the phone blocked on de bootloader unlock screen, I tried to switched of but always back on the same screen, please need help how to do ,thanks
whenever i boot i am stuck at this screen. I flashed the wrong boot.img. How to fix this?
saransh186 said:
whenever i boot i am stuck at this screen. I flashed the wrong boot.img. How to fix this?
Click to expand...
Click to collapse
Enter fastboot and flash the correct boot.
@soka said:
Enter fastboot and flash the correct boot.
Click to expand...
Click to collapse
Unable to enter fastboot
Everytime i switch on the device this is the only screen i see
saransh186 said:
Unable to enter fastboot
Everytime i switch on the device this is the only screen i see
Click to expand...
Click to collapse
I figured it out. basically when i get to the above attached image I was required to hold volume up+down+power key until the fastmode doesn't comes up. It will take 20-25 seconds. So you will be required to hold it for that long.
My Poco X3 Pro was running in Pixel experience plus custom ROM. My pixel experience recovery was gone. so i installed TWRP recovery. but my phone got stuck in bootloop while installing magisk via TWRP then I tried to flash MIUI 14 fastboot rom using mi flash tool but failed again and again. I also tried to flash directly using platform tools. but it doesn't work. after then I flashed Pixel experience recovery via fastboot and then installed Pixel experience ROM this time my phone started. but when I power off the device and tried to on it again it stuck in bootloop. then I again installed Pixel experience ROM and turned my phone on. but I'm afraid that if I turn off my phone will again stuck in the bootloop. how can I fix this?
Shahriar566 said:
My Poco X3 Pro was running in Pixel experience plus custom ROM. My pixel experience recovery was gone. so i installed TWRP recovery. but my phone got stuck in bootloop while installing magisk via TWRP then I tried to flash MIUI 14 fastboot rom using mi flash tool but failed again and again. I also tried to flash directly using platform tools. but it doesn't work. after then I flashed Pixel experience recovery via fastboot and then installed Pixel experience ROM this time my phone started. but when I power off the device and tried to on it again it stuck in bootloop. then I again installed Pixel experience ROM and turned my phone on. but I'm afraid that if I turn off my phone will again stuck in the bootloop. how can I fix this?
Click to expand...
Click to collapse
Pixel with magisk and modules?
No I was just installing magisk via TWRP
try installing magisk via image patching, works for me everytime. Magisk creator himself warn against using TWRP to flash magisk.zip
I was asking how to fix bootloop. My device is on but if I power off it will go to bootloop again then I will have to flash Pixel experience again. My problem is bootloop not installing magisk
Shahriar566 said:
I was asking how to fix bootloop. My device is on but if I power off it will go to bootloop again then I will have to flash Pixel experience again. My problem is bootloop not installing magisk
Click to expand...
Click to collapse
Tried flash official MIUI recovery ROM with TWRP?
Tried official MIUI fastboot rom not recovery
Shahriar566 said:
Tried official MIUI fastboot rom not recovery
Click to expand...
Click to collapse
Put the fastboot ROM in C drive directly, then go into the folder, find the "flash_all.bat" to flash it under fastboot mode.
Don't use Mi-Flash.
Can try the recovery flashing method with TWRP.
Check if you still got mobile SIM card working, with the original intact IMEI.
I tried "flash_all.bat" but after clicking it runs for 1 sec then disappear
Shahriar566 said:
I tried "flash_all.bat" but after clicking it runs for 1 sec then disappear
Click to expand...
Click to collapse
Rename the folder name shorter, like "ROM."
Phone needs to be in Fastboot mode, before running that flash_all.bat.
There could be some issue connecting your phone with the PC. Could be driver issue, permission issue, AMD CPU issue and/or other reasons.
Try TWRP to flash the recovery ROM would be easier.
Remember to "Format data" in TWRP.
Yeah I know the rules . I did it several times with no issue . And I have all the drivers installed in the PC.
Actually I'm afraid of power off the phone cuz if I power off it will go to the bootloop again then I again have flash pixel experience.
I just want to know does this ever happen that my phone is totally ok and if I power off it will go to bootloop?
Shahriar566 said:
Yeah I know the rules . I did it several times with no issue . And I have all the drivers installed in the PC.
Actually I'm afraid of power off the phone cuz if I power off it will go to the bootloop again then I again have flash pixel experience.
I just want to know does this ever happen that my phone is totally ok and if I power off it will go to bootloop?
Click to expand...
Click to collapse
This had happened to me rarely that the phone failed to start, stuck on the booting logo and self-boot again, then it booted correctly on the 2nd boot.
Don't know if your phone is totally ok or not, since there are cases that had the CPU ball issues. To make sure, it's better to find Xiaomi/Redmi/Poco official repair center and or customer service.
Even if the phone is out of warranty, could still ask for a phone hardware checkup, with some fee needed.
Thanks for the advice
pl1992aw said:
This had happened to me rarely that the phone failed to start, stuck on the booting logo and self-boot again, then it booted correctly on the 2nd boot.
Don't know if your phone is totally ok or not, since there are cases that had the CPU ball issues. To make sure, it's better to find Xiaomi/Redmi/Poco official repair center and or customer service.
Even if the phone is out of warranty, could still ask for a phone hardware checkup, with some fee needed.
Click to expand...
Click to collapse
Actually today I rebooted my device and it went to bootloop but after showing it's boot logo 3 or 4 times it started.
What do you think about it?
Shahriar566 said:
Actually today I rebooted my device and it went to bootloop but after showing it's boot logo 3 or 4 times it started.
What do you think about it?
Click to expand...
Click to collapse
Unknown reason. Don't know if it's ROM issue or hardware issue.
Can try downgrade to old firmware versions.
Can also try older ROM versions.