Related
I have a Mytouch 3G running test 7 on my phone, and i just installed the clockworkmod rom manger. After, installed it i wanted to flash a new rom, so flashed the clockwork mod recovery, and when i tried to install the new rom from the sd card, it keeps on getting stuck on the mytouch screen, and nothing happens. How do i get into the recovery screen? thanks
First: This belongs in Q & A !!!!111
Which ROM did you flash? Maybe you had to wipe before
right now, i'm running cyanogen test-7, but when i go into the clockworkmod rom manger app and pick the flash rom from sd card, it just says it has to go to the recovery, and then my phone will reset and it would just get stuck on the mytouch screen. So, i just pull out the battery and reset the phone again, and i realized if i press the end button, it will go the rom that is already on the phone. I'm i suppose to push some buttons or something to get to the recovery screen?
No it should flash the rom you select and reboot the phone to boot the new rom without keypress needed.
maybe the wrong device was selected when downloading the recovery image? Try reinstalling clockworkmod recovery from rom manager.
Mod edit: not dev related, moved to q&a
I have the same problem.
I downloaded and installed Rom Manager from the Market and it has completely screwed up my recovery (I can't get into it at all). I tried flashing Amon's again (through Rom Manager) and it still doesn't work.
HTC G1. CM5.07 test 7 (trying to go to stable!).
Your recovery has been corrupted, you will need to flash it through fastboot.
JAguirre1231 said:
Your recovery has been corrupted, you will need to flash it through fastboot.
Click to expand...
Click to collapse
Yes thank you. I erased recovery partition in fastboot then reflashed Amon's.
Working now.
i got into the fastboot screen, but i have 4 options. hboot mode, reset device, restart to hboot, and power down. how do i flash from here?
illmatic282 said:
i got into the fastboot screen, but i have 4 options. hboot mode, reset device, restart to hboot, and power down. how do i flash from here?
Click to expand...
Click to collapse
Connect to your PC via USB, and from the command line issue "fastboot erase recovery" and then "fastboot flash recovery filename.img"
More on common fastboot commands here can be found on these forums, i'm not allowed to post links.
i connected my phone to my computer but nothing on my computer pops up. only the new hardware wizzard pops up. what do i do from here? im i suppose to get a adb popup? how do i set up the fast boot? i'm so confused..thanks
some one, please help..i want to be able to flash new roms in the future...thanks in advance
Can I sugges that you try this sticky thread at the top of this forum board.
It contains all you need to know on who to set up fastboot and how to use it - there are a couple of tutorials on it if you read through the thread.
CM 5.0.7 for Dream/Sapphire introduced a bug in flash_image. It causes recovery flashes to fail. It has since been fixed in the latest test of 5.0.8 I believe.
Man i have the same darn bug cant get back into recovery for nothing, and i dont have a pc to fastboot i have a non intel based mac so no adb or fastbooting, i have been doing fine for forever without adb or fastboot but is there any way around this one, i need help bad, im on HTTClay Superbadv1.3 and it has all sorts of bugs but i cant nandroid or bart or flash any rom without recovery, can someone please help!!!
Also is there another way to erase the recovery partition?
I have a G1 running cyanogen 5.0.8. Everything was going well until I wanted to add widgets to my left-side of the screen. Anytime I wanted to add a widget to the left-side of the screen it would force close. So I went to Rom Manger and fixed permission, cause it would help with my force closing issue. So I flashed my recovery to clockwork from RA-1.70. It was successful. Stupid me, was like, "You didn't need to flash clockwork recovery to fix permissions," so I flashed back to RA-1.70." That too was successful. Then I went to fix permissions. Fix permissions was successful. It prompt me to reboot, so I reboot. Now it got really ugly. My phone now stays at the T-Mobile G1 screen, I can't get into recovery, and the only thing I can do is get into fastboot. So in fastboot, it shows "No img. No img. No img. Then returns back to the fastboot screen, until my only options it to shut it down.
So I am screwed or it the hope?
Please help me
Thanks Matt
So is there hope is what I meant to say....my bad
If you can get into fastboot -then there is hope. I made the same mistake - and flashed two recoveries - and that is a problem.
What I had to do was get into fastboot - plug my phone into the usb cord, so that I could communicate with the phone from my laptop. I'm a newbie at this as well, but if you did not know, fastboot allows you to run command prompt from your PC - and send commands to your phone
Once I had fastboot running on the PC - I had to
Wipe the system, and then
flash my recovery image
Once my recovery image was flashed - I was able to
restore my last back-up without issue
others have reflashed their rom of choice
As noted - I too am a newbie, and your best tool will be to read and learn. I am not up to speed at this point as to commands in fastboot, etc - so do not want to write commands - or copy commands from other posts - in case I lead you in the wrong direction. I'm learning as I go along as well.
As noted, if you can get into fastboot mode - there is hope
Did you have to download ADB and SDK? I read some info on fastboot. And it seems like I have to download those programs and download drivers. Also where did you go to get the right commands?
Thanks for replying
I've seen that you have been involved in some of the other posts with similar issues. Yes, you need to download and install adb, and the drivers - check the sticky posts, all links are there for where to download - and how to get started
http://forum.xda-developers.com/showthread.php?t=532719 this is a good place to start
Good luck - take your time, I already bricked my first G1 and then transplanted a motherboard and started over again.
I now read twice, and make changes once - trying to learn from my mistakes, and not make them again
I think I have had the same problem. I fixed permissions via rom manager and then it prompted me to reboot. Now it is stuck at the G1 screen. I can load it up after holding "home+red power button" so that is good I guess. Is my only option to wipe and start over? I do have a backup but it is 1+months old and I dont want to lose everything in the last month unless absolutely necessary.. My mod info is in my signature.. Please help, my phone is out of commission right now and I need it back soon!
any solutions besides the 1 month old backup? or wiping and starting again??
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
attempted root and used superboot grj22 from modoco pphone is unlocked and after double clicking on indows bat file as directed phone is locked on boot x
this phone has just come back from htc with a new power switch installed and 2.3.4.
anyway could use some help daughter is upset I locked her phone.
can get to boot menu however can not get into recovery. I get a triangle with exclamation in it
thanks
Please read the Wiki, Rooting guide for unlocked bootloader.
Flash recovery through fastboot.
Flash whatever ROM you want from recovery.
You've flashed a wrong kernel (which is contained in "superboot"), that's why you can't boot.
another question
read wiki and followed instructions which said after loading passimg that this was an older version. searched more and found another thread that gave a new file that was supposed to load the older version of the rom and get around the error "older version"
still not working any other ideas will be appreciated
Just to make sure I understand right you tried the frg83 passimg file and you got "main version is older" error? If so then can I just ask you is your bootloader unlocked (at the X screen before the cyanogen mod logo do you see an unlocked padlock)?
hi
yes padlock on screen is unlocked tryed to flash again and get the same error version is older
thanks for trying to help kid leaves for school tonight and is freaking
more
also askes if I want to reboot device
It'll be long fixed by then don't worry
Boot into bootloader then from there select the recovery option. Once there tell me what you see if you see and android with a /!\ next to it then press power and vol+ power slightly before. Then you will get a menu select power down. If you go straight to the menu tell me what color the writing is.
hi
get the triangle white with a orange exclamation in it
Ok then you'll need to flash a recovery via fastboot. So since you bootloader is unlocked I assume you already have the SDK set up and the drivers installed if not then I can help you with that too, but now just download this file and place it in the same directory as fastboot on the computer and download this file and put it on the root of your sd card (not in any folders).
Then boot the phone into fastboot (hold down the trackball while powering up) then connect the phone to the computer via usb and open a command prompt in the directory where you have fastboot. Then input these commands:
fastboot devices (this should return the s/n number from your phone)
fastboot flash recovery recovery.img (where recovery.img is the name of the first file you downloaded earlier)
fastboot boot recovery.img (same thing here)
The phone should then boot into recovery from there use the trackball to navigate go to flash zip from sd card then chose zip and chose the second file you downloaded earlier (the one you put on the sd card), after that wait for it to flash then press vol- to go back to the recovery main menu then select reboot system now and your all good you have stock with root access, if you want to flash a custom ROM then just ask I can explain that too.
As I've said, follow the guide FOR UNLOCKED BOOTLOADER.
You didn't.
The guide for unlocked bootloader is in Unroot/Restore section, called "using fastboot".
Actually, the only thing you need to do is to install recovery. Go to "recovery" guide - again, FOR UNLOCKED BOOTLOADER - and install Amon_Ra's recovery.
Once you have it, you can flash whatever you want, including stock ROM.
ok
everything is good except that i tryed to flash downloaded zip from sd and got error that zip is signed wrong also zip verifacation failed
again thanks excited I got this far.
so after this gets fixed than will phone reboot and go to 2.3.4 that was on there before?
will I be good to go for a new rom and last but least like the miuis and recommendations from an expert?
funny I bought the sensation and forgot how to do all this probably the pressure of the child (oh my god you wrecked my phone) Forgetting of course it was dads to begin with DARN KIDS
me dumb as a box of rocks toggled zip verifacation and ra unzipped.
afraid to push any buttons.
should I reboot?
and then Its ok to load a rom?
thanks
radio should be ok as it was just loaded from htc?
Ya you should be good don't worry you can't brick it by flashing something to the system partition only to the recovery and hboot partitions. Just select reboot system now and all should work fine.
Sorry for the late response I was away from my computer
still stuck on nexus x screen ??
earlier someone posted that when I used superbot I got the wrong kernel?
not sure but still stuck
just tryed to boot into recovery and it wouldnt go
Oh right sorry forgot an important step you kind of need a ROM my bad ok so forget about su you're going to need to flash a ROM I suggest cyanogen mod as a first ROM but it's up to you if you want miui or something then go for it. Here's a link to cm7 http://dl.dropbox.com/u/31690913/android%20files/update-cm-7.0.3-N1-signed.zip
So to flash this simply boot into recovery then go to wipe, wipe all at least 2X I do 5X to make sure then just go to flash zip from sd card and flash the ROM.
In that case do like we did last time and reflash it through fastboot. Now sorry but I gotta go maybe someone else can come and help you if not I'll be back later tonight.
thanks
thank you so much for helping me with this got everything working including the new miui rom.
when you panic just a little you forget all the things you knew how to do before.
thanks again.
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
PoRco1x said:
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
Click to expand...
Click to collapse
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Hey I got the phone to restart and it goes almost immediately into the HTC screen again. I think "fastboot" setting is on or something. I just can't get it to go to the bootloader
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Just tried it under my bright lamp too. No dice
Okay so I used Hansoons AIO toolkit to get it to load into CWM-based Recovery... phew
What's next!?
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
expertzero1 said:
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
Click to expand...
Click to collapse
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
PoRco1x said:
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
Click to expand...
Click to collapse
It doesn't matter, once you're in cwm recovery, reflash the Rom with a full wipe and you should be good. Calm down dude.
Sent from my HTC One using xda premium
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
What are you holding to try to enter bootloader? I use power and volume down and it works every time. Just hold them until the bootloader screen appears then let go.
Also, like others have said, it's better to use adb and fastboot commands yourself in cmd or terminal, rather than using the toolkit - it's not too hard, there are plenty of guides, you learn quicker and it's more satisfying
Sent from my HTC One using xda premium
ryryzz said:
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
Click to expand...
Click to collapse
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
redbull123 said:
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
Click to expand...
Click to collapse
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
PoRco1x said:
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
Click to expand...
Click to collapse
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume and power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
JazLiew said:
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, I tried that too. The phone was INITIALLY just stuck and wouldn't even restart. Nothing I did made it restart until finally... I used adb reboot bootloader to make the phone finally restart into the HTC screen. But no matter what I try to do, it hasn't taken me to the bootloader even ONCE, ever since I got the phone in fact.
Should I push in a new rom using adb? And if so, which one? Android Revolution HD (fresh download) or a different one that you recommend?
Btw, I apologise for the delayed replies, the forum is making me wait between each message since I'm new
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
redbull123 said:
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's funny you mention that! I had serious issues navigating through the aroma installer, I would have to click the "next" button at least 2-3 times. And when I tried using the volume buttons, it would only go to the button inbetween "back" and "next" which was something like "more info"
Does this point toward any other issue? Or should I go ahead with flashing rom again?
ryryzz said:
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
Click to expand...
Click to collapse
I used adb reboot bootloader to get OUT of the installtion screen, but it didnt take me to the bootloader (as usual) it just restarted. The AIO tools also didn't take me to bootloader when I used one of the commands there. So going to booatloader is really being impossible now!!
I think u need to send it to repair or warranty. Since you can't go to bootloader there's a lot of things you can't do right now.
So now I have two options at hand now...
1) Go ahead with rom installation (this I know how to do)
2) Flash official stock using RUU (this I dont know how to do yet, since I'm not entire sure what carrier this was initially on)