Database Users

JL2 + ClockWork

Hey guys,
I don't know if I missing the BIG picture somewhere but I just can't seem to find a way to get CWM installed on a fresh JL2 install?
Iv'e googled, xda, android forums, I'm just not finding anything!
As of now:
Rooted phone with Super One Click
SU latest
Titanium Backup
ROM manager
I tried an Odin CMW.tar via PDA field and bricked my phone. Took me about 2 hours to get it back. I had Phone-!-PC icon, then I had /dev/sd/slt01 (... something along those lines), then I had infinte boot loops. What a mess!
I have also tried it from ROM manager, and tried older CMW offered in ROM Manager.
There has to be some simple thing I'm missing.
That is all I have done with the phone. Ill leave like this until someone can point me in the right direction. Just so we are clear phone is well now.
Thanks.

All I did to get Clockwork working in my JL2 was flash CF Root using odin and then flash clockwork via rom manager. All the instruction are in the cf root thread in the development section.
Sent from my GT-I9000 using XDA App

http://forum.xda-developers.com/showthread.php?t=788108 is the url for CF-Root and I used the CF Root JPK v1.1 file. It'll root your phone too so if your not already rooted then you don't have to worry about super one click or anything.

Ok, I flashed CF JPK v1.1 and installed CWM via ROM Manager but it does not boot into CWM, it goes straight to <e2>. but if i select update.zip it will boot CWM but if I reboot, it goes straight back to <e2>.

After you flash cwm with rom manager you have to go in recovery
And select update.zip and it might take a few times but it should end up in cwd. Works everytime on mine, after it does it the first time I'm usually good.
Sent from my GT-I9000m using XDA App

The reason why you can't apply update.zip is because JL2 comes with recovery 3e i stead of 2e like eclair version and 3e verify for the signature of update.zip, so no unofficial customization this way. The easiest way is to flash a custom kernel. Speedmod by Hardcore will enable CWM recover by default and give you the option to root if not done prior to flashing the kernel. It's pretty easy to do with odin and takes only 5 sec as these kernel are 5-6 mb. Moreover it's really safe.
Sent from my GT-I9000M using XDA app

That would work too, cf-root is with odin too and only takes a few seconds but as usual the instructions are on the first page of the thread.
Sent from my GT-I9000 using XDA App

sp991 said:
The reason why you can't apply update.zip is because JL2 comes with recovery 3e i stead of 2e like eclair version and 3e verify for the signature of update.zip, so no unofficial customization this way. The easiest way is to flash a custom kernel. Speedmod by Hardcore will enable CWM recover by default and give you the option to root if not done prior to flashing the kernel. It's pretty easy to do with odin and takes only 5 sec as these kernel are 5-6 mb. Moreover it's really safe.
Sent from my GT-I9000M using XDA app
Click to expand...
Click to collapse
I would also recommend this method. Super easy and it works.

+1 that's how I got CWM from a stock JL2 (speedmod 13a).
And if you get errors, reflash JL2 with update bootloader checked. It worked for me... ymmv.
Sent from my GT-I9000 using XDA App

[Q] Help with att and rom!!!

I rooted and installed wicked v4 on my att galaxy s4 and it can up with the att lock saying that att doesnt support the rom or some thing similar to that. So i booted into recovery and installed a att kernal for the rom. I rebooted it and it booted into the system perfect running the new rom. I heard that wicked v5.1 was released and i downloaded it and went into recovery to install. It came up the att lock not letting me get into recovery mode. I can boot into download mode and click cancel and it restarts and boots into system fine but cannot get into recovery. Help plz

nomad836 said:
I rooted and installed wicked v4 on my att galaxy s4 and it can up with the att lock saying that att doesnt support the rom or some thing similar to that. So i booted into recovery and installed a att kernal for the rom. I rebooted it and it booted into the system perfect running the new rom. I heard that wicked v5.1 was released and i downloaded it and went into recovery to install. It came up the att lock not letting me get into recovery mode. I can boot into download mode and click cancel and it restarts and boots into system fine but cannot get into recovery. Help plz
Click to expand...
Click to collapse
What firmware are you on? Please if you know how to flash ROMs you should know where to find it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Sent from my SGH-M919 using xda app-developers app

