Database Develop

[RECOVERY] ClockworkMod Recovery for Galaxy S (Beta 2!)

WARNING: You must be comfortable using Odin when flashing this. It is very difficult to brick using Odin, but I don't want to handhold people through fixing their devices.
This is Clockwork Recovery beta 2, it is tailored for the Vibrant. Please let me know how it works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery/Boot TAR download (do NOT extract):
http://koush.tandtgaming.com//test/package1279903787.tar
3e106a2a8828158d334fb70e4874907a
Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush
Installation instructions:
Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)
Start Odin3
Press PDA
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads

Works for me...but so did the first one...so I guess risk may still remain for others.

Ok so I started ODIN, put my phone into download mode, and opened up the new PDA file.
Now my Odin has been stuck on this message for the last 10 mins.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
And my phone is still in download mode. I don't wanna pull the wire or turn the phone off and mess something up hehe.
Also was I suppose to load the .pit file into odin too?

sxfx said:
Ok so I started ODIN, put my phone into download mode, and opened up the new PDA file.
Now my Odin has been stuck on this message for the last 10 mins.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
And my phone is still in download mode. I don't wanna pull the wire or turn the phone off and mess something up hehe.
Also was I suppose to load the .pit file into odin too?
Click to expand...
Click to collapse
Yes, when flashing you always need to load the PIT file. I use 512 as it doesnt cause as many problems. Try to hit reset on odin and load the pit file and flash again...As long as you didn't have repartition clicked you should be fine. And without the PIT file it prob didn't even flash anything.

sxfx said:
Ok so I started ODIN, put my phone into download mode, and opened up the new PDA file.
Now my Odin has been stuck on this message for the last 10 mins.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
And my phone is still in download mode. I don't wanna pull the wire or turn the phone off and mess something up hehe.
Also was I suppose to load the .pit file into odin too?
Click to expand...
Click to collapse
It'll also stay like that if you forget to check "Force Reboot".

While this didn't brick my phone...it made my brand new out of the box vibrant to where it doesnt boot the stock firmware. Thought it was working fine, but spoke too soon. And now it just boots back to the battery indicator everytime. Nothing a new flash can't fix, but just saying for feedback purposes.
****Edit****
Phone just randomly booted....it seems to be acting erraticly...not sure what the difference that caused the phone to start booting.

Same as fykick if I leave the usb plugged in. If I take the usb out and turn it on it gets to the lock screen and then reboots, continuously.
Edit:
Did a wipe and rebooted the phone a couple of times and now it is running ok

Worked for me, although navigation keys are somewhat strange, have to press vol down key to go up
Have tried to do nand backup, have got md5 checksum error

stillyone said:
Worked for me, although navigation keys are somewhat strange, have to press vol down key to go up
Click to expand...
Click to collapse
Yeah, until the recovery is specifically written for the Vibrant, it still contains the keymappings of the INTL version where the volume buttons are flipped.

Now started to get kernal panic...tried reflashing couple more times ...same thing

I can now boot into clockwork recover, but my phone keeps crashing, I've tried resetting everything, but I get continuous errors like:
Sorry! The process com.android.phone has stopped unexpectedly.
I get them every few seconds. Sometimes the error is for web other times media. These pop up over and over and don't let me do anything. Any ideas?

I was successful in flashing clockwork and successfully created a nandroid.
There were however issues that were present with the 1st build. The phone would loop reboot if the SD card was inserted. If removed the phone would boot and stay functional, however once the card was inserted it would reboot loop again within a couple min. Had "force closes" on the market and file manager.
Oh and the only other thing was the "Home" button acted as a back button.
I posted these on the irc channel Koush, but I do not believe you were in there at the time.
For those of you having huge issues, following this should set you straight.
http://forum.xda-developers.com/showthread.php?t=728698

I'm such an idiot, I tried fixing my phone by flashing it to a stock rom (after repreated crashing after install Clockwork recovery today), not realizing that it was a Captivate rom, and now all my Vibrant will do is load an AT&T World Phone screen over and over. I used the one click Odin/Rom thing from the Captivate forum (obviously not realizing that's where I had ended up).

