Related
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
I have to have screwed the pooch pretty bad, I'm caught in a loop at the HTC splash screen and then it reboots. Any helps would be very much appreciated. I know I did something, I just don't know what.
you dont give enough info..i mean what steps did you follow? when did things go wrong? what step was it? what was the last thing you did?
pull the battery and then boot into recovery (hold volume down+hold power)
EVOKeith said:
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
Click to expand...
Click to collapse
Flash the RUU from the "All roms" thread
Everything was fine after the root guide I followed (the idiot-proof one). When I attempted to do the Nand access portion something went wrong because I got an error that the SD card was blank or had an unsupported file system. The only choice I had was to format the SD card.
Now, when I attempt to install a downloaded .zip from recovery it acts like it is going to install but goes right back to the menu after a few seconds. IF I tell it to reboot then I get caught back in the splash screen rebooting over and over again.
do a full wipe and cache wipe, reboot and see if that helps before you go any further. you do that when you boot into recovery. that will likely fix it. If not post what it does then.
What happens:
When I boot into recovery the first bit is that it tried to load PC36IMG.zip, I get the following:
Main version is older!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
I selected No and went into Recovery. I wiped all data and cache and rebooted. Once again the white HTC EVO 4G screen comes up for a few moments and then the phone powers off and restarts with the same screen over and over. I'm at a complete loss.
bumping for help
is that pc36img.zip the rom that you initially flashed that worked or is it a different one that was part of the 'nand access portion'? I figured that would be from an 'update.zip', but I barely know what I'm doing outside of the well detailed guides.
If it isn't the rom you flashed, try loading that rom back on there. I hope you have another device you can read/write micro-sd's from.
If it is the rom you flashed try flashing another rom.
...I'm a noob here too, but I'm on my second rooted/custom recovered phone so I'll help as I can.
Did you make a nandroid backup?
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
EVOKeith said:
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
Click to expand...
Click to collapse
Lucky for you that none a single rep I've ever spoken to in any Sprint store has any idea about anything whatsoever. I returned a Samsung Moment that I never bothered to restore to stock...hey turned it on, it booted up with a "Hacksung, XDA developers" screen, proceeded to load up a (then hours old) 2.1 lock screen and said "Okay, it still works", didn't check to see if I had kept the memory card in or even re-packed the charger and gave me a refund for everything on the receipt, even things I didn't have in the bag.
...another time before that I was asking about the Android 2.1 update and when it was being rolled out to which the sales rep stood up, turned around and yelled "Bobbyyy....what's an android and when do we get one in?"
Though I'm sure there is a way to bring your phone back...perhaps check in on the thread where you got your rom and see if anyone else has had such issues, give all the details you can in the order in which they happened.
If you can still get to the hboot screen try the zip posted here using the instructions here
I kept getting a pop up message on my phone saying a new software update is available for my device. It appears to be an Android update MB860 v4.5.141. So I downloaded the update with no problems but the update won't install.
When I clicked Install the phone shut down as it's supposed too. But the update fails and I keep getting a black screen with Android & an exclamation point inside a Triangle. I have to pull the battery and restart but once the phone boots up it shuts down again to attempt to Install the update and again I get the black screen with the Android and exclamation point. The phone is unusable at this point. Any ideas?
My Atrix is NOT rooted.
I just tried the manual update and it won't work because the phone can't start up long enough, it shuts down before I can do anything. How can perform a factory reset if the phone shuts off before I can get into the menu to select factory reset? Will a factory reset even fix this problem?
Hi,
check this:
http://forum.xda-developers.com/showpost.php?p=22636544&postcount=5
Good luck
Thank you for the help. The problem is I'm new to Android so I don't really understand what that post is telling me and I'm a new member here so the forum won't let me post a question there. I don't understand how to boot into CWM or how to format the /cache partition once I get there. Any help would be greatly appreciated.
NY Yankee Pride said:
Thank you for the help. The problem is I'm new to Android so I don't really understand what that post is telling me and I'm a new member here so the forum won't let me post a question there. I don't understand how to boot into CWM or how to format the /cache partition once I get there. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you flashed a custom recovery? If you have, boot into it by holding volume down after turning the device on. Then hit volume down until you have selected recovery. Then hit volume up to boot into recovery. From there, wipe the cache partition and reboot.
If you haven't flashed custom recovery... I dunno what to tell you. It's strange that the OTA update isn't working on a non-rooted, non-unlocked phone.
I don't even know what flashed recovery is. Is that what the post above is about where it explains to boot into CWM and format the /cache partition? Sorry for the newb questions but I'm really lost here and kind desperate because now I'm without a phone.
NY Yankee Pride said:
I don't even know what flashed recovery is. Is that what the post above is about where it explains to boot into CWM and format the /cache partition? Sorry for the newb questions but I'm really lost here and kind desperate because now I'm without a phone.
Click to expand...
Click to collapse
Make sure phone is off.
Press and hold the volume down button, then press the power button.
When text appears on the screen, release the down volume button. Then press the down volume button again and watch the text change... keep going until text reads "Android Recovery". Press up volume button. IF YOU go to far (too many down presses) keep pressing down and it will cycle back...don't press the up volume expecting to go back.
You are now in recovery...if you have a screen with a big triangle and an exclamation point, press both volume buttons at the same time. A menu will appear. Use volume buttons to move to the option you want and the power button to select it. Most likely, you'll want "factory reset". do that.
If you end up with any other screen (not the triangle) then you have a custom recovery and you knew everything I just told you...
Yeah it looks like a factory reset is my only option at this point, I was hoping to avoid that. Thanks for all the help and tips.
I got it working!! I spent about an hour searching google with different search phrases and I found a post where someone had a similar problem about a year ago with a different phone. This is what I did:
-I pulled the battery then booted up the phone by pressing the power button & the volume down button at the same time until "Fastboot" showed at the top of the screen.
-Then I scrolled through & selected "Android Recovery"
-I then selected "Wipe Cache Partition"
-Then I selected "Yes-Wipe Cache"
The phone then restarted and I got a message that the update failed but the phone stayed up and running and has been working fine since. I've since restarted it several times.
So the update did not install but I'm not going to attempt the update again at this point because I'm sure I'll just have the same problem.
I know I said the phone was not rooted but I failed to mention that I did buy the phone used so I don't know what the previous owner did to it. But I did a Factory Reset on the phone when I bought it so wouldn't that remove any previous rooting on the phone if there was any?
NY Yankee Pride said:
I got it working!! I spent about an hour searching google with different search phrases and I found a post where someone had a similar problem about a year ago with a different phone. This is what I did:
-I pulled the battery then booted up the phone by pressing the power button & the volume down button at the same time until "Fastboot" showed at the top of the screen.
-Then I scrolled through & selected "Android Recovery"
-I then selected "Wipe Cache Partition"
-Then I selected "Yes-Wipe Cache"
The phone then restarted and I got a message that the update failed but the phone stayed up and running and has been working fine since. I've since restarted it several times.
So the update did not install but I'm not going to attempt the update again at this point because I'm sure I'll just have the same problem.
I know I said the phone was not rooted but I failed to mention that I did buy the phone used so I don't know what the previous owner did to it. But I did a Factory Reset on the phone when I bought it so wouldn't that remove any previous rooting on the phone if there was any?
Click to expand...
Click to collapse
No. Factory reset does not clear out rooting, unlocking, or any modifications to the bootloader or recovery.
for root: There's a root checker app in marketplace to test root access. If you do have root access you need to unroot before applying the update.
for unlocked: the only way I know to tell is when you power on the phone the word "unlocked" will appear at the top of the screen.
bootloader and recovery: if you have a locked bootloader than you should have stock bootloader and recovery = ok to apply OTA update. If you're unlocked, do NOT apply the OTA update. A few people have succeeded somehow, many do not.
Thanks Gnac. I just noticed when I turn the phone on it does say "unlocked" at the top left of the screen, I never noticed that before. I know for sure the previous owner was using it on AT&T so I don't know why he would have unlocked it. I think I'll just skip the update to avoid any further problems.
I know it's been a couple of months since my last post but I never got the update to work even with the manual update from Motorola's site. I followed the exact directions more than once but I just can't get it to work. At this point I don't really care about the update but the nagging pop up every hour on my phone reminding me to update is getting annoying. Is there an easy way to stop the nagging update pop up that give the option to download now or download later? I always choose later but it nags me probably 20 times a day.
NY Yankee Pride said:
I know it's been a couple of months since my last post but I never got the update to work even with the manual update from Motorola's site. I followed the exact directions more than once but I just can't get it to work. At this point I don't really care about the update but the nagging pop up every hour on my phone reminding me to update is getting annoying. Is there an easy way to stop the nagging update pop up that give the option to download now or download later? I always choose later but it nags me probably 20 times a day.
Click to expand...
Click to collapse
titanium backup's freeze function (you need to buy the paid version) can fix this. Just freeze Updater to stop the pop up.
Thanks for the suggestion but that won't really work for me since I have no experience in rooting and I'm way too worried about bricking it to even try that.
You say you bought your phone used, and haven't rooted or modified it. Are you on AT&T? If so, and were it my phone, I'd be taking it to an AT&T store and having them check it out.
We are great at looking for alternate routes to fix our own stuff and using "official routes" as a last resort (as it requires putting it all back to stock first), but to me, this is a clear case of their own update screwing up for some arbitrary reason -- totally not your fault.
I don't think that will work because the bootloader is unlocked so I have to assume the previous owner rooted the phone. When I start up the phone it says "unlocked" in the top left corner during start up.
Wait for the update but I know that come in 2013 when android world will be jelly bean
Inviato dal mio MB860 usando Tapatalk
Ok I'm sorry to be a pest but I can't take this darn nagging pop up 20+ times a day. Obviously I don't have a clue about rooting but a guy a work with said he could probably unroot this phone for me so I can install the update. My question is if I take the SIM card out & sign into blur will he be able to do whatever needs to be done without a SIM card in the phone? That way I can put my SIM card in an older phone I have so I won't be without a phone if it takes him a few days.
NY Yankee Pride said:
Ok I'm sorry to be a pest but I can't take this darn nagging pop up 20+ times a day. Obviously I don't have a clue about rooting but a guy a work with said he could probably unroot this phone for me so I can install the update. My question is if I take the SIM card out & sign into blur will he be able to do whatever needs to be done without a SIM card in the phone? That way I can put my SIM card in an older phone I have so I won't be without a phone if it takes him a few days.
Click to expand...
Click to collapse
Actually you could probably do this yourself.. search for "Petes Motorola root" then download and follow instructions in how to "unroot"..
Sent from my MB860 using XDA
Thank you for that suggestion. Since I don't have any experience in rooting I'm a little nervous but it seems pretty straight forward. How do I verify steps 1 & 2?
1. Make sure the Motorola drivers are still installed.
2. Make sure USB Debugging is still selected.
3. Connect your Bionic to your computer.
4. Run the Pete's Motorola Root Tools.exe.
5. Select UnRoot My Phone at the bottom.
6. Your phone will reboot 3-4 times as the program goes through all 4 steps in the process.
*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?
This is the first time I tried to root my phone. My phone is a Galaxy s4 GT-i9505
I followed this guide to the letter and it was supposed to be easy peasy. https://www.youtube.com/watch?v=LlVCjtRUrgs
Well when I was doing all that I got to the last step where I had to update my binaries but that didn't work and superSU kept closing itself down.
Someone recommended I do an factory reset and repeat all the steps, but then when I got back into my system I kept getting errors saying SuperSU has stopped and Youtube has stopped.
Those were really annoying and I tried another factory reset but I couldn't get rid of them, somehow they kept inserting themselves in my app list eventhough the apps did not work.
So I used TWRP to do an advance wipe and that's when things went horribly wrong since I had no clue what I am doing :S
I ticked the boxes Dalvik cache - Internal storage - Data and something else I can't remember.
After that was completed I could not boot up my phone anymore and now I'm freaking out trying to follow guides to fix this.
like this one : http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/
I installed this toolkit: http://forum.xda-developers.com/showthread.php?t=2226263
But the problem is that my computer is not opening the device anymore through the USB port, and when I try to install these drivers : http://androiddrivers.net/samsung-android-drivers/galaxy-s4-windows-drivers-3264bit/
there's an error when installing it fails on mobile device MTP or something probably since my computer does not reckognize the mobile device anymore.
I don't have a SD card atm I never owned one. I might need to get one in order to fix this?
I'm totally new to this and totally regretting ever trying this and being so stupid and impatient as to try an advanced wipe before informing myself well enough.
I'm freaking out like mad here and now I have to go to sleep which I won't be able to catch ofc I'm so afraid I need to toss my phone and when I think about the $$$ .. well you know what I mean.
I've tried looking through these forums and guides but I just don't understand most of it and I can't get it figured out it's driving me insane.
Just chill, there is nothing wrong with your phone. You cannot kill your phone doing the things you did.
Just flash a stock firmware true Odin and everything will be working again. Pick a 4.4.2 rom though.
The reason why you are messing up is because you tried to use a year old rooting method.
So the steps you want to take:
- Flash a stock firmware
- Flash cf-auto root http://forum.xda-developers.com/showthread.php?t=2219803
- Flash TWRP
- Flash this script in TWRP http://forum.xda-developers.com/galaxy-s4/general/scriptknoxout-complete-brutal-knox-t2807172
done.
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie