yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] mrcaligula:
Thanks for Your help !! ;)
[One (M7) Android Development] mike1986.:
What's wrong with this guide that someone is sill rating it with 1 star? Just asking, let me know and I will do corrections if needed.
[One (M7) Android Development] ipmanwck:
Hi Mike, hope i can help here. Firtsly your work is superb.

Being a sammy user i am very happy rooting and flashing sammy phones. Never had any issue.

Since having htc one i tried every guide and came here as your reputation is good :)

Petsonally i found your instructions were not detailed enough and lacked some info. Example - i tried to flash recovery in command prompt but failed everytime until a user told me windows hides the full file name ??? I didnt know this.

So to make this clear the file name you see in c: is not the full file name. I had to right click on recovery file then properties and then details. It was only then i saw file name was different.

Hope this helps.
[One (M7) Android Development] langer hans:
I think a note that the new hboot doesn't allow fastboot boot *.img would be good. Saw a lot of questions about that lately.

Gesendet von meinem GT-N5100 mit Tapatalk 4
[One (M7) Android Development] mike1986.:
Done :)
[One (M7) Android Development] descenpet:
that's more of windows/user issue rather than htc specific. no? unless all other phones doesn't use things with .img extension. :rolleyes:
[One (M7) Android Development] ipmanwck:
Dude i am just trying to answer a question op asked. Cut me some slack. Not all of us are windows experts.
[One (M7) Android Development] mike1986.:
I agree, however I can't predict everyone skills here. This way I would have to start the guide by explaining how to turn ON the computer, how to log in into Windows, what it commands shell etc. etc.

I assume users rooting their device already have some common and basic knowledge. But thanks for the tip anyway, appreciated :)
[One (M7) Android Development] pritam.paul.360:
"fastboot boot recovery.img" command doesn't work anymore

so, I've updated to 2.24.401.8 today through OTA and I'd like to flash CWM recovery and ElementalX kernel. but first, I'd like to backup my current STOCK Recovery so that I can get back to "completely stock" anytime I want to. but when I try to BOOT the CWM recovery through command prompt in order to backup my stock recovery, my bootloader menu just freezes and nothing happens after that! this process used to work for the previous versions of hboot but doesn't work anymore. my hboot version is 1.54.0000. Is there any other way to backup my stock recovery before flashing a custom one?

thanks......
[One (M7) Android Development] descenpet:
You can't really back up recovery as you are now. but you can easily get a copy out of ota zips available on these forums so don't worry about it.
[One (M7) Android Development] pritam.paul.360:
right, that's the plan then. searching for the ota.zip right

away! :cool:
[One (M7) Android Development] crazyg0od33:
you think this'll work on vzw tomorrow?
[One (M7) Android Development] moosc:
I hope so, I'm heading to VZW at noon and picking a ONE up. Like to at least root before I activate my one.

Sent from my Nexus 4 using Xparent Cyan Tapatalk 2
[One (M7) Android Development] crazyg0od33:
yeah I'm trying to at least root before I set up the phone so that I dont really wipe anything big
[One (M7) Android Development] paul_59:
Does anyone know where I can find rooting tools ?

The link

http://goo.gl/J3zJv

