Develop Bugs

{full proof method of not getting bricked cause of battery}

as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
5.to flash a custom Rom just flash a custom recovery in the fastboot
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Edit: (credits to cpv5 for this info)Make sure you don't go to recovery when you're on stock recovery as it will wipe everything on your phone & virtual sdcard and you will be back to setup screen again.

gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
I've done that now, ta for that.
Sent from my HTC One X using XDA Premium HD app

gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
even better is that once you have done the OTA update to 1.28 you get the new Hboot which can boot properly so you never have to replace the stock recovery. just fastboot boot recovery.img if you need to change rom or nandroid

I dont think that the 1.28 Hboot has fixed the fastboot boot commands...

You can fastboot boot a recovery? not just a boot.img?

broncogr said:
I dont think that the 1.28 Hboot has fixed the fastboot boot commands...
Click to expand...
Click to collapse
it has because i have used it
flakz0r said:
You can fastboot boot a recovery? not just a boot.img?
Click to expand...
Click to collapse
and yes, you can boot a recovery aswell as a boot.img

bagofcrap24 said:
it has because i have used it
Click to expand...
Click to collapse
Very interesting, seems to be working for recoveries here as well (s-on unlocked hboot 0.94).
I'm really interested if this works properly for zImages as well. I thought PaulOBrein was working with htc for a solution for this "fastboot boot" though? Maybe some parts ain't working?

This is a great tip, thanks!
and is it just me, or does adb work when fastboot booting clockwork with the stock recovery flashed?!

bagofcrap24 said:
it has because i have used it
and yes, you can boot a recovery aswell as a boot.img
Click to expand...
Click to collapse
Are you using windows to fastboot boot or linux?

broncogr said:
Are you using windows to fastboot boot or linux?
Click to expand...
Click to collapse
Just tested it here, works on both host-machine types
It also lead to a nice find: http://forum.xda-developers.com/showthread.php?t=1594819&page=21

gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
I just add further note on your question here
See the edit part.

Thanks a ton ckpv5

Has a question here, how do we flash stock recovery in hboot? I only know the way of flashing stock recovery via fastboot with the command of "fastboot flash recovery [recovery name].img*
Is my way wrong or there is some other way?

Where do I get stock recovery from? Tempted to do this until cwm supports charging....
Sent from my HTC One X using Tapatalk 2

landwomble said:
Where do I get stock recovery from? Tempted to do this until cwm supports charging....
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You can get it from the link below
http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Btw bro, wanna ask if you are able to guide me on flashing the stock recovery? Is it the same way as flashing custom recovery?

williamyi said:
You can get it from the link below
http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Btw bro, wanna ask if you are able to guide me on flashing the stock recovery? Is it the same way as flashing custom recovery?
Click to expand...
Click to collapse
yes same thing. not a single change except from the name
fastboot flash recovery (stock name).img

gunswordx said:
Edit: (credits to cpv5 for this info)Make sure you don't go to recovery when you're on stock recovery as it will wipe everything on your phone & virtual sdcard and you will be back to setup screen again.
Click to expand...
Click to collapse
ok so...when you mean this, you are saying that by simply going to hboot and afterwards "recovery", it will wipe it all?! wtf?!
any reason for it?

casca said:
ok so...when you mean this, you are saying that by simply going to hboot and afterwards "recovery", it will wipe it all?! wtf?!
any reason for it?
Click to expand...
Click to collapse
Because the stock recovery doesn't have menu like the CWM recovery, so once you choose recovery, the recovery process will run. Not like the CWM recovery, you need to choose which function to run.
So two things can happens when you go to recovery when you're on stock recovery:
1) the recovery will runs and wipe everything on your phone (I tested this)
2) the recovery will runs and there is error where you see the phone logo with red triangle, then you need to shutdown and restart to your current ROM.

