Database Users

Guarantee, flash, ship rom

Hi!
Earlier I had Hard SPL, now I have USPL and Dutty's 3.0.
If I'll return to stock SPL and stock ROM (using one of these http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Ship_exe), will it be possible to tell that my phone was flashed? Can I use guarantee?
Thanks.

I think the general consensus is that you can. I'm sure if they really looked hard there maybe some trace of hard spl but I doubt they would. They'd see the phone boot up with stock spl and take that as a given.

Simply I'm going to sell the phone, and I'm thinking of, what to tell.. If the phone still have guarantee or it doesn't. The price depends on it.
Maybe anybody had a real experience?

crankshaft said:
I think the general consensus is that you can. I'm sure if they really looked hard there maybe some trace of hard spl but I doubt they would. They'd see the phone boot up with stock spl and take that as a given.
Click to expand...
Click to collapse
I also think that they won't search for some tracks of flashing really hard, but still...

I have an HTC Touch phone that keeps coming up with this same error...

I have tried a lot of things, and I finally updated the rom, and it still isn't working. It just keeps coming up with the same error, "No Radio."
Is there anything anybody can suggest to help fix my problem? Thank you very much...
I also have a thread on ppcgeeks.com:
http://forum.ppcgeeks.com/showthread.php?t=71643
Thank you so much!

Have you flashed a radio? You need to read a FAQ on flashing.

lol.
she doesnt need to read a faq.
her radio disappeared from her phone.
she didnt mod it either.
we tried reflashing the stock rom,
and she said it loaded, but it did the same thing pretty much.
im personally stumped about this one.
anyone have any ideas??

If you haven't flashed any custom roms nor unlocked it, I'd bring it to the store and see what they have to say.

Spalla said:
If you haven't flashed any custom roms nor unlocked it, I'd bring it to the store and see what they have to say.
Click to expand...
Click to collapse
If you read the other thread she linked to,
that describes what we have done to it already,
and more description of where she stands with the phone,
you'd realize her dad gave her the phone.
It's an older phone with no insurance or warranty.
Meaning that would do her no good to take it to the store.
I sent her over here because there's usually more advanced developers over here and I would have thought they'd know what to do.
I just didn't think it was at all possible to have the radio just disappear like it did to her. VERY STRANGE!
Especially with no modding...

..Bump..
..Bump..
..Bump..
..Bump..
..Bump..
Any help would be appreciated!!

codybear said:
..Bump..
..Bump..
..Bump..
..Bump..
..Bump..
Any help would be appreciated!!
Click to expand...
Click to collapse
I had a quick read through what you have tried so far... Have you unlocked the device with ImCokeMan's unlocker. Then you will be able to try non standard roms and radios, might help.
My only other though is that the radio hardware is stuffed which means you are out of luck.
I would take the phone apart and carefully and clean out any dust etc that has gathered in the device (a very long shot but you never know).
Good luck

njakobs said:
I had a quick read through what you have tried so far... Have you unlocked the device with ImCokeMan's unlocker. Then you will be able to try non standard roms and radios, might help.
My only other though is that the radio hardware is stuffed which means you are out of luck.
I would take the phone apart and carefully and clean out any dust etc that has gathered in the device (a very long shot but you never know).
Good luck
Click to expand...
Click to collapse
hmmmm, never would have thought about that.
and what does it mean stuffed?
is that the term I should use to research that.
This is the first I've ever heard of that...
And no, we didn't try unlocking.
I was thinking that the stock rom would have a better chance at making the radio stick versus a custom radio. but it is worth a try.

Unlock, flash to custom radio, flash to custom ROM.

derekwilkinson said:
Unlock, flash to custom radio, flash to custom ROM.
Click to expand...
Click to collapse
I found some older threads about this just now,
most of them gave up on trying to fix this.
And one said it was definitely a hardware issue. :/

codybear said:
hmmmm, never would have thought about that.
and what does it mean stuffed?
is that the term I should use to research that.
This is the first I've ever heard of that...
Click to expand...
Click to collapse
Stuffed, broken, busted, fubar'ed etc

njakobs said:
Stuffed, broken, busted, fubar'ed etc
Click to expand...
Click to collapse
Ahhh,
Well Thanks for that info,
that's what I was thinking,
and what was said in the old threads I found.
I'm just going to send her my vogue.
Don't need it anymore....And it's part of the Karma thing PPCGeeks has.

I've just bricked mine. Don't make the same mistake!!!!

