Related
So, I tried to update my P10 (like an idiot) and obviously failed leaving me in a bootloop, I can access fastboot and recovery, but nothing else, I have an unlocked bootloader too, what can I do to solve this? My P10 is the VTR-L09C605B166 variant that I tried to update to the B210 version (Oreo) I just want a real fix I didn't try anything because of the fear of breaking my phone even more, and I don't know if a technician will help me because of my unlocked bootloader and the warnings that appear, please help, thanks in advance.
Are you able to install and boot twrp?
How did you try to update?
For twrp you can use my guide.
You can easily check if you're on Oreo by using fastboot command "fastboot flash recovery_ramdisk TWRP.IMG". If it shows a partition length error, you're still on nougat and need to install a nougat twrp with command "fastboot flash recovery TWRP.IMG".
When TWRP work you can proceed with my guide.
But I need to say: without any warranty.
Everything you do can cause a brick even if it should be safe.
Other solution is to try to relock your bootloader (you need your unlock code!) and try a factory reset or restore with eRecovery - this is the official way and works only if nothing is modified in the system.
BTW: B210 isn't Oreo, I think.
B36(X) are Oreo builds.. You must have downloaded some unreleased software :/
Jannomag said:
Are you able to install and boot twrp?
How did you try to update?
For twrp you can use my guide.
You can easily check if you're on Oreo by using fastboot command "fastboot flash recovery_ramdisk TWRP.IMG". If it shows a partition length error, you're still on nougat and need to install a nougat twrp with command "fastboot flash recovery TWRP.IMG".
When TWRP work you can proceed with my guide.
But I need to say: without any warranty.
Everything you do can cause a brick even if it should be safe.
Other solution is to try to relock your bootloader (you need your unlock code!) and try a factory reset or restore with eRecovery - this is the official way and works only if nothing is modified in the system.
BTW: B210 isn't Oreo, I think.
Click to expand...
Click to collapse
Ok I need help in this part, just installed twrp for nougat, but the version of my phone just shows the OTA update not a FULL OTA, what do I do? And I cant seem to find a Oreo update for my region (C605) does the region matter?
JamesRLS said:
B36(X) are Oreo builds.. You must have downloaded some unreleased software :/
Click to expand...
Click to collapse
Well, f*** and what BXXX are official nougat builds?
This should be the right Oreo version:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2323/g1699/v113112/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...12/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L09_hw_la/update_full_VTR-L09_hw_la.zip
It's VTR-L09C605B321 FullOTA-PV.
Can you enter in eREcovery?
CriticalImpact said:
Well, f*** and what BXXX are official nougat builds?
Click to expand...
Click to collapse
The official oreo builds are B365,363,360
CatalinMAW said:
Can you enter in eREcovery?
Click to expand...
Click to collapse
Yup
Jannomag said:
This should be the right Oreo version:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2323/g1699/v113112/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...12/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L09_hw_la/update_full_VTR-L09_hw_la.zip
It's VTR-L09C605B321 FullOTA-PV.
Click to expand...
Click to collapse
Holy! You're awesome! Im gonna try to unbrick the phone now, I hope it works, either way thanks! really.
Jannomag said:
Are you able to install and boot twrp?
How did you try to update?
For twrp you can use my guide.
You can easily check if you're on Oreo by using fastboot command "fastboot flash recovery_ramdisk TWRP.IMG". If it shows a partition length error, you're still on nougat and need to install a nougat twrp with command "fastboot flash recovery TWRP.IMG".
When TWRP work you can proceed with my guide.
But I need to say: without any warranty.
Everything you do can cause a brick even if it should be safe.
Other solution is to try to relock your bootloader (you need your unlock code!) and try a factory reset or restore with eRecovery - this is the official way and works only if nothing is modified in the system.
BTW: B210 isn't Oreo, I think.
Click to expand...
Click to collapse
It worked!!! Youre just awesome, I really owe you one, thanks, for real <3
Jannomag said:
Are you able to install and boot twrp?
How did you try to update?
For twrp you can use my guide.
You can easily check if you're on Oreo by using fastboot command "fastboot flash recovery_ramdisk TWRP.IMG". If it shows a partition length error, you're still on nougat and need to install a nougat twrp with command "fastboot flash recovery TWRP.IMG".
When TWRP work you can proceed with my guide.
But I need to say: without any warranty.
Everything you do can cause a brick even if it should be safe.
Other solution is to try to relock your bootloader (you need your unlock code!) and try a factory reset or restore with eRecovery - this is the official way and works only if nothing is modified in the system.
BTW: B210 isn't Oreo, I think.
Click to expand...
Click to collapse
Hello, I am in the same situation as the guy above: I can access fastboot and recovery and my phone is unlocked - I have Nougat VKY-L09C432B185...
Can I follow your guide with a Nougat phone?
Thank you
P.S.
I tried to install update.zip via TWRP but I got the "Error 9" error
Roter_Freiherr said:
Hello, I am in the same situation as the guy above: I can access fastboot and recovery and my phone is unlocked - I have Nougat VKY-L09C432B185...
Can I follow your guide with a Nougat phone?
Thank you
P.S.
I tried to install update.zip via TWRP but I got the "Error 9" error
Click to expand...
Click to collapse
You can try it. The recovery within my archives is from VKY, so it should work. The devices are kinda similar. Just download the right firmware for your model (VKY) and region (Cxxx, like C432), and also FullOTA.
It can be possible that my script doesn't work with your phones partitions. If so, please post the TWRP output, then I'm able to rewrite the script for you.
You can do it by yourself if you know the partitions for recovery and recovery on you device.
Hi. I can't access recovery. Phone is completely off. I connect to USB and computer recognizes de phone USB SER. I hard bricked. It happened after I upgraded to oreo version. It shut off and it never turned on again. I tried power +vol. Can't get aceess to recovery just black screen. I appreciate if you can help. Thank you
How many people bricked specifically hardbricked their phone after 2018-04-16 updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if they see we are bunch of people.
Edit: Just comment only if you solved the issue with this tool or any other tool that is not mentioned,here we are seeking help.
reza6d said:
How many people bricked specifically hardbricked their phone after 2018-04-16 noxloader updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if the ysee we are bunch of people.
Click to expand...
Click to collapse
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
ante0 said:
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
Click to expand...
Click to collapse
maybe i recall wrong but after first time seeing these noxloaders,somethings changed,anyway i edited the post.thanks.
My BLA-L29 is still on the black screen and I can not even revert to DC-Phoenix. After upgrading to 138.
Used funky
mikaole said:
Used funky
Click to expand...
Click to collapse
i think your phone was in fastboot or bootloop,we are talking about hardbrick bro,black screen not even charge led in our devices.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
durc12 said:
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
Click to expand...
Click to collapse
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Carnage! said:
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Click to expand...
Click to collapse
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
I see. I only tried flashing the recovery_ramdisk and system.img. I will try it later and I will let you know if it worked.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
durc12 said:
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
Click to expand...
Click to collapse
No, first he has to recover the current OS, and my advise was only for that.
Then he will need to use a TWRP + NoCheck combo, to get back to Oreo.
HuRUpdater can't get you back to Oreo so you guys should stop using that with Pie.
Mate 10 Pro BLA-L09
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
diowil4 said:
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
Click to expand...
Click to collapse
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Pretoriano80 said:
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Click to expand...
Click to collapse
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
diowil4 said:
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Click to expand...
Click to collapse
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Pretoriano80 said:
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Click to expand...
Click to collapse
After flashing It cannot boot to recovery.
diowil4 said:
After flashing It cannot boot to recovery.
Click to expand...
Click to collapse
So you can only boot to fastboot, no matter what?
Pretoriano80 said:
So you can only boot to fastboot, no matter what?
Click to expand...
Click to collapse
Yes.
How to revert back to stock firmware
October 26, 2018
WARNING :do not try to downgrade your device.
For example, if you are on September security patch level (on stock firmware) and rooted your device or installed a custom ROM and if you want to revert back to stock firmware then flash the firmware which have September Or greater then September Security patch level.
As downgrading (flashing firmware of older versions or older security patches) can result in hard bricking of your device.
As in example, if you flash august security patch firmware your device may got bricked and believe me guys you don't want it!!).
If however you flashed downgraded firmware then it's recommended to do not update your device via OTA. Wait for latest stock firmware or update and flash it.
Fastboot adb files or platform tool links given below
Fastboot- https://androiddatahost.com/wp-conte...oot_v1.4.3.zip
Platform tools- https://developer.android.com/studio...ools#downloads
Motorola driver- http://www.motorola.com/getmdmwin
Stock fastboot firmware August security patch- https://mirrors.lolinet.com/firmware...d50_oem.tar.gz
Now sit back and follow these steps
1.install motorola USB driver, fastboot adb files or platform tools or you'll get adb files inside that firmware folder..
2. Extract tar.gz file through winrar in a folder,copy adb files in that same folder
3. Boot your phone to bootloader screen for that power off your device press volume down following by power button..
4. In that extracted folder press shift in your keyboard and right click on the mouse in a blank space you'll get a option called "open windows command here" type 'fastboot devices' to make sure your device is connected
Exit that cmd window and double click on 'flashall'.bat file(it'll available in the folder) sit back and relax it'll flash your stock firmware...
For more enquiries join telegram group of Motorola one power official
https://t.me/MotoOnePower
Now we can update monthly security patches after flashing this above firmware
1.download ota zip https://drive.google.com/file/d/1PUDntncjTNeqgCyzvqCjdCLpNF3ElxZx/view?usp=drivesdk
move or copy update.zip in SD card into root directory...
2.boot into bootloader scroll down to recovery through volume down button--hit power button to enter recovery mode,once you enter you'll see a "no command" massage,don't panic.hold power button and press once volume up.now a new menu will open.
3.navigate the option called update from sdcard(volume down,hit power button to enter)
4.find update.zip and hit power button..sit back and relax it'll take time to complete the update process...??
Hey,
You did a great job bro, but i want to give you a suggestion, plzz add a warning that flash latest stock firmware with latest security patch only, do not try to downgrade your device.
For example, if you are on September security patch level (on stock firmware) and rooted your device or installed a custom ROM and if you want to revert back to stock firmware then flash the firmware which have September Or greater then September Security patch level.
As downgrading (flashing firmware of older versions or older security patches) can result in hard bricking of your device.
As in example, if you flash august security patch firmware your device may got bricked and believe me guys you don't want it!!).
If however you flashed downgraded firmware then it's recommended to do not update your device via OTA. Wait for latest stock firmware or update and flash it.
ADITYA_KUMAR said:
Hey,
You did a great job bro, but i want to give you a suggestion, plzz add a warning that flash latest stock firmware with latest security patch only, do not try to downgrade your device.
For example, if you are on September security patch level (on stock firmware) and rooted your device or installed a custom ROM and if you want to revert back to stock firmware then flash the firmware which have September Or greater then September Security patch level.
As downgrading (flashing firmware of older versions or older security patches) can result in hard bricking of your device.
As in example, if you flash august security patch firmware your device may got bricked and believe me guys you don't want it!!).
If however you flashed downgraded firmware then it's recommended to do not update your device via OTA. Wait for latest stock firmware or update and flash it.
Click to expand...
Click to collapse
Thnx bro.. I'll add it
September security patch firmware available you can follow op's flashing method
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Happy flashing:fingers-crossed::fingers-crossed:
dayask said:
September security patch firmware available you can follow op's flashing method
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Happy flashing:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
can you attach flashing bat file which I can relock boot loader.
tnmsrkr said:
can you attach flashing bat file which I can relock boot loader.
Click to expand...
Click to collapse
Just type after flashing firmware
fastboot oem lock
dayask said:
just type after flashing firmware
fastboot oem lock
Click to expand...
Click to collapse
after the command bootloader hasbeen locked but ,
while sturtup it is showing different os. Error screen.(it looks like unlocked bootloader screen).
tnmsrkr said:
after the command bootloader hasbeen locked but ,
while sturtup it is showing different os. Error screen.(it looks like unlocked bootloader screen).
Click to expand...
Click to collapse
Go this link above as mentioned
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And unlock the bootloader first.
Then install it. After installing the rom, see if it boots. Let it boot the first time.
Then go back to fastboot mode and relock the bootloader.
Don't do both of these at the same time.
Worked for me.
Reference link here: https://www.getdroidtips.com/stock-firmware-moto-one-power/
Look at the 2nd method in this thread.
Good luck.
Time to upgrade PIE
WARNING: (DO NOT DOWNGRADE YOUR DEVICE)
(From Android pie to Oreo)you may face IMEI and RIL issues later..this process will erase all your internal memory..so do take a backup before proceeding...
You can follow earlier process for upgrading to Android pie..
Flashall.bat should be with in your pie firmware folder
Just double click on it and you good to go...
https://mirrors.lolinet.com/firmwar...PT29.74-25_64be_release-keys-cid50_oem.tar.gz
Happy flashing
Credits @erfanoabdi
Doesn't work even after applying OTA update
nitish2706 said:
Go this link above as mentioned
And unlock the bootloader first.
Then install it. After installing the rom, see if it boots. Let it boot the first time.
Then go back to fastboot mode and relock the bootloader.
Don't do both of these at the same time.
Worked for me.
Look at the 2nd method in this thread.
Good luck.
Click to expand...
Click to collapse
I flashed fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After booting, installed OTA update
then fastboot oem lock, Still shows different os error
rahulsharma0810 said:
I flashed fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After booting, installed OTA update
then fastboot oem lock, Still shows different os error
Click to expand...
Click to collapse
facing same problem
need solution for this
One_Hermit said:
facing same problem
need solution for this
Click to expand...
Click to collapse
We are working on it, it's something related with splash screen or boot img.
I already updated to January security update and messed up which caused a bootloop on my device. can anyone point me to a stock ROM which won't brick my phone? I don't care about my data, just want the phone in working condition again.
rahulsharma0810 said:
I flashed fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After booting, installed OTA update
then fastboot oem lock, Still shows different os error
Click to expand...
Click to collapse
Does your device working proper except this error getting update etc.?
Is it possible to downgrade to stock Oreo safely?
Edit: Nevermind. Got it .
JaggedPill said:
Is it possible to downgrade to stock Oreo safely?
Edit: Nevermind. Got it .
Click to expand...
Click to collapse
Not possible I tried it. You will stuck on logo or lost imei
I have stock pie with April security patch and want to revert to oreo. So, does this mean I should use oreo firmware file with April security patch or greater only?
Also should I unlock bootloader for this?
i rooted my phone after unlocking bootloader but i messed up in the process and my phone went to bootloop and then when i relock bootloader it said "your device is untrusted nd wont boot" but somehow i managed now to flash stock rom but when iam booting it is showing in booting screen "your device has downloaded different os" well after that it is booting fine and phone is running also fine .. is this any problem .. will it create any problem ? and how do i update ota updates which comes in future ???\
how to downgrade ?
I am new here can anyone tell me how can i downgrade my motorola one power from android pie to its original oreo 8.0 version.
So, I rooted my device following this https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390, but I cannot update my nokia...
The only thing I did different was that I had to rollback my device (with this guide) to June update, and then proceed accordingly.
When I try to update now, I keep getting an error on the update: "Couldn't update. Installation problem".
Can someone please help me? I am ok with both manual or automatic updates, but I need to update.
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
***
Edit: See my second post.
Also there is magisk uninstall feature, which you can restore the partition to stock and update and then magisk-root the inactive partition (newly installed system).
I have not upraded my phone, yet. That is, I didn't try anything I mentioned here.
Click to expand...
Click to collapse
Dr. Slump said:
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
Click to expand...
Click to collapse
Thanks, I'm in the same situation, unlocked bootloader and rooted on the October patch, do I flash the stock Oct patch and then update via OTA?
Thanks!
vonManstein said:
Thanks, I'm in the same situation, unlocked bootloader and rooted on the October patch, do I flash the stock Oct patch and then update via OTA?
Thanks!
Click to expand...
Click to collapse
That is right. You are welcome.
Also there is magisk uninstall feature, which you can restore the partition to stock and update and then magisk-root the inactive partition (newly installed system).
I have not upraded my phone, yet. That is, I didn't try anything I mentioned here. You may verify the ideas by wandering at some topics like that:
https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390
Dr. Slump said:
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
***
Edit: See my second post.
Click to expand...
Click to collapse
The magisk uninstall have not worked, the same error persists... I'm gonna try the first method you mentioned, and will be back with results, thanks!
Edit: also, could you please provide steps for doing that?
Not sure if supposed to do that through Nokia software, twrp or fastboot.
Thanks again
guideo said:
The magisk uninstall have not worked, the same error persists... I'm gonna try the first method you mentioned, and will be back with results, thanks!
Edit: also, could you please provide steps for doing that?
Not sure if supposed to do that through Nokia software, twrp or fastboot.
Thanks again
Click to expand...
Click to collapse
It is "fastboot flash". It seems OK. This is what I will do if magisk uninstall doesn't work for me. But, again, you should know that I have not tried this yet.
Also, if your plan is to upgrade to pie, AFAIK there is some preliminary problems with it. They are mentioned in relevant topics here. I think it is better to wait for a better version.
Dr. Slump said:
It is "fastboot flash". It seems OK. This is what I will do if magisk uninstall doesn't work for me. But, again, you should know that I have not tried this yet.
Also, if your plan is to upgrade to pie, AFAIK there is some preliminary problems with it. They are mentioned in relevant topics here. I think it is better to wait for a better version.
Click to expand...
Click to collapse
Hi, thanks for the help.
The command fastboot flash boot "june.img" worked, but now I can't turn on my WiFi... It turns on then off again on its own...
Im gonna tinker around a little with it, but probably be back on the 25th or 26th, due to xmas.
Thanks a lot and merry christmas to you
Worked with may patch...
I think that my device was trying to apply the June patch, and so it was in may patch.
Ive installed it and now the update is ongoing.
Gonna try to re-root it after the holidays
I'm not going to apply the pie update, gonna wait for a while.
Thanks a lot man! You saved my device :laugh:
guideo said:
Worked with may patch...
I think that my device was trying to apply the June patch, and so it was in may patch.
Ive installed it and now the update is ongoing.
Gonna try to re-root it after the holidays
I'm not going to apply the pie update, gonna wait for a while.
Thanks a lot man! You saved my device :laugh:
Click to expand...
Click to collapse
I just got to the september update (should have stopped in august), but now I cannot root my device... TWRP wont boot, neither the prerooted september image.
If you have any idea about this, I would really appreciate! Thanks!
guideo said:
I just got to the september update (should have stopped in august), but now I cannot root my device... TWRP wont boot, neither the prerooted september image.
If you have any idea about this, I would really appreciate! Thanks!
Click to expand...
Click to collapse
Thanks, marry christmas to you, too. TWRP won't work because there isn't a dedicated recovery partition anymore, it was patched into boot partition and wiped out with the flashing
If you are trying the prerooted boot image with "fastboot boot", it is broken after the august update. If not, maybe it is better to download the stock image to /sdcard and patch it with your latest magisk, later upload it to computer and "fastboot flash" it.
So guys any way to root official pie with december security patch?
nabil427 said:
So guys any way to root official pie with december security patch?
Click to expand...
Click to collapse
You can find a twrp-prepatched boot image for Pie + December Patch here: https://cloud.tmsp.io/s/nb1?path=/Boot Images/2018-12
Enter download mode and use fastboot to flash it into your active boot partition (either boot_a or boot_b, depending on the output of "fastboot getvar current-slot").
Then boot into recovery mode (using adb reboot recovery, or by shutting the phone down and pressing volume up while connecting it to the PC) and flash the Magisk installer .zip
THMSP said:
You can find a twrp-prepatched boot image for Pie + December Patch here: https://cloud.tmsp.io/s/nb1?path=/Boot Images/2018-12
Enter download mode and use fastboot to flash it into your active boot partition (either boot_a or boot_b, depending on the output of "fastboot getvar current-slot").
Then boot into recovery mode (using adb reboot recovery, or by shutting the phone down and pressing volume up while connecting it to the PC) and flash the Magisk installer .zip
Click to expand...
Click to collapse
Hi,
thank you for your help but i'm stuck in boot here are the commands I did:
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar current-
slot
current-slot: b
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe boot twrp-3.2.3
-1-NB1.img --slot=b
downloading 'boot.img'...
OKAY [ 0.127s]
booting...
OKAY [ 5.208s]
finished. total time: 5.337s
I've also tried to boot on TWRP 3.2.3-1 but same issue I could not boot onto it and then flash it.
Any Idea ?
Regards
>> Hi, never mind working OK thx
Dr. Slump said:
Thanks, marry christmas to you, too. TWRP won't work because there isn't a dedicated recovery partition anymore, it was patched into boot partition and wiped out with the flashing
If you are trying the prerooted boot image with "fastboot boot", it is broken after the august update. If not, maybe it is better to download the stock image to /sdcard and patch it with your latest magisk, later upload it to computer and "fastboot flash" it.
Click to expand...
Click to collapse
This worked for me with September boot. Just did what you said and then "fastboot flash boot patched_boot.img".
Thanks again
UPDATE: @Titokhan has confirmed this issue was fixed with the latest 9.5.4 update!
Ok so I did some things today to my phone and I ended up with the 9.5.4 version of the OOS ROM.
Earlier in the week I did NOT have the ability to "fastboot boot img" but now I do.
Can somebody please verify that the latest version of the ROM brings back the fastboot boot command?
if the latest version doesn't fix it I will post a quick guide about how I was able to get it back on mine. I'll turn this post into a guide at that point.
I'm on the unlocked international version.
texasaggie1 said:
Ok so I did some things today to my phone and I ended up with the 9.5.4 version of the OOS ROM.
Earlier in the week I did NOT have the ability to "fastboot boot img" but now I do.
Can somebody please verify that the latest version of the ROM brings back the fastboot boot command?
if the latest version doesn't fix it I will post a quick guide about how I was able to get it back on mine. I'll turn this post into a guide at that point.
I'm on the unlocked international version.
Click to expand...
Click to collapse
My device is still stuck on 9.5.3 but I know I can boot img when I switch slots
Logan0829 said:
My device is still stuck on 9.5.3 but I know I can boot img when I switch slots
Click to expand...
Click to collapse
Here's the 9.5.4 ota https://drive.google.com/file/d/1-0eczDjrIR7Op3Ut-2mVKicjuxPXH-Ar/view?usp=drivesdk
Also, I didn't have to do anything special to get fastboot boot img to work
I can confirm that the dev team fixed the fastboot boot part with the recent most 9.5.4.GM21AA/9.5.5.GM21BA OTA update.
Titokhan said:
I can confirm that the dev team fixed the fastboot boot part with the recent most 9.5.4.GM21AA/9.5.5.GM21BA OTA update.
Click to expand...
Click to collapse
That's great to hear now I don't have to flash back boot img Everytime I test a twrp build.
I'm on 9.5.5 and I still can't get "fastboot boot ..." to work using the latest fastboot binaries from google. Says something like unrecognized command every time I've tried. What steps did you change to get it working pre-9.5.5?