Database Info

[GUIDE] T-Mobile US One S - How to ROOT and flash ROMs

So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.

bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.

Worked great for me
Sent from my HTC VLE_U using xda premium

So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??

Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?

cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.

nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1

androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.

First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help

I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.

not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.

suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium

yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.

Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.

nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.

Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.

nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!

suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.

the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.

I sent you a PM, trying to find a solution.

Installing TWRP per instructions and now phone DOA...

Hi all,
I've been ROM'ing since 2013 on multiple devices so I am somewhat familiar with adb/fastboot flashing and commands, what to do, what not to do, etc.... I just picked up a used pixel and first thing I did was unlock the bootloader - no problem. Next I go to root, so I began following this tutorial https://android.gadgethacks.com/how-to/root-your-google-pixel-pixel-xl-0174670/ , as instructed I DL the required drivers, image files, patch file etc...and follow this tutorial for installing TWRP https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ , I get to step 8 and instruct via the command window to fastboot boot twrp.img, just as instructed. Everything appeared to be going the way it should as it started to boot to TWRP but almost as quickly the phone just died. I mean dead as a door nail. It won't do a thing. It won't even charge now. I have never had a phone just die like this. I fear I have met my first true full on brick.
I mean, yeah, I have soft bricked phones many a times but always had a backup to restore or was able to dig my way out one way or another but that was explainable by messing with questionable ROM's or something similar. Here I was just booting to the phone specific most recent version of TWRP by a solid well known tutorial with solid links, no indication that these could be the wrong images or zip's at all....but I'll be damned if this phone is dead as hell. I'm hoping someone can shed some light as to what happened or even miraculously tell me that it can be fixed.
Guys, is this a worst case scenario full on brick with no hope or getting it back to life? If so, why? Where did I go wrong? If this is going to be what I fear it is I hope to at least understand how it happened so I can avoid it in the future. This was a very expensive F-up on my part. I am beside myself with grief and disbelief that I could have done this with as many times as I have unlocked bootloaders, rooted, installed TWRP, flashed ROM's, etc.. I mean I 'm not the best but I am not a noob by any means. I feel like such a dumb ass right now!
Appreciate any help or explanation anyone can offer. Thanks.

We don't flash avb or any other patches anymore and haven't for like an android version and a half. For future reference look for more current information when modding a phone and for simple things like root guides go to xda don't just ask Google.

@kerryh420,
Those are some pretty old tutorials!
After plugging in the charger and wait for say 10seconds, can you boot into bootloader with button combo?
(Power + volume down or power + volume up for recovery as alternative)
Cheers
Sent from my Galaxy Tab S2 8.0 using XDA Labs

No offense, if you've been ROM'ing since 2013 you'd know not to go to other websites for tutorials! XDA is your best friend to follow instructions on Rooting, Flashing a recovery, and etc! Sorry that happened to ya. If it's literally dead you're probably out of luck and I know that's not what you want to hear. My best advice is to not follow tutorials on other websites. Good luck on your next device!

alcatel 3v project treble

Just thought would leave this here.
The Alcatel 3v supports project treble it's probably the cheapest on the market that supports this

If there is a way to unbrick it, I might try flashing a GSI to see if it will actually work. The thing is that for some reason my 3v has a MT6735

nintendobuster420 said:
If there is a way to unbrick it, I might try flashing a GSI to see if it will actually work. The thing is that for some reason my 3v has a MT6735
Click to expand...
Click to collapse
Ok just to give you guys an update, GSIs actually work! I managed to unlock the bootloader by typing in fastboot oem unlock and ticked oem unlock in developer options. Then I followed XDA's guide on flashing a GSI and it actually worked. Now we have stock android on the alcatel 3v. The only problem is that the phone is really slow and the stock camera app is upside down so its probably best to stay on stock

Have you had any luck trying out different gsi's, perhaps there's a certain one that works better? Also, would you happen to have a stock rom for an Alcatel 3v 5099a? Or at least a boot.img?

Laney613 said:
Have you had any luck trying out different gsi's, perhaps there's a certain one that works better? Also, would you happen to have a stock rom for an Alcatel 3v 5099a? Or at least a boot.img?
Click to expand...
Click to collapse
Oreo seems to be less laggy also I have a 5099y which is the nfc version I could try and dump my rom
I just really want to fix the youtube lag on this phone as it always lags at 1080p or 720p

