Related
Hi all. I went on a trip and I'm not sure if it was the plane ride or what, but my cell is completely messed. It freezes on the HTC screen after the Bell loading screen.
I have pressed the camera + power + reset button and loaded the Bell ROM but it just keeps freezing at the same screen. Interestingly enough, when I flash the new ROM it always is blank under current version - not sure if this is normal? Also, I never had any ROM except the Bell one.
I have read some stuff about MicroSD with the ROM on there, not sure if you guys can help out? I need my HTC back.
csifan29 said:
Hi all. I went on a trip and I'm not sure if it was the plane ride or what, but my cell is completely messed. It freezes on the HTC screen after the Bell loading screen.
I have pressed the camera + power + reset button and loaded the Bell ROM but it just keeps freezing at the same screen. Interestingly enough, when I flash the new ROM it always is blank under current version - not sure if this is normal? Also, I never had any ROM except the Bell one.
I have read some stuff about MicroSD with the ROM on there, not sure if you guys can help out? I need my HTC back.
Click to expand...
Click to collapse
Please do not open new threads to ask questions. Instead, please use the Q&A thread in this section. Opening new threads should only be done for contributions to the site (roms, kitchens, apps, themes, fixes, etc.). I have transferred your question over there. Thanks for understanding.
So, I flashed my frist rom back in April. I tried out the Energy Rom. Last night I tried out the Core Cell Evo Rom. This Rom started to give me trouble so I flashed to the current energy rom. I'm still new to this, so I think I may have made some kind of mistake that I'm not aware of.
I noticed that when I flashed to the new energy rom, the splash screen for the cell rom came up. Now whenever I try to change the date and time on my phone, it kinda locks up. I think it still functions, but because the screen is frozen I can't see what to press so I end up doing a restart. Does anyone know how I can remove all the remnants of the cell rom? I thought when you flash a new rom, it's supposded to completely get rid of the old rom?
First run TASK29, then flash preffered ROM, after that do HARD RESET, and then it must be OK
Some ROMs include a new splash screen, and some don't. The EnergyROM series doesn't include a splash screen, so that's why you can still see the Core splash screen.
You can find utilities to replace this if you search for "splash screen".
Task29 won't affect this (i.e. it doesn't touch the splash screen, nor the radio either), but it does a good job at wiping the ROM area itself.
If the problem still happens after a task29 and a flash (i.e. the lockups), then you should post about this in the thread relevant to the ROM you're running.
Thanks for the info guys. I'm at work but I'll try out the task29 thing when I get home. I didn't post this in the energy rom thread because I didn't want to seem like I was directing my problem at that rom until I had a good idea of what was going on. If the problems still persist, then that's where my next post will be.
You can always reflash a stock ROM. That will give you the original spash screen back and then you can flash the custom ROM again.
Well, it wasn't the splash screen that I was worried about. Seeing the splash screen made me think that the core cell rom was conflicting with the energy rom. After hearing what steviewevie had to say on the subject, I know otherwise. I'll also install a custom splash screen later now that I know that can be done to.
You can go here for the steps to change the splash screen its actually pretty easy and fun.
http://forum.xda-developers.com/showthread.php?t=576703
Ok, I ran Task29 and I've installed the stock rom. Do I need to do another HardSPL before I can flash a new rom?
No you only need to perform the hardspl once which you have already done so from now on when changing roms just make sure to task 29 then flash new rom and thats it
creglenn said:
No you only need to perform the hardspl once which you have already done so from now on when changing roms just make sure to task 29 then flash new rom and thats it
Click to expand...
Click to collapse
Oh? I didn't use the stock rom that was put up on this site. I actually downloaded the Tilt 2 rom from the HTC site. So I thought that would have made some kind of difference.
sigma20xx said:
Oh? I didn't use the stock rom that was put up on this site. I actually downloaded the Tilt 2 rom from the HTC site. So I thought that would have made some kind of difference.
Click to expand...
Click to collapse
HardSPL was designed to stay on the phone, even if you flash stock ROMs. You have to specifically run the relocker utility (from the HardSPL thread) if you want to go back to the stock SPL (e.g. for warranty return).
MOD Note
I'm moving your thread to General. This has nothing to do with ROM development. Custom ROM usage yes, but not Development.
Russ741
Hi guys, I've had a Bell-branded Desire Z (on AT&T's network) for some time now, but I've never gotten around to rooting / flashing a different ROM on it. Since I have some free time this weekend, I figure I'll finally tackle it. Have a few general questions though:
1) Is the method listed in the guide: http://forum.xda-developers.com/showthread.php?t=928160 still the best method for rooting a desire Z? I've heard bad things about visionary, but every rooting method I've read seem to involve it in some way.
2) with S-OFF, am I free to flash any Desire Z / G2 ROM? or will only certain ROMs work with a Bell Desire Z? Any specific recommendation on ROMs? I'm planning on trying out CM7, then going from there
3) What is the best method for backing up my current image + a few other things (mostly contacts and SMS)? Titaniumbackup gets thrown around a lot, but I only have a handful of apps, and really would rather just redownload them then go through the trouble of backing them up
Thanks
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
that is going to be your safest way to root your vision. eventhough this is longer, there is a lot less chance of bricking your phone. the one you listed is very simple to do, but runs a high risk of turning your phone into a paper weight.
when you do have your phone completely s off, you now have every right to flash kernels, roms, and other things. you can find all of the things i just listed over in the development forum on the g2/desire z. download rom manager from the market. that allows you to back up your current rom, flash the latest recovery and so on. it just allows you to not have to manually install everything. it has the popular g2 roms under the "download rom section".
in terms of backing up everything, there are a few different options. every contact to save is linked to your gmail account, so whatever rom you flash and load youll always have those contacts coming with you. thats the beauty of google and gmail on a android device! but with rom manager, you can back up your current rom and image with that app and save it to your sd card. BEFORE YOU FLASH ANY ROM, OR BEGIN TO START TRYING OUT ROMS, BACK UP YOUR STOCK ROM. whenever i got my g2 when it first came out, i made a nandroid backup of my stock rom and i still have it. when i originally backed it up, i just named it "stock" and havent messed with it since. i just know that i have the stock image(it helps me sleep at night). jk, heh. for your text messages and stuff, download sms backup from the market and you can back everything up through that. all of the apps that you download, including the paid ones of course, travel with you between roms, etc.
i hope i helped ya out, and i wish you luck. if you have any other questions, just shoot me a private message!
Thanks for that;
I actually went ahead and used that method in the guide since upon further research, it seems that visonary was only causing issues when it was use for perm root; temp root, which is what that method uses visionary for seems to work fine.
So did that, reboot into the bootloader, confirmed that I had S-OFF on the first line.
Installed ROM manager from the market
Flashed Clockwork recovery
Booted into recovery and did a system backup to SD card
Rebooted and decided to download the Virtuous ROM from ROM manager
Told it to reboot into recovery and flash that image, wiping all data and settings
Got stuck on an bootup loop (HTC logo + start up sound -> black screen -> HTC logo + startup sound ad infinitum)
Rebooted into recovery, and did a restore from the backup (whew)
Phone seems to be working fine now
Now I'm trying to figure out what went wrong... any ideas?
K, I redownloaded virtuous from XDA, checked the MD5, and tried to flash it again.
Same problem, infinite loop on startup screen.
Do i need to flash the engineering hboot? I was under the impression that that wasn't necessary for using custom ROMs.
Still can't figure out what's wrong.
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Im new to this stuff here, and i DO want to learn about it as this stuff is very interesting to me! Technology is something i learn very quickly if im directed in the correct direction
The question i have here is about my Desire Z ( Bell Cannada ).
A few months ago we received a OTA update. So its currently running on Android 2.2.1 : Build - 1.84.666.2 CL322105, and its SUPER slow! Is it still possible to root this version?
I want to install the Gingerbread version on my phone, but i cant find instructions to root this OS version to be able to do so.
Or should i wait till the Official gingerbread Os to come out for our phones?
Ive been searching every where's for this info and everything i find is all back dated to last yr and nothing up-to-date after the OTA.
I hope this question is not TOO n00bish as i tried to search every where for it, and ether i could not find it or i did not enter the correct word search to get a result i needed.
Thanks in advance!
Andrew
Edit: NVM my question here.... i have finally found an update post within the wiki ( April 1 2011 )
Sorry for a useless post!
Thank you all for your efforts in posting in this forum! Very informative!
Athrun88 said:
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Click to expand...
Click to collapse
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
deaththeorist said:
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
You do not need to debrand to flash custom ROMs to the Bell Canada Desire Z.
makken85 said:
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
Click to expand...
Click to collapse
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
redpoint73 said:
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
Click to expand...
Click to collapse
Yeah, I assumed that flashing from ROM manager just meant that it rebooted to recovery and flashed it from there. I guess there is a difference.
Either way, been playing with Virtuous 1.0.2 for a few days now, really like this ROM, but I'm itching to try out something different now. Man, I can see this is going to develop into a time consuming hobby.
Plus, I'm going to need a bigger SD card to store all of these ROMs + backup =X
Oh, another noob question; I've come across a few zip files that included a system folder and an META-INF folder. How exactly do I install these?
G2 only works with at&t
alright here it is my t-mobile G2 won't connect to the t-mobile network at all, I've went through 3 SIM cards because this thing use to kill the SIM card from working on other t-mobile phones and it works perfectly fine on at&t network. so I've unlocked so it will work on at&t just to see if it would work. so i gave p and bought a MT 4G, but i still want to know if the G2 is fixable because I'm just about ready to throw in the towel this is what I've tried to resolve the problem called t-mobile they ended up saying just return the phone but i can't since i didn't buy it from them. Called them again got the unlock code. I've flashed the radio a few times. I've also just got the leaked 2.3.3 update and nothing has worked. It find t-mobile network but says your SIM card isn't allowed to connect to this network then after trying again it says unable to connect to network please try again later.
Just so frustrating i don't know what to do just about to say forget it. this thread is my last resort.
also i still have S-OFF
i used this method on my G2 just yesterday and put on CM7.0.3. the only issues i came across were because i restored everything (should have just done apps and app data) using Titanium, which put me in a boot loop. I'm dumb, so i did it twice before i figured out what was the problem. the thread has a comment about how Visionary is dangerous, but the OP responded that since it is only used to gain temp root, there should be no problems.
Hopefully this is the right place to post. I apologize if it's not.
Last week I bought the Samsung Galaxy S2 X from Koodo Mobile. The model # is SGH-T989D and runs the newest version of ICS. 4.04 I believe.
I hadn't had any problems until recently. I was trying to root my phone when I ran into some trouble. I forgot to make a backup of my system, so when I ran into problems, I just decided to try out a couple custom roms. At some point something got messed up badly with my phone. Whenever I turn it off now the lights at the bottom of the screen stay on. Unless I hold the power for 30 seconds to a minutes it won't turn back on. The factory reset has also been a problem. I'll go to reset it, and it formats the usb storage, but doesn't restart. When the phone is on, it seems to work fine.
I finally managed to get a telus stock rom to flash and work. So I have two questions I'm hopeful someone can help me with.
1. Are there any Koodo stock roms for ICS? I've looked on tons of different sites, and it seems it's all either for T-mobile or Telus. Is that because Koodos just came out with their phone? I'm just looking for the exact version that would have been on my phone when I got it. I found one online, but it had no baseband version. If I have to return the phone or send it in for repairs, I'd like it back to stock,
2. My other question is, does the light not turning off, and the turn on problems sounds like a hardware issue? I've been trying to fix this for the last 24 hours and it's driving me nuts. Since I'm a noob I have no idea whether I should keep trying or just send it in for repairs. Does it sound like something that can be fixed? Like maybe I'm flashed a wrong kernel or am using a bad rom? I don't know, but advice would be much appreciated.
Thanks to anyone who answers.
you have various roms made for koodo..2) are you talking about the soft keys? depending on what rom you use they can be different (locationwise) ... if I'm not mistaken all --- This is my personal opinion. Jedi on koddo should be more than sufficient as to suit your daily driver needs. Dev is very helpful and keeps a very organized thread. You can also try darkside, if I'm not mistaken he had a koodo version. i own a hercules so i at give more information... for your best info, go into the thread and ask the ppl i n them for their experience. everyone's needs are different so for what might work for me might not for you Infamous is another one. Just click on the t mobile dev section and you just scroll for what you like.. Hope this help
I guess my main question is about the key lights staying on. I'm pretty sure it means its not shutting down correctly because it also won't turn on again unless I hold down the power button for 30 seconds. So could that be caused by anything I did? Like any of the flashing or customers roms I used, or should I just send it back into Koodo?
Okay download this: http://sourceforge.net/projects/darksidetools/files/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip/download
And then flash a rom (any one, just pick one)
That is a flash able zip (in cwm recovery) that will completely wipe off every piece of system and rom data (does NOT touch anything on your internal memory or external sd). If your hardware lights are malfunctioning due to software, this will fix it. Then, when you flash your rom, if you still have the issue with your hardware lights, it's likely a hardware issue and you should follow a guide to return to stock everything and send it in for warranty repair.
Also, this is a Koodo based rom if you're interested:
http://forum.xda-developers.com/showthread.php?t=1849748
yoft1,
I appreciate your help. I did what you said and downloaded both the darkside clean wipe and the darkside cache wipe. Flashed my rom, and the light finally started to shut off.
Except when I did a normal factory reset just from the settings menu, when it reset I still have the same problem, it goes back to keeping the lights off. Does that make any sense to you? Like could something in the darkside clean or cache wipe fix it but then a factory reset mess it up again?
Also if I wanted to make a backup of my system, what program would you recommend to do it? Thanks again.
Just run the cache wipe again. It will fix that.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Great, thanks for the help.
One other question, if I want to put my phone back to the EXACT way it was when I bought it, do I just need to flash a stock rom, or do I need to flash a kernel as well?
robois88 said:
yoft1,
I appreciate your help. I did what you said and downloaded both the darkside clean wipe and the darkside cache wipe. Flashed my rom, and the light finally started to shut off.
Except when I did a normal factory reset just from the settings menu, when it reset I still have the same problem, it goes back to keeping the lights off. Does that make any sense to you? Like could something in the darkside clean or cache wipe fix it but then a factory reset mess it up again?
Also if I wanted to make a backup of my system, what program would you recommend to do it? Thanks again.
Click to expand...
Click to collapse
If you're looking to make a backup of your entire device image, your cwm recovery will do that for you under backup. No other way to do it, you have to do it via a recovery mode.
I don't know why factory reset would be causing that problem since I never use that but it does seem odd.
robois88 said:
Great, thanks for the help.
One other question, if I want to put my phone back to the EXACT way it was when I bought it, do I just need to flash a stock rom, or do I need to flash a kernel as well?
Click to expand...
Click to collapse
To return exactly how you bought it, you need to first flash the stock ics kernel through cwm. Then flash an Odin tar file through Odin (desktop) which will restore stock rom as well as stock recovery. Unfortunately, I've looked around but could not find an Odin tar file for Koodo stock. Maybe you'll have better luck but in any case that is the process.
You seem competent and willing to learn, which doesn't happen as often as you would think. Let me know if I can help further. Good luck.
yoft1,
Many thanks again for your help. I am extremely green to this type of stuff so I feel like I've been thrown into the deep end here.
I've been looking around for the tar file and can't seem to find one either. But with the amount of people on here, there is probably someone who could upload it right? Would there be a thread or better forum for me to make a request? Or is that poor etiquette on this site?
I've just seen so many different roms, kernels, updates, etc...and I'm thinking somebody might be able to get it on here.
Ok you also said the first thing to do is to flash the kernel. Am I just lookng for any stock ics kernel? I just know I've looked through so many website and threads with different kernels, I just want to make sure I flash the correct one. Like is there a specific one per carrier, or model, or brand?
Again thanks for the help.
I would probably start a thread in the general section to see if someone can compile/upload an Odin flashable tar from Koodo stock. If that doesn't work or if no one responds after a bit, I would PM Mr X (a user on these forums). He is a dev that has uploaded stock roms for Telus and tmobile and he's also a really nice guy. He would probably know where to get one.
As for the kernel, I'm not sure if it matters but I would say with 80% certainty that there is no difference between the stock tmobile kernel and the stock Koodo kernel. On top of that, I would say with 99% certainty that it doesn't matter either way because I highly doubt they would look that closely (if there's anything to find at all) if you send it in for warranty purposes (but no promises of course) . If you get your hands on that tar file for Odin, I'm almost positive that the stock tmobile/Telus ics kernel will do it for ya.
Here is one of MrX's threads so you can PM him if the general forum doesn't work out:
http://forum.xda-developers.com/showthread.php?t=1356739
Hello and good afternoon,
I received this Xperia Arc (LT15a) from my dad to fix and I can't get it worked out so here it is
When you unlock the phone the screen responds to touch, I can swipe back and forth as one would expect. If you keep your finger on the screen or touch it atleast every second the screen stays responsive. If however you stop using the screen, sometimes for 10 seconds most the time just 1 second and the screen will no longer respond. In order to get the screen to respond you have to lock the device and unlock it again, as if refreshing it or restarting the touch screen service in the phone is the fix... temporarily.
I saw a thread somewhat like this and the fix was to downgrade to make sure no bad firmware had been put on so I downgraded to the 4.0.2.A.0.42 that the phone shipped with. This didn't solve the issue. I tried all sorts of firmwares thinking perhaps one would work. My dad tells me that this started happening when he updated the phone to 4.0.4 through the Sony upgrade software.
Has anyone run into this or do you guys believe this is more likely to be a hardware problem (which seems strange because I would think the screen should either work or not)
Thank in advance.
Hi @Laydas,
This is a weird one, for sure.
I've seen something similar on my phone, and for me the problem was definitely linked to an "upgrade / downgrade" kind of thing.
My solution was to install another rom.
So now I guess your bootloader is locked (because the phone is not rooted).
So the best thing to do is to try flashing a stock rom using "flashtool".
Here's some pointers to help you on your way...
Try this thread - http://forum.xda-developers.com/showthread.php?t=1304634
you're looking for info on flashtool, and on stock roms (I think that some stock roms are available in post 2 of the thread)
On top of that, there is an older thread (so a bit outdated) here - http://forum.xda-developers.com/showthread.php?t=1133650
It has good background reading thread to get a grip on all the ideas involved.
Good luck
I forgot to mention that I had already rooted the phone
I have used flashtool to restore the stock rom which didn't solve the issue either.
I have now taken the phone apart to check for loose connections, everything looked good.
I put the phone back together, tried it out, I still have the same screen issue.
Laydas said:
I forgot to mention that I had already rooted the phone
I have used flashtool to restore the stock rom which didn't solve the issue either.
I have now taken the phone apart to check for loose connections, everything looked good.
I put the phone back together, tried it out, I still have the same screen issue.
Click to expand...
Click to collapse
OK, wow. This problem is really sticking around.
So my next question is: - Do you have an unlocked bootloader?
If yes, then try flashing a custom kernel and a custom rom.
My favourite ICS based rom is JJ's Hybrid - http://forum.xda-developers.com/showthread.php?t=1537717&highlight=jj+hybrid
It works 100% with the ArcKnight kernel.
If your bootloader is locked, then you cannot flash a custom kernel. You can still try try the JJ Hybrid rom to see if it sorts out the problem.
At this point I'm running out of ideas. For me this issue was software related, so flashing a different kernel and rom fixed my problem.
It seems like your issue is software related too (because it popped up after an upgrade), but if you flash a rom and a kernel, then there's not much else that you can try flashing,,,
OK, maybe there's also a base-band you can try flashing - There's a base-band thread here - http://forum.xda-developers.com/showthread.php?t=1688049
So try a custom rom and a custom kernel, and if that fails try updating your baseband to 72 or 77.
That's all I can think of to completely overhaul your phone's software.
Please let me know how it goes...
Take care,
Hotfingers
The bootloader is locked on this phone unfortunately.
This phone is not like my other phones, even trying to get a custom rom onto it is a hassle as installs from zips in CWM almost always fail.
Pushing roms from flashtool works but I couldn't find the JJ hybrid rom in a ftf format for flashtool.
At this point I will continue trying to get a custom rom onto this phone when I have time but it has dropped off my priority list as it is being so difficult haha.
Thanks for the help, hopefully sometime next week I will be able to go through some of these steps and get back to this post on what helped
Laydas said:
The bootloader is locked on this phone unfortunately.
This phone is not like my other phones, even trying to get a custom rom onto it is a hassle as installs from zips in CWM almost always fail.
Pushing roms from flashtool works but I couldn't find the JJ hybrid rom in a ftf format for flashtool.
At this point I will continue trying to get a custom rom onto this phone when I have time but it has dropped off my priority list as it is being so difficult haha.
Thanks for the help, hopefully sometime next week I will be able to go through some of these steps and get back to this post on what helped
Click to expand...
Click to collapse
OK, thanks for the feedback. This isdefinitely weird...