Develop Bugs

Help me find a ROM, one step closer to JB on my GSM Nexus

Hello all!
So I rooted and unlocked the bootloader on the Galaxy Nexus using the rather noobish way of WugFresh's toolkit.
I know that TWRP is installed and working, as well as root is working. My next question would be that, given my build,
Here as some specs:
Android Version: 4.0.1
Baseband Version: I9250UGKK7
Kernel: 3.0.1-ge2433f2 [email protected] #1
Build Number: ITL41D.I9250UGKK7
I know that it's origianlly unlocked and Canadian GSM/HSPA+ model.
I am looking for two things:
a) a ROM that I could flash on my Nexus - of 4.1.1 JellyBean.
b) a revovery image that would work, in case something screws up.
https://developers.google.com/android/nexus/images has images, but none of the stock ITL41D build. (I keep getting references to Verizons images)
Oh and lastly, the Nandroid backup I did; if something goes wrong, and I am no longer on 4.0.1 ICS, - say in a unusable state, but I can access TWRP, will restoring the backup also restore all files and bring it (the phone) to a usable state (for example, say if I install JB, and do a recovery, will my recovery nandroid backup revert it back to ICS?)
Thanks!

http://forum.xda-developers.com/showthread.php?t=1626895
This process will make you lose root and wipe everything, including /sdcard/. I believe you have Samsung build right now, and you need to flash yakju or takju. Good luck
Also, you shouldn't use toolkit... Here's why

kyokeun1234 said:
http://forum.xda-developers.com/showthread.php?t=1626895
This process will make you lose root and wipe everything, including /sdcard/. I believe you have Samsung build right now, and you need to flash yakju or takju. Good luck
Also, you shouldn't use toolkit... Here's why
Click to expand...
Click to collapse
Thanks.
I understand the the reason for not using the One-step-root kits, however, I feel that in this case it may be somewhat justified. I work with Linux almost daily (by use I mean not simple Ubuntu stuff, but IBM AIX, PHP, perl, shell scripting compiling using gcc), and have no 'fear' of just enterting commands into terminal, or writing a simple shell script to do if for me.
Essentially you are setting the SUID bit (chmod 4xxx) and root. (as far as I understand). I just am somewhat hesitant in the land of phones, where I am kind-of paranoid of things breaking.
And please forgive me if what I said is sounding like I am trying to defunc your reasoning, and I fully agree - using one step anything is usually a bad choice, I was just justifying why I did it.
From what I understand, the 1 root toolkit did this:
Unlock bootloader -> flash TWRP -> install SuperSU binaries for root -> done.
But with TWRP, wouldn't that allow me to install a custom ROM such as yours. AOKP JB 1 (http://aokp.co/index.php/releases/_/jellybean-build-1-r28) Maguro?
Am I write in thinking that if I were to reboot into TWRP, factory reset -> flash gapps and the AOKP JB ROM, it's pretty much the same process?
I used to think that I wanted the Stock, official, JB build, but there really isn't enough customization options there.
I had a HP Touchpad with ICS CM9, and a Droid 2 Global with CM9, and I really loved the custom ROM features there.
Thanks!

I used a toolkit and I think they're a great option. After I started flashing ROMS I have been on forums nonstop. I learn from others questions and resources that are available. I feel a great deal more comfortable now than I did 4 months ago when I rooted. If I have a question I will search out the answer and if I can't find it or its too difficult to understand I will ask. Also when others post a question that my limited knowledge can answer, I will. That's why this community exists. We help each other out.
I do however understand the frustration that some have with people who come here and ask the same question that has been asked a hundred times before. There is no excuse for laziness and laziness will exist with or without Toolkits. Not all people who use toolkits are unwilling to help themselves or unable to learn the process.
Just saying.
Sent from my Galaxy Nexus using xda app-developers app

Xfanatic said:
I used a toolkit and I think they're a great option. After I started flashing ROMS I have been on forums nonstop. I learn from others questions and resources that are available. I feel a great deal more comfortable now than I did 4 months ago when I rooted. If I have a question I will search out the answer and if I can't find it or its too difficult to understand I will ask. Also when others post a question that my limited knowledge can answer, I will. That's why this community exists. We help each other out.
I do however understand the frustration that some have with people who come here and ask the same question that has been asked a hundred times before. There is no excuse for laziness and laziness will exist with or without Toolkits. Not all people who use toolkits are unwilling to help themselves or unable to learn the process.
Just saying.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have no issues with using manual meathods, I just thought this is most conveniant.
Now back to my original question however, with the GSM Nexus, Is AOKP my real only viable JB build for the Galaxy Nexus?

