Roms, Updates, Anything - Moto Z2 Force Questions & Answers

Roms, Updates, Anything - Moto Z2 Force Questions & Answers

SO, Is there ever going to be any custom roms or anything of the sort?? I check the site at least 2-3 times a week and nothing seems to ever change. Is this phone dead to the modders now??

Dirty unicorns said they are adding weeklies for the Z2 force starting the 6th. That's all I've heard other than the unofficial build of lineage os

AOSiP has an official build on their site. I'll get a thread going in a bit for detailed install instructions. The ROMs still aren't stable enough for official status. Gapps need to be baked in until they fix that, LTE still doesn't work for sprint. Video recording has no audio, VoIP traffic stutters... There are too many issues to release a "stable" build.

Edit:
Can the AoSip be installed from TWRP just as any other. There is also a kernel (Elemental Kernel in the nash download page.)Must this be used or can we still use pantheon. Can this not be installed from twrp as a regular rom? Boot twrp, Flash Rom, Flash Gapps, Flash Kernel, Reboot??? I am so ready for this. I did lots of rom porting, bug fixing on my old device. I feel if I can get in I can be some help.

Due to my impatience went ahead and tried to flash the latest AOSiP official from 3/28 Apparently I missed something because I am stuck at the boot animation. Here was my process exacly.
Pre Flash.
I was running the Tmo 8.0 27.1 December Security Patch. Pantheon Kernel. Twrp 3.2.1.1 on device.
Booted to twrp on device. Wipe Cache/Data/System. Flashed AOSiP 3/28/2018.zip . Elemental boot image. Reflash Twrp to device. Reboot to twrp. Flash OpenGapps 8.1 . Reboot to system.
Stuck at boot animation.
Apparently Im missing a step or doing things out of a particular order. Because I get no further than the boot animation.
Edit: After Playing with it a bit and wiping data and reinstalling gapps i get to a welcome screen with "google services has stopped" and bootloop repeatedly to that point. Wrong Gapps perhaps?

mr.duck254 said:
Due to my impatience went ahead and tried to flash the latest AOSiP official from 3/28 Apparently I missed something because I am stuck at the boot animation. Here was my process exacly.
Pre Flash.
I was running the Tmo 8.0 27.1 December Security Patch. Pantheon Kernel. Twrp 3.2.1.1 on device.
Booted to twrp on device. Wipe Cache/Data/System. Flashed AOSiP 3/28/2018.zip . Elemental boot image. Reflash Twrp to device. Reboot to twrp. Flash OpenGapps 8.1 . Reboot to system.
Stuck at boot animation.
Apparently Im missing a step or doing things out of a particular order. Because I get no further than the boot animation.
Edit: After Playing with it a bit and wiping data and reinstalling gapps i get to a welcome screen with "google services has stopped" and bootloop repeatedly to that point. Wrong Gapps perhaps?
Click to expand...
Click to collapse
Have you tried wiping the dalvik cache?

41rw4lk said:
Have you tried wiping the dalvik cache?
Click to expand...
Click to collapse
I am wiping it prior to flashing anything. Should I do it at another point also?

mr.duck254 said:
I am wiping it prior to flashing anything. Should I do it at another point also?
Click to expand...
Click to collapse
I usually wipe the dalvik cache after I flash an upgrade or anything major, that way I'm booting into a cleaner slate.

mr.duck254 said:
Due to my impatience went ahead and tried to flash the latest AOSiP official from 3/28 Apparently I missed something because I am stuck at the boot animation. Here was my process exacly.
Pre Flash.
I was running the Tmo 8.0 27.1 December Security Patch. Pantheon Kernel. Twrp 3.2.1.1 on device.
Booted to twrp on device. Wipe Cache/Data/System. Flashed AOSiP 3/28/2018.zip . Elemental boot image. Reflash Twrp to device. Reboot to twrp. Flash OpenGapps 8.1 . Reboot to system.
Stuck at boot animation.
Apparently Im missing a step or doing things out of a particular order. Because I get no further than the boot animation.
Edit: After Playing with it a bit and wiping data and reinstalling gapps i get to a welcome screen with "google services has stopped" and bootloop repeatedly to that point. Wrong Gapps perhaps?
Click to expand...
Click to collapse
try it without flashing gapps

mr.duck254 said:
I am wiping it prior to flashing anything. Should I do it at another point also?
Click to expand...
Click to collapse
Don't flash gapps for one. After a flash to any AOSP based ROM, you need to boot back into bootloader "AFTER" the flash and do a "fastboot -w" this will wipe your whole internal SD but is needed to avoid any idiosyncrasies between how the 8.1 AOSP ROMs handle data over stock.

Uzephi said:
Don't flash gapps for one. After a flash to any AOSP based ROM, you need to boot back into bootloader "AFTER" the flash and do a "fastboot -w" this will wipe your whole internal SD but is needed to avoid any idiosyncrasies between how the 8.1 AOSP ROMs handle data over stock.
Click to expand...
Click to collapse
I will try these when I get home from work. So just to clarify.
Twrp->wipe->rom->kernel->reboot to fastboot->fastboot -w from fastboot->reboot->profit?
At what point do I flash gapps? Reflash twrp?
Thanks in advance guys.

mr.duck254 said:
I will try these when I get home from work. So just to clarify.
Twrp->wipe->rom->kernel->reboot to fastboot->fastboot -w from fastboot->reboot->profit?
At what point do I flash gapps? Reflash twrp?
Thanks in advance guys.
Click to expand...
Click to collapse
Stock kernel will not work. Here is the AOSP kernel: https://drive.google.com/file/d/1nypgskfAoSOpOa_E-pfyaRO_mp_JWFxw/view?usp=drivesdk
Edit: gapps is included, no need to flash... Yet
Edit 2: reflash twrp right after flashing ROM if you want twrp on your boot images.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Worked like a charm. Thanks for the help guys. Time to take it for a test drive
Uzephi said:
Stock kernel will not work. Here is the AOSP kernel: https://drive.google.com/file/d/1nypgskfAoSOpOa_E-pfyaRO_mp_JWFxw/view?usp=drivesdk
Edit: gapps is included, no need to flash... Yet
Edit 2: reflash twrp right after flashing ROM if you want twrp on your boot images.
Click to expand...
Click to collapse

mr.duck254 said:
Worked like a charm. Thanks for the help guys. Time to take it for a test drive
Click to expand...
Click to collapse
Let us know the stability and what you've had issues with and what works!

Koohara947 said:
Let us know the stability and what you've had issues with and what works!
Click to expand...
Click to collapse
It was stated in the first page what's the issues with the roms.

Just got a z2 force on tmo. Unlocked and rooted already and now I've got the itch to flash something. Any recommendations on which rom to try out first? Preferably the most stable

raphi809 said:
Just got a z2 force on tmo. Unlocked and rooted already and now I've got the itch to flash something. Any recommendations on which rom to try out first? Preferably the most stable
Click to expand...
Click to collapse
All aosp ROMs currently out are based off the same, so they will have the same stability. They are stable, just features aren't working, like audio recording is hit and miss on apps

Uzephi said:
All aosp ROMs currently out are based off the same, so they will have the same stability. They are stable, just features aren't working, like audio recording is hit and miss on apps
Click to expand...
Click to collapse
Any special instructions as far as flashing goes. Since the rom section is kind of dead right now information seems to be kind of all over the place. My device is currently already on the stock Oreo rom. Can I just flash whatever rom zip and be good to go right now or do I have to worry about things like gapps, firmware and modem? Thanks for replying btw.

raphi809 said:
Any special instructions as far as flashing goes. Since the rom section is kind of dead right now information seems to be kind of all over the place. My device is currently already on the stock Oreo rom. Can I just flash whatever rom zip and be good to go right now or do I have to worry about things like gapps, firmware and modem? Thanks for replying btw.
Click to expand...
Click to collapse
In ROMs section, I got permission by the maintainer to create a thread for AOSiP, it has detailed instructions. All ROMs have the same install instructions.
I am open to any clarification, just post any issues you have with the instructions given. (say which number and what needs clarified).
Edit: firmware flashing will always be needed. You need the same firmware on both slots for seem-less updates to work on that ROM.

Update, any build after 05/05 will have the sprint LTE fix. I.E. you will have LTE on boot without any trickery.

Related

Problem I can not start 4.3 ROM! PLEASE HELP!

I had this problem with every ROM, when you load the boot animation to give his first vibration when you start to put your information, freezes and restarts. restarted like 5 times. download all the 4.3 Roms to the forum t989 but all feel the same.
Wipe the internal and external memory. so try and nothing. I went back to Stock Rom 2.3.6, I redid the Root. everything perfect. UVMC6 also install radio perfect, but still, still doing the same. I have a backup copy of AOKP 4.2.2 and as I have been much with it, I want to upgrade to 4.3 or 4.3.1 any help would really really bothers me and trying everything to update and no fun.

josue276 said:
I had this problem with every ROM, when you load the boot animation to give his first vibration when you start to put your information, freezes and restarts. restarted like 5 times. download all the 4.3 Roms to the forum t989 but all feel the same.
Wipe the internal and external memory. so try and nothing. I went back to Stock Rom 2.3.6, I redid the Root. everything perfect. UVMC6 also install radio perfect, but still, still doing the same. I have a backup copy of AOKP 4.2.2 and as I have been much with it, I want to upgrade to 4.3 or 4.3.1 any help would really really bothers me and trying everything to update and no fun.
Click to expand...
Click to collapse
What version and recovery are you using? What's your flashing process?

