Database Develop

Downgrading from 4.3 to 4.2.2 using RUU.

בס"ד
So now I'm on :
Bootloader *Locked*
Android 4.3 Google Edition - RUU : http://forum.xda-developers.com/showthread.php?t=2358781
system vers: 3.07.1700.1
Cid: HTC__K18
Mid: PN0711000
And I'm willing to flash Sense 5 - 2.24.401.9 - 4.2.2 RUU. ------- which only workes with my current Cid and Mid.
Would it go smooth? I'm going from 4.3 to 4.2.2... (I'm also asking about the downgrade, but generally on the whole procces..)
Thanks

...

Please post a fastboot getvar all removing s/n abd imei
Are you s-off

stovie_steve said:
Please post a fastboot getvar all removing s/n abd imei
Are you s-off
Click to expand...
Click to collapse
What?
Yes I'm S-Off.

TunneIVision said:
What?
Yes I'm S-Off.
Click to expand...
Click to collapse
Hi @TunneIVision, you mean this thread??
Please post a "fastboot getvar all", ie boot into bootloader/FASTBOOT USB, open a command prompt, go to your adb folder, and type "fastboot getvar all", copy/paste the output here (remove IMEI and s/n)

nkk71 said:
Hi @TunneIVision, you mean this thread??
Please post a "fastboot getvar all", ie boot into bootloader/FASTBOOT USB, open a command prompt, go to your adb folder, and type "fastboot getvar all", copy/paste the output here (remove IMEI and s/n)
Click to expand...
Click to collapse
Yea it is man
Got it. Just need to delete "s/n" . What is it? serialno?

TunneIVision said:
Got it. Just need to delete "s/n" . What is it? serialno?
Click to expand...
Click to collapse
yes serialno. we don't need to see your IMEI and serialno

nkk71 said:
yes serialno. we don't need to see your IMEI and serialno
Click to expand...
Click to collapse
Thanks man , I really appreciate it
C:\Users\user>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3817mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s

TunneIVision said:
בס"ד
So now I'm on :
Bootloader *Locked*
Android 4.3 Google Edition - RUU : http://forum.xda-developers.com/showthread.php?t=2358781
system vers: 3.07.1700.1
Cid: HTC__K18
Mid: PN0711000
And I'm willing to flash Sense 5 - 2.24.401.9 - 4.2.2 RUU. ------- which only workes with my current Cid and Mid.
Would it go smooth? I'm going from 4.3 to 4.2.2... (I'm also asking about the downgrade, but generally on the whole procces..)
Thanks
Click to expand...
Click to collapse
TunneIVision said:
Thanks man , I really appreciate it
C:\Users\user>fastboot getvar all
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
Click to expand...
Click to collapse
S-Off :good::good: do not change that
So you want to go back to a Sense 5 or Sense 5.5 ROM, am I understanding correctly? any one in particular? (link?)
Hit the thanks button once in a while if I've helped

nkk71 said:
S-Off :good::good: do not change that
So you want to go back to a Sense 5 or Sense 5.5 ROM, am I understanding correctly? any one in particular? (link?)
Hit the thanks button once in a while if I've helped
Click to expand...
Click to collapse
Be sure that I **it him more then once before
As I said
Sense 5
2.24.401.9 - System vers
4.2.2
RUU

TunneIVision said:
Be sure that I **it him more then once before
Click to expand...
Click to collapse
You got your first one too :laugh: (anyway no need to hit each and every one, just the ones you find useful, I hope they all are )
TunneIVision said:
As I said
Sense 5
2.24.401.9 - System vers
4.2.2
RUU
Click to expand...
Click to collapse
Don't think there's an RUU for you, can you read through this: http://forum.xda-developers.com/showthread.php?t=2519672 and see if it helps, otherwise let me know. I'll be on my laptop for a couple more hours
EDIT: do you have a nandroid backup by any chance?

nkk71 said:
You got your first one too :laugh: (anyway no need to hit each and every one, just the ones you find useful, I hope they all are )
Don't think there's an RUU for you, can you read through this: http://forum.xda-developers.com/showthread.php?t=2519672 and see if it helps, otherwise let me know. I'll be on my laptop for a couple more hours
EDIT: do you have a nandroid backup by any chance?
Click to expand...
Click to collapse
I got this RUU after alot of searching.
So.. will it work?

TunneIVision said:
I got this RUU after alot of searching.
So.. will it work?
Click to expand...
Click to collapse
didnt see the link can you post it again (and any details of it)

nkk71 said:
didnt see the link can you post it again (and any details of it)
Click to expand...
Click to collapse
Let my corrent myself.
My carrier agreed to run this 2.24.401.9 - 4.2.2 RUU .
"after alot of searching"
So?

