Hi! I need to know how likely it is I can sort this problem out.
Alas I was rushing through unlocking my newly-returned device (Stock VODAP021 - 4.3 with HBOOT 1.55) and in my haste to attempt to nandroid backup the stock device, I believe I flashed Clockwork Recovery Mod 6.0.3.1 to my boot.
As such, if I reboot the device with the buttons in an attempt to get to Recovery, it gives me a dreaded red triangle. If I boot normally, it takes me to CWRM.
I was hoping to be able to connect to the device with ADB, however this doesn't seem to be working. I'm using Windows 8.1, but I also have access to a Windows 7 machine.
Thoughts on a possible recovery?
Progress update, after many attempts it seems I was able to get in to the bootloader, which in turn has given me access to Fastboot.
I flashed TWRP 2.6.3.3 to the device and was subsequently able to access ADB again in Recovery.
I'm attempting to upload a custom ROM to the device in the hope it will restore my system to a bootable state.
nesvand said:
I'm attempting to upload a custom ROM to the device in the hope it will restore my system to a bootable state.
Click to expand...
Click to collapse
This seems to have resolved the issue. I really wish I was able to get that stock nandroid, but alas it was not to be :/
Related
Background on phone: flashed TWRP recovery 2.4.4 and unlocked bootloader
Installed Paranoid Android custom rom
Do not like low call volume issues, low Bluetooth volume issues, and doesn't recognize my wired headset as containing a mic, people cannot hear me on it.
I am wanting to go back a stock rom. I dont care if its ICS or JB, preferably ICS. It seems the there were many options to going back stock. I tried running the .exe for the RUU, you must have a relocked boot loader. I relocked the bootloader, now i am stuck with a constant loop of booting bootloader, cannot access the recovery.
So i unlock bootloader again, reinstall recovery. Then now cannot load my rom. I keep getting errors in twrp stating it cannot mount the drive(internal sd) Get same error if i try to wipe caches. So i wipe system and rom off. Now I can clear caches and error about mounting internal drive goes away.
Now I am left without a rom. In order to run .exe RUU installer I must have locked bootloader, and have rom running in usb debug, As if right now that's impossible.
My last option is flashing the BORKED rom. My version of twrp is to new, i treid to install an older version and just messed up twrp.
Any help is appreciated, and returning to stock would be awesome. Thanks
OK...
You have a laundry list of issues...
First... You should get twrp 2.5.0.0
Then... Using fastboot...
Fastboot flash recovery (recovery name)
Then reboot to recovery...
Mount USB...
Plug phone into computer...
Hopefully windows will offer to format your internal sdcard...
After that...
If you want BORKED... find wcx recovery... Flash that with fastboot... Then install borked...
Good luck
Sent from my Vivid 4G using Tapatalk 4
I don't remember if I deleted it or what but I only have TWRP 2.6.1 on my device as a recovery and I would like to reinstall CWM on my device. However, every "flashable" CWM zip I have tried through TWRP has failed and I'm not sure why. Don't nwant to brick my device and don't necessarily want to WebOS doctor it if I can avoid it, as my device has run fairly well (I am on 4.2.2). Any/all help is appreciated. Thanks!
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
bananagranola said:
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
Click to expand...
Click to collapse
Not yet, although I managed to get a workable CWM running by moving an image to the boot folder and then updating to the latest working version (couldn't get the "touch" version to work via touch, however).
However, I may try flashing via fastboot if something unexpected happens. Thanks for the help
hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19
Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA
still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.
1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.
Hi guys i have a big problem with my phone htc one m7
i was flashing my phone with a 4.4 viperone rom, and performed a nandorid back up prior to the flash.
Installation failed and i was forced to reboot the phone, now when it loads it brings up TWRP for a few seconds and loops.
is there anything I can do to resolve this ? i cant get into recovery itself to flash a custom Rom but can access HBOOT 1.44.
i have S-On.
any help would be greatly appreciated, have i bricked this phone if i cant get into the recovery or it doesn't load ?
thanks so much
nmagriplis said:
Hi guys i have a big problem with my phone htc one m7
i was flashing my phone with a 4.4 viperone rom, and performed a nandorid back up prior to the flash.
Installation failed and i was forced to reboot the phone, now when it loads it brings up TWRP for a few seconds and loops.
is there anything I can do to resolve this ? i can get into the recovery menu i.e. fast boot etc. but i cant get into recovery itself to access my backed up img.
i have S-On.
any help would be greatly appreciated, have i bricked this phone if i cant get into the recovery or it doesn't load ?
thanks so much
Click to expand...
Click to collapse
First if you want help, change your thread title to something more specific like: ''Help - bootlooping after custom rom flash''
Did you wiped cache? What version of twrp are you using?
nmagriplis said:
Hi guys i have a big problem with my phone htc one m7
i was flashing my phone with a 4.4 viperone rom, and performed a nandorid back up prior to the flash.
Installation failed and i was forced to reboot the phone, now when it loads it brings up TWRP for a few seconds and loops.
is there anything I can do to resolve this ? i can get into the recovery menu i.e. fast boot etc. but i cant get into recovery itself to access my backed up img.
i have S-On.
any help would be greatly appreciated, have i bricked this phone if i cant get into the recovery or it doesn't load ?
thanks so much
Click to expand...
Click to collapse
alray said:
First if you want help, change your thread title to something more specific like: ''Help - bootlooping after custom rom flash''
Did you wiped cache? What version of twrp are you using?
Click to expand...
Click to collapse
Thanks very much for getting back to me, after 12 long hours of research and getting my head around it, i finally found a solution!
In a nut shell this is what i did to resolve the issue:
installed ADB and Fastboot drivers
flashed a recovery img using fastboot
in recovery TWRP, used ADB to push a custom rom to my sd card
flashed with custom recovery and installed OS
What wasnt made clear was the fact that you need to be in a custom recovery (TWRP or CWM) in order for the ADB drivers to work. I was stuck for a number of hours troubleshooting why fastboot would detect my device (fastboot devices) and ADB wouldnt! It was only when i had my phone connected to my windows machine and phone was in TWRP, i could talk to my device and run adb shell, and adb push.
thank god that little cookie is over, heart attack and a loss of my Sunday, but all good now
Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)
You can install stock recovery using fastboot command.
However to apply OTA, if your phone is S-On, you must lock the bootloader.
You don't have to lock bootloader if your phone is Soff, for OTA, just stock recovery is good enough.
lyciansarpedon said:
Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)
Click to expand...
Click to collapse
Just flashing the stock recovery will probably not allow you to successfully install OTAs. You have to have stock rom, stock recovery and possibly some /preload/ files that were deleted when you unlocked your bootloader. The quickest way to stock for OTA would be to flash a RUU. I would propose this route:
Option A
Lock your bootloader
Flash RUU 3.17.502.3
Receive OTA updates if they are still available
Option B
Lock your bootloader
Flash in bootloader: firmware 4.18.502.7
Flash RUU 4.18.502.7
Flash in bootloader: firmware 5.12.502.2
Flash TWRP 2.6.3.3
Download Guru Reset 5.12.502.2 and place on your sdcard
Boot into TWRP and install GURU Reset
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery
Thanks for the feedback. I was a bit surprised to find out about needing to re-lock the bootloader even with stock recovery since a bunch of other places I looked said that I could use an unlocked bootloader as long as everything else was stock (just couldn't find a way to return to stock recovery without an RUU - which would require re-locking the bootloader - at the time). Used this (http://forum.xda-developers.com/showthread.php?t=2545227) from Majmoz's signature and got the relevant recovery.img from it. Since I had it, I figured I might as well try it before going through the process of re-locking the bootloader since being bounced out of the OTA and then going through the full process of relock-RUU-OTA anyhow was the worst that could happen. Turns out it worked.
So, for posterity's sake in case anyone else should come across a similar issue, everything I did (most of it probably unnecessary, but who knows):
-Made CWM backup (in case I happened to need to re-lock the bootloader which would wipe the device data to factory)
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
-Went into recovery from the bootloader, fastboot, plugged in the usb, and flashed the stock recovery (fastboot flash recovery [the downloaded stock recovery .img file in the platform-tools directory])
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
-Went into AT&T Software Update, let it download off the Wi-Fi, and let it apply. Did its thing with the image of the green downward arrow within the circulating arrows followed by reboot a few times, the "Android Update" screen where it runs through your applications, and voila, I am now on 4.4.2.
Updates:
-Have downloaded the updated stock recovery image.
-Flashed CWM Recovery back onto device
-Re-rooted via CWM (confirmed root)
-Made a new backup through CWM.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.
lyciansarpedon said:
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
Click to expand...
Click to collapse
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
Click to expand...
Click to collapse
no but again its a good practice to check if the recovery is working correctly.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.
Click to expand...
Click to collapse
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Is your apn correctly configured?
alray said:
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
Click to expand...
Click to collapse
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
alray said:
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Click to expand...
Click to collapse
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!
lyciansarpedon said:
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!
Click to expand...
Click to collapse
youre welcome glad it worked!