Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP - T-Mobile Samsung Galaxy S 5

So I flashed latest firmware of lollipop thru ODIN lollipop everything went smooth, New Stock Lollipop rom flashed and everything was perfect......... Now the problem I rooted using cf autoroot that went well, Flashed Twrp, But when I try to restore any backup roms they bootloop...... Try to flash any new roms, Bootloop, So my question is ? Does the new bootloader new the stock kernel for this to work ? and once we flash this are we not able to flash any 4.4.2 roms since it won't have the 5.0 kernel ??
Hopefully I did something wrong ??? But who else that has flashed full firmware or bootloader been able to flash any other roms after ?????
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I am having the same problem, im not able to flash any ASOP roms (bootloops) but touchwiz i can flash without a problem.
idk if it has to do something with the bootloader or not. i also flashed the full stock .tar

eventheodds1 said:
I am having the same problem, im not able to flash any ASOP roms (bootloops) but touchwiz i can flash without a problem.
idk if it has to do something with the bootloader or not. i also flashed the full stock .tar
Click to expand...
Click to collapse
Is not even letting me flash touchwiz roms....... Which one have you tried that's worked for you ??? I keep getting stuck on bootloops with any 4.4.2 rom that I try I even tried Xtrelight or whatever the internation one and i can't get it to past the samsung logo.............. Just flashed the full firmware again and stock rom loads just fine...... How did you get root when you flashed 5.0 did you flash the old 4.4.2 cf autoroot ???

@gdmlaz i let the stock tar boot up than moved flash version of vision in the sdcard, used odin and flashed phliz. After doing so, wipe cache+data, than flashed vision. Read the instructions clearly or else you won't have mobile data! hope that helps!
[ROM]ViSiON-X US TMO[Android L 5.0][G900TUVU1DOB1][02-18-15]

eventheodds1 said:
@gdmlaz i let the stock tar boot up than moved flash version of vision in the sdcard, used odin and flashed phliz. After doing so, wipe cache+data, than flashed vision. Read the instructions clearly or else you won't have mobile data! hope that helps!
[ROM]ViSiON-X US TMO[Android L 5.0][G900TUVU1DOB1][02-18-15]
Click to expand...
Click to collapse
So you just flashed recovery before rooting ??? I'll try that this time, I usually root before try to flashing a recovery in the past it has not stuck around

gdmlaz said:
So you just flashed recovery before rooting ??? I'll try that this time, I usually root before try to flashing a recovery in the past it has not stuck around
Click to expand...
Click to collapse
yep, flashing phliz will trip your knox tho

eventheodds1 said:
yep, flashing phliz will trip your knox tho
Click to expand...
Click to collapse
My knox has been tripped for years lol

gdmlaz said:
My knox has been tripped for years lol
Click to expand...
Click to collapse
hahaha, i always flash recovery (via odin) than flash the rom, which most (if not all) coming with superSU and root access.
im just little ticked off I get stuck on bootloop for ASOP roms tho :l I'm not big fan of touchwiz.

eventheodds1 said:
hahaha, i always flash recovery (via odin) than flash the rom, which most (if not all) coming with superSU and root access.
im just little ticked off I get stuck on bootloop for ASOP roms tho :l I'm not big fan of touchwiz.
Click to expand...
Click to collapse
Still stuck on bootloops....... whenever I try to flash anything using ktoonz twrp Ugghhhh sooo annoying only thing I get to work is just stock rom when i fully flash the firmware file thru odin..... Going to try to restore an old 4.4.2 rom see if this even boots up..... I'm getting close to giving up

gdmlaz said:
Still stuck on bootloops....... whenever I try to flash anything using ktoonz twrp Ugghhhh sooo annoying only thing I get to work is just stock rom when i fully flash the firmware file thru odin
Click to expand...
Click to collapse
try using philz touchwiz, i dont think that would make a difference but it's worth a shot!
Also if you flashed the rom, vision, than it takes a good solid 10min!

eventheodds1 said:
try using philz touchwiz, i dont think that would make a difference but it's worth a shot!
Also if you flashed the rom, vision, than it takes a good solid 10min!
Click to expand...
Click to collapse
Yea I used vision before and used to work fine....... I been trying to flash regular 4.4.2 and none of them get past the samsung boot screen before it bootloops all over again..... Which philz version are you using I'm willing to try anything at this point lol

gdmlaz said:
Yea I used vision before and used to work fine....... I been trying to flash regular 4.4.2 and none of them get past the samsung boot screen before it bootloops all over again..... Which philz version are you using I'm willing to try anything at this point lol
Click to expand...
Click to collapse
try the 5.0 lollipop, seems like you already have 5.0 bootloader

eventheodds1 said:
try the 5.0 lollipop, seems like you already have 5.0 bootloader
Click to expand...
Click to collapse
Yea this is my problem the stupid 5.0 bootloader doesn't let me do anything for some reason............... Not even my backups load a soon as i try to restart my phone to load them phone goes into bootloop and nothing works...... I guess I'll just use the stock firmware file till somebody figures out what to do
I'm guessing it has to be with the Bootloader tied down to the stock tmobile 5.0 Kernel........... Since the only thing that loads up is the full firmware

