Database Info

Can I still root? Got new one x today

I got the one x coming from the s3 and I like it but was wondering if I should update or am I okay to root on what I am running?
Sent from my HTC One X using xda premium

Optimizer said:
I got the one x coming from the s3 and I like it but was wondering if I should update or am I okay to root on what I am running?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
yes, currently software version 1.85 is rootable. i would strongly recommend staying away from any ONE-CLICK rooting methods, as you may inadvertently OTA yourself. one click asks you to check for updates, but back then there wasn't an update to be found. if you do one click, and you do begin to update, quickly run a factory reset to get out of the OTA
once you OTA, you can never root or unlock your phone. (that's what happened to me)

wdkingery said:
yes, currently software version 1.85 is rootable. i would strongly recommend staying away from any ONE-CLICK rooting methods, as you may inadvertently OTA yourself. one click asks you to check for updates, but back then there wasn't an update to be found. if you do one click, and you do begin to update, quickly run a factory reset to get out of the OTA
once you OTA, you can never root or unlock your phone. (that's what happened to me)
Click to expand...
Click to collapse
Well does anyone know a current good root method to unlock bootloader and gain root?

Optimizer said:
Well does anyone know a current good root method to unlock bootloader and gain root?
Click to expand...
Click to collapse
user "google" knows how.
http://www.theandroidsoul.com/root-htc-one-xl-att-one-x-1-85-update-with-just-one-click/

Optimizer said:
Well does anyone know a current good root method to unlock bootloader and gain root?
Click to expand...
Click to collapse
Use this one click:
http://forum.xda-developers.com/showthread.php?t=1709424
I disagree with the other poster. Sure, you're going to check for updates, and if the one-click root does not work, it will start to download the update. The update is 100's of mb, so you have plenty of time to go and manually change the date in your settings. Just add two days. This will immediately confuse the server, and it corrupts the download and stops right away. Then try the root process again. It took me many tries of adding two days (got somewhere near the end of August), but low and behold, it finally was successfully.
Also, at any point feel free to do a factory reset and start again. All of the people's recent experiences are near the end of the thread I posted above.
FYI, I did this 3 days ago on my phone.

ckombo said:
Use this one click:
http://forum.xda-developers.com/showthread.php?t=1709424
I disagree with the other poster. Sure, you're going to check for updates, and if the one-click root does not work, it will start to download the update. The update is 100's of mb, so you have plenty of time to go and manually change the date in your settings. Just add two days. This will immediately confuse the server, and it corrupts the download and stops right away. Then try the root process again. It took me many tries of adding two days (got somewhere near the end of August), but low and behold, it finally was successfully.
Also, at any point feel free to do a factory reset and start again. All of the people's recent experiences are near the end of the thread I posted above.
FYI, I did this 3 days ago on my phone.
Click to expand...
Click to collapse
i, unfortunately, was not bright enough to realize all of this, and it was not spelled out clearly, so i ended up OTA'ing. if you are competent enough to do what is quoted here, then it works.

Got mine 3 weeks ago. ONE CLICKS not working at all for 1.85
SUPERCID is the one that worked for me.
http://forum.xda-developers.com/showthread.php?t=1709424
Here is the link.
I couldn't get CWM recovery to work. Flashed TWRP and very happy with that.

wdkingery said:
i, unfortunately, was not bright enough to realize all of this, and it was not spelled out clearly, so i ended up OTA'ing. if you are competent enough to do what is quoted here, then it works.
Click to expand...
Click to collapse
Well, you're competent enough to be getting 2x better fuel economy than me!

How about reading a little and using the manual method? You should have no problem with that one.
Sent from my One X using xda app-developers app

yup
wdkingery said:
i, unfortunately, was not bright enough to realize all of this, and it was not spelled out clearly, so i ended up OTA'ing. if you are competent enough to do what is quoted here, then it works.
Click to expand...
Click to collapse
Same here thats what I did, 1.85 lost...also hope.....lost

SkizzMcNizz said:
How about reading a little and using the manual method? You should have no problem with that one.
Click to expand...
Click to collapse
Given the fact that this thread started with a question that has been answered tens, if not hundreds of times, I suspect that "reading a little" is not an option for the OP

subarudroid said:
Got mine 3 weeks ago. ONE CLICKS not working at all for 1.85
SUPERCID is the one that worked for me.
http://forum.xda-developers.com/showthread.php?t=1709424
Here is the link.
I couldn't get CWM recovery to work. Flashed TWRP and very happy with that.
Click to expand...
Click to collapse
Yeah.. CWM isn't supported by the One X, TWRP is.
So if anyone new is reading this, please avoid CWM. It'll be of benefit for you.

New to Inspire

Hey guys, I just picked up a Inspire as a play toy since my cousin upgraded.. What in looking for is a RUU for the latest update if there is any.. 2.3.5, firmware 3.20 if I'm not mistaken. (Its not in front of me at the moment).. I've tried numerous sites and it seems as though they don't exist anymore..
Quick history, phone worked fine. Bone stock, never rooted or unlocked. So she took the latest update, and ever since then it has problems... Main thing is when the screen goes black, it reboots. EVERY SINGLE TIME. So I decided to unlock via htcdev, fastbooted twrp 2.4.4.0, and flashed a rom to see if it fixed it. Flashed jellytime and respective gapps, no dice. Phone is still rebooting upon locking. Last resort is a ruu... I've tried over clocking, overvolting, etc... No go. I'm not ruling out hardware 100%, but bc it didn't do this before the update makes it last on my list... Any advice?
Sent from my One X using Tapatalk 2

Test it without the sd card.
Reflash the ruu.
Sent from a dream.

I don't have the ruu lol. That's why I posted here... It seems like every site has it taken down...
Sent from my One X using Tapatalk 2

InflatedTitan said:
I don't have the ruu lol. That's why I posted here... It seems like every site has it taken down...
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
https://www.google.com/#hl=en&output=search&sclient=psy-ab&q=htc_inspire4g_att_RUU_3.20.502.52_US&oq=htc_inspire4g_att_RUU_3.20.502.52_US&gs_l=hp.3...3147.3147.0.4546.1.1.0.0.0.0.204.204.2-1.1.0.les%3B..0.0...1c.2.6.psy-ab.m3erFIGkS8Q&pbx=1&bav=on.2,or.r_cp.r_qf.&bvm=bv.43828540,d.eWU&fp=c539a620ba7dec8b&biw=1366&bih=641
There seems to be a link with the files, haven't checked if it's in it. As well, I have a copy of the last inspire update but no where to upload it and in case you can't find it via the provided link.

Hey thanks man. I'll give that a shot .
One more question, if I flash the stock lower firmware zip, would that be enough to run the aahk to s-off? Or is there more to it than that? Last time I tried it said the firmware was not supported up to that version
Sent from my One X using Tapatalk 2

InflatedTitan said:
Hey thanks man. I'll give that a shot .
One more question, if I flash the stock lower firmware zip, would that be enough to run the aahk to s-off? Or is there more to it than that? Last time I tried it said the firmware was not supported up to that version
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I wouldn't recommend flashing a lower firmware.... Not sure if anything bad will happen but it does not seem like a good idea. Besides, aahk has been retired. There is no support for it and it is only for advanced users.
You can try glevitans tool in the development section to unlock your bootloader but he two has left these forums due to too many self rightious (or however you spell that) noobs.
Sent from a dream.

Right... I'm already unlocked and rooted.. So there's no way to s-off without jumping through hoops? Lol... I can throw out some fastboot and adb commands... But as far as DD'ing blck partitions I'll just give up on s-offing
Sent from my One X using Tapatalk 2

Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file..
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2

InflatedTitan said:
Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file..
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I can't give you any other advice to the first problems you had but yes when you boot into hboot. It automatically searches for a pd98img.zip.. That is completely normal
Sent from my Inspire 4G using xda premium

Small carrier, model/build version, flashing decision issues

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

[Q] bricked and terrified 4.3

okay i upgraded to 4.3 OTA and tried to revert back and soft bricked my phone. I still have access to download mode and the stock recovery. I know now that i can not revert but is there any way of getting it back to 4.3 so i can have a phone again?
thanks for the future help.

This is similar what happened to me. I have never done anything with my phone as far as rooting and I tried reverting to stock 4.1.2. In Odin I kept getting the "Nand Start! Fail (Auth)" because of the locked bootloader I guess. I flashed some other firmware that was unofficial with the locked bootloader and now I get the "unauthorized software detected" and I cant do anything but enter Odin download mode. What should I do?

that is exactly what is happing to me. same error and all.

Once you took the OTA 4.3 you got locked in. No way of going back.
Sent from my SCH-I535 using Tapatalk

I dont want to go back just get rid of the soft brick so i can use it

im having the same problem and need to get it fixed please help anyone???!!!! im leaving for florida in two days and have nothing else. HELP!!!!

If you took the OTA and tried to flash 4.1.2 Odin or unlock bootloader you are Hard bricked , no method or recovering it yet.
If you have stock recovery and download mode , only hope is wait for 4.3 .tar file

Theres no custom recovery I can flash and flash some other software or something?

Elemt said:
Theres no custom recovery I can flash and flash some other software or something?
Click to expand...
Click to collapse
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661

jlyle said:
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
Do you know if anyone is working on a fix? or a .tar file of 4.3?

dvdavid2 said:
Do you know if anyone is working on a fix? or a .tar file of 4.3?
Click to expand...
Click to collapse
Thanks for the info. hopefully a fix will be done soon. And do you know how i should keep to see when the work around is finished .
thanks in advanced guys.

This might give you a chance to unbrick.... possibly
http://forum.xda-developers.com/showthread.php?t=2581166

I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app

ScubaSteev said:
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app

jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Any break throughs????

dvdavid2 said:
Any break throughs????
Click to expand...
Click to collapse
None that I have seen
Sent from my SCH-I535 using xda app-developers app

jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.

BattsNotIncld said:
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
Click to expand...
Click to collapse
The first time I ever rooted, I was worried about bricking. So i read everything I could find relevant.
Why in the world anyone would flash without reading is beyond me. Every single thread in Verizon Galaxy S3 at least mentions, if not totally devoted, to how bad 4.3 is and if you flash something on it you will brick.
I just don't get it.
Sent from my Last Ever Samsung Device.

If you do a battery pull and start back up in download mode (might take a couple of times to get it to work) then use the Verizon software upgrade assistant it should fix it but you will be stuck with 4.3. Worked for me

Can't install Marshmallow

Hi,
I just got a notification on my Z3 saying that Marshmallow-update is available. When I first tried to download it, it said I needed more space. I now have 1.84GB available (the update is about 980mb). When I install it, it reboots and I see the update screen. Then it suddenly boots back into phone and says "The update could not be installed. Try again."
Do I need even more space? The phone is rooted, in case that matters.

I have same issue with Hydro Icon update to lollipop. Is it because the phone doesn't have service? (Which might be my problem.)
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I have same issue with Hydro Icon update to lollipop. Is it because the phone doesn't have service? (Which might be my problem.)
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I have service, never had issues with updates. Im thinking either its lack of space (while the update is 980mb, and I do have more than that, it might be a compromised file?) Other than that it might be because its rooted, but I have no idea to be honest.

I could be... My Icon is rooted too... Maybe that IS stopping it.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I could be... My Icon is rooted too... Maybe that IS stopping it.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I just read up on it and it seems you cant get OTA updates if you have a rooted phone. You need to flash original firmware (which I assume completely wipes your phone, so remember to backup). After that, you can get the OTA update.
Also make sure its the correct original firmware you get for your specific model (ie. for my Z3 there are different firmwares for different models).

Thanks. Good piece of info right there... All I did was root so I assume if I unroot I'll be able to get the update.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Thanks. Good piece of info right there... All I did was root so I assume if I unroot I'll be able to get the update.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Yep, you will. How it is done is different from phone to phone though I believe. Just make sure you get the correct firmware!!!
Im gonna wait to update for now, since it seems Sony's Stamina Mode still isn't on MM at the moment.