Database Develop

[Q] Nexus One, Return to stock 2.2 after trying 2.3.3

After the initial jubilation of finally getting Gingerbread on my stock Nexus one, I have come to the conclusion that its a little half baked and setting aside all the little annoyances, the current battery life bug that seems to be affecting some people (myself included) is just terrible.
So my question is, how to I get back to stock 2.2 (or 2.2.2) now that I have 2.3.3 installed.
I don't want to root, or open the boot loader or do anything to invalidate the warranty. Is there a way ?
Thanks, and sorry if this has already been covered somewhere else (could not find it)

shimsim said:
...I don't want to root, or open the boot loader or do anything to invalidate the warranty. Is there a way ?...
Click to expand...
Click to collapse
No.
10chars

shimsim said:
After the initial jubilation of finally getting Gingerbread on my stock Nexus one, I have come to the conclusion that its a little half baked and setting aside all the little annoyances, the current battery life bug that seems to be affecting some people (myself included) is just terrible.
So my question is, how to I get back to stock 2.2 (or 2.2.2) now that I have 2.3.3 installed.
I don't want to root, or open the boot loader or do anything to invalidate the warranty. Is there a way ?
Thanks, and sorry if this has already been covered somewhere else (could not find it)
Click to expand...
Click to collapse
http://www.google.com/support/forum/p/android/thread?tid=3ee1ccfdaffc5881&hl=en
Worked for lots of people, don't know if it works for 2.3, it worked for 2.2.
So.. ya might just wanna keep an open mind.
Anyway, some of the links on the page are dead, you might need to dig around for what you need.
Google is your friend

http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21

I tried this also (just to see for myself, instead of listening to the rumors), and can confirm it works.
The only comment I would make is that the filename is NOT case sensitive (I got it to work as PASSIMG.zip, passimg.zip, and also combinations like PassImG.zip)
Sent from my Nexus One using XDA App

Passimg method is working? Nice find! I imagine this will be of great help to many people.

Thanks for all the suggestions and help, I will give it a go.
In terms of the most recent version that I can go back to, I assume it has to be a manufacturer shipment ROM or full system image.
The latest release on shipped roms is FRG33 http shipped-roms.com/index.php?category=android&model=Passion%20(Nexus%20One
I found on the HTC developers site (http developer.htc.com/) FRG83 but the link seems to be broken http dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
Assuming I can find a copy of FRG83 system image, am I correct in assuming I can also rename this to passimg.zip and downgrade or does it have to be the FRG33 manufacture shipped rom?
ps, sorry i cant post url links hence the http

If it's a shipped image, then yes.
If you look in the zip, and see a bunch of image files, instead of a folder structure, then it will probably work...
Let me know if you find FRG83.
I know someone who would LOVE to find it!
Sent from my Nexus One using XDA App

danger-rat said:
If it's a shipped image, then yes.
If you look in the zip, and see a bunch of image files, instead of a folder structure, then it will probably work...
Let me know if you find FRG83.
I know someone who would LOVE to find it!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks!!!

Hi,
I know this question may sound stupid but I have this doubt and I would like to understand better one thing:
Can someone please explain me why it's not possible to restore 2.2 from 2.3.3 using directly a nandroid restore skipping the PASSIMG.zip part?
I'm new to this and I'm still learning some things, but if the nandroid is a backup of the entire system, why can't I just wipe out everything and restore from that file?
Thank you so much for your help!

If you have nandroid - great.
If you flashed stock image - you don't have it anymore, because stock image overwrites your custom recovery, and without unlocked bootloader or option to root, there is no way to restore it.

Thank you so much for the reply
So, just to be sure: since my bootloader is unlocked this means that if I wipe everything, then I can flash a custom recovery and then restore from a nandroid backup without having to flash first another stock ROM and root again, right?

That is correct.
However, keep in mind that rebooting your phone when you soil have the stock ROM will cause the stock recovery to be restored, so as soon as you install your custom recovery, you need to boot into recovery without rebooting the phone...
Sent from my Nexus One using XDA App

efrant said:
http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
Click to expand...
Click to collapse
The dowload link include in the link above for the ROM is not working. I am getting this error message: "Unable to open shipped/Passion (Nexus One/"
efrant: Can you please update the link?
Thank you!

jay_supreme said:
The dowload link include in the link above for the ROM is not working. I am getting this error message: "Unable to open shipped/Passion (Nexus One/"
efrant: Can you please update the link?
Thank you!
Click to expand...
Click to collapse
Updated...

I think I found a copy of FRG83 here:
androidpit.de/de/android/forum/thread/407726/ROMs-Kernels-Radios-fuer-das-Nexus-One
p.s. sorry, i still cant post url links ..... so add the w w w

OTA update file (4.0.19915 to 4.1.26)

Here is the update that the test phones(4.0.19915 to 4.1.26) received right before the launch of the retail unit. You might think this is useless, but it paints a very clear picture of how Moto updates work on the Atrix.
For each file that is being updated it hash checks and then applies the binary patch. This means changing the file permissions, mounting the system as rw will not cause this to fail as someone else had mentioned before. When it comes time to update, we can extract it and run the patch against the retail dump to create an updated dump.
This also tells us we can use recovery to flash update.zip files, we just need to figure it out. This would be very helpful when creating an updated dump.
This file is downloaded to /cache/tmp. A simple script was used to capture it before it was deleted.
Download the file here:
http://www.ponack.net/designgears/atrix/update.7z

This is very good news.
does this also mean that an OTA can be packaged as a zip and "flashed" to a phone?

verrry nice

Thanks DG!
and please stay
we will miss you

GSeeker said:
Thanks DG!
and please stay
we will miss you
Click to expand...
Click to collapse
I will still be around doing things here and there

Anyway to unbrick my atrix with this?

hassanjanjua2002 said:
Anyway to unbrick my atrix with this?
Click to expand...
Click to collapse
What kind of brick do you have on your hands?
Also, thanks dg

Very informative!

Hmmm, tried to flash it as an update.zip through recovery and signature check failed. I'm guessing since this was prior to release it was test signed? Had to try since I need something via RSD, Recovery, or Fastboot to get my phone up and running again.

navalynt said:
Hmmm, tried to flash it as an update.zip through recovery and signature check failed. I'm guessing since this was prior to release it was test signed? Had to try since I need something via RSD, Recovery, or Fastboot to get my phone up and running again.
Click to expand...
Click to collapse
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.

Im on my tablet no computer. . . Is there a boot.bin in therr if so id like to run it through my keyfind program see if i can find the same aes key in it

t0dbld said:
Im on my tablet no computer. . . Is there a boot.bin in therr if so id like to run it through my keyfind program see if i can find the same aes key in it
Click to expand...
Click to collapse
baseband_ota.img and mbm_combo.bin

I want Update.zip signed for this orginal files from /system/lib
libskia.so
libskiagl.so
libwebcore.so
Because I changed these files to make the device read Arabic, but the device stops working and Restart
Now I want to push this and return the original files

designgears said:
baseband_ota.img and mbm_combo.bin
Click to expand...
Click to collapse
Lol damnit lying in bed so tired , but so tempted by what ever mbm_combo.bin is but linux machine and keyfind back at my store only cr-48 and mac air here not enough processing power :-( anyhow thanks so much for post i cant wait to check it out. On side note you sure you going to leave dg ? I mean ever sense we got dock hack figured out im more leaning twoards keeping it . . Also because this is first cheep device i have bought $150 small invesment payed $500 or more for most my devices and cause i think we will get bootloader now and something seems weird abiut that dev dump of gb being vanilla. Maybe an option they will offer to quiet the devs anyhow at least keep posting us the leaks if you wont stay

designgears said:
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Same situation here, as you already know. is there a forum for one with a test signature?
Click to expand...
Click to collapse

Im not a dev far from one but from what i am reading this sounds like some pretty good information has been gathered just from this old update.....Also you dont have to stay just keep the leaks and any others a coming....Thanks

it seems as they signed all of the partitions... have you guys looked at the odexed version.... under recoveryand overall... what are they trying to patch... BZIP2 is attached and renamed "updater"??? Also traces of BSDIFF just like in other moto images... .
Also this is from the radio_baseband image...
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_target.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_nand.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_onenand.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_shared.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_clk.c
OLYMPUSBP_N_01.61.01P.dbl

hassanjanjua2002 said:
designgears said:
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Same situation here, as you already know. is there a forum for one with a test signature?
Click to expand...
Click to collapse
are you brave enough to flash the engineering bootloader from the other tread.... ?
It might circumvent the signature checks...
Click to expand...
Click to collapse

zambezy said:
are you brave enough to flash the engineering bootloader from the other tread.... ?
It might circumvent the signature checks...
Click to expand...
Click to collapse
Not saying that I will do it, but; How would we flash those *.bin files to the phone?

mp2ning said:
Not saying that I will do it, but; How would we flash those *.bin files to the phone?
Click to expand...
Click to collapse
I'm guessing with NVFlasher

Official Motoblur ICS for the Droid 4 possibly leaked

Just saw this thread at droidforums: http://www.droidforums.net/forum/droid-4-roms/208767-stock-motoblur-ics-droid4.html
Can anyone confirm if this is legit?
EDIT: Removed link to the update file for everyone's safety. This is not an update you want to install. It will take you off the update path and attempting to flash one of the currently available fastboot files will result in a brick.

I pulled the same thing by the cake method earlier today but was afraid to flash a unknown.

I tried, based on the instructions on the page, and as usual, cheesecake won't work for me. I get the "account needed" prompt. I'll try again tomorrow.

Thanks!
I'm downloading it now. I hope this works with Safestrap and I get to keep root. Or at least be able to re-root again. Have to be carefull. Need GSM to work

The day after I sold my T-Mo Sensation, and the day before I get my VZW Droid 4. Looks like the gods have decided not to smite me today.

Booted Safestrap. Flashed stock 215.
Can't update to 219 So no wonder I couldn't update to ICS... Here I go again...

It sounds like a couple of people over on DroidForums HAVE gotten this to load. To paraphrase what hashcode said over there, be very very careful with this guys. There are quite a few Razr owners now stuck outside of the upgrade path and unable to use fastboot to restore after flashing an ICS leak. I think I am going to hold off on this one personally. What I am REALLY hoping to see is some improvements to CM9, AOKP, and Gummy come out of this. Particularly the data issues.

Trying it the Cheesecake way and its downloading. Anyone tried it yet? Curious if Safestrap survived. As long as it works I'll be glad. Hope the different baseband fixed audio over UMTS/HSDPA.

Die Bruine said:
Trying it the Cheesecake way and its downloading. Anyone tried it yet? Curious if Safestrap survived. As long as it works I'll be glad. Hope the different baseband fixed audio over UMTS/HSDPA.
Click to expand...
Click to collapse
You are a brave man Try using OTA RootKeeper. It worked with the last update. I would be very interested to see if it works with the ICS update as well.

Ok guys, I installed it. Voodoo OTA RootKeeper did NOT work for me, and attempting to flash the 6.13.219 fastboot file resulted in a brick.
I would strongly advise not installing this update.

SGMD1 said:
Ok guys, I installed it. Voodoo OTA RootKeeper did NOT work for me, and attempting to flash the 6.13.219 fastboot file resulted in a brick.
I would strongly advise not installing this update.
Click to expand...
Click to collapse
Really sorry to hear that. Thanks so much for the information though. Did you try the .215 fastboot file? I'm guessing the result would be the same but might be worth a shot.

Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
XDA app on XT894

kwyrt said:
Really sorry to hear that. Thanks so much for the information though. Did you try the .215 fastboot file? I'm guessing the result would be the same but might be worth a shot.
Click to expand...
Click to collapse
Downloading .215 as we speak, but I'm not getting my hopes up. No big deal though, VZW is overnighting me a warranty replacement and I've got an old phone I'm using for the day.
EDIT: .215 failed at 6/18 as well.
Die Bruine said:
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
Click to expand...
Click to collapse
There were a several things with this ICS build that were a bit disappointing (native ICS screenshot function didn't work, no "Charge only" mode when connected via USB to PC) but no root access was the dealbreaker. I knew flashing the .219 file was a risk based on what happened with the RAZR ICS leaks but I just figured I'd be the guinea pig
I had the same problem you did when attempting to install it, so I flashed the clean .219 fastboot file and then the ICS update was successful.

build.prop
Die Bruine said:
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
XDA app on XT894
Click to expand...
Click to collapse
Here is the build.prop file... it is compressed into a zip archive since .prop cannot be attached.
****EDIT: THIS IS THE .215 build.prop

build.prop 219
rumgool said:
Here is the build.prop file... it is compressed into a zip archive since .prop cannot be attached.
****EDIT: THIS IS THE .215 build.prop
Click to expand...
Click to collapse
Okay... here is the 219 build.prop zipped

You gotta be kidding me pffffff. Those guys at Motorola check eeeeeeverything. Thnaks for the build.prop btw rumgool. But now it hangs on Motorola_XT894....3gp. Unbelievable...
Finally got it going. But like you said, had to flash SBF. That's some pretty scary **** . I'm used to Milestone / Droid 1 flashing and I've flashed a Razr before. This one takes twice as long. So for you wanting to flash SBF, don't be alarmed. It takes a while, a very loooong while.

Question: Why would the update prevent flashing via fastboot? I'm only familiar with SBFs, but the point of those were that no matter how bad things got, you could wipe everything out and start over. Is that no longer the case

GSM working!!!!!!
Yes!!!! audio over 3G GSM!!!!
Finally. Don't know what works and what doesn't. But audio works and you have GSM settings right from the get go. Now I'm gonna eat, then I'm gonna play and after that I'll tell you what I think of it.
Thanks guys!

podspi said:
Question: Why would the update prevent flashing via fastboot? I'm only familiar with SBFs, but the point of those were that no matter how bad things got, you could wipe everything out and start over. Is that no longer the case
Click to expand...
Click to collapse
The new fastboot files are nothing like the old sbf's. Wrong radio, different build number and many other things can cause it to fail. Then your stuck in fastboot mode with a soft brick.
Sent from my DROID4 using Tapatalk

This is a really nice build! I am not at all sorry to have risked being stuck, to be honest.
Everything appears to work very well so far and I am posting from Chrome Beta.
Still looking for the downside...

Trying to get back to Stock - Rogers M7_ul

I could really use your help guys. I'm trying to get back to stock so I can get the updates being pushed by HTC/Rogers. There are a couple bugs that are really annoying me. So, before i tell you what I need, here's what I have.
M7_ul
Locked Bootloader - was relocked after unlocking a while ago
Rooted
CWM recovery
Stock HTC ROM
S-OFF
Baseband 4a.14.3250.14
Main 1.29.631.4
Modelid: PN0712000
CID: Roger001
Now, what I need is either the RUU or the stock recovery files and some sort of guide on how to install them. I've tried downloading from here: http://www.htcdev.com/devcenter/downloads/P60 but i can't flash it via CWM. I've also tried downloading and RUU from here: http://bugsylawson.com/files/file/1...5013-1033115001-release-312087-signed-2-4zip/ but when i unzip i get corrupt files and i can't move it to the phone.
I'm at a complete loss here. I would really appreciate any guidance you guys can provide. Any idea where I can get the proper RUU and how I can install it? Or if it's easier to just get the stock recovery, any idea where I can get it and how to install it using CWM or another method such as terminal emulator?

no need to relock bootloader is s-off'd
easiest way, IF there is an ruu or ruu zip for the rogers variant (you would need the ruu files that match 1.29.631.4) floating around i suggest this...back up sd card contents,boot into recovery...wipe the system,reboot into bootloader connect device via fastboot,run the ruu..one it boots except the ota
done

but how do i run the RUU and how do I know which exactly is the right RUU for me? I've heard RUUs are exe files but i haven't found any that are. The one I think is right for me is a zip and it seems to be corrupt though I dled the 1gb file twice. So i'm a bit confused.

vijn said:
but how do i run the RUU and how do I know which exactly is the right RUU for me? I've heard RUUs are exe files but i haven't found any that are. The one I think is right for me is a zip and it seems to be corrupt though I dled the 1gb file twice. So i'm a bit confused.
Click to expand...
Click to collapse
You can find the RUU you need here: http://forum.xda-developers.com/showthread.php?t=2207874
Hope to has been usefull

Thanks so much. But I'm still not sure which version to get. I tried the RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed.exe but no go. I get an error. Says it's the wrong ROM. Ugh. I've had no luck with this. So frustrating.
ImJacky said:
You can find the RUU you need here: http://forum.xda-developers.com/showthread.php?t=2207874
Hope to has been usefull
Click to expand...
Click to collapse

So, I've tried Rogers 1.29.631.4.zip which is an nandroid backup but no go on that either, using CWM. At a total loss here.

vijn said:
So, I've tried Rogers 1.29.631.4.zip which is an nandroid backup but no go on that either, using CWM. At a total loss here.
Click to expand...
Click to collapse
This is what I did and it worked like a charm... minus of course the issue after the software update which got fixed anyway.
http://forum.xda-developers.com/showthread.php?t=2357881

Ugh. Thanks cue_32. I had just downloaded that file when I saw your post, so I was very hopeful this would work. Pushed it to my phone, tried installing via CWM but almost immediately it said installation aborted. I have no idea what's going on. Nothing seems to be installable. WTF? And the link you posted for the stock recovery doesn't seem to lead to anywhere that has a recovery file for DL. So, I'm totally stuck now. UGH. Been on this for almost 2 days now. Haven't run into this much trouble with any of my previous phones, despite trying out almost a dozen different ROMs. Here, I'm just trying to revert to stock recovery and RUU and can't even do that. Sigh. I just don't get why none of the RUUs are installable.

vijn said:
Ugh. Thanks cue_32. I had just downloaded that file when I saw your post, so I was very hopeful this would work. Pushed it to my phone, tried installing via CWM but almost immediately it said installation aborted. I have no idea what's going on. Nothing seems to be installable. WTF? And the link you posted for the stock recovery doesn't seem to lead to anywhere that has a recovery file for DL. So, I'm totally stuck now. UGH. Been on this for almost 2 days now. Haven't run into this much trouble with any of my previous phones, despite trying out almost a dozen different ROMs. Here, I'm just trying to revert to stock recovery and RUU and can't even do that. Sigh. I just don't get why none of the RUUs are installable.
Click to expand...
Click to collapse
There's no RUU available yet for Rogers so I personally wouldn't try any other RUU.
So you downloaded the Nandroid backup from Whamboush (or whatever the name was), you extracted and moved the EXTRACTED FOLDER to the proper location (Clockwork>Backup) and updated the permissions correct? I used Root Browser to do this, the permission should be exactly like your other CWM backups. If I recall correctly there are 3 columns with 3 rows, all are X'd except for the last box on the 2nd column\3rd Row. (middle\bottom)
example:
X X X
X X X
X _ X
From there I just did the restore using the original clock work mod (non-touch cause I'm old skool)
After it successfully flashes, before it prompts you to reboot you'll be prompted to re-root from within CWM itself. Select No.
After it reboots, test to make sure everything is ok.
Then enter fastboot mode (adb reboot bootloader), from fastboot mode you can then flash the recovery.
You're welcome
---------- Post added at 11:29 PM ---------- Previous post was at 11:14 PM ----------
vijn said:
Ugh. Thanks cue_32. Here, I'm just trying to revert to stock recovery and RUU and can't even do that. Sigh. I just don't get why none of the RUUs are installable.
Click to expand...
Click to collapse
here's your stock recovery...I know how frustrating it can get so don't mind the step by step procedure.
http://d-h.st/dyr
You're welcome

well, cue_32 has give you the link to stock recovery..... what you can do is , flash the stock recovery first...try flashing the OTA......if still doesnt work..you can go for restoring the nandroid backup.....

mathrania said:
well, cue_32 has give you the link to stock recovery..... what you can do is , flash the stock recovery first...try flashing the OTA......if still doesnt work..you can go for restoring the nandroid backup.....
Click to expand...
Click to collapse
If I had the original nandroid, of the original Rom for example, would all that one needs to do is flash it and unroot and that's it?
Sent from my HTC One

chc31 said:
If I had the original nandroid, of the original Rom for example, would all that one needs to do is flash it and unroot and that's it?
Sent from my HTC One
Click to expand...
Click to collapse
Flash, unroot (if necessary) and flash stock recovery, which is what the instructions I provided, and optional lock the boot loader

So, I tried changing the permissions, which I hadn't done before, using Root Explorer but it says that some files can't be modified. So I can't set the permissions and CWM won't see those files at all, so that's not an option it seems. So I decided to just flash the recovery but when i do i get an error in adb Failed (remote: not allowed). So, that's not working either. Hehe. Every time I think i got it, something stands in the way. Will definitely feel like an accomplishment when i get this thing done finally, just not sure how or when it'll happen.
cue_32 said:
There's no RUU available yet for Rogers so I personally wouldn't try any other RUU.
So you downloaded the Nandroid backup from Whamboush (or whatever the name was), you extracted and moved the EXTRACTED FOLDER to the proper location (Clockwork>Backup) and updated the permissions correct? I used Root Browser to do this, the permission should be exactly like your other CWM backups. If I recall correctly there are 3 columns with 3 rows, all are X'd except for the last box on the 2nd column\3rd Row. (middle\bottom)
example:
X X X
X X X
X _ X
From there I just did the restore using the original clock work mod (non-touch cause I'm old skool)
After it successfully flashes, before it prompts you to reboot you'll be prompted to re-root from within CWM itself. Select No.
After it reboots, test to make sure everything is ok.
Then enter fastboot mode (adb reboot bootloader), from fastboot mode you can then flash the recovery.
You're welcome
---------- Post added at 11:29 PM ---------- Previous post was at 11:14 PM ----------
here's your stock recovery...I know how frustrating it can get so don't mind the step by step procedure.
http://d-h.st/dyr
You're welcome
Click to expand...
Click to collapse

Ya, I tried flashing the recovery, no go. No go on the nandroid backup either. The good thing is, i'm getting much more familiar with adb. Hehe.
mathrania said:
well, cue_32 has give you the link to stock recovery..... what you can do is , flash the stock recovery first...try flashing the OTA......if still doesnt work..you can go for restoring the nandroid backup.....
Click to expand...
Click to collapse

vijn said:
Ya, I tried flashing the recovery, no go. No go on the nandroid backup either. The good thing is, i'm getting much more familiar with adb. Hehe.
Click to expand...
Click to collapse
well, interested in another option.....i havent done this, but some people do...
change you CID to some device which has rcvd OTA, like mine is HTC_J15....just an example... now your mobile would be WWE internation blah blah... now grab the RUU.exe for it....backup all your data...and run it.....and then go for the OTA's ...in short the region of your device would be changed... you will have to find it in the forum itself... there are tutorials out there to do it...

Well, I'm leaving for the weekend, so I'll have to put this aside for now. In my research I had come across what you are suggesting but it seemed like more trouble and a little confusing so I opted against it, but maybe I'll have to revisit it when i get back. Hopefully you guys will still be around to provide some guidance. I do appreciate all your help. THanks again.
mathrania said:
well, interested in another option.....i havent done this, but some people do...
change you CID to some device which has rcvd OTA, like mine is HTC_J15....just an example... now your mobile would be WWE internation blah blah... now grab the RUU.exe for it....backup all your data...and run it.....and then go for the OTA's ...in short the region of your device would be changed... you will have to find it in the forum itself... there are tutorials out there to do it...
Click to expand...
Click to collapse

cue_32 said:
Flash, unroot (if necessary) and flash stock recovery, which is what the instructions I provided, and optional lock the boot loader
Click to expand...
Click to collapse
alrighty! ill keep that in mind, thinking of rooting! i had a htc sensation i bought online, if anything would happen to it i couldnt do anything about it, so i rooted and kept it like that. Now a Rogers One.. different lol. Thanks!

vijn said:
So, I tried changing the permissions, which I hadn't done before, using Root Explorer but it says that some files can't be modified. So I can't set the permissions and CWM won't see those files at all, so that's not an option it seems.
Click to expand...
Click to collapse
Just to be sure, the EXTRACTED FOLDER I'm referring to is the last folder before you see ALL the files of the 'ROM' like boot.img, cache.ext4.tar, recovery.img, etc...This folder is the one you want to make the permission changes to.
I had the exact same problem before and tried on ES File explorer, Astro File explorer, and Root browser (not root explorer although Im sure it works too). (I've never had to have this many installed at once) but basically this was the problem because after I extracted and updated the permission using Root browser, it worked on 1st try.
What I had done as well is make sure I was moving the extracted folder to the proper location by doing a nandroid back up first. From there I located the backup I just created and moved the extracted folder there. Once the extracted folder is in the right place, I went and used root browser and updated the permissions.

This totally worked Cue. Thank you so much. Finally managed to get the nandroid back up flashed, but then when I went to flash the recovery, i got an error: Failed (remote: not allowed). Ugh. So baby steps, but still in the right direction. So now my status is, Locked bootloader, s-off, flashed nandroid backup, but still have CWM recovery which I apparently can't seem to shake. Anyone know where I can maybe find a .zip recovery that I can try flashing via CWM? Not sure whether that's even possible, as CWM would essentially be overwriting itself but not sure what other options i have. From the research I've done so far though, it seems i can't flash a recovery with a locked bootloader. It does feel like i'm going around in circles here.
cue_32 said:
Just to be sure, the EXTRACTED FOLDER I'm referring to is the last folder before you see ALL the files of the 'ROM' like boot.img, cache.ext4.tar, recovery.img, etc...This folder is the one you want to make the permission changes to.
I had the exact same problem before and tried on ES File explorer, Astro File explorer, and Root browser (not root explorer although Im sure it works too). (I've never had to have this many installed at once) but basically this was the problem because after I extracted and updated the permission using Root browser, it worked on 1st try.
What I had done as well is make sure I was moving the extracted folder to the proper location by doing a nandroid back up first. From there I located the backup I just created and moved the extracted folder there. Once the extracted folder is in the right place, I went and used root browser and updated the permissions.
Click to expand...
Click to collapse

Do i really have to go through the entire unlock bootloader process to flash stock recovery? Ugh. I honestly don't get why this is so complicated. My previous phones were SOOO much simpler in comparison. This just feels like way too much trouble. I originally just wanted a rooted phone to get rid of bloatware and other small tweaks. I had no idea it would have such annoying consequences. Now, I'm just trying to get the stock ROM updated with HTC's latest bug fixes and software upgrade before i try and custom roms. I suspect it's not going to get easier though. I think once i get this finally done, i'm just going to leave the phone as is, completely stock at least until the 4.2.2 upgrade. Then after that I'll root it again. I used to love this process of rooting, installing custom roms, etc. Was fun, but this is just tedious as all hell. Hehe. Anyway, enough ranting. Ya, if anyone can tell me what my next step is, I'd be grateful.

[Q] Need Help Deciding What to do With Rooted Phone

So I just successfully rooted my lovely HTC One from Sprint. I've got TWRP 2.6.0.1 on it and all.
I'd REALLY like to get rid of all this garbage on my phone that I'm never going to use, however I also would like to keep it as close to stock as possible. I really enjoy Sense for the most part (minus quirks that I'm willing to live with, and BlinkFeed). I know how/can find out how to load a custom rom - I had CM7 on my HTC EVO 4G (1st Gen) and loved it. But I really don't want to be without Sense.
Can anyone make any suggestions as to what I should do/which rom I should use?

wolfbuck22 said:
So I just successfully rooted my lovely HTC One from Sprint. I've got TWRP 2.6.0.1 on it and all.
I'd REALLY like to get rid of all this garbage on my phone that I'm never going to use, however I also would like to keep it as close to stock as possible. I really enjoy Sense for the most part (minus quirks that I'm willing to live with, and BlinkFeed). I know how/can find out how to load a custom rom - I had CM7 on my HTC EVO 4G (1st Gen) and loved it. But I really don't want to be without Sense.
Can anyone make any suggestions as to what I should do/which rom I should use?
Click to expand...
Click to collapse
omj's stock rooted sounds like the rom for you

wranglerray said:
omj's stock rooted sounds like the rom for you
Click to expand...
Click to collapse
With a custom kernel. And greenify.
And a whole boat load of other mods you can only discover by spending time on these forums.

Stock with goodies
Sent from my One using XDA Premium 4 mobile app

wranglerray said:
omj's stock rooted sounds like the rom for you
Click to expand...
Click to collapse
Sorry, I'm overwhelmed at the wealth of knowledge here. Is there a link to the specific one you're talking about? Search didn't do me a ton of good. Though I suppose I could send the guy a message and inquire about his ROM.
Thank you for all your help guys!

Okay so I've decided that I want to try the OMJ ROM. Now here's where I am unsure of exactly how to do it. I see that certain ROMs require different methods. I can't just copy the ZIP to my internal storage and use TWRP to flash it, right? It has to be more complicated than that...
Also, I just went past the return window for the phone so I really cannot afford to brick it. I assume that there's next to no chance of the aforementioned tragedy befalling me providing I stick with the mainstream ROMs?

Most roms are in a flashable format i use the CM 10.2 nightly myself. from what i can tell as long as you can get into the bootloader your safe. I wiped my whole phone SD card and everything accidentally with TWRP one time. Ended up having to use sideload to get a CM rom installed again but i was never in danger of bricking. When flashing roms always remember to do a factory reset to wipe the cache and do an advanced wipe of the data and system. after the rom is installed it will ask you to wipe the cache again which is always nice to do.

cloppy said:
Most roms are in a flashable format i use the CM 10.2 nightly myself. from what i can tell as long as you can get into the bootloader your safe. I wiped my whole phone SD card and everything accidentally with TWRP one time. Ended up having to use sideload to get a CM rom installed again but i was never in danger of bricking. When flashing roms always remember to do a factory reset to wipe the cache and do an advanced wipe of the data and system. after the rom is installed it will ask you to wipe the cache again which is always nice to do.
Click to expand...
Click to collapse
Awesome! So what was I hearing about having to plug the phone into the computer to flash the boot.IMG file? Sorry, I'm just really overwhelmed with the new ways of doing things.

wolfbuck22 said:
Awesome! So what was I hearing about having to plug the phone into the computer to flash the boot.IMG file? Sorry, I'm just really overwhelmed with the new ways of doing things.
Click to expand...
Click to collapse
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.

cloppy said:
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.
Click to expand...
Click to collapse
Awesome! I guess it really is that easy! Thanks so much for all your help!

cloppy said:
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.
Click to expand...
Click to collapse
Alright, so I've got OMJ's rom running no problem. Love the new feel but what I'm wondering is...is there still a way to delete apps like Stocks and other crap I won't use? I can disable some but not all, and none am I able to uninstall completely.
Would it be something as simple as going into the OMJ ZIP file and removing the unwanted apk files and then re-flashing to that version?

wolfbuck22 said:
Alright, so I've got OMJ's rom running no problem. Love the new feel but what I'm wondering is...is there still a way to delete apps like Stocks and other crap I won't use? I can disable some but not all, and none am I able to uninstall completely.
Would it be something as simple as going into the OMJ ZIP file and removing the unwanted apk files and then re-flashing to that version?
Click to expand...
Click to collapse
I suppose that could be one way of doing it, but i dont think its necessary. if you are already rooted or can install root easy i would just install a Root file explorer. Browse to the /system/app folder i think it is and delete the APKs from there.

cloppy said:
I suppose that could be one way of doing it, but i dont think its necessary. if you are already rooted or can install root easy i would just install a Root file explorer. Browse to the /system/app folder i think it is and delete the APKs from there.
Click to expand...
Click to collapse
Yeah I tried that with ES explorer AND Root File Manager. ES would have an error, and Root File Manager would simply say it was deleted but it was never actually deleted. I think it has something to do with the security. I'm not really sure, haha! I'm used to being able to just openly delete apps from within Settings>Apps like the old days of my EVO 1st gen.

hmm interesting as long as the /system is mounted as r/w permissions you should be able to delete. well if you are planning on reflashing using the modify zip method im curious to know if that works.

wolfbuck22 said:
Yeah I tried that with ES explorer AND Root File Manager. ES would have an error, and Root File Manager would simply say it was deleted but it was never actually deleted. I think it has something to do with the security. I'm not really sure, haha! I'm used to being able to just openly delete apps from within Settings>Apps like the old days of my EVO 1st gen.
Click to expand...
Click to collapse
use Root explorer, and set it at r/w
also Titanium Backup will delete it for you too.

If I remember correctly there are a few apps in the play store that are specifically for getting rid of "bloatware".....maybe search bloatware removal, our uninstall bloatware something like that. Hopefully this helps!
Sent from my HTCONE using xda premium

Aldo101t said:
use Root explorer, and set it at r/w
also Titanium Backup will delete it for you too.
Click to expand...
Click to collapse
Well for whatever reason neither of those two suggestions worked. So I installed Root Browser and was finally able to get rid of some things.
Scratch that. Rebooted phone and the apps are back.

wolfbuck22 said:
Well for whatever reason neither of those two suggestions worked. So I installed Root Browser and was finally able to get rid of some things.
Scratch that. Rebooted phone and the apps are back.
Click to expand...
Click to collapse
ROMCleaner

bigdaddy619 said:
ROMCleaner
Click to expand...
Click to collapse
Thanks! I'm working on it now. I did not see an app called "ROM Cleaner" or "ROMCleaner" but I did find something called Rom Toolbox Lite that I'm going to attempt to use.
Will post back. I may look for the ROMCleaner on the net and just install it manually.
Edit: So I guess I showed my ignorance there. It appears ROM Cleaner is something offered through the forum. I'm unsure of how to use it so I'll take a look around.

wolfbuck22 said:
Thanks! I'm working on it now. I did not see an app called "ROM Cleaner" or "ROMCleaner" but I did find something called Rom Toolbox Lite that I'm going to attempt to use.
Will post back. I may look for the ROMCleaner on the net and just install it manually.
Edit: So I guess I showed my ignorance there. It appears ROM Cleaner is something offered through the forum. I'm unsure of how to use it so I'll take a look around.
Click to expand...
Click to collapse
ROMCleaner
It's very doubtful you will have success with Romtoolbox either once you reboot all the apps will return