how did you unlock the bootloader ? i have the 5099y, i tried adb fastboot oem unlock,i have adb installed ,i have google usb installed,ive got updated drivers, but it still says waiting for device,it boots into fastmode fine ,but then once i do adb devices it doesnt see it,it does show in the device manager as alcatel,usb debugging is allowed, oem unlock is ticked

CrunchyKevlar said:
how did you unlock the bootloader ? i have the 5099y, i tried adb fastboot oem unlock,i have adb installed ,i have google usb installed,ive got updated drivers, but it still says waiting for device,it boots into fastmode fine ,but then once i do adb devices it doesnt see it,it does show in the device manager as alcatel,usb debugging is allowed, oem unlock is ticked
Click to expand...
Click to collapse
It's fastboot OEM unlock, when in fastboot

The procedure was fairly easy and I'm now running phhussons AOSP 9 v114 on my 5099Y.
Very smooth and much faster than stock 8.0.
No camera issues at all.
Google play verification was an issue but soon sorted
This device needs further development though, it has a few random glitches running pie, but nothing than stops it working well.

After reading @ivan1972 comments I've today also flashed a couple of gsis on my 5099Y and had good success all round.
I unlocked the bootloader, this device has the easiest unlocking bootloader ever!
I then tried lineage 15.1 with Go gapps and that worked really well.
I tried Descendants 3.0 and flashed via fast boot (fastboot flash system system.img - I obviously renamed the GSI to "system.img") I have that installed on my Moto E5 play but it was far too glitchy on the Alcatel and I had huge problems trying to get the play store certification working, so I was bombarded with notifications about my 3V not being Google play verified almost every three seconds!!!
I'm also using AOSP 9 v114.
The battery life is double that of stock oreo, the phone works twice as fast as it did on stock, and I had no issue with Google device certification.
I suggest any user wanting to flash a Gsi on a 3V spectrum should aim to install lineage 15.1 or AOSP 9 as they are both great gsis.
Edit, the Gsi was flashed in fastboot as I haven't rooted or flashed (found) a twrp for the 3v yet.

Some screenshots from my 3V Spectrum (using the latest Lawn chair V2 as default launcher)
You will note the status bar is glitchy and doesn't show until a notification is received, then it appears in the middle of the screen, not at the top.
The only major issue I've seen so far.
The device is listed as "PHH treble" in device settings

After a week's usage Ive found one major flaw.
Whilst you can make an out going call with no problems, with good clarity and good service, no one can actually phone you.....!
Incoming calls are diverting straight to voicemail, nothing in settings to explain why.
Everything else is perfect on pie, flawless and way better than stock.
But this phone is no use if you cannot use it for its primary function - to receive a phone call :crying:
Edit - I'm told it's an AOSP issue on mediatek chips, and it's not an easy fix.
And as there is no way to go back to stock, I'm now stuck with a device that cannot receive any calls.
Just putting that out here incase anyone does read this and feels the need to flash pie.
Don't bother!
I'm done with this Alcatel - no one really seems that interested in this device anymore.
Edit.
My Alcatel has been traded in (as non functional) for a Nokia 4.2

I'm not quite sure why are people sending me private messages asking if I can send them the custom recovery for the Alcatel 3V?
I have quite clearly stated in my previous posts that I flashed the GSIs I tried via FASTBOOT - there is NO custom recovery for 3V that I can find - so please don't message me requesting the custom recovery.
*WARNING*
I also recommended users do not flash android pie gsis on this device as it breaks RIL / modem function and there is no current fix - but for a strange reason people are still asking me about the process and any bugs / issues.
Please read things properly before posting private messages - whilst I'm happy to help anyone, I'm not prepared to keep unnecessarily repeating myself for the sake of repeating myself when the information is already there for everyone to see.......

bubba1601 said:
After reading @ivan1972
I unlocked the bootloader, this device has the easiest unlocking bootloader ever!
Click to expand...
Click to collapse
I wish that was easy to believe, but I have an Alcatel 3v (5032W) and I CANNOT unlock the bootloader for the life of me!

