i want to change the kernel of the original ROM ,but after i changed the kernel,then cannot open the wifi ,why??
I'm afraid you're going to have to be a bit more specific and clear to get a helpful answer.
Sent from my DROIDX using XDA App
Try wiping data and cache from the recovery. It might help!
If it doesn't work, try posting more details, like which device are you using, which kernel you have installed or which recovery you used to install it.
Which phone?
Which rom?
Which version of android is it on?
Sent From Space Using My ICS Flavored Sensation
How did you manage to change the kernel on the Droid X?
Sent from my DROID X using XDA App
Oops thought I was in DX forums, sorry!
Sent from my Nexus S using XDA App
Related
What should I do
Sent from my Desire HD using XDA App
jaymccoubrey said:
What should I do
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Might help if you said what you did...
jaymccoubrey said:
What should I do
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
If you are using the phone in your sig that might be a clue.
Sent from my B.A.M.F. Thunderbolt
gadget! said:
If you are using the phone in your sign that might be a clue.
Sent from my B.A.M.F. Thunderbolt
Click to expand...
Click to collapse
That made me lol.
Sent from my ADR6400L using XDA App
Nope its a freinds phone
Sent from my Desire HD using XDA App
It says if can't find the log files
Sent from my Desire HD using XDA App
jaymccoubrey said:
It says if can't find the log files
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
The original question still remains. What did you do to the phone? Did you root it? Flash a new ROM? Did nothing and it is just going crazy?
Sent from my ADR6400L using XDA Premium App
If you flashed a custom ROM, I would do 2 things.
First, check if the poster of the ROM has the md5 check sum posted. If so, check it with your download to make sure it is complete and not corrupt.
Second, try installing it again without wiping or clearing anything. Just re-flash it over what you have now.
Also, if you are flashing a custom ROM and other mods, flash the ROM first and let it completely boot and go through the set up before installing any of the mods.
Sent from my B.A.M.F. Thunderbolt
When I go into recovery it still shuts off and restarts I put the leaked ROM and radio on in hboot. Its still doing it
Sent from my Desire HD using XDA App
I put cm7 on it and it was fine. I put the google apps on. And that when it started. I used that file before and it worked fine.
Sent from my Desire HD using XDA App
Restored stock. Thanks for trying.
Sent from my Desire HD using XDA App
If you try again make sure you clear out your caches before you flash CM7 and then when you get in make a backup. then after that flash the Google apps using rom manager. it should be listed in your apps after a fresh CM7 install. plus then if that screws up again restore the backup you had just made and try again
I got s on IM returning it. its still boot looping. I did use clockwork. I should have done it manually. Like always.... New tbolt tomorrow. Root and try again.
Sent from my Desire HD using XDA App
If I could have gotting in recorery life would have been grand. I got 4 differnt Roms backed up, fully set up and ready to go. I had so much time into setting each on up. guess thats how the cookie crumbles
Sent from my Desire HD using XDA App
I would still like to no caused it tho. IM still learning bout my learning curb is steeper then most.
Sent from my Desire HD using XDA App
Does anyone know why the android market is now telling me that 2 out of 3 apps "are not compatible with my device"? Can it be rom related. I'm using VU 2.35 but I wouldn't think that'd have anything to do with it. My apologies this is the wrong section. I posted it originally in general "Q & A's" & was told it needed to be posted here...
Sent from my Inspire 4G using xda premium
Have you tried clearing your market cache and/or data?
Sent from my Inspire 4G using xda premium
cwhitney24 said:
Have you tried clearing your market cache and/or data?
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I have tried that, still have the same problem as the creator of this thread...
Do you have your LCD density set to something other than 240? I have heard that this causes the exact issue on the market.
When I try to open cyanogenmod settings or the browser it just forces close. I'm running on nscollab 1.0.60 with Trinity kernel!
Sent from my Nexus S using xda premium
Try installing setcpu and seeing if that fixes it.
Just install it no need to open it.
Sent from my SPH-P100 using Tapatalk
Have you tried a fresh install? Always works ;-)
Sent from my Nexus S using XDA App
What do you mean by a fresh install?
Sent from my Nexus S using xda premium
A fresh install means wiping the dalvik cache and factory resetting the phone in recovery mode before flashing the rom. Best use titanium back up if you want to keep your apps
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.
heavy_metal_man said:
A fresh install means wiping the dalvik cache and factory resetting the phone in recovery mode before flashing the rom. Best use titanium back up if you want to keep your apps
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.
Click to expand...
Click to collapse
Like he said. Just go into recovery. And do all that and flash CM again.
Sent from my Nexus S using XDA App
devgee said:
What do you mean by a fresh install?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Have you tried installing setcpu yet?
Sent from my Nexus S 4G using Tapatalk
I Tried IT. still forces close!!
Sent from my Nexus S using xda premium
are you just did a theming to your phone??
usually causes by mod of theme...
fastest way is fresh install new rom
al_madd said:
are you just did a theming to your phone??
usually causes by mod of theme...
fastest way is fresh install new rom
Click to expand...
Click to collapse
Do you remember doing anything to your phone before the fcs started?
Sent from my Nexus S 4G using Tapatalk
If it always has been like this, you've most likely corrupted the ROM file during download.
Download it again and install it after doing a factory reset & caches wipe.
Greetz
Thanx bro it worked!!!!
Sent from my Nexus S using xda premium
Hi
I have made some modifications to an MTD ROM posted in dev section.
I would like to test it on an emulator before I flash it to my actual device.
I installed Eclipse (with ADT plugin) and downloaded some Google APIs (2.1,2.2,2.3.3) but I haven't seen our device in the list...
So I just launched a virtual device based on 2.3.3 but I don't think it is heping me much, it's just a general 2.3.3 android device.
My questions are : (and I did read quite a lot, maybe haven't looked in the right places)
1. what target do I need to download and add to AVD to emulate SGH-T959V ?
2. How do I get it to function with recovery ? and actually flash kernel etc.
3. Do I need specific actions to emulate MTD over our phone ? same as in real phone ?
4. Will I be able to virtually flash a ROM on an emulator ?
links to constructive/informative sources are also appreciated.
Thanks a lot !
itzik2sh.
I'll rephrase, how do you guys test your ROMs prior to flashing them, or you don't...
Sent from my SGH-T959V using xda premium
*bump*
I'm interested in the answer as well.
Sent from my SGH-T959V using xda premium
itzik2sh said:
I'll rephrase, how do you guys test your ROMs prior to flashing them, or you don't...
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Mayb on some unbrickable moded phones :-"
Sent from my SGH-T959V using xda premium
I have been trying to do that for a while. What I've discovered is that you can build emulater version from source, or use a nandroid backup.
Sent from my SGH-T959V using xda premium
I was messing around with this last night, but couldn't get a nandroid backup image to load properly in the android emulator. I was following these threads:
http://forum.xda-developers.com/showthread.php?t=1591924
http://forum.xda-developers.com/showthread.php?t=906161
I'll get back to you if I find anything else that works.
I couldn't get it tot work either, but I thought it was just me.
Sent from my SGH-T959V using xda premium
itzik2sh said:
I'll rephrase, how do you guys test your ROMs prior to flashing them, or you don't...
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I test by flashing..and logcat the fooker...and fix my errors that way of course an emulator would be a lot better
sent from my batcave
So I've been trying to find why ROM manager should not be used with this device and I just see that I shouldn't. I came from a MyTouch 4G where that or 4EXT were standard.
What symptoms does ROM manager cause?
I've noticed that any ROM I try to flash that doesn't use aroma installer fails at checking the update package. Is this one and how do I avoid it?
Sent from my SGH-T959V using XDA Premium HD app
Rom manager does not support our device so any recovery you flash is going to result in a bricked phone. It's just that simple. Even after installing the correct custom recovery, stay away from it because you won't find any compatible roms either. Not to mention that in order to flash a rom with rom mangler you first have to flash a recovery so it knows which roms to look for.
Sent from my SGH-T959V using xda premium
I have ROM manager on my phone already. Hasn't seemed to brick it yet. I just can't flash ROMs through it unless they are packaged with aroma. But wiping works fine.
Sent from my SGH-T959V using XDA Premium HD app
Chomanator said:
I have ROM manager on my phone already. Hasn't seemed to brick it yet. I just can't flash ROMs through it unless they are packaged with aroma. But wiping works fine.
Sent from my SGH-T959V using XDA Premium HD app
Click to expand...
Click to collapse
How are you using it at all? Doesn't it prompt you to install a recovery?
Sent from my SGH-T959V using xda premium
He will learn.....soon to be a statistic,wanting to know how to unbrick his phone.
I'm more than prepared to fix a brick.
It flashes through the market app fine using the i9000(?) option. I can then reboot into recovery fine and flash/wipe/mount just fine. Though the model mismatch might also be causing the issue where I can't flash anything not packaged with aroma.
Sent from my SGH-T959V using XDA Premium HD app
Chomanator said:
I'm more than prepared to fix a brick.
It flashes through the market app fine using the i9000(?) option. I can then reboot into recovery fine and flash/wipe/mount just fine. Though the model mismatch might also be causing the issue where I can't flash anything not packaged with aroma.
Sent from my SGH-T959V using XDA Premium HD app
Click to expand...
Click to collapse
Your lucky flashing that recovery should have soft bricked your phone. This is not the i9000. That's the galaxy s international version of the phone. Then there's the t959 vibrant. And the t959w for wind Mobile. Which are all slightly different. Like i said really lucky. Sooner or later it's likely to burn you.
Sent from my SGH-T959V using xda premium
I know this isn't the I9000. Perhaps I should consider dusting off my coding knowledge and make a compatible recovery.
This phone is so much different than my old HTC glacier... -_-
Sent from my SGH-T959V using XDA Premium HD app
Chomanator said:
I know this isn't the I9000. Perhaps I should consider dusting off my coding knowledge and make a compatible recovery.
This phone is so much different than my old HTC glacier... -_-
Sent from my SGH-T959V using XDA Premium HD app
Click to expand...
Click to collapse
We have cwm recoveries for the phone they just don't flash thru Rom Manager.
Sent from my SGH-T959V using xda premium
Given that CyanogenMod is dumping ROM Manager, it seems like energy could be better put elsewhere.
One reference (past the code itself) -- http://en.wikinoticia.com/Technolog...od-rom-manager-abandons-its-own-update-system