[Q] Boot Loop HELP - Only fastboot aviable! - HTC Incredible S

Hi everyone!
Here, I got a serious problem!
The other day, I was trying to get back my Incredible S to defaults ... It was S-off, routed, and runing the lastest version of cyangenmod and also had clockworkmod recovery ...
Here the thing: While not really knowing what I was doing, I "updated' it by using an official PG32IMG.zip file from my provider ( Bell ) ... Everything was looking good, until I restarted the phone after it was completed : I'm now stuck with a 3 seconds boot loop on the HTC logo.
I can still access my "recovery screen" ( Where I can choose FASTBOOT, of RECOVERY, ect... ), but the only thing here that works is fastboot ( RECOVERY and FACTORY RESET will only bring me back to the loop )
So, I tried a lot of things, without any success :
-Tried to reinstall CWM from fastboot : Done well, but the loop is still here ( even when I choose RECOVERY, it still brings me back to the loop )
-Tried to update by using an update zip file ( using fastboot update XXXX.zip ) by the only thing I got was this error message :
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now, I'm still stuck in my boot loop, and really don't know what to do!
Is there somebody here who could help me out??
Here all the informations I can see from my Incredible S :
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
radio-3805.04.03.27_M
eMMC-boot
Apr 1 2011,18:34:39
Thanks for helping me!!!!

rouxchauve said:
Hi everyone!
Here, I got a serious problem!
The other day, I was trying to get back my Incredible S to defaults ... It was S-off, routed, and runing the lastest version of cyangenmod and also had clockworkmod recovery ...
Here the thing: While not really knowing what I was doing, I "updated' it by using an official PG32IMG.zip file from my provider ( Bell ) ... Everything was looking good, until I restarted the phone after it was completed : I'm now stuck with a 3 seconds boot loop on the HTC logo.
I can still access my "recovery screen" ( Where I can choose FASTBOOT, of RECOVERY, ect... ), but the only thing here that works is fastboot ( RECOVERY and FACTORY RESET will only bring me back to the loop )
So, I tried a lot of things, without any success :
-Tried to reinstall CWM from fastboot : Done well, but the loop is still here ( even when I choose RECOVERY, it still brings me back to the loop )
-Tried to update by using an update zip file ( using fastboot update XXXX.zip ) by the only thing I got was this error message :
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now, I'm still stuck in my boot loop, and really don't know what to do!
Is there somebody here who could help me out??
Here all the informations I can see from my Incredible S :
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
radio-3805.04.03.27_M
eMMC-boot
Apr 1 2011,18:34:39
Thanks for helping me!!!!
Click to expand...
Click to collapse
Try flashing the CWM recovery.img file in FASTBOOT mode using the command:
fastboot flash recovery recovery.img
Also how exactly did you try to install Bell official PG32IMG.zp file? Is it possible you still have a PG32IMG.zp file on your SDcard which is getting run every time you try to get into the bootloader?

tpbklake said:
Also how exactly did you try to install Bell official PG32IMG.zp file? Is it possible you still have a PG32IMG.zp file on your SDcard which is getting run every time you try to get into the bootloader?
Click to expand...
Click to collapse
Aha...
Sent from my HTC Incredible S using XDA App

tpbklake said:
Try flashing the CWM recovery.img file in FASTBOOT mode using the command:
fastboot flash recovery recovery.img
Also how exactly did you try to install Bell official PG32IMG.zp file? Is it possible you still have a PG32IMG.zp file on your SDcard which is getting run every time you try to get into the bootloader?
Click to expand...
Click to collapse
As I said in my first post, I've already tried to flash CWM using fastboot but it did nothing, sadly ( The instalation went well, but the loop is still there )
Else, I installed my PG32IMG.zip dirrectly by puting it on the root of my SD card, so it installed automaticly when i went back on recovery .... but I deleted the file after the installation, so that's not the problem ....
Since the loop appeared after updating PG32IMG.zip, I think the problem sould be around this.... I tried reinstaling it ( to make sure it installed correctly the first time ) and I did nothing... I also tried other Radios ( PG32IMG.zip ) but every other I tried wasn't compatible...
Any other ideas???

rouxchauve said:
As I said in my first post, I've already tried to flash CWM using fastboot but it did nothing, sadly ( The instalation went well, but the loop is still there )
Else, I installed my PG32IMG.zip dirrectly by puting it on the root of my SD card, so it installed automaticly when i went back on recovery .... but I deleted the file after the installation, so that's not the problem ....
Since the loop appeared after updating PG32IMG.zip, I think the problem sould be around this.... I tried reinstaling it ( to make sure it installed correctly the first time ) and I did nothing... I also tried other Radios ( PG32IMG.zip ) but every other I tried wasn't compatible...
Any other ideas???
Click to expand...
Click to collapse
OK which version of the BM RUU did you try to use? If you tried to go back to the 1.37.666.3 version I believe that is a Froyo version and since you had been running CM 7.1 then you had a Gingerbread radio installed and you cannot downgrade the radio back to a Froyo radio, even with a RUU.
If that is the case, then you might try flashing the 2.28.666.3 RUU.

tpbklake said:
OK which version of the BM RUU did you try to use? If you tried to go back to the 1.37.666.3 version I believe that is a Froyo version and since you had been running CM 7.1 then you had a Gingerbread radio installed and you cannot downgrade the radio back to a Froyo radio, even with a RUU.
If that is the case, then you might try flashing the 2.28.666.3 RUU.
Click to expand...
Click to collapse
OMG!!!!!! Ok that worked!!! I was soooo desesperated lool.. THATKS A LOT!