TunneIVision said:
Let my corrent myself.
My carrier agreed to run this 2.24.401.9 - 4.2.2 RUU .
"after alot of searching"
So?
Click to expand...
Click to collapse
OK I understand
wish it could be shared though
Anyway, yes with s-off you can run a downgrade RUU, it will fully restore your phone to previous condition, you will keep S-Off, it won't change (a good thing)
I saw you are already LOCKED (not relocked) and have you removed TAMPERED? If LOCKED, no TAMPERED, go ahead and run the RUU. should you receive an error 155 (I think) while running the RUU, then you may need to downgrade hboot.
Go ahead an run it, and let me know if all good

nkk71 said:
OK I understand
wish it could be shared though
Anyway, yes with s-off you can run a downgrade RUU, it will fully restore your phone to previous condition, you will keep S-Off, it won't change (a good thing)
I saw you are already LOCKED (not relocked) and have you removed TAMPERED? If LOCKED, no TAMPERED, go ahead and run the RUU. should you receive an error 155 (I think) while running the RUU, then you may need to downgrade hboot.
Go ahead an run it, and let me know if all good
Click to expand...
Click to collapse
What do you mean error 155 ?
Both , my phone in it current condition and the 2.24.401.9 RUU use same Hboot 1.54.

TunneIVision said:
What do you mean error 155 ?
Both , my phone in it current condition and the 2.24.401.9 RUU use same Hboot 1.54.
Click to expand...
Click to collapse
Sorry, didn't explain, sometimes (usually hboot 1.55) when running a RUU it gives an error 155 (on the PC), that would need to first flash an older hboot to get the RUU to work.
So everything good now

nkk71 said:
Sorry, didn't explain, sometimes (usually hboot 1.55) when running a RUU it gives an error 155 (on the PC), that would need to first flash an older hboot to get the RUU to work.
So everything good now
Click to expand...
Click to collapse
Thanks man. They should call me sometimes this week , I'll let you know if it worked

nkk71 said:
Sorry, didn't explain, sometimes (usually hboot 1.55) when running a RUU it gives an error 155 (on the PC), that would need to first flash an older hboot to get the RUU to work.
So everything good now
Click to expand...
Click to collapse
בס"ד
Yayayayayayayayay !!!!!
Now im on 2.24.401.9 !
whooooooooooooooooooooooooooo !!!
You are the BEST !!!!
thank you so much man !!
You were so patiente with me !!!
I dont need my carrier anymore !
How can I repay you?
I LOVE YOU !!!
If I will root it i wont get OTA? I would like to root and lock the bootloader without custom recovery..

TunneIVision said:
בס"ד
Yayayayayayayayay !!!!!
Now im on 2.24.401.9 !
whooooooooooooooooooooooooooo !!!
You are the BEST !!!!
thank you so much man !!
You were so patiente with me !!!
I dont need my carrier anymore !
How can I repay you?
I LOVE YOU !!!
If I will root it i wont get OTA? I would like to root and lock the bootloader without custom recovery..
Click to expand...
Click to collapse
So all good now?
As for root, as far as I know, it won't affect OTAs, and you can also keep bootloader unlocked, doesnt affect OTAs. But definitely keep S-Off in case you wanna change something later on.

[Q] New HTC One - S-OFF!!

Hi,
My friend purchased a new HTC One and it gave the following information on bootloader. I was surprised to see its S-OFF by default.
M7_UL PVT ship S-Off RH
CID - 111111111
HBOOT-1.54.0000
radio-4a.18.3250.15
open dsp - v31.120.274.0617
os-2.24.708.4
eMMC-boot 2048MB
and Build No is : 2.24.708.4 cl2111355 htc build
Can anyone please tell me if this is a debranded phone or anything.
If this is kept, would there be any issues for flashing custom ROMs? Like after S-off and Unlocked Bootloader. Would it still restrict that I would be able to flash only certain ROMs on it..
Please tell asap

Rah0ol said:
Hi,
My friend purchased a new HTC One and it gave the following information on bootloader. I was surprised to see its S-OFF by default.
M7_UL PVT ship S-Off RH
CID - 111111111
HBOOT-1.54.0000
radio-4a.18.3250.15
open dsp - v31.120.274.0617
os-2.24.708.4
eMMC-boot 2048MB
and Build No is : 2.24.708.4 cl2111355 htc build
Can anyone please tell me if this is a debranded phone or anything.
If this is kept, would there be any issues for flashing custom ROMs? Like after S-off and Unlocked Bootloader. Would it still restrict that I would be able to flash only certain ROMs on it..
Please tell asap
Click to expand...
Click to collapse
i think that this phone is regenerated or phone test! You do not have any problem to flash rom! the s-off is the best thing for our phones! where did you buy it?

mago988 said:
i think that this phone is regenerated or phone test! You do not have any problem to flash rom! the s-off is the best thing for our phones! where did you buy it?
Click to expand...
Click to collapse
He he .. Its from eBay from a known seller The Mobile is S-off and SID is 111111 .. That means I can flash any RUU Right? or Unlock bootloader is mandetory?

Yes
Sent from my HTC One using xda premium

