Related
I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
chamo311 said:
I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
Click to expand...
Click to collapse
did you install the correct version for the htc one sprint(wls)(spr)
Aldo101t said:
did you install the correct version for the htc one sprint(wls)(spr)
Click to expand...
Click to collapse
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
chamo311 said:
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
Click to expand...
Click to collapse
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Kraizk said:
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Click to expand...
Click to collapse
That sucks! So should I do try adb fastboot or go back to the previous version (2.5)?
What sucks is that without 2.6 working properly, I won't be able to flash any ROM with the new android version (4.2)
Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Did the ADB and still the same problem. Should I go back to previous version of TWRP?
chamo311 said:
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Click to expand...
Click to collapse
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Aldo101t said:
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Click to expand...
Click to collapse
It is broken, several users are reporting it in the original TWRP post as well
Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
Now that's some "good news" LOL! because I thought I screwed my phone and I wasn't going to be happy about it. I went back to v2.5 and everything works great!!
Thank you so much for all your help, guys!
Bless!!:good:
Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
that could be, thanks for the heads up
STUCK in TWRP Recovery
Aldo101t said:
that could be, thanks for the heads up
Click to expand...
Click to collapse
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
just revert back to 2.5.0.0 and you are good to go
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you just recently update your firmware to the new base? The reason I ask is because after I did I used the the firmware with the bootloader and recovery included. I had reflashed TWRP 2.5. Well I noticed that the method of holding down volume key and and power button would not work for me at all whether I was in the os, bootloader or recovery. So I flashed the Rom I was on again and it fixed it. So I am wondering this is what is happening to you. Maybe just let the phone lose charge then plug it in reboot to the os then into bootloader and flash the 2.5 TWRP recovery. Only thing I can think of your not bricked
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you try holding the phone under a bright light then holding power and vol down to reboot. This works sometimes
Sent from my jacked HTC One!!
Aldo101t said:
just revert back to 2.5.0.0 and you are good to go
Click to expand...
Click to collapse
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
mzel said:
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
Click to expand...
Click to collapse
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Aldo101t said:
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Click to expand...
Click to collapse
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
mzel said:
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
Click to expand...
Click to collapse
that error is nothing don't worry about it, if you install a custom rom(make sure it's for sprint)that will go
Hello XDA I'm new to these forums but i'm hoping you can help me out.
So basically I was following a youtube video I was linked to by a guide on here on how to root my One. and everything was going smoothly and then i got to the stage where i was to boot into recovery mode so i could load into twrp. But what happens on my phone now is the loading screen for recovery mode where it says for developers only ect. will just hang there for a while then the phone will shut off and boot back into regular mode. could use some help. I wouldn't mind resetting and starting fresh if that's what's needed im just not sure how to. thank you guys!
Kdenery said:
Hello XDA I'm new to these forums but i'm hoping you can help me out.
So basically I was following a youtube video I was linked to by a guide on here on how to root my One. and everything was going smoothly and then i got to the stage where i was to boot into recovery mode so i could load into twrp. But what happens on my phone now is the loading screen for recovery mode where it says for developers only ect. will just hang there for a while then the phone will shut off and boot back into regular mode. could use some help. I wouldn't mind resetting and starting fresh if that's what's needed im just not sure how to. thank you guys!
Click to expand...
Click to collapse
read this: http://forum.xda-developers.com/showthread.php?t=1435228
you will need to reflash recovery using fastboot/adb
Aldo101t said:
read this: http://forum.xda-developers.com/showthread.php?t=1435228
you will need to reflash recovery using fastboot/adb
Click to expand...
Click to collapse
first problem, how do i select charge only? and second when i try the first command code posted it just wouldn't work and when i tried it while the phone was slected on fastboot usb (just incase that would work) it said no device.
Ok i figured it out i did everything in that thread. the same thing is happening. it just says entering recovery then restarts in normal mode.
Kdenery said:
Ok i figured it out i did everything in that thread. the same thing is happening. it just says entering recovery then restarts in normal mode.
Click to expand...
Click to collapse
do you have sdk tools installed on your computer.
make sure usb debugging is on, apperently you do.
did you put the recovery image in the folder where fastboot is then run cmd(as administrator) and cd to that folder(example/:cd c:/Program Files/Android/android-sdk/platform-tools or where ever you have it)then adb reboot bootloader>enter----Then fastboot flash recovery(name of recovery image).img>enter--- then type fastboot reboot recovery
If you are unlocked already, watch this https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
Sent from my HTCONE using Tapatalk 4 Beta
Aldo101t said:
do you have sdk tools installed on your computer.
make sure usb debugging is on, apperently you do.
did you put the recovery image in the folder where fastboot is then run cmd(as administrator) and cd to that folder(example/:cd c:/Program Files/Android/android-sdk/platform-tools or where ever you have it)then adb reboot bootloader>enter----Then fastboot flash recovery(name of recovery image).img>enter--- then type fastboot reboot recovery
Click to expand...
Click to collapse
yes. the problem is that it just stalls out on the entering recovery screen. with the htc logo and motto in the middle.
Kdenery said:
yes. the problem is that it just stalls out on the entering recovery screen. with the htc logo and motto in the middle.
Click to expand...
Click to collapse
which recovery are you installing if its twrp v2.6.0.0 try 2.5.0.0 there was a bug in the 2.6 don't know if they fixed it yet.
Aldo101t said:
which recovery are you installing if its twrp v2.6.0.0 try 2.5.0.0 there was a bug in the 2.6 don't know if they fixed it yet.
Click to expand...
Click to collapse
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Kdenery said:
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Click to expand...
Click to collapse
no i wouldn't think you do, it just overwrites the other, you're sure your bootloader is unlocked, check in settings under development option to make sure debugging is on.man you got me stumped here.
Kdenery said:
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Click to expand...
Click to collapse
Are you typing "fastboot erase cache" without the quotes after you flash the recovery?
Aldo101t said:
no i wouldn't think you do, it just overwrites the other, you're sure your bootloader is unlocked, check in settings under development option to make sure debugging is on.man you got me stumped here.
Click to expand...
Click to collapse
I retried the whole process once more and made sure usb debugging was on and its just frozen again.
bigdaddy619 said:
Are you typing "fastboot erase cache" without the quotes after you flash the recovery?
Click to expand...
Click to collapse
Just tried and made sure to do this. same problem.
Perhaps i'm just being extremely retarded. I am unlocked but not rooted, i thought this was how to get rooted. but maybe im just far off.
Kdenery said:
Perhaps i'm just being extremely retarded. I am unlocked but not rooted, i thought this was how to get rooted. but maybe im just far off.
Click to expand...
Click to collapse
NO, you are NOT retarded, you install recovery, then su to get root, for all intent and purposes you're doing it all right, just can't figure out why it's not working, one more redundant question, you have fastboot under power settings disabled?? Just tryin to cover all the bases
you are installing the recovery for the m7wls(m7spr)?
Aldo101t said:
NO, you are NOT retarded, you install recovery, then su to get root, for all intent and purposes you're doing it all right, just can't figure out why it's not working, one more redundant question, you have fastboot under power settings disabled?? Just tryin to cover all the bases
you are installing the recovery for the m7wls(m7spr)?
Click to expand...
Click to collapse
fast boot is not checked. and i think/hope so, how do i check that?
Kdenery said:
fast boot is not checked. and i think/hope so, how do i check that?
Click to expand...
Click to collapse
in settings under power scroll to the bottom fastboot is there.
Sorry i guess i phrased that wrong. i'm sure fastboot is unchecked, i was asking about the second part of your post, about "you are installing the recovery for the m7wls(m7spr)?"
Kdenery said:
Sorry i guess i phrased that wrong. i'm sure fastboot is unchecked, i was asking about the second part of your post, about "you are installing the recovery for the m7wls(m7spr)?"
Click to expand...
Click to collapse
what exactly is the zip you're using,should be something like(fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls.img
I've tried
cwm-recovery-vivow
openrecovery-twrp-2.5.0.0-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.6.0.0-m7wls
openrecovery-twrp-2.6.0.1-m7
recovery-clockwork-6.0.3.2-m7spr
recovery-clockwork-touch-6.0.3.3-m7spr
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
shartwell said:
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
Click to expand...
Click to collapse
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
flashallthetime said:
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
shartwell said:
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
Click to expand...
Click to collapse
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
flashallthetime said:
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Follow what flashallthetime is suggesting.
btw, Rogers firmware is correct for your phone as there is no Fido specific firmware.
shartwell said:
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Click to expand...
Click to collapse
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
flashallthetime said:
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
Click to expand...
Click to collapse
Getting somewhere...
The command prompt can seemingly now interface with my device. It runs commands but clearing the cache didn't fix the problem. I've ran the command though so if there is a next step...
EDIT: Okay it's charing and I can interface with it via cmd. I can now use RTDlite with it as it's battery is charging. Should I flash the other Rogers now? I have my unlock code for the bootloader if that's what I've got to do first.
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Steve-x said:
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Click to expand...
Click to collapse
It's all fixed up. Thank you everyone who contributed to this! Time to enjoy my phone.
Last thing would be flashing twrp. Does someone have a link to the proper files?
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
flashallthetime said:
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
Click to expand...
Click to collapse
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
shartwell said:
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
Click to expand...
Click to collapse
Here's twrp http://forum.xda-developers.com/showthread.php?t=2458449
Flash with fastboot( fastboot flash recovery twrp 2.6.3.IMG)
Place the recovery image in platform tools folder. After it flashes make sure you go directly to recovery by pressing the volume up bottom to make it stick
Sent on my Moto X
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
PrimalMK said:
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
Click to expand...
Click to collapse
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
clsA said:
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
Click to expand...
Click to collapse
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version of TWRP does not work. I have no preferences when it comes to OS's. A stock OS (is OS and ROM the same thing?) would be fine.
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
PrimalMK said:
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version does not work. I have no preferences. A stock OS (is OS and ROM the same thing?) would be fine.
Click to expand...
Click to collapse
Well your going to need adb / fastboot on your PC
use mine here >> https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
and install the HTC Drivers here >> http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
unzip that to c:\ so you have c:\fastboot in windows explorer
now inside the folder you shift + right click / command prompt here
now you have a command prompt window type
fastboot getvar all
and post the result here / minus your serial number and IMEI
then i can find you the correct recovery and rom for your phone
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
PrimalMK said:
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
Click to expand...
Click to collapse
yes window 8 will be a problem till you get another hboot above 1.44/1.54
hboot 1.55 has no problem on windows 8 ( I use windows 8.1)
clsA said:
instructions
Click to expand...
Click to collapse
Downloaded fastboot, unzipped in c:
Drivers from that link are classed as malware. Trying to find earlier drivers/other mirror.
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
PrimalMK said:
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
Click to expand...
Click to collapse
this will work fine
just put TWRP and the Rom in the fastboot folder
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
clsA said:
this will work fine
just put TWRP and the Rom in the fastboot folder
Click to expand...
Click to collapse
error: cannot open 'openrecovery.......img'
What to do?
PrimalMK said:
error: cannot open 'openrecovery.......img'
What to do?
Click to expand...
Click to collapse
is it in the fastboot folder ?
clsA said:
is it in the fastboot folder ?
Click to expand...
Click to collapse
Yes, see screenshot.
PrimalMK said:
Yes, see screenshot.
Click to expand...
Click to collapse
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
clsA said:
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
Click to expand...
Click to collapse
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
PrimalMK said:
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
Click to expand...
Click to collapse
fastboot crashes ?
no if fastboot getvar worked it will all work
it's only 4 commands and your phone will be working
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb sideload rom.zip
sideload takes about 8 min
calculation icatkg
clsA said:
fastboot crashes ?
no if fastboot getvar worked it will all work
Click to expand...
Click to collapse
Restarted a couple of times etc. It worked. Will do the ROM thing now.
PrimalMK said:
Restarted a couple of times etc. It worked. Will do the ROM thing now.
Click to expand...
Click to collapse
great your about done ...your phone will be android 4.3 when it finishes
don't take any updates to the OS
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
PrimalMK said:
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
Click to expand...
Click to collapse
no problem, hit the thanks button
Hi all, I did a dumb thing and I took the recent Verizon OTA on my dev ed moto x with a custom recovery installed (TWRP).
Now my phone seems to always stop booting at recovery, then if i hit 'reboot system' from recovery, I can get into my system for about 2-3 minutes, and then it reboots to recovery again.
Any help would be greatly appreciated!
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
KidJoe said:
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
Click to expand...
Click to collapse
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
switch81 said:
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
Click to expand...
Click to collapse
First, if you can't boot your phone into Android, you can't use Rashr.
Next... ADB needs you to be up in Android, and have the "USB Debugging" options checked. Also, it can not be used to flash the components of the SBF/ROM like recovery.img.
Fastboot mode works with Fastboot.exe or mFastboot.exe... ADB commands do not work when the phone is in fastboot mode.
Here is what you want to do AFTER you have the stock reocvery.img you want to flash... (this is pretty much exactly what you did to flash TWRP on there in the first place, except you will be flashing a stock recovery.img instead)
have the latest Moto drivers installed. You can get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Make sure you have the Android SDK/Platform Tools installed (don't know how, see -> http://mark.cdmaforums.com/ADB.htm )
You need the latest version of Moto's fastboot, and it needs to be put in your windows Path (there are steps on -> http://mark.cdmaforums.com/ADB.htm )
Once you have that... do the following...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you have your recovery.img you want to flash
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
You should enter STOCK recovery.
use the VOL DOWN Key to scroll and the POWER Key to select reboot.
The phone should reboot and and be ready for the update
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
I'm sure KidJoe will respond, but I found this thread of his very useful:
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
switch81 said:
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
Click to expand...
Click to collapse
I was able to flash back to stock recovery and take the 212.166.3 build KXA21.12-L1.26-3 (which is still 4.4.4) OTA that Verizon is pushing out.
I didn't even have to disable Xposed or anything else. Then again, other than Xposed, root and twrp, I'm running stock. No tethering hacks, build.prop changes, no system files removed or renamed, etc.
---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
Yup., Clearing cache will delete the OTA ZIP file that was downloaded. So the next time you reboot, it wont try to install, instead you'll be back to being notified that an update is available asking you if you want to download it.
But yup, those instructions I just typed should work...
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
switch81 said:
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
Click to expand...
Click to collapse
The release notes on VZW's page only seems to mention bug fixes.. no real details.
So far I haven't noticed any changes.
It will likely be a required step to get to lollipop. So either take it now, or wait and take it later, just before you upgrade to Lolliop