Still_living714 said:
What version and recovery are you using? What's your flashing process?
Click to expand...
Click to collapse
All Wipe ( Wipe Factory Reset, System, Data, Cache)
And Version Recovery TWRP 2.6.1.0 and CWM and nothing.

josue276 said:
All Wipe ( Wipe Factory Reset, System, Data, Cache)
And Version Recovery TWRP 2.6.1.0 and CWM and nothing.
Click to expand...
Click to collapse
I had a issue sorta like yours and I think had bad download of recovery I was using. I went through everything like you did and even used ODIN to back to stock reflashed and same problems. I switch versions of Recovery and retried and everything is smooth since.

msg1285 said:
I had a issue sorta like yours and I think had bad download of recovery I was using. I went through everything like you did and even used ODIN to back to stock reflashed and same problems. I switch versions of Recovery and retried and everything is smooth since.
Click to expand...
Click to collapse
that version installed to see if I will? and use TWRP and several CWM 2.6.1.0. which you worked for you?

Here a picture with TWRP 2.6.1.0 and I think a clean install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and here another after the boot animation that is where it freezes and reboots.

Hmmm this is weird. Flash your recovery thru Odin again and try it then

JesusWazBlack said:
Hmmm this is weird. Flash your recovery thru Odin again and try it then
Click to expand...
Click to collapse
I am on TWRP 2.6.1.0 as well.
I install the rom only no gapps or anything extra and let it boot and see what happens.
I know it may not be poss now but you could try taking out your ext-sd card and simm card and boot just from the internal drive.
I don't know that it would help but it can't hurt and it reduces variables.