Rah0ol said:
He he .. Its from eBay from a known seller The Mobile is S-off and SID is 111111 .. That means I can flash any RUU Right? or Unlock bootloader is mandetory?
Click to expand...
Click to collapse
If your phone is S-OFF you can flash a ruu with a locked/unlocked/relocked bootloader, with s-on you need a LOCKED bootloader to flash a ruu.
You can flash any ruu that match you CID (not a problem with supercid) and MID (MID can be changed easily with s-off).
Don't forget you will not receive ota updates with super cid.

alray said:
If your phone is S-OFF you can flash a ruu with a locked/unlocked/relocked bootloader, with s-on you need a LOCKED bootloader to flash a ruu.
You can flash any ruu that match you CID (not a problem with supercid) and MID (MID can be changed easily with s-off).
Don't forget you will not receive ota updates with super cid.
Click to expand...
Click to collapse
So as u said, I have a SuperCID and a locked bootloader and S-OFF, I can flash any RUU (international, anything coz I wanna flash Indian RUU or atleast International) so will it work fine without bootloop etc?? ??

Rah0ol said:
So as u said, I have a SuperCID and a locked bootloader and S-OFF, I can flash any RUU (international, anything coz I wanna flash Indian RUU or atleast International) so will it work fine without bootloop etc?? ??
Click to expand...
Click to collapse
MID must match too
better to post a ''fastboot getvar all'' except imei/sn so we can tell if you can flash that ruu
also post a link to the ruu you want to flash.

and you can always pull mmcblk0p6 to find the true origins of your phone

nkk71 said:
and you can always pull mmcblk0p6 to find the true origins of your phone
Click to expand...
Click to collapse
How to do that? I dont know about that

Rah0ol said:
How to do that? I dont know about that
Click to expand...
Click to collapse
you need a custom recovery, or a rooted ROM, do you have that?
then you open a shell and dd it out, for example:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bak.img
exit
exit
adb pull /sdcard/mmcblk0p6_bak.img
^^ careful with "dd" commands, you don't want to write something to one of your partitions (with S-Off you can brick easily using this command)
in particular the "of=" (output file)... do not want to write something to one of your partitions!! (by mistake)
reading (and saving to /sdard) is perfectly safe, just not writing
this is what a p6 looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the MID the system reads is at offset 0x4000, the others remain unchanged, and CID the system reads is in a completely different partition(s).... so from here you can pretty much get the all the info what your phone originally was.

<typed this by Mistake>

alray said:
MID must match too
better to post a ''fastboot getvar all'' except imei/sn so we can tell if you can flash that ruu
also post a link to the ruu you want to flash.
Click to expand...
Click to collapse
Here is the info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.708.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3888mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0\
Not sure of flashing any RUU right now.. as I will nt be doing it now.. But would like to know if I can flash any RUU I want...

Rah0ol said:
Here is the info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.20.708.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
Not sure of flashing any RUU right now.. as I will nt be doing it now.. But would like to know if I can flash any RUU I want...
Click to expand...
Click to collapse
I highly recommend you either change your MID and/or pull that partition i was talking about earlier... obviously the previous owner thought that there is something called SuperMID, which (in my very humble opinion) doesn't exist
SuperCID (CID = Carrier ID)... fine, you're just changing carrier ID
MID = model ID = hardware... not fine, thinking you can change it that easily and "get away with it", you cannot change the phone hardware simply by changing MID.

nkk71 said:
I highly recommend you either change your MID and/or pull that partition i was talking about earlier... obviously the previous owner thought that there is something called SuperMID, which (in my very humble opinion) doesn't exist
SuperCID (CID = Carrier ID)... fine, you're just changing carrier ID
MID = model ID = hardware... not fine, thinking you can change it that easily and "get away with it", you cannot change the phone hardware simply by changing MID.
Click to expand...
Click to collapse
'
Thanks a lot for that information. My question was, Secondly, I need to know if this phone can be used for development purposes? Like.. In future if I unlock the bootloader by HTC Dev method, and as its S-OFF and SuperCID already present, will I be able to flash recovery and flash any Firmware present here in dev section? Or I need to correct the MID else it wouldnt allow flashing?