out of curiousity where is everyone getting this 512 pit file? the only pit file i have is the one that came with odin but it is 513
ok answered my own question....use search first
sorry

kelmerp said:
I'm such an idiot, I tried fixing my phone by flashing it to a stock rom (after repreated crashing after install Clockwork recovery today), not realizing that it was a Captivate rom, and now all my Vibrant will do is load an AT&T World Phone screen over and over. I used the one click Odin/Rom thing from the Captivate forum (obviously not realizing that's where I had ended up).
Click to expand...
Click to collapse
Check out the link in the post above yours. Should help with your issue. Good luck.

Yes, it did, thanks. Back to a stock-ish ROM. Will retry Clockwork later today once my heart starts beating again... Modding my new baby is like a rollercoaster ride.

kelmerp said:
Yes, it did, thanks. Back to a stock-ish ROM. Will retry Clockwork later today once my heart starts beating again... Modding my new baby is like a rollercoaster ride.
Click to expand...
Click to collapse
No point in trying until he releases an new one. The others will just put you right back were you were before.

I have odin v4.03 from flashing behold II roms wondering if this is the corect version since some of these posts mention odin3. thanks

will clockwork recovery wipe every folder on the phone? or will the /sdcard folder remain? (I believe the /sdcard is the phones memory ~16gb) thanks

Pancake345 said:
will clockwork recovery wipe every folder on the phone? or will the /sdcard folder remain? (I believe the /sdcard is the phones memory ~16gb) thanks
Click to expand...
Click to collapse
In a standard wipe it does not touch sd storage.

FRP LOCK ON Can't ODIN firmware... Lord help me.

Canadian NOTE5 here, I forgot to unclick the OEM Lock in the developer options and now I cannot boot up, I cannot flash ODIN stock firmware from Canada, although only Puerto Rico seems to exist for SM-N920W8 etc... I get the error HIDDEN.IMG then FAIL
I cannot flash TWRP because I get BLOCKED BY FRP LOCK.
Smart Switch does not support my device. So that doesn't work either.
I have tried ODIN TMOBILE firmware, that fails right away.
I have had 10 different rooted devices without a hitch, is this my first brick ever?
Do I have to wait for different firmware?
Anyone? Happy to buy anyone a beer or two who can assist me!
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Model Number: N920W8
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sboot.bin
NAND Write Start!!
cm.bin
boot.img
recovery.img
system.img
cache.img
hidden.img
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)

I guess your best bet is to wait for official Bell firmware. But it's strange that I never came across that. Did you read the instructions on getting the phone rooted? Did you enable the OEM unlock?

Did you try Samsung Kies software.
Sometimes it can restore phone to original.

LouK said:
Did you try Samsung Kies software.
Sometimes it can restore phone to original.
Click to expand...
Click to collapse
jqmalang said:
I guess your best bet is to wait for official Bell firmware. But it's strange that I never came across that. Did you read the instructions on getting the phone rooted? Did you enable the OEM unlock?
Click to expand...
Click to collapse
Solved! I reflashed the firmware and flashed the hidden.img separately in Odin and success!
Sent from my Gorgeous Note5

Brava27 said:
Solved! I reflashed the firmware and flashed the hidden.img separately in Odin and success!
Sent from my Gorgeous Note5
Click to expand...
Click to collapse
how please??

edwardob said:
how please??
Click to expand...
Click to collapse
You need to flash firmware from your provider.

Brava27 said:
You need to flash firmware from your provider.
Click to expand...
Click to collapse
how to flash
" I reflashed the firmware and flashed the hidden.img separately in Odin"
do you remove hidden .img from firmware..
how did you do it please??

edwardob said:
how to flash
" I reflashed the firmware and flashed the hidden.img separately in Odin"
do you remove hidden .img from firmware..
how did you do it please??
Click to expand...
Click to collapse
Why do you want to remove hidden.img? You only have to do this if you get an error message fail hidden.img

Brava27 said:
Why do you want to remove hidden.img? You only have to do this if you get an error message fail hidden.img
Click to expand...
Click to collapse
thats right/........so how do you do it?

heres mine
similiar problem different file
anyone any ideas?

