Related
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.
Hey all,
Earlier today i flash cm7 and the glitch 13.1 kernel, ive gotten to grips with all the changes now and now i am trying to overclock to 1.5 as is possible under glitch.
I got voltage control and after doing some reading decided to get the xtreme version.
The problems i am having now is the phone wont go past 1.3mhz... and if the screen is off too long the phone reboots its self... any ideas what i can do to overcome these?
Is glitch or cm7 holding me back at 1300? Or is it my handset...?
Cheers everyone
You have to experiment with the voltages(be careful!). If you can't get it runnig, well, then your devices' OC capabilities are limitated(1300Mhz is normal, some people even get up to 1800, others only 1100Mhz-there are big differences between every single device).
Hey dark_knight35,
Thanks for letting me know about device specific limitations, much like x86 overclocking in a way.
I will try and get my head round over and under volting and see if it will let me set a higher clock, but i am also going to try diffent kernels i think... know of any amazing or 'the best' oc'ing kernel(s)?
Cheers.
Also the phone randomly crashes and reboots... this is with or without voltage control oc'ed or stock, fault of the kernel or rom? Going to be trying differnt kernels anyway at some point...
mod2max said:
Also the phone randomly crashes and reboots... this is with or without voltage control oc'ed or stock, fault of the kernel or rom? Going to be trying differnt kernels anyway at some point...
Click to expand...
Click to collapse
Well, if phone crashes even without OC, you should do a clean reflash of ROM and kernel.
UPDATE
So this moning this I reflashed Glitch 13.1 as dark_knight35 said, and guess what? As of yet, it has not rebooted its self xD
I should have known something was amiss... because when I came from CF-Root with stock rom the Glitch kernel writing is all read with its own boot logo.
And in recovery at the top it now says "Glitch kernel - CWM-based Recovery v5.0.2.7" and full screen is red text instead of "CWM-based Recovery" with blue text.
So it's all good now and can OC to 1.7 if I wanted to.
Only thing I am missing if anyone know if the baseband as it currently says "Unknown" and you need the correct baseband or (modem) to do anything telecomms wise... so gunna head over to SamMobile in a min and try and hunt down the JV2 modem.
Does anyone know where I can get JV2 modem? Also how do you flash a modem in Odin? Just set it to PDA and start? ...wouldn't wanna do something wrong.
Cheers all.
ANOTHER UPDATE
Phone still reboots, but it's only when it's running off the battery because when it's charging it's fine.
I never had this problem yesterday morning before I learned how to flash etc etc so it's defo software/firmware related and not the handset's hardware.
I'm going to reflash CM7.1 then before even booting up I will reflash Glitch aswell.
If this doesn't stop it would I be right in saying that the modem (or lack of it) is making it crash when it sleeps or locks the screen?
Something about the modem causing unwanted behaviour I sorta of remember from one of TotallyDubedHD's videos but please no one hold me to that lol.
mod2max said:
ANOTHER UPDATE
Phone still reboots, but it's only when it's running off the battery because when it's charging it's fine.
I never had this problem yesterday morning before I learned how to flash etc etc so it's defo software/firmware related and not the handset's hardware.
I'm going to reflash CM7.1 then before even booting up I will reflash Glitch aswell.
If this doesn't stop it would I be right in saying that the modem (or lack of it) is making it crash when it sleeps or locks the screen?
Something about the modem causing unwanted behaviour I sorta of remember from one of TotallyDubedHD's videos but please no one hold me to that lol.
Click to expand...
Click to collapse
Dunno if the modem can cause reboots. If you want to flash one, look into silky's modem thread in dev section and choose one.
Gesendet von meinem GT-I9000 mit Tapatalk
Ok been running 4.04 for a sometime now. I got it as it first came out.
Some issues that u have noted outside of the bricking issue. **disclaimer I am running my own built version of this ROM deoxeded zipaligned bla bla bla plenty of tweaks etc and the ROM is faultless(not really it has its faults and I am about to list them) with exception of a few things that may or may not be kernel related. IT DID NOT flash the new .pit file. I have built the ROM as according to 4.03 builds and used Siyah kernel.
1. initial boot and dalvik cache build takes an extremely long time. Easily mistaken for bootloops and possibly another reason people prematurely ejected this ROM
2. Android is upgrading/updating splash does not exist. Further adds to the concern that phone has enternal bootloops...it doesn't it just doesn't warn you. It goes back to the gingerbread days where you wore a big question mark ? on your head "What is my device doing?"
3. Bluetooth enablement does not work. We go from 4.03 that had wifi issues much similar to fixed wifi and issues with bluetooth. Sux. Guess you cant win eh?
My guess is that this is specifically related to the kernel and framework. Ihave the framework decompiled now and I will be looking into maybe making some adjustments to allow for the bluetooth drivers in 4.03 kernels to interact with 4.04, rather than a whole new re-reslease of kernels just to combat this issue.
4. USB not detectable in Windows 7? Hmmm I am not sure what happened here? It worked flawlessly for 2 days and then all of a sudden not recognised? USB speeds were perfect when it did work, reflashing the ROM did not fix this? My guess is that this is also kernel<->framework related. Also to note here that within the siyah recovery you can mount USB no issues and transfere, so no eMMC corruptions before you freak out.
5. Vol down + power button for screen capture does not work? This again maybe because of the kernel used?
Can anyone give any reason for me not running the new pit and flashing stock kernel? Does the stock kernel require that there is a repartition or is this an assumption?
Additional notes: Further testing my eMMC with Gotbrickbug *MASSIVE thanks to chainfire for this support* personal thanks from me. Thanks Chainfire you're a legend! After testing it revealed oddly enough that my eMMC was inconclusive, so not that it helped me much, but I have flashed this firmware now several times and have not had any issues. Everything working smoothly and 100% except for the above mentioned.
I am tempted to flash the standard kernel now (again no repartition) and then do CFroot for the stock kernel image on this firmware to see if these issues are alleviated in 4.04?
Additional to this is that I have the 15 toggles mod by Jkay translated and compiled with exception of the last file on systemUI for 4.04. I would REALLY love to have this ROM running for everyone.
Any input suggestions warnings (besides the brick scare - I am not scared cause I doubt my phone will brick considering I have flashed it so many times now with the phone acting the same every single time)are welcomed. Please use your head when you respond and not your bricked phone, I would like intelligent answers and discussions. Preferrably not from n00bs or those that are only rehashing all that has spilled out across the petition thread already.
My understanding is that it is a repartition issue with bricking not a kernel or ROM issue its self. My understanding is that I can flash any kernel I like I can flash the stock one and I should be able to flash a rooted one after it to get back if I want?
Proceedure now:
Flash ROM
Flash kernel
Flash CFroot
Flash Modded recovery
Happy days?
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Again flashed this ROM no problems.
I also attempted to run 4.04 czech republic version of this ROM to which it did not boot or run. Just to let those know that were considering doing this. I had 3 apks from that 4.04 build that refused to deodex? Also the sizes of all apks in this version of 4.04 (which does not come with a supplied .pit file) are vastly different to those in the Euro 4.04 supplied with .pit?
Yet to download and try 4.04 Chinese version? I figured someone else has probably already done this....the chinese are fast lil buggers. They don't much around! haha. If anyone has feel free (and please I would like you to contribute) to comment in this thread on your findings?
James
PS: Just about to flash standard kernel on unpartitioned GS2 if all goes well I will implement CF-Root. Cheers
donalgodon said:
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Click to expand...
Click to collapse
Did you re-partition when you flashed stock kernel? I like the sounds of this. I have the 4.04 working nicely.....if i can achieve the above I will create a ROM and upload. Thank you for your valuable input
I may even test with the czec 4.04 kernel and see what happens there? Hmmm
Kernels are identicle sizes but not the same?
czec zimage: MD5 2A4AE1B758D934E2AD1791E318F94424
europe zimage: MD5 FCB26E67AE9E7F701793B6014E4AF7D2
see attached for additional size details? I am wondoering if czec might be better for no repartition was/is used in this 4.04 build?
James
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Jarmezrocks said:
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Click to expand...
Click to collapse
No fix for USB enablement? I have switched the customboot.sh for the MTP application. I however don't have MTP.apk in system? I may place this apk and then re-try to see if I might be able to get the thing to be recognised by my PC.
USB Mass storage is now working via the old method. I need to have the MTP client in system/app for this to work. No longer getting the USB device not recognised which is great.
Any kernel devs want to share with me how to embed the correct components in the kernel to allow for customboot.sh to work? I am certain then that USB mass storage will work when that script can be run and enabled at boot. I dare say that boot animations should work then also.
4.04 is starting to shape up nicely now
My Mojo has died... It acts like it wants to boot but never makes it - just leaving a blank screen. I feel like I have lost my bff. I was trying to install the REMIX OS, I guess it went left instead of right. IF anyone is willing to help me , I will even ship it out to ya if it will help. I am in Poplar Bluff, MO USA. I feel so sick when I think about how I killed my bff. Thanks Andy.... Pls reply.
Welcome to the club. Mine died on me too. The blue lights comes on but nothing but a black screen.
Have you guys tried looking up old threads with the same issue?
@kevinthefixer helped lots of folks with bricked (or seemingly dead) MOJOs.
Those posts are actually the reason why I don't wanna upgrade my MOJO with new ROMs. The only thing my stock rom doesn't do is play videos on Prime Videos. I can survive without that. And for some reasons, it magically mount my external HDD on boot with no extra app or stuff. I can't ask for more than that.
Hope you guys get some fix among those old threads. If not, try to contact Mad Catz if they can replace or something. I know rooting doesn't void the warranty. But I don't know if that's the case with unofficial builds. Plus, @Unjustified Dev was begging those Mad Catz guys to release the source code so that he can develop better roms.
Check out the recovery thread in the development section. It explains how to force the MOJO to boot into recovery via Fastboot using a PC. Now, I don't want to say that this makes the MOJO unbrickable, I don't believe all the gods together could do that to any machine. But it makes bricking it very unlikely. Once you're in recovery, you can try a factory reset, flash the same ROM again, flash the stock FW back (extremely quick & easy if you shot a Nandroid backup before flashing a custom ROM), and (this one I recommend whenever changing ROMs) format your /data partition.
I doubt Mad Catz will warranty your hardware because of a software problem that you caused. I recommend you learn to repair that problem, especially since it is so easy on the MOJO.
Hello,
Does anybody know how to fix the "INPUT SIGNAL OUT OF RANGE" error.
Please help, I dont want to give up on my Mojo.
Having kind of the same issue. the hdmi was starting to come off board so i opened and fixed it. But when i turned on nothing but i did the the instructions from the forum and was able to flash twrp on it and custom rom. I can do whatever i want in recovery but when it boots i get nothing no light on front. ive tried all the custom roms and official and wiping everything but still no boot felt like a big loss. is there anything else to do? What did i possibly mess up strange since i can get into recovery.
buggin0915 said:
Having kind of the same issue. the hdmi was starting to come off board so i opened and fixed it. But when i turned on nothing but i did the the instructions from the forum and was able to flash twrp on it and custom rom. I can do whatever i want in recovery but when it boots i get nothing no light on front. ive tried all the custom roms and official and wiping everything but still no boot felt like a big loss. is there anything else to do? What did i possibly mess up strange since i can get into recovery.
Click to expand...
Click to collapse
Very strange, you're saying that you get a video output when booted into recovery but not when booting a ROM? From your description I'd be ready to say so solly, you have a hardware problem, but if TWRP can output video it's almost certain that it's a software glitch. Did you try a full format of the /data partition? If that filesystem is corrupt it might conceivably cause that.
How did you fix the hdmi port. Mine was a little loose so I soldered the 4 contact points but with no luck. Can you give me some pointers of how you fixed yours? Thanks.
Ok, so I've been lost as far as for what is going wrong with my device, I managed to downgrade to VS99513b from the 14b update through kdz, and I got TWRP installed successfully, but when I install ANY custom rom made for my device it gives me graphical glitches on the Boot logo, and even when it boots into the actual OS itself?
I don't know what's causing this, I mean TWRP looks to be just fine while I'm flashing these ROMS I did make a back-up prior, but I'd prefer a custom firm if I can get it any suggestions, or any explanations would be nice
Ok, I found the issue
It had to do with the kernel somehow? I just successfully flashed a Rom, and repeated the steps with a previously "broken" rom the only change is my use of a Stock Kernel Mod zip which seems to fix the graphical bug entirely... why that is I don't know, but hell if it works IDC
ProtoPropski said:
Ok, I found the issue
It had to do with the kernel somehow? I just successfully flashed a Rom, and repeated the steps with a previously "broken" rom the only change is my use of a Stock Kernel Mod zip which seems to fix the graphical bug entirely... why that is I don't know, but hell if it works IDC
Click to expand...
Click to collapse
this has been discussed so many times is why no one is responding.
if you googled v20 and static screen you would have had 1000 posts discussing this or even when you read disclaimer on root.
The static is due to changing your aboot aka bootlaoder for the us996 unlock one, casuing ALL stock boot.img to display static. Fortunately months after root had been released the devs developed fixes to hide static and return a normalish boot experience. with the exception 1st boot takes a little longer.
The static can be overcome by locking screen after bootup, then covering the proximity sensor until 2nd screen falls asleep then unlock and use as normal.
This was the initial fix that was the ONLY way to use the device after root, but now most stock kernels being built include the fix, and dont require this.
Hope this helps, and i dont mean to be rude by my response but theres a ton of this info everywhere on the forum and these questions that have been asked 1000 times wont keep getting answered. Please use the search function or read the disclaimers us devs are putting out there before using the methods to gain root and be using cfw.
Team DevDigitel said:
this has been discussed so many times is why no one is responding.
if you googled v20 and static screen you would have had 1000 posts discussing this or even when you read disclaimer on root.
The static is due to changing your aboot aka bootlaoder for the us996 unlock one, casuing ALL stock boot.img to display static. Fortunately months after root had been released the devs developed fixes to hide static and return a normalish boot experience. with the exception 1st boot takes a little longer.
The static can be overcome by locking screen after bootup, then covering the proximity sensor until 2nd screen falls asleep then unlock and use as normal.
This was the initial fix that was the ONLY way to use the device after root, but now most stock kernels being built include the fix, and dont require this.
Hope this helps, and i dont mean to be rude by my response but theres a ton of this info everywhere on the forum and these questions that have been asked 1000 times wont keep getting answered. Please use the search function or read the disclaimers us devs are putting out there before using the methods to gain root and be using cfw.
Click to expand...
Click to collapse
I was looking up info on "LG V20 Graphical Glitched Boot Screens" prior to posting this, and in that process I had only found one dead post, trust me I looked guess the search term I used was too descriptive, or uncommonly used? thanks for the reply though, I kinda fixed it on my own (by accident) through patching in a Stock Kernel Mod through TWRP after writing a fresh VS995 custom ROM it's all good now, my last post wasn't a bump, it was a poorly explained solution lol
Sry, I'm still not use to how this forum is ran, I kinda bounce between forums like a drunk whore on prom night
Link To Kernel Mod Used | ModStock