Database Users

HELP Needed to flash rom

I have a retail XT907 on 4.1.2 that I got rooted, unlocked and twrp installed
I want to try the Energy rom and have it downloaded.
Where do I place the zip on the phone to install it in recovery?
I have backed up my system to the sd
Do I need to partition my phone? How to do it?
Can I instal the rom on my phone running 4.1.2?
Thanks

khalilcr said:
I have a retail XT907 on 4.1.2 that I got rooted, unlocked and twrp installed
I want to try the Energy rom and have it downloaded.
Where do I place the zip on the phone to install it in recovery?
I have backed up my system to the sd
Do I need to partition my phone? How to do it?
Can I instal the rom on my phone running 4.1.2?
Thanks
Click to expand...
Click to collapse
Energy is 4.1.1 and right now can only be installed via safe strap.
Sent from my XT907 using xda app-developers app

jco23 said:
Energy is 4.1.1 and right now can only be installed via safe strap.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
How do I flash safestrap? I currently have TWRP.
I downloaded safestrap.md5 but do I flash it through TWRP or rename .apk?

khalilcr said:
How do I flash safestrap? I currently have TWRP.
I downloaded safestrap.md5 but do I flash it through TWRP or rename .apk?
Click to expand...
Click to collapse
see this thread:
http://forum.xda-developers.com/showthread.php?t=1979383
and then this:
http://www.droidrzr.com/index.php/topic/11600-installing-custom-rom-to-stock-using-ss-312/

safestrap.md5 is NOT the flashable/installable file. You want the .apk file.
And why can you not install Eclipse on CWM or TWRP?

I got energy Rom to flash just fine on twrp
Sent from my XT907 using Tapatalk 2

TWRP would not allow me to create a partition.
I renamed the md5 to apk and installed it just fine, but now I have 2 recoveries
Installed the Energy ROM and its awesome but camera app fc every time :crying:
I want to try the PAC rom next.
To do so I assume I need to delete the current partition where I have the Energy ROM installed?
Can I install the PAC rom on the stock ROM slot?
If so how do I get rid of safestrap and keep only TWRP?
Thanks to the Razr M community for all the help, I only had Sammy experience before getting the Razr M and been trying to learn it all over again

khalilcr said:
TWRP would not allow me to create a partition.
I renamed the md5 to apk and installed it just fine, but now I have 2 recoveries
Installed the Energy ROM and its awesome but camera app fc every time :crying:
I want to try the PAC rom next.
To do so I assume I need to delete the current partition where I have the Energy ROM installed?
Can I install the PAC rom on the stock ROM slot?
If so how do I get rid of safestrap and keep only TWRP?
Thanks to the Razr M community for all the help, I only had Sammy experience before getting the Razr M and been trying to learn it all over again
Click to expand...
Click to collapse
Camera will not work on energy if you install it on top of a 4.1.2 ROM.
SS can been cleanly uninstalled without impacting twrp.
I'm now on pacman, and it is great except for camcorder not working.
Sent from my XT907 using xda app-developers app

So if I erase system on twrp, restore to stock backup, all the changes made on ss and energy will be gone? Than just click flash and choose PAC.zip and gapps?
Sent from my XT907 using xda app-developers app

khalilcr said:
So if I erase system on twrp, restore to stock backup, all the changes made on ss and energy will be gone? Than just click flash and choose PAC.zip and gapps?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if wiping system/factory reset will undo the partitions made via SS - but otherwise, I think you are correct. you don't need both SS and TWRP going forward. however, the only reason to have SS is to install the awesome Energy ROM (although Brandon claims to get Energy installed via TWRP just fine - so you might want to check with him). however, that ROM is based on 4.1.1. all ROMs going forward will be flashable via TWRP.
if you don't mind camcorder not working, then go with PACman.
i would recommend once you download the 5/24 PACman ROm and GApps, go into TWRP, mount everything, wipe cache, wipe dalvik, factory reset, system wipe, mount everything again, install PACman ROM, install GApps, then reboot.
if you cannot deal with camcorder not working, then you can install the base 4.1.2 component, posted on droid-hive:
http://droid-hive.com/index.php?/topic/1767-98161-base-components/
go into TWRP, mount everything, wipe cache, wipe dalvik, factory reset, system wipe, mount everything again, install 4.1.2, then reboot
once you are at a good spot, then you can uninstall SS

