Android development xda developer

Android development xda developer

Nothing launches the ear (1) wireless earphones in black, and we tried them out

Nothing’s first product launch was a pair of truly wireless earbuds that came with a transparent case and a see-through housing for the earbuds, with the company’s philosophy being to…

Hands-on with Qualcomm’s Snapdragon 8 Gen 1 Reference Device

It’s Qualcomm’s Snapdragon Technology Summit, and just as it does every year, the company announced its latest flagship mobile processor. It changed up its branding this year after maxing out…

The new Qualcomm Snapdragon 8 Gen 1 is the flagship SoC of 2022 — Here’s what you need to know

Qualcomm’s Snapdragon chipsets are found in every segment of the Android world, powering millions of devices. This year marks a change in the naming strategy for the company, and not…

Google Pixel 6 Pro vs Apple iPhone 13 Pro: The best of Android vs the best of iOS

The Google Pixel has always been designed to be the «iPhone of Android,» and the Pixel 6 Pro comes the closest to living up to that goal yet. In addition…

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Источник

Android Development

Breadcrumb

svetius

User Experience Admin

psychoticsmiley

Member

So jazzed to see what is possible with this device!

Drewmungus

Senior Member

DangKid

Senior Member

Drewmungus

Senior Member

john10101

Senior Member

If the Nook Tablet is anything like a Nook Color, its going to be a modders playground.

the NC was by far the best android tablet on the market for the money. Just needed a bit of tweaks.

If BN took the NC and upgraded some Hardware, its going to be one sweet device.

DarkDvr

Senior Member

WTH, where is my ICS port? It’s been what.. 3 hours now.

(kidding, of course =)

smatticus

Senior Member

ItsMeMasih

Senior Member

The B&N by our house has them in stock and on sale. I just picked one up. Never having the original Nook color to compare with, I can’t comment on that but so far it’s a nice little tablet. I really only picked it up for the eventual root and port action.

I’m curious about the K Fire as well, but the lack of SD card slot made me think that rooting, flashing and overall modding would be a pain. I’ve got 2 weeks before I change my mind and pick that one up instead. Either way, I’m excited!

connor32

Member

I am not an Android development expert but.

I have seen that the ICS sourcecode can be built for the Pandaboard which has the same processor of the new Nook Tablet (TI OMAP4430).

Does this mean that the ICS ROM could run on the Nook Tablet as well? What am I missing here?

diamond_lover

Senior Member

I am not an Android development expert but.

I have seen that the ICS sourcecode can be built for the Pandaboard which has the same processor of the new Nook Tablet (TI OMAP4430).

Does this mean that the ICS ROM could run on the Nook Tablet as well? What am I missing here?

It’s not just a CPU thing. Every hardware need his own drivers.
Surely soon we will have a full port of ICS for our NookTablets, but now we have still no ROOT, so. just be patient

CM9 will arrive maybe in 2 months, MIUI on middle Dec.
We need Autonooter first.

deserthi

Senior Member

insanemongol

Member

Nook Tabled FTW

well im going to buy a Nook Tablet, cuz SD Card Slot and double size Space and RAM is really making the difference between the KF and Nook Tablet. i just hope that enough Developers would see that the same way and buy Nook Tablet so we can get KickASS Custom ROMS and goodies

Entropy512

Senior Recognized Developer

I’m tempted to expand my kernel hacking to OMAP — but it’s hard to justify when I already have a Samsung 10.1.

Has kernel source been posted yet?

ItsMeMasih

Senior Member

I’m tempted to expand my kernel hacking to OMAP — but it’s hard to justify when I already have a Samsung 10.1.

Has kernel source been posted yet?

DarkDvr

Senior Member

I’m tempted to expand my kernel hacking to OMAP — but it’s hard to justify when I already have a Samsung 10.1.

Has kernel source been posted yet?

japzone

Senior Member

It makes me a tad sad to see the KF get rooted already and the NT has had little to no progress. I hope development picks up soon. It’s kind of depressing to see Amazon stealing the thunder from the little guy.

____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk

Andrmgic

Senior Member

It makes me a tad sad to see the KF get rooted already and the NT has had little to no progress. I hope development picks up soon. It’s kind of depressing to see Amazon stealing the thunder from the little guy.

____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk

Keep in mind that BN moved up the release date at the last minute.. not every store had them today and the BN.com website still said 11/18..

I’d be surprised if we don’t get root before too long.

Entropy512

Senior Recognized Developer

Yeah, I believe the KF is already officially on sale, while the only NT owners are some lucky preorder customers who managed to get the unit earlier than planned.

Remember, right now, technically the NT is still a «pre-launch» device.

My guess is kernel source will show up when the NT support pages go live (they don’t exist yet.)

Andrmgic

Senior Member

I was able to just walk in to a store and buy one yesterday without a pre-order.. but I suppose I was lucky.

Here’s hoping for the kernel source soon.

Similar threads

Breadcrumb

Top Liked Posts

Essentially, the thought is that it is theoretically *possible* to boot from SD, but that you need the encryption key in order to do it?

(Please correct me if I’m wrong. This is not my area of expertise)

Yes. Specifically, you need Barnes and Noble’s private signing key.

The bootloader verifies that the firmware came from Barnes and Noble — if it didn’t, it won’t boot it.

So if you get one of B&N’s «unbrick» SD images, you’ll be able to boot it to restore a device to stock. But the whole point of code signing is to verify that the code came from a particular source, *unmodified* — modify the image, you invalidate the signature.

Private signing keys like this are VERY carefully guarded. It’s fairly rare for them to get leaked. In fact, I don’t know of any case where one got leaked.
1) The SBK leak for the Asus Transformer wasn’t a private signing key — it was just an access key to enable an alternative flashing mode. The bootloader of this device NEVER enforced code signing to my knowledge.
2) Sony’s private signing key was compromised, it took 2-3 years of multiple attacks including a hardware glitching attack to get there. Even then, the hardware glitching attack alone wasn’t enough, in addition Sony had to epicfail and release two updates where a number used to sign the update was supposed to be random but actually was the same value for two different firmwares.
3) I have yet to hear of an example of a sidechannel attack (the most common way to attack modern crypto algorithms) causing the signing key of a code signing mechanism to get compromised directly. (The closest would be the PS3 — a combination of a sidechannel attack to get «deeper» into the system to analyze the algorithms used, combined with a severe flaw in Sony’s signing approach.)

The problem is that in the case of 2/3, for people to bother, Sony had to have a fairly open system that they started to lock down post-purchase. A device that is locked down from the get-go usually results in people saying «****it» unless that device has something that sets it WAY apart from the competition. The Nook Tablet has none of those attributes — it’s a little nicer than the Kindle Fire, but not by enough to make it worthwhile for crypto experts to mess with. It would be easier to solder a larger RAM chip onto the OMAP4430’s PoP than it would be to mess with the Nook’s locked bootloader.

Источник

How to Root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!

Welcome to the XDA-Developers Root Directory. Here, you can find root tutorials for most devices that are on the XDA Forums. Learn how to root any Android device, even the best Android phones! If you don’t see your device listed or you see a misplaced link, send a message to Skanda Hazarika (SkandaH on the forums) with the device details.

Table of Contents:

What is Root?

For those new to the world of rooting, acquiring root access essentially grants you elevated permissions. With root access, you are able to alter or replace system applications and settings, run specialized apps that require administrator-level permissions or perform other operations that are otherwise inaccessible to a normal Android user. And by proxy, you may also be able to access certain “hidden” device features or use existing features in new ways.

DISCLAIMER: Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!

How to root a popular Android smartphone

We can go on about the virtues of root access ad infinitum, but we’ll stop for now because we can sense you’re salivating at the prospect of root access and what you can do with your device once root is achieved. Head to the following section to begin the journey. You should find device-specific root guides for latest flagship models from every major OEM below.

Sr. No.	Device	Codename and Device Forum	Root Guide
1.	ASUS ROG Phone 5	I005D	Click Here
2.	ASUS ZenFone 8	I006D	Click Here

For other ASUS devices, kindly check out the ASUS section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Google

Sr. No.	Device	Codename and Device Forum	Root Guide
1.	Google Pixel 5	redfin	Click Here
2.	Google Pixel 5a	barbet	Click Here

For other Google devices, kindly check out the Google section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Motorola

Sr. No.	Device	Codename and Device Forum	Root Guide
1.	Motorola G100 / Edge S	nio	Click Here
2.	Motorola Edge 20 Pro / Edge S Pro	pstar	Click Here

