Related
Hi guys!
Download OEM Image: http : // 4pda . ru/forum/dl/post/7735591/WileyfoxOEM.img
Download TWRP Backup: https : // drive. google . com/file/d/0B6yu5JrPyY9mdDVxZHo0b2ZsVFU/view
Requirements:
-Wileyfox Swift with TWRP installed
How to install:
1. Download Files
2. Enter Fastboot
3. Delete old OEM and flash new OEM
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem WileyfoxOEM.img
4. Extract TWRP backup to sd:/TWRP/BACKUPS/*yourdevice*/*backupname*
5.*Optional* Wipe System, Boot, Data and Cache
6. Restore Backup via TWRP(System & Boot)
7. Reboot and enjoy!
Screenshots & Source: http : // 4pda . ru/forum/index.php?s=&showtopic=730213&view=findpost&p=52438437
PS: Remove the spaces in the links. I'm not able to post direct urls because of my low post count.
phncx said:
Hi guys!
Download OEM Image: http : // 4pda . ru/forum/dl/post/7735591/WileyfoxOEM.img
Download TWRP Backup: https : // drive. google . com/file/d/0B6yu5JrPyY9mdDVxZHo0b2ZsVFU/view
Requirements:
-Wileyfox Swift with TWRP installed
How to install:
1. Download Files
2. Enter Fastboot
3. Delete old OEM and flash new OEM
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem WileyfoxOEM.img
4. Extract TWRP backup to sd:/TWRP/BACKUPS/*yourdevice*/*backupname*
5.*Optional* Wipe System, Boot, Data and Cache
6. Restore Backup via TWRP(System & Boot)
7. Reboot and enjoy!
Screenshots & Source: http : // 4pda . ru/forum/index.php?s=&showtopic=730213&view=findpost&p=52438437
PS: Remove the spaces in the links. I'm not able to post direct urls because of my low post count.
Click to expand...
Click to collapse
New user with 1 post, looks sketchy. Think I'll hold out on this one. Be careful with this people.
LaneyUK said:
New user with 1 post, looks sketchy. Think I'll hold out on this one. Be careful with this people.
Click to expand...
Click to collapse
I understand your concerns, but you can check the source I provided. It's the same thread where the DP was released. The OEM image is even the exact same. You don't have to believe me, I just saw that this wasn't posted here yet, so I figured I'll link it for english speaking audiences, who don't want to use Google Translate or simply don't know that it's out there.
Greetings!
EDIT: Goddamn, I just wanted to share some screenshots to confirm it's indeed legit, but unfortunately I can't even post pictures because of my low post count.
phncx said:
I understand your concerns, but you can check the source I provided. It's the same thread where the DP was released. The OEM image is even the exact same. You don't have to believe me, I just saw that this wasn't posted here yet, so I figured I'll link it for english speaking audiences, who don't want to use Google Translate or simply don't know that it's out there.
Greetings!
Click to expand...
Click to collapse
Roger that! I just went back to stock for the vulnerability patches so I'll wait for confirmation before trying this. Thanks for clearing that up.
Thank you. It's working like a charm. But in about phone our phone is Genereal mobile 4G.
Ferrumlan said:
Thank you. It's working like a charm. But in about phone our phone is Genereal mobile 4G.
Click to expand...
Click to collapse
Really? Mine's still showing "Wileyfox Swift"? Well, that's weird, but if it still works, I guess it shouldn't matter.
phncx said:
Really? Mine's still showing "Wileyfox Swift"? Well, that's weird, but if it still works, I guess it shouldn't matter.
Click to expand...
Click to collapse
did you forgot to edit build.prop?
I snatched Nougat for General Mobile 4G I remember it
Sounds interesting. Are there any known bugs or lacking functionality?
nhmanas said:
did you forgot to edit build.prop?
I snatched Nougat for General Mobile 4G I remember it
Click to expand...
Click to collapse
I didn't edit anything, I installed the OEM images and the DP5 system & boot images and then dirty flashed the full release. I don't know if that makes a difference. In build.prop my device is listed as "seed"(GM 4G) but anyway it's still showing "Wileyfox Swift" in Settings
pucka said:
Sounds interesting. Are there any known bugs or lacking functionality?
Click to expand...
Click to collapse
No, everything works. It's an official OTA from Google for an Android One device.
Followed the instructions in first post...installed fine but I'd recommend a wipe of cache,data otherwise first boot hangs.
Everything seems to work but you can see its an initial build...jerky animations for example. After a brief play I restored my CM 13 backup. There's a world of difference in polish and options between the two at the moment.
is it purely stock android? or is it as customizable as cyanogenmod/os?
goodybags said:
is it purely stock android? or is it as customizable as cyanogenmod/os?
Click to expand...
Click to collapse
Stock...wanted to change order of nav buttons but its a no go.
aww. guess ill have to wait for cm14 then
I've got the files...
Question..
There is no wifi eap sim auth in this rom.
Where can I enable/tweak/mod wifi eap sim auth on Android 7.0 ?
On 6.0.1 There was an option in wifi options to select.
Thanks
Can anyone confirm that cellular works? I thought Android One used a different modem to the Swift.
seb5049 said:
Can anyone confirm that cellular works? I thought Android One used a different modem to the Swift.
Click to expand...
Click to collapse
It's working just fine here. I don't know if that's making a difference, but I'm living in Europe(Germany).
piromanneo said:
I've got the files...
Question..
There is no wifi eap sim auth in this rom.
Where can I enable/tweak/mod wifi eap sim auth on Android 7.0 ?
On 6.0.1 There was an option in wifi options to select.
Thanks
Click to expand...
Click to collapse
I'm sorry, but I have no idea. Hopefully someone else, who knows a bit more than I do, is watching this thread and can help you with this.
BTW: @ all I just noticed the OEM link seems to be down. I'll look for a mirror in the next few hours. Unfortunately, I deleted the file after flashing it. If you find one, please share it in this thread, so I can update OP.
phncx said:
It's working just fine here. I don't know if that's making a difference, but I'm living in Europe(Germany).
Click to expand...
Click to collapse
Ok, thanks. One more question: How would I go about restoring Cyanogen OS back? Can I just flash a backup I made?
phncx said:
It's working just fine here. I don't know if that's making a difference, but I'm living in Europe(Germany).
I'm sorry, but I have no idea. Hopefully someone else, who knows a bit more than I do, is watching this thread and can help you with this.
BTW: @ all I just noticed the OEM link seems to be down. I'll look for a mirror in the next few hours. Unfortunately, I deleted the file after flashing it. If you find one, please share it in this thread, so I can update OP.
Click to expand...
Click to collapse
Edit: Found new bug with Bluetooth, I can't turn it on, in settings it says Bluetooth disabled and WiFi EAP SIM support is not available in settings...
Otherwise ROM is stable, battery performance is superb (better than marshmallow or cm), no problems with lagging, network etc... I've tested only one SIM, I don't know if dual sim works , othervise in settings second sim slot is listed.
I've successfully rooted rom with lastest chainfire supersu, waiting for xposed framework nougat support.
FOR INSTALLING I've used the SIMPLE twrp method:
1. Unlocked bootloader
2. Flashed lastest TWRP
3. Cleaned everything
4. downloaded this zip
https:// docs.google.com /uc?id=0B6yu5JrPyY9maUJfMGNKai03VEk&export=download
5. Flashed it in TWRP recovery, first boot takes more time, google apps are included.
DE NADA
any custom kernel for N?
---------- Post added at 11:26 AM ---------- Previous post was at 11:24 AM ----------
seb5049 said:
Can anyone confirm that cellular works? I thought Android One used a different modem to the Swift.
Click to expand...
Click to collapse
wileyfox swift modem works fine on android one.
little problematic but works. so there's no reason to not work for you
so today i was testing the roms availble outside of oxygen os (forgot to make a back-up of oxygen was on the oreo beta wich seems to have been pulled now )when i flashed liquid remix and saw everything worked well, so i went back to twrp to adb sideload the open beta build i ha saved from when it was released, adb sideload fails cant read the zip figured oh ill redownload it, see that oneplus has deleted the download link son i decided to test crdroid and that worked as well as the other so i flashed omni and loved it except that it couldnt get wifi working so i downloaded the stock zip for 4.74 adb sideload from the stock recovery and boot up, still not able to connect to wifi it allows me to enter the password and it starts connecting then fails for no reason after 3 tries to connect the ssid shows that it is disabled
Learn a bit before flashing
Do you still have a MAC address for the WIFI on your phone?
Flash stock including radios from the factory image via fastboot
i dont have the ip address on that phone but i can get it off my friends. where would i find the fastboot images for the oneplus 5T?
I had/have the same problem with my 5T. I flashed the Oreo beta and now I can't use any of the Nougat versions of Oxygen. I flashed the Oreo back on and the WiFi works fine.
RLD831 said:
I had/have the same problem with my 5T. I flashed the Oreo beta and now I can't use any of the Nougat versions of Oxygen. I flashed the Oreo back on and the WiFi works fine.
Click to expand...
Click to collapse
i cant find a version of the oreo beta that boots through could you link me to it
No problem. Let me upload it to my Google Drive and I'll post a link.
thanks ill report back
ummm its right in front of u... if it was a snake it would have bit u
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074
Bradl79 said:
ummm its right in front of u... if it was a snake it would have bit u
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074
Click to expand...
Click to collapse
already tried that build adb sideload cant read it and the stock oneplus recovery cant seem to see my internal storage whereas twrp can twrp flash fails
kanaan360 said:
already tried that build adb sideload cant read it and the stock oneplus recovery cant seem to see my internal storage whereas twrp can twrp flash fails
Click to expand...
Click to collapse
that is a full zip whether its stock or twrp... what error does it give u in twrp
or r u having an error flashing TWRP recovery via fastboot?
it doesnt give an error in twrp it just fails to boot after the flash also i know that it doesnt matter sice its a full zip im getting more at adb fails on both
kanaan360 said:
it doesnt give an error in twrp it just fails to boot after the flash also i know that it doesnt matter sice its a full zip im getting more at adb fails on both
Click to expand...
Click to collapse
sorry to hear the issues u are having, but this device is a Pain the Ass to try different things and flashing different things, unlike older devices which u could flash anything and everything back and fourth. I am not even going to try Open Betas on this device, I may even stay away from Oero and custom roms for awhile until we can find an unbricking tool
have u tried to the rollback and/or nougat full zip
Bradl79 said:
sorry to hear the issues u are having, but this device is a Pain the Ass to try different things and flashing different things, unlike older devices which u could flash anything and everything back and fourth. I am not even going to try Open Betas on this device, I may even stay away from Oero and custom roms for awhile until we can find an unbricking tool
have u tried to the rollback and/or nougat full zip
Click to expand...
Click to collapse
yea i think ill just fix my onplus 3 screen because damn only had one issue with that and it was an easy fix. ive gone back to 4.7.4 and im about to try the rollback
kanaan360 said:
yea i think ill just fix my onplus 3 screen because damn only had one issue with that and it was an easy fix. ive gone back to 4.7.4 and im about to try the rollback
Click to expand...
Click to collapse
good luck man... let me know how it goes
no luck, btw the roll back build puts you on 4.7.5
kanaan360 said:
so today i was testing the roms availble outside of oxygen os (forgot to make a back-up of oxygen was on the oreo beta wich seems to have been pulled now )when i flashed liquid remix and saw everything worked well, so i went back to twrp to adb sideload the open beta build i ha saved from when it was released, adb sideload fails cant read the zip figured oh ill redownload it, see that oneplus has deleted the download link son i decided to test crdroid and that worked as well as the other so i flashed omni and loved it except that it couldnt get wifi working so i downloaded the stock zip for 4.74 adb sideload from the stock recovery and boot up, still not able to connect to wifi it allows me to enter the password and it starts connecting then fails for no reason after 3 tries to connect the ssid shows that it is disabled
Click to expand...
Click to collapse
have you tried to remove the wifi Networks from the Network list and reconnect it? i had a similar issue where it showed my wifi Networks as saved by Default as it was synched trough Google. and i had to remove and reconnect in order to get it working.
nadejo said:
have you tried to remove the wifi Networks from the Network list and reconnect it? i had a similar issue where it showed my wifi Networks as saved by Default as it was synched trough Google. and i had to remove and reconnect in order to get it working.
Click to expand...
Click to collapse
yes i even have this issue without gapps
I had similar issue yesterday after flashing the liquid ROM - when i try to connect to Wifi it says "Disabled" after many struggle i flashed the OOS Open Beta 1 now it works fine.
This Mod uses your fingerprint to lock your device. Longer presses will take you to the reboot menu.
:good: Download in my rom section or this quicklink.
https://forum.xda-developers.com/devdb/project/dl/?id=29427
How can i remove it from my phone?
nemanco said:
How can i remove it from my phone?
Click to expand...
Click to collapse
Unfortunately I had to reinstall my rom. :x
The problem was that the FP sensor is way too sensitive after installing the mod.
I couldn't hold the phone in the hand without instantly triggering the FP sensor.
Foremost the FP sensor doesn't react not only to saved FP's.
You should definitely look into that, Jerome.
Or at least offer a patch to uninstall the mod.
Besides that it's a very good idea, but it needs fine tuning.
Could you please give me the uninstalation for the mode the fingerprint sensor is to sensitive, and i realy dont want to reflash the stock rom again ?
nemanco said:
Could you please give me the uninstalation for the mode the fingerprint sensor is to sensitive, and i realy dont want to reflash the stock rom again ?
Click to expand...
Click to collapse
Put without unzip inside this zip only the META-INF folder from the zip that you flashed meanwhile OP can solve this, hope this works
View attachment restore-fingerprint.zip
SubwayChamp said:
Put without unzip inside this zip only the META-INF folder from the zip that you flashed meanwhile OP can solve this, hope this works
View attachment 4505426
Click to expand...
Click to collapse
Worked as a charm, thanks! !!!
after flashing the zip file all working and really good but the volume rocker and power doesent work, I downloaded the removefingerprint.zip but also doesent work when I flashed the file.
My currently Rom is AOSP Extended 7.1
thanks.
mavid26 said:
after flashing the zip file all working and really good but the volume rocker and power doesent work, I downloaded the removefingerprint.zip but also doesent work when I flashed the file.
My currently Rom is AOSP Extended 7.1
thanks.
Click to expand...
Click to collapse
Almost any rom would need a proper remover/replacer zip, last was for miui roms so try this, read the post #5 and apply to this zip before flashing it. I hope it works
View attachment restore-fingerprint-aex71.zip
I installed the lineage os 15.1 on my xiaomi redmi 5 plus, but the fingerprint settings are not there and I do not know how to put them.
Are there any mods? How can I do?
thank you
Thanks for your amazing mod it's working prefect on my miui but now i installed pixel experience rom and the mod not work. Please update it for costume roms.
Tested on MIUI 10 RN5 Global (AI) and it broke both power button and fingerprint button.
EDIT: the fix provided did not work for me. Copied the folder as requested to the zip but even after flash the buttons are still broken (had to flash the ROM, just a system restore could not fix it too.)
it ****ed up my Redmi 5 Plus phone i don't want to reinstall my rom please publish uninstall for oreo or Pie patch .
sfnemis said:
it ****ed up my Redmi 5 Plus phone i don't want to reinstall my rom please publish uninstall for oreo or Pie patch .
Click to expand...
Click to collapse
Which version firmware are you using?
lock unlock fingerpriner
does it exist for redmi note 7?
Way to fix...
Perhaps a bit late, but...
For those who lost power and volume rockers the problems is file permissions.
You have to change file permission of 3 files on /system/usr/keylayout:
- Generic.kl
- uinput-fpc.kl
- uinput-goodix.kl
and set them to "-rw-r-r--"
also set them to be owned by root:root
While booting these files must be read for non root process. On some installs the last "r--" (other user privileges) are not set correctly.
Also, you must know that each keymapping files are for each brand and model. Where key 353 if for virtual fingerprint on RN5, the same "virtual fingerprint key" is number 96 on Mi Mix2, so if you flahed these files por RN5 on other model, you should find these files from a ROM (TWRP/nandroid backup from your device previous to the flash), or other rooted device and copy them to your own.
With these instructions you could prevent flashing entire rom
king.com said:
Perhaps a bit late, but...
For those who lost power and volume rockers the problems is file permissions.
You have to change file permission of 3 files on /system/usr/keylayout:
- Generic.kl
- uinput-fpc.kl
- uinput-goodix.kl
and set them to "-rw-r-r--"
also set them to be owned by root:root
While booting these files must be read for non root process. On some installs the last "r--" (other user privileges) are not set correctly.
Also, you must know that each keymapping files are for each brand and model. Where key 353 if for virtual fingerprint on RN5, the same "virtual fingerprint key" is number 96 on Mi Mix2, so if you flahed these files por RN5 on other model, you should find these files from a ROM (TWRP/nandroid backup from your device previous to the flash), or other rooted device and copy them to your own.
With these instructions you could prevent flashing entire rom
Click to expand...
Click to collapse
Hi, Is there a code you know for the mi A1 (tissot) is needed to lock the screen.
or there may be a hint on where to find it, thanks :victory:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CLICK HERE TO READ THE MEGATHREAD BEFORE DOING ANYTHING TO YOUR DEVICE
Here we are guys... After searching here and there i found some working ways to Root this device without getting bricked. So let's discuss about these :
1. UNLOCKING BOOTLOADER :
- Download the Mi Unlock app to PC, and sign in with your Mi Account;
- Enable Developer Option in your phone by tapping the "Build Number" 7 times
- Go to Developer Options "Settings > Additional Settings > Developer Options
- Enable USB Debugging and OEM Unlocking
- Aslo add account in Mi Unlock Status (Can be found in Developer Options
- Install all the required drivers (adb drivers, vcom drivers etc.) In your PC [I'll link these below]
- Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot mode
- Connect your phone to PC using USB cable and click "Unlock". In Mi Unlock Tool
- You will be given a specific time (168 hours mostly)
- Wait until that and redo Unlock process
- Woah you have Unlocked your device
2. FLASHING TWRP :
- Install Minimal ADB and fastboot on your PC [Link will be provided below]
- Download LR Team TWRP [This work for now, I'll provide link below and will update it after we have another proper TWRP]
- Put that TWRP in the file location of ADB and Fastboot (Right click on Minimal ADB and Fastboot icon on desktop and click on Open file location)
- rename that recovery to "twrp" for convenience (optional)
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode
- Type
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type
Code:
fastboot flash recovery twrp.img
- When it's done, Remove cable and Hold Power + Vol. Up when phone starts turning on leave the power button but keep pressing Vol. UP until TWRP splash Screen shows up.
- Done U did it
3. ROOTING :
- In TWRP mount System
- Go to Advanced > file manager
- then go to system_root > system and delete "recovery-from-boot.p"
- Go home and again go to advanced and Select "Close AVB2.0" swipe to confirm.
- Go back and select "Install Root"
- Here you go magisk 19.4 will be installed (U can chose any other versions afterwards.)
- Reboot the device to system.
- Ah Yes you did it
In case anything goes wrong ask me here or in official telegram group
LINKS
1. Mi Unlock tool
2. Minimal ADB and Fastboot
3. ADB Drivers for MTK
4. MTK USB Drivers
5. LR Team TWRP
If this helped you then hit the Thanks Button. Good Luck
Does it work for the china edition of the phone?
These are the the same instructions as found here https://forum.xda-developers.com/showpost.php?p=80604223&postcount=2
Why create a new thread without giving any credits. It's cluttering the forum.
In case anything goes wrong ask me here or in official telegram group
Click to expand...
Click to collapse
Reported, read the FAQ about telegram.
donkyshot said:
These are the the same instructions as found here https://forum.xda-developers.com/showpost.php?p=80604223&postcount=2
Why create a new thread without giving any credits. It's cluttering the forum.
Reported, read the FAQ about telegram.
Click to expand...
Click to collapse
Ah ok...i didn't check that thread... I just searched here and there and created a simple guide...
Robstir said:
Yes it does, I just rooted mine, Chinese 8gb RAM with Chinese ROM (no Google) only problem I just found was - can't make a TWRP back up on either storage, says can't make the folder, key unavailable.
I tried a couple of other methods which didn't work, so great stuff for posting here, I don't use Telegram, so it's really helped me, even if it is a duplicate, wind your neck in with the reporting Donkeywhatever!
Thanks OP
Click to expand...
Click to collapse
I'm glad to hear that it helped you...
Robstir said:
Thanks, it did brilliantly, any advice on the TWRP can't make the backup folder?
I'm keen to start pruning the system of the useless Xiaomi bloatware but not without a backup, flashed Magisk 20.1 also, working perfectly.
Click to expand...
Click to collapse
Wait for a proper TWRP. Cuz devs are already working on it
anybody tried that with chinese phone swapped to global rom?
Robstir said:
Yes it does, I just rooted mine, Chinese 8gb RAM with Chinese ROM (no Google) only problem I just found was - can't make a TWRP back up on either storage, says can't make the folder, key unavailable.
I tried a couple of other methods which didn't work, so great stuff for posting here, I don't use Telegram, so it's really helped me, even if it is a duplicate, wind your neck in with the reporting Donkeywhatever!
Thanks OP
Click to expand...
Click to collapse
Erm the issue i have with ChinaRom is that I cant use my own homescreen launcher... even with root I cant bypass it... so I have to be on Global ROM... but china variant with global rom causes boot loop.... and seeing that you are using the only TWRP available i think the results are the same...
---------- Post added at 05:42 AM ---------- Previous post was at 05:42 AM ----------
pritish1998 said:
Wait for a proper TWRP. Cuz devs are already working on it
Click to expand...
Click to collapse
Oo really? Gee can't wait....
so always bootloop issue with china/global device?
Bricked my China Rom Phone
I just bricked my phone - story here:
https://forum.xda-developers.com/redmi-note-8-pro/help/help-to-unbrick-china-redmi-note-8-pro-t4004681
So does anyone have any idea how I can unbrick? Should I REM out the antirollback check lines in flash_all.bat?
Any help is much appreciated! Thank you!
My phone came with the Global EU (EEA) version ROM, i have flashed Global (MI) version. Will this method still work or will it cause bootloop? I don't want to brick my device so asking in advance. I was lucky to just get stuck in bootloop with my previous try using a different recovery.
P.S. I used MiFlash Tool and flashed the ROM through Fastboot.
Hey Pritish1998,
I must admit, I was a little leery, after reading all the other threads about installing twrp and rooting and the horror stories they contained. Well, your instructions seemed fairly simple. I followed them EXACTLY... and I lost my ass, everything got wiped, my imei, everything!!!
Totally kidding, everything worked perfectly, I followed your steps exactly as stated. I did not loose any data, nothing, every app, all my downloads, everything is still on my phone. THANK YOU SO MUCH!
Also, TWRP, is still installed, didn't get wiped out by the stock recovery. I have root, and oh, I am on MIUI Global, on the United States phone I ordered off of Amazon. More Specifically, MIUI Global 11.0.1.0(PGGMIXM) Android Version 9 PPR1.180610.011. I received the MIUI 11 update about 3 days ago, and was still waiting the 160 some hours out for the bootloader unlock. I just got the bootloader unlocked about 3 hours ago. Went through numerous instructions and posts and this one seemed to make the most sense. I wasn't sure about MIUI 11 working, but fudge it, I thought I would just return the phone if I had a problem, but nope, you're instructions were clear and precise and I followed them to a tee and its working great and I have Magisk and did the safetynet update, and I'm all good.
I haven't updated Magisk to 20.1 though. Didn't want to press my luck.
Thanks so much bro, really, thank you.
this procedure worked as well on an indonesian 11.0.1. rom!!!
thx!
Hello good day! I have a question about TRWP:
1) Is it safe to install this TRWP f I am on 11.0.1.0 PGGEUXM?
Has anyone else done it since rom EEA instead of Gobal (MI)?
Thank you
Thank you very much, magisk works perfectly
donkyshot said:
These are the the same instructions as found here https://forum.xda-developers.com/showpost.php?p=80604223&postcount=2
Why create a new thread without giving any credits. It's cluttering the forum.
Reported, read the FAQ about telegram.
Click to expand...
Click to collapse
NOTHING WRONG WITH THE ABOVE POST BUT MORE INFORMATIVE. The link you claimed to be original is for the Chinese device only not for the Global. TWRP is also different. Check the files.
neoxcool said:
NOTHING WRONG WITH THE ABOVE POST BUT MORE INFORMATIVE. The link you claimed to be original is for the Chinese device only not for the Global. TWRP is also different. Check the files.
Click to expand...
Click to collapse
No need for caps lock. We can read.
It was initially a double post he just edited it later and changed it to a guide, which is fine.
It's the same procedure like initial Chinese twrp which was and is already posted here.
I'm on xiaomi.eu beta Android 10 but now i can't boot the recovery, any ideas?
.
Martin213 said:
You can't boot to stock recovery?
Be careful now i think you're one step ahead brick...
Click to expand...
Click to collapse
Phone is working normally but i want to change to stable, but the recovery is not booting.
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.
zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash
I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters
Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.
As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.