Database Info

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?

.

[ROM] Stock Oreo 8.1 With June Security Patch (OPM1.171019.019.V9.6.2.0.ODHMIFE)

Ladies and Gentlemen,
It is my pleasure to present the latest stock Oreo 8.1 (Beta) ROM for Xiaomi Mi A1. Up till now, only a handful of testers were able to use the stock beta 8.1
But now, everyone has the opportunity to use it on their device.
Disclaimer:
If you are planning to flash the ROM on your device, you are on your own. I would not be responsible if anything happens to your device. Your warranty will be void after flashing the ROM. You need to go back to stock stable ROM with a locked bootloader for Warranty.
Requirements:
1. Xiaomi Mi A1 (Ofcourse)
2. A PC (I am using Windows 7 here)
3. The ROM file (Available on the link below)
4. MiFlash Tool ( Link: http://en.miui.com/thread-345974-1-1.html ) (A big thanks to Miui forum for making the tool available on miui forum)
5. ADB Platform tool (Search on google)
6. Patience
Installation Process:
1. Download the ROM file from the given link and unzip it.
2. You will see a folder with name as tissot_images_V9.6.2.0.ODHMIFE_8.1
3. Keep it on C drive
4. Install MiFlash Tool on your PC from the given link
5. Set up ADB driver properly on your PC (It's very important)
6. Now go to your device and enable Developers option by tapping on Build Number 7 times.
6. Open Developers Option and enable "OEM Unlocking" and "USB Debugging" option.
7. Now press and hold the power button and Volume down button for about 10 seconds until you see a small bunny on the screen.
Now connect your device to your PC and open a command box and type fastboot oem unlock
8. Once the bootloader is unlocked, put your device in fastboot mode again and connect it to PC. (BE WARNED!!! if anyone is on May security patch, unlocking bootloader will erase everything from the device and device will restart again. You will need to unlock developers option again and enable "USB debugging" option once more)
9. Now open MiFlash Tool and see if it reads your device serial number by clicking on "Refresh". Now, select tissot_images_V9.6.2.0.ODHMIFE_8.1 and click on "Flash". Make sure you are doing it in a proper way.
10. Wait until you see a "Flash Done" message on the screen. It may take around 5-10 minutes. Once done, your device will boot into system and Congrats! Now you have Oreo 8.1 on your device with June security patch.
N.B. It is best that you select "Clean all and lock" option on MiFlash tool.
Flashing Guide For TWRP & Custom Kernel:
1. Grab the latest twrp recovery image (Oreo) and twrp installer zip file.
2. Put the recovery image in ADB folder and the installer zip in your device.
2. Boot your device into fastboot mode and connect it to the PC.
3. Make sure the bootloader is unlocker.
4. Open a command box and type fastboot boot xxx.img (xxx= recovery image name)
5. Once your device is boot into twrp, flash TWRP installer zip file and reboot back to recovery.
6. Now flash the custom kernel of your choice and Magisk (optional).
7. Reboot back to system.
Important Note:
If anyone has any problem understanding the steps, I would recommend that you google or search on Youtube. There are lots of Videos showing on how to flash stock ROM on MiFlash tool. Please don't blame me if you skip any step or do it wrong. I have shared the standard steps that remain the same for flashing both stable and beta rom. It is advised that you STAY AWAY if you don't know what you are doing. I am certainly not going to take any blame for improper flashing. As you have decided to flash the ROM, I expect you to have a little knowledge about how to use MiFlash tool. A lot of newbees have problem at first, especially when flashing rom on MiFlash tool. That's because of selecting and flashing the rom file in an improper way. You need to first learn exactly which folder to flash or else you will always end up on a bootloop. Please don't blame me for not spoon feeding you.
Bugs Encountered:
I have been using the ROM for two days and I am yet to find any bugs except ctsProfile shows as false and Google Play Store shows Uncertified.
*For better battery life, you can try Void kernel (Choose the stock version).
ROM Download Link:
https://www.androidfilehost.com/?fid=818222786056041186
Credit:
Xiaomi, 4PDA, @topjohnwu for Magisk, @flex1911 for Void kernel, @CosmicDan & @mohancm for their work on TWRP.
Special Note:
I apologize to all for breaking any possible XDA rule and hurting anyone here!! Please note that I am not getting paid for sharing this post here. If anyone still feels something bad, you can either let me know or you can report it to the admin. But again, I am extremely sorry for breaking any rule here.

MiFlash Tool

Screenshots will be added shortly.

Screenshots

Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.

exodius48 said:
Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.
Click to expand...
Click to collapse
I can confirm battery drain with this rom.

Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
Did xiaomi give you the permission to share it on xda?

muruu said:
Did xiaomi give you the permission to share it on xda?
Click to expand...
Click to collapse
No, this is leaked beta. He just reshare from displax @ 4pda.ru

after sucessfully flashing using miflash it stucks on andriodone

N1ck474 said:
This update is leaked from weeks, why complaining here and now?
We're getting delayed updates cause Xiaomi is far away from Quick updates (MIUI or Stock, still Xiaomi).
Click to expand...
Click to collapse
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?

joeniz said:
when unlock bootloader cause erase all information like may update?
Click to expand...
Click to collapse
Why would they remove a security feature they just recently added?

joeniz said:
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?
Click to expand...
Click to collapse
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.

Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.

dback31 said:
Why would they remove a security feature they just recently added?
Click to expand...
Click to collapse
Cause i found no phone that u can't root !!
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
Rowdyy Ronnie said:
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.
Click to expand...
Click to collapse
What about messenger fb in any rom i use i get animation lag in messenger when message appear things like that and if someone send me message while i using phone the phone animation lag .... Only in fb messenger i found this problem i hate this app .... Anybody have that issue because iam going mad .

Rowdyy Ronnie said:
Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.
Click to expand...
Click to collapse
If you just share a rom build by someone else, this is the wrong section of the forum to post it.
Too, you say (in op) you have permission from xiaomi to post it here in xda. This sounds unusual. Do you have any proof for this claim?

Thread cleaned.
Thread moved to the guides section where shared ROMs belong. The redirect from development section will expire in 24 hours.
:good:

Rowdyy Ronnie said:
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
hahahah oh wow
the best joke i ever seen
seriously
copyright to leaked build? hahaha i can't stop

Closed beta ROM, so no point in "allowing" you to share it. They could open beta and do it themselves.
I call fake news on that
You share a rom from another forum. Okay. It was already been shared in XDA by the original poster in 4pda.
I call this reposting in the same forum.
You state that the ROM isn't yours and you "share" it with other people on XDA. And then you say reposting is stealing? Didn't you repost it as well? For you is not stealing but for others is?
Conclusion: Are you that desperate for attention?

Is this the official beta rom?

Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
Click to expand...
Click to collapse
How did you manage to get permission from Xiaomi? Have some proofs?

[Tool] Nubia Red Magic 3S Unbirck Tool

This tool can help you to unbrick the Red Magic 3S. It will restore the phone to the oldest version, you need to update the system software by yourself. This tool is based on Qualcomm firehose protocol, so it should fix all kinds of software issue.
ALL DATA ON YOUR PHONE WILL BE LOST
DO NOT USE THIS TOOL IF YOU ARE RED MAGIC 3!!!!!!!! IT MAY DAMAGE YOUR MOTHER BOARD!!!!!!!YOU MAY VOID THE WARRENTY WITH THIS TOOL
If the tool have any problem, please send me a pm or reply down below.
Download Here:
EU ONLY
NON-EU

Everyone with a rm3 should use this. The SW on rm3s is much more stable. There will be no issues with your phone. I have done 3 already. Everything works fine.

@JerryYin and other members
you might think that sharing middle fingers on our forums looks funny but actually is not at all...
Forum Rules
2. Member conduct.
2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street
Click to expand...
Click to collapse
a small cleaning has been performed, please keep it civil and report anything that may concern instead of engaging, we are here to deal with whatever you think is not OK.
have fun and enjoy the forums!

suzook said:
Everyone with a rm3 should use this. The SW on rm3s is much more stable. There will be no issues with your phone. I have done 3 already. Everything works fine.
Click to expand...
Click to collapse
Hi Suzook i also confirm that Rm3s brick tool works on RM3 perfectly. I also changed my RM3 rom to Rm3s, thanks for your help..
@ jerry thanks to create a very useful utility..

vijaytechno21 said:
Hi Suzook i also confirm that Rm3s brick tool works on RM3 perfectly. I also changed my RM3 rom to Rm3s, thanks for your help..
@ jerry thanks to create a very useful utility..
Click to expand...
Click to collapse
Yup I already seen a Red Magic 3s with that rare RM3 grill for sale online. Just glad to see people can get a bit more resale value on there RM3 now. Just gotta figure out who is is. I might buy it just to find out.
Jerry said this would happen lol

vijaytechno21 said:
Hi Suzook i also confirm that Rm3s brick tool works on RM3 perfectly. I also changed my RM3 rom to Rm3s, thanks for your help..
@ jerry thanks to create a very useful utility..
Click to expand...
Click to collapse
what u got with rm3s rom? .. whats the new change!! .. and why should i do it?

Found little more optimized rest all is same, transition also find smooth. Rest need to check.

This is not changing a rm3 to a rm3s. Anyone who thinks this, is an IDIOT. What it is doing is giving you a better, more stable FW. Another bonus is TWRP on the NA FW works. No need for the CN FW. Any idiot buying a rm3 with rm3s fw is, well, an idiot.

Well since people are flashing the 3s ROM to the 3 I'll just post this.
While ago I tested this. Found a few issues. Never tested the latest 3s ROM on the 3 but I'll just leave you with these test.
I advise people only use the 3S ROM on the 3S.

install package failure 25% help me !
JerryYin said:
This tool can help you to unbrick the Red Magic 3S. It will restore the phone to the oldest version, you need to update the system software by yourself. This tool is based on Qualcomm firehose protocol, so it
Click to expand...
Click to collapse

phivietnam said:
JerryYin said:
This tool can help you to unbrick the Red Magic 3S. It will restore the phone to the oldest version, you need to update the system software by yourself. This tool is based on Qualcomm firehose protocol, so it
Click to expand...
Click to collapse
Which package are you using?
Click to expand...
Click to collapse

PLease help, I am getting this error message:
"Download port number=8
Downloading firehose programmer...
[Error]: Download programer FAIL.Please check phone status and reset into edl mode and try again.
Software download FAIL.Press any key exit"
I checked Device manager and "Qualcomm HS-USB QDLoader 9008 (COM8)
I also tried to use QFIL but I don't know where to find the .mbn file to use. Please help, thanks in advance

Update: The non eu version worked for me!!! Thank you a ton!

I can also confirm this works on the Red Magic 3 without issue. I have the US version so I used the Non-EU tool. It was straight forward without any issue. This ROM finally has an app drawer!!
My phone seems very stable and runs very quick. It is also able to do OTA updates without issues. I'll comment back if I find any issues.

Oh it has issues lol. You just don't know what your looking for.
He put the disclaimer in for a reason.
Now after a few months I'll post an article about degradation lol

I'm having an issue - the program never asks to install qualcomm drivers like in the guide .docx. Just goes straight to extraction. Am I missing something?
Edit: Nevermind, it seems to be working. Must've had the drivers already installed and for some reason the phone didnt show up properly the first time.

Help me
How to use the tool bro?when I open the downloaded zip,it's always show the file is damaged.Please help.

Do I need the bootloader unlocked? Because I get Download software image fail.

wildchild048 said:
Do I need the bootloader unlocked? Because I get Download software image fail.
Click to expand...
Click to collapse
Nope, no need for unlocked bootloader. Use the Non-EU version.

Having some issues. Super bricked phone. I can get into fastboot and edl.
Tool is not working. I get an error. Download programmer fail. Using another programmer im getting firehose communication handshake failed. I know these works i used it a few times but i did switch over to a new install of windows 10 but im using pro now. 9008 driver is installed showing up in device manager.
Any ideas?

custom rom question

Hi im just new in this kind of stuffs and i dont know where to start.
Base on others said that its better to use custom rom than miui
I am afraid that i might brick my phone thats why i afraid to do it.
Im currenty playing wild rift and so far, for the past weeks im experiencing FPS drop which is so annoying.
So whats the most stable custom rom you can recomend?
and just in case something wrong happened. can i still revert it back to miui?
any topic or thread you can link in comments would be really appreciated.
thanks

I haven't done that for long so I can't give you an accurate answer, but if you brick your phone you should be able to unbrick it using Mi FlashTool. Example here: https://www.technobuzz.net/xiaomi-unbrick-guide. I've never had completely bricked a phone even though I did take very very bad decisions. And yes custom roms are lighter than MIUI. Try to find a step by step tuto.

so where should i start?
any thread you can link?

Some will say this is outdated, but I still find it a good starting point: https://forum.xda-developers.com/t/4196271/ (especially this step-by-step guide: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14; unless your preferred ROM developer tells you otherwise -- if unsure, always follow dev instructions).
After that, you could maybe proceed with the Index: https://forum.xda-developers.com/t/4176491/.

pnin said:
Some will say this is outdated, but I still find it a good starting point: https://forum.xda-developers.com/t/4196271/ (especially this step-by-step guide: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14; unless your preferred ROM developer tells you otherwise -- if unsure, always follow dev instructions).
After that, you could maybe proceed with the Index: https://forum.xda-developers.com/t/4176491/.
Click to expand...
Click to collapse
thanks bud. highly appreciated

pnin said:
Some will say this is outdated, but I still find it a good starting point: https://forum.xda-developers.com/t/4196271/ (especially this step-by-step guide: https://telegra.ph/How-to-install-Poco-x3-ROM-10-14; unless your preferred ROM developer tells you otherwise -- if unsure, always follow dev instructions).
After that, you could maybe proceed with the Index: https://forum.xda-developers.com/t/4176491/.
Click to expand...
Click to collapse
btw im getting an error opening this link https://telegra.ph/How-to-install-Poco-x3-ROM-10-14
it says error 404

pakloybaloy said:
btw im getting an error opening this link https://telegra.ph/How-to-install-Poco-x3-ROM-10-14
it says error 404
Click to expand...
Click to collapse
Just tried it, works fine from here. Try a webproxy, maybe.

pakloybaloy said:
Hi im just new in this kind of stuffs and i dont know where to start.
Base on others said that its better to use custom rom than miui
I am afraid that i might brick my phone thats why i afraid to do it.
Im currenty playing wild rift and so far, for the past weeks im experiencing FPS drop which is so annoying.
So whats the most stable custom rom you can recomend?
and just in case something wrong happened. can i still revert it back to miui?
any topic or thread you can link in comments would be really appreciated.
thanks
Click to expand...
Click to collapse
custom rom don't destroy/brick your fone, its
a) wrong kernel or right kernel taken from unpopular source (telegram groups etc)
b) flashing error due to cable or otg failure!
where to start?
1. download miui unlocker, on windows pc/laptop
2. from developer option miui12, link miui account (which you must've already signed in to, )
3. don't use wifi, use 4g sim to link account in developer options
4. shutdown device and goto fastboot mode by pressing volume downd+power button for 10+ seconds untill u see fastboot and BOT
5. runn miui unlocker and attach cable, sign in to your miui account. it will verify and give you one week waiting time! , DONOT TOUCH ANYTHING IN THE SETTINGS OR MIUI ACCOUNT NOW. after one week, unlock the device (take backup before)
6. flash recovery
7. flash rom ( i would suggest RR8.0 or HAVOC) , if you want android 11, then go for Crdroid!
8. flash google apps / or nick apps IF the rom doesn't have it!
9. keep oem firmware 90mb file handy! sometimes o translate programming language the script requires latest Fw. , you can download it from xiaomifirmwaredownloader site!
10. flash magisk if you want rooted poco
11. reboot!

Question Your device is corrupt. Oneplus 9

I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9

Flash by edl if you can't do it then pm I'll fix it by tv

Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck

applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day

SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above

rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.

I had this problem because I flashed a custom kernel on a custom rom today

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.