i have a Nokia x which i was trying to install the new update via the Stock Recovery after flashing the file i click reboot system now but my phone never turned on and i also tried to boot in twrp but still do not start up and not even charging and nokia care suite does not detects it but the pc detects it in the Device Manager/ports.
how do i fix my phone
thank you,
Related
Hi guys hopefully I posted this in the right place. I have a rooted Nexus 5 with multirom installed and had a few ROMs in mind that I wanted to try out, most of them just installed simply and booted without problems however when I chose to try and install slimrom or another (can't remember the name of the other ROM sorry) a message would appear stating I need to install a different bootloader IMG to install/ boot that ROM. I searched around for a while and found an image to install through twrp but when I installed it I now can't boot the phone to launch a ROM or get into recovery mode as the screen will go black. Any ideas? I'm trying to used adb to install a twrp img but so far it doesn't detect the device :/ I would much appreciate any help or suggestions! Ask me if you have any questions! Thanks.
Have tried to flashing back to a completely stock rom?
Problem is I can't get my computer to recognize my nexus 5 in the boot loader mode if I could I could then flash twrp again and flash the stock rom but it doesn't detect
Does the phone boot into fastboot mode? You tried different USB ports, cables, computers, and operating systems?
The only mode I can get my Nexus into is boot loader mode so yes fast boot. I have a windows xp and 8 so I use 8 as its the only PC that I can run adb & fast boot on without problems. I have used a USB cord the recognized my sisters phone also so it shouldn't be a faulty cable I'm pretty sure. Thanks for those ideas I appreciate your help a lot!
Rooted Droid said:
The only mode I can get my Nexus into is boot loader mode so yes fast boot. I have a windows xp and 8 so I use 8 as its the only PC that I can run adb & fast boot on without problems. I have used a USB cord the recognized my sisters phone also so it shouldn't be a faulty cable I'm pretty sure. Thanks for those ideas I appreciate your help a lot!
Click to expand...
Click to collapse
Use the cable that came with the phone.
Use this well made thread
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I once wiped my system and rebooted and got stuck in a loop. at his thread is what I used to save my phone. Hope it helps.
Sent from my Nexus 5 using Tapatalk
Speaking from personal experience, I found that the USB cable could make a difference. I also have Samsung phones and, although the USB cable allowed win7 to install drivers, I could never flash anything. Once I switched back to the original cable, flashing works without any problems.
tahnks guys i managed to fix my problem using the nexus in bootloader mode on Windows 7 as windows 8 and xp wouldn't recognize it for some reason. From there i managed to install twrp reset the device, flash theserurection remix rom and flash a correct bootloader. Thanks for your help as it lead me in the right direction!
Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
joao.m.neto said:
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
Click to expand...
Click to collapse
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Mr.Ak said:
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Click to expand...
Click to collapse
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
joao.m.neto said:
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Yes,as I said, could be a battery issue but we are still not sure yet.I can give you the link for winxp or win7 if you need and then you can dual-boot it alongside windows10.You should install drivers from cm11s restore toolkit thread(executable drivers),maybe then your device will show up in device manager though it is highly advised to do this on Xp or 7 since 8,8.1 and 10 has driver signing issues.
Hi Guys,
I got a Moto Z from US recently(I live in Asia).One day I was charging my phone.I got uncomfortably hot.So I decided to power off my device and when i restarted it,it got stuck on bootloop.I did try factory resetting my phone and then went to Motorola Service Center.Even though it was under warranty they refused to service it because it is from another country(Even though I agreed to pay $300 they were charging for a MoBo replacement.
After any hope of getting the device up and running,I tried to update the device in fastboot mode.I made the mistake of using an older firmware thereby Hardbricking my device
I did manage to get it to back to life by using this file
https://forum.xda-developers.com/mo...-to-unbrick-moto-z-hardbricked-t3590133/page2
(post#18)
Step 1: If your PC detect the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.
(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)
Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.
Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.(thanks to:manish54 ,benzinerwin)
Then I started to update the stock ROM.But it wont take any gpt.bin(GUID Partition Table) files.
(error)Preflash Validation failed
Without GPT I cant update anything at all.If anyone can help that would be great.
I have an Alcatel Onetouch Pixi 3 (10) Wifi 8079 tablet with an MT8127. I tried flashing a twrp recovery following Kirito’s guide but I had a glitching screen in a bootloop instead, so I tried flashing another twrp providedby the same user (was named twrp-new) and instead of the glitchy screen this time I’d see the twrp logo and then it would auto reboot after giving several unable to mount data errors. I was not able to do anything in twrp.
I then formatted the whole device except the bootloader. I realize that I should now be flashing a ROM (I have all the required stock ROM files including the scatter file) but SP Flash Tool won’t recognize my device (on three different OSes: Win7, Win8.1, a Linux distro). I also tried out Mobile Upgrade S but it too won’t see my device.
The device’s battery is soldered with three wires to the motherboard, so I can’t easily plug it out. Why do you think that my laptop won’t detect the device? Could it be that the tablet is running all the time (so it’s not off) and the battery lasts long because the device isn’t performing any operations?
As for drivers, when I used SP Flash Tool to flash the new twrp, I didn’t install any drivers myself on Windows 7. Now that it didn’t recognize my device, I installed all kinds of drivers on both Win 7 and 8.1 like MediaTek VCOM USB and Preloader drivers but I stll couldn’t get it to work. I get no feedback from my device no matter what I do (power button, volume up and down buttons).
Do not say that it is hard bricked because all I did was formatting the device except the bootloader.
tesiz22 said:
I have an Alcatel Onetouch Pixi 3 (10) Wifi 8079 tablet with an MT8127. I tried flashing a twrp recovery following Kirito’s guide but I had a glitching screen in a bootloop instead, so I tried flashing another twrp providedby the same user (was named twrp-new) and instead of the glitchy screen this time I’d see the twrp logo and then it would auto reboot after giving several unable to mount data errors. I was not able to do anything in twrp.
I then formatted the whole device except the bootloader. I realize that I should now be flashing a ROM (I have all the required stock ROM files including the scatter file) but SP Flash Tool won’t recognize my device (on three different OSes: Win7, Win8.1, a Linux distro). I also tried out Mobile Upgrade S but it too won’t see my device.
The device’s battery is soldered with three wires to the motherboard, so I can’t easily plug it out. Why do you think that my laptop won’t detect the device? Could it be that the tablet is running all the time (so it’s not off) and the battery lasts long because the device isn’t performing any operations?
As for drivers, when I used SP Flash Tool to flash the new twrp, I didn’t install any drivers myself on Windows 7. Now that it didn’t recognize my device, I installed all kinds of drivers on both Win 7 and 8.1 like MediaTek VCOM USB and Preloader drivers but I stll couldn’t get it to work. I get no feedback from my device no matter what I do (power button, volume up and down buttons).
Do not say that it is hard bricked because all I did was formatting the device except the bootloader.
Click to expand...
Click to collapse
Did you ever get this resolved? I have this same exact problem just with a different device
ayetab said:
Did you ever get this resolved? I have this same exact problem just with a different device
Click to expand...
Click to collapse
I have got it all resolved. My device is running fine with Magisk. I recommend that you take a look at my post history.
tesiz22 said:
I have got it all resolved. My device is running fine with Magisk. I recommend that you take a look at my post history.
Click to expand...
Click to collapse
How do I see your post history? I have a Blu view 3 and pc recognizes it cause I hear the ding sound I'm stuck in fastboot mode cause dm-verity failed I need to flash stock eom but flash tool just sits there nothing happens.
Kireej said:
How do I see your post history? I have a Blu view 3 and pc recognizes it cause I hear the ding sound I'm stuck in fastboot mode cause dm-verity failed I need to flash stock eom but flash tool just sits there nothing happens.
Click to expand...
Click to collapse
I don't know what a Blu view 3 is, but you can click my name to open my profile and hit "postings" to see my post history.