vlambrecht said:
I have no issues with using manual meathods, I just thought this is most conveniant.
Now back to my original question however, with the GSM Nexus, Is AOKP my real only viable JB build for the Galaxy Nexus?
Click to expand...
Click to collapse
Stock JB does not work for you?

Man, I've always used tool kits. If you're confident in your ability to follow directions, go for it. All this "stay away from tool kits" stuff should be taken with a grain of salt..
Just my opinion...

SocialReject said:
Man, I've always used tool kits. If you're confident in your ability to follow directions, go for it. All this "stay away from tool kits" stuff should be taken with a grain of salt..
Just my opinion...
Click to expand...
Click to collapse
As long as everything goes well, toolkits are easy indeed. But if somethings screws up, most toolkit users have no clue whatsoever what they need to do to fix it (just browse a few pages of history of the Q&A forum to see what I mean). That's why lots of regular helpers here advise against them. So not a grain of salt, but with good reason.
You can also read the advice as: don't mess with something you don't understand.

efrant said:
Stock JB does not work for you?
Click to expand...
Click to collapse
It does and doesn't. There are a lot of features on the custom ROMs that I liked.
what about the AOKP ROM? How is it?
Edit: so is there a JB ROM I could flash using TWRP? Or do I have to flash the stock image?
Sent from my Galaxy Nexus using xda app-developers app

vlambrecht said:
It does and doesn't. There are a lot of features on the custom ROMs that I liked.
what about the AOKP ROM? How is it?
Edit: so is there a JB ROM I could flash using TWRP? Or do I have to flash the stock image?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Somebody correct me if I'm wrong, cuz I don't know this either, but I think you need to update radio.img, bootloader.img and userdata.img in order to move to Jelly Bean. I don't know if custom ROM has that...

I know that JB and ICS use two seperate bootloaders, however I thought this was only the case for official OTA updates?
Reason why I think it's only for OTA is this:
http://aokp.co/index.php/releases/_/jellybean-build-1-r28
Download build for your device, place on SD card
Download gapps, place on SD card
Reboot into recovery
Wipe/factory reset! If you think you can get away without wiping from ICS -> JellyBean, you won't be happy camper. Wipe!
Flash jb-build-1
Flash Gapps
Reboot
So this implies that you don't need to update the bootloader, radio and userdata images.
I boot into TWRP -> reset/wipe -> flash gapps and jb -> done?
I don't believe that anything else needs to be done. I am pretty sure that the baseband radio is fine, and should work. Userdata image may be included?
BUT you are completely right about factory install of JB:
http://betanews.com/2012/08/20/how-to-install-jelly-bean-on-galaxy-nexus/

vlambrecht said:
[snip]
Edit: so is there a JB ROM I could flash using TWRP? Or do I have to flash the stock image?
Click to expand...
Click to collapse
There are a bunch of JB ROMs in the dev section, no?
But if I were you, I would try stock out for a while, so that you have a basis for comparison. (Less bugs vs. more features, etc.)
kyokeun1234 said:
Somebody correct me if I'm wrong, cuz I don't know this either, but I think you need to update radio.img, bootloader.img and userdata.img in order to move to Jelly Bean. I don't know if custom ROM has that...
Click to expand...
Click to collapse
On the GNex, it is always a good idea to update the bootloader to the latest version.
vlambrecht said:
I know that JB and ICS use two seperate bootloaders, however I thought this was only the case for official OTA updates?
Click to expand...
Click to collapse
Almost every iteration of Android for the GNex has had a new bootloader, it is not only JB and ICS.
Some have reported issues using JB on bootloaders older than LA03. I would recommend you update.

Isn't this phone a Maguro build? If that's the case you should be able to flash about any ROM.
Make a nandroid before flashing and flash them all until you find one that suits your needs.
Sent from my BAMFed Nexus
---------- Post added at 11:53 PM ---------- Previous post was at 11:48 PM ----------
I have been flashing JB for over a month and just updated my bootloader last week. Not because I was having trouble, but because I figured I would do it while I was updating my radios. The JB bootloader is said to possibly speed up boot time but I haven't noticed any difference.
Sent from my Galaxy Nexus using xda app-developers app

