Related
Not sure if this has been posted before, I did some searching but there are so many threads and posts I couldn't look through them all. So I apologize in advance if this has been posted before.
I have a Galaxy S4 on ME7, rooted with SafeStrap installed. I had a bit of an issue last night, I installed BoneStock on a custom ROM slot as instructed, and it booted up just fine. WiFi didn't work (it just wouldn't turn on), and I figured that could be because of the modules not being there or something, I remember reading in the SafeStrap thread that there's a zip you're supposed to flash after flashing a ROM that I assumed had those modules within. In the BoneStock power options menu (I think, can't exactly remember) there was an option to reboot to recovery. I pressed that, and it sent me to download mode with no apparent way of getting out. Did a battery pull and tried the Volume Up/Power combination, which didn't work I assume because the bootloader is locked so the recovery isn't actually installed where the regular recovery is? Please correct me if I'm wrong.
Anyway I ended up getting back onto stock ME7 by reflashing through Odin and it kept all my data. I sent a few texts, just played around on the phone this morning but I had to reinstall recovery through SafeStrap because the flash got rid of it. So I reinstalled recovery, rebooted into it, and it still had Custom Rom slot 1 active. I changed it to stock ROM, rebooted, and the phone looked exactly as it did in custom rom slot 1, complete with the texts I had sent after reflashing.
Sorry for the wall of text, but here are my questions:
1) Is that normal for reboot to recovery to not work on ME7 ROMs? I assume it is, just wanted to make sure I hadn't done anything wrong.
2) Why were my texts still there even after switching it through SafeStrap to reboot to the stock ROM, when I had apparently sent/received the texts in Custom Rom 1? And why was all the data I had in the stock ROM slot in the Custom ROM slot after reflashing even though I never installed anything to that slot except BoneStock, then reflashed stock?
Sorry if these are silly questions, but I haven't had an Android for a while (got an iPhone 5 for my last phone, such a mistake) so my knowledge of rooting/recovery/etc is a bit lacking.
gmonox said:
Not sure if this has been posted before, I did some searching but there are so many threads and posts I couldn't look through them all. So I apologize in advance if this has been posted before.
I have a Galaxy S4 on ME7, rooted with SafeStrap installed. I had a bit of an issue last night, I installed BoneStock on a custom ROM slot as instructed, and it booted up just fine. WiFi didn't work (it just wouldn't turn on), and I figured that could be because of the modules not being there or something, I remember reading in the SafeStrap thread that there's a zip you're supposed to flash after flashing a ROM that I assumed had those modules within. In the BoneStock power options menu (I think, can't exactly remember) there was an option to reboot to recovery. I pressed that, and it sent me to download mode with no apparent way of getting out. Did a battery pull and tried the Volume Up/Power combination, which didn't work I assume because the bootloader is locked so the recovery isn't actually installed where the regular recovery is? Please correct me if I'm wrong.
Anyway I ended up getting back onto stock ME7 by reflashing through Odin and it kept all my data. I sent a few texts, just played around on the phone this morning but I had to reinstall recovery through SafeStrap because the flash got rid of it. So I reinstalled recovery, rebooted into it, and it still had Custom Rom slot 1 active. I changed it to stock ROM, rebooted, and the phone looked exactly as it did in custom rom slot 1, complete with the texts I had sent after reflashing.
Sorry for the wall of text, but here are my questions:
1) Is that normal for reboot to recovery to not work on ME7 ROMs? I assume it is, just wanted to make sure I hadn't done anything wrong.
2) Why were my texts still there even after switching it through SafeStrap to reboot to the stock ROM, when I had apparently sent/received the texts in Custom Rom 1? And why was all the data I had in the stock ROM slot in the Custom ROM slot after reflashing even though I never installed anything to that slot except BoneStock, then reflashed stock?
Sorry if these are silly questions, but I haven't had an Android for a while (got an iPhone 5 for my last phone, such a mistake) so my knowledge of rooting/recovery/etc is a bit lacking.
Click to expand...
Click to collapse
Not sure if this helps but I never boot into Recovery directly from the ROMs. I always just go to regular reboot and then press the menu key to get into SS.
vzwnexus said:
Not sure if this helps but I never boot into Recovery directly from the ROMs. I always just go to regular reboot and then press the menu key to get into SS.
Click to expand...
Click to collapse
That is correct. The best way is use power and just reboot. The one in the ROM is meant to take you to the real recovery not ss
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
Hi All,
My friend use Apollo 14.3.2.3. I follow the guides and help to downgrade to 14.3.1.0. Then, I also helped him to install safestrap and Apollo Gapps Version 1.2. Everything was fine and prefect.
However, my friend tried to use factory reset at Gapps rom v1.2 without telling me. It made Kindle can't boot. Fortunately, he can go to recovery and make stock rom active. It can boot. However, I found that this is not original stock rom. I think the stock rom was replaced by Gapps rom v1.2.
Does anyone know how to restore the original stock rom? I have a stock rom backup copy from my kindle. Can I use that?
Thanks in advance.
Why not just autoupdate? That would lose you root but you can get it back.
http://forum.xda-developers.com/showthread.php?t=2793253
Thank you for all suggestion. Now, the HDX 8.9 is not bricking. It just losts the stock rom but has Apollo Gapps Version 1.2 instead. I'm still thinking to use the bricking method as I don't want HDX becomes bricking.
uhg
wck01 said:
Hi All,
My friend use Apollo 14.3.2.3. I follow the guides and help to downgrade to 14.3.1.0. Then, I also helped him to install safestrap and Apollo Gapps Version 1.2. Everything was fine and prefect.
However, my friend tried to use factory reset at Gapps rom v1.2 without telling me. It made Kindle can't boot. Fortunately, he can go to recovery and make stock rom active. It can boot. However, I found that this is not original stock rom. I think the stock rom was replaced by Gapps rom v1.2.
Does anyone know how to restore the original stock rom? I have a stock rom backup copy from my kindle. Can I use that?
Thanks in advance.
Click to expand...
Click to collapse
Simple
First of all what you describe it did not happen or at least not right you described it sounds like they don't know exactly what they did. Second of all if they do not realize what they are doing to their device and they are very likely going to end up with a paperweight but that is neither my problem or your problem. Third if you do have a stock back up. Make sure you are on the stock slot then restore your stock back up...WARNING If you are both ignorant of this device. You will be back
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
mactechnm said:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
Click to expand...
Click to collapse
3.72 is for 4.4 KitKat and was made for the AT&T version of the S4, therefore, you are not able to create slots. You would need to install 3.71 and only flash 4.3 based roms. If you want 4.4 based roms you need to upgrade to NC5 and install 3.72, but you are only able to flash to the stock side.
There's plenty of info for you to read in the General section.
riker147 said:
3.72 is for 4.4 KitKat and was made for the AT&T version of the S4, therefore, you are not able to create slots. You would need to install 3.71 and only flash 4.3 based roms. If you want 4.4 based roms you need to upgrade to NC5 and install 3.72, but you are only able to flash to the stock side.
There's plenty of info for you to read in the General section.
Click to expand...
Click to collapse
Thank you for your response. Actually what I failed to mention is I did have 3.71 installed first, and I had the exact same problem. So it's not an issue with the safestrap version. And I have tried about 12 different ROMs. Including BajaROM-S4-Release-v-2.2 and BoneStock4.3_S4v2.1. As I said, I'm not a newbie at all, and I'm not about to hunt and peck for information again (which is what I've been doing for two days now). I wouldn't have asked for help if I had been successful in my search.
I have never had an issue installing any safestrap compatible rom...3.72 is strictly for android 4.4 and no rom slots...so no way you would ever get a rom installed using 3.72 on MK2 base build. As for 3.71...never heard of any issue with SS compatible roms for 3.71 not installing right. Really difficult to figure out what you are doing wrong from what you are giving us...
sent by safestrap powered echo v26
decaturbob said:
I have never had an issue installing any safestrap compatible rom...3.72 is strictly for android 4.4 and no rom slots...so no way you would ever get a rom installed using 3.72 on MK2 base build. As for 3.71...never heard of any issue with SS compatible roms for 3.71 not installing right. Really difficult to figure out what you are doing wrong from what you are giving us...
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Again, thanks for your help. I'm going to start with Odin. Wipe it all clean and start over. That's always the best option. Thanks!
basically, I'd follow this:
http://forum.xda-developers.com/showthread.php?t=2763834
I'd go back to MK2, root, BB, SS 3.71. Then go up to NC5 ROMs with SS 3.72. Wiping EVERYTHING along the way, system included, not just factory reset
Similar Issue
I not a noob either im very familiar with how this whole operation works.
I have a very similar issue as well I'm (unable to flash roms including my own recovery). I'm 100% knowledgeable on CM, but when it comes to Safestrap or TWRP base Recoveries I'm far from noon but not an expert so to say... Here's my issue. I have the NC5 firmware and once had the Hyperdrive RLS17.1 KK S4 Final.zip... I went back to the I545VRUFNC5-Stock-Root-Deodex.zip.... I recently attempted to download another ROM, (based on the same firmware of course) as soon as I attempted to flash it (which only took about 1 min and didn't work) I figured something was wrong. So I just decided to go back to my recovery that I've made a few moments ago. When I tried to do that. The msg " E: Unable to mount '/system' " appeared.
Now I've notice since then Wiping and Flashing return the same results.
There is no longer an OS on my S4... I can not Mount the System.
So I believe in stuck in Safestrap 3.72.
(Please let me know what other info you need, I spent the last couple of days trying to figure this out on my own, so far I'm losing the battle)
Please help guys.
same problem
mactechnm said:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
Click to expand...
Click to collapse
im having the same problem i am also frustrated i don't know what to do
Similar Issue
I know there must be a way... If only I can get it to mount the "system" and "systemorig"...
I'm going to play around with the Slots and the datas Size's and see what I come up with.
Pretty sure you will need to Odin the stock NC5 image and start over.
Sent from my SCH-I545 using Tapatalk
jmgib said:
Pretty sure you will need to Odin the stock NC5 image and start over.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Oh ok. The Stock NC5 image... Great.
Where can I find the stock image?
If possible, could you please send a link?
Thanks in advance
damien302 said:
I not a noob either im very familiar with how this whole operation works.
I have a very similar issue as well I'm (unable to flash roms including my own recovery). I'm 100% knowledgeable on CM, but when it comes to Safestrap or TWRP base Recoveries I'm far from noon but not an expert so to say... Here's my issue. I have the NC5 firmware and once had the Hyperdrive RLS17.1 KK S4 Final.zip... I went back to the I545VRUFNC5-Stock-Root-Deodex.zip.... I recently attempted to download another ROM, (based on the same firmware of course) as soon as I attempted to flash it (which only took about 1 min and didn't work) I figured something was wrong. So I just decided to go back to my recovery that I've made a few moments ago. When I tried to do that. The msg " E: Unable to mount '/system' " appeared.
Now I've notice since then Wiping and Flashing return the same results.
There is no longer an OS on my S4... I can not Mount the System.
So I believe in stuck in Safestrap 3.72.
(Please let me know what other info you need, I spent the last couple of days trying to figure this out on my own, so far I'm losing the battle)
Please help guys.
Click to expand...
Click to collapse
shonnick01 said:
im having the same problem i am also frustrated i don't know what to do
Click to expand...
Click to collapse
I only just saw these posts, I have not been on here for a week or so but if you are still having issues... As far as what went wrong to begin with, did you factory reset/advanvanced wipe all but the internal sd before flashing? Are you only installing into the 'stock' slot on SafeStrap? As far as the fix, if you are suck in Safestrap, you will need to boot into recovery mode, if possible and wipe/factory reset and then boot into download mode and flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin.
liljoe727 said:
I only just saw these posts, I have not been on here for a week or so but if you are still having issues... As far as what went wrong to begin with, did you factory reset/advanvanced wipe all but the internal sd before flashing? Are you only installing into the 'stock' slot on SafeStrap? As far as the fix, if you are suck in Safestrap, you will need to boot into recovery mode, if possible and wipe/factory reset and then boot into download mode and flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin.
Click to expand...
Click to collapse
Thanks a lot man. The is has been resolved...
I had to Odin the stock NC5 (exactly what you've just mentioned in your response.) I had to flash it twice actually. The first time only took about 3 mins. I then tried to restore my backup, but during the time it restari SS (when the flash was approximately 90% done) I then went to restart the system and then received the notice "No OS loaded). So I wiped all except my SD card and then I just thought to myself to just try and Odin the stock NC5 one more time (it was getting late and I was about to give up). On the 2nd attempi it took almost 3 times the length as before (15-20mins) when it finished, it bypass the " unlock Samsung screen " and displayed the stock splash screen and audio then the Verizon screen. ( I was happier the a crackhead at a free crack-give-away)...
So I want to thank you for responding, I was determined not to give up,, and it was really close before I was about throw in the towel... Thanks a bunch. (You're response was exactly what I did last night)... I was about to update my issue as soon as I fixed it las night was it was so late and I was really sleepy, then I wake up to your message with the exact fix.
Thanks a lot ☺☺
Hi all, I got myself in a bind here. I came from NK1 stock. I used ODIN to downgrade to NC5, TowelRooted, ODINed back to NK1. Installed BusyBox and Safestrap. Made a backup of stock slot in Safestrap. Everything up to that point was flawless.
So I created ROM slot 1 in Safestrap, and installed Hyperdrive v20. The install seemed to go well, but upon booting into Hyperdrive, there was no WiFi. Stock still had WiFi. No big deal, just need to flash gigilie's WiFi fix, right? Well I installed the zip in Safestrap, no errors occurred, but it did not fix WiFi.
So I decided to go back to stock until I could figure out the problem, but suddenly my PIN code no longer worked on the lock screen; I had to factory reset stock. Now that I've done the factory reset, there's no WiFi in stock, either. What's my next step?
Tried installing I545_NK1_Modules.zip, no change. I think I'll try muniz_ri's I545_NK1_Stock_Rooted_Safestrap_Backup.rar and I545_NK1_Stock_Partitions.tar.md5 when I get home from work. Any suggestions are welcomed.
Yup, muniz_ri's Alternative Safestrap Method seems to have fixed it. Back on rooted stock with everything working. I think I'll hold off on custom ROMs until more information about NK1 is available. It's hard to sift through so much information, much of which is not applicable to NK1.