Database Users

I think she bricked?

I was attempting to flash 2.x using behnaam and lox's rom.
Rom: http://forum.xda-developers.com/showthread.php?t=592596
Here is the HBoot info previous to my tinkering:
HERC XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
SEP 1 2009,19:18:45
Phone is rooted using adb.
I used unlockr's guide to flash a custom recovery image onto my CDMA hero and that worked fine, here is the guide I followed:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I first moved the radio recommended for the rom by the dev to root on the sd and renamed it update.zip. After, I used the recovery image to wipe, then apply update.zip from sdcard. It seemed to flash fine, as it said please select reboot to complete, which I did, and it completed and rebooted the phone.
Once rebooted it gave me the android installing software image without anything else for a while, then turned off. I cannot seem to awaken my phone with any combo of keys or by plugging it into its use cable. The charging led doesn't even light up anymore.
Well I seem at the moment to be SOL, unless someone can come by and throw me a bone. I really am at a loss as to what I did wrong, as I have always read to do radio first. Not to mention as I watched it install radio it said it was installing radio.
Thanks for the help everyone.

You attempted to flash a GSM ROM to your CDMA phone, this is why your phone is bricked. I'm not sure if its possible to recover, people with more experience than I have can help you there. The problem was flashing a GSM ROM to CDMA. You are not the first to have done it, we all mess up from time to time.

Uuuh Umm...that software was for the GSM hero's NOT THE CDMA Hero.............bless your heart.

Ah **** I thought it was CDMA, guess it was a bad idea jumping into roms while still a noob.
Yea I only got the radio installed, not the rom, although that probably doesn't make a difference.

I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.

Hmm well if worst comes to worst I'm going with what I read on another thread and saying that I was installing the update that it found when I went to phone details and halfway through the update the phone just turned off and won't turn on anymore.
According to the other thread once it is bricked beyond belief and you play stupid they can't prove you wrong.
Best case scenario they replace it, and I won't feel bad seeing as it was a defective phone that is allowing dust to enter under the screen. But that who ordeal is an entirely different rant...lol
Sigh

ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
Go......Now......Move with haste...

gu1dry said:
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Click to expand...
Click to collapse
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.

flipzmode said:
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
Click to expand...
Click to collapse
All is lost!!!!

Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.

unfortunately, flashing the GSM radio on pretty much destroys the phone.
i think its got something to do with the voltage and electricity used by the GSM radios. probably higher than what the CDMA radios use, so you didn't really brick your phone, you 'fried' it in a sense.
sorry bout that... but if you have the equipment protection plan you can probably get it replaced real easily, since the sprint people probably won't really understand what's wrong.

again I am reminded why I dont screw with radios

willowmp said:
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
Click to expand...
Click to collapse
Once you do get it replaced and you want to put a custom ROM on it, look at the first page of this forum and you'll find sticky threads regarding four different ROMs you can put on your phone (two production release and two experimental betas).
I would suggest either MoDaCo's rom or Fresh rom. I use Fresh in mine and had no problems (although I have used MoDaCo's before and also had no issues).
Also, if you want to root the phone, there are also sticky threads that will tell you how to root your phone from Windows, Mac and Ubuntu.
Good luck.

Yep thanks everyone.
Yea I figured once no buttons would do anything and the leds wouldn't even light up for charging that it was pretty much fried. Definitely got that sinking feeling in the pit of my stomach.
I definitely should have come into this section specific to my phone and read this info instead of just doing tons of searches and getting mixed up.
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Once again thought, thanks for the help. Especially to a noob that made a real noob mistake lol.
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.

willowmp said:
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Click to expand...
Click to collapse
Well once you are retry the flashing on your new phone, just msg me & I'll give you my contact info & I'll walk you thru it.

willowmp said:
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
Click to expand...
Click to collapse
while the attempted flash was boneheaded , this (what I quoted) was very smart. I've had them try to reverse the decision and noted on my account in the past. All ended well, but a hard copy of the convo between me and Corporate would have been nice to have.
props for a good idea.

if you don't want trouble with rooting and flashing new ROMs to your phone, try flipz's pre-kitchen. just to try it, i RUU'd my phone and re-rooted it through that app, and its simply amazing. you just sit back and watch, don't even have to do anything.

Ok so its pretty funny but whoever it was who says that once you flash for the first time its addictive, I do have to agree. I will be getting my phone tomorrow because they had to replace it and I will be flashing, although this time I will play it safe and triple check before I get click happy...lol
So what are the danger zones in flashing, like what can brick or kill your phone? I know playing with radios can kill it if the wrong one is flashed, and I know powering off or interrupting a flash will kill/brick, but what else.
I know people said firmware alone usually will not brick you.

willowmp said:
So what are the danger zones in flashing, like what can brick or kill your phone?
Click to expand...
Click to collapse
Well obviously it can brick your phone if you flash the Radio I kid, I kid
willowmp said:
I know playing with radios can kill it if the wrong one is flashed
Click to expand...
Click to collapse
With the CDMA Hero, you do not have to flash the Radio. So if your attempting to flash the Radio, you're doing it wrong.
willowmp said:
I know powering off or interrupting a flash will kill/brick, but what else.
Click to expand...
Click to collapse
Well if the custom recovery is installed (RA-heroc), if the phone looses power while flashing the firmware, you are usually still safe, because you (usually) still boot into the recovery without issues.
Like I already said, if you want I can walk you thru the entire process thru an IM client, Steam, or Skype.

Oh ok thanks, I'm actually headed up to PA for a little trip but definitely will hit you up on that offer when I get back.

Phone needs to be returned. How do I go back to stock?

So, all of the sudden my menu key light started flickering. So I restarted the phone, and noticed it's flickering (going on and off) during boot as well, so it's definitely a hardware issue. I just got the phone 3 days ago, so I'll be returning it. Question is, I've been trying out custom roms and should probably go back to stock before I return it. I'm new to Android (ex WM user) so I'm not really sure how to go about doing this. With Windows Mobile, you could just load the stock ROM back on, and relock. Any help would be greatly appreciated. I'm hoping to return it today. Thanks!

http://forum.xda-developers.com/showthread.php?t=794138
Did you even bother looking?

suzook said:
http://forum.xda-developers.com/showthread.php?t=794138
Did you even bother looking?
Click to expand...
Click to collapse
Thanks! And yeah man, I searched titles for "stock", didn't realize I needed to search titles for "*OFFICIAL* SPH-D700-DI18-8Gb-REL.tar.md5"... My bad...

Can't we all just get along?
Forgive My Brevity. To Be Or Not To Be...

"Its better to be quiet and to be thought a fool, than to open ones mouth and prove them right"
-Abraham Lincoln

G2 Constantly Reboots..LG Can't/Won't Fix

still under warranty i might add...
http://youtu.be/dPsu7OxR2Lk

Wow, I'd post this LG's Twitter account! Have you tried to revert back to stock?

comk4ver said:
Wow, I'd post this LG's Twitter account! Have you tried to revert back to stock?
Click to expand...
Click to collapse
it is stock. 100% factory stock, locked bootloader and all. just booted from the packaging and entered gmail info. the thing is, when i go to factory reset it maybe 90% of the time it can't complete it because of the rebooting

No use this: http://forum.xda-developers.com/showthread.php?t=2448960