I flashed laurentius29 rom to my tmous leo.
Result - expensive paperweight.
Already exchanged it in tmob store telling them it just died. I've had it for just two days.
Seriously! Don't attempt to flash non-tmous roms to your tmous phones.
I thought they are fos saying you can brick your phone doing that.
I thought I knew what I was doing with my quite long winmo history. (Samsung i730, Kaiser, Rafael and Leo just recently)

do you have hspl installed?

Doesn't matter as non-TMOUS ROMs won't work on a TMOUS HD2

gees.....better buy openline HTC HD2...

Just to make sure:
Flashing a TMOUS ROM to a NON-TMOUS device won't brick your device?

With Hspl you should be able to recover... ROMS dont touch the bootloader. And without Hspl you wouldnt be able to flash..

It is not the fault of his ROM but your choice of a ROM not compatible. I think his base is 1.72 or 1.66 and with drivers from this same build. I would ask him to be sure.
Make sure you flash a ROM with 2.10 base and you should be ok.
Sorry to hear about your device but at least you were lucky enough to be in the US and they changed it out quickly for you.

Hi Stank0,
I'm very sorry to read this and will make an anouncement immidiatly that the rom isn't compatible with the T-Mob US model.
Sorry to ask you as you got damage enough but can you tell me the procedure you followed flashing the rom?
Thank you.
Stank0 said:
I flashed laurentius29 rom to my tmous leo.
Result - expensive paperweight.
Already exchanged it in tmob store telling them it just died. I've had it for just two days.
Seriously! Don't attempt to flash non-tmous roms to your tmous phones.
I thought they are fos saying you can brick your phone doing that.
I thought I knew what I was doing with my quite long winmo history. (Samsung i730, Kaiser, Rafael and Leo just recently)
Click to expand...
Click to collapse
Indeed that's true far as I know but I realy like to know how Stank0 bricked it to avoid this in future.
snipey said:
With Hspl you should be able to recover... ROMS dont touch the bootloader. And without Hspl you wouldnt be able to flash..
Click to expand...
Click to collapse

