Related
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
dibblebill said:
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
Click to expand...
Click to collapse
I wouldn't say flash-crazy, but i've tried two different roms in the past two days. It's not really freezing either. It will just start to restore, make it half way through, and reboot. My rom will be restored but none of my data.
sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
Yep, seems to be happening a lot. One suggestion was to revert to 2.4 or even 2.3.3.0. I tried that, and thought the problem was solved, but then it happened again, so I figured what the hell, I'll go back to 2.5.
You're right, it always happens during the data restore, but so far the second attempt at restoring always succeeds, so it's more annoying than anything. I can't recall it ever happening on my phone, though, so I wonder if it's a device issue. Also my phone is running JB 4.1.2 and my N10 is on 4.2.2.
Sent from my Nexus 10 using Tapatalk HD
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
brGabriel said:
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
Click to expand...
Click to collapse
So yesterday I went to flash a new ROM and TWRP froze immediately after doing a Factory Reset Wipe. Nexus kept bootlooping and then getting stuck on the TEAMWIN screen. Was able to get into the bootloader and flash the stock image and unroot through the Nexus Toolkit. I lost all my data though. So my question is, if you can get to bootloader mode and the toolkit recognizes it in bootloader mode, can you recover data without having to do what I did and wipe the device? For future reference sake. God I need to get better about backing up my data on my PC.
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
ky3bmu4 said:
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
Click to expand...
Click to collapse
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Yes, i'm thinking the same. Maybe it also because the backup was huge (maybe like 4 gb).
But I am not really sure if it is corrupted because the system restores fine and data do not, but it fails in different places, i.e. it may reboot in 30 seconds and may reboot in 2 minutes...
But it's more than that
I need help pretty badly. I flashed cm 10.2 on my Sprint GS4 (from cm 10.1) (Sidenote: I did it because the cm updater offered 10.2 to me inside my 10.1 install), after having made a nandroid in twrp.
The camera is lolbroke in cm 10.2, so I just did a factory reset in twrp and attempted to restore my backup. << This is where everything goes failshaped.
All seemed to go well, although I didn't pay a ton of attention to it, but when I rebooted it, it just stayed on the Samsung Galaxy S4 screen. For like 5 minutes. ok I thought that was odd, so I pulled the battery and booted into recovery. Now TWRP wants a password in order to decrypt the internal sd card, which is new, because I never encrypted it.
I cannot flash anything nor restore my backup until I have this fixed. So I read somewhere that reinstalling twrp would generally fix it. Ok well I'm on 2.5.0.2 anyway, so I figured I would upgrade to 2.6.
Figured out how to update twrp to 2.6.0.0 via download mode and odin, but still it was asking for a password.
So I read elsewhere that others have fixed it by flashing completely back to stock via download mode and odin. So with the help of this thread http://forum.xda-developers.com/showthread.php?t=2357471 I flashed "Download Odexed No Data Wipe Tar" (because the Deodexed one refused to pass an md5 check).
I don't care if data is wiped, in fact, at this point I would prefer it, but it seems that all of those are zips, and if I try to run one through twrp it'll just say "failed" again.
I don't know what to do at this point. Please help :crying:
So since I've been in never give up never surrender mode, I have been able to fix this, 3 hours after the initial problem. This is how I did it.
[02:05] atm I'm using odin to flash stock everything again, and I'm going to go into the stock recovery and do a factory reset and I hope that that somehow has power over the internal sd or something
[02:05] From what I understand a repartition in odin can do the trick, but that checkbox also seems to be the great destroyer of android devices
******* HUGE SIDENOTE HERE... I DID NOT DO THE REPARTITION IN ODIN AND NEITHER SHOULD YOU UNLESS YOU ARE A FAN OF PAPERWEIGHTS!!!*******
[02:14] I fixed it
[02:14] oh thank you jesus
[02:14] I was almost to the point of tears tbh
[02:16] Stock recovery reported that it could not mount /data due to an stale NFS handle or some ****
[02:17] SO I told stock recovery to do a factory reset and it worked
[02:17] SO now I'm going to go back into download mode, install twrp, and recover my backup
[02:27] Woot, it worked
[02:27] Sigh of relief
[02:29] I flashed twrp via odin and booted into recovery and restored my backup, but when it rebooted the phone took a solid 10 minutes to un**** itself before showing the cm boot animation. I was about to pull the battery when the boot anim showed up.
Hopefully this thread helps someone else later on down the line.
Great work
Sent from my SPH-D710 using Xparent BlueTapatalk 2
Here is what i did. I got TWRP. TAR and loaded it with ODIN. that reset the need for a password and all is good now!!!
enricay said:
Here is what i did. I got TWRP. TAR and loaded it with ODIN. that reset the need for a password and all is good now!!!
Click to expand...
Click to collapse
A few times I had TWRP 2.5.0.2 ask me for a password. I just hit back and it took me right to the main recovery menu. No password was ever needed which is good since I never set one to begin with.
Stock Recovery
Having same problem and Stock Recovery worked for me. Just did what you said and factory reset. Thanks!
This is the most helpful post I've found.
Forboding Angel said:
So since I've been in never give up never surrender mode, I have been able to fix this, 3 hours after the initial problem. This is how I did it.
[02:05] <Forboding> atm I'm using odin to flash stock everything again, and I'm going to go into the stock recovery and do a factory reset and I hope that that somehow has power over the internal sd or something
[02:05] <Forboding> From what I understand a repartition in odin can do the trick, but that checkbox also seems to be the great destroyer of android devices
[02:14] <Forboding> I fixed it
[02:14] <Forboding> oh thank you jesus
[02:14] <Forboding> I was almost to the point of tears tbh
[02:16] <Forboding> Stock recovery reported that it could not mount /data due to an stale NFS handle or some ****
[02:17] <Forboding> SO I told stock recovery to do a factory reset and it worked
[02:17] <Forboding> SO now I'm going to go back into download mode, install twrp, and recover my backup
[02:27] <Forboding> Woot, it worked
[02:27] <Forboding> Sigh of relief
[02:29] <Forboding> I flashed twrp via odin and booted into recovery and restored my backup, but when it rebooted the phone took a solid 10 minutes to un**** itself before showing the cm boot animation. I was about to pull the battery when the boot anim showed up.
Hopefully this thread helps someone else later on down the line.
Click to expand...
Click to collapse
So, just to confirm, you didn't mess with the PIT check box at all? You only loaded the image file in PDA and ran with it?
---------- Post added at 03:24 AM ---------- Previous post was at 02:57 AM ----------
Forboding Angel said:
So since I've been in never give up never surrender mode, I have been able to fix this, 3 hours after the initial problem. This is how I did it.
[02:05] <Forboding> atm I'm using odin to flash stock everything again, and I'm going to go into the stock recovery and do a factory reset and I hope that that somehow has power over the internal sd or something
[02:05] <Forboding> From what I understand a repartition in odin can do the trick, but that checkbox also seems to be the great destroyer of android devices
[02:14] <Forboding> I fixed it
[02:14] <Forboding> oh thank you jesus
[02:14] <Forboding> I was almost to the point of tears tbh
[02:16] <Forboding> Stock recovery reported that it could not mount /data due to an stale NFS handle or some ****
[02:17] <Forboding> SO I told stock recovery to do a factory reset and it worked
[02:17] <Forboding> SO now I'm going to go back into download mode, install twrp, and recover my backup
[02:27] <Forboding> Woot, it worked
[02:27] <Forboding> Sigh of relief
[02:29] <Forboding> I flashed twrp via odin and booted into recovery and restored my backup, but when it rebooted the phone took a solid 10 minutes to un**** itself before showing the cm boot animation. I was about to pull the battery when the boot anim showed up.
Hopefully this thread helps someone else later on down the line.
Click to expand...
Click to collapse
I was going to follow your plan even before I read your post... except for the part about factory resetting from stock recovery. I would have been quite distraught when my phone wouldn't boot up after an Odin. I followed your method with a wipe from the factory recovery, and I'm golden!
THANK YOU!
Hey scubamike! Glad you got it sorted. Sorry I took so long to respond.
No I did not do the pit thing. I'll update the op. &yeah... I have an s4 which I hate with an undying passion. The s3 was a lot better supported by aosp.
I should have gotten an oppo find 5. Anyway, yeah...
Cyanogenmod really really needs to fix 10.2 builds showing as nightly updates to 10.1 builds.
That's how I got screwed.
Sent from my SPH-L720 using Tapatalk 4
I am totally going through what you did. I am completely flabberghasted.
I will never risk installing another CyanogenMod ROM for the rest of my life.
I have like 7 hours to wait to download the factory image due to my net being throttled....
I am just glad I have another device on hand.
What? Don't be silly! CM is awesome, but just like me, you should have known better than to try to dirty flash a completely different version of android over another different one.
I did know better, but it showed up in the update list, so with trepidation, I tried to upgrade it and learned. CM is fine and a great ROM.
We shouldn't really get mad at CM simply because we made a mistake
Sent from my SPH-L720 using Tapatalk 4
Forboding Angel said:
What? Don't be silly! CM is awesome, but just like me, you should have known better than to try to dirty flash a completely different version of android over another different one.
I did know better, but it showed up in the update list, so with trepidation, I tried to upgrade it and learned. CM is fine and a great ROM.
We shouldn't really get mad at CM simply because we made a mistake
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
Who said I'd dirty flashed? I certainly didn't. This is an encryption error that seemingly affects TWRP users.
It was not an error on my part as I've flashed this device numerous times and had zero problems.
I think CM and TWRP are not entirely compatible. I switched from CWM a while back due to a ROM that wouldn't flash in it.
Sent from my SGH-T889 using Xparent Green Tapatalk 2
I'm having a similar issue on my gf's Kindle Fire I w/CM10.2, but without the prompt for password. So annoying! - http://forum.xda-developers.com/show....php?t=2563695
Good idea about nandroiding and returning to stock - I suspect that's what I'll have to do. Also an interesting point about TWRP, although I don't think that's it. Might try CWM for good measure.
In my case I suspect a data wipe is really all that's necessary.
Phateless said:
I'm having a similar issue on my gf's Kindle Fire I w/CM10.2, but without the prompt for password. So annoying! - http://forum.xda-developers.com/show....php?t=2563695
Good idea about nandroiding and returning to stock - I suspect that's what I'll have to do. Also an interesting point about TWRP, although I don't think that's it. Might try CWM for good measure.
In my case I suspect a data wipe is really all that's necessary.
Click to expand...
Click to collapse
I would. Once I switched to CWM on my Note III, I had zero issues with any CM/AOSP ROMs. I had done a full wipe in TWRP too. Don't know but that's just my experience. ^_^
Sent from my SM-N900T using Xparent Green Tapatalk 2
I thought I had everything backed up and i do but I can't restore from twrp. Tells me it can't mount system. I'm lost at this point. Using a Canadian based lg g2. Any help would be amazing.
Thanks.
Nevermind. I tried flashing the new CM10.2 released and it took forever so I cancelled it is therefore unmounting the system. I reflashed it waited it got "fast boot" error then restored and all is well. My stupid mistake
Sent from my LG-D802
Brava27 said:
Nevermind. I tried flashing the new CM10.2 released and it took forever so I cancelled it is therefore unmounting the system. I reflashed it waited it got "fast boot" error then restored and all is well. My stupid mistake
Sent from my LG-D802
Click to expand...
Click to collapse
How did you solve it? i cancelled while formatting and it unmounted /system and can seem to mount it again, how can i solve it? thanks
skfalco said:
How did you solve it? i cancelled while formatting and it unmounted /system and can seem to mount it again, how can i solve it? thanks
Click to expand...
Click to collapse
i would love to know this as well!
when u flash roms on the g2 it can take upto 10 mins to wipe cache and dalvick and a few more mins to finish it seems to take forever after having an n4 but that's the way it seems to be,so hang in there and let it do its stuff ?
I ended up using adb and sideloaded my original CleanRom and let it sit.. and sit.. and sit.. finally it went through TWRP told me there was no OS installed but I rebooted anyway.. and it booted into my ROM.. I rebooted back into recovery and restored my backup I had done before flashing team CM ROM.. I may try again later since now I know it just takes FOREVER... I am just glad I did not have to wipe everything and go back to stock..
Sent from my VS980 4G using XDA Premium 4 mobile app
My device:
SPH-L720
Android 4.4.2
Baseband L720VPUFNAE
Kernel Version [email protected] #2 Mon Feb 24 14:19:28 EST 2014
Carbon Version: CARBON-KK-SHINYSIDE-EDITION-20140224-140
Build Number: carbon-jfltespr-userdebug 4.4.2 KVT49L e71e225082 test-keys
SELinux status
Enforcing
Interal space/free: 9.59/8.84
I have formatted my phone completely. There was no rom on it, nothing installed on the SD card. Formatted the system, data, cache, preload, etc. I installed the stock firmware NAE with odin, and it went fine. I booted the device, and it boots into a encrypted screen. When I try to press enter, it says failed. When I type in a previous password of mine, it fails. I shut down the phone, boot into download mode. I install root with CF-root via odin, and flash the NAE modem. I shut down the phone, and put it back into download mode. I install philz-touch recovery, and i install a stock, rooted Deodexed rom. It installs, and reboots. Once it boots, i get an ecnrypted screen.
If i install a different rom, anything Cyanogenbased (hellkat, cyanogen, carbon) then I do not have this problem. Does anyone know what's going on? I have formatted my phone 4 times now. The device was once encrypted, but I have removed that several roms ago.
Can someone tell me what's going on?
edit/
I'm seeing stuff about knox security. Is this what i'm seeing?
edit-fixed!
Alright, thanks to a user suggestion in this thread this is what I have done.
1) Install Unofficial Carbon and complete the initial setup.
2) Encrypt the device. Your phone must be plugged in, and at least 80% battery.
3) Then rebooted into Philz Touch recovery, and cleaned to install a new rom.
4) Installed 4.3 stock(ish) rom
5) I was then able to boot, and the device did not ask for an encryption password.
The only conclusion I can come up with is that since I re-encrypted the data, that it deleted it and the old partition when I cleared my system/data. I have no idea to be honest, but now the phone works.
I was not able to get any stock rooted firmware other than Stock(ish) to work with the modem. I flashed it, I used CDMA to write the PRL..but nothing. I may try to do that later, but for now i'm on an essentially stock 4.4 ROM with an NAE modem.
Sorry, but if your phone was encrypted before, you may be out of luck with out a password. If it was as easy as a factory reset to defeat encryption than your data would never be safe. You may need to take it into Sprint and see if the tool they use to force a firmware install can fix it. Also, if you have an sdcard installed remove it and try to odin the stock tar again and boot up. It may just be that your sdcard has been encrypted and without it in your phone it will work.
cruise350 said:
Sorry, but if your phone was encrypted before, you may be out of luck with out a password. If it was as easy as a factory reset to defeat encryption than your data would never be safe. You may need to take it into Sprint and see if the tool they use to force a firmware install can fix it. Also, if you have an sdcard installed remove it and try to odin the stock tar again and boot up. It may just be that your sdcard has been encrypted and without it in your phone it will work.
Click to expand...
Click to collapse
The Sdcard isn't in when I am experiencing the problem. The encryption before shouldn't matter, as it's been formatted and i've installed countless roms since.
Looking for a better answer
Nobody has had this issue or knows someone that has? A google search hasn't returned anything useful other than what i've already done.
Encryption has nothing to do with SD cards. You can encrypt your phone data. And without that password, no amount of flashing with get you back in.
Sounds like you need a visit to a Sprint store to help. They have tools that can get you back in to your phone.
Sent from my XT1080 using XDA Premium 4 mobile app
VandyCWG said:
Encryption has nothing to do with SD cards. You can encrypt your phone data. And without that password, no amount of flashing with get you back in.
Sounds like you need a visit to a Sprint store to help. They have tools that can get you back in to your phone.
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't see how me encrptying the device won't bring the storage area back. If i format an encrypted flash drive, i get all of my storage back?
I visited the spring store today, and they told me they couldn't help me..so i'm here again.
could it be possible that re-encrypting while your runnin on cyanogenmod rom would either over-ride or over write the previous encryption? (i have little knowledge of encryption, but just a thought)
bioshocked said:
could it be possible that re-encrypting while your runnin on cyanogenmod rom would either over-ride or over write the previous encryption? (i have little knowledge of encryption, but just a thought)
Click to expand...
Click to collapse
That's an interesting idea..will give it a go later.
backdown said:
I don't see how me encrptying the device won't bring the storage area back. If i format an encrypted flash drive, i get all of my storage back?
I visited the spring store today, and they told me they couldn't help me..so i'm here again.
Click to expand...
Click to collapse
I think the issue is, once you encryrpt your device, its encrypted. Have you tried to ODIN back to stock firmware. You would probably lose your data, but you would get your phone back.
That's a guess. But this highlights a reason why encypting devices can be bad.
VandyCWG said:
I think the issue is, once you encryrpt your device, its encrypted. Have you tried to ODIN back to stock firmware. You would probably lose your data, but you would get your phone back.
That's a guess. But this highlights a reason why encypting devices can be bad.
Click to expand...
Click to collapse
I have already flashed it to a 4.4.2 firmware. The problem only exists with stock firmware and stock rooted ROMs, not custom ROMs like CyanogenMod.
An update..
So I encrypted my device using the Carbon-rom, and rebooted into recovery. I wiped my device, and installed the Stock(ish) ROM. I was able to boot into the device, without any kind of encryption screen.
I am going to try a fully stock rooted 4.4.2 app and update this post.
backdown said:
So I encrypted my device using the Carbon-rom, and rebooted into recovery. I wiped my device, and installed the Stock(ish) ROM. I was able to boot into the device, without any kind of encryption screen.
I am going to try a fully stock rooted 4.4.2 app and update this post.
Click to expand...
Click to collapse
Definitely let us know how this plays out.
Like the other guy said though this certainly highlights the reason a lot of people are scared to encrypt. their phones. I hope you get it going again!
Sent from my SCH-I545 using Tapatalk
I was able to encrypt my phone while running carbon. Upon completion, I rebooted into recovery and wiped to install a new ROM. I installed the stock(ish) ROM running 4.3. I then updated my profile and the device activated. Everything works as it should.
I tried installing a stock rooted NAE ROM and it installed fine. The handset was taking ages to update though. I flashed the NAE modem, but that doesn't work either. All in all I'm still happy.
edit/
I have updated the original post with more information about what I did. If anyone faces this problem, let me know and I will try to help you the best I can.
Guys need help urgently.
Today i uninstalled a software called smule and it caused by phone to hang. This automatically restarted my phone and was stuck at the Samsung Logo.
Tried to do soft reset did not work, tried wipe cache from recovery did not work. When I try to mount from the system recovery it will not connect to my PC.
I have 40 GB of pic and videos on my phone which I just can't loose. Need to recover anyhow. Hence one option that i can think of is using the TWRP recovery and mount the phone and copy my important data to pc.
My phone is the 128 GB version Black Pearl. Box say SM-g935FD1
Please help as the data is very precious to me - I don't mind loosing all the apps and settings but can't afford loss of data for me.
I can enter recovery mode and download mode. But can't enter the safe mode.
I have downloaded the following twrp-3.1.1-0-hero2lte.img and ODIN.
Forget twrp. This thing require your /data to be formated first to be able to read data.
Sent from my SM-G935F using Tapatalk
NonXtreme said:
Forget twrp. This thing require your /data to be formated first to be able to read data.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Is there a way to get the data back if formatted.
Cant I install the TWRP and boot to the recovery and mount the disc to read. Even that will not be possible ?
kailashnj said:
Is there a way to get the data back if formatted.
Cant I install the TWRP and boot to the recovery and mount the disc to read. Even that will not be possible ?
Click to expand...
Click to collapse
No.
TWRP can't mount the disk because it is encrypted.
Data on S7 are encrypted by default.
You need to remove encryption by formatting before twrp be able to mount the disk. So any data before being formatted will be lost and unrecoverable.
Sent from my SM-G935F using Tapatalk
No way to recovery. NonXtreme said it as it is.
Just don't do anything that might compromise the data. Wait until someone with experience shows up and meanwhile take it to a samsung store. They might have the tools to bypass whatever causing the bootloop.
doctor_vai said:
Wait until someone with experience shows up
Click to expand...
Click to collapse
is 4 years on xda and over 350 posts not experience?
NonXtreme was correct in what he posted, so why are you saying ignore him?
Damn man. Really need to make regular backups to avoid this my first thought would have been TWRP but of course, as the guys above had said, you simply can't mount /data unless you format it first.
Was it simply an app install? I've never had this sort of thing happen over a simple install.
DON'T DO THIS YET. WAIT FOR FURTHER FEEDBACK.
Guys, could he install fw over the top with odin and home_csc to try avoid wiping data or does this still present an issue with encryption?
Or maybe even just the AP? I can't remember exactly which options wipe data and which ones don't.
Maybe you can try flashing with HOME_CSC. If I remember correctly that doesn't wipe anything - apps and data all remain as-is. Only point where you might be stuck is that during the flashing process or at first boot it will ask for a Pin, and if you have not setup a start up pin in secure startup, you can simply enter "default_password" (without quotes - used to work with older firmwares for S7 edge, but I think I read somewhere that this pin trick now doesn't work with latest one) - so maybe flash the latest and try, if that doesn't work flash an older firmware (with HOME_CSC) and boot and connect your phone to pc and recover - though phone will keep throwing force close errors, and once data is copied flash latest with CSC (instead of HOME_CSC) to wipe the phone clean and start afresh.