ckpv5 said:
Because the stock recovery doesn't have menu like the CWM recovery, so once you choose recovery, the recovery process will run. Not like the CWM recovery, you need to choose which function to run.
So two things can happens when you go to recovery when you're on stock recovery:
1) the recovery will runs and wipe everything on your phone (I tested this)
2) the recovery will runs and there is error where you see the phone logo with red triangle, then you need to shutdown and restart to your current ROM.
Click to expand...
Click to collapse
ok, tks for explaining mate

What is the meaning of the error where you see the phone logo with red triangle

[Q] New Android user :)

Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA

KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
Yes that means its rooted, you should have a custom Recovery. If you power off and hold the volume keys and the power button then a green android will pop up use the volume keys and hit up twice to the "recovery mode" then hit the power button... then if you could tell me what you see? At the bottom it should say Clockworkmod 5.x.x.x or it will have TWRP which it will show TeamWin at first and a curtain will pull up. If you do have custom recovery you could just simply flash a custom ROM like AOKP for you device .

KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER on your ability to install updates OTA. It will happen if your recovery does not match your ROM.
You have a few options:
1) you can go to the "update" link in my signature, find the update for your build, and install it manually as per the instructions in that thread.
2) you can go to the "flash" link in my signature and flash stock (yakju) 4.0.4 as per the instructions.
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER or your ability to install updates OTA.
Click to expand...
Click to collapse
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.

ÜBER™ said:
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.
Click to expand...
Click to collapse
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.

ÜBER™ said:
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.
Click to expand...
Click to collapse
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha now that we are done bickering.. i hope the OP can find his way.

ycholish siempre
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
then if you could tell me what you see?
Click to expand...
Click to collapse
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .

KrizTM said:
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .
Click to expand...
Click to collapse
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium

ÜBER™ said:
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?

Check my sig to get yourself on AOKP.

KrizTM said:
[snip]
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
Click to expand...
Click to collapse
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
KrizTM said:
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Click to expand...
Click to collapse
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
KrizTM said:
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?
Click to expand...
Click to collapse
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).

efrant said:
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).
Click to expand...
Click to collapse
Awesome. That clears up a lot of things. Thanks a lot You're right. Gonna stick to stock 4.04 till I get better at this hehe.
Thanks

[Q] Cannot boot to recovery (on two completely separate phones).

I flashed CM10 onto my phone a couple weeks ago, everything went smoothly. Today, I reverted back to stock and locked the bootloader so that I could receive the stock JellyBean update. Well I download the update, reboot phone into fastboot, attempt to go into recovery and I get the red triangle !. I know this is an issue with the phone apparently not finding a recovery boot but why didn't my reverting to stock reinstall the stock recovery? Does anyone have any guides they suggest to get stock recovery back? (I've found a few but thought I would ask).
Now, this is understandable that my phone can't boot into recovery since I flashed CM recovery onto it and whatnot, but I attempted to boot into recovery on my girlfriends phone (same phone, NEVER BEEN UNLOCKED OR FLASHED) and it can't boot into recovery either... Is something going on here or am I just missing a huge piece of the puzzle? I don't really want to have to flash anything on my girlfriends phone to fix it, she's not into the tinkering and would rather not have her data reset. Any help would be appreciated.
And for the record, I did a search to figure this out but at the very least I can only find solutions for people who have flashed CM or similar and nothing pertaining to the problem my girlfriend's phone has.

Tried reflashing recovery already? How did you "revert" to stock?
Sent from my Galaxy Nexus using xda app-developers app

nktje said:
Tried reflashing recovery already? How did you "revert" to stock?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Used this method:
http://forum.xda-developers.com/showthread.php?t=1848566
It worked, I'm on stock ICS, but I didn't do ANYTHING after booting into ICS again and attempting to install JB and booting into recovery. Did I miss something? How do I "flash recovery"?

Unzip the factory image you get from developers.google.com/android/nexus/images
Then use fastboot to flash the recovery.
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Sent from my Galaxy Nexus using xda app-developers app

I think you are confusing a few things here. First off, the Android with the red triangle IS the stock recovery main screen. (If you want to flash the update manually, you need CWM -- go into fastboot mode and type: fastboot flash name-of-recovery.img, where name-of-recovery is the recovery that you downloaded and want to flash.) Second, you need the stock recovery for an update to install over-the-air, but you need a custom recovery if you want to flash it manually.

Muffinabus said:
Today, I reverted back to stock and locked the bootloader so that I could receive the stock JellyBean update.
Click to expand...
Click to collapse
this happened. you installed stock recovery when you reverted, whats the surprise?
and you dont need to relock bootloader to successfully update through ota. seems to me know the op needs to refine his searching skills.
nktje said:
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Click to expand...
Click to collapse
just press vol up+power to bring up the stock recovery menu.
edit: damn efrant, i got this man
sent from my i9250

nktje said:
Unzip the factory image you get from developers.google.com/android/nexus/images
Then use fastboot to flash the recovery.
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So in the context of my girlfriend's phone where nothing has been done to it in the 4 months she's had it, why would it be giving the recovery error? Also, does flashing the recovery wipe the phone?
It's funny too because I just got the JB OTA but I'd still like to get this figured out.

Muffinabus said:
So in the context of my girlfriend's phone where nothing has been done to it in the 4 months she's had it, why would it be giving the recovery error? Also, does flashing the recovery wipe the phone?
It's funny too because I just got the JB OTA but I'd still like to get this figured out.
Click to expand...
Click to collapse
run the update manually (found on the Update link on efrants sig) through cwm, that should give you a more detailed description of whats going on.
flashing a recovery doesn't wipe the device. unlocking will, btw. its not an error, its the stock recovery!
sent from my i9250

bk201doesntexist said:
run the update manually (found on the Update link on efrants sig) through cwm, that should give you a more detailed description of whats going on.
flashing a recovery doesn't wipe the device. unlocking will, btw. its not an error, its the stock recovery!
sent from my i9250
Click to expand...
Click to collapse
Alright, I think I got it... so the android with the red ! triangle IS stock recovery? I just remember on my Nexus S being able to boot into recovery and load up a stock .zip update manually without any custom recovery mod. Is this not possible on the Galaxy Nexus then? So what does the stock recovery DO other than sit there and reboot after a minute?

Muffinabus said:
Alright, I think I got it... so the android with the red ! triangle IS stock recovery?
Click to expand...
Click to collapse
Correct! As was mentioned by bk201doesntexist, hold power and press volume up to access the menu.
Muffinabus said:
I just remember on my Nexus S being able to boot into recovery and load up a stock .zip update manually without any custom recovery mod. Is this not possible on the Galaxy Nexus then?
Click to expand...
Click to collapse
No, that does not work on the GNex.
Muffinabus said:
So what does the stock recovery DO other than sit there and reboot after a minute?
Click to expand...
Click to collapse
Have a look at the menu, and you can see the options.

efrant said:
Correct! As was mentioned by bk201doesntexist, hold power and press volume up to access the menu.
No, that does not work on the GNex.
Have a look at the menu, and you can see the options.
Click to expand...
Click to collapse
Thank you! I feel like an idiot now. I honestly thought it'd be the same as the Nexus S where you were able to do this...

[Q] Cant flash CWM

I'm trying to get cwm recovery on my htc ove v VM. I have unlocked boot loader and rooted successfully. When i fast boot the recovery image, it says sending writhing and done. When I reboot and try to boot cwm it just stays on the htc screen with the red letters, is this normal? I should think not. I'm sure this has happened to someone else I just need a solution. Any advice would be great.

Hi
CWM is not recommended for CDMA AFAIK
Use TWRP for CDMA instead
max

