With unlocked bootloader we should be able to flash GSI. There are only two photos yet, but no instruction how to do it.
I tried yesterday flashing the image with fastboot, but ended in boot loops.
Any hint what I did wrong is welcome.
Regards,
Mart
@Mart Son
If you have fastboot commands (which you mention you do), just follow the Google Installation guide for GSI images and you'll be good to go,
Just remember to do a Factory Reset or fastboot command to wipe Userdata after the GSI flashing , or you'll end up with bootloops, plus keep in mind there is no Security options using Android 10 Google GSI image.
Yeah, I haven't wiped userdata... and ended in bootloops. In the meanwhile I read some guides and installed Android 10. When gaming it got slow and I went back to official.
Thanks @DrakenFX. I followed you since Axon7.
You did a lot for that device and I hope your knowledge will meet the Axon 10 the same
Hello,
I'm probably not posting this in the right section, nor the way it should be posted. This is my first post, and I'm sorry if this is the case.
I'll try to provide as much information as I can concerning my problem.
I have an OP7 (GM1900) that was rooted with TWRP recovery and magisk. I upgraded to OOS 10.0.3 through normal system upgrade. As I have done this many times before, I figured it wouldn't be much different. Upgrade done, everything's working but I lost the root and magisk as expected. Went back to fastboot mode, tried to boot to a temporary TWRP image, which failed (only showing fastboot logo in center of the screen). I googled, and ended up flashing both boot_a and boot_b (big mistake I know...)
Now, I'm stuck in a fastboot loop, with no access to recovery whatsoever. Nevertheless, I can still use fastboot and adb to execute command.
I figured I should download a global ROM and flash it again? I'm not sure which one to download since I didn't take note of the build beforehand and have access to nothing right now.
Is there no way to factory reset through fastboot in any way?
Thanks in advance
Update:
I made it worse by trying to flash a ROM I found on internet and totally bricked it to Qualcomm crash dump screen.
NEvertheless, everything is now solved using the MSM tool that can be found here:
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Hopefully, this will help someone with the same problem
This is MSM tool "Hydrogen" Version...
There is msm unbrick tool for OxygenOS (European & International firmware, android 9 & 10)
https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
daitalos said:
This is MSM tool "Hydrogen" Version...
There is msm unbrick tool for OxygenOS (European & International firmware, android 9 & 10)
https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
Thanks a lot ! I'll definitely download this one just in case, it could save the time going back to OOS with a local upgrade.
HI Everybody,
I have a Oneplus 8T, European, I installed lineage recovery and Lineage OS 18.1, rooted, but now I would like to reinstall Oxygen 11. Please, can you tell me how to do or where to find the answer?
Please, don't tell me to use TWRP because at moment it's not available for this smartphone.
Thank you All in advance!
You'll need to download the msm recovery tool for your device. Will take it back to new
11mackey11 said:
You'll need to download the msm recovery tool for your device. Will take it back to new
Click to expand...
Click to collapse
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I guess you could try to fastboot flash a full rom zip I think that should work. If not you can just use the MSM tool to restore.
The steps to fastboot flash a full OOS rom zip should be the same as listed in this conversion thread https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I believe it can fastboot flashed. I just haven't tried it yet. I did see another post where the steps were laid out but remember where I saw it
I am also very interested in the answer to this question. And I think I know why the answer is "use the MSM tool".
Here's how I arrived at that:
If you use payload_dumper to have a look at what gets flashed when installing a rom, there's a number of image files that aren't listed in /dev/block/by-name such as odm, product, vendor and even system(!). This means that you cannot flash them using fastboot and the only way to flash them is via fastbootd (which is in recovery.img).
So the theoretical process is:
- boot into fastboot
- flash boot, recovery, and the other "normal" partitions
- start fastbootd using "fastboot reboot fastboot"
- flash the remaining partitions
- reboot
The problem with OOS is that fastbootd looks very much like recovery: it has no ADB/fastboot connectivity. So you cannot flash the remaining partitions.
Conclusion: the MSM Tool is the only way to return.
Acknowledgment: thanks to @chandu dyavanapelli for the Evolution-X rom installer script which helped me understand what's going on. See https://forum.xda-developers.com/t/...0_r34-evolution-x-passion-22-04-2021.4266067/
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me
I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I would really appreciate it if anyone can explain the additional steps that would be required to do this on the 8T
It's a very different world with the 8T (I also come from a 3T).
The 8T has A/B partitions as well as virtual A/B partitions. It also supports streaming OTA and seamless OTA updates. It has fastboot and fastbootd.
There's lots of good information on all of this in:
Virtual A/B Overview | Android Open Source Project
source.android.com
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
platform/system/update_engine - Git at Google
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
And more on this at the same site.
And, if you get into serious trouble, the unbricking tool is really easy to use and works wonderfully.
pratyush28 said:
I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I wouls really appreciate it if anyone can explain the additional steps that would be required to do this on the same thing on an 8T.
Click to expand...
Click to collapse
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
dpryor88 said:
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
Click to expand...
Click to collapse
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
pratyush28 said:
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
Click to expand...
Click to collapse
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
dpryor88 said:
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
Click to expand...
Click to collapse
Thanks mate, I won't hesitate to ask if I need help once I get the new device
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
I have the other model. Unbrick tool works fine on mine.
pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
BillGoss said:
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
Click to expand...
Click to collapse
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
pratyush28 said:
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
Click to expand...
Click to collapse
Yes, I installed a couple of custom ROMs and they were fine.
The only place I know that matters is the xbl and xbl_config partitions. The full OOS ROMs have an extra -lp5 set of files that get flashed on lp5 phones instead of the "normal" xbl files.
But since this only applies to firmware and the xbl partitions are never touched by custom ROMs, there cannot, therefore, be incompatibilities due to lp4 vs lp5.