I've tried 3 different roms today, Viper one, badboys, and android revolution HD.
After I flashing with the latest TWRP then, wiping davik/cache, and rebooting the same result. I can see the fancy LOCK screen but after I slide up to unlock it, all I can see is the green HTC logo with the wite background, then after awhile it'll reboot. in addition it tells me that com.htc.htcdialer isn't responding and asks if I want to close it.
help would be appreciated.
Try flashing twrp 2.6.3.3. Some of the newer versions have issues
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
Try flashing twrp 2.6.3.3. Some of the newer versions have issues
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, will do.
Ok, i tried twrp version 2633, I tried to go to recovery but it goes straight to a regular boot, I also tried philz, which did the same as the latest twrp.
Try the fastboot erase cache command and then see if u can get into recovery. U need twrp for arhd
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
Try the fastboot erase cache command and then see if u can get into recovery. U need twrp for arhd
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That worked, I got back into recovery. But we're back at square one, Green HTC logo with white background also, "Process com.htc.htcdialer isn't responding"
I let it sit there for about 40 mins after i chose to wait instead of closing com.htc.htcdialer and the phone setupstarted. wooo. Lets see how it runs. so far i'm getting no service bars from sprint and sync'ing contact is stuck of syncing, it's been more than an hr.
UPDATE, i rebooted and once again i'm stuck at the green HTC logo with the white background after unlocking the screen.
Bump. reading around, nothing is working. tried formating and full wipes before rom flashes, also tried doing a RUU but it fails. giving me a 155, Yes I was relocked for for the RUU and i had to go in fastboot usb for the RUU to detect my phone.
Can you Do a fastboot getvar all on here minus serial and imei
Sent from my HTC One using XDA Premium 4 mobile app
Sure.
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 3826mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
Click to expand...
Click to collapse
nateboi81 said:
Can you Do a fastboot getvar all on here minus serial and imei
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried all sorts of things bro. If the sprint released RUU doesn't work Idk what will. Hope it's just some simple solution that we're all overlooking.
I'm no expert on that. But that is the Sprint mobile correct? I'm not sure of the difference between that and the international one. Did you try flashing roms from the Sprint HTC one forum. They may not be compatible
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
You really should post in the Sprint forum anyways
Sent from my HTC One using XDA Premium 4 mobile app
nibblemynutz said:
Sure.
version-bootloader: 1.56.0000
version-baseband: N/A
version-main:
version-misc: PVT SHIP S-OFF
product: m7_wls
modelid: PN0720000
cidnum: SPCS_001
Click to expand...
Click to collapse
I think you're doing quite a few mistakes here, including using recoveries not for you phone.
TWRP for Sprint is here: http://techerrata.com/browse/twrp2/m7wls
Now luckily you are S-Off, so best to RUU back to Sprint to fix your partitions, then you can start customizing again.
With S-Off there is no need to lock/relock bootloader, you can leave it UNLOCKED.
If you are using an RUU.EXE then you will manually have to downgrade hboot to 1.44 first for it to work, otherwise I would really recommend you use a ruu.zip (and make sure it's Sprint and check MD5 on the download to know it's not corrupt):
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE !!
fastboot reboot-bootloader
And don't even think about S-ON!!
.
nkk71 said:
I think you're doing quite a few mistakes here, including using recoveries not for you phone.
TWRP for Sprint is here: http://techerrata.com/browse/twrp2/m7wls
Now luckily you are S-Off, so best to RUU back to Sprint to fix your partitions, then you can start customizing again.
With S-Off there is no need to lock/relock bootloader, you can leave it UNLOCKED.
If you are using an RUU.EXE then you will manually have to downgrade hboot to 1.44 first for it to work, otherwise I would really recommend you use a ruu.zip (and make sure it's Sprint and check MD5 on the download to know it's not corrupt):
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE !!
fastboot reboot-bootloader
And don't even think about S-ON!!
.
Click to expand...
Click to collapse
nkk71
I ran different recoveries for the m7, twrp 263, philz, twrp 70 because I was told the newer twrp recovery has slight bugs. I always wiped clean after I tried installing roms also. I'll take your advice and try the RUU.zip.
nibblemynutz said:
nkk71
I ran different recoveries for the m7, twrp 263, philz, twrp 70 because I was told the newer twrp recovery has slight bugs. I always wiped clean after I tried installing roms also. I'll take your advice and try the RUU.zip.
Click to expand...
Click to collapse
best to use an ruu.zip to get your partitions back in order, then go ahead and flash a recovery (specifically for Sprint; eg I don't think Sprint has a 2.6.3.3 version), and then you can customize your phone to your liking
most of us are on m7_u/ul , so it's sort of "second nature" to say: use twrp 2.6.3.3
So i pushed Ruu.zip to my /sdcard idk if i needed that and did fastboot fastboot oem rebootRUU then fastboot flash zip ruu.zip twice like you said. I tried again after deleting Ruu.zip from my /sdcard and it still gave me
sending 'zip' (1601236 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.008s
Click to expand...
Click to collapse
I got the RUU.zip file from here.
http://forum.xda-developers.com/showthread.php?t=2658910
I'm gonna try this RUU file from here
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
nibblemynutz said:
So i pushed Ruu.zip to my /sdcard idk if i needed that and did fastboot fastboot oem rebootRUU then fastboot flash zip ruu.zip twice like you said. I tried again after deleting Ruu.zip from my /sdcard and it still gave me
I got the RUU.zip file from here.
http://forum.xda-developers.com/showthread.php?t=2658910
I'm gonna try this RUU file from here
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
Click to expand...
Click to collapse
the RUU.zip needs to be in the folder with fastboot ..not on the phone
the 4.xx. one should work fine just be sure you got the decrypted one not the RUU.EXE in a zip file
clsA said:
the RUU.zip needs to be in the folder with fastboot ..not on the phone
the 4.xx. one should work fine just be sure you got the decrypted one not the RUU.EXE in a zip file
Click to expand...
Click to collapse
Haha, I had double checked and found that out.
Thanks so much, I really appreciate the help. Especially nkk71!
All is well, my phone is functional again!, now for the 2nd attempt for a custom rom flash! Looking at bad boy or android revolution! I'm not sure about viper one but heard good things about it.
Related
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode and in RUU mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
awer25 said:
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
Click to expand...
Click to collapse
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
alray said:
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
Click to expand...
Click to collapse
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
Click to expand...
Click to collapse
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
Click to expand...
Click to collapse
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
Thank you for that explanation. I got into RUU mode by doing fastboot oem rebootRUU, which took me to a black screen with silver HTC. That may not be RUU mode...I'm just guessing.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
edit: Wait, there is also a 3.22.1540.1 ruu.zip on htcdev.com so try it first.
fastboot oem rebootRUU
fastboot flash zip <name_of_file>.zip
fastboot flash zip <name_of_file>.zip
fastboot reboot
Click to expand...
Click to collapse
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
awer25 said:
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
Click to expand...
Click to collapse
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
alray said:
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
Click to expand...
Click to collapse
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
awer25 said:
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
Click to expand...
Click to collapse
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on.
Click to expand...
Click to collapse
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
alray said:
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
Click to expand...
Click to collapse
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
awer25 said:
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
Click to expand...
Click to collapse
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
alray said:
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
Click to expand...
Click to collapse
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
awer25 said:
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
Click to expand...
Click to collapse
Try the ruu.exe on windows 7.
alray said:
Try the ruu.exe on windows 7.
Click to expand...
Click to collapse
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
awer25 said:
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
Click to expand...
Click to collapse
I got it! I had to relock my bootloader for some reason. Then, the Windows RUU installed fine.
Thank you alray for your help!
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
-marco- said:
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
Click to expand...
Click to collapse
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
awer25 said:
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
Click to expand...
Click to collapse
thanks !
but which one? And how?
also getvar !
(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.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
-marco- said:
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
finished. total time: 0.066s
Click to expand...
Click to collapse
-marco- said:
I am at work in the office and at some point I look at my phone and I see it rebooted on its own. now it's stuck forever on the HTC one beats audio loading screen.
I didn't even touch anything before. Tried to reboot but it just gets stuck there.
Click to expand...
Click to collapse
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
nkk71 said:
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
Click to expand...
Click to collapse
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
-marco- said:
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
Click to expand...
Click to collapse
Well first I would recommend you update recovery to TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
since they are more compatible when flashing 4.4 ROMs (make sure to check MD5 on the files, that site doesn't play nice with download managers!)
Code:
[B]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader[/B]
-> enter recovery
Second, in TWRP, make a nandroid backup, you may need it later *** (please check below)
Third, put a ROM on the phone (in custom recovery):
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HT34xxxxxxxx recovery <- you need to be in recovery
[B]adb push <name of rom>.zip /sdcard/[/B] <- this will take about 5 mins without any progress
and install the ROM, don't select WIPE during installation, and you should have your million $ question solved... all apps, data, etc should be there, but if you get apps crashing it's because of the "dirty-flash"
As to which ROMs you can use for the above procedure, there's is a 100% stock version of 4.19.401.9 here: http://forum.xda-developers.com/showthread.php?t=2224752
I'm personally using ARHD 52.0 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (stock but with improvements, and rooted)
I haven't checked if there's a 100% stock 4.20.707.6 ROM around, so you could do some googling and see.
Hope that helps
*** once you've done the backup, you can try wiping "data, cache, dalvik", and then restore the nandroid... sometimes that works
if not keep the nandroid, as it has all the information, and you can use Nandroid Manager (in play store) to extract individual information, if need be.
Good Luck
Hi everybody,
I've been flashing custom ROMs for years now, but now I screwed up -.-
I've got a One M7UL and accidentally flashed a Sprint ROM .. Now the only thing left working is fastboot.
If I try to boot into TWRP recovery (tried different versions already) the splashscreen will appear and crash back into bootloop. If I try to boot into clockwork recovery, it will boot but throw various errors 'E:Can't mount /cache/[..]' .. as soon as I try to do anything @ clockwork, it will crash back into bootloop.
I thought about flashing a RUU, but the bootloader is unlocked but still s-on. Modelid: PN0170000 Cidnum: VODAP102. I think the device has to be s-off to flash a RUU.exe, correct ? How about a RUU.zip ? oO Is there a way to get the device s-off without having ADB working ? How do I find a working RUU for this device, because I've read that I need a '1.xx.161.xx' for it's a Vodafon-brand and I won't find a damn usable RUU for it .. Is there a way to use a different RUU ?
help would be MUCH appreciated
thx & greets
hendi
Ok, got ADB working at the damaged clockword recovery .. but sideloading another ROM won't work and it seems like Revone S-OFF only works with a booted 4.2.2 ROM -.-
Any suggestions ?
Here's the output off 'getvar all':
(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.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4246mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.052s
If I could get my hands on another HTC ONE M7ul PN0710000/VODAP102 would I be able to build my own RUU ?
Help would be really appreciated ^^
Have you tried fastboot erase cache?
Sent from my GT-I9305 using xda app-developers app
nateboi81 said:
Have you tried fastboot erase cache?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
yep, sadly without any success.. I also tried different versions of TWRP & clockwork recovery.
thx for the reply
doomhendi said:
If I could get my hands on another HTC ONE M7ul PN0710000/VODAP102 would I be able to build my own RUU ?
Help would be really appreciated ^^
Click to expand...
Click to collapse
it's been a while but i think the old developer edition RUU may work
this is the one for hboot 1.44
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
clsA said:
it's been a while but i think the old developer edition RUU may work
this is the one for hboot 1.44
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
Click to expand...
Click to collapse
hey there
Don't I need a RUU with the version 1.xx.161.xxx because of the s-on + Vodafon-branding ? oO
doomhendi said:
hey there
Don't I need a RUU with the version 1.xx.161.xxx because of the s-on + Vodafon-branding ? oO
Click to expand...
Click to collapse
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in
clsA said:
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in
Click to expand...
Click to collapse
ah, cool that's good to know oO - I am already downloading
doomhendi said:
ah, cool that's good to know oO - I am already downloading
Click to expand...
Click to collapse
Sorry I was doing some more reading ..that RUU requires CID 11111111 and MID PN0712000, I'll keep looking
clsA said:
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in
Click to expand...
Click to collapse
Sorry, didn't read, but if s-on, then don't start fashing things not for your phone... High chance you won't be able to unlock bootloader again!
If s-off, then ok.
Sent from my HTC One using Tapatalk
clsA said:
Sorry I was doing some more reading ..that RUU requires CID 11111111 and MID PN0712000, I'll keep looking
Click to expand...
Click to collapse
big thanks, pal
nkk71 said:
Sorry, didn't read, but if s-on, then don't start fashing things not for your phone... High chance you won't be able to unlock bootloader again!
If s-off, then ok.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
hey, yeah I am afraid it's still s-on .. but I didn't try to flash it so far.
How can I manually lock the bootloader again ? oO I've just tried method 1 from your guide (http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3) but the bootloader still says it's unlocked oO
I haven't tried yet, but 'fastboot oem lock' should do the trick .. Now I just need a fitting RUU oO
Damn it, I'm kinda flashoholic since the good old Windows Mobile 6.51 Pro-times .. but I never took the wrong ROM xX
You guys really seem to know what you are doing .. the wrong ROM seems to have messed up at least the cache partition, may be there is another way than flashing a RUU, to fix this ? If I would be able to get clockwork recovery to install a working rom, it should reconstruct everything or at least give me the opportunity to s-off the device oO
I would be really grateful for some help
I just got an idea: Is it possible to tweak an developers RUU ? oO
Sorry for all the questions, I just really want to get that baby up an running again ^^
doomhendi said:
hey, yeah I am afraid it's still s-on .. but I didn't try to flash it so far.
How can I manually lock the bootloader again ? oO I've just tried method 1 from your guide (http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3) but the bootloader still says it's unlocked oO
I haven't tried yet, but 'fastboot oem lock' should do the trick .. Now I just need a fitting RUU oO
Damn it, I'm kinda flashoholic since the good old Windows Mobile 6.51 Pro-times .. but I never took the wrong ROM xX
You guys really seem to know what you are doing .. the wrong ROM seems to have messed up at least the cache partition, may be there is another way than flashing a RUU, to fix this ? If I would be able to get clockwork recovery to install a working rom, it should reconstruct everything or at least give me the opportunity to s-off the device oO
I would be really grateful for some help
I just got an idea: Is it possible to tweak an developers RUU ? oO
Sorry for all the questions, I just really want to get that baby up an running again ^^
Click to expand...
Click to collapse
sure you can try
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
clsA said:
sure you can try
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
sorry, may be you misunderstood me: The bootloader is open & s-on. I've tried to flash different versions of TWRP & Clockwork Recovery via fastboot, including erase cache.. TWRP won't even start and Clockwork will start but throw multiple 'Can't Mount / Open /cache/[...]' errors and crash as soon as I try to do anything
doomhendi said:
sorry, may be you misunderstood me: The bootloader is open & s-on. I've tried to flash different versions of TWRP & Clockwork Recovery via fastboot, including erase cache.. TWRP won't even start and Clockwork will start but throw multiple 'Can't Mount / Open /cache/[...]' errors and crash as soon as I try to do anything
Click to expand...
Click to collapse
try and flash the stock recovery and do a factory reset
then try and flash TWRP again
Stock recovery's are here >> http://d-h.st/users/guich/?fld_id=29380#files
clsA said:
try and flash the stock recovery and do a factory reset
then try and flash TWRP again
Stock recovery's are here >> http://d-h.st/users/guich/?fld_id=29380#files
Click to expand...
Click to collapse
damn, sorry I've spent the whole day and night, reading how to possibly fix this and already tried to flash stock recovery .. The recovery won't start at all. It doesn't matter if I try to start via 'Factory Reset' or 'Recovery'.
According to the errors clockwork recovery throws, I guess the partition table got (partly?) messed up oO
*edit* Of cause I've tried again, following the link you've just sent me - thx for the effort
doomhendi said:
damn, sorry I've spent the whole day and night, reading how to possibly fix this and already tried to flash stock recovery .. The recovery won't start at all. It doesn't matter if I try to start via 'Factory Reset' or 'Recovery'.
According to the errors clockwork recovery throws, I guess the partition table got (partly?) messed up oO
*edit* Of cause I've tried again, following the link you've just sent me - thx for the effort
Click to expand...
Click to collapse
do you know how to start stock recovery ?
clsA said:
do you know how to start stock recovery ?
Click to expand...
Click to collapse
After flash, erase cache & reboot-bootloader, I've tried 'Factory Reset' @ Hboot and the 'usual' way via the bootloader oO
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
Relax, no payment is required
What you need to do is get a rom onto the phone, RUU isn't required.
You will get a ROM onto the phone using the 'adb sideload' tool. The tutorial is here:
http://forum.xda-developers.com/showthread.php?t=2318497
I recommend that you use the latest ARHD ROM
I have the same exact problem... Only when I try side loading from adb I get an error message saying "device not found" is my HTC one lost forever?
Sent from my Nexus 5 using XDA Free mobile app
mayaakel said:
I have the same exact problem... Only when I try side loading from adb I get an error message saying "device not found" is my HTC one lost forever?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Didn't mean to thank you.. Using my phone to write this
Read the Q&As here to get your phone recognised
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
After that, install these files to a folder called htc one on your desktop.
http://koush.com/post/universal-adb-driver
Sent from my HTC One using XDA Premium 4 mobile app
Thanks will do
Sent from my Nexus 5 using XDA Free mobile app
raghav kapur said:
Relax, no payment is required
What you need to do is get a rom onto the phone, RUU isn't required.
You will get a ROM onto the phone using the 'adb sideload' tool. The tutorial is here:
http://forum.xda-developers.com/showthread.php?t=2318497
I recommend that you use the latest ARHD ROM
Click to expand...
Click to collapse
Done as you have said and installed ARHD. Now I get only the HTC logo on boot and in Hassons2000 toolkit for almost anything it says something about "more than one device and emulator"
Torcidas1950 said:
Done as you have said and installed ARHD. Now I get only the HTC logo on boot and in Hassons2000 toolkit for almost anything it says something about "more than one device and emulator"
Click to expand...
Click to collapse
okay, let's stop using toolkits for a while and do it the old fashioned way, and start at the basics.
so first get this http://www.androidfilehost.com/?fid=23329332407585867
and extract the files into a simple folder, maybe something like C:\ADB
then go to bootloader/FASTBOOT USB, and copy/past the output of "fastboot getvar all" (excluding IMEI and s/n).
nkk71 said:
then go to bootloader/FASTBOOT USB, and copy/past the output of "fastboot getvar all" (excluding IMEI and s/n).
Click to expand...
Click to collapse
I get this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34xxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4183mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Torcidas1950 said:
I get this:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
okay that looks more or less OK, is your bootloader unlocked, and which custom recovery do you have (name and version number please)?
And what is really your ultimate goal? It wasn't very clear in your first post....
Maybe just to get the phone up and running for now?
nkk71 said:
okay that looks more or less OK, is your bootloader unlocked, and which custom recovery do you have (name and version number please)?
And what is really your ultimate goal? It wasn't very clear in your first post....
Maybe just to get the phone up and running for now?
Click to expand...
Click to collapse
ClockWork Mod Recovery 6.0.4.3
Bootloader is unlocked
My ultimate and only goal is to make the phone run again normally after i fix this (if i fix this) I will never touch any system file on this or any other phone
Torcidas1950 said:
ClockWork Mod Recovery 6.0.4.3
Bootloader is unlocked
My ultimate and only goal is to make the phone run again normally after i fix this (if i fix this) I will never touch any system file on this or any other phone
Click to expand...
Click to collapse
and that was the problem, wrong recovery and you tried to probably flash a 4.4 ROM (such as ARHD 53.0)
so get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, and install 53.0
the first boot can take anywhere from a few minutes to 15 minutes.
my personal experience (m7_ul)... after a clean flash (ie wiping userpartition during the installer, and before rebooting wiping dalvik & cache [a bit redundant, but i do it anyways]):
during the first bootup, the screen brightness changes after 3~5 minutes, then i know i'm not in a bootloop, and wait another 5~20 minutes.... more than 20 minutes (as in... "i left it overnight") is unreasonable.
PS: we can fix everything else later
nkk71 said:
and that was the problem, wrong recovery and you tried to probably flash a 4.4 ROM (such as ARHD 53.0)
so get TWRP
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, and install 53.0
the first boot can take anywhere from a few minutes to 15 minutes.
my personal experience (m7_ul)... after a clean flash (ie wiping userpartition during the installer, and before rebooting wiping dalvik & cache [a bit redundant, but i do it anyways]):
during the first bootup, the screen brightness changes after 3~5 minutes, then i know i'm not in a bootloop, and wait another 5~20 minutes.... more than 20 minutes (as in... "i left it overnight") is unreasonable.
PS: we can fix everything else later
Click to expand...
Click to collapse
Yes, I was trying to flash ARHD 53.0 . I will try this method in an hour or so and I will contact you after I'm done. Thank you for your help
Torcidas1950 said:
Yes, I was trying to flash ARHD 53.0 . I will try this method in an hour or so and I will contact you after I'm done. Thank you for your help
Click to expand...
Click to collapse
no problem, and just in case (to avoid more unnecessary headaches) verify MD5 sum on all your downloads, and you should be good to go
Good Luck
nkk71 said:
no problem, and just in case (to avoid more unnecessary headaches) verify MD5 sum on all your downloads, and you should be good to go
Good Luck
Click to expand...
Click to collapse
How can I push the custom ROM zip file to the recovery so it can install it?
Torcidas1950 said:
How can I push the custom ROM zip file to the recovery so it can install it?
Click to expand...
Click to collapse
either:
1- OTG cabe
2- adb push
3- adb sideload
here's an example of push:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
nkk71 said:
either:
1- OTG cabe
2- adb push
3- adb sideload
here's an example of push:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
when I type "adb devices" my HTC One doesn't show up
Torcidas1950 said:
when I type "adb devices" my HTC One doesn't show up
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
FAQ#2
nkk71 said:
go here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
FAQ#2
Click to expand...
Click to collapse
When i pushed the ARHD.zip and tried to install it started and said fail, I tried with another version of TWRP and it said fail again.
Torcidas1950 said:
When i pushed the ARHD.zip and tried to install it started and said fail, I tried with another version of TWRP and it said fail again.
Click to expand...
Click to collapse
sounds like a bad download, please check the MD5 on the ARHD.zip file
nkk71 said:
sounds like a bad download, please check the MD5 on the ARHD.zip file
Click to expand...
Click to collapse
Maybe I will try tomorrow, now I'm going to sleep
I've just flashed ARHD 71.1 gone through aroma successfully but it fails to get past the 'HTC' screen (not boot animation). I have the correct build number Hboot 1.56 and s-on via HTC Dev
Sent from my HTC One using XDA Free mobile app
ShaheenXE said:
I've just flashed ARHD 71.1 gone through aroma successfully but it fails to get past the 'HTC' screen (not boot animation). I have the correct build number Hboot 1.56 and s-on via HTC Dev
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
You need to use TWRP 2.6.3.3 or 2.6.3.4 and have an M7_U or M7_UL model.
ShaheenXE said:
I've just flashed ARHD 71.1 gone through aroma successfully but it fails to get past the 'HTC' screen (not boot animation). I have the correct build number Hboot 1.56 and s-on via HTC Dev
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Post a fastboot getvar all,( minus imei & Serial no ) and a screenshot of your bootloader.
What recovery and version no are you using?
I am using CWM Touch Recovery version 6.0.4.8
Sent from my HTC One using XDA Free mobile app
ShaheenXE said:
I am using CWM Touch Recovery version 6.0.4.8
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
I now searching is hard :crying:, but if you had even bothered in the slightest to read the thread, almost every page says (including the OP!!):
You need to use TWRP 2.6.3.3 or 2.6.3.4 and have an M7_U or M7_UL model.
flash TWRP
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
MD5 72067aefb69541d40e8420d7aa46408d
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Enter recovery and try again
It pays to read the instructions on flashing a custom rom, found usually on the first page..
Sorry I am fairly new to this, what is OP? And if I install twrp will it definitely work?
Sent from my HTC One using XDA Free mobile app
ShaheenXE said:
Sorry I am fairly new to this, what is OP? And if I install twrp will it definitely work?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Original Poster or Original Post. Take a look at the top of this post, you are the original poster of this thread....
and YES... TWRP 2.6.3.3 or 2.6.3.4 will defiantly work
Ok I will test this and see if it works
Sent from my HTC One using XDA Free mobile app
IT WORKED!
It worked! Thanksss!!!
bored_stupid said:
original poster or original post. Take a look at the top of this post, you are the original poster of this thread....
And yes... Twrp 2.6.3.3 or 2.6.3.4 will defiantly work
Click to expand...
Click to collapse
bored_stupid said:
Original Poster or Original Post. Take a look at the top of this post, you are the original poster of this thread....
and YES... TWRP 2.6.3.3 or 2.6.3.4 will defiantly work
Click to expand...
Click to collapse
Hi I face a similar issue to OP with my international One, it says fastboot USB on my phone but using any toolkit shows that no devices are attached. Could you please guide me to a solution to flash twrp?
wilfred888 said:
Hi I face a similar issue to OP with my international One, it says fastboot USB on my phone but using any toolkit shows that no devices are attached. Could you please guide me to a solution to flash twrp?
Click to expand...
Click to collapse
Let me guess - you have windows 8.1 on your computer?
donkeykong1 said:
Let me guess - you have windows 8.1 on your computer?
Click to expand...
Click to collapse
I do, but I also tried using a computer with windows vista and face the exact same issues?
wilfred888 said:
I do, but I also tried using a computer with windows vista and face the exact same issues?
Click to expand...
Click to collapse
Known issue. Seach for latest fastboot drivers and install them on your PC without htc sync. That should do the trick. I have them on my laptop, but I'm not at home right now so I can't help you at this time
donkeykong1 said:
Known issue. Seach for latest fastboot drivers and install them on your PC without htc sync. That should do the trick. I have them on my laptop, but I'm not at home right now so I can't help you at this time
Click to expand...
Click to collapse
Thanks for your help, I'll install these:
http://forum.xda-developers.com/showthread.php?t=2588979
Are these the correct drivers? I'll edit my comment later to see if it works.
EDIT: I installed those drivers but it still has the same result with no ability to flash twrp, so maybe those aren't the right ones?
facing same issue
I'm facing a similar issue; installed ARHD 71.1 using TWRP 2.7 (then again using TWRP 2.6.3.3). Process I followed is like this:
1. Wipe System/Cache/Dalvick Cache/Data
2. Install ROM, complete the AROMA installer - says installed successfully
3. Wipe Cache/Dalvik Cache
4. Reboot
Bootloader is HTCDev unlocked, HBOOT 1.56, M7_UL is the type I have. I have tried several times, but the phone can't get past the HTC screen. I can boot into bootloader and into recovery too - both fastboot and adb working if required.
Any solution to be able to boot this ROM?
navsin said:
I'm facing a similar issue; installed ARHD 71.1 using TWRP 2.7 (then again using TWRP 2.6.3.3). Process I followed is like this:
1. Wipe System/Cache/Dalvick Cache/Data
2. Install ROM, complete the AROMA installer - says installed successfully
3. Wipe Cache/Dalvik Cache
4. Reboot
Bootloader is HTCDev unlocked, HBOOT 1.56, M7_UL is the type I have. I have tried several times, but the phone can't get past the HTC screen. I can boot into bootloader and into recovery too - both fastboot and adb working if required.
Any solution to be able to boot this ROM?
Click to expand...
Click to collapse
Post a fastboot getvar all ( minus imei & serial no ) and links to TWRP Recovery
Sent from my HTC One using Xparent Skyblue Tapatalk 2
bored_stupid said:
Post a fastboot getvar all ( minus imei & serial no ) and links to TWRP Recovery
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
C:\ASDK\sdk\platform-tools>fastboot getvar all
(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: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxx1
(bootloader) imei: xxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.048s
And the TWRP I use the teamwin's download pages on techerrata. Sorry, if you are asking for some other links. I'm not very well versed with this.
navsin said:
I'm facing a similar issue; installed ARHD 71.1 using TWRP 2.7 (then again using TWRP 2.6.3.3). Process I followed is like this:
1. Wipe System/Cache/Dalvick Cache/Data
2. Install ROM, complete the AROMA installer - says installed successfully
3. Wipe Cache/Dalvik Cache
4. Reboot
Bootloader is HTCDev unlocked, HBOOT 1.56, M7_UL is the type I have. I have tried several times, but the phone can't get past the HTC screen. I can boot into bootloader and into recovery too - both fastboot and adb working if required.
Any solution to be able to boot this ROM?
Click to expand...
Click to collapse
It takes few minutes for the first boot. If it doesn't boot try pressing power button till your phone shuts down. Second boot should work fine (at least it works for me every time)
donkeykong1 said:
It takes few minutes for the first boot. If it doesn't boot try pressing power button till your phone shuts down. Second boot should work fine (at least it works for me every time)
Click to expand...
Click to collapse
Thanks, but this does not work for me. Waited for like 10 minutes, rebooted multiple times... no luck
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
No one could help me?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please ensure you have a custom recovery (TWRP) and your bootloader is UNLOCKED if you are going to side load or push a custom rom onto your phone. If you are going to use the RUU route, then you need to have the bootloader LOCKED or RELOCKED. Here is a post that explains the steps to each method.
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
Click to expand...
Click to collapse
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done..
Click to expand...
Click to collapse
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery
Click to expand...
Click to collapse
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
tried push with adb a new system
Click to expand...
Click to collapse
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
FAILED
Click to expand...
Click to collapse
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
Click to expand...
Click to collapse
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
And my question is there a way to that my HTC One to get back to life?
Click to expand...
Click to collapse
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Soon as I get my HTC back from a friend ho want to try do it i will post everything thing that is needed with screenshots and errors
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
This is what i got on it in the white screen is Android revolution hd tring to bot(installed with otg cable and USB) the other 2 pictures are the the data from bootloader and the twrp recovery
Sent from my SM-N9005 using XDA Premium 4 mobile app
alray said:
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Click to expand...
Click to collapse
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Laurentiu27 said:
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
Click to expand...
Click to collapse
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
nkk71 said:
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
Click to expand...
Click to collapse
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
and tere is a few post earlier 3 pictures one about bootloader one about booting the rom and last is the twrp
this is the thread of the rom http://forum.xda-developers.com/showthread.php?t=2183023
Laurentiu27 said:
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Click to expand...
Click to collapse
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
alray said:
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
alray said:
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
error:device not found
update:seems that now is pushing it
flashed now waiting to boot
nkk71 said:
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
Click to expand...
Click to collapse
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Laurentiu27 said:
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Click to expand...
Click to collapse
check md5 and you'll know if its the right rom. must match the md5 value I posted above.
if it still dont work, do what nkk71 said above, format data cache and system. you'll have to push to rom again after formatting.
to format data, go in twrp, ''wipe'' ---> "Format data"
to format system and cache go in "wipe" --> advanced wipe --> select cache and system and swipe to wipe
then adb push the rom again and install it again.
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so does it boot or not?
alray said:
so does it boot or not?
Click to expand...
Click to collapse
thank you!!! Thank you!!! It worked!!!
Laurentiu27 said:
thank you!!! Thank you!!! It worked!!!
Click to expand...
Click to collapse
:highfive: