Related
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9500 (S4). Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'as i9000' for giving me the stock recovery and stock boot.img. As you can see, it works:
Acuap said:
Hey! I can confirm that it works flawlessly on i9500. No Bricks, instalation went smooth, boots to CWM without problems. Gonna post some more details later. See ya!
Click to expand...
Click to collapse
This has not been tested by me but is reported to work, but is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided CWM and the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #2: http://d-h.st/jca
Stock Recovery: http://d-h.st/1OW
Changelog:
Code:
[I][U]Experimental #2[/U][/I]
Mount partitions fix
Backup / restore directories fixed^
Now with touch
[I][U]Experimental #1[/U][/I]
Public release
Thank you. I have always preferred to use CWM for custom recovery. By chance, are you planning to release a i9505 version of CWM. I'm sure one will surface as soon as the official phone release or as soon as the forum splits, but I thought I would ask just in case. Again, thank you.
scott14719 said:
Thank you. I have always preferred to use CWM for custom recovery. By chance, are you planning to release a i9505 version of CWM. I'm sure one will surface as soon as the official phone release or as soon as the forum splits, but I thought I would ask just in case. Again, thank you.
Click to expand...
Click to collapse
Yeah I can build for it too. I just require the stock recovery img and thr stock boot.img
After trying TWRP i don't want to come back to CWM anymore.
Thanks! Gonna try it today and give you info if this works!
emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9500 (S4). Thankyou to 'as i9000' for giving me the stock recovery and stock boot.img
This has not been tested by me and is extremely experimental. I hold no responsibility for
any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
Anyways I have provided CWM and the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #1: http://d-h.st/MWE
Stock Recovery: http://d-h.st/1OW
Click to expand...
Click to collapse
Can i add your recovery in my tool?
Inviato dal mio GT-I9070 con Tapatalk 2
Hey! I can confirm that it works flawlessly on i9500. No Bricks, instalation went smooth, boots to CWM without problems. Gonna post some more details later. See ya!
sorg said:
After trying TWRP i don't want to come back to CWM anymore.
Click to expand...
Click to collapse
how long until TWRP is released for the S4 after it's released?
I've always used CWM or CWM-based, so this time I'm going to try TWRP
Ill build that too. after CWM is fixed completely.
KINGbabasula said:
Can i add your recovery in my tool?
Inviato dal mio GT-I9070 con Tapatalk 2
Click to expand...
Click to collapse
sure
PLUG313 said:
how long until TWRP is released for the S4 after it's released?
I've always used CWM or CWM-based, so this time I'm going to try TWRP
Click to expand...
Click to collapse
TWRP is opensource. Technically, SGS4 is not much different from SGS3 (from TWRP point of view). So, it won't be a problem to compile for those who already has SGS4 and has experience with compilation.
sorg said:
TWRP is opensource. Technically, SGS4 is not much different from SGS3 (from TWRP point of view). So, it won't be a problem to compile for those who already has SGS4 and has experience with compilation.
Click to expand...
Click to collapse
I dont think so. I have compiled twrp before many times and it has never worked like that for me. A device tree needs to be set up for the i9500 which im working on to compile twrp (maybe im wrong here)
CWM works flawlessly
If any i9505 user or Korean galaxy s4 user reads this. Please post your devices stock recovery.img and stock boot.img. so thst I can provide CWM for you as well
Experimental #2 released. Now more reliable with backup / restore
emwno said:
I dont think so. I have compiled twrp before many times and it has never worked like that for me. A device tree needs to be set up for the i9500 which im working on to compile twrp (maybe im wrong here)
Click to expand...
Click to collapse
Only very basic device setup required for TWRP. Can try some existing device with the same display resolution and then tweak some parameters.
I will try it by myself when i will get SGS4.
sorg said:
Only very basic device setup required for TWRP. Can try some existing device with the same display resolution and then tweak some parameters.
I will try it by myself when i will get SGS4.
Click to expand...
Click to collapse
I have setup the tree for both building source roms and twrp recovery. Tho, the device tree for roms is incomplete, you can find it here: https://github.com/emwno/android_device_samsung_ja3g . And as for the twrp, I cant build it as ill need to sync source code again. (wiped some directories accidentally)
who have galaxy S4 ???
PM me please
emwno said:
I have setup the tree for both building source roms and twrp recovery. Tho, the device tree for roms is incomplete, you can find it here: https://github.com/emwno/android_device_samsung_ja3g . And as for the twrp, I cant build it as ill need to sync source code again. (wiped some directories accidentally)
Click to expand...
Click to collapse
For SGSIII i build just TWRP binary, not whole recovery image. I like to make my own custom ramfs. I don't use exfat_fuse. I use native samsung kernel modules with simple modification of TWRP to let it think it uses FAT volume. Also i use sdcard binary to mount /sdcard as it mounted in android to avoid files access rights mess. That's why i get only TWRP binary linked statically (instead of dynamically).
I use CM9 source tree. When i got first patches for SGSIII TWRP - they were for CM9. So I continue to use CM9 since there are absolutely no reason to switch to CM10.x in terms of recovery building.
Because my recovery requires some amount of manual work and many tries, i cannot make it without having device in hands. So, i will wait for SGS4.
If there won't be SGS4 tree in CM, then i'm going to use SGSIII's one with adjusted resolution. Everything else should be the same as in SGSIII, IMHO.
sorg said:
For SGSIII i build just TWRP binary, not whole recovery image. I like to make my own custom ramfs. I don't use exfat_fuse. I use native samsung kernel modules with simple modification of TWRP to let it think it uses FAT volume. Also i use sdcard binary to mount /sdcard as it mounted in android to avoid files access rights mess. That's why i get only TWRP binary linked statically (instead of dynamically).
I use CM9 source tree. When i got first patches for SGSIII TWRP - they were for CM9. So I continue to use CM9 since there are absolutely no reason to switch to CM10.x in terms of recovery building.
Because my recovery requires some amount of manual work and many tries, i cannot make it without having device in hands. So, i will wait for SGS4.
If there won't be SGS4 tree in CM, then i'm going to use SGSIII's one with adjusted resolution. Everything else should be the same as in SGSIII, IMHO.
Click to expand...
Click to collapse
I should have thought of that. ... anyways I set up one with the twrp flags. Tried building on a 32bit system but failed to do so. If you want, I can send you everything you will need
Will it support extfat?
Because if extfat is the default file system on a S4,there is no point without it.
... And don't give me no license BS. M$ already got my cash when I put my 649€ on the electronic stores counter.
Sent from my GT I9300
TWRP 3.1.1.1 for OREO
Beta version
https://drive.google.com/file/d/1W-m-8DNZM3n7RUrhmjyPxSISuRhhyghS/view
boot into the fastboot and flash it with a command
"fastboot flash recovery_ramdisk_a twrp_8.img"
Finaly!!! Thank you!!!
A stupid general question, what is the advantage/difference between fastboot flash recovery and fastboot flash recovery_ramdisk ?
Many thanks
h9_EU said:
A stupid general question, what is the advantage/difference between fastboot flash recovery and fastboot flash recovery_ramdisk ?
Many thanks
Click to expand...
Click to collapse
No advantage, it's just the name of the recovery partition now on Oreo.
My question @gaguga : does this TWRP decrypt "data"? Thx.
thx for the hint, so for me it seems that oreo is the best now on Honor 9 because u have root, twrp and capacitive buttons+flash right?
h9_EU said:
A stupid general question, what is the advantage/difference between fastboot flash recovery and fastboot flash recovery_ramdisk ?
Many thanks
Click to expand...
Click to collapse
Well, you try the old way and see if it works or not
On the Oreo, the names of the sections have changed accordingly and the firmware paths
FlyingMachete said:
No advantage, it's just the name of the recovery partition now on Oreo.
My question @gaguga : does this TWRP decrypt "data"? Thx.
Click to expand...
Click to collapse
The date has not figured it out yet. It is not available for backup and so on.
4r44444 said:
Finaly!!! Thank you!!!
Click to expand...
Click to collapse
Unfortunately there is nothing to "finally!" about here. This TWRP brings nothing more than the temporary one provided by @OldDroid in his guide to install Oreo... Still not decrypting data partition, still not able to do backups, etc... Cute colors, pretty buttons though. :laugh:
is the Honor 9 such an unimportant device that community support doesnt get picked up? The Honor 8 is officially on the twrp.me site list of supported phones.
h9_EU said:
is the Honor 9 such an unimportant device that community support doesnt get picked up? The Honor 8 is officially on the twrp.me site list of supported phones.
Click to expand...
Click to collapse
Most definitely yeh...
Oh, the lack of support for Honor 9 is killing me! I already soft-bricked 2 devices (bootloop) and the solution should be easy but with Orea changing most of the partitions and TWRP not supporting that yet, I'm just stuck and waiting.
I was hoping this update would bring at least USB support but thanks for the interface though.
Some update? Also about the OTA Oreo for L09-C432?
There is a tested and working root without buttons and camera flash bugs?
I hope to see an update that'll have TWRP recognized by ABD through USB, installing updates suck without this!
For someone may getting too curious and want to try, this version broke my Chinese model STF-AL00.
The navigation bar stop working and so do the flashlight, simply restore the stock recovery will not fix it.
huggingboar said:
For someone may getting too curious and want to try, this version broke my Chinese model STF-AL00.
The navigation bar stop working and so do the flashlight, simply restore the stock recovery will not fix it.
Click to expand...
Click to collapse
With which firmware version number did you used this twrp ?
oslo83 said:
With which firmware version number did you used this twrp ?
Click to expand...
Click to collapse
stf-al00 8.0.0.338(c00)
Could we get TWRP 3.2.1, please? It gets rid of many errors such as createTarFork() errors.
overflyer said:
Could we get TWRP 3.2.1, please? It gets rid of many errors such as createTarFork() errors.
Click to expand...
Click to collapse
I can't wait for this one, too, but Honor 9's support hasn't been the most impressive so far, so I wouldn't have high hopes to see it soon. However, I hope it shocks me and comes out soon.
Barrytoo said:
I can't wait for this one, too, but Honor 9's support hasn't been the most impressive so far, so I wouldn't have high hopes to see it soon. However, I hope it shocks me and comes out soon.
Click to expand...
Click to collapse
I'm working on getting encrypt support.
zxz0O0 said:
I'm working on getting encrypt support.
Click to expand...
Click to collapse
That's good news! I can't wait to see some magic.
Thanks & keep it up!
Hello all,
I understand that TWRP on our devices is built on the Nougat kernel (hence why we can't boot with it) because the touch-screen doesn't work in TWRP when building it with the Oreo kernel (and presumably the Pie kernel -- I don't know if anyone has tried).
However, even if it still has to be built from the Nougat kernel like the current version of TWRP we are all using, could someone who has the skills and knowledge build the latest 3.2.3-1 version, which was just released a few days ago for the Pixels, for our Essentials? It has the capability to unencrypt data in Pie, regardless if you have a lockscreen pattern, pin, or password (along with many other new features and fixes since 3.2.1-0 was released), so it would finally no longer be necessary to delete all fingerprints and lockscreen pattern/pin/password before going into TWRP and then having to restore them all back after leaving TWRP and then teaching all apps the changed fingerprints.
Much, much thanks in advance to anyone who can do this!! I know that anyone who knows how to build a ROM could build TWRP in almost no time at all.
Thanks again,
Chris
and if the new TWRP can flash Magisk to both slots we wont need stock kernel when rooting. Magisk 17.1 has the ability to flash to both slots, but current TWRP patches only active slot when flashing Magisk zip.
supposedly some devs are working on it. Seems like it'll be a while
https://forum.xda-developers.com/showpost.php?p=77421949&postcount=16
Not to jump too far ahead, but a Developer and friend I am working with wants to build an updated TWRP, especially now that Pie is out, we could use those Treble and Pie fixes.... He is also working on a ROM, but we are at the early stages, and he has an Essential and I got mine today. He was finishing up on another Project at the moment, now that I received my Essential we can get things going and work our way, all the way to Official Perhaps? Time will tell...
AndroidDevices said:
Not to jump too far ahead, but a Developer and friend I am working with wants to build an updated TWRP, especially now that Pie is out, we could use those Treble and Pie fixes.... He is also working on a ROM, but we are at the early stages, and he has an Essential and I got mine today. He was finishing up on another Project at the moment, now that I received my Essential we can get things going and work our way, all the way to Official Perhaps? Time will tell...
Click to expand...
Click to collapse
Simply awesome to hear that! Seriously looking forward to what you guys release in the future!!!
starcms said:
Simply awesome to hear that! Seriously looking forward to what you guys release in the future!!!
Click to expand...
Click to collapse
I am hoping we get started on TWRP this weekend. My friend is adamant about getting us a new Recovery or an update one at the very least, but i believe TWRP is the 1st thing on our to do list.... :good: With September breaking our current, outdated Recovery, made it a Priority....
Those of you who came to the channel, we thank you for your support!
Telegram Essential PH-1 Dev Group : https://t.me/EssentialPH1DEV
By the way, we have another Mata Dev working with us!
AndroidDevices said:
I am hoping we get started on TWRP this weekend. My friend is adamant about getting us a new Recovery or an update one at the very least, but i believe TWRP is the 1st thing on our to do list.... :good: With September breaking our current, outdated Recovery, made it a Priority....
Those of you who came to the channel, we thank you for your support!
Telegram Essential PH-1 Dev Group : https://t.me/EssentialPH1DEV
By the way, we have another Mata Dev working with us!
Click to expand...
Click to collapse
Things are worse than I thought. I didn't use TWRP to root the September release. What exactly did September break on the outdated TWRP we currently have available?
Thanks again in advance for getting us Mata users an updated TWRP!!
starcms said:
Things are worse than I thought. I didn't use TWRP to root the September release. What exactly did September break on the outdated TWRP we currently have available?
Thanks again in advance for getting us Mata users an updated TWRP!!
Click to expand...
Click to collapse
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
AndroidDevices said:
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
Click to expand...
Click to collapse
That's bizarre. I thought that was specifically the reason TWRP for the Essential is built on a Nougat kernel, so that the touchscreen would work in TWRP. I was told if it was built on the Oreo kernel (this was before Pie was released), so that we could boot with TWRP installed, the touchscreen wouldn't work in TWRP.
I don't know how the September update (or any ROM) could stop the touchscreen from working in the existing, old TWRP version we have. I thought you were going to say it couldn't mount /system or /data or something to that effect with September. I'll have to try it myself and see.
Regardless, still really looking forward to what you and your team come up with! It'll be great to have an updated TWRP version for the first time in a year. And being able for it to unencrypt Pie (and possibly being able to boot with it installed like on the Pixels) will be a Godsend.
starcms said:
That's bizarre. I thought that was specifically the reason TWRP for the Essential is built on a Nougat kernel, so that the touchscreen would work in TWRP. I was told if it was built on the Oreo kernel (this was before Pie was released), so that we could boot with TWRP installed, the touchscreen wouldn't work in TWRP.
I don't know how the September update (or any ROM) could stop the touchscreen from working in the existing, old TWRP version we have. I thought you were going to say it couldn't mount /system or /data or something to that effect with September. I'll have to try it myself and see.
Regardless, still really looking forward to what you and your team come up with! It'll be great to have an updated TWRP version for the first time in a year. And being able for it to unencrypt Pie (and possibly being able to boot with it installed like on the Pixels) will be a Godsend.
Click to expand...
Click to collapse
In order to have TWRP boot and have it installed, we actually need a TWRP.img to Fastboot Boot into Recovery. At that point you would flash your ROM and then there is a 2nd TWRP required that is a zip file called an installer. This is what allows you to boot into recovery from either the hardware power and volume button, or a standard Reboot to Recovery without having to use Fastboot. So again, (2) TWRP files are needed, a boot img and a zip installer. 1st we need to get the boot img working properly and then the installer.
Also, I was informed there is another DEV working on TWRP. Hopefully we can put 2 and 2 together and produce the proper Recovery.
I will update this thread as things get accomplished, and then hopefully all said and done and we can create an Unofficial TWRP thread.
I hoped, now that prices came down on this phone people would jump on it and development picking up. But even the current state seems slow.
I wish we had a nice working TWRP already, and as far as a ROM being mentioned, oh how we need some ROMS that don't have Gapps preinstalled.
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
hmm
AndroidDevices said:
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
Click to expand...
Click to collapse
It was not a TWRP issue but an issue with the Sept update. Some files were left out and the flash left the touch screen dead. I had the issue and just had to flash tow additional files that Essential issued in their flash download.
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
Can you choose options or screen frozen? Because we know it boots and options can be chosen with the use of a OTG mouse...
*edit*
Remember guys, TWRP11.img still works for the August Factory Image as well as anything before August...It is only the September Factory Image is the only build at this time, that TWRP is frozen FYI
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
Awesome! So glad this is gaining some traction! What kernel/boot image is this based on? Nougat, Oreo, or Pie?
Do you have an alpha or beta 3.2.3 TWRP boot image that you could share?
Also, just FYI, 3.2.3-1 was the version made specifically for the Pixels that was just released about a week ago to allow lockscreen pin/pattern/password decryption for Pie.
...
Here's the reason why touch stopped working in TWRP. In the September update, the hyp and rpm partitions were updated for the first time ever. This is what broke touch in TWRP. However, to confuse the issue, those who downloaded the September fastboot package when it first came out lost touch in Android, but kept touch in TWRP because Essential failed to update the two partitions in the fastboot download package (the updated partitions were initially only in the actual OTA and the OTA download package). Essential has since fixed their mistake and put the new hyp and rpm partitions in the fastboot download package.
You can't simply go and flash the older versions of those partitions, because even though it will fix touch in TWRP, it will break touch in the September (and newer) versions of Android.
More info here: https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
starcms said:
Here's the reason why touch stopped working in TWRP. In the September update, the hyp and rpm partitions were updated for the first time ever. This is what broke touch in TWRP. However, to confuse the issue, those who downloaded the September fastboot package when it first came out lost touch in Android, but kept touch in TWRP because Essential failed to update the two partitions in the fastboot download package (the updated partitions were initially only in the actual OTA and the OTA download package). Essential has since fixed their mistake and put the new hyp and rpm partitions in the fastboot download package.
You can't simply go and flash the older versions of those partitions, because even though it will fix touch in TWRP, it will break touch in the September (and newer) versions of Android.
More info here: https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
Click to expand...
Click to collapse
So basically twrp needs to be repackaged with the updated hyp and rpm partitions and we should be home free?
stryver said:
So basically twrp needs to be repackaged with the updated hyp and rpm partitions and we should be home free?
Click to expand...
Click to collapse
TWRP needs to be made compatible with the new hyp and rpm partitions. TWRP (or any recovery) lives in the ramdisk in the boot image/partition (kernel). So I don't think it can simply be repackaged with hyp and rpm which are two completely separate partitions.
Project Treble For Xperia X Compact
Based on Sony Open Devices
I am not responsible for bricked devices, dead SD cards,.
Big thanks to Sjll member and his tuto to go treble
Suitable for F5321, A-ONLY GSI ROM
Required files:
[SODP Kernel version]
All necessary files
[OEM-File]
Download Link
[SYSTEM-File]
Tested with some system gsi files, these work properly :
Pixel experience
/e/
POSP
ArrowOS
[SYSTEM-File WITH FixZygote installed via twrp]
Android Q developer preview
Find all GSI system image here and here
How to go Treble ?
First: Flash recovery
Code:
fastboot flash recovery < Path of recovery.img >
Second: Flash boot image
Code:
fastboot flash boot < Path of boot.img >
Third: Flash vendor file
Code:
fastboot flash cache < Path of vendor.img >
Fourth: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fifth: Flash a GSI compatible System image (arm64 A-ONLY) and boot !
Code:
fastboot flash system < Path of GSI-System.img >
Look here first for questions resolving Xperia X thread
Source Codes
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-05-09
Last Updated 2020-05-23
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
Normally I set the selinux to permissive so no need to apply the permissiver patch
PS : sometimes it goes into bootloop but if you reboot it starts like a charm (test that with POSP 10)
PS2 : Mobile network does not work with Q roms, if you success to make it work please share
PS3 : POSP Pie works fine
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
bioshp said:
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
Click to expand...
Click to collapse
You can get twrp as recovery but do not wipe cache, as vendor img is flashed in it
Good news that /e/ is working correctly, I was about to try to build a e variant on Chippa's build.
I do have one question. Really new to trebble.
If we wanna root it, we apply usual procedure*? flash the root zip(magisk) in recovery
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Xperia UI GSI also does not start for me. What could be?
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Try to flash userdata also
bioshp said:
Xperia UI GSI also does not start for me. What could be?
Click to expand...
Click to collapse
Q or Pie ROM ?
maluus said:
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
Click to expand...
Click to collapse
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
betacrypt said:
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
Click to expand...
Click to collapse
To avoid SELinux policy errors and fail to boot
nervousapp said:
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
Click to expand...
Click to collapse
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
I flashed /e/ and it's pretty stable and smooth but my device is overheating when charging and even when it's idle and the display is off. I'm getting severe battery drain from it.
EDIT: Wiping all the partitions and flashing from scratch seems to have done the trick.
I've been using Arrow OS and it's pretty stable and smooth so far. Comes with GApps built-in and Jan 2020 security patch:
https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/
maluus said:
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
Click to expand...
Click to collapse
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
mister-13x said:
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
Click to expand...
Click to collapse
I didn't anything extraordinary follow the steps in the first post. (Since android version would change I formatted data) use erfanoabdis' unofficial Q gsi which you can find a link at phhusson' gsi images link list. (You can also find the link to phussons list in the first post)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.
This tutorial assumes you understand how to use adb and fastboot.
Your device’s bootloader has to be unlocked.
IMPORTANT NOTE: It seems some users need to flash a vbmeta image file provided by Google in order to boot and user the Custom Kernel. If you find yourself in a situation were you are not able to boot, please flash the attached vbmeta img along with the Kernel and if still bootlooping share the last_kmsg to determine what's driving the issue.
Download >> Link
Kernel Sources >>> Source
Join the Telegram Group for additional support - Link
Thanks to @afaneh92
11/08/2022 - Update
Upstream to 5.10.83
Based on S908EXXU2BVJA, SM-S908E_13_Opensource
You can now download file from Kernel Source page.
Only Test on SM-S908E for now but should work on all snap dragon android 13 should also should work on android 12 but not tested.
For permissive kernel you can go to the download page.
----------------------------------------------------------
Android 12 only..
07/25/2022 - Update
Upstream to 5.10.84
Added support for all S22 snapdragon devices.
Only tested on SM-S901/906/908 E (b0q, r0q, g0q)
07/11/2022 - Initial Set up
Upstream to 5.10.83
TTL Support
Low Memory Killer for Android
Wakelock Blocker enabled
Enabled more TCPs
Only tested on SM-S908E should work on SM-S9080 as well.
..
Awesome! I look forward to this project. Hopefully I can test it soon.
Any details I can share to confirm if the SM-S908N would work before flashing?
nonomancer said:
Awesome! I look forward to this project. Hopefully I can test it soon.
Any details I can share to confirm if the SM-S908N would work before flashing?
Click to expand...
Click to collapse
I only tired it on SM-S908E you can try it if it doesn't work just flash your boot.img
I look forward to see where this will progress. Oh, I miss the days of custom kernels and custom ROMS so much! I don't think I've ever enjoyed any phone more than I enjoyed the days of the Note 2, then life got busier. Nexus 5 was great too with custom ROMS, and the Pixel 2. These days it seems all the security measures by manufacturers (and it's understandable), is preventing a lot of crazy independent development.
Any
bklyn_syed said:
07/11/2022 - Initial Set up
Upstream to 5.10.83
TTL Support
Low Memory Killer for Android
Wakelock Blocker enabled
Enabled more TCPs
Only tested on SM-S908E should work on SM-S9080 as well.
Click to expand...
Click to collapse
Chance you can do a kernel for S901E?
skinza said:
Any
Chance you can do a kernel for S901E?
Click to expand...
Click to collapse
Try it, it should work since its gki kernel
bklyn_syed said:
Try it, it should work since its gki kernel
Click to expand...
Click to collapse
Do you think it'd be possible to flash the zip with the Franco kernel manager app?
skinza said:
Do you think it'd be possible to flash the zip with the Franco kernel manager app?
Click to expand...
Click to collapse
Thats what I use make sure you flash vbmeta disabler before flashing custom kernel
bklyn_syed said:
Thats what I use make sure you flash vbmeta disabler before flashing custom kernel
Click to expand...
Click to collapse
Awesome, one last thing, the vbmeta disabler, flash with Odin in user data same as when flashing it for twrp? Or fastboot?
skinza said:
Awesome, one last thing, the vbmeta disabler, flash with Odin in user data same as when flashing it for twrp? Or fastboot?
Click to expand...
Click to collapse
AP in odin
Doesn't work, says unsupported device, aborting
skinza said:
Doesn't work, says unsupported device, aborting
Click to expand...
Click to collapse
Ok ill fix the script and upload the file for test
Try this
skinza said:
Doesn't work, says unsupported device, aborting
Click to expand...
Click to collapse
Try the zip I uploaded
Thank you for your kernel mate, im Not rooted yet but will try in a few weeks when im on holydays
Goku1992 said:
Thank you for your kernel mate, im Not rooted yet but will try in a few weeks when im on holydays
Click to expand...
Click to collapse
Ok
bklyn_syed said:
Try this
Click to expand...
Click to collapse
Yep worked didn't need vbmeta disabler, just flashed the zip
skinza said:
Yep worked didn't need vbmeta disabler, just flashed the zip
Click to expand...
Click to collapse
Can you screenshot software information I want to make sure it works