Related
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
RiskTaker10 said:
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Click to expand...
Click to collapse
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Puddi_Puddin said:
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Click to expand...
Click to collapse
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
RiskTaker10 said:
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
Click to expand...
Click to collapse
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
hrishikeshgramani said:
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
Click to expand...
Click to collapse
Unfortunately that is out of the question, there is no Service Center for Oneplus where I live so I cant get it checked ASAP
Puddi_Puddin said:
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
Click to expand...
Click to collapse
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
RiskTaker10 said:
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
Click to expand...
Click to collapse
You can always try..
Puddi_Puddin said:
You can always try..
Click to expand...
Click to collapse
Okay thanks good citizen of XDA I'll try to flash a custom rom and I'll try to report back here ASAP
Is it possibleto flash the Lineage treble rom to mi A2 lite?
I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.
BubuXP said:
I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.
Click to expand...
Click to collapse
As far as i understood treble, it is only the vendor partition which is not flashed. So you would still need a LOS compatible kernel to flash (or you are lucky and the original kernel works). Also, LOS needs to be adjusted for specific things on this phone (like resolution, dpi, options to show up in settings, avaiable ram/storage, etc).
So we have to wait until xiaomi or a proper dev releases a kernel source. It would probably also be possible to adjust the build environment to fit the original kernel.
Or did i understand sth wrong here?
edit:
Flashing GSI's should work, it is a nice way to have another rom with more features on the device, but it is not a homebuilt n optimized rom (probably similar perf/battery to stock).
treble gsi rom don't need the vendor partition that's what makes treble great . you just flash the gsi rom into system on a treble compatible device
Hi
sgi ab images works (does not handle well rounded corners as icons are a bit near corners) but works
lineage booted. I will test and report
Both Lineage and RR boots but they are laggy. Camera quality is quite bad.
Both can be used as daily drivers
*can not handle well rounded corners as max-232 said
BubuXP said:
I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.
Click to expand...
Click to collapse
fastboot erase system
fastboot -u flash system name_of_system.img
The Xiaomi MI A2 Lite stock comes compatible with treble, has it been tested with an image of Androoid 9?
menphis said:
The Xiaomi MI A2 Lite stock comes compatible with treble, has it been tested with an image of Androoid 9?
Click to expand...
Click to collapse
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted
max-232 said:
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted
Click to expand...
Click to collapse
What SGI you use?
forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-9-0-phh-treble-t3831915
This above
max-232 said:
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted
Click to expand...
Click to collapse
max-232 said:
forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-9-0-phh-treble-t3831915
This above
Click to expand...
Click to collapse
I recently received my A2 Lite, because you do not test the next one that is more stable, as everything works: https://androidfilehost.com/?fid=5862345805528067642
All the files:
https://androidfilehost.com/?w=files&flid=280192
How can flash these post zips with out twrp?
I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.
mortmaru said:
I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.
Click to expand...
Click to collapse
I don't think what happening right now is dead, it is still very active and you can flash Lineage or RR if you want
For a few weeks old phone, i consider this as reasonable
mortmaru said:
I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.
Click to expand...
Click to collapse
This device is new, barely has a month that went on the market, also comes with factory Oreo, also Android 9 came out a few days ago official ...
What development do you need urgently?
menphis said:
This device is new, barely has a month that went on the market, also comes with factory Oreo, also Android 9 came out a few days ago official ...
What development do you need urgently?
Click to expand...
Click to collapse
Some custom roms the base version is awful it is missing so much you cant even backup all stuff from miui to this even app data doesn't transfer over using googles so called backup
With it being month old i expected modded versions even if it was based on the current andriod one loaded with new look bunch of extra options
Can anyone confirm if on AOSP/LOS systems notification LED od still single color (white only)?
Doman said:
Can anyone confirm if on AOSP/LOS systems notification LED od still single color (white only)?
Click to expand...
Click to collapse
It's impossible to have other colors on mi a2, as the phisical LED is only white, not rgb
Another month passes and still nothing.
Hopefully some one will come up with something soon even the official updates for this phone are really slow
Tried installing a few GSI 10 and 9 ROMs, didn't work at all, got them to bootanimation at best, since there's no TWRP yet I had to do it all on fastboot, here's my logcat if anyone can help me boot this thing
VyktorJonas said:
Tried installing a few GSI 10 and 9 ROMs, didn't work at all, got them to bootanimation at best, since there's no TWRP yet I had to do it all on fastboot, here's my logcat if anyone can help me boot this thing
Click to expand...
Click to collapse
Well long time since your post. And nobody responding. This advice is not confirmed , as I don't have device yet. But this phone has vbmeta partition, so chances are, you need to flash vbmeta with disable-verity.
I don't remember the exact format right now. But you can simply Google that. ??
VyktorJonas said:
Tried installing a few GSI 10 and 9 ROMs, didn't work at all, got them to bootanimation at best, since there's no TWRP yet I had to do it all on fastboot, here's my logcat if anyone can help me boot this thing
Click to expand...
Click to collapse
install the rom of one macro on it after that boots the blank flash of one macro then it will restart directly on the bootloader and without restarting apply the rom again of one macro and that's it, from there vice you can install gsi arm64 s difficulties
if you apply the wrong commands in the hira to oassar the rom it will bootloop.
sorry english, using google translator from portuguese to english is awful
Hello everyone, Im trying to understand how to flash a GSI img ROM (I want to try AOSP stock, or Havoc OS) but, I saw some posts and looks like is a bit hard to do.
I had TWRP installed (unofficial begonia) and magisk installed.
some informations I found: this device is just A slot supported
What exactly I need?
Orange Fox recovery?
Before flash need to disable something in recovery?
A arm64 slot IMG?
And gapps?
What are the steps?
Im waiting your answer
So far with my personal experience trying to flash Lineage 17 GSI on my RN8Pro and have had no luck. Lost baseband and both imei #'s in the process too (still trying to figure out how to restore).
Finally was lucky!
Flash LR Team TWRP:
https://mega.nz/#!B75xWQQQ!8DQdy09luHihxCziRX7ywUWkAwmAahjnWOQDgHxcTPA
Enable debugging and make sure computer has permission to use
On command promp adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot (immediately disconnect phone and hold volume up)
In twrp go to advanced and Select "Close AVB2.0" swipe to confirm
Go back to twrp home -> Wipe -> Format
Flash gsi
And presto!
I just flashed Lineage 17 GSI as of now I wouldn't recommend it. Fixing to flash ASOP 10 GSI from phhusson see if it is any better!
Also as a favor since I lost baseband and imei for my phone could you please create a backup through twrp of your nvram and nvdata and PM it to me?
If you need any help just pm me!
JuanM2020 said:
Finally was lucky!
Flash LR Team TWRP:
https://mega.nz/#!B75xWQQQ!8DQdy09luHihxCziRX7ywUWkAwmAahjnWOQDgHxcTPA
Enable debugging and make sure computer has permission to use
On command promp adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot (immediately disconnect phone and hold volume up)
In twrp go to advanced and Select "Close AVB2.0" swipe to confirm
Go back to twrp home -> Wipe -> Format
Flash gsi
And presto!
I just flashed Lineage 17 GSI as of now I wouldn't recommend it. Fixing to flash ASOP 10 GSI from phhusson see if it is any better!
Also as a favor since I lost baseband and imei for my phone could you please create a backup through twrp of your nvram and nvdata and PM it to me?
If you need any help just pm me!
Click to expand...
Click to collapse
What problems were there with the los 17 gsi?
Please share what's working on the GSI ROM and what's not. Thank you.
polfrank said:
What problems were there with the los 17 gsi?
Click to expand...
Click to collapse
Off the bat, Bluetooth did not work it just kept giving a Bluetooth has stopped message. Didn't have face unlock. Screen would suddenly flash as if display were damaged and would suddenly freeze when opening stock apps. And a few other things I don't remember as I already flash off of it.
Helhound0 said:
Please share what's working on the GSI ROM and what's not. Thank you.
Click to expand...
Click to collapse
I've flashed Havoc OS 2.9 GSI and after resizing and disabling HW overlays the ROM works near perfectly albeit some camera issues.
JuanM2020 said:
Finally was lucky!
Flash LR Team TWRP:
https://mega.nz/#!B75xWQQQ!8DQdy09luHihxCziRX7ywUWkAwmAahjnWOQDgHxcTPA
Enable debugging and make sure computer has permission to use
On command promp adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot (immediately disconnect phone and hold volume up)
In twrp go to advanced and Select "Close AVB2.0" swipe to confirm
Go back to twrp home -> Wipe -> Format
Flash gsi
And presto!
I just flashed Lineage 17 GSI as of now I wouldn't recommend it. Fixing to flash ASOP 10 GSI from phhusson see if it is any better!
Also as a favor since I lost baseband and imei for my phone could you please create a backup through twrp of your nvram and nvdata and PM it to me?
If you need any help just pm me!
Click to expand...
Click to collapse
Of course and thanks dude. In a few hours i will attach the files.
yayimathrowaway said:
I've flashed Havoc OS 2.9 GSI and after resizing and disabling HW overlays the ROM works near perfectly albeit some camera issues.
Click to expand...
Click to collapse
Newbie here. Please let me know what is it for and how to "resizing and disabling HW overlays"
yayimathrowaway said:
I've flashed Havoc OS 2.9 GSI and after resizing and disabling HW overlays the ROM works near perfectly albeit some camera issues.
Click to expand...
Click to collapse
That sounds good. Thanks for sharing. Did you use GSI since you flashed or did you restore MIUI?
Sorry for my ignorance, but what is a GSI ROM?
montechristos1 said:
Sorry for my ignorance, but what is a GSI ROM?
Click to expand...
Click to collapse
Generic System Image. Basically a single ROM image that should technically work in any device running Android 8.1 or newer. It contains the generic AOSP (Pure android) source.
Helhound0 said:
Generic System Image. Basically a single ROM image that should technically work in any device running Android 8.1 or newer. It contains the generic AOSP (Pure android) source.
Click to expand...
Click to collapse
Thanks.
So people were able to flash LOS GSI on their Redmi Note PRO?
No specific thread for this?
(I am one of the people that are waiting for one of the custom open-source ROMs to replace the (ihmo) horrible MUI)
MarkLev said:
Newbie here. Please let me know what is it for and how to "resizing and disabling HW overlays"
Click to expand...
Click to collapse
Disabling HW Overlays means that your GPU is the only thing that will handle all of the graphics on your phone. If this is not on in some GSI ROMs the screen will flicker when it's about to go to sleep and at other random times. It can be accessed in Developer options.
Additionally, as this is a GSI made to work on many different phones, the proportions on the screen are off when you first install it. On Havoc, all of the resizing options are in Havoc Settings. In other ROMs without customization options, there are ADB commands that can resize your ROM. Specifically, the problems I initially experienced were involving the status bar icons and clock only partially being on the screen.
---------- Post added at 07:57 AM ---------- Previous post was at 07:46 AM ----------
Helhound0 said:
That sounds good. Thanks for sharing. Did you use GSI since you flashed or did you restore MIUI?
Click to expand...
Click to collapse
I am actually using the GSI right now. I didn't restore MIUI because I just did not like it. I think I'll stay on this GSI. Again, after some modifications in Settings, the ROM I'm using works near perfectly.
The cameras, of course, are kind of messed up though. No matter what camera app I use I cannot access the 64MP camera and anything other than the camera app that came with the GSI (which is pretty bad) randomly flickers the screen while I'm taking a picture or recording a video, even after disabling HW Overlays in Developer Options. Maybe could be fixed by flashing a third party camera app as a system app.
Other than that, no problems whatsoever.
---------- Post added at 08:04 AM ---------- Previous post was at 07:57 AM ----------
KonahZave said:
Hello everyone, Im trying to understand how to flash a GSI img ROM (I want to try AOSP stock, or Havoc OS) but, I saw some posts and looks like is a bit hard to do.
I had TWRP installed (unofficial begonia) and magisk installed.
some informations I found: this device is just A slot supported
What exactly I need?
Orange Fox recovery?
Before flash need to disable something in recovery?
A arm64 slot IMG?
And gapps?
What are the steps?
Im waiting your answer
Click to expand...
Click to collapse
If you still need some help, I have a full guide on how to flash here
yayimathrowaway said:
I am actually using the GSI right now. I didn't restore MIUI because I just did not like it. I think I'll stay on this GSI. Again, after some modifications in Settings, the ROM I'm using works near perfectly.
The cameras, of course, are kind of messed up though. No matter what camera app I use I cannot access the 64MP camera and anything other than the camera app that came with the GSI (which is pretty bad) randomly flickers the screen while I'm taking a picture or recording a video, even after disabling HW Overlays in Developer Options. Maybe could be fixed by flashing a third party camera app as a system app.
Other than that, no problems whatsoever.
Click to expand...
Click to collapse
I don't really mind the cameras not working at a 100% tbh since i don't use them that much. However did you try GCam on GSI or any other API2 camera app?
Helhound0 said:
I don't really mind the cameras not working at a 100% tbh since i don't use them that much. However did you try GCam on GSI or any other API2 camera app?
Click to expand...
Click to collapse
Yeah, but the screen flashes randomly on them.
CameraMX works great with the cameras that it does support. CameraF5-V crashes randomly. GCam for RN8P can only take photos, and only supports 2 cameras. I think that some of these issues would be fixed if I flashed then as system apps, because the stock camera app works fine, albeit the fact that it's just not a very good camera app.
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.