This works only if you have working Fastboot AKA Download mode and you have unlocked your bootloader .
First download this --> https://github.com/StollD/NOST/releases/download/v0.6/NOST-v0.6.exe
Its a latest one and the working one. If you have LOST LA installed just unistall it. That doesnt work at all.
Then you need to download this FIRMWARE --> https://drive.google.com/uc?id=1smpap8mB0RZNk1j_HD0IJUX5LjFzKC4a&export=download
Then istall NOST and extract ZIP file. Launch NOST and select next. Make sure you phone is connect to your pc and it is fastboot mode "download mode" and find your phone. If it does then just click next. Now select the extracted nb0 file and go next.
If i remember right there is normal and rescue install method and some other too. I use the normal method. Then just go and start the install. Every first time it do something to my phone but give me the error and did not pass the install. But when i try it again it works just fine and finish the install. Then your phone should just do a reboot and voila, you have a stock nokia firmware installed succesfull.
After i do that, and my Nokia 6 1021 start, its download first PIE version and installed. After that i can do OTA install the latest PIE version. And i still can have my fastboot a live. So if you have like i have unlocked bootloader you can flash the latest TWRP and latest stable MAGISK 19. Then you have a working ROOT your phone
I just use "fastboot flash recovery recovery.img". Then "FASTBOOT REBOOT" and straight push volume up and power button together so long that your phone go twrp. If you fail its install stock recovery back. You can try again. I Try couple of time and i get it
Now my phone have latest PIE and latest MAGISK.
You need an unlocked bootloader for that.
Yakia said:
You need an unlocked bootloader for that.
Click to expand...
Click to collapse
For what?? Unbrick you phone, NO!
But if you want magisk and twrp yes.
Yes you do need an unlocked bootloader for unbricking the phone, i've tried that and it isn't working without an unlocked bootloader.
DoggyStar said:
For what?? Unbrick you phone, NO!
But if you want magisk and twrp yes.
Click to expand...
Click to collapse
is your phone has unlocked bootloader, this cannot done if you dont have unlocked bootloader.
you must flash december 2017 update first in my experience.
frnsl3 said:
is your phone has unlocked bootloader, this cannot done if you dont have unlocked bootloader.
you must flash december 2017 update first in my experience.
Click to expand...
Click to collapse
You don't need to have unlocked bootloader to flash December 2017 update. Just boot on the recovery and update that on your SD card.
Still you don't need unlocked bootloader!
DoggyStar said:
You don't need to have unlocked bootloader to flash December 2017 update. Just boot on the recovery and update that on your SD card.
Still you don't need unlocked bootloader!
Click to expand...
Click to collapse
If everything goes well yes but if it doesn't boot (as I had when I had unlock the bootloader), it won't be able to use NOST because you need an unlocked bootloader to use it and flash the nb0
arl0ng said:
If everything goes well yes but if it doesn't boot (as I had when I had unlock the bootloader), it won't be able to use NOST because you need an unlocked bootloader to use it and flash the nb0
Click to expand...
Click to collapse
Why you need to have unlocked bootloader to use nost?
Nost only need working fastboot.
DoggyStar said:
Why you need to have unlocked bootloader to use nost?
Nost only need working fastboot.
Click to expand...
Click to collapse
NOST refuses to flash your phone if your bootloader isn't unlocked critically. The old OST would just try to flash but never make any progress which confuses inexperienced users.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
arl0ng said:
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
Click to expand...
Click to collapse
This is different version what i use. I use version 0.6. Not that LA version.
arl0ng said:
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
Click to expand...
Click to collapse
And yes, you are right. Nost see if i have critically unlocked phone. So that doesn't work without unlocked bootloader.
My bad
DoggyStar said:
And yes, you are right. Nost see if i have critically unlocked phone. So that doesn't work without unlocked bootloader.
My bad
Click to expand...
Click to collapse
Yes that's what I was trying to tell you, I think you can edit your thread.
Yakia said:
Yes that's what I was trying to tell you, I think you can edit your thread.
Click to expand...
Click to collapse
Thanks man, I edited.
My phone is hard bricked.
Recently I was continuously charging my phone with power bank. One night I forgot to put my phone on charge and it got discharged fully. I tried starting it in morning but it got stucked at Nokia logo, I tried getting it into recovery mode to reset it but was not able to because i haven't connected it to power before. Afterwards I connected it to my laptop whose charger was having earthing problem and giving shocks. In between trying to put my phone into recovery mode along with connected to laptop, the current passed through my phone for 2 times. And that was the last moment i had seen my phone's screen lighted, and then full blackout.
I have taken it to service center first, the person tried installing the software on phone again and confirmed phone is being detected by PC but unable to install software. They had given only one option to change the motherboard to fix it.
Then i tried getting it repaired at local shops, where a person told me internal memory IC has been shorted. Another person at different shop tried repairing it and was also not able to fix and said lastly that motherboard is dead.
I think maybe Hardware kernel got disturbed, so is there any method to install the hardware kernel again?
have you Nokia 6 TA-1033 SS firmware rom download link?
Links are dead
Related
I got a unlocked bootloader XZ dual 8332, download tft from Xperiafirm, and at the end of flash session i got a erro :
Code:
[COLOR="Red"]01/025/2016 17:25:54 - ERROR - Have read only 524256 byte(s) instead of 780004 byte(s)
01/025/2016 17:25:54 - ERROR - Error flashing. Aborted[/COLOR]
What does it's meanning ? My phone got a "update failed" when turn on now.
Do we need check some "check box" or anything before flash a tft file ?
And is anyway to relock bootloader if we want repair by Xperia Companion or update through OTA ?
Thanks.
AFAIK flashtool is not compatible with 7.0 yet and there is no way to relock your bootloader yet.
gregbradley said:
AFAIK flashtool is not compatible with 7.0 yet and there is no way to relock your bootloader yet.
Click to expand...
Click to collapse
Wipe qnovo and try in flashtool
gregbradley said:
AFAIK flashtool is not compatible with 7.0 yet and there is no way to relock your bootloader yet.
Click to expand...
Click to collapse
I relocked by flashtool (same as unlock) and repairing by Companion now.
Btw thank you .
let's wait for new kernel to get back DRM-fix xD
Sorry to be a bother.
Same thing happened to me, how do i relock the bootloader?
Lavievn said:
I relocked by flashtool (same as unlock) and repairing by Companion now.
Btw thank you .
let's wait for new kernel to get back DRM-fix xD
Click to expand...
Click to collapse
Is the camera working for you after relock?
chawlasrijan said:
Is the camera working for you after relock?
Click to expand...
Click to collapse
No, we cant use stock camera app and got very bad and small sound volume.
Cavaleur7 said:
Sorry to be a bother.
Same thing happened to me, how do i relock the bootloader?
Click to expand...
Click to collapse
same as unlock, but now you get a "relock button", click it and everything fine but your DRM-key is gone
Lavievn said:
No, we cant use stock camera app and got very bad and small sound volume.
Click to expand...
Click to collapse
That's just sad No point to relock the bootloader then.
Need do that for update, or wait till new kernel for 7.0 with drm-fix release
chawlasrijan said:
That's just sad No point to relock the bootloader then.
Click to expand...
Click to collapse
When you flash a modified kernel with drm fix your drm is working. When you relock your bootloader your phone got factory reset itself and drm still in your phone.
Try to update via ota
After that because you are unlocked try to flash flashfire and install supersu to be rooted and searsh to drm fix file and flash it manually from any root file manager.
Another step
Uodate your unlocked phone ota update
Restart you phone
It should be working now with no drm fix
Poweroff your phone
Enter falshmode (power button + volum up) you see a purpul led
Enter adb and flash supersu sr5
It should work after flash drm manually
Try and reply please
karrouma said:
When you flash a modified kernel with drm fix your drm is working. When you relock your bootloader your phone got factory reset itself and drm still in your phone.
Try to update via ota
After that because you are unlocked try to flash flashfire and install supersu to be rooted and searsh to drm fix file and flash it manually from any root file manager.
Another step
Uodate your unlocked phone ota update
Restart you phone
It should be working now with no drm fix
Poweroff your phone
Enter falshmode (power button + volum up) you see a purpul led
Enter adb and flash supersu sr5
It should work after flash drm manually
Try and reply please
Click to expand...
Click to collapse
So much wrong info here.
Firstly, once you unlock the bootloader the TA partition where the DRM keys are stored is formatted. They are gone forever. Relocking the bootloader does not bring them back. The DRM fix replicates (Not 100% fixes) the missing functions and this fix only works on rooted phones, which you cannot have with a locked bootloader.
Secondly, do not try and update OTA with an unlocked bootloader. It could brick your device.
Are there any known issues when unlocking the boot loader?
A: Yes. When you select a device, any known issues for that device will be displayed. In addition, the following generic issues have been reported:
•Some users have experienced problems when they are accepting over the air upgrades. Therefore we do not recommend users to accept over the air upgrades, after having unlocked the boot loader. For additional information, check out the XDA Forums for hints and tips from the community.
Click to expand...
Click to collapse
Source Sony unlock bootloader FAQ
gregbradley said:
So much wrong info here.
Firstly, once you unlock the bootloader the TA partition where the DRM keys are stored is formatted. They are gone forever. Relocking the bootloader does not bring them back. The DRM fix replicates (Not 100% fixes) the missing functions and this fix only works on rooted phones, which you cannot have with a locked bootloader.
Secondly, do not try and update OTA with an unlocked bootloader. It could brick your device.
Source Sony unlock bootloader FAQ
Click to expand...
Click to collapse
I am on unlocked bootloader
I will do a backup now and will try to update OTA or via xperia companion
Turning phone off and enter flashboot to inject supersu sr5 for android 7 and then restart
I will try
If not booting ,bye bye my xz
If can't be back to android 6 , bye bye my xz
Wait my reply, it depend to the speed of my connection
karrouma said:
I am on unlocked bootloader
I will do a backup now and will try to update OTA or via xperia companion
Turning phone off and enter flashboot to inject supersu sr5 for android 7 and then restart
I will try
If not booting ,bye bye my xz
If can't be back to android 6 , bye bye my xz
Wait my reply, it depend to the speed of my connection
Click to expand...
Click to collapse
Xperia companion will fail. It will detect unlocked bootloader and not work.
OTA 'may' work, but as I said and quoted it 'may' also brick your device. Do it at your own risk.
gregbradley said:
Xperia companion will fail. It will detect unlocked bootloader and not work.
OTA 'may' work, but as I said and quoted it 'may' also brick your device. Do it at your own risk.
Click to expand...
Click to collapse
Everything you wrote is absolutely correct.
PC companion detects that the device is unlocked & OTA's automatically fails to install.
So apparently, relocking & updating is possible but relocking means you can no longer use the stock camera anymore.
chawlasrijan said:
Everything you wrote is absolutely correct.
PC companion detects that the device is unlocked & OTA's automatically fails to install.
So apparently, relocking & updating is possible but relocking means you can no longer use the stock camera anymore.
Click to expand...
Click to collapse
You should be able to then unlock again and just needo to wait for a modified kernel with drm fix for android 7
Sent from my iPad
gregbradley said:
You should be able to then unlock again and just needo to wait for a modified kernel with drm fix for android 7
Sent from my iPad
Click to expand...
Click to collapse
Unlocking your bootloader again on Nougat using official Sony guide fixed the issue for me.
Make sure you don't use Flashtool to unlock your bootloader on Nougat.
Thank you for the support
chawlasrijan said:
Unlocking your bootloader again on Nougat using official Sony guide fixed the issue for me.
Make sure you don't use Flashtool to unlock your bootloader on Nougat.
Thank you for the support
Click to expand...
Click to collapse
How to unlock
Via adb???
Steps used please
If you have the ftf can you modify your kernel now??
karrouma said:
How to unlock
Via adb???
Steps used please
If you have the ftf can you modify your kernel now??
Click to expand...
Click to collapse
Google "unlock bootloader Sony"
Click the sony developer link & follow the guide.
hi guys ,
I`ve read this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
my ask : Does this rooting goes well with MHA-L29C185B172 ?
if not , then how can i root my device SAFELY ?
thanks all
one, post, no experience with rooting android phones, do NOT root this phone unless there is some important reason to.
do ALOT more reading before you even think about rooting
Thx to reply. Like the others i wanna root to have root apps in my phone ,
Thx . Wanna have apps requires root in my phone . That simple
You don't even need to decrypt if you don't want to.
Unlock Developer Options (Settings - About: tap build number until it says it's enabled)
Go to the Developer Options and enable OEM Unlocking
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
nawraz said:
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
Click to expand...
Click to collapse
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
ante0 said:
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
Click to expand...
Click to collapse
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
I failed install su however still waiting for any updates
nawraz said:
I failed install su however still waiting for any updates
Click to expand...
Click to collapse
You flashed the one I linked? And which twrp do you use?
ante0 said:
You don't even need to decrypt if you don't want to.
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
Click to expand...
Click to collapse
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
FootSlave said:
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
Click to expand...
Click to collapse
He already unlocked and flashed twrp.
3.1.0 installs SuperSU fine. 3.0.3 does not.
And if oem was locked he wouldn't even be in twrp as you can't flash anything with fastboot if it is locked.
But I'll update my post in case anyone does miss to unlock oem.
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
FootSlave said:
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
Click to expand...
Click to collapse
Yeah. Only way then would be to rebrand to C636 using the DLOAD method, then rebrand back to your stock version using the Update thread under Guides. The latter requires twrp though so you'd need to rebrand first to get a working system.
To be honest I just figured he had already unlocked and flashed twrp as he was in the decrypt thread
Missing oem was an error on my side. It was long since I had to unlock oem xD
ante0 said:
You flashed the one I linked? And which twrp do you use?
Click to expand...
Click to collapse
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
nawraz said:
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
Click to expand...
Click to collapse
Weird. I tested with 3.1.0 a few days ago. But I guess it could have to do with builds. 3.1.0 is using kernel for B182. Maybe it's fixed if you use 3.1.0 with B182.
Oh well, good you managed to install it anyway.
Edit: I tested with the SuperSU I linked.
mscion said:
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
Click to expand...
Click to collapse
All I know is that it wasn't present in builds before B182.
@st_voss is the one who found out it was added in B182 (Kernel build April. 11th probably as that's what I have on B182.).
It might be present in B181 on C636 as well, that was released 8th of May.
mr. ante0 ..... u r the man , thank you so much
thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0
thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0
Found this series of blog posts that describe the Emergency Download Mode (EDL) on Qualcomm-based mobile devices.
This thread was made for us to discuss the possibilities around this mode and what benefits could we achieve for our phones.
I have not read them completely yet, but there is a mention of a Secure Boot bypass exploit against a Nokia 6.
xiomi EDL mode does allow to PUSH Twrp after altering the FASTBOOT ROM,
if Nokia is providing Fastboot roms then may be!
it doesn't unlock the bootloader! its just push Twrp so that you can flash modes to disable dm varity and magisk
YasuHamed said:
xiomi EDL mode does allow to PUSH Twrp after altering the FASTBOOT ROM,
if Nokia is providing Fastboot roms then may be!
it doesn't unlock the bootloader! its just push Twrp so that you can flash modes to disable dm varity and magisk
Click to expand...
Click to collapse
I've been trying to find more information on what you commented about xiaomi, could you please provide any additional information or links?
Thanks!
dbpm1 said:
I've been trying to find more information on what you commented about xiaomi, could you please provide any additional information or links?
Thanks!
Click to expand...
Click to collapse
QUALCOM FLASHER (universal)
https://www.youtube.com/watch?v=Koh946ihjAU -----I NEVER USED ,since MI has their OWN Flasher ( MiFLASH)
SINCE I had Xiomi Redmi3s , i EDL it , using FASBOOT ROM ( now miui provides two versions of each rom, recovery Rom and/or FastbootRom
http://en.miui.com/thread-845446-1-1.html
now
see this
http://en.miui.com/thread-276565-1-1.html
tuorial how to change RAMDISK lines, using AIK, for Device REDMI 3s (twrp IDO) and replace signed BOOT image with twrp.img (LOCKED BOOTLOADER) to flash rom with twrp! so that you can flash (from twrp)
1. lazyflasher (tool for xiomi to Switch DM VARITY off)
2. Magisk / Supersu
if you can do something for NOKIA 8
then I will consider it BUYING,! ( I skipped it since i never saw solid piece on XDA / Internet about how to Unlock bootloader! )
Then buy it
YasuHamed said:
QUALCOM FLASHER (universal)
https://www.youtube.com/watch?v=Koh946ihjAU -----I NEVER USED ,since MI has their OWN Flasher ( MiFLASH)
SINCE I had Xiomi Redmi3s , i EDL it , using FASBOOT ROM ( now miui provides two versions of each rom, recovery Rom and/or FastbootRom
http://en.miui.com/thread-845446-1-1.html
now
see this
http://en.miui.com/thread-276565-1-1.html
tuorial how to change RAMDISK lines, using AIK, for Device REDMI 3s (twrp IDO) and replace signed BOOT image with twrp.img (LOCKED BOOTLOADER) to flash rom with twrp! so that you can flash (from twrp)
1. lazyflasher (tool for xiomi to Switch DM VARITY off)
2. Magisk / Supersu
if you can do something for NOKIA 8
then I will consider it BUYING,! ( I skipped it since i never saw solid piece on XDA / Internet about how to Unlock bootloader! )
Click to expand...
Click to collapse
bidhata said:
Then buy it
Click to expand...
Click to collapse
well sir please test and post complete guide about your experience on rooting Nokia 8 (locked BL) and I will
thank you
Found this tutorial on how to make an EDL cable:
http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
dbpm1 said:
Found this tutorial on how to make an EDL cable:
http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Click to expand...
Click to collapse
Yes, it works but on Nokia5 and Nokia6 models only. Most of newer models does not switch to EDL mode. The question is still open: how to downgrade October SP to July to have ability of bootloader unlocking and rooting?
kosmatyj said:
Yes, it works but on Nokia5 and Nokia6 models only. Most of newer models does not switch to EDL mode. The question is still open: how to downgrade October SP to July to have ability of bootloader unlocking and rooting?
Click to expand...
Click to collapse
You have some choice to downgrade
Flash firmware via ost tool,ntool
Flash system via fastboot
If want root... Can use patch boot of trisi... Now nokia 8 more easier
ValKyre said:
You have some choice to downgrade
Flash firmware via ost tool,ntool
Flash system via fastboot
If want root... Can use patch boot of trisi... Now nokia 8 more easier
Click to expand...
Click to collapse
I have no choice because I have updated to Oct. SP, my boot is locked and no possibility to roll back or atleast unlock bootloader. So EDL - is the only way to roll back to happy times with the root, freedom and customizing.
kosmatyj said:
I have no choice because I have updated to Oct. SP, my boot is locked and no possibility to roll back or atleast unlock bootloader. So EDL - is the only way to roll back to happy times with the root, freedom and customizing.
Click to expand...
Click to collapse
At oct security u can't unlock boot with method September???
ValKyre said:
At oct security u can't unlock boot with method September???
Click to expand...
Click to collapse
I already have a key. I had an unlocked boot but I could not install updates later than July. So I locked the bootloader and successfuly updated August, Sept., Oct. Now I cant unlock the boot with the key I have.
kosmatyj said:
I already have a key. I had an unlocked boot but I could not install updates later than July. So I locked the bootloader and successfuly updated August, Sept., Oct. Now I cant unlock the boot with the key I have.
Click to expand...
Click to collapse
Do u try get a new key ?
ValKyre said:
Do u try get a new key ?
Click to expand...
Click to collapse
Why? A new signing algorythm is used in the latest update. It is not supported yet. Nor offficially nor by side sellers
kosmatyj said:
I already have a key. I had an unlocked boot but I could not install updates later than July. So I locked the bootloader and successfuly updated August, Sept., Oct. Now I cant unlock the boot with the key I have.
Click to expand...
Click to collapse
Before July update, YOU got unlock.key,
Then after septemer+ , before Pie-version, did you trie to get the second bootloader-unlock.key? because they changed bootloader? and also I am not sure if they givve away again from oreo and officail app a new unlock.key?
I don't dear to try out, fearing not getting anymore unlock-keys from hmd, need to secure more information.
I am trying to get a new key via official app but it is telling me that google play service isn't installed, although I downloaded open_gapps-arm64-8.0-pico-20190327 and was flashed via twrp and restored to original stock and still the official app is complaining about no play services when I am logged in to google-account inside the phone.
FYI: I donwngraded to oreo 8.0 and for experiment purpose I am trying to test if I will get a new key.
Thank you for replying. My problems are now gone, because I have recieved an official new bootloader unlock key. Now I have 2 keys for old and for new firmwares, so now I can flash anything I want with no fear . I downgraded to Android 7.1.1 and dont want to update any more. Now waiting for custom ROMs.
Hello,
I have a P20 Pro with unlocked bootloader, i decided to updated the phone trought OTA by flashing original recovery and instal OTA of Android 10.
After that i wanted to get back to TWRP then root my phone, but i get surprised that the phone bootloader get locked again after update.
I need to unlock my bootloader again in order to use my phone. the command in fastboot : fastboot oem unlock **************** (i put my old unlocking code which already worked 2 years ago)
but i get as a result :
...
FAILED (remote: invalid command)
finished. total time : 0.027s
can anyone help me getting back my bootloader unlocked and twrp installed please ? i dont want loose my phone
NB : i confirm again that my code was working before on android 9 and had bootloader unlocked
Rovyo said:
Hello,
I have a P20 Pro with unlocked bootloader, i decided to updated the phone trought OTA by flashing original recovery and instal OTA of Android 10.
After that i wanted to get back to TWRP then root my phone, but i get surprised that the phone bootloader get locked again after update.
I need to unlock my bootloader again in order to use my phone. the command in fastboot : fastboot oem unlock **************** (i put my old unlocking code which already worked 2 years ago)
but i get as a result :
...
FAILED (remote: invalid command)
finished. total time : 0.027s
can anyone help me getting back my bootloader unlocked and twrp installed please ? i dont want loose my phone
NB : i confirm again that my code was working before on android 9 and had bootloader unlocked
Click to expand...
Click to collapse
You idiot EMUI 10 cannot be bootloader unlocked, downgrade to EMUI 9.0!!!
If you want android 10 or even 11 you need something called a GSI, which I can inform you about it.
jjgvv said:
You idiot EMUI 10 cannot be bootloader unlocked, downgrade to EMUI 9.0!!!
If you want android 10 or even 11 you need something called a GSI, which I can inform you about it.
Click to expand...
Click to collapse
i'm really an idiot i can confirm that, how to downgrade please ? my bootloader in locked right now
Rovyo said:
i'm really an idiot i can confirm that, how to downgrade please ? my bootloader in locked right now
Click to expand...
Click to collapse
HISUITE
jjgvv said:
HISUITE
Click to expand...
Click to collapse
You saved me mate, was really a dumb move to go thought OTA without checking this point. Didn't now Huawei become that ******
Any advice for a good custom rom based on android 10 ?
And thanks again for your precious help
Rovyo said:
You saved me mate, was really a dumb move to go thought OTA without checking this point. Didn't now Huawei become that ******
Any advice for a good custom rom based on android 10 ?
And thanks again for your precious help
Click to expand...
Click to collapse
I can get you Android 11 actually, though there are a few bugs on both 10 and 11.
jjgvv said:
I can get you Android 11 actually
Click to expand...
Click to collapse
even better if it is android 11, i will try it
also have another dumb question : if i install TWRP on the EMUI 9.1 with unlocked bootloader, can i flash the emui 10 rom thought TWRP ? or this will brick the phone ?
Rovyo said:
even better if it is android 11, i will try it
also have another dumb question : if i install TWRP on the EMUI 9.1 with unlocked bootloader, can i flash the emui 10 rom thought TWRP ? or this will brick the phone ?
Click to expand...
Click to collapse
Yes, system will be 'destroyed', as you modded the recovery.
jjgvv said:
Yes, system will be 'destroyed', as you modded the recovery.
Click to expand...
Click to collapse
that what i was thinking also, so bye Emui 10 for ever i guess.
what was the rom base on android 11 you are referring to ?
GSI Project treble rom.
The definition is https://source.android.com/setup/bu...tem image (GSI,or higher can run successfully.
Google's Offical GSI will not boot on huaweis though.
After unlock bootloader download this https://github.com/phhusson/treble_...v300.l/system-roar-arm64-aonly-vanilla.img.xz
use 7zip(https://www.7-zip.org/a/7z1900-x64.exe) to extract the file once and rename it to system.img and move to C drive WITHOUT under any folders.
Then go to recovery and factory reset, do not advance wipe, wipe>factory reset only
Then go to fastboot and
fastboot flash system C:\system.img
Failing to follow will result in rage!
Backup System, Vendor, Data and Internal storage in TWRP before doing anything will be a wise choice, in case anything is wrong.
Forgot to mention you must flash magisk in TWRP before installing rom, to disable AVB(Android Vertified Boot) so that a custom rom can be loaded.
jjgvv said:
Backup System, Vendor, Data and Internal storage in TWRP before doing anything will be a wise choice, in case anything is wrong.
Click to expand...
Click to collapse
Yeah for sur, i'm rolling back, unlocking BL then TWRP in order to get a full backup. I ll check the rom after that
A senior member refer to for EMUI 10 upgrading :
"Don't update system via OTA when phone is rooted or bootloader unlock. Flash firmware via erecovery and rooted again"
i think this is incorrect right ? he cant root again while on EMUI 10 ?
jjgvv said:
Forgot to mention you must flash magisk in TWRP before installing rom, to disable AVB(Android Vertified Boot) so that a custom rom can be loaded.
Click to expand...
Click to collapse
thanks for the proper advice
Rovyo said:
Yeah for sur, i'm rolling back, unlocking BL then TWRP in order to get a full backup. I ll check the rom after that
A senior member refer to for EMUI 10 upgrading :
"Don't update system via OTA when phone is rooted or bootloader unlock. Flash firmware via erecovery and rooted again"
i think this is incorrect right ? he cant root again while on EMUI 10 ?
Click to expand...
Click to collapse
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Read troubleshooting part, EMUI 10 cannot unlock bootloader
jjgvv said:
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Read troubleshooting part, EMUI 10 cannot unlock bootloader
Click to expand...
Click to collapse
the lasted TWRP release cant decrypt the data, trying to find a working one and the phone don't want to boot to recovery anymore even with volume up + power bouton or via command adb reboot recovery. seems a good day hahaha
Still boots fastboot? Otherwise you are screwed
jjgvv said:
Still boots fastboot? Otherwise you are screwed
Click to expand...
Click to collapse
what do you mean ? yes i still can go on fastboot and already rolled back to Emui 9.1
just want to boot on damn recovery hahaha and if it can decrypt daba will be great
jjgvv said:
Still boots fastboot? Otherwise you are screwed
Click to expand...
Click to collapse
well i'm stuck with twrp not decrypting my data
i managed to install TWRP (several version), boot on them and so nothing to do
also can get root easily and magisk as i sideload zip from crypted TWRP version (worked)
tried the version twrp_clt_0.1.img from XDA stuck on TWRP starting screen
i'm almost giving up
Extract Android 11 Gsi, rename to system.img and move to C drive , not under any folders.
Go to fastboot then
Fastboot erase data
Fastboot erase cache
Fastboot flash system C:\system.img
Background:
I unlocked the bootloader and then proceeded to flash the device from 12 to 11 using THIS tutorial. When I got to the first "fastboot reboot fastboot" the phone never rebooted. The screen is all black. I can't get into recovery or back into fastboot using the button method.
I downloaded the MSM Global tool and got all the drivers installed. I was able to start the flashing process but get "Device not match image" early in the process. I have called OnePlus customer service. They didn't ask any questions just told me to send in the phone. I would rather fix this myself if possible. Any insight and or help is much appreciated.
UPDATE: I found this information, and it had me flash the India 9 Pro version. It worked. I have a booting phone and can now work on getting it back to the US version.
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
EtherealRemnant said:
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
Click to expand...
Click to collapse
Thanks for that! The phone is back to fulling functioning with the proper version of OOS. It has been a long time since I rooted and ROMed. Fastboot used to be a straightforward method of flashing a stock ROM. Doesn't seem like it is anymore.
hillmom said:
Thanks for that! The phone is back to fulling functioning with the proper version of OOS. It has been a long time since I rooted and ROMed. Fastboot used to be a straightforward method of flashing a stock ROM. Doesn't seem like it is anymore.
Click to expand...
Click to collapse
Glad that it worked. Did you have the bootloader locked? I am just trying to confirm I'm not crazy and that I was actually able to use it with a locked bootloader lol.
Yeah fastboot flashing was the gold standard way to avoid a brick back in the days before A/B partitions and Android Verified Boot came along but not so much now. This device in particular seems to be really fussy about fastboot flashing. I never managed to brick my Pixel 3 XL doing it but I have had to MSM multiple times trying to do fastboot commands and custom recoveries to flash custom ROMs on my OP9. I have got the process down tova science at this point lol. I just went back to stock and rooted it and I'm much happier with that than I was with custom ROMs that were plagued with issues.
EtherealRemnant said:
Glad that it worked. Did you have the bootloader locked? I am just trying to confirm I'm not crazy and that I was actually able to use it with a locked bootloader lol.
Yeah fastboot flashing was the gold standard way to avoid a brick back in the days before A/B partitions and Android Verified Boot came along but not so much now. This device in particular seems to be really fussy about fastboot flashing. I never managed to brick my Pixel 3 XL doing it but I have had to MSM multiple times trying to do fastboot commands and custom recoveries to flash custom ROMs on my OP9. I have got the process down tova science at this point lol. I just went back to stock and rooted it and I'm much happier with that than I was with custom ROMs that were plagued with issues.
Click to expand...
Click to collapse
Sorry, I did it with the bootloader unlocked.
I might go back to Stock soon enough. While not as big a pain as Samsung, also not the easiest phone I've played with either.
EtherealRemnant said:
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
Click to expand...
Click to collapse
Hii! My phone is LE2115 a12 C60 can i use this file to go back to OSS11? Also do i need to unlock my bootloader or i can use this even with bootloader locked? Last one where can i find "local update tool"? Thanks a lot
eliasdeejay said:
Hii! My phone is LE2115 a12 C60 can i use this file to go back to OSS11? Also do i need to unlock my bootloader or i can use this even with bootloader locked? Last one where can i find "local update tool"? Thanks a lot
Click to expand...
Click to collapse
Yes, you can use this to go back to OOS11. You shouldn't need to unlock the bootloader as this is an officially sanctioned downgrade package.
Since you're on Android 12 you need to install the local upgrade APK:.
https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Install that, push the downgrade zip to /sdcard/, open the newly installed system update app, hit the gear, and it should show you the zip file waiting.
EtherealRemnant said:
Yes, you can use this to go back to OOS11. You shouldn't need to unlock the bootloader as this is an officially sanctioned downgrade package.
Since you're on Android 12 you need to install the local upgrade APK:.
https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Install that, push the downgrade zip to /sdcard/, open the newly installed system update app, hit the gear, and it should show you the zip file waiting.
Click to expand...
Click to collapse
Hii! by chance do you know where I can download the previous versions of A12 update? specifically C.48. And if i can install it via local upgrade APK. Thanks!
eliasdeejay said:
Hii! by chance do you know where I can download the previous versions of A12 update? specifically C.48. And if i can install it via local upgrade APK. Thanks!
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip
There is a pinned post with them. This is C.48 for global and yes, you use the local upgrade but since you're on OOS11, you don't use the APK, use the update function in system settings and tap the gear and you'll see it.
Hi i tried to use the updater on android12 and try to downgrade it to .48 but it return error. So i need to downgrade to android 11 first and then update it again to .48?
cruzzmz said:
Hi i tried to use the updater on android12 and try to downgrade it to .48 but it return error. So i need to downgrade to android 11 first and then update it again to .48?
Click to expand...
Click to collapse
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
EtherealRemnant said:
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
Click to expand...
Click to collapse
Hii is 11.2.10.10 a lot better than 11.2.8.8? Sorry for a lot of questions im new to OnePlus
EtherealRemnant said:
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
Click to expand...
Click to collapse
Ok if i understand correctly, i just use the updater to flash the android 11 zip file that you provided and it will do a full wipe and will restore to android 11. Then i just use the updater again to flasj it to .48
am i correct?
eliasdeejay said:
Hii is 11.2.10.10 a lot better than 11.2.8.8? Sorry for a lot of questions im new to OnePlus
Click to expand...
Click to collapse
I don't know because I didn't get my phone until February so I went right to 11.2.10.10. It is important to update though because it gets you a working OS on both slots instead of just one.
cruzzmz said:
Ok if i understand correctly, i just use the updater to flash the android 11 zip file that you provided and it will do a full wipe and will restore to android 11. Then i just use the updater again to flasj it to .48
am i correct?
Click to expand...
Click to collapse
Yes, if you want to go back to 12.
EtherealRemnant said:
Yes, if you want to go back to 12.
Click to expand...
Click to collapse
yes i want to go to 12 but not the crappy .60
cruzzmz said:
yes i want to go to 12 but not the crappy .60
Click to expand...
Click to collapse
Lol yeah. I'm not too happy with C.60 either. I really don't want to wipe my device and lose my Signal chats again.
EtherealRemnant said:
Lol yeah. I'm not too happy with C.60 either. I really don't want to wipe my device and lose my Signal chats again.
Click to expand...
Click to collapse
my sentiment exactly dunno how OP fk up with the model and the update
so i dont need MSM Tool to downgrade??
cruzzmz said:
my sentiment exactly dunno how OP fk up with the model and the update
so i dont need MSM Tool to downgrade??
Click to expand...
Click to collapse
I don't know what you aren't understanding but I'm tired of repeating myself. Read what I wrote and it answers your question.
EtherealRemnant said:
I don't know what you aren't understanding but I'm tired of repeating myself. Read what I wrote and it answers your question.
Click to expand...
Click to collapse
Ok done it ... on OOS11 now .... no need to unlock bootloader can just flash the file directly.
Will try OOS11 for a while and see if it is worth updating to OOS12