@mattchusquirtle420
I'm not sure why you find what I said one year ago so hard to believe, but I'll explain it to you.
Are you sitting comfortably?
Then I'll begin.....
This thread deals with the 2018 Alcatel 3v (5099Y)
It's a 2gb ram 16gb ROM / 3gb ram 32gb ROM on Android 8.0 (Oreo)
That had a standard MTK (Mediatek) chip so was super easy to bootloader unlock.
All you had to do was enter fastboot and use the "fastboot OEM unlock" command and press enter.
The bootloader was now unlocked, no unlock codes were needed or necessary.
https://www.gsmarena.com/alcatel_3v-9004.php
********************
You have the 2019 Alcatel 3v (5032w) which is a 3gb ram 32gb ROM device running Android 9 (pie)
Which has a MTK Helio chip and a locked bootloader that cannot be unlocked.
None of the Helio or Snapdragon Alcatel 2019 devices can be bootloader unlocked, infact the only 2019 Alcatel device than can be bootloader unlocked is the 1C.
I'm not being rude to you here, but this thread began back in May 2018 - and you also just replied to a comment I made in July 2019 - That's a whole SIX months before your 3v 2019 became commercially available.....so I don't understand why you even commented, your device isn't relevant, or even has the same processor / chip as the 2018 version, so how can you honestly disbelieve our experience if you have a completely different device?
I now have this device.
Alcatel 3 (2019) 5053Y (Snapdragon 439 chip with 3gb ram and 32gb ROM on Android 9 pie)
https://www.gsmarena.com/alcatel_3_(2019)-9599.php
It's not possible to unlock this device because bootloader unlocking is not supported.
I'm going to ask you now very politely and without being rude to NOT private message me about your device.
Your device is not relevant or related to our discussion or this post.
You are going to have to find a dedicated thread for the 3v 2019 because posting and commenting in the 2018 device thread is not really very clever and achieves nothing, and helps no one, including you.

Oh dear.
You seem to be annoyed and disbelieve what we are saying.....
Well how about you actually read the post properly first before you start telling people you find it hard to believe what they say?
Did it occur to you at any point that we may have been discussing a different device to one you have?
There is more than one version of the Alcatel 3v and they are all different.
Nothing annoys me more than comments from people who don't take time to read the information Infront them properly.
You've commented here saying you can't believe us but you've commented in a device thread that you don't have or have any experience of at all, so your comments are completely unfair and totally unnecessary.
I thought how old the the thread was it would have been completely obvious to you that we were not discussing the same device as yours, or you were just stupid and assumed it was the same.

@bubba1601
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.

Aballamis said:
USER=7682183]@bubba1601[/USER]
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.
Click to expand...
Click to collapse
Really?
Don't you think it's just a bit sad that you felt the need to take me to task over comments I make 16 months ago?
Who cares now?
It's not my fault or my problem if you blindly follow Google links.
It's not my fault you made a mistake, at least you admitted to it, so many here don't.
I'm sorry you made the same mistake but rather than sound off to me about it a year and 4 months later, learn from your mistake, move on and forget about it.
What happened here is none of your business, the "new" guy concerned made a heartfelt and genuine apology privately to me and we both moved on 16 months ago, but now you come along and you have to have the audacity to tell me off!
I can always refer you to the mods here if you are really concerned and upset about my comments, but seeing as it was resolved so long ago I don't really see the point.
Or I could just report you for harassing me, the choice is yours

Aballamis said:
@bubba1601
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.
Click to expand...
Click to collapse
No one has annoyed me only you.
I don't take kindly to getting XDA notifications at 3 am, especially for something I said here so long ago.
So what I need to know is why are you replying to something I said almost 2 years ago?
So you really think I care what you think?
I think it's absurd you come here telling me and the other guy off for something we said 16 months ago - AND after you admit to making a mistake and follow Google links without checking.
That's just stupid.
Did you actually read the thread properly? I think not, you come charging in here with all guns blazing without knowing the full facts.
The other guy apologized to me for his mistake privately and there was no problems between us.
So why are you telling me off now 16 months later without knowing the full facts?
When did you check the facts?
You just charged in here telling people off.
I'm not happy about this as it was resolved 16 months ago with good intentions privately, amicably and in good spirits.
I will be reporting this matter to the moderation team here, as I certainly don't take kindly to being told off by people who cannot check the facts first.

Hello, can someone please send me the official recovery of the alcatel 3v 5099a?

.

Any updates on TWRP?

Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
I was just thinking this the other day. The whole scene of Rooting and flashing ROMs seems to be coming to a dead end. Kinda sucks, I've always enjoyed tweaking my phone in my spare time..

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
Used to take 1-2 weeks when things were simple and easier.
Your comment about factory builds doesn't make sense considering you don't need TWRP to flash custom ROMs etc

