Related
I just rooted my phone lenovo k4 note using golden twrp and flashed resurrection remix with open gapps. Unfortunately the gapps zip file was corrupted and I wasn't able to fix that.
So I booted my phone to the new os , took the new feeling but later realised the gapps are mandatory.
So I downloaded a new file and tried to go to twrp recovery mode. But I wasn't able to. I thought the bootloader must've locked itself up so I unlocked it again, flashed the twrp recovery IMG file with adb and booted my phone to recovery. But still twrp didn't start.
BUT THEN I SAW THAT I HAD NO INTERNAL STORAGE
Just the SD card
Later I was able to wipe the custom rom from twrp and I flashed the resurrection remix and gapps.
Still internal storage was missing. Can anybody help me please?
ParagTheGre8 said:
Later I was able to wipe the custom rom from twrp and I flashed the resurrection remix and gapps.
Still internal storage was missing. Can anybody help me please?
Click to expand...
Click to collapse
Try flashing the stock ROM, see if your storage reappears on your stock ROM.
Also, do you get any information about your internal storage in Settings>Storage on your current ROM?
I don't know if it will help, but in TWRP recovery, go in Advanced>Fix permission
I feel like the OS doesn't have permission to internal storage, in the best case it will fix your issue in the worst case it will do nothing
But safest and easiest way to fix those kinds of issues is to wipe every thing and flash official ROM
Andrew_Geo said:
Try flashing the stock ROM, see if your storage reappears on your stock ROM.
Also, do you get any information about your internal storage in Settings>Storage on your current ROM?
Click to expand...
Click to collapse
Settings>Storage just shows the is size that's is roughly around 7gb
It says 7.11gb used of 7.15gb.
It should have been 16gb
I usually have around 10 GB free internal storage
DevALT said:
I don't know if it will help, but in TWRP recovery, go in Advanced>Fix permission
I feel like the OS doesn't have permission to internal storage, in the best case it will fix your issue in the worst case it will do nothing
But safest and easiest way to fix those kinds of issues is to wipe every thing and flash official ROM
Click to expand...
Click to collapse
So I tried to go to twrp, but the same problem occurred.
It seems my phone is unable to go to recovery.
I did the one with power button and volume keys, and it tries to go to recovery but the ROM boots up.
I also used the is function of reboot to recovery but by this too the ROM boots up and not twrp
ParagTheGre8 said:
So I tried to go to twrp, but the same problem occurred.
It seems my phone is unable to go to recovery.
I did the one with power button and volume keys, and it tries to go to recovery but the ROM boots up.
I also used the is function of reboot to recovery but by this too the ROM boots up and not twrp
Click to expand...
Click to collapse
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
DevALT said:
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
Click to expand...
Click to collapse
Thanks for the help but I found what was the concern (my problem is not fully solved)
The recovery was very stubborn to just start up.
So I used the official twrp app and flash booted through my phone.
Fortunately it worked.
I wiped everything including internal storage and the storage just showed up in my pc.
I flashed the ROM and Gapps again and the problem got solved.
There just one thing now, the internal storage is there when I go to Settings>Storage but cant access through File Explorer or pc.
The apps got downloaded to the internal storage only so its not much of a problem though.
I am having the same issue.
DevALT said:
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
Click to expand...
Click to collapse
I have a huawei Gr5 KII-L21 / kiwi mobile. Initially there was 16GB internal memory now it is just showing 2GB internal memory. I flashed stock rom yet the problem is there. I tried to flash stock rom in bootloader mode from window command prompt. Is there any method to get bak my internal memory?
Hello XDA!
I am writing this thread to ask for help rooting my Samsung Galaxy J2 Pro.
I attempted to use apps such as: Framaroot, Kingroot, etc.. but so far none of them have worked and I have not been able to find a working guide on the internet of how to root my phone.
I also tried installing an unofficial version of TWRP for my phone but everytime I tried to boot into the recovery it would say "No Command" and then boot into the original recovery.
Is anyone able to help me root my phone? Can it even be done?
Any help is sincerely appreciated. Thanks!
Phone Specifications:
Samsung Galaxy J2 Pro.
SM-J250G
Android Version: 7.1.1
Bumpity Bump
Try this at your own risk
Make a backup before trying
I got root access with this method
Download stock Rom from sammobile extract and there should be 5 MD5 files extract the AP file with 7z and copied boot.img on to sdcard
Installed MagicalMmanager-7 used it to patch the boot.img to a tar file
Copied the boot image to my pc desktop then flashed the boot with odin
When I booted it back up magisk manager kept crashing so I uninstalled it and installed magiskmanager-5.23 rebooted it opened magisk and followed the prompts to update it
:good:
putzwon said:
Try this at your own risk
Make a backup before trying
I got root access with this method
Download stock Rom from sammobile extract and there should be 5 MD5 files extract the AP file with 7z and copied boot.img on to sdcard
Installed MagicalMmanager-7 used it to patch the boot.img to a tar file
Copied the boot image to my pc desktop then flashed the boot with odin
When I booted it back up magisk manager kept crashing so I uninstalled it and installed magiskmanager-5.23 rebooted it opened magisk and followed the prompts to update it
Click to expand...
Click to collapse
Hello there.
I have tried to patch my boot.img but when I put into a .tar and flash it, it doesn't flash, it's just stuck on file analysis despite being able to flash other files. Would you be able to send me a copy of your boot.img, thanks.
Kindest Regards
-Jayden
JaydenATC said:
Hello XDA!
I am writing this thread to ask for help rooting my Samsung Galaxy J2 Pro.
I attempted to use apps such as: Framaroot, Kingroot, etc.. but so far none of them have worked and I have not been able to find a working guide on the internet of how to root my phone.
I also tried installing an unofficial version of TWRP for my phone but everytime I tried to boot into the recovery it would say "No Command" and then boot into the original recovery.
Is anyone able to help me root my phone? Can it even be done?
Any help is sincerely appreciated. Thanks!
Phone Specifications:
Samsung Galaxy J2 Pro.
SM-J250G
Android Version: 7.1.1
Click to expand...
Click to collapse
Hi Jayden
I've got exactly the same problem. Have you worked this out eventually? Please help!
MC
qichen said:
Hi Jayden
I've got exactly the same problem. Have you worked this out eventually? Please help!
MC
Click to expand...
Click to collapse
Unfortunately I have not found a solution. Please notify me if you find one.
here is a copy of my boot.img after flashing this you will get a verification problem and you will have to reset your phone if it bootloops into recovery or starts to update and says no command take battery out put it back in and boot it again or boot in to odin mode and push down and boot it eventually it will boot in to recovery then factory reset it. first boot may take 5-10 minutes
my software version is J250GDXU2ARD3_J250GXSA2ARD3_XSA
putzwon said:
here is a copy of my boot.img after flashing this you will get a verification problem and you will have to reset your phone if it bootloops into recovery or starts to update and says no command take battery out put it back in and boot it again or boot in to odin mode and push down and boot it eventually it will boot in to recovery then factory reset it. first boot may take 5-10 minutes
my software version is J250GDXU2ARD3_J250GXSA2ARD3_XSA
Click to expand...
Click to collapse
Hello and thanks a lot! I flashed my boot image and now when it boots it says "Set Warranty Bit : Kernel" and an infinite booting screen.
What do I do from here? or do I need to flash the original rom?
don't worry about "Set Warranty Bit : Kernel" mine does it too here is another boot.img after i flashed this i got verification failed so i used 7z to tar userdata.img.ext4 i extracted from the AP image i got the boot.img from.
i put boot in BL and userdata in AP and flashed it. it fired up as normal and then i installed magisk apk
JaydenATC said:
Hello and thanks a lot! I flashed my boot image and now when it boots it says "Set Warranty Bit : Kernel" and an infinite booting screen.
What do I do from here? or do I need to flash the original rom?
Click to expand...
Click to collapse
Flash the original rom then flash boot and userdata as i explain in next post
Hey, sorry for the late response. Everything is working fine! I now have superuser abilities but everytime I try to flash my recovery with TWRP it just loads the stock recovery. I even tried removing certain files from the root folder to avoid the stock recovery being flashed but it hasn't worked.
Any idea? Ps. You are a life saver my man.
JaydenATC said:
Hey, sorry for the late response. Everything is working fine! I now have superuser abilities but everytime I try to flash my recovery with TWRP it just loads the stock recovery. I even tried removing certain files from the root folder to avoid the stock recovery being flashed but it hasn't worked.
Any idea? Ps. You are a life saver my man.
Click to expand...
Click to collapse
glad i could help and i don't think there is an official twrp for this device here is one i ported a couple things still don't work mtp and sideload but it's not really usable until someone ports a rom due to the data encryption which you have to format to be able to flash anything
putzwon said:
glad i could help and i don't think there is an official twrp for this device here is one i ported a couple things still don't work mtp and sideload but it's not really usable until someone ports a rom due to the data encryption which you have to format to be able to flash anything
Click to expand...
Click to collapse
Hello,
Sorry, I don't have the J250G anymore as I traded it for a J5.
Kindest Regards
Jayden
My internal storage showed I only have 8gb instead of 16gb. Is there a fix for this?
P.S. Wiping data fixes it
ok
You can extract it from the AP file from stock firmware using 7z
hey
hey everyone im just wondering but is there a kernel for this device yet or any rom ("J250G")
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
abdul_manan said:
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
Click to expand...
Click to collapse
Use micro SD card for twrp. You can't remove encryption just by factory reset. I know how to remove encryption on Nougat but that method doesn't work on Oreo. When you flashed TWRP flash SuperSU (not Magisk) then boot to system, after that boot to twrp recovery again and wipe factory reset and wipe internal storage. You have removed encryption. SuperSU needs to be updated to patch plat and non play file contexts to remove encryption on Oreo. Or someone can make flashable zip to remove encryption.
First find nb0 file for Nokia 1 and try to flash rom with OST.
SkaboXD said:
Use micro SD card for twrp. You can't remove encryption just by factory reset. I know how to remove encryption on Nougat but that method doesn't work on Oreo. When you flashed TWRP flash SuperSU (not Magisk) then boot to system, after that boot to twrp recovery again and wipe factory reset and wipe internal storage. You have removed encryption. SuperSU needs to be updated to patch plat and non play file contexts to remove encryption on Oreo. Or someone can make flashable zip to remove encryption.
First find nb0 file for Nokia 1 and try to flash rom with OST.
Click to expand...
Click to collapse
Thanks for the reply!
Can you please tell me where can I find the nb0 file of Nokia 1 with Android 8.1 Oreo Go edition TA-1047?
abdul_manan said:
Thanks for the reply!
Can you please tell me where can I find the nb0 file of Nokia 1 with Android 8.1 Oreo Go edition TA-1047?
Click to expand...
Click to collapse
currently it's not available, you need to wait someone to upload it.
Nokia1 uses MTK CPU right? If you can get the ota zip of the current update on your phone, you can extract the boot.img file then boot into download mode and type fast boot flash boot <boot.img file>
redweaver said:
Nokia1 uses MTK CPU right? If you can get the ota zip of the current update on your phone, you can extract the boot.img file then boot into download mode and type fast boot flash boot <boot.img file>
Click to expand...
Click to collapse
Can you please explain a little bit more!
How to get ota zip file? (My phone is not working as mentioned above)
Where can I get boot.img?
How to extract and where boot.img?
How to boot into download mode?
abdul_manan said:
Hi! I was trying to root Nokia 1
I flash TWRP through fastboot and it worked! But the problem was I was unable to see my files there.I think because of encryption..
So, I accidentally factory reset my phone through TWRP and then, I was unable to boot into system again..
I was stuck in TWRP
So, I go to fastboot and flash stock_recovery.IMG and after that when I reboot. I am seeing a black screen. I can feel vibration when press home key or home + volume up/down. but screen is black
Please help...
Click to expand...
Click to collapse
I'm having a kind of similar issue. I flashed twrp and now its stuck in a twrp loop. It boots only in twrp and not system. What should I do?
Ludba Amb said:
Can you please explain a little bit more!
How to get ota zip file? (My phone is not working as mentioned above)
Where can I get boot.img?
How to extract and where boot.img?
How to boot into download mode?
Click to expand...
Click to collapse
http://www.mediafire.com/file/0xgn9o0b711wcw0/Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip
Stock Rom for 1047
Download it.
Extract boot.img from that
boot into download mode/recovery
adb reboot recovery
answers to all your questions.... not the answer to fix your problem I think... But have a go.
And last but not least... Please use the search option first or google instead of asking all questions at once.
Or try to get familiar with rooting first...…
good luck buddy.
hello everyone i have nokia 1 oreo go edition i don't have any idea how to root
please help me by sending links for :
1 ) nokia 1 (ta-1047 ) TWRP
2 ) nokia 1 custom rom
3 ) nokia 1 current rom (for security)
(remenber thats only model ta-1047)
seriously i want to root it because there are many issues like multitouch screen problem or missing some system apps and also device getting hot because the memory (ram) is lagging (1gb ram is not enough to run android oreo correctly 2018 )
{PLEASE HELP}
help me please !
can you send me a twrp for nokia 1 ta-1047
i need to root my device to dowoad custom rom
MyTH30 said:
I'm having a kind of similar issue. I flashed twrp and now its stuck in a twrp loop. It boots only in twrp and not system. What should I do?
Click to expand...
Click to collapse
Same here. Seems that the decryption does not work. Better make sure your phone is not encrypted before messing with twrp (3.2.3).
Be careful
Some Nokia 1 are a TA 1060 variant number and if you flash the wrong file you are going to have further problems.
The process to root and get TWRP on the nokias Is complicated enough without everyone suggesting wrong model variants / numbers.
I guarantee someone will download the wrong file for the wrong model and come here crying.
is this the real firmware?
inkepinkje said:
http://www.mediafire.com/file/0xgn9o0b711wcw0/Nokia_1_TA-1047_MT6735_V8.1.0_180401.zip
Stock Rom for 1047
Download it.
Extract boot.img from that
boot into download mode/recovery
adb reboot recovery
answers to all your questions.... not the answer to fix your problem I think... But have a go.
And last but not least... Please use the search option first or google instead of asking all questions at once.
Or try to get familiar with rooting first...…
good luck buddy.
Click to expand...
Click to collapse
hi, i needed to know if this is the real one, they show it's mt6735 instead mt6737m, I've already downloaded a file with the similar name nd it has scatter file of mt6735, that's while in the sp flash tool,i don't see all of the partitions being detected to flash
Hey i am facing the same issue but i didn't flash any other recovery mode my phone Nokia 1 TA-1056 am getting black screen and only feel the vibration when i press power key and when i put my phone on charging then its shows the display and boot into recovery mode directly can anyone help me how i can overcome this issue
i downloaded the custom recovery for t20 (TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02) from gethub "i cant attach the link because of the forums rules"
then flashed it using fastboot , but then the tablet didn't boot into normal mode but i was getting the boot mode selection when i hold the (power + volume up) which gave me access to recovery mode and fastboot mode
the problem is that this custom recovery had issues with the touch screen and was basically not usable .
so i switched the phone into fastboot and i flashed the patched boot image that was working before but the tablet still didn't boot into normal mode , then i flashed the stock recovery image and now every thing gone .
the tablet has no options to boot into fastboot or recovery anymore.
basically the tablets boots and i get the teclast logo then the image of the broken android with a "no command" on screen and nothing else
i tried holding the volume up and plug in the usb-c cable but i got the same broken droid
holding volume up and power doesn't give the options for boot modes anymore
i would appreciate any help a this moment , thanks
hany20006 said:
i would appreciate any help a this moment , thanks
Click to expand...
Click to collapse
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
ViAlexSt said:
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
Click to expand...
Click to collapse
thanks for the reply my version is E2
i tried flashing the stock but i keep getting an error that the preloader file is not valid . can u upload yours so i can try with it
hany20006 said:
my version is E2
Click to expand...
Click to collapse
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2: Chinese storage or my Y.Disk
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
ViAlexSt said:
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2:
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
Click to expand...
Click to collapse
thank you very much for providing the y.disk link , i spent the whole yesterday searching for a way to download from baidu without luck.
i managed to flash the stock software (using format all +download) and it worked and now the tablet is up and running (unfortunately its chines ) i changed the language but there is bits here and there with chines still i cant complain.
there is no recovery image with this tablet , do u think i should flash the twrp recovery even if it has touch issues.
i cant thank u enough for your help
have a nice day
hany20006 said:
do u think i should flash the twrp recovery even if it has touch issues
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
ViAlexSt said:
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
Click to expand...
Click to collapse
yeah i just rooted the device and then flashed the recovery using the Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek (TWRP 3.2.1-0)
the touch screen is till having issues , but i guess i have to use mouse as you said
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Draiter said:
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Click to expand...
Click to collapse
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
hany20006 said:
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
Click to expand...
Click to collapse
Hey thanks for the quick reply, I will give it a go
Sent from my SM-G935F using Tapatalk
Got the boot.img flashed and recovery flashed (Phil's), but cannot do a full backup in recovery, cannot Mount data.
Have you been able to do a full backup?
Sent from my SM-G935F using Tapatalk
Draiter said:
cannot Mount data
Click to expand...
Click to collapse
Standard phenomenon for Nougat/Oreo: to mount a partition /date, must first format it. With loss of user data!
Some TWRP editions don't require this, /data mounted.
Hello.
Thanks ViAlexSt for the help, but I´m still having problems with root
, I try with (MTK) Auto TWRP recovery porter and with MTK Auto Philz recovery porter, with success only with TWRP.
Wiith Philz only get into recovery, when go to the OS the screen freeze with Teclast Logo in red.
With TRWP have an error, not able to mound device.
Is no possible install zip or create a backup.
Any idea??
I have a T20 T2E1
Thanks
I format with SPFlashtool with format+flash option, but not work, no backup, no any wipe.
Still with message Unable to mount parition.
I will try with an older version OF TWRP.
Some screenshots.
Thanks
https://photos.app.goo.gl/qwmLqnhxVk8vRmWA8
https://photos.app.goo.gl/VP5vJCDC7HaDpgaB8
AWLanzarote said:
Still with message Unable to mount parition.
Click to expand...
Click to collapse
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
ViAlexSt said:
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
Click to expand...
Click to collapse
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
AWLanzarote said:
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
Click to expand...
Click to collapse
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
toxstoxs said:
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
Click to expand...
Click to collapse
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
AWLanzarote said:
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
Click to expand...
Click to collapse
I went troght that step by step guide but :
1) into Pre requirement steps, i made a NVRAM backup with SP Tool.
step 2 is not so interesting to me as the tablet is new so no personal data are saved.
point 3 : How suppose to make a nandroid backup if no TWRP is intalled???
then.. i suppose that it mean to INSTALL a TWRP and just after make a nandroid backup right?
but...
just after ulock the bootloader and reaching step by step the point 7 and 8 of the guide,
after the command "fastboot boot recovery.img" the device reboot and go in permanent loop.
No way to access the recovery.
is there something that i may check? just once i been able to enter the twrp and the main problem were the impossibilty to access and format the /data partition so, no factory reset were possible and obviously no bbot as well (permanent boot loop).
Im not use adb tools, im only use sp fash tool.
I do it like this.
1 flash the downloaded Rom from Teclast with SP flash tool, to get all fresh.
2 Enable usb debug and oem unlock
3 copy in your device the stock boot.img from the folder firmware from the zip downloaded from Teclast,
4 in your device install the app Majisk manager and use it to patch your original boot.img
5 copy into sd the files magisk.zip, No verity opt encrypt.zip,
6 with sp flash tool flash the patched boot.img and the downloaded TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02"]twrp renamed to recovery.img ”this was the only one trwp which works on my T20”https://github.com/TwrpBuilderTests/android_device_teclast_t20/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02
7 reboot in recovery with TWRP and install magisk.zip and no verity opt encrypt.zip
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
BootLoader needs to be Unlocked and of course Usual T&C's apply. Use at your own risk don't blame me if you brick your device or lose your valuable data etc etc.
So what's different about this ROM??
Ok so I have been working on this for quite sometime during the little free time I have.
The ROM is my own preferences only and it may not be to everyone's tastes so you're quite welcome to take it, leave it, add to it, strip it, mod it, etc, etc.
The ROM ditches the not so useful stuff of Sony's but retains what I consider the good stuff like Music Album and the Camera.
Where possible I have replaced the Sony stuff with Google's Stuff which receive regular updates and keep the Rom looking fresh.
The trick to this ROM was finding a good balance without breaking anything in the process which I think I have now achieved.
This is a list of the visible apps installed, there are quite a few none visible Sony & MediaTek apps still installed that relate to settings functions and some background stuff.
Google Apps:
Clock
Calculator
Contacts
Calendar
Chrome
Drive
Files
GMail
Hangouts
Maps
Messages
Phone
Photos
Play Store
Wallpapers
YouTube
Sony Apps:
Album (Please disable this in /settings/app It will constantly search for other apps I removed otherwise. Use the pre-installed Google Photos app instead)
Camera
Music
Radio
Swiftkey (Left this in because I like it)
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Flashing InstructionsThe ROM is packaged as a TWRP Backup containing system, oem, boot and recovery (TWRP)
First you will need to install this TWRP HERE which has oem partition support and others too.
1. Install the TWRP Recovery above.
2. Boot to the new TWRP and backup oem, system and boot then move it to a safe place off device or to and external sdcard. Same goes for anything you value like pictures, music, etc, etc
3. Once you have Backed Up everything FORMAT your /data partition using TWRP. Wipe > Format Data (type yes to confirm)
When that's done choose Wipe > Advanced Wipe and select Dalvik / ART Cache and Cache after that from the TWRP menu choose Reboot and select Recovery
4. When back in recovery swipe to allow then do a quick Backup of any small partition like boot or recovery. This will just create the folders on your clean data partition unless your default backup is external sdcard.
5. Now extract/unpack the downloaded ROM from HERE and move the folder SonyXA-Android-One to TWRP/BACKUPS/Sony_XA/
6. Once done go to TWRP Menu and choose Restore and select SonyXA-Android-One
7. Once done go to the Reboot Menu and Choose Power OFF
8. Wait a few Mins and power on normally.
First boot can take a while but if you see the boot animation start everything should be fine so go have a brew while you wait.
Play Services will want to Update so allow that then most apps will need to be updated to the latest version.
Arrange the app icons and widgets on your Home screen and choose a nice wallpaper or live wallpaper and your done.
Hopefully everything will be quick & smooth. :fingers-crossed:
The ROM is not pre rooted so Root in the usual way using Magisk
PS: Ensure you check your app permissions and Default APPS the Phone app is Not the Default one even though it's the only one installed so please choose it Manually along with any others that do not set by themselves.
Thanks
Some Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
......
.....
.....
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
z4Android said:
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
Click to expand...
Click to collapse
Thanks. :good:
Be sure to let me know how you get on with it. :fingers-crossed:
I am not sure where you are from or which version of the XA you have but I am sure the ROM could be easily adapted for your own version.
All I would need would be a backup of your /oem & /boot partitions and the build.prop from your /system .
There is a modem config file in /oem which states telefonica uk I am unsure if this has any effect at all as I am sure I have flashed firmware from other European regions with no noticable effects.
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
z4Android said:
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
Click to expand...
Click to collapse
Hi, Your version should have no issues as it's identical to mine :good:
As for TWRP yes it does have issues with Unmounting /system for some reason
So if you mount /system from the Mount Menu TWRP or auto mount system you will not be able to Unmount mount it due to the "device or resource busy" error
If this happens you will need to ensure auto mounting is unselected and reboot to recovery from the Reboot menu.
I will look into the TWRP issue later to make things easier
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Bluesummerz said:
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Click to expand...
Click to collapse
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
bigrammy said:
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
Click to expand...
Click to collapse
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Bluesummerz said:
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Click to expand...
Click to collapse
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
bigrammy said:
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
Click to expand...
Click to collapse
And that is exactly why I like these forums, if you provide enough insight to a question, you'll get the full-spectrum answer, splendid!
And yes, confusing things is in my nature, also I might find it troublesome to know when I get like off topic here, so please stop me the moment, it would be better to switch to pm.
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
PS
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Bluesummerz said:
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Click to expand...
Click to collapse
Correct they are essentially a dd backup of the entire partition in question.
[Edit] To expand TWRP does not convert anything so if those partitions had the stock recovery & boot .elf format on them when the backup was performed they will still be .elf's which are not fastboot compatible. Those in my ROM have already been converted to .img format which is compatible with fastboot.
If you ever got stuck for some reason then you could simply use FlashTool to restore the Stock Recovery (fotakernel), Boot, OEM & System
Bluesummerz said:
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
Click to expand...
Click to collapse
Correct.
My Phone is restored using the F3111_33.3.A.1.97_1302-4476_R2B.ftf (FlashTool Firmware) and the ROM is based on this version.
Try to use a 33.3.A.1.97 if possible as I know that works.
Bluesummerz said:
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
Click to expand...
Click to collapse
Fastboot the recovery and the boot then You Simply need to follow the Flashing Instructions from step 2 in the first post from this point.
It is /data that gets wiped manually BTW (By The Way). TWRP will take care of the /system during it's restore tasks.
Bluesummerz said:
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
Click to expand...
Click to collapse
Yes providing you did everything correctly I see no reason why it would not work for you unless your device is a extra special Sony XA
Bluesummerz said:
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Click to expand...
Click to collapse
It stands for a Work In Progress.
The term work-in-progress (WIP) describes partially finished goods awaiting completion.
Does it has VOLTE support
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
altmash mirza said:
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
Click to expand...
Click to collapse
Not sure about VOLTE
If anyone did try this ROM nobody reported back
I guess this device is dead now as there seems to be very little activity which is a shame
drm fix working in case we use sony backups?
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
z4Android said:
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
Click to expand...
Click to collapse
Thanks for the feed back. :good:
Sorry no Oreo or Pie unless we fix the Ril issue on none Stock custom ROM's like the Lineage 14.1
bootlogo
bigrammy said:
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Click to expand...
Click to collapse
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Codetrr said:
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Click to expand...
Click to collapse
If your TWRP is not working you should fix this FIRST before doing anything else.
Warning: The logo partition is very important and as I said before it's part of the secure boot chain so if the logo does match the signature and or hash the ROM will boot loop or soft brick it did for me when I tried to change it so be very careful and make sure you can recover the phone with FlashTool.
To find partitions on Mediatek devices use this cmd.
Code:
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
This will give you a list of all partitions by-name and the actual dev block.
The logo partition is
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
So to flash the logo.img with dd you would copy the logo.img to your internal sdcard and use the following cmd.
Code:
dd if=/sdcard/logo.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
Sorry I cannot test your logo's because my wife use's this phone now as her everyday phone so she would not let me mess around with it now.
Akinimaginable said:
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Click to expand...
Click to collapse
The ROM is just stock ROM with most bloat ware removed and Google alternatives installed. I would recommend not to use the Sony "Album" app as it requires some other Sony apps which I removed and it continually looks for these apps. So just disable it in /settings/apps and use the pre-installed Google photos instead.
Also ensure you manually set the Phone app as the default dialer even though it's the only one or you will not be able to make or answer calls.
11 year girl! I would not worry they probably know more than we do at that age :laugh:
Yes it should be 100% compatible with a European Xperia XA F3111 ?
How to do this ?
I just rooted and flashed my old LG, and probably the by the "good" method. So if you have a link for the way to root and flash this phone, you'll make me very happy. I know that I have to go in adb flash TWRP as recovery, go in recovery by resetting the phone. Once this is done I have to wipe the phone, put the rom (and opengaps ?). And finally flash the rom. But previously I saw a lot of commands and warning so I'm a bit confused ?
Thanks for your attention ??