Develop Bugs

[ROM] [Lollipop 5.0] Stock AOSP

This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!JdYCnSxZ!fn82nMs3mA0VdDBTYuguT9OXHjQtt7P9jnZUyndrtZA
if someone wants to host mirrors let me know.

Does this have the Wifi fix in it? or has Google not published that yet?

Can't wait to install this and try it. I was going to wait it out for the official release but I've broke I have to try it.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
I don't think it will be as Google haven't released the version with the patch yet as that will be the OTA or factory image versions.

ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
most likely not have not tested for any wifi bugs atm

Thank you I'm really excited about it. But I have a question. Can I have use my flash drives in this ROM without stickmount?

ROM
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??

I seem to be unable to install on my Nexus 10. I've followed the stages, but when I get to flashing the AOSP rom it stays on it forever!
I've updated my TWRP to v2.8.1.0 but it does the same thing.
Sorted the problem I think, some how the download I had on my Nexus was not a happy one haha. just on the boot logo now :3

Thank you, booted up and running. One question, I couldn't install Google+. It cannot be found on Play Store and installing from APK doesn't work neither.

Great work, thanks. Flashed about an hour ago, flawless so far!

seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.

gabegom said:
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
Click to expand...
Click to collapse
Same question here. Can we flash after any ROM or do we have to flash stock .imgs first then this?

Is anyone having problems with Wifi? I have flashed this twice and I cannot get Wifi to connect. It sees networks but won't connect to any of them.

ChaosMinionX said:
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
Click to expand...
Click to collapse
internal storage is working here

Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?

chowynatt said:
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
Click to expand...
Click to collapse
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.

tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Did you manage to install Google+?

kejar31 said:
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!lVYHAAjI!-478q0a5v6QAL9-6bDNzo7utJ1AXZD539CpTP6R63w8
if someone wants to host mirrors let me know.
Click to expand...
Click to collapse
So far so good! I'm in the setup... it's taking a long time checking my wifi connection.
edit:changing to 5ghz did the trick
edit2: after passing setup, changing back to 2.4ghz works just fine.

tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Yeah all working now, took forever to boot, went black a few times and then started working.

Now the $64,000 Question: will it root?
because I've had my fun with it. And without root, I can't keep it. I doubt it can be, but I have to hope.

Flashed yesterday. My experience was as follow:
1) Dirty flash from PA, system erase command did t seem to work. After flashing it booted up all apps were there, 4.4 gapps were force closing.
2) Twrp advance factory reset and erase. normal flash afterwards with gapps 5.0. Setup wizard crash. Couldn't get past that error.
3) Factory 4.4 image. Complete erase, and flash to L, boot up and then TWRP and gapps flash. Tablet booted correctly and works since then.
Regarding the WiFi battery drain bug:
No issue here. Battery drain when idle is a flat line. No misc group with excessive battery is listed in the battery stats.
Further more performance is great, basic apps seem to work correctly. Haven't gotten much into detail.
Regarding the G+ question. It works fine.

HTC Desire 310/320 All Roms,firmwares,recoveries,root,etc

Thread update 15.04.2022, fixed some links, removed others, added RR 5.8.8 and did some formatting.
So since there were many users who had questions for roms,root,firmware and stuff like that which was already available but only in small posts,I finally decided to make a big official thread for the HTC Desire 310 and 320. Why 1 thread for 2 phones? Well,they are practically the same phone but desire 320 is running on stock kitkat and has flash.
Port guys and developers: @MaRtYy01 aka Martin Dimitrov @HTC Desire 310 aka 69techur aka Alija Huskic (Team N3GG3)
@Swoopae (deserves to be here lel) and users in 4PDA Desire 310 and 320 threads
New facebook group (tnx Swoopae) click
1.ROOT​Flashable SuperSU zip: in firmware flashing video
<Moderator Edit>: Files removed due to 15 different antivirus services detecting the APKs as Trojans.
2.RECOVERIES​
Spoiler: For firmware 4.2.2 only
Recommended-CWM 5(you dont need anything else,everything on 4.2.2 can be flashed with it): click
CWM 6 click
TWRP click
Stock recovery(if something messes up with other recovery and you get into bootloop flash it with sp flash tools) click
OTA - for android 4.2.2 click
Steps:
1.Put the OTA (named as update.zip) and the CWM on your SDCard
2.Reboot to Recovery (Volume UP + Power)
3.Select "apply update from sdcard"
4.Choose our update.zip (OTA)
5.It will return an error(if it doesnt then you should flash the stock rom with sp flash tools)(as our device is already updated) and it will let you choose two options. SELECT REBOOT SYSTEM NOW
6.After the phone is fully booted up, proceed to install the recovery as you wish!!!RENAME THE RECOVERY TO RECOVERY.IMG OR YOU WILL END IN BOOTLOOP!!!(You can use Rashr or MobileUncle MTK Tools or whatever you want)
7.After install, reboot to recovery
4.4.2+​These don't work if you are with the jellybean firmware(kernel 3.4.5), only for desire 320 firmware. Required to flash roms with version higher than 4.2.2
- Philz Touch click in this archive you have all stuff required for the rooting and installing the recovery on the d320 kitkat rom. Password is amogus
- Philz Touch mirror link without any other stuff coming with it: click mirror
- Flash the OTA click mirror with the stock recovery and reboot, go to mobile uncle tools and flash the recovery (new recovery.img)
btw OTA for android 4.4.2 is different from the jellybean one
3.ROMS​
Spoiler: 4.2.2
These roms are usually bugless or with minor bugs that dont interrupt the work. All ported from 4PDA users
XPERIA C click (sometimes gives errors while installing apps)
Lenovo(vibe ui) click
MIUI 5 click (one of the best 4.2.2 roms)
Lollifox click
Moonmod click
CyanogenMod 10.1 click (google play doesnt work)
4.4.2/4.4.4​
WARNING:YOU NEED THE DESIRE 320 FIRMWARE TO FLASH ROMS WITH NEWER VERSION THAN 4.2.2
[07.11.2016]MIUI 8 click (bugless) [ported by @Swoopae]
​
Spoiler: 5.1.1
[01.11.2016] AICP 10 click
gapps(for AICP only) click [ported by @MilkyPL]
[26.8.2016]CyanogenMod 12.1 click bugfixed version by @Swoopae
Flyme OS 4.5 link in kk firmware flashing video (google play doesnt work,I will try to fix it soon;gapps built in) [ported by me]
Spoiler: 6.0.1
Not 100% of the roms are well tested, so have a working rom as backup in case the rom you try doesnt work properly, also report back if you experience this.
IMPORTANT-If you own desire 320 flash this patch right after the rom or you will face wifi issue-click
Its made for marshmallow roms,so work for lollipop and kitkat isnt guaranteed. Tbh it doesn't always work on marshmallow too lmao
For mounting the sdcard as internal storage,here is @Swoopae 's patch click
It's made for cm13 but will probably work on other marshmallow roms too.
[14.11.2016]Mokee 3 click (bugless,vpn also works,just 2g switch bugged) [ported by @Swoopae]
[01.11.2016]AICP 11 click (gotta be almost bugless as all new mm based roms) [ported by @MilkyPL ]
[12.10.2016]TemastekPLUS click (improved and tweaked temastek cm13,bugless,vpn also should work) [ported by @Swoopae]
[02.10.2016]SwoopaeOS r01 click (based on slim6,fixed lag and minor bugs plus a sexy theme) [yes its by @Swoopae]
[04.9.2016]Paranoid Android 6.0.3(aospa) click (vpn and audio from headphones doesnt work) [ported by @Swoopae]
[17.8.2016]CyanogenMod 13 click ( very stable, gps, google play work,just fm radio doesnt work) [ported by @Swoopae]
[15.8.2016]Slim Marshmallow click (everything except fm radio works) [ported by @Swoopae]
7.1.2​|27.09.2017| Resurrection Remix N 5.8.4 by Swoopae: click
(should work well,needs some testing)
|15.04.2022| Resurrection Remix N 5.8.8 by me: post download
Steps:
1.Make sure the rom is on the sdcard
2.If you wish you can make a backup of your current rom
3.Wipe cache,data,system;dont mount anything/wipe for a new rom on philz recovery
4.Select update from sdcard/zip from sdcard/whatever is it from sdcard
5.Choose the rom zip and flash it
6.Flash gapps if the rom requires it(pico gapps are strongly recommended)
7.Reboot,first boot takes 3-8 minutes depending on the rom
GAPPS: http://opengapps.org/
Choose arm - whatever android version rom you are flashing - pico are recommended,if you have problems with gapps try with pico,flashing after rom and after 1 boot and then report if still doesnt work
4.Firmwares​
- Have any problems with the gps? Try this: click and this: click
- Desire 310 stock roms:
single sim: click mirror mirror 2
dual sim: click mirror
- Desire 320 stock rom(works for both d310 single and dualsim): click ; When installed on desire 310 bugs of that firmware are little while line on top of the screen and auto rotation(screen flickering too but doesn't happen on 5.0+ roms)
- SP Flash tools: click
- Driver: click
- Fix for driver signature error on windows 8/8.1: click
- Stuff for fixing imei(including toolhero): click mirror
- If you don't want to flash the desire 320 firmware and just want to unbrick this tutorial will be more helpful(also works if you have desire 320 and want to unbrick): click
HTC Desire 310 aka 69techur reported that Lenovo A328 firmware also works without flickering on and white line,but volume buttons,camera,rotation and a lot of other things dont work.
- Instructions for flashing D320 firmware on D310:
1.Backup imei with toolhero on 4.2.2
2.Install the driver on the pc,if it cant install them because they arent signed-disable signature verification(test mode) or try on other pc
3.Run the sp flash tool with compatiblity mode windows 7(only if you are on newer os) and set everything on it like in the video, connect the phone to the pc without battery and holding volume down;da dl with cheksum,high speed,no battery in the options,select firmware upgrade and start to flash
4.Root with the pc software,make sure you have enabled usb debugging in developer settings
5.Flash the OTA with the stock recovery and reboot, go to mobile uncle tools and flash the recovery(new recovery.img)
5.Now you have recovery.Wipe system,data and cache and flash the rom you wanna flash(the 4.2.2 roms dont work anymore) after that flash gapps if the rom requires it and reboot.
KERNEL BUGS:Screen flickering(kitkat roms only),screen rotation,little white line on the top of the screen
5.YOUTUBE​
Kitkat firmware,recovery and roms installation: click
CyanogenMod 13: click
How to fix imei: click
CyanogenMod 12.1: click
CyanogenMod 10.1: click
MIUI 5: click
Galaxy S5 mod: click
The HTC Desire 320 rom: click
AICP 6.0.1: click
CyanPOP 5.1.1: click
CleanKat 4.4.4: click
Wanna port a rom on your own? Here is a video guide for android 5 and 6: click
and written tutorial: click
Credits:​
-The users of 4PDA for all 4.2.2 roms and all recoveries, cm12.1, guides, etc.
-Me for translating the guides, youtube videos and ported roms
-HTC Desire 310 aka 69techur for helping me test stuff, his porting tutorial, ported roms and youtube videos
-Swoopae and Tomi Sudi for ported roms
-other guys that I havent mentioned
If you have questions, reports about bugs, requests or something feel free to ask.
Don't forget to hit thanks

Nice thread
#Proud_To_Be_Team_N33G3!

Many thanks for this! Good job. Cant wait for completed post
EDIT: How about GAPPS? And in which step we should install it?

Immortel.CZ said:
Many thanks for this! Good job. Cant wait for completed post
EDIT: How about GAPPS? And in which step we should install it?
Click to expand...
Click to collapse
in 5.x.x roms flash rom, boot, then flash
in 6.0.1 roms flash rom and then flash gapps

Still not sure about few things so please add what missing or correct me:
Highlighted stuff is what Im not sure.
Want to use CWM5 and Broken OS. Already got root. Stock recovery downloaded too (to be sure).
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options. Continue to 8.
b) It will not return an error and you should flash the stock rom with sp flash tools (How?)
8. Select reboot system now.
9. After the phone is fully booted up, proceed to install recovery as you wish. What? How?
10. After install, reboot to recovery.
11. ??? What next?
12. How to install BrokenOSD310.zip?
13. Flash gapps. How and which one (platform ?, android - 6.0. probably?, variant?)
14. Thats all?
I know that lot of ppl could do it but I need to be sure, to not make any mistakes

Immortel.CZ said:
Still not sure about few things so please add what missing or correct me:
Highlighted stuff is what Im not sure.
Want to use CWM5 and Broken OS. Already got root. Stock recovery downloaded too (to be sure).
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options. Continue to 8.
b) It will not return an error and you should flash the stock rom with sp flash tools (How?)
8. Select reboot system now.
9. After the phone is fully booted up, proceed to install recovery as you wish. What? How?
10. After install, reboot to recovery.
11. ??? What next?
12. How to install BrokenOSD310.zip?
13. Flash gapps. How and which one (platform ?, android - 6.0. probably?, variant?)
14. Thats all?
I know that lot of ppl could do it but I need to be sure, to not make any mistakes
Click to expand...
Click to collapse
Broken os is for the 4.4.2 firmware (kernel 3.4.67),not the stock 4.2.2(kernel 3.4.5) .You need to flash the d320 firmware first,get philz recovery on it then flash the rom and the gapps.
And here my explanation:
7b) I will add that later in the firmware section
9 ''(You can use Rashr or MobileUncle MTK Tools or whatever you want)'' Rashr is in the google play
11.-14. Well,I guess I will have to add instructions how to flash roms
BTW The kitkat firmware installation+installation of recovery and roms video is complete gotta upload today
Edit:video uploaded https://www.youtube.com/watch?v=QRpw5sQA0rs
and thread finished

Sooo...
Today, I´ve managed to install Galaxy S5 rom on gf cell phone. It was super easy.
If I remember correctly, this was my step-by-step:
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD. Upload Galaxy_S5_HTC_Desire_310_Dual_sim.zip on SD too.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options.
8. Select reboot system now.
9. recovery.img (from CWM5) flashed from Rashr.
10. Boot to recovery, flash Galaxy_S5_HTC_Desire_310_Dual_sim.zip
11. Restart.
12. Boot to recovery, full wipe and factory reset.
13. Restart.
14. Boot to recovery, flash gapps for 4.2.2. (from other source).
15. Restart.
Now, there was a few things:
- Keyboard was not installed at all, so I´ve copied [censored] keyboard apk to SD and installed it.
- Dialer not showing dialing number (this is probalby because this rom is for S5 which have bigger display). Solved with 3rd party dialer.
- Same thing with date on unlocking screen. Not solved, ignoring for now. Can be probably solved with 3rd party screen locker. Will test it later.
- There is very annoying pop-up about back cover. Did fast look through google and it is solved by xposed, but will not install it until someone from you confirms it will not brick this phone
- When tap on those six dots in round shape (on desktop) to acces all icons of apps, and then tapping any upper icon (upper meaning first and second line from to), sometimes instead of running the app it will roll down status/notification? bar. Not a critical bug but can be annyoing.
- ADDED: Well, it looks like we cant turn data on, when both sims are present. Yes, we have sim which we want to use for data in slot 1 but still, we cant turn data on (no sign of 3G above cell signal). But I remember, it works when there is just one sim. Major problem.
- Another problem, GPS. It is working but it is still ON. We cant turn it off, not even in settings. Major problem. Will try it later without second SIM.
- CONFIRMED: It is problem with second SIM. When we using just one sim in slot 1, there is no problem, data works, GPS works as it should. So if you could look at it, please (if solution exists).
Last two bugs above (GPS and data) still occuring but not every time. Looks like switch is bugged.
EDIT: Did full wipe, format SD, reflashed G5 mod and now works without those bugs. Probably my fault flash. Yay!
So far so good.
Maybe we will try CM13 but now gf will test it for a few days.
THANKS guys, she is happy with her phone now. And you know, when gf is happy, you are happy too

Immortel.CZ said:
Sooo...
Today, I´ve managed to install Galaxy S5 rom on gf cell phone. It was super easy.
If I remember correctly, this was my step-by-step:
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD. Upload Galaxy_S5_HTC_Desire_310_Dual_sim.zip on SD too.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options.
8. Select reboot system now.
9. recovery.img (from CWM5) flashed from Rashr.
10. Boot to recovery, flash Galaxy_S5_HTC_Desire_310_Dual_sim.zip
11. Restart.
12. Boot to recovery, full wipe and factory reset.
13. Restart.
14. Boot to recovery, flash gapps for 4.2.2. (from other source).
15. Restart.
Now, there was a few things:
- Keyboard was not installed at all, so I´ve copied [censored] keyboard apk to SD and installed it.
- Dialer not showing dialing number (this is probalby because this rom is for S5 which have bigger display). Solved with 3rd party dialer.
- Same thing with date on unlocking screen. Not solved, ignoring for now. Can be probably solved with 3rd party screen locker. Will test it later.
- There is very annoying pop-up about back cover. Did fast look through google and it is solved by xposed, but will not install it until someone from you confirms it will not brick this phone
- When tap on those six dots in round shape (on desktop) to acces all icons of apps, and then tapping any upper icon (upper meaning first and second line from to), sometimes instead of running the app it will roll down status/notification? bar. Not a critical bug but can be annyoing.
- ADDED: Well, it looks like we cant turn data on, when both sims are present. Yes, we have sim which we want to use for data in slot 1 but still, we cant turn data on (no sign of 3G above cell signal). But I remember, it works when there is just one sim. Major problem.
- Another problem, GPS. It is working but it is still ON. We cant turn it off, not even in settings. Major problem. Will try it later without second SIM.
- CONFIRMED: It is problem with second SIM. When we using just one sim in slot 1, there is no problem, data works, GPS works as it should. So if you could look at it, please (if solution exists).
So far so good.
Maybe we will try CM13 but now gf will test it for a few days.
THANKS guys, she is happy with her phone now. And you know, when gf is happy, you are happy too
Click to expand...
Click to collapse
I would recommend you broken os over cm13,I havent updated it from a month(since I currently dont have the phone to test it) and broken os is super stable and almost bugless.
BTW if you have the 512mb ram version,I highly recommend the s6 mod or cleankat(69techur still hasnt uploaded it tho,lazy bastard XD).Kitkat uses less ram and its faster.I actually think that cleankat must be the fastest rom after all.
For the s5 mod:
-Keyboard works by default,just swipe the status bar and choose aoso keyboard
-Weird,dialer worked fine for me.And its not for s5 after all,the dialer looks like jellybean touchwiz,not kitkat,probably ported from s4/s5 chinese clone.
-The unlock screen looks like that because of the navigation bar,if you remove it(find qemu.hw.mainkeys=0 in the build.prop and change it to qemu.hw.mainkeys=1) and add pie controls instead,it will be fine.
-The pop up about the back cover aoso appears in the original s5,but this isnt real touchwiz rom so I suggest you not to touch it/backup the rom and try to remove it.
-Idk,probably sh1tty touchscreen,I think I faced the same issue when I was with the rom
-I dont know about solution of the last problems,the russians have ported the rom not me,checked the forum and they havent even reported these issues XD
BTW,if you have problem with random reboots put the fingerorint unlock.Its not real fingerprint of course,you just have to swipe down on the finger icon.The russians reported that this fixed the random reboots.
Anyway,thanks for the bugs report

Hey MaRtYy01 again!
Thanks for reply.
1) Dunno if it is 512 or 1025Mb ramm version. Now antutu states info about lenovo cell phone and there is 1024Mb, so not sure if I can trust that information. Is there any app which would provide exact info about ramm, without flashing 310 stock rom? Maybe it is really 1024. It is called HTC Desire 310 v1 white and that should have 1024Mb ramm.
2) I would VERY like to try those roms (Broken Os or S6 mod/CleanKat if memory is just 512Mb) BUT I lack of ability to make it without full step-by-step walkthrough. So if you would be so kind and type it by more describing way (videos dont work for me, my hearing english is low) so I can be 100% I know what I will be doing? Pretty please. For example, this is really idiot proof and it worked for me BrokenOs have some bugs as you stated so S6 mod would be much prefered. Or walkthrough for both, that would be amazing.
3) Keyboard could by my fault. I did not do full wipe after installation of rom, just after reboot. But it really wasnt there. In setup, I wanted to enter wifi password and all I can was voice input
4) Could provide screenshot, if you want. But that can be bypassed by another dialer, so it is okay
5) Pie controls is that round thing you press and few apps will show? We turned it off right away Too annoying.
6) So hw problem?
7) Hmm, okay. Maybe another rom will be solution.
8) No random reboots but thanks for advice! Will remember it.
No problem dude.

Reading this comments makes me feel like my IQ decreasing

Why? Because English is not my first language?
Because I'm not that experienced in flashing as both of you are?
Well sorry that you feeling that way!

Immortel.CZ said:
Hey MaRtYy01 again!
Thanks for reply.
1) Dunno if it is 512 or 1025Mb ramm version. Now antutu states info about lenovo cell phone and there is 1024Mb, so not sure if I can trust that information. Is there any app which would provide exact info about ramm, without flashing 310 stock rom? Maybe it is really 1024. It is called HTC Desire 310 v1 white and that should have 1024Mb ramm.
2) I would VERY like to try those roms (Broken Os or S6 mod/CleanKat if memory is just 512Mb) BUT I lack of ability to make it without full step-by-step walkthrough. So if you would be so kind and type it by more describing way (videos dont work for me, my hearing english is low) so I can be 100% I know what I will be doing? Pretty please. For example, this is really idiot proof and it worked for me BrokenOs have some bugs as you stated so S6 mod would be much prefered. Or walkthrough for both, that would be amazing.
3) Keyboard could by my fault. I did not do full wipe after installation of rom, just after reboot. But it really wasnt there. In setup, I wanted to enter wifi password and all I can was voice input
4) Could provide screenshot, if you want. But that can be bypassed by another dialer, so it is okay
5) Pie controls is that round thing you press and few apps will show? We turned it off right away Too annoying.
6) So hw problem?
7) Hmm, okay. Maybe another rom will be solution.
8) No random reboots but thanks for advice! Will remember it.
No problem dude.
Click to expand...
Click to collapse
Just to start from something,6),thats most likely software fault.And indeed I think the tutorials are fine,since you managed to flash s5 mod you are smart enough and for the videos-they are more to see how it happens,if i wanted I could put a song in the background instead of talking,my english sounds like **** tho(sometimes even I dont know what Im saying XD).So if you look at the instructions carefully,then follow what Im doing in the video you will be fine.Just if you dont know,you need to flash the desire 320 stock rom before s6 mod,broken os or other roms with version newer than 4.2.2 which might seem a bit hard for you(its actually easy tho,try to flash roms on htc one x and you will see what is hard ).The desire 320 rom also has a few issues like the rotation and white line.And dont get me wrong,Id choose broken os every day over s6 mod since its wayy better,s6 mod isnt bugless too.Also,your ram seems to be 1gb which is fine.
If you want the fastest solution-flash miui 5,its the stablest and the awesomest rom so far,ive been using it for a month and really loved it.You dont need to flash the desire 320 rom for it.

In first post, there is nothing about flashing via SP Flash Tools, so it is really neded?
Now we have CWM5 and Galaxy S5 Mod
and we want BrokenOS
Is this good way to do it?
1) Flash stock recovery with Rashr.
2) Go to recovery and flash 320 rom.
3) Flash OTA_v01_u-1.zip (from PhilzTouch - PT), reboot and do build.prop thing
4) Flash new_recovery.img (PT) with Rashr
5) Copy BrokenOs on SD
6) Go to recovery
7) Wipce cache, data, system
8) Choose BrokenOs zip from SD and flash it
9) Flash gapps
10) Reboot

Hello!I rooted my htc with kingroot. I uninstalled a bunch of apps and have like 1,2gb free memory in my phone. However when i try to install a game (has like 0.9 gb) it still installs in my phone memory and when it tries to update itself it goes beyond the 1,2gb memory. It also appears that i can't move it to SD. Is there anyway to change the installation folder?

Aconcerneduser said:
Hello!I rooted my htc with kingroot. I uninstalled a bunch of apps and have like 1,2gb free memory in my phone. However when i try to install a game (has like 0.9 gb) it still installs in my phone memory and when it tries to update itself it goes beyond the 1,2gb memory. It also appears that i can't move it to SD. Is there anyway to change the installation folder?
Click to expand...
Click to collapse
Hey Aconcerneduser.
If you have stock room then no, you cant install/move apps to SD. I´ve tried lot of things (like App2SD, Link2SD) and nothing works.
Try flash Galaxy S5 Mod, it is not hard and then you can move apps to SD!
I can make you noob proof walkthrough (how I flashed it), it takes you 15 minutes tops and it works.
EDIT: Updated my bug report about S5 mod!

