Related
My provider is releasing an OTA in the coming weeks. If I purchase a new phone, can I somehow download the new OTA to my new phone, and run an update from the recovery menu of the broken phone? This phone cannot be unlocked at the moment.
techjohnny said:
My provider is releasing an OTA in the coming weeks. If I purchase a new phone, can I somehow download the new OTA to my new phone, and run an update from the recovery menu of the broken phone? This phone cannot be unlocked at the moment.
Click to expand...
Click to collapse
So whay you need to buy new phone to unbrick your old phone. Tell how do you bricked your phone and what are symptoms of your bricked phone? When you coonect your phone to usb did you getting black screen and white led? Is RSD lite detecting your phone? Tell us more information and when i will try to help you. P.S. Defy is unbrickible phone - so it very hard to brick your defy...
turffe said:
So whay you need to buy new phone to unbrick your old phone. Tell how do you bricked your phone and what are symptoms of your bricked phone? When you coonect your phone to usb did you getting black screen and white led? Is RSD lite detecting your phone? Tell us more information and when i will try to help you. P.S. Defy is unbrickible phone - so it very hard to brick your defy...
Click to expand...
Click to collapse
Okay, RSDLite sees the phone, recovery is locked, and phone reboots after showing RW (Republic Wireless) logo, which is about 2-minutes after phone is powered on. I've tried adb wait-for-device, but nothing.
It's a XT557D Republic Wireless phone. It was officially released 2-months ago. No ROM available. I replaced the Phone.apk to brick the phone.
techjohnny said:
Okay, RSDLite sees the phone, recovery is locked, and phone reboots after showing RW (Republic Wireless) logo, which is about 2-minutes after phone is powered on. I've tried adb wait-for-device, but nothing.
It's a XT557D Republic Wireless phone. It was officially released 2-months ago. No ROM available. I replaced the Phone.apk to brick the phone.
Click to expand...
Click to collapse
Try wipe data and cache from stock recovery. Did you tried this, before bricking phone: http://forum.xda-developers.com/showthread.php?t=2023933 .Try it via fastboot. Good luck
turffe said:
Try wipe data and cache from stock recovery. Did you tried this, before bricking phone: http://forum.xda-developers.com/showthread.php?t=2023933 .Try it via fastboot. Good luck
Click to expand...
Click to collapse
I've done a stock wipe/data/cache.
techjohnny said:
I've done a stock wipe/data/cache.
Click to expand...
Click to collapse
Try install cwm via fastboot. LINK: http://forum.xda-developers.com/showthread.php?t=2023933 .I know it's xt535, but it should work on xt557, because it's hardware same, just other career... Also, try this: http://forum.xda-developers.com/showthread.php?t=18273 I'm not responsible for bricked phone.
turffe said:
Try install cwm via fastboot. LINK: http://forum.xda-developers.com/showthread.php?t=2023933 .I know it's xt535, but it should work on xt557, because it's hardware same, just other career... Also, try this: http://forum.xda-developers.com/showthread.php?t=18273 I'm not responsible for bricked phone.
Click to expand...
Click to collapse
Thanks. I just tried running it from the stock recovery, and it says "signature verification failed."
techjohnny said:
Thanks. I just tried running it from the stock recovery, and it says "signature verification failed."
Click to expand...
Click to collapse
Last .: try to flash xt535 ics, i don't know if it will work, so i dont responsible for bricked phone. But i dont think that this could happen, because difference between phones are just career. Its is on general section of defy. Good luck. Edit: try to flash that file via fastboot, connect your phone to fastboot and then unpack zip and click on bat file..
turffe said:
Last .: try to flash xt535 ics, i don't know if it will work, so i dont responsible for bricked phone. But i dont think that this could happen, because difference between phones are just career. Its is on general section of defy. Good luck. Edit: try to flash that file via fastboot, connect your phone to fastboot and then unpack zip and click on bat file..
Click to expand...
Click to collapse
This phone had fastboot removed.
--tj
techjohnny said:
This phone had fastboot removed.
--tj
Click to expand...
Click to collapse
My last hope may have been removed! Here's a response from Republic Wireless on their OTA update, which I was hoping would replace my /system/app/Phone.apk that's causing my boot-loop on my XT557D:
---START
Hi ...,
I received your help request and wanted to let you know that you won't be able to move the OTA install file. It will be downloaded to the memory of the device.
---END
Would it be possible to download the digital keys that are used on this phone and sign an application to run update in stock recovery?
techjohnny said:
My last hope may have been removed! Here's a response from Republic Wireless on their OTA update, which I was hoping would replace my /system/app/Phone.apk that's causing my boot-loop on my XT557D:
---START
Hi ...,
I received your help request and wanted to let you know that you won't be able to move the OTA install file. It will be downloaded to the memory of the device.
---END
Would it be possible to download the digital keys that are used on this phone and sign an application to run update in stock recovery?
Click to expand...
Click to collapse
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
turffe said:
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
Click to expand...
Click to collapse
If I do this, I still won't be able to connect to Republic Wireless via WIFI, since they have a special ROM cooked that connects your phone to their network to update.
turffe said:
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
Click to expand...
Click to collapse
BLACK SCREEN. It looks as though it was going to flash successfully, but the M logo name came back. Now, it shows up at a modem device in my syslog of Linux. Guess I've totally bricked it now?
--tj
techjohnny said:
BLACK SCREEN. It looks as though it was going to flash successfully, but the M logo name came back. Now, it shows up at a modem device in my syslog of Linux. Guess I've totally bricked it now?
--tj
Click to expand...
Click to collapse
Can you enter to fastboot? Is it stuck on bootlogo or on animated bootanimation? If you can enter to fastboot you're just in bootloop. I will try help you much as I can.. I will try to search for XT557 files...
turffe said:
Can you enter to fastboot? Is it stuck on bootlogo or on animated bootanimation? If you can enter to fastboot you're just in bootloop. I will try help you much as I can.. I will try to search for XT557 files...
Click to expand...
Click to collapse
It doesn't even seem to want to power on anymore, but when plugged into USB, it shows up as a Qual Comm Modem?
techjohnny said:
It doesn't even seem to want to power on anymore, but when plugged into USB, it shows up as a Qual Comm Modem?
Click to expand...
Click to collapse
RSD Lite showing your phone or nothing?
turffe said:
RSD Lite showing your phone or nothing?
Click to expand...
Click to collapse
Nothing now. I forced me to manually power on the phone. I've noticed the flash model is different than the flash:
My phone: MSM7627
Flash file: MSM7227
Windows is requesting a USB driver for a modem.
No Charge LED when phone is plugged into AC.
Oh well. Didn't have high hopes this would work, but was worth the try.
techjohnny said:
Nothing now. I forced me to manually power on the phone. I've noticed the flash model is different than the flash:
My phone: MSM7627
Flash file: MSM7227
Windows is requesting a USB driver for a modem.
No Charge LED when phone is plugged into AC.
Oh well. Didn't have high hopes this would work, but was worth the try.
Click to expand...
Click to collapse
Hard brick.
XT557 spec: http://pdadb.net/index.php?m=specs&id=3753&c=motorola_defy_xt_xt556__xt557
XT535 spec: http://www.gsmarena.com/motorola_defy_xt535-4622.php
F***... Different cpu.... Sorry friend, but blame only yourself, because you started bootloop with your bad Phone.apk....... & not maded CWM backup before modding I think now you can buy new XT530 or if you have warranty sent it for repair or try to tell moto & tell that it powered down itself while charging. The service will replace board or with defy xt530 phone, which is as I know low activity device, but if you bootloop it, you can reflash stock ics via RSD....
XT557D repbulic bootloop
has anybody made any progress in the boot loop... my republic xt557d is in bootloop on moto nonanimated screen
First of all i don't know where to post,so sorry if i post in the wrong forum.
I have a huawei p8 lite ale-21 which had android 6.0 with emui 4.1(or 4.0 idk very well).I wanted to unlock the phone,and for that i had to unlock the bootleader,root and install the ROM for dual sim.Bootloader goes great,i didn't have problems in this point.But when came the root,i saw a video(i suppose to use kingroot for more safety),but i didn't see that in the video the phone was with android 5.0 and emui 3.1.The phone was in bootloop.I installed TWRP(3.0.0.2 version).I put in the sd this os:HUAWEI P8 Lite Dual SIM Firmware (ALE-L21, Android 6.0, EMUI 4.0, C185B525) and UPDATE-SuperSU-v2.46.zip.Finally,i rooted my phone from TWRP.Then i tried to install the os with dload folder in micro sd but it didn't work.I put the phone back in TWRP,wipe the cache and malwik,and install the software.But finally,when all get done i get my phone brick:no led charghing,no vol up+vol down+power button,no vol down+power button,effectively damaged.Computer can't recognize the phone,so i can't use cmd.When i connect the phone at laptop i get for few minutes an usb device(i will attach the picture) but disippears after 5 minutes.I installed the drivers,but nothing happened.Also,the phone doesn't charge via usb or charger.
Guys,I have searched all the time various methos,but all include recovery(vol down+power).If you know what my phone just happend and how to unbrick,please reply.Maybe they are some programs to unbrick that don;t allow to enter in system recovery.I really want to make this phone allive again.
Thank you guys very much!
If the phone still has warranty bring it to them, they will change our motherboard
This is a P9 lite community.
Johnny TDN said:
This is a P9 lite community.
Click to expand...
Click to collapse
Yes i know,but a moderator moved my thread from P8 to P9
theov3rc0mer said:
If the phone still has warranty bring it to them, they will change our motherboard
Click to expand...
Click to collapse
Yes,I have the warranty.But they will accept my phone?I can say 'It's a problem with the battery and I can't turn on my phone' but how the will find if I modificated the original firerware?The phone is rooted and has the bootloader unlocked
dragosneagu95 said:
Yes,I have the warranty.But they will accept my phone?I can say 'It's a problem with the battery and I can't turn on my phone' but how the will find if I modificated the original firerware?The phone is rooted and has the bootloader unlocked
Click to expand...
Click to collapse
You bring it to them saying that "my phone doesn't turn on". They can't see if your bootloader is unlockedo or not simply because the phone is dead. They have to change your motherboard and now you will have a new phone.
theov3rc0mer said:
You bring it to them saying that "my phone doesn't turn on". They can't see if your bootloader is unlockedo or not simply because the phone is dead. They have to change your motherboard and now you will have a new phone.
Click to expand...
Click to collapse
i hope it will works.i will get the warranty in few day.when i will bring them the phone i will tell you.thank you for your advice!
@dragosneagu95 same happened with my former phone Honor 4C,,, it was rooted, xposed and BL unlocked too...
after some days, i turn it on and open clash of clans,,, all screen goes orange in color,,, and phone off,,, it never show me any screen just light up on screen,,, i can see white screen of fastboot too,, BL was not relocking,,, i was afraid that they will say warranty voided after fastboot screen commands,,, i bring to them saying its damaged,,, the supplier type no power, no lcd and sent back to huawei,, they give me new 4C,,, with new warranty card of that phone.... hope they will help you too!!
@HassanMirza01
HassanMirza01 said:
@dragosneagu95 same happened with my former phone Honor 4C,,, it was rooted, xposed and BL unlocked too...
after some days, i turn it on and open clash of clans,,, all screen goes orange in color,,, and phone off,,, it never show me any screen just light up on screen,,, i can see white screen of fastboot too,, BL was not relocking,,, i was afraid that they will say warranty voided after fastboot screen commands,,, i bring to them saying its damaged,,, the supplier type no power, no lcd and sent back to huawei,, they give me new 4C,,, with new warranty card of that phone.... hope they will help you too!!
@HassanMirza01
Click to expand...
Click to collapse
thank you for your information.when i will bring them the phone i will tell you what happened
today I brought the phone to customer.she said tomorrow she will sent the phone to service,I will need to wait 15 days and the service will send me an e-mail with the process.i told to customer 'that is a problem with the battery,i can not turn on the phone' and that's what she wrote to warranty.i am very nervous about the guys from the service,i hope they will don't find a way to see that I moficated the OS.i keep you guys with the news!
My phone is back to live!I went to take my phone from the shop.On the bill it writes that they have intervened to the phone.I think they changed the battery and wrote the OS.I am glad that i have my phone back!
Hello,
I am from Greece and Ive bought from Vodafone a Huawei P9 lite vns-l21 before one month. Ive installed the nougat rom 370 with firmware finder but I made a mistake choozing the NRD-90M test key. So I begun to roll back to Marshmallow. Everything ok. Then Itried to install an other rom from firmware finder(i think C432b371) and again NRD-90M test key...
Again roll back to Marshmallow...so in the first step when i was trying to install with dload method the Huawei P9 Lite Rollback Package For L21C432 (EU) my phone stucked on boot loop but I had fastboot. Then I have unlocked the bootloader to see if there is anything that i can do with srk tool and now i have a beautifull bricked phone stuck :
"Your device has been unlocked and can't be trusted.
you device is booting now"
In this point nothing happens, I can not go to fast boot, No recovery mode, The hardware keys not doing anything, only resetting the phone in loop..
I dont know what to do and Huawei wants 215euro to fix my phone.
My mistake I know but is there enything that i can do know? Its a new phone!
Sorry for my english
I would suggest getting an sdcard and creating a dload folder inside, then putting an official rom UPDATE.APP file inside the dload folder and try 3button method
o-w-a said:
I would suggest getting an sdcard and creating a dload folder inside, then putting an official rom UPDATE.APP file inside the dload folder and try 3button method
Click to expand...
Click to collapse
Thanks for the advice but I have already tried that with stock rom B161 and nothing happens with 3 button method. Still in the same situation.. Everything i do with the buttons the phone resetting and stays on until the battery is dead..
ioanpara said:
Thanks for the advice but I have already tried that with stock rom B161 and nothing happens with 3 button method. Still in the same situation..
Click to expand...
Click to collapse
do you get verification error or is it just stuck at "your devices is booting now"
o-w-a said:
do you get verification error or is it just stuck at "your devices is booting now"
Click to expand...
Click to collapse
Stuck on "your device is booting now".
ioanpara said:
Stuck on "your device is booting now".
Click to expand...
Click to collapse
As far as I understand, you can't even power off your device which is a problem since the 3button method won't work if you can't power off the device.
o-w-a said:
As far as I understand, you can't even power off your device which is a problem since the 3button method won't work if you can't power off the device.
Click to expand...
Click to collapse
Exactly!
I am still in the same situation... Anyone who knows what to do?
ioanpara said:
Hello,
I am from Greece and Ive bought from Vodafone a Huawei P9 lite vns-l21 before one month. Ive installed the nougat rom 370 with firmware finder but I made a mistake choozing the NRD-90M test key. So I begun to roll back to Marshmallow. Everything ok. Then Itried to install an other rom from firmware finder(i think C432b371) and again NRD-90M test key...
Again roll back to Marshmallow...so in the first step when i was trying to install with dload method the Huawei P9 Lite Rollback Package For L21C432 (EU) my phone stucked on boot loop but I had fastboot. Then I have unlocked the bootloader to see if there is anything that i can do with srk tool and now i have a beautifull bricked phone stuck :
"Your device has been unlocked and can't be trusted.
you device is booting now"
In this point nothing happens, I can not go to fast boot, No recovery mode, The hardware keys not doing anything, only resetting the phone in loop..
I dont know what to do and Huawei wants 215euro to fix my phone.
My mistake I know but is there enything that i can do know? Its a new phone!
Sorry for my english
Click to expand...
Click to collapse
Hmm I dont get why they want 215 euro to exchange the storage chip.
I guess your phone is pretty much a brick now have fun. Lol sry
I had a similar problem with the boot-loop.
Press PowerOff until the screen goes black, and then immediately leave power-off and press Power Off + Volume Up for ever until the phone boots normally.
That's what I did and worked for me.
Can you boot to fastboot, if you can you can recover it with DC-Phoenix tool.
Dejan Kruljac said:
Can you boot to fastboot, if you can you can recover it with DC-Phoenix tool.
Click to expand...
Click to collapse
No he cant, I have the same problem. Cant fastboot, adb or 3 button method. Even tried unplugging battery then doing 3 button method.
Anyone sopve this problem with no fastboot no recovery no 3 buttons mode?
try to drain the battery, keep screen on, or keep phone on until battery is 0%, you can't turn it on . keep volume down and power pressed, plug usb to pc , if you're lucky fastboot could be ok
Hi there, I also managed to brick my P9Lite - no recovery, no fastboot. After draining the battery completly the phone starts fine but I can't install system updates. I guess I have to live with that. Unfortunately I can't activate bluetooth. Does anyone has an idea how to get bluetooth working again?
idk for your BT issue , but did you try Firmware Finder for Huawei ? easy to use, you will probably able to dl an update. don't use "small " package OTA, use full firmware, about1.6 or 1.8 Go, may could fix your BT.
sonneper said:
idk for your BT issue , but did you try Firmware Finder for Huawei ? easy to use, you will probably able to dl an update. don't use "small " package OTA, use full firmware, about1.6 or 1.8 Go, may could fix your BT.
Click to expand...
Click to collapse
didn't work out as Firmware Finder is only another way to find a firmware but not another way to install the firmware...
Hello guys,
sorry if i write this but i think necessary to grab best helps..
Try to describe problem in detail (ex. - i was upgrading/downgrading from..........to............ firmware and it bricks, etc...)
Your latest working phone/system/firmware (ex. - mine was VNS-L31C432B381-before i upgraded to EliteRom).
Some information changes according to the country / region of the world in which you live,
so they are useful for those who help you to redirect to the correct thread / give right suggestions...
All the best guyz
didn't work out as Firmware Finder is only another way to find a firmware but not another way to install the firmware...
Yes , a way to get last firmware, or firmware you want through the huawei update app. Without firmware finder ,no way to " force" huawei update app to install anything you want on your device
Sorry for the late response, I'm reading the thread right now. Firmware Finder can also be used to install firmware through eRecovery. Install Firmware Finder for Windows: http://pro-teammt.ru/projects/hwff/v2/GetLatestVersion.action
You need to write down your existing and change both DNS addresses in your router to: 81.177.139.39
You also need to deactivate IPv6 protocol.
Open FirmwareFinderRewrite.exe, go to "common base" and search VNS-LXXCXXX (Your model and customization). Copy the link in "changelog" not of the newest, but of the 2nd or 3rd youngest firmware. Check if it has been approved by pasting the link under the tab with the checkmark (5th position counting from left). If the response is "This firmware was approved to install" you are ready to go.
Copy the same link in the proxy field (the cloud symbol, 4th position counting from left). Click on "set" and "register update".
Now switch off your phone, press "Vol+" and simultaneously connect it to the PC. You enter eRecovery now. Tap on "Download latest version and recovery". Your phone should start the download now, after a couple percent you can reset your router settings, the download will continue. If all is well, the firmware will then be installed.
Hi Guys my MI A1 was bricked i just use the test point to fix and my pc recognized as Qualcomm 9008 so flashed latest 8.0 everything worked but wifi and bt was broken so i decided again to put in EDL and flash it with same firmware after that MI flash shows success but device doesn't turn it jsut keep blinking led and goes to EDL everytime i connect to PC...tried with Nougat and Oreo firmwares same...i checked logs and saysthat device is successfully flashed and rebooted...but nothing just black screen and blinking led..Can anyone Help me?I can't send to Service because i will need to wait 1 month also i opened the back cover so i lost the warranty.....:crying::crying:
Hi,
did you try to flash with qfil or only mi flash ?
I'm not sure but may you ask Cosmic Dan he was planing to do an unbrick guide and he mentioned files which you can use with qfil to unbrick your device. I don't know how far he is with it.
But if you did manage to unbrick so far and only BT and WiFi is your issue aren't there several fix guides for the persist partition ?
For my personal experience after I had to unbrick my old n6p I had the same issue after flashing. Phone stays black and led just blinking. Try to long pressing power, or other button combinations while plugg and unplugging USB to pc and I mean really long pressing the buttons. It sounds a bit weired but my n6p came back and booted as usual.
I'm sry, but I can't tell you the right combination because I tried so much that time, because it was my only phone.
Good luck !
Bro if You Have A Backup Of Your phone Then flash It.
Sent from my [device_name] using XDA-Developers Legacy app
Qfil doesn't work because we have A/B Partition Layout....i have backup of my partitions that's not issue....
How much battery had you left at flashing ? May its just drained and not able to boot. Sometimes it's the stupid and simple things. If you have partition backups you should be able to fix your WiFi and BT.
coremania said:
How much battery had you left at flashing ? May its just drained and not able to boot. Sometimes it's the stupid and simple things. If you have partition backups you should be able to fix your WiFi and BT.
Click to expand...
Click to collapse
70%
Alek Dev said:
Hi Guys i ws experimenting something with my device so i bricked fully i just use the test point to fix and my pc recognized as Qualcomm 9008 so flashed latest 8.0 everything worked but wifi and bt was broken so i decided again to put in EDL and flash it with same firmware after that MI flash shows success but device doesn't turn it jsut keep blinking led and goes to EDL everytime i connect to PC...tried with Nougat and Oreo firmwares same...i checked logs and saysthat device is successfully flashed and rebooted...but nothing just black screen and blinking led..Can anyone Help me?I can't send to Service because i will need to wait 1 month also i opened the back cover so i lost the warranty.....:crying::crying:
Click to expand...
Click to collapse
You can get it back. You have lost the Wifi and Bluetooth (Mac Address files). You can boot your phone if it is in edl mode. Just press the Power Button for more than 30-40 seconds. Your phone will boot. If possible, try to stick the back cover and show it to service center. They will change your phone's motherboard! They don't know about edl and everything! They only change internal parts! :good:
birarvindersingh said:
You can get it back. You have lost the Wifi and Bluetooth (Mac Address files). You can boot your phone if it is in edl mode. Just press the Power Button for more than 30-40 seconds. Your phone will boot. If possible, try to stick the back cover and show it to service center. They will change your phone's motherboard! They don't know about edl and everything! They only change internal parts! :good:
Click to expand...
Click to collapse
Yes Go service centre When Your phone in warrenty.
Sent from my [device_name] using XDA-Developers Legacy app
Try updating your drivers. Happened to me once, MiFlash didn't detect it, but driver MANUAL update helped.
If u r using Mac Then Try in windows with Fastboot Rom.
Phone sent to Service Center....hopefully they will repair with my warranty,So No releases/No Builds around 1 month
After lot of waiting (FROM 23 MAY) this is what i got from my service center
" AFTER SERVICE REVIEWS AND SOFTWARE INSTALATION DEVICE REMAINS WITH A LOADING / DAMAGED MEMORY CHIP"
"The phone is stuck in EDL Mode due to improper use and serious damage from all sides. The same after a service overview and software installation could not be turned on or raised (shows no signs). The service order states that if you want to service, you will be offered an offer to change the motherboard. Greeting"
After that they tell me this"
"Otherwise, changing the motherboard with a working hand would be around 182 USD. Greeting"
i don't have that money it's too much expensive for me so i'm without any phone....
Alek Dev said:
Qfil doesn't work because we have A/B Partition Layout....i have backup of my partitions that's not issue....
Click to expand...
Click to collapse
I restored my Mi A1 at least 3 times with QFIL, not a problem.
meltbanana said:
I restored my Mi A1 at least 3 times with QFIL, not a problem.
Click to expand...
Click to collapse
What version of QFIL? What OS did you have? what firmware did you use? or you have made backup with qfil then restore it? if you have that will be good to send me at least i can try it ....i ussually get this error dmssfail with QFIL.....ty
Alek Dev said:
What version of QFIL? What OS did you have? what firmware did you use? or you have made backup with qfil then restore it? if you have that will be good to send me at least i can try it ....i ussually get this error dmssfail with QFIL.....ty
Click to expand...
Click to collapse
Windows 10 Pro, QFIL latest (2.7 or so), I used the latest stock ROM (tissot_images_V9.5.11.0.ODHMIFA_8.0) provided by Xiaomi.
I can only recommend to extract a ROM to a path close to your volume root, for example D:\Temp\tissot_images_V9.5.11.0.ODHMIFA_8.0.
By using deeper paths you'll probably get errors. Flat build. :good:
meltbanana said:
Windows 10 Pro, QFIL latest (2.7 or so), I used the latest stock ROM (tissot_images_V9.5.11.0.ODHMIFA_8.0) provided by Xiaomi.
I can only recommend to extract a ROM to a path close to your volume root, for example D:\Temp\tissot_images_V9.5.11.0.ODHMIFA_8.0.
By using deeper paths you'll probably get errors. Flat build. :good:
Click to expand...
Click to collapse
Thanks when i get the phone back from my carrier i will try it and post here
@meltbanana What Drivers did you use? some link?
Alek Dev said:
@meltbanana What Drivers did you use? some link?
Click to expand...
Click to collapse
I used the drivers provided by QFIL. Btw. flashing a flat build by QFIL recreates the partition layout, it really doesn't care about two system partitions.
Flashed EDL mode when I went back from treblizing earlier without going back to stock partition layout in first place.
Qualcomm Flash Image Loader handled it flawlessly to restore the standard gpt provided by rawprogram0.xml .
meltbanana said:
I used the drivers provided by QFIL. Btw. flashing a flat build by QFIL recreates the partition layout, it really doesn't care about two system partitions.
Flashed EDL mode when I went back from treblizing earlier without going back to stock partition layout in first place.
Qualcomm Flash Image Loader handled it flawlessly to restore the standard gpt provided by rawprogram0.xml .
Click to expand...
Click to collapse
So it restores the partition layout right? Also can you provide me link of QFIL?
Alek Dev said:
So it restores the partition layout right? Also can you provide me link of QFIL?
Click to expand...
Click to collapse
true, it restores the default partition layout, please pick one, that's what I used: https://duckduckgo.com/?q=QPST_2.7.438.3&atb=v89-4_g&ia=web
and here's the ROM link provided by Xiaomi: http://bigota.d.miui.com/V9.5.11.0....0.ODHMIFA_20180504.0000.00_8.0_1a04581058.tgz
My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
me too
waiting, someone pls
LeandroFarias said:
waiting, someone pls
Click to expand...
Click to collapse
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed).
That is the points
vinod3362 said:
That is the points
Click to expand...
Click to collapse
What?
me too. after i reboot my poco m3. it came to black and wont boot up. i google everything, the only need to flash is to modified the firehose. badly needed.
KaMyKaSii said:
My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
Click to expand...
Click to collapse
how do you get into fastboot?? i tried mine but it wont boot in fastboot. i'm stuck in QDLoader.
did someone successfully recover their bricked poco m3 ?
gasleak08 said:
did someone successfully recover their bricked poco m3 ?
Click to expand...
Click to collapse
nothing yet. we need firehose to bypass miflash authentication. or drain the battery then press vol down + power for 10secs.
KaMyKaSii said:
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed). Are you Brazilian too? Call me on telegram
Matheus
You can contact @MatheusCoelho1998 right away.
t.me
Click to expand...
Click to collapse
can u tell me how?mine too?
my phone has bricked with UBL condition and i flash whole partition with twrp and magisk to solve the heating problem now its alive again
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Minoda86 said:
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Click to expand...
Click to collapse
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
I did update it and now my phone wont boot at all,after the battery hits 1%,it just wont do anything and its been 2 weeks,pc does detect it as qualcom loader but flashing without auth wont work,Im just waiting for firehose file for this stupid phone.People with auth asking for $30 for fixing it but without guarantee that it will work,what a joke.
So did you fix your phone?
yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
Yeahhh,my phone finally boot up!
But sadly the latest update failed to install.Guess I should just wait until someone patch the firehose file and try not to update until then.Fingercross!
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
vinzikidz said:
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
Click to expand...
Click to collapse
how did u fix deadboot can you elaborate? how did you flash from edl ?
gasleak08 said:
how did u fix deadboot can you elaborate? how did you flash from edl ?
Click to expand...
Click to collapse
sorry, there's is no tutorial for this and it has a quite process. you just need to throttle the proc temperature of your phone board using hot blower or any device you have. while your phone is in high temp. both pin board and battery is in unplug hold vol down then put back the board pin and battery pin at the same time. it will vibrate and fastboot will be fine.
Guys this is my procedure to turn on the phone:
I can make it turn on Android after messing with the battery and sub-board cables but this is just a workahound, trying to turn it on normally through the power button always makes it turn on in edl mode
But opening the device voids the warranty, so anyone who has access to a repair center is better off asking for the warranty
What to do:
1. Disconnect the battery cable and the secondary board cable.
2. Connect charger.
3. Hold the power button.
4. Connect the secondary board cable and quickly connect the battery cable.
5. Release the power button when the device vibrates.
It doesn't always work the first time, you may need several tries to get it
VID_20210514_152510.mp4
drive.google.com