Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
urbanman2004 said:
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
Click to expand...
Click to collapse
I've not updated my Nexus 7 to KitKat yet, but I just noticed on my Nexus 5 that TWRP is broken after updating to the 4.4.2 OTA. I don't get the "No connection" error, I just get the little dead android icon with the red exclamation point. Too bad I'm at work and won't be able to re-flash it until I get home.
You're not alone.
urbanman2004 said:
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
Click to expand...
Click to collapse
Lacking any and all details about how you upgraded, I would have to say that is to be expected. The OTAs usually directly overwrite the recovery with a new version of the stock recovery.
Moreover, the most recent OTA used that "/system/recovery-from-boot.p" patch file and associated script "/system/etc/install-recovery.sh" mechanism that automatically overwrites the recovery by patching the boot partition image; I think this happens either on every boot (or maybe during a clean shutdown).
So, not having noticed that, I flashed a custom recovery & booted the stock ROM... and next time I rebooted into recovery, I was back at the stock recovery ... WTF?, right?
I renamed those files to stop that from happening. I think some of the recoveries are aware of this and perform similar tricks on your behalf when they "install root" for you, but if you continue to get your recovery overwritten by stock, this is the place to look.
FYI I capture a full nandroid backup of every new stock release, whether or not I plan on using stock. I set them aside (copy them to a PC) so that they are always available.
I do this by:
- TiBu user app & data backup
- make a nandroid backup of my current ROM
- restore a nandroid backup of the prior release of the pure Stock ROM including it's matching stock recovery
- take the OTA and apply it (note everything is COMPLETELY, 100% stock during this operation)
- soft-boot a custom recovery via fastboot ("fastboot boot ...")
- make a nandroid backup of the new pure Stock ROM, including it's matching stock recovery
- flash a custom recovery and either restore a different ROM, or root the stock ROM and move forward with TiBu
This may seem like a lot of work, but it preserves maximum flexibility and safety:
(a) I can roll back to pure stock (any version!) any time I please from my archive of stock nandroid backups.
(b) I never - ever - have problems with OTA installation (including hazardous things like bootloader installs)
(c) I never need to go begging on the internet "please anybody, can you send me file "xxxx" from the stock release "xyz" ? I already have them - all of them.**
hope that helps
** note that TWRP's ".win" files are just tar archives. You don't even need to restore prior ROMs to pluck out individual stock ROM files.
Related
Hello all,
I have a shiny new Sprint LG G2 that I want to flash with CM11. I haven't done anything to it yet; it's currently installing the ZV8 OTA update (and has been for about half an hour, but that's another story).
Before I flash it with anything, I want to make double sure that I can restore it to stock (or to stock post-OTA). Unfortunately, I run Ubuntu, and the only return-to-stock tutorials I have seen are like this one and require hacking up a copy of LG's Windows-only "LG Flash Tool".
I have found a procedure to recover from a few different kinds of soft-bricking, including trying to do an OTA on a non-stock recovery, or having messed up one's boot partitions so the secure boot checks do not pass. It appears that when the phone is in "qhsusb_bulk" mode, Ubuntu will automatically (with no additional drivers) detect it as a 36-partition block device, whereupon you can just dd things to and from all of the various partitions on the phone.
1. If were to get my phone into "qhsusb_bulk" mode, could I just dd all 36 partitions to their own image files from the host PC, and restore them later by doing the reverse?
2. How do I put a Sprint G2 variant (LS980) into "qhsusb_bulk" mode? Do I have to screw up something so that it will fail to boot?
3. Is there any documentation I can read on "qhsusb_bulk" mode? Is it possible to brick the phone so badly by overwriting the wrong partition that I can't get into it to fix it?
4. Is there some other equivalent of the LG Flash Tool process for Linux?
Thanks in advance!
You should just install custom recovery, backup stock ROM, factory reset everything, Install CM11 & GAPPS, and move the stock backup to your laptop or keep on your phone?
That's what I did when i first got my phone, I right away went home backed up stock ROM and flash Paranoid Android. I just went back to stock yesterday from my backup and it's working great
I'm running Ubuntu 13.10 and if anything goes wrong, meaning if you get into a bootloop or recoveryloop, I always adb sideload a ROM and get it up and running again.
xxxrichievxxx said:
You should just install custom recovery, backup stock ROM, factory reset everything, Install CM11 & GAPPS, and move the stock backup to your laptop or keep on your phone?
That's what I did when i first got my phone, I right away went home backed up stock ROM and flash Paranoid Android. I just went back to stock yesterday from my backup and it's working great
I'm running Ubuntu 13.10 and if anything goes wrong, meaning if you get into a bootloop or recoveryloop, I always adb sideload a ROM and get it up and running again.
Click to expand...
Click to collapse
That sounds like it will cover everything but the recovery partition.
How is the stock recovery image backed up in this method, if you overwrite it with the custom recovery as the first step? Is it not backed up? Does the factory reset somehow restore it?
OK, I've done some more experimenting and poking around on IRC, and I have found this (for Sprint models, because that's what I have):
1. ioroot15 can temporarily root the device, without replacing anythig or even instaling su. Just ctrl+c it at the prompt.
2. Once that's done, "adb shell" gives you root, so you can dd the stock recovery (or anything else) from its partition to an .img, and dd TWRP over it like this:
Code:
cd /sdcard
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=stock-recovery.img
dd if=openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
3. If you don't even want to make your own backup the Sprint ZV8 stock partition images are all available for download. I can't tell you where they are, because I am apparently not allowed to post links. So if you ever need them you will have to cry and curse the forum admins. They can be flashed back with the temp-root method.
So, you can back up your recovery, flash a custom recovery, backup the rest of your system, and keep both those backups. To return to stock, restore your backup with your custom recovery, then do the temp-root and restore the stock recovery.
Hello,
today I managed to brick my device and restore it to working state, and I wonder at what point I made an error.
So here's what I did:
Had stock lollipop 30b
Rooted using oneclick root+recovery
Installed twrp using autorec
Xposed etc. and used it for a while without problem
Decided to flash something new
AOSPA 5.1.1 seemed like a good choice
Flashed bootstack, that was mentioned in aospa thread, system and gapps
Wow, that was smooth, but I needed my apps next day so I decided to restore my stock backup
Restored backup and ended up with phone in 9006 mode
Later I did some stupid moves that made whole situation worse, but that's not the point.
I backed up and restored everything that twrp allowed me to, so not only system and data, but also boot, efs, modem, recovery, sns etc. Could this be the cause? I didn't change bootstack, because I thought, that I had the needed one (autorec puts kk bootstack, right? and aosp roms also require this).
What should I do to avoid such problems in the future? I'll probably flash a lot, trying to find best possible rom for me, so it's neccesary to now whatto avoid.
And tip for future newbies like I was: if you can enter download mode, then use it, flash tool won't wipe your device data when you're using normal flash. When you've got normal working system to begin with then you can tinker further.
(Also there seems to be no way to recover from demigod critical error, even though it says it enters recovery. Then it's only this method with shorting capacitors on motherboard (fix real hardbrick)).
Cheers,
Marmelada
You can flash the patch (go back to LP from Sombons), flash, reboot recovery, restore stock rom and reboot.
Really in a bind here. I have a VZW Note 3 with JasmineROM 6.1. This morning I was prompted to do a SuperSU update and I went along and now I'm stuck in a boot loop. When I did Jasmine 6.1 last October I stopped seeing any Safestrap boot, so I'm not sure how to get into a mode where I can grab data. Any help here would be greatly appreciated. Right now all I can do is get into stock recovery and download mode.
Reading between the lines it sounds like you:
- have a locked bootloader
- have no custom recovery
If that is the case, you probably have a trip back to stock in your future: you have lost the only root you had. An unlocked bootloader would allow you to flash whatever you wanted in Odin (for instance, re-flashing a Jasmine system.img or a twrp custom recovery), but without that you are restricted in Odin to only flashing Sammy-signed blobs.
You might spend some time to see if Jasmine supports a "safe mode" boot on the off-chance that the bootloop is being caused by a market app.
A "dirty Odin flash" of only the stock system.img probably will not boot correctly or will also boot-loop, so I suppose that means you are in danger of losing all data on your phone as well. But you could try this as a last-ditch desperation move. The worst that could happen is that you will still have to flash back to pure stock... and lose all your data. (The stock recovery "factory reset" wipes everything, including the so-called "internal" SD card).
sorry
bftb0 said:
Reading between the lines it sounds like you:
- have a locked bootloader
- have no custom recovery
If that is the case, you probably have a trip back to stock in your future: you have lost the only root you had. An unlocked bootloader would allow you to flash whatever you wanted in Odin (for instance, re-flashing a Jasmine system.img or a twrp custom recovery), but without that you are restricted in Odin to only flashing Sammy-signed blobs.
You might spend some time to see if Jasmine supports a "safe mode" boot on the off-chance that the bootloop is being caused by a market app.
A "dirty Odin flash" of only the stock system.img probably will not boot correctly or will also boot-loop, so I suppose that means you are in danger of losing all data on your phone as well. But you could try this as a last-ditch desperation move. The worst that could happen is that you will still have to flash back to pure stock... and lose all your data. (The stock recovery "factory reset" wipes everything, including the so-called "internal" SD card).
sorry
Click to expand...
Click to collapse
I wound up having to do a factory restore which restored me to a clean state of JasminROM. After that I performed the new bootloader unlock and installed TWRP. Lost some data, but didn't have a choice. Last fall when I upgraded JasmineROM to 6.1 it got rid of Safestrap which was the only way to get out of this bind. At least now I have TWRP and can use that in the future.
Hello,
I am having some problems since today i flashed the su binaries over my completely new lineageos install. (a14.4, fully wiped before).
it was stuck during boot at the android logo(let it boot for half an hour, multiple times, no progress). so naturally i wanted to boot to recovery, though it would not boot into recovery with any imaginable key combo.
so i went into bootloader mode (which, in my case, is jsut download mode, no fastboot whatsoever, and yes, i checked fastboot devices, (also adb), nothing to be found there)
next, knowing i had no other choide at that moment, i flashed a stock rom, via download mode. worked so far.
stock rom was running (ics), bootloader was still download mode only, and recovery was now stock android rec.
my next step was flashing a custom rom, since this was the most important thing to get to working then.
via adb sideload i fashed lineageos, once again. was working fine, so recovery next. but nothing worked.
included with lineageos is root access, so i enabled all the stuff, incl. adb, on my phone. but adb sideload always spit out errors (code 7 or 255) on rec install (twrp 2.8.something touch.zip) [some error about /tmp/update.zip] trying cwm resulted in the same thing, like did flashing gapps.
pushing the files to the internal memory (/sdcard) did not help, since 'flash from sdcard' resulted in an empty sdcard folder with no files to install (in recovery. in the file explorer while running the os, the files where there)
then i tried rashr (not sure exactly which app it was) to install rec. it said everything worked fine, trying to install cwm. so i rebooted
and nothing worked. the rom would not boot anymore (again, stuck at android logo) since the stock recovery only allows for adb access in form of sideload, no push whatsoever, and sideload did not let me install the os via zip, it was back to flashing a stock rom once again.
so i did that again (this time lolipop)
this is where i am now:
the rom boots perfectly, like does the kinda stock recovery, but again: no files in the sdcard path within the rec menu, though i pushed them there, and they appear there in the file manager.
i installed root, for those neat apps, that maybe one would work, but they need root and the stock rom does not know how to give those rights to apps, no option found for this whatsoever.
also, download mode is gone. (still no fastboot)
when i try to boot the bootloader, i just goes on to usual os boot (key combo and adb reboot bootloader result in the same thing)
recovery is still working, but pretty useless still. when i try to sideload a file, it quits with failed verification of the file. which is no surprise to me, since it shows the message halfway through the send process (observed from the adb terminal on my pc, never gets even close to 100% before the message appears on the phone which also cuts the connection therefore the file send process.)
i have absolutely no idea what the hell will get this working again. i dont really care about the download mode, but what i really need is a custom recovery to finally work, so i can install all of my stuff again.
does anyone have any idea on what i could try next?
hopefully yours,
azyrael
SOLVED
so i noticed for root apps i need to install supersu (or something like this) to give root access to apps if there is no native way within the rom to do this stuff.
install supersu and found out i somehow had no root access at all. tried ioroot etc, did not work
so i installed a stock jb android rom, rooted the device via ioroot, install recovery via autorec, and it finally worked!
this took me only two days.
thx xda for providing all of the tools i needed for this <3
kinda unsolved
so, it got recovery to work. installation of lineageos also worked perfectly., though this bricks my device.
no matter what i wipe, installing a custom rom will stop it from booting. this could only be fixed by installing a stock rom again, which also reverses root and install a stock recovery. since i only need root and the rec for installing a custom rom, which does not work anymore, i wont bother with this anymore. i have abosutely no idea whatsoever, and tried everything even barely coming to my mind.
still open for suggestions, but the stock rom will have to suffice for now.
I"m having issue with flashing roms, kernels and restoring on my device and i'm not sure if its cause a process was done incorrect and/or a TWRP.
I have a 2017U. Bootloader is unlocked, TWRP 3.1.0, and currently on stock B19 (no root, via TWRP with Draken's Stock system).
Here are the issues I"m facing:
1. Unable to Restore backup. I've made a backup and selected Boot, System and data. Also selected "compression". Restore shows complete, but device freeze on boot screen (the one says hit vol for more options).
2. Issue flashing kernel. I tried flashing Beastmode (a couple of previous versions up to the most currect R45). I keeps booting back into Recovery. I then tried flashing the stock kernel from Freeza and it still boots into recovery.
3. Flashing Roms. This one is possibly a rom issue, but just wanted to throw it out there any ways in case it's not. Flashed Bad Boys rom. Works fine when installing with SU or Magik, but doesn't boot if it select "no root"...
Any help/advice is appreciated.
You either need to flash supersu, or no-dmverity to patch the kernel to bypass this security feature.
3.1 is also not ready according to twrp thread.
Sent from my ZTE A2017U using Tapatalk
Thanks guys.
Just having a difficult time with TWRP recently. I wasn't able to restore properly on 3.0.4.
Every time i tried to restore, it says i need to uncheck mount system partition read only. Do need to flash the no-dmverity after i restore?