rouxchauve said:
OMG!!!!!! Ok that worked!!! I was soooo desesperated lool.. THATKS A LOT!
Click to expand...
Click to collapse
Glad it worked, glad to help.

Same problem, please help!
rouxchauve said:
Hi everyone!
Here, I got a serious problem!
The other day, I was trying to get back my Incredible S to defaults ... It was S-off, routed, and runing the lastest version of cyangenmod and also had clockworkmod recovery ...
Here the thing: While not really knowing what I was doing, I "updated' it by using an official PG32IMG.zip file from my provider ( Bell ) ... Everything was looking good, until I restarted the phone after it was completed : I'm now stuck with a 3 seconds boot loop on the HTC logo.
I can still access my "recovery screen" ( Where I can choose FASTBOOT, of RECOVERY, ect... ), but the only thing here that works is fastboot ( RECOVERY and FACTORY RESET will only bring me back to the loop )
So, I tried a lot of things, without any success :
-Tried to reinstall CWM from fastboot : Done well, but the loop is still here ( even when I choose RECOVERY, it still brings me back to the loop )
-Tried to update by using an update zip file ( using fastboot update XXXX.zip ) by the only thing I got was this error message :
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now, I'm still stuck in my boot loop, and really don't know what to do!
Is there somebody here who could help me out??
Here all the informations I can see from my Incredible S :
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
radio-3805.04.03.27_M
eMMC-boot
Apr 1 2011,18:34:39
Thanks for helping me!!!!
Click to expand...
Click to collapse
==========================
I have the same problem. Could you please explain me step by step how you fix that. You said that you flash the radio for a previous version of android, I tried but it didn't work.
I'm with Bell and I tried to downgrade using the RRU but without downgrading the Radio.
Please help,

might help to run the bell ruu
Sent from my Incredible S using xda app-developers app

This is what I did running the RUU (RUU_Vivo_BellMobility_WWE_1.37.666.3_Radio_Radio_20.23.30.0802U_38.02.01.17_M_release_174461_signed.exe) and after this my phone is stuck on the logo loop problem. I'm not able to run recovery, only fastboot is available.
I tried to flash recovery but without success. Any ideas?
Thx

chris_Andrew said:
This is what I did running the RUU (RUU_Vivo_BellMobility_WWE_1.37.666.3_Radio_Radio_20.23.30.0802U_38.02.01.17_M_release_174461_signed.exe) and after this my phone is stuck on the logo loop problem. I'm not able to run recovery, only fastboot is available.
I tried to flash recovery but without success. Any ideas?
Thx
Click to expand...
Click to collapse
What version of Android were you running on your phone prior to trying to flash this RUU 1.37.666.3?
If you were running a Gingerbread ROM of 2.2.1 or greater than you probably had a GB radio and this RUU is a Froyo ROM with a Froyo radio.

Related

[Q] Unable to flash inc s

Hi
Due to a bootloop on my Inc S running Cyanogen 7 i wanted to flash a new recovery and a new os. But when I try to flash the image via fastboot, the message "FAILED (remote: Image update error)" appears. It's also impossible to erase partitions via fastboot due to an "erasing error". I tried to flash with adb, but the device isn't listed in adb devices .
I also tried to update HBOOT from version 6.13.1002 to 2.00.0000 using a PG32IMG.zip on the sd card, but it hangs on the "Dont power off" dialog.
I'd be happy if someone could help me out...
Thanks and greez
visosilver
Visosilver said:
Hi
Due to a bootloop on my Inc S running Cyanogen 7 i wanted to flash a new recovery and a new os. But when I try to flash the image via fastboot, the message "FAILED (remote: Image update error)" appears. It's also impossible to erase partitions via fastboot due to an "erasing error". I tried to flash with adb, but the device isn't listed in adb devices .
I also tried to update HBOOT from version 6.13.1002 to 2.00.0000 using a PG32IMG.zip on the sd card, but it hangs on the "Dont power off" dialog.
I'd be happy if someone could help me out...
Thanks and greez
visosilver
Click to expand...
Click to collapse
Since you have Rvolutionary S-Off, you cannot simply overwrite the HBOOT with stock 2.00.0000. You need to follow this procedure:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
Then you would able to use the PG32IMG.zip.
I actually dont wan't to get S-ON, but do you think that it will be possible to flash a new recovery and rom after updating the HBOOT?
If your bricked than its definately worth trying. Sounds to me like your internal memory has some kind of error on it if you can't wipe. And it might not be hung when you try to flash the pg32 as it as it says don't power off and you did anyway you might own an unbrickable phone.
Sent from my Incredible S using xda premium
Visosilver said:
I actually dont wan't to get S-ON, but do you think that it will be possible to flash a new recovery and rom after updating the HBOOT?
Click to expand...
Click to collapse
That depends on if you can update the HBOOT. In order to make your current HBOOT 6.13.1001 overwritable, you need to follow the procedure steps 1-2d in the procedure I posted.
If that doesn't work, then there is no sense trying to go on. As the previous posted suggested there is something wrong with your phone's partitions.
If it does work, then I would defintely run a stock RUU to get back to a known working state.
thank you for your answers, i just tried the procedure.
Since the first link is down i wasn't able to install the RUU, so i just tried the second step but i got again the "remote: image update error"
Does this mean my phone is definitely bricked?
Visosilver said:
thank you for your answers, i just tried the procedure.
Since the first link is down i wasn't able to install the RUU, so i just tried the second step but i got again the "remote: image update error"
Does this mean my phone is definitely bricked?
Click to expand...
Click to collapse
Yes it appears that you are unable to flash any of the partitions on your phone, including the HBOOT partition.
Do you have another PC and USB cable to try just to rule out that those aren't causing an issue? If you do, make sure you have the latest HTC drivers installed.
didn't work but thanks for your help anyway
greez visosilver
Visosilver said:
didn't work but thanks for your help anyway
greez visosilver
Click to expand...
Click to collapse
There's no harm in trying a ruu
Sent from my Incredible S using xda premium
try fastboot boot recovery.img
where recovery.img is the recovery image CWM or 4EXT
this wont flash the image..i will just push the recovery on your mobile and then would start it..then try to format all the partions
and can u provide us with all details..like exactly how the error happened..???
and is your phone under warranty..??
i just tried to boot the cwm via fastboot.
the phone vibrated 8 times, three android dudes on a skateboard appeared and the phone rebooted into HBOOT.
I tried also this RUU: http://forum.xda-developers.com/showthread.php?t=1705913, but it results in a 171 USB Error...
The phone isn't under varranty anymore.
How the error occured: I was browsing around, when suddenly whatsapp crashed. So i rebooted the phone and it was stuck in a bootloop. Then i tried to flash a new rom and the error occured
edit: after following to this guide here http://community.htc.com/na/htc-forums/android/f/113/t/10043.aspx, i was able to flash the device using the RUU. But I couldn't use the phone due to crashing processes (mostly android.process.arcore), so I rebooted. Now the phone is stuck again in a bootloop...
try installing the RUU again...and if possible if you are installing a custom rom please wipe all partition ,cache and dalvik cache...
and try booting the mobile withouth the sim card...lets see if it works
i just tried it, with the same result