msg1285 said:
I am on TWRP 2.6.1.0 as well.
I install the rom only no gapps or anything extra and let it boot and see what happens.
I know it may not be poss now but you could try taking out your ext-sd card and simm card and boot just from the internal drive.
I don't know that it would help but it can't hurt and it reduces variables.
Click to expand...
Click to collapse
now just try and pass the same freezes and gives reboot. : (
I feel stupid with this!

josue276 said:
now just try and pass the same freezes and gives reboot. : (
I feel stupid with this!
Click to expand...
Click to collapse
If you have tried a differnt version of TWRP and differnt 4.3 roms all on a clean install, I don't know what else to recommend.

msg1285 said:
If you have tried a differnt version of TWRP and differnt 4.3 roms all on a clean install, I don't know what else to recommend.
Click to expand...
Click to collapse
I can not wipe preload! believe they have to with this error?

and repair as to wipe Preload!. but still! boot freezes and reboots!! ANNOYING!!!!

josue276 said:
and repair as to wipe Preload!. but still! boot freezes and reboots!! ANNOYING!!!!
Click to expand...
Click to collapse
Hey i have the exact same problem! idk what happened, it's fine on 4.1.2 but right when i update to 4.2.2, not even 4.3 it does the exact same thing! any devs have any ideas? idk if a logcat will help in this case

why not just use another recovery like cwm and see if it works with that one.

Still_living714 said:
why not just use another recovery like cwm and see if it works with that one.
Click to expand...
Click to collapse
I use CWM. is the same.

You need completely wipe everything in order to flash a 4.3 ROM for the first time some times.
Sent from my SGH-M919 using xda premium

'Murica said:
You need completely wipe everything in order to flash a 4.3 ROM for the first time some times.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I did a full wipe. but nothing. Even now install the rom Cyanogenmod11
and only get to change language but then freezes and reboots. I was very excited because I thought that had already been arranged until he gave me the error. dont know what else to do to upgrade my phone!

msg1285 said:
I had a issue sorta like yours and I think had bad download of recovery I was using. I went through everything like you did and even used ODIN to back to stock reflashed and same problems. I switch versions of Recovery and retried and everything is smooth since.
Click to expand...
Click to collapse
JesusWazBlack said:
Hmmm this is weird. Flash your recovery thru Odin again and try it then
Click to expand...
Click to collapse
Still_living714 said:
What version and recovery are you using? What's your flashing process?
Click to expand...
Click to collapse
try another board that had saved because it has the USB damaged. try to set you up for the 4.2, 4.3 and 4.4 and also gave me freeze and reboot. and wipe everything very well. I can not be!. but a problem has to see. do not know if I can be my navigation buttons are damaged (broken wire). believe you can be what makes my phone restart?

I had this issue i just updated my twrp. Maybe you should download TWRP from a different source? Maybe the one you have is corrupted or something . IDK try everything.

this doesn't help any, just wanted to confirm the same issue. Anytime I flash ROM above 4.1.2 on this phone it crashes in some way. any custom ROM
Sent from my SGH-T989 using xda app-developers app

[ROM] [4.4.4] Samsung Galaxy S2 [d710] [Milestone 3.2] LiquidSmooth

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAMER
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.
Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave!
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device.
We ask that you do your part to know your device and know how to recover from problems before you flash!
cameron581
cdub50
Cl3Kener
CPA-Poke
deadman96385
iiD4x
itsmikeramsay
Jarrid42
johnnyslt
jsnweitzel
liquid0624
mtb300gt
Ntemis
reginald476
rkpeterson
rwaempires
sandtod
Somber73
sspencer10ls
TheBr0ken
timpohladthomas
Code:
Linaro 4.9 GCC Toolchain
O3 Strict-Aliasing & ISO C++11 Mode
ARM Optimized String Handling Routines
Linaro and Code Aurora Optimaztions
Slims DPI on the fly
Custom animation controls
TRDS 3.0 (Liquid Blackout in settings)
Active Display
Slims QuickSettings
Halo (Renamed to bubble in settings)
Ram Bar
T-Mobile Theme Engine
Privacy Guard
Built in SuperUser
Working wifi Tethering
Cell Broadcasts
Slims Configurable Power Menu
Slims Configurable Nav Bar
Custom animation controls (Listview)
LockScreen Notifications
And way more than this...
Code:
[url="https://plus.google.com/b/102153960718796996774/communities/117452480298315341829/stream/d5e8c0fe-5ee7-44df-97a5-6dd8cdcf8bb8"]Check are Google+ for a updates[/URL]
Code:
[url="http://github.com/LiquidSmooth"]LiquidSmooth Github[/URL]
[url="https://github.com/mtb3000gt/android_kernel_samsung_d710"]LiquidSmooth Kernel Github[/URL]
Code:
[url="http://www.drdevs.com/devs/teamliquid/Milestone/S2_Sprint/"]D710 Milestone 3.2 Download[/URL]
[url="http://www.drdevs.com/devs/teamliquid/Nightly/S2_sprint/"]D710 Nightly Download[/URL]
[url="http://www.drdevs.com/devs/teamliquid/Gapps/"]Liquid Gapps Download[/URL]
CLICK HERE TO SHOW LIQUIDSMOOTH SOME LOVE

This is a stable build for the Samsung Sprint S2 (D710)
Bugs:
Pie needs a reboot to show up
Click to expand...
Click to collapse
Samsung Sprint S2 (D710) specific bugs:
None so far
Click to expand...
Click to collapse
Install Instructions:
First time installing LiquidSmooth to your Samsung Sprint S2 (D710), or coming from another ROM:
- Make sure you're running latest Recovery
- Copy GApps and Liquid ZIP to your internal SDCard
- Boot into Recovery
- Flash Liquid zip from internal SDCard
- Flash GApps zip from internal SDCard
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse

Awesome
Sure glad to see this finally !
I would also recommend going to mounts and storage and manually format system the first time you install this to remove any old gapps and other taint .

MonstaDriva said:
Sure glad to see this finally !
Click to expand...
Click to collapse
I want to give a huge thanks to MonstaDriva for all his help and testing loads of builds until we got it right. It took us a long time to work out the issues but we finally got it to work, also thanks to dastin for his great device tree for the d710, I hope everyone enjoys this amazing rom

mtb3000gt said:
I want to give a huge thanks to MonstaDriva for all his help and testing loads of builds until we got it right. It took us a long time to work out the issues but we finally got it to work, also thanks to dastin for his great device tree for the d710, I hope everyone enjoys this amazing rom
Click to expand...
Click to collapse
I just got Villuminati on my phone and you come out with this.....seems like a great ROM to try out. good job.

......wow! I have not been this impressed with a rom in a long time. Just flashed this morning a few hours ago, changed it to US Cellular, and have been setting it up and it has been running very smooth. No fc's, no bugs, no issues whatsoever so far. The amount of setttings will take days to go through and test. Thank you for this one!

There's no mention of which modem to use. Does this require an ICS modem like all the other ROMs, or can a JB modem be used?
Make sure you're running latest Recovery
Click to expand...
Click to collapse
Which recovery?
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse
All apps or just system apps?

unknownsoldierx said:
There's no mention of which modem to use. Does this require an ICS modem like all the other ROMs, or can a JB modem be used?
Which recovery?
All apps or just system apps?
Click to expand...
Click to collapse
Use ICS for sure .Recovery same as whatever you use for CM 11 etc . Fors example if your currently on any other KitKat then your recovery is fine to use .
I think he means a fresh start without trying to restore apps , settings and data from your previous rom . Need a fresh start and just reset your phone up the first time . Reinstall your apps etc .Then on susequent nightlies you can just flash dirty and not lose your settings or data .

Well, I'm currently on stock rooted JB. I have yet to flash a custom rom on this phone. I'm thinking this will be my first. I suppose I'll start off trying twrp 2.6.3.0 for recovery.
I prefer to do everything on the phone. Guessing it will go like this:
1. Mobile odin StockCWM-EL26.tar.md5
2. Reboot to recovery
3. Flash twrp zip
4. reboot recovery
5. Backup stock install
4. Flash ICS modem
5. Wipe all
6. Flash LiquidSmooth
7. Flash gapps

AMAZING
this ROM is absolutely beautiful the theming settings etc just amazing outstanding job devs

unknownsoldierx said:
Well, I'm currently on stock rooted JB. I have yet to flash a custom rom on this phone. I'm thinking this will be my first. I suppose I'll start off trying twrp 2.6.3.0 for recovery.
I prefer to do everything on the phone. Guessing it will go like this:
1. Mobile odin StockCWM-EL26.tar.md5
2. Reboot to recovery
3. Flash twrp zip
4. reboot recovery
5. Backup stock install
4. Flash ICS modem
5. Wipe all
6. Flash LiquidSmooth
7. Flash gapps
Click to expand...
Click to collapse
I don't think you need to flash twrp.
Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2

unknownsoldierx said:
Well, I'm currently on stock rooted JB. I have yet to flash a custom rom on this phone. I'm thinking this will be my first. I suppose I'll start off trying twrp 2.6.3.0 for recovery.
I prefer to do everything on the phone. Guessing it will go like this:
1. Mobile odin StockCWM-EL26.tar.md5
2. Reboot to recovery
3. Flash twrp zip
4. reboot recovery
5. Backup stock install
4. Flash ICS modem
5. Wipe all
6. Flash LiquidSmooth
7. Flash gapps
Click to expand...
Click to collapse
No, don't flash TWRP. Coming from a rooted, JB ROM
1. Reboot recovery
2. Nandroid backup stock install
3. Flash StockCWM-EL26.zip
4. Reboot recovery
5. Flash FL24-ICSmodem.zip
6. Wipe all
7. Flash Blasphemy kernel 6.2-4.3.zip OR Dastin's CM10.2.zip
8. Reboot into recovery
9. Flash LiquidSmooth
10. Flash Gapps
You can do the Mobile Odin thing but there are zips for the recovery-kernels that work just fine. Some people have reported issues with flashing the Blasphemy kernel 6.6-4.3, so stick with version 6.2.
Let us know what works for you.

ttakacs said:
No, don't flash TWRP. Coming from a rooted, JB ROM
1. Reboot recovery
2. Nandroid backup stock install
3. Flash StockCWM-EL26.zip
4. Reboot recovery
5. Flash FL24-ICSmodem.zip
6. Wipe all
7. Flash Blasphemy kernel 6.2-4.3.zip OR Dastin's CM10.2.zip
8. Reboot into recovery
9. Flash LiquidSmooth
10. Flash Gapps
You can do the Mobile Odin thing but there are zips for the recovery-kernels that work just fine. Some people have reported issues with flashing the Blasphemy kernel 6.6-4.3, so stick with version 6.2.
Let us know what works for you.
Click to expand...
Click to collapse
Does the Blasphemy kernel work on 4.4.4 ROMs or just this one?
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
soldier1184 said:
this ROM is absolutely beautiful the theming settings etc just amazing outstanding job devs
Click to expand...
Click to collapse
THANKS for serving our country.

bigmike6200 said:
Does the Blasphemy kernel work on 4.4.4 ROMs or just this one?
Click to expand...
Click to collapse
The Blasphemy kernel is for 4.2 and 4.3 ROMs; the 4.3 kernel is needed to flash a v.4.4 ROM. I haven't tried this kernel with a v.4.4 ROM.

ttakacs said:
No, don't flash TWRP. Coming from a rooted, JB ROM
1. Reboot recovery
2. Nandroid backup stock install
3. Flash StockCWM-EL26.zip
4. Reboot recovery
5. Flash FL24-ICSmodem.zip
6. Wipe all
7. Flash Blasphemy kernel 6.2-4.3.zip OR Dastin's CM10.2.zip
8. Reboot into recovery
9. Flash LiquidSmooth
10. Flash Gapps
You can do the Mobile Odin thing but there are zips for the recovery-kernels that work just fine. Some people have reported issues with flashing the Blasphemy kernel 6.6-4.3, so stick with version 6.2.
Let us know what works for you.
Click to expand...
Click to collapse
What is wrong with using twrp? I don't like SockCWM-EL26 since it doesn't have a wipe boot option and the nandroids don't have correct dates. The file name of my nandroid had a file name of 2000-01-01 and the timestamp for the files said they were created in 1999.
Also, how can I do your step 2 when I start from stock without a custom recovery?
And why use a different kernel? What's wrong with the one that comes with this rom?

unknownsoldierx said:
What is wrong with using twrp? I don't like SockCWM-EL26 since it doesn't have a wipe boot option and the nandroids don't have correct dates. The file name of my nandroid had a file name of 2000-01-01 and the timestamp for the files said they were created in 1999.
Also, how can I do your step 2 when I start from stock without a custom recovery?
And why use a different kernel? What's wrong with the one that comes with this rom?
Click to expand...
Click to collapse
If you have rooted this phone, you will have installed a custom recovery. On this phone, the kernel and recovery are integrated: that means CWM plus applicable kernel (in this instance, starting with the EL26 or EL29 kernel plus recovery). When the term "safe recovery" is used, it usually refers to one of these. There is a way to flash TWRP but that's after flashing everything (search the forum).
To flash a KitKat ROM requires a 4.3 kernel plus recovery.

I'm rooted, but when I boot into recovery it is "Andoird system recovery <3e>" and there are no options to wipe partitions except for wipe data/factory reset and wipe cache partition, and there is no nandroid feature. I've got the stock GB28 kernel.

unknownsoldierx said:
I'm rooted, but when I boot into recovery it is "Andoird system recovery <3e>" and there are no options to wipe partitions except for wipe data/factory reset and wipe cache partition, and there is no nandroid feature. I've got the stock GB28 kernel.
Click to expand...
Click to collapse
Here's how to flash Agat's custom recovery: http://theunlockr.com/2013/02/08/ho...4g-touch-sph-d710-running-android-4-0-4-fi27/

7-7-14 Nightly Out Now

ttakacs said:
Here's how to flash Agat's custom recovery: http://theunlockr.com/2013/02/08/ho...4g-touch-sph-d710-running-android-4-0-4-fi27/
Click to expand...
Click to collapse
Installed the Agat FI27 repack 2 that you linked to. Still get the same error as with other recoveries. When I try to flash this rom, I get:
set_metadata_recursive: some changes failed
E: error in /emmc/ROMs and RecoveriesKitKat ROMs/LiquidSmooth v3.1/LS-KK-v3.1-2014-07-02-d710.zip
(status 7)
Installation aborted
Click to expand...
Click to collapse

Can't boot any AOSP rom, stuck on 1+ screen, CB still boots

hello,
(with "this rom" i mean >sultan cm13<. I edited the title, before that it "was can't but sultan cm13", but now i know it doesnt boots any aosp roms)
a few days ago i used this rom as secondary with multirom (primary was freedom 1.10). now today, i wanted to use this rom as my dailydriver rom. i made the normal procedure, making a backup, then wiping the partitions (system, data, cache, dalvik) and after it flashing the rom. on the first try, i did it like i usually do, first the rom, then the gapps and then xposed. then i rebooted, and it was stuck on the 1+ logo screen about 10 mins. then i reflashed it, but just the cm.zip. then i still got stuck.
i tried it with the unofficial and the official twrp recovery. now i did a nandroid restore to the freedomos rom, and it boots normal.
please help me, i really want to use sultans cm13, i really like it!
i don't know why it doesn't work, i mean as a secondary it booted flawless..
btw i'm on the 3.2.7 firmware
(problem exists on all 6.0 aosp roms i tried. Please read further posts)

Did you follow the flashing instructions to the letter? If you did, you would have seen that the CM13 requires a one time flash of the OOS 3.2.6 firmware (linked in the thread).

Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks

ReNeH99 said:
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
Click to expand...
Click to collapse
BTW, which xposed version did you flash? If it was v86.x then that's the most likely culprit (since the latest patch, v87 works, v86.x causes bootloop).

i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.

ReNeH99 said:
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
Click to expand...
Click to collapse
Hmm... strange... TWRP doesn't give any errors either?

Hw4ng3r said:
Hmm... strange... TWRP doesn't give any errors either?
Click to expand...
Click to collapse
nope no errors, all the folders and build.prop, etc is in the /system folder too..
i also redownloaded the rom, md5 hash is right and it doesn't help either

May be a silly question but did you uninstall multirom?

Hw4ng3r said:
May be a silly question but did you uninstall multirom?
Click to expand...
Click to collapse
yep
i gonna try to flash RR 5.7.4, to see what happens then
edit: what i forgot to say, i also reinstalled multirom and the multirom recovery for another try. in the multirom menu the touch doesn't work then, and when the primary rom (cm13 sultan) boots after 5 secs, i just get a black screen, the phone isnt of, just a black screen, i have to press all 3 buttons for a reboot then.
edit2: RR also does not boot
edit3: lol i just reinstalled multirom and it boots as secondary rom. then i copied it to the primary slot, and *bling* it doesn't boot again... i dont get this...

Ok i tried it with multiple AOSP roms and it simply doesn't work. Strange thing is, they work as a secondary rom when i have multirom installed.
Does anybody have a solution for this maybe? I hope someone who knows about this problem can help me i don't want oos anymore i need aosp

ROM new Lineage 14.1 Unofficial WhenICanlies d2tmo 4-10-18

I have been working on the sister models also. I saw no one was building these anymore so here it is I hope it can be enjoyed by all. Spread the word. provide feedback so other fans of this ROM may obtain it and work out any bugs if there are any. I will update once or twice a week depending on time and demand. I'm compiling for three different variants. Hit the thanks button and Enjoy. Dirty flash the updates not the initial flash of this rom but the updates to it. Initial install = Factory reset, wipe data and cache, install rom zip, install gapps zip, install su zip, reboot system. As of 9-3-18 i will be switching to Ubuntu 18.04 Bionic Beaver, that being said i do not know if i will have to change anything or do anything different to keep pushing these updates out but i will most definitely try to keep them coming.
4-10-18
https://www.androidfilehost.com/?fid=890129502657597436
4-13-18
https://www.androidfilehost.com/?fid=818070582850507491
4-17-18
https://www.androidfilehost.com/?fid=818070582850508419
4-24-18
https://www.androidfilehost.com/?fid=673956719939836620 If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app
5-4-18
https://www.androidfilehost.com/?fid=818222786056028546
Root is not baked in. Flash and root your preferable way.
5-20-18
https://www.androidfilehost.com/?fid=674106145207488021
5-31-18
https://www.androidfilehost.com/?fid=674106145207490572
7-28-18
https://www.androidfilehost.com/?fid=5862345805528060741
9-3-18
https://www.androidfilehost.com/?fid=1322778262903996744
10-07-18
https://www.androidfilehost.com/?fid=1322778262904022369
12-7-18
https://www.androidfilehost.com/?fid=11410963190603868411
12-16-18
https://www.androidfilehost.com/?fid=11410963190603876081
2-25-19
https://www.androidfilehost.com/?fid=1395089523397901582
3-24-19
https://www.androidfilehost.com/?fid=1395089523397924752
5-6-19
http://download1589.mediafire.com/7...q5/lineage-14.1-20190507-UNOFFICIAL-d2tmo.zip
10-13-19
https://www.androidfilehost.com/?fid=1899786940962607809
i recommend clean flash as i built with different computer
setprop persist.lineage.nofool true in terminal emulator with root privs (type su first grant permission then setprop persist.lineage.nofool true) gets rid of persistant notification
Bluetooth dialtone when playing music fix
Settings > Battery > tap in 3-dot menu at top right tap on Battery optimisation. To show all apps and services here, select the ‘All apps’ options under the dropdown. Tap on both of the Bluetooth services and change them to Don't optimise.

thanks bro... but is it rooted rom or use any method to root it ?

hasan.sy said:
thanks bro... but is it rooted rom or use any method to root it ?
Click to expand...
Click to collapse
I use SuperSU zip

the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it

hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
I appreciate the feedback and no worries mate I'm still trying to get the no sim bug worked out in the att variant no luck so far sprint variant is doing good also

Update posted 4-17-18

It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.

Sammay_Boiii said:
It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.
Click to expand...
Click to collapse
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding

Joker1716 said:
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding
Click to expand...
Click to collapse
Thank you for your rapid response! I will try that as soon as I get to my house and I'll let you know what happens

After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?

Sammay_Boiii said:
After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?
Click to expand...
Click to collapse
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
This should help
https://forum.xda-developers.com/showthread.php?t=1949687

Joker1716 said:
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
Click to expand...
Click to collapse
I will do that. Your rom needs to be flashed over stock rom?

Sammay_Boiii said:
I will do that. Your rom needs to be flashed over stock rom?
Click to expand...
Click to collapse
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?

Joker1716 said:
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?
Click to expand...
Click to collapse
What you said makes a lot of sense actually. Im used to just flashing back ups of other roms that I forgot how to flash fresh ones. I'm not used to this haha but I got it now. Stock rom 4.3 has been flashed via odin and the root method is currently on my screen.

hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3

Sammay_Boiii said:
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3
Click to expand...
Click to collapse
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher

hasan.sy said:
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher
Click to expand...
Click to collapse
Thank you. Ive been flashing this rom repeatedly and always received a "Process system not responding" then it falls into a boot loop

Update posted

Joker1716 said:
Update posted
Click to expand...
Click to collapse
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)

hasan.sy said:
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)
Click to expand...
Click to collapse
If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app

