I came from the bionic and for more than a year enjoyed dhacker's safestrap recovery. For those of you that haven't heard of it, it is a twrp-based recovery that allows you to swap between four rom slots (and a stock slot) at boot and it is "safe" as you are able to boot into it every time you start your phone, even if it would normally fail to boot into recovery or the system.
I doubt dhacker would extend support to the S4 (since the supported devices are all moto) but it would be nice if someone with more technical knowledge than me could look into whether or not it could be ported.
Im sure a dualboot will come
Sent from my SCH-I545 using Tapatalk 4 Beta
Related
I recently tried flashing several different ICS roms and got the same result with each. The phone turns on, but after sitting on the initial Motorola boot screen for a few seconds, the screen goes black. From what I can tell, it is not the roms themselves that are causing it.
I follow all of the wipe instructions to the letter.
I am able to boot into safestrap recovery and do a restore.
One of the roms I tried (I can't remember the other)
Gummy Resurrection rom
Current stock version: 6.12.173 (latest update)
Does anyone have an idea as to what the problem may be?
Are you GSM or cdma?
Sent from my Droid Razr using Tapatalk
Based on the stock version I would assume Cdma. What version of Safe strap? I also assume since you can go into Safe strap you can access the internal memory and external sd card. What cwm are you using? So what other Roms did you try? Were you not ever able to get anything other than stock running?
I am using the latest version of safestrap (1.07)
I can access internal memory and SD card, as I am able to restore my backup of the stock rom.
I'm not using CWM, I'm using safestrap recovery.
I think the other rom was |Aokp| |Icsrazr| |Kang| |4.0.3| Ab (it can be found on droidrzr.com)(I can't post links yet).
I haven't tried anything other than those two roms, but since I got the same result for both, I would assume that the issue affects any rom I try to flash. I can try to flash a different rom and see if that works.
Umm oh that takes alot of thought. No idea at this point. Only think I could say is ditch Safe Strap re install and start again. Im sure smarter people will give a say.
Maybe the update fixed something?
http://forum.xda-developers.com/showthread.php?t=1391900
I got a Gingerbread rom to boot correctly. Maybe both of those ICS roms have the same issue. I dunno lol.
Yeah lol ive flashed both kinds of Roms and always getting them to work. Currently on AOKP M4 | AXI0M | KANG | RAZR and loving it.
ICS roms requairs you to have CWM on boot recovery if I'm not wro ng.
The first thing I see is safe strap maybe he needs to re install or update for some reason.
I wasn't aware that there was a later version of safestrap out. That seems to have done the trick. ICS roms are now booting properly.
Sweet now enjoy some Roms.
So I have bootstrap installed now. Can i just load safestrap overtop of it? or do I need to remove bootstrap first?
IdowhatIwant said:
So I have bootstrap installed now. Can i just load safestrap overtop of it? or do I need to remove bootstrap first?
Click to expand...
Click to collapse
Remove the strap you don't want first
Ask us any Android Related Question @FeraLabsDevs on Twitter
I have a rooted I717. I have tried to load multiple ROMs through CWM (ICS_CLC5_Alpha, SAUROM_XLA2_RCVII, etc.). However, I get the same message every time I start the flash: E: short write of tmp sideload package.zip (no space left on device). I have used multiple apps to confirm that the phone is rooted and have over 10gb of data available on the SD card.
I have rooted multiple devices, namely my past Captivate, and never had much of a problem. I've never worked with a device that fights me like this before.
Any advice, suggestions, tutorial, etc. would be greatly appreciate.
(I also found an ICS ROM that load through odin here:
http://www.androidlookout.com/install-cyanogenmod-9-galaxy-note/168/
Can anyone with a trained eye verify if this ROM would be stable on the I717)
Thanks.
It does not sound to be like you have ClockworkMod Recovery installed. Are you sure you are not trying to flash under Android System 3e recovery? Can you post a picture of exactly what you are selecting in recovery to flash?
I don't know how trained my eyes are, but I can assure you, if you flash that ROM you linked it will bork your device. That is for the International note (our phones weren't released yet when the article was written).
Yes that's for the international note.
Sent from my SAMSUNG-SGH-I717 using XDA
Here's a screen shot (I believe this is what you're asking for). It says I'm running Recovery 2.5.1.2.
Sent from my SAMSUNG-SGH-I717 using XDA
Screenshot didn't come through, but I do believe that is the Android System Recovery version. You can only flash custom stuff through the ClockworkMod recovery here:
http://forum.xda-developers.com/showthread.php?t=1526431
Use Odin to flash that. Then you will be in a blue recovery that will look like this:
http://dl.xda-developers.com/attach...3fd0/4f7f5e62/9/3/3/4/7/6/20120305_160801.jpg
You can flash your zips from there successfully.
I'll try that tonight. Thanks for the heads-up. The shear number of threads here can be daunting to sort through.
By the way, will I be able to delete unwanted applications after correctly rooting the device without flashing a ROM? (I was able to on past devices. Just curious.)
Motorola defy is comes with locked bootloader. But defy have so may custom roms(miui,ics,jb4.1,4.2), custom kernels, and even use two or more roms to boot.( one from internel and others from externel sd card). If defy is able to do this with locked bootloader then why photon ?.
These are the words from defy wiki page.
LOCKED Bootloader, what does this means?For some people is hell, for others (normally non advanced users) is a pretty cool insurance for their phone. This locked Bootloader thing means there is no (so far) way to rewrite the Stock Bootloader or the Stock Recovery.When the phone turns on the Bootloader basically starts all the hardware and make your phone come alive.Then we have the Stock Recovery, this little part of your phone is also locked and cannot be removed or changed from your phone, it will allow you to make Recovery stuff like Full Wipe (Data and Cache) and install Update.zip files.At first this became a problem, because with a locked Bootloader there is no way to install a Custom Recovery like ClockworkMod or install a new Rom.Here is where2nd Initcomes to play, this little awesome app kicks inright after the Bootloader and allows the Defy to load a different, non-Stock Android.With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting allyour stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Litein Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back tolive normally.Thanks to this locked Bootloader, is really, really hard to Brick your Defy.Most of the issues seen on the Forums are NOT Bricks, just incorrectly flashed SBFs (more on this later). With brick one mean the phone has no access to the Bootloader or can’t initialize its hardware, requiring you to use a JTAG to directly reprogram the phone (which I’m not sure is possible on the Defy).
Custom Recovery
A custom recovery is a special"App"** that comes in a separate partition in your phone. This"App"** allows Android Phones to do recovery tasks, like deleting data,installing recovery Zips and so on; The tasks you are allowed to do withStock Recovery are pretty basic. Here is where Clockwork Mod comes into play.CWM is a Recovery that allows you to not only do basic tasks but also create Nandroid Backups, Restore Them, Fix Permissions and quite a lot of other useful stuff.Normally a Custom Recovery is installed by flashing the Recovery Partition in your Android Phone witha Custom Image, but since our Defy comes with a Locked Bootloader, this is not possible. Leaving us without many options to proceed.And that's why we have 2nd Init, thisapplication is what actually installs CWM in the Defy, it does it by installing it in your internal memory and not in your Recovery Partition and then pointing the Android system to it right after the Stock Recovery boots.**Is not actually an App, is more likea Linux Console with UI so you can recover.
Sent from my MB525 using Tapatalk 2
I think if our devs modify the 2ndint apk for photon, then all locked photon users will able to try all roms available here.
Sent from my MB525 using Tapatalk 2
One dev is already working on this....Bt not yet successful...
But we hope he'll b successful.... N we can enjoy the test of different ROMS.
Sent from my MB855 using xda app-developers app
Cooldevil1989 said:
One dev is already working on this....Bt not yet successful...
But we hope he'll b successful.... N we can enjoy the test of different ROMS.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
It is glad to hear that and hope he will achieve it. Compared with photons hardware my defy is far behind.
I was purchased my photon from ebay few days back (only looking its specifications!!)
After reading through this forum i realised that its not possible now to try jb, ics, or even some cm7 roms in my photon becouse it is 2.3.5..
Sent from my MB525 using Tapatalk 2
After researching about safestrap, I was wondering if flashing an SS ROM to my main partition would bork my phone, or simply flag my phone's warranty notification (I could care less about my warranty flag) I want to install a ROM and be able to utilize as much of the storage as possible in the partition and don't mind using ODIN to flash back to stock if that is all it takes to fix it, (I've used ODIN many times in the past w/my other Sammy devices).
Is this a possibility or is the S4 different in such a way that they are bricking left and right because of this kind of thought process?
dogginsteed said:
After researching about safestrap, I was wondering if flashing an SS ROM to my main partition would bork my phone, or simply flag my phone's warranty notification (I could care less about my warranty flag) I want to install a ROM and be able to utilize as much of the storage as possible in the partition and don't mind using ODIN to flash back to stock if that is all it takes to fix it, (I've used ODIN many times in the past w/my other Sammy devices).
Is this a possibility or is the S4 different in such a way that they are bricking left and right because of this kind of thought process?
Click to expand...
Click to collapse
A few of us have flashed a custom ROM to the stock slot with no issues. (I actually just flashed Hyperdrive 13 to the stock slot ) Just be aware, Hashcode doesn't recommend it so if something goes wrong, he can't help. Good luck.
Sent from my NCC 1701 using Tapatalk 4
Thanks
Sent from my SCH-I545 using Tapatalk
After installing hyper drive on the stock partition using safestrap, there still seems to be greater than 6gb of storage that I can't touch. Why is that?
Sent from my SCH-I545 using Tapatalk
I was playing with roms yesterday and I decided to switch form CWR to TWRP now I can boot into system but I can't flash anything the roms that were flashing easily on CWR worn't work anyone anyone knows why ? I am trying to reflash cwr but I don't have gapps on this one and I don't have any backups
[UPDATE]
OK seemed like TWRP Had a problem with my Phone.
I flashed This version https://www.androidfilehost.com/?fid=23501681358543435 and IT WORKED
If you're using the TWRP 2.7 build from its own thread on the Development forum, that's why. As stated several times in the thread, that one doesn't work, and the Dev never ever addressed it.
Use the TWRP from brothaedhungs Pacman thread in Development (not Original Development) and it'll work fine.
I've been using it since he put it up, and haven't needed to resort to using CWM since the early days of 4.3
The multirom twrp seems to work fine as well. I'm currently running it with a single ROM
Sent from my LG-GEEB using Tapatalk