I screwed up my stock slot and was wondering if its safe to reset it as long as i disable OTA IMMEDIATELY after said restore?
I do not have any other roms on my device.
Bootloader is locked.
I DO HAVE SAFESTRAP ACTIVE (what im worried will screw up the restore).
I am rooted.
Yes, my device slot is beyond manual repair (system ui crashes with unknown error, libwebview crashes with missing index error, etc.).
Moral of the story: don't fall asleep ontop of your tablet whilst wakelock is active and es filemanager is open.
I just need to know if there is any risk of bricking my tablet or worse, efusing it.
Yes.
terra_byte_tech said:
I screwed up my stock slot and was wondering if its safe to reset it as long as i disable OTA IMMEDIATELY after said restore?
I do not have any other roms on my device.
Bootloader is locked.
I DO HAVE SAFESTRAP ACTIVE (what im worried will screw up the restore).
I am rooted.
Yes, my device slot is beyond manual repair (system ui crashes with unknown error, libwebview crashes with missing index error, etc.).
Moral of the story: don't fall asleep ontop of your tablet whilst wakelock is active and es filemanager is open.
Click to expand...
Click to collapse
So you didn't backup your stock slot, i.e. you can not restore that backup via Safestrap?
Using an official Amazon file for this is quite risky.
Would be interesting if someone would've a Safestrap backup of the Fire OS you need - which Fire OS and Safestrap versions are on your HDX anyway?
Cl4ncy said:
So you didn't backup your stock slot, i.e. you can not restore that backup via Safestrap?
Using an official Amazon file for this is quite risky.
Would be interesting if someone would've a Safestrap backup of the Fire OS you need - which Fire OS and Safestrap versions are on your HDX anyway?
Click to expand...
Click to collapse
I'm using the built in restore utility (accessed by holding down volume buttons on boot). Not safestrap's.
Sent from my KFTHWI using XDA Premium 4 mobile app
EncryptedCurse said:
Yes.
Click to expand...
Click to collapse
Do you mean: "yes, it's safe to restore" Or "yes, there is risk involved"
Sent from my KFTHWI using XDA Premium 4 mobile app
terra_byte_tech said:
Do you mean: "yes, it's safe to restore" Or "yes, there is risk involved"
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You will likely loose access to Safestrap recovery if you to a 'factory reset' from stock recovery. Even if it does work you likely won't get to a usable version of FireOS. As I recall adb and other forms of tethered communication are difficult/impossible with Safestrap v3 (you didn't say) so restoring an image captured elsewhere will be a challenge. There are reports OSX can communicate via adb in Safestrap v4. Haven't tested that. Would have to track down the post to see if it applies; need more details before investing the effort.
You don't have a lot of good options. Best keep reading. In your shoes I would NOT do a factory reset as it's an extreme long shot that will remove any hope of recovery if it does not work.
terra_byte_tech said:
I'm using the built in restore utility (accessed by holding down volume buttons on boot). Not safestrap's.
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You should've clarified that you were talking about a factory reset. I thought you were just restoring a backup within Safestrap.
Frankly, I'm not sure it'll solve anything. A factory reset doesn't just magically fix everything; it will only wipe the /data partition, so any changes you made to /system will still be there.
If you can still boot into Safestrap, I'd try getting a stock system image onto the device and flashing it from there.
terra_byte_tech said:
I'm using the built in restore utility (accessed by holding down volume buttons on boot). Not safestrap's.
Click to expand...
Click to collapse
EncryptedCurse said:
You should've clarified that you were talking about a factory reset. I thought you were just restoring a backup within Safestrap.
Frankly, I'm not sure it'll solve anything. A factory reset doesn't just magically fix everything; it will only wipe the /data partition, so any changes you made to /system will still be there.
If you can still boot into Safestrap, I'd try getting a stock system image onto the device and flashing it from there.
Click to expand...
Click to collapse
To further clarify flashing any stock rom is risky in Safestrap. Best use one from here. Your bigger problem is getting anything, including an image file, on your device given you can only boot into Safestrap.
Davey126 said:
To further clarify flashing any stock rom is risky in Safestrap. Best use one from here. Your bigger problem is getting anything, including an image file, on your device given you can only boot into Safestrap.
Click to expand...
Click to collapse
okay, so i figured out my version via build.prop and im running 13.3.2.5
is it safe to restore using the 13.3.2.6 file in the post you mentioned?
thank you for your patience.
Related
I tried searching for this, but couldn't find anything.
Timeline:
Rooted, and installed safestrap via razr blade utility... perfect
installed cm 10.1 & gapps on boot sector #1 as instructed.... perfect
tested phone, everything is working great...
Performed a factory reset via android settings menu (phone belongs to a co-worker). on reboot phone is just black.
paid closer attention, and realized that after safestrap timed out, phone wasn't booting to anything.
Now I have no OS installed, and when I try to partition slot 1 to reinstall, I get an error that it is "unable to partition"
Is there anything I can do short of a SBF, and starting over from scratch?
Thanks in advance
mstrpeter said:
I tried searching for this, but couldn't find anything.
Timeline:
Rooted, and installed safestrap via razr blade utility... perfect
installed cm 10.1 & gapps on boot sector #1 as instructed.... perfect
tested phone, everything is working great...
Performed a factory reset via android settings menu (phone belongs to a co-worker). on reboot phone is just black.
paid closer attention, and realized that after safestrap timed out, phone wasn't booting to anything.
Now I have no OS installed, and when I try to partition slot 1 to reinstall, I get an error that it is "unable to partition"
Is there anything I can do short of a SBF, and starting over from scratch?
Thanks in advance
Click to expand...
Click to collapse
mORE ROM ARE NOT FUNCTIONALLY WHIT SAFESTRAP(DIRTY OR CATALYST V2 OR JELLY WIZ OR FTS 3.0 OR RAGE ROM AND D-WIZ)
mstrpeter said:
I tried searching for this, but couldn't find anything.
Timeline:
Rooted, and installed safestrap via razr blade utility... perfect
installed cm 10.1 & gapps on boot sector #1 as instructed.... perfect
tested phone, everything is working great...
Performed a factory reset via android settings menu (phone belongs to a co-worker). on reboot phone is just black.
paid closer attention, and realized that after safestrap timed out, phone wasn't booting to anything.
Now I have no OS installed, and when I try to partition slot 1 to reinstall, I get an error that it is "unable to partition"
Is there anything I can do short of a SBF, and starting over from scratch?
Thanks in advance
Click to expand...
Click to collapse
Maybe if you post in the correct section could find some adequate answers!
NOT HERE !
monkteo said:
Maybe if you post in the correct section could find some adequate answers!
NOT HERE !
Click to expand...
Click to collapse
Well, until a mod can move the thread, he still needs help, right?
Sent from my XT912 using Tapatalk 2
---------- Post added at 06:14 AM ---------- Previous post was at 05:57 AM ----------
mstrpeter said:
I tried searching for this, but couldn't find anything.
Timeline:
Rooted, and installed safestrap via razr blade utility... perfect
installed cm 10.1 & gapps on boot sector #1 as instructed.... perfect
tested phone, everything is working great...
Performed a factory reset via android settings menu (phone belongs to a co-worker). on reboot phone is just black.
paid closer attention, and realized that after safestrap timed out, phone wasn't booting to anything.
Now I have no OS installed, and when I try to partition slot 1 to reinstall, I get an error that it is "unable to partition"
Is there anything I can do short of a SBF, and starting over from scratch?
Thanks in advance
Click to expand...
Click to collapse
Seems to be a big gap between your first & second statements. Can you be more specific about why you did an FDR if everything was running right?
And where did you do it from, the stock, unsafe side or from the ROM in slot 1?
Sounds like you accidentally formatted internal storage where your ROM slots live, in which case, the least you'll have to do is to boot back to your stock side, uninstall recovery from the safestrap app & uninstall the app itself. Then use a file explorer to remove anything that says safestrap or twrp from your internal storage & reboot. Once it comes up, reinstall the safestrap 3.11 apk & install the recovery again & start over.
Your worst case, if you can't boot up into your stock ROM at all, is to use Matt's 1.82 utility to restore your stock image.
Sent from my XT912 using Tapatalk 2
mstrpeter said:
I tried searching for this, but couldn't find anything.
Timeline:
Rooted, and installed safestrap via razr blade utility... perfect
installed cm 10.1 & gapps on boot sector #1 as instructed.... perfect
tested phone, everything is working great...
Performed a factory reset via android settings menu (phone belongs to a co-worker). on reboot phone is just black.
paid closer attention, and realized that after safestrap timed out, phone wasn't booting to anything.
Now I have no OS installed, and when I try to partition slot 1 to reinstall, I get an error that it is "unable to partition"
Is there anything I can do short of a SBF, and starting over from scratch?
Thanks in advance
Click to expand...
Click to collapse
Did you make a backup of the stock system? Does the safestrap revovery screen still come up on reboot? Have you tried to delete slot 1 and re-create it? Or do the three wipes on slot1 (data/dalvik/cache) and re-install the ROM? Have you tried to hit the menu button (left side) and go back in to safestrap and enable the stock system? If the stock system will come back up you can go in and disable the recovery and remove safestrap and try to re-install it. If not I am afraid you will probably have to fastboot back to stock.
monkteo said:
Maybe if you post in the correct section could find some adequate answers!
NOT HERE !
Click to expand...
Click to collapse
sorry, the development forums are the only ones I ever read... didn't even think about it. my bad
garywojdan81 said:
Well, until a mod can move the thread, he still needs help, right?
Sent from my XT912 using Tapatalk 2
---------- Post added at 06:14 AM ---------- Previous post was at 05:57 AM ----------
Seems to be a big gap between your first & second statements. Can you be more specific about why you did an FDR if everything was running right?
And where did you do it from, the stock, unsafe side or from the ROM in slot 1?
Sounds like you accidentally formatted internal storage where your ROM slots live, in which case, the least you'll have to do is to boot back to your stock side, uninstall recovery from the safestrap app & uninstall the app itself. Then use a file explorer to remove anything that says safestrap or twrp from your internal storage & reboot. Once it comes up, reinstall the safestrap 3.11 apk & install the recovery again & start over.
Your worst case, if you can't boot up into your stock ROM at all, is to use Matt's 1.82 utility to restore your stock image.
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
twith70 said:
Did you make a backup of the stock system? Does the safestrap revovery screen still come up on reboot? Have you tried to delete slot 1 and re-create it? Or do the three wipes on slot1 (data/dalvik/cache) and re-install the ROM? Have you tried to hit the menu button (left side) and go back in to safestrap and enable the stock system? If the stock system will come back up you can go in and disable the recovery and remove safestrap and try to re-install it. If not I am afraid you will probably have to fastboot back to stock.
Click to expand...
Click to collapse
I did a factory reset, because the phone is not mine... I checked that everything was working and then reset so he'd start off the the setup wizard.
I think gary is right, I made a backup, which is gone, and I can't partition any of the rom slots? how did a fdr format everything except safe strap... is there no way to fix it without running the unbrick utiity and starting from scratch?
mstrpeter said:
sorry, the development forums are the only ones I ever read... didn't even think about it. my bad
I did a factory reset, because the phone is not mine... I checked that everything was working and then reset so he'd start off the the setup wizard.
I think gary is right, I made a backup, which is gone, and I can't partition any of the rom slots? how did a fdr format everything except safe strap... is there no way to fix it without running the unbrick utiity and starting from scratch?
Click to expand...
Click to collapse
An FDR should not have removed your stock ROM, just the user data. Shouldn't touch the system partition at all. Can you boot into the stock side? If you can't, your only option is to use the 1.82 utility to start fresh with the stock .16 image. Can you boot up the stock ROM?
Sent from my XT912 using Tapatalk 2
garywojdan81 said:
An FDR should not have removed your stock ROM, just the user data. Shouldn't touch the system partition at all. Can you boot into the stock side? If you can't, your only option is to use the 1.82 utility to start fresh with the stock .16 image. Can you boot up the stock ROM?
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
that's what I thought but here I am... I can't do anything but get to safestrap, if I exit safe strap it says No rom install and the screen goes black until I do a simulated battery pull
mstrpeter said:
that's what I thought but here I am... I can't do anything but get to safestrap, if I exit safe strap it says No rom install and the screen goes black until I do a simulated battery pull
Click to expand...
Click to collapse
instead of running the unbrick utility, cause it wasn't bricked... I just ran the razr blade utility again from scratch... flashed the stock rom from there and had to go through all the steps again... good to go now though.
Thanks for the help everybody
mstrpeter said:
that's what I thought but here I am... I can't do anything but get to safestrap, if I exit safe strap it says No rom install and the screen goes black until I do a simulated battery pull
Click to expand...
Click to collapse
Cant you just take stock based zips for safestrap and flash it
I know they may seem like some dumb questions, but coming from the Galaxy Nexus, somethings have been somewhat different on the S4.
I rooted my MDK VZW S4 using this method by open1your1eyes0:
http://forum.xda-developers.com/showthread.php?t=2290798
I can not find this answer to this...I know I'm rooted, but is the bootloader also unlocked?
On the Nexus I had a second step after rooting that was necessary to unlock the bootloader. I don't see any additinal steps for the bootloader anywhere on the forum. I know ME7 does not have a bootloader unlock option, but I'm on MDK.
Next question...
I later flashed the official version of ClockworkMOD Tocuh Recovery which I've been told has the LOKI mod.
At this point can I flash a ROM exactly like I did on my NEXUS through the custom recovery?
I'm looking to flash:
http://forum.xda-developers.com/showthread.php?t=2384362
And my last question regarding back ups and Nandroids...
On my Nexus, my internal storage automatically was partitioned, so doing full wipes before flashing a new ROM never touched my nandroids, titanium backups, photos, etc...
Is this the same on the Galaxy S4 now, or should I be backing everything up to the extSDcard?
Thanks in advance. I really appreciate your help.
Your bootloader is not technically unlocked. Instead it has been bypassed through the "Loki" exploit. This makes no difference whatsoever to you as a user, though. You can flash new ROMs to your heart's content.
With regards to a wipe, when you wipe the system, cache, etc. through your recovery program it will only wipe the folders necessary to erase the OS, kernel, etc. Your downloaded data will be left intact as long as you don't put it in a directory that's used to store OS files.
ymDroid said:
I know they may seem like some dumb questions, but coming from the Galaxy Nexus, somethings have been somewhat different on the S4.
I rooted my MDK VZW S4 using this method by open1your1eyes0:
http://forum.xda-developers.com/showthread.php?t=2290798
I can not find this answer to this...I know I'm rooted, but is the bootloader also unlocked?
On the Nexus I had a second step after rooting that was necessary to unlock the bootloader. I don't see any additinal steps for the bootloader anywhere on the forum. I know ME7 does not have a bootloader unlock option, but I'm on MDK.
Next question...
I later flashed the official version of ClockworkMOD Tocuh Recovery which I've been told has the LOKI mod.
At this point can I flash a ROM exactly like I did on my NEXUS through the custom recovery?
I'm looking to flash:
http://forum.xda-developers.com/showthread.php?t=2384362
And my last question regarding back ups and Nandroids...
On my Nexus, my internal storage automatically was partitioned, so doing full wipes before flashing a new ROM never touched my nandroids, titanium backups, photos, etc...
Is this the same on the Galaxy S4 now, or should I be backing everything up to the extSDcard?
Thanks in advance. I really appreciate your help.
Click to expand...
Click to collapse
You Cannot unlock the bootloader. There is a workaround called loki that will allow you to install a Lokied recovery. Once you have custom recovery, which it seems you have done, installed then you can flash roms. Just be careful with your wipes to know for sure what you are wiping and be sure to make Nandroid backups to your external sdcard. You can then store a copy on your PC. I do all backups to external sdcard as internal space is limited.
Sent from my Hyperdriven SCH-I545 Dev Edition using Tapatalk 4.
So...just to confirm...
The official version of ClockworkMOD Tocuh Recovery 6.0.3.6 does have the Loki, correct?
Can I confirm this somewhere?
The exploit is in getting your custom recovery to run at all. If you can boot into CWM, Loki has already done its job.
Perfect
CrookedKnight said:
The exploit is in getting your custom recovery to run at all. If you can boot into CWM, Loki has already done its job.
Click to expand...
Click to collapse
Makes perfect sense now.
Thank you!
I flashed Bone 1.1.4 with no issues.
My question is regaridng my home screen.
I know custom launchers like NOVA allow you back up your home screen layouts and settings.
Is there anyway to back up your home screen layouts off of the stock launcher, or in this case the stock TouchWiz home screen layouts?
ymDroid said:
I flashed Bone 1.1.4 with no issues.
My question is regaridng my home screen.
I know custom launchers like NOVA allow you back up your home screen layouts and settings.
Is there anyway to back up your home screen layouts off of the stock launcher, or in this case the stock TouchWiz home screen layouts?
Click to expand...
Click to collapse
Titanium Backup. ROM Toolbox PRO also has an excellent back up app included.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Titanium Backup. ROM Toolbox PRO also has an excellent back up app included.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
What feature on Titanium let's me back up my home screen layout?
ymDroid said:
What feature on Titanium let's me back up my home screen layout?
Click to expand...
Click to collapse
When you back up touch wiz home in tibu you can restore just data or the whole thing. Seems like I've done both and it worked out. Clear data from touch wiz home in application manager and you can get back to the default settings.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
When you back up touch wiz home in tibu you can restore just data or the whole thing. Seems like I've done both and it worked out. Clear data from touch wiz home in application manager and you can get back to the default settings.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your help with this.
ymDroid said:
Thank you for your help with this.
Click to expand...
Click to collapse
No problem. It's what its all about right.
Sent from my SCH-I545 using xda app-developers app
so my phone ran out of battery overnight and i charged it not using the stock charger cuz i was at a friends house, it booted all the way to the lockscreen, then shut off and booted again. i let it charge some more and it just went it to a bootloop, every so often reaching the lockscreen and turning off again. i have safestrap installed and i am on the latest 4.2 build. im thinking that i need to odin reset, but i want to see if theres a differerent way so i dont lose any data. if i do have to odin, how does one go about doing that?
thanks
ClassySandwiches said:
so my phone ran out of battery overnight and i charged it not using the stock charger cuz i was at a friends house, it booted all the way to the lockscreen, then shut off and booted again. i let it charge some more and it just went it to a bootloop, every so often reaching the lockscreen and turning off again. i have safestrap installed and i am on the latest 4.2 build. im thinking that i need to odin reset, but i want to see if theres a differerent way so i dont lose any data. if i do have to odin, how does one go about doing that?
thanks
Click to expand...
Click to collapse
Can you boot into safestrap? Do you still have your stock slot? Or did you put a rom over it?
gnubian said:
Can you boot into safestrap? Do you still have your stock slot? Or did you put a rom over it?
Click to expand...
Click to collapse
no roms at all, i tried but none would boot. and yes safestrap does indeed work. stock slot is the one that is having troubles and no other slots have roms on them
ClassySandwiches said:
no roms at all, i tried but none would boot. and yes safestrap does indeed work. stock slot is the one that is having troubles and no other slots have roms on them
Click to expand...
Click to collapse
Have you tried clearing cache and or data, to just start fresh on the stock?
ClassySandwiches said:
no roms at all, i tried but none would boot. and yes safestrap does indeed work. stock slot is the one that is having troubles and no other slots have roms on them
Click to expand...
Click to collapse
Did u try to install roms into your stock slot?
safestrap enabled, Hyperdrive driven
decaturbob said:
Did u try to install roms into your stock slot?
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
His wording is a bit unclear, but it sounds to me like he tried to install roms on the other slots and couldnt get them to boot, with the stock slot intact. OP, correct me if im wrong.
gnubian said:
His wording is a bit unclear, but it sounds to me like he tried to install roms on the other slots and couldnt get them to boot, with the stock slot intact. OP, correct me if im wrong.
Click to expand...
Click to collapse
yeah nothing with the stock slot, didnt mess with that. if i clear just the cache in stock what data will i lose if anything?
gnubian said:
His wording is a bit unclear, but it sounds to me like he tried to install roms on the other slots and couldnt get them to boot, with the stock slot intact. OP, correct me if im wrong.
Click to expand...
Click to collapse
PS, my phone has just started doing this, its wierd i thought because i havent tried anything with any of the rom slots for at least a couple of months now
ClassySandwiches said:
yeah nothing with the stock slot, didnt mess with that. if i clear just the cache in stock what data will i lose if anything?
Click to expand...
Click to collapse
If you clear cache and dalvik cache you won't lose any data or settings. If that doesn't work then do the factory reset in TWRP (safestrap) . That will make it as if you had a new phone. ( except the Safestrap and root access I believe). You will have to re download apps and change settings back to your liking, but it's better than having to odin back to stock.
gnubian said:
If you clear cache and dalvik cache you won't lose any data or settings. If that doesn't work then do the factory reset in TWRP (safestrap) . That will make it as if you had a new phone. ( except the Safestrap and root access I believe). You will have to re download apps and change settings back to your liking, but it's better than having to odin back to stock.
Click to expand...
Click to collapse
safestrap failed wiping the regular cache, but dalvik worked. got to the lockcsreen again and it even gave me a vibrate for my pattern but then it shut off again. right after the verizon boot animation theres a popup window that says "Android is upgrading" with "optimizing app XXX of XXX". ive seen this before, but only very occasionally. what exactly does this mean?
By the way thank you guys for helping, especially on new years
ClassySandwiches said:
safestrap failed wiping the regular cache, but dalvik worked. got to the lockcsreen again and it even gave me a vibrate for my pattern but then it shut off again. right after the verizon boot animation theres a popup window that says "Android is upgrading" with "optimizing app XXX of XXX". ive seen this before, but only very occasionally. what exactly does this mean?
Click to expand...
Click to collapse
I believe that is the normal process for dalvik to rebuild itself
"Android is upgrading" can come from wiping Dalvik cache, which is temporary info about your apps, that would need to be re mapped to the Android os. It can also come from doing a dirty flash or ota.
Your beginning post was about your data though, If you can get into safe strap then you should be able to mount your device to your pc, copy over what data you need, then wipe or Odin flash to bring it all back.
Sent from my SCH-I545 using xda app-developers app
jwoods82 said:
"Android is upgrading" can come from wiping Dalvik cache, which is temporary info about your apps, that would need to be re mapped to the Android os. It can also come from doing a dirty flash or ota.
Your beginning post was about your data though, If you can get into safe strap then you should be able to mount your device to your pc, copy over what data you need, then wipe or Odin flash to bring it all back.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Smart, didnt know TWRP can do that. couldnt i just use the factory wipe feature in safestrap?
You could use factory wipe but your data at that point would be gone. If your not worried about the data then sure.
If data truly is not a concern though Just download the Odin tar for what build you want and start new.
To answer your other question think of Odin as a recovery disc you would use on your computer. Destructive restore. There are some good posts about here in xda or search Google for Samsung s4 Odin and I know your find some good reads.
Good luck
Sent from my Verizon Samsung Galaxy S4 with HD12 on Stock Side
Retired Phones / Devices
- Eris
- Droid 2
- Droid X
- Fascinate
- HP Touchpad
- Thunderbolt
- Droid Raxr
jwoods82 said:
You could use factory wipe but your data at that point would be gone. If your not worried about the data then sure.
If data truly is not a concern though Just download the Odin tar for what build you want and start new.
To answer your other question think of Odin as a recovery disc you would use on your computer. Destructive restore. There are some good posts about here in xda or search Google for Samsung s4 Odin and I know your find some good reads.
Good luck
Sent from my Verizon Samsung Galaxy S4 with HD12 on Stock Side
Retired Phones / Devices
- Eris
- Droid 2
- Droid X
- Fascinate
- HP Touchpad
- Thunderbolt
- Droid Raxr
Click to expand...
Click to collapse
would it just be easier to do the safestrap wipe instead of an Odin one? ive read up on Odin and it seems a lot more complicated than just using safestrap
ive decided that data isnt important because most everything is saved in google play and plus. so what is the most reliable way to get my phone working again? Safestrap reset?
ClassySandwiches said:
ive decided that data isnt important because most everything is saved in google play and plus. so what is the most reliable way to get my phone working again? Safestrap reset?
Click to expand...
Click to collapse
Safestrap would be easier. I would give that a try, because if it doesn't work your only other option would be Odin.
jwoods82 said:
You could use factory wipe but your data at that point would be gone. If your not worried about the data then sure.
If data truly is not a concern though Just download the Odin tar for what build you want and start new.
To answer your other question think of Odin as a recovery disc you would use on your computer. Destructive restore. There are some good posts about here in xda or search Google for Samsung s4 Odin and I know your find some good reads.
Good luck
Sent from my Verizon Samsung Galaxy S4 with HD12 on Stock Side
Retired Phones / Devices
- Eris
- Droid 2
- Droid X
- Fascinate
- HP Touchpad
- Thunderbolt
- Droid Raxr
Click to expand...
Click to collapse
did the safestrap reset, it worked
ClassySandwiches said:
did the safestrap reset, it worked
Click to expand...
Click to collapse
Glad you got it sorted out! Now make a backup after you get it set back up to make it easier if it happens again
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle
So I was messing around with resolution and DPI settings. Changed it to 1920x1080 and 400dpi, rebooted. Now SystemUI crashes constantly and I can't do anything other than close the dialog window and use the power menu. Can't tap anything else (it shows Nova Launcher behind everything) and tried a USB mouse and keyboard via OTG, can't do anything extra with those. I feel like the keyguard is still on, but the same thing happens regardless of whether I do my knock code or a normal screen-on.
Safe mode doesn't help (other than disabling my 3rd party camera app allowing me to use the vol-down shortcut into the camera). I feel like if I could just get access to a root adb shell it would be pretty easy, but neither the stock recovery nor download mode allow for ADB.
I'd like to at least be able to pull smsmms.db so I can just flash back to stock and manually recover my messages.
(remind me to stop messing with things without TWRP or CWM or something...)
just ended up flashing back to stock and walking away with a lesson learned the hard way
Instructions on flashing back to stock?
Sent from my Nexus 5 using XDA Free mobile app
noutoo said:
Instructions on flashing back to stock?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2799647
scy1192 said:
http://forum.xda-developers.com/showthread.php?t=2799647
Click to expand...
Click to collapse
...or, just boot into stock recovery and factory reset (Power + Down(?) Button). Had to do this last nite when I over-froze in TiBu. Can't wait for custom recovery.
tbcpn said:
...or, just boot into stock recovery and factory reset (Power + Down(?) Button). Had to do this last nite when I over-froze in TiBu. Can't wait for custom recovery.
Click to expand...
Click to collapse
factory reset doesn't affect anything outside of /data, so it wouldn't have fixed my issue (I'm thinking the app I used put something in some sort of boot script since safe mode didn't work)
scy1192 said:
factory reset doesn't affect anything outside of /data, so it wouldn't have fixed my issue (I'm thinking the app I used put something in some sort of boot script since safe mode didn't work)
Click to expand...
Click to collapse
Yeah, I know that's generally the case, but in this instance it appeared to re-flash the entire /system...and, it wiped internal sdcard file, which is unusual, at least compared to "factory reset" in TWRP or CM. I'd inadvertently frozen a couple of critical system files in TiBu and bootlooped the phone.
In any event, solved my issue, but lost my TiBu backup on internal sdcard, which made for an extra couple hours work.