If you can boot into OS, download Goo Manager from Market and install TWRP 2.5.0.2 recovery
If you get it working--do a lot of reading--many variants and our bootloader is locked. Get to know loki-doki too, if you don't--

I installed twrp and it still gives me the att lock when I go into recovery. Should I try to install Loki with Odin?
Sent from my SGH-M919 using xda app-developers app

loki doesn't install thru odin--it installs thru recovery as a zip
if you still can't get into revovery you may need to odin back to stock--i never used odin, haven't needed too and on an iMac
there are some threads on using it and someone may help with that
loki bypasses samsung's signature verification on recovery and kernels and lets you flash a kernel that hasn't already been loki'd by dev--

Are you getting a lock on the Samsung screen? Or are you getting the warning saying that software is detected that is not authorized by AT&T.
If you are getting the first. Let it boot.
If you are getting the second, loki-doki patch. Google it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Or u can in fact use ROM manager just to flash a recovery "CWM".after flashing cwm get rid of ROM manager and use cwm to flash any of the recoveries. I use philz touch recovery .Google is badass though
Sent from my SAMSUNG-SGH-I337 using xda premium

ODIN emergency restore fixes it.
Sent from my Nexus 7

here ya go
Step one. Install rom using goomanagers' twrp
step two. flash rom
step 3. flash the attached loki-doki.zip
it will make the phone think that the boot image is signed with at&t. it writes into the firmware, so you don't have to do it every boot. but you do have to do it everytime you flash a rom

vedantgp said:
Step one. Install rom using goomanagers' twrp
step two. flash rom
step 3. flash the attached loki-doki.zip
it will make the phone think that the boot image is signed with at&t. it writes into the firmware, so you don't have to do it every boot. but you do have to do it everytime you flash a rom
Click to expand...
Click to collapse
This is the correct procedure...

Is my phone bricked?

Earlier today I was trying to install the 4.3 Slim Bean Build.1. I was coming from the latest 4.2 Slim Bean ROM. So I did the usual process of wiping everything then installing the ROM and then the GApps. When I rebooted the system from recovery, my phone was just stuck on the Samsung Galaxy S4 loading screen. Now I cannot even boot into recovery, as every time I try to, it will show that the phone is attempting to boot into recovery and then it will just reset. I had TWRP touch recovery installed and everything was working fine until I tried installing this ROM. Are there any suggestions of what I can do/should do? Thanks in advance for any help.

Can you get in download mode(power+vol. Down) if so use odin to flash back to stock.
Sent from my SPH-L720 using XDA Premium 4 mobile app

Yes I can. Is there a guide on how to Odin back to stock? Also, will I lose my root if I do that? Thank you

klgd said:
Can you get in download mode(power+vol. Down) if so use odin to flash back to stock.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I can. Is there a guide on how to Odin back to stock? Also, will I lose my root if I do that? Thank you

On my way to work so cant spend any time helping, but there are sevral guides and you will lose root.
Sent from my SPH-L720 using XDA Premium 4 mobile app

Might just b able to Odin recovery...
Sent from my SPH-L720 using xda app-developers app

Download Odin and the latest firmware for your device,extract firmware zip file,it will extract in tar.md5 file.now extract Odin and run the Odin application and connect the device while it is in download mode. click on PDA and load the firmware extracted file. Don't touch anything other than that click on start and leave for some time to complete.
Samsung lies should be installed before the process start.
Download firmware file from sammobile.com.
Your device will be automatically unrooted.
Sent from my GT-P3100 using xda app-d,evelopers app

youngnick09 said:
Yes I can. Is there a guide on how to Odin back to stock? Also, will I lose my root if I do that? Thank you
Click to expand...
Click to collapse
yes you will have to start all over. here is a video on how to use odin on the s4. http://www.google.com/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=2&ved=0CDMQtw IwAQ&url=http://www.youtube.com/watch?v=hZTTTk7vbVM&ei=3t05UtijLdTc4APV-YDQBw&u sg=AFQjCNGIjlBz9Xgj57ytF2NCGYchd7V1Xg&sig2=hhLZZzmRyDFyxETPrzCmfw&bvm=bv.522881 39,d.dmg make sure you get a stock .tar file found here http://forum.xda-developers.com/showthread.php?t=2338919. make sure you watch the video before you do anything. also this thread belongs in Q&A.

