Related
Need some help or a link to instructions on rooting this phone, This is a T-mobile no contract phone, made by ZTE Phone is running Gingerbread 2.3.7 Since this phone is new on the market is their a similar phone I can look at as an example of how to root it?
Thanks in advance
..
Okay here is what I have tried so far, Superoneclick gets to step 7 waiting on device and hangs up. Have tried the Zurg rush tool, when it attempts to do an adb remount it fails with a msg operation not permitted. So I'm stuck now, so anyone with some ideas or insight please chime in, thanks
Just another update the UniversalAdroot apk does not work, anyone with any ideas?
Still looking for help, since this phone is relatively inexpensive, there is going to be a lot of them out there. And a lot of people looking to root them. Just hoping someone will give me assistance as this will also be solution for others as well.
cnjax said:
Still looking for help, since this phone is relatively inexpensive, there is going to be a lot of them out there. And a lot of people looking to root them. Just hoping someone will give me assistance as this will also be solution for others as well.
Click to expand...
Click to collapse
Well at least your thread pulls up when running a Google search for rooting this phone. Did you try the CyanogenMod instructions for the ZTE Blade? Thats the only other suggestion I have since I don't own one yet.
Post back here if you have any luck. I might just get one as a spare.
FireRaider said:
Well at least your thread pulls up when running a Google search for rooting this phone. Did you try the CyanogenMod instructions for the ZTE Blade? Thats the only other suggestion I have since I don't own one yet.
Post back here if you have any luck. I might just get one as a spare.
Click to expand...
Click to collapse
will give that a try and will post back with the results
FireRaider said:
Well at least your thread pulls up when running a Google search for rooting this phone. Did you try the CyanogenMod instructions for the ZTE Blade? Thats the only other suggestion I have since I don't own one yet.
Post back here if you have any luck. I might just get one as a spare.
Click to expand...
Click to collapse
Question the cyanogenmod instructions say to use terminal on your computer is this the same as using cmd.exe?
cnjax said:
Question the cyanogenmod instructions say to use terminal on your computer is this the same as using cmd.exe?
Click to expand...
Click to collapse
Yes. Please refrain from continuing to bump your own thread. Thanks.
TeeJay3800 said:
Yes. Please refrain from continuing to bump your own thread. Thanks.
Click to expand...
Click to collapse
I apologize was just trying to get some help and sis not know what the wiki was referring to Terminal as I could not find it in win 7
Just an update to save peeps time the CyanogenMod root for the ZTE Blade does not work on this phone.
Hi
So far, anyone found a way to root the ZTE V768 (Concord) ?
Anyway to upgrade to 3.0?
Thanks
Michel
I too would like to see this rooted. Then maybe I can delete some of those factory installed apps I would never use.
ZTE lists a way to manually upgrade the firmware for a Concord (V768) with a PC running Windows. Maybe it can be used somehow to root this device?
I can't post the link because I'm a new user, but just search for the Concord on the ZTE USA website.
ryanflucas said:
I too would like to see this rooted. Then maybe I can delete some of those factory installed apps I would never use.
ZTE lists a way to manually upgrade the firmware for a Concord (V768) with a PC running Windows. Maybe it can be used somehow to root this device?
I can't post the link because I'm a new user, but just search for the Concord on the ZTE USA website.
Click to expand...
Click to collapse
I got the link you're referring to
http://www.zteusa.com/device/201207/t20120728_13066.html
Click to expand...
Click to collapse
, but this does not look like a OS upgrade, only a PC Driver update
I will try it and see if it affects the phone.
I have asked T-mobile to get the Concord unlocked, they couldn't but required an answer from ZTE directly...I should get something next week only!
So did anyone figure out how to get this phone unlocked?
BTW I'm surprised how little support there is for this phone considering it's the cheapest tmobile android option by far.
ROOTED!!
For those looking to root their ZTE Concord I have successfully rooted it using the ZTE Score option! Working on installing the Clockwork mod now and I think I'm going to tinker with the JellyBlast ROM for the Galaxy Y considering these phones are fairly similar
nvm on last post its installed su but did not install the binaries
manny2709 said:
nvm on last post its installed su but did not install the binaries
Click to expand...
Click to collapse
Ah dang, I thought someone had figured it out! Any more luck? I'm going to be getting a hold of one of these soon and I'd really like to know what kind of options there are for rooting.
sagef0ur said:
Ah dang, I thought someone had figured it out! Any more luck? I'm going to be getting a hold of one of these soon and I'd really like to know what kind of options there are for rooting.
Click to expand...
Click to collapse
Yeah im sorry i thought i got it too! But the system is read write protected and its a pain in the a$$. I figured out how to get it in Stock Recovery and tired installing JellyBlast via update.zip but didnt work cause it requires root and CWM go figure huh? SOMEONE HELP US!
Alright I tried rooting with update.zip for the Galaxy Pocket considering these phones have similar hardware but still no go! :crying: Has anyone had any luck?
Hello everyone, I currently have AT&T HTC M8,
I recently came across this issue after I installed an Android M rom (SkyDragon, CM13 etc), I wasn't able to receive any incoming calls, they were all redirected to voicemail, I tried to change roms, change different settings, nothing worked.
Finally I searched for Android M's firmware and came across 6.12.1540.4, just search for it and flash it in fastboot.
Once you'll flash that firmware, do a clean install of TWRP recovery & ROM of your choice, it should work with all Marshmallow roms.
Not sure if it'll work if you'll restore it back to Android L (may get stuck in boot-loop or something, not sure).
I'm not taking responsibility if anything happens to your device, if you have any questions, feel free to write & I'll try my best to answer.
Thanks.
I think what you experienced is a kernel problem and not a firmware problem.
And even so, not everybody can do this as you need S-OFF.
Mr Hofs said:
I think what you experienced is a kernel problem and not a firmware problem.
And even so, not everybody can do this as you need S-OFF.
Click to expand...
Click to collapse
I never modified the kernel, it was always stock, for some reason, it worked for me after updating the firmware from 4.xx to 6.12.xx.
I agree about S-OFF, we really need that to mess around with the device.
rawfire said:
I never modified the kernel, it was always stock, for some reason, it worked for me after updating the firmware from 4.xx to 6.12.xx.
I agree about S-OFF, we really need that to mess around with the device.
Click to expand...
Click to collapse
That's probably a reason. If you installed international/wwe/gsm roms then AT&T/verizon/sprint it could be a problem. Have you checked the specific AT&T subforum for the M8....it's there for a reason because it holds differences.
I personally think you are one step ahead of the real solution. I think it's kernel related. Check the subforum for some info. See if it comes up with something.
I could be wrong......so don't hold that against me, just giving my thoughts
Mr Hofs said:
That's probably a reason. If you installed international/wwe/gsm roms then AT&T/verizon/sprint it could be a problem. Have you checked the specific AT&T subforum for the M8....it's there for a reason because it holds differences.
I personally think you are one step ahead of the real solution. I think it's kernel related. Check the subforum for some info. See if it comes up with something.
I could be wrong......so don't hold that against me, just giving my thoughts
Click to expand...
Click to collapse
That's really a thought, I'm definitely gonna check it and see if it's something related to kernel. Thanks for the suggestion.
And yeah, firmware upgrade was the last resort I guess lol,
Really appreciate that.
rawfire said:
That's really a thought, I'm definitely gonna check it and see if it's something related to kernel. Thanks for the suggestion.
And yeah, firmware upgrade was the last resort I guess lol,
Really appreciate that.
Click to expand...
Click to collapse
If you find anything please let us know. So we all can learn something if possible
Hello,
I've got a Galaxy Tab Pro 8.4 that I bought during the few months when it was the top of the line small tablet from Samsung (before the S series came out). Since it seems clear that Samsung has abandoned it and it won't get an Android update, I want to see what it'll take to upgrade to at least Lollipop. I'm pretty tech savy, but I've never tried to do anything like this with Android and I'm not at all sure where to start.
I've started to read the thread on rooting, but I quickly got a bit lost as I don't understand the terminology.
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking? If it is possible, can someone point me to a how to for complete newbies?
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
CafeKampuchia said:
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
Click to expand...
Click to collapse
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Ichijoe said:
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Click to expand...
Click to collapse
1) I read the OP. He said, "stock Lollipop or Marshmallow."
2) You don't have to root TouchWiz to install a custom ROM. All you have to do is install TWRP, but it doesn't matter because of #1 above.
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it. I read it that he has accepted the fact that Samsung have left us in the lurch concerning any future updates.
That's how I read it, so the question follows in how to install a Custom ROM. Granted it should be possible to install TWRP v. 3.0.1-0, though Odin, and then the Device appropriate ROM. It should go without saying that the T320, and T325 are not the same Device, even if they are both collectively known as Galaxy Tab Pro's 8.4. As such it would be upnto the owner to know which version he might need.
Ichijoe said:
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it.
Click to expand...
Click to collapse
The problem, is folks really need to stop using the word "stock" as it really doesn't mean jack. Or at the least, means so many different things to different people, as to be basically meaningless. I would take stock to mean, what belongs on the device per the manufacturer, so that would be Kitkat TouchWiz in this case. To others (and probably what the OP is getting at) is a "pure" unskinned Google experience like Nexus. But seeing as Nexus is limited to such a small number of devices, I don't personally feel you can consider that "stock". CM is AOSP based, and at one time considered by many to be close to a pure AOSP experience. But those days are long gone, and there are so many proprietary CM features and apps now, you can't even begin to consider this "stock" by any means.
---------- Post added at 03:36 PM ---------- Previous post was at 03:22 PM ----------
_salguod said:
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking?
Click to expand...
Click to collapse
What you are asking for is CM12 or CM13 (LP or MM) or one of the CM based ROMs. Those are really your only choice when it comes to anything past KK on this device. The CM ROMs are are very stable at this point. You might run into an obscure bug, but to be honest, its less laggy and overall a much better experience than the official Samsung TouchWiz ROM. And if you want to be free of Samsung bloat, CM definitely does that as well.
Tweak or maintain? You don't have to do anything after flashing the ROM, if you don't want to. You can decide to update to newer nightly CM builds from time to time, but that is completely optional. And to be honest, even CM13 is so stable at this point, that the nightly updates don't really change much of anything.
Go back? That's a breeze. Just do a backup in TWRP custom recovery before flashing a ROM, and you can restore to that backup (basically a snapshot of your existing configuration).
_salguod said:
If it is possible, can someone point me to a how to for complete newbies?
Click to expand...
Click to collapse
Honestly, just searching and reading are your best friend. You'll learn a lot more that way, than folk spoon-feeding you the info. The process isn't really all that hard. There may be a lot of esoteric lingo, but you can easily Google or use the XDA site search to find out what those terms mean. And once you've gone through the process, you'll likely be happy for the learning experience.
XDA is a wealth of information, for those willing to take the time to learn and search. All the answers you want are here in one form or other. Difficult to wade through at first, I'll agree with that. But all of us here had to go through the same thing at one time or other.
Its really hard to help someone when they say is "I'm a newb, tell me how to do this". Make a lot more sense for you to just dive in, then come back here with some specific questions, which we will gladly answer.
it would help to know what version OS you're running and the build #.
I rooted my tablet late last year (bought it in May 2015). Wasn't hard to do after some reading. Knox is still good too...1 yr warranty will be over soon.
Thanks all, I appreciate it. I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
I definitely appreciate the push to search and learn, but it can feel like drinking from a firehose. Most "how to" posts are written assuming the reader knows the terminology and every post I read means Googling a half a dozen terms to understand it. For example, I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
When I said "stock" I was referring to stock out of the box Android, not stock Samsung. Stock Samsung means staying with KitKat which I'd rather not do. My phone is a Motorola Droid Turbo, which I think is pretty close to stock Android Lollipop, so that I'm familiar with that.
However, I think I'm seeing that going stock Android isn't necessarily possible, or rather, other ROMs are easier to come by. Cyanogenmod seems to be the most popular and sounds very stable, I'll likely try that.
So, I don't need to root in order to flash a new ROM. What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back? Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Any other surprises that a guy who has never done this might want to know before going in?
Thanks again for your patience and help.
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Well you have a number of choices for your T320 (WiFi), Sadly nonmof those stock. Since Samsung has never seen fit to ever giving us one. For me the Samsung (e.g. Vender ROMs), were always the 'Stock' ROMs. 'Pure' ROMs (al-la Nexus), are clearly Custom ROMs.
The best, and quickest way to learn how to update from Stock to Custom would be to hit up YouTube for a few short Vids on the subject.
_salguod said:
I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
Click to expand...
Click to collapse
Those aren't bad general guides, to just introduce you to the basic concepts and terms. Just keep in mind that every different Android device has its nuances, which vary by manufacturer and over time (from one device to another - even from the same manufacturer). So you'll be referring back to Tab Pro 8.4 specific guides eventually.
_salguod said:
I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
Click to expand...
Click to collapse
Basically, if you don't know what the Knox flag is, then it probably doesn't matter.
The longer story, Knox is a enterprise mobile solution made by Samsung. If you company doesn't use Knox (and you don't use your device for work), you don't need it. The huge majority of folks will never need Knox or want it.
You're right, that if the warranty is expired, the warranty flag doesn't matter. And honestly, I rooted my device while it still had a valid warranty. I'd rather have a device that I can use how I wish, and install what software I want (especially if Samsung isn't going to support it with updates) and warranty is a secondary concern, at most.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
Once you install TWRP custom recovery, you can make a backup of the current Samsung TouchWiz KK ROM; and revert to that if needed or desired.
But honestly, you won't want to go back. CM runs faster and smoother, with no Samsung bloat. You won't want to go back to the crappy TouchWiz ROM, that is 2 generations (Android versions) obsolete.
But it is a good idea to have a backup, in case flashing CM doesn't go right the first time, and the device won't boot.
_salguod said:
Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Click to expand...
Click to collapse
You will absolute want to wipe user data when installing CM. Not doing so will likely cause major bugs and/or failure to boot. This is the general rule whenever flashing a new ROM. Although for similar ROMs (such as minor CM updates) you can try to keep user data. This is called a "dirty flash".
You can backup a lot of your data before flashing CM:
Apps: After root, you can use the app Titanium Backup (highly recommended) to backup apps and app data
Accounts: Titanium can backup a lot of this stuff, as well. Depends on what you are talking about, specifically.
Files: just move them to SD card or your computer. Or use a cloud solution (there are many)
You should always be backing up your data, anyway, if its important to you.
_salguod said:
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Click to expand...
Click to collapse
Same firmware as what I had prior to rooting it.
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
AndroidPrince1 said:
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Click to expand...
Click to collapse
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
AndroidPrince1 said:
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
Click to expand...
Click to collapse
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Thanks all, I plan on biting the bullet some time soon. Too much other stuff on my plate (like car repairs, etc.) so it'll have to wait for a bit. I'll check back in when I do. I'm looking forward to it.
redpoint73 said:
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Click to expand...
Click to collapse
Good to know on the sdcard thing...looks like I'll have to read up again on how to do.
Thanks for the note.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
CafeKampuchia said:
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
Click to expand...
Click to collapse
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
_salguod said:
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
Click to expand...
Click to collapse
Cellular South is the US firmware for some reason.
I'm trying to load the latest CM 13.0 nightly this morning and running into issues.
I'm following the install instructions on the CM website and the loading of a custom recovery is failing at step 7. I get the start of the blue bar on my tablet, but I get this error in the command prompt:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've tried twice with the the factory cable and a third time with an alternate cable same result.
How do I fix that?
I should mention that I'm working on a Windows 10 computer.
Howdy, I'm currently playing with bigsupersquid's unofficial cyanogenmod 13.1 rom for the Virgin Mobile variant of this phone. Everything on it works great except for the wifi which seems not to activate at all - also preventing me from using my tethering. I was forwarded to update the firmware for this device to Lollipop, but outside of the "A5-DUG" variant, I seem to be having trouble finding it. Can anyone provide me the right directions or place to start for this? Any help would be appreciated, thanks!
davidw.roggenkamp said:
Howdy, I'm currently playing with bigsupersquid's unofficial cyanogenmod 13.1 rom for the Virgin Mobile variant of this phone. Everything on it works great except for the wifi which seems not to activate at all - also preventing me from using my tethering. I was forwarded to update the firmware for this device to Lollipop, but outside of the "A5-DUG" variant, I seem to be having trouble finding it. Can anyone provide me the right directions or place to start for this? Any help would be appreciated, thanks!
Click to expand...
Click to collapse
yer lucky, I don't often browse the regular forum, just the threads I've already posted in.
however, I obviously need to add this link to the OP for cm13 (and maybe cm12 as well.)
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
straight from the horse's mouth (htc,) that link.
getting it installed without M$ windows is challenging but can be done, requires some searching. with window$ it's relatively painless after downloading the 2+GB file and installing drivers and such.
I know some people are picky about questions in dev threads but I've always welcomed discussion there, so feel free to ask anything else in the ROM threads.
bigsupersquid said:
yer lucky, I don't often browse the regular forum, just the threads I've already posted in.
however, I obviously need to add this link to the OP for cm13 (and maybe cm12 as well.)
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
straight from the horse's mouth (htc,) that link.
getting it installed without M$ windows is challenging but can be done, requires some searching. with window$ it's relatively painless after downloading the 2+GB file and installing drivers and such.
I know some people are picky about questions in dev threads but I've always welcomed discussion there, so feel free to ask anything else in the ROM threads.
Click to expand...
Click to collapse
I'm guessing that this is the process to use a RUU and revert back to stock to get the OTA update? I went through a huge debacle trying to find just this and managed to get it to work with a stroke of luck. I'm actually using your Cyanogenmod 13.1 without much issues. I'll leave a bug report in your thread. Thanks again!
davidw.roggenkamp said:
I'm guessing that this is the process to use a RUU and revert back to stock to get the OTA update? I went through a huge debacle trying to find just this and managed to get it to work with a stroke of luck. I'm actually using your Cyanogenmod 13.1 without much issues. I'll leave a bug report in your thread. Thanks again!
Click to expand...
Click to collapse
How do you get lucky? I am on CM 13.1 and still can't get wifi. I have the RUU and tried through windows and just got errors.
tucker1003 said:
How do you get lucky? I am on CM 13.1 and still can't get wifi. I have the RUU and tried through windows and just got errors.
Click to expand...
Click to collapse
Here, for everyone having firmware issues on chl, I spent all day uploading the zip RUU.
Make sure your phone is charged first. Very bad juju for it to die during firmware flashes.
I'm not sure if it needs stock recovery installed to use it or not. May not install without it and that'd be a hassle. Follow the instructions linked in my cm13 first post for installing stock recovery if you're wanting to play it safe.
Definitely
fastboot oem lock
before putting the 0P9CIMG.zip on external SD and rebooting into HBOOT. Or it won't flash.
Then remove the sd card after it is finally done. It'll take a few reboots to finish.
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Download latest factory image. Extract the boot.img from it and save to your phone. Open magisk manager and patch that boot.img. Save /download/magisk_patched.img to your computer. Disable or remove any magisk modules that you might have running. In bootloader run the flash-all.bat, after editing to remove -w, and boot into system. Reboot to bootloader and run "fastboot flash boot --slot all magisk_patched.img" and you should be good to go. Make sure to back everything up before hand just in case something does wrong. I use a mix of titanium backup, sms backup/restore, export contacts, and manually saving files. There are other ways, but this is what I am comfortable with.
pside15 said:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Click to expand...
Click to collapse
Here ya go... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Google offers their own flashing update tool. You can find it here, https://pixelrepair.withgoogle.com/carrier_selection.
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You will need to wipe data on the upgrade to 10.
You will need to root again after the update. Bootloader will remain unlocked.
Once you have rooted, there is a method to take an OTA, and stay rooted. A description of the procedure is in the forums somewhere.
Again, I would recommend to follow the guide posted by Homeboy76. It will comprehensibly explain all the steps you need to achieve root,update etc. With links to downloads.
Gone are the days of flashing with just your phone. My first rooting experience was with an HTC Amaze. Then an S4 Samsung.
Good luck..
Edit: I stand corrected on data wipe when going to 10. I perhaps was overly cautious, and followed other recommendations.
pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You do not need to wipe data to update to 10. It is perfectly safe, we all did it. And so did all the people with locked bootloaders. You only have to wipe going down. Up is fine.
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
And here is the link to take an ota without losing root.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).
Anyone tried Google's flashing update tool?
Homeboy76 said:
Anyone tried this?
Click to expand...
Click to collapse
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
sliding_billy said:
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
The link is in spotmark's quote: How can it be my link?
When I click it it works.
Click to expand...
Click to collapse
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
sliding_billy said:
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
Click to expand...
Click to collapse
It's working now
Homeboy76 said:
Read the edited post above yours.
Click to expand...
Click to collapse
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
sliding_billy said:
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
Click to expand...
Click to collapse
@sliding_billy
It's working now
Homeboy76 said:
@sliding_billy
It's working now
Click to expand...
Click to collapse
Winner, winner. Even better when you can't see the link.