Database Develop

[SOLVED] [Q] in bootloader at the OS version line text is red. Why ?

Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response

ankorez said:
Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response
Click to expand...
Click to collapse
Maybe its saying your installed system version doesn't match the one that came with the hboot version. Maybe the tampered is something to do with it.

ankorez said:
Hello Guys
Anyone know why my Os version is red line otherwise green...
look my picture please
thank you for ur response
Click to expand...
Click to collapse
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?

nkk71 said:
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?
Click to expand...
Click to collapse
i check it
thank you

nkk71 said:
This guy had a similar problem: http://forum.xda-developers.com/showthread.php?t=2493798&highlight=os+red+text
But then again, yours looks pretty weird: you bootloader is showing two firmware versions: 2.24.401.8 and (3.62.401.1) AND ON TOP OF THAT you're S-On, so you cannot flash unsigned firmware.
were you trying to flash a signed firmware package by any chance?
Click to expand...
Click to collapse
yes i have flash firmware from here : http://forum.xda-developers.com/showthread.php?t=2182823
and he say : Can I flash this firmware.zip on any HTC One?
in your thread the guy say he's fixed with gruureset but i don't found on the forum

ankorez said:
yes i have flash firmware from here : http://forum.xda-developers.com/showthread.php?t=2182823
and he say : Can I flash this firmware.zip on any HTC One?
in your thread the guy say he's fixed with gruureset but i don't found on the forum
Click to expand...
Click to collapse
But he was S-Off. You are S-On -> very dangerous flashing firmware with S-On, as you can only flash signed firmware, and only upgrade NO DOWNGRADE.
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
as opposed to:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot flash zip <name of firmware>.zip <- yes it has to be done twice, the first one will report failed, the second should succeed.
fastboot reboot
?

nkk71 said:
But he was S-Off. You are S-On -> very dangerous flashing firmware with S-On, as you can only flash signed firmware, and only upgrade NO DOWNGRADE.
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
as opposed to:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot flash zip <name of firmware>.zip <- yes it has to be done twice, the first one will report failed, the second should succeed.
fastboot reboot
?
Click to expand...
Click to collapse
yes it's my problem ! i have do this only
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
---------------
i 've found that http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
you think if i flash it my problem solved?

ankorez said:
yes it's my problem ! i have do this only
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
---------------
i 've found that http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
you think if i flash it my problem solved?
Click to expand...
Click to collapse
The Guru Reset will flash stock ROM (and stock recovery and radio, if you select them in the installer), but it may not solve the firmware issue.
I am just guessing, but because you only ran the "fastboot flash zip <name of firmware>.zip" once, your firmware may be in a state of limbo (if I can call it that):
on one hand it was prepared to upgrade to 3.62.401.1 and that's why it's in the brackets, but since you didn't run the fastboot command another time it actually stayed on 2.24.401.8, and that why you have two different firmware versions in bootloader; one installed 2.24.401.8 another "waiting" to be installed 3.62.401.1. (all this is only a theory)
So what are the options now? Since you were trying to upgrade your firmware (even with S-On, which I take is your preference to stay S-On), I guess you should do it, but this time do it correctly and run the fastboot command twice and make sure it reports success the 2nd time around.
Here's what I would recommend (taking into account you do not wish to S-Off),
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- update the firmware, but correctly this time
3- depending on what ROM you were on, either restore it, or get an updated version for your firmware
And actually, before that, if you just want to test the Guru Reset:
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- flash Guru Reset and see if that works out for you
Those are pretty much my thoughts
PS: when I say backup everything to PC, it's because (sometimes) flashing stock recovery will completely wipe your phone including internal storage (not to mention that unlocking bootloader does that too)
Hit the thanks button IF i helped

nkk71 said:
The Guru Reset will flash stock ROM (and stock recovery and radio, if you select them in the installer), but it may not solve the firmware issue.
I am just guessing, but because you only ran the "fastboot flash zip <name of firmware>.zip" once, your firmware may be in a state of limbo (if I can call it that):
on one hand it was prepared to upgrade to 3.62.401.1 and that's why it's in the brackets, but since you didn't run the fastboot command another time it actually stayed on 2.24.401.8, and that why you have two different firmware versions in bootloader; one installed 2.24.401.8 another "waiting" to be installed 3.62.401.1. (all this is only a theory)
So what are the options now? Since you were trying to upgrade your firmware (even with S-On, which I take is your preference to stay S-On), I guess you should do it, but this time do it correctly and run the fastboot command twice and make sure it reports success the 2nd time around.
Here's what I would recommend (taking into account you do not wish to S-Off),
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- update the firmware, but correctly this time
3- depending on what ROM you were on, either restore it, or get an updated version for your firmware
And actually, before that, if you just want to test the Guru Reset:
1- do a nandroid of your phone, then backup everything to your PC (including the nandroid), just in case.
2- flash Guru Reset and see if that works out for you
Those are pretty much my thoughts
PS: when I say backup everything to PC, it's because (sometimes) flashing stock recovery will completely wipe your phone including internal storage (not to mention that unlocking bootloader does that too)
Hit the thanks button IF i helped
Click to expand...
Click to collapse
Thank you very much i have reflash firmware.zip x2 and the second flash has worked
Thankyou again for you rapid help

ankorez said:
Thank you very much i have reflash firmware.zip x2 and the second flash has worked
Thankyou again for you rapid help
Click to expand...
Click to collapse
My pleasure, if everything is OK now, please add [SOLVED] in the main thread title. Thanks.

By the way im the guy in the other thread,did not get any answers or help had no choice but to use ruu zip to downgrade then ota back up
sent from my s-off 801n M7_UL

steelmaggot said:
By the way im the guy in the other thread,did not get any answers or help had no choice but to use ruu zip to downgrade then ota back up
sent from my s-off 801n M7_UL
Click to expand...
Click to collapse
Quite right it was you, sorry I didnt help out, but I honestly didnt know what the problem was. Only after seeing this guy's screen with two different versions and S-ON, did I think it was an incomplete firmware flash.
Might have been the case with you as well, but I couldnt tell cause the versions were the same, and you were S-Off.
Anyway, lesson learned.

HTC One M7 UL 3.62.401.1 Stuck @ HTC Logo

Bootloader unlocked
m7_UL PVT SHIP S-ON RH
hboot-1.55.0000
radio-4a.21.3263.04
opendsp-v32.120.247.0909
0s: 3.62.401.1
emmc-boot 2048mb
oct 17 2013 h6 23.6.14
Problem is that phone is stuck @ HTC logo
Before that phone was rooted and twrp recovery installed.
Customer do something from recovery (that he unable to describe), then phone stuck @ HTC logo.
I am trying to install RUU.exe but not find any RUU that match with 0s: 3.62.401.1 and radio and CID : Htc__j15.
Then I am trying to s-off for flashing different firmware by supercid, but I failed to s-off because phone is stuck @HTC and don't found as adb
so rumrunner_HTC_0.5.0 tool unable to recognized it.
Now unable to downgrade hboot to 1.44 and s-off the device and find any compatible ruu.exe
I tried factory reset both from Bootloader and recovery but no luck.
Now phone is Stuck @ HTC logo . If I select Boot-loader (Hboot) Nothing found in device manger,
CWM Recovery accessible, only fastboot and oem ruu mode assessable (fastboot oem rebootRUU) and by this it is recognized by ruu.exe
what to do? any method to s-off in this situation or any suggestion?
Thanks.

mmrozibul said:
Bootloader unlocked
m7_UL PVT SHIP S-ON RH
hboot-1.55.0000
radio-4a.21.3263.04
opendsp-v32.120.247.0909
0s: 3.62.401.1
emmc-boot 2048mb
oct 17 2013 h6 23.6.14
Problem is that phone is stuck @ HTC logo
Before that phone was rooted and twrp recovery installed.
Customer do something from recovery (that he unable to describe), then phone stuck @ HTC logo.
I am trying to install RUU.exe but not find any RUU that match with 0s: 3.62.401.1 and radio and CID : Htc__j15.
Then I am trying to s-off for flashing different firmware by supercid, but I failed to s-off because phone is stuck @HTC and don't found as adb
so rumrunner_HTC_0.5.0 tool unable to recognized it.
Now unable to downgrade hboot to 1.44 and s-off the device and find any compatible ruu.exe
I tried factory reset both from Bootloader and recovery but no luck.
Now phone is Stuck @ HTC logo . If I select Boot-loader (Hboot) Nothing found in device manger,
CWM Recovery accessible, only fastboot and oem ruu mode assessable (fastboot oem rebootRUU) and by this it is recognized by ruu.exe
what to do? any method to s-off in this situation or any suggestion?
Thanks.
Click to expand...
Click to collapse
1) Flash the Guru Reset ROM in CWM . Download from this link:
http://www.htc1guru.com/2013/10/guru-reset-3-62-401-1-stock-rom/
Follow the instructions on this page to understand how to put a ROM zip on ur phone through ADB:
http://forum.xda-developers.com/showthread.php?t=2317986
Remember, u have 2 push the Guru Reset ROM zip to the phone
2) Flash the zip file in CWM
3) DONT SELECT ROOT. SELECT STOCK RECOVERY
4) Continue the procedure
5) Profit
Basically, no need for S-OFF and HBOOT 1.44