Rah0ol said:
'
Thanks a lot for that information. My question was, Secondly, I need to know if this phone can be used for development purposes? Like.. In future if I unlock the bootloader by HTC Dev method, and as its S-OFF and SuperCID already present, will I be able to flash recovery and flash any Firmware present here in dev section? Or I need to correct the MID else it wouldnt allow flashing?
Click to expand...
Click to collapse
As long as you're S-Off you can unlock even without HTCdev.
and yes, you can flash pretty much anything for the m7_u or ul models (m7_u and ul software/firmware works for both models), the exceptions are CDMA phones (such as Sprint and Verizon), and Dual-SIM stuff.
As for the MID, (for firmware flashing) you may get MID mismatch if the android-info.txt doesn't contain "PN071****"
MIDs should be (as far as I'm aware):
PN0710000 -> international M7_UL
PN0711000 -> international M7_U
PN0712000 -> US/Canada M7_UL
PN0713000 -> US T-Mobile M7_UL
PN0714000 -> Asia M7_UL
To change your MID to one of the above (PN0710000 for example), you can use this tool: [TOOL] MID change without ENG HBOOT | Aroma GUI
which you use in a custom recovery.
And the most important part: do not go S-On!!!!!
.

nkk71 said:
As long as you're S-Off you can unlock even without HTCdev.
and yes, you can flash pretty much anything for the m7_u or ul models (m7_u and ul software/firmware works for both models), the exceptions are CDMA phones (such as Sprint and Verizon), and Dual-SIM stuff.
As for the MID, (for firmware flashing) you may get MID mismatch if the android-info.txt doesn't contain "PN071****"
MIDs should be (as far as I'm aware):
PN0710000 -> international M7_UL
PN0711000 -> international M7_U
PN0712000 -> US/Canada M7_UL
PN0713000 -> US T-Mobile M7_UL
PN0714000 -> Asia M7_UL
To change your MID to one of the above (PN0710000 for example), you can use this tool: [TOOL] MID change without ENG HBOOT | Aroma GUI
which you use in a custom recovery.
And the most important part: do not go S-On!!!!!
.
Click to expand...
Click to collapse
Awesome! Thanks for the info.. One more small thing.. In the HTC help and error reporting, it said that this is a test device... Will that restrict flashing new FW and all?? Also will that error message disappear if I flash a different FW or RUU? I think it shud be because of OS, but I wanna know..

Rah0ol said:
Awesome! Thanks for the info.. One more small thing.. In the HTC help and error reporting, it said that this is a test device... Will that restrict flashing new FW and all?? Also will that error message disappear if I flash a different FW or RUU? I think it shud be because of OS, but I wanna know..
Click to expand...
Click to collapse
That message (test device and error reporting is always on) is due to the device being S-Off (on a stock ROM)... but who cares?
--1) Do you think HTC collects more information than google, your provider, etc
--2) how often does your phone crash? cause that's when it's supposed to send the information
--->> if you are the paranoid type, and think you need to go S-On (because it won't "allow" them to collect information), you're going to get into a lot of trouble if you don't know when and how to do it (which firmware, which ROM, which CID, which MID), and you'll be seriously stuck!!
And that message won't affect your ability to flash anything.

nkk71 said:
That message (test device and error reporting is always on) is due to the device being S-Off (on a stock ROM)... but who cares?
--1) Do you think HTC collects more information than google, your provider, etc
--2) how often does your phone crash? cause that's when it's supposed to send the information
--->> if you are the paranoid type, and think you need to go S-On (because it won't "allow" them to collect information), you're going to get into a lot of trouble if you don't know when and how to do it (which firmware, which ROM, which CID, which MID), and you'll be seriously stuck!!
And that message won't affect your ability to flash anything.
Click to expand...
Click to collapse
Nah, I am not that paranoid type and not concerned about HTC Collecting informartion.. Just wanted to know about the ability to flash The information you gave is perfect and what I wanted to read. Thanks a lot nkk71 ..

Rah0ol said:
Nah, I am not that paranoid type and not concerned about HTC Collecting informartion.. Just wanted to know about the ability to flash The information you gave is perfect and what I wanted to read. Thanks a lot nkk71 ..
Click to expand...
Click to collapse
no problem, remember to:
1- stay s-off
2- flash things only for m7_u/ul models... if you are unsure, then better ask first!!
for example this: http://forum.xda-developers.com/showthread.php?t=2626050 almost looks like for the HTC One, but it does say:
* Target device: HTC Droid DNA (PL8320000)
and it's in the:
forum!!!
you flash that, and you have yourself a serious problem!!
So stick to the correct forum, and make sure what you flash is m7_u/ul
Happy flashing

nkk71 said:
no problem, remember to:
1- stay s-off
2- flash things only for m7_u/ul models... if you are unsure, then better ask first!!
for example this: http://forum.xda-developers.com/showthread.php?t=2626050 almost looks like for the HTC One, but it does say:
* Target device: HTC Droid DNA (PL8320000)
and it's in the:
forum!!!
you flash that, and you have yourself a serious problem!!
So stick to the correct forum, and make sure what you flash is m7_u/ul
Happy flashing
Click to expand...
Click to collapse
Oh that much I am used to.. I was in Incredible S Dev forum earlier and have efficiently used all ROMs starting from GB to KK.. Just that I didnt understand the concept of CID which was not there(or I didnt have to take a look at) but after the information got from you, I think I am sufficient info to start D
I am not a Noob at flashing and Rooting but some concepts change in a higher end phones and its always better to know stuffs indepth before trying it

[SOLVED] REQUEST how to unroot htc one full stock

Am s-off and I need to get back to stock for warrenty
device CID HTC__J15
emirates UAE
cant find correct RUU
raido 4A.25.3263.21 DONT know if it was modified but i did not modified any radio or CID before
if rom installation changes it i dont know im noob
hboot 1.56.0000 modified for no red warning
read a thread says this is the RUU for middle east is it right is it safe to use older RUU to restore am really new to this
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
in samsung i only need odin and stock Rom Here is a whole different situation

Iloudsan said:
Am s-off and I need to get back to stock for warrenty
device CID HTC__J15
emirates UAE
cant find correct RUU
raido 4A.25.3263.21 DONT know if it was modified but i did not modified any radio or CID before
if rom installation changes it i dont know im noob
hboot 1.56.0000 modified for no red warning
read a thread says this is the RUU for middle east is it right is it safe to use older RUU to restore am really new to this
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
in samsung i only need odin and stock Rom Here is a whole different situation
Click to expand...
Click to collapse
post the output of "fastboot getvar all" except imei and serialno
yes you can safely apply an older ruu if you have s-off, but first lets be sure if its the right one for your phone with the "fastboot getvar all"
also post a picture of your bootloader screen.

alray said:
post the output of "fastboot getvar all" except imei and serialno
yes you can safely apply an older ruu if you have s-off, but first lets be sure if its the right one for your phone with the "fastboot getvar all"
also post a picture of your bootloader screen.
Click to expand...
Click to collapse
------------------------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH Deleted it for safety
(bootloader) imei: Deleted it for safety
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
----------------------------------------
is it ok to flash RUU with modded Hboot while in s-off
im scared of doing anything Wrong
BOOTLOADER
-------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dont know why the OS does not show Up
this the file name of the modded hboot
mod_hboot_1.56.0000_M7_4.19.401.11.zip
does RUU install stock hboot???
do i need to restore stock frimware or Hboot before proceeding to RUU installation
is this the file i need http://www.androidfilehost.com/?fid=23329332407579952
ok i took the risk and flashed the RUU my device is now not tempered
but the i dont get the red warning while booting is this means that the hboot did not restored?

Iloudsan said:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
Click to expand...
Click to collapse
Do you need to S-On?
EDIT: check my guide http://forum.xda-developers.com/showthread.php?t=2541082
use RUU.ZIP method (post #1, #2, and #4) using the 1.28.401.7 RUU.ZIP from guru
or AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
S-On/S-Off is your decision, but you should definitely set it LOCKED (not relocked) and untampered.

nkk71 said:
Do you need to S-On?
EDIT: check my guide http://forum.xda-developers.com/showthread.php?t=2541082
use RUU.ZIP method (post #1, #2, and #4) using the 1.28.401.7 RUU.ZIP from guru
or AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
S-On/S-Off is your decision, but you should definitely set it LOCKED (not relocked) and untampered.
Click to expand...
Click to collapse
I used the ruu i posted and and then installed TWRP for Guru_Bootloader_Reset_1.0
and then accidentally installed root via Twrp
and when i use The RUU again it gives me error 158 image error and hw to get stock recovery after finishing from Guru_Bootloader_Reset_1.0
i think i will get stuck with the recovery at the end but know even the RUU is not installing now again what to do
i wish that i found your thread before i think you the one who will help me through this
and yes i need S-on for the warranty
downgraded hboot to 1.44 to avoid any problem
is RUU files can be used once???

Iloudsan said:
I used the ruu i posted and and then installed TWRP for Guru_Bootloader_Reset_1.0
and then accidentally installed root via Twrp
and when i use The RUU again it gives me error 158 image error and hw to get stock recovery after finishing from Guru_Bootloader_Reset_1.0
i think i will get stuck with the recovery at the end but know even the RUU is not installing now again what to do
i wish that i found your thread before i think you the one who will help me through this
and yes i need S-on for the warranty
downgraded hboot to 1.44 to avoid any problem
is RUU files can be used once???
Click to expand...
Click to collapse
so you still have S-Off right?
please check MD5 on the RUU download, sounds like a corrupt download

nkk71 said:
so you still have S-Off right?
please check MD5 on the RUU download, sounds like a corrupt download
Click to expand...
Click to collapse
yes im still S-off
but the RUU had worked once why is not working again ERROR 158
i am trying it now again
what im doing now is trying to get the device the way it was before the RUU running
maybe it wil work i hope it works

Iloudsan said:
yes im still S-off
but the RUU had worked once why is not working again ERROR 158
i am trying it now again
Click to expand...
Click to collapse
Check md5 first
Sent from my HTC One using Tapatalk

nkk71 said:
Check md5 first
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
how to ??
which application should i use
i dont have .md5 file
dont lnow what am saying

nkk71 said:
Check md5 first
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i got the RUU to work
before working with the RUU i used guru reset like in your thread
just now the RUU finished
and now waiting it to bootup
and confirm no tampered
locked
to s-on the device
thank you
dont leave me still in need for you
the only step left S-ON

nkk71 said:
so you still have S-Off right?
please check MD5 on the RUU download, sounds like a corrupt download
Click to expand...
Click to collapse
ok now im s-on no tampered and locked
is it good to go for warranty?
now am installing OTAs
you are amazing

Iloudsan said:
ok now im s-on no tampered and locked
is it good to go for warranty?
now am installing OTAs
you are amazing
Click to expand...
Click to collapse
yep it's good to send to warranty, why bother with OTAs, they'll probably update it for you anyway
and if all is good please mark the thread as [SOLVED]

nkk71 said:
yep it's good to send to warranty, why bother with OTAs, they'll probably update it for you anyway
and if all is good please mark the thread as [SOLVED]
Click to expand...
Click to collapse
Thank you.
Hoping to mark the thread now
Just one last question is the camera lens glass (cover) replaceable.
Is it under warranty or I should pay for it to be fixed
I don't know how the he'll did it broke

[q] q my htc one not entering recovery mode

HI ALL
MY HTC ONE AT&T UNLOCKED
MY HTC ONE hade a problem with battery
three days back i replace the battery but my device keep rebooting :crying:
i can enter bootloader menu but not revcovery
i try to flash boot.img from cmd its don completely but device same
i try to run ruu rom its don completely but device same
there on different in one case the htc screen come with wirning "This build is for development purposes only do not distribute outside of HTC without HTC's permission ..."
- Device details -
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
openDSP-v31.120.274.0617
OS-3.17.502.3
eMMc-boot 2048MB
sep 10 2013,01:32:23.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3562mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
hope you can help guys
best regards

fastboot flash recovery recovery_name.img
fastboot erase cache

First off, remove your IMEI and Serial Number from the post above. That's sensitive information.
Second, normally the "Development Purpose" message should disappear once you flash back to stock with RUU. are you positive that flashing finished successfully?
Anyhow your problem should be solved - as BenPope has said - by reflashing your recovery. Just pick a suitable revocery image, enter Bootloader in FastbootUSB mode and give it a try:
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache

i did this guys and my device still same

supermagic49 said:
i did this guys and my device still same
Click to expand...
Click to collapse
Which recovery exactly did you flash? Are you absolutely positive it was a suitable version for your device?
How by the way did you change the battery yourself? Did you disassemble the phone? If so you might perhaps have broken something?
Gesendet von meinem SM-T705 mit Tapatalk

- I had tried all recovery files CWS__001 in this link http://forum.xda-developers.com/showthread.php?t=2545227
- i changed battery in maintenance center but u think it can start bootloader accept flashing an there is something broken
do u advice to disassemble n see
regards

supermagic49 said:
- I had tried all recovery files CWS__001 in this link http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Those are Stock Recoverys if I'm not mistaken. So even if you flashed those you wouldn't recognize any difference as they don't change anything compared to stock.
But first there's something else I oversaw. In your OP you stated your details. It seems you haven't yet unlocked your bootloader? Or did you just leave out that information? That would be the reason why flashing anything does not work - AT ALL.
Unlock your Bootloader (use seach, there are lots of tutorials on how to do that). Second, please don't temper with the boot.img right now. There is no reason for you to change or overwrite a working bootloader. In fact the chances are you would mess up things even more. So leave the boot.img alone for now.
My suggestion is:
- Unlock your Bootloader (with HTCDev)
- Flash a Custom Recovery (e.g. TWRP - http://forum.xda-developers.com/showthread.php?t=2173870)
- Take it from there. See if recovery works and if so, go ahead an flash a Custom ROM, a Nandroid Backup or get yourself S-OFF (Firewater or Rumrunner) and flash back a stock RUU.
RUUs can be a bit tricky with S-ON. So although you theoretically should be able to flash a (newer) RUU even with S-ON, you can make sure it works by being S-OFF first. SInce only then can you also downgrade your Device via RUU plus it then does not matter if you're locked / unlocked / relocked / tempered. Thing is you need a working Android to get S-OFF. That's why I suggested flashing a Custom ROM. Just about any suitable M7 ROM will do, for example: http://forum.xda-developers.com/showthread.php?t=2334294. Give it a try and tell me how it went, will you? Best of luck. But if you're unsure about anything, ask first. Don't mess things up even more

Ok nosmint
thnx for ur kind following
- my device is unlocked
-i flash one of the recovery u refer to with the order " fastboot flash boot" because "flash revocery" return to me with "remot no allowed"
-flash zip and flash recovery is not allowed i think if i clear this problem every thing will be fine
one more thing i open my device i found to cable not fixed i fix bu no changes
that,s the cable was not fixed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://i.ytimg.com/vi/S5KNmDeJ4Ww/maxresdefault.jpg

nosmint said:
... get yourself S-OFF (Firewater or Rumrunner) and flash back a stock RUU.
RUUs can be a bit tricky with S-ON.
Click to expand...
Click to collapse
the OP says:
(bootloader) version-misc: PVT SHIP S-OFF

nkk71 said:
the OP says:
(bootloader) version-misc: PVT SHIP S-OFF
Click to expand...
Click to collapse
Any advice dear

supermagic49 said:
Any advice dear
Click to expand...
Click to collapse
Well first of all please explain what your goal is.... do you want custom ROM, stock ROM, etc.
Second, we are talking about bootloader unlocked not SIM-unlocked, this
- my device is unlocked
-i flash one of the recovery u refer to with the order " fastboot flash boot" because "flash revocery" return to me with "remot no allowed"
Click to expand...
Click to collapse
indicates your bootloader is either LOCKED or RELOCKED
look at the first line of the attached screenshot.
So please explain what your goal is, and i'll try and help from there.

How can i clear the message of " remote not allowed so i can flash recovery
Regards

supermagic49 said:
How can i clear the message of " remote not allowed so i can flash recovery
Regards
Click to expand...
Click to collapse
you would need to unlock bootloader (it's pretty easy with S-Off), but please first tell us what you want to achieve

nkk71 said:
Well first of all please explain what your goal is.... do you want custom ROM, stock ROM, etc.
Second, we are talking about bootloader unlocked not SIM-unlocked, this
indicates your bootloader is either LOCKED or RELOCKED
look at the first line of the attached screenshot.
So please explain what your goal is, and i'll try and help from there.
Click to expand...
Click to collapse
Fine
my goal to see my device working with custom ROM or stock ROM
my bootloader unlocked i just forget to mention that

supermagic49 said:
Fine
my goal to see my device working with custom ROM or stock ROM
my bootloader unlocked i just forget to mention that
Click to expand...
Click to collapse
use this RUU: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
that will wipe your phone completely and install stock ROM and firmware.

i had tried this too but no change

ruu info
When looking for ruu.exe I went through 6 or 7 different ones. 1 way to know if u have the right ruu is by searching your android and sense version also provider currently on your phone otherwise the ruu won't work s-off dosnt matter I never turned it off on my phone and still got the ruu to work

[SOLVED] HTC One M7 U version hboot 1.44 blocked on JB: impossible to flash RUU

Hi to everybody, I've bought an used HTC One, I've do S-Off, root and everything else.
But after I discovered that it has only 16Gb and not 32Gb and it is the U version, so not LTE available.
So, acting like an idiot, I've tried to restock to send back the phone.
I don't know what kind of ancient Ruu I've flashed so hboot now is 1.44 with Android 4.1.2.
This are all the operations I've done to restock:
1. Change the CID into HTC__001
2. Locked the bootloader
3. Trying to flash PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.401.102_Radio_4T.35.3218.16_10.33Q.1718.01D_release_421804_signed.zip, as I friend of mine has suggested
But it does not work, everytime I've tried to Flash I've get an error and the process hangs down.
I cannot find any other RUU for HTC One M7 U with KitKat, or any other to update the hboot...
What can I do now, I can only use the phone with JB?
This is a bootlader screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and this getvar:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45MW9A0433
(bootloader) imei: xxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.406s
Thank you so much!

HarryCustom said:
Hi to everybody, I've bought an used HTC One, I've do S-Off, root and everything else.
But after I discovered that it has only 16Gb and not 32Gb and it is the U version, so not LTE available.
So, acting like an idiot, I've tried to restock to send back the phone.
I don't know what kind of ancient Ruu I've flashed so hboot now is 1.44 with Android 4.1.2.
This are all the operations I've done to restock:
1. Change the CID into HTC__001
2. Locked the bootloader
3. Trying to flash PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.401.102_Radio_4T.35.3218.16_10.33Q.1718.01D_release_421804_signed.zip, as I friend of mine has suggested
But it does not work, everytime I've tried to Flash I've get an error and the process hangs down.
I cannot find any other RUU for HTC One M7 U with KitKat, or any other to update the hboot...
What can I do now, I can only use the phone with JB?
This is a bootlader screen:
and this getvar:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45MW9A0433
(bootloader) imei: xxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.406s
Thank you so much!
Click to expand...
Click to collapse
Your phone must be at least on a 6.xx.xxx.x firmware with hboot 1.57 to be able to flash the 7.xx.xxx.x RUU and you also must use the htc_fastboot.exe to flash lollipop RUU, not the normal fastboot. You can update the phone normally using ota update from your current version to 7.19.401.122 (settings --> about --> software update) or you'll have to update your firmware and then flash the lollipop RUU:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
htc_fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
htc_fastboot reboot
You don't need to lock the bootloader to flash a ruu when you have s-off
You can find the 7.19.401.102 ruu and htc_fastboot here.
don't forget you'll be prompted to update to 7.19.401.122 after flashing the ruu.
For the firmware update, I would simply use the 7.19.401.2 M7_UL firmware. This update is only required so the lollipop ruu can flash, this firmware will be replaced by the correct M7_U firmware when flashing the M7_U ruu anyway. To be able to flash it, open the zip and add your MID to the list in the android-info.txf file.
Btw next time keep posting in your original thread even if the situation has changed. You can edit your thread title and OP if required.

alray said:
Your phone must be at least on a 6.xx.xxx.x firmware with hboot 1.57 to be able to flash the 7.xx.xxx.x RUU and you also must use the htc_fastboot.exe to flash lollipop RUU, not the normal fastboot. You can update the phone normally using ota update from your current version to 7.19.401.122 (settings --> about --> software update) or you'll have to update your firmware and flash then flash the lollipop RUU:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
htc_fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
htc_fastboot reboot
You can find the 7.19.401.102 ruu and htc_fastboot here.
don't forget you'll be prompted to update to 7.19.401.122 after flashing the ruu.
For the firmware update, I would simply use the 7.19.401.2 M7_UL firmware. This update is only required so the lollipop ruu can flash, this firmware will be replaced by the correct M7_U firmware when flashing the M7_U ruu anyway. To be able to flash it, open the zip and add your MID to the list in the android-info.txf file.
Btw next time keep posting in your original thread even if the situation has changed. You can edit your thread title and OP if required.
Click to expand...
Click to collapse
Hi thank you, but I cannot update from OTA, if I check I obtain "no update".
The phone is "locked", but it has still S-off, I was planning to flash the RUU and than S-on.
I've used the right htc_fastboot to flash the RUU...

HarryCustom said:
Hi thank you, but I cannot update from OTA, if I check I obtain "no update".
The phone is "locked", but it has still S-off, I was planning to flash the RUU and than S-on.
I've used the right htc_fastboot to flash the RUU...
Click to expand...
Click to collapse
I wouldn't recommend to go back s-on unless you are sending the phone for warranty. Are you planning to send back the phone or to use it?

alray said:
I wouldn't recommend to go back s-on unless you are sending the phone for warranty. Are you planning to send back the phone or to use it?
Click to expand...
Click to collapse
No I want only to restock and sell it as I just said I was thinkink it was 32gb and Lte but it isn't.
It's a refurbished phone, so no warranty.
In your opionion is there nothing to do, I can only stay on Android 4.1.2?
Edit: Sorry now I've understood, no OTA update, but I could try to flash the firmware, I do it immeditely and than I'll update the status!
Thanks so much!

alray said:
I wouldn't recommend to go back s-on unless you are sending the phone for warranty. Are you planning to send back the phone or to use it?
Click to expand...
Click to collapse
I've flashed the firmware you've suggested and than the RUU and FINALLY everything is gone right, now I am on Lollipop: so I offer you a beer by Paypal Donate!
Only two questions: Blinkfeed seems to be in Arabian, I can change it. But I do not understand why in languages I can find Italian (arabian), Italian (Egypt), but not Italian (Italy), it is a strange thing.
Second question: I think this is last update, but even if I am S-off can I obtain OTA update? If so I prefer to sell the phone as is, with S-off, I think it is a plus.
If not I'll get back to S-On, so the phone would be completely stock with OTA.
Thank you very much!!!

HarryCustom said:
I've flashed the firmware you've suggested and than the RUU and FINALLY everything is gone right, now I am on Lollipop: so I offer you a beer by Paypal Donate!
Only two questions: Blinkfeed seems to be in Arabian, I can change it. But I do not understand why in languages I can find Italian (arabian), Italian (Egypt), but not Italian (Italy), it is a strange thing.
Second question: I think this is last update, but even if I am S-off can I obtain OTA update? If so I prefer to sell the phone as is, with S-off, I think it is a plus.
If not I'll get back to S-On, so the phone would be completely stock with OTA.
Thank you very much!!!
Click to expand...
Click to collapse
For languages availability, it all depend the CID and the version your are using. In case one of the language you need is not available, you can use an app like "morelocale" to enable it, don't no if it still working, I used this one back in 2012 on my Htc one x.
Last update for this version is 7.19.401.122. We might see another minor update soon as announced by Mo Versi on twitter to address the "stagefright" vulnerability. Yes you can still receive ota update with s-off, even with an unlocked bootloader. All you need is 100% stock rom and stock recovery. I would personally consider s-off as a plus if buying a phone as many other ppl.

alray said:
For languages availability, it all depend the CID and the version your are using. In case one of the language you need is not available, you can use an app like "morelocale" to enable it, don't no if it still working, I used this one back in 2012 on my Htc one x.
Last update for this version is 7.19.401.122. We might see another minor update soon as announced by Mo Versi on twitter to address the "stagefright" vulnerability. Yes you can still receive ota update with s-off, even with an unlocked bootloader. All you need is 100% stock rom and stock recovery. I would personally consider s-off as a plus if buying a phone as many other ppl.
Click to expand...
Click to collapse
Ok perfect! I let S-Off.
I've changed the cid from 1111111 to HTC__001 when I've started all the operation, in your opinion is there way to obtain italian (italy) flashing samething else?
It is not a problem for me, but there are lots of strange people on the world, so I think it could be a problem for some kind of buyer!
And now i will buy another htc one with the right features: I hope to be more lucky!

alray said:
For languages availability, it all depend the CID and the version your are using. In case one of the language you need is not available, you can use an app like "morelocale" to enable it, don't no if it still working, I used this one back in 2012 on my Htc one x.
Click to expand...
Click to collapse
Sorry to disturb you again, but I would like to know if there is a solution, changing CID or samething else, for obtaining the righe Language Italian (Italy), if not I will close the phone in its pocket and than I'll try to sell it hoping the seller does not notice that!