Question How to fix "Failed to mount 'system/system ext./product/vendor/odm (Block device required)

I simply want to flash a different custom rom from custom rom (crdroid) on my POCO F3, but I am unable to do that because of these persistent errors. Please advise me on how to resolve this so that I may successfully flash my rom using the step-by-step instructions. Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Removed]

cyanGalaxy said:
Don't directly dirty flash another Custom ROM, this will almost certainly brick your phone.
You must flash Stock ROM (Official MIUI ROM) inbetween switching to another Custom ROM. It should be done cleanly.
Click to expand...
Click to collapse
I wanna return to the stock rom. What should I do to properly flash stock ROM using TWRP recovery? I usually get those errors (device block required) when I try to flash a rom. Please help.

oyolzn said:
I wanna return to the stock rom. What should I do to properly flash stock ROM using TWRP recovery? I usually get those errors (device block required) when I try to flash a rom. Please help.
Click to expand...
Click to collapse
Sorry, I was mistaken, I think you are flashing Official MIUI, right?..
If you chose the Full Recovery ROM for MIUI, it should work.. I don't know why it's not working.
Have you tried wiping Dalvik Cache & Data?
(after flashing MIUI, you can then proceed flashing a different Custom ROM)

cyanGalaxy said:
Sorry, I was mistaken, I think you are flashing Official MIUI, right?..
If you chose the Full Recovery ROM for MIUI, it should work.. I don't know why it's not working.
Have you tried wiping Dalvik Cache & Data?
(after flashing MIUI, you can then proceed flashing a different Custom ROM)
Click to expand...
Click to collapse
Yes, I'm flashing the official MIUI. I have no idea why it isn't working. Even after wiping the data and dalvik cache, such problems continue to appear. Is there a way to fix such problems on TWRP? Would you kindly assist me? My device doesn't have an OS installed anyway.

