I have been reading these two threads closely:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
But one thing I am yet to understand, is how do you go about flashing a baseband? What I've learned so far, is not to rely on toolkits. I will follow the directions from the first link, which seem pretty straightforward.
I downloaded the factory image "KOT49H" which corresponds with the baseband I want to flash, that being from 4.4.2. If I want to flash the baseband only, would the command be something like this?
fastboot flash radio radio-hammerheadx.x.x.x.x.x.x..img
Click to expand...
Click to collapse
darksome123 said:
I have been reading these two threads closely:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
But one thing I am yet to understand, is how do you go about flashing a baseband? What I've learned so far, is not to rely on toolkits. I will follow the directions from the first link, which seem pretty straightforward.
I downloaded the factory image "KOT49H" which corresponds with the baseband I want to flash, that being from 4.4.2. If I want to flash the baseband only, would the command be something like this?
Click to expand...
Click to collapse
almost all the radios are available in zip format(check the xda thread for the zips. all you do is download one, then go into your custom recovery and flash it there. it takes seconds, then boot up after that. btw, radio and baseband is the same thing in this conversation.
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
darksome123 said:
I have been reading these two threads closely:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
But one thing I am yet to understand, is how do you go about flashing a baseband? What I've learned so far, is not to rely on toolkits. I will follow the directions from the first link, which seem pretty straightforward.
I downloaded the factory image "KOT49H" which corresponds with the baseband I want to flash, that being from 4.4.2. If I want to flash the baseband only, would the command be something like this?
Click to expand...
Click to collapse
if you are using fastboot to flash a radio then that is the correct command. but, as i said, its much easier to download a zipped up version and flash in recovery.
darksome123 said:
I have been reading these two threads closely:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
But one thing I am yet to understand, is how do you go about flashing a baseband? What I've learned so far, is not to rely on toolkits. I will follow the directions from the first link, which seem pretty straightforward.
I downloaded the factory image "KOT49H" which corresponds with the baseband I want to flash, that being from 4.4.2. If I want to flash the baseband only, would the command be something like this?
Click to expand...
Click to collapse
yes that's how it would look like if you want to flash a .img radio file via fastboot
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095
or just download the radio zip you want and flash in recovery,
simms22 said:
almost all the radios are available in zip format(check the xda thread for the zips. all you do is download one, then go into your custom recovery and flash it there. it takes seconds, then boot up after that. btw, radio and baseband is the same thing in this conversation.
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
if you are using fastboot to flash a radio then that is the correct command. but, as i said, its much easier to download a zipped up version and flash in recovery.
Click to expand...
Click to collapse
That was the other question I had. So simply download the zipped file to my phone and flash it in recovery mode, right?
darksome123 said:
That was the other question I had. So simply download the zipped file to my phone and flash it in recovery mode, right?
Click to expand...
Click to collapse
right, that easy. if you want to be safe, make a backup in recovery before flashing. that way if the new radio gives you issues, all you have to do is restore the backup.
I've never flashed anything, but have been doing my research for the last few months. Everything seems pretty easy to follow. I guess the coward in me never really gave it a chance. I'll give it a go and do a follow up on the results.
Thank you so much for the help.
darksome123 said:
I've never flashed anything, but have been doing my research for the last few months. Everything seems pretty easy to follow. I guess the coward in me never really gave it a chance. I'll give it a go and do a follow up on the results.
Thank you so much for the help.
Click to expand...
Click to collapse
are you not happy with your current radio? i do it occasionally, to check if another radio is better. if so, ill keep it, if not, ill flash to the previous radio i had. but anything you flash, if you make a backup in recovery first, itll save what you had before flashing, rom as well. when i first rooted ages ago(g1), it also took me month of reading before doing anything. but once familiar with it, it doesnt take any thought anymore, and ive been helping others with it here on xda since.
After the update from 4.4.2 to 4.2.3 and then to 4.4.4...reception kept getting worse. And then there was the battery issue, I used to be able to keep a charge for over 24 hours...now it doesn't last more than 5 hours. Some individuals from another forum have attributed it to the baseband. Several of them went back to the 4.4.2 version and say the battery issue is gone. I've tried everything and this seems like the last resort.
darksome123 said:
After the update from 4.4.2 to 4.2.3 and then to 4.4.4...reception kept getting worse. And then there was the battery issue, I used to be able to keep a charge for over 24 hours...now it doesn't last more than 5 hours. Some individuals from another forum have attributed it to the baseband. Several of them went back to the 4.4.2 version and say the battery issue is gone. I've tried everything and this seems like the last resort.
Click to expand...
Click to collapse
the radio that came with L gave me issues, the radio before that worked fine, so i went back to that. it would all depend on your location, in how well they work for you.
OK so on an unrelated note, now that I'm unlocked what does this mean now that Android Lollipop is about to be released? How will an OTA update affect my phone? The modifications I've made so far is installed CWM recovery and SuperSU, reverted baseband to previous 4.4.2 version, and changed the kernel to Franco Kernel. All other system apps are intact.
Sent from my Nexus 5 using XDA Free mobile app
darksome123 said:
OK so on an unrelated note, now that I'm unlocked what does this mean now that Android Lollipop is about to be released? How will an OTA update affect my phone? The modifications I've made so far is installed CWM recovery and SuperSU, reverted baseband to previous 4.4.2 version, and changed the kernel to Franco Kernel. All other system apps are intact.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You won't get OTA because you're too modified. But now you're rooted, you owe it to yourself to learn how to manage your modified phone. OTA is the worst way to update in your situation.
Learn about flashing ROMs. All info and guides are in my signature
darksome123 said:
OK so on an unrelated note, now that I'm unlocked what does this mean now that Android Lollipop is about to be released? How will an OTA update affect my phone? The modifications I've made so far is installed CWM recovery and SuperSU, reverted baseband to previous 4.4.2 version, and changed the kernel to Franco Kernel. All other system apps are intact.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
you cant get a flashable ota. you might get an ota, but it wont flash. only the original rom with all of its files intact can receive and apply an ota. a day or two after source is released, youll be able to flash a rooted version. or you can flash the factory img and reroot.
I think I may write a thread about this.
So it sounds like a rooted version would be the easiest thing for me then. Now, it won't delete all my data will it? As in a typical OTA update all the data remains intact. Any suggestions as to where I should be looking for a rooted versiob when it is released?
darksome123 said:
So it sounds like a rooted version would be the easiest thing for me then. Now, it won't delete all my data will it? As in a typical OTA update all the data remains intact. Any suggestions as to where I should be looking for a rooted versiob when it is released?
Click to expand...
Click to collapse
I'm positive you'll have to do a full wipe to flash the 5.0 rom. So, yes you'll lose your data. You could try just flashing the system.img and boot.img from 4.4.4 then taking the ota. But back up everything off your device. 5.0 is a different animal and most likely will require a full wipe before working correctly.
Sent from my Nexus 5 using XDA Free mobile app
Say I were to reinstall the previous baseband along with the stock kernel, I still have stock android running, couldn't I just flash the ROM through fastboot or through CWM?
Sent from my Nexus 5 using XDA Free mobile app
darksome123 said:
Say I were to reinstall the previous baseband along with the stock kernel, I still have stock android running, couldn't I just flash the ROM through fastboot or through CWM?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Could you expand on your question please?
rootSU said:
Could you expand on your question please?
Click to expand...
Click to collapse
I have stock Android 4.4.4, but the baseband from 4.4.2 along with Franco Kernel. If I were to revert these to the originals found in 4.4.4, would it be enough to fastboot a rooted version of Lollipop, without running into trouble? As I understand it, even if I were to revert these I still wouldn't be able to get OTA because of CWM recovery. Am I correct?
Sent from my Nexus 5 using XDA Free mobile app
darksome123 said:
I have stock Android 4.4.4, but the baseband from 4.4.2 along with Franco Kernel. If I were to revert these to the originals found in 4.4.4, would it be enough to fastboot a rooted version of Lollipop, without running into trouble? As I understand it, even if I were to revert these I still wouldn't be able to get OTA because of CWM recovery. Am I correct?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You wouldn't need to revert to fastboot. Fastboot will replace these so it doesn't care what's there now.
Have a read of the thread in my signature about rooted users updating.
Related
Before I get flamed, let me say that I have done ALOT of research on the questions I am about to ask, and the fact of the matter that there is a lot of conflicting information out there. So please bear with me.
I am on a rooted phone, Android 4.1.1, Sense 4+, 3.18.502.6 radio, kernal version 3.4.10
Rooted with S-on
So here's my questions:
1. Can I install a custom rom with S-on?
2. If the answer is yes, can someone give me the quick run-down, or at the very least point me in the direction of another thread that I can refer to?
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Some of these threads are 30+ pages long and go back to 2012. If you miss one post in the thread then you're screwed. Any help is appreciated. For the record these forums have been extremely helpful. Successfully rooted two phones in the past year. I understand the rooting very, flashing custom roms gives me the willies.
First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4
RollTribe said:
First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions
Fivetenfrank said:
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions
Click to expand...
Click to collapse
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4
RollTribe said:
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks. One last question. Ok maybe not the last one but one more question regardless.
With custom roms, does the rom need to be based on the same firmware that's on my stock phone? I other words, right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?
Fivetenfrank said:
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Click to expand...
Click to collapse
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Fivetenfrank said:
With custom roms, does the rom need to be based on the same firmware that's on my stock phone?
Click to expand...
Click to collapse
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Fivetenfrank said:
right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?
Click to expand...
Click to collapse
Link the ROM, and I can probably answer that for you pretty easily.
Notills his
redpoint73 said:
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Link the ROM, and I can probably answer that for you pretty easily.
Click to expand...
Click to collapse
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
And I'm not going to mess with S-off. Ill stick with S-on for now.
You should be fine to flash it. Like redpoint said, you may have to flash the boot.img. I can't remember whether CR6.5 flashes the boot.img for you or not. To be on the safe side, go ahead and flash it.
Fivetenfrank said:
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
Click to expand...
Click to collapse
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
Fivetenfrank said:
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
.
Click to expand...
Click to collapse
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!
redpoint73 said:
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!
Click to expand...
Click to collapse
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side. Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Once this is all done ill post and let everyone know how I made out. Going back now and "thanking" all who have replied
Fivetenfrank said:
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side.
Click to expand...
Click to collapse
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Fivetenfrank said:
Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Click to expand...
Click to collapse
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909
redpoint73 said:
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909
Click to expand...
Click to collapse
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
You don't have to remove TWRP. Just flash over the top of it with CWM.
Egrier said:
You don't have to remove TWRP. Just flash over the top of it with CWM.
Click to expand...
Click to collapse
Got it. Wish me me luck fellas. I am going to give this a whirl tonight
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!
Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Fivetenfrank said:
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!
Click to expand...
Click to collapse
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).
redpoint73 said:
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).
Click to expand...
Click to collapse
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow
Fivetenfrank said:
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow
Click to expand...
Click to collapse
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium
also inpensi
31ken31 said:
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the heads up. I am good on the instructions. I have found a multitude of posts outlining the steps. My biggest fear is/was the compatibility issue - flashing a rom that's not compatible with my phone. I tried flashing a Rom a couple of months ago on an HTC One X on 2.20, and I bricked it. I flashed the wrong Rom. Luckily AT&T didnt catch it and they gave me a new phone. I had to get another new phone this week past because my old HTC One X died for some unknown reason. AT&T gave me another one on warranty. This new one has the 3.18
Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
If my memory serves me correctly, that's exactly what I did.
So ill try to make this short and sweet but i need help. since 4.4.4 i really noticed bad signal issues and with a speed test my ping is 160 making online gaming really bad. ( its the only connection i have where i live to play online before 4.4.4 it was fine ping was like 70ms)
So i figured out the to get the radios say from 4.4.2 i would download the rom from https://developers.google.com/androi...s/images?hl=de
extract the file and the radio file is inside right. now how do i flash it. using Android SDK is there a tutorial or video somewhere. And can i use the roms from that site on a canadian nexus 5 my 4.4.4 build number matches the one on the site so im guessing yes.
android.4.0 said:
So ill try to make this short and sweet but i need help. since 4.4.4 i really noticed bad signal issues and with a speed test my ping is 160 making online gaming really bad. ( its the only connection i have where i live to play online before 4.4.4 it was fine ping was like 70ms)
So i figured out the to get the radios say from 4.4.2 i would download the rom from https://developers.google.com/androi...s/images?hl=de
extract the file and the radio file is inside right. now how do i flash it. using Android SDK is there a tutorial or video somewhere. And can i use the roms from that site on a canadian nexus 5 my 4.4.4 build number matches the one on the site so im guessing yes.
Click to expand...
Click to collapse
From start to finish, skip over what you've already done.
1. Unlock your bootloader.
2. Root.
3. Install custom recovery using fastboot,
Google TWRP Hammerhead and the site for the recovery image and instructions will show up.
4. Have the modems downloaded, search for the thread here in Nexus 5 forum.
5. Go to Install .zip in TWRP recovery and flash the respective modems.
Protip : look up how to make an EFS backup just in case you somehow manage to corrupt your IMEI.
TheLastSidekick said:
From start to finish, skip over what you've already done.
1. Unlock your bootloader.
2. Root.
3. Install custom recovery using fastboot,
Google TWRP Hammerhead and the site for the recovery image and instructions will show up.
4. Have the modems downloaded, search for the thread here in Nexus 5 forum.
5. Go to Install .zip in TWRP recovery and flash the respective modems.
Protip : look up how to make an EFS backup just in case you somehow manage to corrupt your IMEI.
Click to expand...
Click to collapse
I dont really wanna root just flash back to 4.4.2 radios so i can get better service.
android.4.0 said:
I dont really wanna root just flash back to 4.4.2 radios so i can get better service.
Click to expand...
Click to collapse
Check APNs if that doesn't work then
Return to factory default.
Not much else you can do without root.
TheLastSidekick said:
Check APNs if that doesn't work then
Return to factory default.
Not much else you can do without root.
Click to expand...
Click to collapse
Theres nothing wrong with the APN i hear lots of people have issues and sadly only a few countrys got 4.4.4r2 to fix radio issues
android.4.0 said:
Theres nothing wrong with the APN i hear lots of people have issues and sadly only a few countrys got 4.4.4r2 to fix radio issues
Click to expand...
Click to collapse
Which without root is impossible unless the OTA comes through and its dependant on the country you're in. You could flash the 4.4.4r2 stock image using fastboot.
TheLastSidekick said:
Which without root is impossible unless the OTA comes through and its dependant on the country you're in. You could flash the 4.4.4r2 stock image using fastboot.
Click to expand...
Click to collapse
Im going to unlock my bootloader and flash radios from 4.4.2 to my phone thats running 4.4.4 cause the radios on 4.4.4 are garbage. i dont think i need to be rooted to flash radios or a rom
android.4.0 said:
Im going to unlock my bootloader and flash radios from 4.4.2 to my phone thats running 4.4.4 cause the radios on 4.4.4 are garbage. i dont think i need to be rooted to flash radios or a rom
Click to expand...
Click to collapse
You don't need to be rooted persay to flash a modem, just a custom recovery. It just makes things easier. If you're going to unlock for sure, rooting makes things easier even though you don't REQUIRE it.
Best of luck and let us know how it all goes.
Why not extract the radio from the Android image and flash it via fastboot? That doesn't require root, only the phone to be unlocked.
Sent from my Nexus 5 using Tapatalk
TheLastSidekick said:
You don't need to be rooted persay to flash a modem, just a custom recovery. It just makes things easier. If you're going to unlock for sure, rooting makes things easier even though you don't REQUIRE it.
Best of luck and let us know how it all goes.
Click to expand...
Click to collapse
You don't need a custom recovery to flash a radio
Lethargy said:
You don't need a custom recovery to flash a radio
Click to expand...
Click to collapse
That is news to me. Haha, how would one go about doing this? I only knew about flashing a stock image that comes with the radio, and the radio zips in recovery...or did I miss something can you extract the radio from the factory image and flash it alone?
TheLastSidekick said:
That is news to me. Haha, how would one go about doing this? I only knew about flashing a stock image that comes with the radio, and the radio zips in recovery...or did I miss something can you extract the radio from the factory image and flash it alone?
Click to expand...
Click to collapse
Extract it and fastboot flash radio radio.img? Lol
Lethargy said:
Extract it and fastboot flash radio radio.img? Lol
Click to expand...
Click to collapse
Gotta be a man and admit I wasn't aware of the radio parameter. I learned something lol, thanks.
TheLastSidekick said:
Gotta be a man and admit I wasn't aware of the radio parameter. I learned something lol, thanks.
Click to expand...
Click to collapse
See first link of my signature and read threads before posting
Jk :angel: Learn something new everyday, huh? Lol
We have answered all your questions here http://forum.xda-developers.com/showthread.php?t=2839307.
Why open the same thread again?
Tapatalk Team SlimRoms
Tylog said:
We have answered all your questions here http://forum.xda-developers.com/showthread.php?t=2839307.
Why open the same thread again?
Tapatalk Team SlimRoms
Click to expand...
Click to collapse
OP decided to create more (mostly useless) threads in one day than I ever have on my account lol..
Hi everyone, I have a big problem. Recently I got the phone and decided to root it. I used this guide: http://forum.xda-developers.com/showthread.php?t=2788632
I successfully rooted 4.4.2. using TWRP method, no problem but I when I decide it to update to OTA XNPH30O - 4.4.4. after clicking install, it sends me back to TWRP recovery page and I never able to install the update. What I did next was probably what got me in this situation. I went to recovery page, I did both format data and advance wipe but turns out it didn't clean everything on the SD DIR. So now when I restart the system, it just hangs on the OPO page.
Please how do I restore to the original factory ROM so I can re-root it again. Currently I have only access to fastboot and TWRP recovery page. I'm very noob at this and the last thing I want is to messed up the bootloader so I need someone to guide me through it step by step.
Thank You
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
timmaaa said:
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
The OTA updates are bugged.
You might want to consider using a custom ROM.
Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
Like I said just go to my index thread, there are full versions of every release of CM11S in the Stock Images thread. Just flash whichever version you wavy to be on.
Transmitted via Bacon
EddyOS said:
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Click to expand...
Click to collapse
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Gamm86 said:
The OTA updates are bugged.
You might want to consider using a custom ROM.
Click to expand...
Click to collapse
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Majestic_12 said:
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Click to expand...
Click to collapse
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed.zip (taken from the images thread)
Thank you all for helping me with this, I know all this noob asking is lame but I need to ask in order for me to learn.
EddyOS said:
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
link (taken from the images thread)
Click to expand...
Click to collapse
I did just that using fastboot, I flashed ROM XNPH33R which is supposedly 4.4.4 and I again rooted it afterward with TWRP/SuperSU method. But now I think I need to go through a checklist on why my battery still isn't doing good as many would say. I wouldn't consider it draining but it does go down quite fast when I put it to use. Evening idling for 8 hours the phone still drains about 20% when I woke up.
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
I did just that on using the XNPH33R fastboot img but now that I think about it, should I use the zip method instead but that's putting the files onto DIR and flash it from TWRP right?
EddyOS said:
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Click to expand...
Click to collapse
Well I did all that, now I'm on 33R and is rooted, is there anything I can do to help improve the battery life? I';m still experiencing a drain.
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Majestic_12 said:
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Click to expand...
Click to collapse
Getting rid of bloat isn't really going to increase the duration of your battery. Finding which apps are driving your battery the most or causing wakelocks and then dealing with them by using something like Greenify will have a positive effect though.
Transmitted via Bacon
nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
I am unlocked and rooted but the download from verizon automatically started. It did nothing after it was done downloading. I dont know what to expect of this?? I am on viper rom 2.5.
Here's the link folks
https://www.androidfilehost.com/?fid=95747613655049317
Only for stock recovery and untouched system users
dottat said:
Here's the link folks
https://www.androidfilehost.com/?fid=95747613655049317
Only for stock recovery and untouched system users
Click to expand...
Click to collapse
Hey dottat what is the correct directory that the file gets saved to on the phone?
lucky_strike33 said:
I am unlocked and rooted but the download from verizon automatically started. It did nothing after it was done downloading. I dont know what to expect of this?? I am on viper rom 2.5.
Click to expand...
Click to collapse
Won't flash if you have custom recovery or modified system.
krazie1 said:
Hey dottat what is the correct directory that the file gets saved to on the phone?
Click to expand...
Click to collapse
/cache/fumo
dottat said:
Won't flash if you have custom recovery or modified system.
Click to expand...
Click to collapse
Thank you!
Sent from my HTC6525LVW using XDA Premium HD app
Is there a full change log somewhere?
all good here, just reflashed @dottats RUU and updated the organic way. SOFF is good, it even says official in the software status in HBOOT
hboot- 3.19.0.0000
radio- 1.09.20.0926
dsp - v46.2.2-00564-m8974_F0.0811
os- 3.28.605.4
dottat said:
nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
Click to expand...
Click to collapse
Ready for that RUU.... It saved me 1,000 million times...
JB_Da_Greatest said:
Ready for that RUU.... It saved me 1,000 million times...
Click to expand...
Click to collapse
You can just use the 4.4.3 ruu and do the OTA, then your firmware is done all in 1 shot
can someone upload a 4.4.4 system dump? or point me to one if someone has already? thanks!
I have looked around and found all kinds of different answers so can someone here help me out a bit?
I got the phone when it first came out, have S-OFF, root, TWRP custom recovery but have version 4.4.2 still installed with everything being left pretty much stock. I would prefer to keep things pretty much stock so what would I need to do to update to 4.4.4? Do I need to get 4.4.3 first? Do I need to flash stock recovery first before doing anything? Anything with firmware or radios?
Resputan said:
I have looked around and found all kinds of different answers so can someone here help me out a bit?
I got the phone when it first came out, have S-OFF, root, TWRP custom recovery but have version 4.4.2 still installed with everything being left pretty much stock. I would prefer to keep things pretty much stock so what would I need to do to update to 4.4.4? Do I need to get 4.4.3 first? Do I need to flash stock recovery first before doing anything? Anything with firmware or radios?
Click to expand...
Click to collapse
well, this is my idea for you
1. Flash the stock 4.4.2 recovery over the TWRP, then just do the OTA's
aer0zer0 said:
well, this is my idea for you
1. Flash the stock 4.4.2 recovery over the TWRP, then just do the OTA's
Click to expand...
Click to collapse
Reasonable enough, sorry if this is another dumb question but I havent been paying much attention to these boards since I rooted, I see that recent phones require Sunshine to root, is that because of the firewater method being patched via a software update (4.4.3?) or some other manufacturer change that I shouldnt be concerned with if the old root method already works for me?
aer0zer0 said:
You can just use the 4.4.3 ruu and do the OTA, then your firmware is done all in 1 shot
Click to expand...
Click to collapse
I already updated... I was just saying for safe keeping just in case I get in some unforseen trouble.
Go here http://forum.xda-developers.com/showthread.php?t=2723159 and just flash the 4.4.3 with not boot img. YOu dont need to flash the recovery to accept ota's. YOu can just flash this and you will get the updated radios and h boot.http://forum.xda-developers.com/showthread.php?t=2723159
Downloaded OTA and updated, they added file manager and flashlight back ~!
JB_Da_Greatest said:
I already updated... I was just saying for safe keeping just in case I get in some unforseen trouble.
Click to expand...
Click to collapse
yup, its saved a billion times too
---------- Post added at 02:17 PM ---------- Previous post was at 02:16 PM ----------
lchupacabras said:
Downloaded OTA and updated, they added file manager and flashlight back ~!
Click to expand...
Click to collapse
i know, right that was such an awesome surprise
---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------
Resputan said:
Reasonable enough, sorry if this is another dumb question but I havent been paying much attention to these boards since I rooted, I see that recent phones require Sunshine to root, is that because of the firewater method being patched via a software update (4.4.3?) or some other manufacturer change that I shouldnt be concerned with if the old root method already works for me?
Click to expand...
Click to collapse
nope, if your already SOFF, you will stay SOFF. might break your root, but all you need to do is reinstall supersu when you put twrp back on
dottat said:
nice time for androidfilehost to be unreachable... i did post the firmware up. RUU and OTApkg.zip are ready for upload.
FYI guys/gals.. there's a new hboot on this one too.
Edit..uploading now
Click to expand...
Click to collapse
Hi dootat, Hope you remember me. You help me restore my mobile Via team viewer. Thanks for the RUU i am trying to flash but nothing going. Copy zip to SD card rename to 0p6bimg.zip and hit Hboot. i can see it installing and then ask for reboot but when check in mobile still 4.4.3. Any help?
thanks
Best regards
I'm trying to get my phone ready to install this rom ( http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423 ) and my current specs are: Model: SM-G920V, Android Version: 5.0.2. Baseband: OC3, Kernel version: 3.10.61, Build: OC3, Hardware: MDF v2.0 R2, VPN 1.4 R4.
This is a virgin untouched phone from the day S6 released. I wanted to make sure I do this right as I remember messing up my S5 upgrading the build to something nobody could root and you couldn't go back to the old version. I'd like to not repeat that with this phone
Also is it possible to get the newest MM beta perhaps? Like with this rom ( http://forum.xda-developers.com/showpost.php?p=65588463&postcount=9473 )
Thanks.
After 30+ views and 0 replies I decided to try for myself. I found pingpongroot and did that. Rooted successfully. Then I downloaded twrp manager and tried to install the newest of that. It says it installed successfully and asked me to reboot. I rebooted and now I'm stuck at a bright blue start up failed screen.
Any idea how to fix this?
I was typing up something as you posted that lol. Oh well.
You were on a winner with ping pong (root without voiding warranty), but you've blown that now by flashing twrp.
Best bet now would be to flash latest 5.1.1 stock ROM via odin, then install arter97s modded version of twrp 3.0.0-0 (V13) and SuperSU 2.68 to get you up to date and wait for marshmallow.
Or just flash the older twrp 2.8.something as is now to hopefully just get you up and running again.
Latest official twrp is pretty much broken currently.
Edit: scratch that, arters mod won't work on your phone. Just find an older 2.8 version of twrp for your phone and try that.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
I was typing up something as you posted that lol. Oh well.
You were on a winner with ping pong (root without voiding warranty), but you've blown that now by flashing twrp.
Best bet now would be to flash latest 5.1.1 stock ROM via odin, then install arter97s modded version of twrp 3.0.0-0 (V13) to get you up to date and wait for marshmallow.
Or just flash the older twrp 2.8.something as is now to hopefully just get you up and running again.
Latest official twrp is pretty much broken currently.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
How should I go about flashing twrp 2.8? I can use volume down + home + power to get to the downloading screen... Is there an odin way to install 2.8?
ElementalWindX said:
How should I go about flashing twrp 2.8? I can use volume down + home + power to get to the downloading screen... Is there an odin way to install 2.8?
Click to expand...
Click to collapse
Yeah odin is the usual way of installing it. Find the .tar or .tar.md5 and flash that via odin.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Yeah odin is the usual way of installing it. Find the .tar or .tar.md5 and flash that via odin.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
What would be wrong with using 3.0.1 or 3.0? They are only working with MarshMellow at the moment?
Ahhh. Just read up. Your bootloader is locked. No custom recoveries will work.
You should of just stopped at ping pong. It was your only way of getting root. (Which was what I was originally going to suggest lol)
This thread may be of some help recovering.
http://forum.xda-developers.com/verizon-galaxy-s6/help/samsung-s6-sm-g920v-bricked-t3129928
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Ahhh. Just read up. Your bootloader is locked. No custom recoveries will work.
You should of just stopped at ping pong. It was your only way of getting root. (Which was what I was originally going to suggest lol)
This thread may be of some help recovering.
http://forum.xda-developers.com/verizon-galaxy-s6/help/samsung-s6-sm-g920v-bricked-t3129928
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Sorry for sounding so newb but I rooted the phone so doesn't that mean it's unlocked? I read that thread and I'm downloading those 2 zip files to attempt to use odin to flash one of them. Unfortunately the mirror is so 1980s slow it will take 6 hours to download each file.
Ping pong used a completely different exploit to get root. Now you need a custom recovery or kernel to get root, both of which you can't do with a locked bootloader.
What did you flash originally? Hopefully you can just flash stock recovery back and stay on 5.0.2 to keep root.
If you are forced to update you may never get root again unless a new exploit is found.
Sorry, I haven't had much to do with a locked bootloader so can't be a great help. Do plenty of reading while whatever you are downloading is going and hope you can find a way to stay on 5.0.2
Sent from my SM-G920I using Tapatalk
---------- Post added at 06:06 AM ---------- Previous post was at 05:52 AM ----------
Try this link. It is the same firmware you are on currently and I seem to be maxing out my connection downloading it.
http://stockfirmware.androidrootz.com/download-all_vzw_g920vvru1aoc3_g920vvzw1aoc3_cl4318389_qb4424773_rev02_user_low_ship-zip/
Flash that via odin and if it works, You should be able to run ping pong again and keep root at least.
self_slaughter said:
Ping pong used a completely different exploit to get root. Now you need a custom recovery or kernel to get root, both of which you can't do with a locked bootloader.
What did you flash originally? Hopefully you can just flash stock recovery back and stay on 5.0.2 to keep root.
If you are forced to update you may never get root again unless a new exploit is found.
Sorry, I haven't had much to do with a locked bootloader so can't be a great help. Do plenty of reading while whatever you are downloading is going and hope you can find a way to stay on 5.0.2
Sent from my SM-G920I using Tapatalk
---------- Post added at 06:06 AM ---------- Previous post was at 05:52 AM ----------
Try this link. It is the same firmware you are on currently and I seem to be maxing out my connection downloading it.
http://stockfirmware.androidrootz.com/download-all_vzw_g920vvru1aoc3_g920vvzw1aoc3_cl4318389_qb4424773_rev02_user_low_ship-zip/
Flash that via odin and if it works, You should be able to run ping pong again and keep root at least.
Click to expand...
Click to collapse
Thanks I got that file and did successfully flash it with odin and did re-root with pingpong. How do I get my phone to the next step to get a rom loaded? I tried using twrp manager to load 2.8.7.2 and that just gave me the same result of the same blue screen. I'm reflashing back to the original rom right now sigh.
Ahh good times, that worked out well then. No custom recovery will work on your phone unless they find a way to unlock the bootloader. As for roms, check the Verizon s6 section. There was some there although most are probably abandoned by now since not many people would still have 5.0.2. Can't really help you on that front.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Ahh good times, that worked out well then. No custom recovery will work on your phone unless they find a way to unlock the bootloader. As for roms, check the Verizon s6 section. There was some there although most are probably abandoned by now since not many people would still have 5.0.2. Can't really help you on that front.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
So what version allows an unlocked boot loader and whats the best way to upgrade to that? The person whose rom I quoted in post #1 says they recommend using twrp.
ElementalWindX said:
So what version allows an unlocked boot loader and whats the best way to upgrade to that? The person whose rom I quoted in post #1 says they recommend using twrp.
Click to expand...
Click to collapse
It's your specific phone that is locked. (SM-G920V). Big difference to 920F or 920I etc...
Not much you can do about it unfortunately. Lucky you even got root.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
It's your specific phone that is locked. (SM-G920V). Big difference to 920F or 920I etc...
Not much you can do about it unfortunately. Lucky you even got root.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
wtf? So Verizon phones sold in America are screwed out of the ability to do roms? Thats a first for me. This sucks.