my mobile phone, same as you,how can i do? i am using note 5 n9200,what i need to download? 1,odin,and other?can you tell me the step,thank you very much

same here SM-N920W8
Please theres a step by step guide to flash tru odin ,say solved but no how to thanks

pls help us i have the same on my note 5 N9200 and i tryd evrythink so if its working to you you have me some hoop that i dont loose 800 dollar on my note 5

Ekinz1219 said:
my mobile phone, same as you,how can i do? i am using note 5 n9200,what i need to download? 1,odin,and other?can you tell me the step,thank you very much
Click to expand...
Click to collapse
did u solve the problem? i have the same device as you do, and i have the same situation.
After tried almost every Stock Rom, i still get stuck after boot.img.

This problem is because you forgot to unlock bootloader from developper options.
Reflash the official latest stock firmware with odin, then unlock the bootloader and reflash what ever you want after.

edwardob said:
similiar problem different file
anyone any ideas?
Click to expand...
Click to collapse
Ekinz1219 said:
my mobile phone, same as you,how can i do? i am using note 5 n9200,what i need to download? 1,odin,and other?can you tell me the step,thank you very much
Click to expand...
Click to collapse
TIAR2018 said:
Please theres a step by step guide to flash tru odin ,say solved but no how to thanks
Click to expand...
Click to collapse
andixxqaz said:
pls help us i have the same on my note 5 N9200 and i tryd evrythink so if its working to you you have me some hoop that i dont loose 800 dollar on my note 5
Click to expand...
Click to collapse
danielweng said:
did u solve the problem? i have the same device as you do, and i have the same situation.
After tried almost every Stock Rom, i still get stuck after boot.img.
Click to expand...
Click to collapse
Download the latest stock firmware for your device model, and extract from it the file called hidden.img, rename that file as hidden.img.tar Now open Odin and try to install the firmware you downloaded, when you see the error in Odin, load the file hidden.img.tar on AP and flash it. Now turn on the phone and wait around 5 minutes, it should boot up.
Please note that this will only work if the error shown in Odin is:
hidden.img
FAIL!

Brava27 said:
Solved! I reflashed the firmware and flashed the hidden.img separately in Odin and success!
Sent from my Gorgeous Note5
Click to expand...
Click to collapse
Hi, I had the same issue I tried rooting my note 5 and it failed and now i'm stuck
i'm really freaking out I paid a lot of money for it,
odin says " NAND write failed"
can you please help me ?!

m7mdas3d said:
Hi, I had the same issue I tried rooting my note 5 and it failed and now i'm stuck
i'm really freaking out I paid a lot of money for it,
odin says " NAND write failed"
can you please help me ?!
Click to expand...
Click to collapse
You need the correct firmware for your device from sammobile.com

Brava27 said:
You need the correct firmware for your device from sammobile.com
Click to expand...
Click to collapse
I have the exact one, I have downloaded it before rooting in case something wrong happened, which did :crying: !!!
still fails at the NAND write

m7mdas3d said:
I have the exact one, I have downloaded it before rooting in case something wrong happened, which did :crying: !!!
still fails at the NAND write
Click to expand...
Click to collapse
You need to use the odin Odin3 v3.10.7.1

[Help] Samsung Galaxy S4 5.0.1 SGH-I337 won't reboot properly

This is my first post so I'm sorry if I did not post this in the right place or didn't do something else regular-place to these forums. Please guide me in the right direction if I didn't. So I rooted my phone with Kinguser and then switched it to SuperSu pro using the in-app instructions ins SuperSu. My goal is to install Xposed onto my phone but part of the problem is that I have to boot and manual recovery with TWRP or something similar for Xposed to work on my S4 (specifications above). But every manual recovery app I download works up to the point I actually try to reboot. All of them can find my root access and say they install successfully, but when I hit reboot and recovery, it always goes into Odin mode (and in the top left corner of Odin mode it says cannot reboot normally). I can get out of Odin mode easily so the problem isn't that I'm stuck there. I just want to know how to proceed with reboot and recovery when every time I try it goes into Odin mode.

