Bricked my phone. sort of... - ZTE Axon 7 Questions & Answers

So 2 nights ago I decided to switch from a stock based 7.1.0 mi favor 5.0 rom back to lineage os.
Backed up all my goodies, went into twrp wiped out everything. moved my few flashable zips back onto storage and attempted to install
Every time I try to flash any rom at this point It refuses to complete (I tried a few other roms) I also tried to go back to the stock based rom and failed.
flashed bootstack and modem again as supplied in the lineage os page and I am certain I used the files for my phone.
got trapped in edl mode.
used the axon 7 toolkit to recover back to stock. stock wont boot (waited 20 minutes and gave up on boot screen)
got twrp installed again.
twrp cant see internal storage SDcard but my computer can. I had no way to flash any files without going and buying an actual sd card
get into edl mode and recover to stock again (still wont boot) so Installed twrp
twrp can see sd card again so I tried to flash lineage once more (still wont complete) after 10 minutes I give up and reboot
twrp wont mount a few partitions now cache etc.
My next move would be to boot to edl and restore to stock again and get twrp working.
My problem is I expect twrp will still fail to flash any rom.
am I missing something big here? am I just an idiot with a pretty paperweight?
Is it possible that there is some deeper problem with my phone? its been exposed to extreme cold/heat dropped many times, magnets, steel dust etc. over the last 2 years.
I will try any good suggestions anyone has, if anyone is willing to help me.
Also feel free to call me an idiot for any of the many dumb things I did (not making a backup etc.)

Just flash stock version with miflash and EDL.
Gesendet von meinem ZTE Axon 7 mit Tapatalk

^ just that. I did couple stupid moves trying out Oreo and ended up with blank system, but since bootloader was unlocked and EDL mode is independent of everything else and we have nice tools to just flash using it - viola.

marcus.linkenbach said:
Just flash stock version with miflash and EDL.
Gesendet von meinem ZTE Axon 7 mit Tapatalk
Click to expand...
Click to collapse
That's the thing. I did that. The first time it flashed but wouldn't get past the first axon screen (before the "your bootloader is unlocked" screen) and the second time it just wouldn't complete a boot. After 20 minutes I gave up. I guess I'll try again and give it a few hours for first boot time if I need too...

@masong397 get it into EDL .. power off and then power on holding vol up & down plus power for 15 seconds until you get a black screen and hear your pc bing that a device is connected .. then run miFlash and refresh so you see COM4 for example then select it and flash "ZTE_AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS" This will at least get a bootloader working for you again

Related

[Q] Stuck at Boot / Nothing working anymore.

