Related
First of all, let me apologize if this is already posted somewhere, but I'm having trouble understanding some of this.
I rooted my gf's Droid Eris and put a custom ROM on it. She doesn't want it and wants it put back exactly like it was when she got it from Verizon. This means 1) not rooted 2) Android 2.1 w/ Sense (the exact same ROM she would get from the factory).
Everything I've read so far has me doing factory resets (which puts it back to the fresh modded ROM but not the factory ROM) or has me trying to do RSD Lite, but every forum post I read has a broken link to the file because I guess it's illegal to post it or something. Additionally, I can't find instructions for following that method with the Eris anyways.
Can anyone help point me in the right direction?
btw, I'm new to rooting so treat me like a n00b...
I did a nand restore back to the when I originally rooted the phone. It now has 2.1 with HTC but the phone is still rooted.
Also, when I rooted the phone, whatever it did to root it (put something custom on my phone) it turned the trackball light on and that just won't turn off... even when the phone is off!
I'd love to just get this thing back to how it came from the factory.
Maybe if you try searching the Developement Forum, try something like "return to factory stock"
And in the future before you do anything to a phone, you might want to research how to undo it first, I bricked my first eris because I didn't bother to.
buckf1tches said:
First of all, let me apologize if this is already posted somewhere, but I'm having trouble understanding some of this.
I rooted my gf's Droid Eris and put a custom ROM on it. She doesn't want it and wants it put back exactly like it was when she got it from Verizon. This means 1) not rooted 2) Android 2.1 w/ Sense (the exact same ROM she would get from the factory).
Everything I've read so far has me doing factory resets (which puts it back to the fresh modded ROM but not the factory ROM) or has me trying to do RSD Lite, but every forum post I read has a broken link to the file because I guess it's illegal to post it or something. Additionally, I can't find instructions for following that method with the Eris anyways.
Can anyone help point me in the right direction?
Click to expand...
Click to collapse
Sure. It's pretty simple, really. Download and install the Flashback21 ROM in this thread: http://forum.xda-developers.com/showthread.php?t=792026
It will return the Eris to factory stock and remove the custom recovery on the phone. I'd do the one without the radio myself.
A friend told me that there is a way to set a phone back to how it came from the factory by installing a factory ROM directly from Verizon through your PC using an app called ODIN. I'm having trouble finding information for the Eris on this process.
I think this is EXACTLY what I was looking for! Thanks so much!
I'll let you know if it fixes that trackball issue for anyone else who may have searched that issue
This did work! I noticed that the ROM wasn't exactly like what comes with the phone when we received it from Verizon (which was the same day). I am basing this off the type of wizard that opens when you first turn on the device. It wasn't rooted, though, and did put back what appears to be a stock ROM of 2.1. It's going back to HTC/Verizon tomorrow.
buckf1tches said:
This did work! I noticed that the ROM wasn't exactly like what comes with the phone when we received it from Verizon (which was the same day). I am basing this off the type of wizard that opens when you first turn on the device. It wasn't rooted, though, and did put back what appears to be a stock ROM of 2.1. It's going back to HTC/Verizon tomorrow.
Click to expand...
Click to collapse
There are no customizations in this ROM - period.
The "stock" setup screens certainly changed between 1.5 and 2.1, and may have changed slightly from the original HTC/VZW 2.1 OTA to the July 2010 2.1 OTA update.
Having said that, there is one other thing that you might have noticed: you didn't see a device activation screen during setup. That is because NONE of the dev ROMs here on the XDA Eris touch the activation state of the phone - including Flashback21.
If you want to deactivate your phone, you need to perform the Factory Reset process from the OS menu, and a "stock" Eris recovery must be on the phone. (So, if you desire to do so, go ahead and do a Factory Reset after you have installed Flashback21)
If you have already turned in your phone, then no worries - the carrier usually deactivates the phone from their side.
Anyways, that's probably what you noticed. Flashback21 is completely stock.
bftb0
Hi all!
I did try searching, might be too simple...
New to Android, etc...
Windows and Toshiba taught me to always download original files and archive them for later recovery, drivers, etc... to factory recovery years later when needed.
Now with this...
I think I was at JRN84D (4.1) when purchased on vacation, took OTA update to JRO03D (4.1.1).
At Google, ONLY JRO03D is available.
? Should I hunt around to find and archive JRN84D (or ask for someone else's archive PM) or will JRO03D always be THE factory recover baseline for this device?
?If they replace JRO03D with something else, will those always be then considered the factory baseline? (Or should I keep a progression of images?)
?I think since this is flashed, that my OE file (JR84D) is truly gone forever, since JRO03 is flashed 'over' it, and I can never really factory recover to 'out of the box' state - am I right?
(Trying to get my ducks in a row to start trying Mskip's package...)
THANKS
As long as you have the net Mskips tool will download a stock rom and flash it for you anyway
Sent from my Nexus 7 using Tapatalk 2
ROM/ DISK Drive devices.Failure rate .
There is a huge difference in A Tablet os then the tradition installation of windows. Windows is a compiled bunch of software running on a Disk drive.. High Failure rate.
Android Tablet phone/ devices. These are firmware running on a non destructible ROM CHIP. if you are totally stock..and never change that. There is a pre made so to speak backup built in.. This will restore your device to its original state.
You can download the latest firmware os / kernel from gogle as i see you have found already. Be SURE you have and know how to use the tools to flash the software in case of a non boot situation.. I would not count on the install tools mentions above.. FASTBOOT ADB AND BOOT-LOADER COMMANDS .... If you really want to learn about android and understand arm devices more . Lots of information with a google search..
So what im saying is a Un rooted tablet have a very low almost near software error rate. (A QUICK RESTORE WILL FIX EASLY)
If you are not root and you mess up your tablet simple fix.
If you root your tablet and install a custom recovery.. Then you need to save the tools to install the recovery the recovery files. The Boot-Loader files and the ROM. YOU are using or want to use.. Could be stock ROM CUSTOM ROM. if you use a custom kernel you need this as well.
You should also first boot into the CUSTOM Recovery MADE A NANDROD BACKUP... This will be your ticket to restore the device quickly and easy.
I know this is alot of vague information but it kinda touches what your asking..
Good luck .. Guys feel free to fill in the blanks and correct my mistakes.. OOPS Erica makes no mistakes right .. hehe
THX all - I've , let's see - unlocked, rooted, flashed a new rom, restored 'factory' rom, unrooted and relocked - whew!
I think there is a real problem with terminology for OE roms - both by users and the OE. My device says factory or factory state in it somewhere - but that is clearly not what it means. It means current factory or something like that - and that it will never be back to the out-of-the-box factory state. Apparently, I can only ever get back to the cleared-of-user, current 'factory' state.
Anyway, I've a recovery method and the current rom stored for the future.
Is there a site that store earlier roms?
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
GAKB said:
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
Click to expand...
Click to collapse
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Solution
ceefercat said:
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Click to expand...
Click to collapse
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
It's worth a try!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
That's fair enough, I tried a factory reset first myself to no avail. If you do get your nexus replaced, please let me know if the update works!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
I'm considering taking it back because it is not updating as it is supposed to, as it is designed to. A message comes up on the screen that a system update is available. I go through the procedure to download and install said update. The update doesn't install, though the system now says that it is up-to-date.
Bootloader? I don't even know what that is. I don't know that the problem is caused by the bootloader and neither do you. It may be a joke to you but to me its just a pain in the neck.
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
Bootloader issues are a pain in the neck. My bootloader is locked and i cannot erase, flash, format ANYTHING on my Nexus 7... :S
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
obviously the guy doesn't have working knowledge of ADB, rooting/unlocking or any other development terms we use to describe what we are doing to our devices.
The only jokable premise here is some nerd in his mother's basement thumbing his nose at random people because the world he lives in is so narrow it couldn't possibly comprehend the existence of someone honestly asking for advice and then doing the only logical thing he can think of to do as a consumer unfamiliar with a product at a developmental standpoint.
Not everyone wants to root. And not everyone who owns a Nexus has background experience in tinkering with electronics. I've been rooting since my Dinc and I actually want to keep mine as stock as possible. I find more problems come to me when I start messing with the device instead of just leaving it alone.
---------- Post added at 12:58 AM ---------- Previous post was at 12:46 AM ----------
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I appreciate the fix. trying it out now to see if I can get stock 4.2 to update properly
Edit: Worked like a charm thanks bro for the advice
*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?
Hello,
I am not a phone expert by any means. I am probably in the 'knows just enough to be dangerous category,' but I am quite willing to learn. Here is my situation as I understand it. Please advise whether my premise is flawed.
Phone: rooted Verizon Note 3 KitKat NC4 off contract / pre-paid , no warranty
Ultimate Goal: to wipe my phone and have a clean slate. Bonus if I could be able to backup images of my phone for the future. Heheeeee.
Sitrep: phone is in need of a wipe/do-over to resolve some minor annoyances, but factory reset doesn't work. It says "System software not authorized by Verizon detected...please shove it," or something. That is curious, because, since I am trying to get rid of allllllllll the software, it should just let me do it if it doesn't like some of the software. I probably don't understand this fully. (Or else they just want me to go to Verizon so they can sell me a new/worse/more despotic phone.)
I only get that message if i try to reset it, not every time i turn it on, so it doesnt bother me, but i do want to reset it, because it is full of cobwebs and battery issues. From reading this forum, I think the reason it won't reset is that about a year ago, I installed clockwork and did *something* to the recovery, but it freaked out, because my boot loader wasn't (and still isn't) unlocked, so I uninstalled clockwork. I don't remember why I installed it. It was too long ago. I think i thought i could back up my rom or something. Anyway, it has worked fine ever since, I just can't wipe it and it tells me about unauthorized software. I found instructions on here about 'flashing back to stock kitkat with Odin,' which I gather will fix my recovery, and as long as I don't do that clockwork recovery thing again, I can reset it whenever I want to, on KitKat. (I am not interested in "upgrading.") I was all set to do that, when, last night, to my joy, I saw the Verizon note 3 boot loader unlock has arrived. That (I think) means that I can (eventually) unlock the boot loader and go back to jelly bean. Yay! Or cyanogen!! Yayay!
Question: shall I first reflash KitKat in Odin, so that the recovery is operational, THEN unlock it? Or can I unlock it first, even if the recovery is messed up, skip fixing KitKat, and go back to jelly bean (or maybe cyanogen)? I am afraid that there is a right order and a wrong order, and I'm sure to pick the wrong one.
Maybe these 2 things have nothing to do with each other. I have no idea. I just feel like I might be at a crossroad.
Thank you very much for helping a lady in somewhat unfamiliar territory.
Auralay
Auralay said:
Hello,
I am not a phone expert by any means. I am probably in the 'knows just enough to be dangerous category,' but I am quite willing to learn. Here is my situation as I understand it. Please advise whether my premise is flawed.
Phone: rooted Verizon Note 3 KitKat NC4 off contract / pre-paid , no warranty
Ultimate Goal: to wipe my phone and have a clean slate. Bonus if I could be able to backup images of my phone for the future. Heheeeee.
Sitrep: phone is in need of a wipe/do-over to resolve some minor annoyances, but factory reset doesn't work. It says "System software not authorized by Verizon detected...please shove it," or something. That is curious, because, since I am trying to get rid of allllllllll the software, it should just let me do it if it doesn't like some of the software. I probably don't understand this fully. (Or else they just want me to go to Verizon so they can sell me a new/worse/more despotic phone.)
I only get that message if i try to reset it, not every time i turn it on, so it doesnt bother me, but i do want to reset it, because it is full of cobwebs and battery issues. From reading this forum, I think the reason it won't reset is that about a year ago, I installed clockwork and did *something* to the recovery, but it freaked out, because my boot loader wasn't (and still isn't) unlocked, so I uninstalled clockwork. I don't remember why I installed it. It was too long ago. I think i thought i could back up my rom or something. Anyway, it has worked fine ever since, I just can't wipe it and it tells me about unauthorized software. I found instructions on here about 'flashing back to stock kitkat with Odin,' which I gather will fix my recovery, and as long as I don't do that clockwork recovery thing again, I can reset it whenever I want to, on KitKat. (I am not interested in "upgrading.") I was all set to do that, when, last night, to my joy, I saw the Verizon note 3 boot loader unlock has arrived. That (I think) means that I can (eventually) unlock the boot loader and go back to jelly bean. Yay! Or cyanogen!! Yayay!
Question: shall I first reflash KitKat in Odin, so that the recovery is operational, THEN unlock it? Or can I unlock it first, even if the recovery is messed up, skip fixing KitKat, and go back to jelly bean (or maybe cyanogen)? I am afraid that there is a right order and a wrong order, and I'm sure to pick the wrong one.
Maybe these 2 things have nothing to do with each other. I have no idea. I just feel like I might be at a crossroad.
Thank you very much for helping a lady in somewhat unfamiliar territory.
Auralay
Click to expand...
Click to collapse
It is because you are rooted... A factory reset just wipes user data and applications... It does not totally reload Android.
You can reflash the phone via Odin and a firmware download of the proper version (or higher) for the Verizon Note 3. Firmware is available on www.sammobile.com you have to be a member in order to download but membership is free.
If you want to stick with KitKat... You can unlock the bootloader now and then can load either CWM or TWRP and from them can flash any ROM available here.
Even unlocked i don't think you can move back to Jelly bean
Sent from my SM-N900V using Tapatalk
donc113 said:
It is because you are rooted... A factory reset just wipes user data and applications... It does not totally reload Android.
You can reflash the phone via Odin and a firmware download of the proper version (or higher) for the Verizon Note 3. Firmware is available on ] you have to be a member in order to download but membership is free.
If you want to stick with KitKat... You can unlock the bootloader now and then can load either CWM or TWRP and from them can flash any ROM available here.
Even unlocked i don't think you can move back to Jelly bean
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thank you so much for taking the time to consider my question. As sad as I am to think about not ever going back to Jelly Bean, which I assume is a tyrannical Verizon/Samsung thing, I am very glad for your input. I could have sworn I have reset this phone since rooting it, but I could just as easily be mistaken. I think I will do Odin first, and see everything is A-OK before leaping out into the unknown of unlocking. Hopefully after I do Odin, I can do resets the old easy way, but it's ok if i can't. Anyway, thanks a bunch for helping me get smarter every day. <3
Auralay
Auralay
Have you already flashed with Odin?
Hold your horses if not, I have an idea which is worth trying.
(It involves unlocking and reinstalling stock without losing root in the process.)