Develop Bugs

Never never an Lg again

I like lg's hardware. I had optimus 3d and now have optimus g. Both has great hardware.
I have flashed custom roms since windows mobile days, so i should have a little experience..!
But you can never be sure to flash safely especially with Lg. You can loose your imei, baseband...etc
And now i have kernel crash on my loved optimus g... A demogod kernel crash. I can boot in cwm but cant restore system. It restore boot and then system restoring fails. I can also boot in android and after a few seconds it crashes. So it doesnt stay long enough to be fx recognized by pc to save it. Pc doesnt recognize it even in download mode. I will also try with another pc.
You dont have such problems with htc or samsung. The problems with these phones arent so complicated like lg.
SO NEVER AN LG AGAIN...

What about side loading rom? Phones with external sd cards are great in such moments.
Sent from my LG-E975 using XDA Premium 4 mobile app

nchc said:
What about side loading rom? Phones with external sd cards are great in such moments.
Sent from my LG-E975 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I need to try it on another pc, as i said my pc cant see the phone. But it doesnt chage the truth about such problems with Lg.

yup, why not when you mess up the phone and cant do any thing about it, lets rock the blame game..
lu6200 to su640 to lte2 to optimus g to optimus g pro.... never had any issues and never will buy anything else.

You can't blame LG for a mishandeling YOU made.
I had HTC's and Samsung in the past, they all present a "bricking" potential if you start to fool around with Kernel, custom rom, etc.
Now, you should try to restore it back to stock to see if it fixes your issues.

t1mman said:
You can't blame LG for a mishandeling YOU made.
I had HTC's and Samsung in the past, they all present a "bricking" potential if you start to fool around with Kernel, custom rom, etc.
Now, you should try to restore it back to stock to see if it fixes your issues.
Click to expand...
Click to collapse
You should read my post again...
Yes i will try stock rom but i think i have read somewhere that some still has it even after stock rom...

niyazidk said:
You should read my post again...
Yes i will try stock rom but i think i have read somewhere that some still has it even after stock rom...
Click to expand...
Click to collapse
Yes, I've read your post: You've flashed a custom rom and now get a kernel error.
Go back to stock in download mode using KDZ updater and you should be ok.
Follow this guide to the letter:
http://forum.xda-developers.com/showthread.php?t=2010624
And, as I already told, LG can't be blame for anything other than running stock. Even if you only root the device and crash it, you can't blame em for this.

t1mman said:
Yes, I've read your post: You've flashed a custom rom and now get a kernel error.
Go back to stock in download mode using KDZ updater and you should be ok.
Follow this guide to the letter:
http://forum.xda-developers.com/showthread.php?t=2010624
And, as I already told, LG can't be blame for anything other than running stock. Even if you only root the device and crash it, you can't blame em for this.
Click to expand...
Click to collapse
It was stock rom. I have only rooted and unlocked it, then i wiped it in cwm, nothing else...

niyazidk said:
It was stock rom. I have only rooted and unlocked it, then i wiped it in cwm, nothing else...
Click to expand...
Click to collapse
Rooted and unlocked with a custom bootloader is not stock. You can have a lot of issue with the wrong bootloader. I once did!
Get it back to stock with the KDZ, you'll know if it's a software issue and if it's related to the custom/unlocking/rooting.

Wrong post sorrry.

nch26 said:
Man with all respect you even know if LG will update this phone.
Click to expand...
Click to collapse
What are you saying, is this a question? Who are you replying to?
This topic is not about update, it's about a bugus kernel. Don't mix things up please!

Finally... I figured it out. I have used the old KDZ updater and after tons of try, i did it. But again as i said no more LG... Maybe we should stick with a phone that has a sd slot. : )
A sum of what i did
1- find a stock rom from http://lg-phone-firmware.com/index.php?id_mod=20
2-Get old KDZ updater i have uploded and remove zip from the name
3-In KDZ updater choose 3GQCT and i think it was cs emergency, i am not sure and choose your kdz file and finally launch software update
4-Connect your phone in download mode to pc. KDZ updater has kicked the phone out of download mode and couldnt find the phone. Just try again and connect phone again while it extracts kdz file. You could also try different usb ports as i did.
Thats all.