If you guys are trying to revert back to previous version of kitkat coming from lollipop using custom recovery, it will fail. You will have to downgrade with pc odin to a previous kitkat full stock firmware and then reroot. You can not flash kitkat over lollipop, it will fail and bootloop. If you are trying to upgrade to tmo lollipop and then try to restore a asop lollipop rom, it will fail as well. Asop lollipop roms are based off international roms and will not play well with tmo lollipop.

galaxyuser88 said:
If you guys are trying to revert back to previous version of kitkat coming from lollipop using custom recovery, it will fail. You will have to downgrade with pc odin to a previous kitkat full stock firmware and then reroot. You can not flash kitkat over lollipop, it will fail and bootloop.
Click to expand...
Click to collapse
Well that sucks......... The most I got accomplished so far is flash stock firmware/flash twrp recovery/ root it.................. I will make a backup of this on twrp and try to flash another costum rom see if that works but last time I tried XtreStoLite Internation version 5.0 and still got me stuck on the same bootloop ??

galaxyuser88 said:
If you guys are trying to revert back to previous version of kitkat coming from lollipop using custom recovery, it will fail. You will have to downgrade with pc odin to a previous kitkat full stock firmware and then reroot. You can not flash kitkat over lollipop, it will fail and bootloop. If you are trying to upgrade to tmo lollipop and then try to restore a asop lollipop rom, it will fail as well. Asop lollipop roms are based off international roms and will not play well with tmo lollipop.
Click to expand...
Click to collapse
is there anything we can flash inorder to fix the bootloop? for example i flashed stock tar for kit-kat tar, to see if i could flash ASOP lollipop roms. i still get stuck on bootloop?

eventheodds1 said:
is there anything we can flash inorder to fix the bootloop? for example i flashed stock tar for kit-kat tar, to see if i could flash ASOP lollipop roms. i still get stuck on bootloop?
Click to expand...
Click to collapse
From what I remember in the past you weren't able to go back to an older firmware ??? Unless things have changed ?
I think issue we are having is a kernel issue....... Boot-loader is looking for stock 5.0 kernel and we don't have it when we flash any other rom

gdmlaz said:
From what I remember in the past you weren't able to go back to an older firmware ??? Unless things have changed ?
I think issue we are having is a kernel issue....... Boot-loader is looking for stock 5.0 kernel and we don't have it when we flash any other rom
Click to expand...
Click to collapse
you are right you can't go back firmware, i forgot :l so we just have to wait for someone to make flashable kernel that will make it work?

This is one reason why dev always say to wait before you take or do any update that drops from carriers. They will see if it is rootable or if it will lock you down.
Now some people dont care about being able to root or just cant wait for a dev to say it is ok. If you can not downgrade to a previous version using pc odin, then you are stuck untill on of the devs figures this out. Please be careful, search and read before taking any update.

eventheodds1 said:
you are right you can't go back firmware, i forgot :l so we just have to wait for someone to make flashable kernel that will make it work?
Click to expand...
Click to collapse
You can go back. I took the ota update to 5.0 and messed up trying to root so odin'd back to KitKat and then took the update again. I odin'd Phil's touch used that to flash the latest twrp from ktoonsez and then flashed root. Haven't tried flashing aosp yet.

Related

How to downgrade to 4.2.2