For other Motorola devices, kindly check out the Motorola section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

OnePlus

Sr. No.	Device	Codename and Device Forum	Root Guide
1.	OnePlus 9	lemonade	Click Here
2.	OnePlus 9 Pro	lemonadep	Click Here
3.	OnePlus 9R	lemonades	Click Here
4.	OnePlus Nord 2	denniz	Click Here

For other OnePlus devices, kindly check out the OnePlus section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Samsung

Sr. No.	Device	Codename and Device Forum	Root Guide
1.	Galaxy S21	unboundm1(q)	Click Here
2.	Galaxy S21 Plus	unboundn2(q)	Click Here
3.	Galaxy S21 Ultra	unboundo3(q)	Click Here
4.	Galaxy Z Flip 3	b2q	Click Here
5.	Galaxy Z Fold 3	q2q	Click Here

For other Samsung devices, kindly check out the Samsung section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Sr. No.	Device	Codename and Device Forum	Root Guide
1.	Sony Xperia 1 III	pdx215	Click Here
2.	Sony Xperia 5 III	pdx214	Click Here
3.	Sony Xperia 10 III	pdx213	Click Here

For other Sony Xperia devices, kindly check out the Sony section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

Xiaomi

Sr. No.	Device	Codename and Device Forum	Root Guide
1.	Xiaomi Mi 11	venus	Click Here
2.	Xiaomi Mi 11 Pro/Ultra	star/mars	Click Here
3.	Xiaomi Mi 11i/11X Pro/Redmi K40 Pro+	haydn	Click Here
4.	Xiaomi Mi 11X/POCO F3/Redmi K40	alioth	Click Here

For other Mi, Redmi, and POCO branded devices, kindly check out the Xiaomi section of our forums. You should be able to find similar fine-tuned guides for your device under the device sub-forums. You can also follow the generic rooting guide from this tutorial.

How to root any Android device

Nowadays, Magisk is the de-facto rooting solution that lets you have root access by leaving the system partition untouched and modifying the boot partition. This is why it’s referred to as a “systemless” root method.

Before getting started with Magisk, make sure that:

• You have access to a PC/Mac with adb and fastboot installed.
• The bootloader of the target Android device is unlocked.
  • For Samsung devices, unlocking the bootloader will trip KNOX.

Step 1: Identifying the type of the boot image

Download the latest version of the Magisk app from the project’s GitHub repository. Since the APK of Magisk is hosted outside of the Google Play Store, you may need to allow sideloading apps from unknown sources first and then manually install the downloaded package.

After installing, open the Magisk app. You should see a screen like this:

Now, we need to note down the values of the following parameters:

Step 2: Locating the boot image

In order to patch the boot image for your device, you need to extract it from the official firmware packages. In case you’re using a custom ROM like LineageOS, then the flashable ZIP file contains the boot image.

Case I: You have access to the recovery-flashable ZIP file

If you have a device that still uses the A-only partition scheme, then you can find the boot.img right inside the recovery-flashable ZIP file. Just extract it using a suitable archiver program.

Notice the boot.img file inside POCO M3’s recovery ZIP

However, if your device utilizes the A/B partition scheme, then the boot image and other partition images are further packed inside a file named payload.bin as shown below.

The recovery ZIP of the Google Pixel 5 contains a payload.bin file

In that case, you have to extract the payload.bin file first, then use one of the community-developed payload.bin unpackers to get the boot.img out of it. We strongly suggest you opt for the extractor written in GoВ as it is cross-platform and has been actively developed.

Known as “payload-dumper-go”, this fork even allows end-users to extract a single partition image without unpacking the whole payload.bin, which is particularly useful for this usage scenario.

• First, use the -l parameter to list the partition images inside the payload.bin.
• Then use the -p parameter with the name of the boot image (commonly stored as “boot”) to extract it.

Extracting the boot.img of the ASUS ROG Phone 5 from its payload.bin

Case II: You have access to the Fastboot-flashable image

A handful of OEMs like Google and Xiaomi provide Fastboot-flashable factory images for their devices. If you managed to grab such a package, then the raw boot.img can easily be extracted from the archive.

The location of the boot.img inside the Google Pixel 5’s Fastboot firmware

