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

Stuck in infinite loop into Samsung Recovery

I am not a noob, in fact I am actually a software developer, just not for Android devices so all of this is not a level playing field. My end goal is to get CM7 on my Samsung Fascinate (I500). But, I have never been able to boot into Clockwork Recovery despite the numerous attempts and methods to install it. It always has booted the default Samsung Recovery Utils. First I tried installing it thru the app (and yes it is rooted, Superuser agrees). Finally, I think Odin did me in for the final time, I tried installing CWMRecovery.tar using Odin and now my phone is in an infinite loop, always loading the Samsung Recovery Utils, can't get back to the OS. I read the "Unbrick my fascinate" guide, no luck there. How can I just get this thing working?

Question: when you used odin, did you put the cwmall.tar in PDA or PHONE?

I put it in PDA as the guide said. I do have an new update tho, after trying a couple more of the tars on the guide I was able to get it back up and working however still unable to get into Clockwork Recovery. Everytime I try booting into it, it has an error "failed to verify whole-file signature" and "signature verification failed". Would you know why this isn't booting into Clockwork?

codemann8 said:
I put it in PDA as the guide said. I do have an new update tho, after trying a couple more of the tars on the guide I was able to get it back up and working however still unable to get into Clockwork Recovery. Everytime I try booting into it, it has an error "failed to verify whole-file signature" and "signature verification failed". Would you know why this isn't booting into Clockwork?
Click to expand...
Click to collapse
I think you should odin a stock package first. Read the bottom half on going back to stock.
http://forum.xda-developers.com/showthread.php?t=1238070

listen it is very easy to do go to the stock recovery and install apply the update zip file then it will boot into clock mod recovery it will never do it oxn its own

codemann8 said:
I put it in PDA as the guide said. I do have an new update tho, after trying a couple more of the tars on the guide I was able to get it back up and working however still unable to get into Clockwork Recovery. Everytime I try booting into it, it has an error "failed to verify whole-file signature" and "signature verification failed". Would you know why this isn't booting into Clockwork?
Click to expand...
Click to collapse
You have the 3e recovery which requires a signature verification. You need to find the modified 3e recovery package on here that didn't require signature verification. That or find a way to downgrade to 2.1 and then install cwm
Sent from my GT-I9000 using xda premium

My suggestion...Odin eb01 with the atlas 2.2 pit file and repartition checked...run Odin and reboot completely after Odin says pass...pull battery hook back up to Odin cwm3-30 fix all after Odin says pass immediately three finger bout into recovery and flash cm7, it contains a kernel which will make recovery stick and you should be good from there.. I'll shoot ya some links for reference.
3-30 fix all recovery
http://forum.xda-developers.com/showthread.php?t=942021
Cm7
http://rootzwiki.com/showthread.php?2120-NIGHTLY-ROM-GRJ90-CyanogenMod-7-for-Samsung-Fascinate-%28fascinatemtd%29
Info worth reading before you flash back to anything that is a non Mtd build
http://forum.xda-developers.com/showthread.php?t=1124391
Sent from my SCH-I500 using XDA App

or you could Odin the power washed rom which has the CWM already to go on it and then flash the CM7 rom via the CWM

[Q] Bricked! Help!

Hi guys
So I did a restore on my note using the volume up/power restore method, and it worked fine, but then I decided to go back to my later version which I backed up before restoring to the earlier one, and now it sits on the 'samsung galaxy note gt-n7000' screen.
I downloaded the correct firmware from samfirmware, and a .pit, and used heimdall to do a recovery (I have a macbook) and it hasn't made any difference.
any suggestions?
yours glumly
Robsa

Robsa said:
Hi guys
So I did a restore on my note using the volume up/power restore method, and it worked fine, but then I decided to go back to my later version which I backed up before restoring to the earlier one, and now it sits on the 'samsung galaxy note gt-n7000' screen.
I downloaded the correct firmware from samfirmware, and a .pit, and used heimdall to do a recovery (I have a macbook) and it hasn't made any difference.
any suggestions?
yours glumly
Robsa
Click to expand...
Click to collapse
Did the firmware flash fine?
And can you still access download mode / recovery?

Which rom where you restoring and from what rom?
Sent from my GT-N7000 using xda premium