( http://xda4.androidrevolution.nl/db...ns/Android_Revolution_HD_Root_and_BusyBox.zip)

doesn't currently work.
[One (M7) Android Development] descenpet:
try changing the number to something like xda2 or xda7.

anything linking to xda4 mirror is not working for some time. [MENTION=1631739]mike1986.[/MENTION] need to update the links :p
[One (M7) Android Development] moosc:
Sounds like root method is broken. But going to HTC Dev we can unlock the bootloader currently

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
[One (M7) Android Development] paul_59:
Thanks for your reply.

After posting I remembered that CWM will offer to flash Supersu (?) to obtain root
[One (M7) Android Development] Marco.t...:
Deleted
[One (M7) Android Development] b00f13:
Do the nandroid backups contain an hboot? Can I restore a nandroid backup and be done with it or must I first flash 1.44 hboot before running the backup?
[One (M7) Android Development] descenpet:
nandroid doesn't contain hboot. what is your 2nd question even supposed to mean? doesn't make sense at all :confused:
[One (M7) Android Development] b00f13:
My bad I thought I worded that right haha. What I'm asking is if I want to go back to stock by way of Nandroid backup, do I need to downgrade my hboot as well? I want to go back to 1.29 firmware. I currently have 1.54 hboot. Do I need to flash 1.44 hboot before I run the nandroid?
[One (M7) Android Development] descenpet:
nandroid doesn't include any firmware. it only backup boot system and data in most cases. you can flash older firmware manually if you are s-off.

why would you want to go back to 1.29? :confused:
[One (M7) Android Development] b00f13:
Phones acting a bit odd I kinda want to reset it back to complete stock and work my way back to my current setup cleanly. The nandroid I'm using to restore with is from Bugsy's RUU page.

http://xdaforums.com/showthread.php?t=2207874

Those nandroids were made running the older firmware I want back.
[One (M7) Android Development] descenpet:
real RUUs are one thing but usually nandroids won't solve weird issues that can't be solved by full wipe. in any case, if you are restoring 1.29 nandroid, make sure you flash 1.29 firmwares too or touch won't work. assuming you are s-off that is.
[One (M7) Android Development] b00f13:
I can't find 1.29 firmwares for my phone that's why I want to run the nandroid to get them back :p
[One (M7) Android Development] descenpet:
ok looks like there is abit if misunderstanding here. by firmware, i meant hboot and accompanying stuff, that is 1.44 hboot and other firmware images, not rom itself. nandroid doesn't backup those and old nandroid won't work properly without those.
[One (M7) Android Development] b00f13:
Ahhh thank you for answering my question. I guess I can't go back to stock firmware then. There are no RUU's available from my carrier in the list. But thanks for the information!
[One (M7) Android Development] descenpet:
anyway, what is this strange issue you speak of? and are you s-off? if you are, you can try to use any RUU and see if helps. it might help with some general issues. but if your problem is carrier specific, that won't do.
[One (M7) Android Development] b00f13:
I don't know it just doesn't feel as fast. I can see some micro lag when scrolling through the launcher when the apps settle back into place. And some lag here and there. I thought it was the ROM but I've tried GPE, Sense and AOSP. It persists. The only static element common between each set up I've run was the firmware. So I thought maybe downgrading then upgrading would work.

I'm S-OFF with SuperCID.

By the way, can you jump between firmwares? I used to be on 2.24.401.1, upgraded to 3.06.1700.10 then downgraded back to 2.24.401.8. Can you do that? It all seemed too easy lol. I would think I'd have run into a problem by now but I haven't.
[One (M7) Android Development] descenpet:
if you are getting lag all over the places on different roms even with full wipe, i don't think downgrading is gonna help. if you think downgrading would help, you can try any ruu if you are s-off anyway. it doesn't necessarily need to be your stock. it is also possible that you are imagining :p in that kind of situation, the word "lag" is kinda subjective.
[One (M7) Android Development] ipmanwck:
Dam. I want latest firmware but have to go back to stock. I am on UK t-mobile ONE. Any ideas if I can get OTA yet.
[One (M7) Android Development] pritam.paul.360:
u can get the 2.24.401.8 update through ota right now if u have s-off! just change ur cidnumber to HTC__203 and check for updates again! :)
[One (M7) Android Development] ipmanwck:
It's a buggy I am hboot 154 and s on. No way out ...arghhhhh
[One (M7) Android Development] Marco.t...:
deleted
[One (M7) Android Development] tshmit1:
In the "Going Back to Stock" section of the original post it says:

"Your bootloader will never be "LOCKED" again. You can't restore it. You can only relock it"

I don't understand what that means. Can anyone explain?
[One (M7) Android Development] angusc:
It means that after you have used HTC DEV to unlock that when you relock your bootloader it will never say "locked"like it did out of the box new. It will say "Relocked".

However I think that was written before revone came out, so if you have HBOOT 1.44 then you can make it say locked by running a revone command.