Thanks, finally got PAC flashed and am loving it. Camcorder not a big deal for me as long as camera works.
Thanks again for the help
Sent from my XT907 using xda app-developers app

Can't get passed boot logo..

This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.

Try flashing a different compatible kernel.

ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.

Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app

Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr

ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app

I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!

Glad it's working out for you.

If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?

Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.

[Q] Cannot Install Custom Rom On i9505, Help Please?

Hi,
I am pretty new to custom roms ect, I have tried installing Battery King v8.2, Vision X II, Carbon Nightly and Google Edition. All of those roms are compatible with i9505, I have also tried using both recoveries CWM 6.0.3.1 and TWRP 2.6.3.1 and on each i wiped data, cache, dalvik, battery stats and system, then after each rom installed successfuly i wiped the dalvik cache again and rebooted to find the stock rom (Prerooted).
Any advice to what i am doing wrong?
I am currently downloading the official stock rom for my phone now to see if that makes a difference.

AGAWhitty said:
Hi,
I am pretty new to custom roms ect, I have tried installing Battery King v8.2, Vision X II, Carbon Nightly and Google Edition. All of those roms are compatible with i9505, I have also tried using both recoveries CWM 6.0.3.1 and TWRP 2.6.3.1 and on each i wiped data, cache, dalvik, battery stats and system, then after each rom installed successfuly i wiped the dalvik cache again and rebooted to find the stock rom (Prerooted).
Any advice to what i am doing wrong?
I am currently downloading the official stock rom for my phone now to see if that makes a difference.
Click to expand...
Click to collapse
I had the same, I forgot to flash a custom recovery. Samsung's stock recovery will only flash/install Samsung signed ROMS. Flash a custom recovery like CWM, TWRP or Philz (I'm using philz). Then boot into your recovery and flash your ROMS.
If you have done that, ensure the MD5 of your ROM is correct.

RossFixxed said:
I had the same, I forgot to flash a custom recovery. Samsung's stock recovery will only flash/install Samsung signed ROMS. Flash a custom recovery like CWM, TWRP or Philz (I'm using philz). Then boot into your recovery and flash your ROMS.
If you have done that, ensure the MD5 of your ROM is correct.
Click to expand...
Click to collapse
Hi,
Thanks for your reply, i have installed both CWM then TWRP but havent tried Philz (i will try that now) but how do you mean ensure the MD5 of my rom is correct? How would i do this? Because i have downloaded the roms from the i9505 sections therefore i know they are compatible if that is what you mean.

AGAWhitty said:
Hi,
Thanks for your reply, i have installed both CWM then TWRP but havent tried Philz (i will try that now) but how do you mean ensure the MD5 of my rom is correct? How would i do this? Because i have downloaded the roms from the i9505 sections therefore i know they are compatible if that is what you mean.
Click to expand...
Click to collapse
Ok, just checking the basics first, I made that mistake, TWRP didn't flash correctly and I was on stock recovery!
the MD5 is a unique code attributed to the file. It will be given with the download and look something like (as an example only) 1565fs15f1s65f1w8e1wf8f1sw When you download the file you can run a program (have a look, loads free for PC and the phone) that will generate an MD5 sum also, the two should match, if not your download corrupted (this happens me a lot).
Hmmm. What error are you getting, what exactly happens in the recovery when you flash the zip?

