Develop Bugs

Has anyone had success rooting Testra phones with 1.16.184....ROM's?

I need to Root this phone and get rid of the Telstra rubbish, but i am having no luck to date.
Any advice from you Telstra handset owners would be fantastic!

Have a look on the modaco android forums, users there have reported success with rooting and flashing a generic desire rom. But there are also reports that the gps problem, that 1.16 fixes, comes back.

Please excuse this really n00b question...However is the only way to root by loading a modified rom onto the phone? Would it not be possible to root my current (HTC Desire from Telstra) keeping all out of the box software/settings?
I guess much the same way that blacksn0w jailbreaks an iPhone without you having to flash a jailbroken firmware back to the phone.
Cheers

It doesnt have to be a modified rom, it can be a stock one. If you do root your phone, you will have to reflash a rom though, be it stock or modified, and all of your personal setting will be gone.

Is there a particular one that seems to work well. I have had issues with mine because it came with the rom that has the GPS fix already installed. This rom is 1.16, it did not like the new one because it is 1.15
I had no issue creating the goldcard and got it to the bootload screen, but i could not get past that point.

Its best you ask questions in the root thread over at modaco, you'll get better answers.

Thanks Jaa-Yoo. I'll give it a crack.

T-Mobile UK 1.26.110.5 ROM

I am (unfortunately) running this Rom on my second (first was a portable hand warmer) One X on T-Mobile.
I have basically unlocked the bootloader and applied (seemingly the temporary) Clockwork mod which I got off Modaco. I checked with a Root Check app and everything is ok and SU is present.
But i've literally spent my day off trying to get another rom on this thing, tried some official roms, older versions, similar versions, newer ones, they always fail on flashing. Nothing seems to work.
Seems things have gotten difficult since I was slapping imate Rom's on Orange SPV's !
Anyone succesfully updated this ROM ?
cheers

I would like to know this too, have same ROM.

[Q] Most efficient way to update my GS3

http://imgur.com/EgzxWFI
I think this screenshot should have all of the relevant information. I would tried this sooner, but it was end of college, I got my first full time job, etc etc.
My main issue with this phone is that it does random "soft" resets where everything just comes down and it reboots to the lock screen. This is especially fun when I'm driving and using this as a GPS :laugh:. I'm pretty sure the kernel is involved somehow, but I honestly don't know.
I want to know:
1. What do you guys think would be the most efficient way for me to update both the ROM and Kernel?
2. Is there any way to do this without having to re-root?
3. Would I be better off just choosing a non-stock ROM in order to get to the latest version of the android OS more easily?
That's about it, pretty simple. Just some directions would be nice as I'm quite out of the loop. Thanks.

If you don't want to do the research or take the time to go through the trouble of reading through these forums, then the most efficient way will be to remain stock unrooted and update via the approved methods from your carrier and/or Samsung (OTA and/or Kies usually). All software versions from ICS on up (non international S3s are now officially on KitKat) have been covered extensively by now so I doubt anyone is going to entertain your direct request for information. There are many things you need to be aware of, such as but not limited to how the new bootloaders and KNOX, as well as how custom roms and kernels, are working together in the big picture of things.
NOTE: Regardless of which route you take, no one in this forum, including myself, is responsible should anything happen to your phone. Anything you do to your phone is at your own risk, including official updates from your carrier and Samsung.

xshadowinxbc said:
http://imgur.com/EgzxWFI
I think this screenshot should have all of the relevant information. I would tried this sooner, but it was end of college, I got my first full time job, etc etc.
My main issue with this phone is that it does random "soft" resets where everything just comes down and it reboots to the lock screen. This is especially fun when I'm driving and using this as a GPS :laugh:. I'm pretty sure the kernel is involved somehow, but I honestly don't know.
I want to know:
1. What do you guys think would be the most efficient way for me to update both the ROM and Kernel?
2. Is there any way to do this without having to re-root?
3. Would I be better off just choosing a non-stock ROM in order to get to the latest version of the android OS more easily?
That's about it, pretty simple. Just some directions would be nice as I'm quite out of the loop. Thanks.
Click to expand...
Click to collapse
You can get all the info you need here: http://forum.xda-developers.com/showthread.php?t=1725839
As for having to re-root, you won't if you flash a custom ROM. Getting the OTA (or Kies) update will require a re-root which can be easily done with Towelroot.
As for the "most efficient", just follow the ROM's OP instructions to a T - it''s usually straight forward and easy to follow.

