Database Info

[Q] Moto G - TWRP/CWM Do Not Open in Bootmode

I've followed instructions to unlock my bootloader which is done. I'm not sure if - "Device is unlocked. Status Code 3:" is correct or not, but that is what I see.
After unlocking I flashed TWRP 2.6.3.0-xt1032.img and it flashed correctly according to adb (attached). When I reboot the phone into bootloader and select recovery the screen just goes blank. I also tried "recovery-clockwork-touch-6.0.4.7-falcon.img", which seemed to flash OK in adb. The bootloader screen goes blank when I select recovery on the phone for CWM as well.
Both recovery flashes showed a similar result on the phone - this paste is for CWM
In Moto bootmode:
USB Connected
cmd: getvarartition-type:recovery
cmd: getvar:max-download-size
cmd: download:07b2000
cmd: flash:recovery
Mismatched partition zize (recovery)
The phone has stock Android 5.0.2 installed and still works, but I can't get any further than flashing the recovery image in adb. I did flash the logo.bin in adb and it seemed to flash correctly .
I'm running Windows 8.1, USB 3 ports.
Is there something I'm missing, or a different way to do the root? I'm stuck at this point, but luckily can run with the stock ROM for now.
I would appreciate any help I can get, Thanks

both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

koshikas said:
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks

jjcdennis said:
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
Click to expand...
Click to collapse
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries

koshikas said:
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
Click to expand...
Click to collapse
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks

jjcdennis said:
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
Click to expand...
Click to collapse
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.

koshikas said:
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
Click to expand...
Click to collapse
Thanks again.
If I find a correct ROM (I do have a KitKat 4.4.4 version), do I flash back with adb, or with mfastbootv2?
The ROM I showed was from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
I have also found a firmware link on this thread "http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795" that looks to be in the correct format. There are thorough instructions on how to flash the firmware, but I am not sure if this will fix my issue or not.
Would appreciate any advice on how to proceed.
Thanks

I finally understood your comment "...can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries". I got a copy of the stock firmware, extracted the recovery from it and flashed it via adb to the phone - ok. I then tried to get into phone fastboot recovery, but was faced with the blank screen again. I flashed twrp 2.8.7.0 and the same thing in fastboot recovery - blank screen. I also tried cwm 6.0.5.1 and the same thing, blank screen.
ADB sees the device and accepts the commands, but the Motorola fastboot recovery doesn't open any of the recoveries. Nothing else in the bootloader seems to work ie: Factory - blank screen.
Every one of the recovery files other than the stock recovery shows a pink colored error "Mismatched partition size (recovery).
Anybody have any ideas as to what I can do to get a recovery to work?
Is there a different way to root this phone?

@jjcdennis i think you should post this to one of the active threads, since nobody with experience (this is well beyond mine) has dropped in yet. i would highly recommend; http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

Moved to http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

[Q/Help]Bricked XT1032, not visible in ADB

I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?

fillion_f said:
I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?
Click to expand...
Click to collapse
You need to use the mfastboot method. Check this tutorial: http://forum.xda-developers.com/showpost.php?p=47820707. Download the firmware (ideally 4.4.2 or 4.4.3) in *.xml.zip format, and do all the steps at the tutorial. Skip 3a) and go to 3b) - the one with mfastboot commands.
That's what helped me when I accidentally deleted my system - I also made a thread: http://forum.xda-developers.com/moto-g/help/bricked-moto-g-xt1032-converted-to-gpe-t3054655.

fillion_f said:
I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?
Click to expand...
Click to collapse
Ya.. Using mfastboot and typing out those commands as given in tuitorial you can install stock firmware to your phone using the Adb.. Its not hard bricked. Don't worry. Had faced the same issue last month.
Sent from my Moto G using Tapatalk

I cannot flash sparsechunk 1,2 and 3 files, but it can be ROM's fault. I'll download another one to check if its working
EDIT: using another ROM worked for me, thanks for help