HELP! Stuck on HTC quietly brillant boot screen

Hi Guys,
My heads sorta spinning from information overload so I'm hoping one of you guys can help me. I have a Incredible S and I used this guide to downgrade my HBOOT and get my S-OFF using revolutionary and flash clockwork, which I did successfully. I then decided to install this ROM which requires Blackrose. So I installed blackrose beta sucessfully overwriting the revolutionary HBOOT. This is where it all starts to go wrong. I then set about doing a full wipe and tried to install the ROM using Clockwork and the installation completed sucessfully. But when I try to boot up my phone I get stuck at the HTC quietly brilliant screen. I also restored a backup I took with Clockwork with the same results; stuck at the boot screen. I tried following the steps in the thread of the ROM (listed below) with no avail.
Here are some steps you can try if the ROM hangs on the HTC splash screen
1. Download the file lib.zip from here: http://bit.ly/PwK4BH (MD5 SUM: 83dd68b32d39c994b3069d8813b3c3ea)
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Wipe Data/System Reset.
5. Wipe Dalvik Cache.
6. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_8.zip
Do any of you guys have any suggestions or know whats wrong? Even if I can get back to the latest stock ROM while preserving my root I would be happy.
Thanks Guys!!!
BTW i would have posted in the rom thread on I dont have enough posts :crying:
No need blackrose on this rom. Just flash and install rom if you S-On flash boot.img manual via adb flash.
Before, i ve used that rom & back to my prev rom like Stock and Nik Rom.
++no need blackrose++
Sent from my HTC Incredible S using xda app-developers app
wesly.btm said:
No need blackrose on this rom. Just flash and install rom if you S-On flash boot.img manual via adb flash.
Before, i ve used that rom & back to my prev rom like Stock and Nik Rom.
++no need blackrose++
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
It says in the ROM thread "This ROM requires that you upgrade Revolutionary HBOOT 6.13.to BlackRose 2.02.0002 because of space issues with the ICS /system partition."
4.
prodlad said:
It says in the ROM thread "This ROM requires that you upgrade Revolutionary HBOOT 6.13.to BlackRose 2.02.0002 because of space issues with the ICS /system partition."
Click to expand...
Click to collapse
What version of HBOOT does your phone now show?
Did the flashing of thr lib.img in FASTBOOT USB mode show any errors?
What is the exact file name of the vivo_signed_WWE_4.10.405.1_ICS_SENSE36 rom?
Which version of ClockworkMod are you using?
Things have went from bad to worse. I uninstalled blackrose now I'm back to revolutionary hboot 1.13.0000. But now I cannot boot at all or even get to the white htc screen. I am stuck in bootloader and have lost recovery. Thereby my phone will not charge enough to accept a RRU. I tried to reflash recovery by fastboot but I keep getting a Remote:signature verify fail error Have I bricked my phone? :crying::crying::crying:
prodlad said:
Things have went from bad to worse. I uninstalled blackrose now I'm back to revolutionary hboot 1.13.0000. But now I cannot boot at all or even get to the white htc screen. I am stuck in bootloader and have lost recovery. Thereby my phone will not charge enough to accept a RRU. I tried to reflash recovery by fastboot but I keep getting a Remote:signature verify fail error Have I bricked my phone? :crying::crying::crying:
Click to expand...
Click to collapse
The only option you have at this point is to flash an official PG32IMG.zip file extracted from a RUU and copy it to your SD card. Then when you boot into bootloader it will find the file, flash it and that should get you going.
It sound like you need to use the 2.30.405.1 RUU from here:
http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199308_signed.exe
DUDE! This is no lie. You are a legend!!! That worked. I had myself prepared for buying a new phone!!!!!!!!!!! THANKS SO MUCH