Christian.Kodele said:
This is my first post so I'm sorry if I did not post this in the right place or didn't do something else regular-place to these forums. Please guide me in the right direction if I didn't. So I rooted my phone with Kinguser and then switched it to SuperSu pro using the in-app instructions ins SuperSu. My goal is to install Xposed onto my phone but part of the problem is that I have to boot and manual recovery with TWRP or something similar for Xposed to work on my S4 (specifications above). But every manual recovery app I download works up to the point I actually try to reboot. All of them can find my root access and say they install successfully, but when I hit reboot and recovery, it always goes into Odin mode (and in the top left corner of Odin mode it says cannot reboot normally). I can get out of Odin mode easily so the problem isn't that I'm stuck there. I just want to know how to proceed with reboot and recovery when every time I try it goes into Odin mode.
Click to expand...
Click to collapse
Easiest way is to go into download mode(Odin mode) and flash TWRP via Odin. In Odin make sure to uncheck reboot and f. reset once TWRP is flash unplug and pull the battery and reboot directly to recovery (power & volume+) once you get into TWRP it'll stay after that. Then just reboot your phone normally. Also within TWRP you can flash SuperSU.
TWRP download:
https://dl.twrp.me/jfltespr/twrp-2.8.4.0-jfltespr.tar.html
Sent from my SPH-A120

mattzeller said:
Easiest way is to go into download mode(Odin mode) and flash TWRP via Odin. In Odin make sure to uncheck reboot and f. reset once TWRP is flash unplug and pull the battery and reboot directly to recovery (power & volume+) once you get into TWRP it'll stay after that. Then just reboot your phone normally. Also within TWRP you can flash SuperSU.
TWRP download:
https://dl.twrp.me/jfltespr/twrp-2.8.4.0-jfltespr.tar.html
Sent from my SPH-A120
Click to expand...
Click to collapse
Thanks for the response!! I found the twrp file on their website (one which is a .md5 and one which is a .img which both don't work). They would both just freeze in Odin. So I found a tool online that turns .img files to .tar file. Link to tool below
http://forum.xda-developers.com/showthread.php?t=2281287
with another thread that helped to fix the runme.bat file
http://forum.xda-developers.com/showthread.php?p=42511844#post42511844
and that helped make a .tar file which doesn't freeze up Odin, but when I run the .tar file made from that tool, the manual flash using Odin runs through and fails. the Odin prompt is shown below.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Anything I'm doing wrong so far??

Anything I'm doing wrong so far??
Click to expand...
Click to collapse
Pretty much everything. I would not trust converting files like that. High potential for bricking your device.
The link I gave you is a .tar file that Odin likes. The md5 is at the top, yes, but you need the tar file just a little further down.
I linked you the latest one that is .tar. Newer versions are in .img that can be flashed in recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-A120

mattzeller said:
Pretty much everything. I would not trust converting files like that. High potential for bricking your device.
The link I gave you is a .tar file that Odin likes. The md5 is at the top, yes, but you need the tar file just a little further down.
I linked you the latest one that is .tar. Newer versions are in .img that can be flashed in recovery.
Sent from my SPH-A120
Click to expand...
Click to collapse
I downloaded the .tar file you linked above and tried it and it still failed. So to be descriptive as possible the first thing I do is plug my phone (without twrp installed) into my pc. Then I turn it off. Then I try to reboot. Phone can't reboot and forwards directly to Odin mode. I download the .tar file you linked me above. I do not unzip the file. I have Odin3 v3.07 installed. I open Odin and uncheck Auto Reboot and F. Reset Time. I click on PDA and select the unzipped zip file for flash. Nothing is said in the message display after that and is still at.
<ID:0/005> Added!!
Then I click Start. Flash still fails and message displays
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone isn't bricked but it seems that the .tar file linked above isn't working as well. Is it my phone probably?? Samsung Galaxy S4 AT&T SGH-I337 5.0.1 Lollipop rooted with Kinguser and then switched over with SuperSu pro via in app instructions?

Christian.Kodele said:
I downloaded the .tar file you linked above and tried it and it still failed. So to be descriptive as possible the first thing I do is plug my phone (without twrp installed) into my pc. Then I turn it off. Then I try to reboot. Phone can't reboot and forwards directly to Odin mode. I download the .tar file you linked me above. I do not unzip the file. I have Odin3 v3.07 installed. I open Odin and uncheck Auto Reboot and F. Reset Time. I click on PDA and select the unzipped zip file for flash. Nothing is said in the message display after that and is still at.
<ID:0/005> Added!!
Then I click Start. Flash still fails and message displays
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone isn't bricked but it seems that the .tar file linked above isn't working as well. Is it my phone probably?? Samsung Galaxy S4 AT&T SGH-I337 5.0.1 Lollipop rooted with Kinguser and then switched over with SuperSu pro via in app instructions?
Click to expand...
Click to collapse
Jeez I'm an idiot, I thought you were on jfltespr not jflteatt, I believe you need to use the safestrap, check out this thread:
http://forum.xda-developers.com/showthread.php?t=2448925
Sent from my SPH-A120

mattzeller said:
Jeez I'm an idiot, I thought you were on jfltespr not jflteatt, I believe you need to use the safestrap, check out this thread:
http://forum.xda-developers.com/showthread.php?t=2448925
Sent from my SPH-A120
Click to expand...
Click to collapse
Thanks so much for all the help!! After that linked I found a bunch of conversations that helped. If you every help out with someone with the same specifications on their phone then I had there's not much I can say that can help as far as Lollipop goes. I could not find a way to get Xposed on my device as is. But if anyone really does want it, I found that if you find the right .PIT file and the stock ROM for a previous version of Android (I tried a few which all work, but I would suggest KitKat because why not) then you'll be able to do anything you want without all the heartache. After I used Odin to flash KitKat onto my device, I found that I didn't even need TWRP, Xposed installed quite nicely, and even though the layout doesn't look quite as nice as Lollipop, you can find a bunch of display modules in Xposed that fit the bill quite well.
All in all, Samsung Galaxy S4 AT&T SGH-I337 5.0.1 and want Xposed?? You're screwed. Flash KitKat.

[SM-A501FD]Can not upgrade to 6.0.1

Hi, i have version 5.1.1
I can upgrade to android 6.0.1.
This errors log:
PHP:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help!!

t.nt said:
Hi, i have version 5.1.1
I can upgrade to android 6.0.1.
This errors log:
PHP:
Enter CS for MD5.. Check MD5.. Do not unplug the cable.. Please wait.. Checking MD5 finished Sucessfully.. Leave CS.. Added!! Odin engine v(ID:3.1203).. File analysis.. SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. SingleDownload. boot.img cache.img FAIL! Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1) Removed!!
Image:
Please help!!
Click to expand...
Click to collapse
Probably different firmware regions. Cache.img will be a different size.
Unpack the tar file with 7zip, remove the cache.img and then repack the rest of the files to tar with 7zip.

