Current Information
Hi there, UltimateROM is AOSP-based ROM with some features and optimizations added.
Everything I do with UltimateROM I always test personally on my phone, but anyway...
Code:
#include <disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
What's working:
RIL (phone/SMS/3G)
Video (playback & recording)
Audio (playback & recording)
Wi-fi
Bluetooth
Camera (Front and rear)
2D/3D HW Acceleration
USB, MTP, ADB
all native tethers (Wifi/BT/USB)
external storage
What's not
GPS
Vibration doesn't work (disabled temporarily due to an userspace vibrator driver issues)
Internal storage is not recognized
Formatting SDcard as adoptable storage will make it unusable
Buggy MTP implementation
Download
UltimateROM
Installation
before installation make sure you have a TWRP recovery
install chrono kernel (both ROM and the corresponding kernel are located in the same directory - see ROM link below)
reboot recovery
install ROM
install SuperSU
install chrono kernel again
If you proceed with installing GAPPS, you might have running out of space on /system partition. If you are planning to flash Gapps, you're likely need to use sdcard repartition (see below how to). Below is installation sequence with the repartition of the internal sdcard:
like before, make sure you have kernel with TWRP recovery inbuilt
install chrono kernel
reboot recovery
flash ReParted zip. This will wipe system, data and cache partitions!
install ROM
install SuperSU
install chrono kernel again
*please note a possibly undesirable effect of the repartition: cache partition will be decreased to 15 MB and some ROMs that rely upon this partition won't boot. To restore original sdcard partition layout, flash stock 4.1.2 ROM (with PIT file).
Sources:
https://github.com/UltimateROM/android_manifest
Credits
SergeyL - many-many thanks for an initial set of patches, device tree and TWRP 3.x.y! Also thanks for helping me implementing some features to this ROM.
mickybart, millosr, MWisBest - thanks for great cherry-picks!
@Meticulus - thanks for his great contributions on our devices!
@AGONTUK - thanks for an initial Marshmallow bring up!
@nieltg - Sources for Galaxy Ace 2 device
@golden-guy - thanks for great cherry-picks !
@TeamCanjica - vendor and hardware sources
@Unjustified Dev - Audio fixes
Google
CyanogenMod
AOKP
SlimROMs
EuphoriaOS
OmniROM
AOSPA
Viper4AndRroid Team
And many other devs, I could forget (please write me if I did so).
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
XDA:DevDB Information
UltimateROM, ROM for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, SergeyL, mickybart, millosr, MWisBest
Source Code: https://github.com/UltimateROM
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP recovery
Based On: AOSP, LineageOS
Version Information
Status: Beta
Created 2018-03-11
Last Updated 2018-03-11
Changelogs
11.03.2018 - build #1
initial release
Reserved
Flashed both of your roms on janice and... wow, nougat is much smoother than mm (w/o gapps)
Great JOB Chrono , Will test it immediately .
Was dreaming of this.
[YOUTUBE][https://www.youtube.com/watch?v=JgSBPf-jiiM&lc=z23gzrkgcrqcffykaacdp43bvodf3st2izucbuxtgidw03c010c]
Ok Chrono MC I installed the ROM on 2 on my Advance's and you are official KING of the Advance i9070 Now
Thank you very much , this helped me to create my Mod but now under Android 7.1.2 thanks to You and all that worked on this .
Keep up the fantastic work.
Channel48
Hey I have a problem with the reparted script. I get "error opening "data/media"" and "error: No such file or directory"
ErackGamer said:
Hey I have a problem with the reparted script. I get "error opening "data/media"" and "error: No such file or directory"
Click to expand...
Click to collapse
Do these messages lead to any other problems? Try formatting /data partition. If that doesn't help, flash stock 4.1.2 ROM (with PIT file).
ChronoMonochrome said:
Do these messages lead to any other problems? Try formatting /data partition. If that doesn't help, flash stock 4.1.2 ROM (with PIT file).
Click to expand...
Click to collapse
I think that the problem was due to the old twrp I had installed. After flashing the kernel and getting the newer twrp that it includes I was able to successfully run the script. More details at your Lineage 15.1 ROM post
Going to test
can't get it pass thru Setup Wizard :thinking:
it just stuck at Just a sec, do I need a data enabled sim?
I've inserted a fat32 sdcard.
I will try without gapps later...
EDIT : First boot cannot have GAPPS, it needs to be flashed after first boot. Whole system seems slightly unstable with GAPPS.
logcat is weird, the output looks "choppy"
Hi @ChronoMonochrome
I saw you successfully booted this ROM
Did you change much in kernel 6.0.1 to make it boot
unknown said:
Hi @ChronoMonochrome
I saw you successfully booted this ROM
Did you change much in kernel 6.0.1 to make it boot
Click to expand...
Click to collapse
I don't really remember exact changes, since we have booted 7.1.2 a long time ago. You might want to look mostly at the SELinux changes, probably there should be implemented some more (which is recommended but not required to boot the ROM).
For those who are going to use GAPPS on this ROM:
1. Flash GAPPS after first boot! If you flash GAPPS before first boot, you won't be able to pass through Setup Wizard.
2. After flash GAPPS, do not wipe cache/dalvik cahce/data. Wiping these partitions after flash GAPPS seem to make GAPPS causing massive instability to the system.
3. On every boot, open once Settings -> Google and wait for Google Play Services to crash once. I don't really know why, but several GMS services kept crashing and restart GMS is restarted non-stop by the system. After Google Play Services crash once, the GMS services won't crash anymore. This should lead to a more stable system.
Overall, I don't recommend GAPPS with this ROM. With and without GAPPS on this ROM is almost a day and night difference, in terms of stability.
Janice + Nougat (w/o GAPPS) = BEST!
fix ur instructions i got confuesed
hi there, am seeing no comments of usability of this rom after Jun 2018.
Also there have been no no updates on the rom, seems like the developer has given up on the development.
can anyone confirm the bugs and can it used with microg?
Related
Hey Gang - I've got an issue here getting opengapps installed into marshmallow.
Background - N10 needed a refresh - we officially updated a few times (from 4.x to 5.0 to 5.1,etc) and by the end, the tablet was taking forever to reboot (updating or optmizing 160+ apps every boot), so I finally decided to start fresh. I though.. why not marshmallow.
I followed the guide here:
http://www.techtimes.com/articles/9...ndroid-6-0-marshmallow-on-google-nexus-10.htm
Basically unlocked the tablet, installed twrp and then embarked. I diverted from the original instructions to use 2.8.7.0 and used latest. (3.0.2.0)
the marshmallow image referenced in the link installed well and the system boots/runs much better... my problem comes with installing opengapps from twrp. I downloaded the arm/6.0/stock version and pushed to file system with adb, then tried an install from twrp. It seems the opengapps installer (20150519) performs a software check to ensure the version of gapps is compatible with the version on Android. My problem is that it seems to be verifying against the recovery kernel and not the installed kernel.
I have the understanding that the load I installed is in fact 6.0, however it appears that twrp is built from 5.1.1 and the openGapps installer queries (I think) the twrp kernel, then determines that it cannot install. I get an error 20 message and specific dialogue that says the
"This GApps pkg is for Android 6.0.x ONLY
Please download the correct version for
your ROM: 5.1.1 (SDK 22)."
It then fails and returns me to TWRP. So next I tried the TWRP version (2.8.7.0) specified in the techtimes link I referenced above, and I get a similar error except ROM 4.4.4 SDK (19).
So it would appear that Gapps is checking local runtime only.
Is there any to fix this, or is it something I am doing wrong?
Help please!
Same problem here.
giz02 said:
Hey Gang - I've got an issue here getting opengapps installed into marshmallow.
Background - N10 needed a refresh - we officially updated a few times (from 4.x to 5.0 to 5.1,etc) and by the end, the tablet was taking forever to reboot (updating or optmizing 160+ apps every boot), so I finally decided to start fresh. I though.. why not marshmallow.
I followed the guide here:
http://www.techtimes.com/articles/9...ndroid-6-0-marshmallow-on-google-nexus-10.htm
Basically unlocked the tablet, installed twrp and then embarked. I diverted from the original instructions to use 2.8.7.0 and used latest. (3.0.2.0)
the marshmallow image referenced in the link installed well and the system boots/runs much better... my problem comes with installing opengapps from twrp. I downloaded the arm/6.0/stock version and pushed to file system with adb, then tried an install from twrp. It seems the opengapps installer (20150519) performs a software check to ensure the version of gapps is compatible with the version on Android. My problem is that it seems to be verifying against the recovery kernel and not the installed kernel.
I have the understanding that the load I installed is in fact 6.0, however it appears that twrp is built from 5.1.1 and the openGapps installer queries (I think) the twrp kernel, then determines that it cannot install. I get an error 20 message and specific dialogue that says the
"This GApps pkg is for Android 6.0.x ONLY
Please download the correct version for
your ROM: 5.1.1 (SDK 22)."
It then fails and returns me to TWRP. So next I tried the TWRP version (2.8.7.0) specified in the techtimes link I referenced above, and I get a similar error except ROM 4.4.4 SDK (19).
So it would appear that Gapps is checking local runtime only.
Is there any to fix this, or is it something I am doing wrong?
Help please!
Click to expand...
Click to collapse
The error is telling you the problem. You are on 5.1.1 and trying to flash a gapps for 6.0. either upgrade your rom to a 6.0 rom or flash gapps for 5.1.1
Malstrond said:
Same problem here.
Click to expand...
Click to collapse
If you're getting the same error, you have the same solution.
garnet&gold said:
You are on 5.1.1 and trying to flash a gapps for 6.0. either upgrade your rom to a 6.0
Click to expand...
Click to collapse
Then why does the SDK version reported by the opengapps installer change when changing the TWRP version, but not when changing the Android version installed on the device?
Malstrond said:
Then why does the SDK version reported by the opengapps installer change when changing the TWRP version, but not when changing the Android version installed on the device?
Click to expand...
Click to collapse
The only reason the gapps version would be different is if you are flashing different versions. TWRP does not change the version and it does not have a kernel. Sometimes opengapps doesn't seem to play well with TWRP on this device. You could try Khaon's TWRP and / or a different gapps version like Bank's.
Sent from my Nexus 10 using Tapatalk
I am having the same problem twice - 1) When I try to install 7.1.x it states I need to install version 6.0.1.
2) When I try to install 6.0.1 it states I need to install version 7.1.x.
Error 20 each time and it's Lineage 14.1 for Nexus 7 I am attempting to install them in (which is Android 7.1.2).
In addition I am now again (upon 3rd install attempt) being shown error 70, but I (having had it resize the system partition) have more than enough space for as much: (this website is blocking me from posting a link to the photo so simply change the following to the correct format) (drive.google(dot com)/open?id=1aaCiOwzoGRgrZPkJPuEj3jQOc-3hgnH3) so this doesn't make sense...
What now must be done to install this apps application?
I have tried all possible versions of Gapps. None of them install. What must be done in addition to this topic's early post is what I am unclear about. Those instructions claimed that increasing the size of the system partition would do the job, yet did nothing of the sort. I even tried reinstalling the OS, following the instructions here then again attempting to install all forms of the Gapps application, but yet again none would install.
Gapps problem
I faced same issue, gapps error return by 20.
After finished flashing rom, you will reboot system. Then you go back to recovery and flash gapps,it will work
Steps to install a ROM and the GApps (Open Gapps) without problems
1. Boot into Recovery Mode (TWRP)
2. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
3. Swipe to Wipe at Bottom of Screen,
4. Back to Main start screen,
5. Wipe > Format Data,
6. Type 'Yes' and press blue checkmark at the bottom-right corner,
7. Go Back to Main Start Screen to -VERY IMPORTANT---> Install Rom and GApps,
8. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe
9. Reboot System
Source: https://forum.xda-developers.com/no...nofficial-lineage-15-1-rom-t3760969?nocache=1
Bonampi said:
Steps to install a ROM and the GApps (Open Gapps) without problems
1. Boot into Recovery Mode (TWRP)
2. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
3. Swipe to Wipe at Bottom of Screen,
4. Back to Main start screen,
5. Wipe > Format Data,
6. Type 'Yes' and press blue checkmark at the bottom-right corner,
7. Go Back to Main Start Screen to -VERY IMPORTANT---> Install Rom and GApps,
8. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe
9. Reboot System
Source: https://forum.xda-developers.com/no...nofficial-lineage-15-1-rom-t3760969?nocache=1
Click to expand...
Click to collapse
Folowing exactly!!!! your steps, I am getting Error70??? by installing GAPPS.
ROM and GApps v8.01
Nexus 7 2013, latest TWRP
zcseke said:
Folowing exactly!!!! your steps, I am getting Error70??? by installing GAPPS.
ROM and GApps v8.01
Nexus 7 2013, latest TWRP
Click to expand...
Click to collapse
Two options
1 - Install GApps micro no mini
2 - https://www.youtube.com/watch?v=6vT7kyK0WUA
zcseke said:
Folowing exactly!!!! your steps, I am getting Error70??? by installing GAPPS.
ROM and GApps v8.01
Nexus 7 2013, latest TWRP
Click to expand...
Click to collapse
Not to revive a dead thread, but since I've had the same issue as the last post, and resolved it on the same device, Nexus 7 (2013 flo 16 gb) I thought I'd chime in to tell how I worked around it for that device. I could not install any Android 9 ROM that would allow me to install any Open GApps without getting that aforementioned error 70 in TWRP. I finally tried the combination of AICP (unofficial) based on Pie [AOSP Extended (unofficial) also worked] and GApps for Android 9 arm Pico. That version of GApps and either of those two ROMs allow me to get the Nexus 7 running again with Android Pie. I don't know why that worked, but I should mention I didn't have that problem with my Nexus 7 deb that has 32 gb onboard, so I'm guessing it had something to do with the different sizes. I can run any Pie ROM on the deb tablet. I hope this helps.
Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience.. ?
xzy99 said:
Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience..
Click to expand...
Click to collapse
it this a joke? this looks like a chinese copy of a guide posted 1 week ago and is only 2 posts under this:
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
what is your intention?
@massan1 I hope you have eyes through which you can read properly. No offence brother. Well, I didn't copy it. Plus that guide is made for those who have locked bootloader. Second, I am posting this for those who want to clean install Lineage OS with the call audio fix. So, if you believe I have copied it , just keep believing it.
Keep burning.. I'll get ice packs for you. Thanks.
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
r28 said:
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
Click to expand...
Click to collapse
just flash upgraded firmware or change build.prop:
https://forum.xda-developers.com/re...stall-lineage-os-locked-t3546154/post70826457
Raaj52 said:
This is not a build.prop issue!! In order to work with the old firmware (patched one) you have to make fluence to none, this is done when you use patched VoLTE. If you make fluence to none the latest MM firmwares won't give sound in call, many are getting no sound because they are using the old patched firmware. Since the native VoLTE is fixed no need of the old firmware and you don't need to change fluence to none. Just flash the latest firmware and you are good to go.
Still doubt? OK then I need to tell you one more thing, The first patch for VoLTE for MIUI MM was made by me (you can check that in MIUI Global forum) and sudeep made a firmware.zip with my NON-HLOS.bin and I can see that the same is copied in the firmware.zip, in order to get fluence working in the patched firmware it should have used with the correct adspso.bin.
Many are thinking that changing firmware is useless but in reality it comes with lot of stability fixes, so I recommend everyone to update your firmware to the latest one instead of all this build.prop editing craps.
What is the problem if I edit build.prop? --> You have to edit your build.prop whenever you flash a ROM, you can't avoid it unless you flash the latest firmware.
Why I am so confident? --> Because I know what is firmware and How does it work!
If you have "no sound in calls" issue even after you change the firmware I recommend a clean mi flash tool flashing with the latest MIUI ROM (because it will fix all your partition related stuffs, instability issues)
@abhishek987 @akhilnarang could you please add the "solution for no sound in calls is to flash the latest firmware" in your first post?
Click to expand...
Click to collapse
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.3.1-1:
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
DOWNLOADS: twrp-3.3.1-1-kuntao.img
HOW TO FLASH:
Fastboot Method :
Code:
fastboot flash recovery filename.img
Boot to TWRP > INSTALL > Select Image > Navigate to "filename.img" > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod/Lineage Android
XDA:DevDB Information
[RECOVERY] [OFFICIAL] [TREBLE] TWRP for Lenovo P2 [kuntao], Tool/Utility for the Lenovo P2
Contributors
darshan1205
Source Code: https://github.com/TeamWin/twrp_device_lenovo_kuntao
Version Information
Status: Stable
Created 2019-05-22
Last Updated 2019-06-02
Changelog:
* 20190522: Based off LineageOS's TWRP & Kernel with EFS backup & Vendor wipe option.
* 2019-06-02: Its OFFICIAL now!
Reserved
Nice Work ?
Thx. Looks like f2fs formatting issue fixed.
Other link please, can't download from sourceforge.
Use desktop version, it won't download on mobile site.
work well thank you.
Tq brother.... ?
Is this treble compatible?
numenory said:
Is this treble compatible?
Click to expand...
Click to collapse
Yes
Update!
Its OFFICIAL now. Builds from twrp-3.3.1-1-kuntao.img are supported by me.
Sorry ... Which difference about this recovery and the Los one ?
How to Flash a GSI?
darshan1205 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.3.1-1:
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
DOWNLOADS: twrp-3.3.1-1-kuntao.img
HOW TO FLASH:
Fastboot Method :
Code:
fastboot flash recovery filename.img
Boot to TWRP > INSTALL > Select Image > Navigate to "filename.img" > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod/Lineage Android
XDA:DevDB Information
[RECOVERY] [OFFICIAL] [TREBLE] TWRP for Lenovo P2 [kuntao], Tool/Utility for the Lenovo P2
Contributors
darshan1205
Source Code: https://github.com/TeamWin/twrp_device_lenovo_kuntao
Version Information
Status: Stable
Created 2019-05-22
Last Updated 2019-06-02
Click to expand...
Click to collapse
Greetings,
For some reason, I am not able to flash a GSI. I flashed your TWRP as recovery, then flashed your AOSPExtended ROM (because it supports Treble):
https://forum.xda-developers.com/lenovo-p2/development/rom-aospextended-rom-v6-3-lenovo-p2-t3903454
I have used this thread to install a GSI: https://forum.xda-developers.com/lenovo-p2/how-to/ultimate-guide-flashing-gsi-kuntao-t3815070 I've tried using LOS to install GSIs but it didn't work, that's why I later flashed AOSPExtended.
Once i flash any GSI (A, or A/AB), none of them work. They get flashed, but the phone gets stuck at the post screen. Sorry, I'm new at this.
In other words, How can I flash a GSI?
@darshan1205 please help. I am not able to flash any 9.0 rom now as every rom just sticks to boot animation and keeps loading. 8.1 roms and stock rom are working fine.
Twrp also giving different different errors every time like error 7,8,255 etc. When i reboot to recovery my data partition shows 0 mb. I formatted data partition and other partitions also. I have tried reinstalling twrp but same issue persists.
Guys, you really need to put some user guide documentation in along with these.
Did I know that system and system image should not both be ticked for a restore? Nope, I did not.
Hours I spent with TWRP hanging after restoring systyem and telline me it was restoring system image and not doing a darned thing.
And still I just cannot get my backup resatored AND my lernovo P2 restarted where I left off before backup.
Highly frustrating to say the least.
Thanks for the tool though.
myjess said:
Guys, you really need to put some user guide documentation in along with these.
Did I know that system and system image should not both be ticked for a restore? Nope, I did not.
Hours I spent with TWRP hanging after restoring systyem and telline me it was restoring system image and not doing a darned thing.
And still I just cannot get my backup resatored AND my lernovo P2 restarted where I left off before backup.
Highly frustrating to say the least.
Thanks for the tool though.
Click to expand...
Click to collapse
Have u checked your storage before restoration?....i had the same isse but it was because of my low storage
Plenty of storage.
Found out that this phone is a P2C72 with the P2A42 firmnware on it.
I have been able to put the AOSP PIE rom on it, but am having major difficulties putting magisk on it.
I know TWRP is not really built for the P2C72 but it seems to ha
ve worked up to now.
I have tried to install magisk from TWRP 3.2.3 and 3.3.1-1, but all I get on a system reboot is the blue led, the vibration, and a blank screen.
Also 3.2.3 reflash the boot rom so much quicker.
I would love to know how to troubleshoot this.
Note: To ADB sideload large files in TWRP, you may need to make your ADB.exe large address space aware.
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Hi guys, I have been testing the GSI AOSP ROM (from @phhusson) on our CC9e and works well most of the functions (maybe is not for daily driver but you can test and decide), except for :
-the FP sensor doesn't work
- the camera preinstalled not adjust to interface and the quality is bad (install gcam instead)
- Maybe other things
For those who want to test the AOSP Q sensation try the next steps:
You need a unlocked bootloader a TWRP working on your device and maybe some knowledge on how TWRP works.
1- Install the latest android 10 xioami.eu rom for cc9e (in order to get the vendor of android 10).
2- Download the latest AOSP 10 gsi system image (thanks to @phhusson ), extract it to get the .img file, copy it to internal memory or a otg device, then back to twrp.
2- Enter to wipe option on twrp, and slide to wipe data and cache partition, then go to install option and flash the .img file in the system partition.
3- Once it is installed just reboot to system and test the sensation of an AOSP rom
fer15 said:
Hi guys, I have been testing the GSI AOSP ROM (from @phhusson) on our CC9e and works well most of the functions (maybe is not for daily driver but you can test and decide), except for :
-the FP sensor doesn't work
- the camera preinstalled not adjust to interface and the quality is bad (install gcam instead)
- Maybe other things
For those who want to test the AOSP Q sensation try the next steps:
You need a unlocked bootloader a TWRP working on your device and maybe some knowledge on how TWRP works.
1- Install the latest android 10 xioami.eu rom for cc9e (in order to get the vendor of android 10).
2- Download the latest AOSP 10 gsi system image (thanks to @phhusson ), extract it to get the .img file, copy it to internal memory or a otg device, then back to twrp.
2- Enter to wipe option on twrp, and slide to wipe data and cache partition, then go to install option and flash the .img file in the system partition.
3- Once it is installed just reboot to system and test the sensation of an AOSP rom
Click to expand...
Click to collapse
Very nice.Thank you much more.
Hello!
This is my first contribution, for this device so have some patience.
-IMPORTANT: FOR NOW ONLY IT IS POSSIBLE TO INSTALL IT BY RESTORING IT BY TWRP, I HOPE SOON TO MAKE IT A .ZIP.-
HTML:
* Your 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.
Well, let's move on to the important thing.
This is a BACKUP of the original system (Lollipop 5.1) of the HTC Desire 626s, from the operator Movistar (Mexico) -maybe it will work with another, please try it-.
The rom includes everything original from HTC (apps, sounds, wallpapers, fonts, bootanimation, etc)
BUGS:
You tell me.
Apparently there are problems starting the ROM. Wipe Data/Cache/Dalvik and go.
HOW TO INSTALL / RESTORE:
**I recommend, after installing it, do a factory reset to avoid problems with the apps. ***
1. Download the .zip or folder from the link below. (NOTE: It weighs around 1.6GB.)
2. Extract that .zip in TWRP / backups.
3. Reboot into download mode (Vol Down + Power)
4. Select "Reboot into bootloader"
5. Select "Reboot into Recovery"
6. Select "Restore" -> Select the Folder (TWRP/backups)
7. Wait a few minutes..
8. Although it is not necessary, I recommend doing a factory reset (data, cache, dalvik cache).
9. Reboot
10. Enjoy!
Download Links:
Version 1.0 (.ZIP FLASHEABLE) [15/11/20]:
Coming soon..
Version 2.0 (TWRP BACKUP) [08/03/21]:
https://mega.nz/folder/xA4inCRb#oAZ1fkxkYac0pxoUgSEklA
I AM ALREADY WORKING ON AN AOSP VERSION OF LOLLIPOP.
-IMPORTANT: FOR NOW ONLY IT IS POSSIBLE TO INSTALL IT BY RESTORING IT BY TWRP, I HOPE SOON TO MAKE IT A .ZIP.-
Thanks!!! (I will be on the lookout, any problems or improvements to report.)
XDA:DevDB Information
[BACKUP][TWRP][LOLLIPOP] [STABLE] Backup ROM Stock HTC 626s [Movistar] (Mexico), ROM for the HTC Desire 626
Contributors
alexito_dev
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP, Bootloader Unlocked.
Version Information
Status: Stable
Current Stable Version: 2.0
Created 2020-07-22
Last Updated 2021-04-15
Reserved
reserved