My OnePlus 6 suddenly started rebooting non-stop and is currently unusable - OnePlus 6 Questions & Answers

Good morning,
I am currently struggling even trying to diagnose what the issue is. About 2 weeks ago my OnePlus 6 (last released Android update, stock ROM, rooted) has started randomly powering off and rebooting; it only happened sporadically and didn't cause any major problems whatsoever, until a few days ago, when it started freezing and rebooting while (obviously) not under load. The first problems appeared: sometimes when it happened the device wouldn't recognise my SIM card, and sometimes upon restarting the airplane mode was on. It was frustrating to experience but still could use my phone after a few random reboots. Then the problem got worse and the Wi-Fi icon would grey out from time to time, or the Wi-Fi would simply not turn on. Left with no Internet connection (couldn't 'fix' it manually restarting the phone a couple times as I was previously able to) I decided to make a backup and tried to wipe everything, the problem still appeared and I was not able to continue. During the struggle I wiped my phone's cache but it didn't get any better nor did it stop the phone from reeboting over again, sometimes the phone would work for hours (thankfully allowing me to take a backup), sometimes it freezed right upon reaching the unlock screen. Once it started working again by simply removing the case, then the problem came back (probably a coincidence?), do you think it could be a hardware issue? I haven't found anything specific on what has happed to me on the Internet, I am hoping you kind sirs have some knowledge or experience on this exact problem that you can share with me...
Thanks in advance

Hi!
Have you tried to flash another ROM? Like LineageOS or Pixel experience?

If I am reading correctly, you didn't get a backup of the phone prior to the issue occuring, is that correct? If so then doing a restore is, most likely, not going to help as you are simply restoring the same issue back into the partitions. When I wiped out my IMEI I had a known good backup, but on a crappy SD card. This corrupted the backup, which in turn corrupted the partition that was restored from said backup. This caused the issue to persist over many restores and resets. Are you able to get a copy of your stock ROM that the phone began with, not the current update? This is the best source of untainted partition data. That is how I was able to fix my corrupted EFS partitions. This may not be the exact scenario for your particular situation, but to me it sounds software related. Hardware issues tend to be very consistent, whereas software issues are inconsistent at the best of times. Also is there anything particular that you noticed that would always make the problem occur?

Noobie the Ninja said:
If I am reading correctly, you didn't get a backup of the phone prior to the issue occuring, is that correct? If so then doing a restore is, most likely, not going to help as you are simply restoring the same issue back into the partitions. When I wiped out my IMEI I had a known good backup, but on a crappy SD card. This corrupted the backup, which in turn corrupted the partition that was restored from said backup. This caused the issue to persist over many restores and resets. Are you able to get a copy of your stock ROM that the phone began with, not the current update? This is the best source of untainted partition data. That is how I was able to fix my corrupted EFS partitions. This may not be the exact scenario for your particular situation, but to me it sounds software related. Hardware issues tend to be very consistent, whereas software issues are inconsistent at the best of times. Also is there anything particular that you noticed that would always make the problem occur?
Click to expand...
Click to collapse
I thought about that so I didn't restore my backup, I just took the backup and after the ROM was wiped the issues persisted (only reason I took a backup was for the photos, I wouldn't have restored everything that might have been corrupted).
Also I didn't notice anything particular, the problem would occur randomly, at first it seemed it was the SIM card, I removed it and it fixed it, then it came back, it was the Wi-Fi and if the phone managed to restart correctly the Wi-Fi would not turn on if tapped (also sometimes the airplane mode was on upon restarting, which of course I didn't switch on prior to reboot), then the problem seemed the case, upon removing the phone came back to life but with the same connectivity issues...
In general I can tell you I haven't found precise and reliable behaviours that led to freezing and rebooting, the problem only got worse and worse.

shiva-x said:
Hi!
Have you tried to flash another ROM? Like LineageOS or Pixel experience?
Click to expand...
Click to collapse
I was waiting for a reply before trying to flash another ROM, as I wait I might as well give that one a try...

Yes trying another ROM is not a bad idea. And lineage OS is a great ROM. HoweverI noticed with my phone I had issues that were unique to the phone only when I was using custom ROMs, as most custom ROMs are not built for my phone, I use a Moto g7 Plus. You of course using the OnePlus 6 are more likely to find a ROM that was built specifically for your phone. However, did you try to flash it back to the stock ROM? Or is that what you were referring to when you said you took the back up after it was wiped? Also just a thought but a lot of the custom ROMs are very, well customised heavy, this can lead to making narrowing down the root cause of the problem even more difficult. If you were going to flash a custom ROM, I would look towards something more on the later end of the feature heavy ROMs. If only just to remove some functions and see if the problem still persists, if it does well then you have less functions to go over as possibles.

Noobie the Ninja said:
Yes trying another ROM is not a bad idea. And lineage OS is a great ROM. HoweverI noticed with my phone I had issues that were unique to the phone only when I was using custom ROMs, as most custom ROMs are not built for my phone, I use a Moto g7 Plus. You of course using the OnePlus 6 are more likely to find a ROM that was built specifically for your phone. However, did you try to flash it back to the stock ROM? Or is that what you were referring to when you said you took the back up after it was wiped? Also just a thought but a lot of the custom ROMs are very, well customised heavy, this can lead to making narrowing down the root cause of the problem even more difficult. If you were going to flash a custom ROM, I would look towards something more on the later end of the feature heavy ROMs. If only just to remove some functions and see if the problem still persists, if it does well then you have less functions to go over as possibles.
Click to expand...
Click to collapse
I haven't managed to reflash the original ROM, I just wiped out everything, so I guess now I will begin with trying the original ROM (via reflashing) before flashing a custom one.

Leonardo Renzi said:
I haven't managed to reflash the original ROM, I just wiped out everything, so I guess now I will begin with trying the original ROM (via reflashing) before flashing a custom one.
Click to expand...
Click to collapse
It will definitely eliminate any issues that were due to customization. Also if the OnePlus has any software similar to RSA, which is the recovery and software assistant for Motorola phones, that you can use to refresh the stock ROM with it would be a good idea to start with that and then if that doesn't seem to function probably try flashing it with something like TWRP.

I tried to ADB sideload the original ROM and at 47% it said:
adb: failed to read command: No error
TWRP, on the other hand, stated 'Successful'
If I boot nothing has changed...
Edit: only thing changed is that it overwrote the recovery and now TWRP is gone

Leonardo Renzi said:
I tried to ADB sideload the original ROM and at 47% it said:
adb: failed to read command: No error
TWRP, on the other hand, stated 'Successful'
If I boot nothing has changed...
Edit: only thing changed is that it overwrote the recovery and now TWRP is gone
Click to expand...
Click to collapse
For starters, I have also noticed the 47% thing when flashing ROMs, both the original and some of the custom ones did this as well. However, that was always completed with a success message. One thing that is possible is that your stock ROM doesn't recognize TWRP, or the other way around, as using the correct procedure during flash. Do you have the .img file for your stock ROM? Also, I found more than one of the custom ROMs I tried would not boot properly, or at all even, unless I rebooted to recovery upon Comp of the initial flash. Without flashing, or reflashing TWRP, try to flash the ROM again, reboot to recovery, then reboot to the system from there. This allows the a\b system to cycle through to allow for the partitions to completely update with the new information. Only after a successful system first boot should you use fastboot to reinstall TWRP.

Noobie the Ninja said:
For starters, I have also noticed the 47% thing when flashing ROMs, both the original and some of the custom ones did this as well. However, that was always completed with a success message. One thing that is possible is that your stock ROM doesn't recognize TWRP, or the other way around, as using the correct procedure during flash. Do you have the .img file for your stock ROM? Also, I found more than one of the custom ROMs I tried would not boot properly, or at all even, unless I rebooted to recovery upon Comp of the initial flash. Without flashing, or reflashing TWRP, try to flash the ROM again, reboot to recovery, then reboot to the system from there. This allows the a\b system to cycle through to allow for the partitions to completely update with the new information. Only after a successful system first boot should you use fastboot to reinstall TWRP.
Click to expand...
Click to collapse
no biggie, I decided to flash LineageOS 19.1. While installing Open GApps, however, it tells me I have Android 11 (LineageOS 19.1 should be Android 12.1). I sideloaded the GApps for Android 11 and it says Error, status 70: Insufficient storage space available in System Partition... WTH?
Edit: this is the open_gapps_log.txt
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 11
ROM Build ID | lineage_enchilada-userdebug 12 SQ3A.220705.004 89272a802b
ROM Version increment | 2111252325
ROM SDK version | 30
ROM/Recovery modversion | 19.1-20220816-NIGHTLY-enchilada
Device Recovery |
Device Name | OnePlus6
Device Model | ONEPLUS A6003
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | true
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 450
Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | No GApps Installed
Google Camera version | Legacy
Installing GApps Zipfile | /sideload/package.zip
Installing GApps Version | 20220215
Installing GApps Type | nano
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | true[NoRemove]
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | true[NoRemove]
Ignore Google Package Installer | false[PackageInstallerGoogle]
Ignore Google NFC Tag | true[NoRemove]
Ignore Google WebView | true
Total System Size (KB) | 2837072
Used System Space (KB) | 2629400
Current Free Space (KB) | 191288
Additional Space Required (KB) | 390972 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
NOTE: The Stock/AOSP WebView is not available on your
ROM (anymore), not all Google WebViewProviders will be removed.
NOTE: The Stock/AOSP NFC Tag is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Keyboard is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Contacts is not available on your
ROM (anymore), the Google equivalent will not be removed.
!!! WARNING !!! - Duplicate files were found between your ROM and this GApps
package. This is likely due to your ROM's dev including Google proprietary
files in the ROM. The duplicate files are shown in the log portion below.
# Begin GApps <> ROM Duplicate File List
/system/app/GoogleExtShared
/system/app/GooglePrintRecommendationService
/system/priv-app/GooglePackageInstaller
# End GApps <> ROM Duplicate File List
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 191288 | 191288
Remove | Existing GApps | + 3284 | 194572
Remove | Obsolete Files | + 119228 | 313800
Remove | androidauto | + 0 | 313800
Remove | extservicesstock | + 0 | 313800
Remove | extsharedstock | + 0 | 313800
Remove | packageinstallerstock | + 0 | 313800
Remove | provision | + 0 | 313800
Install | Core | - 227284 | 86516
Install | batteryusage | - 6788 | 79728
Install | calsync | - 2396 | 77332
Install | dialerframework | - 12 | 77320
Install | gearheadstub | - 3168 | 74152
Install | googletts | - 62180 | 11972
Install | markup | - 8252 | 3720
Install | packageinstallergoogle | - 3144 | 576
Install | search | - 321668 | -321092
Install | soundpicker | - 6184 | -327276
Install | speech | - 39128 | -366404
Install | wellbeing | - 15352 | -381756
| Buffer Space | - 9216 | -390972
------------------------------------------------------------------
Additional Space Required | 390972
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
Edit 2: I eventually installed GApps pico package
Edit 3: First LineageOS boot, say hello to QUALCOMM CrashDump Mode...
No message, just a freeze and the bare QUALCOMM CrashDump Mode phrase.

Leonardo Renzi said:
no biggie, I decided to flash LineageOS 19.1. While installing Open GApps, however, it tells me I have Android 11 (LineageOS 19.1 should be Android 12.1). I sideloaded the GApps for Android 11 and it says Error, status 70: Insufficient storage space available in System Partition... WTH?
Edit: this is the open_gapps_log.txt
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 11
ROM Build ID | lineage_enchilada-userdebug 12 SQ3A.220705.004 89272a802b
ROM Version increment | 2111252325
ROM SDK version | 30
ROM/Recovery modversion | 19.1-20220816-NIGHTLY-enchilada
Device Recovery |
Device Name | OnePlus6
Device Model | ONEPLUS A6003
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | true
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 450
Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | No GApps Installed
Google Camera version | Legacy
Installing GApps Zipfile | /sideload/package.zip
Installing GApps Version | 20220215
Installing GApps Type | nano
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | true[NoRemove]
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | true[NoRemove]
Ignore Google Package Installer | false[PackageInstallerGoogle]
Ignore Google NFC Tag | true[NoRemove]
Ignore Google WebView | true
Total System Size (KB) | 2837072
Used System Space (KB) | 2629400
Current Free Space (KB) | 191288
Additional Space Required (KB) | 390972 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
NOTE: The Stock/AOSP WebView is not available on your
ROM (anymore), not all Google WebViewProviders will be removed.
NOTE: The Stock/AOSP NFC Tag is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Keyboard is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Contacts is not available on your
ROM (anymore), the Google equivalent will not be removed.
!!! WARNING !!! - Duplicate files were found between your ROM and this GApps
package. This is likely due to your ROM's dev including Google proprietary
files in the ROM. The duplicate files are shown in the log portion below.
# Begin GApps <> ROM Duplicate File List
/system/app/GoogleExtShared
/system/app/GooglePrintRecommendationService
/system/priv-app/GooglePackageInstaller
# End GApps <> ROM Duplicate File List
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 191288 | 191288
Remove | Existing GApps | + 3284 | 194572
Remove | Obsolete Files | + 119228 | 313800
Remove | androidauto | + 0 | 313800
Remove | extservicesstock | + 0 | 313800
Remove | extsharedstock | + 0 | 313800
Remove | packageinstallerstock | + 0 | 313800
Remove | provision | + 0 | 313800
Install | Core | - 227284 | 86516
Install | batteryusage | - 6788 | 79728
Install | calsync | - 2396 | 77332
Install | dialerframework | - 12 | 77320
Install | gearheadstub | - 3168 | 74152
Install | googletts | - 62180 | 11972
Install | markup | - 8252 | 3720
Install | packageinstallergoogle | - 3144 | 576
Install | search | - 321668 | -321092
Install | soundpicker | - 6184 | -327276
Install | speech | - 39128 | -366404
Install | wellbeing | - 15352 | -381756
| Buffer Space | - 9216 | -390972
------------------------------------------------------------------
Additional Space Required | 390972
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
Edit 2: I eventually installed GApps pico package
Edit 3: First LineageOS boot, say hello to QUALCOMM CrashDump Mode...
No message, just a freeze and the bare QUALCOMM CrashDump Mode phrase.
Click to expand...
Click to collapse
Hello sorry about the delay in the response. Speak to my phone and hopefully it types the right things. I do know about the Google apps or g apps if you will causing the needs more space issue if you downloaded anything other than the nano your system partition tends to have not enough space whether it actually does or not I had over a gigs worth of space on my system partition when I installed g ups once the GF file itself was only 300 megs yet because it wasn't the smaller version if you will it fail to install try downloading the micro or nano versions of the G apps and install that. Spilling things out correctly I do apologize for the terrible misspellings however I do not have time to edit with the old fashioned keyboard if I am unclearing anything please ask me and I will try to clarify

Noobie the Ninja said:
Hello sorry about the delay in the response. Speak to my phone and hopefully it types the right things. I do know about the Google apps or g apps if you will causing the needs more space issue if you downloaded anything other than the nano your system partition tends to have not enough space whether it actually does or not I had over a gigs worth of space on my system partition when I installed g ups once the GF file itself was only 300 megs yet because it wasn't the smaller version if you will it fail to install try downloading the micro or nano versions of the G apps and install that. Spilling things out correctly I do apologize for the terrible misspellings however I do not have time to edit with the old fashioned keyboard if I am unclearing anything please ask me and I will try to clarify
Click to expand...
Click to collapse
As mentioned in the edits I eventually managed to install the pico GApps file, but now the problem is the SIM still doesn't get recognized, the Wi-Fi won't turn on and the system crashes are back, this time accompanied by the QUALCOMM CrashDump Mode (no message, it just freezes, the OS crashes and the CrashDump mode appears).
Don't worry abouut your response time, you're the only one replying afterall.

Leonardo Renzi said:
As mentioned in the edits I eventually managed to install the pico GApps file, but now the problem is the SIM still doesn't get recognized, the Wi-Fi won't turn on and the system crashes are back, this time accompanied by the QUALCOMM CrashDump Mode (no message, it just freezes, the OS crashes and the CrashDump mode appears).
Don't worry abouut your response time, you're the only one replying afterall.
Click to expand...
Click to collapse
Does the USDD code *#*#4636#*#* work on your phone? Done through the dialer. If so are any of the fields blank or obviously missing information? It's the testing menu, look under phone information. Here's the main menu from my phone.

I had a chance to look at a few places and I found some of the codes that are specific to your phone.
OnePlus 6 secret codes
mobilespecs.net
This site has many codes that are supposed to give you access to various testing menu to run diagnostics on your phone and it's hardware. I do recommend caution while exploring these menus as they are designed for use only by developers and engineers. Please keep me posted on the development of your issue. I also have an email that I created just for giving to XDA members
[email protected]
If you need to pm me.

Noobie the Ninja said:
Does the USDD code *#*#4636#*#* work on your phone? Done through the dialer. If so are any of the fields blank or obviously missing information? It's the testing menu, look under phone information. Here's the main menu from my phone.
Click to expand...
Click to collapse
Here's the Phone info section

Leonardo Renzi said:
Here's the Phone info section
Click to expand...
Click to collapse
Now see, now we are getting somewhere. Where I'm not 100% yet but we are not stagnant. So with some of those fields being blank I want to ask you about where you are from, it really does pertain to the topic and what can come about from it would you mind sending me an email to [email protected] so I can not have to ask some questions that might be best done in a less public environment. If you would like, I have an email service that I am owner/admin of and have created an email to loan to people to help keep their privacy in tact while still being able to send PM's the account info is:
Webmail: https://webmail.dynu.com/
Username: [email protected]
Password: [email protected]$5word
Please let me know what you decide as I had this very issue with my phone and no one was willing to help so I had to figure it out myself. All the whole everyone was telling me to give up and send it in or just buy a new phone. I would just like to not be that kind of tech. I primarily do pc repair Linux and windows systems.

Noobie the Ninja said:
Now see, now we are getting somewhere. Where I'm not 100% yet but we are not stagnant. So with some of those fields being blank I want to ask you about where you are from, it really does pertain to the topic and what can come about from it would you mind sending me an email to [email protected] so I can not have to ask some questions that might be best done in a less public environment. If you would like, I have an email service that I am owner/admin of and have created an email to loan to people to help keep their privacy in tact while still being able to send PM's the account info is:
Webmail: https://webmail.dynu.com/
Username: [email protected]
Password: [email protected]$5word
Please let me know what you decide as I had this very issue with my phone and no one was willing to help so I had to figure it out myself. All the whole everyone was telling me to give up and send it in or just buy a new phone. I would just like to not be that kind of tech. I primarily do pc repair Linux and windows systems.
Click to expand...
Click to collapse
Just wanting to clarify that depending on where in the world you are at Some of the questions I have next can have legal issues. They do not here in the US where I am at, but I don't know where you are and I don't want to say the wrong thing in a public forum.

Noobie the Ninja said:
Just wanting to clarify that depending on where in the world you are at Some of the questions I have next can have legal issues. They do not here in the US where I am at, but I don't know where you are and I don't want to say the wrong thing in a public forum.
Click to expand...
Click to collapse
I understand if you do not want to communicate privately so I will ask this and determine how to proceed. Is any of the information (ie. The numbers that are missing from the phone information menu) protected by laws that, whether by accident or on purpose, if changed can cause you to have any legal trouble? I ask this very serious question because I would like to help you but not at the risk of you getting in trouble. If you cannot say just simply thank me for my time and I will recommend you get a new device. I just recently fixed this very complex issue with my phone and it was incredibly difficult to get any information on the subject, so I know how sending it is. Please let me know how you would like to proceed.

Well, I am not sure if you will read this but here's what has most likely happened to your device; the partition system that android devices employ is comprised of dozens of different partitions that all have a unique role to play. Boot, system, a few data(user files being one), vendor, oem, and so on. Most have two now for the A/B devices. This is so that updates can take place while the system is operating without having to unmount the partitions. There is a pair of partitions labeled EFS or "modema" & "modemb" these partitions contain, among other critical data, the IMEI or at least the function used to write the software copy of it. This is when the phone reads the firmware, or burned in, IMEI and passes it to the OS. The problem that happened, as did in my case, is that if those partitions become corrupted then they fail to pass the correct information to the OS. This means that the system no longer is getting an IMEI number assigned at boot like normal. As it is pertinent to have not only a valid, but matching IMEI to access cell service you will have no service at all without an IMEI. This can easily be confirmed by booting to the bootloader and checking the IMEI that the bootloader can see, and then booting to the system and running the code *#06# from the dialer(or the "06" variant specific to your device) and seeing how they compare. If the bootloader has the correct IMEI and the system does not, then your device is loading corrupted partitions at boot. This can be solved by getting a valid copy of the ROM that your device began with (The one it left the factory for the first time with). You must then flash the ROM to all partitions (both a and b if applicable) without rebooting until all partitions have been reset to factory standards. Once this has been done a simple reboot should be all that is necessary to get the IMEI back. In some cases a new SIM is required in order to get cell service again. If you check the bootloader, however, and it does not either have the correct IMEI or none at all, then your firmware has been damaged and will need to be replaced. This can only be done with specialized equipment and will most likely be rather expensive. Hopefully this covers the extent of this issue, and that there is no major legal issues to deal with over having changed (whether by accident or not) the IMEI number in your local area. And finally, good luck, this is more information in one place then I could ever find so I hope it helps.

Related

OFFICIAL RELEASE [ROM][5.0.1][cm12 unofficial] [LG-P920] Rom Lolli-P920

OFFICIAL [ROM][5.0.1][cm12 unofficial] [LG-P920] Rom Lolli-P920
ROM name: Lolli-P920
Version Android: 5.0.1 Lollipop
CM version: 12
Hello everyone and sorry for my poor English. I just wanted to inform you of all the features that will have this new rom:
-new Lancher Lollipop
-Android 5.0.1 installed (unofficial)
-new keyboard
-new status bar
-new applications (music, gallery, camera, etc ...)
-Improved wifi, internet browsing, resolution camera, video, streaming video
-Resolution images improved to 100%
-speed system improved by 15%
-Improved sleep mode
-best battery life
-Wireless boosted by 10%
-Improved scan wifi
-new home screen lollipop
- and much more...
------PLEASE READ ALL!!!------
as already I mentioned in my previous post this ROM will install Android 5.0.1 lollipop on our phone. The ROM based on Android 4.1.2 system, in fact, are the main features of andorid 4.1.2, but in practice, and a kind of amalgamation of andorid jelly beans and lollipop.
one of the first features found when you go to turn on the phone and the Manu phone unlock style andorid jelly beans but for practicality and speed are those of Android lollipop. another thing you notice, and the reaction of the system when you go to open an application. then there are other things that make this a unique ROM, that is all based on CyanogenMod 10 and 12 and of course a version modified by me personally and by other developers (Zeta99 and Unity Team).
Now I show you a list of all the new features:
-speed battery charge increased by 30%, comparable "almost" to that of the Samsung Galaxy S6;
-Stability system increased by 10%;
-the improvement of the streaming video and the reaction of the system;
-possibility to increase the RAM phone attraverso swaps that do not create any problems or crash the system;
-possibility to download almost all apps except those that are officially Android lollipop;
-new app including Xposed modules that enhance both the graphics and the phone is its performance;
-all phone app have been partially modified to make it so it is not wasted too much RAM or battery;
-autonomy battery stable (however advise you not straining too much, otherwise it leads to serious problems for both the battery and the phone is);
-and many other new features ...
BUT I'M SORRY tell you, but I HAD PROMISED THAT THE 3D IN A POST PAST ARE NOT ABLE TO PUT IT, WHY PHONE FIRST IS ABLE TO Protect it BUT THEN AFTER A FEW SECONDS WENT IN CRASH AND THEN I WAS FORCED TO REMOVE it, but never say never, in fact it may be that in a future update of the phone to be able to insert, without creating crash the phone. However, I can announce that soon will come two new updates:
-one that will bring Android 5.0.2, with some improvements and fixes minor bugs;
-one that will bring Android 6.0 Marshmallow, with major changes to most of the system is perhaps our dear beloved 3D!!!
the installation file weighs about 780 mb so I recommend you also leave free 2 GB to make room also backup and emergency system otherwise do my (recommended version 4.2.2 pacman).
But now I'll explain how to install the ROM on your LG-P920:
-for the first thing we connect our phone via USB cable to our PC;
-So We copy the RAR ROM Lolli 5.0.1.rar (extracts the desktop) files in the main memory of the phone where we have the backup folder clockworkmod (if there is you then do this: press the power button + volume button upwards , the phone will reboot into recovery mode and you have a couple of options available to us we need backup and restore, let's go on with the volume keys and confirming with the power button, and go to select up and he will make us a backup version and all files, settings, etc ... we have in the phone, you now have the backup folder). "To download clockworkmod clockworkmod.apk write on the internet and download the apk file on your phone."
-after clockworkmod downloaded on our phone we turn off our phone is press the power button + volume button upwards, the phone will reboot into recovery mode and you have a couple of options, we need to us "wipe cache partition "and" wipe data / factory reset ".
-Let's go first to wipe cache partition and run it and after aniamo to wipe data / factory reset and run it.
-Now go to "backup and restore" with the volume keys and confirming with the power button, and then select Restore and select ROM Lolli 5.0.1
- After confirming with the power button the phone will install the package there, waiting lob install the package and now we will have our phone with Android 5.0.1 (unofficial) installed
CAUTION:
1. do not install the "gapps.rar" files because the applications we need are already in the system rar files.
2. Before installing the system, make a backup "total!" our current system (pictures, music, contacts, messages, etc ..) and save it on your computer.
3. in addition to the system that you want to download mettetene also one of "emergency", because if the current gaming system that you downloaded does not work, bring in recovery mode system and install the emergency system and then install the backup you made before .
4. for every problem in the messages ask and I'll try to make a general answer to the problem you have.
5. do not totally rely on the system (for everyday use) because there are still some problems that I will solve in the future with new versions that come out.
6. the phone is responsive to commands you give it to avoid thermal warming much will always recommend every6. the phone is responsive to commands you give it to avoid thermal warming much will always recommend every time you use an app to close it when you do not need or use CLEANMASTER or other application to clean the remaining ram.
7. Enjoy your phone updated
download and ROM image
| | | |
| | | |
| | | |
\/ \/
Download ROM (MediaFire): http://www.mediafire.com/download/c63tffjv76szryy/ROM+Lolli+5.0.1+(unofficial).zip
The website where to find the images of the ROM: http://azzurro2013.jimdo.com/tecnologia/smartphone/area-download-1/
Thanks to all for the support that we are giving you and goodbye to David G., Zeta99 and UnityTeam
Thread exists for this here:
http://forum.xda-developers.com/android/general/rom-rom-lolli-p920-t3225330
Please don't create duplicate threads.
Thread closed.

OFFICIAL [ROM][5.0.1][cm12 unofficial] [LG-P920] Rom Lolli-P920

ROM name: Lolli-P920
Version Android: 5.0.1 Lollipop
CM version: 12
Hello everyone and sorry for my poor English. I just wanted to inform you of all the features that will have this new rom:
-new Lancher Lollipop
-Android 5.0.1 installed (unofficial)
-new keyboard
-new status bar
-new applications (music, gallery, camera, etc ...)
-Improved wifi, internet browsing, resolution camera, video, streaming video
-Resolution images improved to 100%
-speed system improved by 15%
-Improved sleep mode
-best battery life
-Wireless boosted by 10%
-Improved scan wifi
-new home screen lollipop
- and much more...
------PLEASE READ ALL!!!------
as already I mentioned in my previous post this ROM will install Android 5.0.1 lollipop on our phone. The ROM based on Android 4.1.2 system, in fact, are the main features of andorid 4.1.2, but in practice, and a kind of amalgamation of andorid jelly beans and lollipop.
one of the first features found when you go to turn on the phone and the Manu phone unlock style andorid jelly beans but for practicality and speed are those of Android lollipop. another thing you notice, and the reaction of the system when you go to open an application. then there are other things that make this a unique ROM, that is all based on CyanogenMod 10 and 12 and of course a version modified by me personally and by other developers (Zeta99 and Unity Team).
Now I show you a list of all the new features:
-speed battery charge increased by 30%, comparable "almost" to that of the Samsung Galaxy S6;
-Stability system increased by 10%;
-the improvement of the streaming video and the reaction of the system;
-possibility to increase the RAM phone attraverso swaps that do not create any problems or crash the system;
-possibility to download almost all apps except those that are officially Android lollipop;
-new app including Xposed modules that enhance both the graphics and the phone is its performance;
-all phone app have been partially modified to make it so it is not wasted too much RAM or battery;
-autonomy battery stable (however advise you not straining too much, otherwise it leads to serious problems for both the battery and the phone is);
-and many other new features ...
BUT I'M SORRY tell you, but I HAD PROMISED THAT THE 3D IN A POST PAST ARE NOT ABLE TO PUT IT, WHY PHONE FIRST IS ABLE TO Protect it BUT THEN AFTER A FEW SECONDS WENT IN CRASH AND THEN I WAS FORCED TO REMOVE it, but never say never, in fact it may be that in a future update of the phone to be able to insert, without creating crash the phone. However, I can announce that soon will come two new updates:
-one that will bring Android 5.0.2, with some improvements and fixes minor bugs;
-one that will bring Android 6.0 Marshmallow, with major changes to most of the system is perhaps our dear beloved 3D!!!
the installation file weighs about 450 mb so I recommend you also leave free 1 GB to make room also backup and emergency system otherwise do my (recommended version 4.2.2 pacman).
But now I'll explain how to install the ROM on your LG-P920:
-for the first thing we connect our phone via USB cable to our PC;
-So We copy the RAR ROM Lolli 5.0.1.rar files in the main memory of the phone where we have the backup folder clockworkmod (if there is you then do this: press the power button + volume button upwards , the phone will reboot into recovery mode and you have a couple of options available to us we need backup and restore, let's go on with the volume keys and confirming with the power button, and go to select up and he will make us a backup version and all files, settings, etc ... we have in the phone, you now have the backup folder). "To download clockworkmod clockworkmod.apk write on the internet and download the apk file on your phone."
-after clockworkmod downloaded on our phone we turn off our phone is press the power button + volume button upwards, the phone will reboot into recovery mode and you have a couple of options, we need to us "wipe cache partition "and" wipe data / factory reset ".
-Let's go first to wipe cache partition and run it and after aniamo to wipe data / factory reset and run it.
-Now go to "backup and restore" with the volume keys and confirming with the power button, and then select Restore and select ROM Lolli 5.0.1.rar
- After confirming with the power button the phone will install the package there, waiting lob install the package and now we will have our phone with Android 5.0.1 (unofficial) installed
CAUTION:
1. do not install the "gapps.rar" files because the applications we need are already in the system rar files.
2. Before installing the system, make a backup "total!" our current system (pictures, music, contacts, messages, etc ..) and save it on your computer.
3. in addition to the system that you want to download mettetene also one of "emergency", because if the current gaming system that you downloaded does not work, bring in recovery mode system and install the emergency system and then install the backup you made before .
4. for every problem in the messages ask and I'll try to make a general answer to the problem you have.
5. do not totally rely on the system (for everyday use) because there are still some problems that I will solve in the future with new versions that come out.
6. the phone is responsive to commands you give it to avoid thermal warming much will always recommend every6. the phone is responsive to commands you give it to avoid thermal warming much will always recommend every time you use an app to close it when you do not need or use CLEANMASTER or other application to clean the remaining ram.
7. Enjoy your phone updated
download and ROM image can be found under the next message
| | | |
| | | |
| | | |
\/ \/
Download ROM (MediaFire): http://www.mediafire.com/download/c63tffjv76szryy/ROM+Lolli+5.0.1+(unofficial).zip
The website where to find the images of the ROM: http://azzurro2013.jimdo.com/tecnologia/smartphone/area-download-1/
Thanks to all for the support that we are giving you and goodbye to David G., Zeta99 and UnityTeam
Thread exists for this here:
http://forum.xda-developers.com/android/general/rom-rom-lolli-p920-t3225330
Please don't create duplicate threads.
Thread closed.
Thread exists for this here:
http://forum.xda-developers.com/android/general/rom-rom-lolli-p920-t3225330
Please don't create duplicate threads.
Thread closed.

[ROM] AOSP 7.x for Galaxy S 4G

Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
It will wipe your entire SD card! In order to make things work better, I've set it up to use the entire SD card as /data as opposed to having two partitions. The advantage is that you don't have to pick a size of /data.
If on a BML rom (stock-based GB)...
Untested, but is setup to hopefully work. If it doesn't flash my 6.0 Omni first
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash according to instructions in Post #3
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 20+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features"
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico works on the latest 7.0 build, untested on 7.1 but should work just fine
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Camera (built-in app needs workaround, see below)
RIL
SMS
Recovery
Bluetooth - first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P, untested on T959V
Headset Buttons
SElinux in enforcing mode - this may have broken the T959V's gps...
Partially working
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
AOSP 7.x for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Created 2016-10-22
Last Updated 2016-10-21
Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds for your desired android version (7.0 or 7.1). Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b BRANCH" where BRANCH is either aosp-7.0 or aosp-7.1. Continue on with the build guide, the device codename you want is "galaxys4gmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxys4gmtd-kernel
Other aries devices (captivate, i9000, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work.
Changelogs
Changelog for 2016-12-19
December security patches
goes back to the older graphics drivers so hardware recording works but has a kernel patch to prevent crashes
Tweaked the graphics drivers options so it seems a little bit faster
Tweaked the RIL a little bit for better stability
Other things I've forgotten about, see github for details
Changelog for 2016-12-19-V2
Kernel without slowdowns....
Changelog for 2017-1-19
selinux to enforcing - this may break the T959V's GPS - if it does, let me know and send me a dmesg and I'll fix it
Update to the interactive governor - should have less slowdowns if using the default governor
Slightly better RIL reliability (I think)
Better low memory killing - we now don't run out of memory as often
Hardware decoding re-enabled
Slightly less intensive background services
Based on 7.1.1_r13
Source Code, Downloads, Root Options
Main Source
https://android.googlesource.com/
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see aosp-7.x branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see aosp-7.x branch).
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see aosp-7.x branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see aosp-7.x branch)
http://github.com/xc-racer99/android_patches for all the patches necessary for the device to work properly (see aosp-7.x branch)
Downloads!
All builds can be downloaded from AndroidFileHost at https://www.androidfilehost.com/?w=files&flid=58191
Gapps
The smallest http://opengapps.org/ package for 7.0 is known to work, but any small 7.0 gapps package should work. However, they will cause the device to slowdown significantly as they use a fair bit of RAM. Gapps are untested on 7.1
This ROM is compatible with MicroG (https://microg.org/ and http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616) gapps. This is an open-source reimplementation of Google Play Services that doesn't track you and uses way less battery than the original.
Root
Root is achieved via Magisk or SuperSU.
MagiskDue to our odd partition layout, you need to use my custom Magisk install zip (source code here) attached to this post and not the official install or the Magisk Manager install. Then follow the instructions on how to root/install other modules from http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Also, don't try to use the official Magisk uninstall tool as it won't work.
SuperSU
Please note: I've been told this doesn't work any more, YMMV
Again, we need a custom SuperSU install zip for it to work due to our partition scheme. It should be an all-in-one zip so it's simplier than Magisk (but not open source). This is based off of the latest (at time of writing) 2.79SR1 release, the diff is below
Code:
diff --git a/META-INF/com/google/android/update-binary b/META-INF/com/google/android/update-binary
index d437f6f..3a312bf 100644
--- a/META-INF/com/google/android/update-binary
+++ b/META-INF/com/google/android/update-binary
@@ -642,16 +642,23 @@ detect_systemless_required() {
find_boot_image
CONTINUE=true
+if false ; then
if [ -z "$BOOTIMAGE" ]; then
# no boot image partition detected, abort
return
fi
+fi
# extract ramdisk from boot image
rm -rf /sutmp
mkdir /sutmp
+if false ; then
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if (! $CONTINUE); then return; fi
@@ -1331,6 +1338,8 @@ else
ui_print_always "Boot image patcher"
ui_print "******************"
+if false ; then
+ # SGS Modification - we don't have a "real" boot image
ui_print "- Finding boot image"
find_boot_image
@@ -1357,6 +1366,10 @@ else
fi
check_zero_def "- Extracting ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero_def "- Decompressing ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if ($CONTINUE); then
@@ -1545,6 +1558,7 @@ else
check_zero_def "- Calling user boot image patch script" "sh /data/custom_boot_image_patch.sh /sutmp/boot.img"
fi
+if false ; then
if ($CONTINUE); then
DEV=$(echo `resolve_link $BOOTIMAGE` | grep /dev/block/)
if [ $? -eq 0 ]; then
@@ -1564,6 +1578,10 @@ else
dd if=/sutmp/boot.img of=$BOOTIMAGE bs=4096
fi
+else
+ cp /sutmp/ramdisk.packed /ramdisk/ramdisk.img
+ umount /ramdisk
+fi
rm -rf /sutmp
fi
Link for the download ROM is not working... it is private... ?!?
Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191
pickandrew said:
Link for the download ROM is not working... it is private... ?!?
Click to expand...
Click to collapse
Shaggy_thecat said:
Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191
Click to expand...
Click to collapse
Thanks, I used the link that I would use if I was already logged in, my bad. OP is now updated.
It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?
graycow9 said:
It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?
Click to expand...
Click to collapse
Hmm, flash the ROM, go into recovery, change the filesystem of /data to ext4 or f2fs. The error sounds as if the sdcard is formatted as fat while it shouldn't be. If that doesn't work, please send me the contents of /sdcard/aries_mtd.log after you've installed it.
Hadn't noticed the new "persistent logging" section. I suspect that what it does it keep the logcat contents over a reboot. Since the logcat does have a max size, it is probably safe to enable it. I highly doubt it contains any more info than a regular logcat.
Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.
Domunus said:
Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.
Click to expand...
Click to collapse
Ok, sounds like a messed up somewhere. I'll do some testing and try to release an updated build. Could you please post the output of /sdcard/aries_bml.log and /sdcard/aries_mtd.log? The "Encryption Unsuccessful" message sounds as if the SD wasn't properly formatted to ext4/f2fs.
Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?
Domunus said:
Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?
Click to expand...
Click to collapse
Odd, I thought my install script removed the extra partition.
Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Doesn't work....
I'll try to do some more testing with gapps and from stock with 1 or 2 partitions when I get a chance.
I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling. ?
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app
graycow9 said:
I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling.
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, I get a bad handshake as well. Only happens with hotmail/oulook accounts, my gmail and my other email work just fine.
I figured out what was causing the issues with install from BML - on TWRP boot, it wasn't setting up the sdcard properly. I've now fixed it so that it should work regardless (in the next build, obviously).
Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Click to expand...
Click to collapse
Gave this a try and still no luck.
Update **
It actually killed the recovery. Recovery just keeps crashing and rebooting when trying to get in to it. Tried it from the a clean install and same results. Will wait for your next build. Thanks for putting time in to this!
Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore ?? (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build ?
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app
graycow9 said:
Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
I've never used the contact sync.
With SIM not registering, it's because Google introduced a bug and the workaround the bug causes the SIM to occasionally not work. One of the problems with legacy devices I guess.
With the files not saving, manually grant the storage permission in Settings->Apps - it doesn't seem to automatically update for most apps.
With root, sounds like I should modify the SuperSU install zip as it's easier to use (but not open-source). For the PHH Superuser, you need
1) The Magisk-7-SGS.zip from my thread.
2) The phh-superuser-r259.zip from the Magisk root thread (link in OP)
3) The PHH Superuser app from the Play Store or FDroid
Even then, it only works for certain apps as it doesn't mount anything to /system/xbin/su which is what some apps look for
Edit: And I have no issues if you keep posting here with the problems you find, it's good to know.
bootloop
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?
asmalldharma said:
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?
Click to expand...
Click to collapse
Well, it depends on where you are bootlooping. If you're stuck at either of the first two splash screens, then you're out of luck with ADB as it isn't available yet. If you're bootlooping but getting to the bootanimation, then you can. To do so, run
Code:
$ adb root
$ adb shell mkdir /data/ramdisk
$ adb shell mount /dev/block/mtdblock5 /data/ramdisk
$ adb push ramdisk-recovery.img /data/ramdisk
$ adb reboot recovery
where ramdisk-recovery.img is from the AOSP 7.0 zip.
If you're stuck at the first or second splash screens, then you need Odin or Heimdall. With heimdall, you can do
Code:
$ heimdall flash --KERNEL boot.img
where the boot.img is the one from Omni 6.0, the one from 7.x won't work on its own as the recovery is not stored in it. You can use Odin to go back to stock.
I haven't tried gapps so I guess I should sometime and see what the issue with them is.
Gets to the second splash screen. I'll give that a shot when i have some free time. I'm really looking forward to getting this working as I'm amused by the idea of my oldest android phone running the newest OS before my other two.
Update: couldn't get it to work with my cheap laptop. Kept throwing up the libusb 12 error. Then when i finally gave up and pulled the battery, I noticed it was starting to bulge a little. I think I'm out for a while. I'm hoping i can come back to this soon.
Sent from my A0001 using XDA-Developers mobile app

[ROM] [UNOFFICIAL] LineageOS 13 |ASUS Memo Pad HD 7 (me173x) [MT8125]

Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.​
How to Install:
1- BACKUP, BACKUP, BACKUP, All will be WIPED!
2 - Unlock bootloader instructions here
3 - Flash the new mandatory TWRP Recovery
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package "ARM" > "6.0" > "Pico" or "Nano" visit OpenGAPPS
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
Charging
Offline Charging
Video decoding/ Playback (i.e.: Youtube) up to 720p
android marshmallow new features: Adoptable Storage / Multi Window / etc
DRM Widevine : For Netflix, Amazon Prime, etc
Sensor: magnetometer: akm8963
Front Camera: mt9m114_mipi_raw
Front camera: GC0339_RAW
etc ....
NOT Working:
Rear Camera: a5142_mipi_raw
Front Camera: GC0339_RAW (ME173X 8GB) Fixed on build 20220629
Sensors: accelerometer (autorotation)
You tell me
Special Thanks
OMNI Rom
LineageOS
DerTeufel1980 & fire855 ( my Team mates from M.A.D)
GPL Compliance:
GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
ASUS ME173x device for LineageOS 12.1 & LineageOS 13 - GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
github.com
GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1
ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1 - GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / ...
github.com
--> "asus_mm" branchs
FAQ
Small FAQ:
Q: How can i Unlock the Bootloader?
A: Instructions for Unlocking the Bootloader can be found here
Q: After locking the screen, the screen is all black, and/or flickering and I'm forced to reboot, how can I fix this?
A: If you have this issue, then your device uses the second screen/lcm hardware revision
( the lgld070wx3_dsi_vdo ), please use the second kernel.zip for this variant, it'll be added an second kernel . zip for people with this variant, on the download section with the ROM release
Q: how to flash this second kernel for the new hardware variant ?
A: After flashing the ROM, flash the second kernel afterwards
Q: Where are the Developer Options?
A: Go to Settings>About Tablet, and tap 7 times on the Build Number
Q: Where is the multi-window mode?
A: in the developer options, you can enable it there
Q: How can i root this rom?
A: you can use Magisk , or SuperSU
Magisk: v.23
SuperSu v2.82
note: Magisk builds v24.x and v25.x do NOT work.
Q: Do i really need to update recovery?
A: YES
Q: I can't flash this Rom on recovery, why?
A: You need to update your recovery to TWRP
Q: how to work with twrp?
A: in the first time TWRP boots, it'll ask if you want to allow modifications, slide to YES
Q: how to wipe and flash in twrp?
A: Go "mount" and mount "system"
then go "wipe" > and wipe dalvik / cache / data / System
Q: How can i flash the new recovery?
A: If you already have an custom recovery installed:
Download the new TWRP recovery zip
flash the new recovery
reboot to recovery again, TWRP should be now installed
If you don't have any custom recovery installed:
- You can extract the "recovery.img" from the .zip
- Open an terminal
- Boot to fastboot mode, and type:
Code:
fastboot flash recovery recovery.img
then reboot:
Code:
fastboot reboot
Q: I Love your work, how can i thank you?
A: You can press the "Thanks" button, and if you wish, you can pay me a beer
..
Changelogs
Build 20201221
First Release
Build 20210821
Kernel:
DCT / Power resolve more issues
LCM: nt35521_dsi_vdo: Add backlight enable ctrl function
Fix magnetometer sensor: akm8963
Battery: Corrections
Camera LENS AF (for the rear camera) fixed
Front Camera : mt9m114_mipi_raw ( ME173X 16GB Version) fixed
mmc: more handling fixs
msdc: more fixs
Touch Panel: GT927: Implement a proper suspend & resume
Some other small fixs.
LineageOS source and device:
LineageOS LiveWallpapers, Wallpapers are now included ( as per-user requests)
Gello browser removed, it's depricated and has security risks
Disable Live Display by default (not supported by this device)
Some device clean up
Fix some eGL crashs
Fix some core missing symbols
Added Front camera support ( Pictures )
Some other small fixs.
Build 20220629
Kernel:
Security: Fix the following security issues:
PG SU daemon security fix
CVE-2017-1000365
CVE-2017-2618
CVE-2017-2671
CVE-2016-10208
CVE-2016-10208
CVE-2013-4312
CVE-2016-2550
CVE-2017-9074
CVE-2017-9075
CVE-2017-9076
CVE-2017-9077
CVE-2017-9242
LVT-2017-0002
CVE-2012-6703
CVE-2015-8944
CVE-2016-3857
CVE-2016-9555
CVE-2017-8890
ARM: spectre-v1
ARM: spectre-v2
ARM: Merge some bug fixs
imgsensors:
mt9m114_mipi_raw: Enable NightMode & Improve NightMode handling (better handling of Low light pictures)
gc0339_raw support added (CMOS front camera used in some HW revisions)
Memory management / Others:
Merge ZRAM from Kernel 3.10 version, and backport K 3.10 ZRAM fixs
Merge zsmalloc from Kernel 3.10 version, and backport K 3.10 ZRAM fixs
Add support for LZ4 decompression in the Linux Kernel
Other minor fixs
LineageOS source and device:
device: Added 512 MB Virtual SWAP Memory
Fix GPU PowerVR blobs crash, leading to random reboots & wakeup reboots
Disable OpenGL preloading with PowerVR drivers
SHIM: Add UI shim lib to fix some other random crashs
Remove max app limit
ART: Increase and fine tune the heap limit
Camera & nvram blobs fixs
Other minor fixs
Build 20220718
Fixed Bluetooth, that got broken by mistaque on 20220629 release
Downloads
TWRP 3.1.1
TWRP_3.1.1_ME173X.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20220718
https://androidfilehost.com/?fid=15664248565197191338If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220718
https://androidfilehost.com/?fid=15664248565197191342
Old Builds
Build 20220629
https://www.androidfilehost.com/?fid=15664248565197184858If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220629
https://www.androidfilehost.com/?fid=15664248565197184860
Build 20201221
lineage-13.0-20201221-UNOFFICIAL-me173x.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If you have the second hardware Screen revision (check FAQ), flash this
kernel for the Build 20201221
Kernel_rev2_Build_20201221.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20210821
https://www.androidfilehost.com/?fid=7161016148664790672If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20210821
https://www.androidfilehost.com/?fid=7161016148664790675
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Bluetooth also not working
gadom92 said:
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Click to expand...
Click to collapse
Same here
Awesome work, thx and merry xmas
gadom92 said:
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Bluetooth also not working
Click to expand...
Click to collapse
This seems to be the very same issue some users had with Lineage 12.1...
can** replicate this on my units.
EDIT: i meant, can't replicate this
please try this:
[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]
Disclaimer: LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if...
forum.xda-developers.com
Settings > Backup & reset
superdragonpt said:
This seems to be the very same issue some users had with Lineage 12.1...
can replicate this on my units.
please try this:
[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]
Disclaimer: LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if...
forum.xda-developers.com
Settings > Backup & reset
Click to expand...
Click to collapse
Did not solve the problem so far. Wifi is even broken after restoring the los 12.1 backup which worked before
Edit: uploaded logcat
Ok, i reflashed the old carliv recovery via fastboot after installing Los13 and i got wifi back ...
And afterwards i flashed twrp again via fastboot and wifi is still working...
Previously i flashed the twrp zip from carliv, i guess this was part of the problem
reflashing recoveries in fastboot not worked for me :/
I also wiped everything including internal storage before, and bootet into each of the two recoveries and to the system from there.
Maybe the carliv recovery changes some things on the system, idk.
Hi, I am so glad that this is still alive project
I upgraded recovery via mtk flesher. Just rename twrp 3.1.1... into recover.img and click "download".
My wifi and bluetooth are working. Sometimes bluetooth have conflict with wifi and plain reboot fix things.
It is strange that not a single one sensor work(acceleration and gravity, magnetic field, orientation and rotation. They all worked in 12.1 beside rotation. Hope thing are going to get fixed up.
Had a few freezes also(hard reset do the job)
Overall I have a feeling that this is smoother than 12.1.
EDIT: It was misleading about recovery flash. You need to extract from twrp_3.1.1_ME173X.zip "recovery.img" and replace in folder where scatter file with old "recovery.image" is.
Gronkdalonka said:
I also wiped everything including internal storage before, and bootet into each of the two recoveries and to the system from there.
Maybe the carliv recovery changes some things on the system, idk.
Click to expand...
Click to collapse
interesting... likely the wiping of internal storage fixed it..
if anyone is having this issue, please try and report back if the following fixs:
in twrp:
Flash this test kernel
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
cheers
Merry Xmas
superdragonpt said:
interesting... likely the wiping of internal storage fixed it..
if anyone is having this issue, please try and report back if the following fixs:
in twrp:
Flash this test kernel
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
cheers
Merry Xmas
Click to expand...
Click to collapse
not working :/
edit: Flashed old recovery trough Flash Tool, than TWRP in Flash tool wipe all what i can and then install LOS 13. Wifi working like a charm
Any chance you can help with source patches?
First of all thanks to snapdragon for the new LOS13 support.
I'm sorry to tell you that all of your mentioned ways to get WiFi back to work did not work for me. What I did and what I tried:
Normal installation way:
Flashed new recovery via old custom recovery
complete wipe
flashed new LOS13 via new TWRP recovery
WiFi not working!
Going back to old custom recovery and back to TWRP
Flashed old custom recovery via TWRP
complete wipe
flashed new TWRP custom recovery via adb sideload since my sd card can only be mounted via new TWRP recovery
complete wipe
flashed new LOS13
WiFi still not work!
This is all I did. I realized that fastbood mode is not working for my device, could be a driver problem since my device is installed as ùó something when plugging it into the pc in fastboot mode, so I tried the way via adb.
Hint: I have the model with the alternative hardware, so the second kernel is required to fix flickering display issue.
I realized that the new TWRP recovery has this issue aswell, so my display is flickering from the right side to the center sometimes in TWRP recovery.
Any ideas what could help getting WiFi back to work?
Thanks in advance!
Edit: Could it be that this WiFi problem has something to do with the following thread:
FIX FOR MAC 02:00:00:00:00(WiFi and hotspot not turning ON)
Important. Root required..... Hey everyone,I saw so many posts regarding Android & iOS that the Mac address is changing to 02:00:00:00:00 and WiFi is greyed out. None of the WiFi or hotspot not turning on.I get the same problem in my Condor and...
forum.xda-developers.com
I read over some postings and googled the mac address 02.00.00.00.00 and it seems that a lot of devices had this problem when updating from android 5 to 6. It seems that it could have something to do with the partitions where the info (mac address, IMEI) are stored, but in general I have not found a solution and a specific description of the problem.
Anyway: If the problem can be solved by doing the steps described in the thread I provided above I’m not able to solve this. I would not describe me as a noob, but it seems that I need root and knowledge of permission management for the fix, and I am not very familiar with Linux.
Could you do the following test:
In twrp:
Full wipes ( system, etc etc and internal storage) be sure you back up your stuff
Then reboot to recovery
( It'll warn there's no OS installed)
Back to recovery
Do full wipes again , plug the tab into pc and copy the rom to internal storage
Reboot to recovery again
( It'll warn again, there's no OS installed)
Proceed to flash the rom
This has worked with a user
Issue: for an unknown reason some devices seems to fail mounting / reading nvram
@ twrp I'll do a build for people with this second hardware revision, flickering is annoying...
Thanks for your fast reply.
I did two full wipes with rebooting into recovery after each wipe as you said, then I copied the OS zip file to internal storage and rebooted again to recovery.
After installing the ROM I rebootet to system and LineageOS was preparing the first start. I started without flashing the kernel for alternative hardware (2nd kernel) to check if it works first.
I'm sorry to tell you that I still got no WiFi and Bluetooth connections, Mac address still is shown as 02-00-00-00-00, WiFi cannot be turned on.
Edit: Seems that is has nothing to do with wipes (on my device). I've tried all kind of wipes via TWRP
Format Data -> yes -> reboot to recovery
Advanced Wipe -> check all (Davlik, Cache, Data, Internal Storage, System -> Again format data -> Yes -> reboot to recovery
flashed ROM, 2nd Kernel and GApps -> Reboot to recovery -> reboot to system
Still no WiFi. Perhaps I should try to go back to stock rom and see if WiFi works there? Do you think this could make the deal?
test this
full wipes
flash rom, then this kernel afterwards
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Again, thanks for your efforts, it seems to be a really tough and bugging one, since the new kernel did also not fix the problem.
Edit: Just to keep u updated: I just flashed old recovery and afterwords old LineageOS 12, WiFi is working well. So there must be some problem with the update or the update process. I will try to wipe first and then install new recovery and again install new OS, perhaps this will do the job.
Edit2: BTW I forgot to tell you that I had problems with settings -> about tablet -> status on lineageos 12. Just remembered because i wanted to have a look to the mac address. I get an error telling me "unfortunately, settings has stop". Perhaps important for the update?
Important Edit3:
Guess what: I made it to work. I did the following to do it:
1. Format Data and do all wipes possible with TWRP recovery. Reboot to recovery and do the same again.
2. TWRP recovery -> install old recovery
3. In old recovery -> install via sideload (adb sideload) lineageOS12 and second Kernel (for me because of hardware)
4. Boot to system and check if WiFi works well (finish the initialization of the device and connect to a WiFi)
5. Boot to recovery (old recovery) -> WITHOUT WIPING install via sideload TWRP recovery
6. Boot to system. (Still lineageos12) check if WiFi still works
7. Boot to TWRP recovery -> WITHOUT WIPING install lineageos13.
8. Boot to system, finish initialization if necessary and check if WiFi still works.
9. Go to setting and do a factory reset from lineageos13 settings
10. Device will reboot to recovery and do the factory reset and automatically will boot back into system.
11. Finish. All should work now.
I don't know what exactly did the job, so I wanted to provide all steps I did.
Since I never flashed an android custom Rom over another without wiping I don't know what errors this procedure can cause. So if someone knows that please let me now that I can have a look if there are errors.
Thanks again for your assistance.

Searched for the name of a tool available for download on the Microsoft Windows Platform - which has the ability to decompress the Android image.

Hello, I am looking for a tool that will allow you to decompress the img.xz image to the standard Android image format, i.e. to the img format.
Searched for the name of a tool available for download on the Microsoft Windows Platform - which has the ability to decompress the Android image from the img.xz format to the standard img format.
Peazip
It's not about just decompression, 7zip can unzip / decompress it, it's about the contents of img.xz. What's in the img.xz. And why do you want to convert it from that format to img format?
badabing2003 said:
It's not about just decompression, 7zip can unzip / decompress it, it's about the contents of img.xz. What's in the img.xz. And why do you want to convert it from that format to img format?
Click to expand...
Click to collapse
Okay, let's follow step by step.
I go to the website www
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
I go to the tab Assets.
After expanding the Assets tab, I see 3 files - 3 Android images to choose from. Now I will write about it. I am downloading the image with the largest size in Gigabytes.
After expanding the Assets tab, I see 3 files - 3 Android images to choose from. Now I will write about it. I am downloading the image with the largest size in Gigabytes. My friend, after entering the website > https://github.com/ponces/treble_build_pe/releases Before that, I go to this Table >
I choose the option to download the Android image in Android 11. I confirm that the Developer who provides the link via GitHub provides a link to Android 13. Nothing wrong with that. However, at the moment I have LineageOS version 18.1 - that is, it is Android version 11..
In order to avoid possible problems with bricking the phone, I thought it worth choosing an Android image in version 11 - such as I have LineageOS now.
Could you send me a link to download the Pixel Experience image on Android 11 via GitHub?
Because I can't post on GitHub. I need your support. Can you help me ? Please help me. To the best of my knowledge, look for Pixel Experience version 11 for me.
Hello friend, img.xz file format is not detected for me - I am sending a screenshot.
Can you still help me? I toggled in the TWRP menu install Image.
TWRP does not detect this format - i.e. ... img.xz
Okay let's move on. I am posting information about the standard img image - that is LineageOS Android.
As for the image of Android LineageOS - it looks great. See - the image is detected by TWRP Recovery correctly.
I confirm that the img format of the Android LineageOS image is detected and ready for installation by Recovery TWRP.
badabing2003 said:
It's not about just decompression, 7zip can unzip / decompress it, it's about the contents of img.xz. What's in the img.xz. And why do you want to convert it from that format to img format?
Click to expand...
Click to collapse
Hello, I confirm that TWRP Recovery detects a correctly packed file via 7-zip. I packed the Android Pixel Experience img.xz image into a zip format.
I am asking you to send me a link to Flash/Installation - Google Gapps version for Android 13. I am waiting patiently for you to send me a link. Needs access to Google Play Store on Pixel Experience Android 13.
I am asking you to send me a link to Flash/Installation - Google Gapps version for Android 13. I am waiting patiently for you to send me a link. Needs access to Google Play Store on Pixel Experience Android 13.
Will this pack 100% compatible with this Custom Rom - Android / Pixel Experience 13 ? >
[Android 13] [GApps] NikGApps [ARM64]
Hi Everyone, Here I'd like to Introduce you with my custom Gapps package that I use on day to day basis when I flash a new Rom. As I've observed many people struggling with finding the correct version of gapps to flash, I decided to build a...
forum.xda-developers.com
Downloads - NikGApps
NikGapps Website
nikgapps.com
I am asking you to send me a link to Flash/Installation - Google Gapps version for Android 13. I am waiting patiently for you to send me a link. Needs access to Google Play Store on Pixel Experience Android 13.
Will this pack 100% compatible with this Custom Rom - Android / Pixel Experience 13 ? >
I need access to the Google Play Store on Pixel Experience.
I kindly ask for help.
xzenx1234x said:
I am asking you to send me a link to Flash/Installation - Google Gapps version for Android 13. I am waiting patiently for you to send me a link. Needs access to Google Play Store on Pixel Experience Android 13.
Will this pack 100% compatible with this Custom Rom - Android / Pixel Experience 13 ? >
[Android 13] [GApps] NikGApps [ARM64]
Hi Everyone, Here I'd like to Introduce you with my custom Gapps package that I use on day to day basis when I flash a new Rom. As I've observed many people struggling with finding the correct version of gapps to flash, I decided to build a...
forum.xda-developers.com
Downloads - NikGApps
NikGapps Website
nikgapps.com
I am asking you to send me a link to Flash/Installation - Google Gapps version for Android 13. I am waiting patiently for you to send me a link. Needs access to Google Play Store on Pixel Experience Android 13.
Will this pack 100% compatible with this Custom Rom - Android / Pixel Experience 13 ? >
I need access to the Google Play Store on Pixel Experience.
I kindly ask for help.
Click to expand...
Click to collapse
Have you now installed the ROM you wanted to install? Is it running?
Did you really make a ZIP file that contains an XZ file?
Do you really have no idea of the distinction between the three PixelExperience images you found, other than size? They are substantially the same size. Size is no reason to choose one over the others.
J.Michael said:
Have you now installed the ROM you wanted to install? Is it running?
Did you really make a ZIP file that contains an XZ file?
Do you really have no idea of the distinction between the three PixelExperience images you found, other than size? They are substantially the same size. Size is no reason to choose one over the others.
Click to expand...
Click to collapse
Tell me more about this please.
I just suggested that you choose the right pixel experience Android image size.
you understand.
I thought for a 32 GB drive - because that's what I have in my smartphone - LG G4 H815 - choose the smallest img image - Pixel Experience. I'm trying to interpret it in such a way that the Developer who provides these images compresses these images himself and sends them already compressed. Going further - with this thinking he stops. Because I need expert knowledge.
I need a hand in this. When I flashed/installed LineageOS Android Custom Rom - flashed as a zip package. It was always a standard img image. At the moment I have LineageOS 18.1 - that is Android 11th release.
I need to know how to flash/install a Custom Rom - so as not to brick the phone. Because if it installs wrong, I can brick the phone.
When I choose the installation mode as a zip package - the Android image is always installed to the partition where the system is - there is no way to wipe the partition - where is Recovery TWRP? I always select wipe everything in the TWRP Recovery menu.
I have basic knowledge of flashing/installing Custom Roms.
I kindly ask you to pass on the knowledge to me.
First of all, it needs to have a powerful system, more efficient than LineageOS 18.1 Android 11th version.
I have a Smartphone LG G4 H815 - and here is only 32 GB of Rom and only 3 GB of RAM.
Please kindly help me. Which Pixel Experience Custom Rom - will be the lightest for 32G Rom, and for 3GB Ram.
Clearing Cache and Dalvik...
Cleared: /data/dalvik-cache...
-- Clearing Dalvik cache directories complete! Formatting the system with make_ext4fs...
Wiping data without erasing /data/media ... Done.
Clearing internal memory -- /data/media...
Formatting encryption metadata using mkfs. fat...
Done. Formatting cache with make_ext4fs... Updating partition details...
...done Installing ZIP file "/external_sd/Pixel Experience
Android 13/PixelExperience_Plus_arm64-ab-13.0-20230218-UNOFFICIAL.img.zip'
Failed to map file /external_sd/Pixel Experience Android 13/PixelExperience_Plus_arm64-ab-13.0-20230218-UNOFFICIAL.img.zip' Error installing zip file '/external_sd/Pixel Experience Android 13/PixelExperience_Plus_arm64-ab-13.0-20230218-UNOFFICIAL .img .zip' Updating partition details...
...done
Add a signature
Wednesday, February 22, 2023 at 19:43
Correct
IMG_0527
iPhone 7 Plus
JPG
ABOUT
Wide Angle Camera - 28mm f1.8.
12MP 3024×4032 • 2.3MB
ISO 50
28mm
0 possibly
£1.8
1/17 sec
bright
1
Error message when trying to install Pixel.
It's not about de-compressing this Android image right? Isn't that the point?
xzenx1234x said:
It's not about de-compressing this Android image right? Isn't that the point?
Click to expand...
Click to collapse
Does your phone still work?
Do you understand what I mean when I say "DOS window" or "command prompt window"?
In a Command Prompt Window on your Windows computer, type:
Code:
7za l PixelExperience-ROM-you-downloaded.xz
7za l ZIP-file you-used-in-TWRP.zip
What does 7Zip say?
You should be talking to someone who has installed this ROM. Anyone can register on github. Then you can try to post on github.
A standard email registered account allows you to send messages or GitHub posts. Write me details about it. I am asking you - do not be surprised that I am writing about it - but I am a beginner with Github.
xzenx1234x said:
A standard email registered account allows you to send messages or GitHub posts. Write me details about it. I am asking you - do not be surprised that I am writing about it - but I am a beginner with Github.
Click to expand...
Click to collapse
In a browser, go to http://www.github.com and click on "Register" or "Sign up". Follow the prompts. Until they ask for a credit card, you have nothing to lose.
Now your turn: Answer the questions I asked.

Categories

Resources