Database Info

stock recovery corrupted

apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed

Mass1veDynam1c said:
apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Click to expand...
Click to collapse
same here. did you managed to work it out?

Solved
eelc said:
same here. did you managed to work it out?
Click to expand...
Click to collapse
Yes finally. You have to download the update file for whatever version of the rom you currently have installed. Then extract userdata, boot, system, and erecovery1 and erecovery2 images. Fastboot flash them in bootloader mode. Reboot device. Shutdown device. Boot to system recovery and do a full system restore. All set.

Mass1veDynam1c said:
Yes finally. You have to download the update file for whatever version of the rom you currently have installed. Then extract userdata, boot, system, and erecovery1 and erecovery2 images. Fastboot flash them in bootloader mode. Reboot device. Shutdown device. Boot to system recovery and do a full system restore. All set.
Click to expand...
Click to collapse
can u make the total tutorial video of this whole process ???

I would ask if you could post a link to the update you used and a list of the commands you used..im in the US ..so it is honor 6x for the US

bricked honor 6x
You need three softwares
1. huawei multi tool by mt,,,,, in english version bro
2. Huawei update extractor
3. Firmware file update .zip
First extract the zip file , there you will get update.app file . Extract BOOT.IMG RECOVERY.IMG SYSTEM.IMG USER DATA.IMG using Huawei extractor software .
NOW open huawei multitool app (internet connection required)
Put all these files you extracted in unbrick folder of huawei multi tool
Follow steps to unbrick your device
Thank you..

can you send the links please....thank you!

Mass1veDynam1c said:
apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Click to expand...
Click to collapse
Try to flash twrp first , later flash stock recovery from twrp by clicking on flash image . Be sure u are installing a working recovery but not a corrupted one

[Q] Google OG Pixel problems soft bricked

Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.

Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image

To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs

Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel

maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).

[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

Installed TWRP to Boot, want to boot myself in the a**.

Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.

https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

Thank you, the tool worked like a charm.
BTW: I did search and find other "methods" but none of them worked

noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.

MrSteelX said:
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
Click to expand...
Click to collapse
That is exactly what I wanted to do.
I could get into TWRP, but I couldn't see the phone on the PC and couldn't move files (ROM) to the phone (although fastboot was working and I could see the device using adb) but I couldn't figure out how to have TWRP look for or find the ROM on the PC.

There's no recovery partition on A/B phones remember.

RusherDude said:
There's no recovery partition on A/B phones remember.
Click to expand...
Click to collapse
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?

noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.

noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/

MrSteelX said:
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
Click to expand...
Click to collapse
Thanks.
I will give this a try. After I learn a little more about the A/B partitions & recovery on this phone, I want to try one on the custom ROMs.

pankspoo said:
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
Click to expand...
Click to collapse
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).

noncomjd said:
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
Click to expand...
Click to collapse
I have to unzip the downloaded fastboot ROM at any folder on computer and open that folder u will see named [flash all bat]
Now connect phone in fastboot mode to computer and just click [flash all bat] file

noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.

RusherDude said:
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
Click to expand...
Click to collapse
Thanks for the information.
and this is what I did, originally I thought I had accidentally selected the wrong partition, but it seems since there is no recovery partition, I did it wrong from the start.
Q: I'm guessing this is why when you do load TWRP (the correct way, which I did once, following a guide) without a custom ROM (still using Oxygen OS) that the OEM recovery overwrites TWRP or the OEM recovery is called up at the next reboot into recovery?
Q: I understand, at least in theory the benefit of the A/B partitions, what is the benefit of eliminating the recovery partition other than giving more control of the phone to the OEM and OS? Is this setup limited to the stock kernel or mandated to be copied by any potential replacement kernels (this information is new to me, I haven't yet read up on kernels).

Badly f*d Op7Pro. Need help to revert to stock

Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.

If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.

Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?

MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.

Boot into twrp. Then format data. Phone will boot then.