Related
Hello, xda!
I've been around on the forums for some time, flashing and messing with ROMs before, but with an old HTC Touch Pro. So forgive me for seeming like a leecher.
I've come here to ask a few questions reguarding Andriod roms and flashing/upgrading procedures. I'm comfortable with using RUUs to upgrade, but who isnt...
I've had my HTC Hero for about 2 weeks now and I accidently bricked one already. I've rooted manually once, and got no signal on the stock Sprint ROM so I tried to go back to the original flash recovery but killed my phone instead.
Could someone help me out. I've read guides and been very, very anxious to upgrade and root but as you've read, I've already bricked my phone once so I'm pretty cautious now.
From what I understand, I need to root to 1.2.3, NAND backup, WIPE sd card & phone, then flash damage control's rom.....
So do I have it right or should I read a bit more?
Any help and tips from some experienced flashers would be much appreciated. Thanks!
mjones832 said:
From what I understand, I need to root to 1.2.3, NAND backup, WIPE sd card & phone, then flash damage control's rom.....
So do I have it right or should I read a bit more?
Any help and tips from some experienced flashers would be much appreciated. Thanks!
Click to expand...
Click to collapse
First off; we're happy you chose not to give up and came back a second time.
What you do need to do is; 1) Root and flash a Recovery image 2) Make a Nandroid back up, 3) Wipe ONLY your phone (not your SD Card, unless you want to do Apps2SD) and 4) Flash the ROM of your choice.
**The rooting guide I linked above is the way I prefer to do it; via adb commands. However, you could also you use Flipz's kitchen to do all of this for you.
.
For more information about Flipz's kitchen, please go here: Flipz's Kitchen
Also, do note -- for other tutorials/guides/references; go HERE
I was seriously nervous to start the process as well. As I told someone else, being nervous is a good thing. That just means you'll be careful.
I seriously recommend reading this thread and following instructions. Do not skip steps, do not pass go, do not collect $200. I've personally used the Windows guide and the Linux guide. Both are very well done and I can verify that they work.
Beyond that, the Search function is fantastic and provides lots of information. Don't be afraid to ask questions, either. Most of us are nice and like to help, even if we do call people n00bs.
WOW! Insanely quick replies. Thanks for that guys. This is what I wanna hear so I'll be doing the flash when I get home.
I'm using the 2.1update1 sprint beta ROM right now so should I revert back to the 1.56 and THEN do all this or can I just jump right in. I've always been confused as to which rom needs what flash rec root file or w/e.
And yes, I do want the A2SD thing as thats one problem I'm having right now. I've only got 16MB of storage left of my current storage area but my 8GB sd card is almost empty except for a few songs and pictures. Also, should I upgrade my sd card to a higher class if my 8GB is a class 2?
Thanks again guys!
Also, I mentioned that the last time I tried to root, I had no service after I did so. Why is that and what do I do to fix this? I couldn't find anything on this in google searches.
mjones832 said:
Also, I mentioned that the last time I tried to root, I had no service after I did so. Why is that and what do I do to fix this? I couldn't find anything on this in google searches.
Click to expand...
Click to collapse
Some people say to toggle airplane mode on and off. Some people say reboot. The last time this happened to me I just played a video game for ten or fifteen minutes and it fired up.
mjones832 said:
And yes, I do want the A2SD thing as thats one problem I'm having right now. I've only got 16MB of storage left of my current storage area but my 8GB sd card is almost empty except for a few songs and pictures. Also, should I upgrade my sd card to a higher class if my 8GB is a class 2?
Click to expand...
Click to collapse
I've not used apps2sd myself, but I'm told the higher class card the better, for obvious reasons.
Thanks, subcypher! I've got absolutely no reason to not do this. I'll be doing it as soon as I get home.
mjones832 said:
Thanks, subcypher! I've got absolutely no reason to not do this. I'll be doing it as soon as I get home.
Click to expand...
Click to collapse
Have fun! We'll be here when you get back.
yes.. a faster class sd card is highly recommended!!! other wise with a2sd, you might see more lag... and issues.
I personally, would not do a2sd at the same time as you upgrade. finish the upgrade first. make sure all is good...
then do the a2sd. and do a nandroid backup again before.
So I just tried to go back to 1.56 with the signed RUU that sprint gives out and it gave me an error. Failed to load bootloaded or something similar to that.
Remember, I'm on the 2.1update1 beta release of sprint's rom but I wanna root and flash to DamageControl's 2.1.
I've tried looking into how to root my current 2.1update1 beta ROM but I didn't come across anything worthwhile.
Anyone know whats going on???
mjones832 said:
So I just tried to go back to 1.56 with the signed RUU that sprint gives out and it gave me an error. Failed to load bootloaded or something similar to that.
Remember, I'm on the 2.1update1 beta release of sprint's rom but I wanna root and flash to DamageControl's 2.1.
I've tried looking into how to root my current 2.1update1 beta ROM but I didn't come across anything worthwhile.
Anyone know whats going on???
Click to expand...
Click to collapse
What steps did you take to use the Sprint RUU?
In order to run the Sprint RUU, you need to do:
**Make sure you have the appropriate drivers to detect HTC Sync**
1. Install HTC Sync on your computer
2. After install, open and leave the HTC Sync Window open
3. Connect your phone; and click on the sync option. You should be able to sync, if not - then you're having driver issues.
4. After you've successfully synced, NOW run the Sprint 1.5 RUU.
5. Upon a successful RUU, you'll have your phone back to its factory settings.
Now you can reroot, flash whatever ROM you like, and flash any/all add-ons.
As far as the signal goes, the following are from the Fresh 2.0d install page.
A reboot after the first bootup finishes is recommended, especially if you were previously having PRI/PRL problems.
Click to expand...
Click to collapse
If after flashing you end up with any data issues then first try rebooting. If that doesn’t resolve it for you then try updating your profile and PRL. This is a side effect of the different PRI’s and PRL’s that people have ended up on. You may actually need to update your profile and PRL a couple times to get everything going but I promise it will. You should end up on PRL 60663.
Click to expand...
Click to collapse
I personally had no problems, but I was flashing Fresh, not Damage.
Ok, I've got it rooted, and nand-backup stored on my PC.
DamageControl says to wipe before his install. Do I "wipe data/factory reset" or "wipe Dalvik-cache" or any other options?
If its the same as Fresh, they want you to do a Wipe data/factory reset
Thanks everyone! I'm installing DamageControl right now! I'll let you know how it goes.
Success! I've got the phone rooted, at least I think I do, and flashed to DamageControl v2.08.
My next task is I really want to get my apps to install to my sdcard. I've got a 8GB class 4 sdcard. Should and can I put my apps onto this? I've heard that the hero doesnt even read and write faster then 2Mbps so I'm good, right?
Not sure if I'm rooted. I've installed a few apps that require SU and when they try to do a "SU Request" the screen sits at a black screen with that title at the top.
Any idea on whats going on?
If you were able to flash a damage less rom you're rooted.
On the black window there should be am option on the bottom to allow, select it.
-------------------------------------
Sent via the XDA Tapatalk App
The black screen for SU is caused by not having USB Debugging turned on as it is required for superuser permissions. I have not tried A2SD because I only have a class 2, but have read that unless you have a class 6 it can be slow.
When I found out that 2.2 wasnt coming out from this phone I decided that I would root the phone and load a 2.2 ROM, etc. etc. So I started researching all of these about 2 days ago... and for the past 2 days I have read so much information on this that I am now currently so mixed up and lost. There are soooo many different ROMs, different ways to do this, that, etc. I see some people do one thing that it works great, another person do the exact same thing and they havent the same luck.
Even when getting ready to just root the phone, I found an awesome post that had great information... but, then when I looked at it the post was from 7 months ago and in the N1 forums. So, I started to 2nd guess.
I suppose basically what Im in need of is possibly a normal/basic recommendation to get moving on this... Would a possible recommendation be to root the phone with the 1 click root being run through a file manager, then create a nandroid backup, then go with something popular like Cyanogen6 RC1? Its just that mod -seems- to be what a good bit of people have, and problems seem limited on it. But then again, ive read about 10 other ROMs that appear to be just as good, and people like just as well... so agian, this choice leaves me frozen as well.
Im just so overwhelmed with information ive just about frozen up... I think it need to bring it back to a basic simple plan to get moving on this. Everything I read in these forums sounds so awesome and just plain ole fun.... but like I said im currently frozen/lost. Please help if my request isnt too much...
Thanks! Any help with this will definitely melt this horrid ice!!!
Use this to root: http://forum.xda-developers.com/showthread.php?t=753910
Just do as it says and follow directions. I rooted both of my brother's phones this way. It works.
Then do as you were thinking: nandroid then install CM6 RC1. It will probably be your best bet for a solid 2.2 experience.
here's what I posted on my carriers facebook page. I kept things simple and to the point, and the point was to install 2.2 on a hero.
1. go to settings, applications and check allow installation from unknown sources.
2. install bar code scanner from the market if you don't have it.
3. scan the qr code from here: http://bit.ly/d1f0RN
4. download and install the app
5. open universal androot and click root
6. go to the market and download rom manager
7. open rom manager and click flash clockwork mod recovery
8. click backup current rom (you can always restore your backup later to go back to exactly how your phone was)
to load the rom after rooting:
1. download both the rom and google apps from http://forum.xda-developers.com/showthread.php?t=755795
2. copy the zip files to your sd card
3. open rom manager and click install rom from sd card
4. choose the rom file you copied to the sd card and click add zip, then choose the google apps file you downloaded earlier. Click ok and choose backup current rom and wipe data.
5. Enjoy android 2.2 on your Hero!!
(be careful restoring stuff using mybackup, open source roms and htc roms don't store data the same way. applications are safe to restore but system settings can potentially break things requiring you to wipe and reload again)
Not because it is my root method, but I would actually recommend using my root method and following all of the steps. It has you flash a custom recovery and patched boot.img so you keep full root via adb.
http://forum.xda-developers.com/showthread.php?t=694572
CM6 is the ONLY 2.2 ROM for the Hero at this point. But know that it doesn't have much of the Sprint/CDMA or HTC SenseUI functionality and stuff that you're used to from your current phone....like updating Profile and PRL; Sprint Navigation/Football/Nascar/etc.; your Contacts, Dialer, Messaging, and some other menus will be a little different....that's just a few things off the top of my head.
So if you kinda LIKE the way your phone is now (except maybe for some lag/slowness), CM6 won't be a very similar ROM. But you won't know unless you try it out Just offering some helpful info. Good luck -- we're here to help.
I have not found a 2.2 FroYo that I like for the Hero, it's rooted and running Fresh 2.3.3
http://geekfor.me/new-release/fresh-hero-233/
Awesome... the community here is absolutely incredible. Although I am literally tryin my best to read the ****in manual, I continue to fear that im reading something too old or outdated, or that there is something newer (easier) that I should be doing instead. I did the rooting with the 1click which was so simple... I cant believe I even spent that much time on it.
Thinking next the nandroid/recovery image thing would be a breeze, but it appears to almost be the hardest step. I see on most posts that they always tend to mention Nandroid for backups - is there a particular reason that I should use that one? Some other ones appear to be easier, but not as interesting or fun. However, im fearfully coming across a lack of exact guides that explain the process.
I truly think that once I can get the recovery image done, and I can start trying out other ROMs and such... this will become too much fun. But again, im getting so mixed up by should i do this, that, or maybe this... or wait, is that too old of information?
Regardless, thanks for all the help!
Download ROM Manager from the Market. From ROM Manager you can flash ClockworkMod recovery or Flash Alternate Recovery (I prefer this option RA Recovery) there is a newer relase but this works fine.
You can then reboot and go into recovery, back up your system as it is right now, that way you can always go back to the basic root version that you have right now. That my friend is a Nandriod back up. now you can install a ROM of your choice, once it is installed and functioning the way you like make a Nandriod back up of it, that way you always have a good platform to start from if anything isn't playing nice.
saltyclams said:
When I found out that 2.2 wasnt coming out from this phone I decided that I would root the phone and load a 2.2 ROM, etc. etc. So I started researching all of these about 2 days ago... and for the past 2 days I have read so much information on this that I am now currently so mixed up and lost. There are soooo many different ROMs, different ways to do this, that, etc. I see some people do one thing that it works great, another person do the exact same thing and they havent the same luck.
Even when getting ready to just root the phone, I found an awesome post that had great information... but, then when I looked at it the post was from 7 months ago and in the N1 forums. So, I started to 2nd guess.
I suppose basically what Im in need of is possibly a normal/basic recommendation to get moving on this... Would a possible recommendation be to root the phone with the 1 click root being run through a file manager, then create a nandroid backup, then go with something popular like Cyanogen6 RC1? Its just that mod -seems- to be what a good bit of people have, and problems seem limited on it. But then again, ive read about 10 other ROMs that appear to be just as good, and people like just as well... so agian, this choice leaves me frozen as well.
Im just so overwhelmed with information ive just about frozen up... I think it need to bring it back to a basic simple plan to get moving on this. Everything I read in these forums sounds so awesome and just plain ole fun.... but like I said im currently frozen/lost. Please help if my request isnt too much...
Thanks! Any help with this will definitely melt this horrid ice!!!
Click to expand...
Click to collapse
I know exactly what you mean. I've rooted my Hero the day the universal 1 click came out,but as yet have been reading everything I can on which new Rom to install first.
I went out and bought a new 16 gig sd card for more storage as well. I've been trying to read up on how and what is the best way to do all of the various partitions on it cause some say to just have a ext 2 partition,and others say have a ext3/4 partitions on it.Unfortunately I haven't found a easy way to make this happen except by using the FroydVillain 1.4.3 rom and I don't know if it will work with a cdma Sprint Hero or not yet.
I love the phone,and want to upgrade it to the best stable over clocked rom that will allow me to use it for everyday usage,but it doesn't look like it is going to easy as rooting the damn thing was. Seems to me that you need to be a programmer in Linux to make it work the best
I hate posting a bunch of neewb questions about it but I guess I will
Mac
Awesome! Okay perfect... it worked perfect! I know have CyanogenMod running - yeah, it def different. Seems like it will take some time to get used too. Esp since its so far from SenseUI off the bat... err well, just the way that it handles things and such.
I will definitely give it a fair shot before I even try out some other ones... but I def want to try to use one of those Fresh Roms as well.
Thanks a ton for all the help! Most appreciated!
been having some problems with my phone lately and just wondered if anyone else has encountered these. first off it seems to stop playing any media files whatsoever. i have a bunch of music on it and the player just cycles through and says its not supported. youtube always brings up the error message that the video can not be played. i turn the phone off and on and it works after that but around 24 hours later i'm back to the same thing. also tried using kies to download the 2.2 update but that sucks and doesn't work. would like to root but have no idea where to begin and am afraid i'll screw the phone up. does anyone have an explanation as to what my problem can be and the best way to get 2.2 on this phone?
1st things 1st, Go to the noob guide by S15274N in the Gen section. It has all the info you need. Read it..........
Here is basically what you will do:
Make sure you have the Samsung USB drivers loaded on your computer (found in the noob guide)
Download superonclick to Root the phone (on to the computer)
On the phone download rom manager (from the apps store)
Follow the directions from superoneclick (look at unlockcr.com good how to video)
After you root the phone then decide what to load as far as a custom ROM. I would Try the Trigger or Axura, they both very stable Download on to the computer
Then hook up the phone on to the computer Make sure you connect the usb
(the pulldown at the top) make usb debugging is clicked.
Load the rom on to the Internal sd card and then go to the Rom manager and click reboot into into recovery.. install it wait 15 mins to install and you are good to go
READ the NOOB guide it is complete this is just an outline.
good luck
well i'll give it a read and see if i have enough balls to do it. thanks
ndavis_28 said:
been having some problems with my phone lately and just wondered if anyone else has encountered these. first off it seems to stop playing any media files whatsoever. i have a bunch of music on it and the player just cycles through and says its not supported. youtube always brings up the error message that the video can not be played. i turn the phone off and on and it works after that but around 24 hours later i'm back to the same thing. also tried using kies to download the 2.2 update but that sucks and doesn't work. would like to root but have no idea where to begin and am afraid i'll screw the phone up. does anyone have an explanation as to what my problem can be and the best way to get 2.2 on this phone?
Click to expand...
Click to collapse
I'm having these same exact problams and it is very frustrating. Also the video recorder will stop working I found.
So you are using 2.1? I've gone up to 2.2 using kies. I can't remember when I went to 2.2, but my guess is this has been happening since then.
In the past week I've been on the phone way too long with Tmobile support. They say that they have never heard of this (apparently I'm not the only one though) and had me try a master reset. That didn't work and the only solution seems to be to reboot the phone. Am I the only one who thinks having to reboot within 24 hours is ridiculous?
So now that they have sent me 3 phones, they directed me to Samsung which wanted to try the same Master Reset. I know that will only temporarily fix the problem so the next step is to send the phone in. How is that suppose to work? Have no phone for a week.
I guess I could ask Tmobile to do it for me and give me a loaner, but I think it is time to go with a custom ROM.
So is anyone else having the problems we are having? We can't be the only two. Is the stock 2.2 just bad and I will be better served with a custom ROM?
I was hoping to avoid this, but the phone is pretty much crap to me now anyway, so I guess what can I lose?
pmiller said:
So is anyone else having the problems we are having? We can't be the only two. Is the stock 2.2 just bad and I will be better served with a custom ROM?
I was hoping to avoid this, but the phone is pretty much crap to me now anyway, so I guess what can I lose?
Click to expand...
Click to collapse
IMO stock from samsung have never been very impressive especially when compared to all the custom roms out here. The simplest roms to flash will be the kb1 based roms such as Trigger, Axura or Bionix (in no particular order).
Your phone will feel completely different and you will likely gain a new found appreciation for it, so go flash a custom rom
shreddintyres said:
IMO stock from samsung have never been very impressive especially when compared to all the custom roms out here. The simplest roms to flash will be the kb1 based roms such as Trigger, Axura or Bionix (in no particular order).
Your phone will feel completely different and you will likely gain a new found appreciation for it, so go flash a custom rom
Click to expand...
Click to collapse
Thanks for the advice. After reading through the steps and getting lost at only the 2nd step of rooting, I think I'll just stick to stock and deal with the problems.
Not ideal, but I'm just not in the mood to put that much into a phone anymore. Maybe I'm just lazy, but I'd like to have a program that will do all the steps of getting a new ROM on my device. I feel overwhelmed by having to maintain a ROM.
Its not as hard as you think. Just use superoneclick to get root access, download rom manager , download the rom you want on your sd then reboot into recovery from root manager and chose your rom from the sd.
Sent from my Bi-Winning powered SGH-T959 using XDA App
pmiller said:
Thanks for the advice. After reading through the steps and getting lost at only the 2nd step of rooting, I think I'll just stick to stock and deal with the problems.
Not ideal, but I'm just not in the mood to put that much into a phone anymore. Maybe I'm just lazy, but I'd like to have a program that will do all the steps of getting a new ROM on my device. I feel overwhelmed by having to maintain a ROM.
Click to expand...
Click to collapse
Give this a look
http://forum.xda-developers.com/showthread.php?t=954509
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
GeNiO426 said:
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
Click to expand...
Click to collapse
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
gosunta said:
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
Click to expand...
Click to collapse
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Finally working , i replace the file and i did upgrade my phone. Thanks a lot for all the info
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
seraphielx said:
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
Click to expand...
Click to collapse
touch the screen at right-bottom and you will see a list. Select update.zip and touch ok
hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
I'm sure there is a solution, but just forget it and install 2.2 SBF.
hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
Yes, I used Root Explorer. I'm guessing by MCFarmfresh's post that there issome sort of original build for the phone? I've looked everywhere for hours all night last night before resorting to asking somewhere, but I couldn't find anything and the "solutions" I've seen all did not work. I kept getting the same errors.
Thank you for replying. If you can help, it'll be very much appreciated.
I have a rooted Bravo and I deleted some of the bloatware, and I received the Froyo update and everytime I download and the system resets I get an error and the update stops. Selecting from memory card doesnt work for me, and I dont have a backup of the original settings to re-install (which I'm not sure how to do that either). If anyone has any suggestions I'm open.
its checking for att apps
if you renamed them name them back to apk
I didn't rename them, I deleted them off my phone.
Sent from my MB520 using XDA App
I don't know much about these things but I would think that would be a bad thing to do...
I was able to get the update to install to my phone but now it is running slow
Any more info on how to fix this issue?
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
GeNiO426 said:
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
Click to expand...
Click to collapse
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
jorgonv said:
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
Click to expand...
Click to collapse
Thanks. I'm not sure what it was, but I switched to my Windows XP desktop (from my Windows 7 Home 64-bit laptop) and the SBF Flash worked perfectly, thanks bandroid, yourself, and others. I really appreciate all of the help given. 2.2 looks and feels a lot better than 2.1 so I'm really happy about that.
MCFarmfresh said:
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Click to expand...
Click to collapse
please send me one too and where do i put it.????
mismisgh said:
please send me one too and where do i put it.????
Click to expand...
Click to collapse
If you will give me your email I can get it to you. For the life of me I cannot figure out hhow to attach files through pm using my phone lol. You can also use the .sbf method to upgrade but I'll definitely get the files to you if you send me your email.
SBF'in it...
Okay....so one of your gentleman above (I'm new to the forum ish) stated that he had deleted some apps off of his OS. I did the same thing with AT&T Hotspot Locator (unfortunately, AT&T was quick on merging this standalone app into MyAT&T so I couldn't get the atthotspotlocator.apk back). I fixed this using the SBF file.
I won't give you the step by step but I can tell you RSD Lite is a free program from Motorola. It's basically the program they use to flash boot SW onto an otherwise dead device.
Don't be intimidated by it because it really is rather easy to facilitate. Just do like I did and YouTube how to load an SBF into a motorola device. You can pause and replay as you go along to assure no errors. Takes like 15 minutes once you've got all the necessary files downloaded.
Well, that lasted long...
Everything was going fairly well until this morning when I clicked on the phone button (default launcher) and tried to go into the dialer, then it just closed every time I tried doing so.
To try to fix this I rebooted my phone, nothing; restored, nothing; factory reset, nothing; re-installed 2.2.1 FroYo via flashing the SBF with RSD Lite and 'apply:sdcard:update.zip' through Android's Recovery Screen, nothing.
When I tried doing the last 2, however, I received these errors (the first one I had with the first problem and the other 2 are new):
E:Can't mount CACHE: recovery/command
E:Can't mount CACHE: recovery/caller
E:Can't mount CACHE: recovery/log
Now, with the "caller" error, I did NOT touch anything having to do with the dialer and whatnot. That I know.
The last time I had problems with my laptop so I tried it on my desktop and it worked, but now I tried the desktop and it still isn't working properly. Some of the features that I had with the update are now gone such as the "third party apps" option and the sliding "lock screen" is now permanently present.
Any help with this is appreciated.
*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?