Hi,
I recently made the mistake of wiping my system partition trying to just do a factory reset. I was running a stock rooted 4.4.2 rom and TWRP recovery.
I've tried the latest RUU from HTC but it says it can't find my phone. Using the generic FUU and a 1.54.651.8 (the same version I was previously running) zip I found looks like it's starting to work - it finds the phone and everything but seems to be stuck forever on "Updating (0/7) Sending...."
I was able to get a custom rom installed, but some things weren't working quite right (couldn't send texts, kept making a weird sound, and a couple others) so I was hoping for a stock rom - rooted or not, I'm fine either way.
The bad news is that the old threads with the stock rom of that version seem to have broken links so I can't get them that way. I tried contacting a couple of people who posted them but they didn't hang on to them either.
Unfortunately, the SD reader on this phone has broken so I can't get to my old backup from before I originally rooted way back when. So what I had to do to install the custom rom was boot into TWRP Recovery, ADB push the .zip over to /tmp and flash it from there. Which seems to work fine as far as that goes, I just need a stock rom (or nandroid backup, I suppose) that is compatible with my firmware since the RUUs don't seem to want to cooperate.
As an alternative, is there a way of pulling just the rom out of that 1.54.651.8 RUU I have in some format that would be flashable under TWRP Recovery?
I know it's an older phone and I'm on an old firmware (once I was rooted I never wanted to do any updates for fear of breaking something), but any help would be greatly appreciated since all the links I can find seem to be outdated/dead.
Related
I'm having problems with custom roms. I came from O.M.J version 1.4. Everything was fine and then I decided to format everything with CWM by Philz http://forum.xda-developers.com/showthread.php?t=2201860. Attempted to adb push the Android Revolution HD v10 rom, but it threw an error out. So I side loaded it instead. After the install was complete I find it only boots to fastboot mode because my recovery is now gone and there's no OS. After lots of googling I learn to use fastboot command, flash a few recoveries, and end up back on TWRP to load my nandroid backup. Even with my nandroid the phone would not boot past a few seconds into the OD. Only way the phone works is if I run the stock RUU. Somehow it only works with stock RUU because if I go back to anything else the phone won't connect to the sprint network. I only get so far into the setup and it goes thru boot loop. I attempted to relock/unroot and go thru the whole steps again to flash a custom rom and I'm stumped.
To top it all off I end up posting in General instead of the Q&A. It's been a long night sorry.
fixed my problem by flashing from the oldest ruu. that let me flash my nandroid backup and have it running.
Just so you know, Android Rev. 10 doesnt support Sprint yet. Which carrier did you choose on the install?
x714x said:
Just so you know, Android Rev. 10 doesnt support Sprint yet. Which carrier did you choose on the install?
Click to expand...
Click to collapse
International. I was kinda suspicious about it, but they had posted sprint compatibility first post. Mostly because of this misleading post FAQs
6. Can I flash this ROM on my T-Mobile / AT&T / Rogers... variant?
Yes, you can. The ROM will work on all the variants except Sprint, as it has some significant differences. Sprint is supported since version 9.4.
Click to expand...
Click to collapse
Anyway if someone happens to install the international roms. In order for me to return to the previous custom roms I had to flash Sprint_HTC_One_m7wls_1.29.651.7_RUU then flash the custom rom O.M.J v1.4 or like me do my Nandroid backup in which both were 1.29.651.7 based. The biggest problem I had was after installing the International roms I lost my recovery. A simple "fastboot flash recovery recovery.img" with the recovery.img of choice worked out for me.
I was working on getting 4.4 AOSP kitkat on my Atrix HD, and it was going great. While backing up with CWM, it failed on the data, but I figured I could just restore my files from a back up. When I went to put the rom on it, I got some no_contexts error and it said somethign about metadata. I tried to restore the backup and got a md5 fail. I used the advanced restore to let it skip the data part, but all parts gave a md5 fail. Now for somereason, I'm unable to connect through ADB, though fastboot still works, so I can't try pushing a stock rom. I tried adb sideload, but that didn't even remotely work. I also can't charge my phone, and it has a low battery. Does it charge in fastboot or recovery mode? Please help.
Phew
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
ace_case said:
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
Click to expand...
Click to collapse
I'm glad to hear you got things back into working order! With regards to flashing any custom ROM, the safest way is to use a custom recovery. Currently, as far as I can tell, the only official recovery for the Atrix HD is CWM but that's fine. You do want to be sure that you have the latest, most up to date version of CWM installed. As of right now, I believe that is 6.0.4.4 (http://clockworkmod.com/rommanager, mine already might be out of date again) and that may be where your problems came from when you were wiping and getting errors.
With regards to a close to stock 4.4 for the Atrix HD, there is an official build of CM available here: http://download.cyanogenmod.org/?device=mb886 although the latest build is from February, I can assure you that from running it on my Atrix HD it is definitely much smoother than what Motorola has offered (to date) for this device. There have been promises of official 4.4 support but I haven't seen anything come from that as of today (see here for more info: http://goo.gl/oK34W0)
CORRECTION: The official support for Atrix HD is here: http://download.cyanogenmod.org/?device=moto_msm8960
It is a merged thread for all of the devices mentioned here: http://wiki.cyanogenmod.org/w/Moto_msm8960_Info
I can't vouch for it personally but others have said that it has fixed a lot of bugs since the single device support that ended in February...
Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Andza195 said:
Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Click to expand...
Click to collapse
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
Okay, thanks!
StormyNight said:
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
Click to expand...
Click to collapse
Just flashed the stock rooted kitkat rom and everything is working as it was before, thank you all for your help!
Bad boyz current rom
Updated firmware
Super CID
Rooted (obviously)
S-off
adb reboot-works
adb reboot recovery-works
adb reboot bootloader-works
Fastboot reboot- works
fastboot oem rebootRUU- works
RUU-no worky, says usb device not attached even with current htc drivers
Google unable to connect to server after wipe cuz i turned blinkfeed back on and had to push OK a gizzilian times due top FC and did factory reset.
I can go to dropbox thru browser and install app backup/restore and than restore all apps, but it still fails to connect to google servers as i input info from new device (custom rom) and want to start fresh. I dont care if it wipes internal storage (learned long ago how to keep nothing on device that can't be restored off device)
Yes i wiped everything twice (except system and storage, been there done that nightmare)
So.... Bone stock (any version) rom that can be flashed in recovery......
Barebones back to stock is going to require an RUU. Did you make a nandroid of stock before you rooted the phone or is that how you got it?
If you're looking for rooted stock for most recent 5.03.651.3 rom, go here: http://forum.xda-developers.com/showthread.php?t=2766604
MFOsaka said:
Barebones back to stock is going to require an RUU. Did you make a nandroid of stock before you rooted the phone or is that how you got it?
If you're looking for rooted stock for most recent 5.03.651.3 rom, go here: http://forum.xda-developers.com/showthread.php?t=2766604
Click to expand...
Click to collapse
Nope, i'm looking for 100 persent stock RUU bone stock RUU flasable in recovery.
I'm going to go back to roots (and i don't mean ROOTED)
Let's say htc evo. You could take the RUU and extract it in rar, now adays it would be 7zip, take the rom and name it to pmg.3400(example) and put it on sd card, then flash it in bootloader. That no longer exists. I have the vary first bone stock htc one sprint rom, and have extracted rom.zip from it, and it wont flash from recovery. I need to.
Looking for old timers who know what to do with this. I don't want rooted version that will flash in recovery, i have that already and fighting to pull stock OTA update out of it to flash in recovery. There has to be someone here that has had the 1st edition sprint android (hero, or evo 1st edition) that knows what i'm talking about.
Yeah, that's the unfortunate side effect of these phones and no longer have an SD slot. And believe me, I remember the Supersonic days. OG EVO was my first HTC device. EVO LTE after the fact and now this phone. Tinkered with other HTC models for other folks as well.
There is an offchance that having SuperCID not matching for Sprint could be a culprit too. I was checking out a few threads about that after I read your reply. As far as some help from someone that is savvy with the M7... BD619 knows his stuff. PM him.
I recently got my TF701T back from repairs and they of course factory reset it (they put a new battery in). We all know it needs factory reset for that right? Anyways. I do a check for updates and nothing. I know I was running 4.4 previously but updater says no updates and stuck on original. So I start reading and download the latest US 4.4 firmware directly from ASUS, unzip it and put in main directory (verified mine was US) and reboot. Says all is fine, would I like to update, yes, reboot and I get the Android gear guy for about 10 minutes then it reboots. He shows up again and dead android shows up.
Now it just loops forever to this. I spent about 5 hours reading forums here, attempted a restore, but 1. the recovery.img link is bad and 2. my tablet isn't rooted.
Any suggestions? I can access the fastboot screen that gives me "RCK, Android and "Wipe Data". I tried Wipe data 3 times, no good still getting dead guy. I tried copying the latestest zip file to an sd card with boot.img and blob and file and ran RCK and it says match then reboots then dead guy again...
the fastboot screen says "released by: "US_epad-10.14.1.45-20131014" which I believe is the original.
You did a good job on your research. What might have tripped you up could be just a bad download. Files do get corrupted during download once in a while.
The recovery seems to have initially recognized the digital signature of the update file and started to flash it. And then something went wrong....
Download the firmware again. Unzip it once (the result should be a ....user.zip) and place that file onto a microSD formatted fat32 and not into any folder on the card. Boot to recovery (RCK).
If that does not work, try to rename the ...user.zip on the microSD to T4_SDUPDATE.zip and boot to recovery and report back.
Good luck!
So, I had downloaded 3 different versions multiple times before with zero success. But, once I took one and renamed it to T4_SDUPDATE.zip bam!
You just so made my day!
Thank you! Thank you! Thank you!
Devan
I have a question along these lines. What is the difference between the software update and firmware update and when do you do each? I understand the difference between what they are I suppose just not sure if updating is the same. Should I update kernel too or is that updated in an SW or FW update?
Thanks
Anyone?
I have seen these terms used very differently on different device forums.
Here on the Asus tablet forums people mostly talk about firmware when they mean the whole stock package. The stock firmware always comes with everything: Bootloader, recovery, rom and kernel
On the HTC M8 forum for example, they make a clear distinction: Software is rom and kernel, firmware is bootloader, radios, baseband etc.
The recovery seems to fall somewhere in between
Your bootloader version determines everything else. You should only flash a recovery, kernel or rom compatible with that particular bootloader.
You can, or have to, update it if you want to run a rom that requires a later or newer bootloader. Asus encrypts their BLs, so bootloader updates can only come from them - so far only with the release of a new version of the OEM "firmware".
If you as an unlocked, custom rom'd user then want to install a rom based on that new firmware, you have to update the bootloader and possibly but not necessarily your recovery before flashing the new custom rom.
Custom recoveries get more frequent updates. CWM, TWRP or some enterprising dev release new versions every few months. Always make sure it is compatible with your bootloader and rom. In most cases you can easily skip a few versions. But if you update your rom, let's say, from JB to Lollipop you should also update your recovery.
The kernel is considered to be part of the rom. At least every rom I know of comes with a kernel, some even with several to choose from. And it is a popular sport to try the same rom with different kernels.
You update the rom whenever the developer releases a new, updated version - or not if you're happy with what you got.
The safest place to be is always up-to-date: The latest roms usually require the latest bootloader and it's best to run both with the latest recovery.
If you have a working combo you can stick with it for years if you like.
But if you've been away for a while, did not follow the latest development, and want to update, you always have to:
Check if your bootloader is still current. If not, update it
Update your recovery
Wipe data, cache and Dalvik
Flash the new rom.
Nice explanation, I knew all of this but there is no way I could have explained it.
berndblb said:
You did a good job on your research. What might have tripped you up could be just a bad download. Files do get corrupted during download once in a while.
The recovery seems to have initially recognized the digital signature of the update file and started to flash it. And then something went wrong....
Download the firmware again. Unzip it once (the result should be a ....user.zip) and place that file onto a microSD formatted fat32 and not into any folder on the card. Boot to recovery (RCK).
If that does not work, try to rename the ...user.zip on the microSD to T4_SDUPDATE.zip and boot to recovery and report back.
Good luck!
Click to expand...
Click to collapse
THANK YOU!!!! IT worked like a miracle... Thank you !!!! :good::good::good: