Hi all,
I have screwed up my phone through a series of stumbles into the altar of the gremlin gods. you can read all about it here: http://forum.xda-developers.com/showthread.php?t=2372990
I am looking for an image of the MF3 Stock Recovery I can push through ODIN.
Has such a thing been made?
I know it is a long shot but short of a jtag service to rewrite the bootloader , etc...
Thanks...
Salty...
SaltyFoam said:
Hi all,
I have screwed up my phone through a series of stumbles into the altar of the gremlin gods. you can read all about it here: http://forum.xda-developers.com/showthread.php?t=2372990
I am looking for an image of the MF3 Stock Recovery I can push through ODIN.
Has such a thing been made?
I know it is a long shot but short of a jtag service to rewrite the bootloader , etc...
Thanks...
Salty...
Click to expand...
Click to collapse
Too funny! I was reading your other thread, and I was about to write up a new thread for a request of the MF3 recovery! All we need is to find one of the "lucky" MF3-users here that retained root.
If you took the MF3 update and still have root, we need your help! In an ADB shell, please use "su" to gain root access (or using a terminal emulator on the phone - works just as well for this), and type the following command, very carefully:
Code:
dd if=/dev/block/mmcblk0p21 of=/sdcard/mf3-recovery.img
And then, please, upload it somewhere and give us a link! You can use Dev-Host for free without an account.
Thanks!
Aou said:
Too funny! I was reading your other thread, and I was about to write up a new thread for a request of the MF3 recovery! All we need is to find one of the "lucky" MF3-users here that retained root.
If you took the MF3 update and still have root, we need your help! In an ADB shell, please use "su" to gain root access (or using a terminal emulator on the phone - works just as well for this), and type the following command, very carefully:
Code:
dd if=/dev/block/mmcblk0p21 of=/sdcard/mf3-recovery.img
And then, please, upload it somewhere and give us a link! You can use Dev-Host for free without an account.
Thanks!
Click to expand...
Click to collapse
You have a PM.
I generated this, but do not have a way to upload to hosting from here (firewalls, etc).
joeybear23 said:
You have a PM.
I generated this, but do not have a way to upload to hosting from here (firewalls, etc).
Click to expand...
Click to collapse
Got the PM. I await email.
Thanks again! There's probably several people that can benefit from this -including those who tried to manually install a custom recovery.
Aou said:
Got the PM. I await email.
Thanks again! There's probably several people that can benefit from this -including those who tried to manually install a custom recovery.
Click to expand...
Click to collapse
It's on the way
also, it's 10MB in size...
joeybear23 said:
It's on the way
also, it's 10MB in size...
Click to expand...
Click to collapse
Sounds perfect - thanks!
Here's a link:
http://d-h.st/dcg
and another (mirror):
https://mega.co.nz/#!oN93XYrL!ONDIgxPwsNFM5Za1w0VKdxM1HdRj61zoAgcKGcybhBc
I'm working now to package it into an odin-flashable tarball...
---------- Post added at 05:38 PM ---------- Previous post was at 05:27 PM ----------
SaltyFoam said:
Hi all,
I have screwed up my phone through a series of stumbles into the altar of the gremlin gods. you can read all about it here: http://forum.xda-developers.com/showthread.php?t=2372990
I am looking for an image of the MF3 Stock Recovery I can push through ODIN.
Has such a thing been made?
I know it is a long shot but short of a jtag service to rewrite the bootloader , etc...
Thanks...
Salty...
Click to expand...
Click to collapse
Try this - should be Odin flashable, but it's also my first attempt at creating an odin-flashable tarball:
http://d-h.st/g6o
Can someone check my math, please?
Code:
mv mf3-recovery.img recovery.img
tar -H ustar -c recovery.img > mf3-recovery.tar
md5sum -t mf3-recovery.tar >> mf3-recovery.tar
mv mf3-recovery.tar mf3-recovery.tar.md5
Eh, looks like it was supposed to be recovery.bin (not a .img). Here's a new upload:
http://d-h.st/AuY
and here's the new math:
Code:
mv mf3-recovery.img recovery.bin
tar -H ustar -c recovery.bin > mf3-recovery.tar
md5sum -t mf3-recovery.tar >> mf3-recovery.tar
mv mf3-recovery.tar mf3-recovery.tar.md5
hmmm...
Aou said:
Sounds perfect - thanks!
Here's a link:
http://d-h.st/dcg
and another (mirror):
https://mega.co.nz/#!oN93XYrL!ONDIgxPwsNFM5Za1w0VKdxM1HdRj61zoAgcKGcybhBc
I'm working now to package it into an odin-flashable tarball...
---------- Post added at 05:38 PM ---------- Previous post was at 05:27 PM ----------
Try this - should be Odin flashable, but it's also my first attempt at creating an odin-flashable tarball:
http://d-h.st/g6o
Can someone check my math, please?
Code:
mv mf3-recovery.img recovery.img
tar -H ustar -c recovery.img > mf3-recovery.tar
md5sum -t mf3-recovery.tar >> mf3-recovery.tar
mv mf3-recovery.tar mf3-recovery.tar.md5
Click to expand...
Click to collapse
So my first effort:
<OSM> mf3-recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Ideas?
SaltyFoam said:
So my first effort:
<OSM> mf3-recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Ideas?
Click to expand...
Click to collapse
Might have been because I called it "recovery.img" when it was supposed to be "recovery.bin". give the new one a try, please.
Found it... look at previous post...
which new one?
Could I just extract, rename and then tar with 7zip? (I in windows...)
this is the current result...
<OSM> mf3-recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
The phone screen reads in very small almost impossible to read font
odin mode
product name SGH-I337
current binary: samsung official
system state: Custom
start [224, 1440]
then the green droid with the beginning bit of the progress bar...
SaltyFoam said:
this is the current result...
<OSM> mf3-recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Boo!
Any Dev's have ideas? I'm fresh out.
My guess: The file is not signed, and therefore rejected.
Second guess: I messed up somewhere...
Third guess: Something's wrong with the dump?
If it's being rejected because of signatures, you're doomed until Kies gets updated to MF3.
Much Gratitude...
Aou said:
Boo!
Any Dev's have ideas? I'm fresh out.
My guess: The file is not signed, and therefore rejected.
Second guess: I messed up somewhere...
Third guess: Something's wrong with the dump?
If it's being rejected because of signatures, you're doomed until Kies gets updated to MF3.
Click to expand...
Click to collapse
What ever the final result is at this point I want to say "Thanks!" to you and all the other experts behind the scenes.
I will keep plugging away in the mean time...
SaltyFoam said:
What ever the final result is at this point I want to say "Thanks!" to you and all the other experts behind the scenes.
I will keep plugging away in the mean time...
Click to expand...
Click to collapse
I fixed mine by dd - mdl recovery and replacing the recovery files that came with the update in the approrate folders and then ran the .sh file to update recovery to the correct one. if you need the files let me know.
also, if some one could post an odinable system.img I would be greatly happy. mine seems to be corrupt and wont dd back right.
confused...
spdwiz18 said:
I fixed mine by dd - mdl recovery and replacing the recovery files that came with the update in the approrate folders and then ran the .sh file to update recovery to the correct one. if you need the files let me know.
also, if some one could post an odinable system.img I would be greatly happy. mine seems to be corrupt and wont dd back right.
Click to expand...
Click to collapse
Good Morning...
I am not sure I understand.
Could you explain a little more simply? And yes, I would need the files; thanks.
By 'dd' do you mean download mode (odin mode)?
are you saying you used odin to push the mdl version of the stock recovery?
which .sh file?
confused...
Thanks.
SaltyFoam said:
Good Morning...
I am not sure I understand.
Could you explain a little more simply? And yes, I would need the files; thanks.
By 'dd' do you mean download mode (odin mode)?
are you saying you used odin to push the mdl version of the stock recovery?
which .sh file?
confused...
Thanks.
Click to expand...
Click to collapse
no problem.
First, when you ran odin did it fail?
this is how I did it:
I copied the mbl recovery.img to internal sdcard.
from command promt type:
adb su -c "dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
this should only take a second or two.
next: copy the recovery files that came with the update to the right folders using you fav file manager (I use root explorer)
install-recovery.sh goes into /syste/etc and reevocery-from-boot.p goes in /system
next: reboot
next using file manager go to /system/etc and long press on install-recovery.sh, should give you the option to execute, from there you should get a message about passing or failing.
files are attached
Is there an assumption that the os is working? In other words will adb cnnect when the phone is in odin mode??
Can't test because I am out... on a borrrowed phone...
Won't be home till 1030pm est... will try later.
Thanks!
Sent from my SPH-L710 using xda premium
SaltyFoam said:
Is there an assumption that the os is working? In other words will adb cnnect when the phone is in odin mode??
Can't test because I am out... on a borrrowed phone...
Won't be home till 1030pm est... will try later.
Thanks!
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
sorry, yes there is, and that you are rooted?
are you stuck in Dl mode, another words when you reboot it does straight to DL mode,
if so, pull batt, do 3 finger to DL mode ( vol-dwn, home, pwr) when it askes you to to continue, via vol-up or down, chose the one that cancels, it should reboot to system.
Yeah... that's the rub: instead of booting to the OS it goes to 'unath'd software'...
BUT: Two ideas... Maybe a bit way out but hear me out:
1) in theory, as it is not legal, could odin be modded to ignore the version check and force the downgrade?
2) and more complex but interesting:
The 'fuse' is an increment only counter.
It has binary bits that can turned on and off. if not the you can not get from '01 (base two) to '10' (base two) i.e. 1 -> 2...
Let's assume it is a 4 bit counter (although the actual width is not important for this abstraction.) the range is 0-15 (i.e. 0000 -> 1111)
What happens if you increments it 17 times (assuming you are starting at zero)?
Does it cause an overflow error (i.e. set a carry bit)?
Does it rollover back to '0000'?
If (it rolls over to zero)
could we increment the actual 'fuse' in the s4 enough times to roll it over (to '1') and then odin could downgrade the boot sequence?;
(unless it is a very wide register, 64 or 128 bits, which is a very long time especially since I am sure these eproms (?) are much slower than RAM)
Just a thought...
SaltyFoam said:
Yeah... that's the rub: instead of booting to the OS it goes to 'unath'd software'...
BUT: Two ideas... Maybe a bit way out but hear me out:
1) in theory, as it is not legal, could odin be modded to ignore the version check and force the downgrade?
2) and more complex but interesting:
The 'fuse' is an increment only counter.
It has binary bits that can turned on and off. if not the you can not get from '01 (base two) to '10' (base two) i.e. 1 -> 2...
Let's assume it is a 4 bit counter (although the actual width is not important for this abstraction.) the range is 0-15 (i.e. 0000 -> 1111)
What happens if you increments it 17 times (assuming you are starting at zero)?
Does it cause an overflow error (i.e. set a carry bit)?
Does it rollover back to '0000'?
If (it rolls over to zero)
could we increment the actual 'fuse' in the s4 enough times to roll it over (to '1') and then odin could downgrade the boot sequence?;
(unless it is a very wide register, 64 or 128 bits, which is a very long time especially since I am sure these eproms (?) are much slower than RAM)
Just a thought...
Click to expand...
Click to collapse
1) No, ODIN is simply responding to the phone's error "message." The ODIN version predates this phone, thus it knows nothing about the protection.
2) An interesting idea, but I'm not familiar with the mechanics of the fuse. I'd be really surprised if such an attack would work. And in doing so you'd risk a permanent brick!
Related
Hello,
I downloaded the latest firmware for P6800 "P6800XXLB4 3.2 P6800XEFLC1 France February 2012"
I made a flash with odin and now I have an error message
"Encountered year after firmware upgrade, please select kies in recovery mode and try again".
With odin I always "Failed" ...
how do I do now?
Best regard
Press and hold the Volume UP+Power button until a recovery mode screen appears, and do wipe data/factory reset
biopsin said:
Press and hold the Volume UP+Power button until a recovery mode screen appears, and do wipe data/factory reset
Click to expand...
Click to collapse
Thank you for your response!
But I can not, if I do this I get the firmware upgrade encountered an issue, please select recovery mode in kies and try again or volume down mode Odin that's all.
damien92220 said:
Thank you for your response!
But I can not, if I do this I get the firmware upgrade encountered an issue, please select recovery mode in kies and try again or volume down mode Odin that's all.
Click to expand...
Click to collapse
You shouldn't have to do a factory reset when flashing with odin. Odin wipes the whole drive and flashes from scratch-- it may not wipe the partition table or individual partitions, but it at least reformats each partition as if it were new. I'd recommend rolling back to your original firmware.
Sent from my GT-P6800 using XDA Premium HD app
Hello,
I can not put the original firmware with Odin that I tested 5 firmware.
<ID:0/019> Added!!
<ID:0/019> Removed!!
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6800XXLC3_P6800DRELB1_P6800XXLA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Get PIT for mapping..
<ID:0/019> Firmware update start..
<ID:0/019> boot.bin
<ID:0/019> NAND Write Start!!
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
damien92220 said:
Hello,
I can not put the original firmware with Odin that I tested 5 firmware.
<ID:0/019> Added!!
<ID:0/019> Removed!!
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6800XXLC3_P6800DRELB1_P6800XXLA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Get PIT for mapping..
<ID:0/019> Firmware update start..
<ID:0/019> boot.bin
<ID:0/019> NAND Write Start!!
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
ICS IS OUT!!! See if that helps!
Sent from my GT-P6800 using XDA Premium HD app
Same here...
Hello all,
I added a screen dump. First time I tried to flash with the update in the CSC option... I downloaded the file and the G6800 Odin package from Sammobile. Before to go to sleep quickly tried to upgrade but then I messed things up.
I tried various modes. Can someone help me?
Thanks!
Please try to read the instructions for Odin...
http://forum.xda-developers.com/showthread.php?t=1469635
I'll quote the relevant part for you because you missed it somehow:
xenix96 said:
PLEASE DO NOT PUT .PIT FILE AND DO NOT, I REPEAT, DO NOT TICK REPARTITION.
Click to expand...
Click to collapse
If it's already been written and it's not the right one you'll need to find a valid pit file for your model of Tab (P6800 or P6810) to fix it. You'll have to search for it though, I don't know where to find them.
solution
I have this problem yesterday, so I work out via google search.
After a while I discovered that I had used a wrong PIT file ... So the correct downloaded flashed and ready
See attachment for the right PIT
Thanks for the solution!
Co_OL 1977 said:
I have this problem yesterday, so I work out via google search.
After a while I discovered that I had used a wrong PIT file ... So the correct downloaded flashed and ready
See attachment for the right PIT
Click to expand...
Click to collapse
Could you please attach the required PIT file? It is not in your message! En bedankt voor de oplossing!!!
PIT File
Lol not uploaded
Settings
Co_OL 1977 said:
Lol not uploaded
Click to expand...
Click to collapse
Can you tell me exactly which settings were used in Odin? This was while flashing the new ICS software right?
(before I make another stupid choice...)
woevanda said:
Can you tell me exactly which settings were used in Odin? This was while flashing the new ICS software right?
(before I make another stupid choice...)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469635
It explains everything here, evwn how to flash a pit file, and which boxes to check and such.
same problem..help needed asap..thanks
Succeeded!
Co_OL 1977 said:
Lol not uploaded
Click to expand...
Click to collapse
My 7.7 is now running on Android 4.04. Thanks!!!
Man I hit the same issue. Got stuck in the kies recovery screen while upgrading to ICS.
Can someone please provide clear instructions getting out of that? Thank you so much!
Note: download mode and flashing through odin does not get me further than factorfs. =_=
CRAP. Now my battery died. Won't even charge or turn on.
krazykat said:
Man I hit the same issue. Got stuck in the kies recovery screen while upgrading to ICS.
Can someone please provide clear instructions getting out of that? Thank you so much!
Note: download mode and flashing through odin does not get me further than factorfs. =_=
CRAP. Now my battery died. Won't even charge or turn on.
Click to expand...
Click to collapse
See my post about the pit file :cyclops:
And you must have your tablet at least for 10 min on your charger before you can turn on or you can see he is charging
Quote from repair factory:
If your battery is completely discharged, the ten minutes before you see that your device is loaded.
Click to expand...
Click to collapse
Co_OL 1977 said:
See my post about the pit file :cyclops:
And you must have your tablet at least for 10 min on your charger before you can turn on or you can see he is charging
Quote from repair factory:
Click to expand...
Click to collapse
Yup I did thanks. Though - after flashing pit with re-partition, flashing ICS won't seem to go anywhere.
What firmware did u flash it with after pit?
krazykat said:
Yup I did thanks. Though - after flashing pit with re-partition, flashing ICS won't seem to go anywhere.
What firmware did u flash it with after pit?
Click to expand...
Click to collapse
i'm having the same problem with my tab 7.7, can someone guide us through this. I already followed the instructions from the guide of flashing rom but none of this work. TIA.
Thank you...
Co_OL 1977 said:
Lol not uploaded
Click to expand...
Click to collapse
I also experienced the error when doing the update to ICS recently and spent long hours trying to figure out and checking forums.
I tried the PIT file attached by "CL 1977" and it worked like a charm. :good:
Now running ICS 4.0.4. :fingers-crossed:
Hi!
I have big problem with my Xcover2
I have uploaded accidentally recovery from another model Galaxy S3 mini (i8190) from here: http://www.androidfilehost.com/?fid=9390334956548391158 after reboot i saw stock recovery, i reboot device. System start normally, but after this operation I was no longer able to enter recovery mode Only download mode works.
So I have uploaded the original ROM using ODIN3 v3.07, firmware i got from here: http://live.samsung-updates.com/index.php?device=GT-S7710 but i still can`t get in recovery mode using keys Vol-up + Home + Power, phone reboot after that keys So i can`t wipe data.
A few times I've used the ODIN and Kies trying to fix the phone. Flashing was done without any problems, there were no errors. But the phone reboot just after boot screen with the name of 'Samsung' and the phone model - bootloop :/
And then in the ODIN uploading another ROM again ticked the option "Nand Erase All" - after was done, there was no bootscreen at boot, on the display instead of startup screen was blank screen like this for 3sec
and after that was startup animation, system start normally I setup language, date etc, but then i discover that device memory was lost 0.00B
can`t receive SMS because there is no memory space :/
When the phone restarts then I have to set up all the settings again
When connecting the phone into the computer I see something like this:
Download mode works fine :
How can I fix the device memory ? (( Any suggestions, ideas? Every time I reboot device I can see blankscreen for ~3sec, and when phone boot I have to set up phone language and other settings again.
Sorry for my English
I am not an expert but i see you have wrong size on phone, reports as 30GB.
I think you need orginal image INCLUDING .pit file
But i have not been able to find online
hondavf1000f said:
I am not an expert but i see you have wrong size on phone, reports as 30GB.
Click to expand...
Click to collapse
This is size of my SD Card Phone memory is wrong size :/
Z3X Box support this phone, its expensive fixing toy but before i buy this i ask them if i can fix my phone using z3x box
I found PIT file on the support website http://z3x-team.com/support_files/ but for download i need connected card :/
jupii soon i get .PIT file for my S7710 so i have hope that fix my phone :fingers-crossed:
veimus said:
jupii soon i get .PIT file for my S7710 so i have hope that fix my phone :fingers-crossed:
Click to expand...
Click to collapse
:fingers-crossed:
Fixed flashing FULL SERVICE FIRMWARE from Z3X BOX support over 760MB with revovery, bootloader etc
Software publicly available from the Internet is trimmed from important files like recovery.img, parm.lfs etc :/
Code:
<OSM> Please wait..
<OSM> CODE_S7710XXAMB6_963581_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXE_S7710OXEAMB3_CL999465_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> STE_boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> STE_boot1.img
<ID:0/004> STE_boot2.img
<ID:0/004> ipl.bin
<ID:0/004> modem.bin
<ID:0/004> ssgtest.img
<ID:0/004> normal.bin
<ID:0/004> normal2.bin
<ID:0/004> param.lfs
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> userdata.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Odin setup:
auto reboot: yes
re-partition: yes
f. reset time: yes
phone bootloader update: yes
all other: uncheked
Oh and now i can get official update via OTA, Device Status: Official
hello! i have sam problem but i cant download any files from z3x box
Hello!
Have you Guys tried to check the Re-partion option in Odin und reflash a Original Samsung Rom or the rooted one from the boegl?
Thanks
Thanks Veimus
I had same problem, but rooting my phone, the links Z3X BOX from where you download it, still online, but i don't know if i can post it here, i will upload it, if anyone need it just ask!
Thanks a lot:good:
chatomas said:
Thanks Veimus
I had same problem, but rooting my phone, the links Z3X BOX from where you download it, still online, but i don't know if i can post it here, i will upload it, if anyone need it just ask!
Thanks a lot:good:
Click to expand...
Click to collapse
Hello
can u please post me somewhere param.lfs from s7710 (X cover 2 ) ?
thx
Same problem.
Hello! I have the same problem with you. If you want, can you give me the soft? I want to repair my phone (I have the same phone xCover 2).
Plz help me!
I have the same problem, can you show me all steps i need to do? I can't download files from z3x support and z3x samsung program doesn't works. Heeelp!
Me too
Story350 said:
I have the same problem, can you show me all steps i need to do? I can't download files from z3x support and z3x samsung program doesn't works. Heeelp!
Click to expand...
Click to collapse
After going through a bunch of stuff trying to fix my mobile data, I have ended up in this predicament.. I found a link to a full service the full service rom in another thread but the link was dead.
Does anyone have the rom and pit file? It would be very much appreciated.
Thank you
Fixed
Turns out I didn't need the full ROM after all. I was able to flash CWM and then mount and format /data. I'm not sure why this worked when a complete reset didn't but I'm thankful it did.
Full Service Rom
Hey Veimus you could be the Full Service Rome upload again?
Or someone else has a link?
I can think of the Z3X box as a student not afford
Recovery
Guys, I need ASAP torrent with S7710XXAMB6_OXEAMB3.zip I can't find it.
I want to restore my recovery but my wallet is too poor to buy z3box
I have the same problem: noone is willing to share? Thanx
Sent from my Xperia U using XDA Free mobile app
Thanx mate you resurrected my phone! Installed cwm formatted data et voila now I have my ram again!
Sent from my Xperia U using XDA Free mobile app
Hello. I need full service rom for s7710. Lost efs file, baseband xxxx, please. Thanks.
Same Problem
Hello guy, sorry for my not perfect english
I have the same problem with my galaxy, can i help me to find a Full service Rom complet of separately file : CNC, MODEM , PIT ,BOOTLOADER( I Have already the pit file). I have try to flash only PDA and PIT file but the problem is not solved!:crying: help me please.......
-question: but the bootloader in this chanche are Damaged???
I have searched and used as much google fu as I know how, so if I've missed the obvious I'm sorry.
Phone: Att Galaxy S4 SGH-I337
Running: I think stock 4.2.2 that was rooted.
Problem: currently will only get to the att logo then moves no further. Odin always fails to get me back to stock.
Cause of problem: Mostly likely me. I was attempting to unroot my phone using ODIN following a tutorial on galaxys4root.com.
Things I have tried: 6 different USB cords, 4 PCs 1 mac, Odin 3.07 and Odin 1.85, Several different sources for stock roms.
Notes: When I try to use the power button volume button method of booting to recovery it just goes to the odin download screen. This has been happening for a day or so that I've noticed.
Output from odin: <OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Output from phone: Odin Mode
Produc Name: SGH-I337
Current Binary: Samsung Offical
System Status: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
the output is pretty much the same regardless of odin computer or cable.
Any help would be greatly appreciated.
Thanks
#1. did you have usb debugging enabled before booting into download mode?
#2. do you know what firmware version was on the device when you got it (MDB, MDL, MF3)?
#3. booting into recovery is volume up + home + power. when your device vibrates, release just the power button. not sure if this is what you've been doing or if this will even benefit you right now.
Can you get into recovery? Were you stock beforehand or did you have a custom rom? If you can get into recovery do a factory reset. I'm guessing you got the mf3 update and that's why odin is not working.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
xBeerdroiDx
1. It was enabled the last time I was able to boot up.
2. Sadly no.
3. Tried a million on a thousand times. Every way which way i could think. The blue text pops up for a fraction of a second then it dumps off into odin mode.
jd1639
Can't get to recovery. Stock rooted. wasn't even aware i got the update. noobed it up.
Idk what else you can do. Try to see if kies will do an emergency restore. After that I'm out of ideas.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Try an older version of odin like 1.85 get into download mode then try to flash a custom recovery?
Sent from my SAMSUNG-SGH-I337 using xda premium
Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone
rugmankc said:
Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone
Click to expand...
Click to collapse
Immediately, promise, the text flash up for less than time that it would take to read it. just long enough for you to see something blue. I haven't been able to get it into recovery mode. Up until recently it wasn't a problem.
do you have adb access to phone to see if phone is recognized thru windows command terminal
Rabidbot, you got some serious fire power here helping you. I hope you're successful. Good luck to you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
rugmankc said:
do you have adb access to phone to see if phone is recognized thru windows command terminal
Click to expand...
Click to collapse
Working on trying to figure that out now.
UPDATE It isn't coming up in the list of attached devices.
ok, i don't know if phone can be recognized in your situation. It has to have had usb debugging enabled.
rugmankc said:
Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone
Click to expand...
Click to collapse
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?
xBeerdroiDx said:
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?
Click to expand...
Click to collapse
Agreed--
xBeerdroiDx said:
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?
Click to expand...
Click to collapse
Doesn't seem to be recognized.
rabidbot said:
SW REV. CHECK FAIL : fused : 2, Binary : 1
Click to expand...
Click to collapse
I believe you were on MF3 when it died.
Fused:2 means the qfuse was blown by the mf3 update
Binary:1 means the software you're attempting to flash matches a qfuse level 1 (mdl and lower)
I think it's either a samsung warranty replacement or wait for mf3 on kies.
Sent from my SAMSUNG-SGH-I337 using xda premium
Hi,
I would say google these terms to get a better idea of what you need to do to fix your phone:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I am pretty sure it sounds like you somehow flashed the new MF3 update and now it is not possible to Odin an AMDL image onto phone now due to blown Qfuse in the MF3 update. Here is example of what the above terms mean:
http://forum.xda-developers.com/showpost.php?p=43484436&postcount=370
Possible fix? (Not quite the same situation as you are in, but if you try to use Kies to restore your phone, I bet you will be in this same position maybe?)
http://forum.xda-developers.com/showthread.php?t=2360859
Sorry I couldn't provide a definite, quick fix, but I hope this helps point you in the right direction at least!
rabidbot said:
Working on trying to figure that out now.
UPDATE It isn't coming up in the list of attached devices.
Click to expand...
Click to collapse
ok based on other's comments, you may not have a quick solution. i missed the part about "fuse" -- sorry
did you have adb working before as in are your drivers installed. if no drivers, dl kies to get drivers. then uninstall it and try again
sounds like you are familiar with running adb commands?
Klown80 said:
Hi,
I would say google these terms to get a better idea of what you need to do to fix your phone:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I am pretty sure it sounds like you somehow flashed the new MF3 update and now it is not possible to Odin an AMDL image onto phone now due to blown Qfuse in the MF3 update. Here is example of what the above terms mean:
http://forum.xda-developers.com/showpost.php?p=43484436&postcount=370
Possible fix? (Not quite the same situation as you are in, but if you try to use Kies to restore your phone, I bet you will be in this same position maybe?)
http://forum.xda-developers.com/showthread.php?t=2360859
Sorry I couldn't provide a definite, quick fix, but I hope this helps point you in the right direction at least!
Click to expand...
Click to collapse
This is the output from odin. It was successful but my phone still doesn't boot past the att logo.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MF3_BTL_FIX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> rpm.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
rugmankc said:
ok based on other's comments, you may not have a quick solution. i missed the part about "fuse" -- sorry
did you have adb working before as in are your drivers installed. if no drivers, dl kies to get drivers. then uninstall it and try again
sounds like you are familiar with running adb commands?
Click to expand...
Click to collapse
I got the Drives are installed and have worked before. still nothing in the device list.
I tried to install the 4.4.2 N9005XXUENA6_N9005OXXENA5_N9005XXUENA2 update on my Note 3 via odin 3.09.
Got an ext4 update failed error.
After this, the phone's bricked and is stuck on the Kies Recovery Screen. I tried to go into recovery mode in Kies, but it says this model does not have initialization.
I tried installing a 4.3 N9005XXUDMK3_N9005TNLDMK1_N9005XXUDMK2, but again failed. Download mode shows SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Can someone please guide me to unbrick my phone?
I don't know what ROM I was on initially. It was the stock ROM that came with the phone.
I dont have CWM and TWRM installed.
This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.
MrAndroid12 said:
This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.
Click to expand...
Click to collapse
Thank you for that advice. How do I add a .pit file, and would you happen to have a link where I can download it from?
rinuvimal said:
Thank you for that advice. How do I add a .pit file, and would you happen to have a link where I can download it from?
Click to expand...
Click to collapse
search better mate http://forum.xda-developers.com/showthread.php?t=2550823
tasked28m said:
search better mate http://forum.xda-developers.com/showthread.php?t=2550823
Click to expand...
Click to collapse
I've tried all the .pit files in that thread, bro. None work. Cannot generate own pit as in phone is in recovery mode.
rinuvimal said:
I've tried all the .pit files in that thread, bro. None work. Cannot generate own pit as in phone is in recovery mode.
Click to expand...
Click to collapse
i know cfautoroot has the correct pit file in , try rooting your phone with cfautoroot.
MrAndroid12 said:
This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.
Click to expand...
Click to collapse
I tried a variety of N9005 .pits and each time, it shows PIT FAIL: TOTAL SECTORS (30777344) :crying:
(Read OP) . Try flashing the polish firmware again with odin v1.85 and try using different usb ports. Close most of your running applications such as firefox skype etc that can interrupt the process and flash official firmware.
tasked28m said:
(Read OP) . Try flashing the polish firmware again with odin v1.85 and try using different usb ports. Close most of your running applications such as firefox skype etc that can interrupt the process and flash official firmware.
Click to expand...
Click to collapse
Whenever I try the 4.4.2 polish, it fails at system.img.ext4. When I try 4.3, it fails at aboot.
Here's the Odin log for 4.4.2 polish:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.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> aboot.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
bootloop note 3
After installig android 4.4.2, i tried to root with cf-root, now it is in a loop.
I cannot come into in recovery mode.
The phone starts with: -recovery booting,-recovery is not seandroid enforcing,- set warrant bit recovery
when i keep the battery out and then put it in, it says again -recovery booting,-recovery is not seandroid etc.
Who can help me????
rinuvimal said:
Whenever I try the 4.4.2 polish, it fails at system.img.ext4. When I try 4.3, it fails at aboot.
Here's the Odin log for 4.4.2 polish:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.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> aboot.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You won't be able to downgrade back to 4.3 - Use the PDA slot on ODIN and try flashing again.
poedy said:
After installig android 4.4.2, i tried to root with cf-root, now it is in a loop.
I cannot come into in recovery mode.
The phone starts with: -recovery booting,-recovery is not seandroid enforcing,- set warrant bit recovery
when i keep the battery out and then put it in, it says again -recovery booting,-recovery is not seandroid etc.
Who can help me????
Click to expand...
Click to collapse
I answered in your other thread about this...
rinuvimal said:
I tried to install the 4.4.2 N9005XXUENA6_N9005OXXENA5_N9005XXUENA2 update on my Note 3 via odin 3.09.
Got an ext4 update failed error.
After this, the phone's bricked and is stuck on the Kies Recovery Screen. I tried to go into recovery mode in Kies, but it says this model does not have initialization.
I tried installing a 4.3 N9005XXUDMK3_N9005TNLDMK1_N9005XXUDMK2, but again failed. Download mode shows SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Can someone please guide me to unbrick my phone?
I don't know what ROM I was on initially. It was the stock ROM that came with the phone.
I dont have CWM and TWRM installed.
Click to expand...
Click to collapse
try to downlaod and flash the 4.4.2 tar again, you cant downgrade to 4.3 as your bootlaoder got upgraded
Edit- darn am i too slow or are you too fast today @radicalisto? second time...LOL :good:
Khizar said:
try to downlaod and flash the 4.4.2 tar again, you cant downgrade to 4.3 as your bootlaoder got upgraded
Edit- darn am i too slow or are you too fast today @radicalisto? second time...LOL :good:
Click to expand...
Click to collapse
15 hour sleep man, seems to have me buzzing around lol :highfive:
Solution
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:
m1ndst0rm said:
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:
Click to expand...
Click to collapse
Have you tried rooting it with Chainfire's CF-Auto Root yet?
m1ndst0rm said:
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:
Click to expand...
Click to collapse
can you show the download link for the leaked rom with 4 files?
vndnguyen said:
can you show the download link for the leaked rom with 4 files?
Click to expand...
Click to collapse
I have no permission to post links yet, but try googling for N3KitKat.rar.torrent
Leaked download link is in my sig (not this cause I am on xda app l check my other posts)
Sent from my SM-N9005 using XDA Premium 4 mobile app
ManUtdRul3 said:
Have you tried rooting it with Chainfire's CF-Auto Root yet?
Click to expand...
Click to collapse
Just tried latest one, ended up in bootloop with "KERNEL IS NOT SEANDROID ENFORCING"...
Now flashing original ROM again.
m1ndst0rm said:
Just tried latest one, ended up in bootloop with "KERNEL IS NOT SEANDROID ENFORCING"...
Now flashing original ROM again.
Click to expand...
Click to collapse
Seems to be a common problem. Hopefully an update to it will fix it.
Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.
kstehling said:
Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.
Click to expand...
Click to collapse
I would first attempt to flash TWRP and see if it boots.
ashyx said:
I would first attempt to flash TWRP and see if it boots.
Click to expand...
Click to collapse
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.
kstehling said:
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.
Click to expand...
Click to collapse
Where do you find the image, it should also be available in tar format?
kstehling said:
Sorry, I'm a little star struck that you responded to my post. I wanted to use the first TWRP i had installed, but it is a .img and I'm not sure how to use that without being able to access recovery mode. I am a baby when it comes to this stuff. I apologize for my lack of skills in this department. You guys that do this stuff for a living/hobby must have super human abilities. I've only been at this for several days and I'm already pulling my hair out.
Click to expand...
Click to collapse
The Odin version of TWRP can be found here https://dl.twrp.me/gtaxlwifi/ When you flash it with Odin, be sure to go into options and uncheck "auto reboot". When it finishes, press and hold Home, Vol down and Power buttons till the screen goes black. Quickly shift from Vol down to Vol up buttons till the first screen appears. Keep holding Home and Vol up but release the power button. When the screen blanks you can release all the buttons and you should then be in the TWRP menu.
---------- Post added at 03:36 PM ---------- Previous post was at 03:29 PM ----------
kstehling said:
Hi everyone!
I hope I'm asking this in the right place. I think I may have really messed up my tablet. My apologies, this is going to be a long one.
After following some very bad advice I was using my SM-T580 8.1 (rooted with TWRP, Magisk and Manager) to explore Xposed. I now know Xposed + Samsung = bootloops. While trying to restore my poor little tablet I messed something up big time. When I tried to boot into recovery....it didn't work. So I booted into download mode and tried to flash stock firmware downloaded from Sammobile. While flashing with Odin 3.13.1, the connection was broken, my dog decided that it as the perfect moment for playtime. Now I can only boot into Odin mode and nothing else. To let it boot normally I get a bootloop with the Samsung Logo and the red warning "Could not boot into normal mode. Invalid Kernal length." Every time I try to flash the firmware I get "re-partition failed" error. I've tried two different PCs, 7 different USB cords, every USB port I have and stock firmware from 6.0 to 8.1. I've tried with and without the PIT file and tried checking/unchecking the repartition box in Odin's options. If I leave the repartition box empty is hangs on "setting up connection" and never moves past that. In the past week, I'm not sure how, I did get to the recovery menu. I cleared the cache and did a factory reset. It still went into the loop, so I tried recovery mode again and was able to look at the logs. I don't know why I looked because I really dont have any idea what they say. The only thing I did understand was that one of them said there was no recovery file. I assume this is a VERY bad thing. Since then I cant get back to it. Oh, depending on which USB port I plug into... sometimes the FRP is ON, with another port it is OFF. Don't know if that would help with a diagnosis. Sorry again for the long post, but I've tried to include as much information as possible. At this point is there any hope of fixing it?
Thank you in advance and a huge thanks for being my "go-to" since my SM-T530nu.
Click to expand...
Click to collapse
Are you using Home, Vol up and Power buttons to get to recovery? If that works, you can try Factory Reset from that menu. That should wipe the partitions so you can then go to download mode and flash with Odin. If not, then you'll have to try installing TWRP.
edit: If you can't get out of download mode, try the trick of Home, Vol down and Power till the screen blanks and quickly switching from Vol down to Vol up.
lewmur said:
The Odin version of TWRP can be found here... When you flash it with Odin, be sure to go into options and uncheck "auto reboot". When it finishes, press and hold Home, Vol down and Power buttons till the screen goes black. Quickly shift from Vol down to Vol up buttons till the first screen appears. Keep holding Home and Vol up but release the power button. When the screen blanks you can release all the buttons and you should then be in the TWRP menu.
---------- Post added at 03:36 PM ---------- Previous post was at 03:29 PM ----------
Are you using Home, Vol up and Power buttons to get to recovery? If that works, you can try Factory Reset from that menu. That should wipe the partitions so you can then go to download mode and flash with Odin. If not, then you'll have to try installing TWRP.
edit: If you can't get out of download mode, try the trick of Home, Vol down and Power till the screen blanks and quickly switching from Vol down to Vol up.
Click to expand...
Click to collapse
I have tried the Vol up + home + power to get to recovery without success. It happened once, days ago and I wiped the cache and tried a factory reset. It didnt work. I still get the bootloop with the Samsung logo and the Invalid Kernel length error at the top in red letters.
This afternoon I was able to download 3 different TWRP files for my device and tried to flash them. This time Odin stalled...
<OSM> Enter CS for MD5..
<OSM> Checking MD5.. Do not unplug the cable..
<OSM> Please wait..
and it never moves any further.
kstehling said:
I have tried the Vol up + home + power to get to recovery without success. It happened once, days ago and I wiped the cache and tried a factory reset. It didnt work. I still get the bootloop with the Samsung logo and the Invalid Kernel length error at the top in red letters.
This afternoon I was able to download 3 different TWRP files for my device and tried to flash them. This time Odin stalled...
<OSM> Enter CS for MD5..
<OSM> Checking MD5.. Do not unplug the cable..
<OSM> Please wait..
and it never moves any further.
Click to expand...
Click to collapse
Which version of Odin are you using? Also can you actually post screen shots of both odin after the failure and download mode on your device?
ashyx said:
Which version of Odin are you using? Also can you actually post screen shots of both odin after the failure and download mode on your device?
Click to expand...
Click to collapse
Odin 3.13.1
I'm not sure how to include a picture. I have several.
On the Odin/Download screen is says:
Odin Mode
Download Speed: Fast
Product Name: SM-T580
Current Binary: Samsung Official
System Status: Custom
FRP Lock: ON (or off depending on the day)
Secure Download: Enabled
Warranty Void: 1 (0x030c)
the last numbers are B:4 K:1 S:2
This is the log from my most recent attempt. First without the PIT file and then with it included. Don't know if it was the right thing to try, but at this point, why not
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
kstehling said:
This is the log from my most recent attempt. First without the PIT file and then with it included. Don't know if it was the right thing to try, but at this point, why not
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 21 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
I would suggest downloading the combination firmware and see if that can be flashed.
Also where did you obtain the PIT file and are you choosing repartition with the the PIT file loaded?
ashyx said:
I would suggest downloading the combination firmware and see if that can be flashed.
Also where did you obtain the PIT file and are you choosing repartition with the the PIT file loaded?
Click to expand...
Click to collapse
If the combination firmware is the BL, AP, CSC and Home CSC, it did not work. The only file I haven't tried to flash is the Home CSC because there aren't settings I was trying to keep. I got PIT file two ways. One was a download I found and another was by extracting it from the CSC file. I tried to compare them to the best of my ability and it seemed like they matched. I tried flashing with and without the repartition option. The only thing I haven't selected in the options is NAND erase.
I've tried
XAR-T580UEU1APF5
XAR-T580UEU4CRK5
XAR_T580XAR4CSC1
And GTAXLWIFI_EUR_OPEN.pit with all 3.
kstehling said:
If the combination firmware is the BL, AP, CSC and Home CSC, it did not work. The only file I haven't tried to flash is the Home CSC because there aren't settings I was trying to keep. I got PIT file two ways. One was a download I found and another was by extracting it from the CSC file. I tried to compare them to the best of my ability and it seemed like they matched. I tried flashing with and without the repartition option. The only thing I haven't selected in the options is NAND erase.
I've tried
XAR-T580UEU1APF5
XAR-T580UEU4CRK5
XAR_T580XAR4CSC1
And GTAXLWIFI_EUR_OPEN.pit with all 3.
Click to expand...
Click to collapse
Where did you obtain the combination firmware?
https://drive.google.com/file/d/1sSIFiAeBBL5EMKNyxE31aUfsH9CefnfI
ashyx said:
Where did you obtain the combination firmware?
https://drive.google.com/file/d/1sSIFiAeBBL5EMKNyxE31aUfsH9CefnfI
Click to expand...
Click to collapse
SamMobile and Samfew
kstehling said:
SamMobile and Samfew
Click to expand...
Click to collapse
I doubt that is the combination firmware.
Use the one I posted.
ashyx said:
I doubt that is the combination firmware.
Use the one I posted.
Click to expand...
Click to collapse
<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.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection.. it got stuck here for more than 20 minutes.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
The first attempt was without the PIT, second try was with the PIT file as well as the repartition option checked. It did seem to take longer this time before it failed. I thought we were going to get lucky for a second.
kstehling said:
<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.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1016 M
<ID:0/005> SetupConnection.. it got stuck here for more than 20 minutes.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
The first attempt was without the PIT, second try was with the PIT file as well as the repartition option checked. It did seem to take longer this time before it failed. I thought we were going to get lucky for a second.
Click to expand...
Click to collapse
I suppose its worth now trying with nand erase.
ashyx said:
I suppose its worth now trying with nand erase.
Click to expand...
Click to collapse
Ok. I'll try it now. Should I use the PIT file? Or any of the others? BL, CSC? And just to be sure the file you gave me the link to should be in the AP spot, right?
I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.
kstehling said:
I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.
Click to expand...
Click to collapse
So you are able to flash the bootloader files?
Have you tried just AP?
kstehling said:
I found how I could attach pictures for you. There is one that shows Odin with the "Pass" 1 successful/0 Failed. That happened in the middle of all of this by chance. I don't know if that helps any (I doubt it). The same problem was happening before it and after.
Click to expand...
Click to collapse
I don't recognize the file you are using. The latest T580 stock ROM can be found here: https://www.sammobile.com/samsung/galaxy-tab-a-2016-101-wi-fi/firmware/SM-T580/
For the U.S. it is the one for Cellular South. It is a zip file that needs to be extracted. You only want to flash two of the four. The one starting with AP and the one starting with BP.
The Odin screen should look like the attached image before you click start. Don't change any of the default options.