Mackay53 said:
Used to take 1-2 weeks when things were simple and easier.
Your comment about factory builds doesn't make sense considering you don't need TWRP to flash custom ROMs etc
Click to expand...
Click to collapse
True, but it does seem like it has greatly hindered rom development... It wasn't until very recently there were any roms even available.

in_dmand said:
True, but it does seem like it has greatly hindered rom development... It wasn't until very recently there were any roms even available.
Click to expand...
Click to collapse
More cheaper phones will have a higher user base so more development activity.
I think Pixels already has solid software so not much to add and the high price point will hold it back a little

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html

Root-Maniac said:
I was just thinking this the other day. The whole scene of Rooting and flashing ROMs seems to be coming to a dead end. Kinda sucks, I've always enjoyed tweaking my phone in my spare time..
Click to expand...
Click to collapse
No we all just have to move on to next generation rooting an modding. Magisk can be flashed, or the Manager App is used to patch the boot.img manually and flash it afterwards. GSIs ROMs can be flashed via fastboot from fastboot mode as well. So in my opinion it is fastboot flashing an GSI.img, Custom (optionally Magisk patched) boot, or Stock Magisk patched boot. That's it. It's even more, as it's back to the roots of adb and fastboot. TWRP has been there on U12+ for as long as the device exists, bit I never used it, as I switched to GSIs instead, and of on Stock the Magisk ROMs of LeeDrOiD and Team Viper could be easily installed through Magisk Manager. We should all have taken a look at phhussons work much earlier to accommodate to the things that got moving by Googles change in architecture when they introduced treble. We've only been to lazy, and many of today's users on this board, hardly know anything in-depth about adb and fastboot, but only scratch the three or four superficial standard commands. Technical affinity is more in demand again, and our good old adaptability.
Sent from my Pixel 4 XL using XDA Labs

uicnren said:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Click to expand...
Click to collapse
Oh wow, thanks for posting that! I certainly don't expect dees Troy to handle that difficult of a problem by himself with his wife pregnant and everything. Thanks again

5m4r7ph0n36uru said:
No we all just have to move on to next generation rooting an modding. Magisk can be flashed, or the Manager App is used to patch the boot.img manually and flash it afterwards. GSIs ROMs can be flashed via fastboot from fastboot mode as well. So in my opinion it is fastboot flashing an GSI.img, Custom (optionally Magisk patched) boot, or Stock Magisk patched boot. That's it. It's even more, as it's back to the roots of adb and fastboot. TWRP has been there on U12+ for as long as the device exists, bit I never used it, as I switched to GSIs instead, and of on Stock the Magisk ROMs of LeeDrOiD and Team Viper could be easily installed through Magisk Manager. We should all have taken a look at phhussons work much earlier to accommodate to the things that got moving by Googles change in architecture when they introduced treble. We've only been to lazy, and many of today's users on this board, hardly know anything in-depth about adb and fastboot, but only scratch the three or four superficial standard commands. Technical affinity is more in demand again, and our good old adaptability.
Click to expand...
Click to collapse
I agree on most points of you. GSIs are wonderful especially for phones at release start when there are no custom roms available yet.
And luckily device specific custom roms can be flashed over fastboot, too.
But for one reason i want a twrp for our device:
I find data backups with twrp much more easier as without. At least on my pixel 4 xl i miss a twrp somehow because Titanium Backup doesn't work on the gsi which i'm using.
I must create all my app folders again on my phone when i update it and backup all my stuff manually on my pc in extra folders and files.
I could spare me all that with twrp.
(I know there is the Google Cloud too as possibility but i refuse to use it)

dhacke said:
I agree on most points of you. GSIs are wonderful especially for phones at release start when there are no custom roms available yet.
And luckily device specific custom roms can be flashed over fastboot, too.
But for one reason i want a twrp for our device:
I find data backups with twrp much more easier as without. At least on my pixel 4 xl i miss a twrp somehow because Titanium Backup doesn't work on the gsi which i'm using.
I must create all my app folders again on my phone when i update it and backup all my stuff manually on my pc in extra folders and files.
I could spare me all that with twrp.
(I know there is the Google Cloud too as possibility but i refuse to use it)
Click to expand...
Click to collapse
Why do you refuse to use Google cloud

