So what happens (and I've confirmed it doesn't happen with an unmodified phone) is that when I turn the phone off then plug into USB or AC adapter (OEM) it boots into recovery. I've tried with and without development on. It's very annoying and maybe just a side effect of rooting or flashing HBOOT. Please if there is a fix tell me what it is!!
Things I've done:
-Updated to OTA 2.2.1
-Permrooted with Visionary+ v14
-Flashed Recovery with ClockworkMod 2.5.1.2
-Modified S=OFF using theunlockr.com method (flashing hboot with different image)
This is not a question... this is an observation... and yes this behavior has been confirmed and I don't think anyone knows why just yet
Yes, happens to me too. use fastboot and it wont do it
Please post questions in Q&A section.
Apologies for the wrong forum. Fastboot seems more like sleep mode. More of a band-aid then a fix. Anyone know why it happens? Is it because of S=OFF or the permaroot? I couldn't find anything on this by searching, will make sure it gets into the right forum next time. Thanks!
This is a known bug with clockwork recovery..it happens with other phones too(htc aria)..not just a mt4g issue...it didn't always happen for me...but I don't know why it happens...check the clockwork thread around page 9
Follow me on twitter @face_melter
Sent from my HTC Glacier using XDA App
Related
So I have an Evo and got it last Tuesday, 7/6/2010. I have been trying to hack so many different ways and flashed PC36IMG. I want to install new roms but I am not able to change my recovery image. I have used rom manager, tryed flashing different recovery images and nothing. On the screen with the red triangle, it says "E:Can't open /cache/recovery/command" I have tried anything but get stuck in boot loops and other things that don't work. I was wondering if anyone else has had this problem and has a fix for it?
Which root method are you trying? Do you currently have root? If so, You need to use use the start over method in the development section of the forums. I believe OPs name is whitslack or something similar.
Here...i found the link for you.
http://forum.xda-developers.com/showthread.php?t=715915
If you don't have root yet use this page. Follow all steps. http://forum.xda-developers.com/showthread.php?t=705113
This is assuming you were privy enough not to install any OTAs.
Have you tried simple root?
Sent from my PC36100 using XDA App
I have tried booting into recovery with clockworkmod and also stock recovery many times. I have disabled fastboot and each time I have tried I get the picture of the phone and the triangle.Once again I have fastboot turned off. I have searched the threads and tried what ever I found and nothing has worked. I am wanting to do a nanroid backup and I am getting more and more discouraged each time I try and it fails. I guess maybe its time to send it back as I have 4 more days left on buyers remorse. Thought I would try to solicit some help before making the decision to send it back. I have a Nexus One and a Vibrant and have never had this problem with either one of them. I have tried it with the Visionary temp root applied and with it off and does not make a difference. I have not applied the perma root yet. Any and all help is and will be greatly appreciated
I had a similar issue. I would do the full permroot, then flash clockwork recovery through fastboot.
Thanks so much for the swift reply. I am not sure if I am going to keep this phone so I am not wanting to permaroot at this time. Is there not a way to flash recovery without doing permaroot? i read where Paul Obrien states in his thread for permaroot that one should do nanroid backup before doing permaroot. This leaves me very confused. How in the world do you do that???lol It looks like the decison to send it back or keep it is being made for me. I have never called CS and asked for help to flash recovery as I feel that they would not respond favorably and want to know why I want to flash recovery, but that could be wrong also. Help!!!!!!!!!!!
Edit:Just got off the phone with tech support and they state that recovery cannot be accessed as a safety feature. Not sure I believe them as he did not know what fast boot was or what a nanroid backup is. He said the little phone and the triangle with the exclamation is the bootloader screen and no other screen can be accessed after selecting recovery. Any and all help and info is GREATLY appreciated.!!!
Help PLEASE
tenbeau said:
Help PLEASE
Click to expand...
Click to collapse
I'm not sure how far you'll be able to get, but I've been in your position before, so anything I can suggest to help-
http://forum.xda-developers.com/showthread.php?t=834225
If you follow it EXACTLY it should work out- you might have to try a few times- I did, he also includes the script to return it to S=on. The terminal emulator worked best for me
Once you get permroot you can get clockwork on there.
I don't understand what you're trying to do. Are you trying to boot into CWM recovery or the stock recovery? The way I understand it is that once you flash CWM, it overwrites the stock recovery. And furthermore, if you're trying to make a nandroid, you will need to boot into CWM. If you need the stock recovery back, someone posted a link to reflash it back onto the phone.
Follow the above instructions on how to turn s-on. Itz actually easy. Jes download the files, type in 2 commands in terminal emulator, you are now perm rooted with s-off. That easy. If you want to unroot, go to visionary and click on unroot, simple and works like a charm
Sent from my HTC Glacier using XDA App
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
tenbeau said:
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
Click to expand...
Click to collapse
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
bobsbbq said:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
Click to expand...
Click to collapse
yes I a sure am. I trusted the Dorid-Life site and should not have. Thanks for the swift response...
setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Please post questions in Q&A section.
I did the same thing. I flashed the .zip file from droid life forum and got a success message when I installed it through recovery and mine never bootlooped. I didn't get the gingerbread keyboard but it didn't bootloop either
Sent from my HTC Glacier using XDA App
tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
I think you mean bootloader? You only have 1 recovery. If you flashed clockwork you no longer have stock recovery. Vol Down + Pwr gets you to bootloader or SPL where it shows S=off.
I did not flash the zip (sounds like an overkill to flash a zip for new KB). I ADB pushed both files and got a FC on multi-touch KB... oh well, I like HTC_IME better anyway
tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
make sure fastboot is checked off otherwise you cant get into the bootloader. to make sure it is off go to: menu, settings, applications and uncheck fastboot. you're good to go then. to get into recovery, you can do it thru bootloader or by opening up rom manager and clicking on the "reboot to recovery" option
setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
the website was not specific enough. the port at the current moment is for motorola droid devices. they should have been more specific instead of saying any rooted 2.2 android phone. even if you do get it on your phone, its only going to force close every time you try and type something. thats what happened to me, so after about 24 hours i said **** it and removed it. swype in my opinion is better anyway. im trying to port the g2 swype to our phone so we can have a swype with a mic on the keyboard. oddly, ours didnt come with one.
Hello, xda-developers,
I have a myTouch 4G that was updated to the 2.3.4 Gingerbread software and wanted to root it. In order to do so, after many research, it states that there is no root for the 2.3.4 Gingerbread software and for it to be rooted you'll have to downgrade it.
The reason why I wanted to root it is because I am having a problem with the WIFI connectivity in my home and was wondering if it will fix it. Same reason why I update it to the 2.3.4 Gingerbread software in the first place. The myTouch 4G that I have will "RARELY" connect to my wireless router in my home but for some reason it doesn't fail me when connected to other wireless routers outside of my home even when having the same router. But this is now not the problem.
As you can read, the title says it all. My problem now is that I just soft bricked my myTouch 4G after a downgrade that I followed here: http://forum.xda-developers.com/showthread.php?t=1178912# Like the noob always say when something goes or went wrong, "Boohoo, I don't know what I did wrong. Someone, please, help me." But I THINK I know what I did or went wrong.
I followed the guide strict and carefully hoping I don't brick it but then I said to myself, "It's a 99.9% chance I won't, I think... what can possibly go wrong?" Everything went well. I did everything it says and once the update bar fills up to the top, BAM! It hits the "T-Mobile myTouch 4G" boot screen. I was happy. Very happy because I felt accomplished and one step closer to excitingly freeing my phone. But my hopes went down when it stayed like that for hours on end. I pulled the battery out and reboot it and nothing was fixed. Although it was stuck, I still can access the bootloader. I pulled out the battery again and boot it to the bootloader and re-updated it again and nothing was fixed. I yanked out the battery one last time and deleted the PD15IMG.zip file from the SD card to keep it from asking to update everytime I boot it to the bootloader so I can factory reset it but, still, that didn't help.
Like I said. I think I know what I did or went wrong. Examine the guide. The "Gaining Temp Root" part I did right. The "Changing Version Number to Allow Downgrade" I did correct and the results on the command prompt came out the way it stated it should come out. THEN! I yanked out the battery to reboot it after that. When I've done so I continued to the next procedure and everything went how it says it should go but, instead of the end results, I got it stuck on the "T-Mobile myTouch 4G" boot screen after the update. I think that's where I messed up. When I yanked out the battery to reboot it after the "Changing Version Number to Allow Downgrade" part. I believe it kicked it out from root. It is a temp root by the way and I read it somewhere that said, "Once you're rooted you CAN downgrade it." Something like that which made me think it wasn't rooted after that reboot and the downgrade wasn't a success. I also have two other guesses in which I think soft bricked the phone. I either have a bad eMMC-boot or the PD15IMG.zip was bad. These are my thoughts in what went wrong. I'm asking for your help. So can you help me find the solution to this problem?
Thank you very much in advance for your time and effort into reading this and helping me out. I really appreciate it.
-Victor​
P.S. Here's the information on the myTouch 4G's bootloader:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Apr 14 2011,13:18:22
Again, Thank you.
wow, same thing happened to me.
You could try updating it back up to the 2.3.4 RUU. If that works, nothing lost at least.
You used a wrong PD15IMG, most probably.
If you have used the correct one, your bootloader would be 0.86.0000, but it isn't.
Please re-download the correct PD15IMG and try again. When it works, if it throws any messages - write them here, so someone will be able to help you. If you see "Fail-PU" - your phone is dead.
Your mistake might have been removing the battery instead of typing "adb reboot bootloader". Yanking the battery off a working phone can destroy its eMMC. If that's what happened to you - well, you can replace your phone under warranty and follow the instructions better next time.
It was definitely the part where you yanked out your battery. You lost temp root then. Why you did it, not sure. But it's already been done so Let's not linger.
Have you tried starting over from step one?
Sent from my HTC Glacier using XDA App
You used a wrong Rom to downgrade or it is corrupted during download.
Download the official 2.2.1 rom, put it to the root of your sdcard, and try to update.
The original bootloader is 0.86.0000
You can download it here
Rename it to PD15IMG.zip before updating.
Do what he said
Do what the last guy said and rename the image and flashing.
Here is what has happened, you were probably installing a signed downgrade to a previous version. Either you got the wrong file, your download was corrupt (THANKS TO CHROME), or you didn't clear your cache dalvik needs to be clear if you run a different kernel. The main cause of hanging at the bootscreen is the incorrect cache either regular or dalvik. Thats what I've noticed from threads and just in general.
You don't appear to be running clockworkmod recovery. If you are going to mess with the system, DO IT ALL THE WAY! Don't get confused with this one... if you are planning to write radios, flash updates, or do anything YOU WILL NEED ROOT. This is because something could go wrong and you could be locked out. If you aren't willing to commit to basic root privileges, do not attempt to downgrade. Either go all the way, or don't go at all. That's just some friendly advice cause people will make the misconception if they just downgrade thats fine, but getting root is more dangerous... not true! If you have root, you can actually gain control of the phone and restore even a 'broken' one.
ROOT is mostly gained from within the phone in the operating system. You use an APP to gain root privileges. Once you get root, you need to get SU a program to grant privileges to programs that request them. Then you need to get clockworkmod rom manager so you can flash a recovery (internet and market access is required unless you can install from the .apk and use adb). ONCE YOU HAVE THAT RECOVERY you can downgrade, upgrade, flash, flex, backup, restore all with a simple push of a button, no expertise required!!
You can even revert to stock easier when you have root.
Once you get that recovery installed then look for ways to turn s-off and unlock your sim so you don't have to worrry about stuff.
And remember, they might not honor your replacement phone if you hack or modify it... but if you lose the phone they will replace it for you.
Big Thanks For the Help!
Hello, xda-developers,
Thank you, all, for your help! I've figured out the problem.
It was because of the PD15IMG.zip file. It was a bad one and I figured it out by downloading another one BUT, instead of downloading it from the same site I got it from, I downloaded it from a different site. I've barely figured this out and I could have fixed this problem way earlier if I had checked back my post.
Big thanks, again, to you guys for taking your time and helping me figure out this problem. It has been a month since I've been "Android-less" and now I am going to treasure it more than usual and I can not lie... I miss its awesomeness.
My phone is now back and it is officially perm-rooted! Love this phone more than ever with all the things it can do now. Rocking this phone out now with the Virtuous Unity rom and it blows... me... away!
-Victor​
Well..... at last you figured it out.....Iam happy for you....Try Virtuous Unity 2.39 you will really love it.
By the way, where did you get the PD15IMG.zip file???? Can you post the link, so that it will be easy for others with similar problem.
Thanks! You're right, I am trying out Virtuous Unity 2.39 right now and I love it. I was actually looking for an android "bone-stock" gingerbread rom but I can't seem to find one without the customization. Then I bumped into this one. They say sense 3.0 were only made to work on dual-core phones... they were wrong. I really love this rom and I'm sticking to it. Until I find a stock gingerbread rom that has been perfected for the myTouch 4G. You know, the one without the customization.
Oh! Here's the link where I got the radio (PD15IMG.zip) from: www1240.megaupload.com/files/89ce9e2eeb86bb659eceb64baa356c4b/PD15IMG.zip
Since I'm a new member of the xda-developers forum, I couldn't post a link. So, instead, here's the address.
So have you tried the link in my post? Did it work for you?
The link for the PD15IMG.zip radio? Nope. I went onto googling it and finding one myself. The link for the stock myTouch 4G 2.3.4 rom? Nope. Not a big fan of the myTouch 4G's overlay.
My friend gave me his Evo to try to fix. It isn't rooted so S-on. I tried put a recovery file on to see if I can change the rom, but it just won't recognize it. Someone else posted a similar problem, but he got is to work. I tested the card and file and my evo asked if I wanted to update, but his phone will not work. It is stuck in boot loop. Not sure how he got stock on that. He doesn't mess with phones. There was an unbrick program I tried and it didn't seem to work, but I probably wasn't using it correctly since it kept changing the rom to the same rom from what I could tell.
It boots up sometimes to seem to work for a minute then boots again. I get the red triangle when I try to go into recovery. It probably doesn't have a recovery img since we haven't tried to root it.
ask your friend what exactly was he doing prior to this happeing, also whats the info when you go into the bootloader? i only ask cause the more info you provide the better chances are someone can help solve this issue. also you cant put a recovery or a custom rom on till your rooted.
ok
dzee206 said:
ask your friend what exactly was he doing prior to this happeing, also whats the info when you go into the bootloader? i only ask cause the more info you provide the better chances are someone can help solve this issue. also you cant put a recovery or a custom rom on till your rooted.
Click to expand...
Click to collapse
I can hold the power and down vol and go into bootloader. It goes through the zip file loading instructions and can't find the PC36IMG image and never asks if I want to update. I think I read a post where someone was told their bootloader is "locked".
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
ok
Hypeo said:
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
Click to expand...
Click to collapse
I believe it was version .79 or something like that. I'll check it when I get home.
As soon as he gets back from China I'll ask him what he did when started bootlooping. The phone might work for 30 seconds before going into reboot over and over so RUU might not work. But I can go into bootloader and into fastboot and was able to get a unbrick program to run and it seemed to be able to install another rom, but the rom it said it was installing was the same that was on the phone so maybe they needs S-off to function.
If you find your phone is rooted and can turn it on long enough to download an app from the market called Flash Image GUI, in the description it will say for the EVO 3d but it works on the og as well, you can also download off the devs xda thread just google (flash image GUI xda) and it should pop up, another thing make the file is on the root of your sd card and not in a sub folder. Good luck.
Sent from my PC36100 using xda premium
Oh and you can't flash custom roms with s on period, if it is on that's your problem there.
Sent from my PC36100 using xda premium
here it is
Hypeo said:
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
Click to expand...
Click to collapse
S-on
HBOOT-0.79.0000
MICROP-041f
RADIO-1.39.00.04.26
Apr 14 2010, 15:41:34
Does this give any idea of what I can do.