Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
snOwjAwk said:
Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
Click to expand...
Click to collapse
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
zfk110 said:
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Click to expand...
Click to collapse
I tried to install twrp but ran into this error (on mac):
booting...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
EDIT:
Tried it from a windows pc now, got another error:
creating boot image...
creating boot image - 11765760 bytes
Sending 'boot.img' (11490 KB) OKAY [ 0.495s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Phalanx7621 said:
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Click to expand...
Click to collapse
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
snOwjAwk said:
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
Click to expand...
Click to collapse
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
zfk110 said:
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
Click to expand...
Click to collapse
Bootloader is unlocked! That's why im curious why it doesnt work...
snOwjAwk said:
Bootloader is unlocked! That's why im curious why it doesnt work...
Click to expand...
Click to collapse
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
zfk110 said:
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
Click to expand...
Click to collapse
That's what I did... And there was no other USB device connected other than the pixel. Fastboot devices also only showed my device
Related
Dear folks,
today I ran into a problem while trying to root my new LG G4 (H815).
It seems I succesfully unlocked my bootloader since it writes "BOOTLOADER STATUS: UNLOCKED" at every startup.
Now I tried to install TWRP recovery; I downloaded the newest version for my device from the official TWRP website.
I used the following command:
Code:
fastboot flash recovery twrp.img
I got the following output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (31620 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 1.226s
Then I left fastboot via
Code:
fastboot reboot
.
But when I try to boot into recovery mode via
Code:
adb reboot recovery
I just get a picture of a broken android figure with a red triangle over its chest.
When I use the hardware key combinations and then answer "YES" it simply does a default factory reset.
I'm using elementaryOS 0.3 (based on Ubuntu Linux). I already tried different ways (with or without sudo, using the adb version which comes with the full Android SDK or the version featured in the Ubuntu repositories).
Nothing seems to work...
I hope I described my problem right and you can help me.
Thanks for all replys and greetings from Germany.
EDIT:
I now got into recovery using
Code:
fastboot boot twrp.img
.
From there I installed stock-20a-rooted.zip. That seemed to work. But when I boot the phone normally it just shows me the LG logo forever and doesn't boot into normal os. Only removing the battery gets it off again. Factory reset doesn't help either.
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
DerPedde said:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
Click to expand...
Click to collapse
I did that but now I get a bootloop while starting the normal os. Factory reset doesn't help.
Update: When I connect my device with my PC while the bootloop is active, sometimes a Window pops up on my desktop asking for my PIN to unlock it. When I enter it nothing happens.
Ouch...corrupt twrp.img file?
---------- Post added at 12:49 PM ---------- Previous post was at 12:42 PM ----------
So maybe its best to start all over again...get into download mode via holding volume up and Power on. Then install original kdz via LGUP tool. Maybe you have a look at the german Android Hilfe forum, there are also the kdz files for download. Good luck!
DerPedde said:
Ouch...corrupt twrp.img file?
Click to expand...
Click to collapse
Maybe... While in TWRP it looked like always...
EDIT:
Yes, I'm just downloading the KDZ files... Gonna flash it today. However, Thanks for your support!
I just succesfully installed autoroot kernel, flashing kdz was the solution. However, I still can't write TWRP into recovery partition, but at least I got what I wanted.
Thanks for your support!
you can write twrp by using twrp manager from playstore(2.8.7.0) then when you're IN recovery flash 3.0.0.0 (download from official twrp site or from orginal android development of LG G4) or use in adb fastboot boot (recovery).img
HELP!
DerPedde said:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
Click to expand...
Click to collapse
Hi everybody. I'm a newbie in root, xda and forums in general, so please don't shoot me and help me if you can..
I rooted my lg g4 te first time thanks xda, but after having installed nougat via twrp, root is missing in any check, and twrp can be installed but not launched in fastboot. I tried EVERY guide i found in xda, but that famous command "fastboot boot something.img" is still not working... any idea?
Thanks
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.
Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Code:
D:\Programs\Minimal ADB and Fastboot>fastboot.exe flash recovery twrp-3.1.1-0-addison.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11374 KB)...
OKAY [ 0.255s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.246s]
finished. total time: 0.510s
Is there a way to avoid this error ?
Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.
FSabbane said:
Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Is there a way to avoid this error ?
Click to expand...
Click to collapse
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.
Jimi Mack said:
Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.
Click to expand...
Click to collapse
I've changed the filename to "twrp.img" and used the command:
Code:
fastboot flash recovery twrp.img
The output is exactly the same as before.
Kap_Tutan said:
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.
Click to expand...
Click to collapse
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.
FSabbane said:
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.
Click to expand...
Click to collapse
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work
Kap_Tutan said:
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work
Click to expand...
Click to collapse
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?
FSabbane said:
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?
Click to expand...
Click to collapse
Did u unlock bootloader?
Yap it should be in pc adb folder
Kap_Tutan said:
Did u unlock bootloader?
Yap it should be in pc adb folder
Click to expand...
Click to collapse
Yes, I did unlock it with the unlock key received from motorola:
Code:
fastboot oem unlock UNLOCK_KEY
After that a message is displayed at each start:
your device has been unlocked and can't be trusted
ID: bad key
your device will boot in 5 seconds
Click to expand...
Click to collapse
FSabbane said:
Yes, I did unlock it with the unlock key received from motorola:
After that a message is displayed at each start:
Click to expand...
Click to collapse
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.
flashallthetime said:
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.
Click to expand...
Click to collapse
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !
still doesn't work for me
FSabbane said:
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !
Click to expand...
Click to collapse
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
This is not an error. If your bootloader is unlocked this message will display at every boot.
velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.
FSabbane said:
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.
Click to expand...
Click to collapse
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?
velpoori said:
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?
Click to expand...
Click to collapse
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?
FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?
Click to expand...
Click to collapse
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.
velpoori said:
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.
Click to expand...
Click to collapse
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.
FSabbane said:
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.
Click to expand...
Click to collapse
I will try once I reach home by 6pm, you are so helpful thank you...
FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
Click to expand...
Click to collapse
It makes no sense then to flash it. Why don't you just use
fastboot boot twrp.img
when you want to start it? Then no flash will be involved, and twrp will be just booted for this single usage. You can repeat this whenever you need it.
I'm attempting to flash the initial image via fastboot to get into twrp so I can flash it and root but when I do it I get an error saying FAILED (remote: partition [recovery] doesn't exist) also when i try to swap slots to b with the -set-active= b command it says waiting for device and nothing happens... even if i unplug and replug the phone in and hear the sound it makes when its connected the bootloader is unlocked and im currently running 7.1.2 also when i try to switch firmwares it only flashes to one
You dont flash the initial .img file. You boot to it after copying the twrp zip to your phone.
Fastboot boot TWRPfilename.img
Using the real filename of course.
Then in TWRP you install the zip.
TonikJDK said:
You dont flash the initial .img file. You boot to it after copying the twrp zip to your phone.
Fastboot boot TWRPfilename.img
Using the real filename of course.
Then in TWRP you install the zip.
Click to expand...
Click to collapse
thanks lol sorry i must have been having a blonde moment xD but at any rate do you know why fastboot wont swap the slots? but twrp swapped it sucessfully
Veid71 said:
thanks lol sorry i must have been having a blonde moment xD but at any rate do you know why fastboot wont swap the slots? but twrp swapped it sucessfully
Click to expand...
Click to collapse
Guessing.....your fastboot is old, or you are using Minimal maybe.
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.