Related
I'm a newbie with this phone that need some pro point me to the right direction. I have a G1 with unknown history, all it doing now is when turn on, after G1 logo, it go straight to recovery mode. I tried Alt+L and Alt+w to factory reset but it doesn't help. I followed other thread and tried to install Download HTC Dream Image 1.6 but getting the following error
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E: No signature (412 files)
E:Verification failed
Installation aborted
on top of the screen it show Android system recovery <2e>
I been googling but was overwhelm with all different rom and instructions.
and I can't get the phone to enter bootloader mode when press Camera + power, it just go straight to recovery mode.
abcchoier said:
I'm a newbie with this phone that need some pro point me to the right direction. I have a G1 with unknown history, all it doing now is when turn on, after G1 logo, it go straight to recovery mode. I tried Alt+L and Alt+w to factory reset but it doesn't help. I followed other thread and tried to install Download HTC Dream Image 1.6 but getting the following error
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E: No signature (412 files)
E:Verification failed
Installation aborted
on top of the screen it show Android system recovery <2e>
I been googling but was overwhelm with all different rom and instructions.
and I can't get the phone to enter bootloader mode when press Camera + power, it just go straight to recovery mode.
Click to expand...
Click to collapse
something's wrong with the image file you're trying to install. From the looks of it, the files aren't signed, so the phone won't install it.
I'm assuming you're looking for the official 1.6 image and you have a regular g1, not a ADP1 so...
look around the forums here, someone reuploaded those files since htc pulled them down from their website.
Be aware that if you just install the official 1.6 image, the recovery menu is gonna be gone. Or at least it was for me when i did. You're gonna have to reinstall the recovery menu if you use just the official image, without any other roms like CM.
Do I need to install this Dream 1.6 image first or fix SPL since I can't get to bootloader? How can I flash Radio and SPL if I can't get to bootloader mode?
abcchoier said:
Do I need to install this Dream 1.6 image first or fix SPL since I can't get to bootloader? How can I flash Radio and SPL if I can't get to bootloader mode?
Click to expand...
Click to collapse
Follow this guide if you have a Tmobile G1
jamesrdorn said:
Follow this guide if you have a Tmobile G1
Click to expand...
Click to collapse
thanks for the response. I followed the step but stuck at step 4. Whe I hold the camera button and select reboot option, after phone reboot, it go back to the recovery screen, no grey screen at all.
ahhh!
abcchoier said:
thanks for the response. I followed the step but stuck at step 4. Whe I hold the camera button and select reboot option, after phone reboot, it go back to the recovery screen, no grey screen at all.
Click to expand...
Click to collapse
did you ever find a fix?? i'm having the same problem
Your Home key isn't stuck is it? If you only press Back while you're in recovery, does the phone reboot, or do you HAVE to press Home + Back? It's a longshot, but that would be an epic facepalm if I may say so myself.
Im pretty much having this same problem, i cant even get into shell via adb, I get a "exec '/system/bin/sh' failed: No such file or directory (2)" error. another error that i am getting is the E:Can't read MISC: (no space on device) in the recovery console, and i read that the MISC partition contains boot information. i would really like to find a solution to this as i have been looking for a few months now.
abcchoier said:
I'm a newbie with this phone that need some pro point me to the right direction. I have a G1 with unknown history, all it doing now is when turn on, after G1 logo, it go straight to recovery mode. I tried Alt+L and Alt+w to factory reset but it doesn't help. I followed other thread and tried to install Download HTC Dream Image 1.6 but getting the following error
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E: No signature (412 files)
E:Verification failed
Installation aborted
on top of the screen it show Android system recovery <2e>
I been googling but was overwhelm with all different rom and instructions.
and I can't get the phone to enter bootloader mode when press Camera + power, it just go straight to recovery mode.
Click to expand...
Click to collapse
i have the same problem and i try to unbrick but i dont see the grey screen ethir....it took me to system recovery again.....how can u solve this?
Hi,
I have the same problem. My DREA110 HTC G1 T-MOBILE (UK) phone shows me an EXCLAMATION mark in a triangle form.
When i press ALT - L it shows me ANDROID SYSTEM RECOVERY 2E menu with 4 options
reboot system now HOME BACK
apply sdcard:update.zip ALT S
wipe data/factory reset ALT W
wipe cache partition
these are tried so far.
1-I have rebooted phone using 1 option in menu but got same error message.
2-downloaded Android 1.0 RC33 from here (http code google com/p/android-roms/wiki/Unbrick) and renamed as update.zip and put into a FAT32 formatted 2gb memory card and used apply sdcard:update.zip option but received error messages below
E:CAN'T MOUNT /DEV/BLOCK/MMCBLK0P1
(OR /DEV/BLOCK/MMCBLK0
(NO SUCH FILE OR DIRECTORY)
E:CAN'T MOUNT SDCARD:UPDATE.ZIP
INSTALLATION ABORTED
i am a newbie please help.
Anyone ever figure this out? Trying to help a friend out with a G1.
buttered_popcorn:
http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
Just use this^
The downgrading part should restore you back to stock 1.0
My belief is that if you screw up restore to stock 1.0 and redo everything
If you gave us a bit more detail though we might find a easier method for you
Thanks, my friend got the phone with a broken screen and all it does its boot to the screen with the exclamation point on it.
Followed the guide in your link to downgrade the firware. We get stuck on the step to boot into bootloader. Holding camera and power just gets us to recovery (screen with exclamation) not into bootloader. After messing around a bit I found that if I hold "home" and "back" and then press power it SOMETIMES goes into bootloader. When I do get into bootloader nothing works to flash the .nbh file. By nothing works i mean no buttons work at all to flash or to cancel.
buttered_popcorn said:
Thanks, my friend got the phone with a broken screen and all it does its boot to the screen with the exclamation point on it.
Followed the guide in your link to downgrade the firware. We get stuck on the step to boot into bootloader. Holding camera and power just gets us to recovery (screen with exclamation) not into bootloader. After messing around a bit I found that if I hold "home" and "back" and then press power it SOMETIMES goes into bootloader. When I do get into bootloader nothing works to flash the .nbh file. By nothing works i mean no buttons work at all to flash or to cancel.
Click to expand...
Click to collapse
Than its a hardware problem
The buttons are broken
You can try take it apart and look inside, but it sounds like it's totalled.
thats what we decided last night also. Thanks for the help
Same issue but a little more twisted
I tried flashing my G1 and it bricked(Soft Brick).
Somehow by luck I flashed the DREAIMG.nbh and have a stock phone now.
But the problem is I cant pass the Stratup screen because I get no network.
Unable to connect to the internet as well.
I tried the orange DREAIMG.nbh which bypasses the startup screen, even thought i come to the Home screen i get no network.
It gives an Error while trying to search for a Network.
When i try to flash any update.zip files it gives an error
E: No Signature
E: Verification Failed
Installation aborted.
When I enter the Recovery mode i get a error line saying " E: Can't open /cache/recovery/command
Any run around to this??? Is this by any chance a Hardware issue?
I doubt it, what recovery do you have? Also with the spl you know have just use fastboot flash for you roms, your error rate will be down to nothing
Sent from my HTC Desire Z using xda premium
Its a Android System recovery utility, I cant get to the home screen also becuase i have no connectivity to get past the the Google sign in screen...
I tried the Fastboot but have no idea how to go with it!!
Need some help with it...
There are plenty of fastboot how tos amoung these threads here, otherwise go straight to the sdk website and there will be plenty of options, on my phone now so I can't walk you through it well. Pretty much download the sdk package to your comp and then make sure all the proper drivers are downloaded. Either change the variables in your device manager or open a cmd in the folder where fastbooot is located. You can also just change directories to get there. Put the files you need in the same folder as fastboot. Plug in your phone with it in hboot mode and you should see fastboot usb show up. The do fastboot -w then fastboot flash for whatever rom you need. Check the toutorials it will be more help
Sent from my HTC Desire Z using xda premium
sandy_nocturnal said:
I tried flashing my G1 and it bricked(Soft Brick).
Somehow by luck I flashed the DREAIMG.nbh and have a stock phone now.
But the problem is I cant pass the Stratup screen because I get no network.
Unable to connect to the internet as well.
I tried the orange DREAIMG.nbh which bypasses the startup screen, even thought i come to the Home screen i get no network.
It gives an Error while trying to search for a Network.
When i try to flash any update.zip files it gives an error
E: No Signature
E: Verification Failed
Installation aborted.
When I enter the Recovery mode i get a error line saying " E: Can't open /cache/recovery/command
Any run around to this??? Is this by any chance a Hardware issue?
Click to expand...
Click to collapse
have you configured your network orange in APN ?
Sorry I'm French
I have a problem with one phone and I found it on the site
There is just a mistake, we must put the sim card in the phone
"androidforums.com/g1-support/6564-activate-stock-g1-over-wifi.html"
I just downgraded to stock 2.1 on the incredible after rooting in anticipation for the official update. However, now I have a problem. Although the ROM took I can't seem to get into Recovery on the Hboot menu. Any ideas on what went wrong or how to fix this? I am little concerned about trying the procedure again. The screen just hangs at a picture of the phone with a "!". But the phone still boots and functions fine.
Thanks in advance!
Did you lose root?
At that screen you need to press the power button and up button at the same time to get into recovery mode.
No, I no longer have SU permissions.
ijason87, that worked, however now when I get into that screen it says the following "E: Cant Open /cache/recovery/command". Is that normal, I dont recall that error when I did a recovery wipe not long ago. It does give me options to apply update.zip and factory wipe.
Hi,
I've been trying to install different images to a HTC Wildfire. As some apps were unavailable at the marked, I tried to got back to 0001_WildPuzzleROM_v8.0.8.zip.
Thing is, the phone has a bootloop. I cannot enter the recovery. Pressing POWER+VOLDOWN does not start the recovery. Other button combindations don't help. As soon as the green robot comes up, POWER+VOLDOWN+TRACKBALL result in immediate reboot. I tried a replacement of the SD-Card, no SD-card, and no SIM. All of this does not help.
In the BIOS-Bootscreen, there is "press the TRACKBALL" written. But the TRACKBALL does not work there, too.
Checking with ADB yields an unknown device with no permissions.
Is there any chance to unbrick the phone or is it finally dead?
TYIA
dsplayer
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.
Hello
I bricked my M3 and tried using Huawei Tool to unbrick it.
I followed all the instructions, and realized that the bootloader needed to be unlocked. I unlocked it and since then, I can't enter Fastboot mode.
I've tried pressing Vol - and power and it's stuck in a loop where it tells me
"Your device has been unlocked...
Your device is booting now"
And then it doesn't move.
Am I screwed?
Thanks a bunch
My device is a BTV-W09
I saw many of the same symptoms and I showed the same symptoms.
At this time, there seems to be no recovery method.
Same symptons as you. I guess the fastboot partition wiped itself after unlocking so there's no way else to get in anymore.
Same here: unlocked bootloader than flashed TWRP (maybe not the right one) and now the TABLET power ups for only 3 seconds with the message "Your device has been unlocked...Your device is booting now" and then it shuts down!!
Anyone could suggest me how can I return to fastboot mode to try to relock the bootloader?
Thank you very much!!!
(I tried VOLDOWN+POWER / VOLUP+POWER with and without USB cable connected with the PC but after 3 seconds of warning message it shuts down!!)
Anyone could help?
I've found a possible solution: pressing BOTH VOLUME UP AND DOWN and POWER the tablet search for a system update inside SD CARD. I've tried with the only one update I've found online and in fact the system waits few seconds with a blank screen before rebooting again. This is a different behaviour from the usual brick loop.
I think that the update found in the SD card isn't compatible with my tablet.
Anyone knows where can I find the right or compatibile upload->UPDATE.APP for CPN-W09 model? I think this could be the only one way to restore a bricked recovery partition that cause this boot loop.
THANKS!
ETOSoft said:
I've found a possible solution: pressing BOTH VOLUME UP AND DOWN and POWER the tablet search for a system update inside SD CARD. I've tried with the only one update I've found online and in fact the system waits few seconds with a blank screen before rebooting again. This is a different behaviour from the usual brick loop.
I think that the update found in the SD card isn't compatible with my tablet.
Anyone knows where can I find the right or compatibile upload->UPDATE.APP for CPN-W09 model? I think this could be the only one way to restore a bricked recovery partition that cause this boot loop.
THANKS!
Click to expand...
Click to collapse
Volume up + Hold Power for 3-4 Seconds during the locked boot. When the screen goes blank let go of both and it should go into recovery like it was supposed to. You have to let go though at the right time. I unbricked some op phones doing the same thing but it's been awhile.