Database Info

HELP! Tried to root/overclock phone broke phone

Hi Guys,
I checked around but I couldn't find anything. I rooted my phone using the 1 click method provided here http://forum.xda-developers.com/showthread.php?t=1096384 This part went swimmingly. I had my phone rooted and ready to go. I then downloaded CPU set and the program would not let me speed up the CPU past 1 Ghz. so then I downloaded this: kernal netarchy-nexus-1.3.0.2-bfs-2.3.3-cm7-compat-signed which supposedly allowed me to overclock my phone. I then placed the zip file into the root directory of my phone. I downloaded ROM manager and used that to install netarchy-nexus-1.3.0.2-bfs-2.3.3-cm7-compat-signed. When I did this the screen went black and the capacitive buttons at the bottom lit up. I can reach the recovery screen but that is it. There is no USB connectivity with the computer. Is there anyway to fix this or did I just turn my phone into a paper weight.
Thanks,
Cloo

Phone processors are a funny thing. Some can handle being overclocked higher than others. I am assuming that you went all the way up to 1400 and your CPU just gets too hot and everything locks up on you. You need to have a rooted Rom on the root of your sdcard and wipe everything from recovery and flash the Rom from recovery and start over. If you go with Netarchy's kernel again I suggest bumping the CPU up to 1200. If it can handle that bump it up to 1300 and obviously it can't handle 1400. You won't see much of a benefit from 1000-1300 for the most part. I keep mine on 1200 and it runs great. Anything higher for me and the phone starts to get hot and lag somewhat. Your phone is not a brick. If you can get to recover and/or bootloader there is always hope.
Also check out these threads to help you get back to 100% stock and start over.
http://forum.xda-developers.com/showthread.php?t=1072698
http://forum.xda-developers.com/showthread.php?t=1103727

Do you have a NS4G which is what the one- click is developed for or a Nexus S, which is what the Kernel you flashed is for? My guess is that you flashed a kernel which is not compatible with your rom.
Sent from my VEGAn-TAB using Tapatalk

You may not have waited long enough for the phone to boot. His bfs based kernels have a bug that most of the time the phone boots to a black screen captive light shows and no boot animation. It will boot but just takes time of you have right kernel. This is spoken about in his thread.

@housry I never got all the way through the switch to netarchy. Once I used ROM manager the screen blacked out upon reboot and nothing happens now. I managed to get the file SamsungSimpleDL onto my phone but when I try to install it aborts. Any thoughts?
@debh I have the NS4G
@Jerry the phone has been sitting with a black screen for about 10 minutes so I think I screwed something up

According to your op, you flashed a 2.3.3 cm7 kernel. Are you running stock 2.3.4? You need to flash the correct kernel for your rom.
Also, I just read your post above and you aren't supposed to flash the simple.zip on your phone. Download and extract the contents onto your computer and run the .exe from there with your phone connected.
Sent from my VEGAn-TAB using Tapatalk

Deb thanks for the quick reply, am I supposed to have my phone in download mode?

Phone is fixed!!! Thanks to all!

Quick question, im sorry, as I didn't know where to ask. Even checked threads and couldn't find an already posted answer. I have a ns4g, rooted, still on stock rom. Will I still get ota's from google when they push newer software than 2.3.4, which is what I run, and also get ota software bug fixes from goolge when they release it? I really hope so, as I want to stay current with the latest builds from google.
Sent from my Nexus S 4G using XDA App

sh4nk said:
Quick question, im sorry, as I didn't know where to ask. Even checked threads and couldn't find an already posted answer. I have a ns4g, rooted, still on stock rom. Will I still get ota's from google when they push newer software than 2.3.4, which is what I run, and also get ota software bug fixes from goolge when they release it? I really hope so, as I want to stay current with the latest builds from google.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
It will be faster to find them on XDA than the wait for OTA

Thank you Plus waiting a little bit will skip any bugs to be fixed lol
Sent from my Nexus S 4G using XDA App

Issues with installing certain ROMS [SUCCESS!!!]

