Related
Hi,
I bought a water damaged P8 Lite for repair/parts that I was able to bring back to life.
However, volume up key is not working, and phone has a password on it.
I tried a different set of buttons but the problem is in the board.
Consequently I can't boot recovery mode and hard reset the phone.. Is there any other solution to solve this and use this board?
Thanks.
Use fastboot to flash a new firmware....this should work
madz78 said:
Hi,
I bought a water damaged P8 Lite for repair/parts that I was able to bring back to life.
However, volume up key is not working, and phone has a password on it.
I tried a different set of buttons but the problem is in the board.
Consequently I can't boot recovery mode and hard reset the phone.. Is there any other solution to solve this and use this board?
Thanks.
Click to expand...
Click to collapse
Well, since you bought water defective P8 Lite, i guess you're having problem on the board (or at least with hardware), and if that's the case then it is better to change the hardware.
But, you can also once try flashing new firmware via fastboot method. Remember flashing requires your bootloader to be unlocked, so make sure it is..
The Process??
Enable Developers Option and USB debugging (assuming that you can switch it on)
Connect your mobile to laptop/computer.
Make sure you have Minimal ADB and Fastboot Installed. Download link: http://forum.xda-developers.com/showthread.php?t=2317790
Commands:
adb devices ---- will show your serial number if its enabled
adb reboot bootloader --- will show your bootloader status (if it's green then you can flash files)
amageek said:
Well, since you bought water defective P8 Lite, i guess you're having problem on the board (or at least with hardware), and if that's the case then it is better to change the hardware.
But, you can also once try flashing new firmware via fastboot method. Remember flashing requires your bootloader to be unlocked, so make sure it is..
The Process??
Enable Developers Option and USB debugging (assuming that you can switch it on)
Connect your mobile to laptop/computer.
Make sure you have Minimal ADB and Fastboot Installed. Download link: http://forum.xda-developers.com/showthread.php?t=2317790
Commands:
adb devices ---- will show your serial number if its enabled
adb reboot bootloader --- will show your bootloader status (if it's green then you can flash files)
Click to expand...
Click to collapse
Hi,
Unfortunately I'm unable enable usb debugging and can't read the device...
Will huawei SW do any good?
madz78 said:
Hi,
Unfortunately I'm unable enable usb debugging and can't read the device...
Will huawei SW do any good?
Click to expand...
Click to collapse
huawei SW?? i didn't get that.. can you explain please
amageek said:
huawei SW?? i didn't get that.. can you explain please
Click to expand...
Click to collapse
I mean Hisuite or any other..
madz78 said:
I mean Hisuite or any other..
Click to expand...
Click to collapse
hisuite is pretty much useless.
yeah.. I was able to enter fastboot&rescue mode with hisuite but from there i can't recover anything..
Is there any flasher that allows me to flash phone via rescue mode?
Thanks.
Hey, I might have something here, in rescue mode adb doesn't see any devices but using "fastboot devices" i get "QLF7N15615001024"
Can I work with this?
Thanks.
Just read before posting. Since you can enter fastboot just go ahead and download a fastboot flashable firmware from the various threads in this subforum or extract the images from the update.app you want to flash using huawei image extractor.
deleted
keikari said:
deleted
Click to expand...
Click to collapse
keikari are you from finland too?
gabrielkor00 said:
keikari are you from finland too?
Click to expand...
Click to collapse
Yeah
Hey Guys,
recently I tried to root my ZTE Axon 7 and install TWRP on it(A2017G)(Firmware B03).
It failed and i wanted to reinstall my bootloader and my recovery (i think that i wanted this)
Before i did that i backed up my boot and recovery is i´ve been told to.
I think something went wrong there, but i realised it too late.
When it was failed i didnt know how to reinstall the backuped boot and recovry files, so i thought i could rename them to boot and recovery and flash then with ADB. This failed either and now when i want to start my phone the screen that says ZTE pops up for a second and then goes black.
I know that was silly, but now my Phone is broken and i cant do anything with it, i can not start it, i can not boot in recovery, i can not boot to fastboot.
I tried to boot into Recovery Mode, but the same thing either...
The screen flashes and goes off.
I can´t do anything.
Also when i try to turn it on the LED on the top flashes red and green. I don´t know if its related to my problem, but i need help
PLEASE!!!
I don´t know what to do:crying::crying::crying::crying:
I've uploaded the A2017G B03 stock boot.img and recovery.img (both in the same zip file) to Mediafire, here's the link:
http://www.mediafire.com/file/lz2jco2np4innau/B03.zip
This happened once (well, more than once to be precise) to me too but there's a fix for it.
http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
What you want to do is follow all of the steps (using axon7root.exe) and use the boot.img and recovery.img provided by razorblader.
I don't think you will have a chance to bring it back to life. It looks like you are in DFU mode but need EDL mode for using tenfars tools.
Unfortunately for the G model you can't enter this mode with hw keys.
But I also have this issue and looking for a solution.
As of now only way is to send it in for repair...
I had the exact same problem and tried pretty much everything I could think off but as Deje63 mentioned the only way is to give it back to the seller and get a refund (if you still can) or send it in for repair.
Just today an Axon 7 owner in the german android-hilfe forum got information he will get a new Axon 7 from ZTE.
He did also send it in for repair because the same issue. It seems even ZTE (europe/germany) does not have the tools/knowledge to flash a stock rom on such bricked devices.
I ask myself what the hell they did or think in reducing the features (for the G model) in fastboot/adb/firmware to that grund. I am a long time in Android but never had a device were there was no chance to (re)flash at least an official stock rom.
themarcc said:
...
Click to expand...
Click to collapse
Try to access the FTM (Factory Test Mode) by holding the power button and the volume down button. It will say FTM on the display if it was successful.
In case you are still stuck in DFU mode you might have to hold the power button for at least 6 seconds to get the phone to try to reboot.
If you can get into the FTM mode connect the Axon 7 to your PC.
It should show up in the device manager as a Android ADB device.
adb reboot edl
Your screen should go blank and the device should show up as 'Qualcomm HS-USB QDLoader 9008 com X' in device manager. If you get this far you can use tenfar's axon7root.exe to flash the boot.img and the recovery.img and the phone should boot up normally after that.
Are you sure talking about A2017G? I was able to enter stock recovery (volume up and power). All other key combination leads to DFU mode, regardless the phone was plugged in or not. And believe me, I tried even stupid ones.
But will try when it is back from repair.
DeJe63 said:
Are you sure talking about A2017G? I was able to enter stock recovery (volume up and power). All other key combination leads to DFU mode, regardless the phone was plugged in or not. And believe me, I tried even stupid ones.
But will try when it is back from repair.
Click to expand...
Click to collapse
I'm talking about the G model of course, on the U version this wouldn't be a problem.
Hope other people who still have their bricked G version phones try this so we can clarify if there's a chance to get into the FTM mode and can determine which 'type' of brick could potentially be revived.
No clue if this is a possibility if the wrong kind/corrupt/whatever bootloader got flashed to the phone but it's worth a try.
Edit: Read in another thread that another user stuck in DFU mode on the G model couldn't make the FTM mode work so there's little hope for this to be working unfortunately.
I do have a question as well. My G model only boots til ENTER ANDROID PASSCODE. Cannot boot into recovery only FTM is possible. Device Manager indicates an adb device, but there seems to be a special driver. Does anyone know how to help?
Thanks in advance...Marcus
Gesendet von meinem Lenovo K50a40 mit Tapatalk
try it with "default_password" without the "
I just tried it several times. After some time it says: 'wrong password' , unfortunately
Gesendet von meinem Lenovo K50a40 mit Tapatalk
marcus.linkenbach said:
I just tried it several times. After some time it says: 'wrong password' , unfortunately
Gesendet von meinem Lenovo K50a40 mit Tapatalk
Click to expand...
Click to collapse
Hi Marcus,
I have got the same problem. Did you find any solution since then?
Anyone give me any suggestion please ... :crying:
Yes. The solution was to set it up for a repair. They changed my device without any problems. I told them my phone entered into this state by upgrading on an ota update.
sent from zte axon 7 with tapatalk
marcus.linkenbach said:
Yes. The solution was to set it up for a repair. They changed my device without any problems. I told them my phone entered into this state by upgrading on an ota update.
sent from zte axon 7 with tapatalk
Click to expand...
Click to collapse
Hi,
I have finally found the solution. I have boot into edl mode via FTM and re-flash TWRP then do a factory reset. Now, it coming back !!
:good:
dolvliz said:
Hi,
I have finally found the solution. I have boot into edl mode via FTM and re-flash TWRP then do a factory reset. Now, it coming back !!
:good:
Click to expand...
Click to collapse
Good to know. But for that I got second cable, charger, headset and cover ??
sent from zte axon 7 with tapatalk
Hi everyone!
I have bougth a Redmi Pro on Gearbest and it came with Chinese/English Version of MIUI.
After a week of usage, i turned off my xiaomi and when i turned back on, it stucked on a Mi logo. Far as i discovered searching on web, it was a bug that other peopel have reported too.
I took a opportunity of having this bug to fix, to put other rom on the phone. A rom with Portuguese language witch is my mother lang.
I tried to put the new rom via "SP Flash took" with the fastboot mod but without success.
I requested the unlocking on Xiaomi Unlocking site and when they repplyed and i connected the xiaomi to the computer, the program (XiaomiMiFlash) gave me an error message telling ""Couldn´t verify device. Current account is diferent from the account info in the device"
No i can´t do nothing with the phone.
Can you guys have some idea how can i solve this?
Thank you all!
There is a good chance that the phone is already unlocked.
What was the problem with fastboot? Maybe drivers issue?
Have you tried flashing TWRP? If it takes then the phone is unlocked and you can proceed with flashing the xiaomi.eu or globerom.
kremmit said:
There is a good chance that the phone is already unlocked.
What was the problem with fastboot? Maybe drivers issue?
Have you tried flashing TWRP? If it takes then the phone is unlocked and you can proceed with flashing the xiaomi.eu or globerom.
Click to expand...
Click to collapse
Tks 4 the support!
About the Fastboot i putted the phone on fastboot mode and i disabled the Driver Signature Enforcement on Windows. I connected the phone to the computer and started to run the SP Flash Tool. After the process was completed it wont gave me any result because the phone still stucked on Mi logo..
I did'n tried the TWRP because in every tutorial tells me that i need to go to the Developer Mode and activate the USB debugging i can not access to that because the phone don't give me more than the Mi logo.
hmm the fastboot method should have worked. Have you tried it on another computer, maybe 32bit windows?
When finished flashing with miflash in fastboot did it say it was ok at the end or did it give you an error? Als tried to reboot a few times after flashing without usb cable in the phone?
kremmit said:
hmm the fastboot method should have worked. Have you tried it on another computer, maybe 32bit windows?
When finished flashing with miflash in fastboot did it say it was ok at the end or did it give you an error? Als tried to reboot a few times after flashing without usb cable in the phone?
Click to expand...
Click to collapse
Im losing my mind!
I tried again in my father's desktop wich have a 64bit windows 7 (I havent a 32 bit at home. I will try to get one borrowed)
I tried with the SP Flash Tool following a guide from "xiaomitips" and, in this computer, the program dornt even recognize my phone. I push the Download button but that give me no signal.
Is there any other way to do this? Other ways to put the rom in the phone? (Sorry the noob language)
franciscobcl said:
Im losing my mind!
I tried again in my father's desktop wich have a 64bit windows 7 (I havent a 32 bit at home. I will try to get one borrowed)
I tried with the SP Flash Tool following a guide from "xiaomitips" and, in this computer, the program dornt even recognize my phone. I push the Download button but that give me no signal.
Is there any other way to do this? Other ways to put the rom in the phone? (Sorry the noob language)
Click to expand...
Click to collapse
I'm out of ideas at this point.
I had some trouble with fastboot that my phone did restart when in fastboot mode.
Then i had to change the order of plugging in the cable and starting the program but after that all worked.
No idea what next ...
I had this issue with a Redmi 3. I can't remember the exact solution but I believe you have to have the developer ROM installed in order to unlock the bootloader. Maybe if you search for an anterior model such as the Redmi 3 you will find more information on how to load your ROM. I'm sure that it's the same method for most Xiaomi phones. Good luck!
I heard about do a Hard Reset but i dont know how to do that because i cant access to the OS of the xiaomi.
Is there a way to do a hard reset with the xiaomi stucked on Mi logo?
Tks!
Happy 2017 for all!
I tried to put my phone one Recovery Mode but it is blocked. Its like the phone on this video:
https://www.youtube.com/watch?v=tTzdQpex7BQ
How can i unlock this?
I never could get into the xiaomi recovery either but i managed to flash twrp through fastboot though.
franciscobcl said:
Tks 4 the support!
About the Fastboot i putted the phone on fastboot mode and i disabled the Driver Signature Enforcement on Windows. I connected the phone to the computer and started to run the SP Flash Tool. After the process was completed it wont gave me any result because the phone still stucked on Mi logo..
I did'n tried the TWRP because in every tutorial tells me that i need to go to the Developer Mode and activate the USB debugging i can not access to that because the phone don't give me more than the Mi logo.
Click to expand...
Click to collapse
Hi
Does your problem with sp flashtools and flashing the ROM be solved ?
Sent from my Redmi Pro
I had this problem, but I'd installed TWRP already. But you shouldn't need USB Debugging on to flash TWRP. If you manage to flash TWRP, flash a new ROM (I recommend xiaomi.eu (I think they have Portuguese)) and wipe the Dalvik cache, /cache, and /data (you probably won't have to wipe /data/media).
Miui themes
Sorry will start new item
Have you tried a different cable, that is why mine wasn't recognized at first.
I'm having the same problem here. The phone rebooted itself when I changed the locale, and hung at the Mi logo. I already had TWRP flashed. I also took the opportunity to install a new ROM; the Global Dev ROM. It installed with no errors and I wiped the Dalvik, cache, etc. Still hangs at the Mi logo, but this time without the little loading dots at the bottom. Any suggestions?
Update: I can bring it back to the original state with the loading dots and "powered by Android" at the bottom with a backup I took before flashing the new rom, but still no progress.
I managed to restore my phone using the video:
Flash Xiaomi Redmi Pro Using SP Flash Tool [Locked Bootloader]
I can't post links since I don't have enough posts here yet, but search for it on Youtube.
Update: It seems like the unlocking permissions on my account have been retroactively rejected, I wonder if that has something to do with it. I also can't seem to find the Global ROM for the Redmi Pro anymore, just the China one. Does anyone have a link for the official Global ROM on the Xiaomi site?
Update 2: Suddenly I have unlock permission again, without reapplying, so that's cool. I installed the Eu HMPro ROM, everything's working well so far.
Phosphenes said:
I managed to restore my phone using the video:
Flash Xiaomi Redmi Pro Using SP Flash Tool [Locked Bootloader]
I can't post links since I don't have enough posts here yet, but search for it on Youtube.
Update: It seems like the unlocking permissions on my account have been retroactively rejected, I wonder if that has something to do with it. I also can't seem to find the Global ROM for the Redmi Pro anymore, just the China one. Does anyone have a link for the official Global ROM on the Xiaomi site?
Update 2: Suddenly I have unlock permission again, without reapplying, so that's cool. I installed the Eu HMPro ROM, everything's working well so far.
Click to expand...
Click to collapse
What I did bro ?
I still have the same problem?
franciscobcl said:
Hi everyone!
I have bougth a Redmi Pro on Gearbest and it came with Chinese/English Version of MIUI.
After a week of usage, i turned off my xiaomi and when i turned back on, it stucked on a Mi logo. Far as i discovered searching on web, it was a bug that other peopel have reported too.
I took a opportunity of having this bug to fix, to put other rom on the phone. A rom with Portuguese language witch is my mother lang.
I tried to put the new rom via "SP Flash took" with the fastboot mod but without success.
I requested the unlocking on Xiaomi Unlocking site and when they repplyed and i connected the xiaomi to the computer, the program (XiaomiMiFlash) gave me an error message telling ""Couldn´t verify device. Current account is diferent from the account info in the device"
No i can´t do nothing with the phone.
Can you guys have some idea how can i solve this?
Thank you all!
Click to expand...
Click to collapse
You could try dowloading the official rom and then download the CHINESE version of mipc suite then enter fastboot and connect the phone
Normally the chinese mi pcsuite automaticly detects the phone is in fastboot mode, you could use google translate to translate it all just choose redmi pro on model selector (the top selection bar)the text there is untranslateable just choose the one that says pro
And then under it chose the one that translate to chinese
After That there's two tick box under it, choose the ROM you downloaded
After that chose the one that translate to install brush package, if it doesn't work choose the download brush package next to it
Thus method worked for me when my phone bricked hope it helps you
EDL (Emergency Download) Mode has been removed/ disable from MIUI 8.1 onwards and Redmi 4A later Xiaomi devices. So you can flash MIUI Fastboot ROMs on your device by using Fastboot mode only, if your bootloader is unlocked. And, we can't use Qualcomm Jig Cable(s) also now.
So, we have only one way to know Qualcomm HS-USB QDLoader 9008 port from PC. It's Test Point Method. This method will work with every MIUI ROMs (Upgrade/ Downgrade) , Locked Bootloader/ Unlocked Bootloader and also work to recover from a Dead boot device (Bricked).
While touching these two points with a metal tweezers plugin the usb cable to the phone and PC will make the phone enter edl mode. You can then release the tweezers.
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
TioCareca said:
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
Click to expand...
Click to collapse
In any case, the bootloader muz be unlocked to initiate EDL using ADB fastboot..
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command.
Click to expand...
Click to collapse
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
adrenochrome25 said:
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
Click to expand...
Click to collapse
What makes you think I'm so lame as well. I have used this command and flashed my mi max 2 with fastboot rom. Tho I don't remember if bootloader was locked or unlocked. Probably it was unlocked. But still no issues as anyone can unlock thier bootloader officially.
i wasnt intended at you. it seems they forgot some ways when they first deployed the edl blocking access but with the most recent "roms" they have blocked every access way to edl when bootloader is locked : adb, fastboot & cable
the only way left is from internal pins, but we can expect they will hide them even better on new phones.
Today it's much worth to wait 72h (+30days if you just already unlocked another one today) than opening the models that have "non removable" batteries and risking to leave traces/damages
it's really a shame that xiaomi lock their phone this way, it's a very bad message at the users (fastboot is so much restricted that you cant even switch between stable&dev anymore with locked bootloader) but we still have the chance that they allow unlocking and that this unlocking is a real one allowing full control
Fastboot rom isn't needed untill we brick our device and we can't brick the device untill we have unlocked bootloader. So basically edl mode will work when it's really needed.
It doesn't work for my MM2. Got it since 4/12/17. Didn't know i need to login to mi acc to register my device, set usb debugging, developer's mode, unlock status...I had the phone for less than 2 hrs after updating to MIUI 9 from ver 8 (using the updater app) before it suddenly froze up, crashed and went into bootloop. I tried contacting xiaomi svc ctr but those clowns refused to help saying my device is china export.
I cldn't even get them to help me register my device on my mi acc using the imei & s/n info. So if anyone could offer some suggestions as to how I could ressurrect my phone, I wld be most grateful. Failing which the only avenue is to bring it to a svc ctr in China to get them fix it.
Rgds
My test points don't seem to work
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Nike Lee said:
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Click to expand...
Click to collapse
I managed to short the test points and got the Qualcomm HSB device on the device mgr, flashed the mi max2 with the latest global stable (V9.2.1) rom. But the phone is still stuck at the Android logo with 3 dots...
I wld have thought EDL flashing wld have wiped out everything on the phone and start afresh?
I am now thinking of formatting the entire phone and reflashing it again. How wld I do that?
Thanks for any inputs.
Hi, Does EDL with test point flashing refresh the boot partitions?
I have shorted the test points and successfully reflash the phone with the latest stable global ROMs (even back to MIUI 8.5.6) but just couldn't get the phone past the MI/Android logo after restarting it
If the boot partition files have been messed up and EDL flashing is not refreshing these files, no matter how many times I try to EDL flash the device, it's not going to help. Pls correct me if I am wrong.
Any other options I can try?
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
bro thank u so muchhhhhhhhhhhhhhhhhhhhhhhh. it worked im so happy now...........was trying since hours....but u helped me mannn
Hey Folks, i just bricked My Axon 7 some Days ago. It started randomly a reboot which i can't abort anymore. Everytime the Device get's a Charge does it start again. I can't enter TWRP or Fastboot (Reboots after a few Seconds). Same for the Flash Mode. It is now completely discharged and i don't know how to recover it. Any Ideas?
Think i can't fix this, but asking here don't hurts... :angel:
4th grade unbrick guide here in the Forums. That helped me after i cannot access any Mode. No Flash Mode, No EDL, No USB, No Qualcomm Loader. Axon 7 too.
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
HighSierra1014 said:
4th grade unbrick guide here in the Forums. That helped me after i cannot access any Mode. No Flash Mode, No EDL, No USB, No Qualcomm Loader. Axon 7 too.
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
Click to expand...
Click to collapse
Lol. I made a guide based on that one but updated, called DFU unbrick, because everybody had to read my comments there anyways to be able to do it. Not sure why everyone still uses the old one ?
@Miustone: If you want, you can try an EDL cable first. A lot of people say that they could get out of DFU that way. (assuming that you can get into EDL/DFU that is). Google my guide, it's called "DFU unbrick", if the EDL cable doesn't work
Thanks Guys! I will take a look on the DFU unbrick and the EDL Cable. At least a blink of Hope for this great Device... Still good as new, would be sad to use it just as a golden Sculpture lol
Miustone said:
Hey Folks, i just bricked My Axon 7 some Days ago. It started randomly a reboot which i can't abort anymore. Everytime the Device get's a Charge does it start again. I can't enter TWRP or Fastboot (Reboots after a few Seconds). Same for the Flash Mode. It is now completely discharged and i don't know how to recover it. Any Ideas?
Think i can't fix this, but asking here don't hurts... :angel:
Click to expand...
Click to collapse
Hey, sorry for asking but how did you brick it? I am thinking about installing a custom ROM, rooting etc and I would just like to know if it was something in specific so I can stay away from it. Cheers.