thank you guys

I have run into a similar issue and was able to get into recovery by pulling the battery for about 5 minutes then using the hardware keys to boot into recovery.
Sent from my SPH-L720 using Tapatalk 4

[Q] HELP! Stuck in soft brick!

Can someone please help me get out of this soft brick because I am really stuck. Currently I am getting the error message that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." but I have done that and it has failed on both mac and windows 7. I have also tried flashing stock build UCUAMDL 4.2.2 firmware via odin 1.7, 1.85 and 3.07 and I have also used the PIT files along with re-partitioning and F. Reset Time. Every single time in odin it has gotten to system.img.ext4 and then failed immediately following. A couple of times I have been able to get into stock recovery mode and it stated an error that the /system partition could not be accessed and I wiped cache/system/data and then tried rebooting and it stayed in the big white galaxy s4 letters and didn't even go to the boot logo. Based on this can anyone help me please???? If there's an existing thread can you please let me know? Thanks!

Which model do you have? What firmware are you on?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

sounds like you wiped your phone when you wiped system/data, why did you do that
you have nothing to boot
kies don't work with iMac
yeah give all the phone info you have, model, build, etc. build may be on your box
i think you can now only flash stock firmware thru Odin to recover, but if you were mf3, you may need to go to bestbuy and see samsung reps to flash phone. don't have any experience at that or using odin
stay on windows pc to do this
may be tomorrow till you get some help from others
good luck

RAID Xero said:
Which model do you have? What firmware are you on?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Sorry I forgot to mention that it's a SGH-I337 as well and I was running the jamal 4.3 AOSP ROM

well then you are with what custom recovery?
and you are not mf3
sounds like the mf3 update was trying to flash. did you not delete the update files with Titanium so the Update would not run
can you boot into recovery and restore a nandroid
---------- Post added 2nd October 2013 at 12:00 AM ---------- Previous post was 1st October 2013 at 11:54 PM ----------
i gotta call it a nite. maybe some west coasters can help since they are 3 hours behind us
but, please don't say you don't have a nandroid--
i think this is fixable--:good:

restoring a nandroid backup could solve your problem, did you try flashing with fastboot instead? When you installed AOSP ROM were you using a toolkit? If so did you flash a temp recovery?
Sent from my Nexus 7 using xda app-developers app

Kelevra_96 said:
restoring a nandroid backup could solve your problem, did you try flashing with fastboot instead? When you installed AOSP ROM were you using a toolkit? If so did you flash a temp recovery?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you have an i337. We don't have fastboot. Our bootloader is locked.
Sent From My SGH-I337 Using Tapatalk 4

What custom recovery are you using?
Sent from my SGH-I337 using XDA Premium HD app

Br4nd3n said:
What custom recovery are you using?
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
I don't have one, although do you think that I can flash a custom recovery with a PIT file because that seems to be the only thing that works. Also I do not have a nandroid backup. Is there somewhere that I can download someone's already made?

adambombz said:
I don't have one, although do you think that I can flash a custom recovery with a PIT file because that seems to be the only thing that works. Also I do not have a nandroid backup. Is there somewhere that I can download someone's already made?
Click to expand...
Click to collapse
It's been asked a couple of times, but do you know what firmware your phone was on? It's important to know to be able to help you.

jd1639 said:
It's been asked a couple of times, but do you know what firmware your phone was on? It's important to know to be able to help you.
Click to expand...
Click to collapse
I was running a custom ROM AOSP 4.3 that's all I know sorry

adambombz said:
I was running a custom ROM AOSP 4.3 that's all I know sorry
Click to expand...
Click to collapse
That's close enough. That means you aren't on mf3.
Edit, have you tried to odin the stock firmware? Never mind I see you have
I would download the stock firmware from sammobile.com and try Odin again on a pc. Either version of odin is ok, 1.85 or 3.07.
When you use Odin only have auto-reboot checked, Don't check re-partition.

also, if you are running a custom rom you have a custom recovery
cwm or twrp?

jd1639 said:
That's close enough. That means you aren't on mf3.
Edit, have you tried to odin the stock firmware? Never mind I see you have
I would download the stock firmware from sammobile.com and try Odin again on a pc. Either version of odin is ok, 1.85 or 3.07.
When you use Odin only have auto-reboot checked, Don't check re-partition.
Click to expand...
Click to collapse
I have tried doing this many, many times and each time it gets to the system.img.ext14 and then fails.

rugmankc said:
also, if you are running a custom rom you have a custom recovery
cwm or twrp?
Click to expand...
Click to collapse
They key word here is that I WAS running a custom recovery when all of this started. It was actually the recovery that started all of this. What happened specifically was I tried to update TWRP via goo manager and whenever I tried to go into recovery it gave me the error that at&t has detected unauthorized software on my phone which I thought was weird because I believe that goo manager auto-lokis. Anyway I tried using other apps to add a custom recovery like ROM manager by clockworkmodz and nothing worked. I then tried to flash TWRP 2.6.3.0 via odin and that's what sent my phone into the state that it's in now. Something that confuses me even more is is that whenever I plug in my phone a battery logo comes up that I don't recognize and then freezes.

adambombz said:
I have tried doing this many, many times and each time it gets to the system.img.ext14 and then fails.
Click to expand...
Click to collapse
Have you re-downloaded the firmware? It could be a bad download. Are you using the .tar.md5 file

When you get it sorted use twrp 2.5.0.2. I think I posted a zip for you.

jd1639 said:
Have you re-downloaded the firmware? It could be a bad download. Are you using the .tar.md5 file
Click to expand...
Click to collapse
Yes I have tried multiple files and builds and I am using .tar.md5

adambombz said:
Yes I have tried multiple files and builds and I am using .tar.md5
Click to expand...
Click to collapse
When you flashed twrp with odin are you sure it was for your device? I think you might have borked your partitions.

jd1639 said:
When you flashed twrp with odin are you sure it was for your device? I think you might have borked your partitions.
Click to expand...
Click to collapse
That is possible, I know what is causing this has something to do with the partitions being messed up since I can't access /system in the stock recovery mode

Error or Installing TWRF recovery

I have just rooted my GN2, I had a problem while rooting it as it was getting stuck on odin written as stuck? tried other methods also but still the same, somehow i rooted my device.
Now i want to instal TWRF recovery on my device, but when i try it through odin after the recovery finishes , the section where pass should come its written as RESET. So please help me to install TWRF As The DN3 Rom need twrf recovery
. Thanks in advance
Sent from my GT-N7100 using xda premium

TWRP* Recovery
Sent from my GT-N7100 using xda premium

Guyz done, of anyone else facing this problem then uncheck the auto-reboot option
Sent from my GT-N7100 using xda premium

amit.dhatrak95 said:
Guyz done, of anyone else facing this problem then uncheck the auto-reboot option
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I didn't understand if you are facing issue with rooting your phone or installing custom recovery?And which android version is installed on your phone and which method did you follow to root your phone?

I was running 4.4, and while doing both root and recovery i was facing issue in odin, it used to get stuck at reset. But now i uncheckd the auto-reboot option and now its working
Sent from my GT-N7100 using xda premium

But i didnt understand 1 thng, that when I unchecked auto-reboot option although it installed the TWRP recovery, but still PASS didnt come there, it was still stuck on reset.. What is the problem here, as i may also face it in future when updating TWRP
Sent from my GT-N7100 using xda premium

amit.dhatrak95 said:
But i didnt understand 1 thng, that when I unchecked auto-reboot option although it installed the TWRP recovery, but still PASS didnt come there, it was still stuck on reset.. What is the problem here, as i may also face it in future when updating TWRP
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
If you have sucessfully flash twrp you don't need to use odin again to flash another recovery you can do it by flashing it from the same recovery.You'd only need ODIN when you cant access your recovery and need to enter download mode to flash recovery.I hope you are using img.tar file to flash twrp via odin and not .zip

amit.dhatrak95 said:
I have just rooted my GN2, I had a problem while rooting it as it was getting stuck on odin written as stuck? tried other methods also but still the same, somehow i rooted my device.
Now i want to instal TWRF recovery on my device, but when i try it through odin after the recovery finishes , the section where pass should come its written as RESET. So please help me to install TWRF As The DN3 Rom need twrf recovery
. Thanks in advance
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
In odin ... Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
And which android version u r using?