Related
Defy Froyo 3.4.2 Cookie Cutter Rom
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.
um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you
this Zip File is for what ?
Thanks
Greetings
you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App
So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse
eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.
what exactly is the benefit of this new method?
drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx
drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene
I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App
psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market
Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App
I tried to update my rooted TF using a repacked 8.4.4.11 update.zip file (the one with all the patch files in it), but it kept failing on checking of the existing APK hashes. Not sure why, but I got around it by doing a clean install of 8.4.4.5, manually applying the 8.4.4.11 patch, then taking all of the changed (between 8.4.4.5 and .11) files and packing them up in a zip file with an updater-script file.
You should be able to apply this to any US version TF (rooted or stock as long as you have CWR) and bring everything up-to-date without losing root or any of your other install modules, system APKs, etc.
Make sure you back up first, as this is something I quickly threw together and has not been properly vetted. If you find a problem, let me know and I'll try to get it fixed and updated ASAP.
You can also download this ZIP and just take out any APKs you are interested in (the google video apk seems to be popular for example).
Link: http://blog.ryantadams.com/2011/07/...4-5-to-8-4-4-11-changed-files-rom-update-zip/
good work dude! i know a bunch of guys here need this. Now Im assuming this has SU installed
The only thing is you should label this Thread correctly with a [ROM] tag so others will know
nicknowsky said:
good work dude! i know a bunch of guys here need this. Now Im assuming this has SU installed
The only thing is you should label this Thread correctly with a [ROM] tag so others will know
Click to expand...
Click to collapse
Unless I misread this is just an update script and not a full ROM. So this would only work for people on 3.1 though right? You shouldn't flash this from 8.2.X.X for example?
Edit: Thanks this is a great idea, and I was just ready to try this when I saw Prime 1.6 out. Keep it up, I wonder if something like this would work when the 3.2 update comes out.
ToyTank said:
Unless I misread this is just an update script and not a full ROM. So this would only work for people on 3.1 though right? You shouldn't flash this from 8.2.X.X for example?
Click to expand...
Click to collapse
...Not sure why, but I got around it by doing a clean install of 8.4.4.5, manually applying the 8.4.4.11 patch, then taking all of the changed (between 8.4.4.5 and .11) files and packing them up in a zip file with an updater-script file....
Click to expand...
Click to collapse
Looks like so; zip should be run on-top of 8.4.4.5.
thank you worked for me
This does not have SU in it (or anyhtign else "custom"), but when applied to a ROM that already has SU/busybox/anyhting else in it, those files will be retained.
This is an "update" in the sense that it only contains files changed between 8.4.4.5 and 8.4.4.11, so you will need to be coming from 8.4.4.5 (or perhaps anyhtign 3.1, not sure). It is nto really an "update" though, as all of the patch files (blahblahblah.apk.p) and the patch script have been replaced with full 8.4.4.11 version of the files and the script has been udpated to simply copy these over into the appropriate folders on yoru TF.
I see this being most useful for people who have modified their 8.4.4.5 install such that in will no longer be patachable using a script that pataches the existing files.
I just used this to update from 8.4.4.5_US and it seems to have worked just fine! I kept my superuser app, and nothing was touched. My apps, widgets, and settings are all in the right places. I've now got 8.4.4.11! Thank you very much rtadams89!
Thank you for this!! I've been racking my brain trying to get to a rooted 8.4.4.11 with a good CWM recovery and this did it!
thanks.
Can anyone check to see if their BT is able to turn on....?
After doing this...my BT won't turn on.
rpavich said:
Can anyone check to see if their BT is able to turn on....?
After doing this...my BT won't turn on.
Click to expand...
Click to collapse
My bluetooth works fine, using it right now. Did you tweak anyhting else on your TF?
Well done!
I still have the update notification, but "About" shows x.11.
Screen seems both brighter & to have smoother transitions.
-bZj
Does this also give you the Nvidia boot animation?
Is it possible to get a .zip for the WW version?
down8 said:
Well done!
I still have the update notification, but "About" shows x.11.
Screen seems both brighter & to have smoother transitions.
-bZj
Click to expand...
Click to collapse
Try clearing data for the "dmclient" app.
AllTheWay said:
Does this also give you the Nvidia boot animation?
Click to expand...
Click to collapse
Yes. Anything new or updated is included.
rtadams89 said:
Try clearing data for the "dmclient" app.
Click to expand...
Click to collapse
Thanks!
rtadams89 said:
Yes. Anything new or updated is included.
Click to expand...
Click to collapse
My transformer still has the "Transformer" boot animation I added - wasn't replaced when using this file to update.
-bZj
[email protected] said:
Is it possible to get a .zip for the WW version?
Click to expand...
Click to collapse
+1, also interested on this
down8 said:
Thanks!My transformer still has the "Transformer" boot animation I added - wasn't replaced when using this file to update.
-bZj
Click to expand...
Click to collapse
That is the boot animation I use, and I may have accidentally included this in the zip. If you want the real 8.4.4.11 animation, you can download the "update" 8.4.4.11 zip file that has been posted on xda and inside you will find that boot animation.
[email protected] said:
Is it possible to get a .zip for the WW version?
Click to expand...
Click to collapse
Since I don't have a WW version myself, I don't have a need to do this and quite frankly because I don't have much free time, I don't want to say I'll do something and then not follow through. Further, I'm not sure I can install the WW versions on my US transformer. That said, I will see if I can whip one together. If you get impatient waiting, you can follow the same process I did and make one yourself:
Backup your current ROM/setup
Wipe your device (leaving CWR in place)
Install the stock 8.4.4.5 WW with the ZIP found on XDA
"Update" to 8.4.4.11 using the update zip found on XDA
Backup this new 8.4.4.11 ROM
Restore to your first backup
Take the backup of the 8.4.4.11 ROM you made last, and use your computer to "unyaffs" it
You will now have 8.4.4.11 versions of all the system files; Look at the updater-script file in the 8.4.4.11 update zip and remove any files you just "unyaffs"ed that aren't mentioned in there
Put all of the remaining files (in their folder structure) into a zip file
Copy the updater-script (and it's folder structure) from my download to your zip file
Verify that your final zip looks like the one I posted
You should then have a ZIP file that will bring all the files on your device up to 8.4.4.11 WW without touching any of your other files (like su).
My BT doesn't turn on either.
I went to this as a stepping stone while recovering from a failed root. Went to an older stock than this update. I notice a few slow downs here and there and BT not working, but that's about it.
What I would really love is an image of 8.4.4.11 stock/rooted. I like having it rooted for things like Titanium, but I still like having the stock image. I can't seem to get back to that now.
Link is down, Dropbox says too much traffic. Rapidshare/MUpload?
Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Here are the files you will need -
CONQUER-ROOT.zip
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select the SPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.
2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.
3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.
4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.
5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.
I've created a new custom ROM here - http://forum.xda-developers.com/showthread.php?p=29369141
You can just download the new files and follow those instructions if you haven't installed this yet.
it work like charm thank you very much sir very good job done..........
---------- Post added at 04:47 AM ---------- Previous post was at 04:38 AM ----------
there is any custom rom kool one ...
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
AestenD said:
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
Click to expand...
Click to collapse
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
brienj said:
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
Click to expand...
Click to collapse
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
AestenD said:
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
Click to expand...
Click to collapse
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
tar -H ustar -c adsp.mbn amss.mbn appsboot.mbn boot.img cache.yaffs mibib osbl recovery.img system.yaffs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Click to expand...
Click to collapse
You can replace each package_name with whatever you want it called.
brienj said:
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
You can replace each package_name with whatever you want it called.
Click to expand...
Click to collapse
Thanks for your help, took me a bit, because I mistakenly flashed the non-CWM image first, and the bootloader version just wasn't letting me in. Luckily I have a jig for my SGS2, and I'm up and running now. Hopefully just the fact that it's the full image, rather than OTA upgraded will fix some of the issues she's been having. If not, then having root gives me so many more troubleshooting options.
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
"known issue" just keep going, it'll work just fine.
Sent from my SPH-D710 using Tapatalk
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
i did all the step but when i hit start on the odin it says please connect phones what can else can i do. loaded the drive from super one click because my laptop running windows seven wasn't reading my phone. Its reading my phone I downloaded the usb driver from this link http://r2doesinc.bitsurge.net/leaked/
now when i run odin now it say """an unnamed file was not found""" whats to do please help
brienj said:
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
Click to expand...
Click to collapse
i got the phone to be read but now when i hit the start button a window pops out says "unnamed file is not found"
It worked for me.
Question
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
roofus1812 said:
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
Click to expand...
Click to collapse
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Finished
brienj said:
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Click to expand...
Click to collapse
I just finished backing up my Conquer using this guide. It was really easy. Thanks.
Hi guys. Anyone use tethering with this? I had tethering working on the old rom fine and another unrooted phone with the ota update. I got a replacement phone and tethering does not work. It only works for google sites - with any tethering app i tried. Is it the hardware or maybe its the stock fc17? I tried reflashing and clearing everything and the problem persists.
I tried using Odin today to root my Samsung Conquer and had a bit of trouble. When I attached the .tar file it gave me an error but as I read this thread I just kept going as if there was no issue. About half way through the Odin installation my phone just rebooted, I tried again and it rebooted it the same spot. I tried putting my phone back into download mode and continue the process, which it did, and I got a "Pass" message at the end. But I don't have CWM and I'm almost positive its still not rooted. Any suggestions?
Any chance of an update with the new OTA included?
Sent from my SPH-D710 using xda premium
There is a new ota fe17. Does anyone know if it will break root? Will it install?
Sent from my SPH-D600 using XDA
I am trying to unbrick my phone. When I go to import stock.jar file I get the error "Tar Header contained invalid file size" Can anyone tell me what to do?
Not sure what you are saying on importing...
Might i suggest reread the op...follow these directions...
http://forum.xda-developers.com/showthread.php?t=1524081
I see you reading the odin thread...just make sure you follow the op...
You can youtube it for Samsung infuse on odin or heimdall...good vid..
bigjoe2675 said:
Not sure what you are saying on importing...
Might i suggest reread the op...follow these directions...
http://forum.xda-developers.com/showthread.php?t=1524081
I see you reading the odin thread...just make sure you follow the op...
You can youtube it for Samsung infuse on odin or heimdall...good vid..
Click to expand...
Click to collapse
I followed the OP, under the "Load Package" tab I click browse like the instructions say, and then select the [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3 and thats when I get the error
this is how i read it, did i give you the wrong link?
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: Green"]CONNECTED[/COLOR][/B][/SIZE]. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
bigjoe2675 said:
this is how i read it, did i give you the wrong link?
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: Green"]CONNECTED[/COLOR][/B][/SIZE]. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
Click to expand...
Click to collapse
Is there a step between 1 and 2 though? As far as loading the .jar file before you flash?
Gimme a few driving home right now...k
Ok, lets readdress all this...you can get download mode...right? see picture of download mod...
The USB + Volume Down + Volume Up Method: Download mode (Noticeable by an Android robot digging with a shovel) is reached by taking everything out (Battery, SIM, MicroSD). plug in the USB cable to your computer and phone then putting in battery at the same time Holding the volume buttons both up and down, (Don't press the power button at all in this method).
How to INSTALL:
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
download this file for your one click to stock...and using above directions...
once that is done and you want to put CWM mod on for flashing a custom ROM, same directions to get in to download mod...
download this file to use the one click to put CWM mod on your phone
ok, and let us know how it all worked out...
here is the link where i took all this...
http://forum.xda-developers.com/showthread.php?t=1524081
Ya thats what I did and still getting the error. It doesnt like that file I try to open. Maybe its me.
I ended up getting it to work through Odin.
Thanks for all your help though!
lazerus06 said:
Ya thats what I did and still getting the error. It doesnt like that file I try to open. Maybe its me. I ended up getting it to work through Odin.
Thanks for all your help though!
Click to expand...
Click to collapse
hey great if Odin works...work bro...bottom-line is getting your phone up and running again...
let me know if you need any more info...kk
lazerus06 said:
Ya thats what I did and still getting the error. It doesnt like that file I try to open. Maybe its me.
I ended up getting it to work through Odin.
Thanks for all your help though!
Click to expand...
Click to collapse
laz, you tried to load the 1 click into heimdall frontend.
You should have just click...run the jar file. Wait a few minutes and it should be ready. The jar is self executable
@qkster bro i really didnt get what u said...'click on oneclick file,wait for a while...jar file is self executable'
do you want me to extract the oneclick file? if yes,what i am supposed to do with its extracted files?
if not then what?
i am getting following list for extraction...
shri003 said:
@qkster bro i really didnt get what u said...'click on oneclick file,wait for a while...jar file is self executable'
do you want me to extract the oneclick file? if yes,what i am supposed to do with its extracted files?
if not then what?
i am getting following list for extraction...
Click to expand...
Click to collapse
the heimdall-1-click is meant to run as is.
double click in windows to run
no extraction
Java has to be installed.
Planning my escape!
qkster said:
the heimdall-1-click is meant to run as is.
double click in windows to run
no extraction
Click to expand...
Click to collapse
as you are instructing me to open the stock .jar file with jave i tried to open with java a black command window popped up and then disappeared ...after thet nothing happened... what am i supposed to do now?
Make sure you have java installed, then look for the file and make sure it is associated with java. If not, right click, open with... and select Java.
Sent from my sweet & buttery Infuse
dead infuse
andros11 said:
Make sure you have java installed, then look for the file and make sure it is associated with java. If not, right click, open with... and select Java.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
yeah i have intalled the latest java and did ...'open with... java'....got same result...black command window popped up and then disappeared!
shri003 said:
yeah i have intalled the latest java and did ...'open with... java'....got same result...black command window popped up and then disappeared!
Click to expand...
Click to collapse
I believe this is supposed to be executed as administrator per qkster's instructions.
The normal way to do that is to right-click and select run-as-administrator
And if that doesn't work, there is a more detailed method to run java jar files as administrator (using elevated command prompt) discussed here:
http://forum.xda-developers.com/sho...culties+in+run-as-administrator+#post30585561
shri003 said:
yeah i have intalled the latest java and did ...'open with... java'....got same result...black command window popped up and then disappeared!
Click to expand...
Click to collapse
Once again this sounds like someone in the frontend of Heimdall.
Just save the .jar file to the desktop.
Make sure your phone is in download mode.
Double click the .jar file from the desktop (not from Heimdall suite), wait for the file to load.
Another screen will open with a long flashbar on the bottom, click it.
Phone will now be flashing and will disconnect when done.
I managed to pull some files together including the .pit file from my now working tablet and make a fully working 4 file firmware and combo (all in one) firmware that CAN be flashed with Odin. I have tested it on my device and it does work. Since I know people are searching EVERYWHERE for this, I have released a download link for these files below.
Please, feel free to re-post this anywhere, just be sure to credit me.
DISCLAIMER (Obviously): I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE AFTER FLASHING. KEEP IN MIND THAT ANYTHING CAN GO WRONG, EVEN IF YOU'RE FLASHING FIRMWARE THAT IS MADE FOR YOUR DEVICE. THE FIRMWARE AVAILABLE BELOW HAS NOT BEEN MODIFIED, ENGINEERED, OR EDITED IN ANY WAY TO CHANGE THE FUNCTIONALITY OF YOUR DEVICE. IF YOUR DEVICE BRICKS AFTER FLASHING, IT'S ALL ON YOU.
Flashing instructions:
But first, the requirements:
1) SM-T337A, Obviously, but seriously, I can't stress how important it is that you check that your model number is matched with the model number in this thread before flashing anything.
2) A Windows pc (NOT A VIRTUAL MACHINE! Using a VM to flash your device has a high chance to hard-brick your tab, and make sure your computer is running Windows XP or newer.)
3) Your device's USB transfer/charging cable
4) A Brain (Obviously)
Now then, the actual steps (4 File Firmware):
1) Boot your tab into download mode (Shut the device down completely, then hold down the power, volume down, and home button at the same time until a warning message appears)
2) Download and open Odin on your pc
3) Grab the USB charging cable and plug your tab into your pc
4) If Odin does not show your device in the list (It will display an "Added" message if the device is detected) download the Samsung USB Drivers for Mobile Phones and install it to your pc. You may need to/and it is recommended to restart your computer after installing the drivers.
5) Extract the zip file you downloaded containing the firmware to your desktop or a memorable place on your computer.
6) If you wish to wipe your data and start from scratch, click on the 'PIT' tab and select the .pit file in the extracted folder. Then, click the 'OPTIONS' tab and select 'Re-Partition' and 'NAND Erase All'.
7) Insert the firmware files into Odin. Within Odin, for instance, Click on the 'BL' button, which is where the bootloader file goes. Select the extracted package that has 'BL' at the beginning, and vice versa.
Example:
BL: *directory*/BL_T337AUCU2BOH4...
AP: *directory*/AP_T337AUCU2BOH4...
CP: *directory*/CP_T337AUCU2BOH4...
CSC: *directory*/CSC_ ATT_T337AUCU2BOH4...
8) Once done, verify that you have correctly done all the steps above, click 'Start' in Odin and wait for Odin to output a "PASS" message before unplugging anything.
9) If you wish to flash the firmware, but keep your data, make sure that there is no .pit file in Odin, make sure that 'Re-Partition' and 'NAND Erase All' are unchecked, and make sure that there is no file inserted under the 'CSC' row.
Tutorial (Combo Firmware)
1) Boot your tab into download mode (Shut the device down completely, then hold down the power, volume down, and home button at the same time until a warning message appears)
2) Download and open Odin on your pc
3) Grab the USB charging cable and plug your tab into your pc
4) If Odin does not show your device in the list (It will display an "Added" message if the device is detected) download the Samsung USB Drivers for Mobile Phones and install it to your pc. You may need to/and it is recommended to restart your computer after installing the drivers.
5) Extract the zip file you downloaded containing the firmware to your desktop or a memorable place on your computer.
6) Within Odin, Select 'AP' and browse to the directory where you extracted the firmware, and select the .tar package in the directory. There should be nothing else under the other tabs, only 'AP' should have a firmware package in it.
7) Flashing this package (unless you perform the "Developers Tip" at the end of this thread) will wipe all of your data, so be sure that the proper .pit file that came with the firmware package is selected under the 'PIT' tab in Odin and make sure that 'Re-Partition' and 'NAND Erase All' are checked in Odin to ensure a complete wipe of all personal data on the device. If you perform the developers tip at the end of the thread, simply insert the new package you created under 'AP', make sure there is no .pit file under the PIT slot, and make sure that 'Re-Partition' and 'NAND Erase All' are unchecked in Odin.
8) Once done, verify that everything is set and ready-to-go, then click 'Start' and wait for Odin to output a "PASS" message before unplugging anything.
9) Enjoy!
WARNING: If you are seeing sites that charge you money for the files, DO NOT BUY IT. They are scams and I HIGHLY SUGGEST AVOIDING THESE SITES. I didn't have to buy anything. If you do buy the firmware from these scam sites, and your device becomes bricked or messed up in some way, don't say I didn't warn you.
4 File Firmware Download: https://mega.nz/#!n8Q3VIIS!OComhygeI5SL5R6n0EXEfiYMBtVn_aOAIcUuLgmYs-k
Combo Firmware Download: https://mega.nz/#!69oEwbBR!vBtHQnrdwAfdZB3iPeGb99Yp7W79efTQr7t6FZXrzIo
Odin 3.12 Download: https://mega.nz/#!KsZiHKTb!aEHdQgO7JAQeUwdJWqS0xoR3lyJH4ieJ6qTbVKce8Zk
If the link doesn't work or goes down for some reason or if you were confused by my instructions in any way, please let me know.
Developers Tip: If you want to flash firmware without wiping your data, make sure there is no pit file selected under the PIT tab in Odin, then extract your firmware package (extract everything into a separate folder for combo firmware, extract the CSC package for 4 file downloads) and remove cache.img.ext4 then repack as a .tar file. Applies to both combo and 4 file firmware packages. In 4 file packages, cache.img.ext4 is in the CSC file. However, in some cases this may put your device in a bootloop. If you wish to do this on an older device and the cache file doesn't have the .ext4 extension at the end, don't worry, it'll work the same way.
Now that you have the firmware, WHY NOT ROOT IT? Check out my thread on how to do so here: https://forum.xda-developers.com/tab-4/general/root-how-to-root-sm-t337a-supersu-t3553848
Cheers!
Does anyone know the process for extracting the files like this from an OTA update? I have some files I would like to extract from another OTA. Thank you
Sent from my SAMSUNG-SM-N910A using XDA-Developers Legacy app
dkmac said:
Does anyone know the process for extracting the files like this from an OTA update? I have some files I would like to extract from another OTA. Thank you
Sent from my SAMSUNG-SM-N910A using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll be honest and say its not easy. Making this firmware took me about 3 months. OTA update files are very different from actual Odin firmware files. If you want to extract the files from an OTA update, I just used 7Zip and went from there.
Lollipop 5.1.1 Root for SM-T337A
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
18Echo said:
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
Click to expand...
Click to collapse
Your welcome bro, happy to help! I have actually rooted my tab with SuperSU, fully working. The only thing is its temporary, and I avoid rebooting or shutting the device down at all because it's a system-less SuperSU (meaning temporary). I'll make a thread on how to achieve root on this tab later tomorrow when I get home from work, unless someone replies to this before I do (It's late where I'm at).
Cheers!
18Echo said:
@KingOfTheNet - Great stuff. There are definitely some shady sites out there offering firmware for the T337A so thank you.
Not to be greedy but any recommendations on rooting 5.1.1 on SM-T337A. I am trying to remove all of the Samsung and AT&T bloatware and get my Tab 4 running lean and mean. I am pretty sure I went with your firmware - my build number is listed as LMY47X.T337AUC2BOH4.
Appreciate the support.
Click to expand...
Click to collapse
Just made a thread for it here: https://forum.xda-developers.com/tab-4/general/root-how-to-root-sm-t337a-supersu-t3553848
Cheers!
Hello! ... First of all, thank you for all your hard work! But unfortunately that firmware does not seem to work for me. I'm a little newbie, so I'd appreciate if someone could explain the steps to follow specifically with Odin, as a tutorial or something ... so that I can distinguish what I'm doing wrong.
I uploaded a short video so you can see what I mean... If you could take the time to watch it and tell me what I'm doing wrong, that would be awesome.
Here it is: youtu.be/9JsLVJ-xHMA (I cannot post direct link since I'm new user)
I've downloaded some files with name ATT_T337AUCU2BOH4_T337AATT2BOH4.zip (1.19gb) put by poorusernamebychoice and their tar.md5 file is gone 404.
Now i need some help here, this zip contains:
AP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
BL_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CSC_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
MILLETLTE_USA_ATT.pit
This is big file so now I'm stuck what to do or i start a fresh download from above links.
Sent from my SAMSUNG-SM-T337A using Tapatalk
darkcrazy75 said:
Hello! ... First of all, thank you for all your hard work! But unfortunately that firmware does not seem to work for me. I'm a little newbie, so I'd appreciate if someone could explain the steps to follow specifically with Odin, as a tutorial or something ... so that I can distinguish what I'm doing wrong.
I uploaded a short video so you can see what I mean... If you could take the time to watch it and tell me what I'm doing wrong, that would be awesome.
Here it is: youtu.be/9JsLVJ-xHMA (I cannot post direct link since I'm new user)
Click to expand...
Click to collapse
Sorry for the late responce, my internet has been down for a while now (2 weeks). I'll watch the video later today and edit this post with an explainatio n.
_SAM11_ said:
I've downloaded some files with name ATT_T337AUCU2BOH4_T337AATT2BOH4.zip (1.19gb) put by poorusernamebychoice and their tar.md5 file is gone 404.
Now i need some help here, this zip contains:
AP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
BL_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CP_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
CSC_T337AUCU2BOH4_T337AATT2BOH4_HOME.tar
MILLETLTE_USA_ATT.pit
This is big file so now I'm stuck what to do or i start a fresh download from above links.
Click to expand...
Click to collapse
Do you mean you need to re-download the files or you need help with flashing them? Dl links are at the middle of the thread.
KingOfTheNet said:
Do you mean you need to re-download the files or you need help with flashing them? Dl links are at the middle of the thread.
Click to expand...
Click to collapse
I hve these files i wrote above. So if they're working, i just need procedure
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
I hve these files i wrote above. So if they're working, i just need procedure
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
It's actually very easy, that's why I didn't put any instructions in the thread, I just assumed people knew how to do it by now. But I'm happy to provide instructions to those people who don't know how. Instead of posting said instructions right here, I'll update the thread with instructions.
Cheers!
KingOfTheNet said:
It's actually very easy, that's why I didn't put any instructions in the thread, I just assumed people knew how to do it by now. But I'm happy to provide instructions to those people who don't know how. Instead of posting said instructions right here, I'll update the thread with instructions.
Cheers!
Click to expand...
Click to collapse
That means alot after my last reply, i had been trying to flash with odin but i dnt kno why tablet isn't connecting laptop while other phones are. Not evn on media mode. So I'm downloading ota update.zip
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
That means alot after my last reply, i had been trying to flash with odin but i dnt kno why tablet isn't connecting laptop while other phones are. Not evn on media mode. So I'm downloading ota update.zip
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
This might take me a while, I can't edit the thread (kinda odd). I've gotta talk to admin about it but I'll try to get instructions up for ya asap (unless someone replies to you with instructions before I do).
Update: I managed updating to 5.1.1 update. Now i just need January update and root the device. I just need January zip update ota if u can manage me getting that please
Sent from my SAMSUNG-SM-T337A using Tapatalk
_SAM11_ said:
Update: I managed updating to 5.1.1 update. Now i just need January update and root the device. I just need January zip update ota if u can manage me getting that please
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
I believe I have the file stored somewhere on my hard drive, I'll look and pm you a link if I can find it.
Cheers!
KingOfTheNet said:
I believe I have the file stored somewhere on my hard drive, I'll look and pm you a link if I can find it.
Cheers!
Click to expand...
Click to collapse
Sure Thanks for much help
Sent from my SAMSUNG-SM-T337A using Tapatalk
Guys no lollipop update for tab4 t230 ?
tab4map4 said:
Guys no lollipop update for tab4 t230 ?
Click to expand...
Click to collapse
No, this thread is for the Tab 4 8.0 AT&T. Please make sure you consult the relevant forums for your device model as doing anything meant to be done on different devices can be catastrophic.
Cheers!
_SAM11_ said:
Sure Thanks for much help
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
Finally got the instructions up. You can check the very beginning of the thread for instructions on flashing. Just remember, I will not be held responsible if your device is bricked after the matter.
Cheers!