RossFixxed said:
Ok, just checking the basics first, I made that mistake, TWRP didn't flash correctly and I was on stock recovery!
the MD5 is a unique code attributed to the file. It will be given with the download and look something like (as an example only) 1565fs15f1s65f1w8e1wf8f1sw When you download the file you can run a program (have a look, loads free for PC and the phone) that will generate an MD5 sum also, the two should match, if not your download corrupted (this happens me a lot).
Hmmm. What error are you getting, what exactly happens in the recovery when you flash the zip?
Click to expand...
Click to collapse
Okay, ill have a look for a pc tool that will do that. I am currently installing the stock 4.3 i9505 rom then ill flash the Philz recovery and try installing the custom rom if the md5 matches. Ill reply with the results as soon as im done.

AGAWhitty said:
Okay, ill have a look for a pc tool that will do that. I am currently installing the stock 4.3 i9505 rom then ill flash the Philz recovery and try installing the custom rom if the md5 matches. Ill reply with the results as soon as im done.
Click to expand...
Click to collapse
Cool, best of luck with it. I'm not too familiar with doing this on the S4 but got it all working last night. If I'm not full of ideas there's many, many poeple on this forum who know their stuff back to front who will get you sorted!
Any errors you encounter note them down! Make backups!! Then backup your backup on the PC!

FIXED
Just to update, it finally worked. Before i flashed the custom rom i installed the latest official firmware which was 4.3 from sam mobile, then before flash i went onto CWM and did the following:
format cache system and data x 2
wiped cache partition
wiped dalvik cache
rebooted recovery
formated cache system and data
rebooted recovery
installed from sd card
then wiped data/factory reset then rebooted

Awesome! Enjoy your new ROM!
Sent from my GT-I9505G using xda app-developers app

[Q] Super S4 and KT Kernel problem

KT kernel is causing my phone to reboot on Super S4 when launching various apps. I could only find one place to snag the stock kernel which I tried and it fixed those problems. But now dropbox fails when trying to export files. Also the Amazon market fails when trying to download apps. I couldn't even update Lucky Patcher without getting a parse error. It seemed like a permissions issue so I tied to fix permissions in TWRP but that didn't help.
Any suggestions? Should I go back to KT kernel and try to figure out why it reboots my device? Or stick with stock and try to figure out the permissions problems? Or should I try a different kernel completely? Or should I just stick my phone up my ying yang and get an etch a sketch? Any help would be appreciated.

You can try flashing the stock kernel. Its located in the thread or a quick search in the Dev forum.
Did the MD5 SUM match?
Did you follow the install instructions? (Reboot recovery - full wipe)
Did you update Google services framework?
Sent from my SPH-L720 using XDA Premium 4 mobile app
---------- Post added at 06:29 PM ---------- Previous post was at 06:28 PM ----------
Stock kernel
http://forum.xda-developers.com/showthread.php?p=53630603
Sent from my SPH-L720 using XDA Premium 4 mobile app

This is what worked for me
I am happy to report absolutely zero issues on my S4 installing and using Super S4. Let me detail what I did, and maybe you can go back to square one and start over with better results. Prior to installing SS4 I had the OTA version 4.4.2 with NAE modem.
1) After reading through the Super dev thread, I decided to use Philz recovery. I downloaded this one: philz_touch_6.23.9-jflte.tar.md5 and flashed it with Odin 3.07. I made sure to disable the auto reboot, as that has caused trouble for me in the past.
2) I downloaded 1.4 odexed and copied the file to my ext sd card. Then I checked the Md5 sum of the file on the card.
3). Booted to recovery, used the "Wipe Data/Factory Reset>-Clean to Install a new ROM" feature. Twice.
4) Under "Advanced" wiped Dalvik, twice also.
5) Rebooted recovery. DON'T FORGET THIS!
6) Flashed the ROM zip.
7) After flash, Selected "no" instead of "disable install recovery"
Everything came up beautifully. Be careful which KTweaker profiles you use, I had weird stuff happening with the "battery saver" profile. I am using Ktoonsified V6 now and battery life is great.
Hope this helps!

