Related
I am sorry if this is a dupe of other threads but I couldn't find a complete answer to my problem anywhere else.
I have a nexus 7 (2012), on stock 4.4.2, unlocked bootloader (i think, unlocked padlock on startup).
I want to root. I gather this will not wipe? (or will it?) and what tool should i use? I already have N7 toolkit and android sdk, so i can use that most easily, otherwise any other program needed is fine. I want to use stock bootloader and stock rom and ensure ota updates will occur. (i understand i may lose root through ota updates, but i assume i can just reroot as i have unlocked the bootloader?)
Thanks
Since your tab has already gone through the bootloader unlocking process, there is neither a need nor a requirement to wipe the device.
And since you want to stay as close to Stock as possible, you can even "root" without ever flashing a recovery: you just soft-boot a recovery image rather than flashing one. That is - "fastboot boot (...etc)" instead of "fastboot flash (...etc)". That allows you to use a custom recovery every once in a while while leaving a stock recovery on the tablet. That preserves maximum compatibility with future OTAs.*
And with that soft-booted recovery, immediately take a Nandroid backup including the Stock recovery (which is still on the tablet because you soft-booted the recovery you are using). In the same session, use "adb pull" to get a copy of your 100% pure-stock Nandroid backup off the tablet. (Make sure you name it clearly so you will know exactly what it is 12 or 24 months later)
Finally, use a flashable .zip installer package for SuperSU to "flash root".
After an OTA, you can just reinstall root by soft-booting a custom recovery and using the same (or updated) flashable .zip installer method for reinstalling SuperSU. And just like above, capture a new 100% pure-stock Nandroid backup (including the new stock recovery) *before* re-rooting.
This strategy allows you to roll back to any version of stock you please at any time in the future.
good luck
* flashaholics prefer to have a recovery hard-flashed on their device so they can flash things on a whim, wherever they are. The approach here is a bit more restrictive as you have to have a PC handy in order to soft-boot a recovery in order to do any flashing. I would say that the biggest limitation of this approach is that it tends to reduce the number of Nandroid backups of your ROM personalization.
Backup are a good thing. You can always throw them away later, but you can't create a missing one that is urgently needed.
I am getting into development more and have a new load of questions. And yes, I searched first.
Do all Roms include firmware(OS), kernal, baseband, and boot loader?
Do over-the-air updates include the baseband and boot loader, or only the kernal and firmware/(OS).
I once used the Wugfreth toolkit to reinstall the stock ROM. It flashed the baseband with the same version and then attempted to flash the boot loader with the same version, but failed. How can I JUST flash the kernal and firmware/os.
This may be dumb question, but what language is the boot loader and baseband written in? Is it encrypted, or can anyone edit it and flash?
What happens if the boot loader, baseband, kernal, and firmware versions do not match?
I did not know the ROM included the bootloader, and I almost purposely flash the ROM of another device to see what would happen, figuring I could have restored using fastboot. But that probably would have hard-bricked it, right? I thought flashing a ROM was completely safe because it did not touch the boot loader, and could always be undone with fastboot?
How do you developers test out modified bootloaders without making a simple coding mistake and ruining your device?
How can you flash a bootloader using itself (fastboot)?
I saw a post for a different device for changing the boot loader logo. Not the firmware's boot animation. I don't want mine to say "Google" with an unlock icon. Can this be done on the Nexus 7?
I read the partition sizes are determined by the boot loader, and not adjustable. Is this correct? I am running stock 4.4.3 and only have 11MB free on the system partition. How do custom Roms fit within this limit? I am worried this will prevent a custom ROM based in 5.0 Lollipop, and the Nexus 7 2012 will be stuck on Kitkat. Maybe the firmware could be loaded on the data partition with a symbolic link to the system partition?
Thank you
I'm not a developer, but can answer some of your questions (at least as they relate specifically to the Nexus 7).
Custom ROMS typically just include the firmware/kernel (and i believe the radio/baseband if it's for a 3g/mobile device, though these can also be flashed separately, and i could be wrong on this part.) Bootloader is typically untouched, but this might differ on other devices.
As for OTA updates and what all they include, well that depends on the device, manufacturer, carrier, and even the specific OTA. It could potentially include everything (firmware/kernel updates, bootloader, radio/baseband, etc.), but may be any combination of the different components.
Available free space on the system partition doesn't really matter if you're flashing a new ROM, because you'll be wiping the partition as part of the flashing process. ROMs typically don't include GAPPS either (unless it's just a modified version of stock), so will actually take up much less room than the stock ROM on their own. Then you can decide which GAPPS to flash separately, there are various packages available in different sizes; some just include the basic google play services needed to have the play store and related basic functionality, others will mirror the stock pre-installed apps.
If you're using a custom recovery to flash a ROM, they typically contain a script to first verify the device matches, if not, it won't even flash. If you do manage to flash an incompatible ROM (via fastboot maybe, or if it doesn't include a verification script), with a Nexus this typically is not a big deal, you just won't ever actually boot into the ROM, but should still be able to boot into recovery or bootloader and then flash a compatible ROM.
If you flash an incompatible kernel on top of a ROM, you'll likely get a bootloop/softbricked device.
Flashing an incompatible bootloader may brick the device. Any tinkering with the bootloader is always risky.
Hope that helps a little, I'll take another look when I'm not at work
flyoffacliff said:
I am getting into development more and have a new load of questions. And yes, I searched first.
Do all Roms include firmware(OS), kernal, baseband, and boot loader?
Do over-the-air updates include the baseband and boot loader, or only the kernal and firmware/(OS).
I once used the Wugfreth toolkit to reinstall the stock ROM. It flashed the baseband with the same version and then attempted to flash the boot loader with the same version, but failed. How can I JUST flash the kernal and firmware/os.
This may be dumb question, but what language is the boot loader and baseband written in? Is it encrypted, or can anyone edit it and flash?
What happens if the boot loader, baseband, kernal, and firmware versions do not match?
I did not know the ROM included the bootloader, and I almost purposely flash the ROM of another device to see what would happen, figuring I could have restored using fastboot. But that probably would have hard-bricked it, right? I thought flashing a ROM was completely safe because it did not touch the boot loader, and could always be undone with fastboot?
How do you developers test out modified bootloaders without making a simple coding mistake and ruining your device?
How can you flash a bootloader using itself (fastboot)?
I saw a post for a different device for changing the boot loader logo. Not the firmware's boot animation. I don't want mine to say "Google" with an unlock icon. Can this be done on the Nexus 7?
I read the partition sizes are determined by the boot loader, and not adjustable. Is this correct? I am running stock 4.4.3 and only have 11MB free on the system partition. How do custom Roms fit within this limit? I am worried this will prevent a custom ROM based in 5.0 Lollipop, and the Nexus 7 2012 will be stuck on Kitkat. Maybe the firmware could be loaded on the data partition with a symbolic link to the system partition?
Thank you
Click to expand...
Click to collapse
1. roms dont include a bootloader.
2. no
3. easily in a custom recovery.
4. i have no idea, and its the most secure part of the device.
5. nothing.
6. roms DO NOT EVER include bootloaders.
7. developers on nexus devices never modify the bootloader. first off, its extremely tedious and difficult. secondly, there is no need, as our bootloaders are unlockable and lockable.
8. it overwrites itself, but you are on your computer using fastboot, phone is just plugged into it.
9. no.
10. each partition has its own size. roms go into a partition that also holds your storage, and is separated from the storage. another reason why you dont have 16gb storage when you buy a 16gb device, because some of it gets allocated to the system.
I was wondering if someone could give me a direct answer because i cant seem to find one sifting through the forums.
I originally rooted with root master back when i got the phone. it is still on mje/4.3 stock build. things look a little more complicated then i remember, since my phone hasn't seen an update in over 3 years. I originally froze the verizon ota updates with tibackup, along with all the other bloatware.
My main questions are:
1. I would like to get a 6.0 Rom that looks like the note 7 did, can i do it all with odin and just flash a bunch of files?
2. Do I need a custom recovery like twrp or cwm?
3. I've read about an activation lock but can't find it in my menus, did it not exist yet on 4.3?
If anyone can point me in the right direction I would appreciate it, I really dont wanna brick my phone.
I'm still on MJE firmware, but using an older CM13 (temasek) ROM. So it's marshmallow but no Touchwiz or other Samsung add-ons.
Here are the MJE-specific issues:
1) You can't boot N* or O* stock kernels because of differences in the way that DTB (device tree blobs) are packed into the boot image. I've played with re-packing the boot images, but the kernels seem to run off into the weeds after a few tens of seconds.
2) TowelRoot works on MI9 through NC2(leak) but I think not thereafter - if you wanted to avoid a bootloader firmware upgrade but re-flash via Odin the MJE firmware for "starting from scratch" purposes, you have a means to re-root that does not require a PC.
3) If you retain the MJE bootloader, use the TWRP (hltevzw) -4.3 recovery; the -4.4 recovery will not boot, presumably due to issues similar to (1) above.
4) Not specific to MJE - but important - is the fact that if you want to boot either a custom kernel or custom recovery, you need to unlock your bootloader first. You can unlock your bootloader from any rooted ROM, but be aware that flashing stock firmware with Odin thereafter will re-lock the bootloader.
If you were to "start from scratch" but upgrade to more recent stock software before rooting, be aware that there is no publicly available root for NC4 or NK1; you would need to install stock OB6 or OF1, and follow that by using those "yemen" rooting tools. (Are they safe to use? I don't know frankly)
I am assuming that the N* and O* series bootloaders are backwards compatible with regard to device tree booting issues (see #1 above), because the temasek CM13 roms (having a custom kernel) boot on both OF1- and (my) MJE- bootloader phone. I guess that means it uses a "4.3" DTB packing in the boot image.
You are probably going to want to use TiBu to make important backups, and also copy everything off the phone that is important to you. You should assume that if anything goes wrong, an Odin re-install and factory reset are in the device's future.
Having said all this, I'm not sure there is such a thing as a ROM which "looks like Note7" - this is an old phone with almost no ROM developers left. There might have been more, but the bootloader unlock was achieved 2+ years after the phone's release, and most of the active developers moved on to new phones before that happened.
good luck
Hi it is the first time I am flashing Android ROM. I have done some reading already. Before I start, I still have a few questions and also want to make sure I am doing it right.
I own the Galaxy S4 Verizon I545. It is running Samsung ROM Android 4.4.2, Baseband I545VRUFNC5. My goal is to flash a new ROM with recent Android versions, hopefully 7.1.1 (but I would settle with Marshmallow if that is more stable), it can be close to AOSP, I don't need ROMs with extra features.
In my understanding, the bootloader is locked, it will only load signed kernels and recovery. And then the kernel would load the system. In order to flash the system, it is best to flash the recovery first with TWRP. TWRP is modded with loki hack so it would load with the locked bootloader.
So here are my questions:
1. Does it matter which firmware/baseband I am currently on? For some phones (LG G2) I heard newer firmware fixed the loki hack. Should I update to the latest Samsung rom or leave it at NC5?
2. I don't see many ROM posted for the i545, which one is the most recent and reasonable stable? The Cyanogen website is down, should I try LineageOS?
3. I see different instructions for flashing TWRP. Can I flash it with just Odin? Some instruction mentioned rooting the phone first with KingRoot or other root, and then use dd. Does the phone have to be rooted? (I prefer not to if it is not necessary)
4. If after I flashed recovery, it fails to boot into TWRP, what can I do to restore everything to default?
5. The kernel will be untouched in the process right? I am only flashing recovery and system ROM, and the kernel will work fine with the new system ROM?
Here are the step and software I plan to use:
0. reset the phone to factory
1. use Odin to flash TWRP 2.8.7
2. download a ROM compatible with I545 and place it on the phone
3. flash the system using TWRP
Any feedback would be appreciated.
PS: Also I have a LG G2 D801. I would flash that phone instead if it is easier. I just want to get started and learn some things along the way.
https://forum.xda-developers.com/galaxy-s4-verizon
Oh Sorry. Didn't notice there is another forum. Should I repost there?
Yes.
1. Yes, it does matter. As you said, newer firmwares have fixed the exploits which make the phone harder to hack.
2. Any ROM should support your phone. They are generally unified.
3. In the name of anything holy, do not root with KingRoot. If you want to root, then the only way to go is CF-Auto-Root.
Rooting is sometimes necessary because recovery won't always install with Odin.
4. Flash stock ROM.
5. Kernels are specific to ROMs. So no, the kernel won't be untouched.
I have:
Lenovo P1ma40 with last stock ROM (S040_170106_16G_ROW)
Root access
microSD card
stock recovery (but I cat flash TWRP 2.8.7.3)
So, is it possible to install some custom ROMs to sd card, without replacing stock firmware?
0x000000E2 said:
I have:
Lenovo P1ma40 with last stock ROM (S040_170106_16G_ROW)
Root access
microSD card
stock recovery (but I cat flash TWRP 2.8.7.3)
So, is it possible to install some custom ROMs to sd card, without replacing stock firmware?
Click to expand...
Click to collapse
Yes, it's possible, but the stuff to do it isn't available for all devices.
Some options are:
1) Safestrap recovery- this tool lets you keep the stock ROM and install custom ROMs inside Safestrap, then when you boot your device, you choose whether you want to boot stock or one of the custom ROMs. This is a dead project though, if you want it to support your device, you'll probably have to build a version of Safestrap for yourself so that it supports your device, then, if there are no custom ROMs available for your device, you'd have to build the custom ROMs for yourself also.
2) if you can flash TWRP and if there is a version of the Multi-ROM custom ROM for your model number, you can use it. Multi-ROM is a ROM that is built to boot different ROMs.
Sent from my LGL84VL using Tapatalk