Sent with desire from My One
[One (M7) Android Development] kami2k:
Great thanks.................
[One (M7) Android Development] Rehnbergz:
Is there a way to make a nandroid backup before unlocking the bootloader?
[One (M7) Android Development] langer hans:
No. Nandroids are made in recovery (except online-nandroids, but you'd need root). Recovery is only flashable after HTC Dev unlock or S-OFF (which also needs root :D)
[One (M7) Android Development] Rehnbergz:
Hmm... well, I figured so. Then there really is no way to get the bootloader "locked" instead of "relocked", I guess, well at least if you're on 1.54. Thats a bummer. :D

Though actually, you said that you only need root acces to perform a online-nandroid. Would that be possible to do? :confused:

But then I would need a custom recovery, anyways, I guess. Hmmm.... :rolleyes:
[One (M7) Android Development] langer hans:
You guessed correct :(
[One (M7) Android Development] Seahorse:
Cancel.
[One (M7) Android Development] Rehnbergz:
Well, then we play the waiting game.

As we're already discussing this, it will be possible to lock the bootloader (once someone figures out a method, like revone, for 1.54) if you use HTC DEV. And therefore be able to use your warranty etc, right? :)
[One (M7) Android Development] langer hans:
Correct. With S-OFF you can lock your device again.
[One (M7) Android Development] Rehnbergz:
Cool. Then I'll probably root it in the weekend, or today. It is actually a shame that i haven't already ;)
[One (M7) Android Development] assasin34:
hi guys,

my device was 2.24.401.9 before i have unlocked bootloader and flashed custom rom.and now i wanna turn to stock rom.can i flash previous ruu or do i have to flash 2.24.401.09 ruu which is already nowehere:)???
[One (M7) Android Development] assasin34:
we have to be s-off to turn to previous version of stock rom?
[One (M7) Android Development] DominMc:
The Rooting Tools Link don't work... :(
[One (M7) Android Development] deboopi2:
Going back to stock – what about firmware and recovery.

Well, I’m currently at Elegancia 13 running on 3.17 firmware.

Further on I will explain what problems are causing me to revert to stock 4.2.2 based on 2.24 firmware.

Searching on the web taught me I have to relock the bootloader and run a RUU that will install a stock version.

I was searching for a RUU exe and since I live in Belgium (Europe) I have the choice between

RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe

And

OTA_M7_UL_JB_50_HTC_Europe_1.29.401.12-1.28.401.7_release_315849_signedp7vl8dqsvls0h1t0.zip

The first one is the complete exe and the second a smaller zio.

As far as I know it’s easier to start with the executable, so that’s what I want to do and then upgrade to JB 4.2.2 base 2.24 on the official way.

But since I’m running on a custom rom and with firmware 3.17 and a TWRP as recovery image I have the following questions

What’s included in the RUU exe, is it only the rom or also the rom and the firmware and the recovery image.

If it’s not all in there how to proceed?

If it’s in there will I succeed since I’m running on a newer firmware and I thought downgrading the firmware with

the RUU is impossible. Do I need to install a lower firmware myself and how to knw which one matches the RUU?

And all in all proceeding this way is this the best to get back to stock?

So I know where to find a RUU but I’m not sure if I have all to proceed.

The reason why I want to go back to stock are signal problems.

I missed calls in the car because the signal went down to zero.

I monitored this through the Bluetooth carkit

Waking up the phone on such a moment made the signal a lot better.

First off all it was caused by my car because in the car of my wife I had a better reception.

Mine has a Bluetooth kit (probably without connection to the external antenna), my wife’s car also has a Bluetooth kit but with an external antenna .

But even now in the house or in the pub sometimes I have a signal from 5 bars and waking uo the phone it goes down to 3, sometimes the other way round.

Nothing to do with Bluetooth but visible immediate after waking up the phone you can see the signal going up or going down.

So first of all I want to go back to stock and see what happens at a stock 4.2.2.
[One (M7) Android Development] ClydeB1:
The RUU has the complete set of files, it will reflash to complete stock including system, recovery and boot images. As long as you are S-Off you can flash the RUU to revert to an earlier hboot version.
[One (M7) Android Development] deboopi2:
So

relock the bootloader

exe the ruu europe 1.28.exe

update to 4.2.2 the official way with update from htc

am I still s-off thereafter?

unlock the bootloader

root again with superuser or supersu

Is this correct, and then see what happens with the signal and if still problems go back to the shop?
[One (M7) Android Development] fridgeman:
As far as I'm aware you don't need to relock the bootloader if your s-off. I've gone back to stock twice and never had to.
[One (M7) Android Development] ClydeB1:
You can try without relocking the bootloader first. I haven't tried it myself on the One with S-Off so I can't confirm. Flashing the RUU won't remove S-Off. Also I'd try the signal before flashing a custom recovery and rooting again as it will be a few less steps if you do still have problems and need to return the device.
[One (M7) Android Development] deboopi2:
Ok thanks, but one question remains, isn't it possible to root without installing a custom rom, isn't it enough to have s-off and an unlocked phone?
[One (M7) Android Development] descenpet:
it is possible to just root stock rom if that is what you are asking.

