I ran into a corrupted or unaccessible /data partition several times this week, and after searching, couldn't find any tutorials on using heimdall to completely reset the phone back to stock. So... below is my version. Please provide any input on this method, it's worked a couple times with no issues for me.
FILENAMES BELOW ARE FOR ATT PHONE, if you are not ATT, use the relevant files for your carrier.
Instructions here were done on a Mac, but the programs and commands are the same on any Operating System.
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your Mac, open up Terminal, and navigate to the location you extracted the tar.md5 files to
8) In Terminal, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) sudo heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Hope this helps, any questions don't hesitate to PM me.
===================WINDOWS VERSION, by popular request================================
Instructions here were done on a Windows 7 PC
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your PC, open up a Command Prompt (Click the "start" button, and type in cmd and hit enter), and navigate to the location you extracted the tar.md5 files to
8) In the command prompt, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Thanks for taking the time to do this. Provides an Odin - like option for Linux users like myself, and of course, Mac users too.
Sent from my GT-I9505G using xda premium
I'm getting...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
...Any advice? It looks like its uploading, fails, and reboots phone back to download mode.
Encryption Failed everytime i reboot any fix?
Deleted
Interested in any solutions you guys found for your listed issues, as I have an iMac also--
tom_callahan said:
I ran into a corrupted or unaccessible /data partition several times this week, and after searching, couldn't find any tutorials on using heimdall to completely reset the phone back to stock. So... below is my version. Please provide any input on this method, it's worked a couple times with no issues for me.
FILENAMES BELOW ARE FOR ATT PHONE, if you are not ATT, use the relevant files for your carrier.
Instructions here were done on a Mac, but the programs and commands are the same on any Operating System.
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your Mac, open up Terminal, and navigate to the location you extracted the tar.md5 files to
8) In Terminal, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) sudo heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Hope this helps, any questions don't hesitate to PM me.
Click to expand...
Click to collapse
Im having that inaccessible /data partition and ODIN is not working for me. It flashes successfuly in ODIN, but upon boot it just hangs on the Samsung Galaxy S4 logo. When i go into the stock recovery, it shows the broken android and the cannot mount/data error. Its starting to become a real headache for me. I don't have a Mac tho, so i don't think your tool would work for me.
Monkz said:
Im having that inaccessible /data partition and ODIN is not working for me. It flashes successfuly in ODIN, but upon boot it just hangs on the Samsung Galaxy S4 logo. When i go into the stock recovery, it shows the broken android and the cannot mount/data error. Its starting to become a real headache for me. I don't have a Mac tho, so i don't think your tool would work for me.
Click to expand...
Click to collapse
Heimdall works on any platfork, mac/linux/windows...you just need java installed and your good to go, just use the command prompt instead of terminal. this was also stated in the op
You know...im surprised nobody has made a one click heimdal package yet...heimdal is so much better than odin imho
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mg2195 said:
Heimdall works on any platfork, mac/linux/windows...you just need java installed and your good to go, just use the command prompt instead of terminal. this was also stated in the op
You know...im surprised nobody has made a one click heimdal package yet...heimdal is so much better than odin imho
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I'm going to try this when i get home then. I just want my phone to come to life again. Crossing my fingers that this will work! Things were perfect, i don't know why restoring a nandroid and updating my kernel has caused this to become such a terrible issue.
Seems to have worked. It's hung on the AT&T logo for a couple minutes though. How long after you did this did it take to boot up the first time? I'm afraid to pull the battery and screw something up.
---------- Post added at 01:19 PM ---------- Previous post was at 01:09 PM ----------
Never mind, I rebooted to recovery and factory reset just like you said in OP and now it's booted up to the setup screen. Thanks for this man. I really needed to return to stock and didn't want to have to install Windows just to run Odin. Much appreciated!
Try doing just hidden or system, and see if those flash correctly. If they do then come back after those and flash recovery
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
housry23 said:
Seems to have worked. It's hung on the AT&T logo for a couple minutes though. How long after you did this did it take to boot up the first time? I'm afraid to pull the battery and screw something up.
---------- Post added at 01:19 PM ---------- Previous post was at 01:09 PM ----------
Never mind, I rebooted to recovery and factory reset just like you said in OP and now it's booted up to the setup screen. Thanks for this man. I really needed to return to stock and didn't want to have to install Windows just to run Odin. Much appreciated!
Click to expand...
Click to collapse
Glad this worked for you, I was struggling to find a clear method to use heimdall to repair, which is exactly why I wanted to post help for any others.
tom_callahan said:
Glad this worked for you, I was struggling to find a clear method to use heimdall to repair, which is exactly why I wanted to post help for any others.
Click to expand...
Click to collapse
Ugh...I returned to stock so that I could trade this S4 to someone on CL for a HTC One. He had no idea what CM10.1 was and so I figured it'd be best to trade him for a stock unrooted. So, I used your instructions to return to MDL. The guy flaked. Never showed up. GRRR! I kept getting bugged about the OTA, but never took it. I figured I'd just rerun CASUAL when I wake up in the morning and root it then. Well, apparently the update ran without me pressing the continue button. I'm so angry!
I wonder if this would work to roll back? Has anyone successfully rolled back to a previous firmware using Heimdall? I'd try, but I want to be sure I won't brick or mess anything up. Anyone?
InstigatorX said:
I'm getting...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
...Any advice? It looks like its uploading, fails, and reboots phone back to download mode.
Click to expand...
Click to collapse
well ive been trying to make a one click package for heimdall however i too am facing this error, ive narrowed it down to the system.img.ext4 anyone have any ideas whats going wrong?
I am also getting an issue when trying to flash hidden or system, both files claim that the computer cannot open them not sure what the problem is as i have redownloaded and checked the files to make sure all is well and can't seem to figure it out.
works great flashing the UCUAMDL firmware downloaded from Adam's thread, and using Heimdall 1.40 on Mac OS X 10.8.4
Is there a video on how to do this step by step? Im confused on how to execute commands. Or even better is there a way to do this in the front end/ using the gui of heimdall to get back to factory from a custom ROM?
PS using a Mac
white.noise said:
Is there a video on how to do this step by step? Im confused on how to execute commands. Or even better is there a way to do this in the front end/ using the gui of heimdall to get back to factory from a custom ROM?
PS using a Mac
Click to expand...
Click to collapse
I did this on a MacBook Pro running OS X 10.8.4, it was very simple and straightforward. PM if you need help after reading the instructions in the OP
mg2195 said:
well ive been trying to make a one click package for heimdall however i too am facing this error, ive narrowed it down to the system.img.ext4 anyone have any ideas whats going wrong?
Click to expand...
Click to collapse
I am also having this problem, but it is with the second line of commands ;modem.bin/NON-HLOS.bin/Aboot.mbn/tz.mbn.
It might be a bug with this release.
By the way I am running windows 7 64 bit.
tom_callahan said:
I ran into a corrupted or unaccessible /data partition several times this week, and after searching, couldn't find any tutorials on using heimdall to completely reset the phone back to stock. So... below is my version. Please provide any input on this method, it's worked a couple times with no issues for me.
FILENAMES BELOW ARE FOR ATT PHONE, if you are not ATT, use the relevant files for your carrier.
Instructions here were done on a Mac, but the programs and commands are the same on any Operating System.
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your Mac, open up Terminal, and navigate to the location you extracted the tar.md5 files to
8) In Terminal, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) sudo heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Hope this helps, any questions don't hesitate to PM me.
===================WINDOWS VERSION, by popular request================================
Instructions here were done on a Windows 7 PC
1) Download the tar.md5 firmware files from galaxys4root DOT com or any other site which has them. I used the I337UCUAMDL_I337ATTAMDL_ATT.zip file
2) Download and install heimdall latest. I can't post links yet, google heimdall and you should find the site to download it.
3) Unzip the I337UCUAMDL_I337ATTAMDL_ATT.zip file, and you should get a folder with a tar.md5 file in it.
4) Using 7zip or similar, extract the tar.md5 file. You have have to rename it to just .tar instead of .tar.md5 for this to work.
5) You will have several files now, some ext4.img, some .mbn, etc.
6) You will now reboot your phone into "ODIN" mode, by holding Volume Down when booting, just after the vibration. When prompted, hit Volume Up to begin download mode.
7) On your PC, open up a Command Prompt (Click the "start" button, and type in cmd and hit enter), and navigate to the location you extracted the tar.md5 files to
8) In the command prompt, type the following in the below order. The phone will reboot between each, you will need to repeat step 6 for each reboot.
8a) heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img
8b) heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
8c) heimdall flash --CACHE cache.img.ext4
9) When your phone reboots the last time, it may just sit on the Samsung screen and not do anything. If this happens, reboot the phone (hold down the side power button) and hold Volume Up to reboot into Recovery mode. Use volume up and down to navigate to factory reset, and the power button to select. This will reformat and clean up your data partition.
10) Reboot the phone and wait patiently. You will see all the familiar factory logos and boot into a fresh working factory firmware
Click to expand...
Click to collapse
i need help. heidmall can't open large files for example my system.img (2367450528 byte)
I recompile heidmail with -D_FILE_OFFSET_BITS=64
now it can open my system.img
but i got new error:
ERROR: Failed to confirm end of file transfer sequence!
I know that there is patch for this error.
do anybody have this patch?
I downloaded latest sources but still have this error
I don't have 64 bit pc to flash...
please help me
debug
[201.975789] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x8395014 has callback 0xb7763480
[201.975840] [00000c5b] libusbx: debug [bulk_transfer_cb] actual_length=1024
[201.975900] [00000c5b] libusbx: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 8
[201.975985] [00000c5b] libusbx: debug [libusb_submit_transfer] arm timerfd for timeout in 120000ms (first in line)
[201.976044] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[201.976097] [00000c5b] libusbx: debug [handle_events] poll() 3 fds with timeout in 60000ms
[201.984117] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[201.984242] [00000c5b] libusbx: debug [reap_for_handle] urb type=3 status=0 transferred=8
[201.984307] [00000c5b] libusbx: debug [handle_bulk_completion] handling completion status 0 of bulk urb 1/1
[201.984374] [00000c5b] libusbx: debug [handle_bulk_completion] last URB in transfer --> complete!
[201.984434] [00000c5b] libusbx: debug [disarm_timerfd]
[201.984480] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x8394c0c has callback 0xb7763480
[201.984539] [00000c5b] libusbx: debug [bulk_transfer_cb] actual_length=8
ERROR: Failed to unpack received packet.
SYSTEM upload successful
Ending session...
Same problem
InstigatorX said:
I'm getting...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
...Any advice? It looks like its uploading, fails, and reboots phone back to download mode.
Click to expand...
Click to collapse
Did you ever figure this out? I am having the same exact problem. Not sure what to do next. Any help will be appreciated!
Hi,
I was at work Sunday night when the phone offers me an update, not wanting to lose my data I re-growth that has Tuesday morning during my last round (which takes me roughly 25/30 minutes ). So I run the update and go round when I come back I have the phone on the screen of blocked boot ...
Considering I'm looking since yesterday, I have already tried many tutorials that did not work.
I tried everything flashed like to start from zero but nothing worked. I have every time a message like: failed can't install image not signed OR dtb not found ...
I have access at fastboot and nothing else.
There's way to save this phone I for 3 months or it is good to wedge a table ?
Thx in advance
edit :
ok, i do this
http://www.asus-zenfone.com/2015/10/how-to-root-asus-zenfone-2-laser-ze500kl.html
and this
http://forum.xda-developers.com/showpost.php?p=66894780&postcount=5
and i have now acces to recovery mode
Edit 2 :
http://www.asuszenfoneblog.com/2015/04/how-to-flash-asus-zenfone-2-via-adb.html with the firware Version V13.10.7.1(Andriod M) https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
but after reboot i have the message : ERROR : Can't load invalid boot image !
i lose th recovery and i can't flash the boot ( remote dtb not found ) ...
edit 3 :
the phone has restarts with the original firmware but I have so manipulated that I do not know what I did
I remember using the following links : http://www.asus-zenfone.com/2015/09/how-to-flash-asus-zenfone-2-laser.html ans the stock rom for 550KL
when I reinstall the rom of origin, such would not boot and I had to boot the mod_boot.img picture (Flashtool boot mod_boot.img), which launches the phone and now more problem. It remains to remove the root which should be easier than the rest.
@Genux888 This link takes to ZE500KL's firmware downloads https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
Your phone model is ZE550KL but you first attempted to flash MM ROM of ZE500KL
Thats why you got error: invalid boot.img and you lost recovery.
I don't know where you got mod_boot.img from. Neverthless, here's the simplest fix-
1. Download ZE550KL's Stock_boot_recovery.zip
This zip contains stock signed recovery.img and boot.img. Extract it and copy both .img files to the folder where you have adb and fastboot files.
Download correct firmware for your ZE550KL of the correct SKU. You can find your SKU on your phone's box.
WW SKU : Download ZE550KL's firmware v1.17.40.1531 for WW SKU only
Let me know if your phone's SKU is not WW
Copy the firmware zip (UL-Z00L-WW-1.17.40.1531-user.zip) to your external sd card.
2. Connect your phone to computer and Reboot phone to fastboot mode.
3. Now run the following commands
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot oem reboot-recovery
3. Third command should reboot your phone to recovery mode.
Now, in recovery mode-
A) select "wipe cache partition" then select yes
B) select "apply update from sdcard" then select "UL-Z00L-WW-1.17.40.1531-user.zip" and finally select "yes"
stuck at verifying update package
MITHI-N said:
stuck at verifying update package
Click to expand...
Click to collapse
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Hi can you put a link to OTA, I tried searching for it but could only get the full firmware from the asus website.
sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things
MITHI-N said:
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things
Click to expand...
Click to collapse
I did the following-
Input: "Wipe cache partition"
Output: E: unable to mount /asdf (invalid argument)
Input : "mount /system"
Input: "wipe cache partition"
Output: Cache wipe complete
E: unable to mount /asdf
E: Can't open /asdf/recovery/last_log
This shows that I am able to wipe cache after mounting /system (though it doesnt make sense)
I didn't wipe data as I don't want to setup my device again. You may try if wiping data works after mounting /system. Alternatively, you can flash stock 1.15's recovery (download from post #2)
and flash in fastboot mode using
Code:
fastboot flash recovery recovery.img
(assuming you recovery.img file is present in the folder where you have fastboot files)
And, here on XDA, we hit "thanks" good button if a post was helpful to us.
Sorry to reply so late but I managed to unlock my phone has put version 5.0, the update to 6.0, UNLOCK the boot, root the phone and install the TWRP may close 2 or 3 hours after my last post.
thank you.
i really like it when people post all the steps taken and links in their problem posts.
this is great.
(no, that is NOT sarcasm)
The best solution out there for zoold 550kl
This is the best answer for the rooted asus zenfone 2 550kl for upgrading to marshmellow stock .Thank you...
Help
@sziraqui My phone is in a bootloop and I honestly know pretty much nothing as to how to fix it.. I know it's the ZE551KL, but that's pretty much it. Is there any way youcan help me out? thanks in advance
Stock recovery for MM?
Anyone have stock recovery for MM upgrade from LP?
Problem Not Solved
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
I've seen you've tried a lot.
I'd suggest you try this... As long as you can send your phone to fastboot and can pc/add your way through you'll be able to unbrick it. This takes a bit of time as you'll be dealing with two huge downloads (system.img and stock rom) but it should do the trick.
Follow the guide here:
https://www.asus.com/zentalk/thread-80274-1-1.html
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
utkarshdev20 said:
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
The guide at https://www.asus.com/zentalk/thread-80274-1-1.html talks about flashing boot.img first then a huge (1.7GB) system.img second then recovery.img last.
So it could mean the boot.img and system.img needs to be dealt with first before you have any chances of getting your recovery to work.
Follow the steps closely, I've been able to fix a brick with it twice.
NO way to boot into Recovery or Fastboot!!!!!!!!!!!!!
Phone got bricked!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
When connected to PC(Windows), I only get 8 local disk partitons (ext4) asking to format!!!!!!!!!!!
And one with image partition(BOOT)
What to do now to regain access to either fastboot or to recovery!!!!!!!!!!!!!!!!!
PLEASE Reply!!!!!!!!!!!!!!!!!!
utkarshdev20 said:
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
I can help you but first i neef some info about your phone..how it got bricked?was your phone rooted?
Hi,
I made this post/thread because i couldn't find a solution to my problem through this forum and google.
Here is my trouble:
I was trying to install a twrp recovery and was following the instructions of a tutorial.
-So first i installed flashify and proceeded to a back up of the current kernel and current recovery
-Then downloaded a custom recovery image through TWRP release for my nexus 4
-After this i accidentally flashed the recovery image to boot instead of recovery
Now as you can guess the trouble is that my phone only boots to TWRP recovery instead of usual boot.
I tried to find aswers on this forum and google and yet i didn't find a solution.
I tried this post but without results:
http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
I would be grateful for any help and wish to recover this mistake without using a factory reset if possible.
Thank you, as you can see i am pretty new to this environment.
Can you get into fastboot mode? If yes, try flashing a stock Google rom and perform a factory wipe after installing the stock rom.
audit13 said:
Can you get into fastboot mode? If yes, try flashing a stock Google rom and perform a factory wipe after installing the stock rom.
Click to expand...
Click to collapse
Thank you for your answer, yes i can get into fastboost mode. As i am pretty new can you explain me how i can flash the stock Google rom (i guess it is the factory rom provided ?). Will this operation erase my data on the phone ?
Boot into fastboot and flash boot.img and recovery.img file from stock rom. Make sure you use the stock rom that matches the rom currently installed on your phone.
Ilovkos said:
Thank you for your answer, yes i can get into fastboost mode. As i am pretty new can you explain me how i can flash the stock Google rom (i guess it is the factory rom provided ?). Will this operation erase my data on the phone ?
Click to expand...
Click to collapse
Once in fastboot, extract the downloaded zip you got from Google. There you will find flash-all.bat Execute it as admin and wait. If it doesn't work, then extract the zip within the first zip and you should get loads of .img files. You will manually have to flash them. The commands are a bit different for each partition. They go like this:
Code:
fastboot flash system system.img
fastboot flash recovery recovery. img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash data userdata.img
Note that if your cmd/terminal isn't open from the directory where the files are you will have to input it's location, for example
Code:
fastboot flash recovery C:\Users\YOURUSER\Desktop\recovery.img
Also note that there must be no spaces neither in the file name or the directories where the file is located, otherwise it probably won't flash.
Also yes, doing this will completely revert you to stock, and you WILL loose all your data. You could try just reflashing recovery.img and then flashing TWRP over it. If you can get to TWRP after this, then connect the USB cable to your PC and transfer all the data you need, after which I recommend flashing to stock. You can root and/or flash custom ROMs after this.
However in your case I think you don't have to completely go back to stock. Just try flashing the proper boot and recovery images over fastboot like I explained above and try booting then.
nerotNS said:
Once in fastboot, extract the downloaded zip you got from Google. There you will find flash-all.bat Execute it as admin and wait. If it doesn't work, then extract the zip within the first zip and you should get loads of .img files. You will manually have to flash them. The commands are a bit different for each partition. They go like this:
Code:
fastboot flash system system.img
fastboot flash recovery recovery. img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash data userdata.img
Note that if your cmd/terminal isn't open from the directory where the files are you will have to input it's location, for example
Code:
fastboot flash recovery C:\Users\YOURUSER\Desktop\recovery.img
Also note that there must be no spaces neither in the file name or the directories where the file is located, otherwise it probably won't flash.
Also yes, doing this will completely revert you to stock, and you WILL loose all your data. You could try just reflashing recovery.img and then flashing TWRP over it. If you can get to TWRP after this, then connect the USB cable to your PC and transfer all the data you need, after which I recommend flashing to stock. You can root and/or flash custom ROMs after this.
However in your case I think you don't have to completely go back to stock. Just try flashing the proper boot and recovery images over fastboot like I explained above and try booting then.
Click to expand...
Click to collapse
Thanks to both of you I managed to fix this just by flashing the boot.img of the Google factory img. It didn't erase my data except my messages which is nice.
Hi, I want to revert at stock ROM (SM-G935F) but, I'm on MAC. JOdin doesn't work, well I can start it, connect it but saying files are corrupt. Now, since I don't have a Win machine, I want to use Heimdall to flash stock ROM.
I unpacked the files but, from what I've read over the internet, more files would be required....
Atm, I can flash only these:
Code:
heimdall flash --CM cm.bin --PARAM param.bin --BOOTLOADER sboot.bin --RADIO modem.bin --CP_DEBUG modem_debug.bin --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img
Is this enough to revert to stock, if not, from where I can get the other files since are not in the archive from sammobile (after unpacking & unpacking & unpacking ... )
Thanks
PS: If any have a stock ROM (SM-G935F - galaxy s7 edge, UK unbranded) - that can be flashed with TWRP would be fantastic (deodexed or without bloatware or normal - doesn't matter).
So, I took a leap of faith and run the command. There were no issues, all steps were completed with success.
After Heimdall reboots your phone, you'll get a "No Command" screen. Wait there, will reboot automatically in the bootloader (the original one). Factory reset, purge cache, reboot. Welcome to stock android w/o Odin.
Mods: please close this. Thanks
f100019507 said:
Mods: please close this. Thanks
Click to expand...
Click to collapse
Thread closed as you requested.