After I flashed HSPL2, I tried a few ROMs. 2x NRG's and Kumar's. They all worked OK but I wanted to try yours bcz I used to have it for quite a while on my Rafael. (before I switched 2 NRG for some reason I don't remember).
I always flash over old flash without going through all the "necessary" steps and it almost always worked good. I went through flashing stock first only when something went wrong. (very rarely)
So I did the same thing with your ROM flashing it over NRG's. (Via USB)
Obviously, my poor tmous LEO couldn't handle all that "Ultimate Power" and after the flash was succesfully finished, it never started up.
No light, no sound.
First I thought I'll just get into a bootloader and reflash.
But after I found out that I can't get even bootloader up, I realized I'm pretty much screwed.
The phone didn't react to ANYTHING.
When I plugged it up to my laptop, it tried to install new driver for it but of course unsuccessfully.
I've had quite a hard time to find a store with HD2 in stock. Apparently they sell better than fresh rolls.
Oh by the way Laurentius26, I don't blame you for it at all. It was my fault not listening what wise people say. From now on, if it doesn't say "TMOUS COMPATIBILE", I'm not touching it.
And that what I recommend others to do too.
Unless you want to live dangerously and have a nice but quite expensive paperweight.
Laurentius26 said:
Hi Stank0,
I'm very sorry to read this and will make an anouncement immidiatly that the rom isn't compatible with the T-Mob US model.
Sorry to ask you as you got damage enough but can you tell me the procedure you followed flashing the rom?
Thank you.
Indeed that's true far as I know but I realy like to know how Stank0 bricked it to avoid this in future.
Click to expand...
Click to collapse

Sorry to hear about your device but at least you were lucky enough to be in the US and they changed it out quickly for you
Click to expand...
Click to collapse
Sorry too
but if i`m not wrong the brand new TMOUS Leo costs only 199.99 $ in th US vs 600 in Europ

Yes TMOUS Leo costs 199.99 $ in th US with 2 years contract!!!
HTC HD2 in England is for free with contract!!!
So....

yeah it does. With 2 yrs contract. I paid $450 + tax however. No contract.
gf7800 said:
Sorry too
but if i`m not wrong the brand new TMOUS Leo costs only 199.99 $ in th US vs 600 in Europ
Click to expand...
Click to collapse

So let me get this straight, you flash hspl on your device to flash custom ROMs. If you brick a phone, is it completely useless forever in eternity? (besides being a paperweight) Is there anyway to recover it at all? At all, at all?

Hi Stank0,
Thanks for letting me know.
Flashing a rom shouldn't brick your device like that, even if the flash went all ok or not it should always be possible
to reflash (recover) as mentioned earlier that flashing a rom doesn't touch the bootloader.
Dit you try to take out the battery for half an hour and then try to get in bootloader?
Anyway I'm very sorry your device is bricked .
To make sure I've updated my rom threads with a warning to avoid this in future.
Stank0 said:
After I flashed HSPL2, I tried a few ROMs. 2x NRG's and Kumar's. They all worked OK but I wanted to try yours bcz I used to have it for quite a while on my Rafael. (before I switched 2 NRG for some reason I don't remember).
I always flash over old flash without going through all the "necessary" steps and it almost always worked good. I went through flashing stock first only when something went wrong. (very rarely)
So I did the same thing with your ROM flashing it over NRG's. (Via USB)
Obviously, my poor tmous LEO couldn't handle all that "Ultimate Power" and after the flash was succesfully finished, it never started up.
No light, no sound.
First I thought I'll just get into a bootloader and reflash.
But after I found out that I can't get even bootloader up, I realized I'm pretty much screwed.
The phone didn't react to ANYTHING.
When I plugged it up to my laptop, it tried to install new driver for it but of course unsuccessfully.
I've had quite a hard time to find a store with HD2 in stock. Apparently they sell better than fresh rolls.
Oh by the way Laurentius26, I don't blame you for it at all. It was my fault not listening what wise people say. From now on, if it doesn't say "TMOUS COMPATIBILE", I'm not touching it.
And that what I recommend others to do too.
Unless you want to live dangerously and have a nice but quite expensive paperweight.
Click to expand...
Click to collapse

this is bad, im sorry for your loss
though flashing a rom doesnt screw up the bootloader

Problem is T-Mob US model has different NAND.
XDA opened two section as well as the hardware is different.
* HD2 ROM Development
* T-Mob USA HD2 ROM Development
I have no T-Mob USA model and I'm not 100% sure if the device is bricked because
of flashing the rom so it's better to take precautionary measures to avoid this in future.
bbezja1 said:
this is bad, im sorry for your loss
though flashing a rom doesnt screw up the bootloader
Click to expand...
Click to collapse

It sounds more like coincidence.
I can't imagine Leo includes bootleader in his rom, so it shouldn't have effected the spl at all.

Thanks Fards,
Indeed there's no SPL (bootloader) in the rom so if a user flashed HSPL first and then the rom it doesn't touch the bootloader and it should be always possible to get in bootmodus after a bad flash and reflash the rom.
It worried and made me doubt for 2 days but this makes no sense the device is bricked because of flashing the rom it must be coinsidence.
There are enough stickies how to flash a rom and I've included rom flash instructions in my rom thread so I'm going to remove the warning.
@Stank0, I feel sorry your device is bricked but I hope you understand my decission.
Grtz Leo
fards said:
It sounds more like coincidence.
I can't imagine Leo includes bootleader in his rom, so it shouldn't have effected the spl at all.
Click to expand...
Click to collapse

lemonspeakers said:
So let me get this straight, you flash hspl on your device to flash custom ROMs. If you brick a phone, is it completely useless forever in eternity? (besides being a paperweight) Is there anyway to recover it at all? At all, at all?
Click to expand...
Click to collapse
re-bump. can anyone answer this?

I agree with everyone else. It wasn't the flash-it was the flasher. He didn't follow the basics. Wrong rom, flashed repeatedly while bypassing vital steps. It wasn't bricked-he got jumpy. He shouldn't flash if he can't follow simple tutorials and stickies.

Can I safely upgrade my G1 to Android 2.1?

I'm very new to Android (just got an HTC G1 with Android 1.6 from Craigs List) and I was wandering if there is a way to safely upgrade to Android 2.1.
I truly appreciate your help.

It's perfectly safe if you read and understand all the instructions before you do anything. If there's any part where you aren't 100% sure what you're doing and what the aim of it is, do more research before you press a single key. All the information is in the wiki here (link up top) and the wiki at cyanogenmod.com

One must realize that NOT ALL INSTRUCTIONS are correct. SOME instructions can brick your phone.
Using this is brick-proof: http://forum.xda-developers.com/showthread.php?t=717874
HOWEVER, your phone needs to be set up to work with it (the setup is safer for preparing for this than most others).
Installation of 1.33.2005 SPL aka "DEATHSPL" is the most dangerous step anyone puts in their instructions. The above link DOES NOT require 1.33.2005. It works with all SPLs, including all of the "perfectly safe" SPLs -- 0.95.x000 and 1.33.2003.

Thank you for the great responses.
I read a couple of instructions and looks like I have a lot more learning to do before I can touch anything. For example there are terms like rooting, flashing and other terms that I have no idea where to start from.
Do you know of any video that shows all the process?

geora said:
Thank you for the great responses.
I read a couple of instructions and looks like I have a lot more learning to do before I can touch anything. For example there are terms like rooting, flashing and other terms that I have no idea where to start from.
Do you know of any video that shows all the process?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=tS9l2XVG0iY
i cant verify the files, as i just used the wiki and understood from past flashing experience =]

lbcoder said:
1.33.2003.
Click to expand...
Click to collapse
And to add if you use this SPL.. and then decide that (after more reading debugging ect.) it would be easier to use dangerSPL; its a simple mater of using fastboot to flash 1.33.2005 and any future radios without the risks in most peoples instructions.
Information on 1.33.2003 is in CONFIRMED!! BRICKS: Radio and SPL + New SAFETY theory read a few pages around that post to ensure you understand what you are doing and what you want to install.
The important thing is to understand the importance of compatibility between radio->SPL->recovery if you want to flash these without (most) of the risk..
The other thing is to keep focused when flashing a bootloader (spl) and don't get side tracked, of start flashing other things since you last verified the state of your phone. If you can't do this best stick with what works now.

geora said:
Thank you for the great responses.
I read a couple of instructions and looks like I have a lot more learning to do before I can touch anything. For example there are terms like rooting, flashing and other terms that I have no idea where to start from.
Do you know of any video that shows all the process?
Click to expand...
Click to collapse
I absolutely DO NOT RECOMMEND videos.
The processes you need to follow are NOT CONDUCTIVE to being learned through videos and the PEOPLE who make the videos, by and large, are RETARDS.

Unfortunately there isn't a safe method to update G1 to 2.1 ROM. You will have to change SPL and propably a radio and when doing this you can brick phone. However, there is no chance to brick phone other way. You can try to flash as many ROMs as you want, you can do what you want, there is always recovery when you can just wipe and flash a new ROM.

raven_raven said:
Unfortunately there isn't a safe method to update G1 to 2.1 ROM. You will have to change SPL and propably a radio and when doing this you can brick phone.
Click to expand...
Click to collapse
1) while it may take more foot work you can flash a 2.1 rom without spl/radio changes
2) not safe well this depends.. is it safe to walk on a trail next to a cliff without a gaurd rail.. maybe not if you are blind but for most people it is... the problem is many people are blind in the android world.. and thus fall off the cliff.. frequently feeling they did everything correct without realizing they forgot the most important part..

