[ROM][UNOFFICIAL] Resurrection Remix v6.0.0 [8.1.0][ham] - Zuk Z1 Original Android Development

[ROM][UNOFFICIAL] Resurrection Remix v6.0.0 [8.1.0][ham] - Zuk Z1 Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix Oreo
Installation FilesRom :- https://drive.google.com/open?id=1brVLDewli3WRs3u2mSkQeuSin78qRXqe
Gapps :- http://opengapps.orgBig thanks to:
XDA developers
LineageOS team
DU
Omni team
AND OF COURSE TO ALL THE SUPPORTERS, DONATORS AND USERS
Kernel Source : - https://github.com/Srijith2001/android_kernel_cyanogen_msm8974
Code:
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.
A lot.
XDA:DevDB Information
Resurrection Remix v6.0.0 [8.1.0][ham], ROM for the Lenovo Zuk Z1
Contributors
Gautham Asir, Gautham Asir
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Beta Release Date: 2018-02-17
Created 2018-02-17
Last Updated 2018-02-17

Bugs: Camera record is shaking. By default cpu is performance. Magisk+ kernel adiutor, change to interactive. From Time to Time camera starts not For the first touch. Battery life - 6 hours of working screen(without gps and games). Gps works unstable.

Wow thanks for the rom, waiting for it to become stable
Screenshots plsssss

So you blatantly copied ankur's build

Unselfish 1985 said:
Already using but official. Bugs: Camera record is shaking. By default cpu is performance. Magisk+ kernel adiutor, change to interactive. From Time to Time camera starts not For the first touch.
Click to expand...
Click to collapse
What about the lock setting is it working properly in Gauthams built

Sir I want Resurrection Remix Oreo to become stable. its my favourite ROM.plz remove bugs as soon as possible thanks

Sarfraz ahmed850 said:
Sir I want Resurrection Remix Oreo to become stable. its my favourite ROM.plz remove bugs as soon as possible thanks
Click to expand...
Click to collapse
Dude, developers are very busy in their work, they're working for us even though we don't pay them, so have some patience ?