Open Developer Mode
Enter Developer Options
Find OEM unlock and tick enable.
Try upgrade again.
Sample Picture
http://forum.xda-developers.com/attachment.php?attachmentid=3669615&d=1457070651

ashyx said:
Probably different firmware regions. Cache.img will be a different size.
Unpack the tar file with 7zip, remove the cache.img and then repack the rest of the files to tar with 7zip.
Click to expand...
Click to collapse
I TRIED IT, BUT UTIL NOT OK...
This is my device info:
Regions: Malaisia.
I don't know this issue, why i cannot flash via Odin?

xpity34 said:
Open Developer Mode
Enter Developer Options
Find OEM unlock and tick enable.
Try upgrade again.
Sample Picture
http://forum.xda-developers.com/attachment.php?attachmentid=3669615&d=1457070651
Click to expand...
Click to collapse
Yes, i did

t.nt said:
I TRIED IT, BUT UTIL NOT OK...
This is my device info:
Regions: Malaisia.
I don't know this issue, why i cannot flash via Odin?
Click to expand...
Click to collapse
So what's not working now?

ashyx said:
So what's not working now?
Click to expand...
Click to collapse
I cannot find ROM for my devices...

Maybe it's not working because your device is A510FD, from what i see in your baseband, and you try to flash A510F. In download mode what device name is showing? Also download latest samsung drivers, try with another odin version, another usb, another pc and so on.. Report here.
Sent from my SM-A500F using Tapatalk

