Related
It sucks I have to ask this. I actually left XDA because of people who decided it was no longer good enough to do it for the community and they needed to get their bills paid, but screw it, I don't feel like buying a new phone. Hardbricked after flashing the MM ROM like everyone else, tried the willcracker diag thing, looked on Google until my eyes turned red, now I'm just aggravated and ready to get this fixed... Just point me and my wallet in the right direction.
However, if you know a way that doesn't involve me having to spend my last it would be greatly appreciated. I'm hoping a good Samaritan on XDA will come to aid instead of someone looking to make a quick buck but my hands are tied here...
Sent from my draconis using Tapatalk
Oh no...
mingolianbeef said:
It sucks I have to ask this. I actually left XDA because of people who decided it was no longer good enough to do it for the community and they needed to get their bills paid, but screw it, I don't feel like buying a new phone. Hardbricked after flashing the MM ROM like everyone else, tried the willcracker diag thing, looked on Google until my eyes turned red, now I'm just aggravated and ready to get this fixed... Just point me and my wallet in the right direction.
However, if you know a way that doesn't involve me having to spend my last it would be greatly appreciated. I'm hoping a good Samaritan on XDA will come to aid instead of someone looking to make a quick buck but my hands are tied here...
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
You can't boot into a custom recovery? Otherwise you could just flash a different rom...
hallosup said:
You can't boot into a custom recovery? Otherwise you could just flash a different rom...
Click to expand...
Click to collapse
Thanks for the reply bro. The issue is that it's hard bricked, though. Nothing happens, though, not even a charge light. I'm by far no stranger to this modding gaming lol, been doing it since I was 15 and I hard bricked my Evo 3D back in the day. It goes into the QCOM 9008 mode and that's about it. The only other screen it goes to is that if I short it sometimes the screen will come on with a battery icon and a triangle with an exclamation point.
Like I said, hours of Google pointed to me having to blow money because nobody has successfully unbricked the D851 yet. Which is why I asked for the above solution. However, again, if you know another way that doesn't involve spending money please share ?
Sent from my draconis using Tapatalk
mingolianbeef said:
Thanks for the reply bro. The issue is that it's hard bricked, though. Nothing happens, though, not even a charge light. I'm by far no stranger to this modding gaming lol, been doing it since I was 15 and I hard bricked my Evo 3D back in the day. It goes into the QCOM 9008 mode and that's about it. The only other screen it goes to is that if I short it sometimes the screen will come on with a battery icon and a triangle with an exclamation point.
Like I said, hours of Google pointed to me having to blow money because nobody has successfully unbricked the D851 yet. Which is why I asked for the above solution. However, again, if you know another way that doesn't involve spending money please share
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
don't mean to get on your case or anything but why would you flash mm rom for your d851 if it's not even out for our phones yet?....
Still_living714 said:
don't mean to get on your case or anything but why would you flash mm rom for your d851 if it's not even out for our phones yet?....
Click to expand...
Click to collapse
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
mingolianbeef said:
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
well I guess it's a lesson learned lol. I get what you're saying but by doing so you still dont know how the phone might react.
mingolianbeef said:
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
Well, i am in the same or almost the same pot as you. I flashed Fulmics ROM which was supposed to give me MM. But after downloading the almost 2GB rom, i noticed that my device wasnt part of the supported devices in Aroma Installer. But i went ahead and flashed the D855 version thinking that it might work with my D851 and incase it didnt work, the worst that could happen would be the device getting stuck on the LG Splash Logo. And when that happened, all i would have to do would be to boot into recovery and restore my backup. Little did i know that the ROM dev had added tz.img,rpm.img,boot.img and modem.img to the ROM. And what this means is that, the ROM wasnt just replacing my stock KK with Fulmics, but it was also overwriting and patching my D851 tz.img,rpm.img,boot.img and modem.img with that of the D855. The ROM flashed smoothely without an error and when it finnished, i hit the reboot button. Waiting for the device to bootup up into MM, but sadly, the the device never booted again. All i get now is Battery notifications.
For example, if i connect a USB to the phone without battery inserted, i get an empty battery with a yellow triangle with an exclamation mark in the middle of the yellow triangle. And when i exhaust the battery, and i press the power button, i get presented with an empty battery notification on the screen. Thats all i ever get.
I have tried shorting the pins... which gets me into QDownloader 9008 mode but Board Diag tool doesnt seem to work on the D851. My reasons for saying this is because i helped someone who had a D855 with the Board Diag process and it was able to flash all the files. The only pain was that, after every flash with board diag, we had to disconnect the device and re-short the pins and flash the files till we flashed all the files.
But for some unkown reason, this tool wont work on our device (D851). Apparently, the D851 motherboard is different from the D855. As i compared mine with the D855.
I just hope someone makes a tool to unbrick our D851.
Is anyone trying to build lineage 15.1 for this device? I have been trying unsuccessfully for two months. I have gotten as far as like 30%. I changed a few lines here and there and got it to build a kernel but, after it builds the kernel it runs into sepolicy errors. I'm making progress but I was wondering if anyone else was trying and had knowledge we might could swap? I'm not a full fledged developer but I have made progress.
You could ask for help from previous mainteiners of this device.
https://forum.xda-developers.com/ga.../rom-octos-t3532529/post75186090#post75186090 the reply on this post said he will maintain the device he was on octos team .you can ask him for help, hope he can
https://forum.xda-developers.com/member.php?u=6264948 his page
I don't think we will ever get 15.1. Last time I checked the kernel change, it's huge. Almost you need to rewrite everything... Can't use the old stuff. To be honest, it's not hard to port a rom. You can learn it to do it yourself in probably a day. But to build a kernel, it will take a team plus many months. It's not a one man's job. Most of the kernel developers here are taking a similar device as a base and port new functions or changes. Unless we can get a similar base, I don't think we will get a kernel works for 15.1.
It's not easy but I think it's possible I keep trying in my free time that I don't seem to have alot of
I have gotten it to compile to 52%. I ran into a failed parsing overlays error and I am trying to work through this error. Alot of work and time has been invested in this I'm hoping it pays off soon.
Joker1716 said:
I have gotten it to compile to 52%. I ran into a failed parsing overlays error and I am trying to work through this error. Alot of work and time has been invested in this I'm hoping it pays off soon.
Click to expand...
Click to collapse
you can do it bro :good::victory:
Still encountering errors but I've gotten it to 75% or better. Still trying
Joker1716 said:
Still encountering errors but I've gotten it to 75% or better. Still trying
Click to expand...
Click to collapse
Awesome, bro
Sent from my Samsung SM-A520W using XDA Labs
Joker1716 said:
It's not easy but I think it's possible I keep trying in my free time that I don't seem to have alot of
Click to expand...
Click to collapse
Good luck to you. What's your base?
I've gotten all the way through the build basically. But I keep getting a recovery partition size too large error. I am trying to work it out. Not very successfully but I am still trying. I have devoted all of my free time into trying to get this done. Hopefully it's worth it. Even if it builds the Ota zip, it may still not even boot. But I am dedicated to attempting to make this happen.
I finished still gotta try to flash it. About to pass out no sleep in a while.
Wouldn't flash. Changed updater script to kinda force it to flash. It flashed but will not boot and messes up the system mounting. I guess I will go back over my device files try to work on the partitions and other stuff.
Joker1716 said:
Wouldn't flash. Changed updater script to kinda force it to flash. It flashed but will not boot and messes up the system mounting. I guess I will go back over my device files try to work on the partitions and other stuff.
Click to expand...
Click to collapse
Awesome! Glad someone is doing this for us!
Don't give up bro! And try to ask for some help.
I managed to compile the recovery it's still a little iffy but it does flash and factory reset. dirty flashing works but if you factory reset first it deletes everything and does not mount to the usb to the computer. It also does not match the assert right. what i did was unzip the d2att rom.zip , delete the assert line on the META-INF/com/google/updater-script, and re-zip to get it to flash. It did flash. haven't tried with a SD card yet. So it's not where it needs to be just yet. If you plan on messing with this recovery it will flash in TWRP under install/install image the lineage recovery will not flash an image so make sure you know how to flash one in odin, and have everything ready if you plan on going back to a different recovery. The rom i built with it flashes tries to boot up led light pulses like 7 times and then goes into download mode . Making progress but I'm going to be taking a break for a few days. AYOR I assume no responsibilty for whatever you may do to your device with this file. if you dont know what you are doing dont mess with it if you do its At Your Own Risk . Enjoy.
if anyone wants to check it out here is the download link
#Recovery
https://www.androidfilehost.com/?fid=11410932744536990805
Truly appreciate the amount of time, effort, and sleeplessness you have put into and endured for this development! :angel:
Can you not use twrp?
ibuddler said:
Good luck to you. What's your base?
Click to expand...
Click to collapse
Not really sure if I understand the question. I'm using the d2att device tree. Msm8960 board, krait architecture. I built for the klte (krait, Msm8974) which is very similar so I could see how everything goes down then compare, make changes, and wait an extremely long time for the build to compile. My computer is old. I run into .jackserver problems like there's no tomorrow. I am a landscaper I cut grass. build walls, lay sod, plans flowers,trees, dig up flowers,trees, etc. That being said I am a tad out of my element but I started doing android developmental things on my s2 and have not stopped sometimes I think smoking crack would be easier but I kinda enjoy this type of stuff. Just basically saying I have no clue what I'm doing in technical terms but I can read compare and research and maybe get something accomplished
iloveoreos said:
Can you not use twrp?
Click to expand...
Click to collapse
Yeah I can use TWRP.?? I can use what I have build a new one etc. But I'm trying to build 15.1 for the d2att and lineage recovery is included in the build
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
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.
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.