This is literally just the Odin Flashable bootloader and tar files. These files don't allow direct flashing of lp from nk2 as previously suspected. As there are some new differences between nk2 and lp that don't allow this. This is basically obsolete for general use. Ill leave the files for a few of those that are on roms like cm12 and some nk2 that want to use the modem.
{
"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"
}
Downloads:
Modem : here
Bootloader : here
sms gps
Will flashing these fix sms and gps issues on lp roms?
When I took the Ota from NK2 to BOB7. After that I jacked it up and I was able to go back to NK2 via Odin. Is it me or did it used to be once you updated to new version of Android you couldn't go back? Or is it how you update?
Can you get the stock kernel?
MJ523 said:
Will flashing these fix sms and gps issues on lp roms?
Click to expand...
Click to collapse
Not likely, this is for OFFICIAL BOB7 roms. (which there is only 1 currrently out and it doesn't have either of those problems to my knowledge)
sml2004 said:
When I took the Ota from NK2 to BOB7. After that I jacked it up and I was able to go back to NK2 via Odin. Is it me or did it used to be once you updated to new version of Android you couldn't go back? Or is it how you update?
Click to expand...
Click to collapse
You can go back, some devices don't allow you to downgrade. Its normally a bootloader things to not allow this. But they were nice and allowed it this time. Rom's seem to be able to be flashed (if you have a custom kernel to flash) on the newer bootloaders as well.
Androidwarrior said:
Can you get the stock kernel?
Click to expand...
Click to collapse
Search Function. Not going to confuse ODIN flashables and recovery flashables in the same area.
millerboy3 said:
Not likely, this is for OFFICIAL BOB7 roms. (which there is only 1 currrently out and it doesn't have either of those problems to my knowledge)
You can go back, some devices don't allow you to downgrade. Its normally a bootloader things to not allow this. But they were nice and allowed it this time. Rom's seem to be able to be flashed (if you have a custom kernel to flash) on the newer bootloaders as well.
Search Function. Not going to confuse ODIN flashables and recovery flashables in the same area.
Click to expand...
Click to collapse
Thanks for your help.
Flashed the bootloader and modem successfully. Cant activate phone on Sprint network so no OTA.
BOB7 shows up in About device.
Flash LP ViSion-X Rom , reboot loop at startup.
Maybe the DL of the rom was corrupt...doubtful. Will try again.
Anyway this is just a note for people in similar situation who want to update to TW LP.
At any rate, thanks so much for the BL and Modem tar files.
oa12 said:
Flashed the bootloader and modem successfully. Cant activate phone on Sprint network so no OTA.
BOB7 shows up in About device.
Flash LP ViSion-X Rom , reboot loop at startup.
Maybe the DL of the rom was corrupt...doubtful. Will try again.
Anyway this is just a note for people in similar situation who want to update to TW LP.
At any rate, thanks so much for the BL and Modem tar files.
Click to expand...
Click to collapse
I had this same problem trying to flash a LP rom.
Can I flash just the modem over a CM12 based rom?
I realize that historically modems have nothing to do with the OS but I am already on a CM12 based rom and have TWRP recovery installed.
Thank you!
hermeticist said:
Can I flash just the modem over a CM12 based rom?
I realize that historically modems have nothing to do with the OS but I am already on a CM12 based rom and have TWRP recovery installed.
Thank you!
Click to expand...
Click to collapse
I guess you could try. Not sure what it will do for/with CM12 at all. I'm only aware of the effects on TW based LP.
oa12 said:
Flashed the bootloader and modem successfully. Cant activate phone on Sprint network so no OTA.
BOB7 shows up in About device.
Flash LP ViSion-X Rom , reboot loop at startup.
Maybe the DL of the rom was corrupt...doubtful. Will try again.
Anyway this is just a note for people in similar situation who want to update to TW LP.
At any rate, thanks so much for the BL and Modem tar files.
Click to expand...
Click to collapse
treo4life said:
I had this same problem trying to flash a LP rom.
Click to expand...
Click to collapse
I did the same thing when I first made this. It did work however going from KK custom rom-> LP custom rom with this method. Didn't try a fresh install of LP with it however. I'm doing more testing now. But the files themselves are good, came from the official tar and packaged correctly in the correct order. So Not sure what the problem is. It seems as though the bootloader isn't sticking? I'm getting a bootloop like I'm not on LP when I flash the bootloader/modem from stock nk2 -> stock LP. I'll double check things.
millerboy3 said:
I guess you could try. Not sure what it will do for/with CM12 at all. I'm only aware of the effects on TW based LP.
Click to expand...
Click to collapse
Generally newer modems include some network performance upgrades.
millerboy3 said:
I did the same thing when I first made this. It did work however going from KK custom rom-> LP custom rom with this method. Didn't try a fresh install of LP with it however. I'm doing more testing now. But the files themselves are good, came from the official tar and packaged correctly in the correct order. So Not sure what the problem is. It seems as though the bootloader isn't sticking? I'm getting a bootloop like I'm not on LP when I flash the bootloader/modem from stock nk2 -> stock LP. I'll double check things.
Click to expand...
Click to collapse
Thanks for the update, im trying it again with another LP rom, keep us updated on what you find.:good:
UPDATE: it failed trying on another LP rom as well..
hermeticist said:
Can I flash just the modem over a CM12 based rom?
I realize that historically modems have nothing to do with the OS but I am already on a CM12 based rom and have TWRP recovery installed.
Thank you!
Click to expand...
Click to collapse
yes I did, after the boot loop trouble. I restored cm12 with BOB7 modem and BL and it worked fine.
LP OTA tar for Odin was posted here:
http://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3056478
flashed Odin and worked. Currently updating apps.
edit- sammobile has posted the official stock for 910P! woot! let the games begin.
oa12 said:
yes I did, after the boot loop trouble. I restored cm12 with BOB7 modem and BL and it worked fine.
LP OTA tar for Odin was posted here:
http://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3056478
flashed Odin and worked. Currently updating apps.
edit- sammobile has posted the official stock for 910P! woot! let the games begin.
Click to expand...
Click to collapse
The link is the same file as Sammobile. Just faster download.
I just wanted to point this out for people who might not know. This is only the Lollipop BOB7 modem & bootloader and it's purpose is straight forward for those who need it. Thanks for sharing @millerboy3
However, in order to fully and correctly upgrade from any KK rom you will first need to either take the Lollipop ota update OR odin flash the BOB7 stock rom tar. There are several other partitions that must be written/updated. If you've never updated to Lollipop by one of these two methods then you really need to. So in other words you can't simply flash this modem/bootloader tar and expect to be able to flash a custom Lollipop rom without problems.
tx_dbs_tx said:
I just wanted to point this out for people who might not know. This is only the Lollipop BOB7 modem & bootloader and it's purpose is straight forward for those who need it. Thanks for sharing @millerboy3
However, in order to fully and correctly upgrade from any KK rom you will first need to either take the Lollipop ota update OR odin flash the BOB7 stock rom tar. There are several other partitions that must be written/updated. If you've never updated to Lollipop by one of these two methods then you really need to. So in other words you can't simply flash this modem/bootloader tar and expect to be able to flash a custom Lollipop rom without problems.
Click to expand...
Click to collapse
Correct after testing and testing we discovered this. Editing the op for the file usages. Thanks @tx_dbs_tx for confirming our suspicions!
tx_dbs_tx said:
I just wanted to point this out for people who might not know. This is only the Lollipop BOB7 modem & bootloader and it's purpose is straight forward for those who need it. Thanks for sharing @millerboy3
However, in order to fully and correctly upgrade from any KK rom you will first need to either take the Lollipop ota update OR odin flash the BOB7 stock rom tar. There are several other partitions that must be written/updated. If you've never updated to Lollipop by one of these two methods then you really need to. So in other words you can't simply flash this modem/bootloader tar and expect to be able to flash a custom Lollipop rom without problems.
Click to expand...
Click to collapse
I'm a little confused by this.
I've been on a CM12 based lollipop rom for a couple months now.
I flashed the modem and have already noticed improved handover.
Are you saying that I should flash the bootloader as well?
(ie back up my system, flash bootloader, then restore recovery and system).
Mods please close this thread.
Thread closed at OP request
Edfunkycold
Have a great day!
Related
Hi
My LG G2 is currently running Software Version "D80220c" which is "Kitkat 4.4.2"
It's not rooted or anything. It's in devices stock form.
In order to install Cloudy G3 rom, what should i do?
Like root install some custom recovery and then the rom? (I am sort of new to these stuffs)
If there is a complete video instruction then please do share.
Thanks
in_core said:
Hi
My LG G2 is currently running Software Version "D80220c" which is "Kitkat 4.4.2"
It's not rooted or anything. It's in devices stock form.
In order to install Cloudy G3 rom, what should i do?
Like root install some custom recovery and then the rom? (I am sort of new to these stuffs)
If there is a complete video instruction then please do share.
Thanks
Click to expand...
Click to collapse
You should root your device first(use towelroot to root your device, link: https://towelroot.com/ ) and after you done rooting, install authored for a custom recovery, link: http://www.droidviews.com/install-twrp-recovery-on-lg-g2-running-android-4-4-2-kitkat/, what phone carrier are you subscribed to?
Sent from my LG-LS980 using Tapatalk
TechGirl90 said:
You should root your device first(use towelroot to root your device, link: https://towelroot.com/ ) and after you done rooting, install authored for a custom recovery, link: http://www.droidviews.com/install-twrp-recovery-on-lg-g2-running-android-4-4-2-kitkat/, what phone carrier are you subscribed to?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I am using the D802 international unlocked version
I am currently running LG's Stock Kitkat firmware. In CloudyG3 thread they mentioned about flashing Kitkat baseband. Thats what actually got me confused as i already have official kitkat lg rom installed so if i need to do that
in_core said:
I am using the D802 international unlocked version
I am currently running LG's Stock Kitkat firmware. In CloudyG3 thread they mentioned about flashing Kitkat baseband. Thats what actually got me confused as i already have official kitkat lg rom installed so if i need to do that
Click to expand...
Click to collapse
no there is no need to flash the kk baseband if you are already on official kk, it is placed in instructions of most kk roms to flash kk baseband because some people are going from jb to kk and they need kk baseband
in_core said:
I am using the D802 international unlocked version
I am currently running LG's Stock Kitkat firmware. In CloudyG3 thread they mentioned about flashing Kitkat baseband. Thats what actually got me confused as i already have official kitkat lg rom installed so if i need to do that
Click to expand...
Click to collapse
The kit Kat baseband only applies if you already have a custom Rom installed (like Cyanogenmod, Paranoid Android, or Mahdi Rom, etc), and you're trying to flash CloudyG3 Rom, you'll need the kit Kat baseband for your variant for the Rom to recognize you device, but since you're stock rooted, no need to go through the kit Kat baseband procedure, just backup all of your files in TWRP, and proceed with the steps of installing CloudyG3 in the CloudyG3 Thread by the OP, good luck[emoji4][emoji106]
Sent from my LG-LS980 using Tapatalk
The towelroot is supposed to say "Make it ra1n" but it says "ra1r"
"Also it says If phone reboots, towelroot failed"
Anyways i tried to too root but it says my device aint supported. Is there any other easy method like this? That can root with a click or so
{
"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"
}
in_core said:
The towelroot is supposed to say "Make it ra1n" but it says "ra1r"
"Also it says If phone reboots, towelroot failed"
Anyways i tried to too root but it says my device aint supported. Is there any other easy method like this? That can root with a click or so
Click to expand...
Click to collapse
Hmmm, try out this link
http://forum.xda-developers.com/showthread.php?p=48709232
READ THE INSTRUCTIONS VERY CAREFULLY
Sent from my LG-LS980 using Tapatalk
TechGirl90 said:
Hmmm, try out this link
http://forum.xda-developers.com/showthread.php?p=48709232
READ THE INSTRUCTIONS VERY CAREFULLY
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Ok so i managed to root and use autorec to install twrp.
1. Do i need to run the autorec app everytime and proceed with the options to go to recovery? Or how do I get into custom recovery?
2. It installed TWRP 2.7. Now can i install any other roms like PA4.4.3+ and CM11 M9 from this version of TWRP?
in_core said:
Ok so i managed to root and use autorec to install twrp.
1. But after installing twrp Knock-On feature does not work for unlocking the screen. It can only be used for locking.
2. Do i need to run the autorec app everytime and proceed with the options to go to recovery? Or how do I get into custom recovery?
3. It installed TWRP 2.7. Now can i install any other roms like PA4.4.3+ and CM11 M9 from this version of TWRP?
Click to expand...
Click to collapse
1. Open Dialer in your Stock LG Rom, and put in this code 3845#*802#, and go to update touch firmware.
2. No you don't need to run the autorec app everytime, go to the playstore and install Rom manager, and there's an option that says "reboot into Recovery Mode', choose that option, and you'll automatically reboot into Recovery Mode.
3. Yes you can now install custom Roms like PA4.4.3+ and CM11 M9, just make sure you backup your Stock LG Rom.
TechGirl90 said:
1. Open Dialer in your Stock LG Rom, and put in this code 3845#*802#, and go to update touch firmware.
2. No you don't need to run the autorec app everytime, go to the playstore and install Rom manager, and there's an option that says "reboot into Recovery Mode', choose that option, and you'll automatically reboot into Recovery Mode.
3. Yes you can now install custom Roms like PA4.4.3+ and CM11 M9, just make sure you backup your Stock LG Rom.
Click to expand...
Click to collapse
Already found a thread regarding the Knock On issue and solved so edited it before you replied
Thanks a lot
Have a good day and keep helping us newbies and ones in trouble
in_core said:
Already found a thread regarding the Knock On issue and solved so edited it before you replied
Thanks a lot
Have a good day and keep helping us newbies and ones in trouble
Click to expand...
Click to collapse
No Problem[emoji4][emoji4], glad that it worked out for you, you too have a good day.[emoji106][emoji106]
Sent from my LG-LS980 using Tapatalk
Thanks for the thread. Found answers I was looking for.
Thanks to this thread, now i know ive learned many new things i was searching for. Thanks to the Op as well as the person who was helping the OP . Kudos and cheers. ^.^ !!
Questions -
1. So, i have kk 4.4.2 on my lg g2 d802, so if i was going to install Cloudyg2 3.3 LP, i need to flash LP baseband first so the LP roms could detect eh?
2. Can i install custom roms using autorec? I mean ,yes i did backup on the internal storage and all (no sd card slots), will it wipe my backup if supoose i have to install roms that requires clean or full wipe?
{
"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"
}
Ok so hear is the problem. I bricked my g2 and had to flash back to stock. so i Used stump root to gain root again and flash recovery. But when i go to flash anything i get a failed updater binary. i have never had this problem before. i would appreciate any help. would like to try some of the 5.0 roms.
pcwizkid1994 said:
Ok so hear is the problem. I bricked my g2 and had to flash back to stock. so i Used stump root to gain root again and flash recovery. But when i go to flash anything i get a failed updater binary. i have never had this problem before. i would appreciate any help. would like to try some of the 5.0 roms.
Click to expand...
Click to collapse
I think maybe you flash the wrong version of your phone. (D80x, F320x.....)
fong360 said:
I think maybe you flash the wrong version of your phone. (D80x, F320x.....)
Click to expand...
Click to collapse
I think I added the error pic the the op . I have the vs980 version but it also happens with the G3 roms.
pcwizkid1994 said:
I think I added the error pic the the op . I have the vs980 version but it also happens with the G3 roms.
Click to expand...
Click to collapse
Maybe its something wrong with the zip file.. i saw another user posting that he couldnt flash android L using the same version of TWRP like you.. and you are saying that you cant flash G3 ROMs like CloudyG3 or OptimusG3 but other ROMs are working?
Look here: http://forum.xda-developers.com/lg-g2/help/error-executing-updater-binary-zip-twrp-t2988604/page2
Read the last post, but i dont recommend you to flash the first version of TWRP (2.7.0.0) you could try a newer one but if dont works then try 2.7.0.0
EDIT: I see there a loki error... how did you flashed the TWRP? did you used AUTOREC? if not, did you downgraded the bootloader to JB ?
raulx222 said:
Maybe its something wrong with the zip file.. i saw another user posting that he couldnt flash android L using the same version of TWRP like you(i dont know if he managed it to work).. and you are saying that you cant flash G3 ROMs like CloudyG3 or OptimusG3 but other ROMs are working?
Click to expand...
Click to collapse
None of the roms I am trying to use are flashing. All give the same error.
raulx222 said:
Maybe its something wrong with the zip file.. i saw another user posting that he couldnt flash android L using the same version of TWRP like you.. and you are saying that you cant flash G3 ROMs like CloudyG3 or OptimusG3 but other ROMs are working?
Look here: http://forum.xda-developers.com/lg-g2/help/error-executing-updater-binary-zip-twrp-t2988604/page2
Read the last post, but i dont recommend you to flash the first version of TWRP (2.7.0.0) you could try a newer one but if dont works then try 2.7.0.0
EDIT: I see there a loki error... how did you flashed the TWRP? did you used AUTOREC? if not, did you downgraded the bootloader to JB ?
Click to expand...
Click to collapse
When I bricked I had to flash back to jb and took ota to get back to kitkat. And I used flashily to flash the recovery.
pcwizkid1994 said:
When I bricked I had to flash back to jb and took ota to get back to kitkat. And I used flashily to flash the recovery.
Click to expand...
Click to collapse
Ok.. and I think that you used the BUMPed TWRP by Blastagator? you also need to downgrade your bootloader to JB
Uhm.. if you used AutoRec it will downgrade the bootloader automatically..JB bootloader is essential!.. you had luck that you got that error, if you would successfully flashed any ROM your phone would hard brick because you are using the KK bootloader right now and the loki patch gives you a error..loki works only with JB bootloader
Next time when you go to stock:
- root using ioroot OR towelroot + supersu from market
- use AutoRec to flash recovery (this will also downgrade from KK bootloader to JB bootloader)
- update recovery (flash the latest version) *recommended but not obligatory
So.. right now you need to flash the JB bootloader in order to can install other ROMs but I dont think that somebody made flashable zip with vs980 bootloader :/.. you could extract yourself the bootloader from the KDZ firmware file..But I think its easier just to reflash the firmware using flash tool and then use AutoRec
raulx222 said:
Ok.. and I think that you used the BUMPed TWRP by Blastagator? you also need to downgrade your bootloader to JB
Uhm.. if you used AutoRec it will downgrade the bootloader automatically..JB bootloader is essential!.. you had luck that you got that error, if you would successfully flashed any ROM your phone would hard brick because you are using the KK bootloader right now and the loki patch gives you a error..loki works only with JB bootloader
Next time when you go to stock:
- root using ioroot OR towelroot + supersu from market
- use AutoRec to flash recovery (this will also downgrade from KK bootloader to JB bootloader)
- update recovery (flash the latest version) *recommended but not obligatory
So.. right now you need to flash the JB bootloader in order to can install other ROMs but I dont think that somebody made flashable zip with vs980 bootloader :/.. you could extract yourself the bootloader from the KDZ firmware file..But I think its easier just to reflash the firmware using flash tool and then use AutoRec
Click to expand...
Click to collapse
Thanks for the reply! I have a question tho. When i restored the first time towel root did not root that is why i used stump root. any idea why?
pcwizkid1994 said:
Thanks for the reply! I have a question tho. When i restored the first time towel root did not root that is why i used stump root. any idea why?
Click to expand...
Click to collapse
Uhm..i think because it doesnt work on the latest update of our firmware..use ioroot instead
raulx222 said:
Uhm..i think because it doesnt work on the latest update of our firmware..use ioroot instead
Click to expand...
Click to collapse
For some reason i dont have the stock recovery menu where i need to select sideload for adb. do you have any idea why that is?
pcwizkid1994 said:
For some reason i dont have the stock recovery menu where i need to select sideload for adb. do you have any idea why that is?
Click to expand...
Click to collapse
you are saying that you are trying to root via ioroot and it doesnt boot into the stock recovery?.. you still have TWRP :/?
raulx222 said:
you are saying that you are trying to root via ioroot and it doesnt boot into the stock recovery?.. you still have TWRP :/?
Click to expand...
Click to collapse
Ya trying to root with ioroot but there is just a little android guy there and a red exclamation point.
pcwizkid1994 said:
Ya trying to root with ioroot but there is just a little android guy there and a red exclamation point.
Click to expand...
Click to collapse
Uh.. :/..i dont know.. you followed the instructions properly ? http://forum.xda-developers.com/showthread.php?t=2448887 ..i dont have my D802 until next week..
raulx222 said:
Uh.. :/..i dont know.. you followed the proper instructions ? http://forum.xda-developers.com/showthread.php?t=2448887 ..i dont have my D802 until next week..
Click to expand...
Click to collapse
Yes i did. I think i am going to try and root with sump root again and then use autorec to flash recovery. Because stump root gave me root before but was having problems with jb bootstack.
raulx222 said:
Uh.. :/..i dont know.. you followed the instructions properly ? http://forum.xda-developers.com/showthread.php?t=2448887 ..i dont have my D802 until next week..
Click to expand...
Click to collapse
Just thought i would give you a update. I restored to stock and then used stump root to root and auto rec to instell recovery. Every thing is working like a charm now. Thanks for the help i appreciate it!
I seem to be having an issue with downgrading my S5 G900H Exynos to Kitkat from Lollipop BOAD. I've tried 4 different stock Kitkat firmwares from sammobile but all of them cause the phone to hang at the Samsung logo however I can flash back to stock lollipop BOAD and it works fine again.
ODIN gives me no errors when I try to flash kitkat or lollipop and infact both gives the "PASS!" mark what should I do?
I downgraded to KK from LP the other day, and ended up stuck at the Samsung logo too
Tried factory resetting, didn't work
The only thing that finally worked was flashing the same KK ROM again over the top of the one that got stuck at the Logo
Once I'd done that, it booted
*Detection* said:
I downgraded to KK from LP the other day, and ended up stuck at the Samsung logo too
Tried factory resetting, didn't work
The only thing that finally worked was flashing the same KK ROM again over the top of the one that got stuck at the Logo
Once I'd done that, it booted
Click to expand...
Click to collapse
Doesn't seem to work for me bud
CntrlAltDel45 said:
Doesn't seem to work for me bud
Click to expand...
Click to collapse
You might need to flash the PIT file for your model S5, maybe the partitions are different between ROMs for that specific model
Be sure to get the exact PIT file though or you'll brick it
PIT file and KK ROM in ODIN at the same time, it will flash the PIT, then it will flash the ROM
*Detection* said:
You might need to flash the PIT file for your model S5, maybe the partitions are different between ROMs for that specific model
Be sure to get the exact PIT file though or you'll brick it
PIT file and KK ROM in ODIN at the same time, it will flash the PIT, then it will flash the ROM
Click to expand...
Click to collapse
I cant seem to find those pit files bud
CntrlAltDel45 said:
I cant seem to find those pit files bud
Click to expand...
Click to collapse
Check here, post 2
http://forum.xda-developers.com/showthread.php?t=2737448
*Detection* said:
Check here, post 2
http://forum.xda-developers.com/showthread.php?t=2737448
Click to expand...
Click to collapse
Thanks for your support so far bud but the pit file there for my phone model is only for 16GB versions and mine is 32GB
CntrlAltDel45 said:
Thanks for your support so far bud but the pit file there for my phone model is only for 16GB versions and mine is 32GB
Click to expand...
Click to collapse
No probs, I`ll see if I can find one, in the meantime try requesting it in that thread
*Detection* said:
No probs, I`ll see if I can find one, in the meantime try requesting it in that thread
Click to expand...
Click to collapse
It is possible for me to reflash the phone with lollipop firmware and install custom recovery could I flash stock rom via that custom recovery?
CntrlAltDel45 said:
It is possible for me to reflash the phone with lollipop firmware and install custom recovery could I flash stock rom via that custom recovery?
Click to expand...
Click to collapse
You could flash a custom recovery like TWRP, but unless someone has made a flashable zip of the stock firmware for custom recovery it'll not work
You could flash a custom KitKat ROM from TWRP
The only method that works for mine is flashing CF Auto Root, to gain root, then using TWRP manager from Google Play to install TWRP Recovery
This will void your warranty though
*Detection* said:
You could flash a custom recovery like TWRP, but unless someone has made a flashable zip of the stock firmware for custom recovery it'll not work
You could flash a custom KitKat ROM from TWRP
The only method that works for mine is flashing CF Auto Root, to gain root, then using TWRP manager from Google Play to install TWRP Recovery
This will void your warranty though
Click to expand...
Click to collapse
Mine is similar to that too. I have to install CF Auto Root first and then install Flashify and then install TWRP via flashify img file to gain custom recovery
Might be worth flashing a custom KK ROM, then trying to flash stock over the top after 100% wiping everything & formatting from TWRP advanced wipe
*Detection* said:
Might be worth flashing a custom KK ROM, then trying to flash stock over the top after 100% wiping everything & formatting from TWRP advanced wipe
Click to expand...
Click to collapse
I'm working on that now mate. I appreciate your assistance so far.
No bother, Lollipop not your taste?
I went back to KK just to see what everyone was on about, lasted a couple hours and flashed back to LP, some people get great LP performance, some bad, for me LP is way better
*Detection* said:
No bother, Lollipop not your taste?
I went back to KK just to see what everyone was on about, lasted a couple hours and flashed back to LP, some people get great LP performance, some bad, for me LP is way better
Click to expand...
Click to collapse
I actually prefer lollipop over kitkat but the performance is horrible and i have to charge my phone 3 times daily
CntrlAltDel45 said:
I actually prefer lollipop over kitkat but the performance is horrible and i have to charge my phone 3 times daily
Click to expand...
Click to collapse
Stupid question, but you did factory reset after upgrading to LP?
KK leaves behind rubbish files which cause battery drain, I got the same after first upgrade, but after a reset, it has been great since
Performance is definitely better with LP this end too, but you're not alone, the majority who upgraded say KK is way better atm
*Detection* said:
Stupid question, but you did factory reset after upgrading to LP?
KK leaves behind rubbish files which cause battery drain, I got the same after first upgrade, but after a reset, it has been great since
Performance is definitely better with LP this end too, but you're not alone, the majority who upgraded say KK is way better atm
Click to expand...
Click to collapse
Yep bud.
I decided to install a custom lollipop rom Zephyr Lite to address the battery and performance issues, if it works out well I will use it as my daily driver.
Nice one, fingers crossed
*Detection* said:
Nice one, fingers crossed
Click to expand...
Click to collapse
I installed a custom rom called XtreSoLite with Aroma addon and so far I'm happy with it. I tried Zypher Lite but it didn't work, rooting failed and had all sorts of problems so I'm glade to say I'll stay with XtreSoLite for now.
Thanks for your help mate
Good stuff, I was gonna suggest that exact ROM weirdly, I haven't tried it yet but heard good things about it
A new superSu was released. It will give you systemless root on Samsung TW 5.1.1 and does not require a cutom kernel.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
It also looks like CF Auto root for DOK2 firmware has been updated as well using the newest SUPERSU.
https://autoroot.chainfire.eu/
Nice! For some reason, Link isn't working for me.
Bruce lee roy said:
Nice! For some reason, Link isn't working for me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
ShrekOpher said:
A new superSu was released. It will give you systemless root on Samsung TW 5.1.1 and does not require a cutom kernel.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
Did you tried it?
Avide said:
Did you tried it?
Click to expand...
Click to collapse
Yeah I'm on stock DOK2 firmware, and I have root using the stock kernel.
However V4A will not work right now, it is not compatible with systemless root. Besides that everything is working great.
ShrekOpher said:
Yeah I'm on stock DOK2 firmware, and I have root using the stock kernel.
However V4A will not work right now, it is not compatible with systemless root. Besides that everything is working great.
Click to expand...
Click to collapse
Why do you prefer stock over custom?
Bruce lee roy said:
Why do you prefer stock over custom?
Click to expand...
Click to collapse
I did this so I can use Android Pay, not because of kernels, but in general a stock kernel is going to be more stable and cause less issues.
ShrekOpher said:
Yeah I'm on stock DOK2 firmware, and I have root using the stock kernel.
However V4A will not work right now, it is not compatible with systemless root. Besides that everything is working great.
Click to expand...
Click to collapse
Could you post some steps on how to use this new systemless root on the Note4?
chodaboy19 said:
Could you post some steps on how to use this new systemless root on the Note4?
Click to expand...
Click to collapse
If your on the stock firmware you just flash the new SuperSu.Zip in TWRP, it's available in the thread linked in the OP. And you will have root, no need to flash a custom kernel.
I tested this system less root out earlier and it doesn't seem like it's 100% stable. I was on stock dok2 freshly Odin and then flash this system less root. Titanium back up doesn't Uninstall system apps (debloat), after you restart your phone the apps remains intact. Anyone else?
I just tried this out. I was rooted on 4.4.4 NK4. So far everything seems to be working fine. I froze and defrosted some apps using Titanium backup without any problems. I will keep an eye on things as I use 5.1.1, but from a casual glance, it looks like a nice update.
Steps to install from 4.4.4:
1. Install the DOK2 image using ODIN
2. Install TWRP using ODIN
3. Install the SuperSU Beta zip using TWRP
aznvi3tric3guy said:
I tested this system less root out earlier and it doesn't seem like it's 100% stable. I was on stock dok2 freshly Odin and then flash this system less root. Titanium back up doesn't Uninstall system apps (debloat), after you restart your phone the apps remains intact. Anyone else?
Click to expand...
Click to collapse
If you read the forum that the zip is provided, you'd see it's not 100% yet. Still on beta phase but making it available because it's 'mostly' working.
{
"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"
}
Sent from my SM-N910T using Tapatalk
When booting are you getting the message: "Kernel is not SEAndroid Enforcing"?
Not sure, where I messed up...
aznvi3tric3guy said:
I tested this system less root out earlier and it doesn't seem like it's 100% stable. I was on stock dok2 freshly Odin and then flash this system less root. Titanium back up doesn't Uninstall system apps (debloat), after you restart your phone the apps remains intact. Anyone else?
Click to expand...
Click to collapse
Yeah, this is a systemless root. This means there are certain root apps that will not work correctly. Mainly things that modify the system. However, you can flash a debloater script in TWRP and remove the applications you want.
Right now removing system apps in Titanium Backup does NOT work, but freezing them all does. Also Viper4Android can't install the drivers. Both of these issues are related to the new Root Method.
However if there was a flashable zip to install the drivers for V4A I think the app itself would still work fine.
Remember this is a beta version of SuperSu and most of the developers have not adjusted the root apps to work with the new systemless root method.
chodaboy19 said:
When booting are you getting the message: "Kernel is not SEAndroid Enforcing"?
Not sure, where I messed up...
Click to expand...
Click to collapse
Yeah I get that as well, but if you go look at the About Phone screen once you are booted up you will see that you are still SE Android Enforcing. something with how this is gaining root access is making the boot sequence think you have modified the kernel, even though you have not.
So you guys are able to freeze system apps in TiBu, yes? I ask because this sounds an awful lot like how I was able to root my new Tab S2 a few weeks ago. If I'm onto anything here, then I would just make sure that everything related to Knox is frozen; all have Knox in the name except Security Log Agent but make sure that's frozen too. After getting that straightened out and learning which apps didn't currently cooperate, the tablet runs like a dream :angel:
There are still a few limitations and a handful of apps that don't seem to enjoy the situation, but I simply refuse not to administer my own device (I got the 817T, 9.7" Tmo variant). There are no custom/permissive kernels yet for that model yet as we're still waiting for the code to be released... , honestly makes me wish there was a GPL for individuals and another for "corporate entities" who've made billions off of generously GPLed work that had some (sharp) teeth and a taste of enforcement
Anyway, making sure that Knox is entirely frozen solid will hopefully help out anyone having issues. I'd also advise not going overboard with Xposed modules and making frequent Nandroids in case you get stuck in a bootloop or similar (happened to me after flashing the fix for FolderMount... just restored a Nandroid but I really miss FolderMount :crying
Hopefully that's of some help and I'm not just babbling about my sweet new tablet here... well, ya know, I suppose it can be two things
Can I install twrp without root ????
This will work for samsung 12.2 tab pro right???
ShrekOpher said:
I did this so I can use Android Pay, not because of kernels, but in general a stock kernel is going to be more stable and cause less issues.
Click to expand...
Click to collapse
Depends on the kernel...
As of right now BeastMost only has the root restriction removed, other then that its stock. (It still DOG1 as Sammy hasn't released the DOK2 source yet)
The reason freeza called his kernel BeastMode stock is because the only thing changed are tweaks no real mods.
For example some logging is turned off etc.
The things that are changed do not affect stability like a heavily modded kernel that needs a tweaker app etc.
(so long as the kernel that is compiled is for that carrier and that variant device)
Skrillexsgames said:
Can I install twrp without root ????
This will work for samsung 12.2 tab pro right???
Click to expand...
Click to collapse
yes you can, use odin
aznvi3tric3guy said:
I tested this system less root out earlier and it doesn't seem like it's 100% stable. I was on stock dok2 freshly Odin and then flash this system less root. Titanium back up doesn't Uninstall system apps (debloat), after you restart your phone the apps remains intact. Anyone else?
Click to expand...
Click to collapse
Try installing busy box from the Playstore.
So I had DarkLord N5 on my N9005 before, which was awesome, but it had performance issues (especially when gaming). Then i downgraded to Stock KitKat using Odin and after boot up It showed No Signal, and everything was freezing and force closing. I somehow went to settings and found that i also have issues with IMEI and Baseband version, it was all unknown. The worst part is i did not backup my EFS. Any help guys please :crying:
I also have no audio playback
Im no pro here, but as i found in my research it is hard to downgrade from lolipop to kitkat as in 5.0 new architecture has been presented which they called art. I think. So it gives lots of incompatibilities. I tried the same as you but i ended up going stock lolipop for a while.
Yesterday i flashed Ressurrection remix 6.0.1 Marshmallow based off Slim roms and CM and i admit this is so far best rom i have tested. (Unless you need all fancy spen features)
I'd try to stick to anything that is 5.1 or above since great battery life.
Sorry for not much info, but i couldn't get past your post unanswered.
oxoconstantineoxo said:
Im no pro here, but as i found in my research it is hard to downgrade from lolipop to kitkat as in 5.0 new architecture has been presented which they called art. I think. So it gives lots of incompatibilities. I tried the same as you but i ended up going stock lolipop for a while.
Yesterday i flashed Ressurrection remix 6.0.1 Marshmallow based off Slim roms and CM and i admit this is so far best rom i have tested. (Unless you need all fancy spen features)
I'd try to stick to anything that is 5.1 or above since great battery life.
Sorry for not much info, but i couldn't get past your post unanswered.
Click to expand...
Click to collapse
I had many experiences with downgrading from new version to old version with my S3 and my Note, but never had this issue. Something is causing this...
founded a old backup of CM11.. Flashed CWM and restored to CM. Works flawlessly, but still no sound and those stuff
Honix5962 said:
I had many experiences with downgrading from new version to old version with my S3 and my Note, but never had this issue. Something is causing this...
Click to expand...
Click to collapse
So i had problems with my either s2 or note 4.
But afaik if u have updated your bootloader there may be no way to get back. And lack of IMEI on reverted KitKat isn't anything new. I bet going simply to anything art. Based will do.
People here are arguing on same issues as yours. Just don't listen to these "flash with odin" guys.. This doesn't work. Even if u flash the stock one.
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
Hope you will dig up something.
You could try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Have you tried flashing to the latest stock rom for the phone using Odin?
audit13 said:
Have you tried flashing to the latest stock rom for the phone using Odin?
Click to expand...
Click to collapse
Nope, I downloaded the KitKat firmware from Sammobile, and I'm downloading the Lollipop one now.
deejhay14 said:
You could try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Click to expand...
Click to collapse
I tried it, but still no use :c
I would not try any other ROMs before trying to flash the latest stock rom from sammobile.com. Hopefully, this will resolve the baseband and imei issue. Sometimes, the missing or wrong imei is caused by a mismatch between the bootloader and modem firmware.
audit13 said:
I would not try any other ROMs before trying to flash the latest stock rom from sammobile.com. Hopefully, this will resolve the baseband and imei issue. Sometimes, the missing or wrong imei is caused by a mismatch between the bootloader and modem firmware.
Click to expand...
Click to collapse
I hope so.
I have seen this sort of problem on the Samsung s3 and note 3 phones.
audit13 said:
I have seen this sort of problem on the Samsung s3 and note 3 phones.
Click to expand...
Click to collapse
I did downgrading from 5.0 (CM12) to Stock 4.4 KitKat in my S3, but never had issues like this.
Downgrading from a cm rom to a stock rom via Odin can be fine because installing a cm rom does NOT alter the phone's bootloader or modem. Trying to downgrade from stock 4.4.2 to stock 4.3 with Odin on an s3 cannot be done.
audit13 said:
Downgrading from a cm rom to a stock rom via Odin can be fine because installing a cm rom does alter the phone's bootloader or modem. Trying to downgrade from stock 4.4.2 to stock 4.3 with Odin on an s3 cannot be done.
Click to expand...
Click to collapse
Oh, never knew about this, thanks for the info
Sorry, I meant to say that installing a cm rom DOES NOT change the bootloader or modem. When you flash back to stock via Odin, you are simply writing over the existing modem and bootloader with the same bootloader and modem if you are flashing the same stock rom that was on the phone before installing cm.
I flashed between KitKat and LP official just fine.
audit13 said:
Have you tried flashing to the latest stock rom for the phone using Odin?
Click to expand...
Click to collapse
Never mind, It works. Thanks for the help.
Which method worked? Thanks.
Use gsii repair