I really need help on this issue.
It got into a bootloop and the only thing available is fastboot. No recovery or erecovery. This happened when I was at B170 with unlock bootloader and un-rooted on my L01.
Since this, I´ve flashed
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
using Update.app from B100, B121 and B130. No erros with any of these.
I´ve read all the threads about similar problems and used other solutions like:
Change the order of fastboot flash;
Use Multitool-unbrick
Flash TWRP and oficial recovery with multitool but none worked
Remove sim tray
Connect fastboot to Hisuite, but the PC detects the phone, as it plays a sound, but the Hisuite says no phone is connected
Right now my phone is on at fastboot, because I cant even turn it off. It just restarts, vibes, shows Honor screen and restarts after a few seconds.
I really appreciate any help on this.
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
zinko_pt said:
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
Click to expand...
Click to collapse
Hi !
A few months ago I unlocked my bootloader in order to root the phone. Last month I decided that I no longer needed root, so I flashed stock recovery and stock ROM. I updated yesterday to B180 without problem. You don't need to re-lock bootloader. It can stay unlocked without affecting the phone behaviour.
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
Hi man, can you explain it more clearly pls? Having same problem even masters keeping silent,3 of them couldn't fix it.
---------- Post added at 06:44 AM ---------- Previous post was at 06:28 AM ----------
zinko_pt said:
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
Click to expand...
Click to collapse
Hi Zinko
It seems to me you have a great experience fixing that type of problem,please share with me as well,I have Huawei Mate 7 and it's rebooting only after trying to upgrade to Marshmallow.
As Sideness said for sure it's due to a bad recovery and boot partition flashed.In my case it's most probably "boot partition".
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
God thank you so much, 4 days i'm struggling with my Honor and now i flash the boot and recovery from the 170 update and IT BOOTS !
Thank you so much.
Now i just had to update to 170 (i was in 121) via OTA and the updates starts and ends properly (first time in big time).
Main thing to understand is that you don't need a matching system.img, just an proper boot and recovery to flash. (if anyone is bricked to hell just like i was)
Demeth said:
God thank you so much, 4 days i'm struggling with my Honor and now i flash the boot and recovery from the 170 update and IT BOOTS !
Thank you so much.
Now i just had to update to 170 (i was in 121) via OTA and the updates starts and ends properly (first time in big time).
Main thing to understand is that you don't need a matching system.img, just an proper boot and recovery to flash. (if anyone is bricked to hell just like i was)
Click to expand...
Click to collapse
I guess if you try to update from B170 to B313 it will mess the recovery.
To fix this, it is required to re-flash the recovery from B170, AND THEN go back to B121. After that it is up to you to go through B140 and jump to B313 or follow the Lollipop path until B180.
Im stuck with the same issue. I had trwp + root installed, the 180 update came, i derooted the device, installed 313 official recovery- rebooted- and installed the update. After this the phone would not boot again.
I have tried everything, and if i choose the B170 recovery from multi tool, i come to the "Huawei software installing" but it stops at 90%.... What can i do to fix this? are there any way to flash a stock rom with TWRP?
---------- Post added at 07:41 PM ---------- Previous post was at 06:59 PM ----------
flashing recovery.img and boot.img from the update.zip from (B170 to B180) update file worked! the phone starts on version b130! but im struggeling to update the phone any further? what do do?
leholtet said:
Im stuck with the same issue. I had trwp + root installed, the 180 update came, i derooted the device, installed 313 official recovery- rebooted- and installed the update. After this the phone would not boot again.
I have tried everything, and if i choose the B170 recovery from multi tool, i come to the "Huawei software installing" but it stops at 90%.... What can i do to fix this? are there any way to flash a stock rom with TWRP?
---------- Post added at 07:41 PM ---------- Previous post was at 06:59 PM ----------
flashing recovery.img and boot.img from the update.zip from (B170 to B180) update file worked! the phone starts on version b130! but im struggeling to update the phone any further? what do do?
Click to expand...
Click to collapse
Flash a complete B121 and then go all the way untill B180. The updates will show automatically, as you will have only to choose to update.
Related
I am in bootloop and cannot power off phone. I have tried to fastboot recovery, boot, cust, cache, system, userdata from B121. Still impossible to power off the phone.
Did you try to go back to B100? Your file could be corrupted :/
Envoyé de mon PLK-L01 en utilisant Tapatalk
Sideness said:
Did you try to go back to B100? Your file could be corrupted :/
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
No, not yet. I cannot enter Recovery. I can enter in Bootloader only. There is no way to go into Recovery from Bootloader without powering off the phone.
If you can access the bootloader, you can repair your phone.
Try the step 5 from this post :
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
You must have already tried with B121. But try with other versions like B100. Be careful to flash everything (System, recovery, cust, cache, ...).
If it stlll doesn't work, I don't have anything left, but someone else might ! Good luck
Sideness said:
If you can access the bootloader, you can repair your phone.
Try the step 5 from this post :
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
You must have already tried with B121. But try with other versions like B100. Be careful to flash everything (System, recovery, cust, cache, ...).
If it stlll doesn't work, I don't have anything left, but someone else might ! Good luck
Click to expand...
Click to collapse
I am aware of the thread you mention, already tried everything in there. I left the phone overnight in Bootloader to drain battery, which happened, but after connecting charger bootloop remains, I still cannot power off the phone and reach Recovery. The only partition I did not rewrite is /data.
How to do it from fastboot? If I rewrite /data, does it rewrite also phone /sdcard?
UPDATE: getting tools to open phone and remove battery, there is no other way to brake bootloop.
flash TWRP and there is a poweroff option in [Reboot]
sminki said:
flash TWRP and there is a poweroff option in [Reboot]
Click to expand...
Click to collapse
did not work, I could not go to TWRP. As I wrote in separate thread, now I am in B130 with B170 BOOT and RECOVERY. I have tried to reflash TWRP, but is no coming up.
I also do not like small space on SDCARD, total available (root / plus local /sdcard) is only 3GB
were you on B140 when you applied the 170? was it the french B170 or the Indian B170? (different phones)
170 patches those "blackbox" partitons, which could cause earlier kernels to suffer
I haven't moved from 140. people (in general) are just flashing anything posted it seems and for no good reason...
B121 works with B170 bootloader/recovery, but not with B121 bootloader/recovery
at http://www.android-hilfe.de/thema/honor-7-downgrade-von-b170-auf-b121-loesungsfindung.742330/ we discussed about quite the same problem.
the solution can be found in post #20.
if you flash b121 system and b170 boot/recovery your system should boot and you should be able to enter recovery by power & vol+ as well as force upgrade by power & vol+/-
you have to put the update.app from the 313>121 downgrade packag on your sd-card or internal memory (dload folder) and start the update process. the update will fail at 95%, but the system will boot and the build-number is B300.
after that you have to copy the update.app from the full b121 to your sd-card/internal memory and start the update process. update will reboot at 100% and your phone is back to stock b121
sminki said:
were you on B140 when you applied the 170? was it the french B170 or the Indian B170? (different phones)
170 patches those "blackbox" partitons, which could cause earlier kernels to suffer
I haven't moved from 140. people (in general) are just flashing anything posted it seems and for no good reason...
Click to expand...
Click to collapse
Exactly, I was on B140 and applied French B170, but forgot to unroot, I have returned just the recovery, and then the hell on earth started
bamserl said:
B121 works with B170 bootloader/recovery, but not with B121 bootloader/recovery
at http://www.android-hilfe.de/thema/honor-7-downgrade-von-b170-auf-b121-loesungsfindung.742330/ we discussed about quite the same problem.
the solution can be found in post #20.
if you flash b121 system and b170 boot/recovery your system should boot and you should be able to enter recovery by power & vol+ as well as force upgrade by power & vol+/-
you have to put the update.app from the 313>121 downgrade packag on your sd-card or internal memory (dload folder) and start the update process. the update will fail at 95%, but the system will boot and the build-number is B300.
after that you have to copy the update.app from the full b121 to your sd-card/internal memory and start the update process. update will reboot at 100% and your phone is back to stock b121
Click to expand...
Click to collapse
My recovery story was like this:
first B130 from bootloader (all partitions: boot, system, recovery, cust, cache, userdata), disconnecting USB and manual reboot to bootloader and then fastboot partitions BOOT and RECOVERY from B170; reboot and I was out of bootloop; however the root and internal SDCARD was only 3 GB instead of normal 10 GB, so I have updated complete UPDATE.APP (B122) from EMUI placing it in external SDCARD in /dload; then factory reset from stock recovery and the I have now 10 GB total space;
I did not need the B313, however I have noticed that boot and recovery partitions from B313 stopped the short-period bootloop, it just got stuck at boot logo; in this config it allowed me to go to stock recovery GUI and once left there to discharge the battery, the phone finally powered off itself and once reconnected to charger it did not start, it has started to recharge battery
problem
Hi, I have the same problem!
Wholen said:
Hi, I have the same problem!
Click to expand...
Click to collapse
Then try the same cure: fastboot 121 partitions (see above), then fastboot BOOT and RECOVERY from B170 and you are out of booloop.
the problem is , no fastboot no recovery. I tried to press the 2 volume button + power , and the quick button in any combination, but nothing happens.
---------- Post added at 09:17 PM ---------- Previous post was at 09:16 PM ----------
and i updated from b140--- to b313
Hi there, same problem here as FearFac, exactly the same
My PLK_L01 operate only in fastboot mode, and B170 (boot + recovery) and B121 (system, cust) did not repair anything, still cant go in recovery mode :/
Wholen said:
the problem is , no fastboot no recovery. I tried to press the 2 volume button + power , and the quick button in any combination, but nothing happens.
---------- Post added at 09:17 PM ---------- Previous post was at 09:16 PM ----------
and i updated from b140--- to b313
Click to expand...
Click to collapse
you can enter fb by only pressing vol- and connecting your phone to your pc.
the method by flashing system 121 und boot/recovery 170 was found suitable for peple who tried to upgrade from 121/140 > 170.
if you have tried to upgrade from 140>313, it could be worth trying to use boot/recovery from 313 instead of 170.
the 3gb space is a result from flashing userdata.img by fastboot. you also can resolve this problem with a factory reset.
Finally, after battery has left its last % of charge, phone has power off and I was able to boot in Update mode and it works as described !
Now I booted in B121 and it works !
FabienZE said:
Finally, after battery has left its last % of charge, phone has power off and I was able to boot in Update mode and it works as described !
Now I booted in B121 and it works !
Click to expand...
Click to collapse
Great, you can smile again.
FearFac said:
Great, you can smile again.
Click to expand...
Click to collapse
Yes I do ! But I can't update to B140 for now, it simply fails. Tomorrow, I will reflash complete B121 update ?
FabienZE said:
Yes I do ! But I can't update to B140 for now, it simply fails. Tomorrow, I will reflash complete B121 update
Click to expand...
Click to collapse
Yes, complete reflash is a must, including factory reset from RECOVERY, this will delete USERDATA including local SDCARD
Hi,
Today i received a notification on my L22 to update to Marshmallow (310).
But when it reboots into recovery (stock), it says system update failed.
Note:
I have rooted my phone and installed custom rom before. But i used to get back to stock (both rom and recovery) with a TWRP restore. This has worked with all the previous updates of Lollipop (e.g. 130 to 150), but its not working with Marshmallow.
Can someone please help!!.
Can someone please help. I hope this is a beta version. Actually I had opted for the beta previously.
there are no restoration files zips for MM yet, alternatively, you can flash TWRP back via adb and restore your back up. else, follow the steps in thread below....good luck!
http://forum.xda-developers.com/honor-5x/help/bricked-honor-5x-t3328308
Thank you @nandakalyan @Arobase40 for the information.
I can check with them. But when i tried to login to their community, for some reason, my login credentials weren't recognized.
As an update, I tried the following
I downloaded the lollipop 150 firmware and flashed the BOOT, RECOVERY, SYSTEM and CUST image files. But I received REMOTE: COMMAND NOT ALLOWED error while flashing CUST. I even tried installing the USB/ADB drivers again. Still no luck.
Then i tried the update. Still the same error.
Again i followed step 1, then relocked the bootloader (successfully). But still got the same error. (Because i read somewhere that it could be due to modified firmware)
Looks like some issue with the package. So i might have to get back to them.
I will post the update once i get the update from them. Thank you very much guys.
Arobase40 said:
The CUST image file can't be flashed !
But I saw someone was able to rebuild the /Cust folder and its content but I'm too lazy to do the search...
It's in the Honor 5x thread.
Click to expand...
Click to collapse
That is correct, cust.img can't be flashed through ADB, I have had this issue too.
@mani0608
The only best way is to flash stock recovery, create a dload folder in the root of the sd-card, place the update.app (original firmware file) in it, boot into download mode (power + vol up + vol down) and let the whole factory image be flashed.
nandakalyan said:
That is correct, cust.img can't be flashed through ADB, I have had this issue too.
@mani0608
The only best way is to flash stock recovery, create a dload folder in the root of the sd-card, place the update.app (original firmware file) in it, boot into download mode (power + vol up + vol down) and let the whole factory image be flashed.
Click to expand...
Click to collapse
I followed this and then tried the OTA and voila it worked!!
mani0608 said:
I followed this and then tried the OTA and voila it worked!!
Click to expand...
Click to collapse
Super....congrats! Glad it worked
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
it seems like u dint have an proper boot.img
try flashing ftf
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
macjagger said:
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
Click to expand...
Click to collapse
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
altvolt74 said:
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
Click to expand...
Click to collapse
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
macjagger said:
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
try flash e5823 lates nougat e5823_32.3.A.0.376_R2R_AU instead of (e5803) firmware
also to enter flash the rom using kernel partition
off phone . ...hold vol down and power release power when see sony keep holding volume down all the way till recovery
format system
flash zip
i will update intrustions since theres people having issues while flashing an rom using e5823 on e5803 or probably ur flashing it wrong using the recovery that is integrated to the boot.img
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
also sorry for late reply been cooking xperia xz rom to our z5 compact also finish is uploading it now
I'll give it a try in a couple of days. Need my phone as a daily driver currently. Appreciate your help
macjagger said:
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
To me it seems like you are just flashing twrp to the wrong partition.
How do you flash it?
You have to flash it with command:
Fastboot flash recovery "twrp.img"
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
oh hai
just wanted to link you in on this:
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71433741#post71433741
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
macjagger said:
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
Click to expand...
Click to collapse
Have you tried to do a restore yet?
Just wanted to ask so I can isolate twrp with rootkernel
Hi,
Ok, so I'm scratching my head now.
I had Project Treble running fine on my phone with Magisk but then it stopped booting.
I tried re-flashing and still had the booting issues.
I then tried HuRUpdater and I think its done something to the recovery.
I can't use TWRP 3.2.1 (0.1, 0.2 nor 0.3) The phone complains that recovery cant load.
The only recovery I can make work is TWRP-3.1.1-0 and -1, however from them I cannot use HuRUpdater due to the MagicZip error with the recovery.
Can anyone point me in the direction of TWRP-3.1.1 with the magiczip issue corrected seeing as I cant use the 3.2.1's.
I have tried a plethora of things, from the update.app (fails to install every time on various versions).
I have tried extracting the update.app and flashing the recovery.img, boot.img and system.img via fastboot (doesnt even boot, screen goes black and restarts).
The bootloader is unlocked, the FRP is unlocked. I have tried running the unlock command and I just get "bootloader already unlocked"
any pointers or things to try??
You're somehow back on nougat partitioning scheme ?
If so, flash using the service repair firmware for your region.
---------- Post added at 00:36 ---------- Previous post was at 00:34 ----------
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
You are a legend. Thanks so much for this, its now working so I have handed it down to my Son and got myself the P20 Pro
Here is my problem,
I have a BLN-L29, now:
running on Lineage OS Beta 4
unlocked bootloader
TWRP
Now my mission is to revert back to stock EMUI Firmware.
Apparently, many of you guys refer to this thread and this thread for solution.
However, i still cant understand the steps. Especially this:
Download Update ZIP
A. Get ROM update link through hwmt.ru. Click "filelist.xml".
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA from previous step. Example ALP-L29 8.0.0.115 (C636) filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "ALP-L29_hw_spcseas/update_ALP-L29_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip"
I have downloaded three zip for BLA-L29C636b139 (8.0.0.139) that contains:
update.zip
BLA-L29_hw-spcseas/update_full_BLA0L29_hw_spcseas.zip
public/ update_data_full_public.zip
I hope there are the correct one needed to restore my phone back to stock.
Can anyone guide me please?
Hi, I was at LineageOS too.
I didn't need TWRP flash to install it.
I returned to Stock without problems, so my advice is to follow the next steps, but remember, it is you who decides to do it, I only offer you a solution that should NOT make things worse.
1. Stock recovery flashes from the version you were before Lineage, NONE other recovery version.
2. You go into recovery and do a Wipe Cache, and then a Factory Reset.
3. You restart Fastboot, and Syste.img flashes the version before Lineage.
4 Restart in recovery, and Reset Factory again, restart, and you're good to go.
To find the recovery and the Systen.img you should download the version that had your phone, download it, the full version, no other, unzip it, and with Huawei update Extractor, you get those two files that I told you.
I repeat, this should work if or if I'm not responsible for anything.
And above all, make sure first that you have the OEM Unlock, and the Bootloader open
Good luck
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
rey_lagarto said:
Hi, I was at LineageOS too.
I didn't need TWRP flash to install it.
I returned to Stock without problems, so my advice is to follow the next steps, but remember, it is you who decides to do it, I only offer you a solution that should NOT make things worse.
1. Stock recovery flashes from the version you were before Lineage, NONE other recovery version.
2. You go into recovery and do a Wipe Cache, and then a Factory Reset.
3. You restart Fastboot, and Syste.img flashes the version before Lineage.
4 Restart in recovery, and Reset Factory again, restart, and you're good to go.
To find the recovery and the Systen.img you should download the version that had your phone, download it, the full version, no other, unzip it, and with Huawei update Extractor, you get those two files that I told you.
I repeat, this should work if or if I'm not responsible for anything.
And above all, make sure first that you have the OEM Unlock, and the Bootloader open
Good luck
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
Click to expand...
Click to collapse
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
babadaba said:
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
Click to expand...
Click to collapse
latest update,
after the phone stuck at bootlooping,
i "fastboot flash system" the old lineage OS system img
now my phone is still in custom ROM.
back to square 1.
babadaba said:
Thank you for your reply,
This is what i do:
downloaded a FULLOTA update for my phone
extracted system.img and recovery.img from UPDATE.APP using huawei update extractor
flash recovery using this command fastboot flash recovery_ramdisk recovery.img
factory reset
flash system.img using this comman fastboot flash system system.img
factory reset (lowlevel)
now it bootlooping
Click to expand...
Click to collapse
If, your phone logs into bootloop, logs back into recovery, an option should appear to download the latest version available to you, it installs itself.
Anyway, if you have a bootloop problem, the terminal takes you to that step by itself, that's what happened to me when I installed Xposed Framework.
In any case, the first step should have been to do a Factory reset. I hope you can work it out.
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------
babadaba said:
latest update,
after the phone stuck at bootlooping,
i "fastboot flash system" the old lineage OS system img
now my phone is still in custom ROM.
back to square 1.
Click to expand...
Click to collapse
Okay, I didn't read that last one. You're back at TWRP? I hope not.
You should check to see if you have any objections to entering Recovery Stock. In case of no problems, you can try a Factory Reset again, and Wipe Cache, then just flash System.img, and again Factory Reset.
Those, and NOT others, are the steps I took, and I had no problems.
Perhaps as it is a different process from your move to Custom, it must also be different to return to Stock.
Translated with www.DeepL.com/Translator
Enviado desde mi BLA-L29 mediante Tapatalk
Hey, have you made any progress?
Greetings.
Enviado desde mi BLA-L29 mediante Tapatalk