i4cbj45 said:
I'm trying to get cwm recovery on my htc ove v VM. I have unlocked boot loader and rooted successfully. When i fast boot the recovery image, it says sending writhing and done. When I reboot and try to boot cwm it just stays on the htc screen with the red letters, is this normal? I should think not. I'm sure this has happened to someone else I just need a solution. Any advice would be great.
Click to expand...
Click to collapse
check ur commands it shud be
fastboot flash recovery recovery.img
and check if the image is not broken TWRP 3.0 is come use that!

I got it
cybervibin said:
check ur commands it shud be
fastboot flash recovery recovery.img
and check if the image is not broken TWRP 3.0 is come use that!
Click to expand...
Click to collapse
I got CWM flashed using the android ultimate tool found on this site. Before that nothing worked. The only minor thing is that you have to scroll through the cwm menus three times to get to where you can select with the power button, but then it works fine. I've made my nandroid backup. But haven't flashed a rom yet... kinda nervous about getting into that one, But if you guys have any suggestions about STABLE roms, that would be helpful as well. Thanks,

i4cbj45 said:
I got CWM flashed using the android ultimate tool found on this site. Before that nothing worked. The only minor thing is that you have to scroll through the cwm menus three times to get to where you can select with the power button, but then it works fine. I've made my nandroid backup. But haven't flashed a rom yet... kinda nervous about getting into that one, But if you guys have any suggestions about STABLE roms, that would be helpful as well. Thanks,
Click to expand...
Click to collapse
I don't believe in those all on one Tools,i prefer to do it manually...Cause if u screw up u know where u went wrong.....and check out cm9 its almost stable...i used to use it....i like it....don't be nervous ... flashing is awesome
Sent from my One V using xda app-developers app

TWRP 2.6.3.3 Problems