[Q] Risks of Rooting

Hey guys, I've been thinking about rooting my MT4G, but I can't risk getting this phone bricked. I was wondering what the risks are using this method http://forum.xda-developers.com/showthread.php?t=858021
I've heard that it can only be truly bricked if you mess with the HBoot or radio stuff. Is this true and what are your thoughts on the matter?
Thanks,
Barrett

The method that's depicted in that link is the "safer" one generally. While there is always a risk involved with this type of thing, you can be safe by following those directions EXACTLY. if you do that, it should be just fine.

There SHOULD be no risks to rooting. But check if you have a good or bad chip first... Because the myTouch 4G is just dumb like that. HTC really messed up with this phone with it's plethora of hardware problems.

I personally think that if you "can't risk" a brick, you probably shouldn't root it. And yes there should be no risks, but with these crazy chips floating around and people not being able to follow directions, there are always risks.

lowandbehold said:
I personally think that if you "can't risk" a brick, you probably shouldn't root it. And yes there should be no risks, but with these crazy chips floating around and people not being able to follow directions, there are always risks.
Click to expand...
Click to collapse
+1
There are always risk when you are tampering with the firmware of anything. Phones, Computers, Routers what ever. If you cannot "RISK" it you might just want to use VISIONary.apk r14 and just leave "temp root on boot" checked.

Read up as much as you can and then read some more, watch some youtube howto videos and if after all that you are still doubtful that you can do it then stick with stock. Its really not as overwhelming as it seems to root a phone though, but it is pretty basic and after youve done it once you will wonder why you didnt do it sooner.

I also agree with these guys. If you cant take the risk, then dont do it. There are people that want to root and those who dont. Then there are people who should root and those who should not. Rooting is only needed if you want to flash custom kernels,roms, radios etc. If your an average user then dont worry about rooting. It will do you no good.
If you do decide to root, then just read and take your time. The instructions are all laid out and have been used many times. When in doubt ask.
Good luck