EDIT:
UPDATED POST AT THE BOTTOM!
Hey guys,
flashed czechops CM 10.2 a while ago everything was running fine.
On Saturday i decided to let the battery drain completely to do a full recharge. That`s when the Problems started.
After booting the Phone up i was stuck in a Bootloop with the Cyanogenmod Logo turning around and around and around and so on.
Okay i thought let`s reboot and see what happens.
Still the same.
I then booted into recovery by holding the x button on the keyboard and power and then when the androind in the triangle showed up using vol + and vol - to get into recovery.
I then deleted the cache and rebooted again (No full wipe to factory default trying to avoid that).
After that the phone turned on saying Android is getting updated Updating Package x of y.
After its done its now stuck in Apps getting started.
After i found out to get to the Bootmenu i decided to check the Recovery Menu there.
I can choose between Motorola Stock Recovery (the normal one i already was on)
and Team Win Recovery.
So i choose Team Win Recovery and thought okay since its not working im gonna install the Update of czechops 10.2
Installing itself worked fine. But now im stuck in the same loops.
Currently im goind a Backup of the System with the Team Win Recovery in the hope i wont loose the data even if what im trying to avoid a full factory wipe.
What kinda poped in my eyes when i started the recovery was that it said E: Unable to locate '/boot' partition for backup.
Could this be the problem which is stopping the phone from booting correctly?
And if so how can i fix it?
Hope anyone can help me,
Kind Regards,
Invi
I had te same problem before doing a clean install.
I don't know why but, if you install the android 10.0 tezet and from there start the gapps, creating a account and installing your apps, you do not have problems to install the 10.2.
Good luck.
Sent from my A953 using xda app-developers app
jonasgitz said:
I had te same problem before doing a clean install.
I don't know why but, if you install the android 10.0 tezet and from there start the gapps, creating a account and installing your apps, you do not have problems to install the 10.2.
Good luck.
Sent from my A953 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the heads up jonas.
Unfortunately its too late its seems. My Milestone is just a stone now it seems.
After trying to install 10.2 12.03.14 and that not working correct after doing a full factory wipe i decided to install cm 11 from czechop.
Unfortunately it seems it failed.
My milestone just boots up and stops at the First Logo. No lights. No chance to get in any recovery mode except the normal one.
Bootloader was working some time but stopped cause the Battery is almost empty.
The Problem is i cant even load the Phone anymore cause as soon as i put it on a charger it boots up and wont get enough battery power to live for a few minutes.
So the only thing left working is the normal Android 3e Recovery. Hope i can do anything from there.
Don't give up.
Your problem it's normal, you fisrt need a global battery charger to recharge your battery.
After it, go to boot recovery, you must turn on the milestone holding " volume down + camera" or "volume up + camera", than you need to uses the RSD Lite to reflash your milestone 2.
Normaly, when do you came from another room, you stay in boot loop, so you need to entery in Miestone recovery, "x + volume down" than after it you do a factory reset. It will boot normaly after that.
To go to boot recovery, you must turn on.
Try harder.
(Guys, lets try to help a little)
Sorry about my poor english
I wont. Already ordered an global battery charger yesterday. In the mail from the store delivery is 7-10 Weekdays.
Good thing i have a second cellphone which i can use in the meantime.
i had a similar scenario
Invisan said:
Thanks for the heads up jonas.
Unfortunately its too late its seems. My Milestone is just a stone now it seems.
After trying to install 10.2 12.03.14 and that not working correct after doing a full factory wipe i decided to install cm 11 from czechop.
Unfortunately it seems it failed.
My milestone just boots up and stops at the First Logo. No lights. No chance to get in any recovery mode except the normal one.
Bootloader was working some time but stopped cause the Battery is almost empty.
The Problem is i cant even load the Phone anymore cause as soon as i put it on a charger it boots up and wont get enough battery power to live for a few minutes.
So the only thing left working is the normal Android 3e Recovery. Hope i can do anything from there.
Click to expand...
Click to collapse
hi, I had a similar situation to that earlier today, in that I got to the situation where on boot up I got the Motorola logo then nothing else (I was trying to install C.M. 11 from 10.2 but when it went to install got a message E;// error - verification signature installation aborted), after major panic thinking I'd bricked my milestone, I tried starting the phone in bootloader mode (press camera, volume up and power buttons at the same time) which gives a black screen saying boot loader 70.13 and towards the bottom says boot menu, connect USB, then on your pc find program MOTOROLA SOFTWARE UPDATER (hope you've got it) open the program, it'll say connect a device plug your phone in and let it do it's stuff, takes about an hour (charge your battery using a desktop battery charger beforehand) and your phone will be returned to the stock Motorola rom but at least your phone isn't a brick and you can always start again trying cyanogenmod.
hope this helps
mark13_2001 said:
hi, I had a similar situation to that earlier today, in that I got to the situation where on boot up I got the Motorola logo then nothing else (I was trying to install C.M. 11 from 10.2 but when it went to install got a message E;// error - verification signature installation aborted), after major panic thinking I'd bricked my milestone, I tried starting the phone in bootloader mode (press camera, volume up and power buttons at the same time) which gives a black screen saying boot loader 70.13 and towards the bottom says boot menu, connect USB, then on your pc find program MOTOROLA SOFTWARE UPDATER (hope you've got it) open the program, it'll say connect a device plug your phone in and let it do it's stuff, takes about an hour (charge your battery using a desktop battery charger beforehand) and your phone will be returned to the stock Motorola rom but at least your phone isn't a brick and you can always start again trying cyanogenmod.
hope this helps
Click to expand...
Click to collapse
So i downloaded Motorola Software Updater and RSD Lite + Motorola Device Manager newest Version
Unfortunately my Milestone seems not to be recognized by either Software updater nor RSD Lite.
In the Device Manager S Flash OMAP3630 shows up and is recognized.
Im running Windows 8.1 x64 and on a second Computer Windows 7 x64
What tool can i use ander Linux? Maybe the Phone will be recognized there.
EDIT:
K found it. Doing it with Linux at the Moment. Its working.
Only need to Root it then and after that flash my old Files and hope they are working.
At least i have an old Backup i made from Tezet before going up to 10.2 which i made with Clockworkmod
Hope it will work and not be broken like the one i made with Team Win Recovery.
Anyone knows how i can change stuff in a Team Win Backup?
Invisan said:
So i downloaded Motorola Software Updater and RSD Lite + Motorola Device Manager newest Version
Unfortunately my Milestone seems not to be recognized by either Software updater nor RSD Lite.
In the Device Manager S Flash OMAP3630 shows up and is recognized.
Im running Windows 8.1 x64 and on a second Computer Windows 7 x64
What tool can i use ander Linux? Maybe the Phone will be recognized there.
EDIT:
K found it. Doing it with Linux at the Moment. Its working.
Only need to Root it then and after that flash my old Files and hope they are working.
At least i have an old Backup i made from Tezet before going up to 10.2 which i made with Clockworkmod
Hope it will work and not be broken like the one i made with Team Win Recovery.
Anyone knows how i can change stuff in a Team Win Backup?
Click to expand...
Click to collapse
I did find it took a long time for the Motorola software updater (about 20 mins) to detect my milestone 2 (I'm using windows7 x64), I'm thinking the mistake I made when trying to upgrade to CM 11 was I didn't wipe data/cache before trying to install it
mark13_2001 said:
I did find it took a long time for the Motorola software updater (about 20 mins) to detect my milestone 2 (I'm using windows7 x64), I'm thinking the mistake I made when trying to upgrade to CM 11 was I didn't wipe data/cache before trying to install it
Click to expand...
Click to collapse
Hi mark,
well Windows popped up saying N/A
when it should show new Software.
It also couldnt recognize my Cellphone correctly it seemed.
But i flashed it with Linux anyways.
Flashing to tezet`s 10 worked also like a charm
and i could install my Backup i made in december before
updating to czechops 10.2.
Guess after i know what to do now i will try to update to cm11 now.
Invisan said:
Hi mark,
well Windows popped up saying N/A
when it should show new Software.
It also couldnt recognize my Cellphone correctly it seemed.
But i flashed it with Linux anyways.
Flashing to tezet`s 10 worked also like a charm
and i could install my Backup i made in december before
updating to czechops 10.2.
Guess after i know what to do now i will try to update to cm11 now.
Click to expand...
Click to collapse
let us know how you get on as I'm tempted to try again (I do like how CM10 gets rid of all the un-necessary apps but gives you control of all the system parameters) but want to step up to CM11 without having the same problem as before.

[SOLVED] Bootloop. No recovery. Bootloader locked.

================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008

TWRP Frozen on load Screen Help!

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!

Hard Brick P10 Lite - need help

Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.
Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny
Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.
lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?
I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please

edl mode; cannot receive hello packet

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!

Categories

Resources