Related
Immediately after rooting my phone my wireless was permanently disabled. When trying to re-enable, the gui displayed "error" and nothing else.
I'm not new to linux and have successfully gotten adb and fastboot working under gentoo.
I have all the apks I need to root, but I erased my boot and recovery images when I tried to install the cyanogen mod. The cyanogen mod loops at the mytouch animated logo when I flash it to boot.
I have three simple questions:
First, has anyone successfully resolved the wifi "error" message? When I looked (yesterday) there were tons of confirmations about the problem, but not a single fix I could find.
Second, has anyone gotten cyanogen or clockworkrecovery working on the mt4g? It was very frustrating trying to get out-of-band access to the android market. It makes no sense to me whatsoever that access to free software should be controlled in any way by google. Have they been deliberately uncooperative in letting apks be downloaded to pcs?
Third, would anyone be willing to mail me copies of their boot.img or recovery.img? As I was unable to get clockwork recovery, I didn't backup my roms before trying to flash an attempted fix.
Help would be greatly appreciated.
Google hosts the market and the Market app itself is not open source, which if why they can and do prevent distribution of it. There's no restrictions of people distributing apks (license notwithstanding) through other means.
I think there's an alternate method to installing clockworkmod via fastboot. I reinstalled stock recovery this way, though I don't think that helps you without a signed system image.
There's also an ruu available but I don't think I've heard of anyone trying to user it yet.
Sent from my HTC Glacier using XDA App
poseidon1157 said:
Immediately after rooting my phone my wireless was permanently disabled. When trying to re-enable, the gui displayed "error" and nothing else.
I'm not new to linux and have successfully gotten adb and fastboot working under gentoo.
I have all the apks I need to root, but I erased my boot and recovery images when I tried to install the cyanogen mod. The cyanogen mod loops at the mytouch animated logo when I flash it to boot.
I have three simple questions:
First, has anyone successfully resolved the wifi "error" message? When I looked (yesterday) there were tons of confirmations about the problem, but not a single fix I could find.
Second, has anyone gotten cyanogen or clockworkrecovery working on the mt4g? It was very frustrating trying to get out-of-band access to the android market. It makes no sense to me whatsoever that access to free software should be controlled in any way by google. Have they been deliberately uncooperative in letting apks be downloaded to pcs?
Third, would anyone be willing to mail me copies of their boot.img or recovery.img? As I was unable to get clockwork recovery, I didn't backup my roms before trying to flash an attempted fix.
Help would be greatly appreciated.
Click to expand...
Click to collapse
the reason it's not working is because, I'm assuming, you followed the guide about forcing your update. When you did this it patches the kernel, but does not update the bcm4329.ko kernel module. There are a bunch of guides on how to root in the dev section. It looks to me like you started following my guide. If you look at my guide (entitled forcing update 2.2.1 and rerooting) it will give you the steps to complete the process with all files linked.
There are a bunch of us in IRC who would be willing to help.
Please post questions in Q&A section.
Ok, I have looked everywhere, and haven't really found a solution for my issue. I wanted to get a lagfix put on my phone (T-mo Froyo), and couldn't get the 3E script to work right, causing no clockworkmod. I saw where someone had posted that you should put a kernel on there that already had the clockworkmod on it. I wound up flashing a zimage, that put Clockworkmod v2.5.1.0 lagfix edition. The only thing is, is that it won't boot all the way up. It's like it is confused. It starts with the gt-i9000 screen, goes to the t-mo boot up, and then black screens and vibrates occasionally. I am able to boot into the recovery screen, but don't can't get a rom onto the phone's sd. I can put one on the sd card, but can't get the phone to that point. I have downloaded and re-installed three sets of drivers, and I keep having a fail on them. Now, I got Windows 7 64 bit. I am going to give Xp 32 a try in a few minutes, because I know on some other things they can be finicky. I was going to put the bionix V on this phone, but right now I will be just happy to get it back to stock. I am sorry for being a dumbass. I believe that it is in the blood though I have been looking for about a full day on a reso. This link seemed promissing, but I wasn't too sure where to go after recovery? Thanks peeps..
http://forum.xda-developers.com/showthread.php?t=771247
yea...the kernels you need were the voodoo kernels that Supercurio posted in the DEV section. Sounds like you flashed the european version instead of a US vibrant version. And you flashed a zimage instead of a kernel. Get it into download mode and odin a kernel for your corresponding base from supercurio. You may need eugenes froyo that doesnt brick and then odin to stock JFD to get rid of the bootscreen first.
jmcghee1973 said:
yea...the kernels you need were the voodoo kernels that Supercurio posted in the DEV section. Sounds like you flashed the european version instead of a US vibrant version. And you flashed a zimage instead of a kernel. Get it into download mode and odin a kernel for your corresponding base from supercurio. You may need eugenes froyo that doesnt brick and then odin to stock JFD to get rid of the bootscreen first.
Click to expand...
Click to collapse
This, definitely.
I try to avoid ClockworkMod Recovery to be honest, I make fewer errors if there's an Odin option.
Thank you so much guys! I am rolling again, and all is well in my village! (Remember, I am the village idiot).
Thanks so much! You have no idea how relieved I am!
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Click to expand...
Click to collapse
Well that i a good start. Good to see some reading before the jump in feet first.
corruptsmurf said:
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
Click to expand...
Click to collapse
That's why we're here.
corruptsmurf said:
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
Click to expand...
Click to collapse
Edited: added Later
ADB is a commander center/protocol (if you will) that allows you to control your phone via a PC/Mac/Linux. You can push files which would be taking the file and "pushing" to the phone. Or "pulling" files from the phone and putting them on the computer. It's simply as it states, pushing and pulling the files.
To see what a Kernel is read This.
A ROM is the phones physical Operating system. Similar to what Window, Mac or Linux world be.
corruptsmurf said:
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Click to expand...
Click to collapse
Before you can flash Clockwork Mod you need to root your phone and turn s=off. For one of the methods, - before you can start you need to set up the ADB (Android Debug Bridge). See my signature for the quickest and most painless way to get that set up. You will also need VISIONary.apk. A quick Google Search will find it for you. Link
corruptsmurf said:
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
If you want a 2.3 based ROM you will need to flash Recovery image 3.0.0.6, link can be found in my signature, and hit up the development section to read reviews on different ROMs. I personally like the plain AOSP look so that leave Cyanogen(mod). But i know TeamRoyal has put together some newer ROMs that i haven't tampered with yet.
I do everything on my phone through CWM (clockworkmod) or terminal emulator, so there's no need for a PC, unless to download the files and transfer them to my SDcard, as I don't understand adb. Anyways, I'm gonna explain this very short and sweet cuz I was once in your shoes, and remember how much I had to read to understand something That could've been explained so simply.
Think of it this way. You're building the software version of a car. Now, if the whole car is the ROM, then the engine is what would be the kernel. And flashing would then be another word for installing , Now, a toyota with a ferrari engine, would be a custom ROM. While a toyota with a ferrari engine and BMW insignias all over it would then be a custom themed ROM.
**Remember, you can never install a car on something, but you can always install something in a car**
Ex. You can never flash a ROM on a kernel, but you can always flash a kernel on a ROM.
Anyways, first off, you will need CWM recovery to flash. Get it from the market. In the app itself, flash (this is the "flash" in the app) recovery 3.0.0.6. This will flash (this flash is not in the app) anything; any ROM, any kernel, etc. as long as its a FLASHABLE ZIP.
To boot into the recovery (the place you do flashing), hold both volume down and power buttons down as you either turn on or restart your phone. The screen you see is the bootloader. Choose recovery using the volume buttons, and use the power button to select it.
Going to flash a new ROM? Do a factory reset (in recovery), wipe cache (in recovery), and wipe delvik cache (this is in advance in recovery). Then install zip. Its pretty straight forward from there.
Going to flash an updated ROM, skip factory reset (as this deletes all data on your phone) and do the rest.
After you've flashed the ROM, you can now flash the kernel.
Note that, kernels are ROM specific. Read what kinds of ROM's the kernel is for before you flash it.
There, easy as pie, yeah? Hope that helped.
I recommend cyanogenmod 7 (Gingerbread based ROM) with faux's kernel (Gingerbread based kernel)
Sent from my HTC Glacier using XDA App
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
Neidlinger's got your back.
1. Glad you're reading before doing. What a welcome change of pace!
2. Flashing is the process of installing new software. We "flash" it to the phone's memory.
3. ADB is using a computer to control the phone via command-prompt from DOS. Push is a command which sends a file from your computer to your phone. Do a search, there are lots of good guides on ADB. TrueBlueDrew made one just recently that I highly recommend.
Here's Drew's thread. Don't forget to hit his thanks button! - http://forum.xda-developers.com/showthread.php?t=928370
4. Start with Clockwork Recovery and a nandroid backup. That's good practice. CWR2 is compatible with Froyo (2.2) ROMs. CWR3 is compatible with Gingerbread (2.3) ROMs. CWR 3.0.0.6 is compatible with BOTH. Very convenient.
5. I say start with CM7. It's extremely stable, even though it's still in development. A ROM is a complete OS replacement for the phone. ROMs contain kernels, which control the most basic hardware, such as processor. If you flash a custom kernel on your stock ROM, you can overclock it more. You can also flash custom kernels on top of custom ROMs for different battery life, clock speed, etc.
To be honest I don't even bother with custom kernels since this phone is so damn fast out of the box I really don't see the point.
QUICK TIPS FOR CM7 - On your first boot, let it sit for 5-10 mins before setting up. There are background processes running and interrupting can harm stability. BEFORE you sign into google for the first time, after it's finished sitting, reboot. This will clear out any wifi glitches and give you smooth sailing.
Have fun!
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Uchennadi said:
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This is pretty much spot on. The developers have included kernels that they feel make the OS preform at it's peak. and most of them will allow for overclocking. However on some of them you may need to use a program called "setCPU" to adjust the frequencies. Cyanogen(mod) will have this built into the ROM natively. However most of the veterans will not promote running your phone in an over clocked status 100% of the time. most of us leave the phone at 1Ghz or slower. There are physical reasons, ie the constant expansion and contract of the chip isn't good for the mother board.
If i were you i'd stick with the Stock Kernel and leave it running as it. That way the developer can adjust their ROM, if you use an 3rd party kernel they aren't familiar with the coding so it's not going to act correct.
I'm not putting down what the kernel coders do, they do an awesome job. but for a n3wb i'd leave well enough alone.
I have been using droid2bootstrap on my milestone2. I notice there is an option for 1st init 2nd boot or something like that. I have been holding out from trying tezet's cm9 because of the camera not working and now i saw a new post that someone has a cm9 rom with a working cam (sorry i forgot the dev's name i think its ondavol or something) i would like to try it out. I have read somewhere about safestrap. Is it safe to use on m2? Tia.
Safestrap is based over CWM, so it should be easy to port, but I'm not sure it's currently compatible with M2. You can try to install it, just keep in mind that you'll need to flash a sbf in case something goes wrong.
2nd init is a set of scripts that run on the OS startup, allowing devs to sideload some files, required to run custom ROMs. At least that's what I understood of it while I used it. I can be completely wrong about it. Be careful =P
Flashing a custom ROM is relatively harmless, just keep a nandroid of your original system and you should be OK. Safestrap just automatizes it, automatically flashing safe and unsafe ROMs on your device with a few clicks, safe being the custom ROM, where you can play as you want without harming the original system, and unsafe being the original system, where it's unsafe to tinker with it. Besides that, it's just CWM.
M3 XT860
DarkDroid 1.1 (Unsafe) + Hash's ICS Beta 1 (Safe)
Thanks you very much for the reply. I am happy with m currentt setup but i am really itching to try out ics. Like i said the lack off camera is put me off from trying just yet. The moment i read about this new rom with camera somewhat working, i just cant resist anymore.
I guess nandroid is the way to go then.
The developer is called rondoval
Just keep in mind, that it's not possible at the moment (afaik) to unlock your SIM card. So you can use Wifi only.
That's just a reason for me to wait for another build with fixed SIM unlock...
Camera works with normal photos only, so no panorama and no videos
Still a step
Hey people, I really need some assistance understanding the process of modding my phone. I did a root, rom, and kernel on a galaxy s2, but everything felt simpler back then. I've been looking at threads for hours and still have no idea where to start. I want my phone to perform (react) the best that it can while having the best battery life possible too. That being said, I still want it to be kind of a normal phone that I can install all the normal apps on. What's the best combination of installations to make that happen, and what order do I need to do it all in? I'm terrible at making decisions so I prefer if you narrow stuff down to "the best" selection in your mind. If need be, provide an alternate and explain why to choose one over the other please.
Update: I've rooted, installed twrp, arter97 kernel and supersu. Now I just need help finding/picking a good ROM right? Help please?
I'm currently using audax V12 rom and his own kernel.
I love this rom
Uh oh, something is wrong. I installed audax and I thought everthing was going smoothly until I started getting calls. I can't hear them and they can't hear me. Whats the most likely place that i ****ed up to make this happen. My phone mic must be working because I can say "OK Google" From a quick glance at search results, it appears the kernel is probably the cause.
Should I be using this Audax: https://forum.xda-developers.com/s6-edge-plus/development/rom-audax-plus-v1-0-t3219017
Or this Audax: https://forum.xda-developers.com/tmobile-galaxy-s6-edge-plus/development/rom-audax-plus-3-0-m-featured-g928t-t3363901
Will I need to wipe the phone again to fix this kernel issue? or can you just install a kernel over a kernel?
I did find this while searching, but it makes not a wink of sense:
"Anyway, you need a file manager to change sth in /system directory(Root explorer, es file explorer, etc etc). Please try to find mixer_paths.xml from your old rom. If you have got a stock or custom rom for S variant, this file is in /system/etc Copy it to your device and paste into /system/etc.. 'Overwrite', then change the permissions of 'mixer_paths.xml' as rw- r- r- Check it to be sure. Then reboot. And call someone to see if that fixes or not "
Click to expand...
Click to collapse
I also found this post that someone claimed fixes the no audio call issue, but I'm not sure I understand the instructions: https://forum.xda-developers.com/showpost.php?p=67957026&postcount=58
EDIT: The last link there fixed it, I missed the part about extracting a zip out of the zip, then installing that one.
Try RootJunkys extralite MM version, that is what i used for a stock, currently on CM13, if i go back to stock i plan to just keep it stock, no need to root these ones if you can't manage to AOSP it.