corsicanu said:
Maybe it's not working because your device is A510FD, from what i see in your baseband, and you try to flash A510F. In download mode what device name is showing? Also download latest samsung drivers, try with another odin version, another usb, another pc and so on.. Report here.
Sent from my SM-A500F using Tapatalk
Click to expand...
Click to collapse
I download ROM here:
http://s-update.samsungvn.com/
PDA: A510FXXS3API4
CSC: A510FDOLB2APF2
OS: 5.1.1
Please check the attachments to see process...

t.nt said:
I download ROM here:
http://s-update.samsungvn.com/
PDA: A510FXXS3API4
CSC: A510FDOLB2APF2
OS: 5.1.1
Please check the attachments to see process...
Click to expand...
Click to collapse
When the flash fails reboot the phone again in download an reconnect it to pc. Open tar.md5 file with 7zip, pull cache.img, add the image previously pulled into a .tar archive and flash it in AP tab. Reboot into stock recovery, wipe data, reboot and profit. Cheers!
Edit: at each flash uncheck "Autoreboot" in odin and reboot it manually.
Sent from my SM-A500F using Tapatalk

t.nt said:
I download ROM here:
http://s-update.samsungvn.com/
PDA: A510FXXS3API4
CSC: A510FDOLB2APF2
OS: 5.1.1
Please check the attachments to see process...
Click to expand...
Click to collapse
I thought you wanted to upgrade to MM?
Why don't you just flash this:
http://forum.xda-developers.com/sam...a510fd-official-firmware-4-files-one-t3470085
Leave out the CSC part if you want to keep your original CSC.
---------- Post added at 08:01 AM ---------- Previous post was at 07:57 AM ----------
corsicanu said:
When the flash fails reboot the phone again in download an reconnect it to pc. Open tar.md5 file with 7zip, pull cache.img, add the image previously pulled into a .tar archive and flash it in AP tab. Reboot into stock recovery, wipe data, reboot and profit. Cheers!
Edit: at each flash uncheck "Autoreboot" in odin and reboot it manually.
Sent from my SM-A500F using Tapatalk
Click to expand...
Click to collapse
I think you mean wipe CACHE. Wipe DATA will factory reset the device and wipe all personal files.

ashyx said:
I thought you wanted to upgrade to MM?
Why don't you just flash this:
http://forum.xda-developers.com/sam...a510fd-official-firmware-4-files-one-t3470085
Leave out the CSC part if you want to keep your original CSC.
---------- Post added at 08:01 AM ---------- Previous post was at 07:57 AM ----------
I think you mean wipe CACHE. Wipe DATA will factory reset the device and wipe all personal files.
Click to expand...
Click to collapse
To avoid issues or bootloops is better to wipe data, and since he's playing with odin and several fw files with God knows what android version, he knows the risks. So i meant what i said.
Sent from my SM-A500F using Tapatalk

corsicanu said:
To avoid issues or bootloops is better to wipe data, and since he's playing with odin and several fw files with God knows what android version, he knows the risks. So i meant what i said.
Sent from my SM-A500F using Tapatalk
Click to expand...
Click to collapse
He doesn't need to wipe DATA.
Samsung official upgrades don't usually require wiping DATA.
If it doesn't boot or there are issues afterwards then wiping DATA may fix it, but there is no need otherwise.

i think is wrong rom

Unbrick I9000 - all old links are dead.

Hey guys, I have a problem with i9000. Its bricked (not soft) I have to use USB jig to access download mode.
In Heimdall I recevice either libusb error -12 (1.4 version), or no detection (1.3.1 on windows).
All host links for recoveries or unbricking are not not active. Can you please help me to unbrick phone and install maybe lineageos or any other android?
Thanks in advance.

Do you have USB jig, can you enter download mode? I restored mine with ezbase recovery kit to Gingerbread, then updated it with kies to 2.3.6 then flashed LineageOS 11.
.

MobileTechArena said:
Do you have USB jig, can you enter download mode? I restored mine with ezbase recovery kit to Gingerbread, then updated it with kies to 2.3.6 then flashed LineageOS 11.
.
Click to expand...
Click to collapse
Yes, I do have USB Jig and I can access download mode, but Odin and other programs are not able to connect
EDIT:
Odin usually gives:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