niyazidk said:
Finally... I figured it out. I have used the old KDZ updater and after tons of try, i did it. But again as i said no more LG... Maybe we should stick with a phone that has a sd slot. : )
A sum of what i did
1- find a stock rom from http://lg-phone-firmware.com/index.php?id_mod=20
2-Get old KDZ updater i have uploded and remove zip from the name
3-In KDZ updater choose 3GQCT and i think it was cs emergency, i am not sure and choose your kdz file and finally launch software update
4-Connect your phone in download mode to pc. KDZ updater has kicked the phone out of download mode and couldnt find the phone. Just try again and connect phone again while it extracts kdz file. You could also try different usb ports as i did.
Thats all.
Click to expand...
Click to collapse
That's pretty much what the link I've posted said to do!
Anyway, good to know you're ok now.
If you want to unlock, use this:
Root:
http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
To unlock after, install Project FreeGee from google play
Then CWM/TWRP from FreeGee

t1mman said:
That's pretty much what the link I've posted said to do!
Anyway, good to know you're ok now.
If you want to unlock, use this:
Root:
http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
To unlock after, install Project FreeGee from google play
Then CWM/TWRP from FreeGee
Click to expand...
Click to collapse
That was what i did last time. But i think my problem was cwm. Because i wiped device in cwm and i had that problem. I have choosen cwm instead of twrp because it was preffered. What do you think? Should i choose twrp or cwm? Do you have experience with them?

niyazidk said:
That was what i did last time. But i think my problem was cwm. Because i wiped device in cwm and i had that problem. I have choosen cwm instead of twrp because it was preffered. What do you think? Should i choose twrp or cwm? Do you have experience with them?
Click to expand...
Click to collapse
CWM has issues with the latest Cyanogen, TWRP is apparently required so I installed the latter. I've been running "stock rom" for a month tought, I can't realy tell about Custom roms.

t1mman said:
CWM has issues with the latest Cyanogen, TWRP is apparently required so I installed the latter. I've been running "stock rom" for a month tought, I can't realy tell about Custom roms.
Click to expand...
Click to collapse
Ok so i try also twrp...
Thank you for your time.

niyazidk said:
I like lg's hardware. I had optimus 3d and now have optimus g. Both has great hardware.
I have flashed custom roms since windows mobile days, so i should have a little experience..!
But you can never be sure to flash safely especially with Lg. You can loose your imei, baseband...etc
And now i have kernel crash on my loved optimus g... A demogod kernel crash. I can boot in cwm but cant restore system. It restore boot and then system restoring fails. I can also boot in android and after a few seconds it crashes. So it doesnt stay long enough to be fx recognized by pc to save it. Pc doesnt recognize it even in download mode. I will also try with another pc.
You dont have such problems with htc or samsung. The problems with these phones arent so complicated like lg.
SO NEVER AN LG AGAIN...
Click to expand...
Click to collapse
Can't blame on lg. I see a ip***e fired, my s2 baseband fu***d, all companies made there best. Maybe it's about damaged/dropped phone.

aren't threads/guides on rooting, flashing custom roms/kernels had warned you about a potential bricked device? sometimes it pays to understand/accept what we read.

Dont blame our root or unlocking methods. One day after unlock and root, my battery drain in 4 hours. I even cant flash custom android 4.2.2 ROM.Even twrp doesnt work, appears a black screen. One day i uninstalled NFC apk. And thats it. Everything go back to normal. I dont know why Android 4.2 ROMS dont work on my device in that time, but the battery problem was NFC.
Just sharing an experience.

atifsh said:
yup, why not when you mess up the phone and cant do any thing about it, lets rock the blame game..
lu6200 to su640 to lte2 to optimus g to optimus g pro.... never had any issues and never will buy anything else.
Click to expand...
Click to collapse
Truly. Nitro to LTE2 to OG Pro to G2 :victory: :highfive:

Problem solved! Low battery warning on LG Mobile Tool

Problem solved! Low battery warning on LG Mobile Tool
1. Uninstall LG flash tool , LG Mobile Tool , lg drivers and msxml in your control panel or delete their folder
2. Install everything again ( tested on windows 8 and 8.1 i fixed my phone.. yey)
3. and follow these instructions http://forum.xda-developers.com/showthread.php?t=2420219 and tadaaa your phone is working
Hit Thanks if this helps ) Finally i fixed my phone 9:58am 2/28/14 Philippine Time

