Related
Is it just my device or is it T-Mobile on edge this device is super slow loading web pages. My signal strength is always bouncing about but usually its -85dBm 15asu. Should I take the device in or am I just thinking to much. I just got the replacement.
Sent from my Nexus S using XDA App
Did you try the new radio introduced in 2.3.3?
Nope does it work with cm7? Can you link me to it?
Sent from my Nexus S using XDA App
Darrien13 said:
Nope does it work with cm7? Can you link me to it?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11661588&postcount=2596
bootloader.img and radio.img must be in your sdk\tools folder.
Boot into bootloader/fastboot mode
To flash the radio, use the fastboot command:
fastboot flash radio radio.img
select "reboot bootloader" and you should see the new version of the radio
To flash the bootloader:
fastboot flash bootloader bootloader.img
select "reboot bootloader" and you should see the new version of the bootloader
The new version numbers:
radio I9020XXKB1
bootloader I9020XXKA3
The versions that came with my phone:
radio I9020XXJK8
bootloader I9020XXJK1
Click to expand...
Click to collapse
also. if you haven't make sure you wipe dalvik/factory/cache to see if it would fix it.
its just difficult whether or not to say if your device is defective because you flashed a custom rom.
was it like this when you were on stock?
try flashing netarchy's 1.2.5 cm7 compatiable kernel as well
- Incorporate many updates from the newer 2.3.3 kernel sources,
including wifi driver updates, touchscreen updates, drivers for
future SLCD nexus-s variants, and more
Click to expand...
Click to collapse
If I wanted to would I be able to go back to the old radio
Sent from my Nexus S using XDA App
Darrien13 said:
If I wanted to would I be able to go back to the old radio
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
you can but there is no fastboot for the old radio available. it might be in the 2.3.2 OTA and you can pick it out from there but im not sure if its there since there wasn't a radio change in 2.3.2.
There wouldn't really be a reason for me to go back though right? Also I would still be able to flash, things from the bootloader?
Sent from my Nexus S using XDA App
Darrien13 said:
There wouldn't really be a reason for me to go back though right? Also I would still be able to flash, things from the bootloader?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes. flashing the updated bootloader is optional, but thats up to you. im not responsible for any bricks, i would just update both of them.
both of those two files are extracted from the 2.3.3 OTA.
there has been a great number of feedback that says that this radio definitely helps.
to figure out if your device is defective or not (it probably isnt).. return back to stock and see how it is. it could be based on your location since you are in a EDGE only area.
Thanks for your help. I put my sim in my G1 and it was even slower so I don't think it's my device
Edit:it was just like this when I restored back to stock
Sent from my Nexus S using XDA App
Darrien13 said:
Thanks for your help. I put my sim in my G1 and it was even slower so I don't think it's my device
Edit:it was just like this when I restored back to stock
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
It's most likely your area then. If you could get a backup of the old radio, you could try the new radio and see which one is better performance.
Hi,
i have a Xoom and it wont install any ROMS. It is a wingray model and it gets status 7 (symlink) when installing CM10 and errors when install Superuser.zip. It isnt recovery as GAPPS install. Its running CWM and i cant get the tablet to boot up. I also used HWI69.zip and restored the images and no its askes for a password? Wth? But I really want CM10 back on my tablet. I restored ALL the images. Can i get rid of this password screen?
Please help
It has a password screen. what does that even mean? is that encrpyted from the seller as I can ask the seller to put it in... What am i even meant to do?
weeo said:
Hi,
i have a Xoom and it wont install any ROMS. It is a wingray model and it gets status 7 (symlink) when installing CM10 and errors when install Superuser.zip. It isnt recovery as GAPPS install. Its running CWM and i cant get the tablet to boot up. I also used HWI69.zip and restored the images and no its askes for a password? Wth? But I really want CM10 back on my tablet. I restored ALL the images. Can i get rid of this password screen?
Please help
Click to expand...
Click to collapse
Boot into fastboot, then unlock it
Code:
fastboot oem unlock
Mjamocha said:
Boot into fastboot, then unlock it
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Hi,
Thank you for reply but I got it working. It's on 3.01 now but how do I root this properly and get it on CM10?
weeo said:
Hi,
Thank you for reply but I got it working. It's on 3.01 now but how do I root this properly and get it on CM10?
Click to expand...
Click to collapse
Universal Root
or
7Heavens Projekt
Mjamocha said:
Universal Root
or
7Heavens Projekt
Click to expand...
Click to collapse
It'll have to be 7heavens as the other one hasn't got a download link. File has been deleted
Thanks
weeo said:
It'll have to be 7heavens as the other one hasn't got a download link. File has been deleted
Thanks
Click to expand...
Click to collapse
The universal root - has the links witin the instructions. I just tried the links and they are valid.
Mjamocha said:
The universal root - has the links witin the instructions. I just tried the links and they are valid.
Click to expand...
Click to collapse
Have you got a rooted Xoom? Could you take me through the process as it never works for me
Sent from my Xoom using xda app-developers app
weeo said:
Have you got a rooted Xoom? Could you take me through the process as it never works for me
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
How far have you got? Have you unlocked the bootloader through fastboot?
Once that's done it's fairly easy. Just fastboot flash a custom recovery. I recommend Team Rogues recovery: http://forum.xda-developers.com/showthread.php?t=1235170
then reboot the device, but go into recovery before the device boots or the recovery is overwritten. To get into recovery: power on, 2 seconds later press the down button, then press the up button once you see 'Android Recovery'
Then flash the zip I have attached to root the device. Choose the JB one if you're on jelly bean, anything else, so honeycomb or ICS use the other one.
From there it's the same as any other device. Backup apps etc, make a nandroid, wipe data/factory reset, install CM10
matt4321 said:
How far have you got? Have you unlocked the bootloader through fastboot?
Once that's done it's fairly easy. Just fastboot flash a custom recovery. I recommend Team Rogues recovery: http://forum.xda-developers.com/showthread.php?t=1235170
then reboot the device, but go into recovery before the device boots or the recovery is overwritten. To get into recovery: power on, 2 seconds later press the down button, then press the up button once you see 'Android Recovery'
Then flash the zip I have attached to root the device. Choose the JB one if you're on jelly bean, anything else, so honeycomb or ICS use the other one.
From there it's the same as any other device. Backup apps etc, make a nandroid, wipe data/factory reset, install CM10
Click to expand...
Click to collapse
Oh ok. I'll flash that as I'm on honeycomb. Will report back if I get a status 7 again.
weeo said:
Oh ok. I'll flash that as I'm on honeycomb. Will report back if I get a status 7 again.
Click to expand...
Click to collapse
That's something to do with CM reads the device as XOOM but on stock a wingray is MZ604 so if I remember rightly that's what causes the status 7, to get around it, once rooted use a build prop editor to change your model to XOOM not MZ604. I think that's the way to get around it if my memory serves me well
matt4321 said:
That's something to do with CM reads the device as XOOM but on stock a wingray is MZ604 so if I remember rightly that's what causes the status 7, to get around it, once rooted use a build prop editor to change your model to XOOM not MZ604. I think that's the way to get around it if my memory serves me well
Click to expand...
Click to collapse
Thank you. So that's what a sym link error is?
weeo said:
Thank you. So that's what a sym link error is?
Click to expand...
Click to collapse
Don't me hold to it, but I seem to remember others getting status 7 errors and it was just to do with how the CM zip reads your device. You can also turn off script verification in android recovery. I think that was also another solution
matt4321 said:
Don't me hold to it, but I seem to remember others getting status 7 errors and it was just to do with how the CM zip reads your device. You can also turn off script verification in android recovery. I think that was also another solution
Click to expand...
Click to collapse
Thanks. Doing it now. Just install SU. Good luck with Gigatechworld... formerly known as Orion... BTW i know this as im your website owners friend.
weeo said:
Thanks. Doing it now. Just install SU. Good luck with Gigatechworld... formerly known as Orion... BTW i know this as im your website owners friend.
Click to expand...
Click to collapse
Glad you got everything working alright. Cheers. sweet! you know friends through xda or you actually know know him? if you know what I mean
matt4321 said:
Glad you got everything working alright. Cheers. sweet! you know friends through xda or you actually know know him? if you know what I mean
Click to expand...
Click to collapse
XDA. We've been friends for 2 years. I use to make ROMS for the ZTE blade. I think he started talking to me when I made HTC Sense with a few others on the blade. I have him the idea for Orion
weeo said:
XDA. We've been friends for 2 years. I use to make ROMS for the ZTE blade. I think he started talking to me when I made HTC Sense with a few others on the blade. I have him the idea for Orion
Click to expand...
Click to collapse
that's pretty awesome! I remember you over at modaco, used to be fairly active there as the zte blade has a big community there but the xoom has a bigger one here. how come you didn't come aboard with us on the blog?
matt4321 said:
that's pretty awesome! I remember you over at modaco, used to be fairly active there as the zte blade has a big community there but the xoom has a bigger one here. how come you didn't come aboard with us on the blog?
Click to expand...
Click to collapse
I was active a lot here too. Till I shut my account down. I already have my own website. That's where the idea was set off from.
Success, CM10 is booting on my Xoom .
weeo said:
I was active a lot here too. Till I shut my account down. I already have my own website. That's where the idea was set off from.
Success, CM10 is booting on my Xoom .
Click to expand...
Click to collapse
That's awesome!
Nice to hear you have CM10 running too, so much better than stock
matt4321 said:
That's awesome!
Nice to hear you have CM10 running too, so much better than stock
Click to expand...
Click to collapse
Thanks to you
Sent from my Xoom using XDA Premium HD app
Just got an upgrade from my carrier (a small local carrier) and I chose the s3. Came from some Motorola peice of fail. I'm looking to root and flash an insecure bootloader but I have encountered a confusing conflict. Having a Verizon model phone with a us cellular build of android loaded. And yes I'm certain it is a Verizon model phone (google schi535mbb if you don't believe me) with us cellular stock rom loaded (with some tweeks like 4g disabled). Rom and software model say the following R530 & d2usc. Bootloader is I535VRALE6 baseband I535VRLF2. This as far as I can tell was acomplished by a company called ultimobile. Which customizes devices to function on small mobile carriers. If anybody has any ideas or suggestions on what I might try, please let me know. I just don't want to screw something up and have a brick, just coming from a device that was all but brickable.
Sent from my SCH-I535 using xda premium
Lrs121 said:
Just got an upgrade from my carrier (a small local carrier) and I chose the s3. Came from some Motorola peice of fail. I'm looking to root and flash an insecure bootloader but I have encountered a confusing conflict. Having a Verizon model phone with a us cellular build of android loaded. And yes I'm certain it is a Verizon model phone (google schi535mbb if you don't believe me) with us cellular stock rom loaded (with some tweeks like 4g disabled). Rom and software model say the following R530 & d2usc. Bootloader is I535VRALE6 baseband I535VRLF2. This as far as I can tell was acomplished by a company called ultimobile. Which customizes devices to function on small mobile carriers. If anybody has any ideas or suggestions on what I might try, please let me know. I just don't want to screw something up and have a brick, just coming from a device that was all but brickable.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Interesting. From the sound of it it may just be software blocked. Verizon root and unlock should work. The trick is gonna be finding software that will work with that carrier. If it is using straight UC Cellular may be able to run what those guys are running. If it is that small carrier that controls access then that would be the problem. Without a backup of the stock rom don't know how you would get it running again. According to the numbers it is a Verizon S3 running Us Cellular. Good luck.
prdog1 said:
Interesting. From the sound of it it may just be software blocked. Verizon root and unlock should work. The trick is gonna be finding software that will work with that carrier. If it is using straight UC Cellular may be able to run what those guys are running. If it is that small carrier that controls access then that would be the problem. Without a backup of the stock rom don't know how you would get it running again. According to the numbers it is a Verizon S3 running Us Cellular. Good luck.
Click to expand...
Click to collapse
The recovery that's on it right now has built in options for nvbackup. From what I've read that is the radio, imei, and other files used to connect to the network. I was gonna make several backups of everything as soon as I gained root control. The real problem comes down to when I go to throw cm on here. Figuring out which vzw or usc will cooperate with the carrier files.
Sent from my SCH-I535 using xda premium
Lrs121 said:
The recovery that's on it right now has built in options for nvbackup. From what I've read that is the radio, imei, and other files used to connect to the network. I was gonna make several backups of everything as soon as I gained root control. The real problem comes down to when I go to throw cm on here. Figuring out which vzw or usc will cooperate with the carrier files.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Make a nandroid backup and maybe post to see what your running as?
Sent from my SCH-I535 using Tapatalk 2
Addiso said:
Make a nandroid backup and maybe post to see what your running as?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Was definitely gonna make a nandroid, but as for 'post to see what I'm running as' what do you mean?
Sent from my SCH-I535 using xda premium
Lrs121 said:
Was definitely gonna make a nandroid, but as for 'post to see what I'm running as' what do you mean?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Maybe the build.prop?
Edit: Attach it via Pastebin!
SlimSnoopOS said:
Maybe the build.prop?
Edit: Attach it via Pastebin!
Click to expand...
Click to collapse
Here ya go. Have fun http://pastebin.com/eUj5z2VT
Sent from my SCH-I535 using xda premium
Lrs121 said:
Here ya go. Have fun http://pastebin.com/eUj5z2VT
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Addiso said:
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's weird though right? I'm not sure how to go about suggesting how to flash roms. I have to side with prdog1 and say it's a VZW GSIII running USC. I really can't suggest a good way to proceed since it's hard to tell what you would use to revert back to stock in case of emergences.
Anyone familiar with Team US Cellular? Any input from there?
Addiso said:
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thats what i saw too. the difficult thing to figure out is if to use the verizon unlock and root or the us cellular model. it is most definately a verizon model of phone just loaded up with us cell software. ive flashed verizon a based rom over a locked down motorola peice of fail, but that couldnt touch the kernel, base band, or anything but the system with out it requiring a complete reflash to stock. i dont exactly have that option if every thing screws up in the process of gaining root. id have to take it into the store and wait till they can reflash it there.
Lrs121 said:
thats what i saw too. the difficult thing to figure out is if to use the verizon unlock and root or the us cellular model. it is most definately a verizon model of phone just loaded up with us cell software. ive flashed verizon a based rom over a locked down motorola peice of fail, but that couldnt touch the kernel, base band, or anything but the system with out it requiring a complete reflash to stock. i dont exactly have that option if every thing screws up in the process of gaining root. id have to take it into the store and wait till they can reflash it there.
Click to expand...
Click to collapse
I'm fairly certain you should use the unified toolkit to root and maybe unroot. In your build.prop, I noticed it reads on the fifth line:
ro.build.version.incremental=R530UVXALK5
Click to expand...
Click to collapse
and the toolkit supports LK5 build for the d2usc. I think they're both locked down the same but on Team US Cellular's website that's what I'm seeing some people have used too. Idk about your specific case using another carrier but a d2usc GSIII but I'm thinking that's a start. Idk about returning to stock though.
Edit: Gonna add this, this means there is an Odin flashable of LK5 available somewhere.
Edit x2: POW!
SlimSnoopOS said:
I'm fairly certain you should use the unified toolkit to root and maybe unroot. In your build.prop, I noticed it reads on the fifth line:
and the toolkit supports LK5 build for the d2usc. I think they're both locked down the same but on Team US Cellular's website that's what I'm seeing some people have used too. Idk about your specific case using another carrier but a d2usc GSIII but I'm thinking that's a start. Idk about returning to stock though.
Edit: Gonna add this, this means there is an Odin flashable of LK5 available somewhere.
Edit x2: POW!
Click to expand...
Click to collapse
really i need to gain fastboot access to the phone. there are some files i need to check and i need to pull the special recovery that came with the phone. if i can do that i should be able to pull what i need from the phone to be able to return to stock. im also gonna perform an nvback up, a qpst backup and the synergy back up. but first things first i need fastboot access to the phone. i know how to get into recovery and download mode but for the life of me i cant figure out how to get to a fastboot compliant mode. from there i can figure how im gonna proceed to root.
edit: what i see in download mode
odin mode
Product name: sch--i535
custom binary download: yes (1 counts)
current binary: custom
system status: custom
Qualcom secureboot: enable
Lrs121 said:
really i need to gain fastboot access to the phone. there are some files i need to check and i need to pull the special recovery that came with the phone. if i can do that i should be able to pull what i need from the phone to be able to return to stock. im also gonna perform an nvback up, a qpst backup and the synergy back up. but first things first i need fastboot access to the phone. i know how to get into recovery and download mode but for the life of me i cant figure out how to get to a fastboot compliant mode. from there i can figure how im gonna proceed to root.
edit: what i see in download mode
odin mode
Product name: sch--i535
custom binary download: yes (1 counts)
current binary: custom
system status: custom
Qualcom secureboot: enable
Click to expand...
Click to collapse
Here's a left field suggestion, could you call this UltiMobile company and ask about what they used?
SlimSnoopOS said:
Here's a left field suggestion, could you call this UltiMobile company and ask about what they used?
Click to expand...
Click to collapse
havent done that yet. its on a list of things to do the problem is that everywhere they put information out they say to contact the carrier not them for everything. i may just have to wait till the phone isnt so new at my carrier and let the IT department play around with it for a while. i can then get information from them.
Lrs121 said:
havent done that yet. its on a list of things to do the problem is that everywhere they put information out they say to contact the carrier not them for everything. i may just have to wait till the phone isnt so new at my carrier and let the IT department play around with it for a while. i can then get information from them.
Click to expand...
Click to collapse
That's real tricky but sounds like your best option. At least you're rooted and unlocked with the VRALE6 bootloader and can debloat. Out of curiosity, what recovery are you using that has all these options?
As an aside, this table tells you where the recovery partition is. I've heard of people using dd commands to pull whatever partition they want to their sdcard but idk how viable an option this is in terms of pushing a recovery to that partition. I'm not recommending you try it either.
SlimSnoopOS said:
That's real tricky but sounds like your best option. At least you're rooted and unlocked with the VRALE6 bootloader and can debloat. Out of curiosity, what recovery are you using that has all these options?
As an aside, this table tells you where the recovery partition is. I've heard of people using dd commands to pull whatever partition they want to their sdcard but idk how viable an option this is in terms of pushing a recovery to that partition. I'm not recommending you try it either.
Click to expand...
Click to collapse
The vrale6 is unlocked? If so then why does it say that the qualcom secure boot is enabled. And I haven't rooted just yet but am working on it. Its a recovery built by ultimobile.
Sent from my Nexus 7 using XDA Premium HD app
Lrs121 said:
The vrale6 is unlocked? If so then why does it say that the qualcom secure boot is enabled. And I haven't rooted just yet but am working on it. Its a recovery built by ultimobile.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yes indeed. VRALE6 is the prerelease bootloader that was leaked which EVERY d2vzw (d2usc I suppose too) uses in order to allow flashing of roms/kernels. It's a little weird to explain but basically everyone's Download Mode reads almost the same. Mine reads "custom binary: Samsung Official" though and I'm rooted/unlocked. Idk the technical or even the proper way to explain it but the unlocked VRALE6 bootloader has no bearing on what Download mode says. Although your custom binary should be at 0 if/when you do warranty exchanges.
SlimSnoopOS said:
Yes indeed. VRALE6 is the prerelease bootloader that was leaked which EVERY d2vzw (d2usc I suppose too) uses in order to allow flashing of roms/kernels. It's a little weird to explain but basically everyone's Download Mode reads almost the same. Mine reads "custom binary: Samsung Official" though and I'm rooted/unlocked. Idk the technical or even the proper way to explain it but the unlocked VRALE6 bootloader has no bearing on what Download mode says. Although your custom binary should be at 0 if/when you do warranty exchanges.
Click to expand...
Click to collapse
Ah makes sense now it just doesn't do a hash/encryption check. I've dealt with a lot of bootloader stuff with my old phone. the phone came like that with the count at 1. Was like that before I tried anything. Probably was triggered when the d2usc stock was flashed onto it. Which probably means I should stick with d2usc builds to ensure compatibility with connecting with my carrier.
Sent from my Nexus 7 using XDA Premium HD app
...and you DON'T want to perform a Factory Reset.
Figured this out while returning to the stock kernel after poor performance on a custom one...
THIS WILL LIKELY NOT WORK IF YOU ARE ON A CUSTOM ROM
If you are still on the Stock ROM you can do this to get new updates from your carrier (I have only tried AT&T):
1. Unfreeze AT&T updater (if you have it frozen)
2. Use ODIN to return to stock WITHOUT performing a factory reset. AdamOutler has a thread HERE with the stock firmware download in the Android Development section
3. Boot up and check for updates
4. After you have updated, root it, apply your custom recovery, and/or kernel again
5. Hit the THANKS button below
All your apps and settings will remain. You may have to re-sign-in to some, but you should be good to go.
joeybear23 said:
Figured this out while returning to the stock kernel after poor performance on a custom one...
THIS WILL LIKELY NOT WORK IF YOU ARE ON A CUSTOM ROM
If you are still on the Stock ROM you can do this to get new updates from your carrier (I have only tried AT&T):
1. Unfreeze AT&T updater (if you have it frozen)
2. Use ODIN to return to stock WITHOUT performing a factory reset. AdamOutler has a thread with the stock firmware download in the Android Development section
3. Boot up and check for updates
4. After you have updated, root it, apply your custom recovery, and/or kernel again
5. Hit the THANKS button below
All your apps and settings will remain. You may have to re-sign-in to some, but you should be good to go.
Click to expand...
Click to collapse
Where can you find out when carrier updates are released?
This will always work no matter what Rom your on...even if your on aosp...Odin is created so that you can return to stock. Once your on stock you can receive any update available...
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
This will always work no matter what Rom your on...even if your on aosp...Odin is created so that you can return to stock. Once your on stock you can receive any update available...
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, however if you are on a custom ROM you must perform a factory reset prior to or after ODIN, which will make you lose your apps, settings, etc.
If you are still on the stock ROM, you don't have to factory reset... which is kind of the point for people who want the update but don't want to factory reset.
blyndfyre said:
Where can you find out when carrier updates are released?
Click to expand...
Click to collapse
Just follow the forum. When an update is released, I guarantee you there will be no less than 50 new threads in here.
joeybear23 said:
Just follow the forum. When an update is released, I guarantee you there will be no less than 50 new threads in here.
Click to expand...
Click to collapse
Assumed as much, but wanted to be sure. I'm on this forum exclusively and hourly anyways lol. So much reading to be done!
Will updates be specific to carrier? For instance I'm on Telus in Canada so I'll need to wait for my specific update, download and flash via ODIN? (Since I'm 'custom' status and won't be able to OTA. Root only, stock recovery, kernel and ROM.)
And thanks btw!
blyndfyre said:
Assumed as much, but wanted to be sure. I'm on this forum exclusively and hourly anyways lol. So much reading to be done!
Will updates be specific to carrier? For instance I'm on Telus in Canada so I'll need to wait for my specific update, download and flash via ODIN? (Since I'm 'custom' status and won't be able to OTA. Root only, stock recovery, kernel and ROM.)
And thanks btw!
Click to expand...
Click to collapse
Unfortunately I can't speak for anything other than AT&T since I don't have the ability to test any other carrier's devices... however the update will likely be pushed by your carrier with their proprietary update mechanism.
If you want to use something other than OTA, you can wait for a flashable zip when it comes available, which will likely be pretty quick after initial release.
joeybear23 said:
Unfortunately I can't speak for anything other than AT&T since I don't have the ability to test any other carrier's devices... however the update will likely be pushed by your carrier with their proprietary update mechanism.
If you want to use something other than OTA, you can wait for a flashable zip when it comes available, which will likely be pretty quick after initial release.
Click to expand...
Click to collapse
Thanks man. One last question, would this flashable zip flash via ODIN or Custom Recovery (TWRP/CWM) or either method?
blyndfyre said:
Thanks man. One last question, would this flashable zip flash via ODIN or Custom Recovery (TWRP/CWM) or either method?
Click to expand...
Click to collapse
Depends on the Developer... most likely a flashable zip for TWRP/CWM
joeybear23 said:
Depends on the Developer... most likely a flashable zip for TWRP/CWM
Click to expand...
Click to collapse
Maybe a tad off topic, but if one were to follow the directions in the OP, wouldn't it still not work? You'd still have the custom unlock button with stock firmware, which would prevent it to look for any OTA update.
Maybe I'm wrong?
MattMJB0188 said:
Maybe a tad off topic, but if one were to follow the directions in the OP, wouldn't it still not work? You'd still have the custom unlock button with stock firmware, which would prevent it to look for any OTA update.
Maybe I'm wrong?
Click to expand...
Click to collapse
I thought the same thing, until I tried it and the OTA came over just fine. That's one of the reason I started this thread, so others would know they can do it.
The ODIN gives you back the stock recovery so you can pull the OTA.
joeybear23 said:
I thought the same thing, until I tried it and the OTA came over just fine. That's one of the reason I started this thread, so others would know they can do it.
The ODIN gives you back the stock recovery so you can pull the OTA.
Click to expand...
Click to collapse
Do you know if doing so removes the custom unlock icon?
If I'm running custom rom s and kernels would the att update even be beneficial?
MattMJB0188 said:
Do you know if doing so removes the custom unlock icon?
Click to expand...
Click to collapse
It will not.
Sent from my SAMSUNG-SGH-I337 using xda premium
Bigtjmc said:
If I'm running custom rom s and kernels would the att update even be beneficial?
Click to expand...
Click to collapse
ROMs? No
Kernels only? Yes imho
Sent from my SAMSUNG-SGH-I337 using xda premium
joeybear23 said:
It will not.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Ok, how about if one follows your method and then updates via AT&T OTA. Would it then get rid of the custom unlock status? How does one remove this if they're not rooted with 100% stock? I don't get why it still shows it.
MattMJB0188 said:
Ok, how about if one follows your method and then updates via AT&T OTA. Would it then get rid of the custom unlock status? How does one remove this if they're not rooted with 100% stock? I don't get why it still shows it.
Click to expand...
Click to collapse
I am not 100% certain what all gets looked at when the firmware runs its "custom status" check. I do know that there are a wide variety of fixes/solutions that work for some and not for others... I have the custom icon, but it doesn't bother me, so I haven't done too much research into it.
joeybear23 said:
I am not 100% certain what all gets looked at when the firmware runs its "custom status" check. I do know that there are a wide variety of fixes/solutions that work for some and not for others... I have the custom icon, but it doesn't bother me, so I haven't done too much research into it.
Click to expand...
Click to collapse
+1
Doesn't bother me one bit, although my bootloader is unlocked so I don't get the unlock icon boot screen.
Maybe a stupid question, but could one flash SGH-I337 UCUAMDL firmware instead since its the latest, or would it better to flash the original firmware then update?
MattMJB0188 said:
Maybe a stupid question, but could one flash SGH-I337 UCUAMDL firmware instead since its the latest, or would it better to flash the original firmware then update?
Click to expand...
Click to collapse
Not a stupid question at all. Yes you can do that. When I started this thread there was not one available.
Sent from my SAMSUNG-SGH-I337 using xda premium
So I am waiting for my nexus 5 to arrive (hopefully by end of this week or early next week) and I am pretty sure I want to root it. Coming from a rooted s3, there are just way too many advantages of Rooting that I cannot give up. So I have a few questions:
1) how easy it is to relock the bootloader for warranty purposes? Has anyone had to send back their rooted phone to Google and been successful?
2) has anyone here unrooted their phone successfully and sent it back to Google for warranty?
3) if I root but do not flash a custom rom, will I still be able to do Ota updates?
4) will simply uprooting the device (with stock rom) cause any unstability issues?
Thanks!
Sent from my Galaxy S3 on CM10.1 using XDA App
1) see the return to stock thread (sticky) in general
2) yes by following the thread in 1)
3) theres a great thread called "ota help-desk" in general that covers this. Its not a sticky but easily located with search
4) uprooting? If you mean unrooting, then no
Sent from my Nexus 5 using Tapatalk
blackdragon12 said:
So I am waiting for my nexus 5 to arrive (hopefully by end of this week or early next week) and I am pretty sure I want to root it. Coming from a rooted s3, there are just way too many advantages of Rooting that I cannot give up. So I have a few questions:
1) how easy it is to relock the bootloader for warranty purposes? Has anyone had to send back their rooted phone to Google and been successful?
2) has anyone here unrooted their phone successfully and sent it back to Google for warranty?
3) if I root but do not flash a custom rom, will I still be able to do Ota updates?
4) will simply uprooting the device (with stock rom) cause any unstability issues?
Thanks!
Sent from my Galaxy S3 on CM10.1 using XDA App
Click to expand...
Click to collapse
Watch these 2 videos and everything will be clear
Sent from my Nexus 5
generally, if its a hardware issue with your device, google will accept rooted devices to fix/replace. if its a software issue, theyll just send it back. ive sent a nexus phone and tablet in for replacement last year, both were still rooted, both still had custom recoveries, custom animations, custom roms, and custom kernels. they gave me no issues about the exchange.
Oh that's great to hear. Then why is known that unlocking your bootloader voids your warranty?
That's my biggest fear. If I unlock the bootloader and then have a hardware issue and cannot relock the bootloader, Will Google refuse to fix it?
Thanks for all the replies! I will check out those topics and videos.
Sent from my Galaxy S3 on CM10.1 using XDA App
Also use this for a quick 'untampered':
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en
simms22 said:
generally, if its a hardware issue with your device, google will accept rooted devices to fix/replace. if its a software issue, theyll just send it back. ive sent a nexus phone and tablet in for replacement last year, both were still rooted, both still had custom recoveries, custom animations, custom roms, and custom kernels. they gave me no issues about the exchange.
Click to expand...
Click to collapse
LG will not procede the same way in country`s where you can`t buy the N5 i`am afraid and will say your warranty is voided because of rooting the phone.
blackdragon12 said:
Oh that's great to hear. Then why is known that unlocking your bootloader voids your warranty?
Sent from my Galaxy S3 on CM10.1 using XDA App
Click to expand...
Click to collapse
Fear tactic for the unfortunate contract phone buyers.
blackdragon12 said:
Oh that's great to hear. Then why is known that unlocking your bootloader voids your warranty?
That's my biggest fear. If I unlock the bootloader and then have a hardware issue and cannot relock the bootloader, Will Google refuse to fix it?
Thanks for all the replies! I will check out those topics and videos.
Sent from my Galaxy S3 on CM10.1 using XDA App
Click to expand...
Click to collapse
if you buy the phone from somewhere else, it will void the warranty, but its easily locked with "fastboot oem lock". but through google, as long as its a hardware issue, they will take care of you.
I ordered the phone from the play store (in canada) so I assume all will be good.
Also to the link to an app to the play store, how exactly does that work? It seems like the perfect solution so why don't more people use it?
Sent from my Galaxy S3 on CM10.1 using XDA App
blackdragon12 said:
I ordered the phone from the play store (in canada) so I assume all will be good.
Also to the link to an app to the play store, how exactly does that work? It seems like the perfect solution so why don't more people use it?
Sent from my Galaxy S3 on CM10.1 using XDA App
Click to expand...
Click to collapse
Bootunlocker works great. More people don't use it. because they don't know about it. It's also not an app you're going to use everyday
Sent from my Nexus 5
gee2012 said:
LG will not procede the same way in country`s where you can`t buy the N5 i`am afraid and will say your warranty is voided because of rooting the phone.
Click to expand...
Click to collapse
right, with lg it will "void the warranty", thats why i specifically stated that google will except it
jd1639 said:
Bootunlocker works great. More people don't use it. because they don't know about it. It's also not an app you're going to use everyday
Sent from my Nexus 5
Click to expand...
Click to collapse
Additionally, it only covers a few phones (Nexi).
http://forum.xda-developers.com/showthread.php?t=1731993
That makes sense.
Can't wait to get my nexus! It said that it will ship by 21st...so I should be getting it the week after. I will probably root it right away before I start installing all my apps
Sent from my Galaxy S3 on CM10.1 using XDA App
May aswell. Just make sure you read all the sticky threads first and stay away from toolkits
Sent from my Nexus 5 using Tapatalk
blackdragon12 said:
That makes sense.
Can't wait to get my nexus! It said that it will ship by 21st...so I should be getting it the week after. I will probably root it right away before I start installing all my apps
Sent from my Galaxy S3 on CM10.1 using XDA App
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showthread.php?t=2507905
Sent from my Nexus 5 using Tapatalk
Mr hOaX said:
Read this http://forum.xda-developers.com/showthread.php?t=2507905
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
If I do not install a custom recovery, can I still root?
Im thinking of just using this as I only want root access and do not need all the features from a custom recovery: http://forum.xda-developers.com/showthread.php?t=2507211
blackdragon12 said:
If I do not install a custom recovery, can I still root?
Click to expand...
Click to collapse
You can using CF-AutoRoot, but it's all a bit one-click which removes your learning curve and invariably ends with you bricking your device, so lets go the custom recovery route please
blackdragon12 said:
If I do not install a custom recovery, can I still root?
Click to expand...
Click to collapse
Yup, download the latest TWRP recovery, plave it i the fastboot folder and rename it to twrp.img. Place the superSU.zip file on the phones `s sdcard.
Boot into bootlader and type in cmd: fastboot boot twrp.img, twrp will boot (not install) and you can flash the superSU.zip file and reboot.
gee2012 said:
Yup, download the latest TWRP recovery, plave it i the fastboot folder and rename it to twrp.img. Place the superSU.zip file on the phones `s sdcard.
Boot into bootlader and type in cmd: fastboot boot twrp.img, twrp will boot (not install) and you can flash the superSU.zip file and reboot.
Click to expand...
Click to collapse
Get the latest twrp image here http://techerrata.com/browse/twrp2/hammerhead
Sent from my Nexus 5