Related
Been following this site for weeks and it is getting more popular eacha nd every time someone buys a Diamond phone, so keep up the good work.
I have finally decided to see what I can do with mine by upgrading the ROM and I would appriciate any advice you guys can give me as i am a totally newbie.
Here are the details:
It is on T-Mobile (UK)
Version -
1.37.110.3 WWE
06/20/08
1.00.25.03
Thanks
Hello there!
Not sure what you mean by upgrading the rom? Guess you mean applying a cooked rom?
A cooked rom is one thats been customised and is flashed over the top of your current rom, in your case probably a "stock" or out of the box/factory rom.
First thing to do in your case would be to upgrade the Radio. You may well need to run the HardSPL (I needed developer edition) and then apply the radio upgrade.
From then on, its up to you which cooked rom you run as they all have advantages and disadvantages. For example, im running the Diamond TLR rom as I don't like touchflo (i think its a gimmick that slows things down - drasticaly). Using this rom i'm able to uninstall touchflo and free up significant memory. This suits me down to the ground but not those who want to use touchflo!
Take a look at the wiki (mostly) and the Rom development sub-section of this Diamond section of the forums. As long as you follow the Wiki instructions on HardSPL and then use a rom specifically for a touch diamond, you should be fine.
Be very carefull though and DOUBLE check everything, one wrong flash program and you can destroy your phone.
Have fun!
p.s. Many people think that the factory 1.37.xx roms are the most stable, even more than the later versions. I'm running a TLR based 1.37something and I am very happy with it and never have to reboot my phone.
Got it....Its all here
Hi Lats... I've tried a variety of roms on my Compact IV and I have to say, me and my colleagues at work find that Swiftblades roms are pretty much as good as they come. He's now released version 5.0 and if you're still on the original T-mobile rom, then you'll notice one hell of a difference and improvement in speed and usability.
Go for it and don't worry if your concerned about warranty, there is a stock T-mobile rom floating around on the forum and instructions on how to return your Compact IV back to it's original state.
If you find the whole rom thing confusing, then take a look at this site:- www.modmydiamond.info It'll pretty much tell you everything.
Basically though, you'll find there are 3 phases to upgrading
1) HardSPL - In laymans terms, this pretty much opens the phone up for flashing roms. Most people seem to go for and recommend using Hard-SPL 1.40 Olinex Developers Edition-Unsigned. There are consequences to using an unsigned version, it means you could in theory download and install a dodgy untested Rom, but it's up to you to go for roms on the thread from reputable guys where you can see lots of other people have installed their tried and tested roms.
Once you've done this, you'll not need to do this again.
2) The Radio - This deals with the comms side of the phone, ie phone signal strength etc etc. It's pretty much been agreed by most people that v1.00.25.05 appears to be the best of the bunch.
3) Lastly choose a rom, there are half a dozen really good roms out there and many of them are down to personal choice. Many of them are customised too much for my liking. I chose Swifts as he pretty much keeps his clean and looking like a stock rom.
You'll only have to do the Hard-SPL once and probably the radio once, unless a better radio arrives. So once you've done all this, you can keep trying different roms without the need to do the Hard-SPL and radio all over again.
Hope this clarifies things a bit for you.
Good luck and have fun!
Thanks ever so much guys. I already feel alot more confident about this. Just one question... guide suggests the following:-
Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time
Where is the camera button and it sounds as I need 3 hands to do this!
They're refering to the main round button below your screen in the middle of the 4 buttons, and yes you need 3 hands, but you can just about do it with 2
Let us know which ROM you upgrade to - I'm on the same ROM and radio as you are. Bit nervous about flashing the rom as my last phone (Vario II/Hermes) had to go back a month after I had it due to the screen alignment issues. After the warranty expired, I was flashing daily (lol) and yes, they do make a big difference.
I've got a copy of the UK Tmobile rom from this site, but cant remember the page now or what i typed in to get it... will try again later. It's called "RUU_Victor_TMO_UK_1.37.110.3_Radio_Signed_Diamond_52.26a.25.09_1.00.25.03_Ship"
Lats said:
Thanks ever so much guys. I already feel alot more confident about this. Just one question... guide suggests the following:-
Manually enter the Bootloader by pressing the Power button, Camera button and performing a soft reset at the same time
Where is the camera button and it sounds as I need 3 hands to do this!
Click to expand...
Click to collapse
That is for last resort methods only...
Ensure you are connnected via activesync when doing any flashing, remembering to hard reset again after every flash,
Yeah, most definetly I will let you know but I think it will be over the weekend now. I had a quick attempt to get bootloader going, but it don't look easy. Phone just resets everytime and just reboots back to normal.
If anyone has any tips on which buttons I need to press first or if there is any easier way of doing this, I'm listening.
Lats said:
Yeah, most definetly I will let you know but I think it will be over the weekend now. I had a quick attempt to get bootloader going, but it don't look easy. Phone just resets everytime and just reboots back to normal.
If anyone has any tips on which buttons I need to press first or if there is any easier way of doing this, I'm listening.
Click to expand...
Click to collapse
If you want to flash any ROM - you dont need to manually enter boot loader to do so...
As I mentioned before.
just make sure you have active-sync running and working and the battery id over %50 charged.
I'll be doing this tonight
The Tmobile stock rom can be found here
http://forum.xda-developers.com/showthread.php?t=406327
The other day my screen stopped responding to my touch completely (only about 2 months old). The phone would randomly put itself into airplane mode and when I turned that off I was still able to send and receive text messages. I was unable to view my contacts folder or make calls though because android.phone or various other processes would crash when I tried. So I did a hard reset on my phone to see if that would fix my screen problem and now I cannot even send or receive text because I am stuck at the startup for the device and am unable to complete the startup because I cannot touch the screen. The red light of death comes up briefly when the phone is plugged in but goes away very quickly even with the battery in. The phone boots normally although it seems to take a little bit longer than usual. Does anyone have any idea on what is going wrong and how I can fix my screen?
Thanks!
this sounds like a hardware issue. if your phone is covered by the warranty then just call your provider and they should send you a new one.
is your phone rooted?
My G1 is stuck like this too, although mine was waterlogged so it's no longer under warranty @[email protected]
no it's not rooted
You can try to reflash the stock rom to see if that will help or you can root it and load a custom rom and see if that will make any difference. You can always use your trackball to navigate. If all that doesn't work then like david said its a hardware problem and is covered under warranty.
I can't scroll to navigate because the initial setup after a hard reset requires touch. Where do I find the info on re-flashing the stock rom?
Just find the official t mobile rom and flash like you would any rom. Put the update.zip on root of sd card then power on phone with home + power then in your case I would wipe (alt + w) then update (alt + s). I would try to find you a link but I'm bout to be leaving work. A google search will come up with it or someone else might chime in and give you a link.
http://android-dls.com/wiki/index.php?title=OTA_Updates
Try this.
i'm going to need the rogers stock rom ,not the t-mobile one I can't seem to find it anywhere. also will reflashing the stock rom void the warranty in any way. i assume it won't since there would be no way for them to tell but just double checking.
KYLEFALL said:
i'm going to need the rogers stock rom ,not the t-mobile one I can't seem to find it anywhere. also will reflashing the stock rom void the warranty in any way. i assume it won't since there would be no way for them to tell but just double checking.
Click to expand...
Click to collapse
nope youre basically just re applying the ota update
I have CM6 running and love it. Props to the Cyanogenmod XDA crews for making a non-techie such as myself about to stumble through the process. It took some bouncing around between websites but I was able to get it done.
However, I did have a blackout week over the holidays and did drop my phone a few times. Long story short, my smart phone is no longer so smart looking.
I need to get it back to stock just to make sure I don't have any warranty/insurance issues. When I take it in to get replaced.
I tried running the RUU from htc.com and that didn't work. It doesn't get past the Bootloader phase. Something about the phone isn't connected to the USB (even though it is & the comp recognizes it as a android device). This happens when the black screen comes on with the silver HTC letters.
I thought maybe it was the fact that I had a different baseband version (necessary to get Cyanogenmod on there) and when I try to boot into recovery mode to flash the official radio it gets stuck at the white screen with green htc letters on it.
Some things I just noticed as well, I am unable to have the PC HTC Sync software recognize my phone.
Thanks for the help.
I figured it out, don't worry about it
seminerd said:
I figured it out, don't worry about it
Click to expand...
Click to collapse
What was wrong with it?
please state what you did to fix the bootloader screen cause im stuck there too
Ok, first up I want to apologize for being a huge noob when it comes to smart phones, the Velocity is my first.
Ok, recently upgraded to stock ICS as was told by a Telstra store it would improve battery life.
Suffice to say I now need to charge my phone 2 times during the day, even with all non essential things turned off. Also while my 4g has picked up slighly, my 3g is almost non existent.
I work in a remote town and I usually dont have the luxury of charging the phone at noon, hence a dead phone by 1pm now (used to last all day fine)
Simply, I just want to take it back to the stock gingerbread it came with so I can at least use it again.
I have read through the forums for about 7 hours now, can't find what I need (noob remember)
I did find the holiday shipped rom collection post and D/L the RUU_HOLIDAY_SENSE3_5_Telstra_WWE_2.27.841.6_Radio_3.01.4720.09_3
file.
If I run it it wont do anything because its older than what is on the phone.
Found the instructions on how to turn it into a PH39IMG.zip file and loaded to a SD card. pretty much did the same thing at the hboot menu (older file)
Found out how to turn autoloader to unlock and did that, the sd card method now runs through (every file says missing or something though) till the end, but if you reboot its still ICS.
Yes, I have seen the super guide, but it seemed to be for AT&T phones, and being that i don't know much about them, I didnt want to go through it and be wrong.
I have been told it should be as simple as dl the ruu from HTC and running it, but HTC only have the ICS ruu for telstra phones, not the old GB version.
I have emailed both HTC and Telstra asking about it and no response.
Local telstra shop had conflicting info.. one guy said they could do it, but would cost $100, a different guy said no way to go back.
I'm hoping someone can show an extreme noob how to fix this, otherwise I'll have to look at buying a new phone as its pointless having this one for just half a day!
First of all, thank you for actually taking the time to read.
Second, anything in the superguide is applicable to your phone. Just replace any instances of ATT with Telstra, and you're good to go.
What you're going to have to do, if you want GB again, is to unlock your bootloader and fastboot flash a recovery image (ClockworkMod recovery will do), and then you can get a Telstra stock ROM zip from GB and flash that in recovery.
My other suggestion would have been to do the RUU method, but you've already tried that. I'm working under the presumption that your bootloader is locked, as the RUU method is guaranteed to fail if it is.
I'm curious, however, as to why ICS is using more battery on your device than GB did. That's not normal. Do me a favor, could you either screencap or read out what it says in your Settings -> Power -> Battery Use screen when your phone is nearly dead (14% battery or just an extended usage period). Something is very abnormal if you are getting worse battery life on ICS over GB.
Thanks very much for that,
Bootloader is unlocked (I think I said autoloader before, oops) Did it via the HTC unlock tool.
For a bit more info, I had an error 140 before I unlocked, and an error 155 afterwards. I did look up the error codes and the 155 seems to be a wrong version.
Will do a screen cap when I can for you, but from reading the Telstra forums and Whirlpool, it seems there are a lot of people with the same issue and more
(lower battery life, worse signal strength, tinny speaker on calls, call drops, random reboots on charging.. I only have the first 2 issues)
Most of them are looking for fixes for the issues, well.. complaining about them mostly. I think I'm one of the few that want to return to the old version.
As i said, I dont know a lot about them, and I know GB worked for me
EDIT: Get the Telstra stock rom.. is where I got the first one from ok, or is there somewhere else?
You CANNOT run an RUU with an unlocked bootloader, but that's another story for another day.
Do you have some form of recovery on it (CWM, WCX, TeamWin Touch)? If so, it's just a matter of finding a zip of the stock GB ROM. Else, you can use Jirv311 (I hope I spelled that right)'s method of compiling the stock RUU-based ROM posted on the development forum. I know a PH39IMG flash was made for ATT users, but I would advise against using that.
Per your question about ROM source, where did you find it exactly?
Worse comes to worst, just flash a custom GB ROM instead of a stock one if you can't find it. Holiraider is hella nice and gave me plenty of battery life.
By the by, if you choose a rooted ROM, I would heavily recommend to you to use SetCPU and underclock your phone. Search the HTC Dream G1's app board (under legacy devices), and you'll find a link. It's free to XDA members. On ICS, I have no problems ending the day at 50% battery, and that's with reasonably heavy use and my 3 email accounts checking mail at highest frequency.
Rom was from
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=holiday+shipped+rom+collection
The link has a telstra GB rom there.
Have also read something about radios? From what I see that is what runs the phone signal side.. some threads have said that a RUU rollback wont change the radio version.. is that correct?
Well, doing some thread hopping I think I have done a proper rollback. Using mainly the superguide and associated links, I have unlocked the phone, think I have rooted it, flashed the Kernal and flashed the rom.
For some reason the only proper RUU/roms I could find wouldn't work, so have installed holiraider. I think I did it right because its running and usable on my phone now.
Unfortunately though, the issues I got when I upgraded to ICS are still there. Bad signal and battery life.
As a guide, I used to be able to have full 3g signal anywhere inside my house, now it fluctuates wildly, if I put my wife's phone alongside mine, hers is steady full signal, mine fluctuates between 0 and 3 bars.
Battery life: If left on screen locked, it seems to last overnight (8 hours)
As soon as you use it you can see the battery metre falling.
Sending a txt messages is using 2-3%, a post on facebook is about 5%
PRE ICS: Standby time about 32 hours, usable time: about 8-9hours
POST ICS: Standby time about 8-9 hours, usable time: anywhere from 4-6 hours.
I can only think with my limited knowledge that the signal fluctuating all the time may be what is chewing up the battery? (Bluetooth and wifi both off) And maybe the ICS update 'upgraded' something that the Holiraider rollback hasnt downgraded?
Same thing happened to me upgrading from GB to ICS. Turns out GoogleBackup was causing partial wakelocks, using both CPU and radio constantly. To check for this or anything else keeping your phone from sleeping, install and run BetterBatteryStats (free for xda users) from http://forum.xda-developers.com/showthread.php?t=1179809 and look at partial wakelocks.
Otherwise try checking a process monitor to look at what is active all the time, or perhaps use DroidWall to block internet access to apps that don't require it but may be using it.
Regarding the phone's signal, you'll have to go into the network status (in settings) to get numbers (IIRC correctly anything above -106dBm is a usable 3G signal). If this doesn't help, 2G will give you a better signal but it's not ideal. Nothing should be affecting your signal if you don't change the radio however.
Only major thing in the wake locks is alarm manager.
Signal goes from about 91db to 108db. Borrowed a friends phone and sits stable on about 85db.
I think the radio would have been updated when ics was installed. Can the radio be rolled back too?
Jaximus said:
Only major thing in the wake locks is alarm manager.
Signal goes from about 91db to 108db. Borrowed a friends phone and sits stable on about 85db.
I think the radio would have been updated when ics was installed. Can the radio be rolled back too?
Click to expand...
Click to collapse
Are you talking about the HTC Clock app, or did you install a third-party app by the name of Alarm Manager? If the latter's the case, you know what to do.
If the former is the case, you might just need to go to Settings -> Applications -> All -> Clock and clear its data.
Is your friend also on a Velocity? Different phones can have different readings based on random variables like interference and antenna placement.
Yeah, its just the HTC clock app. turned off the alarm earlier and its gone from the wake lock, but battery life hasnt changed. My last post was from the phone in question and it used 8% battery to type and post it.
Had a 15min phone call today too, used up 45% of my battery ( made sure to check before and after call.)
Nope, friends phone was a moterola Defy+
Thing is, I had this phone from a few days after they released here, so have been using it since Feb-ish on stock GB with no abnormal battery problems or signal problems.
Installed ICS and problems. Rollback to GB, still problems. I'm using the phone in the same area at home that had no issues before, so its gotta be something ICS, or at least Telstra's version of ICS, did to it.Since I still have the issue, its also gotta be something that didnt rollback with just flashing the rom..
So My phone is most certainly bricked this morning. I saw a few posts on the topic, as well as one that was locked. Seems that there a re more than 5 of us, can a mod by chance merge the posts, so we can start troubleshooting the issue, and keep it from happening in the future. I will describe what I have done, and maybe it will help someone come up with an idea of what binds us all to our bricks.
Once upon a time in a galaxy far far away I was a flashoholic:
So I get my black one in the mail, and start playing in the forums, seeing what's what, and I go about trying to moonshine, firmware doesn't match so it doesn't work, get her rooted, s-off with revone, and flash a few sense based roms. No problems. Try the cm rom listed in the first post of the 10.1 link, no gps, weak signal, back to sense. Finally get a few of the threads completely read, and find rc2 of 10.1 flash(using twrp 2.6.1.0, and I do all the wipes and format data, and factory reset before sideloading my roms) get it up and running, gps works, find the build.prop line to edit to get it to stick to sprint to work, and away we go, rom is good, problems are small, phone working exactly llike it's supposed to. I did play with trickster mod here and there, but didn't much care for the program. So was playing in original development, and saw that the twrp forum had new input, so I go into it, and see a new twrp available (2.6.3.0) dl, flash the .img, reboot recovery, wipe everything, sideload 10.1 rc2 again and gapps. Almost immediately noticed the temp on the phone was very warm, almost hot, and that was without being on the charger. It was bedtime, so plugged phone in, go to bed, get up look at phone, and its at 50 percent on the dot, and no red light. Houston we have a problem. So I start researching how to ruu back to stock, and just to see if it was the recovery, I flashed cwm, didn't like it, and then reflashed the older twrp, problem persists, well I really didn't want my phone to reach 0 percent battery, so the race was on, set phone on ac vent and charge it, take it off charger, it would drop 20 to 30 percent in five to ten minutes. Get ruu downloaded, can't get it to run, troubleshooting that, my battery plugged in is down to 6 percent and the speakers are hissing at me, when I see the problem, plug it in to the laptop, run ruu, watching phone, watching progress, complete!!! yes reboot phone, log in to gmail, get message about phone using more power than it's receiving (plugged in to wall again) and boom shutdown. So now I'm thinking to myself hrmm good or bad, red light says charging, go smoke a few cigs comeback in phone boots, and is charging, no errors, everything is running like it is supposed to, everything works. It's still very warm though for not running much of nothing, leave it in the cold air, and she charges up to 100% (albeit slowly took most of the day) unplug her, go to sleep, and about 3 hours later I heard the low battery warning, and woke up to my nice black brick. No red light, no pressing buttons for x amount of time, she is most certainly dead.
Hopefully this can help us figure out what is causing the bricks.
And only 3 more hours to the sprint store opens :victory: that's bound to be fun
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
phatmanxxl said:
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
Click to expand...
Click to collapse
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
I don't know, I love Slim ROMs but if it happens again Sprint will start asking questions and might investigate the phone, plus I got the last red phone in stock
raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
How many brick threads have you seen in here on Sense roms?
n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
Including folks that flashed gsm roms? Zero
n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
i wont even flash an aosp rom on this phone i have seen a few people brick while on aosp.. and the dude i got my one from he bricked his first one running an aosp rom.. he said he rooted it flash an aosp rom.. was fine for a week or so the while listing to music on the phone it died brick.. im not saying its deff aosp roms but i have seen and heard enough where im not going to try it... lol im good with my sense:good:
I wonder what's the difference between GE ones and Sense ones.
raptoro07 said:
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
Click to expand...
Click to collapse
I guess you could summarize it like that, but I thought that I stated I knew it was going to die, shortly after I upgraded my recovery. All flashing after that was an attempt to troubleshoot/save the beast if at all possible.
Well I know what's causing the bricks.
So i figured out in part at least what is indeed causing the bricks. It was my first guess, but I messaged a couple of kernel devs, and the information they gave me led me to believe my first assumption was wrong. Apparently it was not. i am not sure if it's an aosp thing, a twrp (was using 2.6.1.0) when I found out, or just a really nice user error experienced by a handful of people. But regardless, either the kernel, and or some of it's settings are not being wiped in twrp to include an advanced wipe of all check boxes besides usbotg, a format data, and then a factory reset wipe. So when kernel or settings interact with new kernel/rom that you install and they don't play nice together, you get your nice little brick. Oh but how do I come across such preposterous conclusions you ask yourself? So I payed my 50 bucks, got my new phone, put my go to rom on it, and play away; lo and behold a stable 10.1 cm comes out. Can't resist, must flash, disapointing to see in the stable release the first thing I have to do is edit build prop to get sprint signal(it is a sprint rom yes?) Still liking the rom for what it is, probably my favorite, except Trebuchet is laggy as S**t(ping pongs kernels alleviate this, but his kernels are for 10.2). So in an attempt to fig the lag, i play with different settings and whatnot that I found laying around xda here and there. nothing is helping with the stutter I see on the home screen. So I go to the main One thread, and look around for kernels, I find one, don't figure it will work, but figure I'll just wipe if it does bad things to my phone; and it did. 8 boot loops later what do I do? Wipe everything as mentioned above, and sideload 10.1 stable, guess what happens on reboot? That's right bootloops. So some how the kernel or some of it or its settings at least are not going away as they should on a clean install, and that I'm sure is what is causing the bricks.
Ty,
I'll be here all night
You sure do keep a really good attitude through it all though. We've all been there but you are purposely putting yourself and wallet through it over and over to find the culprit. I for one appreciate it.
D