Xfanatic said:
Isn't this phone a Maguro build? If that's the case you should be able to flash about any ROM.
Make a nandroid before flashing and flash them all until you find one that suits your needs.
Sent from my BAMFed Nexus
---------- Post added at 11:53 PM ---------- Previous post was at 11:48 PM ----------
I have been flashing JB for over a month and just updated my bootloader last week. Not because I was having trouble, but because I figured I would do it while I was updating my radios. The JB bootloader is said to possibly speed up boot time but I haven't noticed any difference.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I did make a nandroid backup, already, but a few questions about that:
When you do make one, is it a complete backup, where if something goes wrong, everything even OS will be recovered (i.e. all hypothetical. I am on Android 2.3 GB, make a nandroid backup, install ICS, then revert nandroid snapshot (while on ICS), will I be back to a usable state of GB?)
Also, updating the bootloader will only update the /boot partition and not the /recovery partition, right? Or will it also flash my TWRP on the /recovery partition back to the stock Recovery?
Thanks!

vlambrecht said:
I did make a nandroid backup, already, but a few questions about that:
When you do make one, is it a complete backup, where if something goes wrong, everything even OS will be recovered (i.e. all hypothetical. I am on Android 2.3 GB, make a nandroid backup, install ICS, then revert nandroid snapshot (while on ICS), will I be back to a usable state of GB?)
Also, updating the bootloader will only update the /boot partition and not the /recovery partition, right? Or will it also flash my TWRP on the /recovery partition back to the stock Recovery?
Thanks!
Click to expand...
Click to collapse
A nandroid backup will back up the following partitions: boot, recovery, system, cache, and all data in /data except /sdcard. So to answer your question, yes, I it is essentially a complete backup other than the radio and bootloader, and but all of the radios are available in the radio thread, and all of the bootloaders are available in the bootloader thread.
As for your other question, the bootloader does not update the boot partition. The boot partition contains your kernel, not the bootloader. Flashing the bootloader does not wipe/replace any other partitions. You should really have a read of the 'basics' link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

vlambrecht said:
I did make a nandroid backup, already, but a few questions about that:
When you do make one, is it a complete backup, where if something goes wrong, everything even OS will be recovered (i.e. all hypothetical. I am on Android 2.3 GB, make a nandroid backup, install ICS, then revert nandroid snapshot (while on ICS), will I be back to a usable state of GB?)
Also, updating the bootloader will only update the /boot partition and not the /recovery partition, right? Or will it also flash my TWRP on the /recovery partition back to the stock Recovery?
Thanks!
Click to expand...
Click to collapse
I usually make my backups after I wipe the cache. The backup will save your system as it is at the time it is done including apps, data and setup. You want to make a nandroid of your phone while it is stable so you can revert to a stable build if something goes wrong.
Updating the bootloader will not change your recovery.
Sent from my Galaxy Nexus using xda app-developers app

Using fastboot to root

I have a new M8 and, for the moment, I want to keep it stock, but rooted. Is it possible to fastboot boot TWRP, flash SuperSU for root, and still be capable of receiving OTA updates, since TWRP isn't actually installed? I'm coming from a N4 and N10 where I didn't care so much about official OTAs, so I've never tried this.
Also, do I still have to unlock the bootloader first in order to use fastboot at all? And does having an unlocked bootloader prevent OTAs?
Sent from my Nexus 10 using XDA Free mobile app

No, you can't root with a locked bootloader. That's the whole point (well, mostly) of a locked bootloader.
Also, its my strong opinion that OTAs have no place on a modded/rooted device. It won't work anyway, the OTA will check for root and fail to install. Or even if it did install, it would unroot the phone.
If you want to root, just do the whole deal, unlock bootloader, install custom recovery, etc. You can flash anything you want, including the awesome array of custom ROMs, or stock rooted ROMs for other carrier versions (which usually get released soon after the OTAs anyway).

Totally makes sense. Knowing me, it won't be long before I feel constricted with a locked bootloader (especially if I can't root}, but just wanted to see how "virgin" I can't keep the phone while I break it in. Plus I read a recommendation to use fastboot to boot into TWRP as an alternative to flashing it. But if I have to have an unlocked bootloader to do even that, I suppose I should just install TWRP and be done with it, like I'm used to.
Sent from my Nexus 10 using XDA Free mobile app

bruce7373 said:
Plus I read a recommendation to use fastboot to boot into TWRP as an alternative to flashing it. But if I have to have an unlocked bootloader to do even that, I suppose I should just install TWRP and be done with it, like I'm used to.
Click to expand...
Click to collapse
Not sure what will happen if you try to boot TWRP with a locked bootloader. Maybe only one way to find out
But that would be purely academic. You can't flash SU or SuperSU, since you need write access to the system partition to do so (and therefore an unlocked bootloader), regardless of whether you can boot TWRP or not.

