i downloaded twrp 2.3.3.0 from goo apk it automatically installed. i booted into recovery wiped everything , but sd ofcourse, so to flash back to magiorom, and bootlooped every since. Cant reboot recovery, it flashes twrp then back into bootloop. adb does not recognize my device??? idk why never been a problem b4. any help would be appreciated. im s-off just ruud to 3.18 a couple days ago and touchscreen downgraded
Can you get into bootloader? How did you flash TWRP? Though fastboot or ROM Manager?
Sent from my Evita
If you can get into bootloader maybe you can fastboot flash the recovery again then try to access it
Sent from my HTC One X using Xparent Green Tapatalk 2
yes i can acess bootloader. i tried flashing a different recovery .img with success but now adb doesnt see my device. i initially installed through goo manager it was automatic i didnt know it would
traesnaidensdad said:
yes i can acess bootloader. i tried flashing a different recovery .img with success but now adb doesnt see my device. i initially installed through goo manager it was automatic i didnt know it would
Click to expand...
Click to collapse
Use twrp 2.3.3.1 all later versions have issues
Sent from my HTC One XL using xda premium
Ahh yeah goo manager what was I meant. So you've manually flashed a recovery now, does it boot into the recovery ok?
Sent from my Evita
So you can get into twrp now that's a start lol do you have a Rom to flash
Sent from my HTC One X using Xparent Green Tapatalk 2
I have fastboot flashed twrp 2.2.2.0, but it still won't go fully into recovery. The twrp screen comes on then goes black and back to bootloop
Sent from my Nexus 7 using XDA Premium HD app
traesnaidensdad said:
I have fastboot flashed twrp 2.2.2.0, but it still won't go fully into recovery. The twrp screen comes on then goes black and back to bootloop
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Fastboot erase cache....
Sent from my HTC One XL using xda premium
OK....trying now
Sent from my Nexus 7 using XDA Premium HD app
I was able to fast boot erase cache' but adb again can't see my device. Trying recovery manually
Sent from my Nexus 7 using XDA Premium HD app
I don't understand what you mean. Why are you trying to use adb?
Sent from my Evita
Woot! That worked! I'm still learning all about adb. I don't know ALL COMMANDS and why it would not recognize my device after each command that worked. Many thanks guys..many thanks
Sent from my Nexus 7 using XDA Premium HD app
timmaaa said:
I don't understand what you mean. Why are you trying to use adb?
Sent from my Evita
Click to expand...
Click to collapse
Because I could not access anything manually
Sent from my Nexus 7 using XDA Premium HD app
Fastboot was working because you were in bootloader. Adb requires you to be booted into a ROM with usb debugging turned on.
Sent from my Evita
Related
I was about to flash flash the new cleanrom and recovery tells me error mounting sdcard and so i tried formmating but get another error so is there anyway to flash back to stock because the ruu require the phone to be on
What have you tried? Have you tried holding the power button to reset the phone?
Sent from my HTC One X using xda app-developers app
Which recovery did you flash?
Depending on what you've already tried, we can get you back just need to know where you are.
I pushed cwm and twrp using flashboot and everytime i cant mount the sdcard is there any way to flash to stock using flashboot or bootloader
moneyover said:
I pushed cwm and twrp using flashboot and everytime i cant mount the sdcard is there any way to flash to stock using flashboot or bootloader
Click to expand...
Click to collapse
yes. relock your bootloader
from bootloader type fastboot oem lock
then you can flash the 1.85 RUU
just run the file from windows.
After that you can unlock with the same unlock token you got when you unlocked in the first place
then you can install recovery again
but the ruu requires the phone to be on and usb debugging on
moneyover said:
but the ruu requires the phone to be on and usb debugging on
Click to expand...
Click to collapse
No. It doesn't. Run it from fastboot
Sent from my HTC One X using Tapatalk 2
says its not plugged in and could you please post a link to the correct ruu
Install drivers.
Sent from my HTC One X using Tapatalk 2
please post a link
Sorry. I would have to use Google for you. I don't do that. Do a little leg work man.
Sent from my HTC One X using Tapatalk 2
moneyover said:
says its not plugged in and could you please post a link to the correct ruu
Click to expand...
Click to collapse
http://www.htcdev.com/bootloader/unlock-instructions
Sent from my HTC One X using xda premium
http://lmgtfy.com/?q=at&t+one+x+drivers
Sent from my HTC One X using xda app-developers app
Thanks guys i got it workin
Sent from my SAMSUNG-SGH-I777 using XDA
You can find a link to the drivers in the first post in http://forum.xda-developers.com/showthread.php?t=1709424
Once you have them installed you'll have to reboot in to fastboot and install the official 1.85 RUU.
Also so you know I had a similar experience when I was on cleanrom 2.6 and tried to format and go to 3.0. I had to relock the bootloader, RUU to stock and install a different rom cause 3.0 would just never install for me for whatever reason, it would always bootloop back in to recovery. However I had backed up my NANDROID to my PC so I copied it back over to my SD card after I was on stock then restored it then did an in-place upgrade to 3.1 which worked. I was able to install cleanrom 4 after a wipe without issue.
Ok, after using FlashRomGUI and flashing the latest nightly my phone will not load into TWRP recovery. I try to go to recovery and it takes me to the bootloader. I try to go into recovery from bootloader and and takes me back to fastboot. How do I get to TWRP recovery again?
Reboot boot loader. Or reboot and hold volume down
Sent from my One X using xda app-developers app
absolutelygrim said:
Reboot boot loader. Or reboot and hold volume down
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I've done that and its like TWRP is not there.
So when you try to boot into recovery what happens
Sent from my One X using xda app-developers app
I've tried everything and I can't get back to TWRP. Phone still works. It restarts and loads CM10, everything is functioning properly. When using this app should i do recovery or kernel when running flashromgui?
Kernel
Go flash twrp again from fast boot
Sent from my One X using xda app-developers app
absolutelygrim said:
Kernel
Go flash twrp again from fast boot
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Success! Once again you have come to the rescue. Thank you for having the patience to deal with my incompetence.:highfive:
you probably somehow flashed kernel as recovery.
I have a HTC Inspire 4G, I got the bootloader unlocked and had it rooted. I had CWM Recovery on it that was like version 5.8 the one before that. I tried flashing a jellybean firmware, the phone never went by past the HTC white screen. I tried updating the recovery and it still didn't work. Right now my phone can only boot into hboot and that's still unlocked, but fastboot commands won't work, I can only flash new recoveries, but no ROMs actually get flashed. I tried using the PDimg thing for HBOOT to get back into full stock, I followed all the rules about going to ext3 (can't remember off the top of my head). It won't see the image, I've tried everything out there. ADB won't see the device unless in recovery mode, fastboot won't work, except to flash new recoveries.
Any possible ideas?
After flashing a ROM you need to fastboot flash thr ROM zip's boot.img.
Even if it doesn't boot into the ROM? It should work?
Sent from my Nexus 4 using xda app-developers app
No. I missed that. Can you fastboot flash a recovery? If not, you can try running a RUU.
Yeah I am able to flash a recovery via fast boot, but to actually do any other commands via fast boot it won't recognize anything. HBOOT won't see any .zips, tried everything.
Sent from my Nexus 4 using xda app-developers app
I don't understand. Where are these zips? Computer or phone?
Phone. The .zips are like the pd98img things. Those don't read on my phone from HBOOT
Sent from my Nexus 4 using xda app-developers app
Wait, if you have a working recovery, just flash a ROM (not PD98IMG) zip from the recovery (not fastboot). Download a custom ROM, full wipe in recovery, and flash in recovery.
Tried that. It seriously just sits there till the battery dies trying to turn on, doesn't pass the HTC white screen.
Sent from my Nexus 4 using xda app-developers app
And then extract the boot.img from the ROM zip and fastboot flash boot boot.img.
I love you haha
Sent from my Nexus 4 using xda app-developers app
OK so the other day I was using my phone and it had cm10.2 on it. The phone started to act up so I went to recovery (cwm) and wiped everything but the sdcard. When I went to flash a new ROM the recovery said that it couldn't mount the sdcard so I instantly think OK let me try to flash twrp and this is where the issue come in...... I'm using Ubuntu and when I go into fastboot mode and plug the phone up Ubuntu/adb won't see the phone. I ran "adb devices" and it shows that the phone isn't connected even though in looking right at it and its plugged in.... Any ideas? Because I'm fresh out of them XD
Sent from my Nexus 7 using Tapatalk
If you're in fastboot in bootloader use fastboot devices
Adb won't work in bootloader
Sent from my One Xl using xda app-developers app
exad said:
If you're in fastboot in bootloader use fastboot devices
Adb won't work in bootloader
Sent from my One Xl using xda app-developers app
Click to expand...
Click to collapse
I know that, I said both because both of them aren't working. I did it on windows no problem but I still would like to know why it wouldn't pick up. I had the phone in fast boot and put in fastboot flash recovery (file location here) and got stuck on waiting for device. Did it on my moms windows computer no problem though
Sent from my HTC One XL using Tapatalk
Most likely something, who knows what, was interfering with the driver
Sent from my One Xl using xda app-developers app
As of now fastboot isn't working on Windows 8.1 due to driver issues. This might be the explanation for your problem.
Lol he was using Ubuntu?.....
Sent from my One Xl using xda app-developers app
fimbulvetr_nears said:
As of now fastboot isn't working on Windows 8.1 due to driver issues. This might be the explanation for your problem.
Click to expand...
Click to collapse
... I'm not using Windows man, look at the post again lol
Sent from my HTC One XL using Tapatalk
OK so my nexus 5 is rooted and I installed twarp and nothing works on it. So I think downloaded ROM manager and it won't download! So now both Recovery's are not working. What did I do wrong??? Please help. I am SOO confused!
Sent from my Nexus 5 using XDA Premium HD app
enzosly said:
OK so my nexus 5 is rooted and I installed twarp and nothing works on it. So I think downloaded ROM manager and it won't download! So now both Recovery's are not working. What did I do wrong??? Please help. I am SOO confused!
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
First, restore back to stock, using any toolkit in development section
Then use that toolkit to install the recovery + superSU
Then download & install rom manager
Are you sure you do it right?
go to fastboot mode, then type
Code:
fastboot erase recovery
fastboot flash recovery TWRP.img
Besides, the latest twrp.img is 12.9 MB.
enzosly said:
OK so my nexus 5 is rooted and I installed twarp and nothing works on it. So I think downloaded ROM manager and it won't download! So now both Recovery's are not working. What did I do wrong??? Please help. I am SOO confused!
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
Were you careless with your fastboot commands? Did you flash a kernel/ something else to your recovery partition while you were flashing multiple files at once? I ask becasue I was updating my kernel this morning and noobed up. I flashed my recovery with my kernel.:victory: