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.ROOTFlashable 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.
Related
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.
Hello everyone! Just want to share this little gem I've put together.
So as some of you might know, CM13 and other ROMs based on it do not yet support the new LCD on OPPO Find 7s (R63419). I use to have the first version of the panel, but got drunk one night and cracked the screen. Bought a new one and suprise suprise, everything looked messed up as I was running CM. I didn't want to start over so I put this build together using latest CM13 nightly + Pojiku's patched kernel.
WHAT IS IT?
- It is the latest nightly (will try to update) with already patched kernel for LVM + NEW LCD from Pojiku (his thread here: http://forum.xda-developers.com/find-7/orig-development/rom-cyanogenmod-nameless-builds-lcd-t3327530)
WHAT WORKS:
- New LCD
- Supports LVM (Wuxianlin LVM patch)
- Sound works on this version (didn't work on latest version from Pojiku)
- Gestures (Circle for camera, V for flashlight, double tap to wake)
- Actually, everything works except 4K video recording
This build IS EXPERIMENTAL! ALWAYS BACKUP!
If you want GAPPS, I'm using OPENGAPPS's pico version. I think you need to fully boot once, then install GAPPS, then boot again. I'm not sure exactly as I'm coming from CM12 dirty flash. Did a system install, first boot + setup, then restore data partition.
PLEASE NOTE: You might need to change permissions for the Google SetupWizard in Settings! Go into Settings -> Apps -> SetupWizard and grant all permissions. OR else gapps might not work!
You need to be unified by flashing ColorOS 2.1.5 using Alexander Tashi's method.
Please use this recovery (UNIFIED TWRP 3.0.0: https://drive.google.com/open?id=0B0IQuS71Z8k2WmVnTGVrdFJTZVU)
Please use this script if UNIFY don't work: https://drive.google.com/open?id=0B0IQuS71Z8k2eXVXNlMtSU9wNGc
DOWNLOAD
Latest version: cm-13.0-20160402-NIGHTLY-find7
Link : https://drive.google.com/open?id=0B0IQuS71Z8k2Q3dCMFhFdlp1amM
Hi, this works perfect for me! Thank you man, and thanks also to Wuxianlin and Pojiku. You got it, works fine, everything. Only one bsod at first start, no more bugs.
I will try the rom for a week, if its stable sure i'll use it as daily rom.
Thanks again for your job
Cheers
I will try soon when I have time.
Hope this ROM keep update.
Thank you very much.
sugarsweetcandy said:
Hello everyone! Just want to share this little gem I've put together.
So as some of you might know, CM13 and other ROMs based on it do not yet support the new LCD on OPPO Find 7s (R63419). I use to have the first version of the panel, but got drunk one night and cracked the screen. Bought a new one and suprise suprise, everything looked messed up as I was running CM. I didn't want to start over so I put this build together using latest CM13 nightly + Pojiku's patched kernel.
WHAT IS IT?
- It is the latest nightly (will try to update) with already patched kernel for LVM + NEW LCD from Pojiku (his thread here: http://forum.xda-developers.com/find-7/orig-development/rom-cyanogenmod-nameless-builds-lcd-t3327530)
WHAT WORKS:
- New LCD
- Supports LVM (Wuxianlin LVM patch)
- Sound works on this version (didn't work on latest version from Pojiku)
- Gestures (Circle for camera, V for flashlight, double tap to wake)
- Actually, everything works except 4K video recording
This build is stable for me, BUT IT IS EXPERIMENTAL! ALWAYS BACKUP! Battery life is good, no crashes after a modest amount of testing.
If you want GAPPS, I'm using OPENGAPPS's pico version. I think you need to fully boot once, then install GAPPS, then boot again. I'm not sure exactly as I'm coming from CM12 dirty flash. Did a system install, first boot + setup, then restore data partition.
DOWNLOAD
Latest version: cm-13.0-20160402-NIGHTLY-find7
Link : https://drive.google.com/open?id=0B0IQuS71Z8k2Q3dCMFhFdlp1amM
Let me know if it works for you
Click to expand...
Click to collapse
Hi, I have tried flashing this and every now and then after locking the screen, it does not show up.
EDIT: It happens when you turn on Ambient Display
Many thanks.
I'm going to try this immediatly.
I hope you will continue to update and if no, it will be great if you can explain how did you do to make that possible like that we souhld continu the work.
Thanks again and hope you'll continue.
Have a nice day.
I don't know if i did something wrong . I m familiar with flashing etc... I flashed the rom(clean install. full wipe) 3 times and i always have the same issue. when i open the file explorer integrated in the rom, i can see my external sd and can open it but there is no internal storage listed. I tried with sd maid (explorer) and same, no inernal storage listed. when i go in system settings under storage, i see the internal storage (i'm on lvm) and i see 2 sd cards : one wich is corrupted and a second which is my external sd and i can open it. when i plug the phone to my pc, i see only my external sd card partition (iternal storage doesn't appear) and when i click on it my data are not visible. it seems to be empty but in reality no. In TWRP the phone plugged to the pc, i can see internal and external storage and all data are there.
I will try another time maybe i will find the problem.
I had similar issue. Try going to settings in file manager and then to storage settings I think, and enable root access mode. Worked for me. However I have installed the arm 6.0 pico gapps and just get everything crashing (google services, etc) so I'm not sure what I'm doing wrong.
I stand corrected.......I see what you mean now. Thought I actually had valuable input but spoke too soon lol. Can't download anything now due to "no sdcard" issue ;(
ok i have some news.
I think lvm is not supported. Let me explain.
The 3 first times, i maked a full wipe, flashed lvm setup package, flashed the rom and open gapps (tried stock and nano) and after the reboot and setup, issues i've related appears.
I've decided to read a new time the op and my english is not very good. So i've read : "...already patched kernel for LVM...". I've decided to make a new clean install but this time without flashing the lvm setup. after a reboot and setup, all is good but i have the 2 partitions. once for install app (2.93go), and once for data. Clearly no lvm.
Please sugarsweetcandy, give us new build with complete lvm compatibility as quickly as you can.
Thanks for your work.
p.s : i read on oppo forum a comment saying that this build is not for x9076. is that right. I hope no because my find 7s is a x9076 model
---------- Post added at 03:50 AM ---------- Previous post was at 03:44 AM ----------
thecell_2007 said:
I had similar issue. Try going to settings in file manager and then to storage settings I think, and enable root access mode. Worked for me. However I have installed the arm 6.0 pico gapps and just get everything crashing (google services, etc) so I'm not sure what I'm doing wrong.
I stand corrected.......I see what you mean now. Thought I actually had valuable input but spoke too soon lol. Can't download anything now due to "no sdcard" issue ;(
Click to expand...
Click to collapse
Thank you for your help thecell. I've already did this but it did'nt work for me. the internal storafe doen t appear if i flash lvm setup package.
For your problem, i figure that you've followed the installation instructions on op. Maybe i'm wrong but i think you flashed the rom and reboot then setup and reboot to recovery then flashed gapps....
when i did the this manipulation i had the same issue.
So what you have to do is in twrp : select all packages you want to flash (rom, gapps, supersu, hal mod, xposed....) and reboot then setup, reboot system and all will done
.
I am not too sure what's causing problems with LVM. I actually have unified chinese method, and this is what I get: i.imgur.com/34KSCBP.jpg
Although there seems to be a "corrupted" SD card, everything works and I can download correctly. I will try looking into it!
sugarsweetcandy said:
I am not too sure what's causing problems with LVM. I actually have unified chinese method, and this is what I get: i.imgur.com/34KSCBP.jpg
Although there seems to be a "corrupted" SD card, everything works and I can download correctly. I will try looking into it!
Click to expand...
Click to collapse
Thanks for your response.
I have exactly what you have when i flash "setuplvm_find7_FULL_WIPE_09012014.zip" (http://forum.xda-developers.com/showpost.php?p=55187001&postcount=558). but in the file explorer my sdcard 0 doesn't appear. I tried with flashing the wuxianlin lvm patch for cm 13 and then i have no the corrupted issue that we can see in your screen but my internal storage doesn't show 25go it shows 2.93go only and the 22go doesn't appear. i didn't sleep all the night testing many methods lol. I will try a last time flashing this "twrp_find7_lvm_09012014.img" (http://forum.xda-developers.com/showpost.php?p=55187001&postcount=558). Maybe there will be in this twrp versio some option for lvm.
Thanks for your invest. I and many find 7 owners i think are waiting for this since a long time. I really want to own this rom. Please bring us some great news. Of course you have a life and we will be patients.
thanks again
I'm on x9077 so it might be different for you, but my install pattern went like this:
1. Was using CM12 fine with old LCD.
2. Did full backup, unified with Chinese ColorOS install method (see CM thread on OPPO forum), and then restored data
2. Broke screen, installed new LCD, and then CM12 didn't work anymore.
3. Did a full backup, wiped everything, installed CM13 + pico apps
4. Booted and did setup.
NOTE: You might need to change permissions for the Google Setupwizard in Settings. Go into Settings -> Apps -> SetupWizard and grant all permissions
5. Some apps will need reinstalling because they will have wrong permissions.
Hope this helps!
CM13 20160406 snapshot is release.
is this version support new X9077 LCD ?
zw963 said:
CM13 20160406 snapshot is release.
is this version support new X9077 LCD ?
Click to expand...
Click to collapse
Yes, the new LCD is supported!
proazy said:
Yes, the new LCD is supported!
Click to expand...
Click to collapse
I tried the CM13 20160406 snapshot from cyanogen official downloads, in my x9076 with panel r63419 and not works, blanck screen, the same ever
roi_xordo said:
I tried the CM13 20160406 snapshot from cyanogen official downloads, in my x9076 with panel r63419 and not works, blanck screen, the same ever
Click to expand...
Click to collapse
Try the one that is mentioned in this thread, it works for me! The official ones are not supported.
Cm13 20160406 nightly
proazy said:
Yes, the new LCD is supported!
Click to expand...
Click to collapse
I tried the CM13 20160406 NIGHTLY in my x9076 with panel r63419 it not works...
Keukul said:
I tried the CM13 20160406 NIGHTLY in my x9076 with panel r63419 it not works...
Click to expand...
Click to collapse
Me too, X9077, when start up, panel is keep black, not work.
this hacked version is work fine for me for now.
I am in the process of redownloading sources and updating to ROM to latest. I lost everything!
Thanks for merging LVM into CM13, I switched today from Nameless and unified storage works for me, however I'm experiencing a lot of random reboots during the day. Is there any log I can catch, so you can help me identify the source? Thx (also posting this on OPPO forums).
I am an oppo find 7 user, if I flash this rom will vocc fast charge works in my oppo. Pls let me.know
SamFail presents...
PartCyborgRom
BQL1
A Rooted Custom Rom
For G955U/W, Bootloader Revisions 1, 2, 3
Updates
NOW Supporting Bootloader V3!
I am happy to announce that BL version 3 phones are now supported by PartCyborgRom!
Just download the Version 3 BL further down in this post (after reading everything in between!) and use it in place of the normal BL Part2 file.
NOTICE: Rooting Process Steps Updated!
Enough people are coming from later bootloader revisions that have some extra protections that I updated the process to use an additional step. Many of you have used this step already at my suggestion when your AP flash was failing with Auth Error without a reboot to Upload.
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should keep working as long as nougat
(is that a haiku?)
Xposed Preinstalled
PCR now comes out of the flasher with xposed pre-installed!
NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot
New Boot Animation
Another great one from @Ryan-refoua.
This one is my favorite so far.
JamesDSP
I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have made me a fan and a regular user. Among other things, it has a better convolver (IRS processing) implementation, and its bass boost is significantly better than v4a. If there are things you like about V4A you can use both at the same time.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by @laura almeida, @Razerman and @ZaneZam. It features some cool additions like native adblocking (no more xposed module), overriding your max youtube resolution (you can watch 4k videos on your phone, but not 4k hdr). I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR
Improved Debloating
Found better stuff to delete. Added back some stuff I took out before that some of you asked for.
If you find something missing that you want back, pull it from the stock rom and install it in /system/app or /system/priv-app, wherever you got it from.
Improved Battery Life
Thanks to some battery sleuthing by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.
Performance Improvements
That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due some personally tested build.prop tweaks. Another part is some data optimisation scripts that now run at boot. You wont notice those, but they are there doing their thing.
Other Features
New for first time flashers
- Pre-Rooted with SuperSU installed
- CSC OYN pre-installed. Tested working on several carriers
- RCS and VoLTE icons removed from status bar.
- High quality audio mods, including
- Viper Audio (V4A)
- Dolby Atmos from the Axon 7
- Pandora hifi audio framework
- Native Google Dialer & Contacts support, including local search, spam call blocking
- Oreo 8.1 Emoji Icon Set
- Custom Lockscreen Clock font
- Stock system display fonts replaced with Apple's original San Francisco Font
Special Thanks
- @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
- The Aiur crew for Pandora (now a legacy mod but works great on the s8)
- @syndre for the Google Dialer and Contacts framework mod
- @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
- Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
- everyone who tested
Warnings/Disclaimers/Known Issues
- 80% Battery life like every other rooted US snapdragon device
- Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
- If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager.
SamFail Rooting Process
and Rom Installation
WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. It has neer happened to me, but I have a backup of my sdcard so I can be a little more risky. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up
- Both Prince Comsy Odin, and Regular Odin for flashing stock
- A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. Lets use this rom as our example. The full build number is as follows: G955USQS2BQL1
Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. But we are not flashing the BQL1 firmware (or Baseband), We are using an older version because it works better. The version we are flashing is: G955UEU2AQK2. Can you tell which revision it is?
Is my Phone Compatible?
Is it a G955U? Is it a G950W? If you answered "yes" to one of those questions, then the answer is "yes". That being said, flashing this rom if you are on bootloader revision 1 will upgrade your bootloader revision to 2, which means that any previous rom you were running wont work, so be prepared by having a copy of stock for bootloader version 2. If you don't want to move to version 2, you can still run the latest PartCyborgRom though, just use the G955UEU1AQk1 BL_ tar under Old Downloads in place of the one that came with this one. It will work just fine. However if you are unsure I suggest you go ahead and upgrade, there are not really any benefits to staying on 1 at this point.
Steps to Root
1) Download and unzip AP Part 1 and BL Part 2 zip files.
2) Download and unzip Prince Comsey Odin and start it up
3) Reboot device into Download mode and connect it to your pc
4A) Open Comsy Odin and Reboot into Download mode. Add Only the BL Part2.tar.md5 file. Go to the options tab and remove the checkbox next to "Auto-Reboot". Do not check any additional checkboxes and leave the other ones alone. Connect your phone and Start. Odin will flash the BL file to your device and will say PASS, but will just sit in download mode (because we turned off auto-reboot!). This makes the next part a little easier...
4B) Reset Comsy Odin and use the "three button salute" on your device to Reboot back Download mode. This time only add the AP Part1.tar.md5 file. Select only the following options:
- "Auto-Reboot"
- "F-Reset Time"
- "Nand Erase All"
NOTE: Odin will freeze while checking the AP tar.md5 hash.
Be patient, it will come back. If your computer is old this will take even longer.
5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while.
ATTENTION
When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".
If your device stays in Download Mode:
If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of usb ports as you have likely suffered from the usb3 corruption
When you see the upload mode page, do the 3 button salute to reboot into download mode again.
WARNING: When you reboot from upload mode, it wont look like download mode. You will see an error.
When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar. Just continue the process. It is safe to do so and that error will go away after the next step.
6) Close and re-open Comsy Odin or hit the reset button, and once again add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.
7) Do not change any of the options checkboxes, thus leaving the checkboxes checked for "F Reset Time" and "Auto Reboot". Click "Start" and flash the BL (part 2) to your device.
Note: Flashing BL twice is necessary as some newer stock BLs have patched the Root method we use, but the Combo Factory firmware is still vulnerable. In other words, the SamFail nickname continues to be prolific :good: :good:
Note: If you forgot to uncheck nand erase all, don't worry. You are just wasting time doing something again that you already did, the outcome is the same. "All" in "Nand Erase All" means "all userdata", which means cache and, well, userdata. Nothing else is deleted.
8) Wait for the flash to finish . It won't take very long at all as the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
From this point forther the scary download error message will be gone for good (or until next flash). Don't go looking yet though, you have more work to do to get root.
Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage
10) When in recovery issue a factory reset. This ensures that your device has a userdata and cache partitions that are valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
11) Boot the device as normal. Wait for it to come up. Its deodexed so it will take longer than even your average odexed rom.
All done!
FlashFire Instructions
- Get the ROM on your phone and unzip it
- Open up FlashFire
- Add a Wipe task, select the top 3 items only
- Select Flash Firmware and load up the AP_PartCyborgRom-BootLoopEdition-<version>.Part1.tar.md5 file to flash your new system
- Select Reboot to Recovery
- Make sure "Inject Root" is NOT checked
- Press go. Wait for the rom to flash and your device to reboot into recovery
- From recovery do a factory reset
- Then select reboot to Download Mode
- When device reboots into Download mode, flash BL_PartCyborgRom-BootLoopEdition-<version>.Part2.tar.md5
You have to use odin for the BL file because flashing bootloaders in FlashFire is a bad idea.
Dirty Flashers
Yes, you can dirty flash this rom to upgrade, however it is problematic and can cause issues. I did it for a long time, but my install was a mess by the time I gave up and reset.
To dirty flash, follow your preferred method of flashing above, but skip the Wipe step.
Odin
Skip "Nand Erase All" during the Part 1 flash. Do everything else the same
FlashFire
For the first Wipe task, instead of selecting the top 3, select only Dalvik like the second wipe task.
NOTE: This procedure is ONLY for people upgrading from an earlier PartCyborgRom version. If you are coming from stock you can not dirty flash because you userdata is encrypted which is not supported by the Factory firmware. If you are coming from other rom, or stock, I have no idea man but don't look at me if it blows up.
ANOTHER NOTE: This method of flashing is unsupported! If you do this and you have issues, you are on your own. If you think they are the rom, then back up your entire rom, wipe and reproduce them.
Help! I Got a Boot loop!
If you get a boot loop or your device hangs at boot, try the following:
1) Reboot to recovery and factory reset again.
To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode. If this doesnt help, or you can't get to recovery because you cant press the buttons right, proceed to the next step.
2) Try flashing just Part 2 (the BL) again. not only will this get you back in recovery, it will also format your cache again. Its worth a shot and doesnt take long.
Kernel Panic, Invalid Argument
Start Over
Go back to the beginning and do everything again. If it fails again, even in a slightly different way this time, bad interaction between the s8 and your USB port/controller/cable/etc are causing the image to be corrupted as its being written to disk. Try the following:
1) New USB Ports. If you have them, use a different set of usb ports (not the one next to it, but one further away). Its possible that that will be your "good" port, and that will be enough. Lots of machines also have some USB3 ports and some USB2.
2) New Cable. Its less likely, but maybe a new cable will help. Do the whole thing over with a new cable.
3) Try a few times. It sounds silly, but people who have had this issue have reported that eventually it just works. Try a few times until you get sick of trying. If you try like 10 times it probably wont work on the 11th though.
I Dont Have Another USB Port!
Try to borrow your partner/spouse/roommate/friends computer for a quick flash. Ask about the USB ports though, because another 3.0 port may not help you.
If you can't get someones computer, you can purchase a USB2.0 Hub online or at your friendly neighborhood electronics store. They arent very expensive, and I have heard positive reports from people saying it did the trick.
None of that Worked! I'm Screwed!
No you probably arent. I can count on one hand the number of people who someone couldnt get this working eventually. Some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Its right here!.
And they all rooted happily ever after.
The End.
XDA:DevDB Information
PartCyborgRom, ROM for the Samsung Galaxy S8
Contributors
partcyborg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: TouchWiz/Samsung Experience
Version Information
Status: Stable
Current Stable Version: BQL1
Stable Release Date: 2017-12-10
Created 2017-12-11
Last Updated 2018-2-10
Downloads
BQL1 (G955U and G955W)
AP_PartCyborgRom_G955U_BQL1.Part1.zip
[Alternate Mirror]
BL_PartCyborgRom_G955U_BQL1.Part2.zip
[Alternate Mirror]
NEW: Bootloader V3 Support!
BL_PartCyborgRom_G955U_U3BQL1_R5.zip
[Alternate Mirror]
Other Downloads
Do Not install any of these unless you are running an older version.
BQL1 has all of these mods already!
Remove OTA apps, downloads and debug messages
Remove RCS and VoLTE Icons Zip (Flash in FlashFire)
Odin3-v3.12-PrinceComsy-.zip
Previous Versions
SM-G955USQU2BQK5
AP and BL Parts 1 & 2
AP_PartCyborgRom-G955USQU2BQK5_Part1.zip
BL_PartCyborgRom-G955USQU2BQK5_Part2.zip
SM-G955USQU1AQK3
AP and BL Parts 1 & 2
AP_PartCyborgRom-BootLoopEdition-G955USQU1AQK3.Part1.zip
BL_PartCyborgRom-BootLoopEdition-G955USQU1AQK3.Part2.zip
One more
@partcyborg , nice work and thank you for posting your PCB ROM for S8+!
Thank you @partcyborg!
You ARE the f'ing man!!!!! THANK YOU!!!
And to the peeps whining, over the past 5+ months that there wasn't a custom ROM available for this phone, I would hope to see you hitting the 'Thanks' button.
You said you would do it, and you did it! Thanks for doing this for us! Very excited to give this a try.
Can't wait to get home and try this out!!!!!!
Im sooooo excited to try this .... Sucks im at work !!!!! Ahhhhhhhh no laptop !!!!!!
im wondering to get to this ROM and start from scratch .... do initial root process from https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911 ... then just flash this via flashfire in part II ... sounds correct yes?
ok so i have wiped everything before install and then followed install instructions all the way....
scratch that a reboot fixed the rotation issue
Wow ! I watched you actually say you wouldn't mind doing a rom for us and you did do it. AMAZING. I gotta try this when i get home ! time to back everything up lolol. Do you know if xposed works for this ? and also can we change the font with iFont now since you managed to? Once again thanks for port !
Flashed . No service. Cant upload picture because tapatalk is garbage. (Wrong file extension garbage)
On Sprint. Do i have to reflash the csc.?
Sent from my SM-G955U using Tapatalk
matthewd769 said:
Im sooooo excited to try this .... Sucks im at work !!!!! Ahhhhhhhh no laptop !!!!!!
im wondering to get to this ROM and start from scratch .... do initial root process from https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911 ... then just flash this via flashfire in part II ... sounds correct yes?
Click to expand...
Click to collapse
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work
partcyborg said:
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work
Click to expand...
Click to collapse
Any ideas?
Sent from my SM-G955U using Tapatalk
partcyborg said:
Nope you can do samfail. See the directions in op. It's super easy unless you only have usb3.0 ports in which case it probably won't work
Click to expand...
Click to collapse
thanks dog ... appreciate the hard work and answer .... i might start coughing and leave early
Goddly said:
Flashed . No service. Cant upload picture because tapatalk is garbage. (Wrong file extension garbage)
On Sprint. Do i have to reflash the csc.?
Click to expand...
Click to collapse
I solved this problem though flashin the bl through odin and doing a factory restore, i can use phone and data, but i can not message other people
Stovall Family said:
I solved this problem though flashin the bl through odin and doing a factory restore, i can use phone and data, but i can not message other people
Click to expand...
Click to collapse
Factory restore?
Sent from my SM-G955U using Tapatalk
Goddly said:
Factory restore?
Click to expand...
Click to collapse
Factory restore through stock recovery.
Goddly said:
Any ideas?
Click to expand...
Click to collapse
Can you fire up PreConfig and try and set your csc?
Also try flashing 1 more time. If you have a usb2 port absolutely use that. Several people have had major issues with flashing on usb3.0 ports and every one whose had a usb2 port to try it's worked flawless after. This rom will fail when stock doesn't because of its size. In order for samfail to work we have to use a raw image not a sparse one like in the stock AP. This means the image is the full size of the partition despite not being completely full
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.
Hey guys, if you're a noob or you haven't flashed a custom ROM to an android device since the likes of the Galaxy S2 like me, this guide is made for you!
Disclaimer: I am by no means taking credit for any links posted, credits to the creators of anything mentioned! And a special thank you to the creators of the TWRP and the ROM, hopefully development will grow for such an awesome device! I am not responsible if you brick your device (by not following my tutorial :/)
The only complaints I have about this ROM is the camera quality but install the GCAM port for the Mi10T Lite, it may help!
You will need:
A Mi10T Lite (duh) or any other supported device with MIUI Installed (Android 10)
A SD card
A laptop with fastboot installed ( [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 | XDA Developers Forums (xda-developers.com) )
A Mi account
TWRP (https://www.mediafire.com/file/qaea...0I_3.5.A10_05-01-2021_BL-L-fixsdcard.img/file)
The ROM (https://forum.xda-developers.com/t/rom-unofficial-10-0-gauguin-lineageos-17-1.4224633/)
GApps (I used this one: Download NikGapps from SourceForge.net)
B*lls
First (Ignore this if you already unlocked your bootloader):
Download MiFlash_Unlock (http://miuirom.xiaomi.com/rom/u1106245679/4.5.813.51/miflash_unlock-en-4.5.813.51.zip)
Make sure you have a Mi account and a SIM
Go to settings, enable developer options
Once you have done this, go to developer options (additional settings, scroll down)
Enable OEM Unlocking
Enable USB Debugging (not sure if this is necessary but I like to have it enabled anyway)
Click on Mi Unlock status and add your account, remember your details! (You may need to sign out and sign back in again)
It should say account linked to device successfully or something along those lines
Grab a cable (the included cable worked for me but other cables didn't)
OPTIONAL: YOU MAY WANT TO BACK UP ALL OF YOUR DATA
Open MiFlash_Unlock which you previously downloaded and connect your phone in fastboot mode (if it doesn't show up follow this tutorial: Fixed: Fastboot not detecting your Android device (qasimtricks.com) )
Click on unlock device! It should automatically reboot when it's done
Complete the set-up process, input your Mi account details and you should be good to go!
Enable developer options again and enable USB debugging
Installing TWRP (Ignore this if you already have TWRP installed!):
Turn off your device and boot into fastboot, connect and verify that it is connected by opening command prompt then typing "fastboot devices", it should show up
Point command prompt to the folder where your TWRP is downloaded (if it is located in downloads, type cd c:/users/(your username)/downloads
Then type fastboot flash recovery "twrp".img (replace "twrp" with the name of the recovery installed)
It should say successful, then type fastboot reboot and hold volume up + power
You've booted into TWRP! Hooray!
If it asks for the password to decrypt put it in, if it doesn't then no worries
You will notice that your internal storage is encrypted, not to worry!
Installing the ROM:
Connect your phone to your laptop (it can be in TWRP) and move the ROM to your SD card
Boot into TWRP if you haven't already, click wipe, advanced wipe and wipe Dalvik Cache/ART, Data and Cache
Once this has completed, go to install, then change the storage to SD Card
Locate the ROM file and swipe to flash!
Once the flash has completed, DO NOT REBOOT
Go to wipe and click format data, then type yes
Reboot to system! Done!
Installing GApps (Optional):
Move the GApps file provided to your phone
Boot to TWRP
It will prompt you to enter your passcode, this will decrypt the internal storage!
Click on install and locate GApps, swipe and flash!
Reboot
Congratulations! You have installed the first custom ROM made specifically for the device You can install Magisk if you want, I'm in the UK and my metro bank app didn't work but by using Magisk hide and changing the name of the Magisk manager everything worked (hide every Google app)
Enjoy! I hope you found this useful
thanks, after installing it can i go back to stock with locked bootloader?
jeuxtype said:
thanks, after installing it can i go back to stock with locked bootloader?
Click to expand...
Click to collapse
yes you can using xiaomi flash tool
Might want to confirm when to install gapps as if it's done after a boot it's not going to work!
Chari69 said:
yes you can using xiaomi flash tool
Click to expand...
Click to collapse
so it's safe to flash lineage, i want to use it but i need to get back to stock to watch netflix and for google pay?
jeuxtype said:
so it's safe to flash lineage, i want to use it but i need to get back to stock to watch netflix and for google pay?
Click to expand...
Click to collapse
Yes its safe, download the stock fastboot ROM online and use miFlash as mentioned, before you start flashing make sure the setting at the bottom right of the app is set to wipe + lock, I've already done it once and it worked fine
benfleet5 said:
Might want to confirm when to install gapps as if it's done after a boot it's not going to work!
Click to expand...
Click to collapse
Hey, that's awfully weird. When I tried flashing alongside the ROM I kept getting an error, but after I booted and done initial set up and tried installing it worked fine
Good guide a++++
deanlee121 said:
Good guide a++++
Click to expand...
Click to collapse
Thanks Dean!
Google pay works on this?
Xts7 said:
Google pay works on this?
Click to expand...
Click to collapse
Yeah just changed the magisk package name, enabled magisk hide and used gpay sqlite fix and it was all working. Metro Bank worked too
The only thing I'd say is that Open GApps Micro is the package you want to install; anything larger won't fit in the system partition - you get an Error 70! JT
jdtanner said:
The only thing I'd say is that Open GApps Micro is the package you want to install; anything larger won't fit in the system partition - you get an Error 70! JT
Click to expand...
Click to collapse
Hey, I've just been made aware that that works too, but NikkGapps also works! Also, ArrowOS comes pre-built with GApps and it's better imo, only thing is bluetooth audio doesn't work and the speaker crackles occasionally.
fizzy900 said:
Hey, I've just been made aware that that works too, but NikkGapps also works! Also, ArrowOS comes pre-built with GApps and it's better imo, only thing is bluetooth audio doesn't work and the speaker crackles occasionally.
Click to expand...
Click to collapse
Waiting until these bugs are sorted before trying that ROM. Bluetooth and general audio are fairly important to me
jdtanner said:
Waiting until these bugs are sorted before trying that ROM. Bluetooth and general audio are fairly important to me
Click to expand...
Click to collapse
Same somewhat lol, its annoying but thank God my headphones have a 3.5mm jack too!
Thanks for the guide, I recently got a redmi note 9 pro 5g from chinaland shipped to the uk then followed this guide pretty much, but instead of going twrp and lineage I went Orangefox and Arrow OS
I wasn't sure how all would go so was grateful of the guide as my first flashing on the new beasty..
I used this guide + info from the arrow thread before I jumped in..
just for info's it worked flawlessly
Steps I did
1. Unlocked bootloader ofcourse
2. installed Orangefox via fastboot
3. flashed latest version of china android 10 from sdcard (no reboot)
4. flashed arrow OS android 11 from sdcard
5. wiped data
To my amazement it booted first go and real fast like in under 5min!
can somebody explain why we need to wipe data after flashing ? surely wiping data means wiping ? but I guess it is not somehow wiping the good flash data..?
Where does all the data go when I flashed the first chinarom and why is it required to flash chinarom first ?
I have one bug bar the odd crackle, has anyone else noticed keyboard issues ? When i type sometimes it shows up backwards
ie google will appear as elgoog ?
I tried swiftkey keyboard + changing languages still the issue persists..
Thanks again @ Fizzy900
Jonny5isalivetm said:
Thanks for the guide, I recently got a redmi note 9 pro 5g from chinaland shipped to the uk then followed this guide pretty much, but instead of going twrp and lineage I went Orangefox and Arrow OS
I wasn't sure how all would go so was grateful of the guide as my first flashing on the new beasty..
I used this guide + info from the arrow thread before I jumped in..
just for info's it worked flawlessly
Steps I did
1. Unlocked bootloader ofcourse
2. installed Orangefox via fastboot
3. flashed latest version of china android 10 from sdcard (no reboot)
4. flashed arrow OS android 11 from sdcard
5. wiped data
To my amazement it booted first go and real fast like in under 5min!
can somebody explain why we need to wipe data after flashing ? surely wiping data means wiping ? but I guess it is not somehow wiping the good flash data..?
Where does all the data go when I flashed the first chinarom and why is it required to flash chinarom first ?
I have one bug bar the odd crackle, has anyone else noticed keyboard issues ? When i type sometimes it shows up backwards
ie google will appear as elgoog ?
I tried swiftkey keyboard + changing languages still the issue persists..
Thanks again @ Fizzy900
Click to expand...
Click to collapse
Hey bro, nice glad you enjoyed! So you have to format data after flashing a custom ROM from what I know in order to remove encryption, if you don't it'll show your internal files in a strange way and if you further tinker with it and do something it might stop you from installing apps full stop (happened to me cause I was being a tw*t lol). You need to flash the latest stock firmware (if the ROM requires you to) so you get the latest vendors which work with the custom ROM, although I believe there is a method to just flash vendor images themselves (fastboot flash vendor nameofvendorfile.img).
Yeah so arrowOS has notification crackles for some reason, most of the bugs are audio related (BT audio doesn't work either).
My typing was backwards too sometimes, it's because you're touching the fingerprint slightly which goes to the first element on a page or something (when you're typing it goes to the start of the box where you enter text). To understand what I mean go onto your launcher and tap the fingerprint scanner, it should highlight something.
I just flashed dotOS from arrow, works a charm! No audio related bugs afaik and BT audio works (lifesaver, phew).
Any other questions feel free to drop me a message on Telegram, @stillw0rking.
Take care! Also how in the world did you import the device from China hahahaha
epic fast reply!
<3
ahha the fingerprint!! I was wondering why I got random white box appearing on my home screen (and at random times) can it be disabled ?
So we got another rom already lol how excellent, I would like a rom that is stripped to the bone so we can install what we like, aka the least amount of crap running in the backround the merrier I am
Yea I just ordered from one of the china phone shops, got a note 9 pro 5g for £ 211 including postage, when I saw the price I just had to buy even tho my trusty oneplus 3t is still fine but but had the upgrade bug hehe, was from giztop, risked the custom charge and succeeded haha
Finally thanks for explaining the Encryption bit, yes I did read that but it seemed to go in one ear...
Guessing you are on the mainland somewhere, Greetings from across the pond
Jonny5isalivetm said:
epic fast reply!
<3
ahha the fingerprint!! I was wondering why I got random white box appearing on my home screen (and at random times) can it be disabled ?
So we got another rom already lol how excellent, I would like a rom that is stripped to the bone so we can install what we like, aka the least amount of crap running in the backround the merrier I am
Yea I just ordered from one of the china phone shops, got a note 9 pro 5g for £ 211 including postage, when I saw the price I just had to buy even tho my trusty oneplus 3t is still fine but but had the upgrade bug hehe, was from giztop, risked the custom charge and succeeded haha
Finally thanks for explaining the Encryption bit, yes I did read that but it seemed to go in one ear...
Guessing you are on the mainland somewhere, Greetings from across the pond
Click to expand...
Click to collapse
Haha yes I'm from near London! You must be the first English person I've actually bumped across on XDA ever lol. Aah yes, as far as I know it can't be disabled, it'll be stuck w that until the dev fixes it... ROMs have started to release quite quickly for the phone ever since the mi10i got dropped thank God, hopefully this is a good sign!
DotOS seems to be pretty light, heavy on the customizing side but when I started from fresh I had the basic google apps but gmail wasn't even installed lol. Dot is giving me the same sort of sot as Arrow, so really its up to you, but if the BT audio bug is a major thing for you (thank God one of my headphones can be used with a 3.5mm jack too lol) then I'd recommend Dot, but otherwise they're both extremely similar in terms of performance
And I was gna try and order the mi9T Pro like that but didn't bother, read some bad stories lol.
And no worries But yeah I'm pretty sure that is all it is, when you modify /system or something, the internal storage encrypts so you can't access it on stock ROM with TWRP but with custom you can decrypt easily
Take care mate!
Does lineage for mi 10t lite support 120 hz on screen ? Is it adaptive or locked?