Hi guys
I was running ice cream sandwich after an ota update, then I rooted it and installed franco r5 kernal via CMW.
I backed up using CMW then today a week later I backed up using the backup/resotre option you get when doing vol up/power/home
I went back to my original backup which worked, but then decided I wanted to go back to my current set up, which is when it stopped working.
I downloaded the firmware for the irish/uk n7000 N7000XXLQ2_EULP4_XEU and the 16meg pit from the site as well.
I selected 'restore' in heimdall and chose 'repartition' and the .pit I had downloaded and the firmware I downloaded. Heimdall said it had done it all ok but it sits on the boot screen, then goes blank after 10-15 seconds, then the boot screen reappears and stays there.
ETA .pit file was: N7000_I9220_Q1_20110914_16GB.pit and I cannot access recovery, just the volume down reset to use Heimdall

OK, try to flash a stock gb with heimdall. If it gets stuck, let us know at which point ie factoryfs.img
Usually if a rom flash gets stuck at Samsung logo, wiping cache and dalvik cache will let it proceed.
Using a pit file should always be a last resort as its a risky process.
Sent from my GT-N7000 using xda premium

Sorry, I'm a noob at this - only had the phone 13 days!
I have already used Heimdall to flash recovery and .pit and it said it all worked fine. The screen showed a green bar transferring the files and then it restarts, only to sit there on the boot screen again...
So what do you mean about flashing a stock GB? Is that not what I have already downloaded?
-R

Okay, I have located the firmware for gingerbreas 2.3.6 on samfirmware and I'm downloading that.
I assume I just factory restore using the same .pit and the 2.3.6 as before? Think it will work?
Otherwise I will have to take it back to the shop tomorrow and tell them its not working

You don't need a pit file, that's just for repartitioning the chip in extreme circumstances, should only be used for emergencies.
Just flash the gb rom (which contains 3 files, rom, csc and modem). I haven't used heimdall myself so can't advise on setup. Once flashed let me know if it worked or not and if not where it got stuck.
Sent from my GT-N7000 using xda premium

Thanks ST
Heimdall makes you locate a .pit file before you can select the firmware. It then gives you the options:
BOOT
EFS
SBL1
SBL2
PARAM
RECOVERY
CACHE
MODEM
FACTORYFS
DATAFS
UMS
HIDDEN
GANG
KERNEL
So I chose 'Recovery'. most of the others wont let you choose the .tar.md5 file, then mainly ask for either a .bin file or a .img file. KERNEL lets me select it with the .tar.md5 firmware though.
So I will just try RECOVERY again, this time using the 2.3.6 firmwares, not the 4.0.3?
Sorry, I don't mean to act thick! it doesn't help using Heimdall because there is so little online about how to use it compared to ODIN
R

OK. Again, I'm not sure as never used it, so you may want to get some confirmation on this before accepting my response.
If you unzip the gb tar file with 7zip, you'll expose those files, cache.img, zimage (kernel), boot.bin, modem.bin, sbl.bin,factoryfs.img, hidden.img, param.lfs
Perhaps try to allocate each of these to the corresponding section and flash that if recovery option doesn't work.
Is there any reason you choose heimdall over Odin? Are you a Mac user?
Sent from my GT-N7000 using xda premium

when I try to manually upload Kernel, Cache, FactoryFS, Hidden and Modem it does the kernel but falls over at the cache saying:
"ERROR: Failed to confirm end of file transfer sequence! CACHE upload failed!"
what does that mean then?

Okay, so it looks like pretty much all the parts are failing in Heimdall - factoryFS, cache etc. Kernel copied Ok, but all the others return some sort of error.
I have tried both GB and ICS, both fail at the same-ish point in factoryFS.

Robsa said:
Okay, so it looks like pretty much all the parts are failing in Heimdall - factoryFS, cache etc. Kernel copied Ok, but all the others return some sort of error.
I have tried both GB and ICS, both fail at the same-ish point in factoryFS.
Click to expand...
Click to collapse
Sorry youre bricked
Sent from my GT-N7000 using xda premium

so back to the shop tomorrow then I guess?

ssss69 said:
Sorry youre bricked
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
No you're not. Find a friend with a PC and load up Odin. Give that a whirl before declaring defeat. Odin and heimdall are similar but not identical.
Sent from my SGH-T989 using Tapatalk 2

ian577416 said:
No you're not. Find a friend with a PC and load up Odin. Give that a whirl before declaring defeat. Odin and heimdall are similar but not identical.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
+1 for this. Odin is really simple. Make sure samsung drivers are installed on pc (can just load kies). Run odin as administrator, put the phone in download mode (volume down, power and select button held down until it reboots into download) connect to PC, Odin will change to yellow colour if connection good, then all you do is point to the tar file in "pda" and it will sort out all the partitions for you. Really simple. Don't need any pit or repartitioning.
Sent from my GT-N7000 using xda premium

