Hi guys, first of all, thanks for all the help that you guys from here always give me.
For my problem:
This phone was in the latest version (5.1), i've downgraded to 4.4.4 via RSD Lite. I was updating via OTA to 5.1 again, when it was fineshed upgrading (the battery was 100%) the phone reset in fastboot with error "Invalid CID" so i came here and find an answer to only flash again via RSD the 4.4.4 and it would be fine. So i tryed it, but can't flash anything anymore, always returns error... via RSD, via fastboot and everyhing i tryed to flash into.
In PC it recognize as "mot single adb interface", so it is softbricked... i saw a tutorial to recover hardbricked, regarding to flash a blank bootloader via qflash, but i cant get the com port that it is using...
Can I get flash this blank bootloader from fastboot?
Any other ideas how to recover this baby phone?
Thx in advance
Related
Hi, my best friend she had a HD phone, one day got stuck into the M logo, the only thing I can do is get into the fastboot, no recovery no nothing.. So i try to reinstall the rom, have download several tools but i cant do anything, after several intents to install roms i hace in AP fastboot flash mode, device is unlocked status code 1fastbookt Reason sticky bit factoy_fastboot. for a 2nd time but i can install roms, I dont know if phone bootloader unlock and cant check... I dont know if phone is usb debugging cause it wont load the system. I dont see any internal files from phone I also try rsd lite, but the same it says that it start doing the process but nothing else happen.. any ideas on how to get a rom install there..
thanks
SAME thing..
Please do help us...No recovery...No debugging...stuck at logo..!!
If you don't have an unlocked bootloader, I don't think you can use Myth or RSD to flash an ICS rom over a JB rom.
Did you load the latest Motorola USB drivers? When you connect the phone, run adb to list the devices. Does your phone appear?
not for me doesnt show any devices... and while trying to do other commands always get stuck ad *daemond started succesfully* but doesnt do anything.. also when trying to use motorola device manager it says it will update and never connect to server and close the app.
if i do fastboot commands like reboot-loader it does work it reboots the phone, but if i try to flash something doesnt it doesnt do anything.. i try using mfastboot also and the same happen.
Is there a way to flash a rom or something so i can fix this phone or it is dead?
On the Fastboot screen, if it says UNLOCKED in capitals next to "Device Status:" , then this problem is easily fixable.
Download RSD Lite from here: http://forum.xda-developers.com/showthread.php?t=2231249
Download Motorola Stock Firmwares:
Stock Jellybean for AT&T: http://sbfdownload.droid-developers...MB886_NII_TA-2-16-release-keys-NII-MX.xml.zip
Stock Jellybean for Bell Canada: http://sbfdownload.droid-developers...FFW-11-4-release-keys-BellMobility-CA.xml.zip
Open up your zip file and replace the .xml with the new XML you will download from this link: https://www.box.com/s/num1eshkf0c2or2h4160 You really can't forget to do this!
Launch RSD, connect device to PC, make sure RSD recognizes it. Navigate to your firmware file, select it, and press the start button. Sit back, relax, and let it do its work. It will take around 5-10 minutes. Do not unplug the cable, and do not attempt if you are in a situation in which you think you may lose power (especially if running from a desktop PC).
If RSD Lite won't work, then this thread will show you how to manually flash your stock firmware: http://forum.xda-developers.com/showpost.php?p=40929335
Basically, you repeat all the instructions I just gave you and then manually input some lines in Command Prompt.
X1053, rooted and unlocked bootloader on T Mob US
Tried to install a new kernel but it failed. Wiped cached (factory reset in twrp) and now it won't boot past the animation logo.
As its not booted into the OS, windows won't recognize it as a device so i can't install a new rom to try again. Windows 8 'bings' when I connect it but it won't load as a drive.
I CAN get into AP Fashboot Flash Mode If I then go to Recovery, it still takes me to twrp. But there are not zip files to install that work and I can't work out how to copy them over without windows recognizing the device?
Thanks in advance
You'll maybe need to flash the same stock firmware version you're on now...4.4 or 4.4.2 or whatever version you were on. Then root again.
This will help you...
http://forum.xda-developers.com/showthread.php?t=2603358
Good luck!
kj2112 said:
You'll maybe need to flash the same stock firmware version you're on now...4.4 or 4.4.2 or whatever version you were on. Then root again.
This will help you...
http://forum.xda-developers.com/showthread.php?t=2603358
Good luck!
Click to expand...
Click to collapse
Thanks for the reply. the problem is I can't connect to the phone to transfer a new firmware on. It 'bings' on USB plug but won't open as a USB drive. I can't get the phone to boot, can only get it to recovery. i tried reinstalling the motorola drivers again but still no luck.
When it was running Ok, I could plug it in (when it used to load into the android OS OK) and it would appear as a USB drive in Windows 8. I also tried on a different laptop.
emailrob said:
Thanks for the reply. the problem is I can't connect to the phone to transfer a new firmware on. It 'bings' on USB plug but won't open as a USB drive. I can't get the phone to boot, can only get it to recovery. i tried reinstalling the motorola drivers again but still no luck.
When it was running Ok, I could plug it in (when it used to load into the android OS OK) and it would appear as a USB drive in Windows 8. I also tried on a different laptop.
Click to expand...
Click to collapse
When you boot into bootloader, does the phone itself recognize that it is connected via USB? If so, you have to obtain the current SBF of your phone and flash over the files via fastboot.exe and mfastboot.exe.
There are plenty of guides throughout this site. Take your time and read everything before you make your first move.
Cyphir said:
When you boot into bootloader, does the phone itself recognize that it is connected via USB? If so, you have to obtain the current SBF of your phone and flash over the files via fastboot.exe and mfastboot.exe.
There are plenty of guides throughout this site. Take your time and read everything before you make your first move.
Click to expand...
Click to collapse
OK panic nearly over! I managed to get it flashed using RDS lite. 4.4 is back on now, although I lost my root Not sure I want to go down the whole downgrade to 4.2.2 etc but I'll see. Thanks again
Just adding a reply in case anyone has a similar issue.
RSDLite managed to get the firmware back on. It lost root, but what actually happened is the recovery got deleted / corrupted.
So i went back through the rooting guide which started by adding twrp and then flashing. Rebooted, and SuperSU tells me all is OK and root is there.
:laugh:
Is your phone recognized by fastboot or adb?
Since your bootloader is unlocked, manually flash the 4.4.2 firmware files, then TWRP, then boot into recovery, use adb to push SuperSU or whichever root program you prefer to /sdcard, then use TWRP to flash it.
nhizzat said:
Is your phone recognized by fastboot or adb?
Since your bootloader is unlocked, manually flash the 4.4.2 firmware files, then TWRP, then boot into recovery, use adb to push SuperSU or whichever root program you prefer to /sdcard, then use TWRP to flash it.
Click to expand...
Click to collapse
Its all working OK now thanks. I just flashed 4.4 again and re-installed TWRP.
Hey guys,
I think I might have bricked my phone. I've installed yesterday a new firmware (device is s off, rooted). Version 6.09.401.5. So far so good. Downloaded a new ROM. Wiped everything including sdcard in twrp, then tried to push the rom to the sdcard. Also worked. But, I can't install it. Tried 100 different recoveries. It keeps me saying that it can't mount /system. Tried another firmware, but this time it failed (don't know why, it hang on the RUU screen, and windows didn't detect my m7 anymore). So i tried to boot in the bootloader (I think the firmware update failed..) I get the normal bootloader screen, but now fastboot isn't working anymore. My phone get's recognized by adb in recovery, but nothing other than that. i tried to install another rom again, but this time it sais that /cache /system etc. are unmountable. What have I done? Can someone help me or did I just brick the device?
Yeah, this means I can't get by no means inside the RUU environment, so I can't flash a new firmware. The phone doesnt get recogdnized by Windows in the bootloader, however the bootloader screen is normal. So can't use fastboot.
Okay, little update guys. Picked up a Windows 8 machine (mine was running on 8.1) So fastboot works. Tried to flash firmware, but now it sais remote: not allowed. Any idea's? Tried 2 different firmware packages.
Alright! Got it fixed. Here's the solution:
Thanks to Windows 8.0, not 8.1, i was able to flash a firmware, so that windows recognized the phone again. Then, picked up a flashable firmware zip (~1GB) and flashed it via the standard procedure. I think that that repartitioned the whole device, so that the original rom could be installed via the firmware.
My phone is rescued again, thanks xda!
batuhanxtx said:
Alright! Got it fixed. Here's the solution:
Thanks to Windows 8.0, not 8.1, i was able to flash a firmware, so that windows recognized the phone again. Then, picked up a flashable firmware zip (~1GB) and flashed it via the standard procedure. I think that that repartitioned the whole device, so that the original rom could be installed via the firmware.
My phone is rescued again, thanks xda!
Click to expand...
Click to collapse
Did you just have a 6 post conversation with yourself and change your name on the 7th post ?
Most people here know about windows 8.1 and fastboot
a little reading would have saved you a lot of stress
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!
Help Please.......
So I've owned sammy devices before in the past and never been afraid to flash custom kernels/roms etc on them. Since the p9 was the first Huawei device I've owned i was a little scared to flash it. But it got too much for me and i tried, and fail Now i have a P9 that doesn't work and a very upset wife because I've killed my phone.
So what i did was tried to flash via dload 3 button method a nougat fw (official)but had no camera/file manager/calendar etc. Found it was possible to downgrade via flashing a downgrade fw. I cant remember what nougat fw i tried to flash but in the about device the build number was nrd10testkeys or something like that. My official fw before was EVA-L09C706B145. After flashing the downgrade fw my phone rebooted and just hung at the Huawei boot splash screen. All i can do now is access fastboot by holding vol - while plugging in usb. I cant access recovery/cant boot past Huawei splash screen. I have tried fastboot flashing via adb but it fails due to permission error (thinking because of locked bootloader?) Have tried using Huawei updater with hisuite to recover device, download, unpacks and installs recovery to 99%then fails. Pleaee help me fix my phone so i can get back into the goodbooks with the wife.......
Tia all
Try following post #4 instructions from here: https://forum.xda-developers.com/p9/help/failed-downgrade-nougat-to-mm-bricked-t3464156