Related
So, after following this forum on and off over the past few months, I finally decided to root my Rogers Dream.
I was one of the first customers to receive a phone with SPL 1.33.0010, as mine was shipped to me directly from rogers as a hardware upgrade. Because of this, rooting was a little more difficult for me than I had initially anticipated, however, after having found this thread (http://forum.xda-developers.com/showthread.php?t=558301), I was able to downgrade to SPL 1.33.2005.
From this point, I started following the instructions found here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod. I was able to re-flash the downgraded OS, and rebooted to a T-mobile G1 splash screen. After going through the various steps, I got stuck where it said to reboot into recovery mode. I held down the home key while powering up, as instructed, but instead of booting to the recovery screen, I was greeted with an image of an exclamation point inside a triangle, hovering over a cartoon of a G1.
I was able to reboot using the 3 fingered salute (send-menu-power), but I was unable to load the recovery screen. I then attempted to bring up the boot loader by holding down the camera button while powering on. The screen I was greeted with did not resemble the boot loader I was used to seeing. It is composed of four horizontal coloured bars, and lists the phone information as follows:
DREA210 PVT 32B
HBOOT-0.95.000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I'm looking for suggestions on how I should proceed from here. Any help would be most appreciated. Although the phone does make phone calls, and will send and receive text messages, it will not send or receive data, unless connected to wifi.
Thanks,
Grant
So I'm a little rusty but let me give it a shot. While holding home + power it may seem to just get stuck after a minute, but have you tried pressing alt + L ? This makes the recovery text visable (if it's not by default).
hope this helps..
Looks like you've ended up on the stock g1 bootloader.. did you flash the rc29 DREAIMG?
goldenarmZ said:
Looks like you've ended up on the stock g1 bootloader.. did you flash the rc29 DREAIMG?
Click to expand...
Click to collapse
Yes. The phone thinks it's a T-mobile G1, but it still works with my Rogers SIM.
sonikamd said:
So I'm a little rusty but let me give it a shot. While holding home + power it may seem to just get stuck after a minute, but have you tried pressing alt + L ? This makes the recovery text visable (if it's not by default).
hope this helps..
Click to expand...
Click to collapse
I did this, and the recovery text did indeed become visible, however, I now have a new problem.
I hit Alt+W as per the instructions in the wiki, and it reset the phone. I then hit Alt+A, and nothing happens.
This is the text I see on the screen when I'm in recovery mode:
Androind system recovery utility
E:Can't open /cache/recovery/com
mand
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
After attempting Alt+A, I hit Alt+S, just to see what would happen. Of course, it tried to update from package, but returned an error because there is no "update.zip" on the phone. I'm tempted to rename "update-cm-4.2.5-signed.zip" as "update.zip", just to see what happens. I'll post again once I've done this, but any suggestions from more experienced people would be most appreciated.
Grant
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Alright, so I renamed "update-cm-4.2.5-signed.zip" as "update.zip", and it aborted the installation because there was no signature. I did the same thing with "signed-dream_devphone_userdebug-ota-14721.zip", with the same result.
It sounds like you still have the stock recovery image
jackslim said:
It sounds like you still have the stock recovery image
Click to expand...
Click to collapse
When you say stock recovery image, are you referring to the one I have installed on the phone already, or the one I'm trying to install with no success?
The image currently on the phone is the DREAIMG.nbh (rc29), which I downloaded via the wiki. The images I am trying to load also came from links in the wiki.
By recovery I'm refering to what you access when you boot with home + power where you can apply your updates (where you're seeing your triangle & exclamation point)
I just looked at cyanogen's wiki and it seems like that particular part could stand to be updated androidandme has a decent guide on how you could do this though.
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
I'm not sure if flashrec works with RC29 which is what version you should be on after flashing DREAIMG.nbh, but you can give parts A1, A2, & A3 a shot, that would probably be the easiest way to update your recovery. If you can't get flashrec to work skip down to B2 and that will show you how to do it using telnet which does work from RC29
Once you update you're recovery image you should be able to apply "update.zip" or without renaming them by selecting the "apply any zip from sd" option
Thanks, Jackslim. I did as you suggested, and was able to install the CM update, as per the wiki, however, when it boots up, it shows the blue cyanogen android, and then reverts to a completely blank screen. I'm going to try reinstalling everything to see if that fixes it. Thanks for your help though.
gmupps said:
Thanks, Jackslim. I did as you suggested, and was able to install the CM update, as per the wiki, however, when it boots up, it shows the blue cyanogen android, and then reverts to a completely blank screen. I'm going to try reinstalling everything to see if that fixes it. Thanks for your help though.
Click to expand...
Click to collapse
After you install that recovery image you still have to go through the steps to install the ADP image before you add the cyangen update, then you should be cookin' with crisco
So just start back up on cyanogen's wiki from the section called "File Download"
Just to clarify, even though it is not booting up properly, I am now able to install whatever I want using recovery mode, so it's just a matter of figuring out what will work. Thanks again for all your help.
jackslim said:
After you install that recovery image you still have to go through the steps to install the ADP image before you add the cyangen update, then you should be cookin' with crisco
So just start back up on cyanogen's wiki from the section called "File Download"
Click to expand...
Click to collapse
I did get it working, thanks. Now I just have to reload all my contacts and apps, but I have already noticed a difference in device responsiveness. It's like going from Windows Vista to Windows 7. Thanks again.
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
If you have recovery, you should be fine. Just flash your favorite image and wipe your userdata.
DOD1 said:
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
Click to expand...
Click to collapse
Holding Home + Power is supposed to take you into the recovery image.
At the bottom of your recovery image does it say Amon Ra 1.5.2 or 1.6.2 or something like that?
If your phones rooted then just wipe and reinstall you rom.
Like lets say your doing the new cyanmod
you apply zip
DR83
With out rebooting apply zip
Cyanmod-rom 1.4xxxx
If it boots back into Android System recovery Utility just hold home and back again.
Give it time to write its radio and its first time rebooting it says on the boot screen for a awhile some longer then others.
This site has always helped me its better to see the instructions rather then read them.
http://www.google.com/search?q=the+...s=org.mozilla:en-US:official&client=firefox-a
figured it all out.. thanks!
Means you don't have a recovery. Need to most likely run the 2.1 ruu and reroot with eris one click. Something went wrong and it didn't flash Ra recovery
i hope your ok buddy,try it again but check if the root me.zip file is in your sd card first before you go into recovery,if its their it should of flashed the recovery.
Sent from my Vanilla Tazz using Tapatalk
thank you. i googled and found instructions for flashing amon ra recovery. but it fails in the first couple steps. when it tells me to run "su" from the shell command it tells me permission denied. the phone is not rooted yet, so i can not allow superuser from the phone as most of my googling has suggested.
what now?
the rootme.zip is on the sd card.
did u reboot after you pressed the button? and then did u turn it off and go to recovery?
mindnumbinglyfun said:
trying to root my friends phone (using the one-click root for eris) ive run into a problem i havent seen before, and cant find answers for on google or this site.
when i reboot the phone into recovery holding volume up with powering on, i get a picture of the eris, with a red triangle and exclamation point. and thats it. i cant do anything.
any idea what it is or how to get rid of it?
Click to expand...
Click to collapse
That is the splash screen of the stock recovery.
It means that flashing of Amon_RA never happened.
[ For goofs, you can prove it is a stock recovery by pressing Vol-up+End again when that image is on the screen. (If you were rooting a Cupcake Eris, the key sequence would be Home+End) ]
As others have pointed out, the primary reason that OneClick fails is that the person using it fails to perform a normal reboot in between use of the app and cold-booting into the recovery. Just reboot your phone once normally, shut it down, and then cold-boot to recovery.
- install app
- run app
- shut down phone normally
- reboot phone normally
- shut down normally
- cold boot into recovery
One more thing; you know that this is not a development topic, yes?
bftb0
Hey!
This is the issue: when I try to turn the phone on by just pressing the red button it goes directly to the fastboor menu. If I try to go to the recovery from there shows "TATTOO" for hours. If i try to go to the recovery dirctly by pressing HOME+ red button, it firsto shows the fastmenu for a second and tries to boot unsuccessfully. During this boot tries, I try to get some info with adb logcat, but the device is not casting anything. And well, if a picture is worth a thousand words, I guess a video is way better:
youtube.com/watch?v=zAejyMIVNGk (newbie, no urls!)
sorry for my english
And well, I have no idea how I got to this, this used to be my phone, but I bought a Nexus One and gave this to my sister, who has no idea what happened (as usual). Oh, this morning somehow I managed to get to the recovery menu, and booted until the android bootscreen, then vibrated and died again. I got to the recovery again, made a nandroid backup and wiped all data, it booted successfully, but the rom had no home application and ran really bad.
I was about to try to make a goldcard and install the stock RUU rom, but if I have no adb I cannot make one...
Any idea?
PS: the rom was nFinity 1.18 (2.2 Froyo) and the recovery was the lastest Clockwork.
PS2: I just realized that in every place I say fastboot I mean HBOOT, sorry again
sounds like recovery is still there, if you hold home + menu when phone if off , and then click red power button you should get recovery menu.
Then hopefully you can try full wipe and install a rom , rember the first time u boot a rom might take a few minutes
let me know how it goes
Yup, not using that method but I can manage to get to recovery sometimes. I'm trying to flash another ROM, but for some reason it doesn't let me. I've tried KalimochoAz (gingerbread) and HDCR (donut) and says something about assertion failed when checking if the device was click on the first case and in the second, complains about unsupported stuff...
I was about to try another roms by random but the SD does not refresh or even mounts, there must be something really messed up with this phone...
You can try to flash your stock rom from fastboot.
You don't need a goldcard, just run the update utility on pc, go to your temp directory and take the rom.zip file, rename it to CLICIMG.zip, copy it to sd card, put card on device and on fastboot menu pres vol down to start flashing the rom. I is the same version with the rom that device has before rooting, you will not get any errors.
I think there's a little misunderstanding here, mainly because of my confusion, it's not the fastboot menu qhat I get, but the HBOOT menu, and pressing the back button in order to access fastboot doesn't work...
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
manutenfruits said:
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
Click to expand...
Click to collapse
Of course will not work like this.
You must first run the RUU utility on pc and while is open to search your temp directory(maybe is inside another folder) for rom.zip file. This is the rom, the executable is an installation program which contain the rom and the app to flash the rom from pc packaged. You need only the rom.zip for flashing from sd card.
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
manutenfruits said:
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
Click to expand...
Click to collapse
You don't need to go so far. Just run the ruu utility and when the first screen appears go to temp dir(c:\users\you user's name\local\appdata\temp on windows 7). The executable is an encrypted package and when you run it extracts all included files and then starts the installation program. These files will deleted after this program exits(when the installation complete or an error occurs)
Cool! I just renamed it to CLICLIMG.zip and I finally loaded. The problem now is that when it finishes, instead of asking me to flash it, says
"CID Incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No"
While running the RUU I made sure that it was for HTC Tattoo since it showed me the device during the steps. And I got it from a post describing the steps to flash it using the goldcard.
Furthermore, this error is something similar to what happened when I tried to flash from the recovery. This is REALLY weird...
Probably this isn't the sama as your device's stock rom. I think goldcard needed for flashing any htc original rom, but without goldcard only the device's version will be flashed successfully. Try to download other original roms if you don't know which you had before.
Here is a site with shipped roms for tattoo:
http://www.shipped-roms.com/index.php?category=android&model=Click
The RUU wasn't a problem, I tried now with a goldcard and flashed successfully! I could not get ADB connection to make it, but I once made one and still had the .img in my mail inbox.
But still nothing has changed...
pressing on drives me to the HBOOT screen, whose only options that work are "simlock" to flash CLICIMG.zip, and recovery (freezes on "TATTOO")
EDIT: does not freeze, but goes back to HBOOT after a while... ¬¬
You say that now you have the stock HTC rom and again you cannot boot it and instead the device reboots again to HBOOT?
Then maybe you have a hardware problem which leads to this behaviour.
OK, now I guess it still has warranty, but the problem is that I rooted it.
But now that I flashed somehow the original rom, should be no problem right?
Yes, if you successfully flash the stock rom, you're not root any more.
had that problem to, but theres easy fix for it without doing all whats being sayd here
Even tho phone dont boot annymore and stays on logo plug in the usb cable
and work with adb shell and reflash recovery (to be good tattoo-hack.ko etc tricks need to be done before doing it or you get errors)
http://forum.xda-developers.com/showthread.php?t=716282 step 1.5 and tools from step 1.3
and ether get Amon RA recovery or clockworkmod and use
Code:
./flash_image recovery /sdcard/recovery.img
then reboot into recovery
HTML:
adb shell "reboot recovery"
mount usb put in a custom rom and flash it
if all done well should work (had same problem)
bascly adb still work even if you think you bricked phone just have to let it "startup"
Greetings
I'm afraid that won't work. I've been trying all the time with adb logcat and adb devices unsuccesfully. I thought that the TATTOO bootscreeb would give me some feedback in all cases, but now doesn't seem to work...
I've had similar problems when trying to flash nfinityGB.
My problem was that I missed something on the way from
- creating a gold card
- rooting device
- installing recovery
- flashing rom
All I did was to download and execute "RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe" (or any other ruu).
Be shure to have SDK with all drivers installed properly.
After this your device is in unrooted (original) state as dancer_69 already told you.
Now you can decide whether to claim warranty or properly follow the guides on xda to get root and flash custom roms.
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
manutenfruits said:
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
Click to expand...
Click to collapse
Something like this thought when I said that maybe is a hardware problem.
woke up and it was sitting in recovery, so i rebooted a few times to only end up in the recovery screen. i then wiped the cache and system and rebooted,and when TWRP asked if i wanted to root, i swiped right(never seen that screen before). but this time im stuck at the LG logo with no options for recovery/reset/etc.
when i plug it into my PC, device manager sees it as "LGE Android phone". HELP PLEASE! thanks.
bump?
Were you rooted running stock or a custom rom at the time this happened? Try to long press power for 15 seconds to shut the phone down, then use the hard keys to enter recovery. Is TWRP still availabe or no?
iowabowtech said:
Were you rooted running stock or a custom rom at the time this happened? Try to long press power for 15 seconds to shut the phone down, then use the hard keys to enter recovery. Is TWRP still availabe or no?
Click to expand...
Click to collapse
custom rom based off the stock 4.4 and im not sure i remember if i rooted or not. I cant enter recovery. thanks for replying!
wasssabi5 said:
custom rom based off the stock 4.4 and im not sure i remember if i rooted or not. I cant enter recovery. thanks for replying!
Click to expand...
Click to collapse
Well you were clearly rooted if you were running a custom rom. Since you were in TWRP following the mishap, it should still be there. You sure you're going about that correctly? You need to press and hold power for 15 seconds to power off. Then use whatever button combo is necessary for your variant, there are some differences. Then accept the factory reset option to enter TWRP.
My guess, and it's only a guess...is that your phone, being close enough to stock, applied an OTA without your knowing or even choosing to accept it which landed you in a recovery reboot loop. That's a known side effect on a G2 with stock + custom recovery. But since you were on a custom rom and you said you wiped system, it's no mystery that you don't have a booting phone. You need to get back into TWRP, adb push a rom to /sdcard and flash it. Unless of course you have a working nand backup in which case you can restore that and save yourself some time and effort.
iowabowtech said:
Well you were clearly rooted if you were running a custom rom. Since you were in TWRP following the mishap, it should still be there. You sure you're going about that correctly? You need to press and hold power for 15 seconds to power off. Then use whatever button combo is necessary for your variant, there are some differences. Then accept the factory reset option to enter TWRP.
My guess, and it's only a guess...is that your phone, being close enough to stock, applied an OTA without your knowing or even choosing to accept it which landed you in a recovery reboot loop. That's a known side effect on a G2 with stock + custom recovery. But since you were on a custom rom and you said you wiped system, it's no mystery that you don't have a booting phone. You need to get back into TWRP, adb push a rom to /sdcard and flash it. Unless of course you have a working nand backup in which case you can restore that and save yourself some time and effort.
Click to expand...
Click to collapse
how exactly do i get back into TWRP? my phone cant access recovery
wasssabi5 said:
how exactly do i get back into TWRP? my phone cant access recovery
Click to expand...
Click to collapse
If using hard keys it can vary slighly by variant. adb reboot recovery should do it though.
huh, took apart the phone to try the linux fix(didnt end up working), put it back together, and now the download mode works. not sure if i was just being stupid in the past or what, but HURRAY! thanks so much