^^This
Probably NO its an old device but i still like it so there is still a change of it and maybe CM13.0 too it just need time.
Working on Lineage OS 13.0 Rom for this device with TWRP 3.0.2.0 but new CM 12.1 got already new version so maybe i can try to grab 3.1.1 twrp source and compile for our device but dont know if it will work
Tried not possible our devices have too much modified TWRP that the branch don't wanna to merge.
I would greatly recommend checking galaxy nexus TWRP thread, where they also had a lot of problems with 3.1.0.0.
Situation is remarkably kind of similar to ours: they are stuck to 3.0 kernel, and they haven't QCOM hardware (they have support for nougat though)
I had ported it to our device but it doesn't compile because of sdk it showed errors always about sdk i have it on my GitHub branch 7.1 I may create new branch and try again because you are not the only one who want latest stuff if there were moreeeeeee time and more people we might be able to Port android 7.1 but this device is not much used anymore there is lot less devs. But if anybody wants to try download android 6.0 source add our vendors and all our device stuff and add my TWRP and try to build only TWRP without android you might get successful build
Sent from my nypon using XDA Labs
---------- Post added at 07:19 PM ---------- Previous post was at 07:16 PM ----------
In few days i will create new thread In p general and will post there stuff about my porting diary maybe more devs will add and will be help me
Sent from my nypon using XDA Labs
---------- Post added at 07:30 PM ---------- Previous post was at 07:19 PM ----------
And I don't think sdk problems are releated to my porting since android 6.0 don't compile on 5.1.1 but it does on 6.0 so I don't know guys about that
Sent from my nypon using XDA Labs
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
mirhl said:
I would greatly recommend checking galaxy nexus TWRP thread, where they also had a lot of problems with 3.1.0.0.
Situation is remarkably kind of similar to ours: they are stuck to 3.0 kernel, and they haven't QCOM hardware (they have support for nougat though)
Click to expand...
Click to collapse
Also would you help me post some stuff if you have this device ?
Sent from my nypon using XDA Labs
Sorry, I don't.
mirhl said:
Sorry, I don't.
Click to expand...
Click to collapse
Oh ok Then i will try to port it on my own. But thanks still.
I have done it i build TWRP 3.1.1 for xperia P its on my LineageOS thread but its build from omni tree so it will not boot CM roms yet im going to build on CM tree somehow(CM doesnt support TWRP officialy omni do so thats why i build it first in omni).
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
It wasn't booting because it was built using omni tree now I compiled using cm tree and its working and yes I'm writing with adrianDC about FOTAkernel I want to do that one mainly now and then official support.
---------- Post added at 11:01 PM ---------- Previous post was at 10:55 PM ----------
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
But idk if we don't need to make the fota partition or does Nypon have it already ?
---------- Post added at 11:07 PM ---------- Previous post was at 11:01 PM ----------
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
And I meant kernel cannot boot the ROM because it was built for omni ROM.
Haxk20 said:
But idk if we don't need to make the fota partition or does Nypon have it already ?
Click to expand...
Click to collapse
Every sony phone should have it.
That was exactly the secret of the smart idea.
Supposedly, I think at least on XU that should correspond to /dev/block/mmcblk0p13
mirhl said:
Every sony phone should have it.
That was exactly the secret of the smart idea.
Supposedly, I think at least on XU that should correspond to /dev/block/mmcblk0p13
Click to expand...
Click to collapse
And how can we check which one it is on XP ?
After I know which partition it is I can start working on it.
First add it to TWRP as FOTA (just to addone line )
Then well edit few files in device tree and then well we would have fota partition used by recovery yayyy.
It shouldn't be too hard to do .
I just need to know what files should I edit from adrianDC I will write him.
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Garcia98 said:
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Click to expand...
Click to collapse
Yes I know all of this but still thanks and the benefit here is that with the new method I can request official support for xperia P from twrp team.
Cause if I must build a boot.IMG still when new commit comes in twrp I would have a ton of boot.IMG and users will not use them cause they would have to flash every new version. And also if users use omni and I build cm boot.IMG they cannot boot to system.
If we add fota then users could update twrp just from twrp app ifimwrong about this please correct me.
Also why is not our FOTA recognized as recovery then ?
---------- Post added at 10:00 PM ---------- Previous post was at 09:53 PM ----------
Garcia98 said:
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Click to expand...
Click to collapse
And also which partition is FOTA on xperia P ?
Haxk20 said:
Yes I know all of this but still thanks and the benefit here is that with the new method I can request official support for xperia P from twrp team.
Cause if I must build a boot.IMG still when new commit comes in twrp I would have a ton of boot.IMG and users will not use them cause they would have to flash every new version. And also if users use omni and I build cm boot.IMG they cannot boot to system.
If we add fota then users could update twrp just from twrp app ifimwrong about this please correct me.
Also why is not our FOTA recognized as recovery then ?
---------- Post added at 10:00 PM ---------- Previous post was at 09:53 PM ----------
And also which partition is FOTA on xperia P ?
Click to expand...
Click to collapse
The FOTA partition is the 13, the same as Xperia U, Go and Sola.
Our bootloader doesn't flag the FOTA partition as a recovery partition, that's why fastboot can't access to it, and only Sony could solve that through a firmware update.
I don't really know how the TWRP official app works, but if they accept devices with boot.img based recoveries the current method would be fine. If the recovery ramdisk has to be on a separate image then you would need to use the newer method, ask them about that.
Also it doesn't matter whether you're building TWRP on Omni or CM sources, the recovery ramdisk will be the same and that's everything that matters, you can then use that recovery ramdisk in a boot.img for CM, Omni or whatever ROM you want.
Garcia98 said:
The FOTA partition is the 13, the same as Xperia U, Go and Sola.
Our bootloader doesn't flag the FOTA partition as a recovery partition, that's why fastboot can't access to it, and only Sony could solve that through a firmware update.
I don't really know how the TWRP official app works, but if they accept devices with boot.img based recoveries the current method would be fine. If the recovery ramdisk has to be on a separate image then you would need to use the newer method, ask them about that.
Also it doesn't matter whether you're building TWRP on Omni or CM sources, the recovery ramdisk will be the same and that's everything that matters, you can then use that recovery ramdisk in a boot.img for CM, Omni or whatever ROM you want.
Click to expand...
Click to collapse
Yes recoveryramdisk is same of course but the boot.img itself isn't and tested it doesn't boot with omni one.
I will lookup if current method will work but I don't think so
Haxk20 said:
Yes recoveryramdisk is same of course but the boot.img itself isn't and tested it doesn't boot with omni one.
I will lookup if current method will work but I don't think so
Click to expand...
Click to collapse
You have to take only the recovery ramdisk you get after compiling the recovery and swap it with the old recovery ramdisk in the target boot.img, check AGONTUK script, you can throw the boot.img you get after compiling the recovery to the recycle bin.
Garcia98 said:
You have to take only the recovery ramdisk you get after compiling the recovery and swap it with the old recovery ramdisk in the target boot.img, check AGONTUK script, you can throw the boot.img you get after compiling the recovery to the recycle bin.
Click to expand...
Click to collapse
Hi well the link to download doesn't work and well now im going to makethefota working.
Haxk20 said:
Hi well the link to download doesn't work and well now im going to makethefota working.
Click to expand...
Click to collapse
Check the attached files of this post
Related
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
34.3.A.0.244 - 7.1.1 - 09 NOV 2017 update
F5122 IS AT https://mega.nz/#F!DEQykYjL!Vux2m1_Rug9hg9B4_q0ifw
F5121 .. https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ (THANKs @eagleeyetom )
both f5121/5122 folders have 1 kernel image,
FLASH THE ROM
FLASH THE KERNEL,
FLASH TWRP,
BOOT IN TO TWRP .
FLASH MAGISK or SUPERSU, VIA FLASHABLE ZIP
BOOT THE DEVICE
IF YOU HAVE FLASHED MAGIK THEN INSTALL MAGIS MANAGER
MAGISK POST https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
CHAINFIRE SUPERSU ZIPs LATEST AT https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
PREVIOUS KERNELS
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
https://forum.xda-developers.com/xperia-x/development/rooted-kernels-f5121-f5122-34-3-0-238-t3683968
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
https://forum.xda-developers.com/xp...ted-kernels-f5121-f5122-34-3-0-224-8-t3669793
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5121-f5122-34-3-0-217-7-t3654368
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
siggi77 said:
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
Click to expand...
Click to collapse
on https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ
the F5121_34.3.A.0.244_su.img is the kernel
just flash and your device will wakup ROOTED.
twrp 3.1.1 problem
on my 64 GB xperia X F5122
1. after flashing ROM if
2. I flash twrp 3.1.1 it will
3. make my system partition 40GB and i get only 20gb workable
I tried many things but flashing recovery via adb always create this problem and if i BOOT the device before going in to the partition , sony stockrom makes internal storage encrypted which then twrp3.1.1 is unable to read
plz help
@serajr @shoey63 @munjeni
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
siggi77 said:
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
Click to expand...
Click to collapse
i am sorry,
i have fixed it
please check again
thank you
Hi, great
thx for the new package
Siggi
clean kernel image is drm fixed??
kloroform said:
clean kernel image is drm fixed??
Click to expand...
Click to collapse
yes sir, it is,
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
xxarigattoxx said:
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
Click to expand...
Click to collapse
the guide is here
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
also twrp3.1.1 works best at 32gb variant by giving 20gb workable and putting systemparittion to 12gb
however it does the SAME with 46gb variant and give only 20gb workable and put system partition 40 gb
thats why for 64gb variants i don't recomend using twrp3.1.1
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Jomoteck said:
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Click to expand...
Click to collapse
once you flash the modified kernel with supersu then there is no need for twrp, simply boot your device and it will wakeup rooted.
however if you wana use magisk and your device is 64gb then i highly recommend you to do this
1. flash rom
2. flash the modified kernel
3. boot the device and go thru sony setup , give google account and let it sync
4. switch off mobile after 15 or so mins
5. flash twrp3.1.1 suzu (given in the mega link, in the OT)
6. HOLD power and VOLUME DOWN BUTTON till PINK led comes on sonylogo and you are taken to twrp, keep system readonly and flash magisk ( via otg or if you had it in your sd card prior) ( at this point you may flash other zips also, if there are any)
7. twrp may give you error such as... cannot mount internal storage etc, just ignore.
8. after flashing, switchoff mobile, and boot it into system.
9. for safty purposes, you can erase twrp by connecting device in fastboot mode and executing following command
Code:
fastboot erase recovery
now you can ask me why i let you boot your device first. normally its unprecedented.
the reason i explain here
https://forum.xda-developers.com/showpost.php?p=74573987&postcount=121
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
nova001 said:
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
Click to expand...
Click to collapse
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
YasuHamed said:
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
Click to expand...
Click to collapse
thats oke, but we cant dowload anywhere? only xperifirm ?
nova001 said:
thats oke, but we cant dowload anywhere? only xperifirm ?
Click to expand...
Click to collapse
Xperifirm is the best
Other servers i cant guarantee
I was able to flash rom, flash kernel, flash root and boot the phone and was able to use it.
PROBLEM:
- It heats up during use.(FIXED) constant mobile data was the cause..
- Everytime I lock the screen my mobile data turns on when I unlock the SCREEN. (FIXED) disable find my device as administrator.
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
cyanides13 said:
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
Click to expand...
Click to collapse
Yes it works I use it actually.
Hello everyone ! I have a big issue :
I installed the following rom OpenKirin's AOSP Treble Oreo For Honor 9. But, the capacity buttons didn't work at all.
So I went to the following topic [Oreo] [TWRP 3.2.1-0] [0.3] [+Capacitive fix].
This topic said that I "just" had to flash the kernel to get my capacitive buttons working again, but now, my phone can't boot at all. It keeps on restarting and shows me the honor disclaimer then the honor blue starting screen and it loops.
So can you guys tell me is there any fix or is my phone a brick, knowing that I still can access the fastboot and TWRP?
Thanks
You flash a B360's kernel over a build which is not B360 ; So bootloops.
What stock firmware were you on before flashing AOSP system ?
---------- Post added at 23:36 ---------- Previous post was at 23:34 ----------
Just flash back the stock kernel from your firmware version before AOSP.
oslo83 said:
You flash a B360's kernel over a build which is not B360 ; So bootloops.
What stock firmware were you on before flashing AOSP system ?
---------- Post added at 23:36 ---------- Previous post was at 23:34 ----------
Just flash back the stock kernel from your firmware version before AOSP.
Click to expand...
Click to collapse
Thank you for being that fast, I had the STF-L09C432B365 firmware.
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
oslo83 said:
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
Click to expand...
Click to collapse
OK, so once it's extracted I just have to do a ./fastboot flash kernel <my_extracted_stock_kernel>.img right?
I'll try it, once I finish to install my VM (I have a mac ><)
dandas said:
OK, so once it's extracted I just have to do a ./fastboot flash kernel <my_extracted_stock_kernel>.img right?
I'll try it, once I finish to install my VM (I have a mac ><)
Click to expand...
Click to collapse
Well it didn't work :/
Code:
./fastboot flash kernel KERNEL.img
does not work ? What does it output ?
(By the way adb and fastboot are working just fine on osx without need of a VM for those.)
oslo83 said:
So extract the stock kernel img (ramdisk) from the Update.app file included in the file update.zip from this firmware.
Use a windows app called HuaweiUpdateExtractor
---------- Post added at 23:43 ---------- Previous post was at 23:41 ----------
Then wait for a B365 kernel that fixes buttons.
(Or go back to stock B360 for applying the b360 kernel fix)
Click to expand...
Click to collapse
Really? I have made a thread on Guides with all stock EMUI8 kernels, ramdisks and recoveries for easy access to people but i guess no one noticed... why do i bother...
JBolho said:
Really? I have made a thread on Guides with all stock EMUI8 kernels, ramdisks and recoveries for easy access to people but i guess no one noticed... why do i bother...
Click to expand...
Click to collapse
No need to be offended mate, I tried all your files with the exact same commands, and none is working on my device
oslo said:
Code:
./fastboot flash kernel KERNEL.img
does not work ? What does it output ?
(By the way adb and fastboot are working just fine on osx without need of a VM for those.)
Click to expand...
Click to collapse
I did the same command, here's the log :
Code:
➜ platform-tools ./fastboot flash kernel ~/foo/KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.650s]
writing 'kernel'...
OKAY [ 0.262s]
I still have a bootloop... And thanks for the VM advice, but you told me to use HuaweiUpdateExtractor which only works on Windows, so I still had to use a VM. Anyway, my previous message wasn't clear about that point, sorry for the misunderstanding.
Do you have any other suggestion? I start to doubt about my original build number, do you know if I can cat the original stock kernel with the adb shell, or if I can get out of the loop with some others kernel and ramdisks imgs?
Thank you guys
You'll need stock kernel of your actual build.
So it's seems you were not STF-L09C432B365 kernel as you still are bootlooping.
Try with stock kernels from :
STF-L09C432B364
STF-L09C432B363
STF-L09C432B362
STF-L09C432B360
You could try with images provided by JBolho : https://androidfilehost.com/?w=files&flid=266088
oslo83 said:
You'll need stock kernel of your actual build.
So it's seems you were not STF-L09C432B365 kernel as you still are bootlooping.
Try with stock kernels from :
STF-L09C432B364
STF-L09C432B363
STF-L09C432B362
STF-L09C432B360
You could try with images provided by JBolho : https://androidfilehost.com/?w=files&flid=266088
Click to expand...
Click to collapse
As I said, I tried them already, but I'll try again. BTW the B360_kernel.img is missing inside JBolho's repo
Maybe he messed something when uploading them.
Maybe you were not on one of those.
Ok, is there any other version I can try? Or maybe my process is wrong, I do the same commands, and in the same order as Jbolho describes in his post.
Except for the recovery flash, does it matter? Because since that I don't have the erecovery anymore, before I still had it in combination with the twrp.
Thanks
oslo83 said:
Maybe he messed something when uploading them.
Maybe you were not on one of those.
Click to expand...
Click to collapse
No, I didn't mess anything, checked them already, all in the same folder on AFH and properly uploaded.
And I never stated that the B360 fixed kernel was in my repo, I point it to zxz0O0's thread.
What I would recommend is to flash recovery and ramdisk too, not just kernel (corresponding to previously installed firmware of course)
@dandas Please note that recovery & erecovery are two differents mode.
help !!
did you find a solution for this problem
i have the same problem after flashing kernel to my honor 9 STF-AL10 please help me
kalilou23000 said:
did you find a solution for this problem
i have the same problem after flashing kernel to my honor 9 STF-AL10 please help me
Click to expand...
Click to collapse
What version did you flash specifically, on what firmware?
help honor STF-AL10
my phone was on
STF-AL10C00B172 the capacitive botton wont work when i google the problem xda team have solved the problem with flashing kernel
when i have flashed kernel the phone bootloop and reboot into e-recovery mode
i tried to download emergency software from erecovery with wifi but it didnt work ''failed ''
when i trie to flash the honor with his one version again onlly system.img flashed seccessfully via fastboot mode with cmd
other img wont pass it saise failed
i have tried other ways like flashing stock rom 5GB via upgrade mode with sd card but the flash failed and it write failed to install software
in my case i dont have money to activate dc unlocker and unbrick my device with dc-phoenix so i downloaded a board software '' xml file '' for my honor 9 and installed acm and handset driver but the device when i install acm device it is connected on com 11 huawei mobile connect Fake acm interface i cant flash my honor 9 via IDT tool what should i do !!!
kalilou23000 said:
my phone was on
STF-AL10C00B172 the capacitive botton wont work when i google the problem xda team have solved the problem with flashing kernel
when i have flashed kernel the phone bootloop and reboot into e-recovery mode
i tried to download emergency software from erecovery with wifi but it didnt work ''failed ''
when i trie to flash the honor with his one version again onlly system.img flashed seccessfully via fastboot mode with cmd
other img wont pass it saise failed
i have tried other ways like flashing stock rom 5GB via upgrade mode with sd card but the flash failed and it write failed to install software
in my case i dont have money to activate dc unlocker and unbrick my device with dc-phoenix so i downloaded a board software '' xml file '' for my honor 9 and installed acm and handset driver but the device when i install acm device it is connected on com 11 huawei mobile connect Fake acm interface i cant flash my honor 9 via IDT tool what should i do !!!
Click to expand...
Click to collapse
That's confusing to say the least. You flashed the kernel on B172 firmware??? That's Nougat firmware! No wonder you screwed everything up. Don't mess with board software and stuff like that, you have to install the firmware with dload method probably.
Code:
*** Disclamer * 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.
DISCONTINUED, MOVED TO BUILDING CRDROID AND AICP ANDROID PIE
Known Issues
No audio through speaker, currently trying to find a fix.
ROM ResurrectionRemix-O-v6.2.1-20181202
TWRP DOWNLOAD
INSTALLATION
I am assuming that most of you already know how to flash custom ROMS.
Boot into TWRP Recovery Flash TWRP 3.2.3-0 image
Wipe the System, Cache and Data.
Flash ROM Zipfile
Flash the GApps (optional, needed for Google Playstore to work).
(Optional) Flash root zipfile Majisk/SuperSU.
Wipe ART/Dalvik cache.
Reboot
Flashing the ROM itself the boot time is around 5 mins, if you flash Gapps + Majisk or SuperSU expect the first boot time to increase to about 7-8 mins
XDA:DevDB Information
SM-T350 ResurrectionRemix Oreo, ROM for the Samsung Galaxy Tab A series
Contributors
nubianprince
Source Code: https://github.com/Nubianprince/gt58wifi_rr
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Nougat
Version Information
Status: Beta
Beta Release Date: 2018-12-02
Created 2018-12-02
Last Updated 2019-03-23
Reserved
reserved
Did you guys just use the open source code of lineage 15.1 that didn't have working speaker. So is basically the same rom with different name. I'm still going to flash it for kicks but doesn't seem kinda pointless? Twrp should be better I'll let you know I'm assuming you forgot to mention gapps.
Funny cause the guy that built that took the source codes from someone else and that's why the speaker never got fixed because you don't know how to build or compile your just copying.
I got the rom up and running i was on marshmallow firmware and it worked fine. It takes awhile to boot up give it 10 minutes then when you start up it's really slow and lagging but after a couple reboots it works fine. I do say it's resremix tons of customization I haven't used any yet. I still think it's based off the lineage codes but it's different very different setup so it's worth installing if the damn speaker could get fixed it would be great. Bluetooth speaker or headphones work camera works I think the camera on this tablet is **** but works lol. Thanks for the rom guys. Twrp also seems to be working fine which is great because that's been a pain before.
Good job
Enviado desde mi SM-T320 mediante Tapatalk
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
joejunior253 said:
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
Click to expand...
Click to collapse
After you flashed the new twrp 3.2.3 did you reboot back into recovery? You can't just flash it then flash the rom you have to reboot in to recovery again to have it take effect. Also then follow all other instructions what instructions did you follow just a little more detail. Also what room or system were you on before?
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
Device?
Firmware?
TWRP version?
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
joejunior253 said:
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
Click to expand...
Click to collapse
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
nubianprince said:
Device?
Firmware?
TWRP version?
Click to expand...
Click to collapse
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
joejunior253 said:
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
Click to expand...
Click to collapse
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
joejunior253 said:
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
Click to expand...
Click to collapse
Are you not English speaking? I said you had a efs error that's what I thought. You should have flashed the last version of nougat you had working when the error happened boot into stock and turned on USB debugging. Then you flash twrp either t355 3.1.1 or 3.2.3 are the best. I guess flash 3.1.1 for 355 at first then when you flash twrp on stock nougat boot into twrp and flash magisk 17.1 I'm having trouble with magisk 18 on some devices so use 17.1. Those terminal codes are tricky type them perfect or they don't work I recommend a couple times until it works. They should reset your efs partition then you reboot and flash your firmware again I'd say flash nougat again. Cause I flash marshmallow and got drk error. The firmware doesn't touch efs partition so once you screw it up your ass is grass unless you have a efs backup that works not the one from 3.2.1 twrp that screws everyone up. This is why people should not put stuff out until they have tested it. After you fix efs and can reboot then use twrp to flash twrp 3.2.3 by install image find the twrp 3.2.3 image select recovery. Flash because you can't flash Oreo with twrp 3.1.1. Then you can flash this rom.
You need root so you have to flash magisk in twrp after you flash twrp.
Try this code that will list partition blocks. Your efs should be 13. If it's not you don't have smt350 lol. Those codes work it Should say writing inode or something
ls -l /dev/block/bootdevice/by-name enter
mke2fs /dev/block/mmcblk0p13 enter
mount -w -t ext4 /dev/block/mmcblk0p13
Edit try SuperSU 2..82 sr5 beta or 2.79 sr3 because SuperSU is better for Samsung it's made to disable dm verity I think. Only up to nougat SuperSU will not work on Oreo you'll have to use magisk. The most important thing is after you flash the working stock firmware one of them will work I had this problem to only nougat q1 would work the rest didn't boot. So after I got my tablet running I flashed twrp 355 3.1.1 and went into terminal inside advance in twrp. I typed this commands and it worked it reset my efs partition my Bluetooth worked again my tablet would flash custom roms again and even downgrade back to marshmallow but I'm not recommending that. You type the first one hit enter type the second one hit enter then reboot. The firmware needs to be the same one you had when it errors if it's q5 then q5. I'm trying to help man I don't think your tablet is done I think it'll work again but it'll take some time and effort. You got this man . I always flash root first I don't think you have to because twrp already has root but I would say flash SuperSU first .
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
Read everything i ve posted I said it was efs
Dude your all over the map man
1. Flash nougat firmware the last one you had boot up in the rom
2. Flash twrp 3.1.1
3. Flash SuperSU 2.7.9 or magisk 17.1 probably should go with SuperSU 2.82 SR5 beta.
4. Mack a back up
5. Reboot into rom
6. Reboot back into twrp and type that code it fixes your efs partition and resets it. Into terminal emulator inside twrp try it to it says writing inode or something like that. Both lines.
Reboot .
7. Go back into twrp flash image in install menu find twrp 3.2.3 I'm file make sure it's a image file.
Here's a section of my first post
Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
If you can't boot into nougat go into twrp and type that code into the terminal emulator then when you get it to say writing idone or something it's working if you can't see the screen is black you have to search xda on tab a forms there's a fix a don't remember anyone please if you had twrp black screen what did you do? I've never had it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:24 PM ----------
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
No you can't flash magisk before twrp that makes no sense.
Please let me know what firmware update your trying to flash it Should be a the last one you had when you got the efs error and was able to boot into rom. That firmware only that one. No others will work I had this problem and fixed it. Also what twrp were you using when you got the efs error? Please answer it will help others to not touch it. I noticed that twrp 3.2.1 was taking down so I'm wondering did twrp 3.2.3 cause the error?
---------- Post added at 03:34 PM ---------- Previous post was at 02:36 PM ----------
Everyone did I not explain the fix right? I'm trying to learn how to help people on xda and if you guys think I didn't explain things right please let me know. I am fine with criticism so I can learn how to better help people.
liking it so far (been using for a day), i like the customization options for the UI. it took a bit in the setup thingy... it took a couple tries to get passed the "checking for update" spot. but it runs nicely now
Hi Bro., Can I flash this Rom on t355y ?
Unofficial TWRP Recovery for Moto G7 Power
(XT1955-5/ocean/supra)
I didn't want to wait any longer for an official build of TWRP for the Moto G7 Power (ocean) so I ported it over myself following these directions . So far it appears to work with little to no issue with the exception of decryption of userdata on later rom buids...
I was even able to install fastboot(ed) image to ramdisk & flash Magisk-19.3 via TWRP. Hopefully this can hold some of you off until an official build comes out.
If you guys wish to try it out I have uploaded it to my Android file host here.
Latest attempt HERE
Installation Instructions:
1. You will need to boot image via fastboot initially
Code:
fastboot boot twrp-3.3.1-0-ocean-20190904-0715.img
2. Once TWRP boots push Magisk v19.3 to /tmp/ & flash if not installed or you will bootloop
a.
Code:
adb push Magisk-v19.3.zip /tmp/
b.
Code:
adb shell
c.
Code:
twrp install /tmp/Magisk-v19.3.zip
3. Push twrp-3.3.1-0-ocean-20190904-0715.img to /tmp/
Code:
adb push twrp-3.3.1-0-ocean-20190904-0715.img /tmp/
4. Install recovery to ramdisk via fastboot(ed) TWRP
Code:
Tap Advanced > Install Recovery Ramdisk > Navigate to /tmp/twrp-3.3.1-0-ocean-20190904-0715.img
5. If Magisk is installed prior you may bootloop back to recovery
Code:
Advanced > Fix Recovery Bootloop & Reinstall Magisk
NOTE:
When providing feedback please include the build date of port, carrier, security patch, and rom build number of your G7 Power. The last two items can be found in Settings > System > About phone > tap Android version .
E.g.
20190904-0715
Metro
March 1, 2019
PCO29.114-54-2
good, step 1 is in fastboot mode, the 2,3,4 is the pc? or how can I flash
Yes 1 - 2 PC. 3-4 in TWRP. Pretty simple.
Geofferey said:
Yes 1 - 2 PC. 3-4 in TWRP. Pretty simple.
Click to expand...
Click to collapse
install very well start but not let me do anything on the mobile screen does not respond
Alexhdavila said:
install very well start but not let me do anything on the mobile screen does not respond
Click to expand...
Click to collapse
yes, but when it is installed to the device Ramboot, the screen responds then. Use this image to boot TWRP, then use it to install G's build
---------- Post added at 08:10 PM ---------- Previous post was at 07:49 PM ----------
https://drive.google.com/open?id=1n2YwMJ0CcZU5rze6ibaOM68Ox6bxPL9M
One problem i see here, is that TWRP doesn't decrypt storage when formatting.. GSI systems say it's encrypted still.. isn't it supposed to decrypt when formatting?
Scholeggo said:
One problem i see here, is that TWRP doesn't decrypt storage when formatting.. GSI systems say it's encrypted still.. isn't it supposed to decrypt when formatting?
Click to expand...
Click to collapse
The touch screen works for me when I fastboot it & it works when installed to ramdisk.
I think it worked for me when I used the format data option that requires typing yes. What GSI's are you using? I attempted to install one last night no data/wifi.
@Alexhdavila @Scholeggo
I will need more info. Does touchscreen work when booting via fastboot? Do you have a non US variant? What is output of command lsmod through adb shell in Android?
I can most likely make the screen work for you if you provide that info.
Try the latest one with date appended... Touchscreen should work.
https://drive.google.com/file/d/1Clvwof18aLCF8NQqqjvSCkNEpQAkp6tO/view?usp=sharing
Edit: ^ Touch screen works on initial boot and after for my device. Added driver /vendor/lib/modules/aw8624.ko to /sbin/load_drivers.sh. Though I'm not sure if that is a touch related device and a google of aw8624.ko returns nadda.
Geofferey said:
The touch screen works for me when I fastboot it & it works when installed to ramdisk.
I think it worked for me when I used the format data option that requires typing yes. What GSI's are you using? I attempted to install one last night no data/wifi.
@Alexhdavila @Scholeggo
I will need more info. Does touchscreen work when booting via fastboot? Do you have a non US variant? What is output of command lsmod through adb shell in Android?
I can most likely make the screen work for you if you provide that info.
Try the latest one with date appended... Touchscreen should work.
https://drive.google.com/file/d/14JN1e8OlK_sj-AgpD5i97T-vrB5STOSJ/view?usp=sharing
Click to expand...
Click to collapse
Ok, I did send logs that should indicate that decrypting does not work.. I am using Phhusson's AOSP GSI for this test. My G7 Power is 1955-5 on Metro
If you're on a gsi, go into settings and look into lock screen/security and head down to encryption and credentials, and you will see my point.
This screenshot is in fact taken from my decrypted Moto E5 plus
Scholeggo said:
If you're on a gsi, go into settings and look into lock screen/security and head down to encryption and credentials, and you will see my point.
This screenshot is in fact taken from my decrypted Moto E5 plus
Click to expand...
Click to collapse
Did you update the device to the latest release? I forget where I read but after a certain security update TWRP is no longer able to decrypt user data on some devices. I am still on the OG software that came with device (security patch March 1, 2019), no updates. When I installed magisk on this device and disabled force ecrypt/dm-verity it would no longer boot either. I have yet to try disabling force-encrypt while leaving dm-verity. For me TWRP decrypts my data perfectly when installed to ramdisk but not fastbooting. If you flash a GSI rom in my experience you will have to wipe the data and phone will pretty much force this on you with stock recovery.
Also you didn't answer my question about touch screen. In your post you said to fastboot the test-v1.img then flash mine to ramdisk. Did the touchscreen on my build not work for you when fastbooting?
Edit: Actually I didn't ask lol.
Geofferey said:
Did you update the device to the latest release? I forget where I read but after a certain security update TWRP is no longer able to decrypt user data on some devices. I am still on the OG software that came with device (security patch March 1, 2019), no updates. When I installed magisk on this device and disabled force ecrypt/dm-verity it would no longer boot either. I have yet to try disabling force-encrypt while leaving dm-verity. For me TWRP decrypts my data perfectly when installed to ramdisk but not fastbooting. If you flash a GSI rom in my experience you will have to wipe the data and phone will pretty much force this on you with stock recovery.
Also you didn't answer my question about touch screen. In your post you said to fastboot the test-v1.img then flash mine to ramdisk. Did the touchscreen on my build not work for you when fastbooting?
Edit: Actually I didn't ask lol.
Click to expand...
Click to collapse
huh.. before flashing, i was last on the August build.. and yes, i flashed it to ramdisk and did not have an effect with decrypting the device.
no, touch screen does not work when fastbooting your build.
update: with your newer build (with datestamp), touch still doesn't work on fastboot
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP. Right now my main concern is getting touch working for everyone. If you tried 20190902-1422 and touch doesn't work on fastboot I have some ideas to make it work all around. Do you have Hangouts or something so we can work faster to bring fully functional TWRP together? Since you have a device with the problem. Development via threads is slow.
Geofferey said:
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP. Right now my main concern is getting touch working for everyone. If you tried 20190902-1422 and touch doesn't work on fastboot I have some ideas to make it work all around. Do you have Hangouts or something so we can work faster to bring fully functional TWRP together? Since you have a device with the problem. Development via threads is slow.
Click to expand...
Click to collapse
No Hangouts, but what about Telegram? +561-800-8299
---------- Post added at 12:22 AM ---------- Previous post was at 12:16 AM ----------
Geofferey said:
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP.
Click to expand...
Click to collapse
ok, maybe not decrypt like that, but at least have TWRP not mess up internal storage when wiping system?
On the test-v1 I sent, it does that when wiping system alone, rebooted or not. With yours, it does that only when rebooting recovery; as long as you flash another system right after wiping, internal storage seems to be unaffected with your build.
If not decrypting the storage, it shouldn't mess up internal storage at all when wiping system
I think it's a mechanism of the device. When I flash any GSI on top of any userdata that was created by stock rom it messes up that data, most likely intentionally. That happens with 'fastboot flash system system.img' as well. Can you help me with the touch issues?
Try Me!
LATEST ATTMEPT !
Edit:
My last attempt before I say I don't know what I am doing. I've attempted to include all the kernel modules this recovery should need inside the image. There should be no need for it to load modules from /vendor/lib/modules. Hopefully this fixes the touch screen for most users when fastbooting and installing to ramdisk.
your newest build works touch functions properly
Thank you for the confirmation @OGandroid. Hopefully I can put touch to rest now and find other issues.
Geofferey said:
Thank you for the confirmation @OGandroid. Hopefully I can put touch to rest now and find other issues.
Click to expand...
Click to collapse
In my experience touch works fine booting into TWRP but once installed it's gone
I've tried flashing multiple times. Am I doing something wrong here?
Metro by T-Mobile Variant
Hey man thank you so much for your work! Just wanna triple verify tho! This will work on the metro variant? Also is it possible do you know to flash rims from the other g7 series phones?
yes I have the metropcs variant and it works fine on my device both ways booting or flashing it
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
uHeash said:
In my experience touch works fine booting into TWRP but once installed it's gone
I've tried flashing multiple times. Am I doing something wrong here?
Metro by T-Mobile Variant
Click to expand...
Click to collapse
try the newest build touch works perfectly whether booting into twrp or flashing the ramdisk
OGandroid said:
yes I have the metropcs variant and it works fine on my device both ways booting or flashing it
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
try the newest build touch works perfectly whether booting into twrp or flashing the ramdisk
Click to expand...
Click to collapse
Sick man this is awesome I've been waiting for this! Now for some rims and it'll be smooth sailing!
Custom TWRP Recovery for Nokia 4.2 codename Panther
Firmware : 136
For September Security patch
Link: https://drive.google.com/drive/folders/1tqQVK_IAQLSq2RDHhPD_p3v7IEXkAwbI?usp=sharing
Request: Unlocked bootloader
How to install:
Go to bootloader/fastboot mode:
fastboot flash boot "path to twrp.img"
Control volume to "reboot recovery mode"
Done
It no support decrypt data at the moment. So,you need format data
fix slot on sep twrp
Added a/b slot. You can flash system,boot to a or b if you want
Update link tomorrow
Good news: Tree ready for build rom
Bad news: doesnt boot???
Hello, the TWRP link above is no longer available. Can you send it to my mailbox? Thank you! Email account: [email protected]
clurs said:
Hello, the TWRP link above is no longer available. Can you send it to my mailbox? Thank you! Email account: [email protected]
Click to expand...
Click to collapse
I sended a friend request in qq,check it
Is there a way to use this on october patch?
thegamingcat13 said:
Is there a way to use this on october patch?
Click to expand...
Click to collapse
I cant test it. My computer cant backup oct patch. I think you need ask calyx for it
thinhx2 said:
I cant test it. My computer cant backup oct patch. I think you need ask calyx for it
Click to expand...
Click to collapse
Ok thank you
Hello,
I want to port TWRP to my Nokia 3.2. how did you port it? Or what's the procedure?
Thanks
s3tupw1zard said:
Hello,
I want to port TWRP to my Nokia 3.2. how did you port it? Or what's the procedure?
Thanks
Click to expand...
Click to collapse
send me boot.img of 4.2
Hi, I've uploaded the firmware here:
https://drive.google.com/file/d/1jJkDi807fagKFJ1ggzFY1Lc4TGY-llEB/view
If you don't want to download the whole firmware I'll upload the boot.img file when I'm at home on my computer.
Thanks
---------- Post added at 10:07 AM ---------- Previous post was at 09:57 AM ----------
Btw. Could you write a guide on how to Port TeamWin for Android One devices? I think it would be interesting for other people who don't have TeamWin for their Android One devices.
---------- Post added at 10:42 AM ---------- Previous post was at 10:07 AM ----------
I got the boot img from my system using dd. I packed boot_a and boot_b into a rat file
https://drive.google.com/file/d/1-DRQ_LRdEMez-Qpj2jboJsDysG5awl_b/view?usp=drivesdk
Hi,
how did you port TWRP to Nokia 4.2 ? Is there a guide on how to do this ?
bro can u please how to use the files??!!
Any news on this
Which variants of the 4.2 will this work on?
doesnt work just stuck on twrp loading
Hi everyone. I am trying to install twrp but stuck at fastboot menu.
I have unlocked bootloader, because it says device state: unlocked. Then i am trying to fastboot flash but get error. I am trying flash:raw and set_active a and b. I try boot recovery.img. no matter what I do the phone restarts, shows android logo and then go back to fastboot. Fastboot devices shows the phone. What am I missing? Wrong files, wrong order, any better guide or files to test? I am not sure what I have done also flashed a vbmedia file