Subject pretty much says it all..
The Verizon Note2 and the USCC Note2 are almost the same animal. What would I need to modify in order to be able to install a ROM for the i605 on a R950? So far I have not been able to find anyone building lollipop roms for that phone, which leaves it even more the poor cousin of the N7100 Note2 device than the i605 is. They don't even have a separate group for it here. Where's the love??? Where can I go other than the TeamUSCC site for help with this device?
For the most part I'm happy with the device, and I'd really like to hold out until somebody comes out with a daylight readable screen, before I switch to a different device.
On another note. What's this about locked bootloaders? I'm assuming that given my luck I have one. Does that mean that I am locked into waiting until/if support is forthcoming from USCC?
My Phone information:
Model: SCH-R950
Android Version: 4.4.2
Baseband version: R950VXUCNE2
Kernel Version: 3.0.31-1526780 [email protected] #1 05/08/2014
Build Number: KOT49H.R950VXUCNE2
SE For Android Status: Enforcing
Hardware Version: R950.06
Related
Greetings! I've recently acquired an unwanted Motrola Atrix 4G and I'm wanting to upgrade it to the latest version of Android. Here's the tricky part - it's a Canadian (BELL) phone with an inactive SIM, and I'm not too sure what has actually been installed on it.
As far as I can tell, the previous user has 'Greyblurred' the device (See Here: http://forum.xda-developers.com/showthread.php?t=1070076) and flashed it with the custom SBF linked in the thread.
How would I go about updating the phone to Gingerbread? Is an OTA update possible without bricking it?
I should mention that this is my first smart phone, though I quite familiar with the terminology and it's applications. Just a nudge in the right direction would be fantastic.
Here's the system information, if it's of any help:
Code:
System Version: Version 4.2.1.1.MB860.Retail - Blurred
Model Number: MB860
Android Version: 2.2.2
Baseband Version: N_01.92.00R
Motorola Webtop Version: OSHWT_U1_6.54.0
Kernel Version: 2.6.32.9
[email protected] #1
SMP PREEMPT Thu Apr 28 22:58:25 CST 2011
Build Number: OLYEM_U4_2.1.1 - GreyBlurred
Thank you kindly in advance - any help is appreciated!
So it's been almost a year and I figured I'd give this a bump rather than create a new thread. Does anyone have even a whiff of a suggestion? Thank you kindly, in advance.
Okay, I must say I'm quite surprised. Even after almost a year you still haven't been able to research this on your own?
This forum is crammed with various detailed tutorials and guides, that should be enough to get anyone started...
The most obvious first step would be to determine if the phone shows "Unlocked" while booting and/or has a custom recovery installed.
ravilov said:
Okay, I must say I'm quite surprised. Even after almost a year you still haven't been able to research this on your own?
This forum is crammed with various detailed tutorials and guides, that should be enough to get anyone started...
The most obvious first step would be to determine if the phone shows "Unlocked" while booting and/or has a custom recovery installed.
Click to expand...
Click to collapse
The phone does not say unlocked. However, it does have CWM installed.
I have read through every tutorial. The issue isn't determining how to get the phone flashed to a newer ROM, it's the fact that it has a unique SBF's on it, and I am unable to receive OTA updates (though that's obvious). I'm wanting to simply upgrade it to the newest version without bricking it.
Since it dealt with flashing an SBF that has since been unsupported, I figured I should ask first, before going ahead and fiddling on my own.
Also, it being a BELL model it all the more frustrating!
(And, I am unable to take it to a BELL service store/send it in etc. since I am in Sweden.)
You have CWM. You have absolutely no need to touch a SBF ever again.
Just flash a ROM through CWM. There is no way to brick the phone that way.
All CWM-flashable ROMs work on all devices.
I have a Samsung Galaxy S2 I-9100M originally purchased from Bell. I rooted the phone using Odin. That was my first time rooting and I must admit, I kind of took blind faith in the instructions without actually taking the time to understand what's going on. In any case, everything has been working fine (except the GPS lock takes forever).
However, I would really like to see some improvements in battery life... and I heard that Gingerbread v2.3.6 has improvements from previous versions. I don't want to go to ICS because I've heard it's slow, etc. Below are the details from my phone:
Android version: 2.3.3
Basebad version: I9100MUGKG2
Kernel version: [email protected] #2
Build number: GINGERBREAD.UGKG2
Can anyone help me understand the above? Since the kernel version says 2.6.3, does that mean I am already on it? Eventhough the OS version says 2.3.3? Sorry if that's a totally ignorant question...
Hi all,
I successfully rooted my phone a year or two ago, and haven't done anything with it since. I know basically nothing about phones, but I can follow instructions pretty well.
I would like to have a general update to the phone with a new ROM (just for the sake of variety), and I would specifically like to add the following features:
-Shrink the screen down with the side-swipe motion for one handed use
-Ultra power saving mode
-Quad multi window
I would also like to do whatever needs to be done to smooth the operation of the phone out a bit--it does lag occasionally when switching between apps and stutter when moving between screens or scrolling. It isn't awful, and I don't expect perfection, but I would like to improve upon this if possible.
Here's my current set up:
TWRP Recovery; v2.6.3.1
Model number: SCH-I605
Android Version: 4.1.1
Baseband Version: I605VRALL4
Kernel Version: 3.0.31-414933 [email protected] #1
Build Number: JRO03C.I605VRALJB
Hardware Version: I605.06
Please let me know if I need to post any other information.
So here are my questions:
-I rooted my phone ages ago and haven't done anything else with it since...is there anything I need to do to my phone to move to the more recently released custom ROMs? If I need to update something, what do I need to update?
-What ROMs would you recommend I try out? I found the R3DS and DN3 ROMs, and it looks like they might work for what I'm looking for. Any thoughts on that, or other suggestions? The DN4 ROM sounds perfect, but as I understand it, it will only work on the N7100.
-As I understand it, a new kernel will allow me to overclock the phone and smooth things out. Any recommendations on that, one way or the other?
Thanks in advance for the help. :good:
Hi,
This is my first post on XDA, and I'm rather new to the site so if I'm posting in the wrong section, please let me know. Also, if I need to add any additional information, again, let me know.
I've been trying to root my Verizon Galaxy S4 for a little while now, and for some reason, every time I attempt to flash an older kernel onto my device, it fails and I don't know why. I am rooting my phone by following the instructions in this video: How To Root Samsung Galaxy S4 Android 4.4.2 EASY!!! (XDA is not letting me put the URL in the post due to the fact that this is my first post.) The video is by Sam Pullen.
Below is all of my information for my phone.
Model Number: SCH-1545
Android Version: 4.4.2
Baseband Version: I545VRUFNK1
Kernel Version: 3.4.0
[email protected] #1
Tue Nov 4 23:03:49 KST 2014
Build number: KOT49H.I545VRUFNK1
SE for Android status: Enforcing
SEPF_SCH-I545_4.4.2_0027
Secure boot status: Type: Samsung
Security Software version: MDF v1.0 Release 3
VPN v1.3 Release 2
My issue is that on my device, whenever I attempt to flash a new kernel to it, the readout on my device is Secure Magiccode Check Fail: Recovery
Any help with this would be greatly appreciated.
phughes930 said:
Hi,
This is my first post on XDA, and I'm rather new to the site so if I'm posting in the wrong section, please let me know. Also, if I need to add any additional information, again, let me know.
I've been trying to root my Verizon Galaxy S4 for a little while now, and for some reason, every time I attempt to flash an older kernel onto my device, it fails and I don't know why. I am rooting my phone by following the instructions in this video: How To Root Samsung Galaxy S4 Android 4.4.2 EASY!!! (XDA is not letting me put the URL in the post due to the fact that this is my first post.) The video is by Sam Pullen.
Below is all of my information for my phone.
Model Number: SCH-1545
Android Version: 4.4.2
Baseband Version: I545VRUFNK1
Kernel Version: 3.4.0
[email protected] #1
Tue Nov 4 23:03:49 KST 2014
Build number: KOT49H.I545VRUFNK1
SE for Android status: Enforcing
SEPF_SCH-I545_4.4.2_0027
Secure boot status: Type: Samsung
Security Software version: MDF v1.0 Release 3
VPN v1.3 Release 2
My issue is that on my device, whenever I attempt to flash a new kernel to it, the readout on my device is Secure Magiccode Check Fail: Recovery
Any help with this would be greatly appreciated.
Click to expand...
Click to collapse
read here and use the kernels from here and nothing else your phone does not and will never support any custom recovery outside of safestrap
http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613
Legitsu said:
read here and use the kernels from here and nothing else your phone does not and will never support any custom recovery outside of safestrap
http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613
Click to expand...
Click to collapse
Okay thanks. I did that and it works. So since I can't use CWM or TWRP, does that mean I also can't use things like cyanogenmod too? And not that this matters too much, due to the fact that its based in curiosity, but why can't I use CWM or TWRP? I'm just curious
phughes930 said:
Okay thanks. I did that and it works. So since I can't use CWM or TWRP, does that mean I also can't use things like cyanogenmod too? And not that this matters too much, due to the fact that its based in curiosity, but why can't I use CWM or TWRP? I'm just curious
Click to expand...
Click to collapse
No CM/ASOP/ or anything the only exception is kitpop 1.2 which is ASOP hacked together to run on the stock kernel which you are also stuck with
so basicly your choices for roms are these two
hyperdrive - touchwizz based
kitpop 1.2 ASOP based but has issues (no usb MTP,wifi requires a softboot apon every restart to work,spotty data/mms issues)
Legitsu said:
read here and use the kernels from here and nothing else your phone does not and will never support any custom recovery outside of safestrap
Just got this phone today! How sure are you that the NK1 will never support a custom recovery? I'm debating on waiting it out and staying on stock 4.4.2 after the Official Lollipop OTA hits the streets.
Click to expand...
Click to collapse
britecrawler said:
Legitsu said:
read here and use the kernels from here and nothing else your phone does not and will never support any custom recovery outside of safestrap
Just got this phone today! How sure are you that the NK1 will never support a custom recovery? I'm debating on waiting it out and staying on stock 4.4.2 after the Official Lollipop OTA hits the streets.
Click to expand...
Click to collapse
100% sure the only thing that would change that is somebody could figure out how to get kexec/kgraft to work which would grant us custom kernels and then allow us to run fully custom roms based on ASOP/CM via safestrap
anything newer then VRUMDK will never support anything other then safestrap
lolipop OTA is miles away
Click to expand...
Click to collapse
Legitsu said:
britecrawler said:
100% sure the only thing that would change that is somebody could figure out how to get kexec/kgraft to work which would grant us custom kernels and then allow us to run fully custom roms based on ASOP/CM via safestrap
anything newer then VRUMDK will never support anything other then safestrap
lolipop OTA is miles away
Click to expand...
Click to collapse
Or so I thought? VZW rolled out 5.0 to both the S5, M8, and the leaked documents say that the M7 is ready... maybe we will luck out here
Click to expand...
Click to collapse
So, I've read around the threads and haven't found anyone with my particular issue as of yet (unless I missed it).
My gf was with Verizon and had a Galaxy S5. She switched over to T-Mobile and has been able to use the phone normally (data, calling, etc.).
The phone was a little bit boggy and there was still a massive amount of bloatware from Verizon.
Is there a way to root this? I've tried towelroot (which failed), tried Odin (which failed)... I've unlocked dev options, checked the proper settings, etc... (I've been rooting all kinds of phones since Android G1).
The phone info:
Phone name: Samsung-SM-G900V
Model number: SM-G900V
Android Version: 5.0
Baseband version: G900VVRU1BOC4
Kernel version: 3.4.0 [email protected] #1
Build number: LRX21T.G900VVRU1BOC4
SE for Android status: Enforcing SEPF_SM-G900V_5.0_0002
Hardware version: G900V.05
Knox Version 2.3
Configuration version: J13.SAM.SMG900V.1
Thank you
Spitballing here, but I would say your best bet is to flash a custom recovery (in ODIN) from the klte build and flash a Cyanogenmod-based ROM + gApps from there. That will take care of the bloat. From my understanding, the majority of s5's (across carriers) have the same hardware and can flash just about anything (EXCEPT MODEMS/BASEBANDS) that is klte-based. I use Cyanogenmod 13 on my tMobile g900t s5 daily with no issues, but you may want to double check the supported phones in the ROM listing. Bliss is also an excellent option for a clean, user-friendly interface.
due to the fact you have a verizon version of the phone, the bootloader is LOCKED therefore its very difficult to root and extremely difficult to use custom rom.
I've had same phone before, i was able to root and use titanium backup to remove bloats.
i was also able to use (some) custom roms but selection is limited due to the software you need to use to fake unlock its bootloader.
at this point, i'd say your best bet is to go to just find a root that works... search http://forum.xda-developers.com/verizon-galaxy-s5
Indeed, it is a difficult process. The majority of phones I have rooted in the past were either T-Mobile or International. However, with it being a Verizon phone, it is a lot more difficult when it comes to rooting.
I have already searched that Verizon GS5 forum for ways to root and have tried practically all feasible methods with no avail, which is why I turned towards creating this post.
Thanks for your response, though. I'm hoping someone who has rooted a Verizon phone before post their process in doing so.