Some of the user's here, myself included, have been having issues installing any ROMs/ kernels built by Faux. What I'm trying to do is pinpoint the exact cause of this and hopefully rectify the issue.
I'm currently downloading all available ROMs and will install each to determine which are flashable and which are not.
Flashing Procedures
0. Boot into CMW Recovery: External with EXT 4 support using volume down + power method
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Format /System
5. Flash ROM
6. Select Power Down from CMW Menu
7. Power on phone without wall charger plugged in
ROM List:
Bionix- Confirmed as working
EagleBlood GB- Confirmed as working
EagleBlood FR- Confirmed as working
Ultimate- Confirmed as working
Light&Sinister- Confirmed as working
Dark&Sinister- Confirmed as working
Faux AOSP-NOW WORKING!!
CM7- Confirmed as working
LG Stock- Confirmed as working
Observations:
Bionix converts /system and /data to ext3. I figured that if the issue we were having with Faux was due to format errors then I could just flash Faux over Bionix and it would boot. In testing, it seems like Faux gets further when flashed this way but still refuses to boot. Before I would only get the initial LG screen and then it would black out. Now I can get to the second LG screen with blue background but it hangs there. Will run logcat to see what is causing the freeze once I get logcat running again.
My current theory is that there is a difference in the boot.img that Faux has built for his ROM that will not boot correctly. I have the same issue with his kernels as well. They boot to the first LG splash screen and then the screen shuts off. Still struggling with my logcat issue so I'm at a standstill until that is fixed.
Development:
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Morfic's CM7 kernel. I personally believe this definitely proves that there is something in Faux's boot.img that doesn't function properly on all devices.
At Faux's suggestion, I flashed his Stock Voltage kernels in order to see if I could get the phone to boot.
Kernel:
[ Start @ 1.0 GHz, Stock Voltage, Max @ 1.2 GHz ]
(Official LGE/Tegra Voltage Values, Same as STOCK LGE Kernel)
CM7 Kernel Version 0.1.9- Boots to second LG splash screen then freezes.
CM7 Kernel Version 0.1.9 With EXT4-Booted fine but still displayed Morfic boot animation for some reason. Kernel version shows as Faux's in about phone, though.

I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?

Mikeglongo said:
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Click to expand...
Click to collapse
I didn't test any of the ROMs for quality but I would personally stick with a Froyo based ROM for now. Gingerbread is simply too buggy and missing a lot of features.

[B][U]SUCCESS!!![/U][/B]
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Trinity's CM7 kernel. I personally believe this definitely prooves that there is something in Faux's boot.img that doesn't function properly on all devices. That would explain why I am unable to flash any of his kernels, either.

Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.

faux123 said:
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
Click to expand...
Click to collapse
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.

hiko36 said:
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
Click to expand...
Click to collapse
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.

faux123 said:
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
Click to expand...
Click to collapse
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.

hiko36 said:
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
Click to expand...
Click to collapse
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.

faux123 said:
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
Click to expand...
Click to collapse
Glad I could help and especially glad I finally figured out a way to boot your ROM. I was feeling left out haha.

Doh! He said rectify lol
Sent from my Xoom using XDA Premium App

[Q] Diagnosing Random Crashes/Freezes

Hello android gurus/deities (too much?),
Just got my first smartphone, a Droid Charge. Great phone, especially for the price. The screen is freaking fantastic and of course Android is amazing as ever.
However, since first activating it, I seem to get random crashes. I can't replicate the problem, since it doesn't seem connected to anything visual. First time it happened when I decided to check out the camera, took a picture, and tried to view it. Other times have been the first time trying out netflix, first time sending a text. Seems to happen the first time I use some apps.
The crash basically consists of a short 5-10 second freeze followed by a reboot. Any ideas? Is this a hardware issue I need to have addressed or more likely a software issue that I just need to wait for updates to come along and fix it? Or is this a common occurence with Android and I just need to suck it up? lol
Edit: Has also happened 3 or 4 times while browsing the web, including this site...

charges hardware are pretty great for the price the software is a big issue for the charge whitch is why most of us myself included suggest rooting your device whitch literally a dummy could do using odin... i am running a stock based of a leak called infinity rom pretty amazing for a stockish rom for now so reboots are known at least for me but i really think the majority of the problem for this phone is the software gps loss signal going in and out as in data (this is a hit and miss) ..... hope this helped you iron things out...

