Related
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Background
AS of March 27, 2015, the most recent firmware for Note Pro 12.2 international version is the Russian P905XXUAOB1 (with CSC905SERAOB1 and Modem905XXUANA7), Since it doesn't seem that any country is in a hurry to push a lollipop update into this device, I made these files to update the tablet to the latest available firmware. The procedure is designed to achieve two thing: 1- by leaving the bootloader untouched, it is reversible to your current version, if you have the firmware corresponding to your current version at your disposal, 2- it gives you root.
This procedure should not in theory wipe your data but DO MAKE A BACKUP, in case.
And no, it doesn't trip the knox.
Upgrade Procedure
All files that you need are available at the link further down. The are zipped but you should unzip them before using them.
1- Backup everything you have on your tablet
2- Reboot the tablet to the "Download Mode" (by pressing down vol + home key when the device is rebooting, right before you see the first splash logo, then push Up Vol to continue).
3- Run PC Odin v3.09 and load these files (remember to unzip the files after downloading) :
BL: leave empty
AP: AP.tar.md5
CP: CP.tar.md5
CSC: CSC.tar.md5
Leave everything else unchanged and Start.
4- Let the tablet reboot. It will first go to recovery to complete the upgrade and then reboots and initializes your apps.
Note 1: This process should not erase your data but I suggest you do a factory reset yourself (provided you have saved you data somewhere)
Note 2: After the upgrade is complete, the tablet may run slow and get hot for about 20 min because all the apps are trying to get set up and catalog your system. However, if after 30 minutes is is still slow and hot, first try to wipe the data for Google Plus App. If that doesn't work you may want to disable Google Plus, or as a last resort do a factory reset.
Note 3: If you end up doing a factory reset, the tablet will start up in Russian. You can change the language to English at the very first step of the initial set up. After that, go to settings and change the keyboard and input language to English. Then everything will be OK.
Note 4: If you try this out and don't like it, download your old firmware (must match or be newer than what you had before) and flash your tablet back to how it was (you have to do a factory reset after the downgrading).
Root Procedure
If you need to root the tablet, do the following after you finish the upgrade procedure:
1- Install towelroot v3 on your tablet, but don't run it. The app is inside a zip file at the download site and you should unzip it with the password 12345
This is done because some systems flag this app as a virus when it clearly is not. There are two versions there in the zip file. Either one should work just fine.
2- Install SuperSU, but don't run it.
3- Reboot to download mode.
4- Run PC Odin and load ANC3_Kernel.tar.md5 in AP field and start.
5- Let the system reboot. You may get some force closings after the reboot but ignore them.
6- Run the towelroot app and make it rain!
7- Reboot to download mode.
8- Run PC Odin and load AOB1_Kernel.tar.md5 in AP field and start.
9- Let the system reboot.
10- Run the SuperSU app and let it update the binaries the "normal" way.
11- Allow it to disable knox for you.
12- If SuperSU freezes up for more than 5 minutes reboot your tablet and run it again. Everything will be fine.
13- Your tablet is rooted now.
Download Link
https://mega.co.nz/#F!491wSaQa!wxjErs3ZamrmEPKjYVi50A
Hi
My p905 is on p905xxuanh3. Is it ok to use your method? Tnx
vvkuz said:
Hi
My p905 is on p905xxuanh3. Is it ok to use your method? Tnx
Click to expand...
Click to collapse
Yes. Make sure a matching nh3 firmware is available from sammobile.com if you think you may want to go back to your existing rom at some point.
successfully updated & rooted a p905 with your instructions,
thanks for your help.
Any idea if I can flash this rom into a P905M? Thanks in advance
andrew.mackew said:
Any idea if I can flash this rom into a P905M? Thanks in advance
Click to expand...
Click to collapse
No, because 905M has different cellular and LTE bands and the modem is different. If you still feel adventurous and want to try it, exclude the CP tar file when you are flashing. Make sure you have your current firmware available to restore in case you soft-brick your tablet.
najoor said:
No, because 905M has different cellular and LTE bands and the modem is different. If you still feel adventurous and want to try it, exclude the CP tar file when you are flashing. Make sure you have your current firmware available to restore in case you soft-brick your tablet.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I really wish to change, I mean, since Samsung stuck us on 4.2.2 so far.. I just wish, at least to get a minimal improvement.
If I get to merge things to have a P905 rom working on my P905M it would be an achievement in direction to break the P905M rom prison.
It worked!
Now I have the latest firmware into my P905M.
Thanks!
najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Background
AS of March 27, 2015, the most recent firmware for Note Pro 12.2 international version is the Russian P905XXUAOB1 (with CSC905SERAOB1 and Modem905XXUANA7), Since it doesn't seem that any country is in a hurry to push a lollipop update into this device, I made these files to update the tablet to the latest available firmware. The procedure is designed to achieve two thing: 1- by leaving the bootloader untouched, it is reversible to your current version, if you have the firmware corresponding to your current version at your disposal, 2- it gives you root.
This procedure should not in theory wipe your data but DO MAKE A BACKUP, in case.
And no, it doesn't trip the knox.
Upgrade Procedure
All files that you need are available at the link further down. The are zipped but you should unzip them before using them.
1- Backup everything you have on your tablet
2- Reboot the tablet to the "Download Mode" (by pressing down vol + home key when the device is rebooting, right before you see the first splash logo, then push Up Vol to continue).
3- Run PC Odin v3.09 and load these files (remember to unzip the files after downloading) :
BL: leave empty
AP: AP.tar.md5
CP: CP.tar.md5
CSC: CSC.tar.md5
Leave everything else unchanged and Start.
4- Let the tablet reboot. It will first go to recovery to complete the upgrade and then reboots and initializes your apps.
Note 1: This process should not erase your data but I suggest you do a factory reset yourself (provided you have saved you data somewhere)
Note 2: After the upgrade is complete, the tablet may run slow and get hot for about 20 min because all the apps are trying to get set up and catalog your system. However, if after 30 minutes is is still slow and hot, first try to wipe the data for Google Plus App. If that doesn't work you may want to disable Google Plus, or as a last resort do a factory reset.
Note 3: If you end up doing a factory reset, the tablet will start up in Russian. You can change the language to English at the very first step of the initial set up. After that, go to settings and change the keyboard and input language to English. Then everything will be OK.
Note 4: If you try this out and don't like it, download your old firmware (must match or be newer than what you had before) and flash your tablet back to how it was (you have to do a factory reset after the downgrading).
Root Procedure
If you need to root the tablet, do the following after you finish the upgrade procedure:
1- Install towelroot v3 on your tablet, but don't run it. The app is inside a zip file at the download site and you should unzip it with the password 12345
This is done because some systems flag this app as a virus when it clearly is not. There are two versions there in the zip file. Either one should work just fine.
2- Install SuperSU, but don't run it.
3- Reboot to download mode.
4- Run PC Odin and load ANC3_Kernel.tar.md5 in AP field and start.
5- Let the system reboot. You may get some force closings after the reboot but ignore them.
6- Run the towelroot app and make it rain!
7- Reboot to download mode.
8- Run PC Odin and load AOB1_Kernel.tar.md5 in AP field and start.
9- Let the system reboot.
10- Run the SuperSU app and let it update the binaries the "normal" way.
11- Allow it to disable knox for you.
12- If SuperSU freezes up for more than 5 minutes reboot your tablet and run it again. Everything will be fine.
13- Your tablet is rooted now.
Download Link
https://mega.co.nz/#F!491wSaQa!wxjErs3ZamrmEPKjYVi50A
Click to expand...
Click to collapse
Hey mate,
Can you make the same with the latest Lollipop for P905? I wish to flash them into my P905M.. Thanks
andrew.mackew said:
Hey mate,
Can you make the same with the latest Lollipop for P905? I wish to flash them into my P905M.. Thanks
Click to expand...
Click to collapse
Hello from Sao Paulo. Please let us know if you have succeed in installing the italian lollipop on your p905M.
js345 said:
Hello from Sao Paulo. Please let us know if you have succeed in installing the italian lollipop on your p905M.
Click to expand...
Click to collapse
Yep I did. But lost signal.. I am testing a few things..
---------- Post added at 01:13 PM ---------- Previous post was at 01:02 PM ----------
Anyone knows if I can flash a P905 modem into a P905M device?
thanks! successful!:good:
Thank you so much! I've been worried about rooting without tripping knox and this worked perfectly.
One question... If I didn't want to upgrade, could I have just flashed the two firm ware to root?
One of the clearest rooting guides I've used.
Thanks,
Zabben W
zabbenw said:
Thank you so much! I've been worried about rooting without tripping knox and this worked perfectly.
One question... If I didn't want to upgrade, could I have just flashed the two firm ware to root?
One of the clearest rooting guides I've used.
Thanks,
Zabben W
Click to expand...
Click to collapse
No because the second firmware in step 8 should match the existing kernel on your device.
najoor said:
No because the second firmware in step 8 should match the existing kernel on your device.
Click to expand...
Click to collapse
Oh right. That makes sense. Great root guide. If I think about upgrading, I will definitely take a peek at your lollypop one.
Upgrade to P905XXSABQC1_P905BTUABOF1_BTU for SM-P905
Hi All,
Need your help, Tried to upgrade my SM-P905 using ODIN V3.13, using the file downloaded P905XXSABQC1_P905BTUABOF1_BTU. connecting ODIN via USB Cable to the tab. Tried all USB Ports, same issue.
but ODIN unable to move forward with error:
<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/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2365 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> boot.img
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Please help.
After, and if, aboot and boot are flashed, the rest should get flashed with no issues.
99% of the time this kind failure is either due to a bad USB cable or unnecessary physical movement of the device (which affects the connection) during the flashing process.
So my suggestion is:
1- Make sure you have the latest Samsung drivers installed.
2- Find the best quality cable you have and use that.
3- If the problem persists download another firmware (maybe from another region) and try flashing that.
Hope this helps.
felix_sashi said:
Hi All,
Need your help, Tried to upgrade my SM-P905 using ODIN V3.13, using the file downloaded P905XXSABQC1_P905BTUABOF1_BTU. connecting ODIN via USB Cable to the tab. Tried all USB Ports, same issue.
but ODIN unable to move forward with error:
<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/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2365 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> boot.img
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Please help.
Click to expand...
Click to collapse
I've flashed the most recent versions of both CWM and TWRP, but it boots into android stock recovery every time.
I tried using the hardware buttons. I tried booting into recovery from ROM manager, first setting up the correct recovery in settings
I also tried the fast boot options, but I can't locate my device through the "fastboot devices" command, even when run in administrator mode.
There's an option described elsewhere, for other devices, which involves unchecking reboot when flashing the recovery in Odin, and then temporarily dislodging the battery, but the 530 has a closed back cover so I can't do that either.
I'm really stuck here, and any help would be appreciated
BTW running 4.4.2
MadBigMadBoatMan said:
I've flashed the most recent versions of both CWM and TWRP, but it boots into android stock recovery every time.
I tried using the hardware buttons. I tried booting into recovery from ROM manager, first setting up the correct recovery in settings
I also tried the fast boot options, but I can't locate my device through the "fastboot devices" command, even when run in administrator mode.
There's an option described elsewhere, for other devices, which involves unchecking reboot when flashing the recovery in Odin, and then temporarily dislodging the battery, but the 530 has a closed back cover so I can't do that either.
I'm really stuck here, and any help would be appreciated
BTW running 4.4.2
Click to expand...
Click to collapse
If you flash custom recovery via Odin and have this situation you need untick restart checkbox in Odin . And then handly reboot to recovery .
There are no fastboot mode in our tab .
repey6 said:
If you flash custom recovery via Odin and have this situation you need untick restart checkbox in Odin . And then handly reboot to recovery .
There are no fastboot mode in our tab .
Click to expand...
Click to collapse
Hello, and thank you for responding.
I run ODIN 3.09, and I must assume by "restart" you mean the "Auto reboot" box? If so, I've tried with that box unchecked, and then booting into recovery with the buttons, but it still brings me to stock recovery. And I can't flash any ROMs from that one obviously.
Tried again now after a wipe/factory reset, still goes to stock.
I must admit this particular challenge is proving a but frustrating. Usually I get somewhere, anywhere...
MadBigMadBoatMan said:
Hello, and thank you for responding.
I run ODIN 3.09, and I must assume by "restart" you mean the "Auto reboot" box? If so, I've tried with that box unchecked, and then booting into recovery with the buttons, but it still brings me to stock recovery. And I can't flash any ROMs from that one obviously.
Tried again now after a wipe/factory reset, still goes to stock.
I must admit this particular challenge is proving a but frustrating. Usually I get somewhere, anywhere...
Click to expand...
Click to collapse
Do you have root ?
repey6 said:
Do you have root ?
Click to expand...
Click to collapse
Yes, root is fine
Add this to methods tried: Wiping cache+wipe user dats+factory reset - download mode without booting to stock rom, flashing recovery with reboot disabled, straight to recovery.....
Still stock recovery
I looked into safestrapping, but it seems that's just for locked bootloaders
And by the way, I tried boot to bootloader from quickboot, got me to download mode... so maybe it is locked? Wasn't listed under devices
And, I reboot to recovery with power+home+volume up
Is there any other way to reboot this device to recovery?
MadBigMadBoatMan said:
Yes, root is fine
Add this to methods tried: Wiping cache+wipe user dats+factory reset - download mode without booting to stock rom, flashing recovery with reboot disabled, straight to recovery.....
Still stock recovery
I looked into safestrapping, but it seems that's just for locked bootloaders
And by the way, I tried boot to bootloader from quickboot, got me to download mode... so maybe it is locked? Wasn't listed under devices
And, I reboot to recovery with power+home+volume up
Is there any other way to reboot this device to recovery?
Click to expand...
Click to collapse
Sorry i was busy .
That correct understand i have some questions , sorry .
Settings-general-about device name of your device ? Your firmware ?
Can you give me copy Odin log of flashing recovery ?
repey6 said:
Sorry i was busy .
That correct understand i have some questions , sorry .
Settings-general-about device name of your device ? Your firmware ?
Can you give me copy Odin log of flashing recovery ?
Click to expand...
Click to collapse
Device name
T530 (i just set it up after factory reset, so this is my input I think)
Model number
SM-T530
Android Version
4.4.2
Kernel Version
3.4.0-1090229
Build number
KOT49H.T530XXU1ANH7
ODIN Gives me this:
<ID:0/010> 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/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
MadBigMadBoatMan said:
Device name
T530 (i just set it up after factory reset, so this is my input I think)
Model number
SM-T530
Android Version
4.4.2
Kernel Version
3.4.0-1090229
Build number
KOT49H.T530XXU1ANH7
ODIN Gives me this:
<ID:0/010> 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/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
Click to expand...
Click to collapse
OK . Thanks . I propose to get root at first by CF-Root/CF-Auto-Root . Link https://download.chainfire.eu/441/C...uto-Root-matissewifi-matissewifizs-smt530.zip . Unpack and flash via Odin . Dont unchecked checkboxes . When you will have root you can to use different method that to install custom recovery ( i recomend last TWRP by @sub77 http://android.comtek-wiebe.de/index.php?folder=T3BlblJlY292ZXJ5 )
repey6 said:
OK . Thanks . I propose to get root at first by CF-Root/CF-Auto-Root . Link https://download.chainfire.eu/441/C...uto-Root-matissewifi-matissewifizs-smt530.zip . Unpack and flash via Odin . Dont unchecked checkboxes . When you will have root you can to use different method that to install custom recovery ( i recomend last TWRP by @sub77 http://android.comtek-wiebe.de/index.php?folder=T3BlblJlY292ZXJ5 )
Click to expand...
Click to collapse
Wiped cache, factory reset, and rooted using autoroot from your link, then flashed the revovery image.
Still not able to access custom recovery, only stock.
Then I installed Rashr, and was able to reboot to TWRP from there, so my problem is solved
Thanks a lot for taking the time to help out!
Here's the Play Stor link for Rashr:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools&hl=en
It is okay to downgrade?
Does anyone knows if something could go wrong if I downgrade from lollipop to kit kat?
I'm trying to downgrade to kitkat but doesn't work for sm-g530h :'( :'( :'(
Go here and make sure your flashing the correct firmware for your varient >> http://samsung-firmware.org/model/SM-G530H/
Note: the country code is very important also for correct firmware.
Also: maybe some varients cannot be reverted because of write protected files that once on a newer version, the older cannot over write a later version..I'm new to Samsung, but some Moto devices are this way..maybe research this..
---------- Post added at 07:49 AM ---------- Previous post was at 07:38 AM ----------
mohamedbk said:
I'm trying to downgrade to kitkat but doesn't work for sm-g530h :'( :'( :'(
Click to expand...
Click to collapse
Is Odin3 failing to flash (or) is the device bootlooping..or both.?
Have you tried a "system erase" via recovery, starting anew, clean OS before flashing.?
sent by my: SM-G531M-88 Grand Prime (or)
my: SM-N910C Note 4 (Lollipop 5.1.1)
I just did it today...
... and if you're careful with the baseband model #, and country code, you should be fine. Here's how I did it:
1- go to Sammobile and search for SM-G530H under the firmwares page, and download the firmware for your country region, and watch the PDA and CSC codes, you need to download the ones for your baseband model;
2- Once the firmware is downloaded, make sure you have Odin and Samsung drivers installed in your PC;
3- Open Odin, load the firmware under AP/PDA option. Start your phone in download mode, plug it and once it's recognized, start the flashing procedure;
4- The phone will start, and once the Samsung bootloop screen shows, it will hang/freeze in that screen. That's because Lollipop is still the main system, and Kitkat is trying to update "in" it. So, open your phone and take the battery out, this will turn it off;
5- Place the battery back in, and restart the phone in recovery mode. Wipe cache partition, then wipe the system to factory default. Then restart the phone;
6- It will now boot up Kitkat. It may take sometime, as it is setting up the apps.
Gonna try it now, thanks!
it is safe
Yeah, its safe, I already did it :3
its works... and now i will again upgrade lollipop.. so if im going to setting>about device>system update and this is upgrade lolipop?? plzz tell m
PHP:
Consider this 1. Choose the right baseband to your device 2.after flashing via odin go to stock recovery by pressing vol up power button and home then choose wipe dalvic cache then wipe phone data after that reboot then it should boot normaly with kitkat installed ☺ thats what ido ive no problem encountered when downgrading
Am trying
Hi
Am trying to downgrade my samsung grand prime g530H from 5.0.2 to 4.4.4
every time it fails and said : " secure check fail : aboot "
what should i do ?!
please help me
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
these three buttons together press 5-10 sec (vol(-) button , home button, power button), then a windows open, select the download mode by pressing vol+ button, then from odin flash rom
Flashing on this rom OK G530HXXU2BOH5_G530HSER2BOH5_SER_5.0.zip
but when i select G530HXXU1ANI8_SER1ANI8_Russia_4.4.4_Repair_Firmware this to downgrade .. i got aboot fused error
im getting same type of error too. any alternative method?
I am also trying to downgrade with z3x but fail. try all methods
I maybe a years late or so but I am pretty much sure you can't downgrade from 5.0.2 to 4.4.4. I think the 5.0 bootloader won't allow to downgrade to 4.4.4.
Obviously I maybe wrong since I didn't tried it myself. I only heard it from others. And even if you are able to flash it it will probably go hard brick or something. Do at your own risk.
Hello,
I have problems with my s4 I9505 while I try to unbrick it
After a ota update from android 4.4.2 to 5.X (Orginal Firmware from Samsung) it cannot boot and enter Recovery and now I try to flash Firmware with odin but my phone turning screen off during odin says System.img.ext4 but the phone seens still working because it is showing in odin as connected but it doesn't continue flashing
I also see a new stuff in Download Mode Like Write Protection Enabled and eMMC Burst Mode Enabled
MichalPlays said:
Hello,
I have problems with my s4 I9505 while I try to unbrick it
After a ota update from android 4.4.2 to 5.X (Orginal Firmware from Samsung) it cannot boot and enter Recovery and now I try to flash Firmware with odin but my phone turning screen off during odin says System.img.ext4 but the phone seens still working because it is showing in odin as connected but it doesn't continue flashing
I also see a new stuff in Download Mode Like Write Protection Enabled and eMMC Burst Mode Enabled
Click to expand...
Click to collapse
Which firmware were you trying to flash through Odin? Is it KK or Lollipop?
Post the Odin log here.
Mandark52 said:
Which firmware were you trying to flash through Odin? Is it KK or Lollipop?
Click to expand...
Click to collapse
I tryed to flash Lollipop 5.0.1 (Orginal Firmware) and before brick I had Cyanogenmod Lollipop with Old Samsung Lollipop Modem and all worked fine until this **** ota update :/
Lennyz1988 said:
Post the Odin log here.
Click to expand...
Click to collapse
Ok, I will post it at 4:30p.m. (German Time Zone)
Lennyz1988 said:
Post the Odin log here.
Click to expand...
Click to collapse
ODIN LOG:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
(Device Freeze,after 2h battery empty)
<ID:0/007> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
MichalPlays said:
ODIN LOG:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
(Device Freeze,after 2h battery empty)
<ID:0/007> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Use a different usb port/different usb cable. That will solve it.
Lennyz1988 said:
Use a different usb port/different usb cable. That will solve it.
Click to expand...
Click to collapse
Nope I tryed now this already :/
I tested also the battery with my other s4 and it worked fine.
There is a pict. that showing where I put the firmware file and what option I select
hmm, what is this CSC and Phone slots at odin?
sry 4 my bad english
Maybe try a newer version of Odin?
MichalPlays said:
Nope I tryed now this already :/
I tested also the battery with my other s4 and it worked fine.
There is a pict. that showing where I put the firmware file and what option I select
hmm, what is this CSC and Phone slots at odin?
sry 4 my bad english
Click to expand...
Click to collapse
Then try a different pc. the log doesn't show anything strange that would let me doubt my suggestion.
Lennyz1988 said:
Then try a different pc. the log doesn't show anything strange that would let me doubt my suggestion.
Click to expand...
Click to collapse
At all my pc's one with win7 and another with windows xp - sp3 it are the same, maybe I need to flash something other and them the firmware :/
@MichalPlays Try using Odin 307.
downgrade Samsung s4 [GT-I9505] from Lolipop 5.0.1 to kitkat 4.4.2
Please read the entire post and don’t skip any steps, note that we cannot be blamed in case something goes wrong and you brick the phone.
1)-Make sure that your phone version is GT-I9505 (if you don't know how to check ; remove your battery then you will find)
2)-Download[/B] " SAMSUNG USB Driver for Mobile Phones" and setup, if you dont have it already
-Download Odin3-v3.09
-Download "PDA" ; "[email protected]" [1.52 GB]
-Download "BL" ; "Bootloader_GNK2.tar" [2.12 MB]
-Download "CP"; "Modem_GNK2_FULL.tar" [61.46 MB]
3)- your phone must be Charged 70% or more, and Rooted, if you have Samsung Kies; reboot your pc then end Kies from CPU (Ctrl + Alt + Supp).
4)-extract Odin and Start a program as an administrator then put only the PDA file which you've already downloaded and extracted before "([email protected])"
-Disable « Auto Reboot » and « Re-Partition »
-Enable « F. Reset Time » only
-Reboot your phone on Download Mode ( Power off the Phone completely, Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.).
-Connect your device with your PC and check "Added Message" and « ID:COM » in Odin
-Start
5)-Once you have "PASS" Plug out your Phone, and Reboot again in "Download Mode",
-Reset Odin
-Enable « Auto Reboot »and « F. Reset Time » only
-Put « Bootloader_GNK2.tar » on "BL"
-Put « Modem_GNK2_FULL.tar » on "CP
-Plug in your Phone and check "Added Message" and « ID:COM » if it doesn't work; restart Odin.
-Start to Downgrade
6)-Once the Downgrade done, plug out your phone and Hard Reset ;
(Power off your phone completely. Boot it in Recovery Mode. Select the ‘wipe data/ factory reset’ option. Confirm process by selecting the ‘Yes — delete all user data’ option. Press Power to confirm process. Reboot the phone when the Hard Reset/ Factory Reset is completed).
7)-Enjoy...
MichalPlays said:
At all my pc's one with win7 and another with windows xp - sp3 it are the same, maybe I need to flash something other and them the firmware :/
Click to expand...
Click to collapse
Ok then we can probably rule that out.
Are you using the original cable? Did you try different cables?
Lennyz1988 said:
Ok then we can probably rule that out.
Are you using the original cable? Did you try different cables?
Click to expand...
Click to collapse
I use always Original Cable and tested with cable from s4, s3, s3neo and htc one x plus and all doesn't work I tryed now the tutorial from this one guy this all was the same :/
btw. can I flash and enter a costum recovery without android on it ??
MichalPlays said:
I use always Original Cable and tested with cable from s4, s3, s3neo and htc one x plus and all doesn't work I tryed now the tutorial from this one guy this all was the same :/
btw. can I flash and enter a costum recovery without android on it ??
Click to expand...
Click to collapse
Yeah you can do that. Flash the latest TWRP. Uncheck auto-reboot before flashing with Odin.
Lennyz1988 said:
Yeah you can do that. Flash the latest TWRP. Uncheck auto-reboot before flashing with Odin.
Click to expand...
Click to collapse
oh, ok I will try this becasue I have this cyanogenmod .rar file on sd card and have also there an nandroid backup
I have down the TWRP recovery and then installed SU Root. It was working fine untill I mistakenly disabled developer options in my settings.
I have done the following already but none of them worked:
Downloaded Kies 3 and Smart Switch Firm Upgrade and Initialization. Tried giving my S/N and Model, but somehow, it is not recognizing my details correctly.
I do not want to load a stock ROM since I do not have a backup of my calls and contacts which are most important to me.
Thanks
amjadakmal said:
I have down the TWRP recovery and then installed SU Root. It was working fine untill I mistakenly disabled developer options in my settings.
I have done the following already but none of them worked:
Downloaded Kies 3 and Smart Switch Firm Upgrade and Initialization. Tried giving my S/N and Model, but somehow, it is not recognizing my details correctly.
I do not want to load a stock ROM since I do not have a backup of my calls and contacts which are most important to me.
Thanks
Click to expand...
Click to collapse
Ive had same problem earlier, just because ive wrote "stop" command in terminal emulator without knowing what it does lol, so never write that.
At me was saying FAP, not FRP though, but the way i solved my problem should solve yours too.
GUIDE to restore phone from "Custom binary blocked by FRP/FAP"
If you dont have a backup and you dont want to re-flash stock rom and lose all your stuff, then this will help you.
1. Download ODIN program. I'm using v3.09.
2. If you have J500FN model, then download this .rar file (made by me): J500FN stock recovery & kernel and skip to 3.
If you dont have J500FN model, then download the official stock firmware for your model from HERE or other website.
a) If the downloaded stock rom has .tar.md5 extension, remove .md5, then it should be only .tar
b) Extract the .tar file.
c) Now you will see recovery.img and boot.img. You need to make those two to .tar . To do this, you need a small program.
d) Go HERE and download Caboomi's_Recovery_img2tar_odin_maker from attachements.
e) Now, extract the .zip file, delete the actual recovery.tar.md5 from folder and then copy recovery.img and boot.img from the folder where you extracted .tar file to Caboomi's_Recovery_img2tar_odin_maker.
f) We will make recovery.tar.md5 first. Right-click Runme.bat and choose edit and replace
PHP:
bin\tar -H ustar -c recovery.img > recovery.tar
with
PHP:
bin\tar --group=1 -H ustar -c recovery.img > recovery.tar
And now save it, then run it. After you ran it, you will see recovery.tar.md5
g) Now lets do boot.tar.md5. Right-click Runme.bat and choose edit again. Now replace
PHP:
bin\tar --group=1 -H ustar -c recovery.img > recovery.tar
bin\md5sum -t recovery.tar >> recovery.tar
bin\mv recovery.tar recovery.tar.md5
with
PHP:
bin\tar --group=1 -H ustar -c boot.img > boot.tar
bin\md5sum -t boot.tar >> boot.tar
bin\mv boot.tar boot.tar.md5
And now save it, then run it. After you ran it, you will see boot.tar.md5.
3. I assume your phone is already powered off. Reboot your phone in download mode by keeping pressing Power button + home button + volume DOWN button at same time for few seconds. After an blue screen will appear, press volume up button.
4. Connect your phone with usb cable to your PC.
5. Open ODIN program (if it doesnt work, then right-click it and run it as administrator) and an number should appear at ID:COM. If it doesn't, then make sure that the phone usb drivers are installed.
6. Click on BL and go to the directory where is located the recovery.tar.md5 which we made, click on it and then click on Open. Now click START in ODIN. Wait until the process finish.
7. Now the phone should reboot byself. Power it off and repeat steps from 3. to 5.. Now, click on AP or PDA ( according to the version of odin which you downloaded) and and go to the directory where is located the boot.tar.md5 which we made, click on it and then click on Open. Now click START in ODIN. Wait until the process finish.
8. Phone should reboot again and this time it will boot. All your data is there.
9. Re-enable OEM unlocking in Developer Options again and now you can flash TWRP & kernel again.
10. If this guide helped you, then reply saying that or click thanks button. This way i know that i didnt wrote this guide for nothing Thank you!
Click to expand...
Click to collapse
Like me, you shouldve learnt something from this. ALWAYS have a backup.
Firmware link is bust
Im not sure what you mean by "bust", but you can download stock firmware from other website too, although sammobile is recommended.
got the same issue (but with J5 (2016))].
Is this working as well?
About data backup I do not care.
Thanks a lot. Followed all the steps and worked like a charm. Working on model SM-J510GN
HI
I have same problem with custom binary blocked, I tried your fix, but I can't download in download mode, it says MDM MODE CAN'T DOWNLOAD !!!!!
Please help!!
Thanks
Hi
I have the same problem . but I can't download in download mode, it says "MDM MODE CAN'T DOWNLOAD"
Please help!!!!!!!!!!!!!
Hi would this method work if i have the recovery.img and not .tar ??
Thank you #Henkate, very cool!
Jokes and Trump references aside, this method really worked, worth a try. I downloaded the firmware from sammobile, the speed was limited to 300 kB/sec so it took me 50 minutes but the everything went quite well after, the whole thing took about an hour.
Hi, doen't work, see comments,
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.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> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I didn't have choise to execute step 6 : BL choise not activate,
Thanks for Help.
Thank you
I've spent a week trying to open my phone again! It worked. I watched videos etc and changed each file to tar with Odin tool but I couldn't figure out where each img went once it was in tar format! You are awesome
Your selfmade J500FN stock recovery & kernel broke my phone now it wont boot and theres green screen
After aaaaall tose years this method still works! You are a legend. The only thing to note is that I was not able to locate "Caboomi's_Recovery_img2tar_odin_maker". I just googled "img2tar_odin_maker" and I found a working program. Time to see what I had on my very old phone!