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.
Related
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.
Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img
This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?
WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!
@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT
Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?
@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs
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.
I'm not completely brand new to flashing with custom roms, but I sometimes go 2-3 years running stock, so when I do come back I have forgotten everything and it feels like starting over.
So far I have achieved the following:
1 - backed up device
2 - reset device back to stock
3 - flashed stock image using Heimdall
Unfortunately after all that I am not sure if I have made any progress. It just took my phone back to factory settings.. My storage is full, my SDCard is empty and I can't push a file to the sdcard because I don't know how to reference the right path.
I tried flashing a TWRP recovery.img file to the recovery partition, and it indicated success. But when I boot into recovery it looks exactly like it did before. I get no TWRP gui interface. The TWRP app has no official build for this device, so is unusable. I also tried installing Magisk but got errors and just uninstalled it.
Frankly I don't know what to do yet. I'm not sure the device is officially 'rooted' or not. I'm not sure what to do next. Do I flash an Enigma Android 6 image? Do I have to do that before I can update to Android 9?
dixonge said:
I'm not completely brand new to flashing with custom roms,.........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at the following TWRP thread that's specific to your device and variants. Don't be afraid to ask for some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3616589
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
Ibuprophen said:
I don't have this device but, your best bet is to take a look at the following TWRP thread that's specific to your device and variants. Don't be afraid to ask for some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3616589
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
Click to expand...
Click to collapse
Yes, that's where I got my twrp recovery.img file from. I'll go back through those steps and ask in the thread if I have further issues. Thanks.
Typically there is a reboot into system after flashing twrp. Some stock ROM replace twrp with stock recovery in that case.
Known workarounds:
Flash twrp to boot partition also
Remove battery after flashing twrp
Use windows Odin and unchecked reboot
Do some key tricks to force recovery during reboot.
Once twrp booted, it normally does tricks to not get overwritten.
Asgard holds your answer
dixonge said:
I'm not completely brand new to flashing with custom roms, but I sometimes go 2-3 years running stock, so when I do come back I have forgotten everything and it feels like starting over.
So far I have achieved the following:
1 - backed up device
2 - reset device back to stock
3 - flashed stock image using Heimdall
Unfortunately after all that I am not sure if I have made any progress. It just took my phone back to factory settings.. My storage is full, my SDCard is empty and I can't push a file to the sdcard because I don't know how to reference the right path.
I tried flashing a TWRP recovery.img file to the recovery partition, and it indicated success. But when I boot into recovery it looks exactly like it did before. I get no TWRP gui interface. The TWRP app has no official build for this device, so is unusable. I also tried installing Magisk but got errors and just uninstalled it.
Frankly I don't know what to do yet. I'm not sure the device is officially 'rooted' or not. I'm not sure what to do next. Do I flash an Enigma Android 6 image? Do I have to do that before I can update to Android 9?
Click to expand...
Click to collapse
OK, bad jokes about Nordic deities aside. Try using ODIN rather than Heimdall to flash TWRP. In ODIN, make sure the automatic reboot on exit feature is turned OFF. After exiting ODIN, MANUALLY reboot the thing into recovery mode using whatever multiple button combination is required, and you "should" find it starting up TWRP for you. ASSUMING that is so, then power off the device and re-start it. it "should" now be working correctly, meaning with whatever ROM you have in place and TWRP as the recovery. And if THAT worked, you can flash SU using TWRP if you are not already rooted and you are good to go. Good Luck.
I now have managed to finally get TWRP flashed. It worked this time. Could not begin to tell you what I did differently...
I managed to flash the custom ROM and am now dealing with two remaining issues - a password I am being asked for that I never set, and getting the right version of opengapps flashed.
nezlek said:
OK, bad jokes about Nordic deities aside. Try using ODIN rather than Heimdall to flash TWRP. In ODIN, make sure the automatic reboot on exit feature is turned OFF. After exiting ODIN, MANUALLY reboot the thing into recovery mode using whatever multiple button combination is required, and you "should" find it starting up TWRP for you. ASSUMING that is so, then power off the device and re-start it. it "should" now be working correctly, meaning with whatever ROM you have in place and TWRP as the recovery. And if THAT worked, you can flash SU using TWRP if you are not already rooted and you are good to go. Good Luck.
Click to expand...
Click to collapse
FYI - the only version of Odin I could find for Linux is a glitchy Java version. All the tutorials say to put things in the 'AP Slot' - and I can clearly see that in screenshots. But my version didn't have an AP slot. The graphics were misaligned and I finally gave up. I did manage to flash a ROM using ADB sideload. So there's that.
ODIN for Linux ....
dixonge said:
FYI - the only version of Odin I could find for Linux is a glitchy Java version. All the tutorials say to put things in the 'AP Slot' - and I can clearly see that in screenshots. But my version didn't have an AP slot. The graphics were misaligned and I finally gave up. I did manage to flash a ROM using ADB sideload. So there's that.
Click to expand...
Click to collapse
Yeah, Odin can be more than a little bit "glitchy" on Linux boxes. Surprised you found one that worked at all, to be totally candid. I suggest to folks that they just beg, borrow, or steal 15 minutes on a Windows box and do it the easy way. Yes, I know "windows" is a very long "four letter word" in many circles, but sometimes you just bite the bullet and take the path of least resistance. The IMPORTANT question is: is your problem solved ??
nezlek said:
Yeah, Odin can be more than a little bit "glitchy" on Linux boxes. Surprised you found one that worked at all, to be totally candid. I suggest to folks that they just beg, borrow, or steal 15 minutes on a Windows box and do it the easy way. Yes, I know "windows" is a very long "four letter word" in many circles, but sometimes you just bite the bullet and take the path of least resistance. The IMPORTANT question is: is your problem solved ??
Click to expand...
Click to collapse
Good question. Do I have LineageOS on my device? Yes.
Is it a usable version? Uh, no. My device is now reporting to be a Galaxy J7 and the WiFi is useless. This was from an Enigma ROM. So at least I have managed to figure out how to flash the device and TWRP recovery is working. Now to find a better ROM.
I guess the question I have now is this: *IS THERE* an actual, working Android 9 PIE ROM for the J2 Prime (Grand Prime+) model?
dixonge said:
Good question. Do I have LineageOS on my device? Yes.
Is it a usable version? Uh, no. My device is now reporting to be a Galaxy J7 and the WiFi is useless. This was from an Enigma ROM. So at least I have managed to figure out how to flash the device and TWRP recovery is working. Now to find a better ROM.
I guess the question I have now is this: *IS THERE* an actual, working Android 9 PIE ROM for the J2 Prime (Grand Prime+) model?
Click to expand...
Click to collapse
Hui. Quick search in XDA shows: there is probably no aosp based ROM for your device. So you flashed a ROM for a different device? You should learn a bit about model names and codenames. And be glad to not have bricked your phone.
kurtn said:
Hui. Quick search in XDA shows: there is probably no aosp based ROM for your device. So you flashed a ROM for a different device? You should learn a bit about model names and codenames. And be glad to not have bricked your phone.
Click to expand...
Click to collapse
Well, it's from here on XDA, and it was advertised as being ported for my model specifically. Just surprised to see the other model info in 'About' - I agree that Pie seems to be non-existent for this phone. What about Oreo? So far every single article I find on the 'net is just click-bait.
Sometimes it is better to stay on stock ROM. With twrp you can install magisk or xposed or nanodroid.
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.
Just as I asked. I would like to know if anyone has made GSI work or at least tried (like me) to make it work.
RandoMike said:
Just as I asked. I would like to know if anyone has made GSI work or at least tried (like me) to make it work.
Click to expand...
Click to collapse
Update: It IS possible to install Lineage OS GSI on the G8 Play. However, you will trigger a security error (nothing critical, since your phone will still boot up). To install it, you really need to flash the One Macro Firmware (evidently, your device can hard brick, but it's possible to fix it ). Later, you can flash the Lineage rom through fastboot.
Even though it's possible to install it and even boot it, the rom is buggy. It would be wonderful if anyone who knows better developing than me would work on this device, which has been abandoned for so long...
Some bugs of this rom are:
Fingerprint sensor sometimes triggers volume up or down.
The screen is not well adjusted, picture seems weird.
Dm-verity error which will not allow the phone to boot unless you press the power button again.
Bluetooth audio not working.
I have not tested the rom completely yet. However, I would like to get this forum revived again, with the possibility of "messing up" with the phone. It's not impossible, it just needs some attention
You can flash a blank vbmeta image to disable security error this may help with some issues. good luck and thanks for your contribution to the device forum. (also, sorry for bad english)
Ale001 said:
You can flash a blank vbmeta image to disable security error this may help with some issues. good luck and thanks for your contribution to the device forum. (also, sorry for bad english)
Click to expand...
Click to collapse
I already tried that on the official ROM and it didn't work. I only get a DM-Verity error amd a bootloop when trying to boot Lineage, which can be solved if flashing the stock ROM again.
It's possible install a arm-ab gsi or I need to install one macro arm64 firmware first?
Ale001 said:
It's possible install a arm-ab gsi or I need to install one macro arm64 firmware first?
Click to expand...
Click to collapse
It didn't work for me on stock firmware. Lineage GSI worked for me on One Macro's ROM