I used RR roms before (3 or 4 versions of Nougat), and it was one of my favorites for the speed and customizations that it gave the Z1.
I had 3 major issues with RR and HexagonROM, which if I remember correctly, use the same "base":
1- GPS never works properly (managed to fix altering a config file in the system)
2- Videos frequently would not be saved, leaving a corrupt video file on the gallery
3- Random restarts.
Installed this ROM (Oreo) on Sunday night, went perfectly. Configured everything as usual, used it normally monday and tuesday. Phone seemed extremely fast and responsive. GPS working flawlessly! Videos are being saved, but they're very "choppy", tried several camera apps, no success. No random reboot on those two days. Battery drainage was VERY HIGH, couldn't get 12h of usage (whatsapp, instagram facebook)
But at the beggining of this night, my battery was very low and I was away from home, no charger. The phone turned off, no big deal.
Got home, put the phone on the charger and it automatically turned on (I read that's normal Oreo behaviour), but was stuck in boot animation for around 2 minutes when I held the power button for a forced restart. Then it went to the TWRP recovery screen and wouldn't go into normal boot again.. Found a tutorial on how to fix, managed to go into normal boot, but it stayed there for some time (30 secs maybe? not sure) and went into the recovery loop again.
I'm not bashing on it or anything, just letting you or the developers know what happened in my case. Guess I'll wait for it get into stable versions and try again some time later!
---------- Post added at 10:05 PM ---------- Previous post was at 09:58 PM ----------
Edit #1: I used this guide to try and get out of the recovery loop:
karimskcs said:
In TWRP, Go to advance, then go to Terminal and write down these codes one-by-one.
1. Code (Text): dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota Now press enter, and write down another code.
2. Code (Text): dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Press enter again! Then go to main menu, go to Reboot and hit System. You're done, enjoy!
Click to expand...
Click to collapse
It worked to get the system out of the recovery loop, but the phone still doesn't work properly.
Edit #2: even after completely wiping the phone (dalvik, cache, data and internal memory) and reinstalling evertything, the phone still was in rec-loop. Installed another ROM and had to repeat the steps on the quote to get it to boot.. Can someone explain WTF happened and what causes this?

epifaas said:
I used RR roms before (3 or 4 versions of Nougat), and it was one of my favorites for the speed and customizations that it gave the Z1.
I had 3 major issues with RR and HexagonROM, which if I remember correctly, use the same "base":
1- GPS never works properly (managed to fix altering a config file in the system)
2- Videos frequently would not be saved, leaving a corrupt video file on the gallery
3- Random restarts.
Installed this ROM (Oreo) on Sunday night, went perfectly. Configured everything as usual, used it normally monday and tuesday. Phone seemed extremely fast and responsive. GPS working flawlessly! Videos are being saved, but they're very "choppy", tried several camera apps, no success. No random reboot on those two days. Battery drainage was VERY HIGH, couldn't get 12h of usage (whatsapp, instagram facebook)
But at the beggining of this night, my battery was very low and I was away from home, no charger. The phone turned off, no big deal.
Got home, put the phone on the charger and it automatically turned on (I read that's normal Oreo behaviour), but was stuck in boot animation for around 2 minutes when I held the power button for a forced restart. Then it went to the TWRP recovery screen and wouldn't go into normal boot again.. Found a tutorial on how to fix, managed to go into normal boot, but it stayed there for some time (30 secs maybe? not sure) and went into the recovery loop again.
I'm not bashing on it or anything, just letting you or the developers know what happened in my case. Guess I'll wait for it get into stable versions and try again some time later!
---------- Post added at 10:05 PM ---------- Previous post was at 09:58 PM ----------
Edit #1: I used this guide to try and get out of the recovery loop:
It worked to get the system out of the recovery loop, but the phone still doesn't work properly.
Edit #2: even after completely wiping the phone (dalvik, cache, data and internal memory) and reinstalling evertything, the phone still was in rec-loop. Installed another ROM and had to repeat the steps on the quote to get it to boot.. Can someone explain WTF happened and what causes this?
Click to expand...
Click to collapse
Try qfil method....zui

Iamtheworst1 said:
What about the lock setting is it working properly in Gauthams built
Click to expand...
Click to collapse
Yes, properly.

How is the ROM!? Any bugs or battery drain?

underwood07 said:
How is the ROM!? Any bugs or battery drain?
Click to expand...
Click to collapse
This is a test rom. Try it if you want to. Has a lot of bugs.

underwood07 said:
How is the ROM!? Any bugs or battery drain?
Click to expand...
Click to collapse
Read first post in topic.

download link does not work
download link does not work

rr died?

vArhont said:
rr died?
Click to expand...
Click to collapse
Yes

Related

[HOW TO] Fix GPS location/locking to satellites issue

Hi all !
Since a week, i had a GPS problem with my i9305, it happened after i had flashed couple of AOSP roms, i dont know after which one it was exactly, the problem was that it couldnt get a lock onto my location, also couldnt find any satellites in any GPS fix/testing apps avaialable in the playstore, it was showing the blinking GPS icon on the left side in the statusbar, but there was no lock, it was endlessly blinking/searching for nothing.. Ive switched many times between AOSP and Samsung based roms, but this was the first time i encountered this kind of problem, which took me a week to figure out how to fix it :silly:
I tried many possible solutions such as, full wiping the rom, factory resetting within the settings, flashing back to STOCK rom with Odin, tightening the screws in the back of the phone, resetting and updating AGPS, changing GPS related files and libs in the rom, trying different roms etc. etc. with all to no avail !!
Then i did some research on the net and found the solution that worked for me, surprisingly it did even fix GLONASS that wasnt working before the problem occured, now GPS works perfectly fine!
SOLUTION:
1. first we need to enter service mode, this may differ for various android versions (4.3 - 4.4.4 - 5.1.1 etc.) just search for the right method if it is different. I did this on my android 4.4.4 KK ported note4 rom (Eclipse ROM)
Note: be sure the rom your doing this on, has the ServiceModeApp(_RIL).apk installed in system/priv-app, otherwise you wont be able to get in service mode!
Note: also if you dont have a sim password set, your phone might get sim locked, so set a pin password before doing this, afterwards you can always disable it again if you want..
2. in dial pad enter *#0011# to get in service mode
3. to unlock the main menu: press menu --> press back --> press menu --> press key input --> enter Q0 --> press ok and wait for the main menu to appear
4. now, press UMTS --> press COMMON --> press NV REBUILD --> press Restore Back-up
5. your device should now be rebooting and after that GPS issue should be fixed hopefully test your GPS with any app from the playstore..
Steps 3 and 4 pictures:
View attachment 3434862
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 3434866 View attachment 3434867 View attachment 3434870 View attachment 3434871
Below are some screenshots of the results of my test with the app ''GPS Test'' from the playstore:
Inside the house
Outside the house
I hope this post will be usefull for others, good luck if you are about to try this out! :good:
Follow this guide by @Alexander_the_B0ss to SIM-unlock your device if it gets SIM-locked after following the steps above!
Remember that i am in no way responsible for anything if you mess up things with your device !!

I had the same problem and the fix I did was to restore previously backed up NV from QPST app on pc
---------- Post added at 07:11 AM ---------- Previous post was at 07:06 AM ----------
I backed-up NV data using the guide in here
http://forum.xda-developers.com/showthread.php?t=1946915

Shadow92.Ahmed said:
I had the same problem and the fix I did was to restore previously backed up NV from QPST app on pc
---------- Post added at 07:11 AM ---------- Previous post was at 07:06 AM ----------
I backed-up NV data using the guide in here
http://forum.xda-developers.com/showthread.php?t=1946915
Click to expand...
Click to collapse
Yep, same thing, different procedure :good:

I really appreciate you sharing the fix. I've spent the best part of today trying to find a solution to this, and have taken my S3 apart more than once.
I even think I tried this fix earlier on my non-stock ROM and it didn't work.
Worked for me on the stock 4.4.4 ROM for EE.

MaHo_66 said:
Yep, same thing, different procedure :good:
Click to expand...
Click to collapse
We all try to help each other

GPS problem fixed
Hey,
and thank you soooo much for your helping advice
I did like you said and voila, GPS problem is history.
But what problem I still have is that I can´t flash any 5.x.x custom ROMs. Flashing goes well, but when it is time to reboot, my i9305 stuck to somekind of loop. I can flash stock ROM 4.4.4 and custom ROMs 4.4.4 as well, but Lollipop doesn´t work.
First time I had this problem was when I flashed some 5.1 ROM ( I don´t remember what was it ) But in that ROM suddenly happen that "Google services has stopped" or something like that. I couldn´t do nothing with phone. That error came again and again to phone´s screen..
So I was in situation that I had to flash stock 4.4.4 stock ROM. eveything went well, but GPS didn´t work anymore. Then I found your advice and I thought that now I can again flash custom ROMs as well. Flashing any custom 5.x.x ROM goes well, but in reboot, pghone stuck to loop.
Or had I wait longer in first time I reboot phone after flash?
Thank you so much in advance
/markkus

MarkkuAS said:
Hey,
and thank you soooo much for your helping advice
I did like you said and voila, GPS problem is history.
But what problem I still have is that I can´t flash any 5.x.x custom ROMs. Flashing goes well, but when it is time to reboot, my i9305 stuck to somekind of loop. I can flash stock ROM 4.4.4 and custom ROMs 4.4.4 as well, but Lollipop doesn´t work.
First time I had this problem was when I flashed some 5.1 ROM ( I don´t remember what was it ) But in that ROM suddenly happen that "Google services has stopped" or something like that. I couldn´t do nothing with phone. That error came again and again to phone´s screen..
So I was in situation that I had to flash stock 4.4.4 stock ROM. eveything went well, but GPS didn´t work anymore. Then I found your advice and I thought that now I can again flash custom ROMs as well. Flashing any custom 5.x.x ROM goes well, but in reboot, pghone stuck to loop.
Or had I wait longer in first time I reboot phone after flash?
Thank you so much in advance
/markkus
Click to expand...
Click to collapse
I don't know if it is related to your problem, but I had many problems with 5.X.X builds boot looping because of wrong gapps package. For example, using PA gapps with CM12.1 or Resurrection Remix causes a bootloop, but just flashing the rom and rebooting doesn't cause any bootloop at all. You might want to flash just the rom and let it boot. Cheers

I tried this and it ****ed my IMEI and efs folder i think my phone is dead

xellosx said:
I tried this and it ****ed my IMEI and efs folder i think my phone is dead
Click to expand...
Click to collapse
Can you confirm that your IMEI is really f***ed by flashing this zip file in recovery? Always helped me to bring back my IMEI (uploading to Gdrive ATM)
Edit: https://drive.google.com/file/d/0B9NUrR6bPQUxT2R6cWNiNHBTdjg/view?usp=sharing here you go.

I fixed it by flashing an official stock rom but thanks any way

Thank god for this fix, had to do it manually coz flashing the zip in recovery didn't work out for me. Thanks!
Sent from my GT-I9305 using Tapatalk

Thank you so much bruh
Sent from my GT-I9305 using Tapatalk

Help quick please!
I am with 4.4.4<<<[KK][STOCK][TW][STABLE][+AROMA] N4 Elite Lite v12, but location issue like others.
I made this solution here with NV REBUILD, but when my phone restarts it was SIM LOCKED and ask me for PIN UNLOCK
My phone was never locked before, but now is locked. What to do please?

lubo_uni said:
I am with 4.4.4<<<[KK][STOCK][TW][STABLE][+AROMA] N4 Elite Lite v12, but location issue like others.
I made this solution here with NV REBUILD, but when my phone restarts it was SIM LOCKED and ask me for PIN UNLOCK
My phone was never locked before, but now is locked. What to do please?
Click to expand...
Click to collapse
I just did the "Fix" GPS is fixed but my phone is locked!!
Whats the deal how do I unlock it again?

bigbossa said:
I just did the "Fix" GPS is fixed but my phone is locked!!
Whats the deal how do I unlock it again?
Click to expand...
Click to collapse
Ok managed to unlock my phone using this method
http://forum.xda-developers.com/galaxy-s3/help-i9305/sim-card-unlock-samsung-galaxy-s3-gt-t2185866
if you need a link to JB 4.1.1 you will have to register (use chrome browser to translate automatically)
https://www.samdownloads.de/download/i9305xxali5-4-1-1-germany-t-mobile/
GPS Fix still works

Thanks so much! This worked for me on AMCHA Rom KK v6.10.
I had previously upgraded to a 5.x ROM and then downgraded and I think this is when the GPS had stopped working.
I ran through the provided steps and did not get a Sim Lock error after reboot either.
Legend!

thnx @MaHo_66
works like a charm..

lubo_uni said:
I am with 4.4.4<<<[KK][STOCK][TW][STABLE][+AROMA] N4 Elite Lite v12, but location issue like others.
I made this solution here with NV REBUILD, but when my phone restarts it was SIM LOCKED and ask me for PIN UNLOCK
My phone was never locked before, but now is locked. What to do please?
Click to expand...
Click to collapse
bigbossa said:
I just did the "Fix" GPS is fixed but my phone is locked!!
Whats the deal how do I unlock it again?
Click to expand...
Click to collapse
bigbossa said:
Ok managed to unlock my phone using this method
http://forum.xda-developers.com/galaxy-s3/help-i9305/sim-card-unlock-samsung-galaxy-s3-gt-t2185866
if you need a link to JB 4.1.1 you will have to register (use chrome browser to translate automatically)
https://www.samdownloads.de/download/i9305xxali5-4-1-1-germany-t-mobile/
GPS Fix still works
Click to expand...
Click to collapse
To all using this method, if your device has been unlocked by someone,
THIS METHOD WILL RE-LOCK IT
Solutions:
You're probably on the knox bootloader, and to use the commands of that xda thread, you need a 4.1 rom.
But you can't flash a 4.1 rom because it will fail on the bootloader, so you need a 4.1 with 4.3 bootloader in ODIN format.
Here's one, fzeta is a forum member, all credits to him:
http://www.mediafire.com/download/9y2xo8a16w41eyr/Firmware_4.1.1_Modificado_for_fzeta.zip
Flash the rom, unlock the device with the known commands, and then re-flash philz recovery by known methods, and you're done.

*#0011# gets me into service mode but Q0 doesnt work for me on 4.4.4
any other codes?

thanks work for me

[Help Thread] BLU R1 HD - Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
BLU R1 HD
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@bullet25
@triggerlord
@jasonmerc
@ColtonDRG
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for BLU R1 HD
[Index] BLU R1 HD - Amazon and OEM Variants
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]BLU R1 HD[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: Can I root the BLU R1 HD?[/SIZE]Yes. for the Amazon Variant please see these posts:
Original Root Post Here (Includes TWRP)
Or Step-by-Step Root Here (Includes TWRP)
For the OEM Variant please see this post:
Step-by-Step Root (Includes TWRP)[SIZE=+1]Q2: Can I unlock the bootloader?[/SIZE]Yes for the Amazon Variant please see this post:
Bootloader Unlock
For the OEM Variant please see this post:
Step-by-Step Root (Includes TWRP)*Forum Rules | New Users Guide | XDA Tour | Report PostsA special thanks to everyone who contributed to the production of this FAQ

revered #2

Yo, I'll help. I'm stalking these forums 24/7 anyway.

Manual Camera Compatibility
Does it fully support the Camera2 API for use with manual camera apps?

TorrentialTech said:
Does it fully support the Camera2 API for use with manual camera apps?
Click to expand...
Click to collapse
Give me an app that uses Camera2 API and I'll test it and let you know.
Also @bullet25 I can never sleep anyway so add me to this glorious list, if you'd be so kind

jasonmerc said:
Give me an app that uses Camera2 API and I'll test it and let you know.
Also @bullet25 I can never sleep anyway so add me to this glorious list, if you'd be so kind
Click to expand...
Click to collapse
play.google.com/store/apps/details?id=pl.vipek.camera2_compatibility_test&hl=en This should do it

TorrentialTech said:
play.google.com/store/apps/details?id=pl.vipek.camera2_compatibility_test&hl=en This should do it
Click to expand...
Click to collapse
Doesn't look too pleasing.

jasonmerc said:
Doesn't look too pleasing.
Click to expand...
Click to collapse
Oh, that's a shame. I was hoping it would support Camera2 being such a recently launched phone. Hopefully it would work with a simple build.prop edit like the Redmi Note 3 or the Moto X Style.

TorrentialTech said:
Oh, that's a shame. I was hoping it would support Camera2 being such a recently launched phone.
Click to expand...
Click to collapse
There's always other alternatives that use their own camera drivers rather than manufacturer-bundled ones. Open Camera for one is a very good app that does not depend on device bundled camera drivers. It is very feature-rich and can be a powerful camera app if used in the right hands. Open Camera might be able to do what you're looking to do:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera

Thought I would ask this in the right thread.
My Amazon subsidized R1 HD is rooted with systemless Xposed installed. I did take the OTA update last week. It had been working fine for two days. I powered the phone off and placed on the charger, at which point it keeps continuously attempting to boot, just flashing the White Blu screen every 4-5 seconds. No combination of button presses, or holding of power seems to be able to stop it, so can't power the phone down, or get into TWRP. Ideas? It does not have a SIM in it at the moment, or when this occurred if that might matter.
While I have rebooted the phone many times since rooting, this may have been the first time that I have completely powered it down since rooting and installing TWRP this weekend. I had not made any changes to anything for a day or so, and it had survived many reboots. The only thing I can think of is that I did freeze the Amazon Offers App in TiBu to see what would happen, however, not sure that is in anyway related since it is not even getting to a point in the startup where it would check.
Is there some kind of boot verification Power Up, that does not occur on reset, where the modified Boot image of SuperSU would be the issue?
The only response I can get from the phone is that if I hold Volume+ and Pwr, the phone takes a few more seconds between reboots.....

ariesgodofwar said:
Thought I would ask this in the right thread.
My Amazon subsidized R1 HD is rooted with systemless Xposed installed. I did take the OTA update last week. It had been working fine for two days. I powered the phone off and placed on the charger, at which point it keeps continuously attempting to boot, just flashing the White Blu screen every 4-5 seconds. No combination of button presses, or holding of power seems to be able to stop it, so can't power the phone down, or get into TWRP. Ideas? It does not have a SIM in it at the moment, or when this occurred if that might matter.
While I have rebooted the phone many times since rooting, this may have been the first time that I have completely powered it down since rooting and installing TWRP this weekend. I had not made any changes to anything for a day or so, and it had survived many reboots. The only thing I can think of is that I did freeze the Amazon Offers App in TiBu to see what would happen, however, not sure that is in anyway related since it is not even getting to a point in the startup where it would check.
Is there some kind of boot verification Power Up, that does not occur on reset, where the modified Boot image of SuperSU would be the issue?
The only response I can get from the phone is that if I hold Volume+ and Pwr, the phone takes a few more seconds between reboots.....
Click to expand...
Click to collapse
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.

bullet25 said:
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.
Click to expand...
Click to collapse
Thanks! Yeah, it is not booting anywhere other than the White Screen that say BLU, so I can't even get to adb or TWRP (If I could I could fix it). Letting it die is my only other thought....... I was using a Nexus charge block, and a 3rd party cable which has been sketchy in the past, so maybe related to that.
But as you say, it may be hardware related, as it does not even seem to be going far enough in boot process to load Fastboot, let alone OS.
I raised a replacement request with Amazon just in case.....

Question on Encryption.
I have root and TWRP working correctly. My work Outlook profile requires (and I want) device encryption. I select the option to encrypt, enter my pin, get the Android guy gear cut in half thing icon for about 30 seconds then just a black screen. I let it sit like this for over an hour and nothing changed, so I rebooted. Phone isn't encrypted. Tried it again and got the same result. Am I missing something obvious here? Can you not encrypt if you have unlocked or something? Thanks!

brockwitting said:
Question on Encryption.
I have root and TWRP working correctly. My work Outlook profile requires (and I want) device encryption. I select the option to encrypt, enter my pin, get the Android guy gear cut in half thing icon for about 30 seconds then just a black screen. I let it sit like this for over an hour and nothing changed, so I rebooted. Phone isn't encrypted. Tried it again and got the same result. Am I missing something obvious here? Can you not encrypt if you have unlocked or something? Thanks!
Click to expand...
Click to collapse
I know with other phones you can do encryption with an unlocked bootloader, I don't know about this one. Either something is wrong with the phone's encryption or I honestly don't know. I'll try encrypting mine when I get a chance.

@brockwitting Encryption seems to be working. You have to unroot first and have a pin/patteren/or password to unlock the device. After that go through the encrypt steps. My phone shows the Android cut in half logo for about 10 second then a black screen for about another 30. It then rebooted and was at just the wallpaper. I hard shutdown by holding the power button then rebooted again. After I got a pin unlock screen after inputting the pin I had to press the power button, this might be normal I've never actually used android encryption before, and the phone was working fine since.
Screenshot
You can reboot into recovery afterwards and reroot.

bullet25 said:
@brockwitting Encryption seems to be working. You have to unroot first and have a pin/patteren/or password to unlock the device. After that go through the encrypt steps. My phone shows the Android cut in half logo for about 10 second then a black screen for about another 30. It then rebooted and was at just the wallpaper. I hard shutdown by holding the power button then rebooted again. After I got a pin unlock screen after inputting the pin I had to press the power button, this might be normal I've never actually used android encryption before, and the phone was working fine since.
Screenshot
You can reboot into recovery afterwards and reroot.
Click to expand...
Click to collapse
Sorry for the noobishness here, is there an easy way to temporarly Unroot without doing a full device restore to my pre-root state?

brockwitting said:
Sorry for the noobishness here, is there an easy way to temporarly Unroot without doing a full device restore to my pre-root state?
Click to expand...
Click to collapse
Open the SuperSU app, go to settings and there's an option for Full Unroot. Select that, reboot, then do the device encryption. After you verify its working okay reboot back into recovery and flash SuperSU again. TWRP will ask for your password, just enter your password/pin when it does.

bullet25 said:
Is it booting into android at least? If it is you can try:
Code:
adb reboot recovery
then in twrp do a default wipe (data, cache, dalvik) then see if everything is fine afterwards.
If not, try just letting it do its thing until it dies then see if it acts normal.
Otherwise its probably a hardware issue and needs to be replaced.
I've shutdown and booted mine several times with the TWRP and Root installed so I don't think its that.
Click to expand...
Click to collapse
So, just wanted to close the loop in the event anyone else runs into this. After 7 hours of rebooting every 3 seconds, the battery ran out. The phone then turned on just fine when I attempted to restart it.......... very odd, but all seems well.

ariesgodofwar said:
Thanks! Yeah, it is not booting anywhere other than the White Screen that say BLU, so I can't even get to adb or TWRP (If I could I could fix it). Letting it die is my only other thought....... I was using a Nexus charge block, and a 3rd party cable which has been sketchy in the past, so maybe related to that.
But as you say, it may be hardware related, as it does not even seem to be going far enough in boot process to load Fastboot, let alone OS.
I raised a replacement request with Amazon just in case.....
Click to expand...
Click to collapse
Well spft is still an option. At the point of power off to power on there is a pause on Android that spft uses to inject a DA program of sorts (download assistant). So try to do a readback of the first like 5mb. The read back information dosent matter itbis the DA injection your looking for. If it works the on off cycle should stop. Then unplug and phone should be off

[Q&A][ROM][7.1] LineageOS 14.1 for Xperia T, TX, V

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About this Q&A thread for LineageOS
Use this area to ask anything you want related to LineageOS,
but try not to spam everyone, always search for an answer before.
LineageOS 14.1 for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/-/-/-t3529554
Xperia TX (Hayabusa) : http://forum.xda-developers.com/-/-/-t3529555
Xperia V (Tsubasa) : http://forum.xda-developers.com/-/-/-t3529556
General Questions & Answers
Is root access included into LineageOS ?
No longer included by default to improve user security.
An addon is shared to add SuperUser features : https://download.lineageos.org/extras.
It will survive to updates the same way GApps do.
Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.
Is the ROM suited for daily usage ? Google Apps compatible too ?
Yes but work in progress. OpenGApps recommended.
Can I flash LineageOS on official and development builds, or even on CM without wipes ?
Migrations from unofficial to official, and from CM builds, are allowed with an experimental migration.
Read more about it here : http://lineageos.org/Update-and-Build-Prep/
Always remember to do backups before doing such changes.
Is the device encryption supported ?
State unknown. If you're coming from an older ROM
please read the details here : a07afb9660a86f702066003b8e81ab63789d1660
When USB connected to a computer, I can't access the storage ?
The phone is in charge-only mode by default on Nougat,
due to a stronger security logic regarding unauthorised data access.
Swipe down the notifications and change the USB mode.
I can't access the ROM's recovery with Volume-
You can either flash the boot.img from the newer Releases with "fastboot flash boot boot.img" or FlashTool,
or follow the instructions of the TWRP Recovery installation to update from TWRP.
Due to an unknown issue in data, the partition still looks like a 2GB
Although very unlikely, it may be possible that your data had an error
that could not be fixed automatically by the time you did the UserData Unification.
Read the ROM instructions and check downloads links on the device's LineageOS Wiki page.
Export the resize_userdata.zip from the unify_userdata zip (from UserData Unification),
and flash it from your recovery. If it works, problem solved.
Against advice, I upgraded without GApps and now it crashes. Any way without factory reset ?
Yes there is, but nothing assures you'll manage to do it fully & preserve all your data...
Once booted, keep saying Ok to all "Unfortunately, ... has stopped",
pull-down the notifications panel, press the Settings icon,
go in Apps, menu, Show System, scroll to Setup Wizard (green Android logo),
Permissions, and activate Contacts + Telephone.
Later, some Play Store apps may need reinstalling.
If not working, then I advise a clean factory-reset reinstallation...
About the battery failure on the Xperia T
If you experience battery issues, please read this : https://forum.xda-developers.com/showpost.php?p=70640214&postcount=8
The AOSP Keyboard does not support swipe gestures ?
Unfortunately the sources for swipe gestures are not available
and Google still requires their prebuilt library to be there for AOSP Keyboard.
Download the following libjni_latinimegoogle.so API 23 from OpenGApps
and push it to /system/lib/libjni_latinimegoogle.so using root access,
or use my one-time install zips : https://mega.nz/#F!ThEAkCRa!byhSwuoTbf6lnC1JxgKrig.

@Adrian DC will the ROM already Support OTA?
@ all
btw. this nice [MOD][SOUND][CM,AOSP][6.0+]SonySoundEnhancement&ViperAudio works with this first Build (Screenshots)

Sina Pack said:
Hello everyone
Which on better?!?!
CM13.snapshat or this ROM
Click to expand...
Click to collapse
Depends what is important for you :silly:
Both working Flawless. :good:
If you want to run MODs like Xposed you have to run Android 6.x (CM13) because the most MODs have no integration for Android 7 until now
If you want the new feautres of Android 7.x you shoud run LinageOS

First of all, a HUGE thank you for your work! Your ROM builds for the Xperia T brought my phone back to life, better than before. Now, I have installed the latest version of LineageOS 14.1, but I am experiencing a small problem. The ROM flashes TWRP 2.8.5 if I recall correctly, but that version does not have an F2FS option for file system. Can you please upgrade the TWRP to the newest version or skip flashing of recovery partition? Also, the TWRP in the AOSP build seems to play better with the device recognizing that Unified UserSpace thing Sony did to the Xperia T. My other problem is, that when I flash the LineageOS ROM, even though I formatted the /system and /cache partitions to F2FS with TWRP 3.0.2.0 after flashing the ROM, the /system partition reverts back to Ext4. Can you convert the ROM to have full F2FS support, maybe even including /data partition?

Also, does anyone have a problem, where you can make and receive calls, use Data connection but can not import contacts from SIM card? The contacts app and various SIM managers find 0 contacts on SIM card.

Your ROM is so awesome, thanks for this. But I see that Root Access options in my Developer Options include only "Disabled" and "ADB only", "App and ADB" option is missing. Can I ask you that this missing option is missing because of your setup ? And can I use your BootBridge to flash SuperSU for this ROM ?

First off thanks Adrian DC for keeping the Xperia T relevant! When I first hear that CM was going offline I immediately started looking for another phone, but I was elated to find out you had decided to work on Lineage OS. I flashed the latest ROM 2 nights ago and I can say that this update is much more quicker and stable for me at least than the last CM 14.1 that I was running from the Christmas night upload. I did notice the Root issue and am not concerned about that right now. The one thing I am concerned with is that I seem to be running through some battery. Is anyone else seeing this issue, my battery life is terrible right now. Thanks again for the great work!!

About battery failures and instant power-offs
Here's a small report about the Xperia T battery failure that I also experienced :
As a few of you reported already, it is quite known that the Xperia T
has a battery that does not survive nicely to years of heavy usage.
Released and sold in 2012, the Xperia T has an inbuilt battery that is not meant to be replaced,
the model is a 3.7V 1780mAh 6.6Wh battery with integrated controller and 3 pins clip plug.
The issues seen when the battery is about to die are random battery drops during reboots
(20+% disappear randomly, reappear later sometimes), below 15% the device goes off fast,
and recharging the device with a wall charger goes high quite (too) fast.
When the battery is truly dead, the device powers off randomly under heavy usage,
for example while taking a picture and the autofocus starts moving or using an USB drive.
Random power-offs also occur while using the device a lot like charging + GPS and such.
The biggest issue is that under a very low level of battery depletion, the device won't power on anymore
even if plugged to offline charge it, only 3 red lights will flash and the device will never boot again.
A solution I found to work multiple times with that situation is to open the device's back (really easy on the T),
unplug the battery plug, connect the USB cable from a wall charger, wait 1-2 seconds,
then directly replug the battery in place to see the device boot in offline charger.
Then leave the phone charge to 100% without interaction.
Small unsure side-effect, after 2 weeks of these mentioned issues, I stopped reviving it,
and ordered a new battery, but the MicroSD was fried. Likely related to the failure but no proof.
About replacing the battery on the Xperia T :
I ordered a "brand" new battery for the Xperia T, the goal is to absolutely avoid fake copies
and try to find a battery identical and original from Sony, otherwise results are unknown.
I bought my battery for 9€ therefore it stays a decent revival of a device that runs properly.
Replacing the battery involves removing the main motherboard flex that goes over the battery,
slightly bend it away from the battery without harming the triple flex plugs on the base of the battery.
Then removing the battery with a bank card takes some work but goes fine with patience.
Harming the flex at the base has to be avoided at all costs, battery can be removed slowly
with an angle to avoid unplugging the flex or touching it in any way.
Boot the battery with my technique and let it charge to 100%.
Then rebuild the device, it should be back to normal usable status.
Posted this as small hints for those experiencing the Xperia T battery issues.

Hi, think my problem fits better in here than in the XT-LineageOS-thread:
Since upgrading to LineageOS14.1 (29.1.17) I can't access the external SD-Card; Lineage-FileManager tells me to try it with root-rights (yea...)
Pretty sure it must be one little "Switch" to trigger, but I have no idea... Thanks for any hints
----------
As for the Battery-Issue:
I had that one several times, but no need to replace it:
First time I encountered it, I installed PacmanROM (think based on Android 5; nothing to loose when the battery is dying, right?) - battery worked well again, for another year - then showed the same "drop to 20% and gone"-symptoms; to revive, I installed CM12 - solved the problem; again one year later (last summer), again the battery... Installed CM13 (thanks Adrian - solved the problem again.
(...thinking about it, maybe I installed CM14.1 too early? ) Everytime, the XT had its old "run-time" (of about 4 days) back it had when first activating it in 2012; before upgrading, the battery hardly lasted one day...
I always made a clean-install including TWRP-upgrades... Maybe a change to a higher version triggers a setting in/for the battery? (eg. "planned obsolency")
---------
Edit:
took a shortcut with the SD-Card; as I could access it via USB I copied all data from it, inserted it back to the XT and initialized it (as external). With the newly possible access, I copied the files back. Seems to be working...

Have a problem with Wi-Fi on Xperia T (mint)
Status bar and settings say "connected, no internet", PlayStore "Check your connection an try again", so I can't install an application.
But Browser is working fine, searching for updates in "About Phone" too, means I have internet.
Have official Lineage Nightly 31st january.
I have already installed it for three times and tried another Wi-Fi, but doesn't work.

ArmW said:
Have a problem with Wi-Fi on Xperia T (mint)
Status bar and settings say "connected, no internet", PlayStore "Check your connection an try again", so I can't install an application.
But Browser is working fine, searching for updates in "About Phone" too, means I have internet.
Have official Lineage Nightly 31st january.
I have already installed it for three times and tried another Wi-Fi, but doesn't work.
Click to expand...
Click to collapse
Seems like your phone can't connect to the preferred DNS server at the moment.
try changing that.

Camera touch focus not working
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?

farooq666 said:
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?
Click to expand...
Click to collapse
It was missing for me too, reverting back to the lineage-14.1-20161231-UNOFFICIAL-mint build fixed it, but it did not fix my issue with the SIM contacts Did you try the builds from the official Lineage OS website?

What about battery life in TX? I'm planning switch back to Xperia T or TX cuz by now I'm using a Moto E 2nd Gen LTE and it doesn't work with the 3G/4G band of my carrier and Moto E's cameras sucks
Btw I saw that in Amazon (See attachment)
As far I'm concerned change the battery of T is a pain in the ass, So is better try again with a TX, isn't it?

farooq666 said:
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?
Click to expand...
Click to collapse
jkristof94 said:
It was missing for me too, reverting back to the lineage-14.1-20161231-UNOFFICIAL-mint build fixed it, but it did not fix my issue with the SIM contacts Did you try the builds from the official Lineage OS website?
Click to expand...
Click to collapse
It's works in '20170214' build

Hi,
I am experiencing recently SoDs again.
I am using a Xperia V (tsubasa) just as a music player.
So only pure LinOS 14.1 without GApps.
It happens always during the night and if it is not charged.
Last night the battery was below 20% when it happened. The other times before I did not pay attention to the battery.
Battery was chenged in 10/2017 and was a new one.
Also I must say the RAM usage is very high. The Android system alone consumes 325MB. But I am not sure if it is related to the SoD.

AdrianDC,
Is there a way to extract the cast feature from the ROM and install it on other devices? Cast in Lineage OS is awesome and works flawlessly, and Samsucks screen mirroring doesn't even work on my same brand TV from my tablet, but Cast works every time.

Gallery shows images twice
After upgrading to lineage-14.1-20170310 (Xperia V), every Gallery-App (Stock, Gallery from F-droid) or Apps with access to images are showing every image twice. Properties of the "gemini-images" will show different paths,
i.e.
/sdcard/Pictures
/storage/emulated/0/Pictures
or
/sdcard/Download
/storage/emulated/0/Download
Has anyone else encountered this issue, too?

unifying the user data trouble guide
I wrote this in the hope this will soon be obsolete. I never succeeded installing lineageOS the official way. I had reproducible errors unifying the user data. I also hard bricked a Xperia V. I wrote a workaround step by step guide which will hopefully work not just for me. I know it sounds a bit crazy but as I did it quiet often and always succeeded by miracle, I wanted to find a reliable way. Everybody interested in the trouble which happens sometimes see attached recovery logs. This guides logs are in the folder UnifySucess. To find the interesting part search for mmcblk0p14. Perhaps it's also useful for diagnostics.
this is made on XPERIA V, if you want to follow this guide for another model you have to replace the files with tsubasa in its name.
EDIT: this is obsolete now
files used:
twrp-3.0.3-20170224-boot-tsubasa.img
recovery-13.0-20161221-SNAPSHOT-ZNH5YAO3Y8-tsubasa.img
lineage-14.1-20170303-nightly-tsubasa-signed.zip
unify_userdata-20170128.zip
restore_sdcard-20170128.zip
cleaner-fota-tsubasa.zip
coming from stock
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
wipe System, Cache, Data, Legacy SD
flash unify_userdata-20170128.zip twice
if there is a failure ignore & flash lineage-14.1-20170303-nightly-tsubasa-signed.zip , gapps (optional)
reboot system ( not sure if necessary )
look into settings if storage is OK, you are done if not reboot bootloader
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
flash restore_sdcard-20170128.zip twice
reboot to bootloader
fastboot flash boot recovery-13.0-20161221-SNAPSHOT-ZNH5YAO3Y8-tsubasa.img
fastboot reboot
in CWM
full factory reset
flash unify_userdata-20170128.zip twice
reboot to bootloader
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
Internal Storage should now be bigger than 2GB, if so
flash lineage-14.1-20170303-nightly-tsubasa-signed.zip , twrp-3.0.3-20170224-fota-tsubasa.zip, gapps (optional)
If you are stuck and already installed the twrp-fota-tsubasa.zip there is a tool from AdrianDC to remove TWRP called cleaner-fota-tsubasa.zip
this is written in the hope to be useful, I'm not responsible for any failures.

guide update
I tried once with TWRP 3.1.0-0 and it did the trick - not initial but instead of CWM.
I am happily hoping not to need the recovery-13.0-20161221 and the cleaner-fota anymore.
@xperanto: I took a short look into the gallery after a clean install and there were no doubles

Bootloop Realme x2 pro RMX1931EX

Hello
I have the RMX1931 with the bootloader unlocked and the twrp recovery [3.3.1-13] installed
I want reset my phone because have random reboots.
Download RMX1931EX_11.A.10 for twrp
First wipe this partition
Cache
Dalvik
Data
Click to expand...
Click to collapse
Then flash
Ozip RMX1931EX_11.A.10 for twrp
Vbmeta
Magisk
Click to expand...
Click to collapse
But dont boot in system
first boot not see realme logo and reboot in twrp
i try restored old backup twrp clear device but same results.
only work backup twrp with data partition full, that I did before starting this experiment.
I believe it is the given partition that makes the device boot. With this clean partition it goes into bootloop
please help me

Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot

perisman said:
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
Click to expand...
Click to collapse
Tonight i try.
Thank you

perisman said:
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
Click to expand...
Click to collapse
you are a genius.
IT WORKS.
Now I have installed the A10 system and restored the app backup via swiftbackup.
everything seems to work, I hope it will not restart.
if you can give me more advice.
thank you very much.
EDIT :
The phone continues to restart.
I'm thinking it can be Magisk root.
Without applications installed
I went crazy with this problem

You can try with last update C25. I flashed from twrp, and now t'he device works fast and smooth. I have magisk, viper4android installed. T'he only problem us FP, because unlocked BL. You can try with a custom ROM, I have tried phh treble and aosip 10, and works very well, and FP works also. You cqn revert to color os 6.x allways flashing A10 ozip. If with other ROMs hsppens t'he random reboots, then is a hardware problem.

it is a real dilemma because with the clean system, however, the phone has restarted for no obvious reason.
I can't understand what makes the phone restart.
only Magisk could be the cause.
I installed Magic which recommends Jerry. but even with the standard version the problem was always the same
Now I send you a screen so it's better evident.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try Another rom, clean system one day to see what It happens

Yes I try In These Days.
Thank you so much for your support

perisman said:
Try Another rom, clean system one day to see what It happens
Click to expand...
Click to collapse
I am now testing the LINEAGE it happened to me this I removed the SIM card and I installed the costum Rom, I made the various customizations and the phone never locked OR restarted.
I inserted the SIM card in the phone worked perfectly, then having messed up with luckypatcher I had to reinstall the Rom.
So I performed the same procedure with the SIM card inserted in the phone and already at the first start it was unstable with reboots.
Currently I have applied for a change of sim card.
As soon as it arrives I will try to remove the sim card Install from scratch The system is to insert the new SIM card only so I can have the mathematical certainty that it is the SIM card
I hope my experience can help someone

perisman said:
You can try with last update C25. I flashed from twrp, and now t'he device works fast and smooth. I have magisk, viper4android installed. T'he only problem us FP, because unlocked BL. You can try with a custom ROM, I have tried phh treble and aosip 10, and works very well, and FP works also. You cqn revert to color os 6.x allways flashing A10 ozip. If with other ROMs hsppens t'he random reboots, then is a hardware problem.
Click to expand...
Click to collapse
i try lienage os, but now i want return colorOS.
i try flashing A10 colorOS.ozip but color OS Boot Loop (Stuck in Realme Logo)
you have solution? for now flash lineageOS and work well but i want colorOS.
please help me

-First, change twrp. Install orangefox or skyhawk twrp (I am using skyhawk and I can revert from C10 trebled rom to
C26 backup, firsr install C26 ozip, and after first boot, reinstall twrp from fastboot and restore full backup)
-Reboot to twrp
-Flash full Ozip , I recommend C26. Works very well, antutu 501.850, no lags, with viper4android installed. With
lineage 371.056 in antutu
-flash vbmeta
-flash magisk
-format data
-reboot
-Once system boots to system, reboot to fastboot to reinstall twrp (with ozip install, you have stock recovery,
check this booting it, depends of twrp you are using. Orangefox saves twrp, skyhawk no)
I hope it helps

I should follow these steps
1 - flash recovery skyhawk twrp
2 - Reboot to twrp
3 - Flash full Ozip (i prefered pie have Fingerprint work)
4 - flash vbmeta
5 - flash magisk
6 - format data
7 - reboot
I have already done these steps with the (ozip A10 FOR TWRP) but color OS Boot Loop (Stuck in Realme Logo).
do you think that recovery creates this problem?
i now have lineageOS work but want return colorOS
thanks for the support
EDIT:
I have run your advice but unfortunately this device perhaps has a hardware problem.
Whenever it manages to boot, just 30 seconds and restart.
I noticed artifacts when starting the sistama.
I'm really desperate.
what do you advise me to do?
thanks

westenlive said:
I am now testing the LINEAGE it happened to me this I removed the SIM card and I installed the costum Rom, I made the various customizations and the phone never locked OR restarted.
I inserted the SIM card in the phone worked perfectly, then having messed up with luckypatcher I had to reinstall the Rom.
So I performed the same procedure with the SIM card inserted in the phone and already at the first start it was unstable with reboots.
Currently I have applied for a change of sim card.
As soon as it arrives I will try to remove the sim card Install from scratch The system is to insert the new SIM card only so I can have the mathematical certainty that it is the SIM card
I hope my experience can help someone
Click to expand...
Click to collapse
Hi, I also have rebooting issues does your X2 pro still reboots? Did changing sim cards solved your reboot problem Im getting desperate.

JKD23 said:
Hi, I also have rebooting issues does your X2 pro still reboots? Did changing sim cards solved your reboot problem Im getting desperate.
Click to expand...
Click to collapse
sorry to tell you but unfortunately this phone has an underlying problem ie the modem hardware is of poor quality.
I have done 1000 tests I have tried everything and more but unfortunately it keeps restarting the user interface when a call comes in or when you try to make a call.
especially when you keep the modem busy for other chores such as navigation with Google Maps or other and you receive a call the phone suffers a stress and this causes a restart.
I have given myself this explanation because it is truly inconceivable that a top-of-the-range phone has these problems.
if you find a solution Let me know.
Thanks so much

westenlive said:
sorry to tell you but unfortunately this phone has an underlying problem ie the modem hardware is of poor quality.
I have done 1000 tests I have tried everything and more but unfortunately it keeps restarting the user interface when a call comes in or when you try to make a call.
especially when you keep the modem busy for other chores such as navigation with Google Maps or other and you receive a call the phone suffers a stress and this causes a restart.
I have given myself this explanation because it is truly inconceivable that a top-of-the-range phone has these problems.
if you find a solution Let me know.
Thanks so much
Click to expand...
Click to collapse
Sorry to hear that ? I'm also suspecting that I have hardware problem it only reboots when connecting to LTE mobile data. I already tried using flash tool for a clean flash didnt work though.
I'm still hoping it's a software issue because I can still get LTE signal I just can't use mobile data. I kinda regretted buying this phone. I'm so unlucky I got a defective device. ?
If I find a solution I'll let you know.

JKD23 said:
Sorry to hear that [emoji853] I'm also suspecting that I have hardware problem it only reboots when connecting to LTE mobile data. I already tried using flash tool for a clean flash didnt work though.
I'm still hoping it's a software issue because I can still get LTE signal I just can't use mobile data. I kinda regretted buying this phone. I'm so unlucky I got a defective device. [emoji24]
If I find a solution I'll let you know.
Click to expand...
Click to collapse
Basically these have mounted a modem on this phone which in my opinion is not fully compatible with the Snapdragon.
In fact, the price is really very low if you consider that this is a top-of-the-range Smartphone with a 90 Hertz screen and latest generation processor.
They are practically giving it away now on the official website it costs € 350.

westenlive said:
Basically these have mounted a modem on this phone which in my opinion is not fully compatible with the Snapdragon.
In fact, the price is really very low if you consider that this is a top-of-the-range Smartphone with a 90 Hertz screen and latest generation processor.
They are practically giving it away now on the official website it costs € 350.
Click to expand...
Click to collapse
Realme should acknowledge these problems and improve the quality of their units. Let's hope Realme Dev team would release updates that could fix our units. (fingers crossed)

JKD23 said:
Realme should acknowledge these problems and improve the quality of their units. Let's hope Realme Dev team would release updates that could fix our units. (fingers crossed)
Click to expand...
Click to collapse
Dear
since you texted me I have been looking for the problem once again.
I have ILIAD as an operator.
I had self-configuring SMS sent for APNs.
With the new APN the problem seems to have disappeared.
try it too and let me know
hello [emoji1309]

westenlive said:
Dear
since you texted me I have been looking for the problem once again.
I have ILIAD as an operator.
I had self-configuring SMS sent for APNs.
With the new APN the problem seems to have disappeared.
try it too and let me know
hello [emoji1309]
Click to expand...
Click to collapse
That's good to hear, I tried your suggestion using self configuring apns through sms, my other operator doesn't send me any sms while the other one was not self configuring. Doesn't seems to work for me Ill try again rechecking the APNs. I also pulled an ADB bug report and sent it to Realme Devs through email they haven't replied yet. When I opened it I saw a few errors like but I couldn't understand it since im not a dev but a run some hardware and sensor diagnostics app and all sensors seems to be working fine. I hope the devs would reply sooner.

JKD23 said:
That's good to hear, I tried your suggestion using self configuring apns through sms, my other operator doesn't send me any sms while the other one was not self configuring. Doesn't seems to work for me Ill try again rechecking the APNs. I also pulled an ADB bug report and sent it to Realme Devs through email they haven't replied yet. When I opened it I saw a few errors like but I couldn't understand it since im not a dev but a run some hardware and sensor diagnostics app and all sensors seems to be working fine. I hope the devs would reply sooner.
Click to expand...
Click to collapse
Hi dear
have you tried to update to Version: RMX1931EX_11.C.32.
From the log it would seem that they have solved the problems that happen to us.
I have the phone too full and rooted and I would not like to update to android 10 so I am still stuck on android 9.
Have you updated?

How To Guide Flashing GSI roms on Redmi Note 10S and then fixing some issues, all without any custom recovery

By Following this guide, you will lose your warranty so keep that in mind before you begin. (Although you have probably already lost your warranty by unlocking the bootloader)
This guide will help you to flash any GSI (Project Treble) ROM onto your Redmi Note 10S, and since TWRP, or any custom recovery for that matter, is not yet available, we have to manually install the GSI roms using fastboot (and fastbootd because of the dynamic partition). The process is lengthy but not that difficult.
It should go without saying that you should backup everything and be prepared to lose your data and potentially soft-brick your phone and the experience with GSI roms is not always known to be stable (although I have not seen any such problems yet aside from a few easy-to-fix bugs) so do all of this at your own risk.
Important to note is that if at anytime you mess stuff up or delete partitions you weren't supposed to (whatever the guides may say, don't erase the product partition, it won't help, you're gonna end up in a bootloop) and soft-brick your phone, as long as you can access fastboot you can easily fix the problem by using the MiFlash tool which will help you get back to square one (you won't have to wait to unlock the bootloader again so don't worry about that)
Now, for the disclaimer:
DISCLAIMER: I'm an amateur in terms of tinkering with android stuff and phones in general. The process mentioned below has worked on my phone but I would still recommend waiting for someone more....experienced to weigh in his/her opinions. If you end up bricking your phone or if things go south, I'm not responsible, that's on you.
NOTE: When I mention fastboot I'm referring to the standard "normal" fastboot and when I mention fastbootd, I'm referring to the dynamic/userspace fastboot which is different (which wiil be indicated by the fastboot screens during either of the modes)
I should mention that using this method I have been able to flash DotOS, Android 12 Beta 5, CorvusOS (my current daily driver) and in my daily driver (Corvus OS), It's passing SafetyNet and the WideVine certification is still at L1 even after rooting, however I have tested neither Google Pay nor Netflix, because I don't use either of them so your mileage may vary, however I did find Netflix in the play store so that is a bit encouraging ig.
Alright, with the appetizers out of the way, let's crack on to the main course:
PART 0: Requirements:-
Please ensure that the following requirements are met:
A Redmi Note 10S with an unlocked bootloader
OEM Fastboot driver and Fastbootd driver is installed
A preferred GSI rom (the file extension should be .img)
Being prepared to lose your data
Obtain android platform-tools along with knowledge about how to use it
Acceptance that the newly flashed GSI rom may/may not be completely stable.
Fastboot rom from here
If you have all that, you can move on to the next step
PART 1: Get Straight to Flashin':
This guide is rather straightforward because there really isn't much to it.
To begin with, extract the vbmeta.img from the Fastboot rom. Once you have done that, reboot your phone to fastboot mode.
Once the phone is in fastboot mode, on your computer, run the following command:
Code:
fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
to disable what is the android equivalent of window's secure boot
Once that is done, issue the following command:
Code:
fastboot.exe reboot fastboot
(No, there is no typo here, this is what needs to be done to enter the fastbootd mode, which is where the real fun begins)
Ensure that you are in fastbootd mode. The blue coloured "fastboot" text at the bottom will be replaced by a yellow coloured "fastbootd"
Okay, now for the most important command, type:
Code:
fastboot.exe -u flash system your_gsi_rom_of_choice.img
Done!
After this, don't forget to factory reset your device by:
Code:
fastboot.exe -w
Note: If you forget to do the factory reset, you're gonna end up with a frankenstein combination of your new and some configs of your previous rom, in this case reboot to bootloader (using power and volume down) and issue the factory reset command (fastboot -w)
And then for the toppings:
Code:
fastboot.exe reboot
That's.....about it. You should boot into your chosen rom. For the first time, the boot animation may stick around for a long time (5 minutes or more). However, if, even after an absurd amount of time (15-20), the rom doesn't boot up, try using MiFlash tool to get back to square one and try the whole process again.
Once it boots up, continue with the setup process and you will (hopefully) be at the home screen of your new rom.
PART 2: Le Bugs
Of course, no software is perfect and considering the especially ambitious nature of Project Treble, it is no surprise that you will encounter some bugs. 2 bugs in particular are the disabled headphone jack and the wonky brightness slider.
Here's how I fixed them in CorvusOS (most probably applies in other ROMs as well)
1. Disabled Headphone Jack:
Once you boot up the rom, you'll notice that the headphone jack will not work; the audio will only play on the speaker. To fix this one, you unfortunately need to root your phone (although that's not necessary, try looking into the Device Specific customisations of your rom).
Through your computer, issue the following commands (one-by-one, don't copy-paste them):
Code:
adb shell
su
setprop persist.sys.overlay.devinputjack true
reboot
Your phone will now reboot and once it does, you will see that the headphone jack is functioning normally again.
2. Brightness Slider Fix:
This one does not require any root. However, this does require that you can access the device specific customisations,
So, in my case, I had to go into {Device Name} Settings > Misc features and then tick the Force alternative backlight scale . Once you have done that, reboot and your brightness slider will be working properly again. Also, if you noticed sudden fluctuations after booting or when device goes to sleep earlier, that should all be fixed as well.
Conclusion:
At this point, you should be ready to rock the world along with your phone. Depending upon the rom you have chosen (DotOS for example), your widevine certification and safetynet may be compromised, even after trying out several fixes (which is what happened in my case). So if that happens to you, I suggest that you either change your rom, hunt around for some solutions or just, you know, live with it.
In my case, (As I mentioned before) I'm using CorvusOS where the widevine rating and safetynet are unaffected, with the latter requiring some special fixes.
Hope that helped. I look forward to hearing from you people about any recommendations or discussion. If you have any problem with the process or think that something may be wrong, post it in the replies and I'll be happy to get back to you (depending upon the time, of course)

How much extra battery life are you experiencing compared to stock? kernel tweaks? Any other minor bugs or issues while using it as your daily driver?
Can you please fill the listing for our rosemary device on GSI wiki @ github?
Xiaomi Redmi Note 10S
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com

miravision said:
How much extra battery life are you experiencing compared to stock? kernel tweaks? Any other minor bugs or issues while using it as your daily driver?
Can you please fill the listing for our rosemary device on GSI wiki @ github?
Xiaomi Redmi Note 10S
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Better than stock, using gpu to render UI and powersave governor.

Xiaomi Redmi Note 10S
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Pre-flash info:
Device name: Xiaomi Redmi Note 10S (rosemary)
Earlier rom: MIUI 12.5.7 (India)
Rooted?: No
Tested images:
Corvus OS
Android 12 Beta 5
DotOS
Steps to installRefer to the guide here: https://forum.xda-developers.com/t/flashing-gsi-roms-on-redmi-note-10s-and-then-fixing-some-issues-all-without-any-custom-recovery.4337099/
Hardware Support post flashing
ComponentCommentCameraWorks but Gcam is a little unstableSpeaker/MicWorks, headphone jack requires a tiny tweakBluetoothNot tested but I'm sure it worksWi-FiWorksSIM/Mobile Data/ VoiceNot testedVoLTENot testedFingerprintWorksNFCNot testedOffline ChargingWorksDisplay Refresh rate60hz (same as before)Screen BrightnessWorks like before after a small tweakVolume scaleWorks fine5GN/ASafetyNet post root?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(requires modification)WideVine certification post flash and rootL1 (requires modification)
Personal Notes:
Battery life seems to have reduced a bit
Phone (extremely rarely) reboots out of nowhere.
Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.
Tested by: randomaccessvemuri (@Tanmay-V22315)

miravision said:
Xiaomi Redmi Note 10S
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Pre-flash info:
Device name: Xiaomi Redmi Note 10S (rosemary)
Earlier rom: MIUI 12.5.7 (India)
Rooted?: No
Tested images:
Corvus OS
Android 12 Beta 5
DotOS
Steps to installRefer to the guide here: https://forum.xda-developers.com/t/flashing-gsi-roms-on-redmi-note-10s-and-then-fixing-some-issues-all-without-any-custom-recovery.4337099/
Hardware Support post flashing
ComponentCommentCameraWorks but Gcam is a little unstableSpeaker/MicWorks, headphone jack requires a tiny tweakBluetoothNot tested but I'm sure it worksWi-FiWorksSIM/Mobile Data/ VoiceNot testedVoLTENot testedFingerprintWorksNFCNot testedOffline ChargingWorksDisplay Refresh rate60hz (same as before)Screen BrightnessWorks like before after a small tweakVolume scaleWorks fine5GN/ASafetyNet post root?
(requires modification)WideVine certification post flash and rootL1 (requires modification)
Personal Notes:
Battery life seems to have reduced a bit
Phone (extremely rarely) reboots out of nowhere.
Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.
Tested by: randomaccessvemuri (@Tanmay-V22315)
Click to expand...
Click to collapse
nope, for me it increased.

Personal Notes:
Battery life seems to have reduced a bit
Phone (extremely rarely) reboots out of nowhere.
Raven Launcher (Launcher that comes with Corvus OS) crashes from time to time, taking me back to the lock screen
I personally feel that the speakers are not as loud as they could be but I did not test it before flash so I can't tell precisely.
Click to expand...
Click to collapse
Has anyone faced these issues or any other issues and how did you fix them/ are they unresolved like random reboots or speaker loudness or mic loudness or noise cancellation or bluetooth HD codec support or bt calls or GCam crashes or instability ...
J6idot said:
nope, for me it increased.
Click to expand...
Click to collapse
Can we please see screenshots of battery drain from 100% to 1% with your app usage statistics in hours?

miravision said:
Has anyone faced these issues or any other issues and how did you fix them/ are they unresolved like random reboots or speaker loudness or mic loudness or noise cancellation or bluetooth HD codec support or bt calls or GCam crashes or instability ...
Can we please see screenshots of battery drain from 100% to 1% with your app usage statistics in hours?
Click to expand...
Click to collapse

Thanks for posting the screenshot. I see that you use AMOLED dark mode to save on battery. Any CPU underclock?
Do you happen to face overnight drain issue which is why for 2 nights battery graph shows 2 blank OFF durations?
With regards to the UX with powersave governor for the GPU can you please clarify the following on GSI ROM:
Can you please attach a short 30s - 1 min screen record session by randomly scrolling through stuff while playing some non copyright NCS audio to see if the g95 SOC is powerful enough to render, a full hd screen with scrolling content, smoothly enough with the least battery draining GPU frequencies?
Can you please clarify by means of some random media playing in the background that internal media sounds are recorded properly? Hence game sounds can be captured with/ without the microphone. Thanks

miravision said:
Thanks for posting the screenshot. I see that you use AMOLED dark mode to save on battery. Any CPU underclock?
Do you happen to face overnight drain issue which is why for 2 nights battery graph shows 2 blank OFF durations?
With regards to the UX with powersave governor for the GPU can you please clarify the following on GSI ROM:
Can you please attach a short 30s - 1 min screen record session by randomly scrolling through stuff while playing some non copyright NCS audio to see if the g95 SOC is powerful enough to render, a full hd screen with scrolling content, smoothly enough with the least battery draining GPU frequencies?
Can you please clarify by means of some random media playing in the background that internal media sounds are recorded properly? Hence game sounds can be captured with/ without the microphone. Thanks
Click to expand...
Click to collapse
Alright so, first of all, powersave governor underclocks to 500mhz -774 mhz. Some of the apps don't use the fully black amoled theme. And i keep my phone off overnight.
About the GPU? governor, same stock one because there is no way to change it/downclock it.
When scrolling, seems smooth to me, it might lag a little but i don't care.
And no, microphone doesn't lag.
Everything with CPU rendering (not GPU)

Hey OP, i would like to also add that few sGSI might completely soft brick the phone.
If you install an sGSI, reboot, and then it bootloops after like 5 seconds, the phone will not boot.
I tried one sGSI, got this problem, reflashed DotOS and it still wouldn't boot, as it would be stuck at the boot animation.
I tried:
Reflashing DotOS
Reflashing the boot image
Reflashing vendor/product
Formatting and wiping continuosly the userdata partition. Nothing.
The only way to fix this is by flashing stock.
Also, if your phone reboots after like 10 seconds or more, then bootloops, reflashing the rom you were using will probably work fine.

How well does the latest Android 12 GSI final release, available since a few days ago, work on the 10s?
Please post detailed review with bug fixes and patches required for various issues on the main rosemary treble GSI rom Github repository to help everybody track the progress on the final release of Android 12 on the 10s.

google gsi? idk, never tried.
Someone built it with phh patches and works fine, except you can't turn off the phone with the Power button, you need to do it from the status bar.

Hi, I installed DotOs 5.2 Android R with Gapps version;
Seems to be smoother than MIUI, and comes without so much bloatware, also, play store works better that in MIUI; I will test for a week, and then I will upload battery usage, and gaming performance in emulators like dolphin, citra, (also the bugs that I will encounter, for now, I encountered only 2 bugs, and the OP already solved them).
PD: There is another bug with bluetooth, you just need to go to settings-->PhhTrebleSettings-->Misc--> mark "Force-disable A2DP offload"

Have you stayed on DotOS or moved to a different GSI? Please post battery usage along with other points you mentioned that have gotten better or worse
seyren00 said:
Hi, I installed DotOs 5.2 Android R with Gapps version;
Seems to be smoother than MIUI, and comes without so much bloatware, also, play store works better that in MIUI; I will test for a week, and then I will upload battery usage, and gaming performance in emulators like dolphin, citra, (also the bugs that I will encounter, for now, I encountered only 2 bugs, and the OP already solved them).
PD: There is another bug with bluetooth, you just need to go to settings-->PhhTrebleSettings-->Misc--> mark "Force-disable A2DP offload"
Click to expand...
Click to collapse

if i want to try DotOS which version should i download? theres a64 and arm64, i haven't installed a custom rom on my phone for a long time.

ono123 said:
if i want to try DotOS which version should i download? theres a64 and arm64, i haven't installed a custom rom on my phone for a long time.
Click to expand...
Click to collapse
arm64 a/b

Is it possible to update using this method using this method? Would it just be this?
Code:
fastboot reboot fastboot
fastboot flash updated_image.img

RandomAccessVemuri said:
PART 2: Le Bugs
Of course, no software is perfect and considering the especially ambitious nature of Project Treble, it is no surprise that you will encounter some bugs. 2 bugs in particular are the disabled headphone jack and the wonky brightness slider.
Here's how I fixed them in CorvusOS (most probably applies in other ROMs as well)
1. Disabled Headphone Jack:
Once you boot up the rom, you'll notice that the headphone jack will not work; the audio will only play on the speaker. To fix this one, you unfortunately need to root your phone (although that's not necessary, try looking into the Device Specific customisations of your rom).
Through your computer, issue the following commands (one-by-one, don't copy-paste them):
Code:
adb shell
su
setprop persist.sys.overlay.devinputjack true
reboot
Click to expand...
Click to collapse
I have successfully installed the DotOS ROM after waiting for a week to unlock the bootloader. I want to inform that NFC can work well on DotOS. but I have a question regarding the headphone jack bug, how do I root this phone after installing the GSI ROM, the things you describe are not clear enough for me. can anyone explain further?

Can installing a different rom help with the video playback oversharpening, etc.? I mean all the miravision related issues. And what happends with HDR playback?

ono123 said:
I have successfully installed the DotOS ROM after waiting for a week to unlock the bootloader. I want to inform that NFC can work well on DotOS. but I have a question regarding the headphone jack bug, how do I root this phone after installing the GSI ROM, the things you describe are not clear enough for me. can anyone explain further?
Click to expand...
Click to collapse
Hi,
You can root the phone using the general procedure (or as shown here) But TL;DR:
Get the boot.img from the fastboot ROM (here)
Install the Magisk Manager APK (from official sources only)
Patch the boot.img with the magisk manager
Flash the boot.img by fastboot flash boot patched_boot.img
Reboot and open Magisk manager
It will prompt you to do some stuff after which your phone should be rooted (it should actually be rooted once you flash the boot.img and boot up the phone but Magisk Manager lets you manage superuser related stuff)
At this point your phone should be rooted and you can proceed with the above instructions. However I'm more than confident that you could fix the headphone jack by looking into the Device specific settings. That's how I fixed it in a later install, anyways.

Database Develop

welcome