Immortel.CZ said:
In first post, there is nothing about flashing via SP Flash Tools, so it is really neded?
Now we have CWM5 and Galaxy S5 Mod
and we want BrokenOS
Is this good way to do it?
1) Flash stock recovery with Rashr.
2) Go to recovery and flash 320 rom.
3) Flash OTA_v01_u-1.zip (from PhilzTouch - PT), reboot and do build.prop thing
4) Flash new_recovery.img (PT) with Rashr
5) Copy BrokenOs on SD
6) Go to recovery
7) Wipce cache, data, system
8) Choose BrokenOs zip from SD and flash it
9) Flash gapps
10) Reboot
Click to expand...
Click to collapse
'' 2) Go to recovery and flash 320 rom.'' XDXDXDXDXDXDXDXDXDXDXDXDXDXDXD
Lollll no.You need to flash it with sp flash tools;before that backup imei with toolhero
After that root it with the pc root program,flash the ota with STOCK recovery,do the ''build.prop thing'' and then flash recovery with mobile mtk tools.And new_recovery.img IS philz touch.
The rest is right.
Also,watch my last video for the kitkat firmware.recovery.You dont need to understand what I say,just look what Im doing.

Immortel.CZ said:
Why? Because English is not my first language?
Because I'm not that experienced in flashing as both of you are?
Well sorry that you feeling that way!
Click to expand...
Click to collapse
1st. English isnt my first language too and Im speaking it fluid
2nd You have a step by step tutorial here and dont post fake bug reports -_-

HTC Desire 310 said:
1st. English isnt my first language too and Im speaking it fluid
2nd You have a step by step tutorial here and dont post fake bug reports -_-
Click to expand...
Click to collapse
He is speaking it fine tho
And they arent fake,just the crappy tries of the russians to port roms correctly-full with bugs.

MaRtYy01 said:
He is speaking it fine tho
And they arent fake,just the crappy tries of the russians to port roms correctly-full with bugs.
Click to expand...
Click to collapse
Mine MLG ports are bugless

And that's your problem, HTC DESIRE 310. Not everyone is like you, not everyone have everything like you. And lol you are not speaking fluidly English.
If you don't want contribute this conversation, please step aside.
Thanks MaRtYy01 for advices. Few hours back I've refreshed my bug reports. Data and gps problems are gone, probably faulty flash or cause of not wiping.
And thanks for correcting me, as you can see I'm still little bit confused Will look it up tomorrow, now is bed time.

[Q] Gapps Not Working Multiple ROMs

I have a 9195 samsung mini s4.
I've tried CM 13, 12 and 11. All three of them work perfectly.
But... it no longer works when flashing Gapps together with any of the ROM's.
On CM 13, I get a bootloop.
On CM 12 and 11 the Gapps simply keep crashing, making my device unusable.
With all three ROM's I've flashed the Gapps package together with the actual rom, I use opengapps by the way.
My recovery is TWRP 2.6.3.0
Am getting real desperate here, any tips on how to fix this?

Elder Lyons said:
I have a 9195 samsung mini s4.
I've tried CM 13, 12 and 11. All three of them work perfectly.
But... it no longer works when flashing Gapps together with any of the ROM's.
On CM 13, I get a bootloop.
On CM 12 and 11 the Gapps simply keep crashing, making my device unusable.
With all three ROM's I've flashed the Gapps package together with the actual rom, I use opengapps by the way.
My recovery is TWRP 2.6.3.0
Am getting real desperate here, any tips on how to fix this?
Click to expand...
Click to collapse
You could try
- booting the rom first then going back to recovery and flashing gapps separately
- using a different gapps package, either from a different provider or an older gapps package that you have used and works. (I'm sure you already know this but I'll say anyway: make sure you are selecting the correct gapps version)
- update TWRP to a newer version(TWRP 3.0.2-1 works well for me)
Also, when you install the rom, wipe /system beforehand. Sometimes the rom installer script doesn't automatically wipe /system.

noppy22 said:
You could try
- booting the rom first then going back to recovery and flashing gapps separately
- using a different gapps package, either from a different provider or an older gapps package that you have used and works. (I'm sure you already know this but I'll say anyway: make sure you are selecting the correct gapps version)
- update TWRP to a newer version(TWRP 3.0.2-1 works well for me)
Also, when you install the rom, wipe /system beforehand. Sometimes the rom installer script doesn't automatically wipe /system.
Click to expand...
Click to collapse
I'll try and install a newer version of TWRP. I've already tried multiple gapps versions, none of them work and keep on crashing.
I'll report back if updating TWRP works out.

noppy22 said:
You could try
- booting the rom first then going back to recovery and flashing gapps separately
- using a different gapps package, either from a different provider or an older gapps package that you have used and works. (I'm sure you already know this but I'll say anyway: make sure you are selecting the correct gapps version)
- update TWRP to a newer version(TWRP 3.0.2-1 works well for me)
Also, when you install the rom, wipe /system beforehand. Sometimes the rom installer script doesn't automatically wipe /system.
Click to expand...
Click to collapse
Good news! Instelling TWRP 3.0.2-1 worked perfectly!
Though when unlocking the phone with the unlock button it always takes a second or two to actually wake up the phone for soms reason. Any idea what could be the cause of this?
Either way, which version of CM would give the best battery life ranging from 10-13? I'm testing out CM13 now, but am wondering which of the three have the best battery life. Soms insight would be much appreciated!

Elder Lyons said:
Though when unlocking the phone with the unlock button it always takes a second or two to actually wake up the phone for soms reason. Any idea what could be the cause of this?
Click to expand...
Click to collapse
My partners phone did this once. Updating to a newer build fixed this....
Either way, which version of CM would give the best battery life ranging from 10-13? I'm testing out CM13 now, but am wondering which of the three have the best battery life. Soms insight would be much appreciated!
Click to expand...
Click to collapse
I can't really comment on that as I don't spend a great deal of time on CM. I prefer roms with a few more options/features. Having said that, purely for battery life I think CM10 and 11 might be slightly better

zibalba said:
Why has nobody answered this????? I have an MOTO G 2nd Gen 2014 LTE its the Uk X1072 model with Cm13.1 and opengapps has stopped working for me too! If i remember correctly i flashed the pico or minimal version of gapps and none of the Google based apps work anymore!?!!??!!! Could anyone please shed some light on this as nothing coming up in Google search?
Click to expand...
Click to collapse
it has been answered, using a newer version of TWRP fixed Gapps. You seem to have a different problem, not Gapps, but Goggle based apps like maps, gmail etc that you seem to be talking about, is that what you mean? Anyhow you should ask on the forum for your phone model for a proper answer.
But you could start by checking your date setting as per
https://support.google.com/googleplay/forum/AAAA8CVOtD821RhY-BKvVA/?hl=en