BWolf56 said:
You can get all the info you need here: http://forum.xda-developers.com/showthread.php?t=1725839
As for having to re-root, you won't if you flash a custom ROM. Getting the OTA (or Kies) update will require a re-root which can be easily done with Towelroot.
As for the "most efficient", just follow the ROM's OP instructions to a T - it''s usually straight forward and easy to follow.
Click to expand...
Click to collapse
Thank you for the reply
Okay so basically the most (time) efficient way for me to update is to get some custom ROM. That's fine, all I need to work on my phone is a few programs nowadays. Namely Google maps and the phone (well and the browser). Is Kernel updating the same? What's one of the good kernels and roms these days for the purposes battery life?
The main reason I'm making this topic is I'm fine with just going out and following directions, but I'm updating from such an old version that I'm wondering if there are any "gotchas". Like I update it to this with my old kernel and the thing is suddenly bricked. That's really what I'm worried about.

xshadowinxbc said:
Thank you for the reply
Okay so basically the most (time) efficient way for me to update is to get some custom ROM. That's fine, all I need to work on my phone is a few programs nowadays. Namely Google maps and the phone (well and the browser). Is Kernel updating the same? What's one of the good kernels and roms these days for the purposes battery life?
The main reason I'm making this topic is I'm fine with just going out and following directions, but I'm updating from such an old version that I'm wondering if there are any "gotchas". Like I update it to this with my old kernel and the thing is suddenly bricked. That's really what I'm worried about.
Click to expand...
Click to collapse
Kernel will be overwritten in the flashing process. All you gotta do is make sure you recovery is up to date if you go the custom ROM way.
We don't make suggestions as for what ROM/kernel to use to avoid flaming and it also comes down to user preference. Although, I do suggest starting to look at some custom ROMs (most of them come with their own kernel but can also flash another one). It will most likely come down to AOSP vs TW (stock) base.
The closest to a suggestion I can make is to look at the top threads in the Dev section, those are the most "popular" ROMs/kernels.

Alright, looking around at the various threads in the development section I see that most of them look pretty simple to install. Just download the zip, reboot into clockwork and install after doing some resets.
I notice that some of these require a new bootloader/modem, though... I haven't seen those terms when I last did this. What are the general installation instructions for those; the same as custom roms? Can they brick your device (assuming that I even pick the one for my device)? I'll probably just install something that doesn't need me to update the bootloader/modem to make things simple.

For the most part, if you've updated to 4.3 you will be able to flash any available roms. The catch is once on 4.3, you cannot downgrade your firmware.
Firmware is updated either by ota or flashing with Odin.

I went ahead and got the Slimkat because the instructions for it were pretty easy. There are some unpleasant changes about it that I would like some assistance on, but I suppose that would go in the dev thread to ask about those. Thanks for the info, it helped give me some confidence about just trying it out. Like I said a little iffy about some of the things but overall I like. At least it hasn't randomly crashed on me yet, and getting all of my apps back was as easy as having TitaniumBackup extract them from my Nandroid backup.

How to best go about backing up stock/installing a custom ROM

Hi,
After doing some reading on here I am a little unsure on the best way to back up my HTC One M9 (GSM) stock recovery/system. My software number is 3.50.710.1 (Android 6.0) and it came from Optus (Australia). I cannot seem to find an RUU file for this firmware anywhere online; only earlier versions are available. My understanding of this is that I need an RUU file for my specific firmware as a fail-safe in case I mess something up and need to return to stock?
My questions are:
1) Can I get my phone back to the current complete stock firmware and be able to receive future OTA updates without turning s-off and without copying anything from my phone before I flash TWRP and a custom ROM?
2) If not is there anyway that I can back up my phone it its current stock state that will allow me to go back to this state if I want to go back to my stock Optus firmware or to install OTA updates? (Including the stock radio/recovery)
3) Reading this post as well as others leads me to believe that I may stop my mobile radio working by flashing a custom ROM (especially as the linked post has the exact same firmware as me). How can I avoid this, or fix it if it happens to everyone?
I am ideally looking for a custom ROM which improves over the stock firmware. My priority is maximum battery life, with customisation and HTC 10 system UI/apps a secondary focus. Any recommendations would be great, as well as tweaks and kernels which help give the maximum battery life.
Cheers!