ceelos218 said:
Why do you refuse to use Google cloud
Click to expand...
Click to collapse
Because i don't want to feed Big G with my data.
And GSIs give me the possibilty to use my pixel without all the Gapps and the Google Play Service. That's a reason too why i like GSIs.

dhacke said:
Because i don't want to feed Big G with my data.
And GSIs give me the possibilty to use my pixel without all the Gapps and the Google Play Service. That's a reason too why i like GSIs.
Click to expand...
Click to collapse
Privacy is an illusion unless you go completely offline.

zetsumeikuro said:
Privacy is an illusion unless you go completely offline.
Click to expand...
Click to collapse
So we should stop fighting for this? Sry but that isn't a option for me.
Yes complete privacy isn't possible mostly but there are ways to improve it. With privacy friendly services, FOSS Apps such as AfWall, AdAway and Ad and Tracking Blockers in Browsers, Linux instead if Windows and no use of Gapps etc.
I know that my comment is probably off topic so sry.

dhacke said:
So we should stop fighting for this? Sry but that isn't a option for me.
Yes complete privacy isn't possible mostly but there are ways to improve it. With privacy friendly services, FOSS Apps such as AfWall, AdAway and Ad and Tracking Blockers in Browsers, Linux instead if Windows and no use of Gapps etc.
I know that my comment is probably off topic so sry.
Click to expand...
Click to collapse
No worries man my comment was also off topic. I too used to a lot of what you currently do. Even using the magisk script Energized which does blocking of ads,trackers etc. But when I saw the sheer amount of information Google has collected even when I opted out of it, just made me realize how futile it almost all is. These companies will never be 100% transparent and honest with us since they're making money off selling our information.

zetsumeikuro said:
No worries man my comment was also off topic. I too used to a lot of what you currently do. Even using the magisk script Energized which does blocking of ads,trackers etc. But when I saw the sheer amount of information Google has collected even when I opted out of it, just made me realize how futile it almost all is. These companies will never be 100% transparent and honest with us since they're making money off selling our information.
Click to expand...
Click to collapse
I have a hobby of reversing stuff, Ive given up trying to go private. With gms code I've seen, they check for so much it's ridiculous. I think a better method for the future is us (the custom rom community) coming together to find a way to block outgoing traffic via an open source app

Surge1223 said:
I think a better method for the future is us (the custom rom community) coming together to find a way to block outgoing traffic via an open source app
Click to expand...
Click to collapse
I think we already have this with AfWall+.

I just wanted to chime in here with a tip to help fill the TWRP void that many are facing right now, especially with Android 10. You can use a manual file flashing app to do most of the same things that TWRP allows you to do, minus the recovery part, of course. You can flash all the TWRP mods you want using this method without needing a custom recovery. Just in case some people didn't know.
You can even install image files too, which means you don't need to be tethered to a computer once you get all set up. This guide should help you understand the power of manual file flashers without having to rely on TWRP for installing certain mod files.

StrifeSoldierVII said:
I just wanted to chime in here with a tip to help fill the TWRP void that many are facing right now, especially with Android 10. You can use a manual file flashing app to do most of the same things that TWRP allows you to do. You can flash all the TWRP mods you want using this method without needing a custom recovery. You can even install image files too, which means you don't need to be tethered to a computer once you get all set up. This guide should help you understand the power of manual file flashers without having to rely on TWRP.
Click to expand...
Click to collapse
It's not Just about flashing. It's about recovery. You can't use a flashing app if you are in a bootloop.

Tulsadiver said:
It's not Just about flashing. It's about recovery. You can't use a flashing app if you are in a bootloop.
Click to expand...
Click to collapse
Oh definitely! Nothing worse than a bootloop. I was just specifically talking about the flashing part. I know a lot of people have been lost without TWRP, so they aren't installing certain mods as much right now since it takes more steps without it. But you can at least do the installing part without TWRP using a file flasher. I don't think as many people are aware of this. It's handy to know. You can use it as a stop-gap until TWRP arrives for any device you want.

the backup and restore functionality of twrp is what i am missing most. just in case something goes wrong with a flash.
is there a way to backup/restore without a custom recovery?

The struggle... (64 bit recovery porting)

I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.

finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.

lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse

The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?

finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.

Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?

As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.

Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.

What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.

finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.

jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.