How to flash PE ROM in MI MIX2S device?

Dear every one, I really like this ROM, but how to flash this ROM?
I try to flash to use fastboot and TWRP with IMG flashIng, but after flashing them, the mobile phone will jump to Bootloader page, but when I use the same method in other ROM(like PHH and RR6.1.0)it works. My last ROM version is MIUI10-8.7.12 Globle.
details here
1.formate data
2.4 wipe
3.install and choose img file with system type.
4.wipe again
5.reboot
THanks.

If supported you can flash the image in bootloader mode.
Type in this command.
fastboot flash system nameofimage.img and reboot.

PE just wont boot for some devices. There is a whole different thread about fixing this, it may be for Huawei, but it could work for more devices. Apparently flashing a patched boot from Magisk works.

flash magisk 16.6 it will boot. but then you will have to also format data(not wipe) in twrp to disable encryption.

It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I used version 3.2.0.1/v5 from here: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
8. Rebooted system again
Works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!

kleinholzinferno said:
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I'm using version 3.2.0.1)
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
9. Rebooted system again and it works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
Click to expand...
Click to collapse
didnt worked for me rebooted into recovery i used 3.2.1-0 can you link me yours?

From this thread
https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
I used version 5 because in version 6 usb MTP mode is disabled.
Which rom did you come from? I came from a working official resurrection remix gsi. But I don't know if this matters as you wipe everything from the device.
Have you ever had a treble gsi running on your device? I remember installing RR after the android P beta from Xiaomi failed. I then started from scratch and installed the latest official global stable miui rom for the MiMix2S from Xiaomi without magisk and all and went from there. Don't know why but this fixed the problem with the RR gsi.
Maybe theres a problem with older mods you have done. You could try and start from zero and get the device back into the original state.
Hope it works out for you! Let us know how it turned out. Could be anyone else has some more input for you.
I know it's frustrating to flash a rom that works for others and not on your device although you have the same as them and followed every step in the tutorial. I've been there so many times that I lost count but it's always the little things that cause problems. Take your time, read some more about this whole stuff. I had to read a lot to get into this topic. Maybe theres a nother method of flashing that works for you.

kleinholzinferno said:
From this thread
https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
I used version 5 because in version 6 usb MTP mode is disabled.
Which rom did you come from? I came from a working official resurrection remix gsi. But I don't know if this matters as you wipe everything from the device.
Have you ever had a treble gsi running on your device? I remember installing RR after the android P beta from Xiaomi failed. I then started from scratch and installed the latest official global stable miui rom for the MiMix2S from Xiaomi without magisk and all and went from there. Don't know why but this fixed the problem with the RR gsi.
Maybe theres a problem with older mods you have done. You could try and start from zero and get the device back into the original state.
Hope it works out for you! Let us know how it turned out. Could be anyone else has some more input for you.
I know it's frustrating to flash a rom that works for others and not on your device although you have the same as them and followed every step in the tutorial. I've been there so many times that I lost count but it's always the little things that cause problems. Take your time, read some more about this whole stuff. I had to read a lot to get into this topic. Maybe theres a nother method of flashing that works for you.
Click to expand...
Click to collapse
i started from 0 flashed in order global official miui rom after rr and after pixel experience all ok without strange messages

PITTAR said:
i started from 0 flashed in order global official miui rom after rr and after pixel experience all ok without strange messages
Click to expand...
Click to collapse
Very good, great it works for you now.
Enjoy the new phone! I have it running for a few days now and so far I love it! I'm never going back to miui again! Never!
Some things are not working at the moment like Bluetooth audio to car stereo. Although it shows the song playing with the title and the correct time on the car head unit I hear no sound. Hands free calls work without any problems.
In band ringing doesn't work so I don't hear my ringtone over the car stereo. I can activate this in developer options but it doesn't stay on and doesn't work. Nevermind, this isn't important.
Haven't found many other things that I need at the moment.
Great rom, hope it gets maintained in the future and there will be a device specific rom for the MiMix2S in the near future.
Hopefully Android P in fall/winter?

kleinholzinferno said:
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I'm using version 3.2.0.1/v5 from here: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
8. Rebooted system again
Works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
Click to expand...
Click to collapse
Thanks for sharing so much...but I wanna know flashing Magisk 16.6 is significant or not? Why should I must flash that..caz I use bank App which is not allowed root device..Oh, I try to flash Omin ROM, but it can't get into the system..and Magisk16.6 can't be flashed in with error..

jayxiao171735 said:
Thanks for sharing so much...but I wanna know flashing Magisk 16.6 is significant or not? Why should I must flash that..caz I use bank App which is not allowed root device..
Click to expand...
Click to collapse
Magisk was mandatory for me because otherwise it ended up booting only to recovery.
I haven't tried what happens when you uninstall magisk after successfully setting up the device.
If you need to hide root use magisk hide, maybe that helps?