raghav kapur said:
1) Flash the Guru Reset ROM in CWM . Download from this link:
http://www.htc1guru.com/2013/10/guru-reset-3-62-401-1-stock-rom/
Follow the instructions on this page to understand how to put a ROM zip on ur phone through ADB:
http://forum.xda-developers.com/showthread.php?t=2317986
Remember, u have 2 push the Guru Reset ROM zip to the phone
2) Flash the zip file in CWM
3) DONT SELECT ROOT. SELECT STOCK RECOVERY
4) Continue the procedure
5) Profit
Basically, no need for S-OFF and HBOOT 1.44
Click to expand...
Click to collapse
I have that rom already, I will try post result..
Thanks a lot..

mmrozibul said:
I have that rom already, I will try post result..
Thanks a lot..
Click to expand...
Click to collapse
Pls hit the thanks button if u think I helped u

raghav kapur said:
Pls hit the thanks button if u think I helped u
Click to expand...
Click to collapse
Problem solved by Adb sideload method.
Phone is alive now

this si my first time writing on this forum.ive been stuck with no OS on my One,hboot 1.55,os-3.62.401.1(4.3),unlocked bootloader,with TWRP,with superuser acces.I acidentali delete my whole os and data/system/nternal... in TWRP.TWRP coudnt mount data/system/dalwik cache/internal storage-nothing.i get bootloop.then i get problem with superuser- in TWRp.Tryed to push or sideload many roms and zips,but adb coudnt recognize my device in the way it should.so,with no os and nothing on my internal storage,and getting problem with superuser in TWRP,i tried to run ruu.zip.it start but stuck cuz i was unlocked bootloader and not s-off.so i go from the bigining.I tried to sideload too,but i failed!!!this is what i done---Relock bootloader.Unlock bootloader.Flash latest CWM recovery.Thru cwm i flash cm 10.1.It boots!!then flash susuperuser.zip to gain root.with root checker i chech if i manage root.if not,use another superuser.zip...then i flash ARHD 11 to try s-off(fail).then i flash ARHD 52.0,again check my root.then i run firewater and get S-off.I see many people stuck with no os and with adb problems,or cant get s-off to retun to stock or run the device which is in bootloop.this is how i manage to un-softbrick my One,and to get S-off
Sory for my english,and sory if the thread is wrong.I just want to help if someone got stuck in bootloop/with no os/with no S-off to run ruu.zip or any rom.
( Im not responsible if you brick your device,this is just sugestion and way how i did it)

[Q] i bricked my M7 with wrong firmware

hi all
i was tried to flash my M7 from 4.3 to 4.4.2
downloaded the OTA update 4.19.401.7
contained :
DATA
META-INF
PATCH
System
Firmware.zip
Fotaboot
Skin_fota
the wrong step is : extracted the Firmware.zip file only
and flashed it only by :
fastboot oem rebootRUU
fastboot flash zip firmware.zip
now the phone is bricked, only boot to the HTC logo and black screen
when i try to press power bottom, the (Back & Home) led blinking
i was boot to bootloader and copy this information to you :
***LOCKED***
M7_UL PVT SHIP S-ON
HBOOT-1.56.0000 (it was 1.55 before)
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.401.9 (it was 3.62.401.1)
eMMC-boot 2048MB
Feb 7 2014,01:06:01.0
i was try to rename the OTA file to Firmware.zip and flash it again, but always failed
i was try to flash downgrade Firmware (3.62.401.1) also failed
i was try to flash RUU.exe (1.28.401.7) from the Fastboot screen and from the rebootRUU screen also failed
i was try to wipe and re-flash the same Firmware.zip file, it's flashed with no failed steps, but still bricked and no system to boot into
can you help me ?

