i flashed the old ere27 using rom manager and put the froyo zip on my sd card. flashed it and got stuck in a boot loop. i pulled the battery and went to recovery but my custom recovery isnt there. its just a picture on an android and a traingle with a exclamation point on it. wtf. i dont care about getting froyo running but i cant get into recovery at all
1. Wrong section
2. Fastboot flash a custom recovery
pjcforpres said:
1. Wrong section
2. Fastboot flash a custom recovery
Click to expand...
Click to collapse
i cant get fastboot working now. damn its not my day. when i hit fastboot devices nothing pops up
Try from your computer: fastboot boot recovery recovery.img
recovery.img = your Amon Ra recovery file and it could be in under another name so rename it to recovery.img
b33zy682 said:
i cant get fastboot working now. damn its not my day. when i hit fastboot devices nothing pops up
Click to expand...
Click to collapse
try using a different USB port or cable.
Related
My first post but I've been lurking for years. Pretty good with search, etc.
If anyone could help I would really appreciate it. I've been working on this for 12 hours!
I updated to Cyanogen 4.1.999
I successfully installed the new radio and fastboot confirms 2.22.19.261
Here's where I made the mistake in the following directions:
I have CMRecovery Image 1.4
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-4.1.99
http://n0rp.chemlab.org/android/expe....99-signed.zip
-put them both on your SD card
-Boot up into CM recovery image 1.4 by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
I mistakenly rebooted normally instead of applying the update in the next step. This is when the black screen began.
-Then update any zip usig CyanogenMod-4.1.99 (update-cm-4.1.99-signed.zip)
-Then power on the phone
I am stuck at the black screen of death.
I can fastboot and I've fastbooted the pimp recovery and still can't access recovery. Just get the triangle.
So, during update after new radio I rebooted normally instead of updating with the final build update got a black screen and have no recovery.
I've tried fastboot flash recovery and fastboot update.
fastboot flash recovery is succesful
fastboot update or fastboot flashall give me the "archive does not contain android-info.text and android-product.text" errors.
Any ideas would be greatly appreciated.
this should be posted in Q/A not development.
cingall said:
this should be posted in Q/A not development.
Click to expand...
Click to collapse
Sorry!
Mod please move. Thanks!
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
theomajigga said:
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
Click to expand...
Click to collapse
any ideas on the commands to flash them as flashall? HTC's site has them as separate files so I can only flash the "recovery" file.
I'm sorry to be somewhat of a noob with the actual codes. Could you be more specifc with which files to flash with which commands?
TIA!
Using the HTC website 1.6 "recovery" with fastboot update I get the following:
Error: update package has no android-info.txt or android-product.txt
I can't figure out how to flash the radio or system files in any other way than update in fastboot.
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Also remove your SD card while booting, as prior stuff in your ext3 partition can cause black screens during boot. If that fixes it, you need to reformat your ext3.
The triangle you see is the standard recovery, to access it you need to do alt-L?or alt-x cant remember. To fix you need to flash cm-recovery to do this reboot into the boot loader (power + camera) plug in usb and hit the back button you should see "fastboot" then run
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
seehttp://forum.xda-developers.com/showthread.php?t=523558
then install rom as normal
okay this happened to me as well. I just made sure that I wiped, then started allover again. i had to do it a couple of times but it worked. just make sure that you still have the files on your SD card.
Good Luck!!!!
brnbock said:
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Click to expand...
Click to collapse
You are a STAR!! Thank you, thank you, thank you!! I knew it was something stupid!
Back at the recovery console! woot!!!
Mods please close this thread!
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
took 30 min to post a re.. sorry i was late
fastboot erase recovery
fastboot flash recovery *name of recovery*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
That should fix it.
ugh, now I am stuck at the g1 screen after a reboot of a successful update.
reformatted sd and all probs are solved!
mghtyred said:
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
Click to expand...
Click to collapse
Hi mghtyred (of tmobile forums) welcome to XDA
So i was trying to use Rom manager with my rogers htc dream with the new universal root stuff and while using the rom manager the part where it said it will boot into recovery mode to flash it just stayed at the Rogers screen any ideas ?
Can you get into the recovery by holding home while you power on? Or Fastboot by holding camera?
cyberclone33 said:
So i was trying to use Rom manager with my rogers htc dream with the new universal root stuff and while using the rom manager the part where it said it will boot into recovery mode to flash it just stayed at the Rogers screen any ideas ?
Click to expand...
Click to collapse
Just boot up the rom normally then go to rom manager
Settings > check erase recovery when flashing a new one.
Then flash it again.
If that doesn't work ADB will do the trick:
Go into fastboot USB
from your computer type:
Code:
fastboot erase recovery
Load up the rom normally again and then try reflashing the clockwork recovery again.
If all else fails
download amon-ra recovery
Fastboot usb
Code:
fastboot erase recovery
fastboot flash recovery (location in with the recovery is stored desktop downloads etc)
If you're using windows you can just drag the recovery over into command promt and it should automatically list the file for you.
I have moto x dev ed, I just unlock the bootloader. i tried to install this custom recovery i keep getting this.
<bootloader> variable not supported!
target reported max download size of 805306368 bytes
etc etc...
im trying to download the twrp custom recovery
i dont why it keeps doing that
I know when fastboot flashing the system.img you must use mfastboot due to the partition size, but the recovery.img should flash with fastboot. Maybe give mfastboot a try?
Groid said:
I know when fastboot flashing the system.img you must use mfastboot due to the partition size, but the recovery.img should flash with fastboot. Maybe give mfastboot a try?
Click to expand...
Click to collapse
It worked But when I try to load it , now When I tried to load twrp it shows the dead android logo
Fastboot the recovery.img then type fastboot reboot and choose recovery in fastboot menu
dat010man said:
It worked But when I try to load it , now When I tried to load twrp it shows the dead android logo
Click to expand...
Click to collapse
Sounds like it did not flash correctly because the laying down android leads to the stock recovery. I would try redownloading twrp for ghost again and make sure that is in the folder with fastboot and verify your getting the file name correct when flashing. Just repeating the steps all the through may be successful, we all miss a step occasionally. Good luck [emoji106]
Edit: p.s. I did read somewhere that some people had issue with recovery not sticking after flashing. They got around this by typing the command fastboot reboot bootloader right after flashing the recovery. After that custom recovery would stick.
I'm still getting the same error. Am I suppose to hold the volume up button until the recovery loads?
If you are boot loader unlocked and rooted just use flashify to flash the image file.
---------- Post added at 03:37 AM ---------- Previous post was at 03:32 AM ----------
After you flash your recovery are you booting straight to recovery with the volume up button?
Travisdroidx2 said:
If you are boot loader unlocked and rooted just use flashify to flash the image file.
---------- Post added at 03:37 AM ---------- Previous post was at 03:32 AM ----------
After you flash your recovery are you booting straight to recovery with the volume up button?
Click to expand...
Click to collapse
Yes I am booting to recovery with the volume up button, immediately after I flash it. Alright I will use flashily when I get home after working. Wait no I am not rooted.. I just unlock the boot loader only. I thought you download twrp first and then download supersu to root?
dat010man said:
Yes I am booting to recovery with the volume up button, immediately after I flash it. Alright I will use flashily when I get home after working. Wait no I am not rooted.. I just unlock the boot loader only. I thought you download twrp first and then download supersu to root?
Click to expand...
Click to collapse
Are you opening the command prompt from the same folder as you twrp.img file and your fastboot.exe file?
Travisdroidx2 said:
Are you opening the command prompt from the same folder as you twrp.img file and your fastboot.exe file?
Click to expand...
Click to collapse
Yes they all are in the same folder. I actually had to rename it recovery.img for it to flash
dat010man said:
Yes they all are in the same folder. I actually had to rename it recovery.img for it to flash
Click to expand...
Click to collapse
Shouldn't have to rename it but sounds like you got it working. Great.
Travisdroidx2 said:
Shouldn't have to rename it but sounds like you got it working. Great.
Click to expand...
Click to collapse
Well the thing is if I don't rename it to "Recovery.img" it will not flash but when I get home I will try using flashify. If that doesn't work, I'd be willing to send anyone $20 through PayPal if they can install twrp with supersu on my phone from teamviewer or another Remote Desktop application
dat010man said:
Well the thing is if I don't rename it to "Recovery.img" it will not flash but when I get home I will try using flashify. If that doesn't work, I'd be willing to send anyone $20 through PayPal if they can install twrp with supersu on my phone from teamviewer or another Remote Desktop application
Click to expand...
Click to collapse
I thought you said when you renamed it that it worked? So still no?
Travisdroidx2 said:
I thought you said when you renamed it that it worked? So still no?
Click to expand...
Click to collapse
I have no problem Downloading the recovery to the phone, the only issue is trying to load it after I flash it
dat010man said:
I have no problem Downloading the recovery to the phone, the only issue is trying to load it after I flash it
Click to expand...
Click to collapse
Put the twrp.img file in your SDK folder with your fastboot.exe files. Not on your device.
Is USB debugging turned on?
If so in download mode when you type fastboot devices do you see your device?
If so you just shift right click and open command prompt from that folder you have the files in on your PC.
Then fastboot flash recovery "name of file". IMG
After that volume down to recovery and then volume up to enter twrp.
Just to be clear, you are using the command:
fastboot flash recovery twrp-2.8.4.0-ghost.img (assuming twrp-2.8.4.0.img is the recovery file) and you have copied 'SuperSU-v2.46.zip' into the root of internal memory (called sdcard). After flashing the recovery, you should definitely not boot directly to the system. You should issue the command fastboot reboot-bootloader. Then, choose recovery from the menu and up arrow to start it. I can't remember the exact order of things, but somewhere along the way twrp will prompt you about the supersu and near the end it will ask about making changes so the stock recovery isn't applied back over twrp. Let it make the changes. When you do boot into the system you should have root.
Hi, is there a way to root through stock recovery? I'm unable to either flash recovery or boot it through
Code:
fastboot boot recovery.img
, i've tried through stock recovery but it says zip isnt signed, is there a way to sign it?
Terramoto said:
Hi, is there a way to root through stock recovery? I'm unable to either flash recovery or boot it through
Code:
fastboot boot recovery.img
, i've tried through stock recovery but it says zip isnt signed, is there a way to sign it?
Click to expand...
Click to collapse
I'm pretty sure it's not possible with stock recovery.
I also think your command might be what's messing you up...
To boot recovery wouldn't be
Code:
fastboot boot recovery recovery.img
I've never tried this so not 100% sure.
To install recovery the command would be...
Code:
fastboot flash recovery recovery.img
I dont think so, because its able to boot it just doesnt get into the recovery, its the same problem when i flash it, it boots but it doesnt load recovery. Damn it, all this bloatware here hunting my privacy and i can't remove it and one of the apps is auto turning wifi on... HTC never more.
I tried to create a custom boot logo using logo builder 1.6
I followed all the steps as mentioned in the thread for creating a logo.
After renaming logo.bin to logo.img , the next step was given to flash this image using twrp.
So, after flashing I got stuck on boot logo (the loop is the starting venom logo as for the venom kernel )and I cannot access twrp recovery nor can I flash anything using SP flash tool via laptop.
Please help ASAP
Wtf!! No one is replying
Should I ping devs then?
use fastboot
Nicconike said:
Wtf!! No one is replying
Should I ping devs then?
Click to expand...
Click to collapse
use fastboot mode to flash twrp then try to boot in it
download twrp and put it in a folder and open command prompt in it use this command fastboot flash recovery twrp.img
akshay_rajput said:
use fastboot mode to flash twrp then try to boot in it
download twrp and put it in a folder and open command prompt in it use this command fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Thanks for your reply
None of the methods are working because phone was always looping in for bootlogo
But no issues just now I found a way , finally I can retrieve all internal data and clean wipe the ROM yayy!!
Now, i won't be using logo builder ever