Related
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
I had this happen to me after installing TWRP for the first time. It would keep rebooting to TWRP. This was after making sure I flashed SuperSU as well. Eventually in a moment of "might as well see what will happen" I rebooted then held down the power button and volume down. Got to the option if I wanted to factory reset my phone which I did which booted into TWRP. Rebooted to system from there which got me out of the TWRP Bootloop.
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
Download the deodex rom flash it, then flash no_verity , then format data.
Mastajeff said:
Download the deodex rom flash it, then flash no_verity , then format data.
Click to expand...
Click to collapse
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Decrypt data.
As a general statement : Almost all TWRP bootloops are due to users not backing up their data, and then formatting data.
Hardware encryption is not supported.
Decrypt your data, flash a ROM, and if that ROM doesn't have SuperSU, flash SuperSU.
Go flash my v5 MOD ROM.
Decrypt your data! 95% of TWRP loop cases are due to data not being decrypted, or some other step the user failed to follow.
Good luck.
---------- Post added at 04:28 PM ---------- Previous post was at 04:28 PM ----------
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
This is because you went to Advanced Wipe, and formatted /system.
Make sure you are on the latest TWRP, make sure you're data is decrypted, and then go flash my v5 MOD ROM.
For those that are still having troubles. My guide works: forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
Mastajeff said:
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
Click to expand...
Click to collapse
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
It's been determined that it does this when it finds an update in the fota and or misc folders. The phone downloads updates even when you tell it not to. It just doesn't install them without your permission.
Easy to get out of with the volume down and power button reset procedure which then deletes the files automatically or you can delete the files in twrp to fix it.
Poda_jj said:
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
Click to expand...
Click to collapse
All the bootloops for the V20 so far are all due to modifications and rooting. There are some roms that work for everyone but just refuses to work on my phone and will just bootloop. I doubt that the cause of the software bootloop is fully known. I've followed directions 100% on working romss and it would bootloop but installed a different version of the same rom and it worked. None of the bootloop "fixes" did anything for me. Fortunately, the rom that I installed is still awesome and works great.
LS997 BTW
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
bond32 said:
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
Click to expand...
Click to collapse
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
dangercl0se said:
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
Click to expand...
Click to collapse
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Team DevDigitel said:
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Click to expand...
Click to collapse
Thanks. I suppose deleting those folders isn't possible without root access?
bond32 said:
Thanks. I suppose deleting those folders isn't possible without root access?
Click to expand...
Click to collapse
yeah MISC and FOTA are protected as read only for the user without root.
Mrsana said:
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
Click to expand...
Click to collapse
Thank you, This Worked for me.
bond32 said:
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
Click to expand...
Click to collapse
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
dangercl0se said:
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
Click to expand...
Click to collapse
Did you try the above where you delete the misc and fota folders?
Hi !
To prepare the Nougat update I wanted to go back to original rom but I'm currently stuck on honor blue screen. I was on CM13 with encryption erase.
For info I was on FRD-L09C432B131
What I did :
Flash the original recovery
Put the dload folder with the full rom uptade.app inside
Reboot with vol+ and vol-
Installation was ok
But at the reboot i'm stuck on honor screen
I tryed to wipe data/factory reset and cache from the original recovery but doesn't change anything.
Every help is appreciate.
Thanks guys.
I unlocked again my bootloader but wasn't able to format custom partition, message : FAILED (command remote not allowed)
I'm not able to erase anything too, same message.
I was able to flash boot, recovery, cust and system. I flash again the rom with dload but get stuck again in honor screen. A Factory reset don't resolve my problem.
I think my encryption is still broken because when I unlock again the bootloader and flash TWRP I can't wipe anything, message : Failed to mount '/data' (Invalid argument). Unable to recreate /data/media folder.
Is there a way to do anything ? This phone is driving me mad..
Thanks !
You need to flash first the rollback update from honor site, then flash b131
I was not on Nougat. Are you sure ?
I'm actually on the same boat. I can't seem to get it working either, I first did the rollback update from the Honor site than flashed the update firmware they had on there. That didn't work. Then I tried going into e-recovery, and try doing that. This say's it was successful, but I'm still stuck on the honor screen on boot.
To be clear again I wasn't on Nougat, were you ? If yes your problem is not the same. Good luck anyway..
Problem fix. I was using an old twrp, the one I used to root the device. I tryed with the TWRP suggest for flashing CM13 and I was finally able to wipe the DATA partition.
After that after flashing the B131 via the dload folder I could boot to the original rom.
Hope my wasted night fighting with my H8 can help someone.
I'm a morron but I definitely hate Honor.
Androhyp said:
Problem fix. I was using an old twrp, the one I used to root the device. I tryed with the TWRP suggest for flashing CM13 and I was finally able to wipe the DATA partition.
After that after flashing the B131 via the dload folder I could boot to the original rom.
Hope my wasted night fighting with my H8 can help someone.
I'm a morron but I definitely hate Honor.
Click to expand...
Click to collapse
WOW, I've been trying to fix my bricked phone for 2 nights already and this worked like a charm! I can breathe now. Thanks!
J V A said:
WOW, I've been trying to fix my bricked phone for 2 nights already and this worked like a charm! I can breathe now. Thanks!
Click to expand...
Click to collapse
Happy to read that
help me,Im using honor 8 FRD-L09 model,I accidently wipe out my os
Androhyp said:
Happy to read that
Click to expand...
Click to collapse
Hwlp me out..to restore the os pleaseeeee
I have European honor8 32gb b389
i install lineage os 7.1.2 but dont like it and wont do restore backup with twrp, but after restore the phone blocked on honor screen.
i tried everything, and now i have a lot of confusion, i tried dload, but nothing happened when i turn on with +-power. I try with huawai extractor to flash boot system cust and recovery but nothing device go in bootloop. if i flash recovery from b131 firmware i can go in dload but freeze at 5%
what i can do? sorry for my English, i speak Italian and Russian if somebody want to help me in pm.
crn4 said:
I have European honor8 32gb b389
i install lineage os 7.1.2 but dont like it and wont do restore backup with twrp, but after restore the phone blocked on honor screen.
i tried everything, and now i have a lot of confusion, i tried dload, but nothing happened when i turn on with +-power. I try with huawai extractor to flash boot system cust and recovery but nothing device go in bootloop. if i flash recovery from b131 firmware i can go in dload but freeze at 5%
what i can do? sorry for my English, i speak Italian and Russian if somebody want to help me in pm.
Click to expand...
Click to collapse
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
davide.melkior said:
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
Click to expand...
Click to collapse
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
ok, i tried now the first update.app to rollback but device freeze (Your device is booting now)
i think i need to flash from fastboot stock recovery from b389 firmware before do this
crn4 said:
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
Click to expand...
Click to collapse
Unless you flash the rollback package you can't flash older version. Not sure if rollback package for your model os released
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
crn4 said:
thnx , i know this method, i tried it yesterday but don't worked, now i retry and reply to you the results
ok, i tried now the first update.app to rollback but device freeze (Your device is booting now)
i think i need to flash from fastboot stock recovery from b389 firmware before do this
Click to expand...
Click to collapse
Ofcourse you need to flash the stock recovery. Are you trying in twrp?
davide.melkior said:
Are you sure you're using the rollback package before? You can download it from honor official website, then you move the firmware file in a dload folder on your sdcard. Boot up using both + and - buttons and the power button in the same time and the phone will force the flashing of the rollback ( package needed to go back from android 7 to android 6) file. Then you have to download the android 6 firmware for your device from the honor official website again and flash it with the same process of the rollback package. If you can't undestand i can try to explain it in italian
Click to expand...
Click to collapse
shashank1320 said:
Unless you flash the rollback package you can't flash older version. Not sure if rollback package for your model os released
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
Ofcourse you need to flash the stock recovery. Are you trying in twrp?
Click to expand...
Click to collapse
yes i tried to flash twrp with fastboot but cant reboot the phone in twrp recovery
crn4 said:
yes i tried to flash twrp with fastboot but cant reboot the phone in twrp recovery
Click to expand...
Click to collapse
Flash stock recovery and try
shashank1320 said:
Flash stock recovery and try
Click to expand...
Click to collapse
yes i tried a lot of times, i have huawei tool, i tried now another time, but with the tool can't reboot in twrp, and with power and+ also
crn4 said:
yes i tried a lot of times, i have huawei tool, i tried now another time, but with the tool can't reboot in twrp, and with power and+ also
Click to expand...
Click to collapse
Are you able to get into the bootloader?
shashank1320 said:
Are you able to get into the bootloader?
Click to expand...
Click to collapse
what do you mean?
in fastboot (- and pw) i have PHONE unlocked and FRP unlocked
crn4 said:
what do you mean?
in fastboot (- and pw) i have PHONE unlocked and FRP unlocked
Click to expand...
Click to collapse
Just flash the stock recovery there in fastboot. And reboot. Shutdown the phone and use dload method
Basically you missed one thing before restoring stock backup. You should have performed a full factory reset using the second recovery and then restored your TWRP backup.
Your device being stuck on Honor screen is because you forgot to enable encryption (that is done by performing a factory wipe through second recovery).
shashank1320 said:
Just flash the stock recovery there in fastboot. And reboot. Shutdown the phone and use dload method
Click to expand...
Click to collapse
I tried flash stock recovery from different firmwares and after try with dload, but dont work, the device freeze e dont wont boot dload, with recovery from b131 firmware (MM) the dload go on but freeze at 5%, now i try with b389 (Nougat) fw, within 15 minutes I tell you the result
hackslash said:
Basically you missed one thing before restoring stock backup. You should have performed a full factory reset using the second recovery and then restored your TWRP backup.
Your device being stuck on Honor screen is because you forgot to enable encryption (that is done by performing a factory wipe through second recovery).
Click to expand...
Click to collapse
Ahhh ok, and now for recover my phone what i need to do ?
now i flashed boot, cust , recovery and system from b389 firmware but nothing, the phone dont boot, dont want to dload, i dont know what to do....
crn4 said:
Ahhh ok, and now for recover my phone what i need to do ?
Click to expand...
Click to collapse
Follow my guide here https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
Before you do it, flash stock Nougat recovery (if you were on EMUI 5) and perform a factory reset. Then flash TWRP again through Fastboot.
Use the TWRP method since you are unable to boot to EMUI. Chose any firmware you want, whether it be Marshmallow or Nougat.
hackslash said:
Follow my guide here https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306
Before you do it, flash stock Nougat recovery (if you were on EMUI 5) and perform a factory reset. Then flash TWRP again through Fastboot.
Use the TWRP method since you are unable to boot to EMUI. Chose any firmware you want, whether it be Marshmallow or Nougat.
Click to expand...
Click to collapse
i flashed stock recovery from you guide but i cant boot in recovery, i flashed different recoverys, from MM to Nougat but nothing i think this is bootloader problem
edit:
in fastboot i see this
ap_s_abnormal na
what is the signification?
crn4 said:
i flashed stock recovery from you guide but i cant boot in recovery, i flashed different recoverys, from MM to Nougat but nothing i think this is bootloader problem
edit:
in fastboot i see this
ap_s_abnormal na
what is the signification?
Click to expand...
Click to collapse
Are you following the steps exactly as mentioned?
You need to flash TWRP first then setup your device to install the firmware. Read the TWRP section again and follow it exactly as mentioned.
Nothing to worry about that Fastboot status. It is normal.
SOLVED!!!!!! thanks at all people, and very sorry for my English,
i relock end unlock boot loader many times and i flash every is flashable from firmware b131 (boot, system......) and whola!!!! the system dont boot but the dload after this has been restored to work, now i update to last fw and root and dont touch more nothing =D
crn4 said:
SOLVED!!!!!! thanks at all people, and very sorry for my English,
i relock end unlock boot loader many times and i flash every is flashable from firmware b131 (boot, system......) and whola!!!! the system dont boot but the dload after this has been restored to work, now i update to last fw and root and dont touch more nothing =D
Click to expand...
Click to collapse
Damn. I forgot you could simply flash files from Fastboot.
In the future only flash system, cust, vendor, boot and recovery. Do not attempt to flash any other file.
Still, if you want to update to the latest OTA, my guide is always there to help you out.
hackslash said:
Damn. I forgot you could simply flash files from Fastboot.
In the future only flash system, cust, vendor, boot and recovery. Do not attempt to flash any other file.
Still, if you want to update to the latest OTA, my guide is always there to help you out.
Click to expand...
Click to collapse
now i have another problem, i tried to update with stock updator, but from 6 to 7 go wrong, device boot but dont work right, the keyboard dont exist and other lags, try to factory reset but error. after this i flash twrp and format data but see this : failed to mount /cust /system /data; repair or change file system do the same.
if i flash with dload b131 the phone freeze on honor screen
Hello, today while trying to get back to stock i wierdly bircked my honor 8
I flashed the stock recovery and stock boot img
Then i flashed a rollback package and a marshmallow package which i used for this same thing before.
Now the phone didnt start for a solid 30 minutes and ive decided to reflash the rollback and marshmallow package, but after i flashed the rollback got stuck at the boot logo, not even the stock bootanimation showing up.
The phone doesnt reboot neither in any of the recoveries nor in bootloader.
Any help would be appreciated.
Stephen
Okay so after all of this i managed to reboot to bootloader and get my hands on one of my previous unlock codes. So now ive got an unlocked bootoader, but after fashing twrp the phone is stuck at the 'your device is booting now' when im trying to get in it
I thing you have flashed the wrong TWRP, check for the latest version or at least the one for your build
uh well, hello there again.
i've tried to do the dload method which failed(i used lots of versions tho none worked)
and i've tried flashing marshmallow twrp, which at the moment, well, it cannot mount anything. no partition can get mounted.
Does any of you guys have an idea of what i could try?
thanks in advance
Does it mean that you have access to TWRP ? if TWRP cannot mount a partition, go into mount section, tick system, data, boot, vendor and then reboot to TWRP again. Then try your previous operation. If it cannot mount data, go into wipe, advanced wipe, and click on format data, then restart TWRP and try again
seems like i somehow broke the partition table, cause it shows every storage as 0 mb and mounting isn't available, cant tick the option. Looks like i will have to find some service center to repair it by my own cost, by the end of the month. Though im giving it around the 25th so i got some more time till then, so maybe i find some solution to this problem.
Hey, so I managed to make the phone work again.
I have flashed boot cust recovery recovery2 and system from the italian marshmallow firmware, then I flashed that same firmware using dload method(tho it failed at 99%)
ØG_SQUAÐ said:
Hey, so I managed to make the phone work again.
I have flashed boot cust recovery recovery2 and system from the italian marshmallow firmware, then I flashed that same firmware using dload method(tho it failed at 99%)
Click to expand...
Click to collapse
You tried only once? Maybe you should now try to flash TWRP recovery and restore a backup made by TWRP. I can provide you one but for FRD-L09, not another. Another method would be to flash the rollback package and then retry flashing an EMUI 4.X ROM (dload method for both), hope you'll figure it out
I think i expressed myself wrong.
That was how i got the phone to work.
Oh lol I misunderstood because of the "it failed at 99%" and I thought the phone wasn't rebooting , no matter I'm glad you succeeded
Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: http://pro-teammt.ru/firmware-database/ Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
you can enter in recovery mode true?
try rebrand your device to stock and download the stock rom to flash via HwOTA or dload.
Can boot only to stock recovery, dload and fastboot. As I said, I rebranded to C432 and did it successfully and installed ROM for this version. I tried flashing both Nougat I used to rebrand and Oreo, both crash at 5% when flashing via dload, HwOTA doesn't work as it flashes TWRP you have to boot into, and I can't enter TWRP because I get Func NO 11 and 2 (recovery image load failed!). I tried 2 different TWRPs, this one from HwOTA and Azan Mughal's version. Neither of them works. Nougat versions don't even flash properly, which is normal because I "have" Oreo
Well, I might just say that this is the toughest phone I have ever been modding. I have just noticed that plugging the phone to charger also makes it enter ERROR MODE, which is also normal in this situation as boot image fails to load.
Just thinking... Might it be that recovery and boot partitions are somehow unformatted? I have no other idea why would recovery boot fail when installed. But on the other hand if it was unformatted it would either format it properly or not install at all, right?
EDIT: Tried to erase recovery but "Command not allowed".
I've got the exact same problem except dload because I don't know how to do that.
dload works with emui 4.x
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
One click away from pushing all the files from UPDATE.APP from stock Oreo through Fastboot, is it safe enough? I mean, what if, for example, fastboot.iso fails to write or is corrupted, completely bricked phone?
Never been so scared modifying a phone, this one is so tough to mod and soft at once...
Can't boot to system, recovery, installing through dload crashes at 5%
i am in same problem plz developers do some work on these issues of this device to get back our devices thanks.
i have tried many mehods (dload, update. app, update. zip etc...... 1 different problem i got is when fladhing boot. img or recovery. img using cmd fastboot flash boot boot. img
failed remote; partition get size error.
---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------
SevenUp9 said:
It should always work. It's there for a reason, isn't it?
I might have discovered why am I getting boot and recovery failures. Obviously having Oreo there are no boot and recovery partitions but recovery_ramdisk and I think kernel (notsure) instead. I only have a question how do I repartition mobile device? There must be a way, right?
Like MTK-based devices have SP Flash Tool.
Click to expand...
Click to collapse
keep searchig
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
SevenUp9 said:
@BaBa Yoga, you have Oreo, right? Try installing proper TWRP for 8.0 then and flash it as recovery_ramdisk instead, because it's how do partitions on Oreo look like. But I doubt it changes anything and makes your phone alive again.
Click to expand...
Click to collapse
yes oreo.... i am still trying twrps of azan mughal and other twrp for my device but now when i install custom recovery {fastboot flash recovery_ramdisk recovery. img}
it shows ok but when i reboot device in recovery mode there is no twrp recovery....... only stock recovery
---------- Post added at 10:02 PM ---------- Previous post was at 09:55 PM ----------
SevenUp9 said:
FIXED IT, FIXED IT!!! Reflashed kernel and it works. Guys up here, you might want to try this out. As I thought, Magisk must have messed up with my boot file.
Adding solution to the main post.
Click to expand...
Click to collapse
great bro....
plz share info here how to reflash kernal
@BaBa Yoga, I posted simple walkthrough in the first post, if you ever need explanation just ask here, I'll try to be more detailic then. Good luck unbricking your phone bro :victory:
SevenUp9 said:
Hello,
I recently got my new Mate 10 Lite and wanted to debrand it, update to Oreo, root and install useful Magisk plugins. Everything went fine and I got my phone debranded from C738 to C432, then I updated to Oreo B330 and tried to root. Couldn't succeed with dry Magisk 16.6 install, so I installed 16.0. Decided to give 16.6 a shot one more time but the story went the same, no 16.6 was installed and Magisk Manager had weird, arabic-like layout (inverted), so I wanted to patch boot image with 16.0 once again in order to clear all the "leftovers" 16.6 could leave. Unfortunately, after this operation my phone got softbricked, constantly entering ERROR MODE trying to boot both system and recovery, getting respectively Func NO 10 and 2 (boot image load failed!) and Func NO 11 and 2 (recovery image load failed!). I hoped that maybe I could just recover via TWRP installing it once again, but, unfortunately, it wasn't a thing and I couldn't boot anyway. I was, of course, installing Mate 10 Lite Oreo version of TWRP. HwOTA 8 doesn't help as well. dload update leaves me with crash at 5%. Any hopes for my baby, or only locking a bootloader and sending on warranty will do (if they even accept it)?
Thank you in advance,
Seven-
EDIT: Fixed. Just had to reflash kernel.img. As simple as that. Seems much more harder, doesn't it?
So here's a quick solution:
1. Go here: Download Firmware Finder, search for Oreo ROM for your specific phone model and codename
2. Find update.zip. Unzip it and put UPDATE.APP to Huawei Update Extractor
3. Extract kernel.img and flash it via fastboot - "fastboot flash kernel kernel.img"
4. Reboot, should work from now.
This is solution for Oreo as I think it's a problem specific for Oreo because this partitioning system, but if you experience such problem with Nougat, download Nougat ROM and change all "kernel" words to "boot".
Hope you have a nice day, I'm glad that I might have helped a few of fellow Mate 10 Lite users
Click to expand...
Click to collapse
bro i did not find firmware for my region i. e RNE L21 C185..... I FOUND DOME FIRMWARES on other sites one of thek i extract update. app using huawei updates extractor but there is no kernal.img file..... i found i. gs of boot, system, recovery, cust etc but no kernal. img what i do.....
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
http://pro-teammt.ru/firmware-database/?firmware_model=rne-l21c185B3 - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
SevenUp9 said:
You downloaded Nougat then, and you have to download Oreo that ends with B3xx, in your case then it will be RNE-L21C185B3xx There must be Oreo for C185, I know that because I was looking at C185 too when I was rebranding but then I noticed that C432 is what I should install for my region.
[m/?firmware_model=rne-l21c185B3[/url] - these are all the official Oreo builds for your specific region. I think all of them should do, I am certain that all the kernels in these packages are similar. Eventually you can just flash another one later
Click to expand...
Click to collapse
should i download OTA-MF or FULLOTA-MF?
I Hope i could find kernal file now....
i am downloading FULLOTA-MF thanks to provide me firmware list of my region
thanks sevenup9 for getting back my device out of that problem i flash the kernel successfully wnd get back my twrp as well now what next..???????? thanks again
---------- Post added at 06:54 AM ---------- Previous post was at 06:01 AM ----------
i flashed kernel. img, cust. img, system. img and then reboot now i have twrp but still in bootloop what next
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
SevenUp9 said:
Yeah, good that you downloaded FullOTA, as it's a full system image. I assume there is no system.img or kernel.img in OTA package at all.
Since you have TWRP now but stuck in bootloop, try to wipe data and cache and try to boot again. If you don't succeed, then maybe try getting all of the 3 zips from FullOTA package on SD card (or USB stick if you have a USB OTG cable) and flash them via TWRP, starting from "update.zip". Should work just fine. Maybe your phone got more partitions messed up, but that should be recoverable as you have a good base being able to boot into TWRP
Click to expand...
Click to collapse
i did usb mathed as well but when flash update. zip via twrp error 9 shows
---------- Post added at 10:10 AM ---------- Previous post was at 10:06 AM ----------
then usi g fastboot i flash recovery_ramdisk kernel cust system ramdisk all these images..... now reboot and i lost twrp and it replaced with stock recovery.... in stock recovery i wiped cache... done... wipe data and factory reset..... stuck at 0% after 10 minutes... plz bro
---------- Post added at 10:12 AM ---------- Previous post was at 10:10 AM ----------
i didn't lock bootloader yet... i keep it still unlock