Has anyone successfully installed TWRP 2.6.3.3 (http://techerrata.com/browse/twrp2/m7) on your HTC One? I have tried all three methods on installing it and I can't seem to get it to stick on my phone.
Method one: Goo.im app
From the menu, selecting Install OpenRecoveryScript and selecting Yes results in No recoveries were found for your device.
Method two: ADB / Terminal
Opened up an ADB shell and used dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 which successfully installed it. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Method three: Fastboot
Booting into the bootloader and selecting the fastboot option in order to run fastboot flash recovery recoveryfilename.img successfully installed. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Holding volume down + power and selecting Recovery from the bootloader also reboots to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
No idea how to get this installation to stick. Can anyone help out?

the twrp for m7 doesn't work.
the twrp for m7vzw is the one you need.

raphytaffy said:
Has anyone successfully installed TWRP 2.6.3.3 (http://techerrata.com/browse/twrp2/m7) on your HTC One? I have tried all three methods on installing it and I can't seem to get it to stick on my phone.
Method one: Goo.im app
From the menu, selecting Install OpenRecoveryScript and selecting Yes results in No recoveries were found for your device.
Method two: ADB / Terminal
Opened up an ADB shell and used dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 which successfully installed it. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Method three: Fastboot
Booting into the bootloader and selecting the fastboot option in order to run fastboot flash recovery recoveryfilename.img successfully installed. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Holding volume down + power and selecting Recovery from the bootloader also reboots to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
No idea how to get this installation to stick. Can anyone help out?
Click to expand...
Click to collapse
I used Flashify from the Play Store and it worked perfectly. The recovery held and was able to flash CM11. My fastboot has been screwed ever since I upgraded to Win8.1 so Ive been using that app as an alternative.
EDIT- Using the correct one as the previous post alluded to would also be a great idea. I didn't even catch that.

wiredout46 said:
the twrp for m7 doesn't work.
the twrp for m7vzw is the one you need.
Click to expand...
Click to collapse
Ah thanks, didn't even notice that. Working great now. If anyone comes to this thread looking for the m7vzw image, it can be found here: http://goo.im/devs/Flyhalf205/M7VZW

raphytaffy said:
Ah thanks, didn't even notice that. Working great now. If anyone comes to this thread looking for the m7vzw image, it can be found here: http://goo.im/devs/Flyhalf205/M7VZW
Click to expand...
Click to collapse
2.6.3.3 is in the verizon htc one original development subforum. just flashed it and it works fine.

Guys help! Installed TWRP 2.6.3.3. specifically for installation Maximus HD after installation did WIPE and accidentally formatted storage on which lay installer Maximus 30 HD, how do I copy installer again on storage, because mode Bootloader - Fastboot USB can not get access to it?

How come I can't find VZW TWRP 2.6.3.3?
and only can find 2.6.3.4?
sorry, just curious

andybones said:
How come I can't find VZW TWRP 2.6.3.3?
and only can find 2.6.3.4?
sorry, just curious
Click to expand...
Click to collapse
2.6.3.3 had the charging bug no?
if you need it, i have a copy of it.

Problem
Hey
I was flashing my htc to CM11 and it says that flash was successful, but now my htc one stuck when you try to power on it says only HTC quietly brilliant and wouldnt go on. What should I do ?

peca_slo said:
Hey
I was flashing my htc to CM11 and it says that flash was successful, but now my htc one stuck when you try to power on it says only HTC quietly brilliant and wouldnt go on. What should I do ?
Click to expand...
Click to collapse
Did you wipe data before or after flashing?

Flyhalf205 said:
Did you wipe data before or after flashing?
Click to expand...
Click to collapse
yes i did i have rot the cm10.2 but it stuck on logo screen of cm

peca_slo said:
yes i did i have rot the cm10.2 but it stuck on logo screen of cm
Click to expand...
Click to collapse
You did flash the Verizon recovery and Verizon rom?

Flyhalf205 said:
You did flash the Verizon recovery and Verizon rom?
Click to expand...
Click to collapse
Yes I did but I think this is not a good verzion for me cuz i have m7-ul model, but now I can do nothing with the phone. It would be good if i could get it back to stock

peca_slo said:
Yes I did but I think this is not a good verzion for me cuz i have m7-ul model, but now I can do nothing with the phone. It would be good if i could get it back to stock
Click to expand...
Click to collapse
Might be better to go to the ul variant thread at http://forum.xda-developers.com/htc-one

Can't Flash TWRP after installing MaximusHD
So I am a noob at this stuff and successfully flashed TWRP 2.6.3.3. I installed the MaxHD ROM shortly after following all instructions that I could find. I ran into bootloop and had to revert to an old firmware then flashed the current firmware and viola MaxHD booted right up. However, now I can not flash TWRP back as my recovery. Everytime I flash it and go into recovery it goes into MaxHD ROM. If anyone has any ideas they are much appreciated.
Also, I have read for over three weeks on these boards before posting even my first post so I have tried to research the problem if anyone was wondering that.

Jaayyrod said:
So I am a noob at this stuff and successfully flashed TWRP 2.6.3.3. I installed the MaxHD ROM shortly after following all instructions that I could find. I ran into bootloop and had to revert to an old firmware then flashed the current firmware and viola MaxHD booted right up. However, now I can not flash TWRP back as my recovery. Everytime I flash it and go into recovery it goes into MaxHD ROM. If anyone has any ideas they are much appreciated.
Also, I have read for over three weeks on these boards before posting even my first post so I have tried to research the problem if anyone was wondering that.
Click to expand...
Click to collapse
Is MaxHD a Verizon rom? That could be an issue if it's not. Also, the latest TWRP is 2.7.0.8. Haven't had any issues with it. Are you flashing it with fastboot commands? You might try the app Flashify.
Sent from my HTC6500LVW using Tapatalk

brholt6 said:
Is MaxHD a Verizon rom? That could be an issue if it's not. Also, the latest TWRP is 2.7.0.8. Haven't had any issues with it. Are you flashing it with fastboot commands? You might try the app Flashify.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Good call...it is not for the Verizon HTC One. Thanks much.
It doesn't say it's not in the write up about the ROM...I had to dig into the replies to see if anyone else asked.