Try the 5-28 build of Kt. Wipe your ktweeker data and cache then flash an older build and redownload your profiles of choice is reset your own. I had some reboots on the latest which I'm sure you can retweek and solve but I've not had time so reverted to 5-28 and smooth criminalv5 just to keep me going though bonfire season lol.
Sent from my SPH-L720 using xda app-developers app

Phone stuck on splash screen after reboot

I was running (and am after the restore) Android 4.3.1 slimBean jflteatt build.2official.
So my friend convinced me to try CM12 lolipop nightly.
I made a backup wiped everything and installed CM12 and the gapps.
upon boot after the instalation all the play services were crashing so we reinstalled CM 12 but without GAPPS and all was fine.
BUT now i CAN"T reboot my phone. Regardless of ROM (except stock) the att galaxy s4 gets stuck on the boot splash screen (the screen before the boot screen) The screen it gets stuck on looks like this: http://img18.imageshack.us/img18/8910/20120813002112.jpg
The screen used to look like this: http://2.bp.blogspot.com/-aCD7kATq-to/UaIBfYW5oKI/AAAAAAAAO88/ShlHR6459kk/s1600/boots4.gif
I have tried restoring and installing a clean ROM but that did not solve my problem. Only way for me to restore is to wipe everything, then format the data and the restore. I restored to stock TW MDL via a TWRP backup i have.
I am running TWRP 2.5.0.1 (I think). I am currently using the SlimRoms 3.4.0 kernal. I am rooted according to root checker.
Can someone please help me solve the reboot problem? (Could it have anything to do with Xposed?)

I would update twrp and try again. You have an old version.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I would update twrp and try again. You have an old version.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
i have 2.5.0.2, what do you suggest i update to ? (and how?)
I've been afraid to update anything because if it aint broke don't fix it.
Do you suggest TWRP 2.8.0.1 touch recovery [2014-09-12]
as this suggests?: http://forum.xda-developers.com/showthread.php?t=2413746
thank you for your reply.

sharpknight said:
i have 2.5.0.2, what do you suggest i update to ? (and how?)
I've been afraid to update anything because if it aint broke don't fix it.
Do you suggest TWRP 2.8.0.1 touch recovery [2014-09-12]
as this suggests?: http://forum.xda-developers.com/showthread.php?t=2413746
thank you for your reply.
Click to expand...
Click to collapse
Flashing roms in an old version of twrp won't work. If your rooted, which I assume you are, get flashify forum the play store. Then download the latest twrp.img and flash it in flashify. http://dl.twrp.me/jflteatt/ The link is for the at&t s4, if you have a different variant you'll need a different image.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Flashing roms in an old version of twrp won't work. If your rooted, which I assume you are, get flashify forum the play store. Then download the latest twrp.img and flash it in flashify. http://dl.twrp.me/jflteatt/ The link is for the at&t s4, if you have a different variant you'll need a different image.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
ok i have succesfully updated to TWRP 2.8.4.0 (newest on the link you provided) via flashify as you suggested.
What do i do now? BTW really appreciate the help.

sharpknight said:
ok i have succesfully updated to TWRP 2.8.4.0 (newest on the link you provided) via flashify as you suggested.
What do i do now? BTW really appreciate the help.
Click to expand...
Click to collapse
If you want cm12 download the zip and gapps and flash those in twrp. Do the default wipe in twrp first. Note, it will wipe your apps but if you have had Google backup your device it will restore them.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
If you want cm12 download the zip and gapps and flash those in twrp. Do the default wipe in twrp first. Note, it will wipe your apps but if you have had Google backup your device it will restore them.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I don't wan't CM12 at this moment. I just need to have old SlimRom working without the reboot issue. too much business related data there at the moment. So should i reinstall slimRom and the restore that data maybe?
Could it be the slimKernal? Ive had the problem where it gets stuck at that screen for a long time now but id just do a batery pull and turn it on and it would work after 2-3 tries.