but there is not much benefit in that so most people who rooted their devices go for custom roms.
[One (M7) Android Development] bobsie41:
Yes, there is no need to relock the bootloader.
[One (M7) Android Development] deboopi2:
That's correct but then I can still use some applications requiring root access, e.g. Titanium Backup, ES File explorer, etcetera

And I can stay on stock until I know is there's something wrong with my phone without loosing too many useful apps even though I have not the modifications of the custom roms.
[One (M7) Android Development] ClydeB1:
Yes it is. The point I was making is that as you wanted to test your signal you can do that relatively quickly without rooting and if the signal is still poor, return your phone under warranty. If the signal is fine then root it and use it, with your useful apps and either stock or custom rom.
[One (M7) Android Development] deboopi2:
That's correct.

After dinner I'm gonna start the ruu and see where it gets me.

I started noticing the problems the last 5 to 6 weeks, it's about 2 months ago I switched the SIM card again, going from private to company subscription, could the sim card be the culprit?

If problems remain after going to stock this might be a faster way it there is a fair chance it is the sim, a sim swap s a lot faster than bringing the phone to the shop.

So first a sim swap or bringing it back to the store, what should I do?

---------- Post added at 07:07 PM ---------- Previous post was at 06:20 PM ----------

Running RUU for going back to stock does not work.

I executed RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe

but I got an 155 Error, image update error.

Going to the OP and searching the web learned me to relock my bootloader, so I did.

But I still get the same error.

Searching again on the web comes up with

flash the boot.img first

flashing the wrong RUU

If it is one, where to find the boot.img.

If it is 2, how to know I'm on the correct RUU.

The only thing I know to compare is the CID.

Mine is HTC__E11

Hboot is 1.55.0000

First line in bootloader = M7_UL PVT SHIP S-OFF RH

or M7_UL PUT SHIP S-OFF RH

Anybody can help?
[One (M7) Android Development] ClydeB1:
Try booting the phone to bootloader screen before running the RUU. The boot.img is included in the RUU. If that still doesn't work then try flashing an earlier version of firmware to downgrade your hboot and then rerun the RUU.
[One (M7) Android Development] Dic3ptor:
Hi all.

Is it possible to s off the one with hboot 1.54 now or I have to wait?

Sent from my HTC One.
[One (M7) Android Development] deboopi2:
Got your message too late to try it out, will be for this evening.

What about the sim, could this have something to do with signal problems?
[One (M7) Android Development] vizzy:
Stock recovery won't work with flashing root etc. You need custom.

Samsung unlocking process is a lot different (and easier), so try not to compare the two.
[One (M7) Android Development] Sango2:
Thank, understand it now. I heard HTC is more strict but was not aware of the extent.

I'll go ahead and go custom rom. I guess there isn't away of getting away of the "TAMPERED" without S-OFF. It was one the reasons why I was thinking I could try to root it from stock recovery like how I done it with Samsung.
[One (M7) Android Development] japjit100:
hi guys my friend have htc one I m also planning to buy htc one

now my question is he rooted but now he having problem of dead pixel

relock boot loader and un root htc one

in recovery show boot loader relock not locked now what to do

I used Samsung phone I m new in htc phones:o
[One (M7) Android Development] langer hans:
This is normal. Bootloader can be relocked, but not factory locked again. If you have everything back to stock and relocked you are okay to send it in for repair. I guess they won't bother with bootlader if you have a dead pixel.

Gesendet von meinem Nokia 3310 via SMS
[One (M7) Android Development] jntdroid:
EDIT: Somehow I missed those instructions in the (fastboot boot recovery recovery.img vs. fastboot flash recovery recovery.img). So ignore my question... learned something new... :)

Maybe a dumb question, but in Method 3 of the "Return to stock" section, it says you can nandroid backup without "permanently" flashing a custom recovery. Then the nandroid backs up the STOCK recovery .img and you can pull it from the Nandroid. I'm on T-Mobile USA, and since we don't have an RUU, I would love to get that stock recovery .img file saved / backed up.

