[Q] Custom Recovery (TWRP) + Phone Encryption = No good? - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Hey guys, I've been having some issues with my AT&T S 4; I'm on KANGAKAT 6.0 (4.4.2), and I recently had to enable phone encryption on my phone for work, so that I could sync my work data to my phone.
Everything has been working fine and dandy until I found out there was a new version of my ROM, and new modems as well. I booted into recovery (TWRP), only to find out that while in recovery, TWRP does not have access to my internal memory since it is encrypted; it always fails to mount the internal storage. I tried updating to the latest TWRP, but it still does not work. I google'd around and apparently your recovery is supposed to ask you for the encryption key, but mine never does.
I wanted to try PhilZ custom recovery or ClockworkMod, but I have not found a Loki'd .img file I could install via Terminal, I've only seen flash methods, which I can't use since I can't use my recovery to write to my phone. I'm going to keep looking, but if anyone has a link to a recovery file I could manually install, that would be greatly appreciated.
Am I doing something wrong, or am I on the correct path to try to find a working recovery?
Edit:
Ok, so after more digging, it seems that I was wrong, recoveries can NOT mount an encrypted /data partition, ever. I was able to succesfully get PhilZ recovery installed, and it too was unable to mount /data. However my /system partition was able to be mounted, so I guess that's kind of what I wanted, I'll miss being able to make nandroid backups though. Hopefully I can update my modem without any problems.

Just like the recovery, the modem also gets flashed to a separate space. So, you should be able to update it without problem.
Sent from my GT-I9505G using Tapatalk

jmjoyas said:
Just like the recovery, the modem also gets flashed to a separate space. So, you should be able to update it without problem.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Yep, I just finished flashing the modem and it worked fine with PhilZ =). For some reason it wouldn't work with TWRP.
I guess the only question remaining now is can I update my ROM?

Related

