Database Info

Weird Soft-Brick, Need Help!!!

Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!

akn4497 said:
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
Click to expand...
Click to collapse
I would flash the new RUU.

andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.

akn4497 said:
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
Click to expand...
Click to collapse
Why not use the new 5.0.1 RUU?

andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
andybones said:
Why not use the new 5.0.1 RUU?
Click to expand...
Click to collapse
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4

akn4497 said:
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
Click to expand...
Click to collapse
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU? Fastboot flash zip nameofRUU.zip

andybones said:
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU?
Click to expand...
Click to collapse
Oh shoot, I feel dumb. I'll let you know, thanks!

The RUU worked! I used the exe and I'm up and running. Thanks!!

akn4497 said:
The RUU worked! I used the exe and I'm up and running. Thanks!!
Click to expand...
Click to collapse
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.

cntryby429 said:
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
Click to expand...
Click to collapse
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks

akn4497 said:
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
Click to expand...
Click to collapse
Glad to hear you're up and running my friend.

[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1

Code:
Warning! any damage done to your device is not my fault, use at your own risk!
This zip should be used mainly if you wiped system for some reason and didn't back up, its TA-1060 May patch system image + kernel + vendor files
Unlocked bootloader required!
TWRP
1. Boot into TWRP
2. Format /data partition in TWRP
3. Use 'adb push ta_1060_oreo_may_18.zip /sdcard/' in windows/linux/mac
4. Go to sdcard in TWRP and flash ta_1060_oreo_may_18.zip
5. Reboot to bootloader
6. use 'fastboot flash recovery recovery.bin' (Link bellow)
7. Optional: fastboot oem lock
8. reboot
9. on boot you will get encryption, click on the reset button when android loads
10. You will reboot into recovery then back into system, done
Fastboot
1. Extract zip file
2. flash system.img, boot.img, vendor.img in fastboot
3. fastboot reboot
Links:
Stock ROM zip May
Recovery image
Good luck
XDA:DevDB Information
[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1, ROM for the Nokia 1
Contributors
sooti
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-06-27
Last Updated 2018-06-27

So we can flash either through TWRP or Fastboot right?

Zeenat11 said:
So we can flash either through TWRP or Fastboot right?
Click to expand...
Click to collapse
I haven't tested fastboot but it should work. TWRP works 100%

Thank you very much, you are a life saver!!
I was stuck in a TWRP loop.
I tried flashing through TWRP but it didn't work but the fastboot method worked like a charm!
My phone is running again.

Thank you very much.
Is there any userdata.img available?

alexstarc said:
Thank you very much.
Is there any userdata.img available?
Click to expand...
Click to collapse
Nope but do you really need it? just format in fastboot or TWRP.

sooti said:
Nope but do you really need it? just format in fastboot or TWRP.
Click to expand...
Click to collapse
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.

alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
I wrote in the instructions...
If you get a password just enter a random one, then it will ask you to wipe the device, click ok and it will reboot to recovery and then wipe userdata and boot fine.
just make sure you flash the recovery.bin and not twrp before you wipe

alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
Same happened to me. I solved it by a hard reset via the stock recovery.
Make sure you flash the recovery.bin like Sooti said.
Wiping through twrp doesn't work.

Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs

A little warning.
It looks like the recovery.bin I took from another nokia 1 device doesn't match the checksum check which causes a failed during ota updates, please only flash this rom if you soft bricked your device.
If anyone can get me TA-1060 stock recovery image that should solve it. for now you can't update the phone until a fix is found

I have Nokia Ta 1066. Will this rom work on mine? Also I read somewhere Ta 1060 is single sim variant. What about the second sim?
Has anyone with TA 1066 tried it?

Thanks. Both methods work fine. Don't ask how I found out.....

Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...

coolboyforeva said:
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
Click to expand...
Click to collapse
I don't have stock recovery from our device i have from another variant of Nokia 1

Hey guys i have a TA-1056 and after unlocking bootloader and flashing TWRP it booted to recovery and came up encrypted, after looking around the only solution was to format data, afterwards when rebooting it always boots to recovery, i tried flashing this zip and i get the same issue and i can't find the stock ROM for the 1056 anywhere online, can anyone help me out? i really appreciate it

Kurajmo said:
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
Click to expand...
Click to collapse
got any custom roms?

Does Nokia 1 support DT2W?

Sir, is that possible to get a stock rom of TA 1056 ?
I have searched everywhere but whole thing available over net just left my phone bricked. All i need is a working rom source. Even if that’s a custom rom too to flash via sp flash tool. Thanks in advance

Can any please repost the firmware , the link isn't working

Magisk uninstall, boots twrp won't boot back into phone OS

I was downloading a OTA update the other day & in preparation I thought I would go ahead & uninstall Magisk. Magisk asked me if I wanted to restore images or uninstall I just uninstalled, not ever having made a image before I didn't know what it was talking about.
The phone rebooted once then booted again into TWRP, I can't get back into my phones OS.
Later I couldn't get back into TWRP so I had to boot using the fastboot commands in Windows. I was able to see & "Backup" the contents of my phone to an external drive.
Now how do I get back into my phone like normal?
Do I need to flash an image or I've seen other threads they wipe the data & there phone boots?
Please advise.
Thank you

justinstrack said:
I was downloading a OTA update the other day & in preparation I thought I would go ahead & uninstall Magisk. Magisk asked me if I wanted to restore images or uninstall I just uninstalled, not ever having made a image before I didn't know what it was talking about.
The phone rebooted once then booted again into TWRP, I can't get back into my phones OS.
Later I couldn't get back into TWRP so I had to boot using the fastboot commands in Windows. I was able to see & "Backup" the contents of my phone to an external drive.
Now how do I get back into my phone like normal?
Do I need to flash an image or I've seen other threads they wipe the data & there phone boots?
Please advise.
Thank you
Click to expand...
Click to collapse
First of all, no need to uninstall Magisk - unnecessary and waste of time.
Once in TWRP (fastboot boot twrp.img, or via your phone if you still can) - flash OOS OTA update (as that was what you were trying to do).
Then flash TWRP, reboot TWRP. Now you can flash Magisk again (so you get root, since you removed it for some reason).
Everything should be fine.

only4dank said:
First of all, no need to uninstall Magisk - unnecessary and waste of time.
Once in TWRP (fastboot boot twrp.img, or via your phone if you still can) - flash OOS OTA update (as that was what you were trying to do).
Then flash TWRP, reboot TWRP. Now you can flash Magisk again (so you get root, since you removed it for some reason).
Everything should be fine.
Click to expand...
Click to collapse
Unfortunately now I can't get the "fastboot boot twrp.img" to boot into twrp? FAILED authentication.
Now what?
Fastboot devices work & the reboot function works, just can't boot twrp.img. I've seen somewhere I can maybe force boot the device idk if it will work. damn

justinstrack said:
Unfortunately now I can't get the "fastboot boot twrp.img" to boot into twrp? FAILED authentication.
Now what?
Fastboot devices work & the reboot function works, just can't boot twrp.img. I've seen somewhere I can maybe force boot the device idk if it will work. damn
Click to expand...
Click to collapse
Sorry to hear. You are going to have to provide logs of what commands you are typing into terminal, and what is the output.
So are you in TWRP or not. I literally have no idea what is going on with your device or what you are doing.
Next time, maybe check guides in this forum of how to do what you are doing.
Randomly uninstalling/installing/flashing/issuing commands via terminal/random backup and restores/etc.... does not sit well with android devices.

I'll try another pc tonight.

If you can get back to twrp you need to flash magik to boot normally

Still can't back into twrp. Failedremote: failed to load/authenicate boot image: Load error.)
Tried a different computer. Tried deleting my fastboot files on PC then copying them from a backup thinking I modified the twrp image wrong thinking this unmotified version would work, still nothing.
Can I get some advice links to guides. Thank you.

justinstrack said:
Still can't back into twrp. Failedremote: failed to load/authenicate boot image: Load error.)
Tried a different computer. Tried deleting my fastboot files on PC then copying them from a backup thinking I modified the twrp image wrong thinking this unmotified version would work, still nothing.
Can I get some advice links to guides. Thank you.
Click to expand...
Click to collapse
Still.... what are you typing into terminal... take a screen shot .....
ARE YOU SURE you are typing 'fastboot boot twrp.img' - BOOT, not FLASH!!!???

I'm now able to boot into twrp. Had to use fastboot --set-active=a. Worked great. Left it like that at home. I'm at work now.
What next?

justinstrack said:
I'm now able to boot into twrp. Had to use fastboot --set-active=a. Worked great. Left it like that at home. I'm at work now.
What next?
Click to expand...
Click to collapse
I would start by reading forum page 1 information about what you are trying to do.
I already explained to you the order to flash to make things work.
If that is not enough, once again, go learn what you are trying to do (via the forum thread).
You will probably save yourself these types of situations in the future if you understand what you are doing.
Good luck.

Everything is FULLY Operational Thank You. What a experience but Ive learned.

justinstrack said:
Everything is FULLY Operational Thank You. What a experience but Ive learned.
Click to expand...
Click to collapse
And not even a single thanks button hit or anything... Weird flex, but OK

I'm so sorry LOL. found it. Have a good day xda forum members, I found the button. THANK YOU

flashed TWRP over boot slot B

I ended up flashing TWRP over my boot slot (B) and now I just boot into TWRP. I have already installed TWRP on boot slot (a). I can't remember which version of oxygenOS I have installed and couldn't find a way to confirm. How can I fix this? Also want to update to latest version of oxygenOS and android. No data on phone yet. phone still connects to computer, adb sideloader and fastboot commands still work work. Thanks

Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.

redpoint73 said:
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
Click to expand...
Click to collapse
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks

doctor_whooves said:
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
Click to expand...
Click to collapse
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success

plasticarmyman said:
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
Click to expand...
Click to collapse
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.

tech_head said:
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
Click to expand...
Click to collapse
in this case the best thing to do is just unbrick using MSM

plasticarmyman said:
in this case the best thing to do is just unbrick using MSM
Click to expand...
Click to collapse
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.

doctor_whooves said:
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
Click to expand...
Click to collapse
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.

hey guys. Not able to flash oos through twrp.
getting "error flashing zip".

tech_head said:
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
Click to expand...
Click to collapse
Doesn't TWRP back up everything including boot partitions?
Is there nothing that will take the entire internal storage and just make a 'bare metal' image of it for restoring.. the whole entire thing, byte for byte? If not, why doesn't this exist? It just seems so logical to me and would be so incredibly useful. Phone borked? No problem. Just re-image it form the archive you made. To me, that is what TWRP is all about, at least conceptually if not technically.

[Help Needed] Semi Bricked - Remove substratum overlay or somehow backup my data

Hey Guys,
So my idiot brain decided to mess around with substatum themes after I updated and rerooted my OP7P. I rooted with magisk but forgot to put TWRP recovery on.
Anyways, got the phone semi bricked when applying one of the overlays. The phone boots and I can see my lock screen wallpaper but the screen is just flashing on/off.
I cant use the fingerprint or pin to get it. Is there a way for me to backup my pictures and data or somehow remove substratum?
Biggest problem is that for whatever reason, the update revoked my ADB authorization so it looks like I cant do anything with ADB.
If someone has any way to salvage my situation, please reply. Factory reset is my last resort due to no backup.
Thank You

Try booting into TWRP and using ADB there.

Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go

tech_head said:
Try booting into TWRP and using ADB there.
Click to expand...
Click to collapse
pranacrockz said:
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
Click to expand...
Click to collapse
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen

morphius88 said:
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
Click to expand...
Click to collapse
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool

pranacrockz said:
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
Click to expand...
Click to collapse
Rebooted to fastboot, entered the PIN but Fastboot is a no go. Just keeps saying <waiting for any device> and nothing happens. Would that be because the authorization keys were not accepted after the update?
I am downloading the MSM Tool and will try that if I cant get it to work with fastboot. Will update if it works.
Thanks for suggestions

Ended up using the MSM tool. Did not know it wipes data and also put me back to Android 9.
Oh well, lesson learned. Gotta make monthly backups, make sure twrp is installed and working before messing around with substatrum.
Thanks for the help.