Debanka said:
Ya.. Using mfastboot and typing out those commands as given in tuitorial you can install stock firmware to your phone using the Adb.. Its not hard bricked. Don't worry. Had faced the same issue last month.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Sorry for pushing this old thread.
My phone is also stucked, adb cannot find my device. How do I do it then? If my device is not listed, is it possible using fastboot to get back to the old stock Firmware?

How to Downgrade bootloader 41.1A to 41.18 or 41.19

please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you

Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help

Why do you need to downgrade? Messing with Bootloaders can destroy your phone.

even i want to downgrade... I cant flash custom recovery on 41.1A

poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.

Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...

@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.

kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).

I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk

I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too

SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.

How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!

Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?

_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.

Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.

_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.

Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.

_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)

Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.

I accidentally removed Bootloader on OnePlus One and softbricked it......

I ****ed up badly and I have no idea what to do. Someone.. help me? I used TWRP, I updated to CM13 and yet didn't come with GApps so I flashed the GApps with another Zip file but it kept giving me, "Set up Wizard has stopped working". How do I get bootloader back on my OnePlus one??? My boyfriend got it from hardbrick to softbrick but I need my phone to work by the 9th. Please help me.........

Wtf?! Why do you think the bootloader is gone?
Reboot back to TWRP, wipe system + data and reflash cm13 + gapps.
DO NOT REBOOT between flashing cm13 and gapps.

AcmE85 said:
Wtf?! Why do you think the bootloader is gone?
Reboot back to TWRP, wipe system + data and reflash cm13 + gapps.
DO NOT REBOOT between flashing cm13 and gapps.
Click to expand...
Click to collapse
We already tried that. Now stuck in bootloop.

w0lfy117 said:
We already tried that. Now stuck in bootloop.
Click to expand...
Click to collapse
Did you flash supersu too? If yes, repeat the above steps and don't do it.

AcmE85 said:
Did you flash supersu too? If yes, repeat the above steps and don't do it.
Click to expand...
Click to collapse
I don't have supersu installed. I had wiped and unrooted it after it was stuck on bootloop.

w0lfy117 said:
I ****ed up badly and I have no idea what to do. Someone.. help me? I used TWRP, I updated to CM13 and yet didn't come with GApps so I flashed the GApps with another Zip file but it kept giving me, "Set up Wizard has stopped working". How do I get bootloader back on my OnePlus one??? My boyfriend got it from hardbrick to softbrick but I need my phone to work by the 9th. Please help me.........
Click to expand...
Click to collapse
You never mentioned what gapps you flashed? Flash opengapps (full) and CM13 and do a full wipe (system, data and cache) and you should be fine. Don't flash Supersu if you're flashing CM13
Sent from my A0001 using Tapatalk

AcmE85 said:
Did you flash supersu too? If yes, repeat the above steps and don't do it.
Click to expand...
Click to collapse
I plugged it into my laptop and then wiped everything. I installed CM12 and flashed it. Was still on bootloop. I could only go into fastboot mode.

Renosh said:
You never mentioned what gapps you flashed? Flash opengapps (full) and CM13 and do a full wipe (system, data and cache) and you should be fine. Don't flash Supersu if you're flashing CM13
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
The GApps for CM13.

w0lfy117 said:
I plugged it into my laptop and then wiped everything. I installed CM12 and flashed it. Was still on bootloop. I could only go into fastboot mode.
Click to expand...
Click to collapse
I would strongly recommend going back to stock rom. This way you can ensure the device itself is not broken or damaged.
Since only fastboot can be entered you should download the CyanogenOS fastboot package from https://cyngn.com/support and flash it with the install script. Please note that cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip is the right pack to flash since no root comes with it.

You should download this file from https://cyngn.com/support cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip
and have Drivers installed, ADB,Fastboot (Android SDK)too.
Chromium said:
[*] Driver Installation - Download and install the Universal ADB Driver. Alternatively, use this method.
Click to expand...
Click to collapse
Or Just let your Windows handle this.
Android SDK - you can download SDK manager(141MB) here and let him download platformtools only or download my attached rar file (2 MB), where is platform tools that u need.
Extract CM fastboot zip to your adb,fastboot folder (mine is: .....\sdk\platform-tools ), run your phone in download (fastboot mode), ofcourse connect it to pc .
Open CMD in that folder (Shift+Right click and open new cmd window here)
Check if its connected by running this command:
Code:
fastboot devices
if it show some device connected, then run these commands one by one:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
U can download TWRP or some else recovery and flash it too.
After that u wont loose any internal data, so i would recommend you full wipe except internal storage and flash some new rom + gapps.

gs-crash-24-7 said:
I would strongly recommend going back to stock rom. This way you can ensure the device itself is not broken or damaged.
Since only fastboot can be entered you should download the CyanogenOS fastboot package from https://cyngn.com/support and flash it with the install script. Please note that cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip is the right pack to flash since no root comes with it.
Click to expand...
Click to collapse
My boyfriend has tried every method possible. Even hard bricking it and then soft bricking it and then trying to recover everything. And it's just stuck on bootloop. Also.. I have tried to boot into bootloader and it only goes into fastboot mode and recovery. Nothing else. As if bootloader didn't exist at all. I'm very concerned and I'm freaking out...

Whatever he did, he did not hard brick it and then soft-bricked it afterwards.
If its hardbricked, you successfully turned it into a brick and there is no easy way to get it back.
I am 98% sure that the solution posted in post #10 works for you.
Instead of posting the same thing over and over, tell us what you tried so far and why it did not work.
Basic IT-Support 101.

w0lfy117 said:
My boyfriend has tried every method possible. Even hard bricking it and then soft bricking it and then trying to recover everything. And it's just stuck on bootloop. Also.. I have tried to boot into bootloader and it only goes into fastboot mode and recovery. Nothing else. As if bootloader didn't exist at all. I'm very concerned and I'm freaking out...
Click to expand...
Click to collapse
There is no bootloader mode on the Oneplus One, just fastboot and recovery. You can do everything you need from those two modes. Try the instructions on post 10
Sent from my A0001 using Tapatalk

keks411 said:
Whatever he did, he did not hard brick it and then soft-bricked it afterwards.
If its hardbricked, you successfully turned it into a brick and there is no easy way to get it back.
I am 98% sure that the solution posted in post #10 works for you.
Instead of posting the same thing over and over, tell us what you tried so far and why it did not work.
Basic IT-Support 101.
Click to expand...
Click to collapse
What I did was flash CM13. It didn't come with CM13 GApps. I flashed that after I noticed it. I still had CM12.1 on my SD card. Or so I thought. I wiped it and found out that I didn't have CM12.1 on my SD card anymore.
I downloaded bacon toolkit because my OnePlus One was then stuck on bootloop. I hadn't done a thing to it. Didn't set up adb or anything. I couldn't. Kept getting a pop up (right after I closed it, it would pop up again. Over and over) "set up wizard has stopped working". I couldn't even open the settings without it harassing me. I restarted my phone and the pop up kept coming back up. Once I wiped the CM13, I went to look for CM12.1. When I didn't have it, I realized that I wasn't going to be able to use my phone die to bootloop for an hour.
I used the Bacom Toolkit. Downloaded ADB.exe and worked my way up. I imputed the information. 64 GB, 12.1 CM and then it went on to loading the information for the toolkit.
When it didn't recongize it, I had to keep launching the ADB.exe to get the Toolkit to read the phone. Finally about 12 minutes or so into it, I clicked on bootloop/softbrick option and it lead me to some other options. When I read carefully through them, I had clicked on these (in order)
"Wipe"
"Install from zip"
"Installed 12.1Yoga(something numbers ;-; I forgot the exact name, I'll see if I find it tomorrow)"
"Unzipped"
"Pushed"
"Full unroot"
"Lock eom"
I was stuck on CyanogenMod.

Then now follow the instructions from post #10 and everything will be fine.

[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