Related
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!
MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this
MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry
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 seem to have a problem
So I was running 4.4.2 with Sense 5.5 on my phone. Vodafone (my phone company in Aus) sent out an OTA update for my phone. I'd already rooted my phone and had a custom recovery, so I knew I wasn't able to install it without going back to stock. So I tried following the procedure to go back to stock. Used 'Guru_Reset_M7_2.24.980.2' to do it and it seemed to work pretty well. It was 4.3, so I did an OTA, first one (like a 3mb file) installed fine, then the second one for 4.4.2 Sense 5.5 downloaded and installed, but not it is stuck in a boot loop. So I tried to do a factory reset from the bootloader which sent it back into the bootloop, then as nothing was working, I thought I'd install the custom recovery (TWRP) and install the ROM again and just leave it at that so at least I have a phone. Only problem is I had to unlock the bootloader again which wiped everything on the internal storage. And I'm stuck.
There's nothing in the internal memory. It's stuck in a bootloop after an OTA. I have TWRP installed as my recovery. I can access both recovery and bootloader.
Any idea's?
Also, for some reason, I can't download or access anything from this website; http://ww35.bugsylawson.com/ which I've seen used in multiple places to try and unbrick your phone
Thanks all!
Gunny007 said:
Hi guys,
I seem to have a problem
So I was running 4.4.2 with Sense 5.5 on my phone. Vodafone (my phone company in Aus) sent out an OTA update for my phone. I'd already rooted my phone and had a custom recovery, so I knew I wasn't able to install it without going back to stock. So I tried following the procedure to go back to stock. Used 'Guru_Reset_M7_2.24.980.2' to do it and it seemed to work pretty well. It was 4.3, so I did an OTA, first one (like a 3mb file) installed fine, then the second one for 4.4.2 Sense 5.5 downloaded and installed, but not it is stuck in a boot loop. So I tried to do a factory reset from the bootloader which sent it back into the bootloop, then as nothing was working, I thought I'd install the custom recovery (TWRP) and install the ROM again and just leave it at that so at least I have a phone. Only problem is I had to unlock the bootloader again which wiped everything on the internal storage. And I'm stuck.
There's nothing in the internal memory. It's stuck in a bootloop after an OTA. I have TWRP installed as my recovery. I can access both recovery and bootloader.
Any idea's?
Also, for some reason, I can't download or access anything from this website; http://ww35.bugsylawson.com/ which I've seen used in multiple places to try and unbrick your phone
Thanks all!
Click to expand...
Click to collapse
instructions
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:
instructions
Click to expand...
Click to collapse
Will this enable me to go fully back to stock and perform OTA updates, or is this just a way to get me out of a rut?
Thanks for the help by the way, currently in the process of doing the sideload.
Gunny007 said:
Will this enable me to go fully back to stock and perform OTA updates, or is this just a way to get me out of a rut?
Thanks for the help by the way, currently in the process of doing the sideload.
Click to expand...
Click to collapse
your just flashing a rom ...nothing to do with getting updates
clsA said:
your just flashing a rom ...nothing to do with getting updates
Click to expand...
Click to collapse
Thanks for the help man, I tried doing an ADB before I posted this and it didn't work for some reason, but when I used this ROM, worked perfectly fine. Just updated to 71.1 just then as well, so now phones working a-okay. Thanks again man!
Gunny007 said:
Thanks for the help man, I tried doing an ADB before I posted this and it didn't work for some reason, but when I used this ROM, worked perfectly fine. Just updated to 71.1 just then as well, so now phones working a-okay. Thanks again man!
Click to expand...
Click to collapse
Good to here
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!
Hello everyone,
as a beginner in flashing roms/kernels, I flashed the dt2w (which is present on this forum) on my HTC One Mini 2. When I tried to reboot it, the screen was all blac. You could tell the thing was running, because of the vibration and sounds, but no image at all.
That's why I now need the stock kernel (original one?) and I don't know where to find it, neither if I have saved it somewhere, which I will flash using fastboot/adb.
Thank you
Linkalex1 said:
Hello everyone,
as a beginner in flashing roms/kernels, I flashed the dt2w (which is present on this forum) on my HTC One Mini 2. When I tried to reboot it, the screen was all blac. You could tell the thing was running, because of the vibration and sounds, but no image at all.
That's why I now need the stock kernel (original one?) and I don't know where to find it, neither if I have saved it somewhere, which I will flash using fastboot/adb.
Thank you
Click to expand...
Click to collapse
I believe someone has posted the stock boot.img somewhere(I can't seem to find it). You can also take the boot.img from the Stock Rom here
I am doing so right now, but will I be able to do the official upgrades? And is this a ROM or a kernel? Thank you
Linkalex1 said:
I am doing so right now, but will I be able to do the official upgrades? And is this a ROM or a kernel? Thank you
Click to expand...
Click to collapse
No , you won't be able to install official updates once you unlock your bootloader. But you can do so manually by flashing it through stock recovery with a relocked one. Just make sure you backup everything in the phone storage if you do it since it is wiped if every time you reunlock the bootloader.
csoulr666 said:
No , you won't be able to install official updates once you unlock your bootloader. But you can do so manually by flashing it through stock recovery with a relocked one. Just make sure you backup everything in the phone storage if you do it since it is wiped if every time you reunlock the bootloader.
Click to expand...
Click to collapse
How can I flash an OTA manually?
I've got an OTA (OTA_M8_MINI_UL_K44_SENSE60_Vodafone_CH-DE_2.18.166.2-2.18.166.1_release_448149.zip) but I am not able to install it.
I've already tried flashing a stock kernel (the boot.img from the link you've posted), I've flashed a stock recovery (M8_MINI_UL_Stock_Recovery_2.19.401.2.img) and I've relocked the bootloader.
But when I get the update notification and try to update, the phone goes to the stock recovery and the update proceeds but after about one quarter of the progress bar, it stops and shows the red exclamation mark (!).
I've also tried flashing the kernel and the recovery which are included in the OTA update, but still the same error.
Do you have an idea how I can manage to successfully update?
TomTomGo! said:
How can I flash an OTA manually?
I've got an OTA (OTA_M8_MINI_UL_K44_SENSE60_Vodafone_CH-DE_2.18.166.2-2.18.166.1_release_448149.zip) but I am not able to install it.
I've already tried flashing a stock kernel (the boot.img from the link you've posted), I've flashed a stock recovery (M8_MINI_UL_Stock_Recovery_2.19.401.2.img) and I've relocked the bootloader.
But when I get the update notification and try to update, the phone goes to the stock recovery and the update proceeds but after about one quarter of the progress bar, it stops and shows the red exclamation mark (!).
I've also tried flashing the kernel and the recovery which are included in the OTA update, but still the same error.
Do you have an idea how I can manage to successfully update?
Click to expand...
Click to collapse
I managed to do it, but it was a really dirty method. What I did was find the firmware.zip file from the Firmware I got from here, locked the bootloader and then flashed it via the bootloader(renaming it to PXXXIMG.zip,check exact file name before proceeding). Make sure you find the firmware of the OTA, or just get the firmware.zip from it.
This gets messy because it will result in you reunlocking the bootloader(which I assume you probably will) which will in turn wipe the internal storage completely. So backup up the Internal Storage AND your SD card before you proceed.
csoulr666 said:
I managed to do it, but it was a really dirty method. What I did was find the firmware.zip file from the Firmware I got from here, locked the bootloader and then flashed it via the bootloader(renaming it to PXXXIMG.zip,check exact file name before proceeding). Make sure you find the firmware of the OTA, or just get the firmware.zip from it.
This gets messy because it will result in you reunlocking the bootloader(which I assume you probably will) which will in turn wipe the internal storage completely. So backup up the Internal Storage AND your SD card before you proceed.
Click to expand...
Click to collapse
I've tried what you did. Seemed to update Bootloader, Recovery and Radio.
Then I rebooted, again got the update notification and tried to install it.
Bit still the same error, software update still fails.