Out of curiosity, what will rooting my device accomplish with respect to the reboots? Anything?
I rooted the device, then tried infinityROM but ran into so many problems I flashed back to the factory rom X(... Rooted again, but still get reboots, any ideas?

Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\

RevTorA said:
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
Click to expand...
Click to collapse
http://rootzwiki.com/topic/4847-guide-new-users-guide-everything-how-to-root-rom-kernels-radios-cwm/
Also depends what rom you are running.

If it keeps happening after you root and flash a new kernel (and maybe install a rom) upload a logcat to a filesharing place and hop on IRC to ask for help.
irc.andirc.net
#charge
Port 6666
Sent from my SCH-I510 using xda premium

Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?

RevTorA said:
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
Click to expand...
Click to collapse
PBJ is a Froyo kernel. It will only work with Froyo.

[Q] Overclock Reboot Cycle

Hello! Long time lurker, first time poster. I finally got around to making an account.
So, I'm having an issue when applying Da_G's overclocking kernels (Here).
The issue proliferates when I go into CWM and apply the AT&T .42 kernel and the 1.83ghz overclock script from the recovery menu. Basically, after cleaning the cache and the dalvik cache, I apply the .zips of the .42 kernel and the script, and reboot, and then I get a restart cycle that ends after the Samsung screen. I went ahead and did a full wipe of the phone, restored via ODIN to stock, and then tried flashing it again and this time I got to an "Android" logo followed by the same power cycling (this time with the camera LED flashing).
The strangest thing is that before I took my first Skyrocket back for dead pixels, I had gotten it running just fine before. But the last two I've had won't do it and get stuck in the aforementioned restart cycle.
I decided that it really wasn't worth the risk of bricking my phone (since I just got out of my 30 day warranty and had to take the phone back twice for dead pixels and the phone not turning on one day), and I guess in the end I'm just curious as to why I was having this issue. I guess if it's something stupid I'm doing, I'd go ahead and do it (especially since I have plans for that performance boost).
Anyways. Feedback appreciated.

The 1.83 isn't very stable that's what's causing the problems. Go one step down on the script

Alright, I'll try it right now. Maybe it was a fluke that it worked the first time.
EDIT: It booted up, but, then it shuts off when I open CPUTuner, but, they're talking about that in the official thread. Thanks!

1.83 is not stable and 1.78 and 1.72 are most stable with oc.
Sent from my SAMSUNG-SGH-I727 using xda premium

After running it for a few hours, now I'm getting Sleep of Deaths. I really want to speculate that it's the .42 version that I'm running, but, I haven't tinkering with it enough. I think I'll try downgrading to .3 to see if that fixes the issues, as that's what people seem to be saying is the most stable, and it's the one I ran before.
And if that doesn't work, eh, I'll flash back to stock kernel. Thanks guys.
Edit: Yeah, still getting SOD, flashing stock.

Did you try deleting your modules folder?

I had the same problem, 'cept I cranked it to 1.89ghz. I just flashed the stock att kernel and everything worked fine
Sent from my SAMSUNG-SGH-I727 using xda premium

[Q] I think I need to downgrade my baseband...can someone please confirm?

G2X LG P999
CM7.2 Nightly 2012-12-02
Faux123-054
BB Mar 11 2012
CWM v5.0.2.0
As a result of trolling this site for a while, I have tried a few different ROMs and a couple of different kernels. All is good with this present combo except for an overheating issue while charging that I'm pretty sure is fixed (checked "Stay awake" in Settings/Applications/Development). I tried Hellfire Phoenix v2.3 last and dug it. I came back to CM7 because I recently had the need for bluetooth (headset) in my car and with my PC. I thought the problem was with the ROM, but after having the same bluetooth issue with CM7, I dug around here and found out that the problem is the baseband.
Am I right in that assessment?
If I am right and the only way to get bluetooth working on a custom ROM is to downgrade the baseband, is this what I need to do?: http://forum.xda-developers.com/showthread.php?t=1048274
Do I really need to go back to stock? Can't I just use CWM to flash a baseband that will work?
TIA,
Nasty

Yes, currently Bluetooth headset only works on the stock gingerbread roms with the new baseband.

Additional question
TwitchyEye said:
Yes, currently Bluetooth headset only works on the stock gingerbread roms with the new baseband.
Click to expand...
Click to collapse
Thanks...bummer. I guess I'll have to live without...not going back to stock.
I reloaded Hellfire Phoenix 2.4.2 and put the OC mod version of Mazout360's CM7/9/10 Kernel. I like it the most. But, it's a battery burner...which isn't that big of a deal most of the time. But if I have to do some traveling and need the extra battery life, I may need to flash the stock voltage version.
Question:
Can I flash the kernel without wiping everything out the ROM and having to go through the whole setup from the ROM's startup (reload apps, adjust settings/drawers/ringtones, enter mail accounts etc)?
Or would it be better to get an app like Setcpu and figure out how to downclock and lower voltage when I need the extra battery life.

Just boot into recovery and flash the kernel, don't need to wipe anything.
Assuming you're talking about mazouts non oc one.
Sent from my LG-P999 using xda app-developers app

You would still need to wipe cache and dalvik... can't flash a kernel without that typically.
Sent from my LG-P999 using xda app-developers app