Related
Stuck on splash screen "Your device has been unlocked and can't be trusted."
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
gabrce said:
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
Click to expand...
Click to collapse
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
mrmazak said:
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
Click to expand...
Click to collapse
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
gabrce said:
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
Click to expand...
Click to collapse
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
mrmazak said:
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
Click to expand...
Click to collapse
Thank you but "fastboot get prop" is not the right command. If anybody has a solution it will be awesome.
Download the latest full ota package for your device (around 2gb)
Extract the contents of the update. App using huawei firmware extractor and
Flash
kernel
Ramdisk
Recover ramdisk
System and cust images using fastboot
After that flash the correct version of twrp for your device and then install images of version and vendor(found in update. App file) partitions using twrp.
.
This method worked for me
It didn't worked for me... Do you know any other method?
I tried many TWRP versions but the phone doesn't boot into TWRP...
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Windwell said:
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Click to expand...
Click to collapse
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
Hey mate,
Thanks for responding. Sorry for the late reply.
From what you had suggested, I did "fastboot --set-active=a" , "fastboot flash boot boot.img", and "fastboot reboot" (with the stock unpatched boot.img) the commands were successful once again, but there were no effective changes.
Afterwards, I did "fastboot --setactive-b", "fastboot flash boot boot.img", and "fastboot reboot" the commands were successful once more, and this time, I was finally able to go into recovery mode. On the other hand, in recovery mode I wiped the cache and erased everything, but unfortuantely I still could not boot into Android, even though I tried to flash boot the image once more.
Thank you for these commands, as I was at least able to recover recovery mode.
Any other suggestions maybe?
Hello,
Use this tool and it will fix it, I had the same problem. Just download the software and flash it in Qualcomm EDL mode.
MSMDownload image needed
Hello guys, I managed to flash the wrong image to OnePlus NORD N100 BE2013, I overlooked for the first time what I'm doing and messed it up Now it's in Qualcomm EDL mode and I need and image to flash it to bring it back do life, anyone I can...
forum.xda-developers.com
I alsp posted boot.img which is compatible you can flash it. Link is in the comments.
Thanks
Boot.img from nord n100 in this thread, I exctracted and rooted it myself.
I WHANT RECOVERY Boot.img FOR ROOT MY ONEPLUS NORD N100
I unlock bootloader and i whant to root with magisk my phone, i need boot.img for rocovery..I try anather boot.img from One plus nord, etc, i sucessfull flash this recovery's with command in windows but is no go in recovery, stay in bootloop..Can...
forum.xda-developers.com
Hello,
I used the tool MSMDownload but unfortunately I was unable at all to boot into Qualcomm Edl mode, even though I have installed correctly all the drivers for Windows Qualcomm, and OnePlus USB drivers, and used the correct method (Volume Button UP and Down at the same time whilst connecting the phone via USB). I tried flash booting with the boot.img you gave me, but still no changes. I am still stuck in Fastboot.
If you had encountered the same issue back then, can you tell me the excat procedure you did please?
Thank you so much.
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
oh
thts ok man
بلوک سبک
I will try to make a fastboot image for OnePlus NORD N100 BE2013 with 10.5.5 and upload it to mega, I'll send you the link. If you are in fastboot mode you will be able to flash it I believe, let me have a look.
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
motovnet said:
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
Click to expand...
Click to collapse
For some reason Qualcomm Mode Edl does not launch whatsoever.
motovnet said:
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
Click to expand...
Click to collapse
Thank you that's very kind of you. I think the only way to fix it by flash boot.img, but I have doubts because it does not work.
The only commands I am doing are "fastboot devices", "fastboot flash boot boot.img"
With the fastboot image you will be able to flash everything, it contains not only boot.img but system and etc. I managed to boot mine and bring it back to life by reflashing everyhing.
So the only thing I need to do is "fastboot flash boot ''.img" right?
Where can I get all the nesscary files?
And how did you manage to root it?
The fastboot image flashes all partitions, not just boot with stock Oxygen OS 10.5.5
What you need to do is run flash-all.bat from the archive and it will flash the entire os not just boot.img.
If you can't get to EDL mode, fastboot flash is the only solution. What model does it say in the back? This one was EUROPE BE2013.
Is your EU or Global device?
Archive is uploading still.
Thanks
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
2.55 GB file on MEGA
mega.nz
This is a fastboot image for OnePlus NORD N100 EU BE2013 device.
Extract it to a new folder, it contains fastboot in it.
Right click flash-all.bat and run as admin.
You can open the flash-all.bat file with notepad to check yourself there is nothing strange in it. I used a bat file from the forum that was fastboot image for OnePlus NORD and changed it to use the .img files for OnePlus NORD N100.
Contains Oxygen 10.5.5, once you bring it back to life (IF YOU HAVE THIS MODEL), you can use magisk to patch the boot.img and flash it via fastboot.
This is how I rooted it and it worked properly.
Please use it with caution and ensure your model matches! I can not guarantee it will work on other devices.
If you can't go to EDL mode, this is your way to go, but I don't know if flashing GLOBAL version will work.
Thanks
Windwell said:
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
Click to expand...
Click to collapse
I would guess BE2013 is the EU one, as this worked on mine.
motovnet said:
I would guess BE2013 is the EU one, as this worked on mine.
Click to expand...
Click to collapse
Okay thank you for helping me. I will try this later and keep you in touch.
Windwell said:
Okay thank you for helping me. I will try this later and keep you in touch.
Click to expand...
Click to collapse
Thanks, let me know if it works for you. If you're unable to flash it via fastboot, only EDL will help.
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.
dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance
Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.
I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)
chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).
Hi Team,
I have an spare Nokia 6.1 (2018) smartphone (Model # - TA -1089)) at my home which I wasn't using since 2-3 years.
Today, I got hands on it, and tried to use it for my development needs.
To begin with, I unlocked its boot-loader using this guide to unlock Nokia 6.1 (2018)
and within "Developer Options", I can see that the "OEM Unlocking" option reads - "Bootloader is already unlocked."
Now, as a next step, I am trying to install TWRP recovery, but nothing seems to be working. No matter which image I try, I get stuck on the TWRP splash screen.
I have tried TWRP Images from the following websites and many more:
TWRP.me
Get Droid Tips - Here when I click on the "Download" option, I get redirected to the "TWRP.me" website only, whose images are not working.
In addition, I have ensured that "ADB and Fastboot" + "Nokia USB Drivers" & other contingencies are properly installed on my system & are not the underlying issue.
I tried running the code
Code:
fastboot flash recovery twrp.img
and my phone got stuck on the TWRP splash screen. Ultimately, I had to use OSA tool and flash the STOCK ROM to get my device working again.
Many websites suggested to simply boot the TWRP and so I used this command:
Code:
fastboot boot twrp.img
in the "Download" mode and then again, nothing happened and I got stuck on the TWRP splash screen.
Note: The only difference between above two commands being - my stock recovery worked fine after executing the 2nd command, and I could boot into my device without much trouble.
Here's my Device Overview:
Device Name - Nokia 6.1
Model & hardware = TA-1089
OS version - Android 10
Security Patch Level - May 1, 2020
Build Number - 00WW_4_15c
Can someone now please suggest where I could be going wrong?
What's my goal:
Root Nokia 6.1 & to be able to install Custom ROM's on Nokia 6.1 and use that device for development purposes
and in case anything goes wrong,
Flash the STOCK ROM again using OSA Tool and bring the device back to its current state.
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
And also not fla#h
It is a/b partition so only boot done your goals and boom
Everytime you need to temporarily boot twrp
White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
Hi @White_devil_04200
Thank you for redirecting me to this Telegram channel.
However, let me share that - On the channel, I found "twrp-3.3.1-1-PL2.img" listed as the TWRP image that works.
The conflict is that - I downloaded this version only from multiple sites & after flashing it, got stuck on TWRP splash screen. I had to use OSA tool to reflash Android OS & restore the stock recovery.
And, when I ran the code -
Code:
fastboot boot twrp.img
, then also I got stuck on the splash screen, but was able to reboot into the OS successfully.
Note: Also, I tried switching the slots too (from 'a' to 'b' or vice versa') but then also, nothing worked for me.
I hope you get my problem, and would now assist me accordingly.
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
For potential readers of this thread, I would like to explain one thing here.
"fastboot flash recovery twrp.img" does NOT change your stock recovery on Nokia 6.1. Because this phone has "A/B system updates" and due to that the recovery RAM disk is now contained in the boot.img file. So Nokia 6.1 has not recovery partition so if you execute the "fastboot flash recovery twrp.img" command it only shows an error message and nothing is changed on your device.
Common issue on Nokia 6.1 is that when you execute only this one command "fastboot boot twrp.img" then it stucks on androidone logo.
But for some special reason, if you execute "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" it successfully boots into TWRP recovery.
Really there is nothing to worry about. This procedure is safe and really works.
White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
And also wipe data with help of fastboot ! Yes it is important if you facing stuck on twrp logo
mAnN14 said:
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
Click to expand...
Click to collapse
Hi,
which file did you use at the end? i have the same problem..
AndreaMariaBono said:
Hi,
which file did you use at the end? i have the same problem..
Click to expand...
Click to collapse
Let me try and find that file link again bro. It's been time I performed the root process, so I will have to search for it.
Will share it with you at the earliest.
Till then, stay calm and be safe.
Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
sayanmitra753 said:
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
Click to expand...
Click to collapse
I don't think it works...
MricCall said:
I don't think it works...
Click to expand...
Click to collapse
Bro it works in real..i am using it on my device
use comand
adb erase userdata
then
adb erase system
adb arase vendor
then fastboot reboot
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
N0t3xx_A said:
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
Click to expand...
Click to collapse
"fastboot flash boot recovery.img" and reboot into recover using Vol+ & Power.
I have a LE 2125, didn't like what OOs12 did ( no Android Auto, worse battery life), so I replaced the ROM with Lineage OS 18.1. THAT broke even more things, especially banking apps, ( and still no Android Auto) due to it needing to be unlocked ( but not rooted). Tried factory reset and flashing the OEM recovery. Now I have that in slot b and the Lineage recovery in slot A. Now the phone cannot go into EDL, by pushing the volume buttons I can bring it into Lineage recovery, OR the stock Recovery if I go to Fastboot. I am so confused with how to install TWRP to regain control of my phone.
All the instructions for installing Magisk, or TWRP ( twrp used to be easy to install, either flashing or from the OS) or using MSM seem to be written by programmers talking to other programmers, ie too much knowledge is assumed when giving steps or making references to other things.
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
When I connect my phone to the USB cable ( stock Oneplus red one connected to USB2.0 port) it brings up the Oneplus logo for about 10 seconds, then blinks, then after 10 more seconds goes blank, then after 5 seconds the pattern repeats.
I am not exactly a noob at this, I installed many OSes on my previous Oneplus ( One, X, 3T, 6T) phones, but none with this slot a/b thing. Admittedly my last OS replacement was on my 6T so it has been a few years, and my how things have changed!
coolvan170 said:
I have a LE 2125, didn't like what OOs12 did ( no Android Auto, worse battery life), so I replaced the ROM with Lineage OS 18.1. THAT broke even more things, especially banking apps, ( and still no Android Auto) due to it needing to be unlocked ( but not rooted). Tried factory reset and flashing the OEM recovery. Now I have that in slot b and the Lineage recovery in slot A. Now the phone cannot go into EDL, by pushing the volume buttons I can bring it into Lineage recovery, OR the stock Recovery if I go to Fastboot. I am so confused with how to install TWRP to regain control of my phone.
All the instructions for installing Magisk, or TWRP ( twrp used to be easy to install, either flashing or from the OS) or using MSM seem to be written by programmers talking to other programs, ie too much knowledge is assumed when giving steps or making reverences to other things.
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
When I connect my phone to the USB cable ( stock Oneplus red one connected to USB2.0 port) it brings up the Oneplus logo for about 10 seconds, then blinks, then after 10 more seconds goes blank, then after 5 seconds the pattern repeats.
I am not exactly a noob at this, I installed many OSes on my previous Oneplus ( One, X, 3T, 6T) phones, but none with this slot a/b thing. Admittedly my last OS replacement was on my 6T so it has been a few years, and my how things have changed!
Click to expand...
Click to collapse
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
TheGhost1951 said:
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
Click to expand...
Click to collapse
That is one of my problems – I cannot find the image file for my device. All the links I followed lead me to source code which I must compile myself. The TWRP installer 3.6.2_11-0-lemonadep zip RAMdisk-twrp.cpio, magisk boot file which is only 300 K bites and a meta-info folder. But it is a zip file not an image file.
Post in thread '[RECOVERY] [3.7.0-12.1] [UNOFFICIAL] TWRP with A12/A13 encryption support' https://forum.xda-developers.com/t/...-a13-encryption-support.4523857/post-87793789
Thus is the latest twrp(unofficial, but decrypts and all functions work) by @der_akinator. U must flash vendor_boot.img 1st, then BOOT boot.img. Then once u get in twrp u can go to advanced and install "latest twrp" permantly if you please. However after that u are suppose to go back to fastboot and flash your stock vendor_boot, for your system to work. However, since you're isn't and you are going to use twrp to install rom/OS I think you can skip last part(stock vendor_boot flashing)
TheGhost1951 said:
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
Click to expand...
Click to collapse
cant get fastboot to work, but ADB sideload does.
coolvan170 said:
cant get fastboot to work, but ADB sideload does.
Click to expand...
Click to collapse
Then for the sake of giving yourself all options possible, I would work on getting fastboot working first.
TheGhost1951 said:
Then for the sake of giving yourself all options possible, I would work on getting fastboot working first.
Click to expand...
Click to collapse
Found the QPST tool so I will try with that.
Shooter7889 said:
Post in thread '[RECOVERY] [3.7.0-12.1] [UNOFFICIAL] TWRP with A12/A13 encryption support' https://forum.xda-developers.com/t/...-a13-encryption-support.4523857/post-87793789
Thus is the latest twrp(unofficial, but decrypts and all functions work) by @der_akinator. U must flash vendor_boot.img 1st, then BOOT boot.img. Then once u get in twrp u can go to advanced and install "latest twrp" permantly if you please. However after that u are suppose to go back to fastboot and flash your stock vendor_boot, for your system to work. However, since you're isn't and you are going to use twrp to install rom/OS I think you can skip last part(stock vendor_boot flashing)
Click to expand...
Click to collapse
I found the QPST tool I will try working with that.
coolvan170 said:
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
Click to expand...
Click to collapse
The PC running MSM should be in "test mode" with driver signing disabled. Then MSM will see your phone.
Skynet30 said:
The PC running MSM should be in "test mode" with driver signing disabled. Then MSM will see your phone.
Click to expand...
Click to collapse
Also you can try to side load TWRP img then use TWRP to boot into EDL mode...
The problem with the new A/B Slot solution is (2) things need to match in order to initiate a correct OS boot:
A Stock or (Working) Custom recovery.img
A Stock boot.img
This need to exist in both slots (A & B)
When in a Bootloop, your device is responding to a mismatch of at least one of these, causing corruption and a looping response.
I've made the same mistake and accidentally soft-bricked (what you're currently experiencing) on both my Oneplus 8 Pro and Oneplus 10 Pro
e.g.
Once in Fastboot mode, try flashing a clean boot and recovery to BOTH slots like this :
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Try following my guide here to get things on track via Fastboot Mode:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713
TheGhost1951 said:
Also you can try to side load TWRP img then use TWRP to boot into EDL mode...
Click to expand...
Click to collapse
Also, be sure you have the correct Qualcomm drivers typically packaged with an MSMTool+Stock ROM
Fwiw. Android auto has worked fine on a11, a12, and a13. Wired and wireless. Multiple head units. Wired is picky with cable however. Bluetooth and wifi both need to be on for wireless.