sounds sweet if only I had a PC.... thanks for all your help guys

I think I've finally sorted it! Just restoring ICS now.
The way I fixed it was this:
Download Heimdall 1.3.1 (NOT 1.3.2) and flashed HIDDEN, KERNEL, CACHE, MODEM - FACTORYFS wouldnt flash.
she is restoring now and I pray all will be well
fingers crossed!
BUT now I stupidly went and flashed a non-genuine kernel so I have a yellow triangle
Can I use Triangle Away do you think?

Okay, now I can get both reset screens but still stuck on boot screen. What do I need to do now?

I suggest you use odin first.. if you still can't flash factoryfs, your emmc is toasted...

Sticking At Boot Logo On Every Custom ROM

I am getting stuck on any and every custom ROM no matter what kernel I install with it. It seems as though my device is not accepting system to be installed. I end up installing ROM and then when I try to boot I get a reboot 10 seconds later after failing to get past the Boot Logo and then I check file manager inside of TWRP and don't get anything inside of System folder along with boot folder no matter what ROM Or kernel. have attempted wiping everything through TWRP. Have attempted Odin back to stock(Which Boots Me Up Flawlessly But Happens Again When Installing Recovery Through Odin And Reinstalling ROM) and even happens when attempting to restore backup I have. Weird since Odin works but not ROM nor kernel boots me up. Started happening last night and continues to happen again and again and again now with zero success. Any ideas?
Sent from my SPH-L720 using Tapatalk 4 Beta

Also, when installing Rooted Stock ROM Odexed from within TWRP I get "Not Rooted" message from recovery but when installing DeOdexed I get "Incorrect Permissions, Do You Want To Fix" message. I have tried selecting yes AND no on both to no avail.
Sent from my SPH-L720 using Tapatalk 4 Beta

Really!? Not a soul has an idea!? Lol
Sent from my SPH-L720 using Tapatalk 4 Beta

I would suggest going back to stock with ODIN and then trying a different recovery. I've had no issues flashing many custom ROMs with OUDHS recovery.
http://forum.xda-developers.com/showthread.php?t=2254678

I didnt have an issue whatsoever when I first obtained the device. Ia also getting the infamous "Get PIT Mapping" message when runnung ODIN. Looks like I just needs to repartition the device once I get my hands on the PIT file. Either way, I have gone to stock and tried all of the available recoveries I am aware of to no avail. Weird.
Sent from my SPH-L720 using Tapatalk 4 Beta

was having this ame issue when i first got my S4 and it was because my root was not sticking. get a SU.zip (easily found if you google it) and try flashing that before you flash anything and see if it helps. i am told this was an issue with earlier binarys being used in recovery but im by no means a dev so i could say for sure. also if your using TWRP make sure that when wiping your doing system,data,dalvik,cache.

[Q] Unusual s4 brick help

Forgive my noobishness. I've actually lurked xda boards for years and used the EXCELLENT user made guides for all my phones. However, I'm at a complete loss and nothing I've searched, read, or tried has worked and it's consumed my entire day and left me with no phone at all. I cannot believe this phone can be dead unless there's some physical problem so I'm really hoping someone can walk me back to normal.
I bought a new S4 from T-Mobile on Labor Day (obviously I'm in the US). 2 days ago I rooted it successfully using Jimmy Mcgee's video and the various links including mattlgroff's and k0nane's threads. No problems whatsoever. After I did that I used Ti Backup and backed up the apps just in case, then I ran the moderate version of the Truly Clean script and did a factory reset. Everything was perfect. Then...
My wireless data stopped connecting. But that's not my current problem.
I decided to unroot and go back to factory to a) see if something I did was causing the data issue or b) take it back for an exchange at the store. I started with the K0nane and the Samersh72 guides, but frankly tried so many things and failed I don't know were I went wrong. First I tried M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
Then I tried Samsung-Updates.com-KERNEL-SGH-M919-TMB-M919UVUAMDL-1366964131.tar
Then I tried the one I did to root it OUDHS-Recovery-jfltetmo-1.0.3.3.tar
Mostly I have gotten a NAND writing fail in Odin with everything I tried (yes I tried making sure Kies is off, the original usb cable, and another PC) which then locks me out of the recovery boot screen and gives me some yellow triangle between a phone and a pc with an error about the stock firmware and tells me to connect to Kies. I can fix that by flashing this PIT file CSB_signed_Fusion3_EUR_0325_V2.pit which allows me to go back to the OUDhs recovery screen.
Also Kies will no longer connect to this device and it says driver install failure when I connect it to the PC (except it stell charges, using the stock cable still).
Dear god someone help me, and I will buy you a beverage. I'm doing instant email notifications of replies. PLEASE.