Mr.Gabo said:
Problem solved! Low battery warning on LG Mobile Tool
1. Uninstall LG flash tool , LG Mobile Tool , lg drivers and msxml in your control panel or delete their folder
2. Install everything again ( tested on windows 8 and 8.1 i fixed my phone.. yey)
3. and follow these instructions http://forum.xda-developers.com/showthread.php?t=2420219 and tadaaa your phone is working
Hit Thanks if this helps ) Finally i fixed my phone 9:58am 2/28/14 Philippine Time
Click to expand...
Click to collapse
thank you very much
I've tried, but still gives me error low battery, I have ls CM ROM, it may be that the problem?

amilio said:
thank you very much
I've tried, but still gives me error low battery, I have ls CM ROM, it may be that the problem?
Click to expand...
Click to collapse
try flashing using lg flashtool and download the tot file for your device. this might work to you. extract the dll in your latest kdz.

Mr.Gabo said:
try flashing using lg flashtool and download the tot file for your device. this might work to you. extract the dll in your latest kdz.
Click to expand...
Click to collapse
Hello, I could not install anything, you can only enter TWRP, and have nothing in memory, as can be done to install a rom Stock?

amilio said:
Hello, I could not install anything, you can only enter TWRP, and have nothing in memory, as can be done to install a rom Stock?
Click to expand...
Click to collapse
Flash using download mode

Mr.Gabo said:
try flashing using lg flashtool and download the tot file for your device. this might work to you. extract the dll in your latest kdz.
Click to expand...
Click to collapse
As far as I know .tot.files are only available for at&t models.
For other g-pro models, there are no freely available flashtools.
"lg support tool" (with the .kdz.loader "uptest.exe") seems only to be safe with a locked bootloader on the phone.
Would be nice to make sure g-pro owners get to know that, before they have costly experiences with their phones.

xifizurk said:
As far as I know tot. files are only available for at&t models.
For other g pro models, there are no freely available flashtools.
"lg support tool" (with the kdz.loader "uptest.exe") seems only to be safe with a locked bootloader on the phone.
Would be nice to make sure lg g pro owners get to know that, before they have costly experiences with their phones.
Click to expand...
Click to collapse
There are also f240's tot file and e988 i saw it on one of the thread i read.
Reading is always the key to success

xifizurk said:
As far as I know tot. files are only available for at&t models.
For other g pro models, there are no freely available flashtools.
"lg support tool" (with the kdz.loader "uptest.exe") seems only to be safe with a locked bootloader on the phone.
Would be nice to make sure lg g pro owners get to know that, before they have costly experiences with their phones.
Click to expand...
Click to collapse
my bootloader is not locked, as can relocket? thanks

amilio said:
my bootloader is not locked, as can relocket? thanks
Click to expand...
Click to collapse
you can relock it by flashing kdz or tot via lg mobile tool or lg flash tool. done it many times and still counting

Mr.Gabo said:
you can relock it by flashing kdz or tot via lg mobile tool or lg flash tool. done it many times and still counting
Click to expand...
Click to collapse
what is going on here?
amilio just told us he isn`t able to flash!
already starting this thread with the misleading information!
this really gets down here to pure spamming!
why are you doing this???
nevertheless trying to give an answer:
TWRP has traditionally among its advanced tab features some sort of "adb" support.
on my other older android phone i could easily push zip files from pc to the phone.
This might be a way to go to get something to the phone that boots up or is close enough to stock firmware to be flashable with lg-support-tool

hello
thank you all, but I could not solve the problem, low battery error, and only enters TWPR, and I tried installing the CM, and error, which can not do.
thanks

xifizurk said:
what is going on here?
amilio just told us he isn`t able to flash!
already starting this thread with the misleading information
this gets realy down here to pure spamming!
why are you doing this???
nevertheless trying to give an answer:
TWRP has traditionally among its advanced tab features some sort of "adb" support.
on my other older android phone i could easily push zip files from pc to the phone.
This might be a way to go to get something to the phone that boots up or is close enough to stock firmware to be flashable with lg-support-tool
Click to expand...
Click to collapse
pure spamming? do you even know what that means? im just sharing my experiece and what i do it works for me. i think the problem on his phone is not yet on my knowledge.

amilio said:
hello
thank you all, but I could not solve the problem, low battery error, and only enters TWPR, and I tried installing the CM, and error, which can not do.
thanks
Click to expand...
Click to collapse
cant you enter download mode? can you open your phone? maybe your file is broken. tried testing the archives using 7-zip it should not have any errors. if there is a single error , redownload it. that's what i when i flash g2 v5. i always get error status 1 but i fix it by redownloading and test if it has no errors in 7-zip. hope this helps