[ROM][P900][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200821 technical preview

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using pico/nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Full wipe all
4. Flash firmware and gapps
Work
almost all
Known Issues
- camera
- screenshots
- missed icons in trebuchet tauncher (install nova or microsoft launcher and other)
Links
LineageOS Builds
1. 20200821: init build: https://drive.google.com/file/d/19-rPOcmlYIhcoZleG4MKRROk9TXytEOe/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official version from: https://twrp.me/samsung/samsunggalaxynotepro122exynoswifi.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_v1awifi
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos5420
Vendor: https://github.com/Valera1978/android_vendor_samsung_v1awifi
Thanks
Thanks to LineageOS team
Thanks to exynos5420 team for the right kernel

Thx @Valera1978 that's great news.
Gonna test today.
Edit 6h later first impressions:
Coming from Lineage 14.1 Vanilla with TWRP 3.4.0-0.
Backed up everything, full wipe plus data format.
Installing purely the ROM with TWRP 3.4.0 led to "Error 7" 3.3.1 did the trick.
Made a reboot to check if it starts.
Noticed screen failures in form of small black bars/stripes which vanished after a few seconds when I let the screen settle.
(Appearing very often even now after full installation of everything I need.)
Rebooted to TWRP and installed BiTGapps (prefer them to opengapps as they are even smaller than pico) and Magisk.
After each flash wiped cache/dalvik of course.
Installed Nova prime (dark mode) and all my other apps.
Camera doesn't work with Lineage App (as said) but does with opencamera from f-droid.
Screenshots neither but using Quickboot is a workaround when activated in its settings.
When writing text and correcting failures the magnifier shows only a white field with now text in it even when dark mode is off.
Great work @Valera1978 will carry on testing.
Edit 18h later:
Firefox seems to have problems with it, doesn't often even open its add-on page or urls.
Lightning browser has no probs.
Only one sudden reboot until now.
Edit 24h later:
Tried to upload a pic with the screen problems but didn't work.
Mostly occuring when switching from portrait to landscape (reproducible).
Because of the Firefox problems I've tried the 79 version but starting it resulted directly in a reboot (reproducible).

I'm surprised there aren't more responses
Can confirm TWRP 3.3.1 is the latest recovery to work. Doesn't seem to work with 3.1.1
Can't change wallpaper. Not sure why. I have to go to live wallpaper to get the default one back
Ok Google needs to be installed manually
I get security flags from SELinux and Public trust certificates. Probably because the release is so early
Overall it's not bad for a Pre-Alpha release.

First of all: an awesome thank you to Valera1978 since I was expecting a newer version than 14.1 a long time
Have the same issue with the wallpaper change and some flickering in the display. Installed nova prime too but can`t close all apps in task manager only each manually single (wipe up)
I am eager for the next version and improvements :fingers-crossed: and willing to give further feedback.
THX a lot for your passion

the current version is rather a technical build for testing (public, the most stable, there were already about 40-50 internal builds for fixing bugs and checking various things).
In any way - lineage 17.1 coming soon (later today), release build done, on tests right now. And I like it much more, then technical 16.0 build.

I tried 16 and I like it. Looking forward to 17.1. Thanks for saving the P900 from an early grave you are and have been the best ?

i will try this process for the first time. Is there a video tutorial? thank you.

kayamece said:
i will try this process for the first time. Is there a video tutorial? thank you.
Click to expand...
Click to collapse
This ROM will probably not be in development any further as the brilliant dev @Valera1978 is already working on a 17.1.
About a video I don't know. Searching in YouTube might help finding out
Here is a very good description which I followed from @thompatry who's ROM is very stable, has a working camera (skype) and gets regularly updated.
[ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi)
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.* (Nougat), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your...
forum.xda-developers.com
Download it to SD.
As he quoted install a TWRP first to exchange the stock recovery.
Easiest to do is use a windows PC with Odin version 3.13.
Battery fully loaded before starting.
1.Download TWRP 3.3.1 for v1awifi from twrp.me but choose the tar version and save it in Odin folder.
2.Get P900 into download mode (turn it off, then press buttons Pwr, home, vol- altogether).
Will give you a warning but continue with vol+.
3.Start Odin then connect P900 to PC and check in Odin if a field on the left turns blue (com+).
4.Uncheck "auto reboot" in Odin.
5.Flash TWRP 3.3.1 with Odin onto P900 putting the downloaded TWRP file in "AP" field in Odin.
When Odin says "Pass" all is fine.
6.Turn P900 off with pwr button but press afterwards directly home and Vol+ together as it automatically reboots.
Then you access the new recovery.
If you fail the Samsung recovery gets reborn and you have to repeat steps 2-6 again but that does no harm.
Save all what is possible with TWRP to external SD using Backup.
Then wipe everything in TWRP (except SD ), select "format data" after that.
Select install and choose the ROM from SD.
Test if system starts. Might take a while.
If you want to use Google apps, download Gapps from opengapps (choose ARM, 7.1 and pico) and save it in advance to SD.
If system starts, turn it off, restart to recovery (pwr, home, vol+) and install Gapps.

bmwdroid said:
Easiest to do is use a windows PC with Odin version 3.13.
Battery fully loaded before starting.
1.Download TWRP 3.3.1 for v1awifi from twrp.me but choose the tar version and save it in Odin folder.
2.Get P900 into download mode (turn it off, then press buttons Pwr, home, vol- altogether).
Will give you a warning but continue with vol+.
3.Start Odin then connect P900 to PC and check in Odin if a field on the left turns blue (com+).
4.Uncheck "auto reboot" in Odin.
5.Flash TWRP 3.3.1 with Odin onto P900 putting the downloaded TWRP file in "AP" field in Odin.
When Odin says "Pass" all is fine.
6.Turn P900 off with pwr button but press afterwards directly home and Vol+ together as it automatically reboots.
Then you access the new recovery.
If you fail the Samsung recovery gets reborn and you have to repeat steps 2-6 again but that does no harm.
Save all what is possible with TWRP to external SD using Backup.
Then wipe everything in TWRP (except SD ), select "format data" after that.
Select install and choose the ROM from SD.
Test if system starts. Might take a while.
If you want to use Google apps, download Gapps from opengapps (choose ARM, 7.1 and pico) and save it in advance to SD.
If system starts, turn it off, restart to recovery (pwr, home, vol+) and install Gapps.
Click to expand...
Click to collapse
Hi everyone, I hope you are all safe and well.
Just a quick question, do I use the latest version of TWRP for my P900 (note pro 12.2 wi-fi). There are versions on the website which are later than the 3.3.1 version in this post. At the moment my version is 1.22, so this is really old! This was obviously installed and I did the flash to 14.1.
Like I say, at the moment, I am using LineageOS 14.1 with an old security patch level (September 19) because I cannot seem to update it. I have tried the auto update, this fails and I have also tried to manually apply but this also does not work.
I was wondering whether it was time to upgrade to version 16 or 17.
I'm not an expert on this by any means and I recall I did struggle with some error message when trying to update to I think at the time line Lineage 15.
Any comments or suggestions would be much appreciated.

@mattgod69 auto updater I don't use/like at all.
My suggestion is download TWRP 2.8.7-0 as zip and flash this with your TWRP. It is the latest zip released.
From that on it can use img files and you can update further to 3.3.1 or higher.
For me 3.4.0 was needed to flash @Valera1978 LOS17.1.
3.3.1-0 for LOS14.1 by @thompatry which's Vanilla (version 20201215) I use for here camera is working instead of being on LOS17.1.

Thanks for the reply @bmwdroid, i was talking about the app which is version 1.2 (doh)... i have just booted into TWRP and i have version 3.3.1. So if you are using the same tablet as me, what would you upgrade to or would you leave it as is. Also, do you think i need to update the security patch level? Cheers and apologies if these are silly questions.

mattgod69 said:
Thanks for the reply @bmwdroid, i was talking about the app which is version 1.2 (doh)... i have just booted into TWRP and i have version 3.3.1. So if you are using the same tablet as me, what would you upgrade to or would you leave it as is. Also, do you think i need to update the security patch level? Cheers and apologies if these are silly questions.
Click to expand...
Click to collapse
Mine is a P900 v1awifi.
I suppose that the app 1.2 refers to the TWRP app which I don't use and I've always read warnings to install it so I never did.
It is said that it sometimes causes problems when flashing.
And imo it's not needed anyhow.
If you need camera working for skype or else I recommend to flash the latest LOS14,1 mentioned above.
https://download.exynos5420.com/LineageOS-14.1-Deathly/v1awifi/
with the deathly adiutor built in
or
https://download.exynos5420.com/LineageOS-14.1-Vanilla/v1awifi/
which is a plain android system
The development of this LOS16 seems suspended as the dev is already working on LOS17.1 which I've tested, but as said has no working camera.
Therefore I can't say much about its stabilty but it worked with Bitgapps and Magisk for 4-5 hours until I switched back to LOS14.1.
If you want to test it: I had to upgrade TWRP to 3.4.0 to avoid "Error 7".
To go back to 14.1 I had to downgrade to 3.3.1 first.
Questions show that someone is willing to learn which should be appreciated.

bmwdroid said:
Mine is a P900 v1awifi.
I suppose that the app 1.2 refers to the TWRP app which I don't use and I've always read warnings to install it so I never did.
It is said that it sometimes causes problems when flashing.
And imo it's not needed anyhow.
If you need camera working for skype or else I recommend to flash the latest LOS14,1 mentioned above.
https://download.exynos5420.com/LineageOS-14.1-Deathly/v1awifi/
with the deathly adiutor built in
or
https://download.exynos5420.com/LineageOS-14.1-Vanilla/v1awifi/
which is a plain android system
The development of this LOS16 seems suspended as the dev is already working on LOS17.1 which I've tested, but as said has no working camera.
Therefore I can't say much about its stabilty but it worked with Bitgapps and Magisk for 4-5 hours until I switched back to LOS14.1.
If you want to test it: I had to upgrade TWRP to 3.4.0 to avoid "Error 7".
To go back to 14.1 I had to downgrade to 3.3.1 first.
Questions show that someone is willing to learn which should be appreciated.
Click to expand...
Click to collapse
Thank you for the detailed response, very helpful.
I dont really use the camera with my tablet, but i might, so its probably best to wait til 17.1 is working. The tablet is really just a browsing device i use beside my bed, its not an everyday machine.. so i am willing to try new things and play about with it.... it also does not matter if it is wiped accidentally etc.
i have to say it has been overall much better with 14.1 installed, far better than the stock OS. It is faster and more responsive.
Presumably I need new google apps etc download any new OS? If i install the latest LOS 14.1 do i also need new gapps etc? Is this OS much better than the one i have?
I do not know what Bitgapps and Magisk are?
Many thanks for all your help.... this community is great because even though i have done this a couple of times on different devices, there are long time gaps between doing it and it is still quite scary because i dont want to brick the device!

Just looked at Magisk... is it not a good idea to have this in any event? it looks like this would be earier to install later OS like LOS17.12? Is this right?

@mattgod69 BitGapps are an even smaller Google Apps version than Opengapps pico.
I use them on Android Q, as opengapps weren't working properly at that time being.
I don't use Google TTS and always had to block it when using opengapps.
Magisk is an equivalent to SU which is no longer continued.
It's neede for all apps needing root like AFWall, DeviceInfo and many others.
If you or your tab are happy without there's no need flashing it.
It causes no probs when switching ROMs as long as it's a clean flash.
Even updating ROMs dirty works on mine.
If you already had LOS14.1 installed and google apps as well you don't need a newer gapps version when updating dirty as gapps get updated by Google itself.
When flashing cleanly I recommend a newer gapps version but you can use any old (designed for the specific android version) as well.
Only setting up might take longer as the gapps will be updated automatically as soon as they find an internet connection.
The newer version of LOS14.1 will imo only be different in patch level nothing else.
Hope I didn't overlook a question.

bmwdroid said:
@mattgod69 BitGapps are an even smaller Google Apps version than Opengapps pico.
I use them on Android Q, as opengapps weren't working properly at that time being.
I don't use Google TTS and always had to block it when using opengapps.
Magisk is an equivalent to SU which is no longer continued.
It's neede for all apps needing root like AFWall, DeviceInfo and many others.
If you or your tab are happy without there's no need flashing it.
It causes no probs when switching ROMs as long as it's a clean flash.
Even updating ROMs dirty works on mine.
If you already had LOS14.1 installed and google apps as well you don't need a newer gapps version when updating dirty as gapps get updated by Google itself.
When flashing cleanly I recommend a newer gapps version but you can use any old (designed for the specific android version) as well.
Only setting up might take longer as the gapps will be updated automatically as soon as they find an internet connection.
The newer version of LOS14.1 will imo only be different in patch level nothing else.
Hope I didn't overlook a question.
Click to expand...
Click to collapse
Many thanks for the message and info. i think maybe i will leave as is for a bit as the tablet is working fine at the moment.... look at this again when 17.1 is ready.....

mattgod69 said:
Many thanks for the message and info. i think maybe i will leave as is for a bit as the tablet is working fine at the moment.... look at this again when 17.1 is ready.....
Click to expand...
Click to collapse
But I hope you will be updating the ROM to be on the latest patch level.

bmwdroid said:
But I hope you will be updating the ROM to be on the latest patch level.
Click to expand...
Click to collapse
ok, i will update with the lastest 14.1 OS.... is there a step by step guide for this on here....?

bmwdroid said:
But I hope you will be updating the ROM to be on the latest patch level.
Click to expand...
Click to collapse
i think i am going to try 17.1... i think most issues have been sorted now?
i did have some questions before i do this which i have put in another post.....
Also, how do you do a dirty install... is this where the cache etc is not wiped?
would you update TWRP to 3.5.0. (the latest one). I assume this can be done from the program in recovery mode?
Many thanks for your help and advice.

mattgod69 said:
.... would you update TWRP to 3.5.0. (the latest one). I assume this can be done from the program in recovery mode?...
Click to expand...
Click to collapse
Updating TWRP can be done with itself.
Working up- and downwards.
Just select "install" switch to "image" choose the file and select "recovery".
Afterwards reboot directly into the new recovery.