comk4ver said:
No use this: http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
Actually use this. (http://forum.xda-developers.com/showthread.php?t=2663369) This is ATT specific.
But I doubt it will help.
I am in same boat but unlike you my phone starting doing RR 7 days after my warranty expired.
I was feeling bad but looking at your video I guess it would not have mattered even if mine was under warranty.
I tried reverting to stock etc but no dice. Most likely HW issue .
Let me know if you find a solution. I like this phone and it worked fine for a year.

epapsiou said:
Actually use this. (http://forum.xda-developers.com/showthread.php?t=2663369) This is ATT specific.
But I doubt it will help.
I am in same boat but unlike you my phone starting doing RR 7 days after my warranty expired.
I was feeling bad but looking at your video I guess it would not have mattered even if mine was under warranty.
I tried reverting to stock etc but no dice. Most likely HW issue .
Let me know if you find a solution. I like this phone and it worked fine for a year.
Click to expand...
Click to collapse
yep, same result. keeps rebooting. so after trying safe mode and this i've concluded it's a hardware issue. and i have no recourse from the mfr. even with it under warranty. good times

Should I go ahead and go through the bootloader/rooting processes?

I've wanted to grill out some of the problems with the A7 that's came with it, but after realizing I've never done this before, I've also noticed there's no actual ROM out yet
Should I just wait until the ROM comes and maybe some full guides?

Rigby J said:
I've wanted to grill out some of the problems with the A7 that's came with it, but after realizing I've never done this before, I've also noticed there's no actual ROM out yet
Should I just wait until the ROM comes and maybe some full guides?
Click to expand...
Click to collapse
Welcome to the A7 Family,
which problems are you running into right now? if you have no need for Root. i'll just say hold on till some development start to kick.......
P.S. not every problem can be fix having root access

DrakenFX said:
Welcome to the A7 Family,
which problems are you running into right now? if you have no need for Root. i'll just say hold on till some development start to kick.......
P.S. not every problem can be fix having root access
Click to expand...
Click to collapse
Really just cosmetic things like the notification bell, maybe switching up the emojis, small things. I always wanted to try a different ROM on this phone, so I guess it isn't anything that needs to be done right now.

Rigby J said:
Really just cosmetic things like the notification bell, maybe switching up the emojis, small things. I always wanted to try a different ROM on this phone, so I guess it isn't anything that needs to be done right now.
Click to expand...
Click to collapse
just unlocked my bootloader and rooted. Wonderful being able to use my root apps again. Chnaged my emoji using emoji switcher which i really wanted to do. Hate the stock android emoji.. debloated a little, and now about to change the system to my favorite font. I say go for it. If you do, let me know. I can send some pointers

considering there is absolutely no rom support yet I would hold off, wait out your 30 day return period and if there are roms after that and you want to void your warranty then do it then. Also I'm sure people are working on getting the bootloader unlocked without contacting ZTE so there is another reason to wait.

pwnerman said:
...Also I'm sure people are working on getting the bootloader unlocked without contacting ZTE so there is another reason to wait.
Click to expand...
Click to collapse
Already done: http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778

osmosizzz said:
just unlocked my bootloader and rooted. Wonderful being able to use my root apps again. Chnaged my emoji using emoji switcher which i really wanted to do. Hate the stock android emoji.. debloated a little, and now about to change the system to my favorite font. I say go for it. If you do, let me know. I can send some pointers
Click to expand...
Click to collapse
Thank you, I'll message you when I do.
pwnerman said:
considering there is absolutely no rom support yet I would hold off, wait out your 30 day return period and if there are roms after that and you want to void your warranty then do it then. Also I'm sure people are working on getting the bootloader unlocked without contacting ZTE so there is another reason to wait.
Click to expand...
Click to collapse
I see, I see

Rigby J said:
Thank you, I'll message you when I do.
I see, I see
Click to expand...
Click to collapse
If you want to wait until the 30 day period is over, you can go ahead. im keeping the phone for a while so ive just gone ahead and rooted. there is a method to unlock the bootloader without contacting ZTE. I did it that way. its fairly easy.

Rigby J said:
I've wanted to grill out some of the problems with the A7 that's came with it, but after realizing I've never done this before, I've also noticed there's no actual ROM out yet
Should I just wait until the ROM comes and maybe some full guides?
Click to expand...
Click to collapse
There is a fairly simple way to Unlock your boot loader right now, it seems to work for most people. Its possible they may figure out a way to block this in future updates (I am not an expert). If you are with in your retail return window I would recommend trying the method because if you manage to really mess something up, you can at least return it.
Just take your time.
The instructions are for multiple versions and slightly out of order. Make sure everything is working before you begin.
If you plan to go through ZTE and in theory void your warranty, then by all means wait until you really need it.
Good luck.

osmosizzz said:
If you want to wait until the 30 day period is over, you can go ahead. im keeping the phone for a while so ive just gone ahead and rooted. there is a method to unlock the bootloader without contacting ZTE. I did it that way. its fairly easy.
Click to expand...
Click to collapse
How is this done?

Rigby J said:
How is this done?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778

xtermmin said:
http://forum.xda-developers.com/axon-7/how-to/bootloader-unlock-t3437778
Click to expand...
Click to collapse
thanks

I just got my A7. Coming from OPO with a sultan rom running xposed. I want to root but honestly I am not super smart developer. I am good following direction and figuring things out. I honestly love Sulan rom and would love it on A& but I doubt he does a rom for it as he mostly is busy with school and sticks with OPO or OP3.
I am debating on rooting as I mostly just want xposed for its youtube app adblocker and in app blocking apps.
I would suggest waiting til roms are developed and little more mature. Which if judging by the speed of root being available I would say could be as soon as few months or less.
Big respect for the developers and who keep the community and advancements going. Thanks all!

Does anyone know a way to disable the notification bell with root? Thanks

mmamedov said:
Does anyone know a way to disable the notification bell with root? Thanks
Click to expand...
Click to collapse
I don't think you can disable the bell and keep the lockscreen exactly as it is.
http://forum.xda-developers.com/axon-7/themes/skipping-notification-bell-root-t3441787

Did I just Hard Brick my phone?

I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:

Are you S-Off? Does your computer see it?
@dottat

acbrocksit said:
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Click to expand...
Click to collapse
Try charging with oem stock charger and cable overnight.
If it starts to take a charge, prepare a blank SDcard with
2PS6IMG_PERFUME_WL_M60_SENSE80GP_VZW_VERIZON_WWE_1.85.605.8_Radio_1.0.C010141xxxx.zip or similar. Rename it 2PS6IMG.zip with only one .zip at end. Try and boot with volume down and power.
With any luck, you'll get enough charge on it to allow you to do this software install.

Hard Brick
I did ask Santod and he said it is hard bricked. I flashed the wrong aboot image and now the phone does nothing, no power, no response from any combination of button presses, the computer does not see it. I don't know of anything else that might work.
I'm going to try to see if HTC can fix it, if not then I may use it for parts because the phone looks great. So I may try to get a beat up phone with a busted screen and swap out the guts.

Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk

Bricked / aboot
dottat said:
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I read your info and warning about it after the fact.

acbrocksit said:
Yeah, I read your info and warning about it after the fact.
Click to expand...
Click to collapse
Yep...Moreso posting for anyone who sees this as further warning.
Sent from my HTC6545LVW using Tapatalk

I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.

Spinkness said:
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Click to expand...
Click to collapse
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk

I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.

acbrocksit said:
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
Click to expand...
Click to collapse
They didn't even ask why Verizon wouldn't warranty it?
Sent from my m8wl using Tapatalk

Evocm7 said:
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.

Spinkness said:
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Click to expand...
Click to collapse
No problem. I called Verizon and even though it was dead, they were still able to communicate with the phone while I was talking to them on another phone. The power led was flashing red and then she said the phone wasn't under warranty because there was custom software. I ended up sending it to HTC where they sent me a refurb with a bad mic then the second one I have now is fine. So after a month and $40 worth of shipping charges, I have a working 10 again. I honestly don't think HTC cares about rooted phones and the time it would take to diagnose what actually happened in our down grade brick wouldn't be worth it for them.
Sent from my HTC6545LVW using Tapatalk

If it's under warranty, make a claim. Verizon will tell you to ship it back to another location where all they do is refurbish the phones for subsequent resale. You will likely get a replacement refurb. The refurbisher has absolutely no clue what you have done; they handle these things in bulk and I have not once ever heard of a phone under warranty being "refused" because an end user did something stupid. Which, as @dottat says, is what flashing an edited aboot to get rid of the red text is, by the way. Stupid.
I *like* the red-text, frankly. It reminds me whether I'm running pure stock boot and recovery or not while I'm flashing updates, etc.