Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
max3o6 said:
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
Click to expand...
Click to collapse
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
[email protected] said:
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
Click to expand...
Click to collapse
Hmm, ok thanks. Maybe I need to reinstall ADB drivers. The HTC USB drivers work ok (fastboot usb is fine) and I do have ADB installed but having meddled with it (reinstalled ADB) I should try pushing again I guess.
Thanks, will try when when home! :good:
ADB without USB debugging turn on
Now sorted!
ADB works when the phone is in recovery, not in hboot. Dur.
Thanks!
Related
Hey all,
I have a Hero on 3 UK network and since the stupid network dont seem to be releasing any updates for it, I want to root it and manually put 2.1/2.2 on there.
Problem is, NONE of the guides on how to flash it work.
Here's what I've tried so far:
Goldcard method - I have succesfully created a goldcard using a Kingston 1GB card (tested on a Desire and works). Trying to downgrade to the stock HTC ROM using HTC's RUU gives me error 140 (bootloader version error).
Rooting the phone - Phone is all hooked up to ADB, can poll it for information etc. Tried to boot it into a recovery image but get an error saying the following: "downloading 'boot.img'... FAILED (remote: not allow)"
Alternate rooting method - So I found out ROM version 2.73 or whatever it is has some kind of extra security on it. The guides are advising me to download flashrec.apk and install on phone to backup then flash the recovery sector of the phone. This doesnt work. I can neither backup nor apply the recovery images. Even if I override the backup part, it still wont work Just gives me yet another error.
Seems that my Hero is locked down with some impossible to break security. Anyone else having the same difficulty with Three UK? If so are there any other ways you guys may have come up with to root/flash your phone? I'm getting really pissed off with it and am probably going to do an insurance job on it if I cant flash it.
FYI, this phone has not been updated since August 2009. Everything on it is stock from Three UK.
Versions (if you think it's useful):
Firmware: 1.5
Build: 2.73.771.62
Baseband (radio): 63.18.55.06IU_6.35.08.22
Kernel: 2.6.27-430d1aea
Any help I shall be most grateful for!!
Follow my newbie guide. Should talk you through it step by step.
The bootloader error is probably a driver thing. Update your HTC Sync and it should update the drivers.
Sorry, just noticed the thread got moved, my mistake.
Anyone able to shed any more light on it?
I followed the noobie guide and it didnt work. I have the latest version of HTC Sync installed.
Insurance job looking more likely.
Still with error 140? Did you update the driver in fastboot / bootloader mode?
Alternatively try this: http://forum.xda-developers.com/showthread.php?t=726118
btdag said:
Still with error 140? Did you update the driver in fastboot / bootloader mode?
Alternatively try this: http://forum.xda-developers.com/showthread.php?t=726118
Click to expand...
Click to collapse
Which one is your noobie thread mate? I followed several threads off this forum all claiming to be noobie. TBH, they were all pretty straight forward enough, and worked when I helped my mate flash his Desire.
Min can be found here: http://forum.xda-developers.com/showthread.php?t=645253 (it's also in my signature )
Ok yeah, I'll just go over the points in your guide then explain how it failed...
Using Flashrec to backup and apply a recovery image...
Flashrec simply doesnt work on my phone (have tried about 3 different versions, including the very latest which is 1.13). No functions work. Cant even use the bypass backup button (hidden button to the right of backup button). That section ended there for me.
Goldcard method...
No matter what RUU I try to downgrade to, it does not work. Keep getting error 140 (incorrect bootloader version). The goldcard I made definitely works as we used the same one to downgrade my mates Desire today.
I found some other guides, which looked like they might help as they go a bit further, but ultimately every time I try and actually do something, it gets blocked, access denied or some other error.
Flashrec won't work if you're on the wrong version of android (i.e. not downgraded using goldcard).
Goldcard is fine it is most likely your drivers in your bootloader mode that are wrong - check them first.
Drivers were ok. I managed to downgrade using a newer version of the stock HTC ROM after scouring these forums for hours.
So in short... ALL GOOD.
Only problem I have now is that there is no manual update option on eclair (1.5). The 2.1 FOTA updates attempted to download before I setup the WiFi and now it wont come back.
If you want to stay official then you can put the month forward a few and the update should show up again.
Surely the point of this was to get root and a custom rom though no?
The point was actually to get Droid 2.1 'cos 3Uk are dragging their heels big time, but now opens up the options of loading custom ROM's.
TBH I'm happy just to have 2.1. Eclair was doing my head in with all its bugs.
Thanks for the tip with the date - it worked!
i wounder if you did it or not ? cuz o have the same demmn problem with my hero G2 touch t-mobile nothing work for me i try all methods i think last solution is to bring a big hummer and break it as i like (
Fellow 3 UK Hero Owner
I'd just like to add how angry I was when the 2.1 update failed to show up. The Goldcard method worked perfectly for me, then I looked at custom ROMs. I currently run Gingerbread and I have to say, not only is it SUPER fast and smooth but its way less buggy than the stock Hero ROMs.
I'm with the Cronos crew. To get the latest ROM, search for cronosproject (.org) and click forums. (cant post link because i haven't posted 8 times )
Seriously, you wont regret it
best way to fix this is...... make sure u have a file manager, download universal androot to your computer and then to your phone install through file manger and root phone then once rooted install rec image with rom manager from market.....there you go its rooted now follow my guide to flash custom roms properly and to root phones....
mayb its ur android version
may i please know it i can surely help you
Hello, recently I have rooted my phone using the toolkit. The current recovery I have is TWRP. I wanted the root in the first place to be able to use xposed. However, it wont work, Whenever I try to install the update or new version it force reboots my phone. Also I found out I cannot update my software! I tried unrooting using the unroot option on SU but it was only temporarily. I want a permanent unroot and back to stock.
Android version : 4.4.2
Software number : 1.12.502.18
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me. Thank you.
Update
So i just downloaded a different image. I flashed it successfully! I am currently rebooting from the original recovery! Currently I am on the htc one loading screen. It's been a couple minutes, hopefully I did not brick it...
NOPE! I successfully returned to stock! ANother issue...I still have root access! How can remove SU? I tried the unroot option in the app but I am still rooted after reboot...
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
helpmeunrootmyphone said:
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know if the app is that big of a deal to you, but if it is, your options are...
1. Try factory reset in settings (may or may not work)
2. Reflash TWRP and flash the SuperSU.zip again than do a full unroot in settings.
3. Reflash TWRP and flash stock Sense ROM
Also, I made a guide in general which will help you fully return to stock. To begin the guide, you will need to be unlocked, rooted, and S-Off. That guide will help you hide the tampered and relocked banner.
If you don't care about the banners and the SuperSU app, it's probably not worth the effort and time.
Good luck.
Sent from my HTC One_M8 using Tapatalk
So you had an issue with Xposed, and you solution was to unroot? Wouldn't it have made more sense to troubleshoot the xposed problem? If you bothered to unlock the bootloader and root in the first place, IMO unrooting is a step backwards.
I'm also not a big fan of applying OTAs to a modded device. Yes, you cannot install official OTA updates on a modded phone. In particular, if stock recovery is not present, as its required for the OTA to install. If you want the latest software, just wait until the rooted version is posted in the Development section. Custom ROMs based on the 1.58 update started to be posted one day after the OTA started rolling out; and the stock rooted version was posted only 2 days after OTA release. For some people, getting it from here may even be faster than waiting for the OTA! That's pretty much how it goes. As long as there is developer interest in the device, you can rely on the latest software being available very quickly in the Development section.
The stock AT&T software is garbage anyway. I can't stand the amount of bloat, gimped features (WiFi hotspot) and other AT&T meddling. I don't understand why anyone would prefer this over other options. Software updates are always going to go to the international version first, anyway (AT&T is notorious for delaying updates for "testing"). What are you really getting with the 1.58 update? Extreme Power Savings mode, and a few other fixes? International M8 has had EPS mode for some time now.
---------- Post added at 09:31 AM ---------- Previous post was at 09:17 AM ----------
helpmeunrootmyphone said:
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me.
Click to expand...
Click to collapse
Why do you need to use the toolkit at all, to flash recovery? Flashing recovery is a single fastboot command. Easy.
The toolkit adds unnecessary complication; and I've seen them cause errors when doing it "manually" works just fine. The toolkit might not be the problem in your case, but we would never know unless you try to do it manually.
If you really want to flash stock recovery (not my personal recommendation), I would start by wiping cache and flashing recovery with fastboot. I've seen maybe dozens of cases where issues with flashing a recovery was solved simply by wiping cache:
fastboot erase cache
fastboot flash recovery "filename.img"
I am having the same issue as above using the same build file from the link given in the other thread. However, whenever I am in Bootloader, the computer or terminal does not recognize my device.
1.12.502.18
Anytime I try to use the toolkit or manually through the command line, it gives me "unc paths are not supported" or "device not found". It is the same for both Bootloader and Recovery. My original problem was the person I bought it from had root on it so I decided to wipe the OS without backing up and now cannot get the Stock Recovery ROM or any other Custom ROM to install on the phone. I have also tried the SD card method and that brought up an error as well resulting in "failed."
Any help would be appreciated as the phone as it sits right now does not have any OS on it so it is stuck on the HTC Boot up screen.
Thanks in advance for those that can help.
I just got by brand new M8 (AT&T, Android 4.4.4). I plan to flash custom roms but in reading about some of the roms it seems I'm better off upgrading to the newest OTA update first. Since I don't have my at&t nano sim yet I figured I'd update manually. I downloaded the ruu from the HTC site along with the HTC sync app. In installed the sync app and connected my phone to it no problem. I then tried to run the ruu. It gives me an error 170. After researching the error and trying a few things still no luck.
I then tried to look in the windows temp files and get the rom.zip file, put that on my sd card, rename it to 0P6BIMG.zip and let the phone flash that. First there are 2 zip files (rom_01.zip and rom_02.zip) in the temp directory and I don't know which to use. I tried the larger of the two files but got an error about large zip file when it tried to flash.
Any suggestions on getting on the latest update before I begin rooting and trying custom roms?
axeman71 said:
I downloaded the ruu from the HTC site I then tried to run the ruu.
Click to expand...
Click to collapse
What version number RUU?
axeman71 said:
It gives me an error 170. After researching the error and trying a few things still no luck.
Click to expand...
Click to collapse
If you don't specifically tell us what you tried, that second sentence isn't particularly useful.
Error 170 is USB connection error. RUU is very finicky, so just because other USB functions work, doesn't mean the RUU will. Try with the phone in bootloader-fastboot mode, try a different USB port, and different cable. USB 2.0 and Win7 have best compatibility with RUU.
axeman71 said:
I then tried to look in the windows temp files and get the rom.zip file, put that on my sd card, rename it to 0P6BIMG.zip and let the phone flash that. First there are 2 zip files (rom_01.zip and rom_02.zip) in the temp directory and I don't know which to use. I tried the larger of the two files but got an error about large zip file when it tried to flash.
Click to expand...
Click to collapse
I'm not familiar with the instance of 2 different ROM.zip files being generated in the temp folder, so its impossible for me to say which to flash, and/or if they are safe.
Large zip file error when flashing zip is usually because there is a new requirement with the MM ROM, where you need to flash the MM firmware.zip before you can RUU. But I can give more guidance once you specify which RUU you are trying.
I am trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. I did try 2 different USB ports and 2 different cables but I was still getting the Error 170 USB error. I have Windows 10, I don't currently have access to a Windows 7 machine.
I thought the 2 roms was strange too. I didn't find reference to it anywhere in my searches.
I have been trying the bootloader-fastboot method but the process hangs at either "Updating...(1/2)Sending" or "Updating...(2/2)Sending". After an hour or and hour and a half I finally just disconnect the phone and reboot it.
axeman71 said:
I am trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. I did try 2 different USB ports and 2 different cables but I was still getting the Error 170 USB error. I have Windows 10, I don't currently have access to a Windows 7 machine.
Click to expand...
Click to collapse
You can't update by RUU to MM, unless you flash the MM firmware.zip first. Its some new requirement HTC added with all the MM RUUs. See the red text under RUU section of my Index thread, for instructions on flashing the firmware: http://forum.xda-developers.com/showthread.php?t=2751432
Although, failure to flash the firmware usually results in Error 155 Unknown Error. I suspect you still have some PC incompatibility with the RUU. Some folks have mentioned you can temporarily "turn off" USB 3.0 (if you have it) and make the port use USB 2.0. I'm not too familiar how to do that, but at least one guy had success with the RUU that way. So may be worth looking into. Otherwise, you may need to try to find a Win7 PC you can use.
The other option is to flash the firmware, then try the ROM zip again by SD card method. But I'm still a bit uneasy why there are 2 ROM zips, so do so at your own risk.
Awesome, flashing the firmware first worked. Strange that HTC would put the file and instructions on their website knowing it's not going to work without the firmware.
Thanks
axeman71 said:
Awesome, flashing the firmware first worked. Strange that HTC would put the file and instructions on their website knowing it's not going to work without the firmware.
Thanks
Click to expand...
Click to collapse
Happy to see it worked for you.
Yeah, I agree its strange. Folks fairly frequently need to resort to RUU to update, due to OTA not working or not available (such as you). So its odd to introduce the requirement to flash the firmware (which the huge majority of users won't have the skills or resources to even figure out is a requirement, must less perform), which AFAIK is present in every MM RUU for the M8 (not just AT&T).
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
moyabrit said:
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
Click to expand...
Click to collapse
use adb and flash androkernel to fix the incorrect kernel that you installed. you can do that by renaming it boot.img and sending the command fastboot flash boot boot.img
i haven't messed with androplus in a while but if you were on marshmallow i believe v34 will work and if you were on the absolute newest marshmallow i think its v35 off the top of my head.
fyi you dont need usb debugging on to use flashtool, you can get into fastboot mode with no rom at all installed.
So my phone works fine but I decided to try my first rooting job on it a few months back and I screwed up somewhere. My intent of rooting was to install a custom rom like Lineage OS. I decided not to flash Lineage OS at the time because I wanted to use the phone rooted right away and I was not patient enough to go through that process so I put it off but I intended to eventually get off stock. Then a new update came out for stock and would continually throw me out of apps and could not install because of the unlocked bootloader (I didn't know about turning off auto-updates in developer options. Must have skipped past it.) so I decided to finally flash Lineage. I got a new computer in the mean time since first root and decided to try and flash Lineage on my phone from it and realized that my TWRP was no longer installed so putting a custom rom had to wait until I reinstalled TWRP. I then tried to re-flash TWRP and realized that only two fastboot commands would NOT freeze up or throw up an error: fastboot devices and fastboot reboot bootloader. So then I realized I am stuck. I cannot, at least as far as I know, flash custom roms OR stock ones without those fastboot commands.
I first thought the issue was my new computer which had only USB 3.0 ports and the original root happened from a USB 2.0 port so I assumed it was an incompatibility with the ports but my old computer threw up the same errors so that wasn't it. I then thought it was an issue with the drivers and that wasn't it either because I must have tried 10 different configurations with the same exact error. So my new thought was to look at the error signs again. Almost all "fastboot flash recovery recovery.img" with TWRP nash img file gave an error similar to max-download-size exceeded. Or just froze. The most common error was "remote: unknown command" but one error was interesting and is why I decided to post here. I don't have it logged because I forgot to paste it out of my clipboard but it went along the lines, "Warning: Device A/B support is outdated. Bootloader update required."
What can I do about this? Buy another phone? Send it to a repair shop? I am exhausted trying all the advice I found online and I am extremely frustrated that I messed up and I don't know how to fix it. This phone was relatively inexpensive but I would love to spend that money elsewhere.