I'm not sunk yet. I'm rereading the FAQs and guides and I'm going to start over to where I was able to get the rooted version to work. I know the CWM recovery is working so we'll see.

Pull out battery for a while, then go to download mode (vol down+home+power) and flash stock fw in odin.
Wysyłane z mojego GT-I9505 za pomocą Tapatalk 2

diodaq said:
Pull out battery for a while, then go to download mode (vol down+home+power) and flash stock fw in odin.
Wysyłane z mojego GT-I9505 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Ok I will try that. Also I am now trying to flash Samsung-Updates.com-SGH-M919-TMB-M919UVUAMDL-1366964131\M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
I am getting a little farther in the Odin process but it still says fail right after
aboot.mbn

Also I originally followed Jonny's video and only flashed the cwm custom recovery though odin. I flashed the rooted zip file from my phone's internal sd card like in the video. Now I can't get to the internal memory so I tried saving the zip file (the one I used to root it) on the ext sd card. I'm unable to flash that rooted zip from the ext sd card because the phone wants to reboot as soon as it starts doing so.
Is there a way to flash that rooted zip file (or a stock one) from an external sd card?
Is there a way to flash that rooted zip file through odin?

All you have to do is get into download mode and flash stock mdl tar with odin. After it's finished, it'll go into recovery by itself and wipe some small cache partition by itself, after it does that, hold onto the volume up button and get into recovery again and do a factory reset. This is so you don't go into a bootloop. Now get CF auto root and flash it so ur rooted. Next flash a custom recovery and ur all set. It's really easy to do.

norml said:
All you have to do is get into download mode and flash stock mdl tar with odin. After it's finished, it'll go into recovery by itself and wipe some small cache partition by itself, after it does that, hold onto the volume up button and get into recovery again and do a factory reset. This is so you don't go into a bootloop. Now get CF auto root and flash it so ur rooted. Next flash a custom recovery and ur all set. It's really easy to do.
Click to expand...
Click to collapse
So far I have been totally unable to get odin to flash a stock tar or any tar since I did the first one 2 days ago. Always, fail.

mattwood440 said:
So far I have been totally unable to get odin to flash a stock tar or any tar since I did the first one 2 days ago. Always, fail.
Click to expand...
Click to collapse
Are you loading the stock tar by clicking PDA?

norml said:
Are you loading the stock tar by clicking PDA?
Click to expand...
Click to collapse
Yes. Also when it fails, it locks me out of the recovery mode. Can you tell me what happens when you flash a new PIT file? Doing that alone does not get a FAIL message and it brings back the recovery screen. However, when I select the pit file it automatically selects the re-partition option which the k0nane says is a no-no (at least for flashing the pda, not sure about the pit which is why I'm asking).

mattwood440 said:
Yes. Also when it fails, it locks me out of the recovery mode. Can you tell me what happens when you flash a new PIT file? Doing that alone does not get a FAIL message and it brings back the recovery screen. However, when I select the pit file it automatically selects the re-partition option which the k0nane says is a no-no (at least for flashing the pda, not sure about the pit which is why I'm asking).
Click to expand...
Click to collapse
Pit file basically means repartitining the storage chip of your device. Yes odin will automatically check repartition when flashing pit files. Flashing pit file is serious business. I recommend following the unbrick/ unroot thtead in the general section. Its pretty precise and I think since you are getting repeated fails in odin you will have to flash pit file.
You will be fine if you follow the instructions there precisely.
Sent from my GT-I9500 using xda app-developers app

OMG it worked. K0nane's procedure worked on a different pc. Dowloaded a fresh Kies but didn't install any of the extra stuff with it. Downloaded, extracted, and ran odin as admin. Hooked it up. Downloaded and extracted the UVUAMDL tar. Put that in the pda box and hit start. Mine would immediately FAIL but this one kept working, and working, and working and reboote. Why why why? I've been at this for about 16 hours. That makes no sense. Thanks anyway. I'll try the other root method when I'm feeling brave again.