I just got a new Tmobile S5. SM-G900T is the model number
Was looking to confirm if this is the correct twrp for my device http://teamw.in/project/twrp2/229
When I used GooManager it said that it could not find a recovery for my device, but see where folks have mentioned that they had a little trouble with goo manager.
I've searched and this is the only version that I am finding for the LTE Tmobile devices.
As an aside to that, if I dl the tar for use with Odin, will this wipe the device if I choose to install it?
TWRP: http://forum.xda-developers.com/showthread.php?t=2727406
T-Mobile Specific Section: http://forum.xda-developers.com/tmobile-galaxy-s5
Flashing any unoffical non-Samsung recovery will trip your Knox warranty flag, making it void and it cannot be reset. What that means to you personally, I don't know.
Flashing any recovery via ODIN will not wipe your phone.
edit: I don't know much of anything about TWRP. I prefer Philz CWM Touch Recovery @ this thread: http://forum.xda-developers.com/showthread.php?t=2201860
For recoveries, you just need the KLTE version. That's the family our phone (G900T) is in.
github said:
TWRP: http://forum.xda-developers.com/showthread.php?t=2727406
T-Mobile Specific Section: http://forum.xda-developers.com/tmobile-galaxy-s5
Flashing any unoffical non-Samsung recovery will trip your Knox warranty flag, making it void and it cannot be reset. What that means to you personally, I don't know.
Flashing any recovery via ODIN will not wipe your phone.
edit: I don't know much of anything about TWRP. I prefer Philz CWM Touch Recovery @ this thread: http://forum.xda-developers.com/showthread.php?t=2201860
For recoveries, you just need the KLTE version. That's the family our phone (G900T) is in.
Click to expand...
Click to collapse
Thanks very much for your reponse, that version I posted is Labeled KLTE. From what I was finding last night that is what seemed to be correct, I just like measure twice and cut once....
I looked briefly at Philz last night. I switched from CWM to TWRP a bit ago and am just realy familiar with it. I could change if necessary, but it's like second nature to use now. That is the thread I glanced at last night, I will check it out more thoroughly to see if it is for me.
I flashed that Tar file and dont see any obvious issues. TWRP yay.
Related
Hi,
I am totally new to flashing phones, so I need your help. My aim is to flash my GT-I9100 (Vodafone UK) with Cynogen Mod Kitkat. Currently my phone has Android version of 4.1.2. I do not have root access to my phone and according to Cynogen Mode wiki, this is not necessary.
Apparently I can't post links before 10 posts, sorry I can't show the links from where I got the instructions.
I have 1st tried to flash a new recovery image so that Cynogen installation would be possible.
1) Heimdall Method as in the Cynogen Mode Wiki Page
2) Odin Method available on the internet.
In both I have been successful transferring the listed recovery images (6.0.4.7 and 6.0.2.9) to the phone but in both cases whenever the phone is restarted, the device is stuck with Samsung GT-I9100 logo and yellow triangle. I can't access to recovery mode at all.
I had to go back to the download mode again (luckily this worked) and flashed with the original firmware in each cases to recover the device.
I am also confused about the version of CWM as when I go to the original website, above versions are not listed under Galaxy S2.(Only 4.0.1.5 and 5.8.1.5)
Am I missing something here?
Many thanks.
hey,here's the instructions you need
http://forum.xda-developers.com/gal...om-official-cyanogenmod-11-nightlies-t2634693
a bit of search wouldn't hurt you know...
good luck:good:
TheImpossibleEnemy said:
hey,here's the instructions you need
http://forum.xda-developers.com/gal...om-official-cyanogenmod-11-nightlies-t2634693
a bit of search wouldn't hurt you know...
good luck:good:
Click to expand...
Click to collapse
Hi
Many thanks for your reply. Believe me I have gone through many posts and search before posting here. I have also checked the link but can't understand why I am encountering yellow triangle after CWM flashing. Am I suppose to flash something else as well together with the version 6.0.4.7?
Don't bother about that yellow triangle,it's normal.When you'll be done flashing your rom,use TriangleAway app to remove it.
TheImpossibleEnemy said:
Don't bother about that yellow triangle,it's normal.When you'll be done flashing your rom,use TriangleAway app to remove it.
Click to expand...
Click to collapse
But after I flash with CWM I can't get access to the recovery to install the rom? The only option I have is the download mode.
I thought after flashing with CWM the stock rom would work normally and flashing with custom rom could be done later if needed.
Just to iterate again, when I flash the recovery, phone does not switch on but stuck with yellow triangle. It does not go in recovery mode. I have to re flash the stock rom to save device.
Could it be you're flashing only a temporary recovery,without an included kernel?Just guessing you may well be.FYI S2 doesn't have a separated partition for recovery as some other phones has.
As you're currently using a stock rom,the easiest way IMO would be flashing Philz kernel first(from Original Android Development section).Then follow the instructions from the CM11 thread.
TheImpossibleEnemy said:
Could it be you're flashing only a temporary recovery,without an included kernel?Just guessing you may well be.FYI S2 doesn't have a separated partition for recovery as some other phones has.
As you're currently using a stock rom,the easiest way IMO would be flashing Philz kernel first(from Original Android Development section).Then follow the instructions from the CM11 thread.
Click to expand...
Click to collapse
It is possible but instructions on cynogenmod wiki page does not advise about a kernel. It gives a link to the recovery file and after recovery is flashed, I should be able to use volume up + home + power to access the recovery. Which I can't.
You just got given the best bit of advice anyone could give you, you have no clue whatsoever, and you're questioning said advice ?
Forget the CM Wiki. As you've just been told, any recovery flashed independently of the kernel on the I9100 will only persist until the next reboot. The easiest way to achieve what you're trying to achieve is to flash a custom kernel which will give you root+permanent CWM, and go from there.
You can either follow the advice you've been given & get this done the easy way, or you can continue to fumble around for days/weeks/months/whatever.
No skin off our noses either way *shrugs*
And no, I'm not going to apologise for being a bit 'rough' with you. People who come here with no idea, ask for help & either don't follow great advice they're given or argue the point about things they have no understanding of **** me to tears & get zero empathy.
So i got this phone yesterday, and i came from my old Galaxy S3. I am used to rooting and installing custom ROMs on that device and was wondering if there was anything I should be aware of with this phone. I do plan on rooting it in about 2 weeks depending on how I feel about touchwiz then, but for now i would like any information about possible brickings due to knox. thank you.
DO NOT USE Kingo root. - I wish I saw that earlier
I tried to use it. ended up failing. Then I followed qbking77s' instructions which also did not work out well for me. I bricked my note 3 and tripped knox on the first day I got the thing lol.
Thankfully I was able to find an odin-flashable to push over to my device and everything is ok. still gotta root the damn thing tho.
Number 1 Rule!!!/ General tips
1.) Heres the big thing about the note 3.
You cannot revert (odin flash) back to previous builds of the note 3, it will soft-brick (maybe even hard-brick) your phone.
Meaning if you are on NC5 its not a good idea to dowgrade back to NAB. This is a smaller jump but ive read of issues. Though NEVER try to odin from kit-kat to Mj4 jellybean. They have different incompatible bootloaders, and it will brick. So ya no downgrading.. Unless you really feel comfortable with "engineering boot loaders" But currently the newest build is "NC5"
2.) think the most convenient root method is to..
-put chainfire's UPDATE-SuperSU-v1.94.zip onto sd card
http://download.chainfire.eu/396/SuperSU
-odin twrp 2.7.01.tar, (found in original development) or link
http://teamw.in/project/twrp2/201
-immediately boot into twrp (Home+Power+Volume Up) and flash UPDATE-SuperSU-v1.94.zip
reboot
Now rooted with twrp recovery to flash new roms
3. Just another warning. Factory reseting with STOCK recovery for this device wipes internal sd card.
Edit/Add on: About knox: Dont worry too much about it. Once your rooted on stock rom, it will probably prompt to attempt to disable knox. just hit okay and thats probably the last you hear about knox. When you flash a new rom the rom devs have it disabled so it never prompts. But ya knox isnt really much of anything but a counter in download mode. Yes it cant be reset, but thats about the only thing that cant. You can still be fully unrooted, with official status. You probably wont have any problems with sprint. Theyd have to check download mode for the 0x1, and they would have to know what that means too lol. And you definitely wont have problems if you have sprint warranty.
Hope that helps good luck, I love this phone!
CollinsB said:
1.) Heres the big thing about the note 3.
You cannot revert (odin flash) back to previous builds of the note 3, it will soft-brick (maybe even hard-brick) your phone.
Meaning if you are on NC5 its not a good idea to dowgrade back to NAB. This is a smaller jump but ive read of issues. Though NEVER try to odin from kit-kat to Mj4 jellybean. They have different incompatible bootloaders, and it will brick. So ya no downgrading.. Unless you really feel comfortable with "engineering boot loaders" But currently the newest build is "NC5"
2.) think the most convenient root method is to..
-put chainfire's UPDATE-SuperSU-v1.94.zip onto sd card
http://download.chainfire.eu/396/SuperSU
-odin twrp 2.7.01.tar, (found in original development) or link
http://teamw.in/project/twrp2/201
-immediately boot into twrp (Home+Power+Volume Up) and flash UPDATE-SuperSU-v1.94.zip
reboot
Now rooted with twrp recovery to flash new roms
3. Just another warning. Factory reseting with STOCK recovery for this device wipes internal sd card.
Edit/Add on: About knox: Dont worry too much about it. Once your rooted on stock rom, it will probably prompt to attempt to disable knox. just hit okay and thats probably the last you hear about knox. When you flash a new rom the rom devs have it disabled so it never prompts. But ya knox isnt really much of anything but a counter in download mode. Yes it cant be reset, but thats about the only thing that cant. You can still be fully unrooted, with official status. You probably wont have any problems with sprint. Theyd have to check download mode for the 0x1, and they would have to know what that means too lol. And you definitely wont have problems if you have sprint warranty.
Hope that helps good luck, I love this phone!
Click to expand...
Click to collapse
I 2nd what CollinsB says, SuperSu v1.94 best way to go to root your note 3. You also might look into Philz CWM recovery. As for KNOX and your warranty don't worry sprint and Samsung have not turned down a warranty fix that I'm aware of. Besides, They have already figured out a way to reset KNOX on the Exynos processor its only a matter of time before they solve KNOX for the Qualcomm processor.
---------- Post added at 05:06 AM ---------- Previous post was at 05:02 AM ----------
One of the best things you can do, is disable touchwiz!!!!! Install the nova launcher, better, faster, and more features. Enough said!!!!
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
kmt5150 said:
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
Click to expand...
Click to collapse
In for at least $20.
Put me down for 2 bucks.
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Grarak said:
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
Well technically all bootloaders are locked (except for the few that aren't) but I take it AT&T is wanting/trying to join the band wagon with Verizon and locking the bootloaders indefinitely by encrypting them on all the devices they can now.
Sorry then, my method will not work straight forward. Good luck. :good:
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Believe me, we have tried it all. I have tried a process similar to this and when the phone got done with all the flashing and went to boot up, I got a prompt that said 'We have detected software not approved for use by AT&T. Please take your phone to an AT&T store for assistance.' It also says Secure Check Failed: Kernel. I had to send my phone to sammy to get it fixed since I tripped a few flags. Should be back by Friday the 10th.
Possible to use this method with 4.4 kernel from mega?
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Will definitely try this again when my phone gets here tomorrow and post updates...
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
kmt5150 said:
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
Click to expand...
Click to collapse
Have you tried towel root
http://towelroot.com/
BarakOsama said:
Have you tried towel root
http://towelroot.com/
Click to expand...
Click to collapse
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Can anyone send me boot.img of ATT KK rom?
captemo said:
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
My bad..
Alright.
To summarize for people who haven't paid attention. Phone was bricked in a last ditch effort to flash back to 4.3 because the 4.4 update made my phone run like s#it. I also have an S4 Active and the service sucks harder than it already did. The 4.4 update makes the S4 drop out constantly and the battery life blows. Samsung told me to run kies in download mode to get it back to 4.3 I did and BOOM, now phone is fu©k!ng bricked and they won't fix it, claiming it's 'rooted' because the kernel says it's version 3 when it's supposed to be at 4 for kitkat. Fu©k!ng duh, you jerks made me flash it back. I am personally never buying another samsung product again because their customer service was horsesh!t. I happen to have a sammy tv, blu ray, home theater and 2 of their former 'top end' phones, but now I'm ditching them. They can lick my scrotum for all I care anymore.
end rant, back to music.
SCH-R960
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
MeatHammer311 said:
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
Click to expand...
Click to collapse
Can you make a complete firmware dump and compile a .PIT file?
No root.
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
MeatHammer311 said:
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
Click to expand...
Click to collapse
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Grarak said:
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Click to expand...
Click to collapse
tell me how to get it any you will have it 1 before 5pm today est.
also here is the pit file you asked for. I used it to unbvrick my phone a few times with odin.
ita for the at&t version
This bump thing is confusing the hell out of me. Then again I haven't slept in 20hrs... regardless.
My phone is rooted and I installed TWRP from the TWRP app in the play store. Do I need Bump to install CM 12.0 or can I just flash CM 12.0 from TWRP? I've been googling for awhile and reading threads here on Bump but I have no clue what it is...
You must follow directions in THIS post. If your not comfortable using adb commands, you can flash the IMG file from that post using flashify from Google Play. Then flash THIS updated zip version of bumped TWRP in TWRP.
sent from my LG G3
drekalots said:
This bump thing is confusing the hell out of me. Then again I haven't slept in 20hrs... regardless.
My phone is rooted and I installed TWRP from the TWRP app in the play store. Do I need Bump to install CM 12.0 or can I just flash CM 12.0 from TWRP? I've been googling for awhile and reading threads here on Bump but I have no clue what it is...
Click to expand...
Click to collapse
I didn't use the twrp app to install twrp but looking through the app the LS990 is listed so I don't really know. The method I used is as follows and works without a hitch. If you are already rooted, grab flashify from the play store and flash the BUMPED LS990 Twrp from flashify. Make sure to flash it as a recovery image. If you try to put a recovery on there that hasn't been BUMPED yet you will probably end up in a bad situation. After you have the bumped recovery on your phone go-ahead and flash whatever rom you want. They will all be bumped before they are uploaded to a server.
Not to sound like an a$$ but you really should read the bump thread in the original development and followed that. That would have been the safest way of doing this. With these phones you really shouldn't deviate from the instructions that are posted.
http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_ls990-signed.img
whoppe862005 said:
I didn't use the twrp app to install twrp but looking through the app the LS990 is listed so I don't really know. The method I used is as follows and works without a hitch. If you are already rooted, grab flashify from the play store and flash the BUMPED LS990 Twrp from flashify. Make sure to flash it as a recovery image. If you try to put a recovery on there that hasn't been BUMPED yet you will probably end up in a bad situation. After you have the bumped recovery on your phone go-ahead and flash whatever rom you want. They will all be bumped before they are uploaded to a server.
Not to sound like an a$$ but you really should read the bump thread in the original development and followed that. That would have been the safest way of doing this. With these phones you really shouldn't deviate from the instructions that are posted.
http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_ls990-signed.img
Click to expand...
Click to collapse
I'd read that but not much was clicking last night.
I ended up following this http://www.droidviews.com/install-twrp-recovery-on-lg-g3-all-variants-using-bump/ to flash the bumped TWRP img. I still have no clue what the difference is though. lol. Right now I'm running CM12.0 and I'm not so much a fan of Lollipop. May need to find another ROM.
drekalots said:
I'd read that but not much was clicking last night.
I ended up following this http://www.droidviews.com/install-twrp-recovery-on-lg-g3-all-variants-using-bump/ to flash the bumped TWRP img. I still have no clue what the difference is though. lol. Right now I'm running CM12.0 and I'm not so much a fan of Lollipop. May need to find another ROM.
Click to expand...
Click to collapse
Essentially your recovery and boot.imgs need to be "bumped" which tricks the bootloader into thinking the file was signed by LG. Otherwise you get a secured boot error after flashing. If you are using a TWRP file or custom kernel from here in the threads, it's already been bumped(or definitely should be) so all you have to do is install it.
I know it may seem confusing because it is very different from other android models but really the devs are the ones that have to bump things, for the end user, there isn't really a difference.
whoppe862005 said:
I didn't use the twrp app to install twrp but looking through the app the LS990 is listed so I don't really know. The method I used is as follows and works without a hitch. If you are already rooted, grab flashify from the play store and flash the BUMPED LS990 Twrp from flashify. Make sure to flash it as a recovery image. If you try to put a recovery on there that hasn't been BUMPED yet you will probably end up in a bad situation. After you have the bumped recovery on your phone go-ahead and flash whatever rom you want. They will all be bumped before they are uploaded to a server.
Not to sound like an a$$ but you really should read the bump thread in the original development and followed that. That would have been the safest way of doing this. With these phones you really shouldn't deviate from the instructions that are posted.
http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_ls990-signed.img
Click to expand...
Click to collapse
HPTesla said:
Essentially your recovery and boot.imgs need to be "bumped" which tricks the bootloader into thinking the file was signed by LG. Otherwise you get a secured boot error after flashing. If you are using a TWRP file or custom kernel from here in the threads, it's already been bumped(or definitely should be) so all you have to do is install it.
I know it may seem confusing because it is very different from other android models but really the devs are the ones that have to bump things, for the end user, there isn't really a difference.
Click to expand...
Click to collapse
Ah. Got it. Thank you for clearing that up.
This is the Odin ROM for the PL1 update. Requires the the use of Odin, computer, and USB cable to use. This is the stock ROM pulled from Samsung Kies3. I've flashed it inside Odin, and it upgraded my device without wiping contents, but I cannot promise the same result for everyone.
To (re)root, follow this:
https://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382/page2
The file:
https://drive.google.com/file/d/0B2iEgzRTFjrQdlhNSlg5bkE4WVE/view?usp=drivesdk
So what does the PL1 update get you? Does it improve the radio modem operations? Is it just so it will work with Nougat?
It's a security update, that's all. Note 3 is done with OS upgrades. 5.0 will be the last official
Sent from my SAMSUNG-SM-G935A using Tapatalk
Hya there..
I have been following all your posts about flashing the PL1 update through either Odin or TWRP. I am familiar with both, but wanted to ask for insight on my particular setup.
Model SM 900P (Sprint)
Im still on 4.4.2 Kitkat Killer and has been doing well but looking to upgrade if I can find a good ROM.
I am still on baseband version NC5
Kernel 3.4.0 BeastMode
I figure I would be smart to flash the Baseband and Modem to the PL1 but would of course like to keep root and keep my TWRP recovery.
Ultimately I would like to flash the DarkLord ROM or even Resurrection Remix ROM for the Note 3 on CDMA (Sprint)
This is my daily driver, and cannot afford to frag my phone so I want to be sure I make the best choices.
If I follow your posts I would do best to downlowad your TWRP Stock Pre Root zip file, and simply "recover' the file as if I was doing any normal TWRP recovery. This would then put me back to Stock Lollipop and upgrade my Modem and Baseband and get me the latest security updates (well fairly recent anyways).
In lieu of that, I can ODIN the PL1 file offered by you and this would in effect 'factory reset' my phone as if I just bought it from Sprint (well you know what I mean) and would re install all my apps etc (through Titanium Backup etc).
From there I can try Resurrection or DarkLord Mod's and load them like any ROM install?
Thanks for double checking my train of thought...
Dave
Thanks! This helped me out.
@Unidave199 -
Use ODIN to push Greaper88's PL1 file to your phone. (now you are updated.) (I just used it, it works.)
Use ODIN to push a recovery to your phone like TWRP
Find yourself a ROM you like (Darklord's is good.)
Flash ROM via TWRP (Read the ROM's OP's entire instructions for flashing.)
Final step....Enjoy!
2manyhobbies said:
Thanks! This helped me out.
@Unidave199 -
Use ODIN to push Greaper88's PL1 file to your phone. (now you are updated.) (I just used it, it works.)
Use ODIN to push a recovery to your phone like TWRP
Find yourself a ROM you like (Darklord's is good.)
Flash ROM via TWRP (Read the ROM's OP's entire instructions for flashing.)
Final step....Enjoy!
Click to expand...
Click to collapse
I hope this is the right thread for this...
Pardon my ignorance here, it's been a few years since I frequented this forum, or even XDA...
Is this what I want to use to get back to total stock, unrooted for resale?
(I've been rocking the Note 3 since it came out, FINALLY upgraded to something newer, and want to sell this to a sprint user.)
Yes it is
Just use the "CSC" file and not the "HOME_CSC." This should completely reset the device and clear user data.