ifsz said:
Yes, I do have USB Jig and I can access download mode, but Odin and other programs are not able to connect
EDIT:
Odin usually gives:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I had the same problem, then i installed Samsung Kies including all additional cable drivers it suggested to install. Then after phone was visible in Kies it was also recognized by Odin.
EDIT: This is the Kies i used..
.

MobileTechArena said:
I had the same problem, then i installed Samsung Kies including all additional cable drivers it suggested to install. Then after phone was visible in Kies it was also recognized by Odin.
EDIT: This is the i used..
.
Click to expand...
Click to collapse
Even with Kies it still gives same errors.

ifsz said:
Even with Kies it still gives same errors.
Click to expand...
Click to collapse
Does Kies sees device as I9000? Maybe try different PC, i was trying to fix that for hours but at the end Kies and its additional drivers fixed it for me..

MobileTechArena said:
Does Kies sees device as I9000? Maybe try different PC, i was trying to fix that for hours but at the end Kies and its additional drivers fixed it for me..
Click to expand...
Click to collapse
Unfortunetly - no luck, on two devices with additional drivers. Any more ideas?

ifsz said:
Unfortunetly - no luck, on two devices with additional drivers. Any more ideas?
Click to expand...
Click to collapse
Don't know, different cable, USB port or something... Uninstall all Samsung drivers, Kies and everything and reboot, then try with the Kies from my link.. But i do believe its problem with drivers.

MobileTechArena said:
Does Kies sees device as I9000? Maybe try different PC, i was trying to fix that for hours but at the end Kies and its additional drivers fixed it for me..
Click to expand...
Click to collapse
MobileTechArena said:
Don't know, different cable, USB port or something... Uninstall all Samsung drivers, Kies and everything and reboot, then try with the Kies from my link.. But i do believe its problem with drivers.
Click to expand...
Click to collapse
I've got some progress:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems frozen.

ifsz said:
I've got some progress:
It seems frozen.
Click to expand...
Click to collapse
Yeah, sometimes it freezes at SetupConnection.. Try few more times.

MobileTechArena said:
Yeah, sometimes it freezes at SetupConnection.. Try few more times.
Click to expand...
Click to collapse
I have tried almost 20 times, different USB cables, even different odin versions. Same.
edit: Wait, I have tried again, and now something moves. TBC
edit2: Unbricking was successful, thank you very much! I have a problem with lineageos installation, it always boots to recovery (clockwork) - installtion complete without errors.

ifsz said:
I have tried almost 20 times, different USB cables, even different odin versions. Same.
edit: Wait, I have tried again, and now something moves. TBC
Click to expand...
Click to collapse
:laugh::good:

MobileTechArena said:
:laugh::good:
Click to expand...
Click to collapse
Unbricking was successful, thank you very much! I have a problem with lineageos installation, it always boots to recovery (clockwork) - installtion complete without errors.
Edit: ok I have managed to install OS, but gapps are missing - and I cannot access recovery now, any ideas?
Edit2: I have reinstalled recovery- now is working
Thank you very much for help!

ifsz said:
Unbricking was successful, thank you very much! I have a problem with lineageos installation, it always boots to recovery (clockwork) - installtion complete without errors.
Edit: ok I have managed to install OS, but gapps are missing - and I cannot access recovery now, any ideas?
Click to expand...
Click to collapse
You should be able to boot into recovery after OS install, if not try everything again. Flash gapps zip right after flashing OS... http://opengapps.org/ (download for ARM, 4.4, nano)
---------- Post added at 08:49 PM ---------- Previous post was at 08:46 PM ----------
ifsz said:
Edit2: I have reinstalled recovery- now is working
Thank you very much for help!
Click to expand...
Click to collapse
Great, no problem. :good:

MobileTechArena said:
You should be able to boot into recovery after OS install, if not try everything again. Flash gapps zip right after flashing OS... http://opengapps.org/ (download for ARM, 4.4, nano)
---------- Post added at 08:49 PM ---------- Previous post was at 08:46 PM ----------
Great, no problem. :good:
Click to expand...
Click to collapse
I have sent you a proper thank you (paypal),