[Q] i9505 /system mount trouble

Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.
Schildkamp said:
Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.
Click to expand...
Click to collapse
OMG! same issue here.. exactly, please HELP someone!!!
Format /system in recovery and then try flashing cm. It shouldn't be an issue mounting system if the partition is formated.
live-evil said:
Format /system in recovery and then try flashing cm. It shouldn't be an issue mounting system if the partition is formated.
Click to expand...
Click to collapse
Please elaborate for me,
Wipe does a format of the partition, is that enough or do I need to actually to use Format in the menu, as in kill the whole internal storage?
thanks
Linus
wipe is enough
live-evil said:
wipe is enough
Click to expand...
Click to collapse
thanks for the answer,
I hoped for that and also tried it.
No fun
I think I'll have to go for full format.
Just hope that does nothing bad >.<
Or is CWM maybe a better alternative?
DemonWareXT said:
thanks for the answer,
I hoped for that and also tried it.
No fun
I think I'll have to go for full format.
Just hope that does nothing bad >.<
Or is CWM maybe a better alternative?
Click to expand...
Click to collapse
what error message did you get?
I had the same problem yesterday in twrp 2.5.0.1 I just formated system and preload and factory resteted and then just rebooted and formated system again and it worked.
Grusburk said:
I had the same problem yesterday in twrp 2.5.0.1 I just formated system and preload and factory resteted and then just rebooted and formated system again and it worked.
Click to expand...
Click to collapse
Hehe I well tried that one,
no luck
interesting since 2.5.0.2 it says, unable to mount /system, and then promptly crashes
oh and the same happened in CWM
Hell XD
could I flash AOKP via odin maybe?
not like I like the idea >.<
It generally takes a few goes for the recovery to flash the rom in s4. Until someone works out what causes that bug in the recoviers you kind of just have to reboot and try again and again if necessary until it sticks.
live-evil said:
It generally takes a few goes for the recovery to flash the rom in s4. Until someone works out what causes that bug in the recoviers you kind of just have to reboot and try again and again if necessary until it sticks.
Click to expand...
Click to collapse
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help
Schildkamp said:
Hi.
I've searched through a LOT of posts, but only found slightly related (and for me unhelpful) comments.
I have a GT-i9505 (i9505xxuame2), and rooted/flashed it using Odin / modified_cf_root. However, although I have succsessfully installed TWRP - AND have (seemingly) been able to make a full backup to my external sdcard, I am completely unable to install CM 10.1 nightly / AOKP (both i9505 versions).
Whenever i try this (via recovery of course), it always fails, reporting it was unable to mount /system. When restarting the phone, it just 'hangs' on the splash screen. The only solution then is to restore my backup, which works fine... HOWEVER, I suspect that since it has problems with the /system folder, It might not actually have backed this up, and that restore only works because /system happens to be untouced by my attempts to flash it.
Trying various tips & tricks found here on XDA - like manually mounting /system in TWRP, reflashing in Odin etc. has not helped me. I also noticed that when entering download-mode, it states that write protection is enabled (as in this thread - which unfortunatly also did not solve my problem: http://forum.xda-developers.com/showthread.php?t=2267107). I also tried CWM, but using this I'm unable to manually mount both /system, /sdcard AND extSdcard (or whatever extrenal memory was called... don't remember.. ) - and it of course has the same problems trying to flash either ROM.
My feeling is that my unit is not (fully) rooted, but like I said, I've been unable to find a solution. I really hope you can help, because I'd love to have CM on this delightful piece of hardware.
Click to expand...
Click to collapse
Crap. Have same problem.
I had this problem after flashing MH8 firmware (new bootloader) with Odin.
No matter what I tried in recovery I kept getting an error saying that it failed to mount system.
I had an older version of PhilZ on my ext SD luckily, so I flashed this, rebooted recovery then I could format system and it was mounted again.
then just flashed my newer recovery back and all was good
Hi guys,
it appears I'm having similar issues to you both but after 5 hours of constantly trying to fix this I'm still stuck! I've opened a new thread and I was wondering if you might be kind enough to help me out on there please?
Here's a link to the thread - would really appreciate any help you could provide... http://forum.xda-developers.com/showthread.php?p=46082532
Obagleyfreer said:
I had this problem after flashing MH8 firmware (new bootloader) with Odin.
No matter what I tried in recovery I kept getting an error saying that it failed to mount system.
I had an older version of PhilZ on my ext SD luckily, so I flashed this, rebooted recovery then I could format system and it was mounted again.
then just flashed my newer recovery back and all was good
Click to expand...
Click to collapse
DemonWareXT said:
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help
Click to expand...
Click to collapse
Sh*t! Sorry:laugh: It really works! At least on my LG G2 D802. Thx, man!
---------- Post added at 01:46 PM ---------- Previous post was at 01:12 PM ----------
DemonWareXT said:
Aright, I think I found the way for me
Boot into recovery --> wipe system --> mount system --> if ok --> flash
if not ok --> retry the whole process
Strange stuff, but yay thanks all for your help
Click to expand...
Click to collapse
Sh*t! Sorry:laugh: It really works! At least on my LG G2 D802. Thx, man!

Factory Reset wiped out the internal SD card! I thought it's not meant to happen?!

This is the first time I'm using a device that doesn't have an external SD card, but I've all along understood that the internal SD card does not get wiped when you do a factory reset, and I'm sure I read that again on another thread just the other day.
My N7 is rooted using Wug's toolkit, with CM10.2 and Bulletproof kernel.
Yesterday I decided to do a factory reset (under Settings, Backup & Reset, Factory Data Reset), but after I did it, all the stuff I had on the internal SD was gone, including my backup files, the ROMs I had transferred there, etc.
Surely this is not meant to be the case, is it??
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
sfhub said:
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
Click to expand...
Click to collapse
Thanks for that! (Thanks coming your way). Well, better to know now than later! The down side is that I lost my CWM backups and my Titanium Backup files, but the good thing is that I think I have a TWRP backup that's on my computer.
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
oohyeah said:
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
Click to expand...
Click to collapse
I am not sure what issue you are having with TWRP, but you can flash it to the recovery partition and boot to it automatically. If that's the only reason you don't like it, I'd work on fixing the install rather than jumping to another recovery.
oohyeah said:
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Click to expand...
Click to collapse
I would probably do it from recovery. I don't know what CWM does on this platform as I've only used it on other platforms.
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Sent from my Nexus 7 using xda app-developers app
geckocavemen said:
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Click to expand...
Click to collapse
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign. I remember doing some searches and it seemed like this was normal. I remember the reason was that the N7 would always rewrite the recovery or something. From your responses, I'm guessing it's not normal?
The only way I could get into recovery was using the Wug toolkit using USB debugging/ADB, which really sucked, cos if it bootlooped and I can't get into the system to turn on USB debugging, then I'm not sure what I would do (though I read there's some way around it or something). I had never encountered any such thing with all my many other devices which all run CWM.
So what's up with all that?
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
User_99 said:
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
Click to expand...
Click to collapse
This will work fine. If you have no aversion to installing apps, Rom Toolbox Lite gives you power widgets you can put on your desktop then go to recovery with one touch. I use Quick Boot PRO, although the free version of that all may do recovery also. One might work for you until you want to play with mods.
Sent from my Nexus 7 using Tapatalk 4
oohyeah said:
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign.
Click to expand...
Click to collapse
That is stock recovery.
You need to get rid of /system/etc/install-recovery.sh
You can get rid of it by hand, or just install SuperSU from TWRP. Then flash TWRP to the recovery partition.
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
oohyeah said:
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
Click to expand...
Click to collapse
None of your blunders has anything to do with TWRP.
khaytsus said:
None of your blunders has anything to do with TWRP.
Click to expand...
Click to collapse
OK let me get something straight.
Obviously, the factory resetting that wiped out all internal storage (the original point of the thread) has nothing to do with TWRP, and I never said it did. On this point though, I'm surprised that it doesn't seem to be more well known that a factory reset would do wipe out all your data (did several searches and only found 'confirmations' that your internal SD data would be left untouched), though I'm glad that I know it now.
The suggestions on different ways to boot into recovery were helpful, though I believe that I would still have encountered the dead android, or would I not have?
What's certainly still not clear to me though is regarding the problem of not being able to boot into recovery and getting the dead android with the exclamation/triangle. After the first few replies, I expected to hear that this was NOT meant to be the case and that I did something wrong in the process or whatever.
However, what I seemed to get was that this is the expected behavior, and what I needed to have done was to "get rid of /system/etc/install-recovery.sh".
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
oohyeah said:
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
Click to expand...
Click to collapse
Dead android = stock recovery, so normal there.
When you flash a custom recovery on a stock ROM, there is a file, /system/etc/install-recovery.sh, or I actually prefer just renaming /system/recovery-from-boot.p, which will automatically verify your recovery image and restore it to stock if it doesn't match. So you must always remove this file, or the ROM will restore the stock recovery on boot.
TWRP makes it easy to remove either file by mounting /system in read-write mode and using its built-in file manager to remove it. You can do the same in CWM using adb.
As for point 3, yes, try to reboot into recovery again. If you didn't remove (either file), you'll find stock recovery again.
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
oohyeah said:
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
Click to expand...
Click to collapse
It really depends on what ordering you do your actions in.
/system/etc/install-recovery.sh doesn't exist on a stock factory shipped system.
It only gets put in place after you install an OTA. If you do all your upgrades using the factory images, you'll never encounter it.
What it does is during your boot process, it will check to see if your recovery is different than what it expects (ie stock). If so, it will install stock recovery by taking the stock kernel and patching it.
If any of the following are true, it will not overwrite your recovery:
/system/etc/install-recovery.sh is missing (or modified to not run as the original file)
/system/recovery-from-boot.p is missing
you are not running the stock kernel
The most common way for install-recovery.sh to be missing is you always used factory images.
The most common way for install-recovery.sh to be modified to not do the original function is if you installed SuperSU. It will overwrite install-recovery.sh with its own.
So in all the back and forth, it is quite possible you got rid of install-recovery.sh or had it modified simply by installing root.
If you then subsequently installed custom recovery, it would stay in place.
Previously you were installing TWRP and flashing it onto the tablet, but upon booting into android, install-recovery.sh realized it wasn't stock recovery, and overwrote TWRP with stock recovery.
That is why whenever you rebooted, you got fallen android (which is stock recovery)
If the way you installed cwm is to use "fastboot flash recovery cwm.img" then the only reason it is around is because something else you did got rid of or modified install-recovery.sh. cwm would be no more immune to install-recovery.sh than twrp was.
oohyeah said:
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
Click to expand...
Click to collapse
Just to clarify, you didn't lose root. You just lost the supersu app, a root permission manager, because it was installed to your /data partition. The su binary was still in /system, all you would have had to do was install supersu from the market.
I'm not sure what else you were expecting from a "factory reset"
creaturemachine said:
I'm not sure what else you were expecting from a "factory reset"
Click to expand...
Click to collapse
Did you read the thread? He explained his reason for expectation quite well.
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Skaziwu said:
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Click to expand...
Click to collapse
Depending on which level you are looking at, it didn't really change the behavior, but rather how your data is organized.
Factory reset has always wiped out /data.
On older devices, they put the /sdcard in a separate partition and formatted fat32.
These are the ones that were surviving a factory reset.
On newer devices, the internal /sdcard is starting to migrate onto a directory in /data and the "sdard" you see is "virtual". Since it is on /data, when you wipe data, the virtual sdcard is also wiped.
Some recoveries try to simulate the previous behavior by doing a "rm" of every directory except the virtual sdard when you choose to wipe, instead of the erase/format that Android is doing.
The advantage of keeping the sdcard as a directory under /data is you don't need to decide how much space to split between the sdcard and your /data. Also permissions on files are more flexible being in an ext4 filesystem. Finally since everything is emulated and accessed via MTP, you don't need to unmount the filesystem, so your PC can access it.
There are also cons with this approach, but that is what Google is going with.

Major Problem using TWRP

Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
doesntmatterx said:
Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
doesntmatterx said:
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
Click to expand...
Click to collapse
:good:
xBeerdroiDx said:
:good:
Click to expand...
Click to collapse
I take it back, stuck in a boot loop even after 2 fresh ODIN unroot tasks. Nothing I do gets me out of this, been a long day getting longer now
Can anyone help? Been at it for hours, I have tried everything, phone still reboots at the Samsung logo (the bluish one )
Unrooted 3 times
Launched stock recovery, wiped factory reset
wiped partition cache
removed battery
Cannot connect to Kies for Emergency restore.
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
seanpr123 said:
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
Click to expand...
Click to collapse
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
doesntmatterx said:
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
Click to expand...
Click to collapse
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Should I ODIN with the RE-Partition Option?
Just Odined again and no dice. I booted into stock recovery and noticed after wiping factory I get "Can't open /efs/log/boot_cause" which pointed me to this fix someone on the Galaxy note forum said they did and it worked but I dont understand the steps, need some elaboration.
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
jd1639 said:
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Click to expand...
Click to collapse
Yep did that mulitple times, also did wipe cache partition in the same stock recovery. I get to the Samsung logo where the blue halo spins around the name, then it freezes there and reboots.
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
seanpr123 said:
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
Click to expand...
Click to collapse
LOL thanks, yes I may have to do that. I had a backup and it was wiped.
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Try flashing using cwm. It'll probably work fine. Then you can go back to twrp. That's worked on other devices. Seems one you flash it once with cwm then twrp works from that point forward. Idk why
doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
jds3118 said:
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I tried flashing with a PIT file I found online but it fails through ODIN everytime. I tried on multiple versions of ODIN as well. I also cant seem to find readily available PIT files to test as well, (perhaps the one I used does not work). Also I did try to flash a CWM through ODIN but failed, but again there isnt anything that I have read that says "hey you can do this that way and it will work".
From what I understand I need to be rooted to install CWM or TWRP, and since I unrooted to try and fix the problem I cannot root myself through conventional methods. Everything I found online requires the phone to completely start up. (to the menu screen etc)
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
jd1639 said:
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
Click to expand...
Click to collapse
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
doesntmatterx said:
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
Click to expand...
Click to collapse
Do you know what firmware you were on? Was it mdl or mf3?

vs980 need help ASAP!

I was attempting to flash a new rom from twrp, I did advanced wipe and accidentally wiped my sd card partition, now I am stuck in twrp with nothing to flash, recoveries are gone as well, how do I add a flashable zip to the phone to fix it??
Jc8206 said:
I was attempting to flash a new rom from twrp, I did advanced wipe and accidentally wiped my sd card partition, now I am stuck in twrp with nothing to flash, recoveries are gone as well, how do I add a flashable zip to the phone to fix it??
Click to expand...
Click to collapse
I had this problem using Philz Recovery, and ultimately sideloaded a zip with ADB and was able to flash that.
Being that it's TWRP, the process will be slightly different.
http://teamw.in/ADBSideload
Bwangster12 said:
I had this problem using Philz Recovery, and ultimately sideloaded a zip with ADB and was able to flash that.
Being that it's TWRP, the process will be slightly different.
http://teamw.in/ADBSideload
Click to expand...
Click to collapse
the phone has been sitting at starting adb sideloadm feature for a while now, does it take a while to load up?
now i cant for the life of me get adb to recognize my device, Ive installed the drivers with no luck
will the rom zip show up in my file list in twrp? or does adb install the rom?
Adb installs it with a push command. You have to put the rom in the same folder as your adb on pc.
Sent from my VS980 4G using Tapatalk
Finally got it, thanks for the info

Recovery can't mount data

Hello, I am a novice at best when it comes to this. That being said I have successfully Unlocked my boot-loader, rooted and installed roms to my phone. Recently when using TWRP 2.7 I noticed that it would not mount data when restoring my backup. I then noticed it would not mount data when creating a new backup while using TWRP 2.7. I then installed CWM latest recovery. It does the same thing. In the process I got stuck in CWM and had to AP Fastboot to stock 4.4.2. Now with CWM it will not mount data when doing a backup. I cant load a rom without having a secure backup. What can I do? Need help! Calling all devs!
I'm pretty sure that the only recovery available is CWM for the RAZR HD. However, that recovery can't mount data. I don't think there is a custom recovery right now that had full functionality for the RAZR M.
With that said, the kernel sources have been released, so I would say its only a matter of time before an updated recovery is available that can support mounting data.
Sent from my XT907 using Tapatalk
queue72 said:
I'm pretty sure that the only recovery available is CWM for the RAZR HD. However, that recovery can't mount data. I don't think there is a custom recovery right now that had full functionality for the RAZR M.
With that said, the kernel sources have been released, so I would say its only a matter of time before an updated recovery is available that can support mounting data.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I have had TWRP work just fine in the past. Others are having no problem with them as I can tell. This is an original Razr M.
ehunter74 said:
I have had TWRP work just fine in the past. Others are having no problem with them as I can tell. This is an original Razr M.
Click to expand...
Click to collapse
There is no TWRP designed for the KK update, yet. CWM is only working aftermarket recovery right now. TWRP should be out any day.
OK let me give more details. I was running Beanstock Rom with Android 4.3 on my ORIGINAL XT907. I was running TWRP 2.6 flawlessly. I tried to load a new ROM (KitStock 4.4.2). When I tried to backup my current configuration with TWRP it would not mount data during the backup procedure. I panicked and backed out. I seen that CWM was a better choice and installed CWM v6.0.4.8 It also would not load data during backup. I then tried to back out of that and it got stuck on boot. would not go past no matter what. tried to load KitStock ROM anyway. Same effect. I could still get back into CWM recovery and also bootloader. I then installed the latest STOCK ROM I could find and it is version 183.46.10XT907.Verizon.en.US. Kernal is [email protected]#1. Build number KDA20.62-10.1 Android version 4.4.2
I think what I have discovered is that I must have a "working" corrupted file script whit this stock ROM. I discovered that if I formatted my SD card I could mount the data and backup my nandroid. So my SD card was corrupted??? Also after I knew I had a good backup when I tried to install CM10.1 it gave me a status 7 error. Ok did the status 7 fix by editing the script on two different ROMs. It still aborts installation. Now I consider myself a noob but I'm no stranger to the ROM installation process. I've done all the right steps. Backup. Wipe 3x, mount system, install. This seems like a deeper problem. Please HELP!

Categories

Resources