Related
.Hey guys I'm new in this world of rooting ...maybe know someone how to put Omega 7.2 ROM into the Samsung Galaxy Note 2 SGH-I317M. ????
First off there is a Q&A section for questions. They don't go here.
Second that's an international rom you can't just simply flash it like the roms in the Development section. This link can tell you how to port it but if you are new you probably shouldn't try it.
http://forum.xda-developers.com/showthread.php?t=2018411
Sent from my SAMSUNG-SGH-I317 using xda premium
NightHawkUndead said:
First off there is a Q&A section for questions. They don't go here.
Second that's an international rom you can't just simply flash it like the roms in the Development section. This link can tell you how to port it but if you are new you probably shouldn't try it.
http://forum.xda-developers.com/showthread.php?t=2018411
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
NightHawk hit the nail on the head. It would be best for you right now to read up and learn as much as you can about how the forum works as a whole and how development and custom roms recoveries etc work in general.....Here is a good place to start!
My note 2 is on its way,in the mean time ill be reading alot.
Sent from my Desire HD using xda premium
lamartino said:
.Hey guys I'm new in this world of rooting ...maybe know someone how to put Omega 7.2 ROM into the Samsung Galaxy Note 2 SGH-I317M. ????
Click to expand...
Click to collapse
A lot of us would suggest you take a bit of time to read up on what you will need. I short a safe bet is to read twice and flash once. Doing any sort of flashing will void your warranty and you run the risk of damaging your phone. Granted most mishaps are fixable with knowledge and experience. For you however, having a bootloop or a soft brick would not be fun.
I suggest you get the proper drivers for your version of the n2
I suggest you read up on how to root the note 2: read the entire thread...yes it is repetitive,but at least you get an idea of what can go wrong and how to fix it be reading what happened to others. Then decide on what recovery you would like....read up on cwm or twrp and how to install them properly. once you have done all that...then it is time to flash a custom rom.
I think I would recommend you do a bit more reading before deciding wether rooting and flashing a custom rom is for you
There is a lot to absorb when first looking to install a custom rom. I'm a visual person so I like youtube a lot. When you find the forum that suits your particular device, there will usually be a thread something along the lines of "all you need to know about (your phone here)". My own method of learning was to make a list of each individual task that I needed to do and then youtube it to see someone doing it in person so I can get an idea of what it looks like.
Usually the steps to a custom rom are:
1) Root:
methods can differ among devices and developers (youtube your phone for root)
2) Install a custom "recovery"
will typically be either Clockworkmod or TWRP. I've only ever used clockworkmod but people say good things about TWRP also. The custom recovery will be where you "flash" (install) the rom as well as perform other functions such as wipe casche, wipe dalvic, fix permissions, etc., all of which are fairly self explanatory once you finally boot into the recovery, but again, youtube your phone for all of these things. Even seeing it on other phones can be a big help also, as long as what you are trying to accomplish is the same between the devices.
3)Pick a rom, download it to your phone, boot into recovery and follow the directions that the developer will leave in the OP. Someone mentioned read twice, flash once. Great advice. Make sure to have all your ducks in a row and are confident about each step you will be taking. Skipping a step or doing it incorrectly can cause serious headaches and can derail you for hours trying to figure out how to fix it if you are not already familiar with what to do.
Best of luck!!!
topshelf95 said:
There is a lot to absorb when first looking to install a custom rom. I'm a visual person so I like youtube a lot. When you find the forum that suits your particular device, there will usually be a thread something along the lines of "all you need to know about (your phone here)". My own method of learning was to make a list of each individual task that I needed to do and then youtube it to see someone doing it in person so I can get an idea of what it looks like.
Usually the steps to a custom rom are:
1) Root:
methods can differ among devices and developers (youtube your phone for root)
2) Install a custom "recovery"
will typically be either Clockworkmod or TWRP. I've only ever used clockworkmod but people say good things about TWRP also. The custom recovery will be where you "flash" (install) the rom as well as perform other functions such as wipe casche, wipe dalvic, fix permissions, etc., all of which are fairly self explanatory once you finally boot into the recovery, but again, youtube your phone for all of these things. Even seeing it on other phones can be a big help also, as long as what you are trying to accomplish is the same between the devices.
3)Pick a rom, download it to your phone, boot into recovery and follow the directions that the developer will leave in the OP. Someone mentioned read twice, flash once. Great advice. Make sure to have all your ducks in a row and are confident about each step you will be taking. Skipping a step or doing it incorrectly can cause serious headaches and can derail you for hours trying to figure out how to fix it if you are not already familiar with what to do.
Best of luck!!!
Click to expand...
Click to collapse
well done and i completely agree, but for someone who's so new you musn't forget to install the drivers for the device you have onto your pc or laptop or whatever is going to run Odin for you.... no drivers is the easiest and fastest way to ensure your shiny new device is on the short bus to not working right
it is often overlooked and ppl presume that they just do it - installing the drivers that is - and it's often mentioned in the rooting thread, but only in passing.
if you do not have the proper drivers your 700+ dollar device will not last long so do yourself a favor and make sure you have them installed properly and that your computer detects the device properly
when you plug into odin you should see a yellow background with COM and a number in it (changes depending on the usb port you are plugged into) if you don't have that, don't click the start button cuz you gonna be in the hurt locker in all likelihood even if you follow the instructions to a T.
I'm relatively new to all of this, only rooting my Evo, and now my Note 2.
I cannot stress enough how correct all the previous replies are. Read everything you can about your device and rooting in general. Use Youtube. Use this forum, use any information you can find. Learn the language(it can be tricky). Learn as much as possible and ask questions....just make sure you look for the answers before asking them.
Once you feel comfortable, the Devs do a solid job of making it easy for us, follow the steps and you should have success.
Here is a link to some terminology.....make sure to thank ThC23!
http://forum.xda-developers.com/showthread.php?t=1394458
You will make mistakes then become a pro. We all battled endless nights of fixing our devices after misreading one line.
Sent from my GT-N7105 using xda premium
Hey guys, this is my first HTC device. I've been reading through the threads here and in the intl forum and I just wanted to get a little info in one place as to what we can flash for this device. I sent mine off to someone with a Java Card, so now that I'm good to go, I wanted to see what all I (and other VZW users) can do at this early stage in the game. I know that until there is an easier way to S-Off/root/etc than sending your device to someone it is still kinda rocky as to development on this particular device, but I've heard mixed reviews on what ROMs/kernels are good to flash.
I assume that as long as I've got a custom recovery, flashing ROMs on this device would be the same as the other devices I've used... just pick the file in TWRP and flash, right?
As far as ROMs go, I've read that ViperOne works, along with InsertCoin with nothing extra.. just flash and go apparently. As for other ROMs, a little editing and some files from the stock VZW ROM should make them work, right? What files exactly would be needed?
Basically, if you've flashed anything, post your results here. What works, what doesn't, anything I should do before I start flashing myself. Any good threads I should read before I jump in. Thanks guys!
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
jtommyj said:
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
Click to expand...
Click to collapse
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
lordcheeto03 said:
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
Click to expand...
Click to collapse
Well first thing you need to have a custom recovery flashed.
Then you would need to backup your stock system. If you are in a soft brick then volume up and power being held at the same time should get you out of it.
There should not be a need to refresh firmware since the original firmware is all we have. I do believe an Ruu is being worked on currently.
Final word- if you're unsure,don't!!
I followed instructions to root it and its rooted, but have never been able to get Cyanogenmod to Install (I always get the same error everyone else does), and when I try to check out different ROMS, no one even posts many pics to show what the difference will be to use that ROM.
My phone looks the same as before and I'm just using ADW launcher to set it up the way I want it to look.
So how can I tell exactly what point of rooting my phone has reached? Do I actually have a different ROM, etc? I don't know much about this stuff and I'm not bricking my phone messing around with it until I know exactly where to start.
What custom recovery and bootloader are currently loaded on the phone?
kmodek said:
So how can I tell exactly what point of rooting my phone has reached? Do I actually have a different ROM, etc?
Click to expand...
Click to collapse
Hi!
Go to your phone's System Settings --> About phone.
In there, you should be able to figure out which Android version is currently installed on your phone; if you have a custom ROM, most of the time ROMs developers will also add an additional line somewhere on that screen to tell exactly what revision of their ROM is installed. If not, you may be able to grab some more information by checking your build number or your kernel revision.
If you tap a few times on where it says Android Version, under Settings>More>About Device , it usually does a little animation of the rom version. Im trying to decide on a rom so mine is kit kat 4.2.2 at the moment and dislpays an Android logo in the Kit Kat logo style.
Since the bootloader version is not displayed on the About Phone page, you will need to determine that with another method. A simple way would be with the Samsung Info app from the PlayStore, the one posted by vndnguyen.
I personally use Terminal Emulator commands to determine phone info.
Code:
getprop ro.bootloader
getprop | grep version.baseband
I got the app from the Play store and it shows I'm on 4.4.2, but that the Knox has been tripped (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
kmodek said:
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
i was watching youtube videos of reviews of the different custom ROMs gave a good idea on the features and layout of each rom. I as well am having difficulty deciding on a ROM to flash as this is my first smart phone and am new to it. ive been reading and watching a bunch of tutorials but finding information on whats currently stable for our particular phone can be somewhat dated. i know moderators want to avoid a "best roms" thread but for those of us just starting out with a rooted phone it sure would be handy to have opinions on what ppl use for the SGH-I747 and why, so its easier to decide on one.
is it reccommended to upgrade or downgrade? in order to compare ROMs its watching a video for 15 min to see what features it had at the time the vid was made and reading the developer forums on each mod to see what bugs are present in the current release but its not all compiled anywhere. its that or randomly flash ROMs on there to test them out and risk making mistakes. its usually always better to have advice from those with expertise and perhaps avoid making commonly made mistakes. ive read a bunch of helpful and handy guides on here but doesnt seem any way to easily compare roms or get feedback on what users have decided on sticking with or anything additional specific to this phone that should be considered before flashing certain ROMs.
kmodek said:
I got the app from the Play store and it shows I'm on 4.4.2, but that the Knox has been tripped (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
this thread may help to explain some badic things.
http://forum.xda-developers.com/showthread.php?t=2343223
my advice , for what its worth ...
1) READ READ READ
2) make a backup of your current setup so you have it to fall back on.
3) NEVER downgrade your bootloader , flash any ROM/kernel not meant for your device (sure way to brick it).
theres always risk when flashing anything , but the risks can be minimized by understanding what your doing , or rather the process.
as far as flashing roms , its pretty simple once you understand it (as with most things. lol). reading thru a ROMs thread will give a general idea of any features , issues that the users have. the OP , first post ; will tell you alot about the ROM/features.
good luck and happy flashing.!
"all i can really do , is stay out of my own way and let the will of heaven be done"
kmodek said:
.... (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
The act of rooting does not outwardly change the look and feel of a ROM in any way. It's what you do after rooting that makes the difference.
Some like the Stock Rom of a device and/or do not want to lose some of its unique features. These people will root but not flash a custom ROM.
I've had two android phones and one tablet. Initially I root a new device but leave it on the stock ROM. At that time I will use an app that requires root to freeze any of the pre-installed apps that I don't use (My definition of bloat.) I don't remove/delete them at the beginning. If freezing them breaks some other functionality I want that app still on the device so that I can unfreeze it and make everything work again. Both of my phones have been Samsungs, a SGS Captivate and a SGS3. After a while on rooted stock I have changed to custom ROMs on each. The Captivate went from stock to CyanogenMod to a CM derived ROM. The SGS3 went from stock to a re-themed, custom ROM based on stock but with much removed (carrier bloat) and some other functions added. I expect to soon change to a later version of the same ROM with even more removed. Others want to have a ROM with every bell and whistle possible to have present. It's all individual preference.
havok6669 said:
i was watching youtube videos of reviews of the different custom ROMs gave a good idea on the features and layout of each rom. I as well am having difficulty deciding on a ROM to flash as this is my first smart phone and am new to it. ive been reading and watching a bunch of tutorials but finding information on whats currently stable for our particular phone can be somewhat dated. i know moderators want to avoid a "best roms" thread but for those of us just starting out with a rooted phone it sure would be handy to have opinions on what ppl use for the SGH-I747 and why, so its easier to decide on one.
is it reccommended to upgrade or downgrade? in order to compare ROMs its watching a video for 15 min to see what features it had at the time the vid was made and reading the developer forums on each mod to see what bugs are present in the current release but its not all compiled anywhere. its that or randomly flash ROMs on there to test them out and risk making mistakes. its usually always better to have advice from those with expertise and perhaps avoid making commonly made mistakes. ive read a bunch of helpful and handy guides on here but doesnt seem any way to easily compare roms or get feedback on what users have decided on sticking with or anything additional specific to this phone that should be considered before flashing certain ROMs.
Click to expand...
Click to collapse
There are so many variations on what is possible that a compilation thread to cover all situations would seem as huge as wikipedia. Your approach, reviewing videos and checking rom OPs, has merit but it also has limitations. Unfortunately some of the devs give you almost no information about the features and customizations of their ROMs. Others will simply state that they have made a change or two to some base, expecting you to be familiar with the base. Which means a lot of more reading/reviewing for a person new to customizing their phone.
To advise any one questioner on what can be installed on their phone a responder must first know what bootloader and modem is on the device, are you already rooted, do you have a custom recovery installed yet, are you willing to risk breaking your warranty; the list goes on. Then the hard part comes - they have to recommend something that is in the realm of what you are expecting, even if you do not know what you are expecting.
dawgdoc said:
To advise any one questioner on what can be installed on their phone a responder must first know what bootloader and modem is on the device, are you already rooted, do you have a custom recovery installed yet, are you willing to risk breaking your warranty; the list goes on. Then the hard part comes - they have to recommend something that is in the realm of what you are expecting, even if you do not know what you are expecting.
Click to expand...
Click to collapse
well i made sure i learned a bunch before even attempting to ask a question so i got as much as possible prepared i'll try to provide the best information i can. my phone is rooted with superuser su2.0 i have cwm 6.0.1.2 installed, ive done a cwm nandroid backup which i copied to my pc as well as a backup of my efs folder and done a titanium backup as well. i have odin 3.07 on my pc and am currently running kitkat 4.4.2 on my sgh-i747m (sasktel version) currently trying to figure out how to determine the modem and bootloader versions . i followed the galaxys3root.com guide galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new and the highonandroid youtube vid in order to root my phone and made sure i read re read and was very cautious to follow instructions to the letter also read some worst case scenario information first like how to cause a phone to become bricked and how to fix it should it happen etc so before ive done anything else ive made sure to back everything up and ask a few more questions befor ei take the final plunge :] as for what ROM would tickle my tailfeathers was liking how carbon looked but it seems it hasnt been maintained :[ something good on battery life that runs fast n stable and is has a bunch of customization features is what i was hoping for. the main reason i decided to root my phone was to learn more about it and customize my os away from the stock look and feel and unlock some of the potential it has that a stock rom would otherwise neglect. the more i learn the sooner i can help by giving back to the community :]
havok6669 said:
....
my phone is rooted with superuser su2.0 i have cwm 6.0.1.2 installed, ive done a cwm nandroid backup which i copied to my pc as well as a backup of my efs folder
Click to expand...
Click to collapse
CWM 6.0.1.2 is a bit dated, their latest version is 6.0.4.7 and even it is a bit dated. You may find that to flash a current ROM you will need to update CWM. For some of the newer ROMs even 6.0.4.7 is not current enough. You will need to change to Philz Recovery, based on CWM, or TWRP. Bear in mind that if you change to TWRP you will not be able to use your CWM nandroid. I don't know if the same applies to Philz Recovery.
https://www.clockworkmod.com/rommanager
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/ (page is down at the moment)
http://teamw.in/devices/samsunggalaxys3canada.html (d2can TWRP, though I think you can use d2att, check before using d2att)
There is definitely a newer version of SuperSu (by Chainfire) available. It went through a lot of development to handle issues related to Knox that came out with Touchwiz 4.3. SuperSu is now up to 2.49 and I would recommend upgrading it no matter what ROM you should end up choosing. http://forum.xda-developers.com/showthread.php?t=1538053 There is a zip you can flash from you current CWM there.
It's not a bad idea to have several fallbacks for imei/nvdata. Give this tread a look: http://forum.xda-developers.com/showthread.php?t=1852255&highlight=synergy+nvbackup I used the reboot nvbackup from there and EFS Backup developed by wanam
... am currently running kitkat 4.4.2 on my sgh-i747m (sasktel version) currently trying to figure out how to determine the modem and bootloader versions .
Click to expand...
Click to collapse
Sasktel has released 4 versions of Android 4.4.2, each with a different bootloader and modem. Any should be fine no matter what ROM you choose, even a Lollipop based ROM. But to check you can get Phone Info - Samsung by vndnguyen from the Playstore. Or you could use a pair of commands in Terminal Emulator
Code:
getprop ro.bootloader
getprop | grep version.baseband
... as for what ROM would tickle my tailfeathers was liking how carbon looked but it seems it hasnt been maintained :[ something good on battery life that runs fast n stable and is has a bunch of customization features is what i was hoping for. the main reason i decided to root my phone was to learn more about it and customize my os away from the stock look and feel and unlock some of the potential it has that a stock rom would otherwise neglect. the more i learn the sooner i can help by giving back to the community :]
Click to expand...
Click to collapse
You could either go straight a Lollipop based ROM or start with a KitKat ROM. The KK ROM would probably be a bit more stable, although some of the nightly 5.1.1 LP ROMs are looking good according to many of the people installing the nightly versions. If you want something already customized with options for your choosing look to CM and its derivatives or one of the AOSP roms that are already tricked out. The other direction would be to install the most barebones AOSP ROM you could find and use XPosed with the GravityBox or Wanam module to tweak just about everything, but not both at the same time.
wow thanks that all helps a ton ill work on locating and updating all of that :]
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
notedroidbrokedroid said:
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
Click to expand...
Click to collapse
The processes were easy enough...and some like me had temp root on first or second try. If you've spent weeks and weeks trying to figure this all out, I'm not sure anyone can help you. There are people in these threads that have answered every question you've brought up, and helped people get through. I know you must be some kind of troll with your "one post" and claiming you've been rooting blah blah blah....engineer...blah blah blah, you should be embarrassed by your lack of understanding and ability to root and unlock. Go read some of the dopey posts by people who can't follow instructions or put a sentence together, yet were successful! I guess what I'm saying is stfu and go away.
Sent from my SM-N910V using XDA-Developers mobile app
gcounts said:
The processes were easy enough...and some like me had temp root on first or second try.
Click to expand...
Click to collapse
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
gcounts said:
you should be embarrassed by your lack of understanding and ability to root and unlock.
Click to expand...
Click to collapse
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
notedroidbrokedroid said:
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
Click to expand...
Click to collapse
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
douger1957 said:
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
Click to expand...
Click to collapse
- Has anybody bothered to state that 40% of the battery charge disappears every time you run Kingoroot? Nope. Nowhere in the guides.
- Has anybody mentioned that the CPD1 VZW bootloader firmware is also locked and will not boot a ROM flagged as custom? Nope! Nowhere. You heard it here first!
- Has anyone examined the content of the BPA1-CPD1 hybrid 5.1.1 ROM to determine whether it contains OEM VZW firmware or a custom firmware revision developed by someone on this forum? No. Nobody has done that.
You don't have to "write full-time" to have good written communication skills. I could write a very respectable COMPREHENSIVE guide on the process involved, but do you know what would happen to it? The admins would never sticky it and it would get buried under a thousand other threads. Somebody decided that there can be ONLY ONE ["Official"] guide, even though the current one is a stupid, incoherent mess that's maintained by an OP who refuses to amend or add anything to it.
And lazy? At least I perused the source code before I blindly copied a script claiming to unlock my bootloader. I doubt you have the slightest clue on either how to look at it or what malicious code looks like.
Lastly and most importantly, you're a fool for being content with giving your money to a phone manufacturer that rails you in the ass for wanting more control over it. After I brought my Note 4 back from the grave, I bought a Nexus. You think donating your change to the Devs is going to fix this problem long-term when you give Samsung $800 to continue doing this to you? I don't have enough crayons to further explain to you what an idiot you are.
Ok as this really is nothing more then a rant I will close this up with a few passing thoughts.
Things like this are not meant to be done by the average guy. This is a developers site. So yes you are expected to do lots of research before you do anything.
Next. No one in their right mind uses that root process. The battery drain is it connecting to the internet and downloading what ever it is they use to root the device after then get your imei and store it.
Also lets leave the name calling for the playground or the next name that will be called is banned.
HI,
I purchased a google pixel xl, the bootloader is currently locked I would like to unlock and root if possible. the phone is running android 7.1.2 build NKG47L. Ive searched youtube, and xda for means of rooting, etc but im not having any luck on finding what would help me.. so some help would be greatly appreciated
https://forum.xda-developers.com/pixel-xl/how-to/index-google-pixel-xl-t3466185
Hopefully you don't have the Verizon version of the Pixel XL.. If you do unlocking the bootloader is impossible. If you don't then flashing and rooting the Pixel XL is possible but unusually difficult. The instructions seem to change from month to month and you need to use a specially modified version of Magisk because the official one doesn't work on the Pixel. If you go the SuperSu route they do have an official version for the Pixel. I've been flashing for years and it pretty much took me an entire day to successfully flash a custom recovery, a custom rom, a custom kernel, root with Magisk and get the phone to pass safety net. I've never owned a phone that was such a headache to flash on. Good luck.
jhs39 said:
Hopefully you don't have the Verizon version of the Pixel XL.. If you do unlocking the bootloader is impossible. If you don't then flashing and rooting the Pixel XL is possible but unusually difficult. The instructions seem to change from month to month and you need to use a specially modified version of Magisk because the official one doesn't work on the Pixel. If you go the SuperSu route they do have an official version for the Pixel. I've been flashing for years and it pretty much took me an entire day to successfully flash a custom recovery, a custom rom, a custom kernel, root with Magisk and get the phone to pass safety net. I've never owned a phone that was such a headache to flash on. Good luck.
Click to expand...
Click to collapse
Because you are having a hard time doesn't mean everyone will. Literally every chance you get you have to post the exact same narrative about how hard this is. It's like you are trying to poison other people's experiences because you find this so difficult. Let OP form their own opinion because frankly there are tons of users having zero issues rooting romming and etc..
Good Lord.
pcriz said:
Because you are having a hard time doesn't mean everyone will. Literally every chance you get you have to post the exact same narrative about how hard this is. It's like you are trying to poison other people's experiences because you find this so difficult. Let OP form their own opinion because frankly there are tons of users having zero issues rooting romming and etc..
Good Lord.
Click to expand...
Click to collapse
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
jhs39 said:
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
Click to expand...
Click to collapse
Not claiming it's easy. Just saying it gets repetitive to see you in how many threads griping about how this is such an insurmountable task.
And of course you see people with issues. Why do I need to comment that I'm not having issues. Heck when someone does comment that they aren't having issues you refute that because you are having a hard time.
You say I should be more constructive, lol please please please read my post history and maybe you will see how many people I have made efforts to help. I've been helping people in the forum, I've been helping people on Reddit, I've been helping people on discord, irc, etc etc. I've turned down money for helping people. How many people have you helped? How have you paid forward any help you have gotten on the pixel? Hell I even told you why you couldn't flash twrp after you downgraded from the O beta. So please don't tell me about being constructive bro.
"Flashing on Android for years" means nil my friend. Maybe if you took the time to understand the device it wouldn't be so difficult.
Do you even know why you couldn't flash twrp? It's because the OTAs flash to the opposite slot so when you got the ota for Android N from O N flashed in the other slot.
TWRP patches both boot.imgs but now your inactive boot.img is incompatible with twrp so it hangs up.
Super simple fix, now that you know there are two slots. You figure out how to swap slots at the bootloader. Then you learn how to flash all and flash all in both slots
Then you get a light that goes off because you took the time to read how twrp works in it's thread and realize you don't even need to flash all. You could simply flash the boot img in both slots. Because if you know what twrp patches then you know exactly what files you need.
I've been flashing for years also but I'm humble enough to know I should read before crying to people that are doing it without issue.
As far as the magisk "issue", well if anyone took the time to go to the magisk thread they would see the device isn't officially supported. Who's fault is it you didn't do that?
What was stopping you from searching the magisk thread before you started? I mean obviously you ignored where it stated it's not supported.
You can lead a horse to water my man. Can't make him drink.
jhs39 said:
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
Click to expand...
Click to collapse
It's "extremely easy" to flash on this phone. It's the hacking and deving thats hard. Give me a zip that works and a functioning Twrp, it will be like taking candy from a baby. Yeah, and Google's not helping any of us.
Well THAT escalated quickly...
Sent from my SM-N910V using Tapatalk
Thanks for the help. I have been able to get the phone rooted, etc but I can't get TWRP recovery to stick. But do I have to reflash TWRP recovery after I flash SU files for root?
yamaha_wins said:
Thanks for the help. I have been able to get the phone rooted, etc but I can't get TWRP recovery to stick. But do I have to reflash TWRP recovery after I flash SU files for root?
Click to expand...
Click to collapse
I had to boot into my rom once, go back into fastboot TWRP and then flash the TWRP zip again in order to get it to stick.
@jhs39 and @pcriz, you're both correct in this matter and hopefully you all can just agree to disagree. I agree with you both, if you're a flasher like most of us and I too have been flashing for years. In fact about 90% of the phones I've owned have all been flashed and I average about two phones per year. That said I'm not expert and do find some things harder here and there but I'm techie enough to work through it with help from members of this forum. @pcriz I've used many of your instructions and assistants on this thread so thank you! I too believe flashing on the pixel has been very difficult mainly because the device changed the way things usually worked (slots etc.). I can't remember the last time it took me hours to flash a simple ROM. After I learned a little bit of what was going on with TWRP and the whole slot A/B configurations I was able to at least troubleshoot my own issues and get things working a little better. I would say anyone having issues need to take the time to really read and understand the device because they don't function the say as before. The instructions do change because Google changes things up. Manufactures don't want us flashing any more and with security being a top priority flashing is quickly being discouraged.
I've gotten to the point now where I just want to get my pixel which is no longer my daily driver (my S8 plus is) to stock but even that isn't working. I've tried numerous times to flash an image and it fails every single time. Why????? I have come to love a stock experience even though I still love the customization you get with a custom ROM. If I were to pick right now I'll just stick with stock; if I can ever get the phone to flash the stupid image so I can try Android O lol.