Before I created this thread here, I had already tried everything you have mentioned in your original post instructions. The instructions you provided are the first things I tried when I was troubleshooting and everyone should have already tried doing the obvious already. The problem most of us are facing, goes well beyond these instructions. I think it has something to do with missing boot files or permissions that were only exposed after the unlocking process using a specific released version of freegee.
I have managed to use LG Flash Tools now, even after being affected. I would not advise trying this though, as it was an accident for me. I had the back cover off while flashing a custom rom with CWM. After the rom file was installed, I rebooted my phone from CWM. As the phone was rebooting (was on the rom boot animation) the battery fell out. After I put the battery back in the phone would load to the rom boot animation, but it would freeze on this screen and then reboot and do the same thing over and over (bootloop to animation) - I then tried to factory reset and flash the rom again, with the same thing happening again) - I then went in to restore my phone using a backup through CWM. After the restoration, then phone would still hang at boot animation and then bootloop. I retried restoring and flashing multiple roms and re root the phone with a saved zip file on my phone. None of this was working. I decided to try to use LG Flast Tools again, only this time it actually passed the low battery warning. The funny thing is, I have tried thousands of times even at 100% battery level and lower (when there was nothing wrong with my phone at all) and it has never worked. This time it did (even though I had 66% battery) and still works now, as I just tried it again.

Thank you!!
Mr.Gabo said:
Problem solved! Low battery warning on LG Mobile Tool
1. Uninstall LG flash tool , LG Mobile Tool , lg drivers and msxml in your control panel or delete their folder
2. Install everything again ( tested on windows 8 and 8.1 i fixed my phone.. yey)
3. and follow these instructions http://forum.xda-developers.com/showthread.php?t=2420219 and tadaaa your phone is working
Hit Thanks if this helps ) Finally i fixed my phone 9:58am 2/28/14 Philippine Time
Click to expand...
Click to collapse
that worked for me...after 2 days of trying i realy was disperate...then i tried this ad worked first time. you saved my phone:good::good::good::good:

23dno said:
that worked for me...after 2 days of trying i realy was disperate...then i tried this ad worked first time. you saved my phone:good::good::good::good:
Click to expand...
Click to collapse
im glad that this help

Updated Magisk Manager - NOW BRICKED?!

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

Question Touchscreen not working

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.

Need help unlocking AT&T Calypso (U318AA)

Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.

adrian0883 said:
Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.
Click to expand...
Click to collapse
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process

i can help you , if your device still soft break
Osamaaj03 said:
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process
Click to expand...
Click to collapse

sahelkhan022 said:
i can help you , if your device still soft break
Click to expand...
Click to collapse
it is, I think the problem is with the super image but I'm not 100% sure. so if you can share a full mtk client backup it would be awesome. if not, a super image will do

your device stuck on logo ? or deadboot ?

842.92 MB file on MEGA
mega.nz

sahelkhan022 said:
your device stuck on logo ? or deadboot ?
Click to expand...
Click to collapse
every time I try to turn it on it bootloops to fastboot mode, I suspect that the issue is a super image I found online, flashed not knowing that it was corrupted (which I discovered later), and I foolishly didn't create a backup (why I went and downloaded the corrupted image in the first place) thinking that I will never go back to the stock rom but now after I have used a couple gsi's for a while found out that the og rom performance was much better and decided to go back

sahelkhan022 said:
842.92 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
so this is just a bunch of .bin files that I have to flash using mtk client to said partitions? just making sure

and just to let you know I might not be able to download the file today, the internet is pretty sucky where I'm rn, so I hope you don't have a problem keeping the file up till tomorrow. and just wanted to thank you for the incredible help, I've been trying to fix this phone for the last two weeks which was headache inducing say the least.

you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..

sorry for the late response, but yeah I've flashed all of the files using mtkclient and it didn't work Idk if I have messed things up, I thought reflashing all of the stock firmware would fix everything but it seems that there's still something wrong

sahelkhan022 said:
you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..
Click to expand...
Click to collapse
I've unlocked the bootloader and disabled boot verification, tried fastboot -w and fastboot format userdata and non of it worked, and I'm really sorry but I can't share my screen because as I've mentioned before my internet is bad and I had to go somewhere else to get the files. can I share anything else with you that might help, I have some recovery log files

IT WORKED!!!!! I don't know what was the problem, I've tried flashing the files again but this time using the terminal instead of the gui AND IT WORKED. THANK YOU THANK YOU THANK YOU

I'm going to upload the files later in case someone else encountered the same problem