Code:
#include
/*
* 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.
*/
This is the well known Build of Jiayu Germany Lollipop Release Candidate 5 (latest) for Jiayu S3 (Advance/Basic) with MTK 6752 SoC
There's also a modified version , for the new Jiayu s3 Pro ( with 32GB of internal memory ) also MTK6752
This is being posted here, as this is a full SPFlashTools "Base" ROM, usually used to recover your device
( or if you want to roll back to Lollipop ...)
The "REPACK" Version is simply the same RC5 Rom, but with latest M.A.D. TWRP already included
There's also a modified version for the s3 Pro (32GB)
The Rom should be flashed in "UPGRADE MODE" on SPFlashTools. (Doesn't matter in what ROM / OS you currently are ...)
DO NOT flash any SP Flash Tools Jiayu s3 (old 16gb) roms on the new Jiayu s3Pro (32GB)
--> Preloader, partitions are different, you'll get an hard brick.
Installation Instructions:
BACKUP EVERYTHING, This will ERASE everything from your internal phone memory (pics, videos, data, etc )
Turn OFF the phone
Open MediaTek SPFlashTools
Load mt6752 Scatter
Choose "Upgrade Mode"
Press "Download"
At this moment, plug USB Cable to phone, it'll start flash ...
Some Jiayu S3, require BOTH Volume Keys to be pressed , while you plug USB Cable to enter in "download Mode"
If you wish to upgrade to latest M.A.D. Android Nougat, after you flashed RC5, it's recommended that you let the RC5 boot up, then you can go back to recovery ( Latest M.A.D. Recovery included already)
Place AOSP Nougat Rom on internal memory/ external SDCard
WIPE ALL
Flash AOSP and GAPPS & SuperSu (latest two optional)
Download ROMs from "XDA DevDB Download Section"
Choose the right rom, for your Jiayu S3 variant (s3 advance / basic 16GB) or ( s3 pro 32GB )
Working:
Everything
The Rom Changelogs, and old discussion can be found on this thread :
https://forum.xda-developers.com/jiayu-s3/development/rom-jiayu-s3-5-1-1-t3217241
GPL Compliance:
https://github.com/MediatekAndroidDevelopers
XDA:DevDB Information
[ROM] [REPACK] [ 5.1.1 ] RC5 Lollipop Jiayu S3 & S3 Pro [MT6752], ROM for the JiaYu S3
Contributors
superdragonpt, DerTeufel1980
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: SP Flash Tools
Based On: MediaTek AOSP
Version Information
Status: Stable
Created 2017-01-25
Last Updated 2017-01-25
Reserved
,,,,,,,,,,,,,,
Please include boot from AICP 10 (with fixed wi-fi hotspot).
superdragonpt said:
ROMs will take a while to be uploaded ...
slow speed...
Click to expand...
Click to collapse
thanks man.....
waiting for the s3 pro version....
My net provider is having issues, I currently have no home connection, hopefully they'll fix this today, for me to upload
Bb
ROMs being uploaded
superdragonpt said:
ROMs being uploaded
Click to expand...
Click to collapse
thank you so much...
hope flashing rc5 and then stable 7 fix my low signal connection on s3 pro
All done ...
Can you also upload the SPFT flash tool so that people would use a similar version and reduce variables and become easier to debug when a problem arises?
I'm sorry for the stupid question but are de download links?
Have searched in the download section but keeps sending me back to this post!
Enviado do meu Redmi Note 3 através de Tapatalk
Found it, sorry for double post!
Enviado do meu Redmi Note 3 através de Tapatalk
Upgrade successfull!
Thank you. This has helped me gretly with my quest to upgrade 4.4 -> 5.x -> 7.x.
I had a problem with uploading through SP Flash Tool that it wouldn't start to download to phone, but after many tries i finally changed USB port, and then it worked like a charm.
I have a question though. Should i stay on this ROM or upgrade to 6.0.1 or what? The problem is that Xposed framework does not work yet with 7.x, so untill it does, i will stay on system that does support it.
AgiZ10 said:
Thank you. This has helped me gretly with my quest to upgrade 4.4 -> 5.x -> 7.x.
I had a problem with uploading through SP Flash Tool that it wouldn't start to download to phone, but after many tries i finally changed USB port, and then it worked like a charm.
I have a question though. Should i stay on this ROM or upgrade to 6.0.1 or what? The problem is that Xposed framework does not work yet with 7.x, so untill it does, i will stay on system that does support it.
Click to expand...
Click to collapse
Then go with AICP11 MM its the best MM rom for the phone with xposed (mm) available ...
superdragonpt said:
Then go with AICP11 MM its the best MM rom for the phone with xposed (mm) available ...
Click to expand...
Click to collapse
Thanks, done.
Will continue replying there if something comes bugs me
A huge thank you for the s3pro version. I have just bought a second S3 32gb without knowing that it was different to my old S3 32gb, and bricked it trying to install the old rc5 that is on my old phone. This version rescued the phone from death!!
Can I use TWRP to install SuperSU and root it? I'm guessing there's zero chance of flashing 7.1.1 on the s3pro.
StoneTheKiwis said:
A huge thank you for the s3pro version. I have just bought a second S3 32gb without knowing that it was different to my old S3 32gb, and bricked it trying to install the old rc5 that is on my old phone. This version rescued the phone from death!!
Can I use TWRP to install SuperSU and root it? I'm guessing there's zero chance of flashing 7.1.1 on the s3pro.
Click to expand...
Click to collapse
I've just found that the recovery is the chinese one, not twrp. Reflashing just recovery does not change this. The build number is 20160302-190806. Any ideas on what might have happened here?
I made this thread mainly for the newer s3 33GB variant...
Since I also got the 32gb variant, after my old s3 died
You just need to follow instructions on the first post
Download full rc5 repack for the 32GB variant
And flash in "upgrade mode"
You,ll get the newer MAD twrp, that is also Nougat compatible.
After flash, just boot to recovery , full wipes (including data, and flash newer Nougat release)
Cheers
superdragonpt said:
I made this thread mainly for the newer s3 33GB variant...
Since I also got the 32gb variant, after my old s3 died
You just need to follow instructions on the first post
Download full rc5 repack for the 32GB variant
And flash in "upgrade mode"
You,ll get the newer MAD twrp, that is also Nougat compatible.
After flash, just boot to recovery , full wipes (including data, and flash newer Nougat release)
Cheers
Click to expand...
Click to collapse
Thanks for your reply. I've just done it all again - downloaded the PRO pkg afresh and flashed as 'upgrade', but again booting to recovery shows a chinese menu. I also flashed in 'format all' mode, but the same result. I'm downloading the pkg from the 'downloads' section of this forum, and it unpacks to show recovery as 'S3_h560_TWRP_3.0.2-0' at 13,074kb. The recovery from the old rc5 pkg is a different size - I suppose that can't be used without rewriting the scatter file? Or does the scatter file reference the recovery that's recommended for your latest 7.1.1 rom? I could just get that separately and copy it in.
Apart from blaming the pixies, I really don't understand what is going wrong here.
Stranger and stranger. I replaced the recovery with the one hosted on mediafire for 7.1.1 (though that has a space in the filename which had to be removed for the scatter txt to recognise it) and after flashing the phone was bricked. Then replaced recovery with the one from rc5 and again it was bricked. Then unpacked afresh the pro pkg and flashed with that in 'format all' mode - this time it booted to chinese recovery but refused to boot normally. Then reflashed in 'upgrade' mode and now it boots normally but refuses to boot to recovery. Perhaps the hardware has been changed even further, or perhaps the gods are just laughing at me, but I've run out of options now. The problem is that supersu won't install without updating itself (though it's 2.79) and it fails to update under the 'normal' update option and doesn't have a twrp recovery to update through. Hence the phone can't be rooted.
Sorry for this question, please how can I revert to this ROM I'm already on 7,1.2, what does repack means or how should I repack it ,any possible way to use spflashtool for this ROM, your answer is highly needed urgently please to whom ever knew
Related
I would firstly like to apologise in advance to all the members in here that are gurus. (I get paranoid when it comes to things that I describe bellow)
So I have just bought and received my mi4c, but as I am sure a great deal of people in this forum, I am experiencing certain things I do not like. What am I referring to you may ask? Primarily the massive amount of Chinese bloatware + unstable google services.
I have done a bit of my homework but I got stuck and came here. So here is the list of things that I am trying to do:
Install international rom (http://xiaomi.eu/community/threads/5-10-8.28692/) for gapps and removal of bloat
root
custom recovery (twrp)
So here is the challenge.. I do not know in what order to do them. I also found this thread here (http://forum.xda-developers.com/mi-4c/development/flash-twrp-using-flashify-app-pc-dev-rom-t3230355) which is basically root + recovery but it asks you to use a developer rom, wouldn't that be pointless if I am going to flash the international one?
Can someone please point me in the correct direction
Thanks in advance.
The rom from xiaomi.eu has to be flashed with TWRP - so you have two choices:
1. boot or flash TWRP via fastboot and after that flash the Rom from Xiaomi.eu
or if you do not want to mess with drivers and computer and fastboot:
2. use the built in updater app to change to the chinese/english stock developer! rom found here (dev version has root built in) - after that flash TWRP via an app like flashify (play store) - flash Xiaomi.eu within TWRP
i chose the 1. Variant and did only BOOT TWRP (fastboot boot .....) and did not permanently flash it at this time - so i could make a nandroid backup of the complete stock ROM - including the stock recovery first ! If you go this way too - do a backup of the ESF partition too because this one contains your IMEI and MAC Adress infos - can help to have this backup in the hand if something fails. If you have an OTG cable you can directly backup to an external USB Stick (must be FAT32 formatted !). I found this was the best solution for me before permanently flashing any other ROM.
Be aware that if you boot TWRP (temporarily or permanent flashed version) the touch sometimes simply does not work (in a few cases the power button did not work too). Solution: wait two or three minutes until the touch begins to work.... i used the TWRP (DEV Variant of the recovery) found here. Because the touch begins to work a little faster (sometimes it works instant).
since the last 2 weeks i stick with the sMIUI ROM (its a "slimmed" Xiaomi.eu ROM) you can cook your individual slimmed variant here. And you can read a little about it here.
Hope this helps you....
Andiii said:
The rom from xiaomi.eu has to be flashed with TWRP - so you have two choices:
1. boot or flash TWRP via fastboot and after that flash the Rom from Xiaomi.eu
or if you do not want to mess with drivers and computer and fastboot:
2. use the built in updater app to change to the chinese/english stock developer! rom found here (dev version has root built in) - after that flash TWRP via an app like flashify (play store) - flash Xiaomi.eu within TWRP
i chose the 1. Variant and did only BOOT TWRP (fastboot boot .....) and did not permanently flash it at this time - so i could make a nandroid backup of the complete stock ROM - including the stock recovery first ! If you go this way too - do a backup of the ESF partition too because this one contains your IMEI and MAC Adress infos - can help to have this backup in the hand if something fails. If you have an OTG cable you can directly backup to an external USB Stick (must be FAT32 formatted !). I found this was the best solution for me before permanently flashing any other ROM.
Be aware that if you boot TWRP (temporarily or permanent flashed version) the touch sometimes simply does not work (in a few cases the power button did not work too). Solution: wait two or three minutes until the touch begins to work.... i used the TWRP (DEV Variant of the recovery) found here. Because the touch begins to work a little faster (sometimes it works instant).
since the last 2 weeks i stick with the sMIUI ROM (its a "slimmed" Xiaomi.eu ROM) you can cook your individual slimmed variant here. And you can read a little about it here.
Hope this helps you....
Click to expand...
Click to collapse
Thank you for your response just 1 thing I do not understand, is there a difference between the developer rom and the international 1 I mentioned? and when you say I can flash it using the the updater app to flash the dev rom (it sounds easier to me + safer) do you know how to do this? (is it this : "You can also use Mi PC Suite to flash the ROM "?)
YES the Rom you posted is a "Custom Rom" and is not officially (Xiaomi). Thats why the website says:
Unofficial International MIUI / Xiaomi Phone Support
the original (official) Xiaomi Rom - Stable and Developer - for Mi4c is only available in Chinese and english language and is translated by the community Xiaomi.eu and optimized (removed chinese apps that wouldn't work for you anyway)
How to install stock android 6.0 on Mi 4c?
I am getting an Mi4c, straight from China, but don't want the heavy MIUI lagging the performance. I would like to intstall the stock android. How can I do it? Also :-
1. Will the edge tap and other features work outside of MIUI?
2. Will Google play services be installed alongwith the stock android ROM?
I'm newbie to the rooting scene......please be little comprehensive in explanation :angel:
Cheers!!
drevankar said:
I am getting an Mi4c, straight from China, but don't want the heavy MIUI lagging the performance. I would like to intstall the stock android. How can I do it? Also :-
1. Will the edge tap and other features work outside of MIUI?
2. Will Google play services be installed alongwith the stock android ROM?
I'm newbie to the rooting scene......please be little comprehensive in explanation :angel:
Cheers!!
Click to expand...
Click to collapse
As far as i know there's no announcement for android marshmallow update for the Mi4c yet. Neither for Miui nor for CyanogenMod (CM).
... I guess CM is what you meant with "stock android".
There's just an unofficial build for CM and I guess as long it's not official there won't be edge tap support for the device.
And you have to flash google apps by yourself.
The reseller ROM they ship with 77.00.44 is total trash. I chose to keep the Chinese dev ROM as there are several Mi apps I like to use in conjunction with Gapps. It is playing very nice with my battery now.
Okay so here's the info to the best of my knowledge,
Phone Model : Moto G 3rd Gen (XT1550, dual sim, 2gb RAM, 16gb ROM, India)
Bootloader Status : Unlocked
Root Status : Rooted
Recovery : Stock
ROM : Stock ROM 5.1.1
I've been running the stock Recovery & ROM with high hopes of getting an official OTA Marshamallow update.
To truly customize the device to my liking I flashed the xposed framework (the arm version) , it worked fine and all the modules I installed worked perfectly.
I also had Device Control, Xposed Gels, and some other apps to bring my Stock ROM experience close to that of Cyanogen MOD.
When the OTA Marshmallow update started rolling in , I was unable to install the update even after successfully downloading the file numerous times. But i was so comfortable with my device and all the customization I had on my device that I decided to keep using my customized Stock ROM.
4 months later (now) the lack of a gyro in this device and my eagerness to get into VR headsets has left me with no choice but to sell it and get another phone. So i needed it in a sale worthy condition, without the customization and with the Marshmallow update installed.
I uninstalled the xposed framework and all the modules but was still unable to install the OTA update.
So i figured i'd install CyanogenMOD with TWRP custom recovery.
I have done this for quiet a lot of my friends and am fairly used to the steps involved. I use the " minimalADB fastboot " kit and my device on fastboot to flash recovery. For some reason i was not able to flash the lastest TWRP image (twrp-osprey-3.0.0-r2.img ) for the device nor was i able to boot from it :crying:. The fastboot command prompt on my PC would show success but the devices would not restart into the custom recovery like it is supposed to, but the device would stay at the fastboot mode and kept restarting everytime i selected the recovery mode option.
I had an older image (twrp-osprey-2.8.7-r3.img ) which i couldn't flash either but i was able to boot into TWRP with this image. From here i tried installing the latest CM12.1 nightly available (cm-12.1-20160227-NIGHTLY-osprey.zip) as soon as i swiped the device would just reboot, i tried this numerous times and with other nightly builds as well.
In haste and frustration i wiped the cache/dalvik , internal storage and system through TWRP , thinking that changes made in the quest of customizing my device were causing this hindrance. I had no OS now. I went over trying to flash TWRP and CM12.1 many times again with the same issues.
I came about a thread on How to " Fastboot Flash Moto G (3rd Gen) Factory Firmware Images " (http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750) & used this firmware image " Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7 ". Still no progress.
The bootloader unlocked warning has come back (i flashed a stock MOTO logo there earlier) which keeps flashing on my screen again and again , no booting into OS or anything else. Not even an error. As if there is no OS installed.
I have gone about the procedure in the above thread a couple of times, with no success and the same problem.
Is there any reason why i'm unable to flash a custom recovery or ROM ??? What am i missing???
Please help i'm stuck, pulling my hair out with no phone and completely frustrated.
Thanks in advance.
Did you check your build no for stock ROM?
samirza692 said:
Did you check your build no for stock ROM?
Click to expand...
Click to collapse
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
ashrith.s said:
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
Click to expand...
Click to collapse
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
samirza692 said:
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
Click to expand...
Click to collapse
the link provided is the exact same link from where I flashed a stock rom before.
build number for stock rom??? am i missing something???
all i see is the model variant (xt1550 is my phone)
RAM specification (mine is 2gb)
and the region (mine is retails asia | india )
so i went with the following firmware
Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7
where does the build number come into the equation???
Please lemme know if im doing something wrong. Thanks for the replies.
So I've successfully flashed twrp-osprey-2.8.7-r3.img to my device and I've been able to boot into twrp. The touchscreen doesn't seem to respond though. It asks to swipe to begin and I'm stuck again.
I had the screen replaced a couple of days ago.
Could it be a faulty screen or a software issue?
P.S. I have not been able to flash any version of twrp after the above mentioned version (v 3.0.0 is the latest stable version) but the ones prior are flashable.
Hey, contact me via PM and il do my best to help you in this.
therealduff1 said:
Hey, contact me via PM and il do my best to help you in this.
Click to expand...
Click to collapse
Is not big issue
Is it still possible to boot back into the OS? If it is, check if you have OEM unlocking enabled, since you're on stock ROM, it might be gotten unchecked after unlocking your bootloader because that's what happened with me. If you do t wether or not that was checked, you're at a dead end and there's nothing you can do. You can try paying someone to fix it, i.e., Motorola.
RO2T - Stock, SELinux Permissive Kernel For Samsung SM-G550FY (On5)
How to install + root on LL 5.1.1:
Enable USB Debugging & OEM Unlock from Settings > Developer Options.
Flash kernel, recovery via ODIN.
Install SuperSU from recovery.
Click thanks, and enjoy!
Note: The TWRP is actually from SM-J200G (j2lte) which shares the same chipset (Exynos 3475), with RO2T kernel & device-tree from stock kernel. I didn't test all features, but the SuperSU installation just did work as it should. Use at your own risk.
Download:
Kernel: https://www.androidfilehost.com/?fid=24499762636000430
TWRP: https://www.androidfilehost.com/?fid=24499762636000429
Sources:
Kernel: https://github.com/ro2t/o5lteswa
You saved my life
You are great. My months long research finally ended in this small post of yours. I have a samsung galaxy on5 chinese model sm-g5500 and I was trying to install gapps on it with no success. I have almost given up searching since its a rare model and there are no custom recovery or custom roms for this model available. But this twrp worked and i am able to flash gapps. Thank you very much. I had to pull the cable and battery immediately after odin shows 'pass' message otherwise it will replace the same old stock recovery after reboot. Not sure mine will be replaced after the next reboot but that doesn't matter because my job is done.
tomo444 said:
You are great. My months long research finally ended in this small post of yours. I have a samsung galaxy on5 chinese model sm-g5500 and I was trying to install gapps on it with no success. I have almost given up searching since its a rare model and there are no custom recovery or custom roms for this model available. But this twrp worked and i am able to flash gapps. Thank you very much. I had to pull the cable and battery immediately after odin shows 'pass' message otherwise it will replace the same old stock recovery after reboot. Not sure mine will be replaced after the next reboot but that doesn't matter because my job is done.
Click to expand...
Click to collapse
@tomo444, does On5 have theme center like J5?
Azhero said:
@tomo444, does On5 have theme center like J5?
Click to expand...
Click to collapse
Yes, same design
need ROOT for glaxy on5 marshmallow updated
you are really great i tried your method and succesfully rooted. but recently i updated to marshmallow. which means it is now GALAXY ON5 PRO. can u try to root thst too please, i hope you wil do it . thanks in advance
re1th said:
you are really great i tried your method and succesfully rooted. but recently i updated to marshmallow. which means it is now GALAXY ON5 PRO. can u try to root thst too please, i hope you wil do it . thanks in advance
Click to expand...
Click to collapse
see this thread: http://forum.xda-developers.com/android/development/requests-team-win-recovery-project-t3420007
join #twrp on freenode IRC and I will work with you to make Galaxy On5 TWRP official.
@vaibhavpandeyvpz, do you live in India? Does your SM-G550FY has Theme Store on 5.1.1?
I don't have the device but my colleague has one. The 5.1.1 did not have a theme store, but the 6.0.1 update does.
I also have the Galaxy on5 with MM. Will wait for a root.
cooltranier13px said:
I also have the Galaxy on5 with MM. Will wait for a root.
Click to expand...
Click to collapse
I also wait plz healp me
Nikup4253 said:
I also wait plz healp me
Click to expand...
Click to collapse
Just wait, a root will come eventually.
tomo444 said:
You are great. My months long research finally ended in this small post of yours. I have a samsung galaxy on5 chinese model sm-g5500 and I was trying to install gapps on it with no success. I have almost given up searching since its a rare model and there are no custom recovery or custom roms for this model available. But this twrp worked and i am able to flash gapps. Thank you very much. I had to pull the cable and battery immediately after odin shows 'pass' message otherwise it will replace the same old stock recovery after reboot. Not sure mine will be replaced after the next reboot but that doesn't matter because my job is done.
Click to expand...
Click to collapse
Did you install both the kernel and twrp? I also have the Chinese G5500. Thanks!
tomo444 said:
You are great. My months long research finally ended in this small post of yours. I have a samsung galaxy on5 chinese model sm-g5500 and I was trying to install gapps on it with no success. I have almost given up searching since its a rare model and there are no custom recovery or custom roms for this model available. But this twrp worked and i am able to flash gapps. Thank you very much. I had to pull the cable and battery immediately after odin shows 'pass' message otherwise it will replace the same old stock recovery after reboot. Not sure mine will be replaced after the next reboot but that doesn't matter because my job is done.
Click to expand...
Click to collapse
I'm hoping someone could help me out. I have the same problem and I don't know how to install these things on my chinese sm-g5500 but I desperately need gapps. Spent months trying to figure this out. I hope somebody can be of assistance
Thanks
Custom kernel
Please upload custom kernel for sm-g550fy 6.0.1
My ON 5 SM-G550FY is not opening
Hi,
I have flashed the kernels and twrp file through odin
But after flashing my phone is simply opening, showing the logo of galaxy on 5 and getting switched off again and it is continued.
i think I have loaded the files in wrong sections .
I loaded the kernel in BL and TWRP file in AP section.
.
please help me out
:crying::crying::crying::crying::crying:
SM-G5500 - Installing Gapps
vaibhavpandeyvpz said:
RO2T - Stock, SELinux Permissive Kernel For Samsung SM-G550FY (On5)
How to install + root on LL 5.1.1:
Enable USB Debugging & OEM Unlock from Settings > Developer Options.
Flash kernel, recovery via ODIN.
Install SuperSU from recovery.
Click thanks, and enjoy!
Note: The TWRP is actually from SM-J200G (j2lte) which shares the same chipset (Exynos 3475), with RO2T kernel & device-tree from stock kernel. I didn't test all features, but the SuperSU installation just did work as it should. Use at your own risk.
Download:
Kernel: https://www.androidfilehost.com/?fid=24499762636000430
TWRP: https://www.androidfilehost.com/?fid=24499762636000429
Sources:
Kernel: https://github.com/ro2t/o5lteswa
Click to expand...
Click to collapse
I have a SM-g5000 which I want to install Gapps on.
The Kernel file is infected by virus. Can you provide the file again here please?
Cheers,
Sathish
Are kernels as tricky as ROM's? What I'm asking is will this work for an SM-G550T?
please teach n how to install gapps on my samsung g5500 to.
---------- Post added at 07:30 AM ---------- Previous post was at 07:27 AM ----------
you should put them both in ap section.
not working on this version G5520ZCU1AQB2
@vaibhavpandeyvpz sir, I have a kind request, please build Lineage OS (with HAL3) for Samsung Galaxy ON5 Pro (SM-G550FY), Codename : o5prolte....
TWRP device tree : https://github.com/jcadduono/android..._samsung_o5lte
Kernel Source Tree :
https://github.com/jcadduono/android.../tree/twrp-6.0
Device Tree :
https://github.com/abhi2121/android-...msung-o5prolte
Attachment - build.prop and default.prop from Stock Android 6.0.1 ROM
I do not have a super fast internet connection, and I don't know how to build it....
This message is for Anyone & Everyone...
Please build Lineage Weeklies for Galaxy ON5 Pro...
<code>
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
</code>
Starting Development on Lineage 15.0. This will hopefully track my progress
Prerequisites:
TWRP
Unlock Bootloader
What Works?
- Don't Know Yet
What's broken ?
Probably Everything
Download Links
ROM:
Coming Soon
Trello:
https://trello.com/b/K9fXDV9L/lineageos-zenfone3
TWRP:
https://drive.google.com/drive/folde...zNmTmpzSWthMTQ
GAPPS:
http://opengapps.org/
Source Code:
https://github.com/LineageOS-Zenfone3
XDA:DevDB Information
Lineage 15.0, ROM for the Asus ZenFone 3
Contributors
mdigiacomi, mdigiacomi
ROM OS Version: 8.x Oreo
Based On: LineageOS
Version Information
Status: Testing
Created 2017-10-06
Last Updated 2017-10-06
Reserved for stuff
Fun Fact: Lineage 15.0 is 85,000+ source files.
Great!!!
Nice!!
Reserve hahahhaha nice
Oreo yeah :victory:
WoooW !!! Nice. Good Work !!!!!
Hello,
Do you think in this new version the "roaming bug" will be fixed ?
I have tried all custom roms available (lineage 14.1, ViperOS and RR) and any is working for data in roaming.
Niteshakee said:
Hello,
Do you think in this new version the "roaming bug" will be fixed ?
I have tried all custom roms available (lineage 14.1, ViperOS and RR) and any is working for data in roaming.
Click to expand...
Click to collapse
To solve data roaming issues you just have to flash the latest stock rom using the stock recovery, start it up, then reinstall your custom rom of choice. Backup your data first!
At least this has worked for me with LineageOS 14.1 (using the stock rom version "WW-14.2020.1708.56").
I've had a hard time figuring this out - I even compiled the ROM myself, trying anything I could imagine to solve this.
By flashing the stock rom properly all the special firmware partitions the phone has get updated too - the bug is in one of them, not the rom itself.
A custom rom installation normally doesn't touch those partitions.
planet9 said:
To solve data roaming issues you just have to flash the latest stock rom using the stock recovery, start it up, then reinstall your custom rom of choice. Backup your data first!
At least this has worked for me with LineageOS 14.1 (using the stock rom version "WW-14.2020.1708.56").
I've had a hard time figuring this out - I even compiled the ROM myself, trying anything I could imagine to solve this.
By flashing the stock rom properly all the special firmware partitions the phone has get updated too - the bug is in one of them, not the rom itself.
A custom rom installation normally doesn't touch those partitions.
Click to expand...
Click to collapse
Thanks a lot.
It's true I upgraded from stock 6.0.1 to lineage 7.1.2
Now i flashed back to latest stock (7.0) but with twrp recovery: it's work fine ( i have only a weird message about dm-verify on boot.)
So if now if I flash lineage with twrp you think the bug disappear ?
Niteshakee said:
Thanks a lot.
It's true I upgraded from stock 6.0.1 to lineage 7.1.2
Now i flashed back to latest stock (7.0) but with twrp recovery: it's work fine ( i have only a weird message about dm-verify on boot.)
So if now if I flash lineage with twrp you think the bug disappear ?
Click to expand...
Click to collapse
I'm not sure if TWRP updated those partitions so it's possible it doesn't work...
I think you should reflash the latest stock rom with the right stock recovery, then reinstall the latest TWRP and Lineage.
planet9 said:
I'm not sure if TWRP updated those partitions so it's possible it doesn't work...
I think you should reflash the latest stock rom with the right stock recovery, then reinstall the latest TWRP and Lineage.
Click to expand...
Click to collapse
Yes right , i am doing his right now :good:
Hello,
you mention the "data" issue on roaming. Do you mean to unlock Band 20?
I have a ZE520KL TW version and rooted it, now I try to make Band 20 working,
but without success. Should i try LineageOS15.0 and will it help or not at all?
Thank you.
Does this work on the ZC520TL X008D? I don't mind testing I just want to make sure it doesn't brick my phone before a blind flash.
Please make rom for ZC551KL. We haven't a custom rom or kernel. i'm so unhappy.
Is the project stopped? No new activity on trello
Any development for Zenfone 3 Laser ? I'm tired it's problems and system.
MoNgoLHİMİK said:
Any development for Zenfone 3 Laser ? I'm tired it's problems and system.
Click to expand...
Click to collapse
oreo
OreoBooyah said:
oreo
Click to expand...
Click to collapse
Asus's firmware or Custom Firmware ? If Asus's firmware , i don't want. Me and A lot of Z3 Laser users need Custom Firmware.
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*/
Working :
Basic twrp features
partially dual boot (different rom can be boot on both slots but still share same userdata, recommend to use fastboot method)
Decryption only support for fbev2 rom (example is some older rom, and kyasu lineageos)
otg / sdcard
Issues / Notes :
vibration is really wonky (which only happened on twrp, not orange fox) not quite fix, but it's stable enough to confirm
you might need to reflash rom "once" after you boot into recovery (flash twrp > boot to twrp > reboot to system (you'll see system corrupt) then reflash same rom that you currently using (via fastboot or twrp if rom support), after that it'll be fine. only on custom rom, stock is fine)
doesn't works with kyasu lineage due to using device model as ota assert (different than twrp ota assert, which is pdx206) fixed in latest build
doesn't support stock, due to different decryption key
ext4 only, no erofs and other models for now (1 ii and pro might release later, busy working new device tree for kumano)
format data, before flashing any rom (unless you doing a dirty flash)
For Stock users, use THIS TWRP instread this one
Big thanks :
most users on telegram for testing
christopher, for send me the device
clfbbn for kernel source
skkk (sekaiacg) for base device tree
Download : Link
device tree :
https://github.com/lolipuru/twrp_sony_pdx206
https://github.com/lolipuru/kernel_sony_sm8250
donation :
contact me via pm due to paypal is no longer able to receive money here
Nice work dude finally some development
I tested and it works on kyasu lineageos...
Nightmare_19 said:
I tested and it works on kyasu lineageos...
Click to expand...
Click to collapse
OTA probably won't work
The Xperia5ii PDX206 doesn't have an official LineageOS, so OTAs don't do much.
Nightmare_19 said:
I tested and it works on kyasu lineageos...
Click to expand...
Click to collapse
there's some problem on some roms for missing ota assert (tested on ricedroid), but if it works. no problem
Cannot install .zip files, neither slot A nor B work.
Nightmare_19 said:
Cannot install .zip files, neither slot A nor B work.
Click to expand...
Click to collapse
lineageos zip?
if lineageos zip, no it don't works. (different ota name)
Can install in au(Japan) version?
rifzan said:
Can install in au(Japan) version?
Click to expand...
Click to collapse
none of my tester (including me) have au devices, but if custom rom works then twrp should be fine
Sorry, but I didn't understand with which ROM(s) and version does this TWRP works.
And any OrangeFox would possibly be developed?
Well, thqnks for your replies
Yoannjap said:
And any OrangeFox would possibly be developed?
Well, thqnks for your replies
Click to expand...
Click to collapse
join xperia group on telegram you will find what you need there
Yoannjap said:
Sorry, but I didn't understand with which ROM(s) and version does this TWRP works.
Click to expand...
Click to collapse
tl;dr
- twrp works on android 12 (but decryption doesn't works on stock)
- twrp can't install lineageos (due to different device target, mine use pdx206 and lineage uase xq-as72)
(we're already discussed about device ota on dev group, so i'll use pdx206 for now, more custom rom in future will use pdx206 as target device)
Ok then, I am a real noob, I don't understand what does mean "PDX206".
I don't understand what you mean saying ‘due to different device target, mine use pdx206 and lineage uase xq-as72’.
To me, the XQ-AS72 is the code of the South Asian variant of Xperia 5 ii, whereas XQ-AS62/52/42 other variants.
Whereas PDX206 is just a codename meaning Xperia 5 ii (whatever variant of XQ-ASXX it is) used by I dunno who.
Am I wrong?
Yoannjap said:
Ok then, I am a real noob, I don't understand what does mean "PDX206".
I don't understand what you mean saying ‘due to different device target, mine use pdx206 and lineage uase xq-as72’.
To me, the XQ-AS72 is the code of the South Asian variant of Xperia 5 ii, whereas XQ-AS62/52/42 other variants.
Whereas PDX206 is just a codename meaning Xperia 5 ii (whatever variant of XQ-ASXX it is) used by I dunno who.
Am I wrong?
Click to expand...
Click to collapse
it's ota assert (in this case, target_device) that custom rom is set when flashing (to avoid flashing into wrong device)
lineage has been set for xq-as72 as default (don't confuse with device variants, ota assert or target_device doesn't affect with device variant that you use)
and twrp have been set to pdx206 (which is device codename for 5ii) so that's main reasons why it can't flash lineageos (but you can still access data normally)
Ok
Thank you loipuru, I got it now.
update,
- add xq-xx72 for lineageos flashing
the rest like /oem (for japanese variant) ltalabel and ta will come out later