Database Info

Reverting to original SPL with microSD ?

Hi.
Last night I flashed TNT on my TynTN II, and this morning, no more USB. Doesn't charge either.
Not too sure what happened here, sounds more like a hardware problem. The mini USB connector looks fine though.
So time for a warranty repair. I've reverted to the original RUU using my microSD, that was easy.
However, I haven't found a way to revert to the original SPL (I have HardSPL installed obviously).
When I follow the usual route to flash from the SD card, it shows that it's flashing the bootloader, yet when I go back into the bootloader, it is still the Olipro version.
Is there a way to revert to the original SPL/bootloader with just a microSD ?
Looked here, but couldn't find that answer, so Im creating a new thread.
Thanks
Jean-Yves

ive read on multiple threads about this issue and the general opinion is that it is not possible.

Bugger....
They will probably deny repairing my unit under warranty then..

jyavenard;2148613 said:
Bugger....
They will probably deny repairing my unit under warranty then..
Click to expand...
Click to collapse
As long as the original rom is on it they more then likely will accept it.

i think there could be a way to get original SPL area with microSD

jyavenard said:
Bugger....
They will probably deny repairing my unit under warranty then..
Click to expand...
Click to collapse
You need to really brick it .... so it doesn't pwr up.
No power, no bootloader, no visual proof of flashing.
After several users flashed the radio from hell, warranty return was the only answer before the fix came out....they got replacements.

don't worry about it. My buddy's Tilt had the same issue with the USB. I just took the latest official ROM and tossed it on my MicroSD card and flashed it that way. They took it no problem.
-Mc

Yes you can. PM me or I'll try to remember to reply when I have time. Prob. should PM me though.

G1 OTA updates for rooted phones? README!!!!

