Related
I guess I missed this over the weekend and I am looking for the original install that I dont need to have root for. I have been reading over the threads here and in the Dev forum and I am not seeing any links to the download for Non-Root users.
I am to much of a ***** to root my phone. i spent way to much cash on it and i am too worried something will go wrong.
So here is want I am asing for
A. The original non root install with instructions on how to do it
or
B. Someone to help walk me through the process of rooting and getting FroYo 2.2 set up on my phone.
Please shoot me a PM if your willing to help out. I am just way to worried if I do this without someone who knows what they are doing I am going to screw up my phone, and my wife would never let me buy another one ...lol
Can somsone help out a fellow Dev, thanks
Sorry I can't post links but here you go
androidandme.com/2010/05/news/how-to-manually-install-android-2-2-on-your-nexus-one/
Ya just found it buried in a thread
Thanks
See if I would have spent another 10 minutes searching I would have found it without having to ask ...lol
Got to remember to scan threads for 30 minutes not 20 before asking ...lol
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Paul22000 said:
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Click to expand...
Click to collapse
Paul, is that Avatar a picture of YOU?
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
attn1 said:
Paul, is that Avatar a picture of YOU?
Click to expand...
Click to collapse
All I wil say is:
λ
LOL ...........
you don't need to root to install froyo and you don't need to hook up your nexus to a pc. my method is pretty simple and it works.
edit: I shouldn't say it's my method. Its actully a backdoor to installing froyo.
theletterj said:
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Click to expand...
Click to collapse
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a nandroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader by flashing the Google Froyo Release with the stock recovery:
Google Froyo Release
You must be on release ERE27 for this to work.
Here's a link to some instructions on how to use the stock recovery program:
jp_macaroni's thread
I suspect that since most people have already rooted or cannot get to ERE27, Paul's guide is the best way to go for them.
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
jcohenlv said:
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
Click to expand...
Click to collapse
Yeah you know, everyone is new once. It's easy to sort out the tripe from the real deal when you've been around the block once or twice. Paul is doing his best to be helpful and not cause more confusion.
The problem isn't that people can't search so much as it is that searches yield too much conflicting information, so lets not jump down people's throats when they ask for a point of clarification. Instead, lets start asking moderators to sticky good info and pulling redundant/bad info so that searches are more meaningful. The number of new threads in here because of the Froyo release is mind numbingly high. Let's all try to exercise some patience.
attn1 said:
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a Nadroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader:
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
Click to expand...
Click to collapse
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
theletterj said:
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
Click to expand...
Click to collapse
You only need to unlock the bootloader. You do not need root.
Unlocking the boot loader allows installation of an alternate recovery, which allows you to install custom software to the existing ROM or to install a custom ROM. It's updating the ROM that allows you to gain root access, not unlocking the boot loader. It goes in this order:
> Unlock boot loader (void warranty - still not rooted)
> Install custom recovery
> nandroid backup (recommended/optional)
> Update ROM (for root access - or not)
The original instructions worked perfect
All that was needed was to change the name to update.zip load it on the root of the SD card then but the phone in bootloader and load recovery from SD.
Took about 5 minutes.
Once the phone came up it did a few things and took about another 5 minutes to chill on the processes then I was able to use the phone without any problems.
So for those interested here are the exact steps:
This is for NON Rooted T-Mobile Version!!!!
To manually install Android 2.2 on the Nexus One, perform the following steps:
1. Download the official Android 2.2 firmware for the Nexus One.
2. Copy the file to your microSD card and name it update.zip (newb warning: not update.zip.zip)
3. Power off your phone.
4. Hold down the VOLUME DOWN button and power it back on.
5. The phone will now search for files like PB00IMG.zip, etc. This is normal. Scroll down to recovery (using Volume Down Key) and press the POWER button.
6. When you see the “/!\” symbol, press the POWER button and the Volume Up button at the same time. You should be presented with a menu and one of the options should be “Apply sdcard:update.zip”.
7. Use the trackball to navigate to “apply sdcard:update.zip” and select it.
8. When you see “Install from sdcard complete”, select “reboot system now”.
Wait 5 minutes, phone will reboot once rebooted let the phone sit for about 5 minutes then you are good to go. It couldn't be any easier
So, flashing Cyanogenmod7/MIUI on the SGS i9000 is an area covered in many, many tutorials to date. However, the vast majority of them are outdated or just downright confusing, this guide tries to make flashing CM7/MIUI as painless as possible.
DISCLAIMER: This guide is based on my personal experience in flashing CM7/MIUI and i take NO RESPONSIBILITY WHATSOEVER in whatever untoward happens to your phone and/or life if you follow this. Also, this guide is meant for the SGS I9000GT PHONE ONLY, other variants please do not follow this guide to the letter and download the appropriate files for flashing.
Edit: This guide can be used to flash MIUI roms as well, seeing as they share the same requirements of needing Froyo bootloaders.
MIUI roms available:
1.MIUI Official [MIUI.us]
2. Galnet MIUI [Galnet and team]
3. MIUI+ [Decalc and Mothatt]
4. fitMIUI [Andro!de]
5 Nothing Fancy [spasms]
Note that this is not an exhaustive list.
Okay, lets go
Now, there are 2 ways to go about flashing CM7/MIUI.
1. ROMmanager method.
-Simple, fast but thats another tutorial altogether
2. The ODIN + CWM flashing method.
- That's what this tutorials all about!
NOTE: For those who wish to pursue Method 1, rschenck has written a guide on it.
Okay, now for the tutorial.
Firstly, find out what firmware you are running. Gingerbread bootloaders are now able to run MIUI/CM7. These give better battery life and are thus encouraged.
Go to ->SETTINGS ->ABOUT PHONE and look at what Android/Firmware Version you are running. If you are on 2.3.x, please skip the conditional step, if you are 2.1.x OR 2.2.x, you have to upgrade your bootloaders to 2.3.x.
CONDITIONAL STEP: Upgrade to GB bootloaders. (FOR 2.1.X AND 2.2.X FIRMWARE VERSIONS ONLY, 2.3.X FIRMWARES PLEASE SKIP THIS SECTION.)
Go to EZboot page.
1. Go to that website and download the Gingerbread bootloaders.
2. Download Odin, if you haven't done so already.
3. If you don't have Kies, you would need Samsung Drivers, which you can easily find around this forum. I believe its a sticky somewhere.
4. Open Odin and put your phone in download mode before connecting it.
5. Set up Odin as per picture in the link provided(The gingerbread one)
6. Flash and wait for reboot!
/END OF CONDITIONAL STEP.
2. Acquiring CM7/MIUI.
CM7 users: CM7 uses the term Nightlies, which are actually so called "experimental" builds that are updated, well, nightly. Despite it being called experimental, most nightlies are actually stable for "everyday usage". So don't be scared to flash 'em!
So,
1. Download the latest(topmost) version of CM7 or the various MIUI roms. (Links above)
2. Transfer the .zip file onto your phone through ADB push or USB cable.
3. Make sure your phone is not connected to your computer or anything. You're almost there!
Third, Flashing time.
1. Boot into recovery mode using the following method.
(a) Phone off.
(b) Press in the following order: VOLUP, HOME, POWER.
2. Now you have to clean out your phone.
-Wipe CACHE
-Go into advance options, WIPE DALVIK CACHE
-Go into mounts and storage. FORMAT SYSTEM, DATA AND CACHE. (Three separate moves)
3. Go to 'Install zip from sdcard' and scroll to your CM7/MIUI .zip file.
Flash.
Wait for reboot. And. You are done.
Congratulations, you are now running CM7/MIUI.
For CM7 users: Go get GAPPs(Google Apps) for Android Market and other android apps. Stay updated by flashing updated Nightlies.
[Small expansion of guide] Flashing from MIUI
If coming from MIUI rom, and wishing to switch to CM7(or vice versa)
1. Download newest version of CM7(or MIUI, whichever the case) and place in phone.
2. Boot into recovery. Format Cache and System. Not necessary to format Data(will erase all apps) but is recommended for stability purposes. You can backup your apps using Titanium Backup or use the native backup app in MIUI.
3. Install from zip and choose the correct file. Flash it.
Done.
Please comment if this was helpful to you. And THANK if it helped you!
Credits:
codeworkx - http://twitter.com/codeworkx
coolya - http://twitter.com/dumdidum
guiper -http://twitter.com/guiperpt
-All for CM7
nitr8 - For EZboot
rschenck - For his guide
And of course, myself for writing this.
Thank you, Very useful
mrsufgi said:
Thank you, Very useful
Click to expand...
Click to collapse
Thanks glad it helped
slotteh said:
Now, there are 2 ways to go about flashing CM7.
1. ROMmanager method.
-Simpler, faster BUT requires premium version of ROMmanager(purchasable in market)
Note: Premium version not required but that's another tutorial altogether.
Click to expand...
Click to collapse
I know this is supposed to be the definitive non-confusing guide, but I started reading your guide and 10 secs into it, you've posted confusing info:
info 1 - you state this first method requires PREMIUM ROMmanager
info 2 - in the very next sentence you state 'PREMIUM version not required"
After reading the rest of your guide, I have to conclude that it's just as - if not more than - confusing as other 'user guides' found in these forums. Your guide is only suitable for people who have learned by trial and error and are already comfortable with the nuances of wiping and flashing their phone.
Experienced users like myself have done it so many times I could do it with my eyes closed now, so I already know how to avoid missteps even if given incomplete, misleading or outright contradictory instructions, which your guide is full of.
I wish I had the time to go through the errors with a fine toothed comb, but I honestly don't at the moment (@work). That said, this guide either needs a complete re-write to improve readability and logic flow, or just be removed altogether.
evilsopure said:
After reading the rest of your guide, I have to conclude that it's just as - if not more than - confusing as other 'user guides' found in these forums. Your guide is only suitable for people who have learned by trial and error and are already comfortable with the nuances of wiping and flashing their phone.
Experienced users like myself have done it so many times I could do it with my eyes closed now, so I already know how to avoid missteps even if given incomplete, misleading or outright contradictory instructions, which your guide is full of.
I wish I had the time to go through the errors with a fine toothed comb, but I honestly don't at the moment (@work). That said, this guide either needs a complete re-write to improve readability and logic flow, or just be removed altogether.
Click to expand...
Click to collapse
Alright thanks for the feedback. It's the first guide I've tried to write so I think I've messed up a lot probably. I'll definitely try to re-write it. But thanks for the criticism.
Also, you've identified one area where I'm not very clear(ROManager part) and thanks for that. Do you have other specific examples of my post which are error-filled so that I can work on them? I want this thread to work. Thanks again
Have updated and removed contradictory statements.
Is it wrong this passage ?
1. Download the latest(topmost) version at : http://insanity.rollus.net/EZbase/img/sc/ezodin.png
Lord Style said:
Is it wrong this passage ?
1. Download the latest(topmost) version at : http://insanity.rollus.net/EZbase/img/sc/ezodin.png
Click to expand...
Click to collapse
Yes it is. Thanks very much for the spot
Edit: Edited it already. Thanks again
Thanks to slotteh for this guide.
Now I have CM 7 Nigthly 15 in my phone.
Stable cm7? Not for the sgs
Sent from my GT-I9000 using XDA Premium App
Mothatt said:
Stable cm7? Not for the sgs
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Yeah i've been a little confused looking for it. I'll edit it.
slotteh said:
Yeah i've been a little confused looking for it. I'll edit it.
Click to expand...
Click to collapse
@slotteh
one more MIUI rom, you may want to update your OP
http://forum.xda-developers.com/showthread.php?t=1184066
krarvind said:
@slotteh
one more MIUI rom, you may want to update your OP
http://forum.xda-developers.com/showthread.php?t=1184066
Click to expand...
Click to collapse
Thanks will do
Updated to include GB bootloaders flashing
what recovey do i need to install cm7 as it doesn't say or how do i install with odin
Are you sure if it's safe to flash MIUI rom with GB Firmware on every single one of the roms? I'm really considering fitMIUI, any suggestions?
Thanks for a nice guide.
bootloader
How i can flash only a new bootloader without lose all data?
Revise?
This section is not clear...
"Go to ->SETTINGS ->ABOUT PHONE and look at what Android/Firmware Version you are running. If you are on 2.2.x, please skip the conditional step, if you are 2.1.x OR 2.2.x, you have to upgrade your bootloaders to 2.3.x. "
I think this is a 'contradictory' point...
Otherwise, if this was a little proof-read, could be a dang good guide.
F x
Hi sorry for all late replies, have been a little busy, you may already have gotten answers to these but still,
got-petrol said:
what recovey do i need to install cm7 as it doesn't say or how do i install with odin
Click to expand...
Click to collapse
You need Clockworkmod Recovery and unless you're coming from a stock rom, you should already have this.
In either case, onstallation of EZbase from odin has been covered pretty well here: http://forum.xda-developers.com/showthread.php?t=1089989
It's really simple to follow, just make sure you have a full battery while flashing via odin.
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]LG G2[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: How do I root my G2?[/SIZE]There are several root methods depending on what android version you're on:
IOroot (Jellybean 4.2x/KitKat 4.4x)
New Root Method for LG Devices (Lollipop 5x)
[Japanese L-01F] Root your L-01F [HOWTO]
[SIZE=+1]Q2: How do I restore my phone to stock?[/SIZE]Visit the Back to stock thread. This has detailed instructions on how to flash factory firmware. If you have bricked your device or are trying to fix software issues then this is the go to method.
[SIZE=+1]Q3: Can I recieve OTA updates while my phone is rooted?[/SIZE]Short answer, no. If you have any modified files at the root level of your device this will break OTA. You may have to flash the stock firmware before you take an update.
[SIZE=+1]Q4: My phone won't connect to my PC. How do I fix this?[/SIZE]You might be experiencing driver issues. To resolve it take the following steps:
Download the LGUnitedMobile driver here
Open programs and features and delete the currently installed drivers
Launch the exe file of the drivers that you downloaded and let it install
Reboot your PC and try connecting your phone again.
If your still not connecting then try using PDAnet drivers. Again, delete the LG drivers you installed and launch PDAnet on your PC. Let the drivers install and try again.
[SIZE=+1]Q5: I have a f320/ isai/l-01f . Where is the development for my variant?[/SIZE]These variants aren't as widely supported as the other ones unfortunately. Many ROM devs support the f320 but the ISAI and l-01f don't get as much love. There are dedicated threads for these variants here:
LG isai LGL22 Central Index - TOT&DLL | KDZ | Root | Recovery | ROM | Discussion
AOSP for Japanese G2 L-01F
[SIZE=+1]Q6: Is it possible to sim unlock the Sprint G2?[/SIZE]Yes. See these threads:
Sim Unlock ZVG lollipop
Permanent SIM Unlock for LS980 (OTA, APN) JB 4.2.2, KK 4.4.2
[SIZE=+1]Q7: How do I flash a custom recovery?[/SIZE]If you are coming from stock you need to root your device first (see Q.1). Here are the recovery methods based on android version:
KitKat
Use Autorec from this thread. Pick the correct one for your variant.
Lollipop
Use the Autorec app from the playstore. You can find them here. There is a separate app for each variant so pay close attention to which one you use.
Launch the app and follow the instructions to reboot to recovery.
Jellybean
There are several methods of doing this. Here is the easiest one:
[RECOVERY] [TWRP] [FLASHIFY] Quick & easy[SIZE=+1]Q8: What is ADB and fastboot?[/SIZE]ADB stands for Android Debug Bridge. These are the android tools developed by Google for developers and users to connect devices to a PC and send commands to it. There's a detailed guide to ADB here.[SIZE=+1]Q9: What is Bump!!!?[/SIZE]Bump is a bootloader exploit developed by team Codefire. It's purpose (in a nutshell) is to allow KitKat bootloaders to load custom boot (kernel) and recovery images to allow the flashing of custom ROMs.
By bumping a boot.img the tool signs it using it's magic keys to trick the bootloader into thinking that it is, in fact an official boot.img.[SIZE=+1]Q10: I bricked my phone and it is now in fastboot mode. How do I fix this?[/SIZE]There are several ways to fix it. If you have download mode you can flash a stock image (see Q.2). You can also use the fastboot tools to flash over the damaged partitions (see Q.8).
@somboons has developed a utility called SRK Tools which has a function to fix fastboot mode, and do many other useful things. You can find his tool here.[SIZE=+1]Q11: I rooted my device and now I need to RMA it. Is there any way to unroot/hide root?[/SIZE]If your device is rooted then there will be a root flag in download mode. This will be there even if you unroot from within superuser.
To remove all traces of root you will need to flash the stock firmware again (see Q.2)[SIZE=+1]Q12: What is a bootstack and why is it important?[/SIZE]A bootstack is a set of partition images that are needed for android to boot. In the case of the G2 partitions need to be slightly modified because the LP bootloader will not load custom images. In other words, if you want to flash a custom recovery and ROM, you need a KK bootloader and bumped kernel and recovery images. Autorec does this automatically or you can flash your own hybrid bootstack [SIZE=+1]Q13: My phone is dead or my PC recognises my phone as QHSUSB_BULK/Qualcomm 9006/8 or security error. How do I fix this?[/SIZE]These errors occur when your device has mismatched/corrupt or missing partitions. This can occur by flashing the wrong ROM, Autorec or bootloader. (eg. nuking your bootloader will give you a security error.) In the case that you still have download mode, you can just flash a stock image to fix it. If your phone is not booting into any mode but it's recognized by your PC then pay attention to device manager to see how windows sees your phone. For QHSUSB_BULK see here and here.
Alternatively you can use the Srk Tools. For qualcomm 9006 see here For Qualcomm 9008 or if your phone is not recognized by PC (windows/mac OR linux) and does not boot then you may need to follow this guide to revive your phone.[SIZE=+1]Q14: How do I enter recovery with the button combination?[/SIZE]If you have a custom recovery you use the button combination to factory reset.
Power off the device
Hold volume down and power button until you see the LG logo
For JB/KK Hold volume down and power
For LL Hold volume down and volume up
Enter at the factory reset screen
[SIZE=+1]Q15: What is an EFS and why is it important?[/SIZE]Your EFS partition contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code and the very main IMEI address, radio settings, programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, etc. An EFS cannot be replaced. It is unique to every device and it is highly recommended that you back it up soon after rooting your device. See this thread for a how to. EFS Partition Backup and More [All G2 Variants[SIZE=+1]Q16: I updated my phone and now the touch screen is erratic and my IMEI is gone. What is happening?[/SIZE]This scenario is common to G2's that are refurbished with mixed parts of many G2 variants. Typically the vendor has used a motherboard from any random G2 variant and packaged it as a d802. It is fixable however, see this thread for more details on how to identify your model. You must get the real model number which is written on the bottom of the mainboard and then flash a stock image accordingly. Restoring your IMEI is trickier though. It is easy if you have previously taken an EFS backup (see Q.15). You can flash the EFS backup zip or use dd to restore modemst1 and 2.
Without an EFS backup you cannot restore a lost IMEI. There are methods that claim to work and they are worth exploring but there is nothing that is definitely known to restore a lost IMEI.*Forum Rules | New Users Guide | XDA Tour | Report PostsA special thanks to everyone who contributed to the production of this FAQ
Judgment Came....
There are a lot of people joining xda on daily basis, and there are a lot of repetitive questions being asked which fill up Development threads. Point them here. Feel free to ask or answer questions. Idea of this thread is to get users to help other users with their problems/questions. Please do not spoon feed, but rather point in the direction where that user can find an answer and educate himself
I do have the G2 fortunately, in order to make XDA a better place, I thought I'd open up a help thread for those who need it. I will be able to give lots of help to fellow G2 users. Hopefully some of the experienced G2 users help out on this thread, because it'd make everything easier. Thanks!
First thing first. I strongly advise you to read THIS thread before posting ANYTHING on XDA.
Then, have a quick look at the names of threads in post no2, you might find what you need right away.
For ROM issues please do mention in your post about:
ROM name
ROM version and base
kernel version and its settings
any mods applied on top of it
flashing "style" aka dirty or clean
something like this
...and be sure you have asked before on the ROM thread unless you have less than 10 posts on XDA
Third. The second post will be used to link to threads for some of the most common problems+fixes. You'll be surprised how much time and frustration it will save you in the future.
ASK ANY QUESTION HERE,adb, drivers, superCID, problems, mods etc...... You will either get an answer or will get pointed in the right direction.
No abuse towards noobs tolerated here! No question is stupid in this thread.
***I feel that a little OT is healthy to the success of this type of thread. The people here who help the most will develop a comradery therefore OT is allowed within reason. Common sense will be applied ***
HALL OF FAME
People who contributed most to this thread and helped countless number of people with their problems/questions. In no particular order.
@cuks
@xanthrax
@Sunandroid
@XxZombiePikachu
@z3pp3lin
@raptorddd
@Art Vanderlay
Special thanks:
Undercover
Xanthrax
XxZombiePikachu
Sunandroid
Thanks for this thread and I do need help here.
So I have barely unplugged three in a half hours ago from full charge and I have 79 percent right now. 21 percent drop in three hours. That's a ton.
I have the 12b rom which I manually got since I'm rooted and couldn't update via Verizon. And flashed the pure audio 2 mod but that's it
Sent from my VS980 4G using xda app-developers app
---------- Post added at 02:04 PM ---------- Previous post was at 02:04 PM ----------
I even hibernated everything through greenify
Sent from my VS980 4G using xda app-developers app
Hard reset it
Would i need to flash a jellybean baseband to go to stockish 4.2.2 from 4.4.2 with savoca boot,img recovery and kitkat baseband? Or am i good to just flash back?
Sent from my LG-D802 using XDA Premium HD app
wadamean said:
Thanks for this thread and I do need help here.
So I have barely unplugged three in a half hours ago from full charge and I have 79 percent right now. 21 percent drop in three hours. That's a ton.
I have the 12b rom which I manually got since I'm rooted and couldn't update via Verizon. And flashed the pure audio 2 mod but that's it
Sent from my VS980 4G using xda app-developers app
---------- Post added at 02:04 PM ---------- Previous post was at 02:04 PM ----------
I even hibernated everything through greenify
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
So you're using a custom rom right? In that case I'd suggest a full wipe then a clean flash followed by flashing PA or Banks gapps. I use those steps on my Nexus 4 and Nexus One (I don't have a G2), but I've never run into any battery issues
brainbeatuk said:
Would i need to flash a jellybean baseband to go to stockish 4.2.2 from 4.4.2 with savoca boot,img recovery and kitkat baseband? Or am i good to just flash back?
Sent from my LG-D802 using XDA Premium HD app
Click to expand...
Click to collapse
Well, I'm no expert at G2 stuff, but if your kitkat rom includes a different radio, then I would suggest that you do flash the jb baseband. Don't mark my words, double check the rom thread just to be sure
g2 framework
is it possible to embed g2 original framework in aosp roms so we can install original g2 apps with no problems?
Hi,
I'm searching for a new phone to buy and this one caught my eye. I have 3 questions.
Is there anything (bad) I should know about the phone before buying it? All the good points are well advertised and easily available to read about on the internet, but the bad things only surface after you used the phone yourself for a while. (No need to mention back buttons though).
Making a custom kernel on non-nexus devices is always a tad (or more) harder, I hear. Are there already (very) stable kernels available like you can expect to see on a nexus device?
Is there any G2 developer looking into/developing Ubuntu Touch for this device? I'm interested in Ubuntu for Android you see, and it'd be awesome if I can use it on this phone like on my gnex.
lugiank said:
is it possible to embed g2 original framework in aosp roms so we can install original g2 apps with no problems?
Click to expand...
Click to collapse
It's be very hard to accomplish that as porting manufacturer specific stuff is quite difficult.
Sent from my Nexus 4 using Tapatalk
I've got a Brazilian D805 here in India. Can someone please tell me if there is a date when KitKat is being rolled out?
I don't understand Brazilian and most of the translated entries are ambiguous.
Advanced Q: can I flash a D802 KitKat ROM for the D805? Is there a thread when I can follow the same?
flashed a nightly rom stuck in boot loop no recovery
I flashed the newest cm 11 nightly rom plus the gapps for the lg g2 ls980 with sprint. I cannot get it to recovery but i can get into download mode. ive tried the lg mobile support tool but it get stuck on downloading software. At this point i really just want to get the phone working again, i dont care how. please help it is the only phone that i have.
I have a european G2 (greek) on rooted stock and custom twrp recovery. If i want to update OTA do i have to revert to stock before updating? Can you tell me how to do that?
Στάλθηκε από το LG-D802 μου χρησιμοποιώντας Tapatalk
Wifi Hotspot and other questions
I purchased a Sprint LG G2. It has been rooted and unlocked. Unfortunately, the person I bought it from doesn't know much about the rooting process that was followed and he just followed instructions given to him by a friend. As far as I can tell, there is no custom ROM on the device. Here are my questions:
- At this moment, there is no Wi-Fi Hotspot option on my device. I'm planning to follow the instructions from here: http://forum.xda-developers.com/showthread.php?t=2675280. But this link is for non-activated devices. Question is: How do I know if my phone has or has not been activated?
- If I do decide to follow the instructions in the above link, what would be the best way to backup my device first? Would you recommend Titanium Backup?
- The 3G connection on the phone seems to be awfully slow. Is this a 'Unlocked Spring G2' issue? Is there anything I can do to fix it?
Thank you in advance for all your help.
HELP.. deleted my stock LG camera app
Hello all,
In a quest to improve everything about my phone I seem to have completely deleted my camera app!!! I was attempting to apply the upgrade to the software that can be found here: http://forum.xda-developers.com/showthread.php?t=2471900. I changed the names of the files and permissions exactly as said, rebooted, and poof the camera app was gone. I have since downloaded a third party app to replace it, but I'd like to have the stock app back. No, I did not back up immediately before, I know STUPID!
Any help?? There are great third party apps and I can get by, but thought I'd try.
Thanks!
Djalaal said:
Hi,
I'm searching for a new phone to buy and this one caught my eye. I have 3 questions.
Is there anything (bad) I should know about the phone before buying it? All the good points are well advertised and easily available to read about on the internet, but the bad things only surface after you used the phone yourself for a while. (No need to mention back buttons though).
Making a custom kernel on non-nexus devices is always a tad (or more) harder, I hear. Are there already (very) stable kernels available like you can expect to see on a nexus device?
Is there any G2 developer looking into/developing Ubuntu Touch for this device? I'm interested in Ubuntu for Android you see, and it'd be awesome if I can use it on this phone like on my gnex.
Click to expand...
Click to collapse
For what you are seeking, nexus devices will be your best bet. They have the easiest developing because of not needed custom code. I really like the G2, but for me, the kitkat update was a bust (battery wonky, lots of random reboots, audio issues), so I went back to stock rooted JB. Very nice device that is very stable, but I don't care about AOSP, if I did, I would have gotten N5. Almost everything can be done through being rooted and xposed modules these days.
android_nashville said:
Hello all,
In a quest to improve everything about my phone I seem to have completely deleted my camera app!!! I was attempting to apply the upgrade to the software that can be found here: http://forum.xda-developers.com/showthread.php?t=2471900. I changed the names of the files and permissions exactly as said, rebooted, and poof the camera app was gone. I have since downloaded a third party app to replace it, but I'd like to have the stock app back. No, I did not back up immediately before, I know STUPID!
Any help?? There are great third party apps and I can get by, but thought I'd try.
Thanks!
Click to expand...
Click to collapse
are you rooted, on a custom ROM? If you are on custom ROM you can just reflash ROM without wiping data and it will be added back. If stock, maybe someone can make you an apk you can install or the files can be pushed via adb.
nrfitchett4 said:
are you rooted, on a custom ROM? If you are on custom ROM you can just reflash ROM without wiping data and it will be added back. If stock, maybe someone can make you an apk you can install or the files can be pushed via adb.
Click to expand...
Click to collapse
Yea, I am rooted but am stock. I have a stock camera APK but when I try and install it just says "App Not Installed" over and over again. Reset permissions, put in privat_apps folder and no lock. May just have to live with third party... Camera Zoom Fx and Procapture are both good. Thanks!!
android_nashville said:
Yea, I am rooted but am stock. I have a stock camera APK but when I try and install it just says "App Not Installed" over and over again. Reset permissions, put in privat_apps folder and no lock. May just have to live with third party... Camera Zoom Fx and Procapture are both good. Thanks!!
Click to expand...
Click to collapse
You would probably have to push it via adb.
something along the lines of
adb push camera.apk /system/app
chmod 644 /system/app/camera.apk
reboot device
If you have an adb folder, put the camera.apk in the root of it, then run the commands. Should work.
You could also have a look at xdabbeb's camera mod. Might be able to get that to install.
http://forum.xda-developers.com/showthread.php?t=2548974
nrfitchett4 said:
For what you are seeking, nexus devices will be your best bet. They have the easiest developing because of not needed custom code. I really like the G2, but for me, the kitkat update was a bust (battery wonky, lots of random reboots, audio issues), so I went back to stock rooted JB. Very nice device that is very stable, but I don't care about AOSP, if I did, I would have gotten N5. Almost everything can be done through being rooted and xposed modules these days.
are you rooted, on a custom ROM? If you are on custom ROM you can just reflash ROM without wiping data and it will be added back. If stock, maybe someone can make you an apk you can install or the files can be pushed via adb.
Click to expand...
Click to collapse
nrfitchett4 said:
You would probably have to push it via adb.
something along the lines of
adb push camera.apk /system/app
chmod 644 /system/app/camera.apk
reboot device
If you have an adb folder, put the camera.apk in the root of it, then run the commands. Should work.
You could also have a look at xdabbeb's camera mod. Might be able to get that to install.
http://forum.xda-developers.com/showthread.php?t=2548974
Click to expand...
Click to collapse
Awesome, will give this a try.
---------- Post added at 03:35 PM ---------- Previous post was at 02:56 PM ----------
nrfitchett4 said:
You would probably have to push it via adb.
something along the lines of
adb push camera.apk /system/app
chmod 644 /system/app/camera.apk
reboot device
If you have an adb folder, put the camera.apk in the root of it, then run the commands. Should work.
You could also have a look at xdabbeb's camera mod. Might be able to get that to install.
http://forum.xda-developers.com/showthread.php?t=2548974
Click to expand...
Click to collapse
OK, I installed xabbebs update and it seemed to go fine, but no camera app still. I looked in settings->manage apps and camera is there!! Just no icon... any advice on how to get Camera back in my app drawer??? It just seems to be hidden.
---------- Post added at 04:06 PM ---------- Previous post was at 03:35 PM ----------
Finally fixed it. Turns out just moving the LGCamera.apk to system/apps instead of priv_apps did the trick. Thanks again for hte help!
miyagi241 said:
How is the buttons in the back?
Click to expand...
Click to collapse
They are so awesome and comfortable
Sent from my VS980 4G using xda app-developers app
Before you go ahead and start unlocking, flashing and rooting, there are things you should know. This thread is a general guide that will serve to explain most of those things.
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.
Table of Contents
A. The layers (Hardware, Firmware, Software)
B. Definitions
C. Troubleshooting Common Issues
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.
The Layers. How does everything come together?
Just like any other computing device there are 3 Layers to your phone. It helps to realize this prior to modifying your phone, so you are able to troubleshoot issues more effectively.
Layer 1 Hardware: The hardware layer is the physical components of your phone. That which you can touch, hold and see. This layer is the least likely to be modified unless you are a crazy super master level modder. Very few bother to mess with this layer so this layer tends to be the most stable with very little issues arising. The best way to make sure a problem is not related to the hardware layer, that is to say, a physical hardware problem where a physical component needs replacing, is to return all software and firmware to stock. This is typically done by running an RUU or manually reflashing stock firmware and software. There are instances where software or firmware modifications can affect the hardware. For example, if you overclock your CPU, the added heat could permanently damage the CPU and even other hardware components so be sure to take that into consideration.
Layer 2 Firmware: This layer is what allows the software to control the hardware in your phone, like a bridge between the two. There is firmware for just about every component of your phone, the camera, screen, radio, processor etc etc. This is the second least likely layer to be modified. S-Off is required to modify most, but not all, firmware files and rightfully so. Modifying firmware components can easily damage your phone if you do not understand what you're doing. In some cases a JTAGG repair can fix your phone from firmware modification damage, other times, only replacing physical components can repair the damage done. (Recovery and the kernel are technically part of the firmware layer but do not require S-Off to flash)
Layer 3 Software: The software layer consists of the "ROM" and applications on your phone. This is where most of the modification takes place and while modifying the software layer is the least likely to cause serious issues, it can still be dangerous. Flashing a ROM not intended for your device could easily put your phone into a bricked state. With SuperUser or Root access, software is capable of modifying the firmware layer of your device. It is up to you to decide what is safe and what's not safe. This is why rooting is not for everyone. How can you properly decide what is safe for your device without the proper knowledge?
Definitions
What is root?
Root, super user or su for short is a level of access giving you permission to read or write to folders, or partitions you could not have access to as a regular user. Think administrative access.
Consider a folder path “/sdcard/downloads/” If we break it down, “downloads” is a folder in “sdcard” and “sdcard” is one of the folders in “/” which is the “root” of the folder structure. As a regular user, one might not consider that folders other than sdcard exist in “/” as they are kind of hidden from us but rest assure they are there and this is typically where the android OS and firmware files are kept. Modifying these files can be extremely dangerous for your phone if you do not understand the modifications to the file you're making, and what steps you can take to recover from any issues you encounter.
What is an RUU?
RUU stands for ROM Update Utility. An RUU is used to reflash an existing firmware/software set or updated firmware/software set. An RUU will wipe everything and basically get your phone back to stock. Unless your phone is S-Off, you cannot run an RUU with an older firmware or software than those currently on your device. You can only run an RUU that matches your MID/CID unless you are S-Off and have SuperCID or have changed the MID/CID to match the carrier you are flashing. There may be differences in hardware/firmware between MIDs and CIDs so be mindful as this can lead to a brick. To properly run an RUU with S-On, you must also have stock recovery installed, the bootloader must be locked/relocked. BE VERY CAREFUL DOING THIS. It is not recommended to RUU or OTA after unlocking your bootloader unless you have to. If you are S-OFF you can RUU whether the bootloader is locked or not and if you are superCID, CID checks will be ignored so be sure to be mindful of the RUU you are running and that it will play nice with your phone.
What is an OTA?
OTA stands for Over The Air and implies an Over the air update distributed by your phone manufacturer, carrier or ROM developer. Unlike an RUU, an OTA will not typically wipe/factory reset your phone but can update your firmware and/or software set. To a apply a manufacturer/carrier released OTA you will need stock recovery and stock system apps installed. Your CID/MID must match that of the carrier/manufacturer your phone came from.
What is a ROM?
When the term ROM was first introduced it stood for Read Only Memory, however, most memory that claims to be Read Only nowadays is not like it was back then. Now a days it is not as complicated to write ROM as only permissions are in your way as opposed to the days when you were required to modify the hardware layer in some way to update the ROM chip. In this particular case, we are referring to the android software on your phone. Stock ROM would imply the manufacturer released ROM that came on your device when you purchased it. Custom ROMs are ROMs the are modified stock ROMs or ROMs built from android source code to. I think you get the idea. It's the device software or Operating System if you will. You should never flash a ROM that is not intended for the device you are flashing it to, this is very dangerous. Like, brick dangerous.
What is a nandroid backup?
A nandroid backup is a backup of your phone's current state. Like a snapshot or image of your phone's software. It includes the ROM currently flashed to your phone, the kernel, apps and settings. It does not include any firmware files other than the kernel and possibly the recovery. A nandroid is done with custom recovery and cannot be done with stock recovery. Taking a nandroid before you start messing with your phone is good practice. In fact, It's good practice to make nandroids before flashing a new ROM, or making any changes that may impact stability. This will ensure you always have a quick way to get back to having a usable phone. Obviously, a nandroid will not help in cases where you mess up firmware files like the radio firmware or hboot.
What is a kernel?
The kernel is the central point of an operating system. It contains the modules and settings necessary for the ROM or OS to work properly. Every Operating System has a kernel, including android. Just like ROMs there are custom kernels, with tweaks and the like that may improve or decrease performance/stability. Also, like ROMs, you should never flash a kernel not intended for your device. Very Dangerous!
What is a bootloader?
The bootloader is as the name implies, a device software/interface for handling boot operations it is contained within the hboot file. The bootloader screen has a few nifty features:
Gives you device information such as:
The bootloader state (locked, relocked or unlocked)
The Secureflag state (S-On or S-Off)
Your hboot and radio versions
Your Cid (only if you changed it)
Allows you to power down, reboot or boot your phone to android.
Allows you to factory reset your phone (Though should never really be used unless you are completely stock as you can properly factory reset in custom recovery)
Allows you access to the recovery
It gives you access to fastboot command operations you can send from your PC to your phone.
To boot to bootloader: Press and hold Power and volume up until the phone shuts off, then let go of power and volume up. Press and hold Volume down until your screen comes up in bootloader mode.
What is recovery?
Recovery is a software/User Interface that allows you to handle and make changes to your device, without having to boot the android OS. The stock M8 comes with a recovery that is quite limited but allows you to factory reset your phone and flash OTA updates which really is more than enough for the average user.
Those of us who want more from our phones, and modify them tend to flash custom recoveries with many extra features. I won't go into all the features they provide as the devs have websites, and you can visit them for more information. The two custom recoveries for the m8 include TWRP and Philz Touch. Both are very functional and choosing one is a matter of preference over anything else.
To flash a recovery image. Put the recovery image in your fastboot/adb folder and in the command prompt:
Code:
fastboot flash recovery recoveryfilename.img
You can find The latest:
TWRP for the M8 HERE
Philz Touch for the M8 HERE
To manually boot to recovery, boot to bootloader (Press and hold Power and volume up until the phone shuts off, then let go of power and volume up. Press and hold Volume down until your screen comes up in bootloader mode). Then select recovery in the bootloader menu.
What is S-Off/S-On?
This stands for Securewrite-on or Securewrite-Off. The name kind of gives some hints as to what it means. Having your bootloader unlocked, affords you the ability to to flash a custom recovery and custom roms as well as a custom kernel however, some people may need more. They may want to alter other system partitions. That is where S-Off comes in. It gives you full write access to all system partitons. It also forces a bypass for all security checks, such as those made by OTAs and RUUs, for CID and MID. S-Off is persistent. No matter if you RUU, OTA, Flash a ROM, Firmware, Factory Reset, S-Off will remain so until you use fastboot to reset the flag. I should say, if you don't know what you're doing, that is to say, if you are the type to follow instructions blindly on a thread, without much idea what is ACTUALLY Happening, what files you're modifying, you should not have S-Off. It should not concern you and that is that. S-Off can be dangerous. You have been warned.
What does a Factory Reset do?
A Factory Reset Clears the Cache, Dalvik Cache and Data Partitions. All settings will reset to default. User Apps (Apps you installed that did not com preinstalled with the ROM) will be removed. This will not restore your phone to when you purchased it. This will not relock your bootloader, Reset the S-Off flag, remove root, or downgrade your hboot. It merely affects the system and user settings and user apps.
What is fastboot?
Fastboot is a command line tool that allows you to manipulate certain parts of your phone from the bootloader. Your phone must be in fastboot mode and you must have the fastboot application and HTC drivers installed if you are on Windows. If you are on linux, the HTC driver is preinstalled.
Popular fastboot commands include:
Fatsboot devices (Lists devices connected for use with fastboot)
Fastboot flash recovery recovery.img (Flashes a recovery image)
Fastboot flash boot boot.img (Flashes a boot image)
Fastboot oem readcid (Shows the CID of the phone installed)
Fastboot oem writecid (Writes a new CID to your phone. Must be 8 Characters. Requires S-Off)
Fastboot oem rebootRUU (Puts the phone in RUU mode which is used for flashing firmwares and/or entire RUUs)
Fastboot reboot (Reboots your phone)
Fastboot reboot-bootloader (Reboots to bootloader)
Fastboot erase cache (Wipes the cache partition using fastboot. Good idea after flashing things via fastboot)
Fastboot help (Will list fastboot commands)
Fastboot boot imagefilename.img (Allows you to boot a recovery image or kernel image without actually flashing to your phone
allowing you one time access to the features without the headache of reflashing stock afterwards) Thanks to @garyd9 for suggesting I include this. Very convenient command.
What is ADB?
ADB is another command line tool used to manipulate your phone. The commands for ADB are way more extensive. ADB can only communicate with your phone while in a custom recovery or while the ROM is booted up with USB debugging turned on. The reason ADB is so much more extensive is because it allows you to remotely access your phone's terminal just like a linux terminal. You can use ADB to push or pull files to and from any partition (Some partitions will require S-Off), list devices, get a logcat, troubleshoot issues etc etc. For an extensive list of commands and how to use ADB I strongly suggest visiting http://developer.android.com/tools/help/adb.html
What is the CID?
CID stands for carrier ID. It's a string of letters and numbers, eight characters long that identify what carrier your phone is from. When you flash an OTA or RUU, The OTA or RUU checks for a few things, one of those things is the CID, to ensure you are flashing software intended for your device. Realistically, There's no hardware difference between the M8s (with the exception of CDMA vs GSM) so all firmwares/softwares should be compatible. With regards to radio firmware, your radio may function better with one firmware over another. There have been occasions with HTC where flashing an RUU or OTA with the wrong CID or SuperCID, while S-On would brick your phone. So try to be mindful of this and be careful.
Thanks to @garyd9 for suggesting I include this in my guide!
Some common CIDs include but are not limited to:
SuperCID: 11111111
HTC International: HTC__001
AT&T: CWS__001
ROGERS: ROGER001
VODAPHONE: VODAP001
T MOBILE: T-MOB010
TELESTRA: TELST001
Bell Canada: BM___001
What is a brick?
The term brick is sometimes thrown around a bit too casually. A brick is when your phone is no longer operable. It does not boot, there is no way to save it without resorting to Jtagg or replacing the nand chip or motherboard. If your phone powers on and something appears on your screen, your phone can almost always be saved. Be sure you know how to save your device before messing with your device.
Troubleshooting Common Issues
I flashed a ROM or Kernel and it's not booting! WHAT DO I DO!?
When this happens. There are actually a number of things to consider but first off, Hopefully you made a nandroid to restore from just in case the reason it doesn't boot is something not quickly or easily fixed.
1. Is the ROM you're flashing indeed intended for your device? ROMs you're flashing should be for the HTC One m8 International. You should not be flashing ROMs designed for the m8 Sprint or Verizon and should not be flashing ROMs designed for other models of phone. If the ROM you flashed is not for your device, best case scenario, it's not flashing properly. Worst case scenario, you have a brick. You will need to factory reset and wipe system then either flash a new ROM or restore a nandroid to get your phone up and running again.
2. Did you wipe Cache, Dalvik Cache, Data and System? (Don't wipe System for Kernel Install)
A factory reset will wipe all but system. You should wipe System manually in case the script for the ROM install does not do it or does it improperly. A factory reset is enough for a Kernel install. If you wiped system and just flashed a kernel, it's no doubt your phone is not booting.
* If you did not factory reset and wipe system, do so and then reflash your rom. It should then boot.
* If you wiped system to flash a kernel, you will need to reflash the rom, and then reflash your kernel again if you are flashing a custom kernel. (Note a GPE Kernel will not work on Sense and a Sense kernel will not work on GPE.
3. Did you matchup the Checksum? MD5 or SHA1 are usually posted on the ROM Download site/post. This allows you to check and make sure the integrity of the file you downloaded has been maintained. If The SHA1 or MD5 of the file you downloaded does not match what is posted, you have a corrupted file and should redownload. If you don't have a MD5 or SHA1 Checker, I suggest downloading one. Google MD5 or SHA1 Checker and you should find one. MD5 is most commonly used but it's up to the Dev as to which they post. Sometimes both. You only need to match one. (Linux comes with utilities for checking MD5/SHA1 called md5sum and/or sha1sum)
4. If you tried all these steps and it's still not booting, try another ROM. If no ROMs appear to be booting, you may be having an issue with your custom recovery. Redownload your recovery (Make sure it's the right one for your phone and check the checksum) Then reflash recovery, then use fastboot erase cache, boot to recovery and try flashing again.
5. If you tried all these and you're having issues, ask in the M8 Q&A!
I wiped everything and I don't have a ROM on my phone to flash! What do I do?
This is quite simple really.
Boot to recovery
Connect your phone to your PC
Make sure your ROM is on your PC and in your adb folder
Then use:
Code:
adb push romfilename.zip /sdcard/
Be patient, this could take a while, when it finishes you will get a confirmation with bytes in/bytes out.
Then flash.
Where can I go to find links to do all this cool stuff I want to do to my Phone!?!?!?!?
HERE!
Thank Yous!
Thanks to @garyd9
Thanks to @keithross39
This is a work in progress. I will be updating this as often as I can, trying to explain as much as I can for newer M8 owners who are not used to HTC or Android devices. If you have any suggestions for what I can put here, post here and let me know! Also, I'm not perfect, I make mistakes if I have/do make any, do not be shy! Let me know.
[08/18/2014] Partially updated and fixed spelling mistakes. More coming soon!
Hey fella, this is a good idea.
Thanks for taking the time to do this.
I am going to be getting the M8 in the near future, so reading up about the HTC specific stuff is really useful for me as I'm currently familiar with Samsung procedures and not a lot else. Most folks reading this should be familiar with the 'cross platform basics', so what you've covered so far should be enough........
But.....
Those (like me) who are getting an HTC device for the first time would probably benefit from more of a detailed description of the HTC side of things......maybe you could concentrate on expanding that information.......
Maybe you could include links to threads for s-off, rooting and/or anything else relevant?
Just my 2 cents worth....for what it's worth.....
Sent from my rooted debloated thingy
keithross39 said:
Hey fella, this is a good idea.
Thanks for taking the time to do this.
I am going to be getting the M8 in the near future, so reading up about the HTC specific stuff is really useful for me as I'm currently familiar with Samsung procedures and not a lot else. Most folks reading this should be familiar with the 'cross platform basics', so what you've covered so far should be enough........
But.....
Those (like me) who are getting an HTC device for the first time would probably benefit from more of a detailed description of the HTC side of things......maybe you could concentrate on expanding that information.......
Maybe you could include links to threads for s-off, rooting and/or anything else relevant?
Just my 2 cents worth....for what it's worth.....
Sent from my rooted debloated thingy
Click to expand...
Click to collapse
Thanks man! I welcome all suggestions! I will do my best to incorporate your suggestions
Sent from my HTC One_M8 using XDA Free mobile app
Great idea, thanks. I've been wondering what S-Off is for weeks but didn't want the flaming for asking a noob question!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Some possible additions:
What is "RUU"?
What is MID (model ID) along with a list of some common MID's
What is CID (carrier ID?) along with a list of some common CID's
How do the MID and CID relate to each other and how does the combination relate and/or interact with RUU. Related, of course, is the third part of the version number.
I was thinking of writing a guide myself, because I was so confused myself after coming from samsung, really nice.
Shebee said:
I was thinking of writing a guide myself, because I was so confused myself after coming from samsung, really nice.
Click to expand...
Click to collapse
Lol...ain't that the truth....
Sent from my rooted debloated thingy
Nice one
Very well done!
Sent from my HTC One_M8 using Tapatalk
I'm one of those who also came from Samsung (S4).
This is really great and easy to understand. This should be sticky :victory:
While I think the OP uses the term "ROM" incorrectly (Read Only Memory), I'll admit that's just me being picky. Otherwise, a very useful post... I've requested it be made sticky.
Take care
Gary
garyd9 said:
While I think the OP uses the term "ROM" incorrectly (Read Only Memory), I'll admit that's just me being picky. Otherwise, a very useful post... I've requested it be made sticky.
Take care
Gary
Click to expand...
Click to collapse
That's not being picky at all! Feel free to suggest any corrections. I welcome criticism and corrections.
Thanks for the recommendation!
Sent from my HTC One_M8 using XDA Free mobile app
exad said:
That's not being picky at all! Feel free to suggest any corrections. I welcome criticism and corrections.
Click to expand...
Click to collapse
LOL. I'm one of those people who goes nuts when people want to install "ROM's" on their phone. I keep reminding them that if it was really "Read Only Memory", that they wouldn't be able to overwrite it. Ever.
I do understand, however, that it's one of the misused terms these days. I guess it's kind of like saying you are "dialing a phone number." (There aren't any dials on our phones anymore. I haven't even seen a working rotary dial phone in years...)
Anyway - I'll stop with my OT bantering. Once I get more familiar with HTC devices I'll probably have some good suggestions for your posts.
Take care
Gary
garyd9 said:
LOL. I'm one of those people who goes nuts when people want to install "ROM's" on their phone. I keep reminding them that if it was really "Read Only Memory", that they wouldn't be able to overwrite it. Ever.
I do understand, however, that it's one of the misused terms these days. I guess it's kind of like saying you are "dialing a phone number." (There aren't any dials on our phones anymore. I haven't even seen a working rotary dial phone in years...)
Anyway - I'll stop with my OT bantering. Once I get more familiar with HTC devices I'll probably have some good suggestions for your posts.
Take care
Gary
Click to expand...
Click to collapse
Read only memory isn't a great name for it. If you've ever updated the bios on a pc, flashed a firmware update to a router, etc... you've written to read only memory. There are types that are truly read only but I can't think of a single practical example. And welcome to htc phones!
Sent from my HTC One_M8 using Tapatalk
lampel said:
Read only memory isn't a great name for it. If you've ever updated the bios on a pc, flashed a firmware update to a router, etc... you've written to read only memory. There are types that are truly read only but I can't think of a single practical example. And welcome to htc phones!
Click to expand...
Click to collapse
I'm old enough to remember (clearly) when you couldn't update the BIOS on a PC - you had to physically replace the BIOS chip. (Usually, they were socketed to make replacement a bit easier.) That was ROM. Also, early game consoles used true ROM in cartridges.
As for current practical example: a simple CDROM (not CD/RW) is, of course, read only.
I agree that it's not the best name lol but that is what it stands for....
Sent from my HTC One_M8 using XDA Free mobile app
Added this to my index thread
Hi guys! I am planning to buy an htc one m8 but can someone please tell me the different models out there? I don't want to end up buying the wrong one. Also is the dev one worth spending the extra money over the international? And is it the same model as the international one? Thanks in advance. I didn't know where else to post this. I didn't wanted to start a new thread.
Karan and all other users, please post questions in Q&A. Only things that should be posted here are suggested additions to this thread.
Also thread has been updated and more to come!
Part on RUUs is wrong...
An RUU can be run at any point and in any state (so long as you can get to the bootloader) as it completely replaces the entire system so doesn't matter if you don't have the stock recovery as it replaces it during the update process. Also, if you're S-OFF it means you can flash any RUU for any phone, handy to go between branded and unbranded software. OK, there's a risk of trying to flash an RUU from another device but if you do that you're a bit dumb!!
I frequent the JasmineROM and CyanogenMod threads in this forum and have noticed (and answered) many repeat questions: questions that have already been answered maybe a page or two back. I've noticed frustration in the answers to these questions (I've felt it myself), so I decided to start a new thread that will address the questions and provide the answers. It won't stop the questions from happening, but at least we can all just paste a link instead of writing the same paragraph over and over to people who don't seem to do any research.
---------------------------------------------------------------
Here's the format I'll be using for the questions and answers. I'd really appreciate it if suggestions could follow it, but it isn't necessary at all.
[SIZE="4"][B]Q: LE QUESTION[/B][/SIZE]
[SIZE="3"][I]A: ZE ANSWER[/I][/SIZE]
Sorry for not adding this in earlier.
---------------------------------------------------------------
(This may be in the wrong section, but I figured General would fit it best. Please move it if it's better somewhere else.)
---------------------------------------------------------------
I know I'm going to forget to include quite a few things. If you've seen a repeat question, I believe (I don't know for sure ) that replying to this post with at least the repeat question and then allowing me to edit it into this post will be a good way to go about this (I'll give credit with a name and link to the post).
---------------------------------------------------------------
Without further ado, here's the "FAQ":
Q: How do I root my Note?
A: http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
Q: How do I upgrade to the MM bootloader and modem?
A: http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
Q: I have no WiFi after using the latest version of CyanogenMod, JasmineROM, PaulPizz or any other Marshmallow-based ROM.
A: Make sure you have upgraded the bootloader and modem to Marshmallow. Guide here.
Q: On CyanogenMod, I'm losing LTE and only getting 3G.
A: Reboot into Recovery and then back to System. It won't fix it permanently, but it will restore LTE for a while.
A2: Delete the StraightTalk APN from your APN settings. (Obviously, you shouldn't do this if you have StraightTalk.) (Not everyone has a problem with the ST APN, but I figure I'll put this here.)
Q: Screen rotation isn't working on JasmineROM 6 or 7.
A: Many people have reported that this is a result of debloating. Not everyone has the issue, but those who have say one they remove Facebook and DT Ignite (among others), screen rotation breaks.
Q: Bluetooth audio is stuttering in CyanogenMod 13.
A: The workaround for this is to enable Daydream. That will prevent the phone from going to sleep, but will display a dark background with a clock, allowing you to still get a fast charge. The problem with BT audio lies in a CyanogenMod change that caused some problems with Bluetooth discovery upon device wake. hsbadr is working on a new build with the fix incorporated.
---------------------------------------------------------------
---- Thanks to @douger1957 || Post ----
Q: I'm already on Marshmallow with a locked bootloader. Is there hope for me?
A: Yes. You need to downgrade to Lollipop first. Flash the full firmware (thanks, @hsbadr!) on ODIN. Make sure that auto reboot is unchecked. When you get a "pass" in ODIN, boot into recovery and do a factory reset, otherwise you could get a bootloop. It takes a while for the first boot... upwards to 15 minutes... so be patient. Then you can start to unlock the bootloader. The bootloader must be unlocked before you can root.
Q: What ROMs can I flash?
A: That's a tough one. If you have a Lollipop unlocked bootloader you can only flash a ROM based on a Lollipop bootloader. Often the developer of the ROM will put the base of his ROM in the title of the thread as the bootloader firmware name (ie N910VVRU2BPA1) is a Lollipop firmware. Otherwise, you'll find the information at the lower left corner of the opening post. If you don't know, ask in that thread.
Subsequently, you must have an unlocked Marshmallow bootloader in order to flash a Marshmallow bootloader based ROM.
Confusing the issue more is the fact that it's possible to have a Marshmallow ROM use a Lollipop bootloader.
You can find all of the ROMs that are specifically for the N910V Note 4 variant (Verizon) here.
Q: I hear there are ROMs for other Note 4 variants. What's up with that?
A: True deal. Some of the other variants, the international models specifically, have been unlocked for awhile and there's a thriving development community. You can find those ROMs here. You've gotta know some stuff before you can flash one of their ROMs.
1) Stick with ROMs developed for the N910F and N910G variants. The radios are closest to ours. Flash a ROM for another variant and you're now a test pilot.
2) The same rules apply to their ROMs: Lollipop bootloader on your phone? Lollipop based ROM. Same for Marshmallow.
3) You'll need to flash a data fix to make their ROMs work on the Verizon network. Further, you may need to flash a kernel to make wifi work. I had luck with the Oscar kernel when I tried the Noble ROM last week.
(Note by Zacharee1: I've only had luck with the data fix on TouchWiz ROMs. AOSP ROMs, like CyanogenMod and Resurrection Remix, have problems with the data fix, resulting in reduced performance and still no cellular.)
Q: I've gotta, gotta, gotta have wifi calling.
A: At this time, you're pretty much stuck with a stock based ROM like Jasmine or PaulPizz. @hsbadr is working on getting it to work on CM13 but I'm waiting for other issues with that ROM to clear up and I am not current on its features. You will not find it on any of the international based ROMs.
(Note by Zacharee1: WiFi calling still does not work on CM. I have hopes for it in the future, but I may be moving to T-Mobile, where I'll probably have it anyway, so I won't be current on this either.)
Q: What are some tips about choosing and flashing custom ROMs on my Note?
A: Read these tips:
1) Find a ROM that interests you and has the features you can't live without. Most ROM developers are pretty thorough in the opening post or so regarding what you can expect.
2) Read the thread cover to cover. But Douger, some of those threads have hundreds upon hundreds of pages. Why? Because you'll know what issues others have had with the ROM and you'll find possible workarounds. You'll find out whether or not there are any showstoppers that'll keep you from using it as a daily driver.
3) Before you flash anything, do a full nandroid backup. In TWRP, check off all of the blocks. If crap blows up in your face, you can be using the phone again in about ten minutes of recovery time. Otherwise, you can spend hours setting the phone up again after flashing a ROM again.
4) Speaking of spending hours, plan on it. If you don't have the time, wait till you do because you;
5) Need to do a full wipe. That means data, system, cache and ART/Dalvik. Often when flashing ROMs, things don't get cleaned out properly, and artifacts will remain. Most ROM developers will include the instruction to wipe, which brings us to the next point;
5) Follow the directions exactly. Do not freelance unless you know what you are doing. That means flashing kernels, modems, bootloaders, etc. Follow the instructions in the order they are presented. If you don't understand any of the instructions, don't proceed until you do.
6) Perform a factory reset after flashing a new ROM but before booting.
7) Before rooting, I strongly suggest that you move anything you have stored on internal storage such as pictures or music, off the phone. Before you flash your first ROM, format the internal storage. The root process involves Chinese software and if you're not one who keeps up with the news, the Chinese are notorious hackers. Make sure you get all of the cooties off your phone.
8) It takes a long time for a phone to fully boot once you've flashed a ROM. Usually, it's over in about ten minutes but twenty minutes isn't unheard of. Be patient and resist the urge to pull the battery.
9) If you can get into recovery and download modes, you did not "brick" your phone. Contain your panic and think things out. The best advice I can give is to try to get back to the last time things worked.
Q: How do I know whether to use ODIN or flash in recovery?
The developer will usually tell you. But, if the file you're flashing has a ".tar" or ".md5" extension, it's flashed in ODIN. Often that file is zipped (extension ".7z") and needs to be unzipped. If the file has a .zip extension it's flashed in recovery.
Q: What is Odin?
A: Not the Norse god in this case. http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Q: What is TWRP?
A: TWRP is what's known as a custom recovery, which is what allows you (for the most part) to flash custom ROMs and packages to your phone. Each build of TWRP is device-specific. Make sure you downloaded the correct version for your device. http://www.xda-developers.com/how-to-install-twrp/
Q: What should I do if I'm having an issue with the ROM?
A: PLEASE don't just complain that something isn't working. See if you can fix it yourself; maybe it was something you installed or changed? If it's not unique to you or even a clean flash doesn't fix it, then you should look into providing some logs for the dev. Check out LogCat. Ask the developer how they want the log delivered.
Don't complain if you dirty flashed the ROM (meaning you didn't wipe /system and /data before flashing -- leaving internal storage and SD card alone is perfectly fine). While it's possible your issue is something wrong with the ROM, the developer will just ignore you. Also don't lie about having done a clean flash. It's pointless, and the developer can probably tell from any logs you provide that you actually dirty flashed. It's not fair to others if you take up their time by helping you try to fix a problem that can be solved by flashing the ROM the way it was meant to be flashed.
Q: Things on my screen are too small/large.
[SIZE="3"[I]A: You can actually change what's known as the DPI. Here's a method for that for the Note 4 on TouchWiz: [url]http://forum.xda-developers.com/note-4-verizon/development/solution-dpi-change-camera-dialer-t3422699[/url][/I][/SIZE]
[SIZE="4"]Q: I really like the ROM I'm using. Is there something I can do to help the developer out?
A: Luckily for you (and the dev), there is. Many developers will have a DONATE button in the sidebar on their posts. Remember, this is the only way most of them get anything from what they do. Developing these ROMs is usually done as a hobby, and considerable time and effort are put into producing something for you to use on your phone.
If you can't donate (or don't want to -- it's understandable), hit the THANKS button on the developer's posts. It's a nice gesture that shows you are interested in their work and that you would like to see more.
Q: What's this Xposed thingy I've heard about?
A: Xposed is a framework that allows almost unlimited customization and feature unlocking. As such, it is not something to play with lightly. This is the forum devoted to Xposed. This is where you'll find the framework, installers, and the modules.
@wanam has done much of the development for Samsung phones. Here's where you'll find his work. Since his is made especially for Samsung ROMs, I strongly recommend sticking with his base until you're more comfortable with using Xposed.
Q: There are so many downloads for Xposed. Which one do I use?
A: As always, RTFT (read the f'ing thread). However, here's a shortcut. Note 4 phones are ARM. Version 86 is current. Use that for AOSP based ROMs. Use the "alt" version for TouchWiz based ROMs. You need both the framework and the installer.
---------------------------------------------------------------
It's not very much so far (it's hard to come up with this on the spot), but I hope you'll all help out by posting the other frequent questions you see around these forums.
Q: What's this Xposed thingy I've heard about?
Xposed is a framework that allows almost unlimited customization and feature unlocking. As such, it is not something to play with lightly. This is the forum devoted to Xposed. This is where you'll find the framework, installers, and the modules.
@waram has done much of the development for Samsung phones. Here's where you'll find his work. Since his is made especially for Samsung, I strongly recommend sticking with his base until you're more comfortable with using Xposed.
Q: There are so many downloads. Which one do I use?
As always, RTFT (read the f'ing thread). However, here's a shortcut. Note 4 phones are ARM. Version 86 is current. Use that for TouchWiz based ROMs. Use the "alt" version for ASOP based ROMs. You need both the framework and the installer.
douger1957 said:
Q: I'm already on Marshmallow with a locked bootloader. Is there hope for me?
Yes. You need to downgrade to Lollipop first. Flash the full firmware (thanks, @hsbadr!) on ODIN. Make sure that auto reboot is unchecked. When you get a "pass" in ODIN, boot into recovery and do a factory reset, otherwise you could get a bootloop. It takes a while for the first boot... upwards to 15 minutes... so be patient. Then you can start to unlock the bootloader. The bootloader must be unlocked before you can root.
Q: What ROMs can I flash?
That's a tough one. If you have a Lollipop unlocked bootloader you can only flash a ROM based on a Lollipop bootloader. Often the developer of the ROM will put the base of his ROM in the title of the thread as the bootloader firmware name (ie N910VVRU2BPA1) is a Lollipop firmware. Otherwise, you'll find the information at the lower left corner of the opening post. If you don't know, ask in that thread.
Subsequently, you must have an unlocked Marshmallow bootloader in order to flash a Marshmallow bootloader based ROM.
Confusing the issue more is the fact that it's possible to have a Marshmallow ROM use a Lollipop bootloader.
You can find all of the ROMs that are specifically for the N910V Note 4 variant (Verizon) here.
Q: I hear there are ROMs for other Note 4 variants. What's up with that?
True deal. Some of the other variants, the international models specifically, have been unlocked for awhile and there's a thriving development community. You can find those ROMs here. You've gotta know some stuff before you can flash one of their ROMs.
1) Stick with ROMs developed for the N910F and N910G variants. The radios are closest to ours. Flash a ROM for another variant and you're now a test pilot.
2) The same rules apply to their ROMs: Lollipop bootloader on your phone? Lollipop based ROM. Same for Marshmallow.
3) You'll need to flash a data fix to make their ROMs work on the Verizon network. Further, you may need to flash a kernel to make wifi work. I had luck with the Oscar kernel when I tried the Noble ROM last week.
Q: I've gotta, gotta, gotta have wifi calling.
At this time, you're pretty much stuck with a stock based ROM like Jasmine or PaulPizz. @hsbadr is working on getting it to work on CM13 but I'm waiting for other issues with that ROM to clear up and I am not current on its features. You will not find it on any of the international based ROMs.
---------- Post added at 06:17 PM ---------- Previous post was at 05:55 PM ----------
Douger's tips for success:
1) Find a ROM that interests you and has the features you can't live without. Most ROM developers are pretty thorough in the opening post or so regarding what you can expect.
2) Read the thread cover to cover. But Douger, some of those threads have hundreds upon hundreds of pages. Why? Because you'll know what issues others have had with the ROM and you'll find possible workarounds. You'll find out whether or not there are any showstoppers that'll keep you from using it as a daily driver.
3) Before you flash anything, do a full nandroid backup. In TWRP, check off all of the blocks. If crap blows up in your face, you can be using the phone again in about ten minutes of recovery time. Otherwise, you can spend hours setting the phone up again after flashing a ROM again. Douger also creates a full nandroid backup when he's got his phone all set up with the apps loaded, just in case the ROM blows up or something.
4) Speaking of spending hours, plan on it. If you don't have the time, wait till you do because you;
5) You need to do a full wipe. That means data, system, cache and ART/Dalvik. Often when flashing ROMs, things don't get cleaned out properly, and artifacts will remain. Most ROM developers will include the instruction to wipe, which brings us to the next point;
5) Follow the directions exactly. Do not freelance unless you know what you are doing. That means flashing kernels, modems, bootloaders, etc. Follow the instructions in the order they are presented. If you don't understand any of the instructions, don't proceed until you do.
6) Perform a factory reset after flashing a new ROM but before booting.
7) Before rooting, I strongly suggest that you move anything you have stored on internal storage such as pictures or music, off the phone. Before you flash your first ROM, format the internal storage. The root process involves Chinese software and if you're not one who keeps up with the news, the Chinese are notorious hackers. Make sure you get all of the cooties off your phone.
8) It takes a long time for a phone to fully boot once you've flashed a ROM. Usually, it's over in about ten minutes but twenty minutes isn't unheard of. Be patient and resist the urge to pull the battery.
9) If you can get into recovery and download modes, you did not "brick" your phone. Contain your panic and think things out. The best advice I can give is to try to get back to the last time things worked.
10) Douger does not use Titanium Backup to restore his apps, especially if he's flashing a different ROM than the one he was on when he created that backup.
11) If you didn't do a full wipe before you flashed that ROM (dirty flash) do not complain about things not working properly on the developer's thread. Do send the developer a logcat so he can look into the issue.
---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------
Q: How do I know whether to use ODIN or flash in recovery?
The developer will usually tell you. But, if the file you're flashing has a .tar5 extension, it's flashed in ODIN. Often that file is zipped and needs to be unzipped. If the file has a .zip extension it's flashed in recovery.
Click to expand...
Click to collapse
Added. Thanks!
Zacharee1 said:
Added. Thanks!
Click to expand...
Click to collapse
From now on, I'm just going to link all questions to this thread. If they're too thick to use it, tough cookies. It'll be all they get from me. I just reported this post to see if we can get it stickied.
And thank you for fixing my boo boos.
---------- Post added at 07:42 PM ---------- Previous post was at 06:49 PM ----------
What you need to know about ODIN.
Everything you wanted to know about TWRP but were afraid to ask yo mama. TWRP is phone specific. Don't try to flash any old copy of TWRP.
Giving back to the community. How to logcat.If you're having an issue with the ROM you're on and you did a clean install, generate a logcat, then PM the developer and ask him how he'd like it delivered. It's basically a system dump which shows where errors were generated. It's helpful to narrow down the bugs. Don't fib about doing a clean install. The logcat knows, and is worthless to the developer.
How to change your DPI Thanks, @charly211297!
Almost forgot the most important thing: If you enjoy using the ROM or kernel and have gotten value from it, please consider sending the developer some beer money. Most of these guys spend considerable time in development and fixing bugs. Remember that no one here gets paid for what they do and if nothing else, hit that thanks button.
douger1957 said:
From now on, I'm just going to link all questions to this thread. If they're too thick to use it, tough cookies. It'll be all they get from me. I just reported this post to see if we can get it stickied.
And thank you for fixing my boo boos.
---------- Post added at 07:42 PM ---------- Previous post was at 06:49 PM ----------
What you need to know about ODIN.
Everything you wanted to know about TWRP but were afraid to ask yo mama. TWRP is phone specific. Don't try to flash any old copy of TWRP.
Giving back to the community. How to logcat.If you're having an issue with the ROM you're on and you did a clean install, generate a logcat, then PM the developer and ask him how he'd like it delivered. It's basically a system dump which shows where errors were generated. It's helpful to narrow down the bugs. Don't fib about doing a clean install. The logcat knows, and is worthless to the developer.
How to change your DPI Thanks, @charly211297!
Almost forgot the most important thing: If you enjoy using the ROM or kernel and have gotten value from it, please consider sending the developer some beer money. Most of these guys spend considerable time in development and fixing bugs. Remember that no one here gets paid for what they do and if nothing else, hit that thanks button.
Click to expand...
Click to collapse
I'll add these after dinner. Thanks again.
Wanna mess with your kernel? Here's a pretty good primer. As always backup first.