Thanks guys, I really appreciate all of the responses! I'm fairly certain I'll root, but I am still reading. I'd like to know some worst case scenarios and what I can do to prevent them. What if I mistype something while perm rooting? Also, what are the risks of loading custom roms? Is there always a way to restore it even if your stuck on bootloop? One more thing, how do I know if I have a bad chip and what happens if I do?
Thanks again,
Barrett

Barrett S said:
Thanks guys, I really appreciate all of the responses! I'm fairly certain I'll root, but I am still reading. I'd like to know some worst case scenarios and what I can do to prevent them. What if I mistype something while perm rooting? Also, what are the risks of loading custom roms? Is there always a way to restore it even if your stuck on bootloop? One more thing, how do I know if I have a bad chip and what happens if I do?
Thanks again,
Barrett
Click to expand...
Click to collapse
Best thing i can say to do as kind of a brick prevention tool is to make sure you flash eng bootloader cause it opens up more options that would be unavailable if you have a problem. If you mistype something it may not be as big a problem as WHERE it is mistyped. I dont think you can check for the bad chip until your phone is rooted. but it is something that can be checked through adb. The post with instructions in how to check the chip is the one that says something about post your emmc serial.
There really isnt any risk in loading a custom rom, other than getting a corrupt file download that wont flash. Make sure you make a backup through rom manager as soon as you get rooted. It will save you bigtime from having to reset everything up after a problem (ie bootloop or phone overclocked to the point of freezing.)

I think there's a high risk of becoming a flash-O-holic!

well, i tried that method several times and i keep getting s-on. good luck with you

Ace42 said:
I think there's a high risk of becoming a flash-O-holic!
Click to expand...
Click to collapse
I second that, I flash new roms too frequently.
Sent from my demonSPEED Glacier using XDA Premium App

I was hesitant at first, but a couple months later, I went ahead and jumped in. Not too much to be afraid of if you follow instructions. Wouldn't ever go back to a stock ROM and I wondered what I was so afraid of after it was all over.
I try out new ROMs like I'm trying on shirts, its that simple once you get over the initial hump of being a bit hesitant to root a device. There's a supportive community here that will answer any questions you have and chances are- someone has already gone through whatever it is you have an issue with and has a fix. Search is your friend, that's how I got by. Just jump in. All the resources are here and other places on the web.
If you're still hesitant... just don't do it. It's not worth your time and anxiety if you're going to be continually fearful of doing something wrong. This is the kind of thing for tinkerers.... if you're not a tinkerer, just enjoy your phone as it is.

You can check your eMMC chip before rooting by using terminal app. The command is: cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name

eqjunkie829 said:
Best thing i can say to do as kind of a brick prevention tool is to make sure you flash eng bootloader cause it opens up more options that would be unavailable if you have a problem. If you mistype something it may not be as big a problem as WHERE it is mistyped. I dont think you can check for the bad chip until your phone is rooted. but it is something that can be checked through adb. The post with instructions in how to check the chip is the one that says something about post your emmc serial.
There really isnt any risk in loading a custom rom, other than getting a corrupt file download that wont flash. Make sure you make a backup through rom manager as soon as you get rooted. It will save you bigtime from having to reset everything up after a problem (ie bootloop or phone overclocked to the point of freezing.)
Click to expand...
Click to collapse
I have heard of the eng bootloader, but can you explain it to me?

Pravox said:
You can check your eMMC chip before rooting by using terminal app. The command is: cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Click to expand...
Click to collapse
It says "no t found"

cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
That is the correct command. Make sure you include the space after "cat". I just tried on an unrooted phone and received SEM04G in reply.

Pravox said:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
That is the correct command. Make sure you include the space after "cat". I just tried on an unrooted phone and received SEM04G in reply.
Click to expand...
Click to collapse
M4G2DE
From what I've read, this is the bad one. Now what?

Barrett S said:
M4G2DE
From what I've read, this is the bad one. Now what?
Click to expand...
Click to collapse
Yup, thats the one they say is the bad one. I've got it too.
Sent from my demonSPEED Glacier using XDA Premium App

eqjunkie829 said:
Yup, thats the one they say is the bad one. I've got it too.
Sent from my demonSPEED Glacier using XDA Premium App
Click to expand...
Click to collapse
Okay, do I go ahead and root and claim a warranty if the chip gives out?