So I think i did something stupid.
I was trying to get MIUI working see (http://forum.xda-developers.com/showpost.php?p=58366462&postcount=159).
Changed the kernel modules and firmware of the rom but I kept aboot.bin to be flashed to my device.
MIUI didnt boot just black screen.
Used TWRP to recovery my system/boot and so on.
Phone still doesnt boot screen black.
I put the device in boot mode but my laptop doesnt detect a usb device. Neither in windows or linux (lsusb).
So I cant manage to use FashBoot none of the versions. I downloaded the tot and the kdz. But without my device being detect I cant do anything with it.
Is there another way to get stock back?
* Edit:
So I figured I look a bit into the G2 forums to find for solutions.
I discovered if i erase my boot partition dd if=/dev/zero of=boot
The devices automaticly boots in fastboot mode.
From fastboot mode i managed to flash to correct aboot.img again and after that boot mode worked again.
grimpy said:
So I think i did something stupid.
I was trying to get MIUI working see (http://forum.xda-developers.com/showpost.php?p=58366462&postcount=159).
Changed the kernel modules and firmware of the rom but I kept aboot.bin to be flashed to my device.
MIUI didnt boot just black screen.
Used TWRP to recovery my system/boot and so on.
Phone still doesnt boot screen black.
I put the device in boot mode but my laptop doesnt detect a usb device. Neither in windows or linux (lsusb).
So I cant manage to use FashBoot none of the versions. I downloaded the tot and the kdz. But without my device being detect I cant do anything with it.
Is there another way to get stock back?
* Edit:
So I figured I look a bit into the G2 forums to find for solutions.
I discovered if i erase my boot partition dd if=/dev/zero of=boot
The devices automaticly boots in fastboot mode.
From fastboot mode i managed to flash to correct aboot.img again and after that boot mode worked again.
Click to expand...
Click to collapse
Glad you're sorted & posted the solution.
Related
Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic
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!
I updated my oneplus and i got the TWRP decryption message, so i formatted it back to the stock format.
now all the phone does is boot into the bootloader but gets stuck on the boot screen of Blu Spark 3.1.1
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
is there anything i can do or is my phone screwed at this point? i see a lot of threads that would answer parts of my issue but nothing that covers this as a whole. id rather ask for help now while there may be some hope.
nickhawkjones said:
my computer wont recognize it while its in the bootloader or while its stuck trying to boot in twrp
Click to expand...
Click to collapse
So no response to fastboot commands, while in bootloader-fastboot mode?
Are you sure you installed the right drivers for your pc? If all else fails, you can do this.
This is how I fixed my phone when i was stuck at a black screen. You can also try a different usb cord or port. Check device manager and see if it recognizes it when its plugged in. hope this helps!
https://www.youtube.com/watch?v=BvfA5WrVDQM
can you boot into fastboot? if your phone can boot to fastboot mode..just flash stock recovery image..then flash rom via adb shell (better flash the stock rom). if it works you can reinstall the custom recovery image or something. dont forget to erase everything via stock recovery..
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon
Hi everyone!
Since yesterday i am having problems with my phone, first it briked after a normal update, thanks god i unlocked the fastboot before, i installed a custom OS but didn't liked it, so i wiped both partition (and i think i ****ed up there)
So now i can still enter fastboot mode, but everytime i try to send fastboot boot judypn_TWRP_bootable-metadata.img (that yesterday worked) not it's not working anymore, it just boots normally and remain stuck in bootloop
On my microsd i put the img of twrp with metadata HavocOS and twrp zip too, yesterday i could install and enter in recovery mode them without any problem, today the boot img is sent but the phone "ignores" it.
PS. I can enter fastboot mode without problem, download mode isn't working
Thanks to anyone who can help!
Sporalinux said:
Hi everyone!
Since yesterday i am having problems with my phone, first it briked after a normal update, thanks god i unlocked the fastboot before, i installed a custom OS but didn't liked it, so i wiped both partition (and i think i ****ed up there)
So now i can still enter fastboot mode, but everytime i try to send fastboot boot judypn_TWRP_bootable-metadata.img (that yesterday worked) not it's not working anymore, it just boots normally and remain stuck in bootloop
On my microsd i put the img of twrp with metadata HavocOS and twrp zip too, yesterday i could install and enter in recovery mode them without any problem, today the boot img is sent but the phone "ignores" it.
PS. I can enter fastboot mode without problem, download mode isn't working
Thanks to anyone who can help!
Click to expand...
Click to collapse
So first, the forum you posted this in is called 'Roms, Kernels, recoveries and other development'... so which 'development' is this? a Rom? a Kernel? a Recovery?
None of the above right? So what you have is a 'question', and it should be in 'Questions and Answers'. Sorry if that offends, but if someone wants to find something in these forums, then posts need to be in the appropriate places...
First thing I'd do would be to get the phone's download mode (lgup) working again and flash a stock kdz. That way you can basically 'start over' (and hopefully have better results with your endeavors).
try this initially: Follow this link and read the 'notes' file. Hopefully that will give you lgup, if it doesn't then it's a more involved process to use edl and flash, basically, a whole image.
cheers