Hello,
i have successfully installed the 4.4.2 KK original rom released on samfirmware 3 weeks ago on my 9205 LTE, and now i would like to downgrade to 4.2.2. Is there a method? Can it be done?
Thanks!
PS: What is the best ROM for mega?
Up!
http://forum.xda-developers.com/showthread.php?t=2773380
trurl3 said:
http://forum.xda-developers.com/showthread.php?t=2773380
Click to expand...
Click to collapse
Not answered at my question.
Tried flashing 4.2.2 and odin fails. What can i do?
corrystile said:
Not answered at my question.
Tried flashing 4.2.2 and odin fails. What can i do?
Click to expand...
Click to collapse
Nothing. You already installed the newest Knox Bootloader included with the Firmware and it can not be downgraded. If you do downgrade the Bootloader you will brick your phone. You can flash "ROMS" ( not Firmwares ) all you like from previous builds meaning you can flash a Custom 4.2.2 Rom but you can not downgrade the newest Knox Bootloader you installed.
DarkAngel said:
Nothing. You already installed the newest Knox Bootloader included with the Firmware and it can not be downgraded. If you do downgrade the Bootloader you will brick your phone. You can flash "ROMS" ( not Firmwares ) all you like from previous builds meaning you can flash a Custom 4.2.2 Rom but you can not downgrade the newest Knox Bootloader you installed.
Click to expand...
Click to collapse
Really?
I have now the TPH beta installed, but is only a beta, and i really want to return in 4.2.2 firmware, that's absolutely a s*it.
So can't donwgrade with or without root, cannot downgrade bootloader, nothing to return to stock 4.2.2?
All the lag from 4.2 just isn't worth going back. I had to go back to my iPhone 5S until the 4.4.2 came out. Now I'm on 4.4.2 and back on my android and loving it. Never want to go back to the iPhone again.
corrystile said:
Hello,
i have successfully installed the 4.4.2 KK original rom released on samfirmware 3 weeks ago on my 9205 LTE, and now i would like to downgrade to 4.2.2. Is there a method? Can it be done?
Thanks!
Click to expand...
Click to collapse
Yes you can, using a mobile ODIN
Ura535 said:
Yes you can, using a mobile ODIN
Click to expand...
Click to collapse
No!! he can't use odin to flash a 4.2.2 firmware because he flash the 4.4.2 kk firmware with the new knox bootloader if he try to flash an older firmware he will brick his phone. @corrystile you can use the MegaFire v11 to go back to jellybean 4.2.2 thanks to @megalomanic14 this is a TW base rom and it work on both 19200 and 19205.
Sent from my GT-I9200 using XDA Premium 4 mobile app
alexischino said:
No!! he can't use odin to flash a 4.2.2 firmware because he flash the 4.4.2 kk firmware with the new knox bootloader if he try to flash an older firmware he will brick his phone. @corrystile you can use the MegaFire v11 to go back to jellybean 4.2.2 thanks to @megalomanic14 this is a TW base rom and it work on both 19200 and 19205.
Sent from my GT-I9200 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And the rom also works on the i527m mega (Canadian version).
Sent from my SGH-I527M using XDA Free mobile app
Dark Angel can you help?
DarkAngel said:
Nothing. You already installed the newest Knox Bootloader included with the Firmware and it can not be downgraded. If you do downgrade the Bootloader you will brick your phone. You can flash "ROMS" ( not Firmwares ) all you like from previous builds meaning you can flash a Custom 4.2.2 Rom but you can not downgrade the newest Knox Bootloader you installed.
Click to expand...
Click to collapse
I bricked my phone. I restored my previous backup(MK1) made with efs pro. I restored all partitions except user data and system. Now it is not responding with any buttons. When i connect it with pc it shows qhsusb_dload. Can you please make a debrick image for it? Or tell me how can i fix it please.
Thanks
bricked
Damn
briked .sorry for my language
DaHulk07 said:
Damn
Click to expand...
Click to collapse
I got the same problem so listen to me
I installed a custom recovery 《philz recovery 》 then i wiped and format everything...
I reinstalled rom 4.2.2 with odin and i pressed nand erase all button and repartition button on odin and i flashed it then it work but i lost IMEI
Then i installed custom recovery and wipped all and reinstalled the 4.4.2 rom ...trattata
All going good and my phone gt i 9200 really working good
Try it bro
aliyassin said:
I got the same problem so listen to me
I installed a custom recovery 《philz recovery 》 then i wiped and format everything...
I reinstalled rom 4.2.2 with odin and i pressed nand erase all button and repartition button on odin and i flashed it then it work but i lost IMEI
Then i installed custom recovery and wipped all and reinstalled the 4.4.2 rom ...trattata
All going good and my phone gt i 9200 really working good
Try it bro
Click to expand...
Click to collapse
This would probably only work if you were still able to get into " Download Mode " on your phone.
Bricked but download mode good
Ok so I tried this and nothing will boot up now. Was the 4.2.2 a custom rom or stock ? I have a replacement screen that cant boot into firmware 4.3 or 4.4.
jimmykirby said:
Ok so I tried this and nothing will boot up now. Was the 4.2.2 a custom rom or stock ? I have a replacement screen that cant boot into firmware 4.3 or 4.4.
Click to expand...
Click to collapse
Yes this is a very big problem right now. I just ordered two replacements and none of them work
Sent from my SM-N900V using XDA Free mobile app
A work around for the cheap screen issue booting on stock 4.3 and 4.4 is to flash phils recovery and root followed by a zip install of a custom 4.4 rom. Boots right up . Also with custom recovery I have backed up stock 4.2 firmware on a diff. mega and used that to restore on my 4.4 mega. Not a true downgrade but bootable into stock rom. Took me a long while to figure this out. Hope this helps.
jimmykirby said:
A work around for the cheap screen issue booting on stock 4.3 and 4.4 is to flash phils recovery and root followed by a zip install of a custom 4.4 rom. Boots right up . Also with custom recovery I have backed up stock 4.2 firmware on a diff. mega and used that to restore on my 4.4 mega. Not a true downgrade but bootable into stock rom. Took me a long while to figure this out. Hope this helps.
Click to expand...
Click to collapse
How can you do that when there is no root?
Sent from my SM-N900V using XDA Free mobile app
Do you mean boot ? If so ; I removed battery to power off, then put it back , then hold volume down and home button and power at the same time to get into download mode. Then used Odin to flash custom recovery. I used Phils recovery. My issue began when I allowed 4.3 OTA update. I lost boot and stock recovery but could still get into download mode.
jimmykirby said:
Do you mean boot ? If so ; I removed battery to power off, then put it back , then hold volume down and home button and power at the same time to get into download mode. Then used Odin to flash custom recovery. I used Phils recovery. My issue began when I allowed 4.3 OTA update. I lost boot and stock recovery but could still get into download mode.
Click to expand...
Click to collapse
There is no root for 4.4. These are the phones with the problems because can't do anything right now. Does the file you have work for 4.4? Have you tried for that version firmware?
Sent from my SM-N900V using XDA Free mobile app

