Related
Hi everyone,
i had the " stupid idea " to update my oppo find 7a to official coloros 2.0 KK !
I didn't like it so much and then i decided to go back to Dirty Unicorn BUT once done that i could not get any NETWORK working!
Following some other user suggestion i went back to 1.2.4 (they say booloader is unlocked) but still couldn't have network working!
SO far the only way to have my network back is to load COLOROS 2.0 KK..
can anyone please tell me how can i have my network BACK on any other rom than coloros 2.0??
thank you so much!
simika said:
Hi everyone,
i had the " stupid idea " to update my oppo find 7a to official coloros 2.0 KK !
I didn't like it so much and then i decided to go back to Dirty Unicorn BUT once done that i could not get any NETWORK working!
Following some other user suggestion i went back to 1.2.4 (they say booloader is unlocked) but still couldn't have network working!
SO far the only way to have my network back is to load COLOROS 2.0 KK..
can anyone please tell me how can i have my network BACK on any other rom than coloros 2.0??
thank you so much!
Click to expand...
Click to collapse
SOLUTION
FINALLY!!!!!!!!!!!
FIRST i had to find the OLD (1.2.3 ) oppo recovery (link: http://d-h.st/pfR )
i INSTALLED it from fastboot
than always in fastboot i did FASTBOOT OEM UNLOCK
then i boot into recovery.. installed Oppo coloros 1.2.4 ( seems to have bootloader unlocked )
now ive 1.2.4 and i'm gonna install back dirty unicorn.. probably will work !!!!!!!!
YES I CONFIRM.. it works..
so for all of those having problems with color os 2.0 kk and decide to go back to other ROM(and having issues on calling ) just do as i did ..
i hope it helps others
simika said:
SOLUTION
FINALLY!!!!!!!!!!!
FIRST i had to find the OLD (1.2.3 ) oppo recovery (link: http://d-h.st/pfR )
i INSTALLED it from fastboot
than always in fastboot i did FASTBOOT OEM UNLOCK
then i boot into recovery.. installed Oppo coloros 1.2.4 ( seems to have bootloader unlocked )
now ive 1.2.4 and i'm gonna install back dirty unicorn.. probably will work !!!!!!!!
YES I CONFIRM.. it works..
so for all of those having problems with color os 2.0 kk and decide to go back to other ROM(and having issues on calling ) just do as i did ..
i hope it helps others
Click to expand...
Click to collapse
@simika
Glad you got it working again.
I have a friend who bought his Find 7a x9007 second hand with no mobile connectivity. It has ColorOS 2.0.1i installed and I was wondering if the situation is similar to yours. I will try to fix it tonight but I have one question. At which point did you get your connectivity back? After installing ColorOS 1.2.4 or after installing Dirty Unicorns?
The easiest guaranteed way to get connectivity and custom rom support back up and running after an official KitKat update is to restore the phone to ColorOS 1.2.5 using the Sahara package from here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
After restoring the phone via Sahara it will be fully reset and you can do whatever you want from there.
MrColdbird said:
The easiest guaranteed way to get connectivity and custom rom support back up and running after an official KitKat update is to restore the phone to ColorOS 1.2.5 using the Sahara package from here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
After restoring the phone via Sahara it will be fully reset and you can do whatever you want from there.
Click to expand...
Click to collapse
Thanks. Downloading now. However, I need to ask two more things. Is this Sahara package international or chinese version? I'm asking bcs I'm going the flash it to a chinese model (x9007). Finally, is it OK to flash it with "TWRP mod for ColorOS" or do I need ColorOS recovery?
Edit:
I've got the file but it's not a flashable zip. How do I flash it? Google search gave me no results!
Edit2:
I found the instructions. Now I only need confirmation that it will work on the x9007. Any feedback will be much appreciated.
Edit3:
I got too impatient and used the tool anyway. It worked like charm. I saw the progress bars while flashing all partitions and in the end it got green. I rebooted the phone and it had gone back to ColorOS 1.2.5i but, guess what, I still had no GSM/3G signal. Then I thought, hey, this tool flashed an international version, so I probably need a Chinese baseband. So I used modded TWRP and flashed modem pack 1.2.5 by zixuan. Rebooted and to my great disappointment, I still had no signal!!! So, I decided to go one step further. I installed a genuine Chinese ROM (v1.2.0) and after rebooting, I still had no signal!!!
I'm about to tell my friend to sell his phone for parts, unless you, gurus, have any further suggestions...
we
dreccon said:
Thanks. Downloading now. However, I need to ask two more things. Is this Sahara package international or chinese version? I'm asking bcs I'm going the flash it to a chinese model (x9007). Finally, is it OK to flash it with "TWRP mod for ColorOS" or do I need ColorOS recovery?
Edit:
I've got the file but it's not a flashable zip. How do I flash it? Google search gave me no results!
Edit2:
I found the instructions. Now I only need confirmation that it will work on the x9007. Any feedback will be much appreciated.
Edit3:
I got too impatient and used the tool anyway. It worked like charm. I saw the progress bars while flashing all partitions and in the end it got green. I rebooted the phone and it had gone back to ColorOS 1.2.5i but, guess what, I still had no GSM/3G signal. Then I thought, hey, this tool flashed an international version, so I probably need a Chinese baseband. So I used modded TWRP and flashed modem pack 1.2.5 by zixuan. Rebooted and to my great disappointment, I still had no signal!!! So, I decided to go one step further. I installed a genuine Chinese ROM (v1.2.0) and after rebooting, I still had no signal!!!
I'm about to tell my friend to sell his phone for parts, unless you, gurus, have any further suggestions...
Click to expand...
Click to collapse
i too have this connectivity issue that even sahara package could not fix. i do sometimes get signal using 2.0.x roms or 5.0.x roms but i cant call or send sms, in phone status it shows mobile network unknown
wish there was a fix for this
thirdzcee said:
we
i too have this connectivity issue that even sahara package could not fix. i do sometimes get signal using 2.0.x roms or 5.0.x roms but i cant call or send sms, in phone status it shows mobile network unknown
wish there was a fix for this
Click to expand...
Click to collapse
Well, in my case, it seems that someone had tampered with the antenna RF cable. As soon as I replaced it, the phone worked normally and I had no problem installing and using Nameless Lollipop over a Chinese baseband. My friend is happy with his phone now!
dreccon said:
Well, in my case, it seems that someone had tampered with the antenna RF cable. As soon as I replaced it, the phone worked normally and I had no problem installing and using Nameless Lollipop over a Chinese baseband. My friend is happy with his phone now!
Click to expand...
Click to collapse
weird, after many attempts i finally gave up, but to my surprise when i woke up one moring my phone just had reception now, was able to call and text and have data and i dont have a clue what happened, the last thing i did was not flash sahara packacge, but flash 2.0.3beta then downgrade to 1.2.3 then flash 1..2.7i but i didnt get any signal back until that morning.. weird but im happy i got signal back and now happily running CoS 2.0.7
Hello, i hope there is someone that can help me with this problem i have.
I rooted and used cm12 sometime in the begining og 2015, then i unified the phone and used another rom(dont remember what), but it crashed sometime last summer and went black.
And after i have had it i started reading and found some posts and figured out i could try to get life in it befor cristhmas, and i found this: community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1[/url]
And i found a computer with win 7 on, and i got the phone back to life, but the rom stopped at language or region settings at installing.
and the i tried using nameless-recovery-twrp-2.8.7.0-find7-20151220 and the rom will start up, but i dont have wifi, radio or IMEI.
And i found someone that gave me oneplus.qcn this file, but i cant get my phone in to diagnostic mode, becouse the code *#801# is not working on my phone(Only *#06# is working).
I have tried different roms and recovery, but onlu namless rom is working in that way that i can start a rom (color os 1.4i up to 1,8i) over 1.8 will not start.
So i would be wery happy if there is someone that can help me fix it..
And i apologies for my English, but hopfully it is possible to understand.
Kindly regard
Johan
JPSimon said:
Hello, i hope there is someone that can help me with this problem i have.
I rooted and used cm12 sometime in the begining og 2015, then i unified the phone and used another rom(dont remember what), but it crashed sometime last summer and went black.
And after i have had it i started reading and found some posts and figured out i could try to get life in it befor cristhmas, and i found this: community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1[/url]
And i found a computer with win 7 on, and i got the phone back to life, but the rom stopped at language or region settings at installing.
and the i tried using nameless-recovery-twrp-2.8.7.0-find7-20151220 and the rom will start up, but i dont have wifi, radio or IMEI.
And i found someone that gave me oneplus.qcn this file, but i cant get my phone in to diagnostic mode, becouse the code *#801# is not working on my phone(Only *#06# is working).
I have tried different roms and recovery, but onlu namless rom is working in that way that i can start a rom (color os 1.4i up to 1,8i) over 1.8 will not start.
So i would be wery happy if there is someone that can help me fix it..
And i apologies for my English, but hopfully it is possible to understand.
Kindly regard
Johan
Click to expand...
Click to collapse
Hey there! Sad to hear that you have bricked your phone and lost your imei.
Im no expert, but have you retry the method provided in oppoforums? I suggest that you retry it once more.
Have tried
DingleBell said:
Hey there! Sad to hear that you have bricked your phone and lost your imei.
Im no expert, but have you retry the method provided in oppoforums? I suggest that you retry it once more.
Click to expand...
Click to collapse
Yes, i have tried it several times, and i only get to the same point every time.
JPSimon said:
Yes, i have tried it several times, and i only get to the same point every time.
Click to expand...
Click to collapse
Have you tried reverting back to stock ColorOS rom? Try to flash stock ColorOS 2.0.8i or ColorOS 2.1.5i to your phone. Usually when things go bad, people usually revert back to stock coloros rom and that fixed their problems as it fixed mine before this.
DingleBell said:
Have you tried reverting back to stock ColorOS rom? Try to flash stock ColorOS 2.0.8i or ColorOS 2.1.5i to your phone. Usually when things go bad, people usually revert back to stock coloros rom and that fixed their problems as it fixed mine before this.
Click to expand...
Click to collapse
The phone will only start up when i use colosos 1.4 up to 1.8, when i use higher or lower it will not start up..
And i can not use color recovery, only with nameless-recovery-twrp-2.8.7.0-find7-20151220..
So I installed the latest Oreo Global ROM on my Mi 6. Everything was smooth until I decided to install some dark theme from the Themes app and the phone bricked.
I booted into recovery mode, wiped all data and rebooted.
As I reboot, it shows the MIUI 9 intro screen. Select language, then select region. AFTER I select region, the phone setup shows 'wait a second...' and then the error happens: a message 'Find Device has stopped' appears and it boots. Eternally.
So far I've tried:
1) Xiaomi PC Suite - says I should update my phone before using it.
2) Xiaomi Mi Flash - says I need to unlock bootloader
3) I asked to unlock bootloader, was authorized for my Mi account a few hours later, but when I use the Mi unlocker app, it says my My Account was not bound to the device (well it was but I wiped data...)
4) If I try an unnoficial flash tool, it says I need to enable USB debugging. I can't enable it anymore because the phone is stuck in the initial setup screen when it boots after Find Device stops.
Any suggestions please? I have no idea how to recover my phone.
Thanks!
Here is a method that worked for bricked Mi 5 devices.
I don't have time to look in your particular problem right now, but rest assured, as a last resort you can always boot into EDL mode and flash right away without unlocked BL. You need to open up your phone for that though.
mkioshi said:
Any suggestions please?
Click to expand...
Click to collapse
Alright, I might have worked out a solution, make sure to follow these steps:
Download Global Dev 8.1.25 ROM zip.
Download Xiaomi ADB, extract the 3 files and put them in a folder with the ROM zip.
Hold Vol + Power down and in the following menu select "Connect to Mi Assistant" or "连接小米助手".
Drag the ROM zip onto the XiaomiADB.exe, let it do its thing.
On successful flash the device will reboot. Enter recovery-mode again.
Via cmd, run xiaomiadb format-data.
Let me know if this works. If you have any questions, feel free to ask.
Good luck!
DavidRJ said:
Let me know if this works. If you have any questions, feel free to ask.
Good luck!
Click to expand...
Click to collapse
Damn, I thought this would work.
I tried to flash your dev rom, it said I can only flash Global ROMs.
So I tried 9.2.2.0,it said I could not flash this because it's older.
Then I tried the current ROM I had, the 9.3 (Oreo) and it flashed alright, I formatted data via adb like you said... But no way, I get the same MIUI welcome screen, choose language, choose region, and after I choose region (only China is listed) I get the same Find Device closed message and it reboots.
Maybe I'll be able to do this with a future MIUI release? Maybe it's a 9.3 OCAMIEK bug?
mkioshi said:
Maybe I'll be able to do this with a future MIUI release? Maybe it's a 9.3 OCAMIEK bug?
Click to expand...
Click to collapse
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
It happened to me exactly the same this weekend in a mix 2. After all the afternoon trying to fix it in this way.
Install a recovery through adb in fastboot mode, from adb restart the device by pressing the volume up button to enter the recovery directly. Once in recovery mode I made all the wipes and then I copied a custom rom to the internal memory of the phone and the flash in my case was epic rom. And the cell phone already works perfectly for me.
I write from a translator I'm sorry if you do not understand something, I hope it helps.
A greeting from Spain!
I just spent hours fixing the same issue. In the end the following method worked. Note that it requires an unlocked bootloader.
Sorry I can't post links yet so just have to refer to Google searching...
1. Download latest miFlash v2017.7.20.0 (Google search for it)
2. Go to "Fastboot Update - Xiaomi MIUI Official Forum" site (again just Google search)
3. Download "★ Xiaomi Mi 6 Latest Global Stable Version Fastboot File Download" from the website in step 2 (other ROMs probably work too)
4. Follow the above guide from the Fastboot section
Good luck!
Pc suite wont work on our mi6 because it only works until android 6 or so, so its not for us.
Id wait for the next global stable release and try that one out. BTW, have u tried flashing MIUI china versions? Maybe that one works out (althugh it said only global, maybe referring to developers and not china stable). GL!
I can't unlock the bootloader. Applied for it on MIUI, it authorized me but the unlocked app says the device is not bound to my MIUI account.
Although i have logged in and backup stuff from my Mi account in that phone, that unlock app says its not associated. Maybe because I wiped the data when it bootlooped, i don't know. Anyway unfortunately can't unlock it right now. Thanks!
Sent from my SM-N920G using Tapatalk
DavidRJ said:
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
Click to expand...
Click to collapse
Oh I'll try other Roms. You did help me a lot tho because i was finally able to at least flash something to my phone. That relieves me a ton, because at least i know it can be saved someday lol.
I'm using my Galaxy note 5 and traveling now but will definitely try other Roms like the Chinese one next week. Thanks again, friend.
Sent from my SM-N920G using Tapatalk
mkioshi said:
That relieves me a ton, because at least i know it can be saved someday lol.
I'm using my Galaxy note 5 and traveling now but will definitely try other Roms like the Chinese one next week.
Click to expand...
Click to collapse
Not too bad of a substitute phone.
Apart from trying other ROMs, the notable thing here is that you can kind of access ADB commands via that tool which might help you fix the issue with "Find Device" FC.
Anyways, if you have any more questions later, I'll gladly help.
David
DavidRJ said:
Not too bad of a substitute phone.
Apart from trying other ROMs, the notable thing here is that you can kind of access ADB commands via that tool which might help you fix the issue with "Find Device" FC.
Anyways, if you have any more questions later, I'll gladly help.
David
Click to expand...
Click to collapse
Thanks David. I'll take a look at all the options in the adb tool when i come back home Monday.
I love my note 5, the screen is gorgeous and the camera is better than the Mi 6 IMHO. Reason i bought the Mi 6 are the 128 tb of storage, the size (this note i too big for my small hands) and the Mi 6 is so much faster, besides having tremendous battery life. My note5 battery was always ****, and I have been using it for the last 2 years (go the Mi 6 like 2 months ago).
You've been extremely helpful, bud. Are you from Brazil too? (Asking because of the RJ in your Nick)
Sent from my SM-N920G using Tapatalk
DavidRJ said:
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
Click to expand...
Click to collapse
I managed to flash the last global dev via xiaomiadb. It all went smooth.
Obviously, after selecting language and region, I get the same Find Device closed unexpectedly and it reboots.
And now, when I try to use xiaomiadb to flash or format data, it says ERROR and the phone reboots, like he's "rejecting" any xiaomiadb command. SO cannot flash anything now.
I'm giving up on this horrible phone.
mkioshi said:
And now, when I try to use xiaomiadb to flash or format data, it says ERROR and the phone reboots, like he's "rejecting" any xiaomiadb command. SO cannot flash anything now.
I'm giving up on this horrible phone.
Click to expand...
Click to collapse
Sorry to hear that. I can't really say what's the issue here as your phone is definitely not hard bricked but I have never seen such behavior before.
Well depending on where you bought your phone, you could definitely file an RMA with the seller. You didn't unlock bootloader and your phone bricked itself basically. If you bought it in China, it depends on how easy it is to ship phones overseas in Brazil. In Europe, we can't easily ship phones with non-removable batteries sadly. (Sou da Alemanha btw mas falo um poucinho de Português )
In any case, your last bet would be the EDL method. You will lose your warranty though.
But I understand that this is way too much hassle for a soft brick caused by a damn theming engine... I'm so glad I switched off MIUI months ago.
Anyways good luck and let me know if you get any further.
David
DavidRJ said:
Sorry to hear that. I can't really say what's the issue here as your phone is definitely not hard bricked but I have never seen such behavior before.
Well depending on where you bought your phone, you could definitely file an RMA with the seller. You didn't unlock bootloader and your phone bricked itself basically. If you bought it in China, it depends on how easy it is to ship phones overseas in Brazil. In Europe, we can't easily ship phones with non-removable batteries sadly. (Sou da Alemanha btw mas falo um poucinho de Português )
In any case, your last bet would be the EDL method. You will lose your warranty though.
But I understand that this is way too much hassle for a soft brick caused by a damn theming engine... I'm so glad I switched off MIUI months ago.
Anyways good luck and let me know if you get any further.
David
Click to expand...
Click to collapse
You're a very nice person, David, thanks a ton!
Oh no xiaomi RMA here. And yeah I saw some people who bricked their phones by installing some dark theme (not the same as mine, but it was always a dark theme) after upgrading to the Oreo global rom.
And just my luck, my Note 5 took a dive yesterday so I'm phoneless lol. Thinking bout getting a Xiaomi A1 or a Moto X4, theyre not expensive and about the same price here...
If you can use adb commands. Try:
> fastboot erase system
> fastboot erase userdata
> fastboot erase boot
> fastboot erase cache
> fastboot erase data
Then try flashing the the latest developer rom as you did before.
mkioshi said:
And just my luck, my Note 5 took a dive yesterday so I'm phoneless lol.
Click to expand...
Click to collapse
Damn... Well you could still try the advice from @golfinry, I didn't think of regular ADB commands at all. Then again, if you can't do RMA anyways, what's stopping you from trying the EDL method? As far as I know you can flash any MIUI ROM you want without unlocked BL with that.
golfinry said:
If you can use adb commands. Try:
> fastboot erase system
> fastboot erase userdata
> fastboot erase boot
> fastboot erase cache
> fastboot erase data
Then try flashing the the latest developer rom as you did before.
Click to expand...
Click to collapse
Oh but I cannot use fastboot on locked bootloader right? Got the message after trying these commands
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.003s
DavidRJ said:
Damn... Well you could still try the advice from @golfinry, I didn't think of regular ADB commands at all. Then again, if you can't do RMA anyways, what's stopping you from trying the EDL method? As far as I know you can flash any MIUI ROM you want without unlocked BL with that.
Click to expand...
Click to collapse
Seems to require unlocked BL. Anyway have you ever seem this error:closed message when trying to do adb commands like adb usb (or xiaomiadb usb), adb format-data, adb sideload, etc?
Started happening after I managed to flash latest global. SO I cannot try to flash anything now
Figured as much... What about the data partition. Same thing?
After the latest update of Oxygen os my 5t had start crashing so I Installed TWRP recovery and Installed Linage OS but in that rom also there was same problem so i Installed another rom OMNI and there was the same problem Today the phone crashed as always and it Didn't boot up It got stuck in Boot animation and that i tried to flash another rom but no rom will get flashed from twrp also so I used ADB Sideload to flash rom it got flashed but it also got stuck in bootanimation It wasn't a Bootloop It just got Hang on Bootanimation and than I use hardbrick method (MSMdownloadTool V4.0.8) It flashed The Stock OS which Booted Fine for 10sec And the same problem happens again I have Flashed two Stock OS (1 - dumpling_43_O.06_171206.ops) and (2 - dumpling_43_O.36_180613.ops) Now there is no boot-animation Its Stuck on One-plus Logo (POWERED BY ANDROID) Plz Help sorry for my English
Sounds like a faulty flash storage. RMA it.
freyrnygaard said:
Sounds like a faulty flash storage. RMA it.
Click to expand...
Click to collapse
what is RMA I Really Need your Help PLZZZ
Why did you use nougat and oreo unbricking tools if you were on pie? No wonder your phone doesn't boot.
The latest unbricking tools for 9.0.3 can be found here: https://www.androidfilehost.com/?fid=11410963190603910105
RMA means Return Merchandise Authorization (send back to the seller). Since you've already used the phone, you can't just send it back anyway. If unbricking doesn't work, you'll have to contact oneplus support to find out what your options are.
bud7dha said:
Why did you use nougat and oreo unbricking tools if you were on pie? No wonder your phone doesn't boot.
The latest unbricking tools for 9.0.3 can be found here: https://www.androidfilehost.com/?fid=11410963190603910105
RMA means Return Merchandise Authorization (send back to the seller). Since you've already used the phone, you can't just send it back anyway. If unbricking doesn't work, you'll have to contact oneplus support to find out what your options are.
Click to expand...
Click to collapse
Offtopic but you can use Nougat and Oreo unbrick tools even if you're on Pie (I did it myself because I was curious to see if it will erase /vendor partition or not). I however agree that this is not a normal situation and that his storage might be faulty.
Can you at least flash stock recovery?
freyrnygaard said:
Sounds like a faulty flash storage. RMA it.
Click to expand...
Click to collapse
Hmm. I was thinking about rooting mine today. But you got me thinking again lol.
I googled "faulty flash storage Android" and not much came up tho. Can you get into a little bit more detail what is that and is it very common with onePlus devices ?
*Sorry if I asked sth dumb. Im new to Android ?
nevethlexfiend said:
Hmm. I was thinking about rooting mine today. But you got me thinking again lol.
I googled "faulty flash storage Android" and not much came up tho. Can you get into a little bit more detail what is that and is it very common with onePlus devices ?
*Sorry if I asked sth dumb. Im new to Android
Click to expand...
Click to collapse
I meant as in a a damaged internal storage drive. You know, a storage drive can fail but it certainly won't happen from rooting your phone. So go ahead and enjoy.
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.