Related
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
ma_moto said:
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
Click to expand...
Click to collapse
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
enaon said:
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
Click to expand...
Click to collapse
So you just flashed CM11, even though it booted back into stock recovery ?
ma_moto said:
So you just flashed CM11, even though it booted back into stock recovery ?
Click to expand...
Click to collapse
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
enaon said:
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
Click to expand...
Click to collapse
I did pretty much the same thing right now and just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
ma_moto said:
I did pretty much the same thing right now just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
Click to expand...
Click to collapse
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
enaon said:
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
Click to expand...
Click to collapse
I used CWM directly from their site, maybe that's why it isn't working probably.
You're right i should do a clean reflash, but I'm getting sick of constantly reinstalling and configuring everything
I'm trying to flash an update to PAC Rom, but I can't get my phone to reboot to recovery (or even shut down).
When I use the power menu, no matter what I choose, the phone does a hot boot. When I hold power and volume down it will go to bootloader then I can access TWRP, but I can't clear dalvik or cache as it says that it can't mount the partitions. The ROM runs fine however and I can access all my data so the cache can't be corrupt.
What can I do here? Thanks to those who help!
Sounds like somethings wrong with your recovery. Get into the bootloader and reflash TWRP using "fastboot flash recovery FileNameOfTWRP.img"
Chromium said:
Sounds like somethings wrong with your recovery. Get into the bootloader and reflash TWRP using "fastboot flash recovery FileNameOfTWRP.img"
Click to expand...
Click to collapse
Would using flashify work here?
It's been a recurring theme on the PAC forum
Synyster06Gates said:
Would using flashify work here?
It's been a recurring theme on the PAC forum
Click to expand...
Click to collapse
Yea that should work too, but if not, fastboot is the way to go.
EDIT : Very very strange. Flashing TWRP again via Flashify got it to work. It seems something in PAC Rom is corrupting the recovery. I think if I get this all worked out then I'm going to have to go back to DK until it's all worked out. I wish there was another ROMs with all the same features as these two but got updates (whereas DK doesn't any more) and is stable enough to DD (lots of FC with PAC).
EDIT 2: Just tried to reboot into recovery again. After booting teh ROM just for a few minutes the recovery was corrupted. I can't access internal memory from recovery any more, even if I get it to boot. It doesn't make any sense as the ROM has full access to it all.
To be clear, TWRP says Internal Storage - 0
Synyster06Gates said:
EDIT : Very very strange. Flashing TWRP again via Flashify got it to work. It seems something in PAC Rom is corrupting the recovery. I think if I get this all worked out then I'm going to have to go back to DK until it's all worked out. I wish there was another ROMs with all the same features as these two but got updates (whereas DK doesn't any more) and is stable enough to DD (lots of FC with PAC).
EDIT 2: Just tried to reboot into recovery again. After booting teh ROM just for a few minutes the recovery was corrupted. I can't access internal memory from recovery any more, even if I get it to boot. It doesn't make any sense as the ROM has full access to it all.
To be clear, TWRP says Internal Storage - 0
Click to expand...
Click to collapse
Here could be the solution. http://forum.xda-developers.com/showthread.php?t=2513701
Flash the cache.img
if it wont work, will have to flash-all
GUGUITOMTG4 said:
Here could be the solution. http://forum.xda-developers.com/showthread.php?t=2513701
Flash the cache.img
if it wont work, will have to flash-all
Click to expand...
Click to collapse
That worked! Thank you!
I actually used to go around the Q&A forum telling people to do just that when they were having issues with wiping on early TWRP versions. Surprised I didn't think to try it. All back on DK now and hunting for a new ROM. :victory:
Synyster06Gates said:
That worked! Thank you!
I actually used to go around the Q&A forum telling people to do just that when they were having issues with wiping on early TWRP versions. Surprised I didn't think to try it. All back on DK now and hunting for a new ROM. :victory:
Click to expand...
Click to collapse
Sounds like you solved it, but I think you could've also done an adb reboot recovery command. Not sure if that works though since I usually only use fastboot.
Sent from my Nexus 5 using Tapatalk
numel007 said:
Sounds like you solved it, but I think you could've also done an adb reboot recovery command. Not sure if that works though since I usually only use fastboot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
After flashing teh recovery again, I could get INTO it, but the data was not showing up so I couldn't actually do anything from within TWRP. It read I had 0mb internal storage.
When I attempt to go to Cofface's Baidu page to download his 5.1 TWRP version, I get a message saying the content is no longer available. Specifically, Google Translate shows "Lol, you visit the page does not exist." Does anyone happen to have a copy they're willing to share? Or is there some issue with the 5.1 version that would suggest that I shouldn't use it? If I shouldn't ask for some reason, I apologize. Otherwise, thanks in advance.
https://yadi.sk/d/5YI63uiAhz5UD/Recovery/TWRP
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
wpennhokie said:
Thanks very much for the link! I think I must have some deeper problems, as every time I flash this recovery (and another version I found in my old downloads), I just get stuck in a boot loop. I was able to use TWRP when I was on B015, but for some reason, I can't get it to work on B106. I'm using:
fastboot flash recovery c:\android\twrp_cn.img
However, like I said I just get stuck in a boot loop. When I flash the stock recovery, everything starts working again.
Click to expand...
Click to collapse
Did you unlock your bootloader?
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
wpennhokie said:
Yes, it is. I was able to run TWRP when I was on B015. The phone is rooted, so I've just been using Titanium Backup to back everything up before I wipe the phone, but it would be nice to take a Nandroid backup instead of having to reinstall from TB.
Click to expand...
Click to collapse
Thats the same problem I have. I used the other twrp recovery https://mega.nz/#!l5kmUByA!41uExNuasZRgLBML9TTSp8myX-_F6UgQZuE2F2BRZUE
This one worked with out boot loops for me. you can give it a shot.
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
I had that exact same problem twice on Kangvip B015. When I would restart it would all of a sudden automatically boot into TWRP every time and never boot into the OS. When that happens, in TWRP make a backup, then Fastboot flash the stock ROM (system, boot, cust, recovery, user data etc) then when it boots do a factory data reset, then reroot, flash TWRP and restore from the backup you made. The OS will boot from your backup. I dunno why this happens, maybe it has something to do with with Kernel.
I've tried it a couple of times now, and I'm still not getting it to boot past TWRP once I flash the recovery. It was able to take a backup with TWRP, but when I restored it, I still had to restore the stock recovery before I could boot into the system. At worst, at this point, I can always flash TWRP, take a backup, flash the stock recovery, and then have my system back. It's a few extra steps, but I think I'll do this until I find a custom ROM that I like. I greatly appreciate the help so far.
wpennhokie said:
Thanks for the link! I can now get into TWRP. However (sadly), after I leave TWRP, it reboots directly back to TWRP. I've tried rebooting from TWRP into the system and shutting down, but each time, it just goes straight back to TWRP. I was able to boot into fastboot, so I reflashed the boot.img file, but it still goes straight to TWRP. I actually have had this issue before, and I wasn't ever able to figure it out. Any help would be greatly appreciated, as usual.
Click to expand...
Click to collapse
Reflash the stock b106 recovery and wipe user data and cache, Then reflash twrp recovery and restore your backup. It should boot then.
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
wpennhokie said:
To follow up, I tried using the updated version of TWRP that you (mtyler7807) posted in the development thread and following the instructions above. I can flash the recovery, boot into it, and take a backup. After that, as long as I boot into the system, I'm fine. However, once I boot into recovery for the first time after that initial backup, it just reboots into TWRP every time. So, right now, I took a backup a day or so ago, and I've just avoided going back in to TWRP again. I have another X2 on the way (a 32GB version), so I'm hoping that I'll have better luck with that one.
Click to expand...
Click to collapse
By any chance, did you delete anything from the Cust Folder at any point?
ajsmsg78 said:
By any chance, did you delete anything from the Cust Folder at any point?
Click to expand...
Click to collapse
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
wpennhokie said:
As far as I know, I have not. I did do a complete wipe of everything (except the SD card) at one point using TWRP, but I've always restored the system using the stock system.img file. Right now, the Cust folder is showing five folders, with several more folders/files underneath. Is there a particular file I should be checking for?
Click to expand...
Click to collapse
I don't think so. It's weird how some of us have different problems than others. I've had zero issues with TWRP but lately my screen has been going crazy. My touches don't work, things jump it's like my digitizer is messed up but when I restart everything is fine again. So I reloaded everything and the problem went away. I guess I debloated too much last time.
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.
theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk
All I did was install TWRP with Odin. Then I backed up my phone, without "data" because it was unable to mount /data.
It said the backup succeeded, so I restarted. Now It won't come off the "Samsung Galaxy S7 (powered by Android) boot screen. Is this really typical of TWRP? Brick my phone for backing it up? All I wanted to do was back it up.
I can get into Download Mode and back into TWRP, but it looks like there's nothing in internal storage!!! Wtf??? The stuff on my external SD is there, including the backup. Am I supposed to restore the backup now? Why was it all deleted? What do I do???
Please help. I was backing up in order to make sure this would never happen in the first place!!
SGS7 SM-G930W8, latest TWRP
Where's the sense here? You wanna back up your phone? Sure, let's delete all your data and soft brick it. Not the same thing?
Whaat?
If I don't get a response soon I'll try restoring that backup. THE THING IS... If my data was deleted before the backup, it might only make **** worse... Maybe.
I attempted the backup. Nothing. Strangely, when I press "Restart," it seems to crash and reboot before I get to "Swipe to Restart".
What do I do???? Why is TWRP not trustworthy?!
Too late, I'm attempting to flash stock firmware to my phone now. Where do I complain to TWRP about backing up having the exact opposite effect?
Kilva said:
Too late, I'm attempting to flash stock firmware to my phone now. Where do I complain to TWRP about backing up having the exact opposite effect?
Click to expand...
Click to collapse
If you flash exactly the same version of firmware that your device had when you installed TWRP, it won't wipe your data.
The TWRP team, nor it's code are to blame here. If its an unofficial TWRP then it was built by someone that isn't a part of the TWRP and probably didn't do a good job, especially if this TWRP was ported from a similar model.
Sent from my LGL84VL using Tapatalk
Hey Kliva,
I have run into the same problem. I flashed TWRP 3.2.3 heroflte, booted into recovery and went to do a backup. I only got an error message that TWRP couldn't mount some partitions and no backup.
I tried to reboot and am stuck in boot loop.
Did you get your phone back up running? and how?
Thanks
ntbergeron said:
Hey Kliva,
I have run into the same problem. I flashed TWRP 3.2.3 heroflte, booted into recovery and went to do a backup. I only got an error message that TWRP couldn't mount some partitions and no backup.
I tried to reboot and am stuck in boot loop.
Did you get your phone back up running? and how?
Thanks
Click to expand...
Click to collapse
Flash your stock firmware via Odin.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Flash your stock firmware via Odin.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for getting back to me. I tried flashing stock through Odin several times and each time the process failed.
Out of desperation I found a different kernel and flashed it through TWRP and it worked. The phone booted and everything seems to be working ok.
Thanks again.