Flashing firmware before ROM?

There's a custom ROM that I wanna flash and it requires a different firmware. Do I flash the firmware first then the ROM? Also, when I flash the firmware is it just like flashing a custom ROM?
Sent from my HTC 1M8
cjbart1009 said:
There's a custom ROM that I wanna flash and it requires a different firmware. Do I flash the firmware first then the ROM?
Click to expand...
Click to collapse
Yes, before you flash the ROM. Main reason, is that the firmware will install stock kernel (therefore over-writing any kernel that is present); so you will want to flash the firmware first, then the custom ROM. That way, the custom ROM install will have the corresponding kernel (if its different from stock, which it may or may not be).
You will also need to re-install custom recovery, as the firmware includes stock recovery (which over-writes the custom one you have now).
cjbart1009 said:
Also, when I flash the firmware is it just like flashing a custom ROM?
Click to expand...
Click to collapse
Not even remotely similar. You need to flash with hboot. You can follow the excellent instructions here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Or here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
In actuality, it is possible to make a recovery flashable zip of the firmware. But I've only seen this on other devices, and haven't seen anyone go to the effort of creating it for the firmware you need.
redpoint73 said:
Yes, before you flash the ROM. Main reason, is that the firmware will install stock kernel (therefore over-writing any kernel that is present); so you will want to flash the firmware first, then the custom ROM. That way, the custom ROM install will have the corresponding kernel (if its different from stock, which it may or may not be).
You will also need to re-install custom recovery, as the firmware includes stock recovery (which over-writes the custom one you have now).
Not even remotely similar. You need to flash with hboot. You can follow the excellent instructions here: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Or here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
In actuality, it is possible to make a recovery flashable zip of the firmware. But I've only seen this on other devices, and haven't seen anyone go to the effort of creating it for the firmware you need.
Click to expand...
Click to collapse
Thanks. I flashed the ROM before flashing the kernel just to see what would happen and for some reason my firmware updated as well. I flashed the custom ROM because I also have a backup of my stock ROM.
cjbart1009 said:
Thanks. I flashed the ROM before flashing the kernel just to see what would happen and for some reason my firmware updated as well. I flashed the custom ROM because I also have a backup of my stock ROM.
Click to expand...
Click to collapse
The firmware version listed on the software information in settings is not an actual representation of your firmware version. Go into your bootloader and see if your firmware version matches your ROM software version.
For example, the bootloader for firmware ver, 2.12.401.3:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Example of rom software version, 1.12.651.17:
revoltech said:
The firmware version listed on the software information in settings is not an actual representation of your firmware version. Go into your bootloader and see if your firmware version matches your ROM software version.
For example, the bootloader for firmware ver, 2.12.401.3:
Example of rom software version, 1.12.651.17:
Click to expand...
Click to collapse
Thanks for pointing it out. What ROM are you using? I've tried flashing the firmware yesterday and I even followed two different tutorials. How did you flash yours?
cjbart1009 said:
Thanks for pointing it out. What ROM are you using? I've tried flashing the firmware yesterday and I even followed two different tutorials. How did you flash yours?
Click to expand...
Click to collapse
I am on ARHD 10.2 and using 2.22.401.4 firmware. I used this tutorial: http://forum.xda-developers.com/showthread.php?t=2696282
I am having connection issues (says I have 4G but I get no data. switching airplane mode on/off fixes this) with this particular firmware and researched that I have to flash the 2.22.1540.3 for my ATT phone. I haven't downgraded yet since I am trying to get more feedback for this issue.
revoltech said:
I am on ARHD 10.2 and using 2.22.401.4 firmware. I used this tutorial: http://forum.xda-developers.com/showthread.php?t=2696282
I am having connection issues (says I have 4G but I get no data. switching airplane mode on/off fixes this) with this particular firmware and researched that I have to flash the 2.22.1540.3 for my ATT phone. I haven't downgraded yet since I am trying to get more feedback for this issue.
Click to expand...
Click to collapse
So it means I haven't flashed a new firmware. I noticed that the service I'm getting isn't as strong as before. Do you thing it's because of the firmware?
cjbart1009 said:
So it means I haven't flashed a new firmware.
Click to expand...
Click to collapse
Incorrect. His screenshot indicates hboot 3.18, so he is on updated firmware.
However, its a known issue that the "international" 2.22.401 firmware does not play well on US networks. He needs to install 2.22.1540, as he already mentioned.
cjbart1009 said:
I noticed that the service I'm getting isn't as strong as before. Do you thing it's because of the firmware?
Click to expand...
Click to collapse
If you flashed 2.22.401 firmware onto the AT&T version, you should try 2.22.1540 as I just described above.
2.22.1540 firmware is linked in Post #2 above.
redpoint73 said:
Incorrect. His screenshot indicates hboot 3.18, so he is on updated firmware.
However, its a known issue that the "international" 2.22.401 firmware does not play well on US networks. He needs to install 2.22.1540, as he already mentioned.
If you flashed 2.22.401 firmware onto the AT&T version, you should try 2.22.1540 as I just described above.
2.22.1540 firmware is linked in Post #2 above.
Click to expand...
Click to collapse
But the ROM that I'm using requires the firmware that I have now.
cjbart1009 said:
But the ROM that I'm using requires the firmware that I have now.
Click to expand...
Click to collapse
No it doesn't, it just requires a 2.22.xxx based firmware.
What ROM? The thread probably just says a certain firmware is required, since having any "old" 1.xx firmware causes severe issues (long boot times, broken Bluetooth and WiFi, etc.). Also, it seems that a lot of the ROMs are being developed by owners of the"international" version, so they seem less aware of US-specific issues (although some ROMs like ARHD discuss it in the thread - but not in the top post).
redpoint73 said:
No it doesn't, it just requires a 2.22.xxx based firmware.
What ROM? The thread probably just says a certain firmware is required, since having any "old" 1.xx firmware causes severe issues (long boot times, broken Bluetooth and WiFi, etc.).
Click to expand...
Click to collapse
ARHD
cjbart1009 said:
ARHD
Click to expand...
Click to collapse
I already posted this above: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
Although its not explicitly clear, it says US users "may with to try" the firmware I specified (1540):
"In order to boot and run properly 10.x will require a firmware update to 2.22.401.4
Note: US users may wish to try the 2.22.1540.3 fw. "
AT&T users have reported various connection issues on "international" firmware 401; which is resolved by flashing firmware 1540. This includes NO SERVICE whatsoever on 401. So you tell me, which one is "required"?
redpoint73 said:
I already posted this above: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
Although its not explicitly clear, it says US users "may with to try" the firmware I specified (1540):
"In order to boot and run properly 10.x will require a firmware update to 2.22.401.4
Note: US users may wish to try the 2.22.1540.3 fw. "
AT&T users have reported various connection issues on "international" firmware 401; which is resolved by flashing firmware 1540. This includes NO SERVICE whatsoever on 401. So you tell me, which one is "required"?
Click to expand...
Click to collapse
" Note: US users may wish to try the 2.22.1540.3 fw. The 2.22.1540.3 fw is unmodified and includes stock recovery, if you flash the 2.22.1540.3 unmodified fw you will need to reflash custom recovery and regain root or you can remove the boot.img and recovery.img from the fw.zip. The 2.12.401.3 fw is wwe and the 2.22.1540.3 fw is for the US developer m8."
OK I didn't catch the last sentence and it's all clear now. I'll flash the 2.22. The second sentence confused me tho.
cjbart1009 said:
" Note: US users may wish to try the 2.22.1540.3 fw. The 2.22.1540.3 fw is unmodified and includes stock recovery, if you flash the 2.22.1540.3 unmodified fw you will need to reflash custom recovery and regain root or you can remove the boot.img and recovery.img from the fw.zip. The 2.12.401.3 fw is wwe and the 2.22.1540.3 fw is for the US developer m8."
OK I didn't catch the last sentence and it's all clear now. I'll flash the 2.22. The second sentence confused me tho.
Click to expand...
Click to collapse
All the 2nd and 3rd sentences mean is that the 1540 firmware package is "unmodified" and therefore over-writes recovery and boot.img with the "stock" versions. This is normal for the "official" firmware packages. For the 401 firmware, it just happens that someone already modified it to remove the recovery and boot.img modules, so they will not over-write what is on the phone.
But for the 1540 firmware, this means you need to re-flash your custom recovery after flashing the firmware. If you do as I suggested (original question of this thread) and flash the firmware before the ROM, the issue of boot.img (basically the kernel, although there is some other stuff in that file) and root is really a moot point. Boot.img will install when you flash the ROM, and all the custom ROMs are pre-rooted.
redpoint73 said:
All the 2nd and 3rd sentences mean is that the 1540 firmware package is "unmodified" and therefore over-writes recovery and boot.img with the "stock" versions. This is normal for the "official" firmware packages. For the 401 firmware, it just happens that someone already modified it to remove the recovery and boot.img modules, so they will not over-write what is on the phone.
But for the 1540 firmware, this means you need to re-flash your custom recovery after flashing the firmware. If you do as I suggested (original question of this thread) and flash the firmware before the ROM, the issue of boot.img (basically the kernel, although there is some other stuff in that file) and root is really a moot point. Boot.img will install when you flash the ROM, and all the custom ROMs are pre-rooted.
Click to expand...
Click to collapse
OK. Thanks for the in depth explanation. Makes sense to me now. So from my understanding I have to start fresh when I flash a new firmware. I won't lose s-off or unlock right?
cjbart1009 said:
Makes sense to me now. So from my understanding I have to start fresh when I flash a new firmware. I won't lose s-off or unlock right?
Click to expand...
Click to collapse
Flashing firmware won't affect s-off, bootloader unlock, or SIM unlock (not sure which "unlock" you meant). None of these can typically be changed unless you do so yourself manually.
redpoint73 said:
Flashing firmware won't affect s-off, bootloader unlock, or SIM unlock (not sure which "unlock" you meant). None of these can typically be changed unless you do so yourself manually.
Click to expand...
Click to collapse
That's probably why it kept on failing when I was flashing the firmware cause I already have it on my phone.
PS. everyone, flashing firmware does NOT replace recovery with stock recovery...
DunamisMaximus said:
PS. everyone, flashing firmware does NOT replace recovery with stock recovery...
Click to expand...
Click to collapse
An official signed firmware will definitely replace custom recovery with stock recovery.
Only if the firmware has had stock recovery removed, or TWRP inserted (such as SneakyGhost's firmware marked "TWRP") will the recovery be TWRP afterwards. And you need s-off to flash any such firmware (as changing it, breaks the signature - and unsigned firmware can't be flashed with s-on).
As clearly stated in the thread by mike1986:
Does firmware.zip contains recovery?
Yes, it does contain recovery image, that's why after flashing firmware.zip you will have to flash custom recovery again, to be able to flash custom ROM afterwards.
revoltech said:
The firmware version listed on the software information in settings is not an actual representation of your firmware version. Go into your bootloader and see if your firmware version matches your ROM software version.
For example, the bootloader for firmware ver, 2.12.401.3:
Example of rom software version, 1.12.651.17:
Click to expand...
Click to collapse
Can I flash firmware After boot the ROM,becuase i forget to flash firmware first, so can i flash it now? Any problem if i do that?

