A Moto G4 Play xt1609 Verizon phone. Locked bootloader.
What I can do:
Boot into bootloader (From now on will be known as BL)
This is actually the default boot. It doesn't loop (anymore). Instead, it goes straight to this. The same goes for recovery. Attempting a Vol up or 'recovery mode' from BL. Turning the phone off will have itself turn right back on.
What I've done:
Taken it off the side of the road caked in mud
Bag of rice
Taken it apart and gotten dirt out
Sodded a connector for the battery to make contact with
I am physically attached to this phone by now
Got it into a boot loop
Got into BL
Flashed STOCK rom files (nothing else as BL is locked by Verizon)
Before the stock flash, it would default into a bootloop. Same for recovery. Now it defaults into BL, so I know I've made progress. I can't tell you what the previous owners did to get it here. I can only tell you what I'm working with.
Again, both normal and recovery boots into BootLoader. Phone auto reboots into Loader.
PLEASE tell me theres a thing to do next. I want this thing to live again!
Does fastboot recognize the device?
So just got the axon 7 mini yesterday and was so excited I decided to try to root it with my laptop while my girl was driving us home from Las Vegas..... Ell I got as far as unlocking the boot loader.... now i get this odd screen after i try to exit fastboot. (pic-1) and no matter what option I pick the only thing that will come up is this screen. The only time its different is if I try to chose start from this screen then I get (pic-2) The best thing about this is that I can still go back to fastboot anytime. And it shows up in fastboot devices. Do I need to reflash stock thru fastboot? If so How and Where can i find it. Can I just flash nougat? I'm new to ADB/Fastboot.... Thank you for your time and consideration ahead of time for any help.
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
William Guo said:
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Click to expand...
Click to collapse
I tried the thing were saying over and over
MrWhite0429 said:
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
Click to expand...
Click to collapse
so I was stuck all day yesterday trying anything and everything. BY THE WAY...Im very knowledgable but im pretty much a newb in rooting dept. especially fastboot. Well it seems I erased everything including the bootloader then battery died and no I have NOTHING on screen, no vibrations. Pretty much looks bricked. But when I try to put it in my computer to charge it it still shows up in my devices. BUT its not being found in adb/fastboot. I've tried every key combo/and length of holding them which doesnt do nothing
Can you place the device in edl? It will not display any lights or images when it is in edl.
So here is my predicament, I got a warranty Axon 7 replacement. Was going through the procedures to get everything setup. I got everything done and flashed RR. Booted up RR and then hit the "Enter Password Screen", which I remember from my first time the data partition needed to be reformatted with a new file system. Here is where my idiot self screwed up. I accidentally chose the system partition used xfat 4 and now TWRP won't load back up. I have one of those devices where EDL is not longer accessible from the hardware keys, it boots into DFU mode instead.
Things I've tried:
- I've tried getting into EDL mode from fast-boot modifications, It simply reboots normally and the whole system is frozen
- I've tried Re-Flashing TWRP using the Axon 7 Toolkit and it freezes on the TWRP load screen. Any solution to completely re-flash stock software includes getting into EDL mode, which I'm unable to do with the hardware keys. (My old Axon 7 gets into it just fine still)
- (update) Tried to flash a new TWRP image via fastboot as well. It's still frozen on the TWRP load screen.
Things I can do
- Get into Fastboot
- Get to a Twrp loading Screen
- Sit on the ZTE logo or unlocked boot loader screen at startup
If anyone can be of assistance, I'd greatly appreciate it. I really do love this phone! If you need more info just ask, I'm happy to provide it. Generally I figure these things out when I screw up(which has happened more often than I care to admit) but I'm honestly stuck here and at a loss of what to do to fix this issue. If anyone has any suggestions, I'd love your help!
UPDATE/EDIT - I figured out a solution! I pulled a factory Image from the EDL Files and pushed it via fastboot. I'm not back into TWRP! Wahoo!
Mi A1 bricked, hard resetted it by opening the back cover and shorting two points.
It gets detected by mi flash tool but I cannot flash the stock room. It is giving me "cannot receive hello packet" and then it times out.
Any help will be appreciated.
Thank you.
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
foggs said:
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
Click to expand...
Click to collapse
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
foggs said:
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
Click to expand...
Click to collapse
Yup, I ruined one of my usb-C cable trying do do deep flash that way. I failed, so I went to one repair shop and open up the device and did the "two point short thing", which helped to be recognized by the flash tool. Then it showed me that "hello packet" thing.
Then I dug around the Internet for couple of hours and changed the USB port on laptop. I also restarted the laptop after I reinstalled the drivers. Then it actually flashed that ROM I mentioned above. But just that ROM. I tried the latest to oldest versions and all of those ROM would flash but then they will brick the phone again. Only that one worked, i.e. helped me to get to bootloader. But alas it is stuck there, no matter how many times I clean flashed it, it is refusing to boot to system. It gives me "Your SYSTEM HAS BEEN DESTROYED" message on every boot. It only goes to bootloader if I press Volume Up + Power button while booting. And it's a dead end for now. I don't know what else to do.
Also this phone was bought in Hong Kong and its warranty won't work where I am right now. I already took it to the authorized service center and those lazy people told me to change the motherboard and it will cost around $180. So I took it back. lol
Disable driver enforcment to get the hello packet.
TrueMS said:
Disable driver enforcment to get the hello packet.
Click to expand...
Click to collapse
still no hello packet
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
:victory: Held the power button, clicked flash.. Success :good: it's in the process of flashing now. Thank you
Edit: successful flash now to just let it charge up. Thanks again guys for the help/suggestions ?
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
foggs said:
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
Click to expand...
Click to collapse
Ur presist partition is damaged..thr are many guides here about recovering it
Do the "factory flash" mode in MiFlash under EDL mode as a last resort. May wipe your IMEI and MAC's, not sure.
Could not receive magic packet is solved by using USB2 port, Windows 7 x86 (32-bit) in a VM, or power-cycling the device and starting over, any or all of the above.
Deep flash cable is only for kicking the phone out of diagnostic mode and into QDFlash mode. Not necessary if using test point. I had to use testpoint method myself, couldn't get deepflash cable to work for getting out of diagnostic mode. I hope I can get it working next time though when I inevitably brick it from repartitioning; as I broke my screen when disassembling
apexashwin said:
Ur presist partition is damaged..thr are many guides here about recovering it
Click to expand...
Click to collapse
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Did you find the guide about fixing constant reboot? It's around somewhere, might be on MIUI forum.
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Please try presist resurrector from guides section
I think i've got it back to life.
first tried to flash 7.1.2 stock the earliest one (tissot_images_7.8.23_7.1), it hung on flashing it for nearly an hour with no success, closed the miflash application then tried another 7.1.2 (tissot_images_7.10.30_7.1)flash successful, then in stalled twrp did the persist command and reboot nearly got to the home screen just never getting over the line. then i flashed January 8.0 oreo (tissot_images_8.1.10_8.0) and was able to get on to the home screen/go into settings/enable developer options but it would eventually reboot itself, went back into twrp and did the persist command again and reboot.. success (fingers crossed) now downloading/applying April security update as i type this.
Boo installation problem with the update
looks like i lost my imei, https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190 this is going to be a pain.. i'll post back when i try this. need a break from this mess ive made lol
thanks for the help/suggestions appreciated big time.
edit: up to the latest update April 1 security patch.
all done, down to 7.8.23 rom, did the stuff to get the imei back then flashed latest oreo rom
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
Man, I was trying to fix my Redmi Note 4X for the past 6 hours and you were the ONLY guy to talk about this. Thank you so much. :victory:
THANK YOU
udaan said:
it was solved after i changed the usb port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then twrp. But after flashing aosp extended rom it gave me "the system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
man you just solved my problem and saved for me like 180 eur thank you you are a god !!!! Thanks for using this site !!!!!!!!!! <3 <3 <3
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I was unable to flash on MiFlash and after changing USB port I managed to do it!.
Many thanks!
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
I love you!
Hello everyone.
My friend has been using ASUS Zenfone Max (ZC550KL, MSM8939) since one and a half year. Unfortunately, it seems in bricked state as of now. Following were the series of events that has led to current situation. Please go through it (although it's long), so that u have idea of what has been done.
Last week, due to heavy raining, some water crept inside mobile phone. We tried to switch off phone, but due to non-removable battery, we couldn't. When I pressed the power button for long enough time, it would restart. The touchscreen was also misbehaving. So, what we did, is we let it discharge and switch off overnight, by opening back cover, below the fan.
Next day, when we booted up (made sure that phone was dry, no putting in rice and all that) the touch-screen stopped working. We went to ASUS service center, and they told us a huge cost. Since, phone was out of warranty, we went to a local guy who replaced the touch-screen digitizer at a lower cost (maybe he put a resistive one). Phone started working completely normally, all the functions.
Next day, due to my friend's negligence, the phone again got discharged and switched off. Now, when we tried starting it, it went till android is starting, and stuck there. We waited for 6.5 hrs, then forced reset it (long press power key). Now it got stuck at ASUS logo. We again waited for >4 hrs. Again we tried 2-3 times, it always got stuck at ASUS logo. The phone was able to go in Stock Recovery and Bootloader (CSC) mode. The bootloader was locked and debugging mode not enabled.
*In recovery mode, following messages were coming "E: unknown volume for path /factory"
Before going to ASUS service center, we have tried following ROMs/ updates (in sequence):
factory reset from recovery mode
UL-ASUS_Z010_2-WW-13.8.26.113-user.zip [adb sideload]
UL_ASUS_Z010_2-WW-13.8.26.80-user.zip [adb sideload]
WW_ZC550KL(8916)-13.8.26.92_M3.1.42_Phone-user.raw.zip [ASUS flash tool] wrong firmware
WW_ZC550KL_8916_V13.8.26.60_M3.1.40_Phone-user.raw.zip [ASUS flash tool] wrong firmware
WW_ZC550KL(8939)-13.8.26.98_M3.1.42_Phone-user.raw.zip [ASUS flash tool]
WW_ZC550KL_8939_V13.8.26.63_M3.1.40_Phone-user.raw.zip [ASUS flash tool]
IN_ZC550KL(8939)-13.8.26.98_M3.3.10_Phone-user.raw.zip [ASUS flash tool] (we thought IN was for India)
UL-ASUS_Z010-WW-13.8.26.76-user.zip [adb sideload]
In all of above, the ASUS logo went till android is starting and stuck, for >3 hours.
In between, we flashed wrong ROM (by mistake).
Even now, the mobile can go into Recovery mode and CSC mode. We went to Recovery mode and would verify on top whether the specific ROM has loaded or not.
The recovery mode would change the version properly every time after update.
Every time after adb sideload or flashing, the mobile would go till starting android and stuck. After waiting good enough time (patiently) when we restart, it would get stuck at ASUS logo.
Finally, we gave to ASUS service center, where they said: "Mobile not accepting software, need to change motherboard", for which we denied, because the cost of motherboard replacement is 87.5% of overall mobile cost!!
Anyways, current situation is: mobile enters the recovery and boot-loader mode. Boots till ASUS logo. Properly recognized in adb and fastboot. On trying to flash custom recovery or boot, it says "Remote: permission denied" (might be because of locked boot-loader) and was unsuccessful.
We don't know what to do further. We are planning to give it to local repair guy, to see if he can do something. But we thought to post here first. Any suggestions are welcome.
More importantly, we want to understand possibly what has happened and why. ASUS guy told that internal memory chip is damaged, but how? If it was, why phone started working properly once, and got damaged once we rebooted?
Thanks in advance
https://drive.google.com/file/...ul1vuE3yJwUjVpSDJMbUJZanc/view
flash with qfil in 9008 mode
Then again flash latest flash filezip with mmc card from asus support ... if not sucess contact me on telegram https://t.me/vikastelecompathankot
Sent from my SM-G935F using Tapatalk