Related
Q&A for Firmware-Only_Odin_Flashable_ Images_For_4.4.. And_5.0_Roms_Updated_12_2_14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Firmware-Only_Odin_Flashable_ Images_For_4.4.. And_5.0_Roms_Updated_12_2_14. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
odd
first off what is; non-hlos
(explain in post 1 for new users also please)
Ok i tried to flash NKD on Cyanogenmod 11.0 build 121214 but it refuses to go.
running the latest teamwin recovery project twrp 2.8.3.0 klte
am i missing something?
Ok so i want to odin the new lolllipop im in nk4. But if i want to go back to nk4 i flash one these in odin? Than i can flash nk4 full tar in odin?
Anyone know of a zip to get back to kit Kat firmware? I used one to get to lollipop because my computer sucks and it's way easier. Not really sure why this method isn't used more.
jtadak said:
Anyone know of a zip to get back to kit Kat firmware? I used one to get to lollipop because my computer sucks and it's way easier. Not really sure why this method isn't used more.
Click to expand...
Click to collapse
Try this post
http://forum.xda-developers.com/sprint-galaxy-s5/development/stock-rom-ni3-kitkat-rom-t2886171
CAJUNMIKE said:
Try this post
http://forum.xda-developers.com/sprint-galaxy-s5/development/stock-rom-ni3-kitkat-rom-t2886171
Click to expand...
Click to collapse
Thank you but I'm looking for a zip to get to the nk4 bootloader.
jtadak said:
Thank you but I'm looking for a zip to get to the nk4 bootloader.
Click to expand...
Click to collapse
Right within the OP of that thread is
Full bootloaders:
4.4.2 - [LINK][ROM][ODIN][TAR]SM-G900P NE5 (NE5 Modem/Kernel/ROM - Stock)
4.4.4 - G900PVPU1ANK4_G900PSPT1ANK4_SPR.zip
CAJUNMIKE said:
Right within the OP of that thread is
Full bootloaders:
4.4.2 - [LINK][ROM][ODIN][TAR]SM-G900P NE5 (NE5 Modem/Kernel/ROM - Stock)
4.4.4 - G900PVPU1ANK4_G900PSPT1ANK4_SPR.zip
Click to expand...
Click to collapse
Wow! That's what I get for reading while at work. Thanks for not blowing up. Haha
G900PVPU2BOD3 added Factory Reset Protection
Bootloaders are locked to BOD3 after upgrading, meaning all the BOA6 stock images are now unusable. I've been stuck using the MOAR rom since the update came out and can't go back to stock, along with a ton of other people. Now I guess we wait for someone to post a BOD3 stock image.
Many aplogies for my ignorance but I am running out of ideas. I wanted to try out Cyanogenmod 12.1 so I flashed philztouch recovery using ODIN and installed the latest CM 12.1 zip from official cyanogenmod download. I did take a backup prior to flashing CM however now I am unable to restore from the backup, it says it is not valid (!!!???).
Can someone please tell me how to get the my sprint GS5 back to completely stock; I don't need root anymore or custom recovery or any of that, I just want it back to how it was when I opened the box. I have all my pics/messages backed up so I am not afraid to wipe it completely. If someone can point me to a file to download and flash in ODIN or whatever needs to be done I will do it. If you need any information from my phone I will gladly provide it.
Please help, thanks!
ej72 said:
Many aplogies for my ignorance but I am running out of ideas. I wanted to try out Cyanogenmod 12.1 so I flashed philztouch recovery using ODIN and installed the latest CM 12.1 zip from official cyanogenmod download. I did take a backup prior to flashing CM however now I am unable to restore from the backup, it says it is not valid (!!!???).
Can someone please tell me how to get the my sprint GS5 back to completely stock; I don't need root anymore or custom recovery or any of that, I just want it back to how it was when I opened the box. I have all my pics/messages backed up so I am not afraid to wipe it completely. If someone can point me to a file to download and flash in ODIN or whatever needs to be done I will do it. If you need any information from my phone I will gladly provide it.
Please help, thanks!
Click to expand...
Click to collapse
You will need one of the full factory tars available from the development thread.
And I've read somewhere that you may need to wipe internal storage coming from CM so backup what you want to save.
Just a warning, if you flash anything newer than OA6, you will not be able to flash back to older firmwares.
http://forum.xda-developers.com/sprint-galaxy-s5/development
tdunham said:
You will need one of the full factory tars available from the development thread.
And I've read somewhere that you may need to wipe internal storage coming from CM so backup what you want to save.
Just a warning, if you flash anything newer than OA6, you will not be able to flash back to older firmwares.
http://forum.xda-developers.com/sprint-galaxy-s5/development
Click to expand...
Click to collapse
I'm getting confused with the different requirements listed...kernels, bootloaders, etc. Can you point me to a specific post/file that I can flash in odin to get everything back to normal? Thank you.
Hello folks. Today I did a cache, system, data wipe in TWRP on my G920F. After that I tried to restore a nandroid backup, but it failed and when I tried to restart it said there was no OS installed. So the phone wouldn't boot. I figured I did something wrong so I downloaded a 5.1.1 stock rom (UK) and flashed it with odin. But after the flash the phone would just bootloop. How can I revive the phone? Tried flashing the firmware again using another version of odin and also, I did a factory reset from the stock recovery, but no dice. Any ideas? Thanks in advance
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Managed to make it work flashing another official rom, then factory reset. Lost all my files though...
Can be closed. Thanks!
Sent from my SM-G925F using Tapatalk
kendall1004 said:
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Click to expand...
Click to collapse
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Immoblize said:
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Click to expand...
Click to collapse
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
kendall1004 said:
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
Click to expand...
Click to collapse
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Immoblize said:
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Click to expand...
Click to collapse
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Immoblize said:
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Click to expand...
Click to collapse
Sleep over it, tomorrow is another day
Also, browse my recent postings here; most of them revolving around your issue, this will surely help.
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Immoblize said:
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Click to expand...
Click to collapse
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
kendall1004 said:
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
Click to expand...
Click to collapse
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Immoblize said:
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Click to expand...
Click to collapse
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. (...) Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
kendall1004 said:
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
Click to expand...
Click to collapse
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
:silly:
Immoblize said:
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
Click to expand...
Click to collapse
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
kendall1004 said:
:silly:
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
Click to expand...
Click to collapse
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Immoblize said:
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Click to expand...
Click to collapse
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
Flash CF-Root for your model with Odin - Make sure you have an custom recovery installed (I advise you to use TWRP) (2.8.7.1 or newer REQUIRED for v.2.1 > of this ROM!!)
Click to expand...
Click to collapse
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
kendall1004 said:
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
Click to expand...
Click to collapse
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Immoblize said:
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Click to expand...
Click to collapse
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed :fingers-crossed:
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed
Click to expand...
Click to collapse
Yeah, i've never had problems entering TWRP menu. I can flash stock firmware via Odin but i can never do it via TWRP because it's says no md5 file found error - tho i can flash XtreStoLite (i think it's because it says aroma installer).
I've read many places about the md5 file error, but for some reason, i can't figure out how to fix it.
No, there is no Denmark model, but we have NEE (Nordic). The only stock firmware i can install is XEF (i don't remember where i got that from actually).
I will try agian and flash stock android via TWRP AND read about the md5 file error now/later. Tomorrow i will call the store i got the phone from and tell them i have a hardware issue or something like that. The guy owns a store for sellings covers, cases and stuff like that. He got the phone from Samsung free and sold it brand new in the package with 1 year warranty, so i will contact him tomorrow if i can't figure out how to flash stock android via TWRP or if it gives me error about the md5 file.
Talk to you tomorrow.
Update: I can not flash NEE model via Odin. Only XEF model - i also found out it was French firmware.
I was looking into the S5 OG5 root a while ago and I sold the device I had because there didn't seem to be a way to root it. I do have a rooted S4 and there was recently a new root method found for the 5.0.1 S4 rom that was released after the OG5 rom for the S5. The MobileGo website says it also supports the S5 so if anyone with OG5 unrooted wants to give this a try and let others know whether it works or not, I'm sure everyone would appreciate it. You guys are probably going to want to flash an older S5 kernel just like the S4 users flashed an older kernel before running the MobileGo program. Link: http://forum.xda-developers.com/showthread.php?t=3254434
Where do I find kernels to flash? I am willing to try this.
MySonsDad said:
Where do I find kernels to flash? I am willing to try this.
Click to expand...
Click to collapse
What you can do for now is try running MobileGo using the kernel you have now. If you're lucky, it'll root. If not, you can read on:
So what I would do first is download the latest version of Odin: http://odindownloadxda.com/Odin3_v3.10.7.zip
Then you'd want to go to this thread for the Odin flashable stock kernels for older versions:
http://forum.xda-developers.com/ver...t/safestrap-odin-safestrap-flashable-t3161043
BEFORE YOU TRY THESE NEXT STEPS: I was unable to find the stock OG5 Odin flashable kernel in these forums. If someone could kindly extract it from the stock OG5 rom and post on here you can begin the next steps. Don't try this before you have the stock OG5 kernel on hand because the older kernels may not let your phone boot up into the rom and the only way to fix it is to either reflash the entire OG5 rom in Odin or to flash the OG5 kernel in Odin. I think you can make the kernel yourself if you have the stock OG5 Odin tar, just extract the boot.img and pack it into a tar.md5 using http://forum.xda-developers.com/showthread.php?t=2446269 Here is a stock OG5 odin flashable kernel I was able to create for you: https://mega.nz/#!SEhzyKaL!ymd4vJ2Jd6ytbZoBIPp4fYh6fCRz0tELRMNAYVmIrqU
Once you have the OG5 kernel as a backup, try flashing VZW_BOD5_RETAIL_KERNEL_ONLY.tar.md5 and run MobileGo, if that doesn't work move on to VZW_BOC4_RETAIL_KERNEL_ONLY.tar.md5 then trying the MobileGo and then if that fails try NI2_stock_kernel.tar.md5 since that's the 4.4 kernel that was rootable. However, there's a strong chance that your phone will refuse to boot into the Lollipop rom using a KitKat kernel. All you have to do is flash back the OG5 kernel in Odin 3.10. Once you go through the different kernels from OG5 -> OE1 -> OC4 -> NI2 and the MobileGo program fails to root on any of them, you'll know that this is not a viable root method for the S5.
I couldn't get MobileGo to connect to my phone on OG5. I flashed the OE1 kernel, connected to MobileGo, then used Mobilego's backup feature. After that I noticed that there's a notification reading SECURITY NOTICE Unauthorized actions have been detected. Restart the device to correct them. I tried the MobileGo root and after about 5 minutes it gave me a failure message. Then I tried to proceed to BOC4 but I kept getting failures from Odin. I cannot get back to OG5 kernel either. After a few tries, I now cannot even get into download mode.
The good news is my phone is working. What do I do now? Is this "tripping Knox?"
Pull the battery. Press the buttons for download mode. There should be no case in such you can't access download mode unless you hard bricked your phone which you didn't since the phone is working. Mobilego doesn't specify if their root method trips Knox. Probably should assume it does but if the root failed then it should've left Knox alone. After a clean battery pull try flashing the OG5 kernel back to your phone.
aznjosh said:
I was looking into the S5 OG5 root a while ago and I sold the device I had because there didn't seem to be a way to root it. I do have a rooted S4 and there was recently a new root method found for the 5.0.1 S4 rom that was released after the OG5 rom for the S5. The MobileGo website says it also supports the S5 so if anyone with OG5 unrooted wants to give this a try and let others know whether it works or not, I'm sure everyone would appreciate it. You guys are probably going to want to flash an older S5 kernel just like the S4 users flashed an older kernel before running the MobileGo program. Link: http://forum.xda-developers.com/showthread.php?t=3254434
Click to expand...
Click to collapse
Where on the mobilego website does it say it supports the s5? I will try this when I get home tonight and post results.
fates13 said:
Pull the battery. Press the buttons for download mode. There should be no case in such you can't access download mode unless you hard bricked your phone which you didn't since the phone is working. Mobilego doesn't specify if their root method trips Knox. Probably should assume it does but if the root failed then it should've left Knox alone. After a clean battery pull try flashing the OG5 kernel back to your phone.
Click to expand...
Click to collapse
I can now get into download mode. If I try the older kernels I get a status bar that goes about 1cm then stops. If I try the kernel you gave me for OG5 ODIN says the binary is corrupt before even letting me flash it.
MySonsDad said:
I can now get into download mode. If I try the older kernels I get a status bar that goes about 1cm then stops. If I try the kernel you gave me for OG5 ODIN says the binary is corrupt before even letting me flash it.
Click to expand...
Click to collapse
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
Click to expand...
Click to collapse
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?
MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?
Click to expand...
Click to collapse
Hey, I might have created the flashable kernel incorrectly. Sorry, this is my first time creating flashable odin images. Try this one: https://mega.nz/#!SEhzyKaL!ymd4vJ2Jd6ytbZoBIPp4fYh6fCRz0tELRMNAYVmIrqU
You can try flashing that over your OG5 rom right now since it's the OG5 kernel and it won't change anything on your phone even if it does flash.
---------- Post added at 10:03 PM ---------- Previous post was at 09:56 PM ----------
Hariiiii said:
Where on the mobilego website does it say it supports the s5? I will try this when I get home tonight and post results.
Click to expand...
Click to collapse
wondershare(dot)(com)/mobile-phone/root-samsung-galaxy-s5(dot)(html)
That guide is from before the OG5 update though. However, my basis for trying this is because it was able to root an S4 5.0.1 rom that was released well after the S5 OG5 rom was released. I was thinking that they would've implemented the same root-fixes into the S4 as the S5 so if the mobilego method worked on the patched S4 rom then it should have a good chance of working on the S5. I would test all this myself but I sold my brother's S5 a couple days ago.
I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install Heimdall For S5
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method
jrkruse said:
I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install Heimdall For S5
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method
Click to expand...
Click to collapse
Thanks for your input jrkruse! I read here http://mobile.tumblrvip.com/2015/09/23/successfully-downgrade-from-bog5-kernel-to-any-kernel-solved/ that Odin 3.10 should allow S5 users to downgrade OG5 to any older kernel supposedly.
jrkruse said:
I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method
Click to expand...
Click to collapse
Thanks for the detailed instructions. Somebody may want to keep trying this. I got an error on step 9 relating to libusb, is that the drivers?
---------- Post added at 06:11 AM ---------- Previous post was at 06:01 AM ----------
MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?
Click to expand...
Click to collapse
Okay. Here's my assessment of the ODIN method.
OG5 on OG5 Kernel - MobileGo Cannot Root this
OG5 on OE1 Kernel - MobileGo Cannot Root This
OG5 on OC4 Kernel - MobileGo Cannot Root This
OG5 on NI2 Kernel - Bad idea. I was stuck in a boot loop for like an hour before I got back to Download mode to reflash the whole stock image.
You can flash any of these kernels from ODIN, and you can flash everything back to rescue yourself. If you leave one of the older kernels on your phone too long, it will soft brick. If somebody figures out a root method that works, ODIN will be able to help use move between Kernels. This has been a fun first foray into Android Hacking. I still hate my phone.
Thank you fates13 and jrkruse, you guys rock.
MySonsDad said:
Thanks for the detailed instructions. Somebody may want to keep trying this. I got an error on step 9 relating to libusb, is that the drivers?
---------- Post added at 06:11 AM ---------- Previous post was at 06:01 AM ----------
Okay. Here's my assessment of the ODIN method.
OG5 on OG5 Kernel - MobileGo Cannot Root this
OG5 on OE1 Kernel - MobileGo Cannot Root This
OG5 on OC4 Kernel - MobileGo Cannot Root This
OG5 on NI2 Kernel - Bad idea. I was stuck in a boot loop for like an hour before I got back to Download mode to reflash the whole stock image.
You can flash any of these kernels from ODIN, and you can flash everything back to rescue yourself. If you leave one of the older kernels on your phone too long, it will soft brick. If somebody figures out a root method that works, ODIN will be able to help use move between Kernels. This has been a fun first foray into Android Hacking. I still hate my phone.
Thank you fates13 and jrkruse, you guys rock.
Click to expand...
Click to collapse
Thanks for testing!
All those people complaining that their updated device can't be rooted, not willing to try this out?
Can confirm that the root does not work and that the NI2 kernel will not successfully boot lollipop. Root might be theoretically possible if NI2 could boot....any thoughts on how to get into lollipop with the NI2 kernel in place?
ldeveraux said:
All those people complaining that their updated device can't be rooted, not willing to try this out?
Click to expand...
Click to collapse
I have an unrooted VZW S5 with OG5 and would like to give it a shot, but download mode hasn't worked for me since OE1. Holding power+vol down+home just boots the device normally. I've tried holding them all the way through the boot, which causes the phone to repeatedly reboot. Am I missing something?
Edit: Nevermind, guess I was pressing power first. I've got download mode now. Will report back if I make any progress...
Verizon
This is unfortunate.
So we are back to square one?
But if I understand, MySonsDad confirmed we have no reason to not update to OK3 since we can jump between the locked kernels?
So no root for 5.0? I've got to start researching these things before I buy a phone.
brd912 said:
So no root for 5.0? I've got to start researching these things before I buy a phone.
Click to expand...
Click to collapse
Same here, I figured it would be a similar process as rooting my Nexus 5 when I was on AT&T. The Verizon and Samsung bloatware is painful when it can't be removed.
Is there no update on this? I'm willing to anything at this point.
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Rawbert.Watkins said:
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Click to expand...
Click to collapse
CFW?
You need a revision 3 firmware.
Rawbert.Watkins said:
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Click to expand...
Click to collapse
Did you do your NANDROID backup to the phone? If so, wiping it would of course wipe out your backup. If you chose a complete wipe, it would even wipe the sd card.
Doh!
I'm not laughing, I did this not long ago myself, and I've rooted dozens of devices.
I'll search for a solution to this, no promises.
ashyx said:
CFW?
You need a revision 3 firmware.
Click to expand...
Click to collapse
CFW=Custom FirmWare
Sent from my Samsung Galaxy Trend Plus using XDA Labs
I'm getting the same error. I was fortunate enough to have another device available and pulled a backup from that device. But I need to use Odin to flash a different modem to get WiFi working again. It currently won't turn on and stays greyed out. It's been a couple weeks since this topic was posted. Any luck getting Odin to work?
Sent from my SM-G950U using Tapatalk
equitube said:
Did you do your NANDROID backup to the phone? If so, wiping it would of course wipe out your backup. If you chose a complete wipe, it would even wipe the sd card.
Doh!
I'm not laughing, I did this not long ago myself, and I've rooted dozens of devices.
I'll search for a solution to this, no promises.
Click to expand...
Click to collapse
Any word by chance?
Sent from my SM-G950U using Tapatalk
lancemulvihill85 said:
Any word by chance?
Click to expand...
Click to collapse
You need a matching NON-HLOS.bin flashed to the APNHLOS partition. You can flash this with TWRP.
However if you'd have paid attention to my previous post all you need to do is flash the correct firmware with odin.
ashyx said:
You need a matching NON-HLOS.bin flashed to the APNHLOS partition. You can flash this with TWRP.
However if you'd have paid attention to my previous post all you need to do is flash the correct firmware with odin.
Click to expand...
Click to collapse
I can't figure out how to flash to that partition with twrp. Just zipping the .bin to .tar and flash just doesn't fly. I apologize for my ignorance in the matter. However I was paying attention, and read the few previous posts. My situation is a little different. The last 3 letters of the current firmware end in QL3. And I can't seem to find that build ANYWHERE. When using the sammobile app to figure out what it's currently running, the CSC partition is empty. I have no CSC. When googling how to flash a CSC with twrp, I run into dead ends about using Odin (which will not work for my build). I'll post screenshots in a lil bit if anyone would help. I'm at a loss right now
Sent from my SM-G950U using Tapatalk
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
Basically, I have a working build, but WiFi is broken. It won't turn on. That's all I need. And I've been googling for about 2 weeks trying to figure this out
Sent from my SM-G950U using Tapatalk
lancemulvihill85 said:
I can't figure out how to flash to that partition with twrp. Just zipping the .bin to .tar and flash just doesn't fly. I apologize for my ignorance in the matter. However I was paying attention, and read the few previous posts. My situation is a little different. The last 3 letters of the current firmware end in QL3. And I can't seem to find that build ANYWHERE. When using the sammobile app to figure out what it's currently running, the CSC partition is empty. I have no CSC. When googling how to flash a CSC with twrp, I run into dead ends about using Odin (which will not work for my build). I'll post screenshots in a lil bit if anyone would help. I'm at a loss right now
Sent from my SM-G950U using Tapatalk
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
Basically, I have a working build, but WiFi is broken. It won't turn on. That's all I need. And I've been googling for about 2 weeks trying to figure this out
Click to expand...
Click to collapse
You don't need to flash the same build, you just need the right revision and version of Odin.
What is the error on the device when flashing the firmware?
hello guys,
i have a rooted xiaomi redmi 5 plus, that stuck in bootloop, i had AEX and tried to get back to miui so i downloaded from miui's site and tried to install it through twrp. My device didnt boot so i tried to install AEX again but it seems like it cant boot properly and is stuck in bootloop.
Until now i have update my firmware with the last version, i wied everything and tried to install again AEX but nothing helped so far:crying:
Can you give me any advice? i am getting really frustrated here
thanks in advance
https://imghost.io/image/1cXI8
iypapaz said:
hello guys, i have a rooted xiaomi redmi 5 plus, that stuck in bootloop, i had AEX and tried to get back to miui so i downloaded from miui's site and tried to install it through twrp. My device didnt boot so i tried to install AEX again but it seems like it cant boot properly and is stuck in bootloop...
Click to expand...
Click to collapse
I don't have this device but, you may be able to obtain some member guidance within the following Official TWRP thread for your device.
https://forum.xda-developers.com/showthread.php?t=3727162
The following, device specific, thread may also be helpful for what you are looking for and don't be afraid to ask for some member guidance within it too.
https://forum.xda-developers.com/showthread.php?t=3776359
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, you may be able to obtain some member guidance within the following Official TWRP thread for your device.
https://forum.xda-developers.com/showthread.php?t=3727162
The following, device specific, thread may also be helpful for what you are looking for and don't be afraid to ask for some member guidance within it too.
https://forum.xda-developers.com/showthread.php?t=3776359
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
thank you for your reply i have just checked the second thread you posted me but doesn't help i will check and the twrp thread the next days.
iypapaz said:
hello guys,
i have a rooted xiaomi redmi 5 plus, that stuck in bootloop, i had AEX and tried to get back to miui so i downloaded from miui's site and tried to install it through twrp. My device didnt boot so i tried to install AEX again but it seems like it cant boot properly and is stuck in bootloop.
Until now i have update my firmware with the last version, i wied everything and tried to install again AEX but nothing helped so far:crying:
Can you give me any advice? i am getting really frustrated here
thanks in advance
Click to expand...
Click to collapse
are you able to boot into recovery, if yes then connect device to pc via cable while in recovery mode. your pc will detect device storage. copy a different rom in device and flash it. if this doesn't work then flash miui with flash tool.
RajeshJangid said:
are you able to boot into recovery, if yes then connect device to pc via cable while in recovery mode. your pc will detect device storage. copy a different rom in device and flash it. if this doesn't work then flash miui with flash tool.
Click to expand...
Click to collapse
hello, i am able to boot into recovery, i can install a rom but when i reboot i am stuck with the boot logo of aosp. Also i have no os for usb debug.
iypapaz said:
hello, i am able to boot into recovery, i can install a rom but when i reboot i am stuck with the boot logo of aosp. Also i have no os for usb debug.
Click to expand...
Click to collapse
flash miui using twrp and don't forget to flash appropriate root solution with it(ex:supersu).