Special Case: Samsung

Samsung Galaxy devices don’t a traditional Fastboot interface, hence their factory images are packed differently.

• Use Samsung Firmware Downloader to download the factory image for your model.
• Unzip the decrypted package and locate the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5.

Step 3: Patching the boot image

Now that we have the boot image in hand, we should proceed with the patching part.

Case I: The value of the “Ramdisk” parameter is “Yes”

• Copy the boot image to your device. In fact, you can patch it on a different Android device than the target one, but you need to install the Magisk app on the secondary device as well.
• Press the Install button in the Magisk card.
• Choose Select and Patch a File in Method, and select the stock boot image.

• The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.

• Copy the patched image to your PC with ADB:
• Flash the patched boot image to your device. For most devices, reboot into Fastboot mode and flash with the following command:
• Reboot and enjoy root access!

Keep in mind that it is possible to patch the boot image on the fly on legacy devices having boot ramdisk through a custom recovery like TWRP, but the method is no longer recommended on modern devices. Having said that, if you have an old phone and want to stick with the custom recovery route, the steps are as follows:

• Download the Magisk APK.
• Rename the .APK file extension to .ZIP (e.g. Magisk-v23.0.APK в†’ Magisk-v23.0.ZIP).
• Flash the ZIP file just like any other ordinary flashable ZIP.

• Note that the sepolicy.rule file of modules may be stored in the cache partition, so don’t clear it.
• Check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.

Case II: The value of the “Ramdisk” parameter is “No”

In this case, you need to locate the recovery.img file from the factory image of your device instead of boot.img file. This is because Magisk needs to be installed in the recovery partition, which means you will have to reboot to the recovery mode every time you want root access.

• Copy the recovery image to your device (or a secondary device with the Magisk app installed).
• Press the Install button on the Magisk card.
• Choose “Select and Patch a File” in method, and select the stock recovery image.
• The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
• Copy the patched image to your PC with ADB:
• Flash the patched recovery image to your device. For most devices, reboot into Fastboot mode and flash with the following command:
• Reboot.

At this stage, there are three possible scenarios:

• Power up normally: You’ll end up with no Magisk, i.e. no root access.
• Recovery Key Combo в†’ Splash screen в†’ Release all buttons: The system should boot with Magisk and full root access.
• Recovery Key Combo в†’ Splash screen в†’ Keep pressing volume up: To access the stock recovery mode.

Special Case: Samsung

• Copy the extracted AP tar file to your device.
• Press the Install button on the Magisk card.
• If your device doesn’t have boot ramdisk, make sure Recovery Mode is checked in options.
• Choose Select and Patch a File in Method, and select the AP tar file.
• The Magisk app will patch the whole firmware file to [Internal Storage]/Download/magisk_patched_[random_strings].tar
• Copy the patched tar file to your PC with ADB:
  • Don’t try to copy over the MTP interface as it is known to corrupt large files.
• Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC from the original firmware.
  • Don’t choose HOME_CSC because we want to wipe data.
• Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
• If your device doesn’t have boot ramdisk, reboot to recovery now to enable Magisk.
• Install the latest Magisk app and launch the app. It should show a dialog asking for additional setup. Let it do its job and the app will automatically reboot your device.
• Reboot and enjoy root access!

Step 4: Verification

The last step is to verify that everything is working properly. Locate the newly installed Magisk app and open it. We want to see a version number beside the “Installed” parameter. This means you have successfully obtained root. Great job!

One-Click Root Methods in 2021: Kingroot, KingoRoot, and others

A few years back, several generic root methods like Kingroot, KingoRoot, and others gained popularity as “one-click root” methods, promising root and related benefits with minimal steps and knowledge needed by the user. However, as Android has matured, these one-click root methods are no longer valid for modern smartphones and Android devices in 2021.

We strongly dissuade against the use of these generic root methods as they are either ineffective or worse, pack in malware that can greatly compromise your device and cause you losses. Practically all of these methods are no longer recommended. You should follow the steps listed above for an effective root solution for most Android devices.

We hope this guide not only points you to the right threads for rooting your device but also provides general rooting instructions that can be applied for a large majority of Android devices generally. We’ll be updating this guide with links to further guides for specific phones, so check back again in the future.

Источник