[Q&A] [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013

[Q&A] [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Q&A for [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Stuck in bootloader/recovery, Return to stock
Hello!
First post here so please be nice
77_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.29.3218.08
openDSP-v32.120.274.0909
OS-6.09.401.5
eMMC-boot 2048MB
Jul 28 2014,18:52:08.0
I've got a problem with my HTC ONE m7
Tried to install ARHD 81.
So I unlocked the bootloader, installed TWRP and then flashed the ROM.
Rebooted the phone and it stuck to the white HTC loading screen.
Waited for about 20mins. then rebooted the phone. tried flashing the ROM again but no luck there.
So then I did a recovery cache wipe, flashed the recovery, and flashed the ROM again but still stuck.
In desperation I did a wipe... and deleted the actual ROM.zip.
Now I've tried to Sideload the .zip (and original oexed) but get stuck/fail when nearly done.
I've tried to download all the "EU" RUU's and install them but get either error 170 (USB) or error 155 (unknown)
Also tried to download RUU.zip but that didn't work either.
So now i'm stuck! If anyone could point me in the right direction that would be great!
Thanks!
0413Fixxer said:
Hello!
First post here so please be nice
77_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.29.3218.08
openDSP-v32.120.274.0909
OS-6.09.401.5
eMMC-boot 2048MB
Jul 28 2014,18:52:08.0
I've got a problem with my HTC ONE m7
Tried to install ARHD 81.
So I unlocked the bootloader, installed TWRP and then flashed the ROM.
Rebooted the phone and it stuck to the white HTC loading screen.
Waited for about 20mins. then rebooted the phone. tried flashing the ROM again but no luck there.
So then I did a recovery cache wipe, flashed the recovery, and flashed the ROM again but still stuck.
In desperation I did a wipe... and deleted the actual ROM.zip.
Now I've tried to Sideload the .zip (and original oexed) but get stuck/fail when nearly done.
I've tried to download all the "EU" RUU's and install them but get either error 170 (USB) or error 155 (unknown)
Also tried to download RUU.zip but that didn't work either.
So now i'm stuck! If anyone could point me in the right direction that would be great!
Thanks!
Click to expand...
Click to collapse
Looks like you did not flashed arhd using twrp version 2.6.3.3.
flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery and adb push arhd:
Code:
adb push name_of_rom.zip /sdcard/
command prompt will be unresponsive for the duration of the push (5-15 min)
then in twrp 2.6.3.3 select "install" and browse to find arhd zip file, select it and swipe to flash then reboot phone.
forget about using a RUU because all RUU available for your phone require S-OFF. (downgrade)
Thank you so very much!
Works brilliantly now!!
Cheers mate! :highfive:
Waiting for device msg after recovery boot
Hi. Please, help me.
So I unlocked my M7 successfully. Then I've tried to make a recovery - I used CWM: recovery-clockwork-touch-6.0.4.8-m7.
But something went wrong. Here's log:
C:\mini-sdk>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... OKAY
But nothing happened, just screen with "root menu". I tried volume up and down - nothing. Power button - nothing. When I repeated command I got:
C:\mini-sdk>fastboot boot recovery.img
< waiting for device >
What can I do now? Why it went wrong?
In fact I don't even know what was my Android or Sense version after unlocking.
terhie said:
Hi. Please, help me.
So I unlocked my M7 successfully. Then I've tried to make a recovery - I used CWM: recovery-clockwork-touch-6.0.4.8-m7.
But something went wrong. Here's log:
C:\mini-sdk>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... OKAY
But nothing happened, just screen with "root menu". I tried volume up and down - nothing. Power button - nothing. When I repeated command I got:
C:\mini-sdk>fastboot boot recovery.img
< waiting for device >
What can I do now? Why it went wrong?
In fact I don't even know what was my Android or Sense version after unlocking.
Click to expand...
Click to collapse
you can't boot recovery unless your on hboot 1.44
you have to flash the recovery to the phone to boot to it
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
clsA said:
you can't boot recovery unless your on hboot 1.44
you have to flash the recovery to the phone to boot to it
Click to expand...
Click to collapse
Oh, right! Thanks! My phone is working again.
@clsA
I rather ask than be sorry, so...
After my newbie recovery flashing I have now TWRP and CWM recoveries. How can I delete them (then I'd like to flash CWM once and proper)?
An second question: I'm not sure how to choose between recovery mode and standard. When I want to get to recovery I do it through fastboot. But is it enough to power down if in recovery and power up for standard mode?
Edit:
When in CW Manager I go to recovery mode I recover in TWRP recovery instead of CWM.
terhie said:
@clsA
I rather ask than be sorry, so...
After my newbie recovery flashing I have now TWRP and CWM recoveries. How can I delete them (then I'd like to flash CWM once and proper)?
An second question: I'm not sure how to choose between recovery mode and standard. When I want to get to recovery I do it through fastboot. But is it enough to power down if in recovery and power up for standard mode?
Edit:
When in CW Manager I go to recovery mode I recover in TWRP recovery instead of CWM.
Click to expand...
Click to collapse
you don't have both recovery's ..when you installed TWRP it overwrites any other recovery. If your goal is to flash roms you want TWRP 2.6.3.3 on their.
What is CW Manager and why do you need it ?
clsA said:
you don't have both recovery's ..when you installed TWRP it overwrites any other recovery. If your goal is to flash roms you want TWRP 2.6.3.3 on their.
What is CW Manager and why do you need it ?
Click to expand...
Click to collapse
Clockwork ROM Manager. It showed both recoveries - TWRP and CWM. But then I flashed Stock Recovery, then TWRP 2.6.3.3, then ROM, then again... Well, after few hours of searching, trying, learning differences between flash and boot, and adrenaline kicks when my HTC One didn't boot or stuck somewhere I manage to flash ARHD ROM. I'm quite proud of myself. I wonder though how much trash I left on phone after all of this (yeah, we girls like to have everything in order...)
And if I can - few more questions
I noticed that battery drain is much faster - I probably should calibrate it. Is there a best-for-ARHD-app, or any should be ok?
And in some apps, like Goodreads, I have now additional menu bar at the bottom. I'm sure there is some mode for removing it (specially if stock can do that), but I can't find it.
terhie said:
Clockwork ROM Manager. It showed both recoveries - TWRP and CWM. But then I flashed Stock Recovery, then TWRP 2.6.3.3, then ROM, then again... Well, after few hours of searching, trying, learning differences between flash and boot, and adrenaline kicks when my HTC One didn't boot or stuck somewhere I manage to flash ARHD ROM. I'm quite proud of myself. I wonder though how much trash I left on phone after all of this (yeah, we girls like to have everything in order...)
And if I can - few more questions
I noticed that battery drain is much faster - I probably should calibrate it. Is there a best-for-ARHD-app, or any should be ok?
And in some apps, like Goodreads, I have now additional menu bar at the bottom. I'm sure there is some mode for removing it (specially if stock can do that), but I can't find it.
Click to expand...
Click to collapse
Theirs no left over trash on the phone (except the CW rom manager)
the phone works with partitions. Only one thing can occupy the partition at a time. Whatever you flashed last is all that's their.
The menu bar you mention is only their on GPe roms .. is this what your using ? Their should be no menu bar using ARHD 81
clsA said:
The menu bar you mention is only their on GPe roms .. is this what your using ? Their should be no menu bar using ARHD 81
Click to expand...
Click to collapse
I'm using ARHD 82. I read the FAQ and I think it is that menu (although looks different than on stock Sense6):
http://forum.xda-developers.com/showthread.php?t=2183023 said:
9. How do I get rid of the 3-dot-menu?
As of the 4.2.2 update HTC introduced the Long-press-home-as-menu functionality, which also removes the black menu bar. Activate it under Settings -> Display -> Home Button.
Click to expand...
Click to collapse
but I don't have this option there.
terhie said:
I'm using ARHD 82. I read the FAQ and I think it is that menu (although looks different than on stock Sense6):
but I don't have this option there.
Click to expand...
Click to collapse
It must be a really bad coded app ..that menu was gone by version 4.3 and your Rom is version 4.4.3 - 6.09.401.10
clsA said:
It must be a really bad coded app ..that menu was gone by version 4.3 and your Rom is version 4.4.3 - 6.09.401.10
Click to expand...
Click to collapse
Yeah, they probably don't care about updating to Google changes. But it's not the same menu as 3 dot menu on Stock which was easy to hide. It's not really menu for an app, 3 dots button doesn't even work and rest of buttons is for phone navigation. Any ideas how to hide it?
Guys, I apologize in advance if this is wrong section for my question but it seems my searching powers are not as good as they used to be
I need help regarding HTC One M7_ul 801s PN0714000
This phone has problems with google processes being stopped and it has all kind of chinese apps and bloatware and I would like to install an european rom on it...Phone is s-offed, it has supercid and modelid is PN0711****
Now, I managed to find one kitkat zip file and tried to flash it with "fastboot flash zip" command but i keep getting remote:02 data length is too large...I tried renaming it to PN0714IMG.zip, it didn't help as well...
Is there anything else I should do(beside s-off and supercid) to be able to flash any rom on it, and should I rather go with RUU exe file...if so, can someone please point me out to a place where I can download official roms...I noticed that htc1gury is down...
One more thing, bootloader is locked, phone is not rooted and has no custom recovery installed, and I would like to keep it that way if possible...supercid and s-off were done with Java card, if it is an important info at all...
Please, let me know where I'm making a mistake and if you need any additional info....I apologize one more time if this is a wrong thread or if the answer was so obvious and I was so blind to find it
Tnx in advance....
will method 1 works on HTC one M8 ?
and if .. will i receive OTA update ?
Hello there,
today I tried to install a Custom ROM on my M7 for the first time.
So I unlocked my device with htcdev.com. Btw: it wasn't possible to skip step 11 and I'm using Mac.
So my device is currently unlocked with S-ON (as it can be seen in bootloader).
I want to flash custom recovery and my problem is step 7. ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)").
When I try this command (on Mac: fastboot-mac), my phone freezes with both ClockworkMod Touch [OFFICIAL] and TWRP. My hboot version is 1.61, maybe that's the problem as mentioned. But I don't want to flash a recovery, maybe I can't use that device after doing that.
Any tips for me?
Best regards
inspi83 said:
Hello there,
today I tried to install a Custom ROM on my M7 for the first time.
So I unlocked my device with htcdev.com. Btw: it wasn't possible to skip step 11 and I'm using Mac.
So my device is currently unlocked with S-ON (as it can be seen in bootloader).
I want to flash custom recovery and my problem is step 7. ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)").
When I try this command (on Mac: fastboot-mac), my phone freezes with both ClockworkMod Touch [OFFICIAL] and TWRP. My hboot version is 1.61, maybe that's the problem as mentioned. But I don't want to flash a recovery, maybe I can't use that device after doing that.
Any tips for me?
Best regards
Click to expand...
Click to collapse
"fastboot boot recovery.img" was only possible on hboot 1.44. Flash your recovery using "fastboot flash recovery recovery.img". Use latest TWRP recovery.
thx, it worked. phew
Hello guys,
im new to the HTC world, mostly familiar with Sony devices, have a friend who has given me their HTC which isn't booting up, it only boots to the start screen then goes blank, she told me the phone was charging and there was a power surge wherever she was and since then the device misbehaves and doesn't boot past the start screen.
how can I flash it back to stock, as from my experience it seems like its a software issue.

Stuck at white HTC screen at boot after OTA

Hello,
I just installed latest OTA with security fixes and after reboots it's stuck at the white HTC screen.
I'm s-off, relocked and have custom recovery.
How to get into android without losing data?
Thanks in advance
mderksen said:
Hello,
I just installed latest OTA with security fixes and after reboots it's stuck at the white HTC screen.
I'm s-off, relocked and have custom recovery.
How to get into android without losing data?
Thanks in advance
Click to expand...
Click to collapse
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
help plz
donkeykong1 said:
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
Click to expand...
Click to collapse
i am facing the same problem.. i downloaded it frm settings>about>software update..
i was running teamwin recovery.. it failed to install..
thn i flashed stock recovery..
thn installed the ota frm software updates...
btw now my phn is stuck on the boot screen... plz hlp...
HTC M7UL
ROOTED
i was running 7.19.401.22
I'm facing the same problem: Stuck on white HTC screen.
1. Saw the notice for the OTA update for 7.19.401.30.
2. Since I was running Teamwin, reflashed 7.19.401.22 stock firmware.
3. Installed OTA 7.19.401.30.
4. Stuck on black screen (nothing on it, but illuminated)
5. Factory Reset.
6. Stuck on white HTC screen.
donkeykong1 said:
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
Click to expand...
Click to collapse
The normal way. I got a new update message on Android. I downloaded it and let it install. It rebooted twice or three times and now after boot it's stuck at the HTC white screen.
The only thing i could imagine is the custom recovery (twrp teamwin) which should be replaced by stock before i ran the update.
Now i see reflashing stock recovery in the replies here is not helping people either...
Same here.
Unlocked, S-Off, Stock 7.19.401.22 Rom and recovery . White Screen after applying the update.
Any hints?
Same problem here.
1. Running stock ROM, downloaded OTA.
2. Flashed stock recovery 7.19.401.22 via fastboot.
3. Installed OTA (default software update tool).
4. Device rebooted into recovery, installed, rebooted.
5. Stuck at htc one logo (white screen).
Is rooted, S-ON.
khfaisal994 said:
i am facing the same problem.. i downloaded it frm settings>about>software update..
i was running teamwin recovery.. it failed to install..
thn i flashed stock recovery..
thn installed the ota frm software updates...
btw now my phn is stuck on the boot screen... plz hlp...
HTC M7UL
ROOTED
i was running 7.19.401.22
Click to expand...
Click to collapse
muschi.muscholini said:
I'm facing the same problem: Stuck on white HTC screen.
1. Saw the notice for the OTA update for 7.19.401.30.
2. Since I was running Teamwin, reflashed 7.19.401.22 stock firmware.
3. Installed OTA 7.19.401.30.
4. Stuck on black screen (nothing on it, but illuminated)
5. Factory Reset.
6. Stuck on white HTC screen.
Click to expand...
Click to collapse
Jorgo-Bo said:
Same here.
Unlocked, S-Off, Stock 7.19.401.22 Rom and recovery . White Screen after applying the update.
Any hints?
Click to expand...
Click to collapse
An3skmbi said:
Same problem here.
1. Running stock ROM, downloaded OTA.
2. Flashed stock recovery 7.19.401.22 via fastboot.
3. Installed OTA (default software update tool).
4. Device rebooted into recovery, installed, rebooted.
5. Stuck at htc one logo (white screen).
Is rooted, S-ON.
Click to expand...
Click to collapse
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Thanks for your explanation. I did a RUU reset with 7.19.401.22 signed zip. After that i installed the update. All fine now. Phone is up and running again.
alray said:
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Click to expand...
Click to collapse
thanks dear dev... i was thinking of doing so.. but i have something important on my phone storage... now am backing up those files using adb... thn am going for it....
many many thanks...
alray said:
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Click to expand...
Click to collapse
weird, i just looked at the updater-script, and everything looks normal, first it checks all the files then performs the patches if everything matches.... did you ever figure out what the culprit was?
nkk71 said:
weird, i just looked at the updater-script, and everything looks normal, first it checks all the files then performs the patches if everything matches.... did you ever figure out what the culprit was?
Click to expand...
Click to collapse
No I did not looked at it yet. I just remember it was the same scenario with the previous ota:
Unlocked BL + custom recovery + stock rooted rom
restored stock recovery
downloaded and installed the ota update, no error during the update process
reboot and stuck at htc boot screen
I remember many ppl were having the same issue early June in the update thread, I have also experienced the same issue from 7.17.1540.7 to .21
(stock rooted, flashed back stock recovery, installed the update and phone stuck at HTC boot screen. Waited a lot thinking it was only the cache being rebuilt but after an hour, still not booted).
Very strange
Same here. I´ve installed the patch via OTA, all was running fine but the boot at the end stops at the white HTC screen.
OS 7.19.401.30, no root
I´ve tried start with power butten, out of the recovery the boot, even today a factory reset was without success. And the phone isn´t recognized by pc.
What should I do to get a working phone again?
Greetings mammaonecat
mammaonecat said:
Same here. I´ve installed the patch via OTA, all was running fine but the boot at the end stops at the white HTC screen.
OS 7.19.401.30, no root
I´ve tried start with power butten, out of the recovery the boot, even today a factory reset was without success. And the phone isn´t recognized by pc.
What should I do to get a working phone again?
Greetings mammaonecat
Click to expand...
Click to collapse
How long did you waited, first boot after an ota update can take longer (10 mins) than usual. Is your booloader unlocked/locked/re-locked?
Could someone provide me with a Nandroid backup of 7.19.401.30?
alray said:
How long did you waited, first boot after an ota update can take longer (10 mins) than usual. Is your booloader unlocked/locked/re-locked?
Click to expand...
Click to collapse
More than 30 minutes. The bootloader is locked. S-Off.
I´ve found also this: Android system recovery <3e>
LRX22G release-keys
E: missing bitmap oem_unlock_bg (Code -1)
E: missing bitmap oem_unlock_bg_yes
E: missing bitmap oem_unlock_bg_no
E: missing bitmap icon ruu (Code-1).
Greetings mammaonecat
I could not recover my data in any way... Tried whole saturday.
Just flashed RUU again and OTA's. The last OTA went fine now. After last OTA i rooted the phone again.
please give me the full stock rom of htc one m7 7.19.401.30 because i fail to flash the new update 186 mb patches... i do evry thing but i when the phone reboot to recovery mode he abrot the instalation of the update notes i m s-on i instal aroma stuck recovery and i relock the bootloader because unloking bootloader give nothing plz help
Hello everyone,
I'm having the same problem. I have an international HTC One M7. My OTA half worked (I put the stock recovery before flash), and now my phone says "7.19.401.30" when I'm in the bootloader. I am S-ON with unlocked.
Can I flash a RUU (zip format) with an older version (7.19.401.22) ? Is it possible ?
Other information, when I go into the stock recovery, I have lines of errors. Something like this :
E:missing bitmap oem_unlock_bg
E:missing bitmap oem_unlock_bg_yes
E:missing bitmap oem_unlock_bg_no
PS : I tried a usual .exe RUU but it failed.
Thanks for your help.
Loweack said:
Hello everyone,
I'm having the same problem. I have an international HTC One M7. My OTA half worked (I put the stock recovery before flash), and now my phone says "7.19.401.30" when I'm in the bootloader. I am S-ON with unlocked.
Can I flash a RUU (zip format) with an older version (7.19.401.22) ? Is it possible ?
Other information, when I go into the stock recovery, I have lines of errors. Something like this :
E:missing bitmap oem_unlock_bg
E:missing bitmap oem_unlock_bg_yes
E:missing bitmap oem_unlock_bg_no
PS : I tried a usual .exe RUU but it failed.
Thanks for your help.
Click to expand...
Click to collapse
I had the same problem. I installed the 7.19.401.22 zip from a connected USB-stick with CWM recovery and my phone booted again with all my settings and apps as they were before the update (apart from supersu)

HTC One m7 loop, no recovery, no debug, no hope

Hello!
I got big problems with my HTC ONE M7.
In September I flashed Cyanogenmod 12.1 on the device.
The ROM coused some problems with one of aplications important to me so I decided to go back to stock.
Then problems arised.
I could not go back to stock. Tried several methods. Any of them worked.
Today I tried HTC Guru's way: Guru Reset one from htc1guru.com
I flashed TWRP recovery instead of Cyanogeon one.
It installed properly. Wiped cache, dalvik, system
Then I run GuruReset file from my SD card. Stock ROM installed properly, without errors. Phone booted in stock, made first customisation steps, locked bootloader and waited for OTA.
Then some problem with WIFI occured so I put a SIM card inside phone and downloaded OTA. Phone was in stock, with SIM working properly. In downloaded and started to install.
After install phone reboot and... started to loop.
Worse, phone cannot go into recovery. It boots into bootloader but cannot go into recovery. After install there were no USB debugging ON.
So situation is:
- phone is without USB debug (no fastboot usb, only fastboot)
- cannot enter recovery: when i try there is red exlamation mark in some geometrical figure after 2-3 minutes phone reboots itself and loops.
- there is loop when system loads: white HTC logo, several seconds, reboot.
I run of options, my limited knowledge of Android left me helpless here.
Is there a way to run recovery?
Phone is HTC ONE M7, LTE edition
As I read before it was (under CM 12.1) PN710000, CID 032
Bootloader:
Tampered, relocked
M7_UL PVT SHIP S-ON RH
HBOOT - 1.61.0000
Radio-4T.35.3218.16
OPENDSP-V35.120.274.0718
OS- (7.19.401.2) <--- this is in red color
eMMc- boot 2048 MB
Feb 12.2015
The goal was to return to stock not to brick...
Help me please step by step how to make phone work.
Lustenmord said:
Hello!
I got big problems with my HTC ONE M7.
In September I flashed Cyanogenmod 12.1 on the device.
The ROM coused some problems with one of aplications important to me so I decided to go back to stock.
Then problems arised.
I could not go back to stock. Tried several methods. Any of them worked.
Today I tried HTC Guru's way: Guru Reset one from htc1guru.com
I flashed TWRP recovery instead of Cyanogeon one.
It installed properly. Wiped cache, dalvik, system
Then I run GuruReset file from my SD card. Stock ROM installed properly, without errors. Phone booted in stock, made first customisation steps, locked bootloader and waited for OTA. ---> Locking the bootloader wasn't required to receive ota updates
Then some problem with WIFI occured so I put a SIM card inside phone and downloaded OTA. Phone was in stock, with SIM working properly. In downloaded and started to install.
After install phone reboot and... started to loop. ---> Probably because you have used the wrong guru reset rom version and that installing the ota caused problems.
Worse, phone cannot go into recovery. It boots into bootloader but cannot go into recovery. After install there were no USB debugging ON. ---> USB debugging doesn't matter. when the phone isn't booted in the system you don't need usb debug to connect to the phone.
So situation is:
- phone is without USB debug (no fastboot usb, only fastboot) ---> Most likely a driver issue, re-install the latest drivers so you can have a "fastboot usb" connection. this is your #1 priority.
- cannot enter recovery: when i try there is red exlamation mark in some geometrical figure after 2-3 minutes phone reboots itself and loops. --> this is the stock recovery splash screen (the exclamation mark inside a triangle). You have tu use volume up and power to reveal the menu, anyway there is nothing useful to do in stock recovery for your situation.
- there is loop when system loads: white HTC logo, several seconds, reboot. ---> You should be able to flash the 7.19.401.2 ruu but it will requires to fix the "fastboot usb" issue first.
I run of options, my limited knowledge of Android left me helpless here.
Is there a way to run recovery?
Phone is HTC ONE M7, LTE edition
As I read before it was (under CM 12.1) PN710000, CID 032
Bootloader:
Tampered, relocked
M7_UL PVT SHIP S-ON RH
HBOOT - 1.61.0000
Radio-4T.35.3218.16
OPENDSP-V35.120.274.0718
OS- (7.19.401.2) <--- this is in red color ----> that mean the firmware didn't updated successfully and that the phone is waiting for the firmware to be updated.
eMMc- boot 2048 MB
Feb 12.2015
The goal was to return to stock not to brick...
Help me please step by step how to make phone work.
Click to expand...
Click to collapse
read comments in red in above quote.
Thank you.
I will try to restore fastboot usb.
May you point me to apriopriate ROM for my device?
The red fragment in bootloader- which indicates bad firmware installation- was already just after Cyanogen install. So the problem started before i tried to go back to stock.
I was lookin for ROMS CID __032 and PN710000 for HTC with LTE. Maybe I did something wrong? I live in Poland if it matters...
Lustenmord said:
Thank you.
I will try to restore fastboot usb.
May you point me to apriopriate ROM for my device?
The red fragment in bootloader- which indicates bad firmware installation- was already just after Cyanogen install. So the problem started before i tried to go back to stock.
I was lookin for ROMS CID __032 and PN710000 for HTC with LTE. Maybe I did something wrong? I live in Poland if it matters...
Click to expand...
Click to collapse
Once you'll have fastboot usb connection working, you'll have to flash the 7.19.401.2 RUU posted here. Follow instructions of post #1 to flash it.
So your version-main (in red) was the same version number before flashing the guru reset rom? And it was red before? What version of the guru reset rom did you flashed?
alray said:
Once you'll have fastboot usb connection working, you'll have to flash the 7.19.401.2 RUU posted here. Follow instructions of post #1 to flash it.
So your version-main (in red) was the same version number before flashing the guru reset rom? And it was red before? What version of the guru reset rom did you flashed?
Click to expand...
Click to collapse
I do not remember what was original version, must say. First was stock OTA updated to last version, then cyanogen from September, then Cyanogen October, then Guru Reset.
I noticed red writing after 2nd Cyanogen install (October) when I decided to go back to stock and started to have problems. Maybe it was red before, dunno.
What version Guru I do not remmeber, maybe it is still on my phone, when I get acces to SD I will write it down.
Thank you for your flashy (intended!) response!
Lustenmord said:
I do not remember what was original version, must say. First was stock OTA updated to last version, then cyanogen from September, then Cyanogen October, then Guru Reset.
I noticed red writing after 2nd Cyanogen install (October) when I decided to go back to stock and started to have problems. Maybe it was red before, dunno.
What version Guru I do not remmeber, maybe it is still on my phone, when I get acces to SD I will write it down.
Thank you for your flashy (intended!) response!
Click to expand...
Click to collapse
Well what I wanted to know by asking you this question is if you used the right guru version for your phone. You should have used the version number that matched your phone version-main. If I understand correctly, you were on 7.19.401.2 then flashed CM in September, updated CM in October and then flashed the guru reset rom. Flashing CM doesn't change your version-main (firmware version). So it sounds like you have flashed the wrong guru reset version on your phone since there is no guru reset for 7.19.401.2. Anyway it doesn't really matter anymore, if you can have back the "fastboot usb" connectivity, it should be pretty easy to fix by flashing the ruu mentioned above.
Reporting Fastboot USB working Hope is returning. Rom is downloading, 1 hour left, Canadian server is slow. Thank you, mate.
Lustenmord said:
Reporting Fastboot USB working Hope is returning. Rom is downloading, 1 hour left, Canadian server is slow. Thank you, mate.
Click to expand...
Click to collapse
I'm also downloading from Can servers since im located there and never had speed issue maybe to much traffic today
When flashing the ruu, don't forget to use htc_fastboot.exe like explained in the other thread. The normal "fastboot.exe" from the android sdk won't work to flash the ruu because it can't deal with files as large as this ruu. Just download htc_fastboot.exe and save it in the same folder where you already have fastboot.exe, adb.exe and their .dll files installed on your computer. When you want to use htc_fastboot.exe instead of fastboot.exe, like for flashing the ruu, start your command with "htc_fastboot" instead of "fastboot"
e.g.
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
htc_fastboot reboot
instead of
Code:
[STRIKE]fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
fastboot reboot[/STRIKE]
When issuing "htc_fastboot flash zip ruu.zip" a few files will be flashed to your phone, then it will stop, the phone will reboot itself and the flash will continue. Don't touch anything until the ruu is completely flashed ---> it should output "Okay. Finished, total time: XXX" when its done. Then its safe to reboot using "htc_fastboot reboot".
First boot can take longer than usual. The phone will sit at the white HTC splash screen for a few min then it will eventually boot to the welcome/setup screen.
You'll then have 2 ota updates to install (settings --> about --> software info --> check for updates)
one from 7.19.401.2 to 7.19.401.22
another one from 7.19.401.22 to 7.19.401.30 which is currently the latest version (android 5.0.2, Sense 6.0)
Now receivin 2nd OTA.
Tommorow afternoon will post a final result but for now I must say that you, sir, helped a lot. Thanks. Big ones.
Lustenmord said:
Now receivin 2nd OTA.
Tommorow afternoon will post a final result but for now I must say that you, sir, helped a lot. Thanks. Big ones.
Click to expand...
Click to collapse
You're welcome, glad it worked :good:

Categories

Resources