Now comes the dumb question... how do you nandroid without a custom recovery permanently flashed, or at least in a way that the nandroid will grab the stock recovery?

TIA...
[One (M7) Android Development] jntdroid:
Second dumb question.. how do you pull the recovery.img file from the nandroid? I used TWRP, trying to open archives with 7zip at the moment.
[One (M7) Android Development] JoeNeckbone:
Maybe I'm wrong but the command "fastboot boot recovery.img" is just running the recovery file without overwriting the stock recovery in phone.
[One (M7) Android Development] ApexPredation:
I'm unlocked and rooted, Hulu plus works perfectly for me.
[One (M7) Android Development] XClemX:
OK, i have a small problem..

i have unlocked the bootloader, loading a CWM touch recovery, and rooted the device with mini-sdk but in HBOOT i cannot get into recovery to do anything...

i can if i use mini sdk and reflash the recovery and then i am away, but i can't from inside the phone itself.

i have erased the cache, i have changed CWM to non touch but nothing.

i have tried with rom manager to get root but the app tells me i don't have root access but i have

UNLOCKED and TAMPERED on the HBOOT screen.

any help?

i am sure i could chuck another rom on and it would work but i want to make sure i have root access and it's accessible via HBOOT.
[One (M7) Android Development] lilvfr400boy:
Iv tried unrooting like I had done on every other of my 20 android phones I.e. es explorer searching all su and superuser apk files deleting them but nothing stops it being there again after reboot? I do not want to have to install all of my apps etc again for the 20th time if I can help it, anyone point me how to ? P s. Iv also tried the terminal emulator way. I'm using koush su please help me rid my device of koush root it's never endingly there
[One (M7) Android Development] mike1986.:
It's system RW protection inside kernel. You must remove it from inside recovery.
[One (M7) Android Development] lilvfr400boy:
How do I remove it in recovery iv never had to do this before I'm clueless about it
[One (M7) Android Development] mike1986.:
adb shell

sysrw

rm /system/app/SuperUser.apk

rm system/xbin/su

exit
[One (M7) Android Development] jntdroid:
Thanks - yeah I missed that part of the instructions the first time around. Now I'm trying to find info on how to pull the actual .img file for stock recovery from the recovery.emmc.win file.
[One (M7) Android Development] giorgit28:
If i do S-off ,

will it reset the phone to factory default and wipes all data and i have to configure everything from the beginning?
[One (M7) Android Development] langer hans:
As we don't have s-off yet, no one knows. It depends on the used method to gain s-off...

Gesendet von meinem Nokia 3310 via SMS
[One (M7) Android Development] giorgit28:
Can I root the phone without S-off?
[One (M7) Android Development] mike1986.:
Sure.
[One (M7) Android Development] giorgit28:
Can you please link me some guide for rooting without S-Off.
[One (M7) Android Development] langer hans:
It is in the very first post of this thread...

Gesendet von meinem Nokia 3310 via SMS
[One (M7) Android Development] ClydeB1:
Not yet, you'll have to wait for now. How've you been bro? :cool:

Not sure. Have you got another sim to try?
[One (M7) Android Development] deboopi2:
No I should swap it in the shop, the One is a microsim, the one from my wife and my daughter are mini-sims.
[One (M7) Android Development] ClydeB1:
It's worth a try
[One (M7) Android Development] deboopi2:
I've been looking a bit further for this error message, maybe answers are a bit old but the conclusion seems to be that downgrading the firmware is the problem.

So I need to find a firmware matching the RUU or being older than the RUU.

So I guess I have to look for firmware 1.28 or older but I haven't got a clue where to find this.

In the threads where people are making custom roms you can find 2.24 firmwares and also 3.09 and 3.17.

Can anybody point me in the right direction for 1.28 or older and confirm that I'm on the right way then.

Over here it was mentioned relock wasn't necessary, the same for downgrading but reading other messages I start doubting this.

So who can tell me the correct way to go so I can go back to stock?

I really need it
[One (M7) Android Development] ClydeB1:
Did you try running the RUU with the phone in bootloader mode? This is often a way of getting around the error 155 message. Running the RUU should change the firmware as well as and with S-Off you shouldn't need to relock the bootloader. I have the 1.29.401.12 firmware, let me know if you want to give it a try and I can upload it for you.