Database Develop

Rogers Dream: Bad radio flashed, bricked?

Bought a new in box white Rogers HTC Dream, from someone who had an extra. Having owned a Dash, TyTN and Diamond before, I knew I wanted to flash a custom ROM, but was not familiar with Android.
I searched Google and came across this: http://www.maximumpc.com/article/howtos/howto_hack_your_android_g1_phone?page=0,0
This turned out to be a really bad guide for me. I found out Rogers phones require special attention AFTER I bricked my phone, and now I'm stuck on the Rogers logo with no access to Fastboot or Recovery Mode. In the linked guide, I flashed the recovery image and booted into Recovery Mode. I then selected the update.zip radio file I downloaded and flashed it, finishing the process with Home+Back to reboot my device, winding up where I am now. Is there any hope for me, since it's just a radio and not an SPL? If not, do you think rogers might do something? I still have the retail box and everything, it just wasn't purchased on my account.
Thanks in advance for any help!

eeesh...Flashing the wrong radio is NEVER good...There might...might be a chance to fix. I'd search the forums for the word "Brick" and see what you can find there is a lot of threads on the subject. I recall reading something about a warranty of sorts offered by HTC, you could look into that as well.

you can TRY this, but im not sure if it will work (like 1% chance maybe, but this guy also had rogers)
http://forum.xda-developers.com/showthread.php?t=568938
if that doesnt work, then idk how to help you.... rogers have a different radio than the regular g1..i think if you flashed 26I, you maybe ok.. but then again idk
please post your results here back
PS: thats the same article that pissed cyanogen off lol

Thanks for the link, I'd actually already found and tried that myself. I guess you can put that thread to rest now, as I am in the exact same situation. His described steps, including any and all variations I could think of, did nothing for my poor Dream. I'd have to say the OP in that thread did indeed have only a semi-brick with some other extenuating circumstances.
Anyways, I got in contact with the one who sold me the phone and we successfully switched the ownership and IMEI over to my Rogers account, so now the phone is registered to me and I have full warranty. As the phone is older than 30 days old a factory refurbished Dream is in the mail and should arrive sometime next week with a return package for the recently deceased.
This time I'm going to make sure to root/flash the phone properly, with this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573 (or the linked guide depending on SPL version...)
Once that's done, do I need a specific ROM too? I've read about 3G problems on the Rogers network with some ROM's...
Thanks for your help!

[Q] Stuck at the X, move on to a new phone?

I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!

Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??

Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.

matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.

SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.

Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.

Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick

Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App

Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G

Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.

You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.

Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed

DEAD or DEATH BOOT/battery totally drained

So my phone's not yet fixed since the 25th of December due to sudden death - http://forum.xda-developers.com/showthread.php?t=2585068
We had it checked again last Thursday, January 3rd. The technician said that the replacement of motherboard is not yet clear to be the best solution as the technicians from the Sony Service Center hadn't opened the phone yet. He said that it might have been a cause of a dead or death boot. Has anyone heard of it? He says not only Sony phones are experiencing this dead or death booth, even other brands. Kind of random.He said that the phone somewhat hangs, the screen isn't on but the system is still running which causes the phone to become warm or hot. And he also said that this lead to the battery getting totally drained. As per him, once the battery is totally drained it won't get charged even if I try to charge the phone for a number of hours. So what he will do when I get back to him on Monday is he will first try to shock the battery to see if it will be revived (which I hope this is just the case) and then dload some firmwares or softwares to fix the unit.
I hope this ordeal will be solved this following week as it's been so inconvenient on my part and I terribly miss my phone.

One of possibility is that they will open the back cover, pull out the battery and charge it to full, then they put it back and flash the stock firmware. With battery charged they have enough time for flashing and the phone should turn on. If it's Sony Center to do that they will also seal the phone as original to get fully working waterproof.

eclyptos said:
One of possibility is that they will open the back cover, pull out the battery and charge it to full, then they put it back and flash the stock firmware. With battery charged they have enough time for flashing and the phone should turn on. If it's Sony Center to do that they will also seal the phone as original to get fully working waterproof.
Click to expand...
Click to collapse
I really, really, really hope it'd work. For the waterproofing it would be fine to take it to the Sony service centre just to have the full waterproofness back.:good:

Just flash kernal from,any firmware by flash tool,and put your cell phone on charge.,it will charge... The same thing happen to me
Sent from my C6903 using xda app-developers app

shahzaib.khan said:
Just flash kernal from,any firmware by flash tool,and put your cell phone on charge.,it will charge... The same thing happen to me
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Flashmode not working and fastboot too the deviice is HARD BRICKED !!!

Meni30 said:
Flashmode not working and fastboot too the deviice is HARD BRICKED !!!
Click to expand...
Click to collapse
Have you managed to find a way to fix it?
I think my phone is hard bricked becuase its stuck on the Sony logo and my pc wan't detect it and none of the buttons work

SpawnCube said:
Have you managed to find a way to fix it?
I think my phone is hard bricked becuase its stuck on the Sony logo and my pc wan't detect it and none of the buttons work
Click to expand...
Click to collapse
Hey guys, do the devs a favour: NOT EVERY SIMPLE BOOTLOOP IS A BRICKED DEVICE!!!
Just go to recovery and wipe everything, it then should boot without problems.
if it doesn't, first check yourself (e.g. did you flash a 4.4 kitkat without flashing a new kernel for it?)
the answers for nearly all problems are here on xda-developers ... just read, read and read and understand ... if you don't know, what you do with flashing your device, what the partitions data / cache / system are for, what a kernel is or what the differences between stock roms, custom rom releases and nightly builds is, you simply SHOULD NOT flash your device.
If you understand what you are doing and if THAT ALL doesn't help you and you think you have a problem noone else have (i allready had such a thing with my defy+, it got bootloop and it was a dead memory chip) THEN (and just then) post your problem here. The devs simply don't have the time to help everyone who simply can't read the existing threads.
Thanks (and dont get angry on me, just saying so you can do it better the next time)

DJ_Synergy said:
Hey guys, do the devs a favour: NOT EVERY SIMPLE BOOTLOOP IS A BRICKED DEVICE!!!
Just go to recovery and wipe everything, it then should boot without problems.
if it doesn't, first check yourself (e.g. did you flash a 4.4 kitkat without flashing a new kernel for it?)
the answers for nearly all problems are here on xda-developers ... just read, read and read and understand ... if you don't know, what you do with flashing your device, what the partitions data / cache / system are for, what a kernel is or what the differences between stock roms, custom rom releases and nightly builds is, you simply SHOULD NOT flash your device.
If you understand what you are doing and if THAT ALL doesn't help you and you think you have a problem noone else have (i allready had such a thing with my defy+, it got bootloop and it was a dead memory chip) THEN (and just then) post your problem here. The devs simply don't have the time to help everyone who simply can't read the existing threads.
Thanks (and dont get angry on me, just saying so you can do it better the next time)
Click to expand...
Click to collapse
Thanks, you just said what I wanted to say.

Constant Rebooting

First off, I apoligize if this has been mentioned before. I did do a search and looked at a few pages to find that this hasn't really been brought up much. Or at least not often or recently.
I have a M8 now, but I gave my old M7 to my dad whos been attempting to use it (and enjoyed it while it worked fine.) But now the phone will reboot itself almost every 10 minutes no matter what I do.
I have
- Unlocked the Bootloader
- Relocked Bootloader and ran an RUU
- Unlocked Bootloader and Installed Custom Rom (AHRD)
all of which have not fixed the constant reboot problem. I was wondering, could the issue involve the firmware of the phone? Or is it a hardware defect.
When I gave my dad the phone he had to take it to best buy to replace, assuming they gave him a refurb I am curious whether or not that could be an issue of a loose part as well.
I have not tried to install a nonsense ROM.

.Ryker said:
First off, I apoligize if this has been mentioned before. I did do a search and looked at a few pages to find that this hasn't really been brought up much. Or at least not often or recently.
I have a M8 now, but I gave my old M7 to my dad whos been attempting to use it (and enjoyed it while it worked fine.) But now the phone will reboot itself almost every 10 minutes no matter what I do.
I have
- Unlocked the Bootloader
- Relocked Bootloader and ran an RUU
- Unlocked Bootloader and Installed Custom Rom (AHRD)
all of which have not fixed the constant reboot problem. I was wondering, could the issue involve the firmware of the phone? Or is it a hardware defect.
When I gave my dad the phone he had to take it to best buy to replace, assuming they gave him a refurb I am curious whether or not that could be an issue of a loose part as well.
I have not tried to install a nonsense ROM.
Click to expand...
Click to collapse
it's a hardware problem return it to Best Buy again

clsA said:
it's a hardware problem return it to Best Buy again
Click to expand...
Click to collapse
Thank you, will do.

What is the biggest mistake you have made fooling around with your android?

I have managed to delete the whole OS without backup and custom recovery. I also deleted the single launcher I had on my previous device. Tell me your biggest blooper you spent hours fixing.

When I was 11 yo, I saw "fastboot mode started" after a badly flashed ROM, I've decided to reflash the whole phone, which ended up in a fully bricked NAND Flash, being the partition table corrupted.
R.I.P LG-P500/h, you were a good friend.

I messed up real bad with my first Moto G. This was the time when Kikat 4.4.4 OTA came out and I should have checked the forums before updating anything(from 4.4.3 to 4.4.4) and needless to say, I had hard bricked my phone due to OTAs reacting violently with unlocked bootloaders. What's worst that my bootloader was unlocked I knew there was no way I was getting a replacement device but somehow I had fooled the warranty centre, because they couldn't boot to fastboot mode to check warranty status and in fact second they couldn't boot it at all so I got a freaking replacement device.
Sent from my XT1033 running good ol' Stock ROM

I think the worst I've done is forget to move a zip to my card before a reflash on a phone, meaning that I did a full wipe and RSD to a specific firmware then didn't have the ROM version that I needed for it. Led to yet another RSD session back to stock, getting the zip to the SD, then RSD again, then flashing the ROM.
Not too bad really, just time consuming.

My biggest mistake was buying a Samsung phone.

Trafalgar Square said:
My biggest mistake was buying an Samsung phone.
Click to expand...
Click to collapse
Yeah,i agree to that...

Trafalgar Square said:
My biggest mistake was buying a Samsung phone.
Click to expand...
Click to collapse
Don't worry. We all reach that point where we just give up on Samsung phones, because let's face it, Samsung is only worth it when you buy NOT low budget phones.
Sent from my XT1033 running good ol' Stock ROM

I told a guy I could update his rooted Kindle Fire HD. Ended up formatting the whole thing wiping the current rom, the backup and the zip I was about to flash. Tried for days and even rang in sick to work to get it working. In the end I ended up buying him a new iPad mini. Next day I sideloaded a rom on the damn thing!
Truth be told, I've still got it and it's a damn awesome little tablet.
Sent from my HTC 10 using XDA Labs

rooted my first phone the first week i got it and bricked it, panicked the whole weekend trying to fix it and thankfully fixed it by the following week

My brother Put on a tempered glass On his gionee and dropped it In the road to test it .the fall only damaged the glass and but a bike ran over it

dropped it

without unlocking bootloader properly installed random buggy ROM on Moto E and then bricked my phone.!
recovered after 1 day of internet seraching.!

Bought a cheap ass Screen Guard from a local dealer. Wanted to test it out. Dropped it from about 5 feet in air.
Goodbye Phone. Yeah it sounds noobish. But I was 12 when I did it

using it as a "personal stimulation" device on a girl. you dont wanna use that phone after that. GG

I accidentally deleted my system partition.

hehe, what a story, 4 years ago, when i was 13,5 years old. It was the first time a had an android(s7562) phone, as i had only symbian(n97) (i had some experiences with symbian as i had flashed it with JAF with some better CFWs, curruntly using a CFW made by Omar_Bazaraa).
Then i started learning android with a symbian'ish background(how to install qt? where's pips,sdl?...hhhh).
I did some foolish things, the worst thing i did is that is downgraded it to GB's cm7 (WHILE CM DOESN'T EXIST TO OUR PHONE AT ALL!, I TRIED A FOOLISH WAY TO PORT IT!).
Well, this caused it to no longer boot in recovery, so i stuck in B.L until i reflashed agin.
Thx for reading,...

Trying to unscrew a screw in order to open the phone. The screw was stucked though and I accidently destroyed the display because it was right under it.
Considering it was my first and only phone, I had to spent lots of time without an phone afterwards

Haha! Install custom Rom in my clean android

Deleted

The biggest mistake with an android phone i´ve ever made was flashing something to a device from a laptop and forgot to plug in the external power suplly. Exacly in the moment i started flashing a system img the battery from the laptop was down to 10% and it shut off itself. After that the phone was never again able to get a fastboot connection. Luckily twrp was already flashed on the device and so i could use it for more then one year xD