My asus zenfone max pro m1 has not been booting since the april 21st update.
It boots completely, asks for pattern to decrypt storage and irrespective of whether or not i enter the pattern, it reboots. Looks like some system services are failing after boot and hence i need to wipe or clean flash the system partition.
Situation:
This is my dad's phone and it wasn't tampered with at all. Unfortunately boot loader is locked and usb debugging is off.
None of my 2 laptops detect it in fastboot or adb in windows and linux. I've installed proper drivers but it doesn't even show up in device manager as unknown or whatever.
It normally enters fastboot and recovery modes.
I did the root integrity check from recovery and it reported 92 files missing and 90 unknown files.
What i tried:
Reinstalling the same update through recovery (makes no difference)
Installing older updates ( recovery doesn't allow)
Factory reset through recovery (makes no difference)
flashing via fastboot (fastboot doesn't detect)
The only thing i did not try is qfil and I'm not doing that because a lot of people have reported losing their IMEI and other hardware information.
Also, I couldn't find a stock qfil firmware they were stock based made by other people.
Asus's update broke the phone. But I don't see a lot of people posting about it. I could use some help.
Thank you
Can you boot to safe mode ?
(Long press power button - then long press on power off)
Doesn't work
Tianhe said:
Can you boot to safe mode ?
(Long press power button - then long press on power off)
Click to expand...
Click to collapse
Safe mode makes no difference. Even factory resetting made no difference.
Related
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
After performed wipe cache and firmware update with "Swift&Fast Slim B160 aio" ROM, the phone reboot and stuck at waiting for booting... ==> wait for 3 hours and still show the same as BOOTING.
Performed the factory reset by press Volume Up and Power, the Factory Reset is now stuck at 99%
Please help to the the phone back in working condition.
Resolved yet?
Possible idea
You can probably still load TWRP. Press and hold volume down + power at the same time to load fastboot mode.
ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
1. adb reboot bootloader (requires USB debugging to be turned on).
or...... power off the device then back on with 'vol up' + power button.
Wipe your device.
2. fastboot -w
Update your ROM.
3. fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM. Try another ROM if Swift & Fast Slim isn't working. Your file could be corrupted.
did u get things fixed?
Hello,
My issue is really weird. I was using No Limits rom with oos 4.5.1
Later, i've reverted back to stock rom and my actual version is Pie with OOS 9.0.7 . Also my recovery is stock at the moment.
The issue is, i can not enter to fastboot mode. İ am selecting that and pressing power button to start fb mode but my device reboots back to desktop without entering to mode. Device is up and running, no stuck at bootloop or etc.
Now i can not load any recovery, root etc. Tried all combinations to enter but doesnt work at all.
İs there any solution to solve this ?
Kaanb93 said:
Hello,
My issue is really weird. I was using No Limits rom with oos 4.5.1
Later, i've reverted back to stock rom and my actual version is Pie with OOS 9.0.7 . Also my recovery is stock at the moment.
The issue is, i can not enter to fastboot mode. İ am selecting that and pressing power button to start fb mode but my device reboots back to desktop without entering to mode. Device is up and running, no stuck at bootloop or etc.
Now i can not load any recovery, root etc. Tried all combinations to enter but doesnt work at all.
İs there any solution to solve this ?
Click to expand...
Click to collapse
Instead of trying to enter fastboot mode from android did you tried to enter bootloader by holding power + volume up while powering the device on.
Also if you have enabled USB debugging you should be able to enter fastboot mode by connecting to a pc and using platform tools: adb reboot bootloader
strongst said:
Instead of trying to enter fastboot mode from android did you tried to enter bootloader by holding power + volume up while powering the device on.
Also if you have enabled USB debugging you should be able to enter fastboot mode by connecting to a pc and using platform tools: adb reboot bootloader
Click to expand...
Click to collapse
Hello, tried that ways too, and it reboots to the desktop anyway. On pc, when i wrote that command, it reboots again.
İ guess something happened to the bootloader firmware if it exists..
Kaanb93 said:
Hello, tried that ways too, and it reboots to the desktop anyway. On pc, when i wrote that command, it reboots again.
İ guess something happened to the bootloader firmware if it exists..
Click to expand...
Click to collapse
Then I recommend to flashing everything from scratch with https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Hey their. So i jsut bought a one plus 6t and started playing around iwth it. I tried to get twrp and i got it but when i rebooted to os i had no wifi. So i download magisk zip and flashed it. After this i got stuck in bootloop and so i wne to twrp and wiped everything except system. Then i rebooted and got this message Qualcomm CrashDump Mode Attempted to kill init! exit code=0x0000000b do_exit. Then i freaked out and accidently wipes system too. Now i think i have a complete brick as adb still works but i cant transfer any file from pc to phone because theirs no system. Please help!!!
Never wipe system and vendor on A/B devices, literally, never.
Boot twrp and flash OOS or use msmdownloadtool.
What do you mean flash OOS. Like flash a fastboot file? And what version of msmdownloadtool should I get as their is no system. Should I get 10 cause that was my last system or it doesn't matter.
Update. I left twrp after flashing a stock image and now adb doesn't recognize my phone. When booting into recovery I go into the one plus recovery. Now I'm really screwed.
Okay now im really screwed. Whenever I boot with power up or power down I get sent to the bootlaoder page that says fastboot mode products name. I cant leave this page however. On the options above the information I click reboot recovery I get sent back to this page.
UPDATE. My phone is a literal brick now. It won't even turn on. I tried to force reboot it before and after it powered off it wont turn on. Its fully charged and when connecting to charger of holding buttons nothing happens. I have no warranty so Im hoping that someone can help me.
The "bootloader page" is fastboot and that's normal because there's no system to boot, you wiped that partition... and ADB only recognizes the phone when the boot process ends and ADB is enabled in the phone.
If you press vol up + down when you connect the usb cable the phone boots in EDL (Emergency Download Mode) mode, long press power + vol up to leave that state.
Now, download msmdownloadtool from here, extract the file, power off you phone, conect the usb cable to your pc, press vol up + down and connect the usb cable to the phone, open msmdownloadtool and flash the OS.
Edit: Read this thread for more detailed instructions.
What do you mean by flash the OS. The OS in the system or do I have to download one?
whenever I plug in my device it vibrates and then goes into the fastboot page. Also adb can detect it if I type in fastboot devices.
So i go the device to work and MsM worked until 4 seconds and then It said param preload for status of connection and status of last communication says device not match image
Try with the fastboot ROM.
When i downloaded another version of MsM it did not say no image match instead it stays at 4sec and says recording download time
Can you give me instructions on how to use the fastboot room? Like after i download it what should i do with it?
Download the rom, unpack it, boot your phone in fastboot (Power + vol up + vol down), connect the phone to your pc and execute the "flash-all.bat" file, and just wait.
um what is flash-all... How does it work what am i supposed to do.
what does unpack it mean?
Hey their im going to assume you meant to unzip the file and then open the file called falsh-all.bash. In that case when i do that i get this message "error: failed to load 'images.zip': No such file or directory
Press any key to exit..." In a CMD window
Seems I found a way to semi brick my SM-T500. I was attempting to install the LOS 18.1 ROM just posted in the guide section. Some how I got the "can only install official" error message on my download screen after flashing TWRP. Made the mistake of flashing only the stock AP without BL or CSC and now I can't get into either recovery or download modes. Holding vol up and down and plugging in USB cable does nothing. Same with holding power button and either vol up or down. Blank screen. Can only power on and boot to system.
Did you install twrp and can you get into recovery. I had similar problem but was still able to get into download mode from power off. However to do so I had to boot into twrp and select reboot and power off... from that menu you can also boot directly to download mode... I know that doesnt halp much if you hadnt installed twrp yet... but thought I would throw that out there...
wizzdome said:
Did you install twrp and can you get into recovery. I had similar problem but was still able to get into download mode from power off. However to do so I had to boot into twrp and select reboot and power off... from that menu you can also boot directly to download mode... I know that doesnt halp much if you hadnt installed twrp yet... but thought I would throw that out there...
Click to expand...
Click to collapse
I can't boot TWRP or download. The only thing that will boot is system. Can't even get to the lock/unlock screen.
can you connect to adb shell? and try #reboot download
or #reboot twrp. I figure if you get to download you can reflash stock and start over.
Also when your trying to boot into recovery try not being plugged in. Not sure about this device but a lot of older Samsung's that I had would not let me get into recovery if I was plugged in during boot.
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
I saw alot of issues with twrp so I tried Magick for first time ever on my SM-T500 and had a minor hiccup bc I wasn't paying attention to firmware and installed an old AP with newer firmware but ended up just reflashing the whole tablet with the same firmware as the AP that is required for Root and presto it worked! AND HEY IM DEF A NEWBIE!
housemusix said:
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
Click to expand...
Click to collapse
Yeah I've run into the same thing, I originally missed the step to run Magisk after I flashed the patched tar and rebooted into the System and it triggered the "Prenormal KG state" problems. Finally I managed to flash stock ROM back and got to exactly where you are now.
I was able to just flash the patched Magisk AP without CSC and BL, and now it will only go to stock recovery and was able to get TWRP to work once but couldn't factory reset or wipe cache due to (which I assume was) a ton of mounting failures when it loaded.
Anyone else have suggestions to get this thing stable so I can flash LOS? I can get to Download mode.
hello, I post this because it's seems the same subject. I have to password protected (forget password) original rom tablet (non root). For me the datas are not important , I just want to remove the password or reflash with original rom. I downloaded Odin , usb driver and correct firmware. I select AP firmware with Odin, I see the connexion (COM3 green) and it's stuck to "setup connexion".
My problem is that it's impossible to enter in download mode.
When I try to shutdown the tablet, it ask me for a password.
When I press for seconds the power button , after few second I see the Samsung Logo and the tablet restarts.
I try to press volume up, volume up and volume down etc...but each combinaison...no recover, no download mode, nothing and impossible to flash . is it normal ? how to do to unsticked SetupConnetion ?
regards
bruno
housemusix said:
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
Click to expand...
Click to collapse
This is not the same as my problem. My problem is that I flashed AP without BL and the two don't match. It isn't that things are locked but that I can't boot to anything but system. Can't boot recovery or download so I can't flash ANYTHING. Not even stock.