My suggestion:
You are acting nervous, don´t know, from where you got the solutions you´ve tried. Your phone is not bricked if you have access to your bootloader as you wrote but yo can´t flash the needed things with a locked bootloader. Would be better to ask before every step, if you don´t know what to do.
1st you can send your device to HTC for repair...i think you have to pay for that
or 2nd (read and think about the warranty):
Unlock your bootloader via HTC.Dev. http://www.htcdev.com/devcenter
With locked bootloader it won´t run. If you have access to your bootloader, you are able to flash a recovery via Fastboot-USB and have access to adb. With S-On you can´t run the RUU you´ve tried, because you can´t downgrade your phone. S-Off would be the solution, but at the moment you can´t get it with your high HBoot version.
I think, the correct firmware is ready on your phone and you should
- unlock your bootloader with your Unlock_code.bin from HTC.Dev, flash it via Fastboot-USB fastboot flash unlocktoken Unlock_code.bin, accept the message on your phone, then
- flash TWRP 2.6.3.3 m7 recovery via fastboot, fastboot erase cache then fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
- sideload Maximus Rom or ARHD 52.0 via adb in recovery adb sideload HTC_One_-_MaximusHD_32.0.0.zip (if other rom, you have to replace the correct filename of the zip)
- or sideload the stock odexed rom 4.19.401.9 from the same download area at ARHD for the One
- check the MD5 sum before sideload! http://www.flashplayerpro.com/MD5Checksum/downloadMD5Checksum.htm
(even saw, the links of ARHD are down at the moment - the server problems of mike 1986 are not gone. Try it tomorrow or read the last sites of the thread to find alternative links),
- wipe data, system, dalvik cache and cache in recovery (not sd card)
- install the rom.zip via recovery, reboot into bootloader and
- flash the boot.img copied out of the rom via fastboot. fastboot erase cache then fastboot flash boot boot.img then fastboot erase cache
Then your device hopefully will boot again.
If the steps of flashing roms with TWRP are after reading this not really known, read the FAQ before.

If you are able to go to bootloader then give it a try. Unlock bootloader then try to flash firmware.
Sent from my HTC One using xda app-developers app

manishvy said:
If you are able to go to bootloader then give it a try. Unlock bootloader then try to flash firmware.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip

alray said:
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip
Click to expand...
Click to collapse
Dont care about anything.. just goto HTC dev website, follow the steps and unlock the boot loader and flash the firmware..

alray said:
Correct me if i'm wrong but with S-ON you need the bootloader to be locked/re-locked to flash the firmware.zip
Click to expand...
Click to collapse
naresh_r said:
Dont care about anything.. just goto HTC dev website, follow the steps and unlock the boot loader and flash the firmware..
Click to expand...
Click to collapse
alray is correct mate! with S-On you need to have bootloader locked/relocked to be able to flash anything in ruu mode.
moha_moha20106 said:
hi all
i was tried to flash my M7 from 4.3 to 4.4.2
downloaded the OTA update 4.19.401.7
can you help me ?
Click to expand...
Click to collapse
OP, didn't we agree that you were going to wait??
I'm not entirely sure if stock recovery will read an OTG cable + stick, but worth a try:
if you haven't unlocked yet, get yourself an OTG cable + stick, put the OTA.ZIP (yes all of it, not just firmware), on the stick. connect it to your phone, and reboot into stock recovery, then press POWER + VOLUP (and hope it sees the otg), and use the "apply from sdcard" option to install the OTA.

Neo XL said:
My suggestion:
You are acting nervous, don´t know, from where you got the solutions you´ve tried. Your phone is not bricked if you have access to your bootloader as you wrote but yo can´t flash the needed things with a locked bootloader. Would be better to ask before every step, if you don´t know what to do.
1st you can send your device to HTC for repair...i think you have to pay for that
or 2nd (read and think about the warranty):
Unlock your bootloader via HTC.Dev. http://www.htcdev.com/devcenter
With locked bootloader it won´t run. If you have access to your bootloader, you are able to flash a recovery via Fastboot-USB and have access to adb. With S-On you can´t run the RUU you´ve tried, because you can´t downgrade your phone. S-Off would be the solution, but at the moment you can´t get it with your high HBoot version.
I think, the correct firmware is ready on your phone and you should
- unlock your bootloader with your Unlock_code.bin from HTC.Dev, flash it via Fastboot-USB fastboot flash unlocktoken Unlock_code.bin, accept the message on your phone, then
- flash TWRP 2.6.3.3 m7 recovery via fastboot, fastboot erase cache then fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
- sideload Maximus Rom or ARHD 52.0 via adb in recovery adb sideload HTC_One_-_MaximusHD_32.0.0.zip (if other rom, you have to replace the correct filename of the zip)
- or sideload the stock odexed rom 4.19.401.9 from the same download area at ARHD for the One
- check the MD5 sum before sideload! http://www.flashplayerpro.com/MD5Checksum/downloadMD5Checksum.htm
(even saw, the links of ARHD are down at the moment - the server problems of mike 1986 are not gone. Try it tomorrow or read the last sites of the thread to find alternative links),
- wipe data, system, dalvik cache and cache in recovery (not sd card)
- install the rom.zip via recovery, reboot into bootloader and
- flash the boot.img copied out of the rom via fastboot. fastboot erase cache then fastboot flash boot boot.img then fastboot erase cache
Then your device hopefully will boot again.
If the steps of flashing roms with TWRP are after reading this not really known, read the FAQ before.
Click to expand...
Click to collapse
Dear , i will send my phone to the HTC Maintenance center and ask them to resolve it with my warranty
if i UNLOCK my phone and S-OFF , i think i will loose my 9months warranty
if they told my the problem is by you (me), i will ask them to maintain it and pay money
thank you very much

