Related
I was trying to go back to XXPE from XXPQ to flash my phone clean again - after flashing latona to my phone, it doesnt boot any more. Any help?
Follow the steps........
1 Download mode
2 start odin
3 connect via usb
4 select pit latona_20110114
5 boot APBOOT_I9003XXKPE_CL409735_REV08_user_low_ship.tar
6 pda CODE_I9003XXKPE_CL409735_REV08_user_low_ship.tar
7 phone MODEM_I9003XXKPE_REV_00_CL1041909.tar
8 csc GT-I9003-CSC-MULTI-OXAKPE.tar
9 press start
10 enjoy
You will need following before beginning installation:
1) Flsher Program + PIT (ODIN3 + Latona.PIT)
2) Firmware: I9003XXKPE
STEPS:
1) Open ODIN. Connect ur phone in download mode. just flash Latona.PIT file with Re-Partition selected.
2) Once flashed, Ur phone will reboot automatically but will show only black screen with background light. Do not worry. Open the back cover, remove the battery, insert battery and boot again in download mode.
3) Close ODIN. Open it again. Now we will be installing XXKPE.
i) Select Latona.PIT File in ODIN. (Make sure the "Re-Partition" is unchecked once you have selected PIT file)
ii) Select "APBOOT_I9003XXKPE_CL409735_REV08_user_low_ship.tar.md5" in bootloader.
iii) Select "CODE_I9003XXKPE_CL409735_REV08_user_low_ship.tar.md5" in PDA.
iv) Select "MODEM_I9003XXKPE_REV_00_CL1041909.tar.md5" in PHONE.
v) Select "GT-I9003-CSC-MULTI-OXAKPE.tar.md5" in CSC.
Now flash it.
this will successfully install XXKPE on ur device. Once your flash is complete, ur device will boot and will ask for initial config.
Hi all i tried to flash i9003 galaxy SL from steps below to 2.3.6 , but the firmware zip file does not have MODEM, CSC and PDA files but only .dll file and tar.md5 file, where can i get the MODEM, CSC and PDA.
I download the firmwares from link below:-
http://www.tsar3000.com/Joomla/inde...alaxy-sl-firmwares&catid=55:samsung&Itemid=82
Firmware Update Steps:
Run Samsung I9003 Galaxy SL Downloader.
Check Re-Partition, Auto Reboot and F. Reset Time.
Click PIT button and select this file: latona_20110114.pit
Put your phone into download mode: Press Volume down + OK + Power.
Connect USB cable and the program will detect the phone's Com number.
Click Start button to download the PIT file to phone.
After it is Done Click on Reset button, then unselect Re-Partition box.
Click PDA button and select this file: I9003xxxxx-xxx...-PDA-low-CL890053.tar.md5 <<<<<<<<<<<<<<<
Click PHONE button and select this file: MODEM_I9003xxxxx_REV_00_CL889972.tar.md5 <<<<<<<<<<<<<<<<<
Click CSC button and select this file: GT-I9003-CSC-xxxxxx.tar.md5 <<<<<<<<<<<<<<<<<<<
Remove the battery, then enter Device into Download Mode again.
Click Start button to flash these files to phone.
Do not touch anything till you see PASS on the program window.
Do full reset by this Code: *2767*3855#.wares i download dont have CSC , PDA
suhailpuri said:
Hi all i tried to flash i9003 galaxy SL from steps below to 2.3.6 , but the firmware zip file does not have MODEM, CSC and PDA files but only .dll file and tar.md5 file, where can i get the MODEM, CSC and PDA.
I download the firmwares from link below:-
http://www.tsar3000.com/Joomla/inde...alaxy-sl-firmwares&catid=55:samsung&Itemid=82
Firmware Update Steps:
Run Samsung I9003 Galaxy SL Downloader.
Check Re-Partition, Auto Reboot and F. Reset Time.
Click PIT button and select this file: latona_20110114.pit
Put your phone into download mode: Press Volume down + OK + Power.
Connect USB cable and the program will detect the phone's Com number.
Click Start button to download the PIT file to phone.
After it is Done Click on Reset button, then unselect Re-Partition box.
Click PDA button and select this file: I9003xxxxx-xxx...-PDA-low-CL890053.tar.md5 <<<<<<<<<<<<<<<
Click PHONE button and select this file: MODEM_I9003xxxxx_REV_00_CL889972.tar.md5 <<<<<<<<<<<<<<<<<
Click CSC button and select this file: GT-I9003-CSC-xxxxxx.tar.md5 <<<<<<<<<<<<<<<<<<<
Remove the battery, then enter Device into Download Mode again.
Click Start button to flash these files to phone.
Do not touch anything till you see PASS on the program window.
Do full reset by this Code: *2767*3855#.wares i download dont have CSC , PDA
Click to expand...
Click to collapse
First of all post in the general section. Second, read a lot.
Thirdly, which firmware are you at present? If KPE, flash LF2. The new stock firmwares only have a single .tar file. No modem, csc or any other files needed. And download from here >> http://forum.xda-developers.com/showthread.php?t=1004647/
nbrian2012 said:
First of all post in the general section. Second, read a lot.
Thirdly, which firmware are you at present? If KPE, flash LF2. The new stock firmwares only have a single .tar file. No modem, csc or any other files needed. And download from here >> http://forum.xda-developers.com/showthread.php?t=1004647/
Click to expand...
Click to collapse
i dont know the firmware as the phone is bricked, i managed to get into firmware download mode but it gives me an error after flashing, i flash the pit file and then reset odin and then enter download mode again and select single firmware file and check PDA option but flashing fale.
What file do i download because i downloaded many firmwares gingerbread ones but they all have one single tar file.
Socon off all what box do i need to select if i am flashing a single file , PDA or phone or CSC.
Suhail
suhailpuri said:
i dont know the firmware as the phone is bricked, i managed to get into firmware download mode but it gives me an error after flashing, i flash the pit file and then reset odin and then enter download mode again and select single firmware file and check PDA option but flashing fale.
What file do i download because i downloaded many firmwares gingerbread ones but they all have one single tar file.
Socon off all what box do i need to select if i am flashing a single file , PDA or phone or CSC.
Suhail
Click to expand...
Click to collapse
Download KPE, the files from the link I gave you ^
and follow THIS guide carefully >>>
Misledz said:
2. Run Odin3 v1.83
3. Check Re-Partition, Auto Reboot and F. Reset Time.
4. Click PIT button and select this file: latona_20110114.pit
5. Set it to download mode : Press Volume down + OK first, then hold Power button.
6. Connect USB cable and the program will detect the phone's Com number.
7. Click Start button to download the PIT file to phone.
8. After it is Done Click on Reset button [Partition box should be unchecked automatically - Thanks to jaskir]
9. Click PDA button and select this file: CODE_I9003XXKPE_CL409735_REV08_user_low_ship.tar
10. Click PHONE button and select this file: MODEM_I9003XXKPE_REV_00_CL1041909.tar
11. Click BOOTLOADER button and select this file: APBOOT_I9003XXKPE_CL409735_REV08_user_low_ship.tar
12. Click CSC button and select this file: GT-I9003-CSC-MULTI-OXAKPE.tar
13: You should unplug usb cable, remove battery, insert battery and bring it back to download mode. I have never been able to bring it to download mode with usb plugged in. [Thanks to jaskir for this suggestion to make it clear to new users!]
14. Click Start button to flash these files to phone.
15. Do not touch anything till you see PASS on the program window.
16. Factory reset
17. [To fix issues that pertain] Reflash from steps 9 -15 again, No need of latona at this point.
Click to expand...
Click to collapse
Must you have any issue at any point, reply again.
The SL can never get bricked unless you flash a firmware not compatible with it
Sent from my Galaxy Nexus using Tapatalk 4 Beta
How can i flash a single file .tar.md5 with odin, becuause now all the firmwares come with a single file i.e. .tar.md5 unlike old firmwares have CSC, modem and PDA file
shall i put pit file first and then flash which option needs to be checked ?
This has become really confusing for me now.
Can i also put my phone in download mode and flash via KIES ?
Thanks in advance,
Suhail
suhailpuri said:
i dont know the firmware as the phone is bricked, i managed to get into firmware download mode but it gives me an error after flashing, i flash the pit file and then reset odin and then enter download mode again and select single firmware file and check PDA option but flashing fale.
What file do i download because i downloaded many firmwares gingerbread ones but they all have one single tar file.
Socon off all what box do i need to select if i am flashing a single file , PDA or phone or CSC.
Suhail
Click to expand...
Click to collapse
HELP NEEDED TO FLASH FIRMWARE IN SAMSUNG GALAXY SL GT-I9003
I have downloaded the firmwares suggested by you... Its not clear how to proceed with the flashing of the firmware, as the steps asked to perform by you are contradicting to your previous post -> As there is only only file i.e GT-I9003_XEO_I9003XWLF2_I9003OXXLF1_I9003XXLE4 and rest of the files i.e PHONE file: MODEM_I9003XXKPE_REV_00_CL1041909.tar, BOOTLOADER file: APBOOT_I9003XXKPE_CL409735_REV08_user_low_ship.tar, CSC file: GT-I9003-CSC-MULTI-OXAKPE.tar are not required. Please be specific what is to be done to complete the flashing procedure.
well i just wanna know how to flash with odin when you have one file for firmware and tutorials show 3 files, but whatever firmwares i download they all have one ta file and no 3 files as suggeted in tutorials.
Suhail
Flash first clean for mandatory starting
On CM10 Alpha 3 and all other basic Froyo, Gingerbread, ICS, JB
- drivers samsung.rar - 5.58 MB
- Open Odin 1.85 only !!!
- KPE FULL (do not forget the PIT) (Froyo only ! no forget bootloader)
reset odin then remove cable and battery after samsung logo
- LF2 (PDA only with Odin)
reset odin then remove cable and battery after second samsung logo
- CF Root LF2 (PDA only with Odin)
I followed all steps, but in STEP 2 when i download the file its iso and not not md5 or tar so i dont know how to proceed and flash it, i tried to mount it , burn it no sucess
Anyways i went to step 3 and flashed again, but phone gets stuck at boot screen samsung logo
Any
UNZIP ?§!
suhailpuri said:
I followed all steps, but in STEP 2 when i download the file its iso and not not md5 or tar so i dont know how to proceed and flash it, i tried to mount it , burn it no sucess
Anyways i went to step 3 and flashed again, but phone gets stuck at boot screen samsung logo
Any
Click to expand...
Click to collapse
Dude, if it's a zip file then extract it & use the file which is extracted.
Good luck!
Sent from my GT-I9003.
LoLaTiOn said:
UNZIP ?§!
Click to expand...
Click to collapse
Hi LoLaTiOn,
I have unzipped the CSROOT file, what I could see was a .img file where as while selecting the file in the ODin 1.85 it demands for a .tar file. Can you please further help in this and pass me the link for the actual file i.e CSROOTXXXXXXXX.tar file in the required format to flash the Android OS.
Rest all the files in the link provided by you are in the required format.
Siddhant Shankpal said:
Dude, if it's a zip file then extract it & use the file which is extracted.
Good luck!
Sent from my GT-I9003.
Click to expand...
Click to collapse
Hi Siddhant,
Anybody in the world knows that we have to unzip a zipped file before using it. The actual problem is that --> After unzipping the file , I see a .img file where as Odin requires a .tar file to flash the Android OS. I tried converting it into a .tar file by using a cygwin terminal but no luck. I also tried searching for the same file in other links (Websites) but still there was no luck.
Can you give a hand to help me out.
suhailpuri said:
Hi Siddhant,
Anybody in the world knows that we have to unzip a zipped file before using it. The actual problem is that --> After unzipping the file , I see a .img file where as Odin requires a .tar file to flash the Android OS. I tried converting it into a .tar file by using a cygwin terminal but no luck. I also tried searching for the same file in other links (Websites) but still there was no luck.
Can you give a hand to help me out.
Click to expand...
Click to collapse
U mentioned "step 2" that means u were stuck in DDLF2 flashing step. But now ur telling "CFROOT LF2" step.
Okay, now in this step u don't need to unzip this file & just flash it from odin as in PDA section.
But I hope ur able to boot into ur phone after flashing DDLF2 firmware.
Good luck!
Sent from my GT-I9003.
Siddhant Shankpal said:
U mentioned "step 2" that means u were stuck in DDLF2 flashing step. But now ur telling "CFROOT LF2" step.
Okay, now in this step u don't need to unzip this file & just flash it from odin as in PDA section.
But I hope ur able to boot into ur phone after flashing DDLF2 firmware.
Good luck!
Sent from my GT-I9003.
Click to expand...
Click to collapse
My bad, I have mentioned it earlier that I have tried flashing the same .img file in the entire process but no luck.
suhailpuri said:
My bad, I have mentioned it earlier that I have tried flashing the same .img file in the entire process but no luck.
Click to expand...
Click to collapse
Download this DDLF2 firmware & extract it. http://forum.xda-developers.com/showthread.php?t=2329200
1. After extracting, switch off your phone & go to download mode.
2. Open odin 1.85 on ur PC & connect ur phone to ur PC. Check, whether it is connected by the yellow signal.
3. First only flash .pit file from the extracted folder. Then remove battery & put it back then again go download mode.
4. Browse & select all respected files from the extracted folder. (Do not include bootloader file if ur coming back to stock from CM 10 based roms.)
5. Click start.
Good luck!
Sent from my GT-I9003.
Hi guys, I need your help. I've got galaxy note 10.1 tab. I stupidly tried flashing cwm through rom manager, even though it wasn't compatible! Now, I'm stuck on the samsung logo when booting up. It is rooted via exynos abuse. Its on stock rom and no custom recovery. I can get to download mode and the android recovery. On top of that, I've been trying to install odin on my computer, but its not working, keep getting Korean message, and when I click ok, the odin window comes up for a split second, then disappears. I really need some help please.
Thanks in advance
Try googling about download mode and fastboot utilite from Android Development Bundle
With this utilite you can try to flash recovery image
Result!!!
Firstly thanks to xxxTy3uKxxx for the prompt reply to my question. It helped me look in the right direction to sort my blunder! In the end I couldn't use the above method because it required to have the tablet in "USB DEBUGGING MODE" which I couldn't do because I couldn't get the damn thing on!
So, now that I've fixed it (if I didn't my missus would have killed me) I wanted to share with all as there doesn't seem to be a lot of solutions around to fix this problem!
From the above post you can see what the problem was, I was only able to get to either download mode or the android stock recovery, and the phone was not booting past the "note 10.1" logo
- I basically had to download the "rootgalaxynote10.1" zip file from rootgalaxynote.com.
- Then, using Odin I flashed the "highonandroidCWMrecoveryGTN8000.tar" file. This gave me custom recovery (you can't flash roms with stock android recovery)
- From here I downloaded a rom for my N8010, and put in on a micro sd card. Put this in the note 10.1, then used custom recovery to flash this rom
NB. I encountered a problem with Odin, and that was I couldn't open it on my lap top! I downloaded numerous files/versions, but no luck. Some forums said to run as administrator or switch off firewall/anti-virus, but nothing worked! I then tried it on a different lap top and VOILA! I don't know why, but it worked on different lap top!
I hope this helps someone out in the future
PS. Hit thanks if I saved your back side
Biggup to u both. Almost thought id lost my tablet after I committed the very same crime
mimik1 said:
Firstly thanks to xxxTy3uKxxx for the prompt reply to my question. It helped me look in the right direction to sort my blunder! In the end I couldn't use the above method because it required to have the tablet in "USB DEBUGGING MODE" which I couldn't do because I couldn't get the damn thing on!
So, now that I've fixed it (if I didn't my missus would have killed me) I wanted to share with all as there doesn't seem to be a lot of solutions around to fix this problem!
From the above post you can see what the problem was, I was only able to get to either download mode or the android stock recovery, and the phone was not booting past the "note 10.1" logo
- I basically had to download the "rootgalaxynote10.1" zip file from rootgalaxynote.com.
- Then, using Odin I flashed the "highonandroidCWMrecoveryGTN8000.tar" file. This gave me custom recovery (you can't flash roms with stock android recovery)
- From here I downloaded a rom for my N8010, and put in on a micro sd card. Put this in the note 10.1, then used custom recovery to flash this rom
NB. I encountered a problem with Odin, and that was I couldn't open it on my lap top! I downloaded numerous files/versions, but no luck. Some forums said to run as administrator or switch off firewall/anti-virus, but nothing worked! I then tried it on a different lap top and VOILA! I don't know why, but it worked on different lap top!
I hope this helps someone out in the future
Click to expand...
Click to collapse
OMG. Thanx for your experience but I have no computer with windows now Are there any ideas how to flash a recovery with Linux?
OK. I've found an alternative to odin called Heimdall and succesfully flashed the Darkman's recovery. However it is not able for some reason to mount the /system and /sdcard partitions (which I'd like to back up first). Any ideas?
flashcactus said:
OK. I've found an alternative to odin called Heimdall and succesfully flashed the Darkman's recovery. However it is not able for some reason to mount the /system and /sdcard partitions (which I'd like to back up first). Any ideas?
Click to expand...
Click to collapse
Sorry mate, not to familiar with that. Might need one of the more experienced guys to help you out. Good luck:good:
Sorry for writing so late and in such a for dummies manner. I want this thread to be helpful for absolutely everyone who bricked his device like this.
COMPLETE SOLUTION:
First, you can try to flash your ROM (stock roms can be found here. There's another topic with more stock roms but I can't find it) with Heimdall, excluding the data partition to preserve... erm.. your data:
Install Heimdall with its graphical frontend.
Connect your device to your computer via USB cable and put it in download mode (ODIN mode) (Power+VolumeDown).
Open the Heimdall frontend, go to the Utilities tab.
Press Detect device. The device detected radiobutton to the left should be checked.
Under Print PIT check the Local File radiobutton and select where to save your device's partition data to (I named the file n8k.pit) in the browse dialog under it. Then press the Print button.
Now go to the Flash tab. Select the file you just created in the browse dialog under Options/PIT.
unpack the .zip containing your ROM. Then unpack the .tar.md5 that was inside it. You'll get several .img files.
Press the Add button. Select 'SYSTEM' from the Partition Name list. Select the system.img file you just unpacked under File (system.img).
For each entry in the following list, do the previous step, substituting 'SYSTEM' and system.img by:
BOOT and boot.img, respectively;
CACHE and cache.img, respectively
Take a deep breath and press Start.
And then you can go the hard, perverted&interesting way, and that's the way I went.
download this zipfile and unpack it. Find highonandroidCWMrecoveryGTN8000.tar among the unpacked files and unpack that. You'll get a recovery.img file.
download another version of CWM reccovery in an Odin-flashable format, unpack it to get the recovery.img
download PhilZ Touch Recovery for your device in ODIN-flashable format. Unpack and get the recovery.img.
Do steps 1-6 from the instruction above.
Press the Add button. Select 'RECOVERY' from the Partition Name list. Select your recovery.img file under File (recovery.img).
Press the Start button and wait for the operation to finish.
If you did not flash the PhilZ recovery right away, download it in CWM-flashable zip format, put on your SD card, load your new recovery and flash the zip.
Open the recovery, go to Backup and Restore => Custom Backup and Restore => Custom Backup job
Uncheck everything except backup data and optionally backup recovery, then press >> Start Custom Backup Job <<[/color].
Download a ROM of your liking, wipe data&cache, flash it, try it.
If you like it, try to restore data. Get the recovery going, go to Custom Restore job => uncheck all except data => >> Start Custom Restore Job <<[/color] => find your backup => data.ext4.tar) and reboot the device. If it doesn't bootloop, congratulations. If it does, GOTO 8.
Remember to hit the [:good:Thanks] button if this guide has saved yer arse.
flashcactus said:
Sorry for writing so late and in such a for dummies manner. I want this thread to be helpful for absolutely everyone who bricked his device like this.
COMPLETE SOLUTION:
First, you can try to flash your ROM (stock roms can be found here. There's another topic with more stock roms but I can't find it) with Heimdall, excluding the data partition to preserve... erm.. your data:
Install Heimdall with its graphical frontend.
Connect your device to your computer via USB cable and put it in download mode (ODIN mode) (Power+VolumeDown).
Open the Heimdall frontend, go to the Utilities tab.
Press Detect device. The device detected radiobutton to the left should be checked.
Under Print PIT check the Local File radiobutton and select where to save your device's partition data to (I named the file n8k.pit) in the browse dialog under it. Then press the Print button.
Now go to the Flash tab. Select the file you just created in the browse dialog under Options/PIT.
unpack the .zip containing your ROM. Then unpack the .tar.md5 that was inside it. You'll get several .img files.
Press the Add button. Select 'SYSTEM' from the Partition Name list. Select the system.img file you just unpacked under File (system.img).
For each entry in the following list, do the previous step, substituting 'SYSTEM' and system.img by:
BOOT and boot.img, respectively;
CACHE and cache.img, respectively
Take a deep breath and press Start.
And then you can go the hard, perverted&interesting way, and that's the way I went.
download this zipfile and unpack it. Find highonandroidCWMrecoveryGTN8000.tar among the unpacked files and unpack that. You'll get a recovery.img file.
download another version of CWM reccovery in an Odin-flashable format, unpack it to get the recovery.img
download PhilZ Touch Recovery for your device in ODIN-flashable format. Unpack and get the recovery.img.
Do steps 1-6 from the instruction above.
Press the Add button. Select 'RECOVERY' from the Partition Name list. Select your recovery.img file under File (recovery.img).
Press the Start button and wait for the operation to finish.
If you did not flash the PhilZ recovery right away, download it in CWM-flashable zip format, put on your SD card, load your new recovery and flash the zip.
Open the recovery, go to Backup and Restore => Custom Backup and Restore => Custom Backup job
Uncheck everything except backup data and optionally backup recovery, then press >> Start Custom Backup Job <<[/color].
Download a ROM of your liking, wipe data&cache, flash it, try it.
If you like it, try to restore data. Get the recovery going, go to Custom Restore job => uncheck all except data => >> Start Custom Restore Job <<[/color] => find your backup => data.ext4.tar) and reboot the device. If it doesn't bootloop, congratulations. If it does, GOTO 8.
Remember to hit the [:good:Thanks] button if this guide has saved yer arse.
Click to expand...
Click to collapse
So i've done all this, but its still stuck on the samsung logo, i have no recovery... only can get into odin mode.
My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.
invalid ext4 image
madsthines said:
My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.
Click to expand...
Click to collapse
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!
ornobohornish said:
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!
Click to expand...
Click to collapse
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )
Grateful to you...
esgie said:
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )
Click to expand...
Click to collapse
Dear Sir,
I am so surprised to see that somebody response me for the core of his heart! I am so pleased to realize that some body look at my problem very attentively! sir, thank you!
so,
** I have tried using different usb cable to flash
** I have tried both 3.9 or 3.7 odin
** I have tried different pc to flash
** I have used 2.0 or 3.0 both usb cable
** I have tried both kies3 or previous kies
** I am giving here the whole odin texts which
was shown
"<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!"
** Long installation process means 5-7 minutes! (I think it is normal, sorry)
** yes, I have used all high end android devices and all was rooted, installed cwm recovery, custom room, so I have experience well on android I am not new to play with android operating system. even now I am also using Note 3 with Omega custom rom and working great.
** I am thinking may be the problem is about pit. and I don't know where I will find a .pit file for SM-P905. some how may be the pit of my note pro is corrupted. i don't know actually I am not a developer!
Here all you wanted to know!
Dear Sir please help me to make alive my Galaxy Note Pro!
Please!!!
screen shot!
after the failed flashing operation all the time my devices shows, i am giving a screen shot!
Downloaded 3 Firmware
Already I have downloaded 3 rom, (because I thought the firmware file was corrupted) but by studying your post I know now when ever odin accept any firmware that means the rom file is not corrupted! thanks!
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
i have download this 3 files!
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
mismatch
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
according to your link there is no file, named "recovery.img" but the file name is "libwfdsm.so"
DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), figured out on my own to be exact, I have managed to unroot and revert to fully-stock state my old Note10.1, which I was not able to flash straight via Odin at all because the port's been broken, so I was able to send it to service center without any worries (at least related to the possibility of detecting the customization by the service) The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.
problem solved!
esgie said:
DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), I managed to unroot and revert to fully-stock state my old Note10.1, which I was not really able to flash straight via Odin because the port's been broken. The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.
Click to expand...
Click to collapse
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?
ornobohornish said:
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?
Click to expand...
Click to collapse
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...
ohh nooo! befor reading you reply I was tried to update my device by kies. but same thing happen here. stuck on Invalid ext4 image!
i am so tired
esgie said:
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...
Click to expand...
Click to collapse
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!
ornobohornish said:
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!
Click to expand...
Click to collapse
My recommendation: repeat the procedure Ive posted earlier. Well se what happens
It looks like some part of your nand may be physically corrupted... and unwriteable.
before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!
can not find "simg2img"
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
dear sir,
in your link nowhere i found "simg2img"! I searched all the page number 9 but no where I found "simg2img"!!!
help please
---------- Post added at 10:28 AM ---------- Previous post was at 10:01 AM ----------
able to download simg2img from this link: http://web.djodjo.org/?a=download:android:tools:x86_linux:ext4tools
but how to use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)?
how to use simg2img?
Will this work with the SM-P900?
esgie said:
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!
Click to expand...
Click to collapse
Hi Esgie.
I'm assuming that most of this would work for the SM-P900 (wifi only) version too? What would I use for the dd command in step 9?
Thanks for your help.
Jo Pop
ornobohornish said:
before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!
Click to expand...
Click to collapse
I had same problem, install rom from greece. Some roms from sammobile and samsung firmware are giving errors, I have tested polish and british giving "odin: invalid ext4 image" error. After installing greece one everything works flawlessly, samsung keyboard also.
Working FRP bypass for Samsung S8+ (SM-G955F) G955FXXS4CSA2 Firmware for Australia with 8.0.0 Oreo
Software used:
Odin
7-Zip
Firmware used:
COMBINATION_FA70_G955FXXU4ARI1
XSA-G955FXXS4CSA2-20190130100335 AUSTRALIA XSA
Unsure if this work around will work for other countries but worth a try by changing the firmware files
Firstly need to download Firmwares for the S8+
Create a new folder where you need to unzip AP BL HOME_CSC Files to delete some files
In BL folder delete cm.bin.lz4, param.bin.lz4, up_param.bin.lz4 leave sboot.bin.lz4 in the file use 7-Zip to convert back to .tar file and rename to BL_G955FXXS4CSA2_CL14483965_QB21338337_REV00_user_low_ship
In AP folder delete meta-data file, userdata.img.lz4 leave boot.img.lz4, recovery.img.lz4 sytem.img.lz4 in the file use 7-Zip to convert back to .tar file and rename to AP_G955FXXS4CSA2_CL14483965_QB21338337_REV00_user_low_ship_meta
In HOME_CSC folder delete meta-data leave cache.img.lz4, hidden.img.lz4 in the file use 7-Zip to convert back to .tarfile and rename HOME_CSC_XSA_G955FXSA4CRJ1_CL14519757_QB20086231_REV00_user_low_ship
CP no files need to be deleted leave as a CP_G955FXXS4CRL2_CP11298465_CL14483965_QB20804611_REV00_user_low_ship.tar.Md5 file
If you use CSC_XSA_G955FXSA4CRJ1_CL14519757_QB20086231_REV00_user_low_ship.tar file the FRP bypass will fail
Firstly need to put the phone into download mode by pressing vol down bixby and power button together use odin to flash the combination file COMBINATION_FA70_G955FXXU4ARI1 to the phone
Once flashed and restarted go to settings developers options make sure USB debugging is enabled next open factory IME type *#0808# change USB SETTINGS to DM+ACM+ADB reboot
the phone back into FACTORY BINARY then turn phone off and reboot into download mode.
Flash the new AP BL CP HOME_CSC to the phone using Odin
with any luck the phone should load back into stock firmware with FRP off go to settings-General Management-Reset-Factory Data Reset
the phone should Factory Reset with FRP still off should be able to set the phone up like a brand new phone
If the phone fails on start up with the new Firmware put back into download reinstall FACTORY BINARY follow the same steps again
shaun2387 said:
Working FRP bypass for Samsung S8+ (SM-G955F) G955FXXS4CSA2 Firmware for Australia with 8.0.0 Oreo
Software used:
Odin
7-Zip
Firmware used:
COMBINATION_FA70_G955FXXU4ARI1
XSA-G955FXXS4CSA2-20190130100335 AUSTRALIA XSA
Unsure if this work around will work for other countries but worth a try by changing the firmware files
Firstly need to download Firmwares for the S8+
Create a new folder where you need to unzip AP BL HOME_CSC Files to delete some files
In BL folder delete cm.bin.lz4, param.bin.lz4, up_param.bin.lz4 leave sboot.bin.lz4 in the file use 7-Zip to convert back to .tar file and rename to BL_G955FXXS4CSA2_CL14483965_QB21338337_REV00_user_low_ship
In AP folder delete meta-data file, userdata.img.lz4 leave boot.img.lz4, recovery.img.lz4 sytem.img.lz4 in the file use 7-Zip to convert back to .tar file and rename to AP_G955FXXS4CSA2_CL14483965_QB21338337_REV00_user_low_ship_meta
In HOME_CSC folder delete meta-data leave cache.img.lz4, hidden.img.lz4 in the file use 7-Zip to convert back to .tarfile and rename HOME_CSC_XSA_G955FXSA4CRJ1_CL14519757_QB20086231_REV00_user_low_ship
CP no files need to be deleted leave as a CP_G955FXXS4CRL2_CP11298465_CL14483965_QB20804611_REV00_user_low_ship.tar.Md5 file
If you use CSC_XSA_G955FXSA4CRJ1_CL14519757_QB20086231_REV00_user_low_ship.tar file the FRP bypass will fail
Firstly need to put the phone into download mode by pressing vol down bixby and power button together use odin to flash the combination file COMBINATION_FA70_G955FXXU4ARI1 to the phone
Once flashed and restarted go to settings developers options make sure USB debugging is enabled next open factory IME type *#0808# change USB SETTINGS to DM+ACM+ADB reboot
the phone back into FACTORY BINARY then turn phone off and reboot into download mode.
Flash the new AP BL CP HOME_CSC to the phone using Odin
with any luck the phone should load back into stock firmware with FRP off go to settings-General Management-Reset-Factory Data Reset
the phone should Factory Reset with FRP still off should be able to set the phone up like a brand new phone
If the phone fails on start up with the new Firmware put back into download reinstall FACTORY BINARY follow the same steps again
Click to expand...
Click to collapse
That's wassup
[emoji3436]I Willl Scarfice For Those That I Love [emoji3434]
Tried this, having issues
So I am obviously using a newer binary because that's all I was able to use. I'm using a modded odin v3.14.1 and i have followed every step to the best of my ability but for whatever reason as soon as i hit start, odin crashes. Any ideas?