oyolzn said:
Yes, I'm flashing the official MIUI. I have no idea why it isn't working. Even after wiping the data and dalvik cache, such problems continue to appear. Is there a way to fix such problems on TWRP? Would you kindly assist me? My device doesn't have an OS installed anyway.
Click to expand...
Click to collapse
Have you tried using TWRP skkk? That one supports Android 12's encryption
skkk/TWRP/A12 • AKR DL
dl.akr-developers.com
I got that link from here: https://forum.xda-developers.com/t/...p-3-6-0_11-v2-9-3_a11-alioth-skkk-is.4373463/

oyolzn said:
I simply want to flash a different custom rom from custom rom (crdroid) on my POCO F3, but I am unable to do that because of these persistent errors. Please advise me on how to resolve this so that I may successfully flash my rom using the step-by-step instructions. Thank you.View attachment 5664333
Click to expand...
Click to collapse
i used to get these but then i tried once to mount all partitions before flashing and i didnt get these comments

partitions encrypted, need to be formatted before reflashing ROM, better backup all your data if you can still access it, if not, then say goodbye to your files because you need to format it.

cyanGalaxy said:
Have you tried using TWRP skkk? That one supports Android 12's encryption
skkk/TWRP/A12 • AKR DL
dl.akr-developers.com
I got that link from here: https://forum.xda-developers.com/t/anybody-know-what-twrp-3-6-0_11-v2-9-3_a11-alioth-skkk-is.4373463
Click to expand...
Click to collapse
SamantaSync said:
partitions encrypted, need to be formatted before reflashing ROM, better backup all your data if you can still access it, if not, then say goodbye to your files because you need to format it.
Click to expand...
Click to collapse
How can I format partition? Given that the device is new, it's okay if my files are gone. I only want to install and get back the official ROM as I'm used to custom ROMs (crdoid) on my device. Is there a step-by-step guide for fixing that? Please help me so that I can continue to flash successfully. Even after formatting the data and entering "yes," those errors continue to appear. Data formatting is not successful.