nkk71 said:
alray is correct mate! with S-On you need to have bootloader locked/relocked to be able to flash anything in ruu mode.
OP, didn't we agree that you were going to wait??
I'm not entirely sure if stock recovery will read an OTG cable + stick, but worth a try:
if you haven't unlocked yet, get yourself an OTG cable + stick, put the OTA.ZIP (yes all of it, not just firmware), on the stick. connect it to your phone, and reboot into stock recovery, then press POWER + VOLUP (and hope it sees the otg), and use the "apply from sdcard" option to install the OTA.
Click to expand...
Click to collapse
Dear, i'm sorry for that
yes, we agreed before for waiting...
but the HTC MEA always lier
i was try to connect the OTG cable, but the bootloader didn't read it, i think the OTG function is by system, not by bootloader
thank you very much dear

Stock RUU need help

Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome

ubas98 said:
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
Click to expand...
Click to collapse
post the ouput of "fastboot getvar all" except the IMEI and SERIALNO so we can help you determine which RUU you can use if any available for your phone.

M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me

ubas98 said:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
Click to expand...
Click to collapse
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?

Seanie280672 said:
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Click to expand...
Click to collapse
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do

ubas98 said:
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
Click to expand...
Click to collapse
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.

Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?

ubas98 said:
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
Click to expand...
Click to collapse
password ? never seen that before, could you post a photo of it ?

Seanie280672 said:
password ? never seen that before, could you post a photo of it ?
Click to expand...
Click to collapse
http://postimg.org/image/ucolu3a83/ here is the img

ubas98 said:
http://postimg.org/image/ucolu3a83/ here is the img
Click to expand...
Click to collapse
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that

Seanie280672 said:
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Click to expand...
Click to collapse
maybe i could use another recovery .if yes anny what is other best recovery?

ubas98 said:
maybe i could use another recovery .if yes anny what is other best recovery?
Click to expand...
Click to collapse
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?

ubas98 said:
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
Click to expand...
Click to collapse
adb push it straight to the sdcard, make sure your phone is plugged into the computer and the rom is in the same folder as adb and fastboot files, then issue this command:
Code:
adb push (name of rom).zip /sdcard/
it will look like its not doing anything but will let you know when its done, then uplug your phone before flashing the rom.
and both TWRP and CWM have their good points, you need CWM to flash AOSP rom's and TWRP to flash sense rom's

Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.

SGSII_LEDnotify said:
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
Click to expand...
Click to collapse
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?

Seanie280672 said:
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Click to expand...
Click to collapse
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.

SGSII_LEDnotify said:
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
Click to expand...
Click to collapse
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.

Seanie280672 said:
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Click to expand...
Click to collapse
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete

SGSII_LEDnotify said:
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
Click to expand...
Click to collapse
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.

Seanie280672 said:
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Click to expand...
Click to collapse
I renamed the zip file because there were spaces in the name causing errors, would that cause a failure when trying to install?
skipping MD5 check: no md5 file found
Error flashing zip '/sdcard/****.zip'
updating partition details
failed

[Q] S-On and unable to reflash stock rom

Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.

OfficialLocdoGg said:
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
Click to expand...
Click to collapse
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/

I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
alray said:
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse

OfficialLocdoGg said:
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
Click to expand...
Click to collapse
its fine to flash a ruu with phone booted in bootloader btw.

alray said:
its fine to flash a ruu with phone booted in bootloader btw.
Click to expand...
Click to collapse
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.

OfficialLocdoGg said:
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
Click to expand...
Click to collapse
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Boot into bootloader/FASTBOOT USB
Type:
Code:
[B][I]fastboot oem lock[/I][/B]
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.

majmoz said:
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
Click to expand...
Click to collapse
Thanks. This restored the phone to a usable state. I'm going to try firewater now.