Related
EDIT: Wrong category, sorry. I'm new.
Rooted Aria/Liberty won't turn on if it's plugged in (wall charger or USB). The orange charging light is on and the screen is lit but black. The menu buttons do not turn on. I have to remove the battery after unplugging it for it to turn on.
The phone is rooted and the problem is consistent no matter what ROM I use. I believe it is a problem with the bootloader, but I'm not very advanced with these things.
I rooted the phone with Unrevoked and whenever I boot into recovery mode it says "Revolutionary CWM v4.0.1.4."
Any suggestions on how to make this problem go away? I know it's minor, but it is my mother's phone and every time I'm on the phone with her she complains about it.
The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!
juzz86 said:
The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!
Click to expand...
Click to collapse
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.
ellaizee said:
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.
Click to expand...
Click to collapse
Tried this one mate?
juzz86 said:
Tried this one mate?
Click to expand...
Click to collapse
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.
ellaizee said:
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.
Click to expand...
Click to collapse
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704
glevitan said:
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704
Click to expand...
Click to collapse
You are MAGICAL. Thank you so much! And thanks to juzz86 for the suggestions as well.
I used fastboot to flash the recovery and now it does the normal battery image when the phone is off and charging.
No problem. When that happened to me, I panicked but after a couple of google searches I came across that...glad you solved it.
Sent from my Inspire 4G using XDA
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
hahaha sorry for that. As u can see, I realised after writing it and erased it, but you probably saw it first.....
ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!
juzz86 said:
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!
Click to expand...
Click to collapse
Even in UK they use mate a lot....but it is no defense for me...I am in Argentina... lol
Hi,
I followed the instructions here (http://forum.xda-developers.com/showthread.php?t=1525100) and after trying to revert back (fastboot oem lock and then flash stock ruu), I now have RELOCKED on the bootloader as opposed to LOCKED. Is there any way I can solve this (preferably without downgrading hboot)?
Thanks in advance.
No, there isn't.
you can S-OFF and then take the S-OFF and UNLOCKED tags off with this:
http://www.xda-developers.com/android/bootloader-customization-now-open-to-more-s-off-htc-devices/
tep_kubo said:
Hi,
I followed the instructions here (http://forum.xda-developers.com/showthread.php?t=1525100) and after trying to revert back (fastboot oem lock and then flash stock ruu), I now have RELOCKED on the bootloader as opposed to LOCKED. Is there any way I can solve this (preferably without downgrading hboot)?
Thanks in advance.
Click to expand...
Click to collapse
in my experience after the downgrade the banner "relocked" disappeared... but just through the downgrade..
i guess that's just what the older version bootloader looks like... i was looking for a way to do it for hboot 2.00 etc but i think the bootloader customisation is the only way...
thanks for the help guys
Jack_R1 said:
No, there isn't.
Click to expand...
Click to collapse
Jack knows. Believe it.
TatoValverde thanks a lot, the program worked a treat.
to anyone thinking of unlocking via htcdev, don't... downgrade and then flash engineered hboot.
From my experience, downgrading Hboot using the RUU can help to make it ***LOCKED*** again (which happened to me), but if you have ever used HTCDev, then although it is Locked, HTC would know that it is actually RE-LOCKED.. That's if HTC bother to dig out their database deeper during repair..
My advice: Don't use HTCDev, or if you have, don't bother about it, just enjoy your freed phone..
Wouldn't something like this work for our device as well? The partition and offset would likely differ, but I think it's doable. http://forum.xda-developers.com/showthread.php?t=1970252
jneapan said:
Wouldn't something like this work for our device as well? The partition and offset would likely differ, but I think it's doable. http://forum.xda-developers.com/showthread.php?t=1970252
Click to expand...
Click to collapse
I have checked this some time ago but unfortunately on my device (htcdev unlocked to escape a bad brick) there is no HTCL nor HTCU on any partition so they probably used another methodology on the DS
Sent from my HTC Desire S
amidabuddha said:
I have checked this some time ago but unfortunately on my device (htcdev unlocked to escape a bad brick) there is no HTCL nor HTCU on any partition so they probably used another methodology on the DS
Sent from my HTC Desire S
Click to expand...
Click to collapse
Well that's a bit disappointing, it made sense in my mind that they would use the same method on all their phones, because of convenience if nothing else.
jneapan said:
Well that's a bit disappointing, it made sense in my mind that they would use the same method on all their phones, because of convenience if nothing else.
Click to expand...
Click to collapse
I hoped they did...
Actually I have made a lot of digging in this area and for example on HTC Wildfire the Relocked/Locked state can be manipulated in the misc partition only. This differs from the guide you linked as well.
I have searched through all of the 30 partitions on my device and have found no trace of the manipulation the unlock_token did. So eventually I gave up, but if someone finds the solution I will be happy. There are still 6 months in my warranty
amidabuddha said:
I hoped they did...
Actually I have made a lot of digging in this area and for example on HTC Wildfire the Relocked/Locked state can be manipulated in the misc partition only. This differs from the guide you linked as well.
I have searched through all of the 30 partitions on my device and have found no trace of the manipulation the unlock_token did. So eventually I gave up, but if someone finds the solution I will be happy. There are still 6 months in my warranty
Click to expand...
Click to collapse
I've still got 8 months left on mine, so I'll be waiting to see if anyone else figures this out. Times like this, I regret not learning anything about this sort of development/hacking, because I'd very much like to fiddle with this myself
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Have you tried not using superwipe and using factory reset/wipe from 4ext recovery instead? Never had a problem with that.
Also I've never had to use the wire trick to have S-OFF. Gained it back when I was running GB, and still have it. Even after flashing OTA updates.
Sent from my HTC Sensation using xda developers app
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Click to expand...
Click to collapse
It has nothing todo with the capacitive buttons running hot. Have you tried a different recovery like CWM because this seems like a recovery issue. As a side note, try disabling signature verification in 4EXT or better still, attempt to flash a ROM with aroma installer in and then save the aroma log and post it here
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
From the start, performing S-OFF was tricky in itself, particularly with the paperclip trick. Miraculously, it worked after the third try. Flashing ROMs was a whole different monster. Even with 4ext, I could only flash THREE ROMs from the huge collection in the Development forum. And I honestly don't even know why--I kept on getting Error 0 for every build I tried to load. It was only through luck or magic that I was able to flash HyperNonsense, a MIUI build, and another one that I don't remember. Upgraded 4ext to latest version: nope. Changed SD card: nope. Different sequences of superwipe/no superwipe, clear dalvik, etc.: nope. I'm using HyperNonsense for now since it's pretty legit, but even then, I'm getting reboots all over the place. Stock kernel or different kernels--doesn't matter. I have a hunch it has to do with the bottom row of capacitive buttons running so hot.
Oh well, just holding out for the One X+ on T-Mobile or the next Nexus device. Just wanted to let out my despair and frustration. Thanks, guys. :good:
Long live the HD2. :silly:
Click to expand...
Click to collapse
Post combat time. *Puts on Armor*
The wire trick is only necessary if you got screwed out of every other S-OFF method. I used Revolutionary and got S-OFF the day I rooted it. As for your ROM issues, that's pretty odd and unheard of to me. Try to flash one of those error 0 ROMs and Dump your recovery.log here after the flash, I'll look at it. As for the capacitive buttons, it's not the buttons running hot, but the fact that the CPU is literally right behind it. It doesn't run hot for me unless I start a game, and even that varies by ROM. Never gets hot on CM9. HyperNonSense 3.3 always runs hot though, no matter what. hyperNonSense 2.7 was the best :/
Anyway send in the recovery log, I'll try help you with that. PM me as well because I won't remember this thread after 5 minutes.
Thanks very much for all of your replies. I think I'll start with removing 4ext and run regular CWM. How would I go about uninstalling 4ext?
Hypernonsense always reboots for me
Sent from my Sensation using xda premium
nuron said:
Thanks very much for all of your replies. I think I'll start with removing 4ext and run regular CWM. How would I go about uninstalling 4ext?
Click to expand...
Click to collapse
just flash over it. Are you sure you're doing everything right? Have the right firmware for the right roms? Sounds like you're missing something
se1000 said:
just flash over it. Are you sure you're doing everything right? Have the right firmware for the right roms? Sounds like you're missing something
Click to expand...
Click to collapse
Seems like I am. I'm S-OFFed, and before 3.33 FW was required, I wasn't on it. When the cooks started requiring it, I flashed it. How important is Super CID? Will that cause an Error 0?
nuron said:
Seems like I am. I'm S-OFFed, and before 3.33 FW was required, I wasn't on it. When the cooks started requiring it, I flashed it. How important is Super CID? Will that cause an Error 0?
Click to expand...
Click to collapse
Your problem may be that you flashed the wrong FW for your CID - that is why superCID is important because it allows you to flash any variation of the firmware you like (you will have seen there are about 10+ variations of the 3.33 firmware)
So maybe try superCID (its really easy) then reflash the radio
fredcorp6 said:
Your problem may be that you flashed the wrong FW for your CID - that is why superCID is important because it allows you to flash any variation of the firmware you like (you will have seen there are about 10+ variations of the 3.33 firmware)
So maybe try superCID (its really easy) then reflash the radio
Click to expand...
Click to collapse
Yep, this.
It takes a couple of seconds to do, and is super easy.
Like fredcorp6 said, SuperCID will allow you to flash any RUU or firmware from any region.
Sent from my CM9 Stable Sensation using XDA Premium
Alright, so I just performed Super CID and was looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1459767&highlight=3+33
I just flash 3.33 Universal?
nuron said:
Alright, so I just performed Super CID and was looking at this thread:
http://forum.xda-developers.com/showthread.php?t=1459767&highlight=3+33
I just flash 3.33 Universal?
Click to expand...
Click to collapse
I recommend 3.32 fw, flash in fastboot or bootloader can't remember which lol. I don't see any reason for 3.33 fw and 3.33 u can't do fastboot commands
Sent from my Sensation using xda app-developers app
nuron said:
Folks, I wouldn't call myself a n00b in flashing phones--I've been flashing ROMs since my HTC Wing so I feel like I have a decent amount of experience under my belt. But this Sensation...
Click to expand...
Click to collapse
Ever installed linux on a d-box2 (famous settop-box of a german pay-tv provider, anno 1999)? No? Well, shut up, with this thing you're SO happy seeing "u-boot" in the display and having it boot from your tftp server, which of course only works with a properly configured arpd and a dhcpd that speaks the ancient "bootp" ...
Haha, no offense For me, sensation was a piece of cake, didn't even need any hardware hacks, just a nice tool called "revolutionary"
Zirias said:
Ever installed linux on a d-box2 (famous settop-box of a german pay-tv provider, anno 1999)? No? Well, shut up, with this thing you're SO happy seeing "u-boot" in the display and having it boot from your tftp server, which of course only works with a properly configured arpd and a dhcpd that speaks the ancient "bootp" ...
Haha, no offense For me, sensation was a piece of cake, didn't even need any hardware hacks, just a nice tool called "revolutionary"
Click to expand...
Click to collapse
Shut up. No one cares about you. This isn't a one-up contest. With that kind of supposed knowledge, you should be helping others. But nope, you instead add nothing to the thread.
Thanks everyone for all the help so far. uml, I'll flash 3.32 and get back to you.
GazaIan said:
Post combat time. *Puts on Armor*
The wire trick is only necessary if you got screwed out of every other S-OFF method. I used Revolutionary and got S-OFF the day I rooted it. As for your ROM issues, that's pretty odd and unheard of to me. Try to flash one of those error 0 ROMs and Dump your recovery.log here after the flash, I'll look at it. As for the capacitive buttons, it's not the buttons running hot, but the fact that the CPU is literally right behind it. It doesn't run hot for me unless I start a game, and even that varies by ROM. Never gets hot on CM9. HyperNonSense 3.3 always runs hot though, no matter what. hyperNonSense 2.7 was the best :/
Anyway send in the recovery log, I'll try help you with that. PM me as well because I won't remember this thread after 5 minutes.
Click to expand...
Click to collapse
True! i never had to use paperclip to S-OFF mine. Both the official HTC method (on HTC website) AND the non-official method here on XDA worked for me to S-OFF my sensation.
I didn't mind the paperclip method too much. I think I needed to do it because my HBOOT was of a different version than the regular easy-to-root versions.
nuron said:
Just wanted to let out my despair and frustration.
Click to expand...
Click to collapse
nuron said:
Shut up. No one cares about you. This isn't a one-up contest. With that kind of supposed knowledge, you should be helping others. But nope, you instead add nothing to the thread.
Click to expand...
Click to collapse
So ... what actual "addition" were you hoping for? I don't think you'd start a thread like this if you didn't kind of enjoy the "hard way" you obviously took
btw -- whole point was to contradict your title by example, just to say: there are worse, much worse
Don't you understand that the Sensation is one of the most aggravating devices ever FOR ME?
This thread could be useful for other XDA members if they run into the same problems that I did and are searching for solutions. But instead, they have to to read through your useless posts. This clutters up the whole thread and detracts from all the members who have helped with a response and possible solution.
Leave.
nuron said:
Don't you understand that the Sensation is one of the most aggravating devices ever FOR ME?
This thread could be useful for other XDA members if they run into the same problems that I did and are searching for solutions. But instead, they have to to read through your useless posts. This clutters up the whole thread and detracts from all the members who have helped with a response and possible solution.
Leave.
Click to expand...
Click to collapse
There are a LOT of useful threads with lots of useful info here. This isn't one of them. Just re-read your original post and stop being such a moron, thanks.
wow, no ****, Sherlock. But I couldn't find an answer so that's why I created this thread. Thanks for not helping. And thanks for cluttering up this thread. Don't start calling others a moron without evaluating yourself first.
So I am a noob to HTC phones. I understand what S-Off is but I am not entirely sure what I could with my phone with it that I can't do now. I am trying to understand whether I should go through the process since there is always the risk of bricking. Thanks!
I have no idea what S-Off is :/ i need some enlightenment
Sent from my One XL using Tapatalk
S-Off is the main thing that allows u 2 root yr phone...
Sent from my GT-I9300 using xda app-developers app
a simple search on the net can tell you what it does
but it does a lot of "techie" things you're not suppose to do
mrjayviper said:
a simple search on the net can tell you what it does
but it does a lot of "techie" things you're not suppose to do
Click to expand...
Click to collapse
I did do that. It said that I could flash ROMs, Radios, stop my bootloader from saying unlocked. Most of this things with the exception of the last I can already do. I was just wondering if there is something that I could be missing out from. Thanks!
Contrary to popular belief, s-off actually has very little to do with your phone being rooted. S-OFF stands for Security-Off, which basically allows you to modify any partition on the device, and changes will not be reset upon a reboot. Also, the signature checking of the firmware zips is disabled, allowing users to flash unsigned firmware zips containing the separate images of the partitions.
Very simply put, that's what it is. There is a lot more to it that you guys can probably look up. For a user on an hboot below 1.14 it really doesn't do all that much, but it's very useful for devs and people post-hboot 1.14
I'm not totally sure what it will do for us, but it was easy enough for me to go through with it, took about 5 minutes if you've already got ADB/Fastboot set up.
I heard it could take away that stupid red paragraph when I boot and that was all I needed to hear haha
I feel like I just got a new toy but can't read the instruction manual... can I flash a new radio? do I need to do something special like flash through fastboot?
I know I sound like a broken record but
I'd love to see someone create a dual boot program for our phone.
Sent from my HTC One XL
BobbyDukes707 said:
I feel like I just got a new toy but can't read the instruction manual... can I flash a new radio? do I need to do something special like flash through fastboot?
Click to expand...
Click to collapse
You got to wait for the new tools to be released. Nothing happens automatically AFAIK.
You can flash ROMs on newer hboot without fastboot
Sent from my One X using Tapatalk 2
so how do you get rid of the red text on boot??? and also how can the unlocked/ tampered flags be reset (while staying unlocked)
31ken31 said:
so how do you get rid of the red text on boot??? and also how can the unlocked/ tampered flags be reset (while staying unlocked)
Click to expand...
Click to collapse
Things will come, just have to give the devs a chance since we just got s-off.
SouL Shadow gave an excellent response to the question here:
http://forum.xda-developers.com/showpost.php?p=38169711&postcount=2462
But as already indicated, things will come in the future, it really doesn't gain much at the moment. Especially for those still on pre-1.14 hboot (and can already flash radios, kernels from recovery).
bootloader currently showing....
Bootloader info:
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.005
RaDIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012,12:17:41
Software Number
2.35.531.12 710RD
Android
4.04
much thanks
the RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe found here is the latest one released for unbranded devices afaik.
alltho itll downgrade your radio as it seems...
Dolour said:
the RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe found here is the latest one released for unbranded devices afaik.
alltho itll downgrade your radio as it seems...
Click to expand...
Click to collapse
That one won't work. He has a T-Mobile US phone (SKU 531) and is a S-ON user. The RUU you linked is for the SKU 401. You can't change your SKU with S-ON.
@20twins10: Try this RUU. It should set your phone back to stock. You can update it afterwards to the latest version by using the OTA function in "settings>about". If the RUU doesn't work as expected you should turn off your internet connection, your firewall and you antivirus software, boot your phone to fastboot mode and try again.
Flippy498 said:
That one won't work. He has a T-Mobile US phone (SKU 531) and is a S-ON user. The RUU you linked is for the SKU 401. You can't change your SKU with S-ON.
Click to expand...
Click to collapse
well, the site linked allso contains the TMO ruus available, didnt figure from the bootloader info its a branded device.
Dolour said:
well, the site linked allso contains the TMO ruus available, didnt figure from the bootloader info its a branded device.
Click to expand...
Click to collapse
I know that. Guess where I found the TMOUS ruu.
Flippy498 said:
I know that. Guess where I found the TMOUS ruu.
Click to expand...
Click to collapse
well gj then i suppose.
a word of warning tho: updates messing with the hboot version seem to have a tendency to bork your mmcblk0p20, causing you to end up on edge only(im trying for weeks now,
to get my hands on a WORKING image for unbranded eu devices, without any luck).
so make sure to pull a backup to be able to revert!
Dolour said:
well gj then i suppose.
a word of warning tho: updates messing with the hboot version seem to have a tendency to bork your mmcblk0p20, causing you to end up on edge only(im trying for weeks now,
to get my hands on a WORKING image for unbranded eu devices, without any luck).
so make sure to pull a backup to be able to revert!
Click to expand...
Click to collapse
I actually never faced such a problem. And I upgraded and downgraded my One S's fimware a lot during the last three years. (But I think this is going too much off topic. So let's leave it at that. )
@20twins10: I just noticed that your bootloader is still locked. (I guess I have missed that info earlier.) So your phone seems to be untouched in terms of bootloader unlocking and rooting. That actually makes me wonder why you don't use the OTA function in settings>about?
Flippy498 said:
I actually never faced such a problem. And I upgraded and downgraded my One S's fimware a lot during the last three years. (But I think this is going too much off topic. So let's leave it at that. )
Click to expand...
Click to collapse
well, considering the 30+ pages long thread on this forum, regarding the issue, i wouldnt exactly call it OT, just bc youve been lucky until now.
btw, you dont, by "chance" *cough*, have one of the above mentioned mmcblk0p20's for unbranded, european devices handy(or could dd one if you find a couple minz)?
Dolour said:
well, considering the 30+ pages long thread on this forum, regarding the issue, i wouldnt exactly call it OT, just bc youve been lucky until now.
btw, you dont, by "chance" *cough*, have one of the above mentioned mmcblk0p20's for unbranded, european devices handy(or could dd one if you find a couple minz)?
Click to expand...
Click to collapse
But as far as I know the problems arose after people S-OFFed their phones and/or downgraded their hboot using a ruu. (Haven't checked that thread for over a year.) And neither of these processes has anything to do with this topic. So let's continue this discussion via PM.
Flippy498 said:
But as far as I know the problems arose after people S-OFFed their phones and/or downgraded their hboot using a ruu. (Haven't checked that thread for over a year.) And neither of these processes has anything to do with this topic. So let's continue this discussion via PM.
Click to expand...
Click to collapse
well it happened to me after doing a simple factory reset, no s-off, not even root, it definetly isnt related to hboot 2.16 or s-offing at all.
therefore i consider the suggestion of backing everything up before doing any changes to the OS pretty important, and totally on-topic.
hey guys thanks for all the responses. i need to get some time to sit and read them. i've been busy with work and school and was not able to get time back to xda till now.. just a quick update: i was able to adjust my driver files and get fastboot to recogonize my phone, i did get my bootloader unlocked and twrp flashed.. as far back as i can remember ive never used OTA's and always go about it . i guess ive always come to the conclusion an ota dl will get you on the hot list if you are out of warranty or conretact type deal..
but either way.. there is progress on my end. my wife runs a couple apps that require 5.0 or better so i'd like to get that to work for her.. she'll ***** when she needs to re-enter her pw's though.. cant wint.. much thanks..
20twins10 said:
hey guys thanks for all the responses. i need to get some time to sit and read them. i've been busy with work and school and was not able to get time back to xda till now.. just a quick update: i was able to adjust my driver files and get fastboot to recogonize my phone, i did get my bootloader unlocked and twrp flashed.. as far back as i can remember ive never used OTA's and always go about it . i guess ive always come to the conclusion an ota dl will get you on the hot list if you are out of warranty or conretact type deal..
but either way.. there is progress on my end. my wife runs a couple apps that require 5.0 or better so i'd like to get that to work for her.. she'll ***** when she needs to re-enter her pw's though.. cant wint.. much thanks..
Click to expand...
Click to collapse
I don't know what you mean with "getting on the hot list". (Sorry English isn't my mother tongue.)
Actually the unlock process and the flashing of TWRP was completely unnecessary. Before you should start flashing any custom files you need to upgrade to the latest firmware. Many of the android 5 custom roms won't work if your firmware is too old. Just flash the RUU and then install the OTAs. (Since you flashed TWRP you now must use the RUU whereas it's been optional at the point where you started this thread.)