redpoint73 said:
Not sure what will happen if you try to boot TWRP with a locked bootloader. Maybe only one way to find out
But that would be purely academic. You can't flash SU or SuperSU, since you need write access to the system partition to do so (and therefore an unlocked bootloader), regardless of whether you can boot TWRP or not.
Click to expand...
Click to collapse
Great, that's exactly what I needed to know. I'll just wait a week or two, see if I'm happy with the phone and, if I am, just do it all. Thanks a lot.
Sent from my Nexus 10 using XDA Free mobile app

Just root ?

Do you think we will ever get something like towelroot for the 5X?
After 5 years of unlocking, messing with bootloaders, kernels, and roms I'm tired. I just want to enjoy my nexus. All I really want is root.
Thanks in advance for your thoughts.

I guess not.

It's so easy to flash superSU I don't know why that would be necessary. It only takes a few minutes.
Sent from my Nexus 5X using Tapatalk

thesoldier said:
It's so easy to flash superSU I don't know why that would be necessary. It only takes a few minutes.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
My understanding is that the OP wants root without having to flash all the images, and ROMs, to keep the phone up to date. OTAs are convenient and don't require much effort other than hitting "Reboot now" and waiting a minute or two. Flashing ROMs, right now, means that you have to download the whole ROM with the latest updates and security patches, boot into recovery, flash the ROM and whatever kernel or gapps you need, and then reboot.
I'm guessing the OP just wants plain root with all the conveniences and privileges that the stock ROM and OTA updates provide. Strangely enough, I'm leaning towards that route myself. I don't mind getting a boot img and custom ROM and kernel, but I don't want to have to flash so many items every single time when an OTA would sufficed.

daver68 said:
I'm guessing the OP just wants plain root with all the conveniences and privileges that the stock ROM and OTA updates provide. Strangely enough, I'm leaning towards that route myself. I don't mind getting a boot img and custom ROM and kernel, but I don't want to have to flash so many items every single time when an OTA would sufficed.
Click to expand...
Click to collapse
This is my situation as well. Especially now that Android security updates should be coming out on a monthly basis, I'm reluctant to give up the convenience of an OTA to get my security patches without needing to flash anything.

OTA updates will fail even if you are on stock and just rooted. I think chainfire is testing a root method that will allow you to take ota's because it doesn't modify the system partition.
This is a nexus device.. Something like towel root is not needed.. Just unlock the bootloader, boot (not flash) recovery and flash supersu..then you have stock just rooted..
Root methods like towel root etc.. Are mostly made for devices where you can't unlock the bootloader.. This is a nexus for Pete sake...It's not needed.. Unlocking the bootloader and rooting is easy enough in nexus devices..
Sent from my Nexus 5X using Tapatalk

[HELP!] Systemless Rooting on 6.0.1 Build MMB29P

Hi! So I'm looking to root my Nexus 5x following this guide. However, I can't find the modified boot.img for my build MMB29P. I have a brand new phone out of the box (my mic stopped working so this is a replacement) so I'd like to get this done in the next little while the phone has no data and I can wipe anything I need to without worry and use the restore afterwards. I also heard something about SuperSU being able to use stock boot.img or something of that nature, could someone clue me in? Thanks!

[GUIDE] Unlock/Root/Flash for Nexus 5X - Heisenberg's How-To Guide For Beginners
take a look at section 6
as an alternative there are some toolkits that may be more convenient to you (on-screen instructions and detailed faq/guides)

The latest version of SuperSU (v. 2.66 I believe) is automated for systems root. I actually used the SuperSU beta v. 2.62 to root. I just unlocked bootloader, flashed TWRP, and then flashed that version of SuperSU.
Sent from my Nexus 5X using Tapatalk

Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?

jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.

https://www.androidfilehost.com/?w=files&flid=43558

k.s.deviate said:
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
Click to expand...
Click to collapse
Even with systemless root?