With all of the (most likely false) articles coming out saying cupcake will be released this week (from what ive heard, good luck getting it by march) everyone is asking "Will rooted G1s get OTA updates?
No, you will not (if you have rooted your phone properly (this means you have JF's latest rom)) receive the OTA update. Technically you might receive it, but it will fail to install if you do. This was done on purpose because if it succeeded you would lose root. Shortly after the OTA updates are released, various members of the G1 "hacking" (yeah, term doesnt quite fit, but it will work for now) community will intercept it, tear it apart, remove all the mean mean code that steals our precious root, maybe add some fun new stuff and then release another modified rom in its place.
If you suddenly decide you do not want root anymore (I am guessing you are too lazy to download the update manually) you can use the RC29 downgrade nbh file found on various threads here, or in my wiki (see my signature) to go back to an official RC29 which would then let you receive OTA updates normally.

duhh lol this should be a board annocuments

I've heard some people saying they got the update but I dont see how that is possible. Wasnt google says like a 2 weeks ago that cupcake isnt close to being ready for the public? The only thing I can think of would be and update to support paid apps. I figured if cupcake was launching someone on here would have announced it.

Correct me if I'm wrong but wouldn't downgrading to RC29 while still rooted just give you RC29 with test keys still enabled? Wouldn't you also need to reflash your recovery partition as well to the stock one?

the rc29 will flash the recovery also the only thing you would be left with is the boot loader

Frankly, we'll all probably have a modified Cupcake before most G1 consumers actually have Cupcake. Google rolls out the updates really slowly. There's no reason to downgrade.

xile6 said:
the rc29 will flash the recovery also the only thing you would be left with is the boot loader
Click to expand...
Click to collapse
Good to know, my g1 has a bad wifi module and I need to restore it and send it back. I figured I would experiment with rooting the defective one first in case it went wrong.
Come to think of it, my wifi reception problem could be an antenna problem which could explain my weak 3g reception, or it might just be the 3g network...

speoples20 said:
I've heard some people saying they got the update but I dont see how that is possible. Wasnt google says like a 2 weeks ago that cupcake isnt close to being ready for the public? The only thing I can think of would be and update to support paid apps. I figured if cupcake was launching someone on here would have announced it.
Click to expand...
Click to collapse
there is going to be a video recorder FINALLY... rumors rumors lol

xile6 said:
the rc29 will flash the recovery also the only thing you would be left with is the boot loader
Click to expand...
Click to collapse
bzzzzzt. wrong answer . the RC29 nbh also flashes the bootloader.

MY bad i meant the Engineering SPL wouldnt that still be left?

hmm....so the new cupcake update coming out will close root again? that is so stupid, why wont they just let it be.
granted, like mentioned above, some of our famed and hard working G1 modders will probably have a modded rom with the whole cupcake update on it before everyone would have recieved the OTA anyway.
we'll see what happens i guess, but not for nothing, im really looking forward to the Cupcake updated features and abilities
im almost tempted to just revert back to RC29 just to get the official OTA and see how it is, but then again, whos to say it wont take months for me to get it.

As a note for all those who read my post and thought "yeah, I am lazy, I might as well downgrade and let the OTA's come." you might want to rethink it. If you downgrade, and the new OTA reflashes your system to not accept the RC29 downgrade, you might never get root again. And yes, this is entirely possible.
If you have root, I would not risk it for laziness or eagerness to have the latest OTA because history shows JF has had modified updates in less than 24 hours (I think they were all about 3-5 hours later) after the OTA's were first found.

i wholey agree with that. i definatly dont want to be locked out of root again. although i dont use it as much as others, root is good to have if needed to use it for something.

It would be stupid to downgrade to receive the ota. It took 1 month after the release just to get rc29. Waiting for someone to rip apart and modify the cupcake ota will be much quicker than to wait for the ota update yourself plus root access probably will be lost. Just say no to ota!

Anyways if people are so eager to see cupcake in action visit their local tmobile retailer I bet they will have it as soon as it gets out

Downgrade? Revert? Not an option now that I have root, no way I would chance losing it. Good heads up, I was pretty sure (actually was one of the ? i had) before rooting that this would occur. I spent some time here on XDA and realized that I could trust this forum and the devs to support the rooted community.
Thanks to all who make root possible and what it is on the G1!

All~G1 said:
Downgrade? Revert? Not an option now that I have root, no way I would chance losing it. Good heads up, I was pretty sure (actually was one of the ? i had) before rooting that this would occur. I spent some time here on XDA and realized that I could trust this forum and the devs to support the rooted community.
Thanks to all who make root possible and what it is on the G1!
Click to expand...
Click to collapse
well said ..... thanx much. XDA has helped me start learning this new language. As I stumble through, I find a surprising lack of b.s. and have learned quite a bit ... way thanx, to all ya all

my theory on when the next RC will drop.
They have been slow to get out updates, unless there is a exploit found.
When the bug was found everybody got rc 30 in a few days, I think that the new found downgrade route will speedup the next update to stop downgrading, if the tmob wants to keep the handset locked they will push for a speedy update to stop downgrades.
They also eluded that a beta was close but the holidays would alow it down but they did say it would be january, and if they are late people grumble and lose faith, for a phone that's sold on what it can become not what it is out of the box, losing faith means losing sales...
Bhang

xile6 said:
MY bad i meant the Engineering SPL wouldnt that still be left?
Click to expand...
Click to collapse
I am pretty sure flashing an NBH will bring you back to the original SPL. Someone correct me if I'm wrong.
They have been slow to get out updates, unless there is a exploit found.
When the bug was found everybody got rc 30 in a few days, I think that the new found downgrade route will speedup the next update to stop downgrading, if the tmob wants to keep the handset locked they will push for a speedy update to stop downgrades.
Click to expand...
Click to collapse
The problem that T-Mobile has now is that in order to stop downgrading, HTC would have to make a new SPL that blacklists the signature of RC29 NBH. Google can patch whatever they want, but I'll be able to downgrade immediately just by putting the NBH file on my sdcard and flash it via SPL

I'm curious as to why everyone assumes that the next update will make moves specifically to remove/block root for those who have it?
My understanding/interpretations of the press relases surrounding RC30 was that it was intended to fix the massive security risk in RC29. Perhaps I've missed something, but I've not seen anything that Google or T-Mobile have done specifically to counteract the "hacker" community, the blocking of the rooting method being "colateral damage" from the security fix. If the superuser method can be used to safely provide root access couldn't this be rolled Android itself? It's over my head but has this question been posed to powers that be at http://source.android.com/?

ROM and warranty

I have been trying to get an answer, but with no success so far.
Does anybody know what happens if you take your phone to warranty service with a custom ROM?
And...
with a custom SPL?
with stock ROM and SPL but a custom official Radio?
with an official ROM, but not the stock one (updated)?
with an official ROM but of another language?
with an official ROM of the same language, but with different or no brand?
Please answer at least a couple of these points... I'm desperate...
And please do not say "it should be" if you don't know, since everybody gives different answers this way. The best would be if somebody had tried that or if HTC had made an official statement about this.
Thanks!

Officially, if you alter your phone in any way, other than official software update, your warranty is void. Period.
My phone stuck in bootloader with a custom rom on it and AT$T online tech could not get it out of bootloader ( didn't tell them it had custom rom and Spl ) just told them it got stuck trying to update the rom. Three days later they sent me a new (refurb ) I sent them the old phone . That was the last I heard of it. For what it's worth.

denco7 said:
Officially, if you alter your phone in any way, other than official software update, your warranty is void. Period.
Click to expand...
Click to collapse
I thought that, but the warranty certificate doesn't even mention that. That's why I am asking. Someone told me that they won't be happy because you are breaking WM's EULA, but my thought then was that flashing SPL or Radio only does not break WM's EULA. And even installing another official ROM, but not officially available for download, may not break the EULA.
denco7 said:
My phone stuck in bootloader with a custom rom on it and AT$T online tech could not get it out of bootloader ( didn't tell them it had custom rom and Spl ) just told them it got stuck trying to update the rom. Three days later they sent me a new (refurb ) I sent them the old phone . That was the last I heard of it. For what it's worth.
Click to expand...
Click to collapse
Good news. Thanks for sharing.

denco7 said:
Officially, if you alter your phone in any way, other than official software update, your warranty is void. Period.
My phone stuck in bootloader with a custom rom on it and AT$T online tech could not get it out of bootloader ( didn't tell them it had custom rom and Spl ) just told them it got stuck trying to update the rom. Three days later they sent me a new (refurb ) I sent them the old phone . That was the last I heard of it. For what it's worth.
Click to expand...
Click to collapse
That's cool, IMO it sounds like you got lucky :-D I've sent phones in before because of physical issues and made sure I did my best to restore to factory settings before that. I'm with AT&T and was told over the phone that if I had used a non AT&T / HTC ROM that the warranty was void. If I sent my phone in like that, AND they checked, I would have been liable for the cost of the phone...not saying it *will* happen, but I wouldn't risk that myself :-D

Hmmm... An idea is that they say that because they don't want you to flash, but that they won't say a single word and repair/replace your phone in any case, since the warranty card does not mention it. Of course they won't if they suspect that the damage was caused by you...

Black Antitoon said:
Hmmm... An idea is that they say that because they don't want you to flash, but that they won't say a single word and repair/replace your phone in any case, since the warranty card does not mention it. Of course they won't if they suspect that the damage was caused by you...
Click to expand...
Click to collapse
Hopefully that's because they don't care and not because there's some people working on the phones who don't remember to check, etc...I wouldn't encourage sending back a phone with a custom ROM until I heard more success stories. Chances are that everyone has been trained that flashing a ROM will void the warranty, but the enforcement? Well who knows...

Of course. The only good reason for doing that would be that the phone does not turn itself on anymore, or does not recognise USB and is without HSPL. In these two cases it is impossible to revert to the stock ROM, but for the same reason it should also be difficult for HTC to notice that...

Black Antitoon said:
Of course. The only good reason for doing that would be that the phone does not turn itself on anymore, or does not recognise USB and is without HSPL. In these two cases it is impossible to revert to the stock ROM, but for the same reason it should also be difficult for HTC to notice that...
Click to expand...
Click to collapse
Ah, excellent point. *facepalm*

Bricked cdma htc hero after ruu 1.56 Semi Solution

Ok, just like all of you I have rooted, experimented to the limits and pushed them well little did i Know is that you cant reflash the 1.56 ruu so needless to say I ended up with a brick but luckily for us it will still connect in fastboot
so this is a solution to at least get it up and running
Pros-
Reactivate your phone since it will be formated
All functions will work
can still root, install .apk's use wifi etc
camera etc
so the pros are it will operate just like nothing ever happened now to the con's
YOU WILL HAVE TO DO THIS EVERYTIME YOU TURN OFF YOUR DEVICE
Ok here is how to fix it
Connect your phone to your PC
open command and navigate to your android tools folder
type in
fastboot devices
make sure it detects your device
should show the HTC logo on your phone
now simply type
fastboot oem boot
wait a couple minutes while your phone reboots
viola you phone is back to running again...just dont turn it off LOL

can you launch the RUU again and (hopfully) have it restore your phone correctly?

You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet

rayborn said:
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
Click to expand...
Click to collapse
hmmmm interesting man. honestly you should be able to rebuild all the / partitions. such as /misc and /radio. we need some linux junkies in this thread to tell us how to rebuild failed / partitions

This is amazing. Sure did work for me. I just wish there was a way to get it flash the original radio. I have only had this thing two weeks and would love to take it back and exchange it, but I am just paranoid since it shows radio 2.41.04.02.03.

wait, what exactly did you do to get your near-bricked phone?
you used the 1.56 RUU on your phone that had a 2.xxxxxx radio?

have you tried both of the RUU's? the original and 1.56?

My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution

did you try the 1.29 RUU?

yeah i tried every sprint hero ruu i promise you i left no stone unturned trying to fix this

BRILLIANT!
I can't tell you how impressed I am that somebody has found what i now consider to be the first step towards getting the RUU 110 error solved.
I still feel that the issue comes down to the lack of ADB that seems to happen once you get 110... maybe a driver issue on the phone vs. driver issue on the computer? after all the RUU starts failing on all the ADB commands when you check out the RUU logs...
sorry i can't help take it from there, i returned my phone to sprint inside of the 30-day window and just told them something i installed form the market "bricked" my phone...
I eagerly await your results though for a final step towards solution, as I am dreading the day i have to RUU my phone for whatever reason that may be, although I've been running a personally customized Pancake ROM for almost a week and totally happy with it so won't be doing anything until 2.1 is official...
R

rayborn said:
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
Click to expand...
Click to collapse
Same exact thing for myself. Multiple people said the way to go back to the stock radio was to use the RUU. I tried both RUU's and same results. Now I am just trying to decide what is better.
Live with this and hope for a better option to come or take back a "bricked" hero that shows Radio 2.41.04.02.03 and hope I don't end up getting charged later.

IMHO I think the best thing for you guys to do is wait for our 2.1 update, which will more than likely have a smiliar radio update. Then you can just say the update bricked the phone.
If we get the same radio version, then just take it back, if we get a different version then maybe we can find a file to edit the number to make it say what ever version you want it to say, something like editing Build.prop. Then Sprint has nothing to ask questions about. Should be out in a few weeks if the rumors are right. Maybe you can deal with this soultion until then.
As far as the don't turn your phone off issue, mines been up for 13 days. I hate turning it off, partially because of the missed emails and partially because I worry that it won't come back up.

Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?

SamXp said:
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
Click to expand...
Click to collapse
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?

mginther said:
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
Click to expand...
Click to collapse
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen

tatonka_hero said:
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
Click to expand...
Click to collapse
True, and if we elect to continue to use either a Fresh or Damageless version of an official 2.1 Sprint ROM, then we should be ok. But if we wanted to go to the Sprint ROM, there are going to be a lot of bricked phones if there isn't a way to understand what is going on when a 1.56 RUU is used over a phone with the 2.x Radio update.

Just wanted to pass along some more information in case anyone else is having this problem. I had reactivated an old phone temporarily since this one was bricked. This morning I reactivated my hero due to this semi fix and immediately I could call and textimg was fine, but i kept getting vision error 67 for data. Sprint reset my data about three times and it never worked. I tried updating my profile multiple times and it never worked. Finally I Ran the RUU again and sure enough after a reboot or an "oem boot" I had error 67again. I went ahead and updated my profile and this time it worked and data started working. Still hoping someing else comes along though.

well I think the issue here might be that it does not have the recovery backup on it after you do an RUU. I could be wrong but who knows? I would say install flashrec-1.1.3-20091107-2.apk on your phone once you are able to get it up and running then flash the recovery backup and restart. That could possibly fix the issue? I have the files if anyone needs them, I'm not sure how to upload them on here...
~Danny

I'm not sure if it's possible boot into recovery console using this method, but if you can, has anyone tried manually flashing the old radio in the same manner they flashed the new one to revert back and then RUU. Perhaps that may do the trick.
My phone isn't bricked so I can't try it out, but seems like it might be worth a shot in theory.

[Q] Touchscreen failing to respond to touches

I've had this problem for a while where while I'm using the phone, the touchscreen and softkeys fail. For now I've just been putting it into wakelock and unlocking it again, however its getting to a point where I can't use the phone anymore.
ROMs it's happened on: CM7.1, CM7.2 and MIUI ICS 2.4.27 (proxuser port)
Kernel: The standard one, I haven't changed that
Something that could cause the issue is the Korean IME from Google (I have that installed as its the best Korean Keyboard out there for the time being)
Pretty sure this is a hardware problem, if so I'll flash it back to stock and S-ON it and get vodafone to replace the phone for me (or try to as the case may be)
If anyone could give advice or a fix that'd be really handy.
Thanks for any help/advice given in advance.

GideonB234 said:
I've had this problem for a while where while I'm using the phone, the touchscreen and softkeys fail. For now I've just been putting it into wakelock and unlocking it again, however its getting to a point where I can't use the phone anymore.
ROMs it's happened on: CM7.1, CM7.2 and MIUI ICS 2.4.27 (proxuser port)
Kernel: The standard one, I haven't changed that
Something that could cause the issue is the Korean IME from Google (I have that installed as its the best Korean Keyboard out there for the time being)
Pretty sure this is a hardware problem, if so I'll flash it back to stock and S-ON it and get vodafone to replace the phone for me (or try to as the case may be)
If anyone could give advice or a fix that'd be really handy.
Thanks for any help/advice given in advance.
Click to expand...
Click to collapse
No fix. Have had exactly the same kind ot issue on a friend's Desire S,which needed replacement. Don't hesitate about restoring S-On and sending it back to HTC. That's the best course of action to take if you're under warranty...
Sent from a Desire S still looking for a good replacement.

Ah, I got my phone basically a year ago next week so I'm not sure if that means its not in warranty anymore.
Its working better now if I don't type really fast, but it is definitely a hardware problem then?
Sent from my Transformer TF101 using XDA Premium HD app

how to back to s-on?
How to get back to s-on? i have the same problem and still have guarantee.
I installed RUU rom but i still s-off.
H-boot version: 6.86.1002

aarnoldaas said:
How to get back to s-on? i have the same problem and still have guarantee.
I installed RUU rom but i still s-off.
H-boot version: 6.86.1002
Click to expand...
Click to collapse
Read the INDEX. Link in my signature. It has all necessary thread links for you to get back to S-On. Read about it and see if you get a hang of it. Then ask questions in the respective threads. Much easier that way than repeating everything all over again. 90% of your questions will be answered while reading the comments, and also some that you haven't thought of yet.
Cheers.

I think I'll hold out until I can get my hands on a Galaxy S or something similar (and then put MIUI on that and sell this phone or something)
Thanks for the help anyways
I'll tag this as solved (if I can)