Related
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.
I've flashed the newest CyanogenMod nightly on my Nexus 4 yesterday, but now I seem to have lost root access (maybe because I encrypted the device?). The device is not being recognized anymore in adb, and if i enter the custom recovery (CWM) to install SuperSU again, i cannot access "choose zip from /sdcard". Also, root apps are not working anymore. How do I get root back, without losing my data?
Ok, so I saw a developer option called something like "give root access to apps" and it did seem to work, i could open up AdAway and download the host files etc (this was the only app with root access that I had on the phone). Then I restarted the device and now I'm in a boot loop - no idea what to do now. Restoring my backup from sdcard obviously doesn't work, because CWM doesn't have access to it, because the device is encrypted. What now? Can I just install a bootloader that supports encryption? Will TWRP work? Need help please.
I have a SGH-I337M S4 via Koodo in Canada. I've spent 15 hours on this so far and am now really confused.
History: I installed Cyanogenmod a couple years ago. Recently wanted to change from that so I decided to install stock first via SamMobile for SGH-I337M Koodo. I downloaded 5.0.1 from here sammobile
I had it installed fine and then went to root, so I used Odin, enabled USB debugging - and installed CF Auto Root. That worked.
Then I went to install Clockwork Recovery mod and it errored out and I don't recall exactly what happened but now I'm stuck with the yellow exclamation point saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
In the TOP LEFT of screen is says:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL: LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: ENABLE
eMMC BURST MODE: enabled
1) I tried to do emergency recovery through KIES but my phone isn't being recognized in Kies.
2) I uninstalled Samsung USB drivers and tried just KIES alone
3) I tried just USB drivers with flashing stock firmware via Odin in download mode - it errors out and says no partition found or says FAIL in red.
I've read a lot but i'm not that technical when it comes to this.. not sure what to do at this point. I can get into download mode but I can't get anything to work.
Is the phone ruined??
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
audit13 said:
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
Click to expand...
Click to collapse
Hi Audit,
Thank you for the reply. I was able to try the original USB cable now and loaded the stock Koodo firmware through Odin and it worked flawlessly. Once loaded and rebooted, it went right to the homescreen and skipped past all the normal setup stages, so I assume something on the phone was there already but just corrupted on a bad upgrade.
Never again using an older USB cable.
Whew, that was a learning lesson. Now I'd like to:
1) re-root again
2) Install custom recovery (clockwork?)
3) Install the marshmallow OS via Broken I believe.
I will keep the thread posted for others who need help and for my own reference.
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
audit13 said:
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
Click to expand...
Click to collapse
I did not know that. I thought I required root first and then had to install a custom ROM. Interesting.
Ok, so the plan then is to find twrp for my phone model and install that first... I'll search and try to do that now.
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
audit13 said:
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
Click to expand...
Click to collapse
Done. I used the latest one for the tar and I have v2.8.4.0 right now. I held volume up and power and it went to Teamwin with a bunch of options. Install/wipe/backup/restore/mount/settings/advacned/reboot
On the TWRP website it says: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
1) I'm not sure what it means by typing that. I'd like to keep TWRP as I install my custom rom. I have the custom rom on an external SD card along with GApps. Should I insert the sd card and then boot to recovery, wipe all data and install from zip on sd card? Is that correct?
2) How do I keep TWRP from not getting overwritten?
Thanks so much for the help. Really appreciate it after a weekend of terror.
I backed up the EFS portion and it wrote it to the internal storage of the phone I believe... data/TWRP something. I did not have my external card in when I did that. Is that the correct way and how would I access that backup if I needed to?
Sorry for the questions. Trying to learn without running in circles.
After I backed up the EFS it also asked me to install SuperSU and I did that - then it rebooted automatically.
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
audit13 said:
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
Click to expand...
Click to collapse
I'm not sure if I can post links due to the new account, but the latest files for me are found on dl.twrp.me/jfltecan/ and the only tar image is twrp-2.8.4.0-jfltecan.tar
I will have to go over your other comments on my own to see the functionality. As of now, this is what I have:
1) Stock firmware
2) TWRP installed
3) TWRP asked if I wanted to root (I said yes, figuring that's what you meant)
4) TWRP installed SuperSu and rebooted
5) I downloaded Root Checker and it verified root.
I did just test it by powering off phone and then booting into recovery. Teamwin came up - so I assume that it's all working correctly and the stock ROM did not overwrite anything?
Questions:
1) Now I can boot into recovery mode and install the custom ROM via a zip file on sdcard?
2) Do I install GApps via recovery mode after I install a custom ROM?
3) Should I wipe/format before installing and if so, which one - "Advanced" or "Format" buttons?
I did a factory reset via TWRP then installed the custom ROM. Seems to be working quite well. Maybe I will try it a couple times in order to get the hang of it.
In order to determine that TWRP is the default recovery - it should load when I go into recovery mode correct?
If the phone boots to twrp once, it should not revert to stock recovery in the future.
Is there a stable ROM for a S4 i337m that is newer? I'm having some trouble finding a solid list that is known to work. I don't want to install a wrong version and mess up. I did try the "broken" ROM but 50% of time when someone phones me, they can't hear me speaking so I'm going to have to go back to stock firmware for now.
You could try ROMs made for the 9505 and i337.
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
This may be an issue with TWRP. When I had my Galaxy S3 rooted back in the day I would have this issue, also with a Nexus tablet I rooted as well. It turns out I needed to flash a specific "fixed" version of TWRP to fix the mount/flash issue. That was a long time ago though, so this might not be the problem, but I thought I would at least tell you my experience.
Sent from my LG-LS997 using Tapatalk
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I beleive you have to do Dirty Santa over again....The steps that is.
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.
imucarmen said:
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.
Click to expand...
Click to collapse
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.
biglightbt said:
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.
Click to expand...
Click to collapse
I would run the dirtysanta exploit again from the beginning. Your assumption about being stuck in read only seems correct. I'm guessing you might have chosen read only on accident one time when you booted into TWRP and now it's stuck there.
Or you could try using flashfire to flash the TWRP.img
I am having the same issue. I tried doing the DAC mod that enables high impedance as always on. Audio quit working along with the stock music app. Did a restore from after I flashed the konverged kernel. And now no r/w ability and twrp will not mount system unless I check mount as read only. I was able to reinstall supersu from the recovery. But still have the issues.
Only thing I can think of is waiting for a return to stock unrooted method to Come out and re-root.
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
Hey I was having the same problem and I fixed it myself messing around with a few things I could think of.
Here it is pasted from another thread.
Dinked around with a few ideas and got my problem fixed! Heres what I did.
1. Made a backup of system in twrp just in case.
2. Formatted system in wipe > advanced > and only checked system.
Panicked because I thought I bricked my device, wouldnt boot farther than the lg logo,
(next steps might be unnecessary but I panicked and tried them lol)
3. still had fastboot access so I repeated step 3 in the root method.
4. Reflashed boot2.img
5. Rebooted to recovery with volume- power, release power while keeping volume- at lg for a second then repress and hold power. Yes twice to get to recovery.
6. Restored system backup. (was able to fully boot now but with lag)
7. Reflashed konverged kernel.
And everything is working perfect now and I have my r/w ability and can mount system in recovery without having to select mount as read only.
---------- Post added at 09:57 AM ---------- Previous post was at 09:10 AM ----------
You can probably just wipe your system like I said in the previous post then Just restore it. I panicked and did a bunch of extra stuff. I realized that when I did my initial backup of my system, or said that its size was about 126247251477482716MB. So I'm guessing when I did my restore (possibly what happened to yours) that it somehow messed up the system.
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?