Related
Alright so my issue is I flashed an ics rom on my evo LTE but accidentally with the wrong firmware. When the update was just about done, the screen went black. No charge light when plugged into a charger and the device will not power on, or do anything(tried button combinations). However when I plug it into my computer,device manager sees my phone as “My HTC”. So it seems to have a connection but it doesn’t do anything to the phone. Fix possibly?
Sorry for asking such a basic question guys. New to the forums but definitely not new to flashing roms. This problem just confuses me to death.
Can you supply as much info as possible.
QUOTE=bigdaddy619;45718286]Can you supply as much info as possible.[/QUOTE]
Yes I can my friend. Of course, I got S-OFF with moonshine. Never had a problem there. Rooted also with moonshine as well. Flashed a lot of different jelly bean roms (CM, Meanbean) to see which one best suited me. Well after awhile I decided to give one of the ics roms a shot but the firmware version on my evo was for jelly bean only, not ice cream sandwich. Just as the flash of the ics rom was about finished, the screen went black. (Battery was above 50%). I tried every button combination, but nothing worked. Tried connecting it to a charger and the orange charge light wouldn't even come on. I even left it on the charger overnight, but no dice. So the phone is totally unresponsive to everything. One thing I did notice however is that when I tried connecting the phone to the computer, my computer makes the connection noise when it finds a
Usb device. Checked my device manager on windows and my phone shows up as "My HTC". So it seems as my computer has some type of connection to the phone. With that being said, would there be some way to use some unbricking software or any other way to unbrick my phone? (From what I see, I think the bootloader may be corrupted)
Since you can hear USB connection, I wonder if running fastboot devices from CMD would yield any results. Though I suspect you'd probably have to be booted to fastboot USB to see.
Sent from my EVO using XDA Premium 4 mobile app
scottspa74 said:
Since you can hear USB connection, I wonder if running fastboot devices from CMD would yield any results. Though I suspect you'd probably have to be booted to fastboot USB to see.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would you know of what commands may work for my device? Cmd is new to me, or well at least when it comes to sending commands to phones lol.
Click the link in my sig. There is a guide for setting up ADB as well as commands in it.
FinZ28 said:
Click the link in my sig. There is a guide for setting up ADB as well as commands in it.
Click to expand...
Click to collapse
Thank you much sir. Here's what I found out. When I type the command "adb devices", nothing shows up. When I type in "fastboot devices" here is what it says:C:\Users\lisa\Desktop>fastboot devices
C:\Users\lisa\Desktop>fastboot devices
t♥☻ fastboot
guessing that's not a serial number, as it should be, but it recognizes my device as a fastboot device. Is there any hope of fixing this paperweight?
ADB commands only work when the phone is booted to the ROM, whereas Fastboot commands only work in the bootloader when connected via Fastboot USB mode.
Can you get to the bootloader at all?
FinZ28 said:
ADB commands only work when the phone is booted to the ROM, whereas Fastboot commands only work in the bootloader when connected via Fastboot USB mode.
Can you get to the bootloader at all?
Click to expand...
Click to collapse
The only way I can get to the bootloader is by using the command prompt. Otherwise, my phone remains inoperable.
What happens when you select the recovery option in the bootloader?
Meaning that fastboot shows my device is connected but I cant access it on my phone.
rwhittaker13 said:
Meaning that fastboot shows my device is connected but I cant access it on my phone.
Click to expand...
Click to collapse
Ah.
HTC bricked
I have the same problem with my lte. I wanted to boot into recovery mode and that was the end of my phone. I can't turn it back on, but when i connect it to my computer it makes the connection sound and thats it, my phone is still dark.
stasikbest said:
I have the same problem with my lte. I wanted to boot into recovery mode and that was the end of my phone. I can't turn it back on, but when i connect it to my computer it makes the connection sound and thats it, my phone is still dark.
Click to expand...
Click to collapse
What did you do prior to booting into recovery? Also, when you plug your phone into your computer, what does your device show up as?
Sent from my HTC EVO 4G LTE
Bricked Phone Stuck in Fastboot
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
juanrocklin said:
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
Click to expand...
Click to collapse
Use Fastboot to fastboot flash a recovery to your phone
Sent from my SPH-L710 using Tapatalk 2
juanrocklin said:
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
Click to expand...
Click to collapse
That's not a brick. Do as instructed above and install TWRP via fastboot.
Sent from my HTC EVO 4G LTE
Thanks
FinZ28 said:
That's not a brick. Do as instructed above and install TWRP via fastboot.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Bammm! Worked like a charm. Back in business. Thanks much!
Hello Guys,
Just registered her at XDA and I hope I have not posted this thread in the wrong place. I will get right in to it without having to type the extra BS.
I have my TF201 which I have modded many times over to install a new ROM and firmware. About a year ago I had just flashed TEAMWIN recovery and got myself the absolutely SICK AndroWok 2.31 ROM. just a couple a months ago I wanted to upgrade my Android version to the latest because I was running 4.2.1. So I downloaded the upgraded Bootlader ZIP for the TF201 and thought while I'm at it I will update my recovery to TWRP 2.6.3.0... Big mistake... When I first go into recovery, it kept asking for a password... tried many times over and disabled my main OS password as I thought in some retarded way it was connected.... So for a little while I can easily reboot to AndroWok from the recovery and it would boot up fine... up until I hit the 5th attempt... From there on in, it keeps booting into recovery.... without a sign of change.... I TRIED everything.... NVFLASH, adb and fastboot the crap out recovery so I can flash the previous edition... it wont work... first off the files transfer way too quick and through all the transfer methods you can think of, I the blue fill up bar would never show... so I knew the flashing protocol was not complete although you would get the ok in command prompt. I even tried tried to flash the stock firmware thats about 112MB... it finished that in 10 seconds which is not possible... basicaly.. im stuck loopin into this retarded TWRP2.6.30... non of my flash or transfer methods work.. i cleared cache, i rebuilt the partition all of that.. im just not getting anything... and one more thing... when i would fastboot something out of command prompt, the selectable option on the tablet... where you usualy see the android logo, clear cache and rck.. (fastboot)... it would get stuck... as soon I flash wut ever file for recovery, bootloader, etc.... please help... i know i can get around this....
DeltaAden said:
Hello Guys,
Just registered her at XDA and I hope I have not posted this thread in the wrong place. I will get right in to it without having to type the extra BS.
I have my TF201 which I have modded many times over to install a new ROM and firmware. About a year ago I had just flashed TEAMWIN recovery and got myself the absolutely SICK AndroWok 2.31 ROM. just a couple a months ago I wanted to upgrade my Android version to the latest because I was running 4.2.1. So I downloaded the upgraded Bootlader ZIP for the TF201 and thought while I'm at it I will update my recovery to TWRP 2.6.3.0... Big mistake... When I first go into recovery, it kept asking for a password... tried many times over and disabled my main OS password as I thought in some retarded way it was connected.... So for a little while I can easily reboot to AndroWok from the recovery and it would boot up fine... up until I hit the 5th attempt... From there on in, it keeps booting into recovery.... without a sign of change.... I TRIED everything.... NVFLASH, adb and fastboot the crap out recovery so I can flash the previous edition... it wont work... first off the files transfer way too quick and through all the transfer methods you can think of, I the blue fill up bar would never show... so I knew the flashing protocol was not complete although you would get the ok in command prompt. I even tried tried to flash the stock firmware thats about 112MB... it finished that in 10 seconds which is not possible... basicaly.. im stuck loopin into this retarded TWRP2.6.30... non of my flash or transfer methods work.. i cleared cache, i rebuilt the partition all of that.. im just not getting anything... and one more thing... when i would fastboot something out of command prompt, the selectable option on the tablet... where you usualy see the android logo, clear cache and rck.. (fastboot)... it would get stuck... as soon I flash wut ever file for recovery, bootloader, etc.... please help... i know i can get around this....
Click to expand...
Click to collapse
So what I understand is, that you can at least boot into fastboot mode, is that so?
Have you tried.the erase command?
Code:
fastboot -i 0x0b05 erase recovery
Advice: One should never, repeat: never!, flash TWRP 2.6.3.0. Too many bricks are reportet. I had to buy new logic board for my tf201 because of this.
Second question: You talked of 'nvflash', you tried. So you have your nvflash blobs? If yes - you are safe!
Post the version of your bootloader.
das chaos said:
So what I understand is, that you can at least boot into fastboot mode, is that so?
Have you tried.the erase command?
Code:
fastboot -i 0x0b05 erase recovery
Advice: One should never, repeat: never!, flash TWRP 2.6.3.0. Too many bricks are reportet. I had to buy new logic board for my tf201 because of this.
Second question: You talked of 'nvflash', you tried. So you have your nvflash blobs? If yes - you are safe!
Post the version of your bootloader.
Click to expand...
Click to collapse
Thanks for the reply... Yes I guess it was a terrible mistake to get 2.6.3.0... In terms of the blobs, I only have the firmware from Asus stock.. I havent extracted or backed anything up previously... and about the command you gave me; yes, I also tried that and no luck. Is there any other way? Something is telling me that partition is off... because basically im unable to flash and write anything.. all flash attempts are failed so nothing is getting written...
DeltaAden said:
Thanks for the reply... Yes I guess it was a terrible mistake to get 2.6.3.0... In terms of the blobs, I only have the firmware from Asus stock.. I havent extracted or backed anything up previously... and about the command you gave me; yes, I also tried that and no luck. Is there any other way? Something is telling me that partition is off... because basically im unable to flash and write anything.. all flash attempts are failed so nothing is getting written...
Click to expand...
Click to collapse
Also... i forgot to mention.... when i erase the recovery and try to flash the new one... command prompt would hang up with <waiting for device> ... that would stay there for ever.
DeltaAden said:
Also... i forgot to mention.... when i erase the recovery and try to flash the new one... command prompt would hang up with <waiting for device> ... that would stay there for ever.
Click to expand...
Click to collapse
Looks bad!
1. Have you got the right USB drivers for Windows (Naked Drivers)?
2. Have you tried another USB port?
3. Have you tried another USB cable?
4. How many icons do you find on BL menue? Do you really know, how to enter fastboot mode (NOI)?
If nothing helps, buy another logic board. It's cheap on ebay.
das chaos said:
Looks bad!
1. Have you got the right USB drivers for Windows (Naked Drivers)?
2. Have you tried another USB port?
3. Have you tried another USB cable?
4. How many icons do you find on BL menue? Do you really know, how to enter fastboot mode (NOI)?
If nothing helps, buy another logic board. It's cheap on ebay.
Click to expand...
Click to collapse
Yes I have the naked drivers... and I beleive it is fuctional because theres clearly a response from my tablet... i usualy start by entering the shel first which sometimes takes a couple of attempts. when its successful, i know a session is now active with my table to i simply exit again... then from there its easy because i know the tablet has a session with my pc so i "adb reboot bootloader" which automaticaly restarts the tablet into fastboot and icon hovering over RCK.... from there I run my commands and command prompts confirms it by the 'ok' displayed along with the time it took in seconds.... clearly theres something wrong there.... i should try it at another pc.... or maybe the issue is a bit more complex... the real question remains, why can i not flash another recovery besides the 2.6.3.0??. still any other suggestions.? i will try another pc and have a go
DeltaAden said:
Yes I have the naked drivers... and I beleive it is fuctional because theres clearly a response from my tablet... i usualy start by entering the shel first which sometimes takes a couple of attempts. when its successful, i know a session is now active with my table to i simply exit again... then from there its easy because i know the tablet has a session with my pc so i "adb reboot bootloader" which automaticaly restarts the tablet into fastboot and icon hovering over RCK.... from there I run my commands and command prompts confirms it by the 'ok' displayed along with the time it took in seconds.... clearly theres something wrong there.... i should try it at another pc.... or maybe the issue is a bit more complex... the real question remains, why can i not flash another recovery besides the 2.6.3.0??. still any other suggestions.? i will try another pc and have a go
Click to expand...
Click to collapse
On second thought:
Are you logged in as an admin in Windows or do you sudo before fasboot in Linux?
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
syedzakiabidi said:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
Click to expand...
Click to collapse
You can't access TWRP because you over-wrote it with the factory RUU firmware image, it isn't there anymore...
Download TWRP image from TWRP official site at https://dl.twrp.me/vigor/ or Flyhalf's build at http://forum.xda-developers.com/showthread.php?t=1902381
Either one is good... then start fastboot, connect usb and flash recovery with the command:
fastboot flash recovery <path/filename of TWRP IMG file>
give it a minute or so, reboot into Hboot and start TWRP.
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
youdoofus said:
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
Click to expand...
Click to collapse
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
acejavelin said:
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
Click to expand...
Click to collapse
fair point, and i do have ubuntu (of differing flavor dates) on 3 of my machines, so i might just do that. Thanks!! Ill also try the goofy htcsynch (which i forgot about, as im a Sammy guy now) Thanks again!!
After upgrading to CM 12.1 everything was just fine. Got my tablet to charger and left it there for a while. And then i saw that i was looping.
It's trying to enter recovery (TWRM) "or something like" and restarting.
I' sitting on forum for 3 days already. trying to get some information and did lot's of things. Nothing helps.
Can anyone help me with this somehow? I'm almost crying and losing it (not really, but that what i feel inside)
Please. Any help. I think I've read all forum about this thing.
Thank you.
Do you have the real TWRP (i.e. not Safestrap!) & an unlocked bootloader?
don't think so. or better say i'm not sure about it. how can i check?
Edit:
i can run adb and after command "adb devices" it shows serial number and status: recovery.
i can use the command adb reboot-bootloader which puts me in fastboot mode. but then i try adb devices and have nothing there.
also, any command like "fastboot...." gets me to "waiting for device" and nothing more.
I tried two different computers. all ports. all cables that i've found.
Edit 2:
also after command "adb shell" i ca see "~ # ←[6n" and i can put there only reboot command
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Cl4ncy said:
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Click to expand...
Click to collapse
Also verify you have a Kindle HDX ... not HD or generic Fire.
the fastboot command got me still only 1 message "waiting for device"
Tried to install drivers. While looping, in device manager, i can see "Fire devices: Android composite ADB Interface"
and "Portable devices: MTP USB Device"
If i enter fastboot mode, gets me to "Other devices: Unknown device" and i just cant figure out how to install the drivers. Tried to download some stuff. plugged, unplugged.
Edit:
After some work done with drivers, i input adb kill-server and adb devices and get "Serial Number Unauthorized"
So maybe i should change word "work" to "messing" with driver
what do i do from here... is there any live chat for it maybe? or i can call someone?
Well, do you have the real TWRP or Safestrap? Can you enter recovery?
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Still haven't answered Safestrap or native TWRP query (you should know). Do this:
- long press power until device shuts off
- restart device with power button (only)
- detail the 1st, 2nd and 3rd screens you see
If you do not have native TWRP (with unlocked bootloader) you likely borked your device with the installation of CM 12.1. Generally not repairable.
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Cl4ncy said:
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Click to expand...
Click to collapse
To check if your bootloader is unlocked (assumes you previously unlocked and still have the prerequisite software installed on host):
- power down device
- press vol-down + power; release both keys when "[fastboot]" prompt appears
- tether your device
- open a command prompt (assuming Windows)
- issue command: fastboot -i 0x1949 oem idme ?
- you will only get a response if bootloader is unlocked
If the (Windows) host displays "<waiting for device>":
- press <ctrl>-c to break wait
- start device manager (different window)
- located device with explanation mark (likely under "portable devices")
- right click -> update driver software -> browse my computer... -> Let me pick...
- select driver from list (ideally one that contains the words 'fastboot'); might have to try a few
- reissue above command
Bit of a PiTA ... might be easier to simply try the one click unlock tool as there is no additional risk to your device. It will either work or not.
I guess i'll check it only next week. Leaving all this things for the weekend.
I'll keep you updated guys.
Anyway, i really appreciate your help! Thank you so much for helping
same problem
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
stephio said:
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
Click to expand...
Click to collapse
I assume you have an unlocked bootloader and were running 'native' twrp (not Safestrap) when the problem occured. Unfortunately, there is no known 'quick fix' recovery from this failure scenario (boot looping on teamwin spash screen) as you have tried to reinstall twrp without success. Someone very talented with android might be able to unravel the problem. Best guess (and it is only a guess) is the recovery partition became damaged to such an extent it the contents can not be replaced without performing a low level format/reset of your device.
Some curiosities:
- Android 5.0.1 and CM11? (impossible combination)
- TWRP freedom? (not supported on HDX)
Are your certain your device is a HDX and not some other model?
same problem
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
stephio said:
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
Click to expand...
Click to collapse
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
same problem
EncryptedCurse said:
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
Click to expand...
Click to collapse
I searched the web and I have definitely amazon kindle fire HD 8.9 because even his appearance differs from the HDX 8.9.
no I do not really think the problem comes from the data flash HD 8.9 (wikicyanogenmod) because I flashed the data after doing a factory reset without actually knowing that this would pose a problem with amazon tablets.
the tablet was working well but I was unable to connect to the wifi. I thought it would be nice to change rom and install a suitable and stable rom for my tablet, but my operation I was surprised because I had never heard of this kind of problems caused by an factory reset
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.