Database Develop

Not completly bricked

Hi guys im wondering if any of you can help me out here.
I have been on cyanogen (latest) for a while but decided to have a go at puting the ''donut'' rom in the android development bit of this forum (eu version as im in uk) on my phone this evening.
I flashed the base version fine and it started up great. Then I flashed the extention (add on) part and it started up but after the ''android'' screen it just went black and nothing happend. So i did a hard reset and tried again, same problem occured.
I then tried to put the latest cyanogen rom back on my phone, put to root, started it up then BAM stuck on g1 screen. Didnt get passed it. So put other roms later cyan roms on and still same problem occurs.
I then freeked out and tried to go back to RC29, so i deleted everything of my sdcard and put the dreming file on, pressed power and camera button and then BAM it comes up with some sort of cyanogen screen and not the rainbow screen. So havent got a clue how to install the dreming file. So gave up there
So this is where im at. Nothing on my sd card. Still got cyan on my phone but cant get it started up, no matter what rom I try it keeps getting stuck on g1 screen.
I know this is completly retarded but I really need help to get this sorted.
ANY HELP WOULD BE GREAT
Thanks

Have you been wipping?

Wiped before flashing donut rom...And when trying to put cyanogen rom back on...

If you can boot into recovery or into fastboot then you should be fine.
Wipe, if you use appps2sd the wipe your ext partition as well.
Flash base defanged rom from Cyan's site and flash Cyan's latest (Check md5 sums of both to make sure that your downloads are not corrupted. Fix permissions and you should be ok. If you still can't boot up (and it will take a while to boot up after a wipe) then you can go back to RC29. Just make sure that your nbh file is named exactly Dreaimg.nbh and your card is formated to FAT32, otherwise fastboot will not find it.
Good luck.

borodin1 said:
If you can boot into recovery or into fastboot then you should be fine.
Wipe, if you use appps2sd the wipe your ext partition as well.
Flash base defanged rom from Cyan's site and flash Cyan's latest (Check md5 sums of both to make sure that your downloads are not corrupted. Fix permissions and you should be ok. If you still can't boot up (and it will take a while to boot up after a wipe) then you can go back to RC29. Just make sure that your nbh file is named exactly Dreaimg.nbh and your card is formated to FAT32, otherwise fastboot will not find it.
Good luck.
Click to expand...
Click to collapse
Wow lots of help there thanks.
Firstly tho I cant find this ''base defanged rom'' from cyans website? Can you give me a pointer as to where it is? Is that its name on the website or is that it in short?

Forget that I found ''DRC83_base_defanged.zip''. Downloading it now.

flashing froyo problem

ok so i reverted back to to old erd27 using rom manager.then download froyo and put it on my sd card and flashed using rom manager. but i got stuck in a bootloop. any reasons why? i was thinking maybe i should wiipe first or maybe i flashed the wrong froyo zip because there were so many yesterday. any info was be appreciated

b33zy682 said:
ok so i reverted back to to old erd27 using rom manager.then download froyo and put it on my sd card and flashed using rom manager. but i got stuck in a bootloop. any reasons why? i was thinking maybe i should wiipe first or maybe i flashed the wrong froyo zip because there were so many yesterday. any info was be appreciated
Click to expand...
Click to collapse
Rooted phones seem to need to be wiped before the update installs from what I'm reading here

z0phi3l said:
Rooted phones seem to need to be wiped before the update installs from what I'm reading here
Click to expand...
Click to collapse
ok well im trying again. same procedure. used rom manager to go back to the old erd27. then put froyo on the sd card wiped and flashed. and im working. thanks

I did it too, went to ERD79, let it update to ERE27, wiped userdata and cache, updated to 2.2 from sd, still gets stuck in boot loop.

acordill said:
I did it too, went to ERD79, let it update to ERE27, wiped userdata and cache, updated to 2.2 from sd, still gets stuck in boot loop.
Click to expand...
Click to collapse
try this exactly: http://forum.xda-developers.com/showthread.php?t=688000

mrandroid,
OK, I went ahead and tried that. I still have problems. When I go to flash CM it fails the verification. I have tried CM versions in the past with the same result. I have even went as far as to verify the files by MD5s. I have tried what I have seen in other posts and downloaded the files through different browsers... to the same results. I often wonder if it has something to do with my phone. Even when I do nand backups the resulting images seem to fail verification, specifically system.img and userdata.img. The only zip update packages that I have been able to verify are small ones. I hope all this information leads way to a solution to my problem.

[Q] Start from Scratch....

I have flashed my Hero with many ROMS, mostly the Cyanogen nightly's. I have seen recently a huge lag no matter which build I use. I think there may be a corrupt file left behind that is causing the problems.
How can I erase everything and start completely from scratch? I have already done a wipse and re-imaged from there and it doesn't seem to help.

Run the officail RUU, then re-root again. that is all you need to do.
Sent from my HERO200 using XDA App

fowen said:
I have already done a wipse and re-imaged from there and it doesn't seem to help.
Click to expand...
Click to collapse
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.

ranger61878 said:
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
Click to expand...
Click to collapse
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.

fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
If you are using the Amon Recovery v1.5.2, it does actually wipe everything even thought it gives you that 'run via adb' nonsense. It's just a small error/bug in that version of recovery that doesn't output the correct string of text, but the wiping part does work correctly and it does actually wipe Dalvik, data, ext, etc. even though the output tells you something else.
As said above, you need to wipe ALL of those (except battery) every time you flash a new ROM, or else it can lead to some corruption like you are experiencing. If still unsatisfied or if you still can't get things to work, then rerun the official RUU as also suggested above to start fresh. But I will tell you that I've never had to rerun the RUU before in the entire 6 months I've been rooted, so I think your problem is maybe just incorrect procedure between wiping and flashing ROMs. All phones are different though. Good luck, and please keep posting so we can continue to help you out.

fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
What recovery are you using? Anyways, the RUU wipes everything, no need to wipe beforehand, see this to RUU

I haven't flashed many types of ROM's, only a few. I have been sticking with Cyanogen Mod I would say 90% of the time. I cleared out everything and it didn't seem to help much.
Most of the time it lags when I am dealing with email, or a email comes in. Last week I got tired of it and OC'd it up to 768 and I saw a huge difference but my battery died after 6 hours. Even with the CPU clocked to 768 I can notice a huge difference when I have a email coming in.
I just flashed to Cyanogen's newest nightly to see if there are any differences. If not, I will try to un-root and flash directly to Cyanogen's rom. Will I need to clear everything before going to a new rom from stock?

I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?

fowen said:
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
Click to expand...
Click to collapse
Assuming you mean going back to pre-root, right out of the box state...you need to run the official RUU from your computer, not via recovery.

Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.

fowen said:
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
Click to expand...
Click to collapse
You are using HTC Sync and have the USB drivers installed?
----------
Sent from the XDA App on my FroYoed Sprint Hero...so forgive my inevitable typos

Sounds like a driver issue. Also make sure you have USB debugging on, otherwise adb will not recognize your device.
I've run across issues with loose fragments of data being left after a wipe via recovery. My favorite was the home key ceasing to work. A full wipe via fastboot always seems to do the trick. Just make sure you have a copy of your recovery image to reflash when done. You'll need the ENG SPL as well.
You'll do this all via adb.
In bootloader:
fastboot erase system -w
fastboot erase boot
fastboot boot your_recovery_image.img
adb shell mount /sdcard
adb push your_recovery_image.img /sdcard/your_recovery_image.img
adb shell flash_image recovery /sdcard/your_recovery_image.img
adb shell reboot
Just make sure your recovery image is on the root of your sdcard. Full wipe in minutes without that long ruu process! I've been doing this every time I flash a new ROM lately, never an issue.

Custom Roms will not boot! Please Help.

Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic

JohnPublic said:
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
Click to expand...
Click to collapse
try amon ra recovery, full wipe including dalvik and flash one of the roms you listed above, like cm6.1 stable (from cyanogenmod.com) with the gapps (from jaybob413's rom thread in hero development). once it starts the boot, give it time, it may take a long time (10 min.) Hope it works.

I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.

Now don't I feel silly! I re-downloaded CM6.1 and put it on the card and it seems to be firing up. I'm on the CM logo bootscreen right now. I have no idea how three separate zips all got corrupted en route to my card, but I suppose that must be what happened. Thanks for the help!

JohnPublic said:
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Click to expand...
Click to collapse
have you tried re-downloading the roms? it sounds like something is missing in them, which shouldn't be. if you are downloading from your phone, try a download from a computer and see what happens. where are you dl'ing the roms from? verification failure makes no sense..... also, did you recently update rom manager from market to 3.0.0.7? there was something listed in the changelog about verification failure fixed when using other recovery, i think....
EDIT: saw your last post, maybe your browser was acting up? delete the bad ones, get new ones, flash away

[Q] Nothing present after custom ROM install

I have spent a day and a half trying to fix all of my issues before I finally turned here but I am at my wits end.
This all started with my attempt to flash Viper to my HTC one. I installed clockwork touch loaded Viper to the drive and went to install. During the install process something happened and my install failed. When I rebooted the phone it returned to the fasboot screen and there was no recovery present. I had heard that sometimes TWRP works better for installing some ROMs so I decided to switch courses and try that. Before installing I went and formatted cache, data, ect. When I tried to install Viper this time it appeared to be a successful install. However, I was once again I was returned to the fastboot screen and no recovery was present. I tried this a few more times with either clockwork or TWRP using sideload with no luck. I also trried using fastboot to flash a sprint stock recovery boot and image. When the phone rebooted it showed the white HTC Screen but nothing happened for a half hour so I restarted the phone again only to be dropped into the fastboot. I also tried locking and unlocking the boot loader and tried a Sprint HTC one RUU with no success.
So at this moment this is where I stand:
I am on the fastboot screen with no recovery.
HBOOT 1.56.0000
S-ON
Any help you can provide would be GREATLY appreciated. Thanks for your time.

Betraythesway said:
I have spent a day and a half trying to fix all of my issues before I finally turned here but I am at my wits end.
This all started with my attempt to flash Viper to my HTC one. I installed clockwork touch loaded Viper to the drive and went to install. During the install process something happened and my install failed. When I rebooted the phone it returned to the fasboot screen and there was no recovery present. I had heard that sometimes TWRP works better for installing some ROMs so I decided to switch courses and try that. Before installing I went and formatted cache, data, ect. When I tried to install Viper this time it appeared to be a successful install. However, I was once again I was returned to the fastboot screen and no recovery was present. I tried this a few more times with either clockwork or TWRP using sideload with no luck. I also trried using fastboot to flash a sprint stock recovery boot and image. When the phone rebooted it showed the white HTC Screen but nothing happened for a half hour so I restarted the phone again only to be dropped into the fastboot. I also tried locking and unlocking the boot loader and tried a Sprint HTC one RUU with no success.
So at this moment this is where I stand:
I am on the fastboot screen with no recovery.
HBOOT 1.56.0000
S-ON
Any help you can provide would be GREATLY appreciated. Thanks for your time.
Click to expand...
Click to collapse
You probably should RUU and stay over.
Sent from my Slim Photon using xda app-developers app

So I have my phone up an running on a stock RUU but I seem to have the same issues with and error when installing Viper. Any ideas as to what the issue could be?

Betraythesway said:
So I have my phone up an running on a stock RUU but I seem to have the same issues with and error when installing Viper. Any ideas as to what the issue could be?
Click to expand...
Click to collapse
... now that its up and running, i recommend you get s-off 1st. it eases many things. then flash twrp 2.7.0.4 recovery and try to flash viper :victory: ...

I was in this situation myself. If you can adb twrp recovery onto your phone. Dont try to flash viper with cwm it will mess stuff up. After you have a recovery loaded flash the viper rom. If it boots up be sure to check about phone section in the settings and see if there is a baseband version present. If not just flash the latest firmware and you should be good to go. This was what i had to do.

Same here, about a month ago. They really need to just remove that option to flash CWM. I managed to get a recovery installed, but now it seems like half the ROMs I try to flash won't boot. I don't even know what Rom I am using, because it has disappeared from XDA. It's a 4.4.2 Sense 5.5 ROM, and it is odexed and came with Xposed Installer. It's the only ROM that seems to work anymore, so I have to wonder if my firmware got messed up. I'm S-On, with no way to S-off for the foreseeable future until I can fix my laptop. Since my laptop is unavailable, I'm a bit hesitant to mess with the phone much more, since I can't fix it again without the computer.
Sent from my HTCONE using Tapatalk

I've read a number of these threads, and many have Viper in common. Viper by itself is an amazing ROM. Maybe too amazing... Incredible amount of customization. I have to remind myself occasionally that as much as I flash ROMs and lurk around here that I am not a dev.
I would do my best to achieve S-OFF if you have any plans for custom ROMs. It's always useful. I would also suggest trying one of the Sense 6 ROMs. They are all amazing.
Sent from my One using Tapatalk

S-OFF is necessary for some ROMs to work, although I'm not sure about Viper. Use firewater.

greywolf928 said:
S-OFF is necessary for some ROMs to work, although I'm not sure about Viper. Use firewater.
Click to expand...
Click to collapse
I am very sorry I know this is a slow response. So I tried to first root my phone so I could use firewater but I ran into issues. First, I tried to place supersu on the internal hard drive via windows but when I rebooted into recovery I was not able to find any of the folders I had access to. So i tried using side load but got errors that I could not mount cache and could not mount system. Do you have any suggestions on how to proceed?