3zozHashim said:
i used to get these but then i tried once to mount all partitions before flashing and i didnt get these comments
Click to expand...
Click to collapse
How can I mount all partition? What recovery are you using? Please help.

twrp

oyolzn said:
How can I format partition? Given that the device is new, it's okay if my files are gone. I only want to install and get back the official ROM as I'm used to custom ROMs (crdoid) on my device. Is there a step-by-step guide for fixing that? Please help me so that I can continue to flash successfully. Even after formatting the data and entering "yes," those errors continue to appear. Data formatting is not successf
Click to expand...
Click to collapse
oyolzn said:
I simply want to flash a different custom rom from custom rom (crdroid) on my POCO F3, but I am unable to do that because of these persistent errors. Please advise me on how to resolve this so that I may successfully flash my rom using the step-by-step instructions. Thank you
oyolzn said:
I simply want to flash a different custom rom from custom rom (crdroid) on my POCO F3, but I am unable to do that because of these persistent errors. Please advise me on how to resolve this so that I may successfully flash my rom using the step-by-step instructions. Thank you.View attachment 5664333
Click to expand...
Click to collapse
Fastboot boot twrp skk 3.6.0 after go to recovery format data , then u able to flash , I had this issue when I use 3.6.0 skk then it's fixed
Click to expand...
Click to collapse

Develop Bugs

welcome