• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Whats next?

O

Onagoth

Newbie
So...I've rooted, flash a decent rom (Leedroid), fixed so that I am running A2SD, changed the boot animation, and overall added some additional apps that are of use.

I still don't know much about custom kernals or radios, or making my own stuff.

What do you think I should move onto....I'm starting to feel like my phone is just a phone again :)
 
Start reading up on kernels, how they work, etc. I'm no GSM guy, but I think you pretty much want to leave the radio alone(Anyone want to confirm/deny?). I'm going to try to get started on some ROM development (I have some coding background), and I've been using this site for guidance Initializing a Build Environment | Android Open Source check it out, see if it's something you can do.
 
Just flash the latest radio. Don't try modify it. Find a good kernel just male sure you use the sense version :) you will get better battery life with a good kernel. Also you could play around with the UOT Theme kitchen. Have a look at thee link in my sign there's a tutorial video I made for it.
 
Oh, it's not hard to flash, though with someone who's not done it before I prefer to warn of the pitfalls. So:

* Radio flashes are straightforward, but a bad one can wreck your device irrecoverably. So always check it has downloaded correctly (check md5), don't try flashing with a low battery, and make sure the radio is compatible with your phone (i.e. don't get GSM and CDMA mixed up!).

* The flash itself is quick, but the install will happen when you reboot afterwards. The phone will reboot itself a couple of times in the process. Don't assume you are in a bootloop and pull the battery - it's vital that a radio install is not interrupted.

* If you've changed your internal memory partitioning (mtd) to one with a small cache, you won't be able to flash a radio from recovery, but should use fastboot instead.

* Don't even think about using ROM Manager to flash a radio!

* If there is anything you don't understand, make sure you do understand it before proceding.

I think that should cover it.
 
Just to reitterate what hadron said about the small cache, this is a BIG deal. Flashing a radio.zip file, unpacks the radio.img into cache. From 11MB to 25MB. If there isn't enough space, the file will corrupt but it may still flash and brick your phone. Extract the radio.img to PC and fastboot flash it.
 
To dumb things down a little....whats the difference between fast boot flashing and recovery flashing?

Everything I've flashed so far has been from recovery.

Also, will a different radio improve reception? Because right now, my reception is very spotty.
 
recovery flashing uses zip and an updater-script to flash. its an automated process once you select the file. the requirement is a cache size of 25mb. anything lower and it can result in a perm brick. its also deemed as "less safe" for radio flashing as its an addition layer that can go wrong however it is the only way with s-on.

Fastboot flashing uses fastboot (as you would guess) and doesnt use cache to temp store the files while extracting. instead it uses your computer to directly write the img to the radio partition. this removes a software layer from the equation as its direct command line.

Android flasher is all well and good but personally i find typing fastboot flash radio radio.img a lot quicker than opening a program and using point and click
 
I use it for flashing splash simply as it coverts the image for you. Other wise command line for me too
 
You must log in or register to reply here.
Back
Top Bottom