Database Develop

I may have bricked my HERO2000 trying to flash a custom ROM.

I'm new to this whole flashing custom ROMS business. I have a CDMA HTC Hero 2000 and I downgraded to the original 2.1 before the update just fine, rooted my phone just fine. Then I tried to flash Aloysius to it using instructions I found here: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore | Android News, Reviews, Applications, Games, Phones, Devices, Tips, Mods, Videos, Podcasts - Android Police
After all was said and done, my phone starts to boot with the "HTC quitely brilliant" logo, following by "SPRINT the Now network" logo and after it shows "Now" for many seconds (as it normally does before pulling up the home screen), it reverts back to the HTC logo and repeats this process until I remove the battery.
I removed the microSD and attempted to boot, same thing. Then I held down HOME+BACK+POWER to do a manual hard reset, this took a little longer but again had the same result.
I may just cry now. Please help!!

Run the official sprint ruu, and see what that does for u. Then read the rooting guide here on xda and try it. I personally recommend amon ra recovery to flash roms, rom manger never seemed to work right. Feel free to pm for more help, dont worry u prob arent bricked unless u flashed a gsm rom (which aloysius isn't)
Sent from my HERO200 using XDA App

That's a bootloop not a brick You could try downloading a different rom and flashing it in recovery, nandroid restoring - if you made one, or flashing the same rom again. just wipe your phone before (data/cache/dalvik)

Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.

chrisdegraw said:
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
Click to expand...
Click to collapse
Four key words to remember when trying out any new rom
Nandroid is your friend!
additionally, you should always remember to wipe before loading a new rom!
Enjoy!

Yeah, don't ever panic, that was, as everyone said, a bootloop by textbook definition. I've never seen a brick before, but I'm damn sure it won't get as far as the Sprint logo. The only way to brick a CDMA Hero is to flash a GSM Radio/Bootloader to it.

Paragon RC5.0 issues

Just installed Paragon RC5.0 on my capitivate. Install went smooth, everything is pretty and the backups restored. Im only running into one issue. I cannot get the screen to turn to the side when holding it horizontally.
I was having this problem last night when i was having issues with my backups. I did something to where i could get it it to turn and thought all was well. I reinstalled the ROM because titanium backup over wrote a few programs that were on the ROM and was more careful about the next restore. No matter what i do i cannot get the screen to move to any other position now.
Tried reading through the 200 page super thread on the ROM, but was unsuccessful at finding any information.

Running same rom not having that issue.
Maybe try reinstalling rom then are if it works before youdo anything with titanium

try to do a master clear first.

Did the Master clear with odin following instructions: http://forum.xda-developers.com/showthread.php?t=731989
Rerooted, re installed paragon. Tilting works now, havent touched titanium backup yet. Lets see how restoring things affects it

Tilt was working. Used titanium backup to manually select a few things to restore, like contacts and a few other things. Then used batch to restore all missing programs, I made sure to go down the list and only select specific programs i wanted back. Rebooted my phone and now tilting doesnt work anymore.....

Was frustrated with Paragon so I master cleared again and installed Serendipity 5.3. Everything working fine and well, tilting worked. I click 2 apps on the phone(market and maps :/) and tilt hast worked after that. Is this a comon problem with ROMs?

So you are saying that your auto rotate after you opened maps and or the market?
No that is not normal

After installing the Rom i let it sit for 5 minutes, opened messaging and rotated it and it worked, opened a new message and went to the keyboard and it worked. I open up the camera, and then tried to put in my market info and the screen wouldnt rotate, along with everything else now. No backups or anything this time. 2nd ROM in a row to do this for no reason. I'm thinking about going back to stock lol

I do not use my auto rotate but I have not heard a problem like yours before. Sorry, I got nothing

Apparently Serendipity 5.3 and paragon has an icon on the pull down menu i mistook for the sync icon thats on the stock ROM( i think thats what it is, i always had it off and it never affected anything). An infuriating little feature when not understood.

Facepalm
So you are cursing at your phone and you had turned the feature off? Live and learn

Yea, when i finally figured it out i felt really dumb. Although, in the frustration caused by this stupid mistake I can now master clear, root, and flash my phone in my sleep haha

Problems with Paragon RC5 ROM
After i flashed the rom, my captivate went to the first boot image and got stuck. My phone has been like that for a couple of hours. is there a way i can flash back to the stock rom or fix this problem? I have tried to reboot into recovery but my phone wont get past the first boot image. PLZ HELP!!!! P.S. I forgot to master clear before flashing rom and I used rom manager to flash the rom. I was running darky's rom b4 trying to flash this one.

bindratn said:
After i flashed the rom, my captivate went to the first boot image and got stuck. My phone has been like that for a couple of hours. is there a way i can flash back to the stock rom or fix this problem? I have tried to reboot into recovery but my phone wont get past the first boot image. PLZ HELP!!!! P.S. I forgot to master clear before flashing rom and I used rom manager to flash the rom. I was running darky's rom b4 trying to flash this one.
Click to expand...
Click to collapse
Can you get into download mode?

how would I do that?

Turn phone off
Take out sim, ext sd, battery
Have usb hooked to pc but not phone
Put battery back in
Hold volume up and down while plugging in usb
Phone should go to a screen with an android with a shovel
If you can do this and have a windows pc I can get you back up and running pretty easy

ok i did that and it went into download mode

Do you have a windows pc?
Have you installed the usb drivers for this phone?
What is your build number of your phone, located under battery something like 1008?

yes i have a windows pc and the drivers and my build number is 0168 i guess

No that its not your build
You do have a captivate right?
Under battery anything from 1006-1012

Roms arn't installing

I have a HTC Hero, today I tried to update my cyanogen mod 7 to 7.0.3 however when I did, I did all the proper steps to update the Rom properly however it did not work. So I tried a fresh install, and even tried a few new Roms still nothing worked. Recoveries work fine. When I restart my phone it hangs at the HTC screen then restarts and it will do this so far for up to 15 mins. someones gotta have an idea on whats going on. btw phone is rooted and running clockwork.

goshxjosh said:
I have a HTC Hero, today I tried to update my cyanogen mod 7 to 7.0.3 however when I did, I did all the proper steps to update the Rom properly however it did not work. So I tried a fresh install, and even tried a few new Roms still nothing worked. Recoveries work fine. When I restart my phone it hangs at the HTC screen then restarts and it will do this so far for up to 15 mins. someones gotta have an idea on whats going on. btw phone is rooted and running clockwork.
Click to expand...
Click to collapse
What version of cwm? Try flashing a different recovery version (maybe 2.7.0.5)
Make sure you factory wipe as well as format, system, data, cache.

Bad download maybe?
®patience is a virtue©

is your battery charged well above 30%?
Sent from my HERO200 using XDA App

Guys i had this problem when i flashed my first ROM too ...(alas)
Buy my problem was a simple fix ,
: restart in recovery
: wipe all data
: restart and Enjoy

i have the most recent cwr and i wiped my data and everything. i have been flashing for more that a year now this is the first time ive had this issue. im gonna unroot and reroot the phone.

If you haven't unrooted yet try just reflashing your current recovery.
#Root/Hack-Mod_Always*

This has happened to me with different builds ( of all of the different gingerbread roms) since the switch from 2.3.2 to 2.3.3 and .4.
When this happens, I will either try a different Rom, or use something called Fix Flash that is in the development section for the CDMA Hero. My phone currently is liking the Jaybob build. Also, as silly as this might sound, but formatting the partitions 3x can actually help too ( boot, system, data, and cache).good luck, I've been there.
Sent from my HERO200 using XDA App

Can't get past the HTC screen...
I got a new HERO200 as a replacement for a damaged one and am able to root it with confirmed SU permissions. I have tried clockwork 2.5.0.7 and RA 1.6.2 for the heroc. I tried flashing Cyanogenmod 7 (7.0.2 / 7.0.3 / 7.1.0 / and even a 6), AOSP and it keeps hanging at the HTC screen when I reboot the device out of recovery. The first reboot after flashing a ROM will briefly display the HTC screen and then go black. I have to remove the battery to reset the phone. When I power it up again, it will display the HTC screen and just hang, even after multiple restarts via a battery removal. I have wiped all the data/cache/etc. multiple times as from a previous post in this thread, but without luck. I'm getting very frustrated to say the least and any help would be GREATLY appreciated.

never had a rom not booting, but i haven't tried them all,
try the older version again see if it works

I just run the nightlies and skipped the rc and haven't experience such things. could be something to do with the signing?
Sent from my HERO200 using XDA App

[Q] G1 Stuck on boot

First I have searched and searched and can't find anything similar to my problem.
G1
CM 5.0.8
RA 1.7
DangerSPL
I had cm5 running on my phone just fine for the last month or so and today my battery was about to die so I shut my phone off and when I went to turn it back on it sticks on the G1 boot screen. I can boot into recovery and fastboot but it will not but past the first boot screen. Is this something I did? Is there a way to fix it without starting scratch?

Did you backup your ROM? If yes, try restoring it.

I just re-flashed the ROM and it works fine. But I did a wipe and my screen saver is the same and google apps is still installed? Is that supposed to be like that after a wipe?

When you re-flashed your ROM and you did not do a full wipe of your data everything stay.

I did do a full wipe, catch, and everything and just flashed CM5 not the G-apps flash and I still have it along with the wallpaper being the same don't really know if this is relevant to the ROM but as far as I know when you wipe it puts the phone back to factory besides the recovery, radio, and SPL. Google apps can't be a part of the ROM either so I'm actually confused.

Oh and I re-partitioned my SD as well before the wipe so I pretty much started fresh but in all reality I didn't?

sometimes google backs everything up so when you re-flash to anything with same firmware as your last rom, and once you sign into google it will automatically install apps you previosly had and restore some settings such as Backgrounds and stuff... since you flashed the same exact rom, im assuming once you signed into google it just had your previous settings saved and restored it like a good friend would

HAHA made me chuckle! Thanks for the help guys! Glad to know google is my good friend! Still confused on why it just crashed like that :/ but as long as it's fixed is all that counts and not bricked

Hmmm.. When I did a full wipe of mine and flashed a new android version, I had to re-install all again!!!! and some of my data was also lost

boscharun said:
Hmmm.. When I did a full wipe of mine and flashed a new android version, I had to re-install all again!!!! and some of my data was also lost
Click to expand...
Click to collapse
Yes that would be correct.

htc dream stuck on boot screen
hi
i was tryng to update my htc dream rogers, firstly i used wrong dreaimg.nbh file my rogers changed into t-mobile g1, then itried again i was installing spl then phone stuck on sartup tmobile g1 screen, nothing works Home + power, Camera + power , power, dosen't work tell how to recovery my phone..
it just stuck on t-mobile g1 screen..
plz hepl me....

nothing is working tell me how to start it back, when sipmle powetr on or try to do any reset it just stuck on g1 start up screen.... plz plz help me ............................... it just stuck on t-mobile g1.... nothing happen...........................

Sorry for bad news, but I suppose you created a brick, i.e. there is no chance to re-animate your phone except with JTAG ...

can he still flash an nbh file? maybe try the orange nbh to re-flash via fastboot? or will it not let him do that because he has wrong/stock software installed?

Yep. No fastboot after Power+Cam. Sounded like a bad news brick indeed.

[Q] Internal memory dying?

hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3

spazzy1912 said:
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
Click to expand...
Click to collapse
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone

markj338 said:
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
Click to expand...
Click to collapse
woops, i forgot to mention that i was on 4ext touch before and it still happened :S
it used to happen before, but not as frequently, so that is why i am a bit worried
when i get my pc back ill try reverting back to 1.13 bootloader :S