You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.

Flippy498 said:
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
Click to expand...
Click to collapse
Thank you so much! I have managed to find the guide you mentioned to backup the stock boot image, system image and recovery. By the looks of it the tab to the right is the guide to return my phone to its original state, which is good. I'm more than happy to share the backup once I do it.
Flippy498 said:
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Click to expand...
Click to collapse
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Thanks again!

Da Doom Lord said:
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Click to expand...
Click to collapse
I've read that several times in the near past and I actually don't understand it. You never needed S-OFF for flashing none-sense based roms as long as I started using Android/HTC phones and that was back in 2012. Why do so many people think they need S-OFF for AOSP?
I personally prefer the Viper rom. But taste differs and in the end the best advice I can give is try it out by yourself. Everyone has different needs and is using his/her phone in a different way. The best rom for person a might be an awful choice for person b since he/she has completely different needs.
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9). However many things have changed since the M9. There is no hboot anymore, the Download Mode got introduced, google changed the way OTAs are checking whether your system is modified, and so on. (Just to mention a few changes.) Those issues with the lost signal didn't even exist on pre-3.x firmware versions of the M9. Therefore users like you who use a not so common firmware (in comparison to the user numbers of the most common firmware bases: international, taiwanese and the developer firmware) have no other choice but trying out by themselves or getting S-OFF and changing to a more common firmware.

Flippy498 said:
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9).
Click to expand...
Click to collapse
I have followed your guide and now have the latest stable LeeDroid ROM installed and TWRP. Just as I predicted the radio was not originally working. When I restored my stock boot.img from the original backup I performed it began to work. Thanks so much for your help! I'll upload the backup to cloud storage when I get access to a decent internet connection and then I'll share it to help others out.

Why can't you update PRL and profile in Lineage and other customs - and can we fix it

So as I've looked into it, it appears that nothing has changed here in the 2-3 years since I last explored this issue. I'm talking about the fact that you can't successfully update PRL and profile on CDMA carriers in LOS and AOSP ROMS. The usual behavior if you even have the option in the UX is that you get a force close. I'd love to understand why this hasn't been addressed.. It's a huge reason someone would stay on stock over AOSP/LOS. I saw someone suggesting a Nexus 5 dev had some success using a couple of APKs including OmaDmclient.apk, and a few threads here and on Reddit talking about how it must've been broken by an AOSP contributor, but in any event it still doesn't work. Isn't this something that the LOS team could fix if they wanted to?

The issue with CDMA is that most of the stuff isn't open source. This is why the aosp source code is targeted to GSM. So I sought this will get fixed any time soon.

Same problem... I think
My neighborhood has excellent Sprint 4G LTE coverage and it's much faster than T-Mobile. I happen to use Ting (which allows you to choose between T-Mobile GSM and Sprint CDMA, although to switch from one to the other costs $20). GSM isn't really an option for me.
Anyway, I used to have this problem with my LG Volt LS740. I could work around it by forcing a PRL and profile update on stock and then flashing to Cyanogenmod.
That phone finally bit the dust. I have now inherited my wife's Moto G 2015 (osprey) XT1548. Really nice phone.... but the issue is, the latest stock I can find is Android 6.0. I can activate the phone and get great 4G LTE on stock, but to flash to Lineage OS 14.1 (or AOSP) I have to wipe the device. I simply can't get it to pick up the 4G LTE service on the custom ROM's (tried both). This is a real problem.
As I understand it (admittedly from reading Wikipedia), the PRL contains an "acquisition table" that prescribes the frequencies/modes that the device will communicate on... so I think that's probably my issue. After doing the prescribed wipes in the ROM installation documentation, flashing the ROM, and booting the device, I think I've lost the PRL somewhere in that process.
Is there some way to retrieve the PRL while the device is on stock and put it back when flashing custom? If the PRL is indeed stored on the R-UIM, should I just remove the R-UIM during the first boot? Maybe I'm wrong and the problem isn't really the PRL.
Any thoughts? Please don't tell me to switch to GSM. The GSM coverage here is just plain bad from both carriers who offer it in my neck of the woods.

