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.
Hi guys, have a few questions...
For starters, I have a Samsung Galaxy S4 / AT&T
Running Android 4.4.2 Rooted with Towel Root
Connected on Straight Talk
~NC1
SafeStrap 3.72 (TWRP v2.7.0.0) Installed.
Im new to all this ROM/Modules and Rooting stuff.
Last time i fully customized stuff was on my Motorola RZR ages ago
making my keypad/ LED light blink with calls, and replacing the Cingular Logo
with a Pirate/2 Swords Logo. hah... good times.
I mean there was jail-breaking and whatnot but...that's easy stuff.
Any who, Im a quick learner so on to the subject.
My original idea was to FULLY customize this phone and install ROMS/other OS, thats
what im all about, customization. Sadly, i realized im on a NC1 which its Boot loader is
locked if im understanding correctly preventing me from installing other? ROMS?
However if i understood correctly, we still can install certain ROMS? Whats the difference?
Is there any ROM i can install that is clean? no bloatware? but with everything I need?
Whats the best, fastest and best looking ROM i can get? or they dont look different because the
boot loader thing? Or they can only be Samsung/AT&T roms? This stuff can be confusing. lol
Module wise, why do i need them? why arent they included in the actual ROM?
Also, is there any App/or way for me to know what causes my phone to randomly crash/reboot?
A few months ago I was at the GYM and my phone randomly shut off. It didnt want to turn back on.
After a while it turned back on, then it would randomly reboot. That eventually went away.
Last night, i was with some friends in a bar and my phone just turned off again. Didnt wanna turn
on...then the same reboot thing happened again.
Today, is working fine. I thought maybe it was an overheat issue but, i wasnt doing anything on my
phone and on top of that im using a CPU tempt program installed through xPosed and according to the
readings it wasnt hot, as it was in the 50-55c (or is that too hot?) Im at home now and its reading
36c but i dont have its case on (if that makes any difference)
There are 3 kind of "ROM"s :
1- Official ones. made by samsung. flashable via odin exclusively. not rooted
2- A bit modified (maybe more than a bit) Official ones, modified by people, flashable via odin or recovery (1), usually already rooted
3- Completely rewritten ROMS, almost made from scratch (Cyanogenmod, MIUI for exemple...), installable via recovery. already rooted
Now, your phone can be in two states : Rooted or not rooted.
From factory, your phone is not rooted (you can compare it to jailbreak)
with root, you become a "super user", which means you have rights on almost every single aspect of your phone, and you give authorisations to apps so they can act on system files (for exemple, they can get hidden informations, they can automatically install apps etc... infinite possibilites there are.)
As for the best rom there is, is like asking what is the best music ever, it depends on the user, you have to try by yourself to find the one that satisfies you the most.
For random reboots, i personally think that it is comparable to windows Blue Screen of Deaths. you maybe messed up something while installing something. your phone can't handle the bug, so it restart or shut down itself. so the safest way to get rid of this problem is to factory reset your phone (via the recovery)
if you are looking for stableness, don't opt for completely remade ROMS, they are usually experimental. but personally i use MIUI and i didn't have any problem and i love this ROM.
Hope i answered every question.
Thanks a lot for the reply.
I understand a bit better now...
That MIUI looks interesting... Reminded me of DreamPassport for my Sega Dreamcast, hah...
I'm guessing I cant install that one huh? Lol
well since you already have a custom recovery you can... just download a miui rom (one for your phone version (be carefull about the model) ) then put it on the root of your sd card, go to the custom recovery and flash zip from sdcard and choose it... but i advice you to factory reset your phone first in order to fix your reboot problem.
also, make sure you have installed the right android version before installing the equivalent miui version (for exemple if you want to install miui that requires 4.2, install an official 4.2 rom first) via odin.
Gotcha. Thanks.
One last question....
If I want my phone with the original OS it came with. But with all the bloatware removed...
which rom would be the best? , since I want the stock experience but no bloatware.
Also...
I noticed when you click to see how much ram is being used, it says
800/1.77GB
Isnt my phone suppose to have 2GB? Can I do something to get that back? is it cause the bloatware?
I appreciate the help.
Raging Tiger said:
Gotcha. Thanks.
One last question....
If I want my phone with the original OS it came with. But with all the bloatware removed...
which rom would be the best? , since I want the stock experience but no bloatware.
Also...
I noticed when you click to see how much ram is being used, it says
800/1.77GB
Isnt my phone suppose to have 2GB? Can I do something to get that back? is it cause the bloatware?
I appreciate the help.
Click to expand...
Click to collapse
I don't think the above information is correct.
From what I know the AT&T has a locked bootloader. So you can run custom roms, just not all of them. I think only custom roms that match the version you are using.
You could better read in the section for the AT&T (this section is for a different model).
http://forum.xda-developers.com/galaxy-s4-att
I'm currently running 4.4.2 and biggins ROM. been running flawlessly since I put it on it when it came out. Now, for about the last month or 2 my WiFi Keeps Shutting off on its own, forgets WiFi passwords, won't connect hardly when it does come in. It's also been randomly rebooting on its own, sometimes 3 or 4 times in a row. Anyone have any suggestions on how to fix it. I've had the phone since the note 3 came out.
Sent from my SM-N900V using Tapatalk
Frankly that sounds more like hardware troubles than software.
(Q) Are you overclocking or undervolting? Using kernel tuning apps? If so, temporarily stop doing that to see if the problem goes away, and if not then there's two approaches for resolving this:
(A) Throw the phone away and get a new one.
(B) Wipe and and install a conservative ROM e.g. Jasmine, retaining the stock kernel. If the same problems continue, then you have verified it is a hardware problem; see (A)
bftb0 said:
Frankly that sounds more like hardware troubles than software.
(Q) Are you overclocking or undervolting? Using kernel tuning apps? If so, temporarily stop doing that to see if the problem goes away, and if not then there's two approaches for resolving this:
(A) Throw the phone away and get a new one.
(B) Wipe and and install a conservative ROM e.g. Jasmine, retaining the stock kernel. If the same problems continue, then you have verified it is a hardware problem; see (A)
Click to expand...
Click to collapse
I'm not overclocked or anything. It's been on Biggins ROM since he came out with it last year. And I haven't done anything since. It's got me baffled as to why it just randomly started doing it.
Sent from my SM-N900V using Tapatalk
donelam304 said:
I'm not overclocked or anything. It's been on Biggins ROM since he came out with it last year. And I haven't done anything since. It's got me baffled as to why it just randomly started doing it.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Actually I guess I wasn't familiar with the Biggins ROM but then I remembered that you said "last year", so (just now I figured that) you were either on a DevEd phone, or it was a "stock kernel" ROM.
So I looked at the Biggins thread. I guess it is actually just a very heavily themed stock-kernel ROM, and you are using Safestrap? And don't have an unlocked bootloader? And don't have a "real" version of TWRP in the recovery partition?
If that's what you did, then you don't have a trivial way of stock reversion short of going back to Odin and starting over with rooting.
Unless you were diligent and backed up the stock slot with Safestrap-twrp right after you flashed Biggins.. Or even better, you also did the same thing right after you installed Safestrap, even before you installed Biggens[/b] Then you could try and dirty-flash the Biggens backup and see if that changes anything. And if that didn't work, restore the original (Safestrapped, pre-Biggens) ROM along with a factory reset and see if that does anything.
But that would only rectify problems that were due to flash memory bit-rot problems (progressive wear & eMMC flash memory pages slowly going bad). And even if that were the case, it's a sign of more of it yet to come.
If you didn't make those backups, then I suppose you have a trip to Odin and re-rooting, re-installation of Biggins - on a phone that might have failing hardware. Either that or you could take the plunge and unlock your bootloader. Then you would have more options.
Are you on NC4?
Hardware does go bad. It happens at a low probability, so usually it doesn't affect most people before the time they would retire their hardware. Although I have to say - based on my experience with other devices - use of MLC flash memory probably does imply a pretty short product lifetime. (It's sort of ridiculous, buying a device that costs $700 and expecting it to be dead in 3 years. OTOH, in those three years most VZW subscribers have spent another $2500+ on service fees for their first line, so it's not the longest pole in the tent.)
bftb0 said:
Actually I guess I wasn't familiar with the Biggins ROM but then I remembered that you said "last year", so (just now I figured that) you were either on a DevEd phone, or it was a "stock kernel" ROM.
So I looked at the Biggins thread. I guess it is actually just a very heavily themed stock-kernel ROM, and you are using Safestrap? And don't have an unlocked bootloader? And don't have a "real" version of TWRP in the recovery partition?
If that's what you did, then you don't have a trivial way of stock reversion short of going back to Odin and starting over with rooting.
Unless you were diligent and backed up the stock slot with Safestrap-twrp right after you flashed Biggins.. Or even better, you also did the same thing right after you installed Safestrap, even before you installed Biggens[/b] Then you could try and dirty-flash the Biggens backup and see if that changes anything. And if that didn't work, restore the original (Safestrapped, pre-Biggens) ROM along with a factory reset and see if that does anything.
But that would only rectify problems that were due to flash memory bit-rot problems (progressive wear & eMMC flash memory pages slowly going bad). And even if that were the case, it's a sign of more of it yet to come.
If you didn't make those backups, then I suppose you have a trip to Odin and re-rooting, re-installation of Biggins - on a phone that might have failing hardware. Either that or you could take the plunge and unlock your bootloader. Then you would have more options.
Are you on NC4?
Hardware does go bad. It happens at a low probability, so usually it doesn't affect most people before the time they would retire their hardware. Although I have to say - based on my experience with other devices - use of MLC flash memory probably does imply a pretty short product lifetime. (It's sort of ridiculous, buying a device that costs $700 and expecting it to be dead in 3 years. OTOH, in those three years most VZW subscribers have spent another $2500+ on service fees for their first line, so it's not the longest pole in the tent.)
Click to expand...
Click to collapse
Here is my current build. I am on NC4.
Sent from my SM-N900V using Tapatalk
Well,
What do you plan on doing? It's not like there's a toggle button in Settings labeled "Act strange and reboot randomly mode" that we can just go in and turn off.
Do you have any Safestrap backups?
How about the NC4 factory Odin firmware file, do you have that? A copy of Odin somewhere & a PC it will run on?
That's how these things go - you need to create a fault hypothesis, and then try something that will hopefully do something to remedy that type of fault... which might or might not work.
The "bit rot" hypothesis assumes that flashing the same software you already have on the phone will correct eMMC memory pages that have gone bad, both by refreshing the data and also through page replacements by the Flash memory controller doing wear leveling. But that's only one hypothesis out of many that are possible. There's no guarantees that this will fix the problems you are having if the origin of the problem has nothing to do with this mechanism.
If it were me I'd probably make TiBu backups of my most frequently used apps, back up the internal SDcard, and start from scratch by Odin flashing NC4 stock*. Its more effort, but pretty much everything gets re-written that way, and if you continue to have issues then you know it is time to move on to a new phone, rather than continuing to diddle with it.
good luck
* I believe that the TowelRoot app works on NC4, does it not?
Yes, towelroot is what I use to root it. I have a backup, but I'm not sure what it is. The Daye on it is 1970. Lol.
Sent from my SM-N900V using Tapatalk
donelam304 said:
Yes, towelroot is what I use to root it. I have a backup, but I'm not sure what it is. The Daye on it is 1970. Lol.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If you do a "tar tvf filename" on those .win00x files the dates of the files listed will give you a better idea. (I suppose that some widows archive programs also understand .tar file formats, but I can't give you a reccomendation)
Also I sort of recall that the Safestrap version of (twrp) recovery adds the name of the slot from which the backup was made.
You actually have lots of choices. You could unlock the bootloader, install a custom recovery, and try a different ROM. Or when faced with Odin flashing, bite the bullet and upgrade to OF1. (As near as I can tell, using towelroot on NC4 is far less of a hassle then that Yemen tool appears to be with OB6/OF1 ... that sort of argues for flashing NC4 instead of more recent firmware.)
Well anyway. If it's failing hardware none of this will make a whit of difference and your phone will still lockup/reboot/drop WiFi.
good luck
Hello guys,I cannot flash TWRP. After putting 'fastboot flash recovery twrp.img' command when I select recovery it shows 'error to load recovery' or something like this in red colour. So I select fastboot and 'Start' the phone. Later when I put the phone again in recovery,I get that it is still the stock recovery.
sounds like it doesn't see the file twrp.img.
I usually go with
Flashboot flash recovery "C:\FILE LOCATION"
"C:\FILE LOCATION" being a click and drag to the CMD Prompt, if your TWRP.IMG is in a different folder than your fastboot files.
Michajin said:
sounds like it doesn't see the file twrp.img.
I usually go with
Flashboot flash recovery "C:\FILE LOCATION"
"C:\FILE LOCATION" being a click and drag to the CMD Prompt, if your TWRP.IMG is in a different folder than your fastboot files.
Click to expand...
Click to collapse
My all files are in same folder.
maybe the .img is corrupted? I'm assuming you are bootloader unlocked...
Michajin said:
maybe the .img is corrupted? I'm assuming you are bootloader unlocked...
Click to expand...
Click to collapse
I have download the image from official twrp.me site. And yes I have unlocked the bootloader months ago.
Can you just boot TWRP, not flash it?
fastboot boot TWRP.img
Replace TWRP.img with your actual file.
acejavelin said:
Can you just boot TWRP, not flash it?
fastboot boot TWRP.img
Replace TWRP.img with your actual file.
Click to expand...
Click to collapse
Ok,but after that? Actually sir,months ago u told me to flash it and go to recovery so I was following ur steps. Boot is temporary,so after boot how to flash twrp permanently to replace stock recovery?
Atanu Mukherjee said:
Ok,but after that? Actually sir,months ago u told me to flash it and go to recovery so I was following ur steps. Boot is temporary,so after boot how to flash twrp permanently to replace stock recovery?
Click to expand...
Click to collapse
Yes, but you are saying it doesn't work... So I was asking if you can boot it to verify the image works.
acejavelin said:
Yes, but you are saying it doesn't work... So I was asking if you can boot it to verify the image works.
Click to expand...
Click to collapse
Ok sir. And if work then what to do next? How to flash twrp in simple process?
Atanu Mukherjee said:
Ok sir. And if work then what to do next? How to flash twrp in simple process?
Click to expand...
Click to collapse
If that works than your image file itself is good... Once TWRP is loaded, copy the twrp.img file to the device and flash it with TWRP.
I know it seems counter-intuitive to install TWRP from TWRP, but it is just running in RAM, so you can flash the IMG to the recovery partition with TWRP.
My assumption is something fastboot or drivers is not correct... using this method would bypass those issues, you could also bypass these issues by using Linux as your OS since it does not require drivers like Windows does to talk to an Android device. If you can successfully flash but NOT load recovery, I would assume you have a defective device.
Of course there always the possibility of a bad cable or USB port on the computer though...
acejavelin said:
If that works than your image file itself is good... Once TWRP is loaded, copy the twrp.img file to the device and flash it with TWRP.
I know it seems counter-intuitive to install TWRP from TWRP, but it is just running in RAM, so you can flash the IMG to the recovery partition with TWRP.
My assumption is something fastboot or drivers is not correct... using this method would bypass those issues, you could also bypass these issues by using Linux as your OS since it does not require drivers like Windows does to talk to an Android device. If you can successfully flash but NOT load recovery, I would assume you have a defective device.
Of course there always the possibility of a bad cable or USB port on the computer though...
Click to expand...
Click to collapse
'Flash twrp with twrp' means just flash it like flashing rom? Copy it to sd card,swipe to flash?
When I cheked the drivers were working or not by putting command,those are working as it gave me back ph serial no. And mine is original windows. Upgradeed it to 10. Is there any issue for windows version?
And the cable,yes I dont know is it defective or not. But u know sir,1st time when I put 'adb devices' it could not recognise my device. Then I pull the usb off and put it again then works.
Atanu Mukherjee said:
'Flash twrp with twrp' means just flash it like flashing rom? Copy it to sd card,swipe to flash?
When I cheked the drivers were working or not by putting command,those are working as it gave me back ph serial no. And mine is original windows. Upgradeed it to 10. Is there any issue for windows version?
And the cable,yes I dont know is it defective or not. But u know sir,1st time when I put 'adb devices' it could not recognise my device. Then I pull the usb off and put it again then works.
Click to expand...
Click to collapse
Boot TWRP, then copy the twrp.img file to the device.
From the main menu in TWRP, select Install, change to Images by tapping the button on the bottom-right of screen, and navigate to the twrp.img file then select it and a new menu will open asking you if it is a Recovery Image or Boot Image, select Recovery Image, then swipe to flash. Once complete go to main menu, select Reboot, then Recovery.
I can't really answer your questions specific to Windows... I don't own a Windows PC and my only access to Windows is via a Virtualbox VM. Sorry.
acejavelin said:
Boot TWRP, then copy the twrp.img file to the device.
From the main menu in TWRP, select Install, change to Images by tapping the button on the bottom-right of screen, and navigate to the twrp.img file then select it and a new menu will open asking you if it is a Recovery Image or Boot Image, select Recovery Image, then swipe to flash. Once complete go to main menu, select Reboot, then Recovery.
Click to expand...
Click to collapse
Ok sir.thank u very much. But sir as u know,I may ask u again some silly ques in future regarding these methods.
One more silly ques,if I boot twrp and from there if I flash lineage,will this process work? And what I have to clear before flashing rom?
Atanu Mukherjee said:
Ok sir.thank u very much. But sir as u know,I may ask u again some silly ques in future regarding these methods.
One more silly ques,if I boot twrp and from there if I flash lineage,will this process work? And what I have to clear before flashing rom?
Click to expand...
Click to collapse
Before flashing a new ROM I always wipe user data, system, and caches, then flash ROM and Gapps. Make sure to backup to your SD card first.
acejavelin said:
Before flashing a new ROM I always wipe user data, system, and caches, then flash ROM and Gapps. Make sure to backup to your SD card first.
Click to expand...
Click to collapse
Yes u told me before to make a nandroid backup.
Do I need to download Gapps? I already backed up apps to lptp. Sir,Lineage or AICP which one is better? I get a max 4.10hrs of SOT with wifi now. Its poor I think as I dont play game. In 2g its lower & 3g sucks totally.
Atanu Mukherjee said:
Yes u told me before to make a nandroid backup.
Do I need to download Gapps? I already backed up apps to lptp. Sir,Lineage or AICP which one is better? I get a max 4.10hrs of SOT with wifi now. Its poor I think as I dont play game. In 2g its lower & 3g sucks totally.
Click to expand...
Click to collapse
Do you need Gapps? No, unless you want any Google applications, such as the Play Store. If you don't care about Google apps and services you can skip them and use an alternative.
Honestly... 4hr is pretty good, I never get better than 3.5 hours of SOT over 18 hours off-charger with no gaming.
No third party ROM will give you better battery life than stock. Moto may not be good at a lot of things, but they can optimize a ROM better than anybody. The only way you will get better battery life than stock is to use a third party kernel and scale everything way back, trading off performance significantly.
The Pure/Style's main battery abuser is the screen... it is beautiful, but it sucks battery like nobody's business, and no third party ROM or kernel can really have any effect on that. Your battery usage due to radio connectivity is kind of locked too, no matter the ROM, the radio firmware is the same.
acejavelin said:
Do you need Gapps? No, unless you want any Google applications, such as the Play Store. If you don't care about Google apps and services you can skip them and use an alternative.
Honestly... 4hr is pretty good, I never get better than 3.5 hours of SOT over 18 hours off-charger with no gaming.
No third party ROM will give you better battery life than stock. Moto may not be good at a lot of things, but they can optimize a ROM better than anybody. The only way you will get better battery life than stock is to use a third party kernel and scale everything way back, trading off performance significantly.
The Pure/Style's main battery abuser is the screen... it is beautiful, but it sucks battery like nobody's business, and no third party ROM or kernel can really have any effect on that. Your battery usage due to radio connectivity is kind of locked too, no matter the ROM, the radio firmware is the same.
Click to expand...
Click to collapse
I have already backed up google apps to my sd cards and pc. So i can install them again,what I do after every hard reset.
Actually as N claims more battery saver than M,so I thought if any of those roms gv bttr bttry bckup. Before I got 5hrs with wifi.now it drops to 4.10 with a good off charger time. And if I use continuously with little sleep,thn 4.30hrs with wifi only.not in 3g,2g(though my home is low network coverage area.red 3g signal)
Atanu Mukherjee said:
I have already backed up google apps to my sd cards and pc. So i can install them again,what I do after every hard reset.
Actually as N claims more battery saver than M,so I thought if any of those roms gv bttr bttry bckup. Before I got 5hrs with wifi.now it drops to 4.10 with a good off charger time. And if I use continuously without little sleep,thn 4.30hrs with wifi only.not in 3g,2g(though my home is low network coverage area.red 3g signal)
Click to expand...
Click to collapse
Your call... When I change ROMs I never restore apps, too many issues with conflicts and other stuff. Experience has taught me to reinstall from Play Store every time, maintain online backups for data and settings and other stuff (contacts, photos, etc), and run a lean device.
As far as restoring Google apps, you can restore most of the apps, but you will want to flash the pico or nano Gapps at a minimum in order to get the framework and basic libraries installed into system, or else your backed up Google apps won't work anyway.
acejavelin said:
Your call... When I change ROMs I never restore apps, too many issues with conflicts and other stuff. Experience has taught me to reinstall from Play Store every time, maintain online backups for data and settings and other stuff (contacts, photos, etc), and run a lean device.
As far as restoring Google apps, you can restore most of the apps, but you will want to flash the nano Gapps at a minimum in order to get the framework and basic libraries installed into system, or else your backed up Google apps won't work anyway.
Click to expand...
Click to collapse
Ok then I will download Gapps also. Btw sir is there news when offifial 7 comes for style? I was waiting for long but after that moto USA tweet I feel little sad.its too late.
And one more think which I dont like is the cpu. I checked and get that CPU 0 to CPU 4 all are working but not the CPU 5. The 6th core is sleeping all the time as I dont play any game. Cpu4 also sleeps normal time. So basically for me its a quad core. :crying:
Atanu Mukherjee said:
Ok then I will download Gapps also. Btw sir is there news when offifial 7 comes for style? I was waiting for long but after that moto USA tweet I feel little sad.its too late.
And one more think which I dont like is the cpu. I checked and get that CPU 0 to CPU 4 all are working but not the CPU 5. The 6th core is sleeping all the time as I dont play any game. Cpu4 also sleeps normal time. So basically for me its a quad core. :crying:
Click to expand...
Click to collapse
Cores are throttled or taken off-line based on load and temperature... The BIG cores (one or both) only come online if the threshold of CPU load reaches a certain level, otherwise they pretty much stay offline as they use much more power than the four LITTLE cores do. This is literally called big.LITTLE architecture, read up on it if you want to know more (I am not an ARM/CPU expert), but if you are not using your big cores, it is probably because they are not needed.
As far as when "official" Nougat will be available? No word, last I heard was Moto Germany said it was pushed back to May sometime... TBH, I am kind of think chances are decent that Lenovo to come up with some lame excuse and just cancel the upgrade, so I wouldn't hold my breath for it.
Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)
*Update 7/30: On my 6P, I found that the original kernel with this mod was using pretty much 1.5 cores, instead of all 4. People with the 5X were also reporting this, so I modified the images to utilize all 4 cores better. It helps performance a lot (able to beat stock 6P in some Antutu marks now, and play intensive games), try it out if you haven't yet!
*Petition:
I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)
*Changelog:
8/26 - EX kernel for Android O uploaded.
8/22 - Android O working, boot.img and source uploaded.
8/08, 2nd Change - Added boot.img for 48C firmware (August security patch).
8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
8/07 - Added boot.img for 1 core, just to see if it would work for devices that didn't work with the 4 core image.
7/30, 2nd Change - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
7/30 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP, and added Marshmallow images.
7/23- Created this fix, stock boot.img, twrp, and EX kernel added.
*What this fix does, and how to apply it:
The problem:
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.
The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.
Requirements: For this fix to work, you need:
A brain
A computer
A bootlooping 5X with an unlocked bootloader/OEM unlocking enabled
The modified files of your choice.
Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.
How to apply the fix:
Boot your phone into bootloader (hold power and volume down).
Connect your phone to the computer.
Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
Edit: with the new universal EX zip, you don't have to flash the modified boot.img now, you can just flash TWRP, and then flash the EX zip, and everything should work.
Boot up your phone, and hopefully it should work!
*If your phone is bootloader locked/OEM locked:
You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.
To enable OEM unlocking and unlock bootloader:
Go to settings.
Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
Once you're in developer options, click on "OEM unlocking" and accept the prompt.
Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.
*Downloads:
Boot.img from Android O DP6: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. As a bonus, it also disables forced encryption. Thank you to @xls654 for figuring out how to get Android O to work.
Boot.img from stock 48C, 7.1.2 firmware (August security patch): Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people on the 6p say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
Boot.img from stock 47Z, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people on the 6p say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
EX kernel version 5.03, for Android O: Download | Mirror. EX kernel for Android Oreo, modified to use 4 cores. You must flash it over the 4 core boot.img for it to work.
EX kernel version 4.12, universal zip: Download | Mirror. This zip is modified to use only 4 cores, and it will also apply the speed fix. Flash this in TWRP. I highly recommend you flash this, as it improves device performance notably, and disables forced encryption. This kernel should work with almost any other ROM, and it applies the core utilization mod from the first image, thanks to AnyKernel.
Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Here it is: Download | Mirror
For Marshmallow:
Boot.img from the latest 6.0.1 20K firmware: Download | Mirror. This boot.img is modified to use only 4 cores, and is modified to utilize those 4 cores more effectively. Untested as of now.
Ex kernel version 1.2.0 for Marshmallow: Download | Mirror. This is the latest EX kernel for marshmallow, it will keep the core utilization mod from the above image, and should work on almost any other ROM, thanks to any kernel. Untested as of now.
*Source Code:
Source for 4 core Android O DP6: Source.
*Tested custom ROMS/kernels
you should be able to use almost any ROM with a stock based kernel, just flash the EX zip over it.
If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.
*To improve performance slightly:
Flash a custom kernel. I will upload more kernels as people request more, so stay tuned.
Flash a custom ROM. Once again, I will upload more as people request more, so stay tuned.
Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
*Credits:
@rchtk, His post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
@xls654, He found out how to get Android O working with 4 cores.
*FAQs:
What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are you have a different problem.
Does EX kernel have the new speed fix? - Yep, the EX kernel zip should apply the 4 core fix, and the speed fix. It should also work with almost any ROM, including stock.
I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.
I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated Donate to me here!
If this guide helped you, please click thanks, it means a lot to me
Didn't work
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Acelogic_ said:
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Click to expand...
Click to collapse
dang :/ If you can get into twrp, pulling the "console-ramoops" would be helpful, but I don't think you can boot to twrp.
this actually fixes my phone, i do the same with elementalx kernel i disable the big cores as soon as my phone boots up so this img is really handy
TheIronLefty said:
this actually fixes my phone, i do the same with elementalx kernel i disable the big cores as soon as my phone boots up so this img is really handy
Click to expand...
Click to collapse
Awesome! Glad to hear it.
XCnathan32 said:
dang :/ If you can get into twrp, pulling the "console-ramoops" would be helpful, but I don't think you can boot to twrp.
Click to expand...
Click to collapse
Yeah Twrp is not working.
So I just flashed this over the May 2017 build and my phone boots and is working just fine, albeit a bit slowly.
I'll update to the latest build and reflash but for now you can say it works as intended. Thanks for the effort
Gonna try this
Sent from my EVA-L09 using Tapatalk
It's worked for me. Phone is slower, and taking picture with hdr+ is okey but processing is very slow. I turned off animation, is there anything else I can change so phone can perform faster ?
Any idea how long this should take? I managed to get into my 5x and enable debug mode / OEM unlocking
I ran the fastboot flash boot N2G47Z_4Cores.img command and its been stuck for about 5 minutes
This works, thanks. First time I've been able to boot my 5X in months.
Acelogic_ said:
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Click to expand...
Click to collapse
I uploaded a custom TWRP image and EX kernel zip. Try flashing the modified TWRP, and then flashing the modified EX kernel, and see if that works.
after trying again I was able to get it to write successfully however the nexus 5x is still bootlooping, this is an original hardware revision nexus 5x if that helps
ragdoll96 said:
So I just flashed this over the May 2017 build and my phone boots and is working just fine, albeit a bit slowly.
I'll update to the latest build and reflash but for now you can say it works as intended. Thanks for the effort
Click to expand...
Click to collapse
X-calibar said:
It's worked for me. Phone is slower, and taking picture with hdr+ is okey but processing is very slow. I turned off animation, is there anything else I can change so phone can perform faster ?
Click to expand...
Click to collapse
I updated the OP with a modified EX kernel, and some tweaks to make your device faster, check it out to see if it helps your device.
stipo42 said:
Any idea how long this should take? I managed to get into my 5x and enable debug mode / OEM unlocking
I ran the fastboot flash boot N2G47Z_4Cores.img command and its been stuck for about 5 minutes
Click to expand...
Click to collapse
My first time took around 10 minutes to boot I think, if it takes over 20 minutes, reboot your device and reflash, and if that fails, update your firmware to the latest version.
stipo42 said:
after trying again I was able to get it to write successfully however the nexus 5x is still bootlooping, this is an original hardware revision nexus 5x if that helps
Click to expand...
Click to collapse
Are you upgrading from stock firmware or a custom rom? This boot.img is for the latest 7.1.2 build. Unless you have files that you can't afford to delete, I would recommend reflashing your stock firmware with the latest version.
flar2 said:
This works, thanks. First time I've been able to boot my 5X in months.
Click to expand...
Click to collapse
Awesome! I just want to say how much I love your kernel, it makes this fix much more viable.
update: I was able to install twrp and boot into that, but its asking for a password.... @XCnathan32 is there a specific password you set or should "default_password" work?
stipo42 said:
update: I was able to install twrp and boot into that, but its asking for a password.... @XCnathan32 is there a specific password you set or should "default_password" work?
Click to expand...
Click to collapse
default_password didn't work for me, I just clicked cancel when it asked for the encryption, and then I factory reset the device through TWRP. If you have important files you can't delete, you can try just flashing EX Kernel, as I don't think EX needs to access the /data partition.
Update 2 : Seems I was able to just cancel out of the password prompt. Flashed Elemental X and it looks like its booting!
Awesome job my friend, you fixed the (temporarily) unfixable. I'll play around with this for a few days and report back.
Thanks!
XCnathan32 said:
So I found a bootloop fix for the Nexus 6p here, and some users reported having the same problem with their Nexus 5X.
I do not own a Nexus 5X, but I made a modified boot.img the same way I made the modified 6P image. It simply disables the big cores, as that's what was preventing the 6P from booting.
Please report if this works/does not work for you, that way I can get a good sample size to determine how effective this is.
Disclaimer: I have not tested this, I uploaded this image so testers could flash it and report if it works or not. If your device breaks/spontaneously combusts after flashing this, you accepted that risk.
Edit: A few people have reported this working, so it should be safe.
N2G47Z_4Cores.img, this image is based on the latest 7.1.2 firmware for the Nexus 5X, modified by me to only use 4 cores. 4 reported working, 2 reported not working.
To flash it: you must have an unlocked bootloader and fastboot on your PC. Boot your device into bootloader, and then run the command fastboot flash boot N2G47Z_4Cores.img Hopefully, your device will now boot up.
TWRP3_1_1_5X.img, modified to use only 4 cores, will get working TWRP on your device. Not tested yet
To flash, navigate to the folder where it is downloaded, make sure you have fastboot installed, and then run this command: fastboot flash recovery TWRP3_1_1_5X.img.
EX4_10_5X.zip, Elemental X kernel V4.10 for android 7.1.2, modified to use only 4 cores, I highly recommend you flash this, as EX kernel is faster, and you can overclock to the little cluster to make up for some speed. Not tested yet.
To flash, copy the zip to your device, then flash it in the modified TWRP, just go through the AROMA installer as usual. Changing the BIG cpu frequency in the installer will not change anything, as the cores are disabled.
Additional notes:
Root worked on my 6p by flashing the regular SuperSu zip just as normal. None tested for 5X yet
To improve performance slightly:
Disable animations in developer options, it helps a lot.
Overclock little cores with EX kernel, I have mine set to 1632 MHz and everything is working fine so far.
Set CPU governor to performance (or some aggressive governor), with the BIG cores disabled, the battery is already much better, so using a better performance governor shouldn't be a problem for battery life.
Doing a fresh flash of the firmware/factory reset can help a lot too.
Fast custom roms can also help.
Roms that me/other users have found working with this fix:
Pure Nexus worked well for me on the 6p, insane battery life and very little lag. If you are going to flash a rom, be sure to flash the modified EX kernel over it.
If you find a rom that works with this fix, tell me, and I'll put it here.
Credits:
@rchtk, his post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
Feel free to ask me for help, If you have a favorite ROM/Kernel that you want to use, tell me and i'll modify it to use 4 cores.
Please click thanks if I helped you, it means a lot to me
Click to expand...
Click to collapse
Hey man I tried this method, and I can confirm that this works! Although it is slow, it's better than nothing I truly do appreciate your efforts. SCREW LG