I rooted my p10 lite device and I tried to decrypt data using this method https://forum.xda-developers.com/showpost.php?p=72556843&postcount=6
I couldnt back the data up. So I wiped data and flashed the link's latest zip.
Since then, I couldn't boot. So, I flashed stefanwe92's twrp backup.
Then it seemed to start the OS correctly , however it shows only a navbar and I couldn't operate anymore.
Is there a solution? Or can only fix this using DC-Phoenix or Funkyhuawei?
Sorry for my English. Thank you.
tuvin5f0 said:
I rooted my p10 lite device and I tried to decrypt data using this method https://forum.xda-developers.com/showpost.php?p=72556843&postcount=6
I couldnt back the data up. So I wiped data and flashed the link's latest zip.
Since then, I couldn't boot. So, I flashed stefanwe92's twrp backup.
Then it seemed to start the OS correctly , however it shows only a navbar and I couldn't operate anymore.
Is there a solution? Or can only fix this using DC-Phoenix or Funkyhuawei?
Sorry for my English. Thank you.
Click to expand...
Click to collapse
Yes you can use the paid services but before you can try to flash hw_data and public in twrp for the firmware you are on ,they should fix ur phone.
Use firmware finder to download those files.
Hi people, i bricked my huawei p10 lite was-lx2. Unlock and twrp. anyone have the firmware? I google it already but does not found any. WAS-LX2C636B130 4gbram 32gbstorage dual-sim malaysia. Or if there is the way i can debrand it with "dual-sim and support my telco" firmware. tell me if its possible. Thanks!
I'm on EVA-L09C09 and would like to go to L09C432 so I can use the RROS ROM. Is it possible to debrand it without downgrading to 6.x? (I have an unlocked bootloader)
Thank you!
I was with a situation very similar and did it.
I was on EVA-L09C02B345 and debranded to EVA-L09C432B383 to test OTA Updates and received the EVA-L09C432B386 correctly via System Update and applied it successfully.
The process was not very clean I was with the same problem all tutorials are for android 6.x and none for 7.x, but I risked to follow this one:
https://forum.xda-developers.com/p9/how-to/vdo-guide-how-to-debrand-huawei-phone-t3410045
Of course before, I unlocked bootloader, installed TWRP and rooted, with help of latest topics about the subject, but you already have this.
Now, the problem on that tutorial was after applying the oeminfo and custombin of C432 the phone needs reboot and it was supposed to reboot and do some more actions on the system but when you reboot it enters in a bootloop that sent me to erecovery... At this point I had another problem, because after this I tried to put with dload an original C02 rom and give up, but the original rom on FF available for C02 was from a test branch(I didn't kown) and it didn't have updates and some other things, at this point I din't have updates to receive the latest C02 rom and had to try again for the C432 so I unlocked again and put TWRP and as a desperate measure I installed via TWRP the zip files of C432B383 and despite my beliefs it didn't gave any error, after reboot It booted correctly and phone info was already EVA-L09C432B383 and all working. At fist the OTA update to B386 didn't apear but after a factory data reset it appeared right after initial setup and wifi configuration, downloaded full update and applied successfully.
This was my story, after this I am with the idea that after the problem of oeminfo and custombin I should have gone to TWRP and flash the C432 rom and everything would be ok but I'm not sure if the "test" rom influenced anything on the process...
Hope it helps...
So did it go out of the bootloop after re-unlocking?
WhatWhatInTheRoot said:
So did it go out of the bootloop after re-unlocking?
Click to expand...
Click to collapse
After re-unlock I didn't followed the tutorial I just unlocked bootloader then installed TWRP and on TWRP installed the zip files of the EVA-L09C432B383 firmware.
I assume that the oeminfo and custombin from the tutorial was still in place because I ended up with a L09C432 and not with a crossflashed L09B900, so probably you can't skip the bootloop, but I'm not sure I'm no expert I just risked and got lucky I guess!
It would be nice If someone who really understand this procedure, to tell us what's the appropriate procedure to do this without problems and bootloops...
If you're willing to risk my recipe is this:
1 - unlock bootloader (you already have this)
2 - install twrp (https://forum.xda-developers.com/p9/development/twrp-t3565703)
3 - root (https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258)
4 - follow tutorial until reboot after apply C432 oeminfo and custombin (https://forum.xda-developers.com/p9/how-to/vdo-guide-how-to-debrand-huawei-phone-t3410045)
5 - when the phone boot to e-recovery, don't do anything just reboot it to TWRP
6 - on TWRP install the zip files of EVA-L09C432B386 previously saved on the sdcard
If step 5 and 6 fail try to flash the EVA-L09C432B386 via dload folder on sdcard. If this fails too I don't really know what I did more to solve the problem because at that point I was a bit scared and trying everything...
Don't forget before you do anything make sure you have your original firmware available don't do like me that only had a old test keys firmware available, and do a full nandroid backup on TWRP so you have more options to revert back!!!
Probably it's best to way for a more expert opinion/tutorial...
Thanks, but sounds way too risky, I think I'll wait for a more proper method.
Sorry for bumping, but has anyone found out a solution?
I and mfPPC can't be the only ones with this problem, surely. :/
So long story short I wanted to get root access in order to install an audio mod for my phone, realized it was basically pain in the ass and most of the time it won't work so I want to revert the changes back to where I started (a.k.a. stock recovery, locked bootloader). Also system update doesn't work with TWRP, it just boots into TWRP and doesn't proceed installing the update. I'd like to fix that.
My phone is VTR-L29C432 B360 Oreo 8.0
I flashed this TWRP -> https://forum.xda-developers.com/p10/development/recovery-twrp-3-2-1-0-emui-8-0-4-04-2018-t3773449
Phone hasn't been rooted.
I'm sorry if it looks like I made something dumb but I just want some help. I'd appreciate anything really.
Anyone anything? At least I'd like to revert to stock recovery so I can install B365.
On the other side would installing B365 from FF work fine with TWRP?
Really nobody has a solution? Can't I extract the stock recovery for B360 from somewhere? It's that I'm new with Huawei phone and I'm not sure how everything works here. I used to own Galaxy Y but things were simpler there.
BloodBullet said:
Really nobody has a solution? Can't I extract the stock recovery for B360 from somewhere? It's that I'm new with Huawei phone and I'm not sure how everything works here. I used to own Galaxy Y but things were simpler there.
Click to expand...
Click to collapse
With this guide I update B60 A B 365 I hope it helps you
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
Hey,
I recently rebranded my VTR-L29C185 to VTR-L29C432. After that, I installed the latest Project Treble Resurrection Remix ROM from phh. The device is rooted, bootloader and frp unlocked, and has TWRP 3.2.1 FromFuture (the one for Treble roms) installed.
I made a full backup with TWRP 3.2.1-0 for stock EMUI 8.0 before the rebrand process.
My question is how do I go back to stock but keep the rebranding ? Do I just need to restore the backup without its OEMInfo via TWRP ? Search a VTR-L29C432 ROM and flash it through fastboot ?
The reason I want to go back to stock is mainly because of the many camera functions you cannot use on these roms even after installing the Huawei Camera (or the Google Camera for Kirin, which I recommend for users of these roms) and because of a few freezes and graphical glitches. Apart from that it's a very smooth and stable experience and I didn't face any big issue (gapps and root are working).
I would really appreciate your help. Thank you !
Anyone ?
should be fine to restore just the system image, because treble roms are just system partitions.
DallasCZ said:
should be fine to restore just the system image, because treble roms are just system partitions.
Click to expand...
Click to collapse
So you mean when I restore the backup I only chose System ? And I will keep the rebranding ?
edited because of double post
yes
DallasCZ said:
yes
Click to expand...
Click to collapse
I did it, I'm on stock again now, but strangely it shows me there's an update with the same version as installed. If I try to run the update it reboots to try to install the update (logically) but with the fact I have TWRP installed it doesn't do so.
I also noticed the designs I download (which worked before on stock) do not apply. What does this mean ?
Thanks
Chrisgia said:
I did it, I'm on stock again now, but strangely it shows me there's an update with the same version as installed. If I try to run the update it reboots to try to install the update (logically) but with the fact I have TWRP installed it doesn't do so.
I also noticed the designs I download (which worked before on stock) do not apply. What does this mean ?
Thanks
Click to expand...
Click to collapse
flash stock recovery and let the update to be installed.
DallasCZ said:
flash stock recovery and let the update to be installed.
Click to expand...
Click to collapse
Done. Everything normal again now, thanks !
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...
Same problem and I didn't find any solution yet.
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli
It worked for me mate! Thank you
k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...
jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?
Worked for me too, thanks!
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader
wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.
Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse
whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.