4.4.4

New firmware is out NJ6. I can't get the OTA yet but it is available from KIES. Hopefully this will solve all of my signal issues.
I saw this on sammobile as well...most likely this will close the current root loophole...will wait patiently until an awesome developer can create a rooted 4.4.4 rom.
Yes, I did lose root but that is okay with me if it helps my signal. Haven't been able to test it in problem areas yet.
murmur70 said:
Yes, I did lose root but that is okay with me if it helps my signal. Haven't been able to test it in problem areas yet.
Click to expand...
Click to collapse
Have you tried to root again with towel root?
Towel Root no longer works, I tried it after I updated...
The-Beast said:
Towel Root no longer works, I tried it after I updated...
Click to expand...
Click to collapse
Thanks!
Sent from my Nexus 7 using Tapatalk
I am cautiously optimistic that my signal is much improved.
Sent from my SM-T700 using XDA Free mobile app
I actually have 4.4.4 rooted right now on my device but safestrap doesn't work properly now. It starts to load but then reboots into OS.
The first 4.4.4 rom I made would boot, but only had a black screen (kernel modules didn't match boot.img), then I tried the nj6 boot.img and got the warning about unauthorized kernel. So, I decided to try one more thing. I reflashed the pre-rooted 4.4.4 rom I made and then flashed all of the 4.4.4 firmware in Odin EXCEPT for the system partition. This allowed me to boot into my rooted nj6 4.4.4 rom.
gr8nole said:
I actually have 4.4.4 rooted right now on my device but safestrap doesn't work properly now. It starts to load but then reboots into OS.
The first 4.4.4 rom I made would boot, but only had a black screen (kernel modules didn't match boot.img), then I tried the nj6 boot.img and got the warning about unauthorized kernel. So, I decided to try one more thing. I reflashed the pre-rooted 4.4.4 rom I made and then flashed all of the 4.4.4 firmware in Odin EXCEPT for the system partition. This allowed me to boot into my rooted nj6 4.4.4 rom.
Click to expand...
Click to collapse
Ain't gonna lie ... a lot of that went right over my head; but I'm excited about it anyway LOL :good:
How do I get it on my phones have 2 Note 3's in my house. It's not available on Kies or OTA in my Texas area. Not rooted phones.. or just wait some more?? Thanks
We're actually getting an update inline with other carriers? Anyone noticing any improvements? And do we have any idea when it'll push OTA?
Can someone post up just the radio?
pez910 said:
We're actually getting an update inline with other carriers? Anyone noticing any improvements? And do we have any idea when it'll push OTA?
Click to expand...
Click to collapse
The only thing I have noticed since updating last night is, data speeds have dropped. Not sure if its the radios, or if its the network being bottle necked, but Its taking me forever to download apps and files from my google drive account..
YankInDaSouth said:
Ain't gonna lie ... a lot of that went right over my head; but I'm excited about it anyway LOL :good:
Click to expand...
Click to collapse
can you send on the link for your root 4.4.4
gr8nole said:
I actually have 4.4.4 rooted right now on my device but safestrap doesn't work properly now. It starts to load but then reboots into OS.
The first 4.4.4 rom I made would boot, but only had a black screen (kernel modules didn't match boot.img), then I tried the nj6 boot.img and got the warning about unauthorized kernel. So, I decided to try one more thing. I reflashed the pre-rooted 4.4.4 rom I made and then flashed all of the 4.4.4 firmware in Odin EXCEPT for the system partition. This allowed me to boot into my rooted nj6 4.4.4 rom.
Click to expand...
Click to collapse
I was having the same issue when I tried to port Sprint 4.4.4 It would boot but I get black screen... Are you sure you flashed the 4.4.4 bootloader?
I would try to make a deodex 4.4.4 system flashable zip and flash and then right after it reboot to odin and flash the 4.4.4 kernel might work without flashing the bootloader and that way we have a working SS.
Kind of a newb to Note 3 firmware upgrades. I just downloaded the new NJ6 firmware from Sammobile. What's the best way to flash this?
gypsy214 said:
I was having the same issue when I tried to port Sprint 4.4.4 It would boot but I get black screen... Are you sure you flashed the 4.4.4 bootloader?
I would try to make a deodex 4.4.4 system flashable zip and flash and then right after it reboot to odin and flash the 4.4.4 kernel might work without flashing the bootloader and that way we have a working SS.
Click to expand...
Click to collapse
Can you upload please
uberalbo said:
Kind of a newb to Note 3 firmware upgrades. I just downloaded the new NJ6 firmware from Sammobile. What's the best way to flash this?
Click to expand...
Click to collapse
If you're a newb I recommend to stay out of it if you want root and ss. We waited all this time we can wait more to have a stable rooted with ss working version
gypsy214 said:
I was having the same issue when I tried to port Sprint 4.4.4 It would boot but I get black screen... Are you sure you flashed the 4.4.4 bootloader?
I would try to make a deodex 4.4.4 system flashable zip and flash and then right after it reboot to odin and flash the 4.4.4 kernel might work without flashing the bootloader and that way we have a working SS.
Click to expand...
Click to collapse
joseph- said:
Can you upload please
Click to expand...
Click to collapse
The only way to tell if it will work is to have someone flash just the system when its a flashable zip and then reboot to download and flash kernel via odin
gypsy214 said:
I was having the same issue when I tried to port Sprint 4.4.4 It would boot but I get black screen... Are you sure you flashed the 4.4.4 bootloader?
I would try to make a deodex 4.4.4 system flashable zip and flash and then right after it reboot to odin and flash the 4.4.4 kernel might work without flashing the bootloader and that way we have a working SS.
Click to expand...
Click to collapse
I tried that and it didn't work. The NC4 bootloader won't let you use the NJ6 boot.img. It gives the unauthorized software message.

(Q) Cant install ROMs

Hello there i have G850F and i can not install roms every time i try i softbrick my phone then i have to restore it
Once i install rom i get stuck on fisrt boot screen (galaxy alpha powerd by android) and it dosent move from there then i have to restore
i use TWRP and Eudemony V3 4.4.4ROM
I do factory reset every time
Am trying to install
Resurrection_Remix_LP_v5.4.7-20150609-slte
Or
SMG850F_GalaxyS6Themed_2.5
I think this because my current rom
amer187k said:
Hello there i have G850F and i can not install roms every time i try i softbrick my phone then i have to restore it
Once i install rom i get stuck on fisrt boot screen (galaxy alpha powerd by android) and it dosent move from there then i have to restore
i use TWRP and Eudemony V3 4.4.4ROM
I do factory reset every time
Am trying to install
Resurrection_Remix_LP_v5.4.7-20150609-slte
Or
SMG850F_GalaxyS6Themed_2.5
I think this because my current rom
Click to expand...
Click to collapse
If you are still on kitkat and you want to go to lolipop then you need the flash a stock LP rom before you can go to custom one.
Sent from my SM-G850F
tileeq said:
If you are still on kitkat and you want to go to lolipop then you need the flash a stock LP rom before you can go to custom one.
Sent from my SM-G850F
Click to expand...
Click to collapse
After I flashed stock LP I had to flash my KK modem because my phone wasn't booting.
Is that normal?
Or maybe I should have flashed twrp, fully wiped everything then flahed LP
Idk, now I'm still stuck with kk modem :/
RobertAslan said:
After I flashed stock LP I had to flash my KK modem because my phone wasn't booting.
Is that normal?
Or maybe I should have flashed twrp, fully wiped everything then flahed LP
Idk, now I'm still stuck with kk modem :/
Click to expand...
Click to collapse
Iy maybe thw cause of problems. Try going clean install and no switching files.
Sent from my SM-G850F
modem also must be LP,or you should go in no network
why you are stick to 444 modem?I use now France XEF modem but LP,& live in Macedonia

[ROM][6.0.1][UNOFFICIAL]Paranoid Android 6.0 for Galaxy S6 [AOSP]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys! Paranoid Android is finally back!
Here I built a first release to share with you. The rom is based on AOSP sources, Paranoid code and Cyanogenmod stability fixes, plus other things hand-written for S6 good compatibility. Now stop talking and enjoy Paranoid!
Disclaimer:
I take no responsibility for lost data, broken devices or anything else you encountered
during/after flashing this ROM.
You are responsible for what you are using on your devices!
Do some research before doing anything and always make sure to have a backup!
Click to expand...
Click to collapse
NOTE: This ROM is based on AOSP. So make sure you follow exactly the steps I write to install.
Download:
Mod Edit
Link removed
Bugs:
some lags, camera starts 50% of times, frame drops here and there playing videos.
Steps:
flash 5.1.1 with odin (cause of bootloader)
flash paranoid (gapps not now, it won't boot!)
reboot
back to recovery
system and cache wipe
flash gapps
reboot
Credits:
Paranoid Android team
CyanogenMod team
Slim team (AOSP-CAF)
tdcfpp
Sources:
Exynos
And some personal fixes I'm still working on
XDA:DevDB Information
Paranoid Android, ROM for the Samsung Galaxy S6
Contributors
Tonylel
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Beta
Created 2016-07-29
Last Updated 2016-07-29
hey man. I am willing to test this ROM, but you are telling us to flash android 5.1.1 to our phone? I mean, the title is saying that It is Android 6.0.1?
I am willing to test this rom too. But we have bootloader for android 6 and we cannot flash back to bootloader 5.1.1. How can we flash this Rom exactly? Which bootloader exatly do you mean??
Gesendet von meinem SM-G925F mit Tapatalk
alfo2004 said:
I am willing to test this rom too. But we have bootloader for android 6 and we cannot flash back to bootloader 5.1.1. How can we flash this Rom exactly? Which bootloader exatly do you mean??
Click to expand...
Click to collapse
Mr.pakkis said:
hey man. I am willing to test this ROM, but you are telling us to flash android 5.1.1 to our phone? I mean, the title is saying that It is Android 6.0.1?
Click to expand...
Click to collapse
You need to flash the stock Android 5.1.1 Rom with Odin because you cant flash the cm 13 Rom over an Android M bootloader (kernel not seandroid enforcing)
Tonylel said:
You need to flash the stock Android 5.1.1 Rom with Odin because you cant flash the cm 13 Rom over an Android M bootloader (kernel not seandroid enforcing)
Click to expand...
Click to collapse
Doesn't exactly make sense that it says Kernel not seandroid enforcing, when its a bootloader problem, and the fact that he is calling it a 6.0.1 ROM, when he asks us to DOWNgrade. I mean, what about all the 6.0.1 functions? Will we loose them? Like doze etc..
Woah, nice one, out of nowhere.
How did you get the camera partially working? Hopefully your hard work can help our progress with this device.
Any links for a SM-g925F 5.1.1 file?
holy ****. amazing
too bad i cant flash it cuz my chqrging port is broken..and odin dsnt recognize my phone anymore((
Tonylel said:
Steps:
flash 5.1.1 with odin (cause of bootloader)
flash paranoid (gapps not now, it won't boot!)
reboot
back to recovery
system and cache wipe
flash gapps
reboot
Click to expand...
Click to collapse
These steps make no sense. Why would you flash paranoid and later wipe the system to flash gapps.. ? When you wipe system the paranoid will be gone too.
Btw the install is taking ages..stuck at "patching system image unconditionally" for like an half hour..
I cant downgrade. Any help guys? it fails at the NAND write start...
Mr.pakkis said:
I cant downgrade. Any help guys? it fails at the NAND write start...
Click to expand...
Click to collapse
Just flash the 5.1.1 bootloader for 925f
In Odin flash it under BL
What about fingerprint?
Quintz said:
Just flash the 5.1.1 bootloader for 925f
In Odin flash it under BL
Click to expand...
Click to collapse
Its really hard to find a link. Do you have one?
Mr.pakkis said:
Its really hard to find a link. Do you have one?
Click to expand...
Click to collapse
I already gave you the link -.- => Click on the "925f"
Quintz said:
I already gave you the link -.- => Click on the "925f"
Click to expand...
Click to collapse
xD sorry, didnt see it. I tried, but when I try to use the choose the file, I get an error saying md5 error! Binary is invalid
What to do now...? Can I perhaps try to flash it under AP?
Edit; It doesnt work underneath AP.
Mr.pakkis said:
xD sorry, didnt see it. I tried, but when I try to use the choose the file, I get an error saying
What to do now...? Can I perhaps try to flash it under AP?
Edit; It doesnt work underneath AP.
Click to expand...
Click to collapse
Reason why you get the error is because you need the delete the .md5 extension from the name just to be .tar. Anyway dont risk it and flash the bootloader i post now.
1. Are you sure you have a 925F not 925I or something.
2.Try this bootloader: https://www.androidfilehost.com/?fid=24052804347786560
I wonder if you can install the rom because for my its busy installing for 30+ min.
Quintz said:
Reason why you get the error is because you need the delete the .md5 extension from the name just to be .tar. Anyway dont risk it and flash the bootloader i post now.
1. Are you sure you have a 925F not 925I or something.
2.Try this bootloader: https://www.androidfilehost.com/?fid=24052804347786560
I wonder if you can install the rom because for my its busy installing for 30+ min.
Click to expand...
Click to collapse
I am 100% positive I have a 925F. Used tons of ROMs, flashed kernels and generally changing stuff on my phone. After flashing the bootloader, should I boot into the recovery and install the ROM?
Not working
I have tried flashing this rom for like 5 times. Every time it get stuck on this:
"patching system image unconditionally"
What I did was:
- Install Lollipop
- Root
- TWRP Recovery
- Flash Rom
I will request you to please provide more detailed steps.
Well, I think that the developer should add support for the 6.0.1 bootloader...
---------- Post added at 07:28 PM ---------- Previous post was at 07:25 PM ----------
Also didnt work either. In the corner of the download side its written SW REV. CHECK FAIL. DEVICE: 3, BINARY: 2
Yes guys you can just flash bootloader 5.1.1 only. This allows aosp flash, it won't downgrade to 5.1.1, the flash will UPGRADE to 6.0.1 later.
For those who have some problem while flashing try perform a full wipe (system/cache/dalvik) and if still persist try change/update your recovery.
Right, I forgot: fingerprint not working because really no sources for that.

Categories

Resources