I have this same exact question. Ting, N910P note 4 that was originally Sprint, and days-old Lineage 16 / Andorid 9.0 . The latest stock rom is 6.0.1, and works fine. Lineage 16 works 99% fine and I'd really rather use that. But LTE doesn't work. If I force it to use 3G only, it actually all works. data, voice, text, bluetooth, gps… and being Lineage, I don't have to try to surgically remove all the spyware and other crapware without breaking it. It's just not in there in the first place. I'd really rather use that.
I would be fine having to extract things from the stock rom and edit files or whatever if it were at least just known what needed to be done. I'm fine with the fact that Lineage nor anyone else can actually include and redistribute any carrier proprietary stuff.

it should be possible
Has anyone figured this out?
I too have devices on ting, fantastically built devices that run amazingly thanks to a solid construction, the support of many many developers who are craft some of the best ROMs for any device I've ever seen, considering the limited specs of the XT1031s. Fortunately/adequately enough though, they only run on 3G Sprint, Boost originally, moved to Ting for their great rates for FreedomPop customers when they bought them out.
Anyway, currently to get a device on ting, I have to flash the latest 5.1 official stock Boost Mobile Rom with the latest radio baseband and firmware and such. A process thats pretty involved. I'm hoping that I can backup the stock image using TWRP, as when I went through the process of reloading the official image through the individual files via mfastboot, I skipped the logo and recovery files, and since I was able to retain my custom logos for boot and bootloaderunlocked screens, and the recovery, I'm hoping to be able to make an image of the stock ROM, which if at all possible, I'm going to do my best to make as bare bones as possible. May start with flashing the bloatware removed version of stock thats available, then going through and removing basically every app on the phone with the exception of settings and anything to do with phone, phone/carrier services, sim toolkit, etc, so I can have the smallest image possible that could maybe be restored everytime/anytime that I want to update the PRL or Profile. Which it looks like theres a new version of each released at a minimum every 3 months, as I just activated another device this way and there was only an incremental update of the last digit. If this works, great. If it doesn't then I hope that theres an answer to the question in the initial post of this thread;
Is there a way to update the CDMA PRL and Profile on a device that is running a custom ROM? If so, is it something the ROM needs to specifically support or is it something that is possible to do with a bundle of apks? Like sim toolkit and the like?
If its ROM related, are there, or would it be possible to take the necessary components from the stock files and install them in Xposed or Magisk? Or perhaps the buttons in the settings panel of the stock rom simply executes a series of commands that can be executed within a terminal CLI on the custom ROM? I assume that since the custom ROM clearly has access to the 3G radio since I can make and recieve calls, I have data, and text messaging (haven't tried MMS, but I assume it works) so why couldn't it do one more thing and initiate the PRL update?
I assume that even the stock rom doesn't ever touch the PRL or Profile, seeing as they remain even after a user data wipe, and are available for the radio to continue to use with custom roms, which means that the radio chip has to be the one storing the PRL Profile, so I bet that the radio also directly downloads those files from the carrier when asked to do so, and the stock rom must only come into play for the base logicstics of it all such as radio-"is this prl/profile a newer version than the one that i have now?" and phone-"yes, download new, purge old, flash new, tell me when done and leave me alone" Since the radio doesn't have its own processor for those sorts of things perhaps? If thats the case, then that should imply that theres nothing particularly proprietary or licensed, etc, that a rom would explicitly need to have in order to initiate these updates since it would never directly need to touch/see the files, just know that they were updated and what version number they are. What also lends me to believe this is the case is the fact that you can't select to downgrade the prl/profile, rollback, or load one manually, at least not that I can see.
So basically I'm saying that I hope it should be something simple to do. And if it is simple to do, you would think that custom roms would be able to read the carrier correctly too? Right now my new device reads "Boost" still. My previous one when I got it on ting I wanna say actually read ting afterwards. But when I loaded ressurrection remix, I had no cell/data/voice nothing, It just kept asking me for a sim card, which this phone doesnt have at all. When I loaded Lineage, everything cell related work. But can't update prl/profile, and carrier reads as "3G Roming Indicator Off" Which idk why thats the case.
Perhaps I'm missing something
Perhaps custom roms are missing a few somethings.
The only sure thing is that carriers need to just not be so greedy/dumb/uselessly difficult, and make giving them money for service easier, preferably without questions. Or at the very least actually provide some security so all this nonsense is at least worth something in the end to the end user, instead of being done so that they can try to spy on your unencrytped texts and calls to sell to advertisers, and selling access to the higest bidders such as the government and bounty hunters, whilst preventing you from restricting that information.