I have TWRP'd my MK2 build SGH-i337. Which now as i am reading kills recovery on the locked bootloader.
I have seen a bunch of threads getting people odin'd back to MF3 using the MF3.tar file, but i have tried this and it fails every time. I am guessing from what i am reading that i cant go back to MF3. Is there a mk2 stock tar file i can odin? I cant ADB or flash via recovery, at this point Odin seems to be my only option for interaction with the phone.
I have also seen people taking these phones up to Best Buy to use SMART tool from Samsung. Is this my only hope? This is my work phone and kinda feeling a little regretful at the moment, so can anyone can confirm my options at this point?
I know this is similar to previous posts about mf3 twrp'd phones but i didn't see anything about mk2, so sorry in advanced if this is to similar and i am missing something.
Follow These Instructions
Follow these instructions.
skip the MJ9 sideload update part and replace with the at&t full mk2 update file. Search the forums for it. :good:
http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
---------- Post added at 03:54 PM ---------- Previous post was at 03:36 PM ----------
joshzdad2013 said:
Follow these instructions.
skip the MJ9 sideload update part and replace with the at&t full mk2 update file. Search the forums for it. :good:
http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
Click to expand...
Click to collapse
Here is more info on the MK2 update file.
http://forum.xda-developers.com/showpost.php?p=47998793&postcount=819
I was able to get to recovery
I am at recovery now but still do not see a full mk2 update. There is the update file for 4.3 i tried to side load that but received E:Error in //tmp/update.zip (status 7).
Is this the mk2 file you are referring to it is about 700 meg? I couldn't find anyone with a full stock mk2. Any suggestions from here?
Yes its the 700 meg one. Side load that. It worked for me. Put it on your sd card then in stock recovery sise load from external sd.
Clarification
Are you wanting me to do this with these fix files?
Download and extract the following files...
mf3-emergency-part-1.tar.md5.7z
mf3-emergency-part-2.tar.md5.7z
And then these steps with the mk2 instead of mj9 update file instead?
Start Odin, connect your phone and boot into Download mode.
Flash mf3-emergency-part-1.tar.md5 which contains modem.bin, NON-HLOS.bin and system.img.ext4.
The flash of system.img.ext4 WILL FAIL at the end. That's OK.
Reboot the phone back into Download mode and restart Odin.
Flash mf3-emergency-part-2.tar.md5 which contains cache.img.ext4.
The flash WILL FAIL at the end. That's OK.
The phone should now reboot to recovery by itself and apply a small update. If it fails, stop and report.
The phone should now reboot to a black screen with the pulsing notification LED.
Reboot into recovery mode and flash mk2update.zip. I recommend sideloading instead of flashing from sdcard because the sdcard method reboots the phone whether the update was successful or not and you lose the error messages.
Reboot the phone and let it initialize.
You should now have MK2.
Yes
---------- Post added at 07:10 PM ---------- Previous post was at 07:00 PM ----------
Just make sure your flashing that 700mb file its the full mk2 update.
I'm stuck in the same boat after TWRP....will only boot to odin. No recovery, if I try it ony goes to a screen where it says to hook it up to Kies and update firmware that way(doesn't work though because Kies tries to download MDL). Will not be able to attempt this method til I get home from work so I'm staying glued to this post in the meantime. Appreciate the updates!
What version of Odin are you using? I have the same problem and cant get past emergency part 2. Phone does not auto reboot after cache flash.
sl1200md3 said:
What version of Odin are you using? I have the same problem and cant get past emergency part 2. Phone does not auto reboot after cache flash.
Click to expand...
Click to collapse
I used Odin 1.85
joshzdad2013 said:
I used Odin 1.85
Click to expand...
Click to collapse
Same here. Thanks. Phone is still stuck after flashing mf3-emergency-part-2.tar. I try and manually reboot and it takes me back into Odin mode.
After flashing mf3-emergency-part-2.tar, phone hangs and says:
Odin Mode
Product Name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: enabled
Start [224,1440]
Bar [240,1440]
Secure Check Fail: cache
Just keep trying again, re-read the main post above. I literally sid it 3 times and it finally worked. I just kept reading thru the post till I found good info. Its in there ya just gotta find it.
Great Success Back at Stock!
I have gotten back to the stock from directions from gtj0, but big thanks to joshzdad2013 for leading me in the right directions :laugh::good:
Using Odin 3.07, I followed the directions except using the mk2 file 2400258.zip in the final adb sideload.
MK2 file
http://forum.xda-developers.com/show...&postcount=819
Also i forced reboot after step 6 by resetting odin and unplugging phone and plugging back in, then i just odin'd this file from this link
http://forum.xda-developers.com/showthread.php?t=1766399 Not sure if this helped any, but after forcing the reboot with the blank tar file it came back up in recovery and forced a small update. I then just used adb.exe to side load the 2400258.zip file after putting phone in adb sideload mode.
:good::good::good:
kevinpc said:
I have gotten back to the stock from directions from gtj0, but big thanks to joshzdad2013 for leading me in the right directions :laugh::good:
Using Odin 3.07, I followed the directions except using the mk2 file 2400258.zip in the final adb sideload.
MK2 file
http://forum.xda-developers.com/show...&postcount=819
Also i forced reboot after step 6 by resetting odin and unplugging phone and plugging back in, then i just odin'd this file from this link
http://forum.xda-developers.com/showthread.php?t=1766399 Not sure if this helped any, but after forcing the reboot with the blank tar file it came back up in recovery and forced a small update. I then just used adb.exe to side load the 2400258.zip file after putting phone in adb sideload mode.
:good::good::good:
Click to expand...
Click to collapse
That's awesome. . I managed to get the force reboot trick to work at Step 6. Now I'm at the blank screen flashing LED phase (Step 8). Better progress than where I was before, but I still cannot boot into recovery. I'll keep trying.
sl1200md3 said:
That's awesome. . I managed to get the force reboot trick to work at Step 6. Now I'm at the blank screen flashing LED phase (Step 8). Better progress than where I was before, but I still cannot boot into recovery. I'll keep trying.
Click to expand...
Click to collapse
Try flashing the recovery again after doing the emergency TAR's. I had to do that in order to fix mine, and then it restored nicely.
DeadlySin9 said:
Try flashing the recovery again after doing the emergency TAR's. I had to do that in order to fix mine, and then it restored nicely.
Click to expand...
Click to collapse
Thanks! :good: That got me back into Recovery mode. Now I'm getting Signature Verification Failed / Installation Aborted when I try and adb sideload this file http://forum.xda-developers.com/showpost.php?p=47998793&postcount=819 (2400258.zip) Looks like a bad download. Tried it twice.
I'm gonna try this file I found here http://forum.xda-developers.com/showthread.php?t=2573080 and see if that will work. DL is taking forever...
Nope. Both links didn't work. I'm also getting a CRC check error on both files if I try and unzip. Unexpected end of archive. Anyone know where I can get a good MK2 update file??
Got home and started with the instructions....flashed the first recovery-mj6.tar.md5 and the phone booted back up normally! I imagine that if I try to boot to recovery it'll soft brick again. Gonna leave it like this for now til the wife gets home and then see what happens.
SUCCESS!
Back on AT&T STOCK MK2 from a bricked TWRP'd install. I had to do the following:
1) Phone into download mode
2) Flash mf3-emergency-part-1.tar.md5 via Odin v1.85
3) Force Reboot
4) Flash mf3-emergency-part-2.tar.md5
5) Unplug phone / Reset Odin / plug phone back in
6) Flash recovery-mj6.tar.md5
7) Force Reboot in Odin using this file http://forum.xda-developers.com/showthread.php?t=1766399 Thanks kevinpc :good:
8) Manually enter recovery
9) ADB Sideload the file: update-mf3-mj9.zip found here: http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
10) ADB Sideload the file: update-MJ9-MK2.zip found here: https://docs.google.com/file/d/0B2iXrnZBB-MVYkYwNkYzU2FJaFk/edit
11) Reboot
Won't be flashing TWRP via Goo Manager again any time soon.
:good::good::good:
sl1200md3 said:
Back on AT&T STOCK MK2 from a bricked TWRP'd install. I had to do the following:
1) Phone into download mode
2) Flash mf3-emergency-part-1.tar.md5 via Odin v1.85
3) Force Reboot
4) Flash mf3-emergency-part-2.tar.md5
5) Unplug phone / Reset Odin / plug phone back in
6) Flash recovery-mj6.tar.md5
7) Force Reboot in Odin using this file http://forum.xda-developers.com/showthread.php?t=1766399 Thanks kevinpc :good:
8) Manually enter recovery
9) ADB Sideload the file: update-mf3-mj9.zip found here: http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
10) ADB Sideload the file: update-MJ9-MK2.zip found here: https://docs.google.com/file/d/0B2iXrnZBB-MVYkYwNkYzU2FJaFk/edit
11) Reboot
Won't be flashing TWRP via Goo Manager again any time soon.
:good::good::good:
Click to expand...
Click to collapse
Went ahead and completed using this method. PERFECT! Can't thank all of you enough!:good::good:
You guys are all lifesavers. This is gonna teach me to be more careful when flashing roms.
Related
I managed to be get rooted by following this.
For some reason, I am have been completely unable to do anything via Odin, but the above method ended up working for some reason (I had to execute the .jar from my C:\ drive though).
In a moment of idiocy, I chose the "Advanced Wipe" option under "Wipe" from the homescreen menu in TWRP and wiped my System directory. I think that this effectively wiped my OS, so I have nothing to boot into (it gets stuck at the "Samsung Galaxy S4" logo).
I have and can still access TWRP recovery, I can send ADB commands--but I do not believe that TWRP allows me to 'push' anything and I have not had any success with 'sideloading'. Some ADB commands leave me hanging at "< waiting for device >". I attempted to install custom ROMs by putting the install .zips onto my external SD and having TWRP install them, but I keep getting failures. I can access download mode, but Odin (v. 1.85, 3.04, 3.07) doesn't want to cooperate with me and all it says is a write failure. No PIT errors, I unchecked everything except " Auto Reboot", PDA mode, I tried all combinations of installing and re-installing Kies with drivers and rebooting my PC, plugging and unplugging my device into front and rear USB ports with different OEM cables, killing Kies/ADB processes via task manager and starting Odin at various points in the process (before and after I plug in my device or press up on the volume rocker to enter download mode). Please let me know if there's any more Odin hocus-pocus I haven't tried.
I was hoping that Kies->Tools->Firmware Upgrade and Initialization would work, but when I entered my S/N it said that initialization was not available for my device.
I'm at my wit's end, at this point; I would welcome someone telling me that I haven't completely bricked my device beyond all repair. I want to blame TWRP for not being able to install a ROM from a .zip. I have attached a recovery log from TWRP.
It seems you have problem in partition table. Did you flash pit file with the firmware in odin?
Sent from my Galaxy using xda premium
I had the same problem when I once had my S3 and I assume it'll be the same. In TWRP mount your storage and move a random rom on to your phone.
samersh72 said:
It seems you have problem in partition table. Did you flash pit file with the firmware in odin?
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
I think you are right about the partition problem, because that is what TWRP is telling me. I didn't flash a pit file in Odin with firmware. Am I supposed to?
Shivammcool said:
I had the same problem when I once had my S3 and I assume it'll be the same. In TWRP mount your storage and move a random rom on to your phone.
Click to expand...
Click to collapse
I was hoping that this would be the solution, but TWRP gives me a partition error. I will definitely re-attempt this once I can resolve that issue.
ncovey said:
I think you are right about the partition problem, because that is what TWRP is telling me. I didn't flash a pit file in Odin with firmware. Am I supposed to?
Click to expand...
Click to collapse
ya, flash the appropriate pit file WITH the firmware, check F.reset, auto reboot, and re-partition (they will be ticked by default).
see my sig for pit file if you dont have it
---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------
wait.... you have the I9505 or the I545 (verizon)???
if I545 then here is the pit http://forum.xda-developers.com/showthread.php?t=2290859
Edit: i check pit files.... they are the same :good:
samersh72 said:
ya, flash the appropriate pit file WITH the firmware, check F.reset, auto reboot, and re-partition (they will be ticked by default).
see my sig for pit file if you dont have it
---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------
wait.... you have the I9505 or the I545 (verizon)???
if I545 then here is the pit http://forum.xda-developers.com/showthread.php?t=2290859
Edit: i check pit files.... they are the same :good:
Click to expand...
Click to collapse
I am downloading one of the official firmwares. Is it possible to install it through my SD card if I can't get ODIN to flash it?
I tried installing the pit file, but I get the "SECURE CHECK FAIL : PIT" error on my S4's display.
I am worried that even though I managed to get rooted through Loki's exploit (I think that's what CASUAL or motochopper uses) the exploit that was pushed to my phone was wiped from it. I have the AT&T GT-I9505, so it definitely has a locked bootloader. I'm not giving up yet though.
Now it's definitely bricked.
Well, I couldn't do any of the methods described above because no manner of Odin'ing got me anywhere except "SECURE CHECK FAIL : " for recovery, boot, kernel, pit, etc.
so i attempted to do adb commands to see the extent of what i could do:
Code:
dd if=i9505-cwm-recovery-6.0.3.2-4.tar of=/dev/block/mmcblk0p21
from here
I should have known that you cannot install a .tar instead of a .img... :crying:
So now there is no recovery. And it only boots into download mode with a message at the top that says: "Could not do normal boot."
Unfortunately under "CURRENT BINARY:" it says "Custom" so I'm fairly certain that AT&T will not do a warranty replacement.
Hooray for popping my brick cherry!
EDIT: since the only way I was able to ADB before was in recovery mode... now that I've fubar'd my recovery... no ADB
EDIT 2: I've only had this phone for ~55 hours, so I think I can still have it exchanged for a restocking fee from AT&T. According to this and this
EDIT 3: I went to the AT&T store, and I was naive to think that they wouldn't turn it on. When the salesperson saw the "unauthorized software" message, she asked if I had attempted to "jail-break" my phone lol. She wanted to factory reset it from recovery mode, but obviously that didn't work. She said, "I am not sure we can accept this, and my inventory manager would kill me if we got back a device like this." She ended asking me to come in tomorrow to talk to the manager. I am very, very certain this will NOT result in me getting a new device.
Also, I realize that in this post whenever I've said "brick" I was not using the term correctly, as I can still turn it on. My mistake.
can you tell me the exact product number (i337 or i9505....) and what is the firmware that you are trying to install?
Hi
I need a help. I was flashed by odin new KitKat rom from samsung website after passed phone restart and stuck on Recovery booting. I cant get any download mode or recovey still this same - only samsung Galaxy note 3 logo and blue info on top"Recovery Booting..." Please help me.
Think I have the same issue.
Followed the guide as quoted in this post; http://forum.xda-developers.com/showpost.php?p=49438067&postcount=402
Downloaded from post; http://forum.xda-developers.com/showpost.php?p=49448237&postcount=443
Can't boot into download mode and it doesn't connect to PC. Just stuck saying "Recovery Booting..."
Edit: I can boot into download mode. Trying the same guide again.
Edit 2: Second flash worked.
sylwek23111 said:
Hi
I need a help. I was flashed by odin new KitKat rom from samsung website after passed phone restart and stuck on Recovery booting. I cant get any download mode or recovey still this same - only samsung Galaxy note 3 logo and blue info on top"Recovery Booting..." Please help me.
Click to expand...
Click to collapse
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Thank you both for help. I fixed. Now i have kitkat with root but is another problem about cwm recovery. I was flashed by odin 6.0.4.5 and was successful but not working on my phone i cant get in. Always when i pressing tree buttons is "RECOVERY BOOTING" and restarting phone and booting system normal. Any advice?
sylwek23111 said:
Thank you both for help. I fixed. Now i have kitkat with root but is another problem about cwm recovery. I was flashed by odin 6.0.4.5 and was successful but not working on my phone i cant get in. Always when i pressing tree buttons is "RECOVERY BOOTING" and restarting phone and booting system normal. Any advice?
Click to expand...
Click to collapse
I found problem. i was flashing cwm 6.0.4.5 but i should 6.0.4.6 now everything fine.:laugh:
sylwek23111 said:
I found problem. i was flashing cwm 6.0.4.5 but i should 6.0.4.6 now everything fine.:laugh:
Click to expand...
Click to collapse
Good news. :good:
orange_dutchman said:
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Click to expand...
Click to collapse
thanks for your help, i thought that i will send my note 3 to claim warranty at tomorrow. My phone just stuck at the "recovery booting" after failed in flashing the rom with mobile odin pro.
Nightmare79 said:
Think I have the same issue.
Followed the guide as quoted in this post; http://forum.xda-developers.com/showpost.php?p=49438067&postcount=402
Downloaded from post; http://forum.xda-developers.com/showpost.php?p=49448237&postcount=443
Can't boot into download mode and it doesn't connect to PC. Just stuck saying "Recovery Booting..."
Edit: I can boot into download mode. Trying the same guide again.
Edit 2: Second flash worked.
Click to expand...
Click to collapse
im note able to boot into download mode any help
---------- Post added at 12:50 AM ---------- Previous post was at 12:28 AM ----------
orange_dutchman said:
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Click to expand...
Click to collapse
thanks you saved me
HELP!!!!
I JUST TRIED TO JAILBREAK MY PHONE USING CF-Auto-Root-hltetmo-hltetmo-smn900t.zip AND NOW MY PHONE IS STUCK IN RECOVERY MODE. I TOOK THE BATTERY OUT AND TRIED TO BOOT IT UP NORMALLY AND IT WON'T ALLOW ME TO. :crying: WHAT DO I DO????
jmanciaz said:
I JUST TRIED TO JAILBREAK MY PHONE USING CF-Auto-Root-hltetmo-hltetmo-smn900t.zip AND NOW MY PHONE IS STUCK IN RECOVERY MODE. I TOOK THE BATTERY OUT AND TRIED TO BOOT IT UP NORMALLY AND IT WON'T ALLOW ME TO. :crying: WHAT DO I DO????
Click to expand...
Click to collapse
Reflash stock firmware with Odin and after that data reset, then find a custom recovery like this one http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltetmo and flash it with Odin and flash the latest superSU.zip in recovery and you`re rooted.
Guys, I have a problem
I was stuck on recovery rebooting and now i'm on download mode and have problem with uploading stock rom
Odin 1.85 Says "Write operation failed"
On the screen i have "WTITE PROTECTION: ENABLE
And - after "Start" of flashing
"UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2"
please help!
konradciok said:
Guys, I have a problem
I was stuck on recovery rebooting and now i'm on download mode and have problem with uploading stock rom
Odin 1.85 Says "Write operation failed"
On the screen i have "WTITE PROTECTION: ENABLE
And - after "Start" of flashing
"UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2"
please help!
Click to expand...
Click to collapse
What were you trying to do before you get this error?
hey_joe said:
What were you trying to do before you get this error?
Click to expand...
Click to collapse
I was trying to flash custom rom (alexandr) with mobile odin. But first i made CF Auto-Root
Now I have nothing but stock recovery N9005_Stock_Recovery_KK.tar.md5
Phone is rebooting on logo Samsung Galaxy Note 3.
I have access to downlowad mode and to this recovery. And now i don't now what to do...
konradciok said:
Guys, I have a problem
I was stuck on recovery rebooting and now i'm on download mode and have problem with uploading stock rom
Odin 1.85 Says "Write operation failed"
On the screen i have "WTITE PROTECTION: ENABLE
And - after "Start" of flashing
"UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2"
please help!
Click to expand...
Click to collapse
Write the stock 4.4 ROM for your phone in normal Odin.
konradciok said:
I was trying to flash custom rom (alexandr) with mobile odin. But first i made CF Auto-Root
Now I have nothing but stock recovery N9005_Stock_Recovery_KK.tar.md5
Phone is rebooting on logo Samsung Galaxy Note 3.
I have access to downlowad mode and to this recovery. And now i don't now what to do...
Click to expand...
Click to collapse
I suggest you do the following;
First boot into stock recovery and do a factory reset, reboot and see if it boots up to android.
If that doesn't work, you can either odin a custom recovery like TWRP or CWM. Make sure you flash the latest one for KK as I've seen lots of people flashing one for 4.3 when they have a 4.4 bootloader.
Lastly, you can odin the stock firmware for your phone which can be downloaded off sammobile.
orange_dutchman said:
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Click to expand...
Click to collapse
Thank you for saving my life, I love you man :laugh:
Thanks!!! Although this tutorial is for a note3 I follow all your recommendations, applied to my note4, and now my phone is working again.
Need help
Hello need help here,
I'm being dumb and fail to root my phone
I try to root my galaxy note 3 by following the step on http://forum.xda-developers.com/galaxy-note-3#root
I downloaded CF-Auto-Root-hlte-hltexx-smn9005 and kies3
However after using odin with check on PDA which is linked to the file in the zip called CF-Auto-Root-hlte-hltexx-smn9005.tar.md5
and check on auto reboot
in odin, it says that my root has pass within 13s
BUT
my device keep looping afterward and
show
Recovery Rebooting....
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
and then turned off
and then show that again
and turn off and show that again and soo on
I tried : removing battery and put it back in, it autoboot even without me pressing the power button and it goes showing above message again.
i tried to press the volume down+home+power button, nothing changed
I desperately need help here
any help is appreciated.
orange_dutchman said:
Don t panick. I did that already... You need to disconnect the cable and take out the battery. Then you press on the 3 buttons for a while (to empty the note completely) and put the battery back in. When you press the 3 buttons again it should be in download mode again.
To me it happened i think due to the fact i didn't tick update boot loader in odin 1.85. After ticking it and flashing no problem any more. Good luck
Click to expand...
Click to collapse
i tried this process which you told but also my samsung galaxy mega lte I9205 stucks on recovery booting. is there any other idea to fix it.
i have samsung galaxy mega lte I9205. i updated it to the new version of kitkat by odin. it became passed but after flashing the rom whenever i open my phone it says recovery booting on the left at the top and frequently gets switch off and opens again and again. i ticked on bootoader update on odin also but it dint fixed the problem. is there any idea to fix it.
This is the first time I'm rooting my phone. Process went smooth upto granting Super user excess to RashR (Flash Tool). And Download Philz Recovery Zip. After that I can only see Samsung Logo. Please Help!
PS: It's not going into Recovery Mode.
What S5 variant do you have and what version of Android are you running?
InsanePostman said:
What S5 variant do you have and what version of Android are you running?
Click to expand...
Click to collapse
G900H. Lollipop. I used Odin with this file - CF-Auto-Root-k3g-k3gxx-smg900h.tar (the process I used for rooting). It has come out of boot sleep. When I'm trying to go into recovery mode, it gets stuck at Logo. My phone is working right now but doesn't go into recovery mode. Can you help me solve this? I want to try Marshmallow. Thanks!
make sure the MD5 hash matches, if you don't know how to hash MD5 look it up, if it fails just redownload the recovery tar because your download was corrupted
---------- Post added at 02:48 PM ---------- Previous post was at 02:48 PM ----------
and don't use download managers
complexiscool said:
G900H. Lollipop. I used Odin with this file - CF-Auto-Root-k3g-k3gxx-smg900h.tar (the process I used for rooting). It has come out of boot sleep. When I'm trying to go into recovery mode, it gets stuck at Logo. My phone is working right now but doesn't go into recovery mode. Can you help me solve this? I want to try Marshmallow. Thanks!
Click to expand...
Click to collapse
Try to flash TWRP recovery
Use ODIN to flash recovery, not some flash tool from G Play, it might have flashed the wrong version recovery
With ODIN, you do it manually, so if you flash the wrong version, it's because you didn't check it first, not because you let some random app do it for you
*Detection* said:
Use ODIN to flash recovery, not some flash tool from G Play, it might have flashed the wrong version recovery
With ODIN, you do it manually, so if you flash the wrong version, it's because you didn't check it first, not because you let some random app do it for you
Click to expand...
Click to collapse
Hi,
Can you please refer a link which I can follow. I followed steps from a youtube video(with a good number of likes and views) which lead to this. I've zero experience in rooting and all. Any help will be highly appreciated. Thanks!
complexiscool said:
Hi,
Can you please refer a link which I can follow. I followed steps from a youtube video(with a good number of likes and views) which lead to this. I've zero experience in rooting and all. Any help will be highly appreciated. Thanks!
Click to expand...
Click to collapse
Loads of guides kicking about here in the S5 forum
Basically grab TWRP 2.8.7.0 .TAR for your model S5, load it into the AP or PDA section of ODIN, put your phone in download mode (Vol down & Home & Power from a powered off state), connect phone to PC USB, make sure drivers are installed, then hit start on ODIN
It should start the flashing process, and say success once done
*Detection* said:
Loads of guides kicking about here in the S5 forum
Basically grab TWRP 2.8.7.0 .TAR for your model S5, load it into the AP or PDA section of ODIN, put your phone in download mode (Vol down & Home & Power from a powered off state), connect phone to PC USB, make sure drivers are installed, then hit start on ODIN
It should start the flashing process, and say success once done
Click to expand...
Click to collapse
I tried using Odin and nothing happened. Tried using TWRP Manager. Getting this error - "Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?"
complexiscool said:
I tried using Odin and nothing happened. Tried using TWRP Manager. Getting this error - "Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?"
Click to expand...
Click to collapse
What do you mean, nothing happened with ODIN?
Did you add the TWRP .TAR (Do not extract)?
Phone was in download mode?
Drivers were installed?
Could ODIN see the phone? Did it show the COM port at the top?
*Detection* said:
What do you mean, nothing happened with ODIN?
Did you add the TWRP .TAR (Do not extract)?
Phone was in download mode?
Drivers were installed?
Could ODIN see the phone? Did it show the COM port at the top?
Click to expand...
Click to collapse
1. I meant when I clicked on Start, a blue bar came in download mode, and phone restarted.
2. Yes
3. Yes
4. Yes
complexiscool said:
1. I meant when I clicked on Start, a blue bar came in download mode, and phone restarted.
2. Yes
3. Yes
4. Yes
Click to expand...
Click to collapse
OK, a common problem
Uncheck the "Auto reboot" setting in ODIN
When it's finished flashing, unplug the phone and pull the battery out of the phone, replace it, and boot straight into recovery with vol up, Home and Power
Today i was trying to install the Android Marshmallow 6.0.1 on my Galaxy S5 Snapdragon via Odin, i downloaded the firmware from Sammobile, i verified that the phone model was exactly the same as named on the firmware, i place the .md5 file in the AP slot and everything was ready to go! (The phone was already plugged and in Bootloader mode, and drivers were up to date) then when finishing the flash Odin FAILS to complete the flash and the phone is left with nothing than the Download mode, i panic and try to access recovery mode but realize that there´s no recovery....I proceed to install the recovery.tar into my phone and it works, i start the phone and Samsung logo comes up, finally it loads and does al the process after you flash a Samsung phone.
Everything works just fine!...except for one thing, THERE´S NO RECOVERY!!!. The phone works perfectly but when i try to enter recovery mode, it sends me to Odin mode as it displays a message saying that failed to boot into recovery.
Please help me i don´t know what to do.
Thanks!
Just flash a custom recovery like twrp or cwm
Already did...same problem, recovery won't boot
adavicco said:
Already did...same problem, recovery won't boot
Click to expand...
Click to collapse
You need to flash a pit file to complete the install correctly.
Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!
Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.
SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there
Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?