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 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?
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
tnsmani said:
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
Click to expand...
Click to collapse
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
the_mentor said:
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
Click to expand...
Click to collapse
You will need to replace the main board if the issue persist.
Same problem here
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
New geek said:
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
Click to expand...
Click to collapse
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
try using msm v3.0 tool fixes most problems not hardware though
the_mentor said:
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
Click to expand...
Click to collapse
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
New geek said:
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
Click to expand...
Click to collapse
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
what you will need to do is download the oneplus 3 recovery tool and put the phone into qualcolm mode and restore the phone that way. here is a link https://www.androidexplained.com/oneplus-3-unbrick-return-stock/
New geek said:
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
Click to expand...
Click to collapse
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
the_mentor said:
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
Click to expand...
Click to collapse
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
tnsmani said:
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
Click to expand...
Click to collapse
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
Please share the guide as I am also suffering with same problem.
Still not working
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
I was about to update here with good news but wife's phone went back to restart loop the next day. I am not sure but probably triggered by her installing whatsapp and facebook. I put the phone away because I have already spend quite a lot of time behind this. Is your's still going? Please list the step by step procedure. Thanks
download from here https://mega.nz/#!zsdnkCDA!UyJRwbJK6kHTDpmesBYao0knaOTwbgu4dSiokV1XLYU then turn off phone run tool,connect phone with volume up pressed,should have a com in the list if so just click start thats it and wait for it to turn green or device restart
First of all, this is a repost from the sub forum Guides, I mis-posted on there, I apologize: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-flash-partition-image-t4190103
(Mods, you may remove my other thread, thank you)
Hello, Recently I discovered that my Pixel 3 XL couldn't use widevine L1. And I did some research and they said it's probably the persist.img. (Thread: https://forum.xda-developers.com/pix...ne-l1-t4183011 ).
And today comparing my pixel 3 XL with my pixel 3 a I found out that my Pixel 3 XL doesn't have secure boot enabled and doesn't have NOS- production (idk what they mean but looks pretty important).
What I'm asking is if anyone could tell me how to correctly flash my device to get those back (and hopefully get widevine L1?). So far I've used Google website flash tool, if I'll have to use adb can someone tell how to do it exactly?
Ty.
Images of both phones fastboot mode info:
https://photos.app.goo.gl/Wj1Vudi8fasbpXfk6
https://photos.app.goo.gl/wbpGg2RyXEmn8aFSA
xDontStarve said:
First of all, this is a repost from the sub forum Guides, I mis-posted on there, I apologize: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-flash-partition-image-t4190103
(Mods, you may remove my other thread, thank you)
Hello, Recently I discovered that my Pixel 3 XL couldn't use widevine L1. And I did some research and they said it's probably the persist.img. (Thread: https://forum.xda-developers.com/pix...ne-l1-t4183011 ).
And today comparing my pixel 3 XL with my pixel 3 a I found out that my Pixel 3 XL doesn't have secure boot enabled and doesn't have NOS- production (idk what they mean but looks pretty important).
What I'm asking is if anyone could tell me how to correctly flash my device to get those back (and hopefully get widevine L1?). So far I've used Google website flash tool, if I'll have to use adb can someone tell how to do it exactly?
Ty.
Images of both phones fastboot mode info:
https://photos.app.goo.gl/Wj1Vudi8fasbpXfk6
https://photos.app.goo.gl/wbpGg2RyXEmn8aFSA
Click to expand...
Click to collapse
Hello,
You can factory flash your device using factory images for Pixel 3 XL, located on google website:
https://developers.google.com/android/images#crosshatch
@Homeboy76 wrote a guide on how to (screw up ) do things with the Pixel 3 XL and flashing factory images is a part of it:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-root-pixel-3-xl-android-11-r-t4160447/
Scroll to this part:
4. Install/Update Factory Image keep or wipe data
It involves unlocking the bootloader.
Read, learn and do it. If you're not confident doing it, try to find someone who is, because you can brick it.
But we'll, I'm a n00b and I haven't killed yet. So I bet you'll figure it out too. :good:
Good luck...
Sébastien.
5.1 said:
Hello,
You can factory flash your device using factory images for Pixel 3 XL, located on google website:
https://developers.google.com/android/images#crosshatch
@Homeboy76 wrote a guide on how to (screw up ) do things with the Pixel 3 XL and flashing factory images is a part of it:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-root-pixel-3-xl-android-11-r-t4160447/
Scroll to this part:
4. Install/Update Factory Image keep or wipe data
It involves unlocking the bootloader.
Read, learn and do it. If you're not confident doing it, try to find someone who is, because you can brick it.
But we'll, I'm a n00b and I haven't killed yet. So I bet you'll figure it out too. :good:
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hello, thanks for your reply, will this remove all partitions and reinstall all of them? I just wanna make sure it does remove everything.
5.1 said:
Hello,
You can factory flash your device using factory images for Pixel 3 XL, located on google website:
https://developers.google.com/android/images#crosshatch
@Homeboy76 wrote a guide on how to (screw up ) do things with the Pixel 3 XL and flashing factory images is a part of it:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-root-pixel-3-xl-android-11-r-t4160447/
Scroll to this part:
4. Install/Update Factory Image keep or wipe data
It involves unlocking the bootloader.
Read, learn and do it. If you're not confident doing it, try to find someone who is, because you can brick it.
But we'll, I'm a n00b and I haven't killed yet. So I bet you'll figure it out too. :good:
Good luck...
Sébastien.
Click to expand...
Click to collapse
ROTFLMAO, needed a good laugh.
Stay safe!
xDontStarve said:
Hello, thanks for your reply, will this remove all partitions and reinstall all of them? I just wanna make sure it does remove everything.
Click to expand...
Click to collapse
Hello,
You can check what's inside the factory image by opening it with winzip, 7zip, winrar, etc...
I haven't found the part talking about the persist partition in this thread you pointed to: https://forum.xda-developers.com/pixel-3-xl/how-to/widevine-l1-t4183011/
The link you provided in the OP is broken by the way...
Where did you see people talking about it..?
I found this one: https://forum.xda-developers.com/pixel-3-xl/help/widevine-level-3-drm-stock-locked-t3923766
Nobody back then (including knowleadgeable dudes) was able to fix it...
I have never dealt with the persist partition, so i can't be of much help with that. But be careful, it contains a bunch of crap, device related... Such as: sensors, camera, display, etc... So you could end up with a dumbphone!
Good luck though...
Sébastien.
Homeboy76 said:
ROTFLMAO, needed a good laugh.
Stay safe!
Click to expand...
Click to collapse
Hey,
Sup? Glad it did the trick!
Still, your guides are pretty good!
Cheers...
Sébastien.
5.1 said:
Hello,
You can check what's inside the factory image by opening it with winzip, 7zip, winrar, etc...
I haven't found the part talking about the persist partition in this thread you pointed to: https://forum.xda-developers.com/pixel-3-xl/how-to/widevine-l1-t4183011/
The link you provided in the OP is broken by the way...
Where did you see people talking about it..?
I found this one: https://forum.xda-developers.com/pixel-3-xl/help/widevine-level-3-drm-stock-locked-t3923766
Nobody back then (including knowleadgeable dudes) was able to fix it...
I have never dealt with the persist partition, so i can't be of much help with that. But be careful, it contains a bunch of crap, device related... Such as: sensors, camera, display, etc... So you could end up with a dumbphone!
Good luck though...
Sébastien.
Hey,
Sup? Glad it did the trick!
Still, your guides are pretty good!
Cheers...
Sébastien.
Click to expand...
Click to collapse
That is the thread I was talking about!
So apparently I won't be able to get it back.
But what bothers me is the secure BOOT and NOS production thing.
I'll try to attach the two images.
Also what I meant with if it would erase all was if doing those adb commands would my storage get cleaned of stuff.
https://ibb.co/mN8dwHm
https://ibb.co/j5WYLFT
xDontStarve said:
Hello, thanks for your reply, will this remove all partitions and reinstall all of them? I just wanna make sure it does remove everything.
Click to expand...
Click to collapse
xDontStarve said:
That is the thread I was talking about!
So apparently I won't be able to get it back.
But what bothers me is the secure BOOT and NOS production thing.
I'll try to attach the two images.
Also what I meant with if it would erase all was if doing those adb commands would my storage get cleaned of stuff.
https://ibb.co/mN8dwHm
https://ibb.co/j5WYLFT
Click to expand...
Click to collapse
Hello,
Well,
I don't know what triggered this message, mine shows secure and NOS = Production.
I wonder why you have:
"Debug Policy(a):" enabled(in-list)
"Debug Policy(b):" enabled(in-list)
Never seen those.
About your datas... Well, if you read Homeboy76 guide (which you obviously didn't) , you'd have noticed this part:
4. Install/Update Factory Image keep or wipe data
Which is pretty straightforward. You can either flash a factory image with or without formatting the Data (user partition).
Well, to flash the factory image, you'll have to unlock the bootloader again. So it'll wipe your Datas anyway! :good:
Backup everything!
Also, no ADB involved. You unzip the factory image. Open the folder and click twice "flash-all.bat" (assuming you use Windows). It will install everything and let you know when it's done.
Everything is explained I'm the guide i linked you earlier...
If you take that route, let me know if this message about "Debug Policy" disappear please?!
Good luck...
Sébastien.
5.1 said:
Hello,
Well,
I don't know what triggered this message, mine shows secure and NOS = Production.
I wonder why you have:
"Debug Policy(a):" enabled(in-list)
"Debug Policy(b):" enabled(in-list)
Never seen those.
About your datas... Well, if you read Homeboy76 guide (which you obviously didn't) , you'd have noticed this part:
4. Install/Update Factory Image keep or wipe data
Which is pretty straightforward. You can either flash a factory image with or without formatting the Data (user partition).
Well, to flash the factory image, you'll have to unlock the bootloader again. So it'll wipe your Datas anyway! :good:
Backup everything!
Also, no ADB involved. You unzip the factory image. Open the folder and click twice "flash-all.bat" (assuming you use Windows). It will install everything and let you know when it's done.
Everything is explained I'm the guide i linked you earlier...
If you take that route, let me know if this message about "Debug Policy" disappear please?!
Good luck...
Sébastien.
Click to expand...
Click to collapse
I just flashed everything and I still have the same policy thing and the SECURE BOOT: none and NOS production no =(
Does anyone know what those are and will they affect my device's performance?
xDontStarve said:
I just flashed everything and I still have the same policy thing and the SECURE BOOT: none and NOS production no =(
Does anyone know what those are and will they affect my device's performance?
Click to expand...
Click to collapse
Hi,
So you unlocked > flashed factory image > rebooted system > relocked the bootloader > rebooted > disabled OEM unlocking in developer options > rebooted in bootloader > and you still see the same thing?!
"Debug Policy(a):" enabled(in-list)
"Debug Policy(b):" enabled(in-list)
Both or just one? A or B?
Well, can you boot in bootloader again and try this:
You have something like: "active slot = a or b"
Issue this command:
fastboot --set-active=a
or
fastboot --set-active=b
Whichever is NOT the one active. If "a" is active, set the active=b and set active=a if b is active.
Reboot in bootloader > flash factory.image again. reboot system > relock the bootloader > reboot system > disabled OEM unlocking in developer options > reboot in bootloader > and see if that changes anything.
Then se are ideas that won't harm your device (co Sider Inc your u do it well0, but I can't guarantee it will solve your issue. If something is messed up on the other slot, it "could" eventually trigger the things you see in the booth after screen...
Otherwise, it shouldn't affect your device's performance.
When you boot your device with a locked bootloader, do you still have a warning that it can't be verified?
Good luck...
Sébastien.
5.1 said:
Hi,
So you unlocked > flashed factory image > rebooted system > relocked the bootloader > rebooted > disabled OEM unlocking in developer options > rebooted in bootloader > and you still see the same thing?!
"Debug Policy(a):" enabled(in-list)
"Debug Policy(b):" enabled(in-list)
Both or just one? A or B?
Well, can you boot in bootloader again and try this:
You have something like: "active slot = a or b"
Issue this command:
fastboot --set-active=a
or
fastboot --set-active=b
Whichever is NOT the one active. If "a" is active, set the active=b and set active=a if b is active.
Reboot in bootloader > flash factory.image again. reboot system > relock the bootloader > reboot system > disabled OEM unlocking in developer options > reboot in bootloader > and see if that changes anything.
Then se are ideas that won't harm your device (co Sider Inc your u do it well0, but I can't guarantee it will solve your issue. If something is messed up on the other slot, it "could" eventually trigger the things you see in the booth after screen...
Otherwise, it shouldn't affect your device's performance.
When you boot your device with a locked bootloader, do you still have a warning that it can't be verified?
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hello, so if the one active is a I should try b, and if the curent active is b, I shall try a?
Will I lose any data doing this? Also can I do this with a locked bootloader?
My current boot slot is b.
I have both debug policies enabled.
EDIT: I just did what u said but instead of flashing factory.img i used flash all, does that work?
EDIT 2: After setting boot slot to a, I checked after flashing, it's back again to slot b!!! ??
xDontStarve said:
Hello, so if the one active is a I should try b, and if the curent active is b, I shall try a?
Will I lose any data doing this? Also can I do this with a locked bootloader?
My current boot slot is b.
I have both debug policies enabled.
EDIT: I just did what u said but instead of flashing factory.img i used flash all, does that work?
EDIT 2: After setting boot slot to a, I checked after flashing, it's back again to slot b!!! ??
Click to expand...
Click to collapse
Hello,
I don't know what factory.img is?!
Did you follow the flashing procedure explained in the guide?
Now you're on slot b again, run flash-all.bat again. So you'll have both slots flashed = nothing left from old installs.
You used latest factory image right? November 2020?
Good luck...
Sébastien.
5.1 said:
Hello,
I don't know what factory.img is?!
Did you follow the flashing procedure explained in the guide?
Now you're on slot b again, run flash-all.bat again. So you'll have both slots flashed = nothing left from old installs.
You used latest factory image right? November 2020?
Good luck...
Sébastien.
Click to expand...
Click to collapse
I followed your steps, the messages are still showing with no secure boot and widevine L3, I'm stressing now, I think
Do you think doing downgrading to Pie would help? I've read from other thread about sensor bug (which is persist) and they could fix it with an android pie downgrade.
xDontStarve said:
I followed your steps, the messages are still showing with no secure boot and widevine L3, I'm stressing now, I think
Do you think doing downgrading to Pie would help? I've read from other thread about sensor bug (which is persist) and they could fix it with an android pie downgrade.
Click to expand...
Click to collapse
Hello,
I have no clue to be honest...
You have seen the thread talking about people being stuck with P3... No one knows exactly how it happened.
You could try, i don't know, i have never downgraded a Pixel 3 XL.
I think I told you everything I had in mind. Sorry it didn't work.
Good luck...
Sébastien.
5.1 said:
Hello,
I have no clue to be honest...
You have seen the thread talking about people being stuck with P3... No one knows exactly how it happened.
You could try, i don't know, i have never downgraded a Pixel 3 XL.
I think I told you everything I had in mind. Sorry it didn't work.
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hey, It's ok. I think I'll just stick with this, And ill watch netflix on my pc instead. Thanks for helping!!!!
xDontStarve said:
Hey, It's ok. I think I'll just stick with this, And ill watch netflix on my pc instead. Thanks for helping!!!!
Click to expand...
Click to collapse
Hey,
Check this: https://forum.xda-developers.com/android/apps-games/netflix-hd-widevine-l1-device-t3942467
https://github.com/longseespace/netflix_patch
Not a real fix though...
Cheers...
Sébastien.
I have the same debug policy error on my pixel 4a. These steps didn't solve the issue. But it was worth the try.
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.