When it comes to upgrading, there are a couple of routes you can take. Both involve downloading the official factory image ZIP first. Extract the contents, reboot into bootloader, and then you have option:
1. Edit the flash-all script (.bat for windows and .sh for Linux/Mac) by removing the -w option. Removing this option will prevent the upgrade from wiping user data. Once the option is removed, simply run the script to upgrade.
2. Flash the images individually. Sometimes certain things don't change like bootloader.img or radio.img. You should always flash boot.img, system.img, and vendor.img when updating. This is the route I take.
After flashing the images, you will need to reboot into Recovery mode and flash SuperSU. Then wipe cache and dalvik and reboot into system. If you use a custom kernel, you will need to reflash that as well after updating.
Sent from my Nexus 5X using Tapatalk

Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.

jkingaround said:
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
Click to expand...
Click to collapse
Google posts the official factory images on the developer site. Here is the link: https://developers.google.com/android/nexus/images
AFAIK the boot warning can't be removed, but I may be wrong. It's nothing to worry about though.
Having a custom kernel is not necessary, but there are benefits to using one. Custom kernels typically provide better battery life with same or improved performance. They can also make your device run cooler and use less memory. Custom kernels also allow for various tweaks such as change vibration intensty, screen DPI, headphone/speaker gain, etc. I personally use ElementalX with the Interactive Governor tweaks from the thread in the general forum, but I've read that Franco Kernel is very good as well and will probably try that out in the future.
Sent from my Nexus 5X using Tapatalk

jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
Just pick a custom rom to try and follow OP instructions. Cataclysm seems to be a hit...

Downgrade from nougat to marshmallow

I am currently on 7.0 and i want to downgrade to pure nexus 6.0.1, i have been given advice and the steps are (in the order which i have in my mind) is:
1. boot into twrp
2. format system, cache, dalvik/ART cache and data
3. flash pn 6.0.1
4. flash gapps
5. flash vendor image
6. reboot? done?
idk if i have to flash the mashmallow radio or if downgrading will give me any cellular/wifi problems. can anyone clarify this? also is it possible doing this with the steps above will lead to a brick? (sorry for being a paranoid idiot, just don't want to end up with paperweight)
thanks.

All I did to downgrade was get into fastboot and flashall google factory M image. Booted fine. Then I loaded TWRP and flashed custom rom (if you want to do that).
The method above may work too but I felt safer loading all stock google M partitions first.
Sent from my Nexus 5X using Tapatalk

milan187 said:
All I did to downgrade was get into fastboot and flashall google factory M image. Booted fine. Then I loaded TWRP and flashed custom rom (if you want to do that).
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yea i thought of that but i wanted to go directly to pure nexus from 7.0 and i wanted to know if this would be safe to do, I've downgraded from 7.0 to 6.0 (cm 14 to cm 13) on my samsung devices but as a new nexus user i am a bit confused as to the general process of things but over time (and help from the xda community) i'll get the hang of things.

niklus101 said:
Yea i thought of that but i wanted to go directly to pure nexus from 7.0 and i wanted to know if this would be safe to do, I've downgraded from 7.0 to 6.0 (cm 14 to cm 13) on my samsung devices but as a new nexus user i am a bit confused as to the general process of things but over time (and help from the xda community) i'll get the hang of things.
Click to expand...
Click to collapse
Well it should work that way too and with unlocked bootloader you should not be able to brick your phone.
Are you trying to preserve your data? That's probably not a good idea.
I just felt an extra 10min and possibly a cleaner load was worth it.
Sent from my Nexus 5X using Tapatalk

milan187 said:
Well it should work that way too and with unlocked bootloader you should not be able to brick your phone.
Are you trying to preserve your data? That's probably not a good idea.
I just felt an extra 10min and possibly a cleaner load was worth it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
nah, loss of data is not much of a problem, just don't wanna end up with a brick but also with my crappy internet the download would take forever so i wanted to know if this shorter method would work.

niklus101 said:
I am currently on 7.0 and i want to downgrade to pure nexus 6.0.1, i have been given advice and the steps are (in the order which i have in my mind) is:
1. boot into twrp
2. format system, cache, dalvik/ART cache and data
3. flash pn 6.0.1
4. flash gapps
5. flash vendor image
6. reboot? done?
idk if i have to flash the mashmallow radio or if downgrading will give me any cellular/wifi problems. can anyone clarify this? also is it possible doing this with the steps above will lead to a brick? (sorry for being a paranoid idiot, just don't want to end up with paperweight)
thanks.
Click to expand...
Click to collapse
Yes that will work fine, steps 1-6. The radio and bootloader are interchangeable.
Sent from my Nexus 5X using Tapatalk

just did it. thanks for the help everyone from here and the pure nexus thread. i can confirm it works perfectly.