Hi
I've been trying to go back to stock android using this post. I downloaded both the stock image and recovery.img, but I was stuck in a bootloop, constantly booting into TWRP. I tried one of two different images until H87020A finally worked. I flashed it using LG's download mode and LGUIP/Uppercut. I setup my phone etc, and then flashed H87020G using LGUIP/Uppercut. Now I'm on a working version V20G.
The only thing that doesn't work is recovery. I first tried the stock recovery that comes with the KDZs, but it keeps saying "No command" when I boot into recovery. Then I flashed latest TWRP (3.2.3) using fastboot and it showed succesful, but when booting into it I keep getting the "no command" error.
So now I have a few questions:
1. How can I get TWRP working on it? Should I keep flashing with fastboot until it works?
2. How can I extract a stock recovery imgage from the 20g KDZ I flashed? I tried using this extractor tool to get the DZ and finally the recvery.img, but there is no recovery.img. It consists only of recovery_10246.bin and recoverybak_20614.bin (and of course a bunch of other files, but none of them are called recovery)? I want to use the closest stock recovery.img to the KDZ I'm using so that there are no issues. I found one from V20B from Westworld24, but I'm not sure if that works fine with my version of Android.
3. Assuming I get TWRP to install, then flash the stock recovery using TWRP, can I then simply run "fastboot oem lock" in fastboot or do I need to do something else? Is it essential to flash a clean ROM first or can I just do it over the KDZ I flashed?
The reason I want to do this is because I wanna sell it on rebuy.com and I'm not sure whether they're fine with an unlocked phone. Also, when starting the LastPass app for the first time it says that it seems that my phone is rooted, so basically I'm not on a fully stock phone, which I want to be on when selling it.
Thanks in advance.
Related
So here's my story.
My device is :
S-ON, 4.4.4 Droid stock, 3.29.161.9.
Yesterday i tried to get root while keeping stock rom for no tampered msg at bootloader.
I was following guide from http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278
so with unlocked bootloader i tried to fastboot boot CWM recovery image.
and it hanged my phone as everyone reported for > 4.4.3 ..... so i gave up for this time.
Today i was in mood for flashing some custom rom and then rooting, but with TWRP(newest 2.8.3.0).
just for gigles i tried to fastboot boot newest twrp. only thing i did was renaming .img file to recovery.img.
guess what? it worked! so i got root, reboot and started enjoying not tampered stock
So now im sharing this lil'christmas story with you.
Of course if it's irrevelant or already found please delete this topic.
happy christmas nevertheless.!
i'm on 4.1.1 and can't install room with 4.4.4 cus it's request 3.28.401.6 firmware or above and when i do it and trying
fastboot boot recovery.img
Click to expand...
Click to collapse
i can touch the recovery screen but cant see what i'm doing.
now using TWRP 2.8.3.0 the phone just doing reset and not going to recovery
any advice?
Plomiwn said:
...
just for gigles i tried to fastboot boot newest twrp. only thing i did was renaming .img file to recovery.img.
guess what? it worked! ...
Click to expand...
Click to collapse
Oh, really...?
Merry Christmas to you.
mb0 said:
i'm on 4.1.1 and can't install room with 4.4.4 cus it's request 3.28.401.6 firmware or above and when i do it and trying i can touch the recovery screen but cant see what i'm doing.
now using TWRP 2.8.3.0 the phone just doing reset and not going to recovery
any advice?
Click to expand...
Click to collapse
Use older recovery. That one has new display drivers.
Merry Christmas to you too.
Sent from my HTC One_M8 using Tapatalk
this is what i get when upgrading the firmware http://oi58.tinypic.com/e0jxqq.jpg
was using Stock Firmware + NoRedText Hboot from here: http://forum.xda-developers.com/htc-one-m8/development/ota-3-28-401-6-t2899900
been trying the following recovery files:
openrecovery-twrp-2.7.0.1-m8 - not working, screen stuck in fastboot
openrecovery-twrp-2.8.0.0-m8 - going reset
* to be clear: this "no display" in the recovery thing happening only after i flash InsertCoin 5.0.6 http://insertcoin-roms.org/2014/12/...rol-market-ota-icon-packs-stable-performance/
(haven't flashed another room yet)
now i need do what i always do when this happen:
- fastboot oem rebootRUU
- fastboot flash zip 2.22.401.4-Firmware-noredtext
after that go back to recovery and restore the backup i made before.
mb0 said:
this is what i get when upgrading the firmware http://oi58.tinypic.com/e0jxqq.jpg
was using Stock Firmware + NoRedText Hboot from here: http://forum.xda-developers.com/htc-one-m8/development/ota-3-28-401-6-t2899900
been trying the following recovery files:
openrecovery-twrp-2.7.0.1-m8 - not working, screen stuck in fastboot
openrecovery-twrp-2.8.0.0-m8 - going reset
* to be clear: this "no display" in the recovery thing happening only after i flash InsertCoin 5.0.6 http://insertcoin-roms.org/2014/12/...rol-market-ota-icon-packs-stable-performance/
(haven't flashed another room yet)
now i need do what i always do when this happen:
- fastboot oem rebootRUU
- fastboot flash zip 2.22.401.4-Firmware-noredtext
after that go back to recovery and restore the backup i made before.
Click to expand...
Click to collapse
not sure what your point is ? this thread is about booting the LATEST twrp on the LATEST firmware because older ones couldn't boot but could only be flashed.
Hi everyone,
I've run out of ideas on this one and other threads couldn't really help me/were closed already.
I tried CM, stock android by Ivan and M1cha as well as some others, but about a month ago, I was curios for MIUI 6 based on Lollipop for my Mi2s and changed from M1cha's CM12 5.0.1.
Now that I've seen that Ivan published his 5.1.1 I wanted to try it out. He also provides us with a modified custom recovery that I wanted to flash.
First, I renamed the file to update.zip and tried to flash it in Mi-Recovery 2.0.1, which didn't work due to the failing signature verification.
Also, choosing update package in the Updater app in MIUI didn't work out, it immediately tells me something went wrong.
Then I thought, why not use fastboot? That worked before.
Not this time. I tried the simple way, meaning just fastboot flash recovery recovery.img: Then, bc it didn't work, I first erased the recovery partition and then flashed the recovery.img, which was still unsuccessful.
Whenever I try to enter recovery mode, my phone just gets stuck showing the MI logo and not doing anything.
I can reenter fastboot mode or simply reboot to the system as usual, except for when no system is installed.
When I gave up on the custom recovery thing, I simply tried to flash the ROM via update.zip methods, as well as via fastboot. None of them worked, either because the signature verification fails (stock recovery) or because the zip file does not contain the android-info.txt and the other txt file.
As mentioned above, upon entering fastboot -w and then flashing the recovery.img, I can suddenly enter recovery mode. This sucks!
TL;DR: No usual method of flashing either custom rom or recovery works (to my knowledge)
Can anyone help me? I know its stupid but I start feeling kind of boxed in on MIUI.
Thanks in advance
fastboot oem unlock
fastboot flash recovery recovery.img
unfortunately, that didn't work either...
leonfromotown said:
unfortunately, that didn't work either...
Click to expand...
Click to collapse
Do fastboot devices and tell us the output
SkiFire13 said:
Do fastboot devices and tell us the output
Click to expand...
Click to collapse
5b799fb fastboot
looks just the way it did before
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
You don't flash a factory image in TWRP. Unzip the file and flash the individual images: boot, system, and vendor. Try that method or use ADB sideload to install the full OTA image. Full OTA images can be downloaded from the same site.
Sent from my Nexus 5X using Tapatalk
I'm assuming you have ADB / fastboot in place (if not, google it): unzip your factory image to a given folder. Navigate to this folder using prompt / terminal. Turn on your phone with vol down pressed and leave it at that screen. Plug it onto your computer and type fastboot devices - you should see a line with a bunch of numbers. If Windows, run flash-all.bat. If Mac / Linux, run flash-all.sh. Your phone should get back to life in a few, sit back and relax.
Tiffiter said:
Hi all,
I grabbed the latest factory build from here <https://developers.google.com/android/images#angler> and the latest TWRP recovery from here <https://dl.twrp.me/angler/>
I then proceeded to boot into recovery, formatted my entire system (including userdata), flashed the latest recovery, copied over the 8.0.0 build and the latest GAAPS, and then attempted to flash the factory image.
Unfortunately, this is where I've now gotten stuck. TWRP replies with my flash command with "invalid zip file format" and refuses to install.
I've attempted to go back to an old recovery and re-install build N4F26J, which also gets "invalid zip file format".
I also have a full TWRP backup from build N4F26J with 3 variations: Boot-System-Data, Boot-System-SysImage-Data, and Boot-System-SysImage-Vendor-Data-Cache-Recovery, but all 3 of them result in a frozen boot animation.
tl;dr: Anyone have an idea of what I can do to get a working factory image back onto my phone? Currently am stuck with a bootlooping backup image and a zip error warning when installing a new image (regardless of image version).
Thanks in advance!
Click to expand...
Click to collapse
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
wizardwiz said:
As already mentioned, you can't flash factory images via TWRP.
Get ADB and use the flash-all.bat that comes with the factory image to clean install your OS.
Just go to bootloader mode and run the file.
Bear in mind it will WIPE all your device.
Click to expand...
Click to collapse
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
ultyrunner said:
Actually that's partially incorrect. You have to flash bootloader and radio via fastboot. You can flash boot, system and vendor with TWRP (choosing img option) and, provided you root before booting, you can preserve the custom recovery.
Click to expand...
Click to collapse
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked.
I wasn't talking about using a manual fastboot option to flash an indevidual image.
wizardwiz said:
Flashing factory images using flash-all.bat (or .sh) will flash ALL OS including modem, bootloader and everything else.
He can't use this method if his bootloader is locked. I wasn't talking about using a manual fastboot option to flash an indevidual image.
Click to expand...
Click to collapse
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
ultyrunner said:
In his original post he doesn't say anything about having a locked BL. As well, if he's stuck the way he is then perhaps you should have given him better information. It'd give him far more control if you directed him to the unlock/root/flash guide, which gives him more options (and more control via flashing individual partitions via fastboot) at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
Click to expand...
Click to collapse
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
wizardwiz said:
We're not in a contest, buddy. Just trying to help that guy.
He can simply choose the best option for him to get his device up and running.
If he is familiar with fastboot image flashing then by all do means he can use your method.
He is stuck with no OS installed and using flash-all.bat file is the easiest way to get his device boot properly.
Click to expand...
Click to collapse
No we're not in competition. My point was you gave him one option with the least control and not remotely the best option to get his device up and running, particularly making an assumption he has a locked bootloader, when you never asked. If he is able to use a command line to run a flash command, then pointing him to the guide is the best bet. If something goes wrong with flash-all scripts then he's probably going to be really lost.
I installed TWRP custom recovery on my Nexus 6P. I was able to boot into it ONCE. When i next tried to enter Recovery, i get a screen showing the Android Robot and the following statement: NO COMMAND
I tried to re-install TWRP using adb twice, but the result is the same.
How can i either fix TWRP, or re-install the stock recovery
I am basically a beginner here, so any help would be appreciated
If you installed the stock system image and then booted into it, it likely automatically reinstalled stock recovery also. I don't know why it does that, but it does. This is why I usually just reinstall TWRP again after each monthly update is completed.
You should use fastboot to install the images, not adb. The command should look like:
fastboot flash recovery twrp.img
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
When you say it didn't work, can you expand on that? Was there an error or anything?
hmodiano said:
I think i just worded it wrong - I used the above command (fastboot flash recovery twrp.img) to install twrp, and then, when i couldn't get back into recovery (Power - Volume Up combo just lest to screen that stated "No Command".), i used the fastboot flash recovery twrp.imp twice to try to re-install TWRP, but it didn't work
I also downloaded the latest stock Oreo ROM, copied the recovery.img file, and used fastboot.flash.recovery.img to try to re-install the stock recovery, but that didn't work either
The once time that TWRP work, it asked it I wanted to use TWRP is read only, to twice i selected NO (don't know if this matters)
Any other suggestions to fix TWPR, or re-install the stock recovery image???
Click to expand...
Click to collapse
If you want TWRP to stick, you need to flash either SuperSU or magisk. The Android with the exclamation mark is what stock recovery looks like.
Once you have TWRP installed and wish to keep it, you don't need to flash stock recovery in the monthly update. Just boot into TWRP after flashing update and root again.
chaoticyeshua said:
When you say it didn't work, can you expand on that? Was there an error or anything?
Click to expand...
Click to collapse
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
hmodiano said:
When the phone is turned on, it never progresses beyond the first screen. No error codes, it just does not proceed to boot up.
I had to buy a new phone (need it for business, but i given up on trying to install Resurrection Remix on the Nexus 6P, which was the reason I was trying to install TWPR and SuperSU. So far, I have only accomplished turning the phone into a brick door stop!!!
Click to expand...
Click to collapse
Use Magisk it's the better solution for root. Never had boot up issues with it just stock you have to boot once through before flashing. Custom ROMs you can flash right away.