Related
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
08G8V8 said:
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
Click to expand...
Click to collapse
First, Status code 3 is normal - that indicates an unlocked bootloader.
You should be able to use the 4.4.4 FXZ to flash back to 100% stock. Afterwards, you can flash TWRP, and re-root. Use the latest TWRP from here: http://techerrata.com/browse/twrp2/ghost
The important thing about TWRP is that immediately after flashing it, you have to "fastboot reboot-bootloader" and immediately boot into recovery - otherwise it doesn't 'stick'. We don't know why, but as long as you do it that way, you will be fine.
Here is the link for the 4.4.4 FXZ: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you follow the instructions, you will be on stock, rooted 4.4.4 in less than 20 minutes.
Good Luck, and let me know if you need additional assistance :good:
Also, please remember to post your questions to Q&A - not General. Don't worry as I have already requested that the Mods move it to the appropriate sub-forum.
EDIT: The problem I see with "rootjunky"s video is that first, he advises that "Status code 1" is required to flash recovery -- this is incorrect. Status code 3 works fine for custom recovery.
Additionally, he did not "fastboot reboot-bootloader" before booting into recovery. This is necessary. I'm not sure why he left that step out....likely he already had custom recovery flashed when he made the video.
Thanks for the quick response. Sorry about posting in the wrong section. I should have known better.....
I will look at this, but probably won't do it until after work tomorrow. I will post back tomorrow, hopefully with success.
Thanks!
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
08G8V8 said:
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
Click to expand...
Click to collapse
Either will work fine. If you don't care about keeping your data, you can use RSD Lite (will wipe everything). If you use one of the tools in the thread I linked you to, make absolutely sure you follow the instructions -- you can't have any spaces in any folder-names. If you use RSD Lite, you just select the zip file and flash (no worries about directory structure).
Ok, I just assumed those were the methods to flash it. I will look into the RSD Lite method, as if don't mind wiping the data.
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
08G8V8 said:
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
Click to expand...
Click to collapse
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
samwathegreat said:
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
Click to expand...
Click to collapse
Sorry, the "adb reboot bootloader" sends me into the bootloop.
I hadn't tried the "fastboot reboot bootloader" or "fastboot reboot-bootloader". Now when I try that, with USB debugging checked I just get "<waiting for device>" It does nothing.
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Travisdroidx2 said:
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
Click to expand...
Click to collapse
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
08G8V8 said:
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
Click to expand...
Click to collapse
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Once you are in the boot loader screen does "fastboot devices" recognize your device?
samwathegreat said:
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Click to expand...
Click to collapse
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
samwathegreat said:
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Click to expand...
Click to collapse
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Travisdroidx2 said:
Once you are in the boot loader screen does "fastboot devices" recognize your device?
Click to expand...
Click to collapse
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
08G8V8 said:
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Click to expand...
Click to collapse
OK, glad you didn't flash to bootloader. That is tricky to fix...but I've dealt with people who have done it before.
Try another PC...or re-install the drivers. Also, DO NOT use a usb 3.0 port, always use 2.0.
Bootloader = AP fastboot mode. They are one and the same. Try to get it recognized with "fastboot devices", on any PC. If you can get to that point, you can flash back to stock and recover everything. The FXZ can actually FIX a corrupted or damaged filesystem. It replaces all the relevant partitions.
Remember you do NOT use adb or usb debugging. They have nothing to do with fastboot.
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
08G8V8 said:
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
Click to expand...
Click to collapse
YES!!!!
It seems you were confusing adb and fastboot. As long as "fastboot devices" recognizes your device, SO WILL RSD LITE!!!
Now follow my initial instrucitons, and you will be up and running in no time...
Thanks guys! I am going to do this tomorrow, but I feel pretty good that it is going to work.
Yes, I got VERY confused, and definitely need to go study up some more. I thought I had it, but obviously not.
Will report back tomorrow.
Happy to help
Absolutely get the Dev Edition for the same price. While Safestrap is out for other Galaxy devices with locked bootloaders (not sure if the S5 got SS yet) it allows customs Roms....but not kernel changes. With a Dev edition, there may be less development, but I'm sure there will still be some development out there.
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
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
TAGTRAUM said:
Hello guys! I I stucked in very interesting case.....Been flashing Resurrection Remix with fullwipe from Chroma, all ok, on first boot i do a silly thing while boot become too long i goind to reboot phone and then see that phone is encrypting......it reboots and here i have "Encryption unsuccessful" and button factory reset which do nothing. I know about reboot to bootloader, but NRT can't reboot my device in bootloader, and my Vol- button broken. What i gonna do, please help, heard about hardbrick method or something else for reboot to bootloader. Thanks for advance :cyclops:
Click to expand...
Click to collapse
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Circaflex said:
Does NRT give you an error when it tries to reboot into bootloader? Another reason to stay away from toolkits, but that is another debate for another time. Have you tried manually running the ADB commands to boot into fastboot? Do you have access to a computer with Android SDK installed?
Click to expand...
Click to collapse
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
TAGTRAUM said:
Yes, tried manually commands before use toolkit, no luck "device not found", drivers are ok, device visible in Device Manager as MTP, before this "unsuccessful" flash works like a charm. And then is no way out, when device is on it show encryption message and still no luck with ADB. Maybe some script that override ADB and took me into recovery/bootloader??
Click to expand...
Click to collapse
Nope.. If adb doesn't work and volume buttons are broken, you're stuck. Get the buttons repaired.
rootSU said:
Not sure what you want to do in bootloader. Recovery makes more sense to me. Flash a non-force encrypt kernel, format userdata and you're away.
From a command prompt / termina (whilst booting and connected with USB cable)...
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Click to expand...
Click to collapse
No luck with running this commands in boot process
TAGTRAUM said:
No luck with running this commands in boot process
Click to expand...
Click to collapse
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
Adb should work from part way through the boot process and any mode. in custom recovery.
gee2012 said:
Adb only works if the device is booted up or in sideload mode in recovery, fastboot works in fastboot/bootloader mode. Is/was the device recognised as a adb device when you typed `adb devices`in cmd?
Click to expand...
Click to collapse
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
TAGTRAUM said:
No, it's not appear in "adb devices" on any process of boot, but Windows recognise in Device Manages as "MTP USB Device" even when phone off and connected via USB
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Tech said:
Try this
Click to expand...
Click to collapse
Will try, but decide to repair my Vol- button myself, i have no mind what can be broken in this part, watching video of N6 dissassembly, its pretty simple part indeed Walking w/o Vol- for a month, and this situation is frustrating me and other situations can happen, in certain cases i still need Vol- :cyclops:
Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!
Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.
blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!
Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.
drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.
I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery
watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4
Hi Community,
I was rooted and got some nasty popup virus, then I factory reseted through settings. Everything was fine, then I entered in my software "superuser" and he said he would reinstall something, then booom bootloop!
I tried factory resetting through fastboot didnt work;
I tried flashing stockrom, latest rom, downgrade rom and the error is the same:
Verifying update package...
E: footer is wrong
Update package verification took 0.2 s (result 1).
E: Signature verification failed
E: error: 21
Installation aborted
ADB doesnt recognize my device!!! guess because after rebooting I never re authorized usb debugging mode or oem..
What Can I do now? any help appreciated
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Everything is described there.
If your Device is on Android One, don't take the Rom from the thread but from this link: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
irongas said:
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
Click to expand...
Click to collapse
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
screwyou00 said:
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
Click to expand...
Click to collapse
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
irongas said:
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
Click to expand...
Click to collapse
Did you install Motorola fastboot drivers?
The menu what you talk about is Recovery. Look if there's an option to boot to bootloader. If not go down to reboot the device and keep VOL-Down pressed so it reboots to bootloader. There you can just use fastboot commands.
sleeptab said:
Did you install Motorola fastboot drivers?
I did, I used to workaround with adb and sending commands, but the command prompt would recognize my device, now, even in bootloader when I plug it in bootloader says: usb plugged in, but the pc wont see my device... im almost crying here lol
Click to expand...
Click to collapse
RESOLVED!
hEY i JUST looked in device manager and there was a driver issue, then I reinstalled the driver from the pc adb phone, and it came back to liiiife!!! I just followed the second sequence and boom its working
Thank you a looot guys!!! sorry being such a noob! =)
Have a nice one!!