Related
So, I've read several times about how to root non-AT&T phones with the new JB OTA (3.17) already installed...phones like the Rogers HOX I purchased with the OTA pre-installed (3.17.631.2).
However, I also came across a post talking about how this method worked but when he tried to flash a different ROM his phone was bricked. (Of course I can't find this now).
So, for those of you who have tried rooting a 3.17 phone, can you please post:
(1) Whether you were successful -- I admit, I'm a bit scared, because all the phones I've previously rooted have used fancy exploits!
(2) What ROMs you have flashed successfully -- of the very few threads I've found about rooting 3.17, it seems that everyone is choosing Viper and not trying others...
(3) Whether you experienced problems with certain ROMs
(4) Whether you've downgraded the touch firmware, and whether this resolved any issues
(5) Any other advice you can give!
Please please please note that I am NOT talking about the AT&T update and I am NOT referring to the bricks people are encountering when they accept that OTA. This is about 3.17, NOT the AT&T-exclusive 3.18.
I'm hoping this info will be added to 1 of the sticky posts on this forum...because what's there is American-centric...
skittleys said:
So, I've read several times about how to root non-AT&T phones with the new JB OTA (3.17) already installed...phones like the Rogers HOX I purchased with the OTA pre-installed (3.17.631.2).
However, I also came across a post talking about how this method worked but when he tried to flash a different ROM his phone was bricked. (Of course I can't find this now).
So, for those of you who have tried rooting a 3.17 phone, can you please post:
(1) Whether you were successful -- I admit, I'm a bit scared, because all the phones I've previously rooted have used fancy exploits!
(2) What ROMs you have flashed successfully -- of the very few threads I've found about rooting 3.17, it seems that everyone is choosing Viper and not trying others...
(3) Whether you experienced problems with certain ROMs
(4) Whether you've downgraded the touch firmware, and whether this resolved any issues
(5) Any other advice you can give!
Please please please note that I am NOT talking about the AT&T update and I am NOT referring to the bricks people are encountering when they accept that OTA. This is about 3.17, NOT the AT&T-exclusive 3.18.
I'm hoping this info will be added to 1 of the sticky posts on this forum...because what's there is American-centric...
Click to expand...
Click to collapse
You can just unlock the bootloader from HTC Dev. I think, and I could be wrong, that only AT&T isn't allowing bootloader unlock. I know for a fact Rogers and Telus can just unlock through HTC DEV and once bootloader is unlocked you can flash TWRP.
If someone bricked flashing a rom, it was not designed for his/her phone. Probably for the international one X which is oh so common.
Since you have 3.17, you would need to downgrade your Touchscreen Firmware in order to use AOSP roms but sense roms will work fine. To downgrade your touchscreen firmware you would first need S-OFF but as SuperCID works only on AT&T phones with certain firmwares you would need to manually change your CID to 11111111
HTC Dev, supercid, soff, downgrade firmware.
Then flash anything.
I know what the procedure is, I'm just a bit worried about what could happen after because of that 1 post that I read.
exad, I wondered if it that ROM was designed for the wrong phone, but confirmed that it wasn't. I do suspect that it was because of the touch firmware, but again, I've never actually seen anyone say that they've rooted from 3.17 and installed a ROM other than Viper...hence my worry...because I prefer ROMs that aren't based on Sense.
I see that you're both outside the USA. Did you root the 3.17 version, or did you do it earlier and never installed the OTA?
skittleys said:
I know what the procedure is, I'm just a bit worried about what could happen after because of that 1 post that I read.
exad, I wondered if it that ROM was designed for the wrong phone, but confirmed that it wasn't. I do suspect that it was because of the touch firmware, but again, I've never actually seen anyone say that they've rooted from 3.17 and installed a ROM other than Viper...hence my worry...because I prefer ROMs that aren't based on Sense.
I see that you're both outside the USA. Did you root the 3.17 version, or did you do it earlier and never installed the OTA?
Click to expand...
Click to collapse
Outside the USA you don't need super cid you can HTC DEV unlock so it's not the same. We can root any firmware.
You can't brick flashing a rom unless you're flashing a rom for the wrong phone, aosp roms won't work with the touchscreen update you'd need to downgrade it. If you're not an idiot, you won't brick.
I really don't understand your fear.. Viper is just fast, smooth and customizable. you'll be fine running other roms except AOSP until you downgrade the touchscreen firmware.
I feel like this thread is going around in circles.
If you have a rogers HOX, htc dev unlock and flash twrp. It's crazy simple.
I can't read.
Dacra said:
I can't read.
Click to expand...
Click to collapse
You and me both buddy, and I've been here for 4 years. Ugh!
Sent from my HTC One X
exad said:
I feel like this thread is going around in circles.
Click to expand...
Click to collapse
Yes, I feel like it's going around in circles too. Of course, that could be because you aren't addressing the questions I actually asked!
I know the procedure, I know what the limitation is in the US, I know about flashing ROMs and making sure they're for your specific phone before doing so. Like I already said, I'm not at all new to Android hacking. What I don't know is whether anyone has successfully rooted and flashed a ROM starting from a 3.1x OTA and its accompanying changes like the new bootloader. After all, we don't really know what changes HTC's made. For all we know, installing a ROM not based on 3.xx (like an AOSP-based ROM) causes issues beyond the touchscreen problem. These worries are compounded by the fact that the only post I've seen where someone tried to flash an AOSP-based ROM was a failure. I've yet to see someone say they've had success, which is why I started this thread in the first place. Because while I do assume that someone in this large user base has done it, in my line of business, acting on assumptions in the absence of even some weak evidence for that assumption and where there's documentation to suggest otherwise gets you fired, sued, and stripped of your licence.
So, let me ask my main question yet again—in fact, the ONLY question I asked in my last post—and hopefully it's clear this time:
Have you or anyone else rooted your HOX for the first time starting from an official HTC 3.17 ROM with its accompanying changes in the bootloader etc. and been successful? And if so, were you or that person able to successfully flash and use an AOSP-based ROM?
Sent from my HTC One X using xda app-developers app
I did. I have a Telus HOXL that was on the OTA Jellybean.
I SIM unlocked the phone (unnecessary but I wanted to use it on Bell). Then I HTCdev unlocked the bootloader. Flashed TWRP, rooted, SuperCID'd then s-off'ed. Finally I downgraded my touchpanel firmware.
However, I haven't installed an AOSP ROM yet since ViperXL has been working so great.
skittleys said:
Yes, I feel like it's going around in circles too. Of course, that could be because you aren't addressing the questions I actually asked!
I know the procedure, I know what the limitation is in the US, I know about flashing ROMs and making sure they're for your specific phone before doing so. Like I already said, I'm not at all new to Android hacking. What I don't know is whether anyone has successfully rooted and flashed a ROM starting from a 3.1x OTA and its accompanying changes like the new bootloader. After all, we don't really know what changes HTC's made. For all we know, installing a ROM not based on 3.xx (like an AOSP-based ROM) causes issues beyond the touchscreen problem. These worries are compounded by the fact that the only post I've seen where someone tried to flash an AOSP-based ROM was a failure. I've yet to see someone say they've had success, which is why I started this thread in the first place. Because while I do assume that someone in this large user base has done it, in my line of business, acting on assumptions in the absence of even some weak evidence for that assumption and where there's documentation to suggest otherwise gets you fired, sued, and stripped of your licence.
So, let me ask my main question yet again—in fact, the ONLY question I asked in my last post—and hopefully it's clear this time:
Have you or anyone else rooted your HOX for the first time starting from an official HTC 3.17 ROM with its accompanying changes in the bootloader etc. and been successful? And if so, were you or that person able to successfully flash and use an AOSP-based ROM?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
There's no limitations with non-aT&T one x. They allow you to unlock bootlader regardless of software. You need to S-OFF after and then downgrade Touchscreen Firmware to run AOSP, there won't be any issues running AOSP.
These questions could have been easily answered with just a little bit of research on your part.
Okay, installed LiquidSmooth and it's working so AOSP ROM's are fine.
Sent from my HTC One X using xda app-developers app
ChronoReverse said:
I did. I have a Telus HOXL that was on the OTA Jellybean.
I SIM unlocked the phone (unnecessary but I wanted to use it on Bell). Then I HTCdev unlocked the bootloader. Flashed TWRP, rooted, SuperCID'd then s-off'ed. Finally I downgraded my touchpanel firmware.
However, I haven't installed an AOSP ROM yet since ViperXL has been working so great.
.....................
Okay, installed LiquidSmooth and it's working so AOSP ROM's are fine.
Click to expand...
Click to collapse
Thanks, ChronoReverse!
exad said:
There's no limitations with non-aT&T one x. They allow you to unlock bootlader regardless of software. You need to S-OFF after and then downgrade Touchscreen Firmware to run AOSP, there won't be any issues running AOSP.
These questions could have been easily answered with just a little bit of research on your part.
Click to expand...
Click to collapse
Again, you're telling me things I already know and completely ignoring the questions I actually asked and the points I already made.
I know you can unlock the bootloader regardless of the current ROM...that doesn't necessarily mean that you can then go and flash any ROM designed for this phone but developed with different bootloaders and expect it to work. Plus, the bootloader was just one example of the many changes.
As I've said in each and every one of my posts, I already know the procedure, including for downgrading the firmware. Saying "there won't be any issues running AOSP" is a very bold statement, considering that I've yet to find evidence of anyone having actually done that (until this thread, that is). Again, theoretical vs. actual experience is a huge distinction.
And no, the questions I have asked aren't easily answered with a little research, since I did a LOT of research and found nothing. Something I have reiterated numerous times. The non-existent questions you are answering can be found with a tiny bit of research, and I already found them, which is why I didn't ask them in the first place.
How bout you unlock your bootloader and flash whatever rom you want?
skittleys said:
Thanks, ChronoReverse!
Again, you're telling me things I already know and completely ignoring the questions I actually asked and the points I already made.
I know you can unlock the bootloader regardless of the current ROM...that doesn't necessarily mean that you can then go and flash any ROM designed for this phone but developed with different bootloaders and expect it to work. Plus, the bootloader was just one example of the many changes.
As I've said in each and every one of my posts, I already know the procedure, including for downgrading the firmware. Saying "there won't be any issues running AOSP" is a very bold statement, considering that I've yet to find evidence of anyone having actually done that (until this thread, that is). Again, theoretical vs. actual experience is a huge distinction.
And no, the questions I have asked aren't easily answered with a little research, since I did a LOT of research and found nothing. Something I have reiterated numerous times. The non-existent questions you are answering can be found with a tiny bit of research, and I already found them, which is why I didn't ask them in the first place.
Click to expand...
Click to collapse
Don't be a ****. I answered your question. You're just not understanding.
S-OFF UPGRADE TO LATEST SOFTWARE, DOWNGRADE TOUCHSCREEN. RUN WHATEVER ROM YOU WANT WITH NO ISSUES. AOSP, SENSE, SENSE BASED SENSELESS. WHATEVER YOU WANT, NO INCOMPATIBILITIES. FFS.
You're assuming there are meaningful hardware differences in this phone across carriers. In fact, there are not.
People have successfully run 3.17 based roms on 3.18 carrier phones and vice versa. The differences are minor and superficial and pertain entirely to carrier branding. The 2.14 hboot is the same across all carriers.
I understand your concern, but you're trying to create an issue where none exists.
Not trying for a useless post but damn pointless topic...
Sent from my HTC One XL using xda app-developers app
Well that wasted about eight minutes and I am still confused.
Sent from my HTC One X using xda premium
iElvis said:
You're assuming there are meaningful hardware differences in this phone across carriers. In fact, there are not.
People have successfully run 3.17 based roms on 3.18 carrier phones and vice versa. The differences are minor and superficial and pertain entirely to carrier branding. The 2.14 hboot is the same across all carriers.
I understand your concern, but you're trying to create an issue where none exists.
Click to expand...
Click to collapse
I know that. That's not what I was worried about. When I mentioned 3.18 in my first post, it was only to make it clear that I wasn't yet another AT&T user who'd just flashed the OTA. What I was worried about was ROMs that were developed using the older hboots...and I wasn't so much worried about the bootloader being different in the first place, it was just an example of the changes that occurred with the OTA that won't simply be overridden with a factory reset/rooting/flashing a new ROM/whatever.
exad said:
Don't be a ****. I answered your question. You're just not understanding.
S-OFF UPGRADE TO LATEST SOFTWARE, DOWNGRADE TOUCHSCREEN. RUN WHATEVER ROM YOU WANT WITH NO ISSUES. AOSP, SENSE, SENSE BASED SENSELESS. WHATEVER YOU WANT, NO INCOMPATIBILITIES. FFS.
Click to expand...
Click to collapse
31ken31 said:
Not trying for a useless post but damn pointless topic...
Click to expand...
Click to collapse
Venomtester said:
Well that wasted about eight minutes and I am still confused.
Click to expand...
Click to collapse
You know, you guys are being awfully mean to someone who just wanted a straightforward answer to something she couldn't find the answer to. Outside of this thread, I challenge you to search for and find a post wherein someone's even implied that they upgraded to the 3.xx RUU, fully unlocked/rooted their phone, and flashed a non-Sense-based ROM. Don't just go clicking to a post you already know exists. Search for it. You'll find that search is fruitless. In fact, until this thread a couple of weeks ago, there was no such thread even for Sense-based ROMs. And finally, there was the aforementioned post I found from someone who'd successfully rooted and installed ViperXL but bricked his phone when flashing an AOSP-based ROM. With all that in mind, can you understand my lack of confidence? Can you understand why I started this thread instead of just going ahead with it? And then can you maybe stop criticizing someone who actually bothered to research her issue before posting and discovered nothing but a lack of information?
Your question was answered in the first response but you dragged it out saying that it wasn't. I spend day and night on the forum giving free help, by choice, mind you, the least you could do is read and take the advice that is given, instead of wasting everyone's time with sillyness and appreciate the time that people spend answering your questions.
This forum is not intended for people who don't understand what they are doing. Devs are doing this stuff for themselves, not you, they choose to share it with you and if you are not familiar with this kind of thing or are weary of risk. DONT ROOT YOUR PHONE.
Sent from my One X using xda app-developers app
Greetings....
Assembling a list of all RUU/firmware threads so that users no longer have to dig to find what's needed. Support for each will be found in the linked thread itself while general questions like "which one is applicable to my situation?" can be handled in this thread.
If you are S-ON
Your options are somewhat limited.. naturally.
RUU (4.4.2, 4.4.3, 4.4.4, 5.0.1, 6.0) in EXE/ZIP format
- http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
If you are S-OFF
RUU 6.0 zip thread
- http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
RUU 5.0.1 (comes pre-rooted (EXE/zip support)
- http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
RUU 4.4.4 (comes pre-rooted) (EXE/zip support)
- http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914
RUU 4.4.3 (comes pre-rooted) (zip support)
- http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
RUU 4.4.2 (comes pre-rooted) (zip support)
- http://forum.xda-developers.com/showthread.php?t=2727831
Firmware only
4.4.3/4.4.4/5.0.1 Stock Recoveries, Stock kernels (boot), Stock ADSP, and many more....
- http://forum.xda-developers.com/showthread.php?t=2723159
4.4.2/4.4.3/4.4.4 Radios
- http://forum.xda-developers.com/verizon-htc-one-m8/development/radios-0-89-20-0222-t2824882
Note.... If you are needing to go back to locked and S-on for warranty purposes but are too leery to do it yourself, help is available via pm. Don't let your s/lock status from getting proper hardware RMA'S!
If you have bricked one beyond fixing and can't get it replaced, please consider donating it rather than throwing it in a desk drawer, shooting it, or whatever other crazy idea comes to mind. I can almost always put a bricked phone to good use.
Anyone who would like to use fastboot/adb for this device please use the following version fastboot/adb. It's HTC's own version. It works on pc's with less ram and it automatically breaks up a single zip into pieces for transfer. It also reflashes automatically if needed.
USE IT!
https://www.androidfilehost.com/?fid=95784891001612150
https://www.androidfilehost.com/?fid=95784891001612150
Looks good bro.
Great job!
Sweet! Thanks bro =]
Nice! I admit that the firmware was confusing for me on this phone, but thanks to dottat's posts, I figured it out.
This clears things up a lot and should help quite a few people.
Thanks!
xdadevnube said:
Nice! I admit that the firmware was confusing for me on this phone, but thanks to dottat's posts, I figured it out.
This clears things up a lot and should help quite a few people.
Thanks!
Click to expand...
Click to collapse
What was so confusing?
You are the MAN dottat!! Thanks!
Tigerstown said:
What was so confusing?
Click to expand...
Click to collapse
I managed to figure out the firmware largely due to dottat. There were multiple threads of various age, some with seemingly conflicting advice. This goes for most device forums I follow. There was no authoritative resource, IMO, until this thread.
The search feature was key, I am pretty thorough before embarking in firmware upgrades.
xdadevnube said:
I managed to figure out the firmware largely due to dottat. There were multiple threads of various age, some with seemingly conflicting advice. This goes for most device forums I follow. There was no authoritative resource, IMO, until this thread.
The search feature was key, I am pretty thorough before embarking in firmware upgrades.
Click to expand...
Click to collapse
@xdadevnube what could I do better in my OP of Vzw m8 firmware thread? I would like your input if you have ideas that would help make it easier for new comers to Xda? I would gladly make positive changes to my op to make it a easier an smoother experience. So feel free to tell me your ideas you/anyone might have that would help everyone..thanks I appreciate it.
Tigerstown said:
@xdadevnube what could I do better in my OP of Vzw m8 firmware thread? I would like your input if you have ideas that would help make it easier for new comers to Xda? I would gladly make positive changes to my op to make it a easier an smoother experience. So feel free to tell me your ideas you/anyone might have that would help everyone..thanks I appreciate it.
Click to expand...
Click to collapse
Your OP does contain the required information and instructions, so I can't really complain. One thing that could be helpful is to list the bootloader version info for each firmware release. You listed the most recent one right at the top of the thread, so at least it is easy to tell whether a given device is on the latest firmware or not. Because your thread is the main firmware thread, perhaps it would be best if the OP were organized into sections for 4.4.2, 4.4.3, and 4.4.4. It could be clarified which partitions are modified in the process, and whether the radios are affected. Install instructions could be put in their own spot.
These are only ideas! Also, your thread should probably be stickied. Thanks for all you do.
xdadevnube said:
Your OP does contain the required information and instructions, so I can't really complain. One thing that could be helpful is to list the bootloader version info for each firmware release. You listed the most recent one right at the top of the thread, so at least it is easy to tell whether a given device is on the latest firmware or not. Because your thread is the main firmware thread, perhaps it would be best if the OP were organized into sections for 4.4.2, 4.4.3, and 4.4.4. It could be clarified which partitions are modified in the process, and whether the radios are affected. Install instructions could be put in their own spot.
These are only ideas! Also, your thread should probably be stickied. Thanks for all you do.
Click to expand...
Click to collapse
hey whats up. I have made major changes to my firmware thread will you go check it out an let em know if i made it user friendly :highfive:
Firmware flash
Hello everyone. I am new to this Forum. I've only been here a few days. I have an Unlocked/S-Off Verizon HTC One M8 that I recently purchased from Ebay. I had a little trouble for a while when I first got it as it was running 4.4.2 and I took the OTA update to 4.4.3 and it messed up the phone. I didn't know it was Unlocked/S-Off'd. And the seller said it wasn't rooted any more. Well so now that I know it is even after running the Verizon RUU, I was wondering if I need to upgrade the firmware one upgrade at a time (meaning 4.4.3 and then 4.4.4)? Or can I jump to a 5.01 Lollipop ROM? I have TWRP installed and I used Flashify to install it. I'm hoping to use Flashify more for installing zips. Any help/suggestions would be greatly appreciated. Thank you....oh and I'm loving this M8!!!!
Tigerstown said:
hey whats up. I have made major changes to my firmware thread will you go check it out an let em know if i made it user friendly :highfive:
Click to expand...
Click to collapse
Looks good to me.
den_hart said:
Hello everyone. I am new to this Forum. I've only been here a few days. I have an Unlocked/S-Off Verizon HTC One M8 that I recently purchased from Ebay. I had a little trouble for a while when I first got it as it was running 4.4.2 and I took the OTA update to 4.4.3 and it messed up the phone. I didn't know it was Unlocked/S-Off'd. And the seller said it wasn't rooted any more. Well so now that I know it is even after running the Verizon RUU, I was wondering if I need to upgrade the firmware one upgrade at a time (meaning 4.4.3 and then 4.4.4)? Or can I jump to a 5.01 Lollipop ROM? I have TWRP installed and I used Flashify to install it. I'm hoping to use Flashify more for installing zips. Any help/suggestions would be greatly appreciated. Thank you....oh and I'm loving this M8!!!!
Click to expand...
Click to collapse
Rom and firmware are to separate things. You can flash straight to 4.4.4 firmware and then flash a lollipop Rom or any custom Rom.
Sent from my HTC6525LVW using Tapatalk
Firmware Updates
dottat said:
Rom and firmware are to separate things. You can flash straight to 4.4.4 firmware and then flash a lollipop Rom or any custom Rom.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Hello dottat. Thank you for replying to my question(s). Yes I know that a ROM is different than firmware. I was just wondering if I had to upgrade my firmware one update at a time or if I could just jump from 4.4.2 to say 5.0 or 5.01 so that if I wanted to I could put a custom ROM on my M8. I'm not actually sure how high the firmware upgrades go. I've only seen 4.4.4 as the highest so far.
den_hart said:
Hello dottat. Thank you for replying to my question(s). Yes I know that a ROM is different than firmware. I was just wondering if I had to upgrade my firmware one update at a time or if I could just jump from 4.4.2 to say 5.0 or 5.01 so that if I wanted to I could put a custom ROM on my M8. I'm not actually sure how high the firmware upgrades go. I've only seen 4.4.4 as the highest so far.
Click to expand...
Click to collapse
You can go straight to 4.4.4 and get crack flashing. No L firmware yet as we don't have L official.
Sent from my HTC6525LVW using Tapatalk
update process on factory unlocked VZW M8 used with GSM
Hi!
I am getting a verizon factory unlocked model and i am going to use it on a GSM network in india.Since its factory unlocked there should be no issues with the network. .however i had some doubts about the software updates. .so will i be able to receive and install updates normally without resorting to rooting the phone. .some people reported that they had an issue installing the update where it said that they have to be on CDMA or something like that. .Will i be able to overcome such issues by connecting to wifi?Is someone could shed a little light on how the update process works when used abroad with a GSM carrier it would be great!Thank you so much in advance!
balag59 said:
Hi!
I am getting a verizon factory unlocked model and i am going to use it on a GSM network in india.Since its factory unlocked there should be no issues with the network. .however i had some doubts about the software updates. .so will i be able to receive and install updates normally without resorting to rooting the phone. .some people reported that they had an issue installing the update where it said that they have to be on CDMA or something like that. .Will i be able to overcome such issues by connecting to wifi?Is someone could shed a little light on how the update process works when used abroad with a GSM carrier it would be great!Thank you so much in advance!
Click to expand...
Click to collapse
You will always be able to install the s-on ruu from here. The problem is that the latter versions of software while sim unlocked have proven very difficult to use on some carriers because you can no longer edit apn. You have to chose from pre-provided apn and thats only if they show up with your SIM card inserted.
You would be really wise to s-off the phone even if you don't root it as this would be the only way to downgrade if you ended up not having a workable situation on the newer software.
My at&t phone was unlocked and rooted when I got it, but it was lacking the last 6 updates, including lollipop, so I unrooted it to bring it up to date (5.0.1). Now I want to root it again, but haven't found any viable way to do it so far.
I tried Framaroot Plus, but that was a bust, and I had to uninstall it or my phone would personally take me out!!
I have read about people going back to KitKat, and I'm beginning to think I may do that, providing I can find out how, or perhaps someone out there knows how to root this phone and can show me?? ~Thanks
Maury000 said:
My at&t phone was unlocked and rooted when I got it, but it was lacking the last 6 updates, including lollipop, so I unrooted it to bring it up to date (5.0.1). Now I want to root it again, but haven't found any viable way to do it so far.
I tried Framaroot Plus, but that was a bust, and I had to uninstall it or my phone would personally take me out!!
I have read about people going back to KitKat, and I'm beginning to think I may do that, providing I can find out how, or perhaps someone out there knows how to root this phone and can show me?? ~Thanks
Click to expand...
Click to collapse
Go to GalaxyS4Root.com, Zedomax has the rooting methods for all the S4 models and all the builds they come with, if you don't see a method for yours then there probably isn't one.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Go to GalaxyS4Root.com, Zedomax has the rooting methods for all the S4 models and all the builds they come with, if you don't see a method for yours then there probably isn't one.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reference. Zedomax shows many ways to root the S4 back from 2013 and 2014, but I couldn't find one that would root the SGH-i337 5.0.1. BTW, I suppose I should have mentioned that I have a MAC. I've posted my question on his website. Meanwhile, is there anyone else out there who might be able to help?
Maury000 said:
Thanks for the reference. Zedomax shows many ways to root the S4 back from 2013 and 2014, but I couldn't find one that would root the SGH-i337 5.0.1. BTW, I suppose I should have mentioned that I have a MAC. I've posted my question on his website. Meanwhile, is there anyone else out there who might be able to help?
Click to expand...
Click to collapse
I've looked this up before for other members but I don't recall finding anything that will root the 5.0.1 build for your model. You can look into whether or not your device is safe to downgrade to older stock firmware(one that is root able) and then root.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I've looked this up before for other members but I don't recall finding anything that will root the 5.0.1 build for your model. You can look into whether or not your device is safe to downgrade to older stock firmware(one that is root able) and then root.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks again. That settles it; I'll downgrade. The only thing is that I have no idea how to find out whether my device is safe to downgrade to older stock firmware that is root able, Can you point me in the right direction?
Maury000 said:
Thanks again. That settles it; I'll downgrade. The only thing is that I have no idea how to find out whether my device is safe to downgrade to older stock firmware that is root able, Can you point me in the right direction?
Click to expand...
Click to collapse
You would need to go to the i337 forum here at XDA and ask other members that have your device, if anyone can tell you, you'll find it there.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
You would need to go to the i337 forum here at XDA and ask other members that have your device, if anyone can tell you, you'll find it there.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Finding my way around on this website is usually laborious and confusing. I did find out about "J0din3" for mac, but that was a bust and a great waste of time, because it's too old and now it's undownloadable. So I tried the latest Wine Bottler; it works with el Capitan OSX (what I'm using on the mac) and was able to get Odin to work. However, it's not recognizing my phone, otherwise, I'd be done by now. Have you ever worked with Wine? Can you tell me how I can get the Odin to recognize my phone? Did I do something out of sequence?
And a separate question for xda-dev at large: Why doesn't xda-dev eliminate all the outdated, old, and useless information that rattles around here like satellite debris and gets a lot of people off on the wrong foot?!
Maury000 said:
Finding my way around on this website is usually laborious and confusing. I did find out about "J0din3" for mac, but that was a bust and a great waste of time, because it's too old and now it's undownloadable. So I tried the latest Wine Bottler; it works with el Capitan OSX (what I'm using on the mac) and was able to get Odin to work. However, it's not recognizing my phone, otherwise, I'd be done by now. Have you ever worked with Wine? Can you tell me how I can get the Odin to recognize my phone? Did I do something out of sequence?
And a separate question for xda-dev at large: Why doesn't xda-dev eliminate all the outdated, old, and useless information that rattles around here like satellite debris and gets a lot of people off on the wrong foot?!
Click to expand...
Click to collapse
Sorry, I won't be of any help with Mac and my knowledge of linux is less than rudimentary, never used Wine, I use windows when windows apps are needed.
The old stuff still has useful info that still applies I guess, I've never checked XDA-Dev out, I'm not that deep in it yet. I'm working in other areas. Try posting your issues with getting recognized in this link:
http://forum.xda-developers.com/android/help
This is more just a general question of your opinion. I can't believe it's been almost a year and no bootloader unlock. I would have loved to see CM running on this device. It almost makes me want to go back to HTC because they openly allow the bootloader to be unlocked. IMO I think we have reached as best as we can with the echo ROM. I uninstalled it due to it not having much benefits. What are your thoughts on this device? Do you think we will ever see a bootloader unlock or is devolopment dead on this device?
I believe that development might pick up again with nougat's official January (i believe) release because it offers much more than Marshmallow. Maybe we'll get an official bootloader unlock or some dev on his spare time finds a way to do it. CM either way is only being made personally through devs now (closed its doors yesterday) but there will be a forthcoming with LineageOS from the same team.
Yeah I read about cm and lineage. So if I'm understanding. An OS update could provide a new vulnerability and allow an unlocked bootloader?
Keyword there is could. Hopefully some progress down the line would be nice and if we got to start a prize pot for it, I wouldn't mind.
I would definitely kick in some money to a bootloader unlock bounty. Right now my only 2 complaints with the s7 are lack of custom roms and not being able to find a good full coverage glass screen protector. If I can help one of those I will. I am half tempted to sell my tmo s7 and buy an exynos s7 because there seems to be more development there. But I'll wait for nougat.
jah feel
I feel your pain. When I first planned on getting the S7, I was excited about getting a sexy-design phone with better specs and putting all my music on the phone via a 128GB SD card and chilling out with ViPER4Android... but that was all a dream. I've been very hesitant to go through with the current root method because from what I've read, there are tons of bugs to deal with and tons of tweaks to do to not get very far in the end. I'm honestly very sad about this purchase. If I had more time to research the locked bootloader issue, I would have gone with a different phone. But my S5 finally gave up and I had to get a new phone ASAP. I would also pitch in for a bootloader unlock or something. I mainly want a stable phone with ViPER4Android. Can't live without it... it's been hell. Halp pl0x.
I would definetely pay for an unlocked bootloader also. The exynos definitely seems to have more devolpment than the u.s. But I'm rooted and after flashing a fix+debloat and installing Xposed everything is running smooth. It would be awesome to see more devolepment though.
sparky2029 said:
I would definetely pay for an unlocked bootloader also. The exynos definitely seems to have more devolpment than the u.s. But I'm rooted and after flashing a fix+debloat and installing Xposed everything is running smooth. It would be awesome to see more devolepment though.
Click to expand...
Click to collapse
Can you link me to the posts about the fix+debloat you flashed please? I have tried rooting and couldn't figure out how to fix the super slowness and the overheating. Also, what Firmware are you running?
r3xx3r said:
Can you link me to the posts about the fix+debloat you flashed please? I have tried rooting and couldn't figure out how to fix the super slowness and the overheating. Also, what Firmware are you running?
Click to expand...
Click to collapse
Sure thing buddy here you go https://forum.xda-developers.com/tmobile-galaxy-s7/help/development-dead-t3530239#post70398278
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
r3xx3r said:
Can you link me to the posts about the fix+debloat you flashed please? I have tried rooting and couldn't figure out how to fix the super slowness and the overheating. Also, what Firmware are you running?
Click to expand...
Click to collapse
Sorry I put the wrong link twice.. Heres the right one https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
It's under recommended next steps for the flash fix
Hi all,
I have found this simple guide to unlock the bootloader on LG V20 H910 have someone tried it then installed lineage OS 17.1 after please ? :
https://www.hardreset.info/devices/lg/lg-v20-at-and-t-h910/faq/faq/lg-bootloader-unlock/
Thanks a lot for your replies.
Sofiene.Saidi said:
Hi all,
I have found this simple guide to unlock the bootloader on LG V20 H910 have someone tried it then installed lineage OS 17.1 after please ? :
https://www.hardreset.info/devices/lg/lg-v20-at-and-t-h910/faq/faq/lg-bootloader-unlock/
Thanks a lot for your replies.
Click to expand...
Click to collapse
That guide is bs
Sent from my LG-H910 using XDA Labs
cnjax said:
That guide is bs
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Can you tell me how please ? This video from 2016 confirm it too :
https://www.youtube.com/watch?v=M-71Z-C4nAA
Yes it was a BS since no bootloader mode in this device so please dirty santa is the unique way ? Please notice I am on oreo so if you have a link to a complete guide please do not hesitate
Sofiene.Saidi said:
Yes it was a BS since no bootloader mode in this device so please dirty santa is the unique way ? Please notice I am on oreo so if you have a link to a complete guide please do not hesitate
Click to expand...
Click to collapse
This is not the right place to ask for help with this... Check out the "guide" section... And ask questions In " Questions & Answers" section.
I think this is best method:
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
Others use h915 kdz.
Please refrain from posting on this thread again. It will make me regret helping.
Don't forget to thank people who help you in the thread with thanks button. Specially if the guide they made helps a ton. Note this will get rid of at&t software. I think there is way too restore it still but I have not checked for a while.
this is helpful
Sent from my SM-N9600 using Tapatalk
Is there any current way to unlock the bootloader on the LG V20 H910 with AT&T's latest firmware release? AT&T has locked diown the bootloader, and with LG no longer in the cell phone game, they aren't able to provide the OEM bootloader unlock code as well. A few people have also mentioned that the Dirty Santa no longer works on these devices. Any help would be greatly appreciated.
grmoro said:
Is there any current way to unlock the bootloader on the LG V20 H910 with AT&T's latest firmware release?
Click to expand...
Click to collapse
At least did you try to follow the instructions available? According to this post from October-2022 it worked on H910 AT&T.
dextructor said:
At least did you try to follow the instructions available? According to this post from October-2022 it worked on H910 AT&T.
Click to expand...
Click to collapse
Yes. I tried it and its useless. Struggling to find a bootloader unlock process that actually works for the H910.
grmoro said:
Yes. I tried it and its useless. Struggling to find a bootloader unlock process that actually works for the H910.
Click to expand...
Click to collapse
You are looking for help, because you don't know how to solve it. So we as a community need a little bit of cooperation from everyone to be able to understand if it's a limitation/roadblock of the method, or if you are doing something wrong for whatever reason.
So posting: "don't work", "it's useless" and anything like that not only don't help but discouraging others who read this threads. Tell the problem/error that you encounter.
I found another user who said that he flashed dirtysanta directly and once have TWRP he worked around it the downgrade flashing necessary.
As last resort you can swap the motherboard for one that is vulnerable for the exploit.
But if you wanna some one-click "I don't wanna have trouble" solution, I'm sorry that I can't provide that.
dextructor said:
You are looking for help, because you don't know how to solve it. So we as a community need a little bit of cooperation from everyone to be able to understand if it's a limitation/roadblock of the method, or if you are doing something wrong for whatever reason.
So posting: "don't work", "it's useless" and anything like that not only don't help but discouraging others who read this threads. Tell the problem/error that you encounter.
I found another user who said that he flashed dirtysanta directly and once have TWRP he worked around it the downgrade flashing necessary.
As last resort you can swap the motherboard for one that is vulnerable for the exploit.
But if you wanna some one-click "I don't wanna have trouble" solution, I'm sorry that I can't provide that.
Click to expand...
Click to collapse
I have a clients device that needs to be updated, hence the search to unlock the bootloader and then update the device. The posts I come across, even new ones seem to be reposts of others work from before LG shut down their bootloader unlocking service, so ehen you follow their steps they don't work at various steps. I've been updating devices as far back as Android 1.5 and for some devices its a struggle to update them at all. Replacing the pcb isn't an option right now as the customer won't pay for it. Hence I scour various websites and forums for solutions as other post their success/failure in doing the same on this device. Too often I find people posting about updating their devices, only to find that they either already had their bootloader unlocked before LG shutdown their service to do so, or they just don;t reply to a PM about their process, hence they're fake posts, or old posts from years prior being reposted for no valid purpose. The amount of tim I spend to update peoples devices and test custom ROMs is actually fruitless in terms of money paid, but more for me to keep devices out of the landfills whenever possible. Every time I mod a device I make and keep notes, as well as the files used, stored on one of my NAS as I know I'll be doing it again in the future, including properly and fully testing custom roms to determine if they're actually working properly, or exactly what their issue(s) is(are), and I keep finding a plethora of bugs and issues with too many custom ROMs being pumped out before proper testing. I routinely turn down some device update requests when update steps are convoluted, fractured or even requirements are no longer valid. I'll keep looking around and trying various methods as I come across them. Thx.
No problems, I feel for you because I like to keep people using devices that otherwise would be discarded without real needs.
grmoro said:
I'll keep looking around and trying various methods as I come across them. Thx.
Click to expand...
Click to collapse
Did you try this other method?