Hello all, similar problem to this thread:
forum.xda-developers.com/t/is-it-safe-to-re-lock-bootloader.4332733/
Help please.
My phone came with global formaware
I am thinking to flash indonesian stock firmware over global.
Is it safe to clear all and lock?
People with other Poco phones did that safely.
Not so sure about Poco F3.
Is Poco F3 global model same as indonesian?
How to check?
zpisudziad said:
Hello all, similar problem to this thread:
forum.xda-developers.com/t/is-it-safe-to-re-lock-bootloader.4332733/
Help please.
My phone came with global formaware
I am thinking to flash indonesian stock firmware over global.
Is it safe to clear all and lock?
People with other Poco phones did that safely.
Not so sure about Poco F3.
Is Poco F3 global model same as indonesian?
How to check?
Click to expand...
Click to collapse
yes they are the same, what changes is the version of the rom.
as far as I know you can not block the bootloader of a stock with a different region from the original, it goes into brick.
I personally would try it, but I'm more risky
RollDload said:
yes they are the same, what changes is the version of the rom.
as far as I know you can not block the bootloader of a stock with a different region from the original, it goes into brick.
Click to expand...
Click to collapse
I checked Poco X3 forum, member Drumfc did relocking safely on X3.
Cant understand why not on F3.
forum.xda-developers.com/t/automatic-call-recording-poco-x3.4188279/
zpisudziad said:
I checked Poco X3 forum, member Drumfc did relocking safely on X3.
Cant understand why not on F3.
forum.xda-developers.com/t/automatic-call-recording-poco-x3.4188279/
Click to expand...
Click to collapse
You know what you can try? Flash the official ROM for your phone first & lock the bootloader!
After you locked the bootloader, you can try flashing the Indian ROM, and see if it accepts the ROM.
If it doesn't let you flash the ROM, it will just show an error in Mi Flash, that way it can never brick the phone.
zpisudziad said:
Ho controllato il forum Poco X3, il membro Drumfc ha ribloccato in sicurezza su X3.
Non riesco a capire perché non in F3.
forum.xda-developers.com/t/automatic-call-recording-poco-x3.4188279/
Click to expand...
Click to collapse
I don't know what to tell you, I read in some discussions that this operation leads to brick .
@dreamytom do you like to change a phone a month? I read in a message from you that you have deleted all partitions, so I have no doubt you might try this too . Anyway, if you do, tell me how it went I'm curious
@dreamytom I wanted to ask you a question, maybe you know, I would like to switch from the stable to the weekly of xiaomi.eu, if I flash the weekly on the stable and format data, you say it works?
RollDload said:
I don't know what to tell you, I read in some discussions that this operation leads to brick .
@dreamytom do you like to change a phone a month? I read in a message from you that you have deleted all partitions, so I have no doubt you might try this too . Anyway, if you do, tell me how it went I'm curious
Click to expand...
Click to collapse
I was almost gonna mention that I once hardbricked a Poco F3 but I kind of didn't want to scare him and sound like an idiot with my great tips xD
RollDload said:
@dreamytom I wanted to ask you a question, maybe you know, I would like to switch from the stable to the weekly of xiaomi.eu, if I flash the weekly on the stable and format data, you say it works?
Click to expand...
Click to collapse
Try without formatting data first! I haven't done that myself, I was always on Weekly. But people here say it works without formatting data:
Update Xiaomi.eu from Stable to Weekly
Im using a mi 9t pro, i am on latest xiaomi.eu stable 11.0.5 MIUI 11 ANDROID 10 Can i switch to latest Xiaomi.eu Weekly without formating data or factory reset ?
xiaomi.eu
I recommend backing up your apps, messages etc. with Xiaomi's built in backup-feature, it's in Settings > My device > Back up and restore > Mobile device
If you do have to format data, you can restore from that backup and don't have to setup your apps again.
On AOSP you can use Swift Backup from Play Store, great alternative.
dreamytom said:
I was almost gonna mention that I once hardbricked a Poco F3 but I kind of didn't want to scare him and sound like an idiot with my great tips xD
Try without formatting data first! I haven't done that myself, I was always on Weekly. But people here say it works without formatting data:
Update Xiaomi.eu from Stable to Weekly
Im using a mi 9t pro, i am on latest xiaomi.eu stable 11.0.5 MIUI 11 ANDROID 10 Can i switch to latest Xiaomi.eu Weekly without formating data or factory reset ?
xiaomi.eu
I recommend backing up your apps, messages etc. with Xiaomi's built in backup-feature, it's in Settings > My device > Back up and restore > Mobile device
If you do have to format data, you can restore from that backup and don't have to setup your apps again.
On AOSP you can use Swift Backup from Play Store, great alternative.
Click to expand...
Click to collapse
it's nice to experiment, even if sometimes the experiment doesn't work very well and turns a nice phone into a very expensive paperweight but this shouldn't make your useful advice less valid, on the contrary... From experiences like yours, reading many threads, I avoided doing a lot of damage.
I'll try without formatting first and see if it creates any problems. Of course, I always do a backup before doing any modding operation, it is the basis, even if the important things are already in the cloud and in various backups on the pc, I learned the hard way by mistakenly deleting the music folder with 200 gb of albums inside , honestly I would have preferred a hardbrick.
I also tried to look for the answer in that forum, without finding it, it's a crazy mess, too messy, it's much better xda. many thanks bro! ! !
zpisudziad said:
Hello all, similar problem to this thread:
forum.xda-developers.com/t/is-it-safe-to-re-lock-bootloader.4332733/
Help please.
My phone came with global formaware
I am thinking to flash indonesian stock firmware over global.
Is it safe to clear all and lock?
People with other Poco phones did that safely.
Not so sure about Poco F3.
Is Poco F3 global model same as indonesian?
How to check?
Click to expand...
Click to collapse
On the Redmi K20 pro, every single attempt I witnessed resulted in a hard brick. Flash another region's ROM if you really want to, but DO NOT relock the bootloader while it's installed.
RollDload said:
it's nice to experiment, even if sometimes the experiment doesn't work very well and turns a nice phone into a very expensive paperweight but this shouldn't make your useful advice less valid, on the contrary... From experiences like yours, reading many threads, I avoided doing a lot of damage.
I'll try without formatting first and see if it creates any problems. Of course, I always do a backup before doing any modding operation, it is the basis, even if the important things are already in the cloud and in various backups on the pc, I learned the hard way by mistakenly deleting the music folder with 200 gb of albums inside , honestly I would have preferred a hardbrick.
I also tried to look for the answer in that forum, without finding it, it's a crazy mess, too messy, it's much better xda. many thanks bro! ! !
Click to expand...
Click to collapse
Big oof. I once lost very memorable family videos & pictures due to a partition manager failing/freezing... think it was EaseUS Partition Manager or GParted. Although that's on PC not phone. That was quite traumatising lol (and maybe irresponsible from me) :x
Do u mean the Xiaomi.eu Forum? Yeah, I started off in that forum because I had a lot of questions when I got my Poco F3 and also in regards to Android 11 because it seems quite a lot different than Android 9 (which I last used). I ended up being very confused because I couldn't quite understand how the new internal structure of Android functions, and also due to some outdated info, and having to do lots of Trial 'n Error...
I also had high hopes that I could get my previous Poco F3 back alive again, but nope. Qualcomm's Support Tool showed almost no sign of life from my Poco F3. Although one thing I didn't try is opening the back and shorting 2 points on the motherboard of the phone to reboot the Emergency Download Mode (EDL). But I don't know if that would've worked.
dreamytom said:
Big oof. I once lost very memorable family videos & pictures due to a partition manager failing/freezing... think it was EaseUS Partition Manager or GParted. Although that's on PC not phone. That was quite traumatising lol (and maybe irresponsible from me) :x
Do u mean the Xiaomi.eu Forum? Yeah, I started off in that forum because I had a lot of questions when I got my Poco F3 and also in regards to Android 11 because it seems quite a lot different than Android 9 (which I last used). I ended up being very confused because I couldn't quite understand how the new internal structure of Android functions, and also due to some outdated info, and having to do lots of Trial 'n Error...
I also had high hopes that I could get my previous Poco F3 back alive again, but nope. Qualcomm's Support Tool showed almost no sign of life from my Poco F3. Although one thing I didn't try is opening the back and shorting 2 points on the motherboard of the phone to reboot the Emergency Download Mode (EDL). But I don't know if that would've worked.
Click to expand...
Click to collapse
I understand you, it is painful to lose important data, in fact it is advisable to have multiple backups of the same files, even if this involves a considerable amount of space available, for this reason I have many HDs (most of them recovered from "old" PCs collected around ) .
yes, xiaomi.eu is a real mess, it is not listed as xda, to find the information you need, if there is you have to read almost the entire forum . actually from version 10 they have revolutionized android, (I was still at 7 with my Huawei p9 lite, still alive ). But they have simplified the updates, separating the system from the oem configuration, plus on the f3 and others there are dynamic partitions that complicate the matter even more.
I also read that to activate the edl mode you have to make a short circuit between two pins on the main pcb, but if you have actually formatted all the partitions, surely the main instructions of the bootloader are missing, including those to start edl, you tried to send it in assistance? or to look for a new motherboard or otherwise there is the option of investing a little money on a phone that maybe only the screen is broken and they sell it for a short time as spare parts, I had seen one on ebay for 100 € with the monitor in pieces and the rear glass cracked and sold it, if you can recover the mobo it settles.
RollDload said:
I understand you, it is painful to lose important data, in fact it is advisable to have multiple backups of the same files, even if this involves a considerable amount of space available, for this reason I have many HDs (most of them recovered from "old" PCs collected around ) .
yes, xiaomi.eu is a real mess, it is not listed as xda, to find the information you need, if there is you have to read almost the entire forum . actually from version 10 they have revolutionized android, (I was still at 7 with my Huawei p9 lite, still alive ). But they have simplified the updates, separating the system from the oem configuration, plus on the f3 and others there are dynamic partitions that complicate the matter even more.
I also read that to activate the edl mode you have to make a short circuit between two pins on the main pcb, but if you have actually formatted all the partitions, surely the main instructions of the bootloader are missing, including those to start edl, you tried to send it in assistance? or to look for a new motherboard or otherwise there is the option of investing a little money on a phone that maybe only the screen is broken and they sell it for a short time as spare parts, I had seen one on ebay for 100 € with the monitor in pieces and the rear glass cracked and sold it, if you can recover the mobo it settles.
Click to expand...
Click to collapse
I've noticed Google's effort to make system updates easier for OEMs, but look at this:
Implementing Virtual A/B - Patches | Android Open Source Project
source.android.com
The fact that OEMs may have to use patches to get around known potentially occuring issues for A/B to work is.. a bit strange, and indicates the whole... A/B layout thing hasn't... 'mature-rerized' yet?
(I swear that's a word, but how the heck do you write it?? I googled it, I said it into the Google app and Google Translate and they both think I'm saying "nacho rice" or "mature arrest" or whatever. I swear that is a word. I heard it multiple times, I've no idea how it's written lol)
Anyway, about my previous phone, well I got it replaced by Amazon for free. No idea what Amazon has done with that device. But I do really feel bad for bricking that device, because I don't know for certain, what Amazon is going to do with that device.
To give that phone a small chance of being repaired, I specifically said to Amazon that "a software update failed", so I hope they let engineers take a look at that phone. This way Amazon knows that it's only software, and not hardware.
I think buying a new PCB would've been hella expensive due to all the high tech in it. The EDL short-circuiting tip is good though, I've seen some YouTube videos of people doing it, but.. I was too terrified of breaking the backglass or something else, and just replaced it ^^
dreamytom said:
I've noticed Google's effort to make system updates easier for OEMs, but look at this:
Implementing Virtual A/B - Patches | Android Open Source Project
source.android.com
The fact that OEMs may have to use patches to get around known potentially occuring issues for A/B to work is.. a bit strange, and indicates the whole... A/B layout thing hasn't... 'mature-rerized' yet?
(I swear that's a word, but how the heck do you write it?? I googled it, I said it into the Google app and Google Translate and they both think I'm saying "nacho rice" or "mature arrest" or whatever. I swear that is a word. I heard it multiple times, I've no idea how it's written lol)
Anyway, about my previous phone, well I got it replaced by Amazon for free. No idea what Amazon has done with that device. But I do really feel bad for bricking that device, because I don't know for certain, what Amazon is going to do with that device.
To give that phone a small chance of being repaired, I specifically said to Amazon that "a software update failed", so I hope they let engineers take a look at that phone. This way Amazon knows that it's only software, and not hardware.
I think buying a new PCB would've been hella expensive due to all the high tech in it. The EDL short-circuiting tip is good though, I've seen some YouTube videos of people doing it, but.. I was too terrified of breaking the backglass or something else, and just replaced it ^^
Click to expand...
Click to collapse
certainly still it is a system that needs to be improved, as each new implementation needs a running-in period to be completely stable, then it must be considered that it passes through the hands of many different manufacturers so there is a greater probability that it will errors occur, I hope an ota update does not brick my phone I'm jealous, or I brick it or nothing ... then as regards the patch update speed I still have many doubts, according to the EAA version there is still the June version.
as for your old f3, i thought you still have it, great move to return it to amazon, i think they send it for service and resell it and service it quickly, if it doesn't start they open it and change the mobo. then I wouldn't worry too much, I'm sure that the 200 € of your brick f3 doesn't weigh that much on their overall annual budget
Related
I request all to first please understand the problem and give me suggestions as this gets slightly bonkers.
Thanks in advance.
So I had my OnePlus3 A3003 repaired for water Damage from a professional non OnePlus service called Yaantra. They basically replaced the Mother Board is what they say.
I have no reason to doubt, the Phone works flawlessly, everything is working nicely, from the camera to the battery performance and charging and SOT, the performance is as expected.
Only it runs on Oxygen OS 3.1.2.
Now I first got an OTA update notification for 4.5.1 and I immediately started downloading and attempted install. It went through the whole cycle of installing smoothly and after the first reboot, it splashed a linux Penguin Logo and then turned off, never turned back on. I manually pressed the power button after a long time but it again showed the Penguin for a few seconds and powered off. I figured that the phone is bricked. (this time my boot loader was Locked)
I had to follow the 2nd Method of the Mega Unbrick guide and got my phone up and running back on 3.1.2
I still get the OTA update but this time i thought I'll download the latest stable build of 5.0.1 and install it via ADB sideload. with the appropriate recovery
The phone got bricked again.
Then I thought of Installing regular TWRP after unlocking bootloader and flashed 5.0.1, No luck. had to unbrick it again.
Then I tried bluspark.
Then I flashed Experience OS with the latest firmware. It went through the entire cycle and installed but this time after it turned off and on again I was greeted to a new error.
it was in red saying "Battery does not match" in English and then in some Asian language. I was able to unbrick from that state as well.
After that I have tried Lineage OS but with same result. I get "Battery does not match"
Then I unbricked the device and i tried #*808# and checked Charger option. it says "itech_3000mah" that doesn't sound original, is it?
Basically no matter what I flash my phone gets bricked.
With Custom ROMs I get the "Battery does not match error"
With Official ROM I get the penguin Logo.
I've tried all sorts of Combination of Recovery and ROMs to no luck.
So far the only thing I haven't tried is flashing another Kernal.
Have to come back to 3.1.2 after unbricking which works flawlessly every time with no problems AT ALL. I wish to upgrade to the latest Official build of OOS (but i am ok with unofficial as well)
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
thes3usa said:
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
Click to expand...
Click to collapse
Thanks for the eyeball
AbhiM7 said:
Thanks for the eyeball
Click to expand...
Click to collapse
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
AbhiM7 said:
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
Click to expand...
Click to collapse
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
SivaMaxwell said:
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
Click to expand...
Click to collapse
I am downloading this msm recovery
https://forum.xda-developers.com/on...k-phone-msmdownloadtool-v3-0-6-t3575801/page2
and try for now.
I'll post my experience soon.
An official technician from OnePlus told me that fake batteries don't work well / won't find with OnePlus at all so there is 99% chance that it's not a mock-up.
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
zelendel said:
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
Click to expand...
Click to collapse
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
AbhiM7 said:
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
Click to expand...
Click to collapse
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
zelendel said:
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
Click to expand...
Click to collapse
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
AbhiM7 said:
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
Click to expand...
Click to collapse
That depends on how good they are but to be honest if it is a really good fake then it may fool even the best. But it cant hurt.
Actually I got stuck in the same situation. I also tried different ROMs but with custom ones I get the Replace Battery error and with official Roms I get the penguin. Is there any way to get rid of the Battery error by modifying the kernel or something?
You've a motherboard of OP3T not OP3
Try oneplus 3t full ota
Cheers
Hello users, I have my Mi Max Hydrogen 3/32 bricked since time ago, I tried all the threads out there to revive my device, as a hard bricked no fastboot, no download mode responsive, of course no recovery.
I guess that bootloader is messed due to a bad flashing of a file uploaded by error.
I found a method, idea is to force device to enter to download mode restoring bootloader or turn on responsive again to allow a new flashing cycle.
I´m now using a Redmi 5 Plus and I did this method to prevent any trouble in the future, one never knows.
If some user wants to help just I need that this zip should be flash it through recovery and the file just will dump/backup the first 125MB aproximately of system and it will kept in sdcard with the name of debrick.img and kindly can upload it to the cloud. This will be greatly appreciated and I hope that also can help to other users with same/similar issue now. If things go fine I´ll explain in details to accomplish that
View attachment Partial_Sys_Dump_for_debrick.zip
Reserved.
A brief explanation:
I have found this tutorial https://forum.xda-developers.com/showthread.php?t=2369125 (applying concerning to this model) among several of the same type, the idea behind this is that in a cell phone bricked because the bootloader is damaged and trying to boot it does not find that partition readable, so burning/writing the first lines of the operating system in a sdcard, then putting it in the device then it will search these files to try to boot. If the emmc/motherboard is not totally damaged or the measurement of the files is sufficient for it to do it then after this it will come to turn on, stay or spend a little more of the bootlogo and that will indicate that it is in a condition of flashing all the system files again through the fastboot or MiFlash to make it functional back and bring it back to life.
In my case I have damaged the buttons, the back cover opened in the repair shop and this may have a negative influence to try it properly, therefore I could not recover it yet, or the size of the files is not completely sufficient since the tutorial is based on a Galaxy S3 with a memory lower than This device or plainly emmc is definitely damaged.
However, each case is different and I think that this explanation can help others who are in similar cases.
There you go: deleted
Please, explain what you are doing even if it didn't work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
A great thanks, my device has sleeping maaaany time. I will try it and I´ll report even if this doesn´t work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
If you want to give me a second chance, I explained the idea behind this. It´s based on a device the half of ram/rom than this so I think that maybe it´s needed at least 200 mb to find working files to let it run. i´m not sure that if you are running in a custom rom and non miui rom it works anyway.
Your help is greatly appreciated and I recommend any user that can keep the zip dumper and Debrick image in a safe place just in case in the future could need it.
View attachment Partial_Sys_Dump_for_debrick-200MB.zip
hydrogen_3-32_debrick.img
Don't think this is going to work...
nijel8 said:
hydrogen_3-32_debrick.img
Don't think this is going to work...
Click to expand...
Click to collapse
Why do you think so? difference in sizes between 128 and 200 doesn´t matter? or plainly this method can´t work in this device in your opinion? I saw this method in other non Samsung devices like Lenovo totally bricked and cause is a similar device I thought that maybe..... and of course one don´t want resign.
Google sent a confirmation to grant access to your file. Thanks for support.
Oneplus finally came through with my bootloader unlocking token.Not to mention all the hoops T-Mobile had me jump through.With that being said im in possession of my very first fully rooted phone that just happens to be a 9 Pro.Any suggestions on which modules I can command Majisk to install first?How bout any general pointers thus being this is my first experience free and in full control of my 9pro.?
Here's some ideas:
What Magisk modules are you using?
Hey all moving up from my OP 7 pro to the OP 9 pro. What are all the magisk modules everyone is using on the OP 9 pro.? 1.Anything to force full screen mode on all apps? The settings for full screen apps dont include all the apps im using as...
forum.xda-developers.com
Shanemichealrowland said:
Oneplus finally came through with my bootloader unlocking token.Not to mention all the hoops T-Mobile had me jump through.With that being said im in possession of my very first fully rooted phone that just happens to be a 9 Pro.Any suggestions on which modules I can command Majisk to install first?How bout any general pointers thus being this is my first experience free and in full control of my 9pro.?
Click to expand...
Click to collapse
To be honest, I would hold off until we have a working TWRP build, especially if this is your first experience of root, etc
djsubterrain said:
To be honest, I would hold off until we have a working TWRP build, especially if this is your first experience of root, etc
Click to expand...
Click to collapse
I was thinking the same thing .I just thought maybe there are some safer mods I should do in the meantime.
@Shanemichealrowland
I've been rooting Android for many years now. I always read read and read some more before I begin to install anything and I always wait until there is a working custom recovery and make a FULL backup of every partition and transfer it to a USB drive and or my computer first thing. Make sure to backup your efs as well so that if you lose your IMEI at some point it too can them be reflashed using fastboot. These are things I've always done and will continue to always do. Many users get excited and rush out to install things and don't read enough about their device and end up with an expensive piece of plastic and glass. If you always wait and read everything and make sure you fully understand how your device works before you install things then you will always have a great experience and never have to go through the bad feeling of ruining your expensive device. I read everything in a forum about my device first. You can't go wrong doing things that way. I hope this helps. OnePlus makes great devices! I'm using my OnePlus 6t now to type this and I still love it!! Welcome to XDA my friend.
Edit added: I see you're from Houston. Me too.
flash713 said:
@Shanemichealrowland
I've been rooting Android for many years now. I always read read and read some more before I begin to install anything and I always wait until there is a working custom recovery and make a FULL backup of every partition and transfer it to a USB drive and or my computer first thing. Make sure to backup your efs as well so that if you lose your IMEI at some point it too can them be reflashed using fastboot. These are things I've always done and will continue to always do. Many users get excited and rush out to install things and don't read enough about their device and end up with an expensive piece of plastic and glass. If you always wait and read everything and make sure you fully understand how your device works before you install things then you will always have a great experience and never have to go through the bad feeling of ruining your expensive device. I read everything in a forum about my device first. You can't go wrong doing things that way. I hope this helps. OnePlus makes great devices! I'm using my OnePlus 6t now to type this and I still love it!! Welcome to XDA my friend.
Edit added: I see you're from Houston. Me too.
Click to expand...
Click to collapse
Wow,your so right. Ive already caught and stopped myself from installing a couple things I wasnt sure about.I think im gonna slow down a bit and keep learning.Thanks for bringing me back to whats should be going on.
Shanemichealrowland said:
I was thinking the same thing .I just thought maybe there are some safer mods I should do in the meantime.
Click to expand...
Click to collapse
There are Magisk modules but if you get into trouble you need to be able to access recovery, OnePlus's default recovery isn't quite as all encompassing as TWRP
djsubterrain said:
There are Magisk modules but if you get into trouble you need to be able to access recovery, OnePlus's default recovery isn't quite as all encompassing as TWRP
Click to expand...
Click to collapse
Afaik you can delete problematic magisk modules in safemode. Plus I havent used TWRP pretty much for anything with OnePlus 8 pro and after. That just helps me understand better how things work. Plus because I use Linux msm is useless to me but thats another topic
Edit: Dont get me wrong, not trying to convince people to mod/flash anything. Just pointing out that TWRP is not necessity.
pyry666 said:
Plus because I use Linux msm is useless to me but thats another topic
Click to expand...
Click to collapse
Could you clarify this? What procedure do you follow in the event of a brick? I use Linux exclusively and would prefer to be able to recover from a brick using Linux instead of relying on MSM, but I'm not clear on all the steps MSM does or where/how I would find the specifics needed to do the same thing myself.
terlynn4 said:
Could you clarify this? What procedure do you follow in the event of a brick? I use Linux exclusively and would prefer to be able to recover from a brick using Linux instead of relying on MSM, but I'm not clear on all the steps MSM does or where/how I would find the specifics needed to do the same thing myself.
Click to expand...
Click to collapse
Ive only done that once myself and that was with 6T. But basicly you need to flash every partition etc via terminal
pyry666 said:
Ive only done that once myself and that was with 6T. But basicly you need to flash every partition etc via terminal
Click to expand...
Click to collapse
Ok, I've flashed all partitions before, but I thought there was more to MSM's steps than that. E.g. fixing the partitions themselves, or some sort of voodoo required to recover from any sort of soft brick.
terlynn4 said:
Ok, I've flashed all partitions before, but I thought there was more to MSM's steps than that. E.g. fixing the partitions themselves, or some sort of voodoo required to recover from any sort of soft brick.
Click to expand...
Click to collapse
AfaIk there is not that much. It locks bootloader though and IF something goes wrong that could cause issues. One of the reasons ive never used it.
Edit: Ill correct myself. MSM uses EDL mode. And if device is borked that badly then only it works. And imo should be used only then
Edit2: One could try using virtual machine to use MSM with Linux but I have zero knowledge how that would play out
pyry666 said:
AfaIk there is not that much. It locks bootloader though and IF something goes wrong that could cause issues. One of the reasons ive never used it.
Edit: Ill correct myself. MSM uses EDL mode. And if device is borked that badly then only it works. And imo should be used only then
Edit2: One could try using virtual machine to use MSM with Linux but I have zero knowledge how that would play out
Click to expand...
Click to collapse
Right, I've been in situations with my last phone where EDL was my only option and I had to use MSM. I have dual boot on a laptop for those occasional Windows-only things like MSM. In the past I've found the USB passthrough to be unreliable for this purpose using a VM in virtualbox, though I haven't tried in a few years so it may have improved.
This isn't an urgent question. Has one of you been able to disable the forced /data encryption on the Poco F3?
I'm curious, because I've tried it many times in the past with multiple ways, to no success.
Edit: This works!: https://forum.xda-developers.com/t/...e-for-poco-f3-alioth-decryption-data.4317277/
Again out of curiosity and without rushing, what would be the benefit of removing encryption?
pegasoc said:
Again out of curiosity and without rushing, what would be the benefit of removing encryption?
Click to expand...
Click to collapse
Probably because any custom recovery needs to read /data partition without the encryption.
My old Xiaomi Mi8 and Mi11 have this problem.
dreamytom said:
This isn't an urgent question. Has one of you been able to disable the forced /data encryption on the Poco F3?
I'm curious, because I've tried it many times in the past with multiple ways, to no success.
Edit: I found a guide, will try: https://forum.xda-developers.com/t/...-decryption-data.4317277/page-2#post-85514117
Click to expand...
Click to collapse
Yes, you need to Format Data (not Wipe) and delete everythings on your device so. [ndr. TWRP offers this way easily]
Of course I suggest you to put a ROM via adb or USB to flash it suddenly after the format.
That's because format the Internal Storage produces No OS Installed error, of course.
Other than that, flash dm-verity and force-no encryption if your Xiaomi device has it.
pegasoc said:
Again out of curiosity and without rushing, what would be the benefit of removing encryption?
Click to expand...
Click to collapse
-Slight speed improvements
-Better for Power-users (or shall I say Superusers ;D) who constantly do mods
-Less problems in potentially buggy environments outside of Android (like a Custom Recovery)
zSyntex said:
Probably because any custom recovery needs to read /data partition without the encryption.
My old Xiaomi Mi8 and Mi11 have this problem.
Yes, you need to Format Data (not Wipe) and delete everythings on your device so. [ndr. TWRP offers this way easily]
Of course I suggest you to put a ROM via adb or USB to flash it suddenly after the format.
That's because format the Internal Storage produces No OS Installed error, of course.
Other than that, flash dm-verity and force-no encryption if your Xiaomi device has it.
Click to expand...
Click to collapse
Have you tried this for yourself? That doesn't work for the Poco F3. That's why I'm mentioning "for the Poco F3".
I'll try the guide I linked above, this afternoon.
dreamytom said:
-Slight speed improvements
-Better for Power-users (or shall I say Superusers ;D) who constantly do mods
-Less problems in potentially buggy environments outside of Android (like a Custom Recovery)
Have you tried this for yourself? That doesn't work for the Poco F3. That's why I'm mentioning "for the Poco F3".
I'll try the guide I linked above, this afternoon.
Click to expand...
Click to collapse
I tried with old Xiaomi Mi8, Poco F1 and F2 Pro (of my family) and Mi11.
Same hardware, same OS and methods. I don't think Poco F3 is different from them.
In fact, a lot of users of this device modded it witouth any problem.
Only problem is that you could lost, most probably, the DRMs apps like Home Banking (in Italy work without problems) and Netflix/Amazon Prime HD. Are you concerned about that, right?
zSyntex said:
I tried with old Xiaomi Mi8, Poco F1 and F2 Pro (of my family) and Mi11.
Same hardware, same OS and methods. I don't think Poco F3 is different from them.
In fact, a lot of users of this device modded it witouth any problem.
Only problem is that you could lost, most probably, the DRMs apps like Home Banking (in Italy work without problems) and Netflix/Amazon Prime HD. Are you concerned about that, right?
Click to expand...
Click to collapse
Poco F3 is different than those devices.
I'm not concerned about anything, just would like to not have encryption. I don't need it.
It's like forcing people to use BitLocker on Windows...
dreamytom said:
Poco F3 is different than those devices.
I'm not concerned about anything, just would like to not have encryption. I don't need it.
It's like forcing people to use BitLocker on Windows...
Click to expand...
Click to collapse
Well, is not different. They're all Qualcomm based, all with the same re-partition and OS.
F2 Pro, F3 and Mi11 are on the same set of Xiaomi haha.
Maybe you're new in modding, but trust me or everyone else on this forum.
For encryption, well every device above Android 7 or 8 have it of default, Google force them with the kernel, too.
zSyntex said:
Well, is not different. They're all Qualcomm based, all with the same re-partition and OS.
F2 Pro, F3 and Mi11 are on the same set of Xiaomi haha.
Maybe you're new in modding, but trust me or everyone else on this forum.
For encryption, well every device above Android 7 or 8 have it of default, Google force them with the kernel, too.
Click to expand...
Click to collapse
Bruh.
zSyntex said:
Well, is not different. They're all Qualcomm based, all with the same re-partition and OS.
F2 Pro, F3 and Mi11 are on the same set of Xiaomi haha.
Maybe you're new in modding, but trust me or everyone else on this forum.
For encryption, well every device above Android 7 or 8 have it of default, Google force them with the kernel, too.
Click to expand...
Click to collapse
Instead of lowkey calling me stupid, try it out for yourself.
Disabling Encryption does, not, work, per the usual methods on the Poco F3.
Unlike the phones you mentioned, the Poco F3 launched with Android 11 and a read-only /system.
And problems with banking apps and Netflix etc don't have anything to do with Encryption, but with SafetyNet.
dreamytom said:
This isn't an urgent question. Has one of you been able to disable the forced /data encryption on the Poco F3?
I'm curious, because I've tried it many times in the past with multiple ways, to no success.
Edit: I found a guide, will try: https://forum.xda-developers.com/t/...-decryption-data.4317277/page-2#post-85514117
Click to expand...
Click to collapse
yep there is a zip that helps disable encryption and works flawlessly, tho you need to format once after flashing it after that you can switch between roms only by wiping data. tried it on multiple roms now except hentai os, There's an xda thread on it as well ill link it ere a
m0lly. said:
yep there is a zip that helps disable encryption and works flawlessly, tho you need to format once after flashing it after that you can switch between roms only by wiping data. tried it on multiple roms now except hentai os, There's an xda thread on it as well ill link it ere a
Click to expand...
Click to collapse
disable force encryption(DFE) for Poco F3(alioth) decryption Data
decryptionData I have simplified patching for the end user as much as possible at the moment. Instructions for ROMs based on MIUI (TWRP) 1. Flash ROM_MIUI.zip 2. Flash DFE_BETA_2.zip. Follow the instructions sent to the TWRP display. 3. If you...
forum.xda-developers.com
ere ye go
he's got a tg group too. join ere too everything is explained in detail.
Thank you! I found that one as well right after I made my post. I will try it now, since at 10 pm afternoon no one is gonna call me lol
dreamytom said:
Thank you! I found that one as well right after I made my post. I will try it now, since at 10 pm afternoon no one is gonna call me lol
Click to expand...
Click to collapse
Did you try the actual fix proposed by the script author in comments?
Boot Android , run script from inside running Android and then later fastboot flash the super image that you get as output?
I was looking at it this morning lmao , I'm really curious how the fk there's such a huge coincidence for me too see your post later the same day...
I don't trust the script developer that wrote the Poco f3 thread... I am not knowledgeable enough to know where to look inside his script and see if there's any malicious code or something so I think going with what's written inside comments is the safer bet.
If you decide to go that route share with us how it went ! I'm not comfortable enough to try it just yet...
Rstment ^m^ said:
Did you try the actual fix proposed by the script author in comments?
Boot Android , run script from inside running Android and then later fastboot flash the super image that you get as output?
I was looking at it this morning lmao , I'm really curious how the fk there's such a huge coincidence for me too see your post later the same day...
I don't trust the script developer that wrote the Poco f3 thread... I am not knowledgeable enough to know where to look inside his script and see if there's any malicious code or something so I think going with what's written inside comments is the safer bet.
If you decide to go that route share with us how it went ! I'm not comfortable enough to try it just yet...
Click to expand...
Click to collapse
You mean system_rw flashable?
Yes, I did try it many months ago with an older version! I don't remember the details, but I had 2 errors while trying to flash it. The first error I somehow fixed, but the second error, I couldn't around it... I have also tried to make system read-write manually by using his instructions, but that hadn't worked out either.
I'm now formatting data and trying out the link (it looks very promising!). It also has a video guide.
After that, I'll try out "MiuiVn" and see what that MIUI Custom ROM has to offer.
dreamytom said:
You mean system_rw flashable?
Yes, I did try it many months ago with an older version! I don't remember the details, but I had 2 errors while trying to flash it. The first error I somehow fixed, but the second error, I couldn't around it... I have also tried to make system read-write manually by using his instructions, but that hadn't worked out either.
I'm now formatting data and trying out the link (it looks very promising!). It also has a video guide.
After that, I'll try out "MiuiVn" and see what that MIUI Custom ROM has to offer.
Click to expand...
Click to collapse
Nothing much... You have everything inside miui beta global + it's much more stable than custom ROM from some random Devs
I was referring to this comment :
This installation error can be avoided if /data is decrypted and mounted properly. Apparently some recoveries still have trouble doing that... This error doesn't happen if script is launched from within Android because /data partition is decrypted/mounted properly in Android.
Before running SystemRW script you can check free space in /data partition using this command in terminal:
df -h
You need at least 10+ GB to run the script properly.
I think you need to do a full boot into Android operating system as soon as you flashed a new ROM for the device to become fully operational. Maybe that's why /data partition is not mounted properly in recovery?
Maybe in next version of script I should use this path as project path:
/data/systemrw_1.32b
What do you think?
__________
If you check his original post there are instructions on how to manually flash.
@Rstment ^m^ The link @m0lly. and I mentioned works!
The script by @LeeGarChat worked flawlessly!
Hello. I've come across the serious problem with my OnePlus 9 Pro 12GB LE2125. It constantly freezes and restart itself after OOS12 update. It's absolutely unusable in OOS12 - literary works for few minutes then freeze with restart. It happens even at the stage of initial setup after factory reset. The only way to make the phone working again is rolling back to OOS 11 using factory tool - MSM Download Tool. Nothing else helps. Tried factory reset it before updates and after - the same issue. Never saw something like that. Not sure wether it's software problem at this stage. So phone works with no issues in OOS 11 only. Please help!
If even after flashing with MSM you're encountering the same problem, it may as well be sone kind if hardware problem, triggered by some specific driver in OOS12.
You got a warranty on your phone?
ekin_strops said:
If even after flashing with MSM you're encountering the same problem, it may as well be sone kind if hardware problem, triggered by some specific driver in OOS12.
You got a warranty on your phone?
Click to expand...
Click to collapse
I wouldn't ask the question if I had a warranty .
WarVic[NZ] said:
I wouldn't ask the question if I had a warranty .
Click to expand...
Click to collapse
And you got the answer technically speaking.
If I've understood correctly, now warranty on phone, caused by modding. Everything works on os11 but not os12.
What is the model and original country your phone is from?
From the feel of the thread, you've rolled back to complete original phone stock, undone all your mods, model number changes, flashed original firmware? effectively making the phone think it's back to factory settings?
Could there be something you've missed ? Is there there a guide on this forum / OnePlus community forum you can check to see if there are any additional steps?
The goal being take it 100% back to factory ( if this is even possible ) - can someone confirm if this is actually possible? I ask in that if it is sent to OnePlus, you'll have a way to pass all their warranty checks
可以尝试重新安装当前版本的oos12
Or may be a virus.., not shure..
In my case a female friend send me a link to a stupid video with whatsapp. I open the video & after i close it the phone shuts off. Just like yourse.
What i did:
1_Factory reset. No good.
2_Reinstall the OOS rom. No good.
3_Go back to OB 1. (I was on OOS OB 3 or 4) . No good.
4_MSM tool made my phone functional. After i did all the updates on OOS Stable (to rool out all the possible things i give up OB) & phone works well.
European phone model & living in Europa. Now i use ColorOS 12.1 C.61
AndyC76 said:
If I've understood correctly, now warranty on phone, caused by modding. Everything works on os11 but not os12.
What is the model and original country your phone is from?
From the feel of the thread, you've rolled back to complete original phone stock, undone all your mods, model number changes, flashed original firmware? effectively making the phone think it's back to factory settings?
Could there be something you've missed ? Is there there a guide on this forum / OnePlus community forum you can check to see if there are any additional steps?
The goal being take it 100% back to factory ( if this is even possible ) - can someone confirm if this is actually possible? I ask in that if it is sent to OnePlus, you'll have a way to pass all their warranty checks
Click to expand...
Click to collapse
No modding of any kind was ever made. It's US model LE2125. Perfectly works in Android 11 with all updates. Once the phone is updated to Android 12 it becomes unusable - freezes and restarts inself all the time, even at the stages of initial setup. The only thing helps is rolling back to Android 11 via MSM Download factory utility. Factory resets before and after update don't help. I live in New Zealand, bought the phone on eBay. I can't send it to the USA official Oneplus service for repair for obvious reasons. Pretty sure that the phone would passsed all checks and would be replaced by warranty but.... I missed nothing. Something is telling me that it's hardware related issue with is triggered by Android 12.
null0seven said:
Or may be a virus.., not shure..
In my case a female friend send me a link to a stupid video with whatsapp. I open the video & after i close it the phone shuts off. Just like yourse.
What i did:
1_Factory reset. No good.
2_Reinstall the OOS rom. No good.
3_Go back to OB 1. (I was on OOS OB 3 or 4) . No good.
4_MSM tool made my phone functional. After i did all the updates on OOS Stable (to rool out all the possible things i give up OB) & phone works well.
European phone model & living in Europa. Now i use ColorOS 12.1 C.61
Click to expand...
Click to collapse
Apart from changing OS from Oxygen to ColorOS, I tried the steps you did. Didn't help either. Againg, suspect hardware issue - some mainboard component or device is malfunctioning in Android 12.
zhijiaqu said:
可以尝试重新安装当前版本的oos12
Click to expand...
Click to collapse
I did it. Still the same issue.
WarVic[NZ] said:
No modding of any kind was ever made. It's US model LE2125. Perfectly works in Android 11 with all updates. Once the phone is updated to Android 12 it becomes unusable - freezes and restarts inself all the time, even at the stages of initial setup. The only thing helps is rolling back to Android 11 via MSM Download factory utility. Factory resets before and after update don't help. I live in New Zealand, bought the phone on eBay. I can't send it to the USA official Oneplus service for repair for obvious reasons. Pretty sure that the phone would passsed all checks and would be replaced by warranty but.... I missed nothing. Something is telling me that it's hardware related issue with is triggered by Android 12.
Click to expand...
Click to collapse
Worth logging on the official OnePlus community forum, you'll need to to a steer from the others on this thread about MSM. Perhaps leave it out for the first thread, but follow the advice of the majority.
I logged that my phone since ungrading to A12, no longer auto powers on ( scheduled ) or sounds alarm when switched off. They'll ask you to submit logs. They've confirmed it was a bug and will be addressed.