Database Develop

Download Lollipop LRX21P Factory Image for 2012 Nexus 7 WiFi Leaked!

Have at it boys!
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
MD5: e68948c23c918436680bd28fc6aaf983)
http://goo.gl/aYbCwf

IM guessing we can flash only system and boot...since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
ADB and Fastboot files attached below, if needed.

Mikey said:
IM guessing we can flash only system and userdata....since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
ADB and Fastboot files attached below, if needed.
Click to expand...
Click to collapse
Don't think that radio needs to be flashed on the N7
Cheers
Tom

I wouldn't flash the recovery partition, either.
The recovery-from-boot.p is in /system. I renamed it before the first boot using TWRP's file manager. I also flashed supersu. It's booting now...need to get to bed, though. Will report tomorrow.
Edit: Boot is successful. L.
Edit: This is my first go around with L. The checking for updates thing at sign on is interesting.

Flashed via fastboot and setting up now. I will report back with initial results and fire away any question you may want specifically answered.
FYI, first boot took about 6 minutes...

tom1807 said:
Don't think that radio needs to be flashed on the N7
Cheers
Tom
Click to expand...
Click to collapse
there is no radio in this....its wifi only....... the commands are generic

Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.

brizey said:
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
Click to expand...
Click to collapse
Probably needs a patch like for the N9.
Cheers
Tom

tom1807 said:
Probably needs a patch like for the N9.
Cheers
Tom
Click to expand...
Click to collapse
brizey said:
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
Click to expand...
Click to collapse
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm

Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
Yep...thanks.
Hmmm...this is not all that useful without Titanium. Will go back to KK in the AM and wait for a patched kernel.

Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
Have to try probably, not sure whether this will run on a newer build of Lollipop
Cheers
Tom

Kernel version?

Any major differences than the couple of versions built from source?
Fyi, you will probably need SuperSU beta 2.19 and modified boot image for root. There is a titanium backup that works with l (beta). There may be a command that reflashes stock recovery on reboot (it's in /system /bin).
Tibu:
https://docs.google.com/file/d/0Bwj2Hf45t6uMSElfSXR6YXdVdVU/edit?usp=docslist_api
SuperSU:
http://forum.xda-developers.com/showthread.php?t=2868133
Nexus 7 5.0

Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
tom1807 said:
Have to try probably, not sure whether this will run on a newer build of Lollipop
Cheers
Tom
Click to expand...
Click to collapse
Not good, the Boot.img is for Nexus 7 (2013)
Hangs at the Google logo.
Back to original Boot.img
Cheers
Tom

Mikey said:
IM guessing we can flash only system and boot...since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
Can I use these steps to clean flash the factory image?
I want to wipe everything and start from a fresh and clean flash.
I haven't flashed a factory image for a long time so I'm out of shape ?

Could someone make a flashable zip for multirom or normal flashing. ?

Nexus Root Toolkit
has anyone tried flashing this via nexus root toolkit? that software recently goot updated to 1.9.3 and has the abiloity to flash the Lollipop factory preview on those devices that got it.

That is exactly way I did. Started fresh and running smooth so far!

I used the toolkit to flash latest TWRP but that was all.

qualitymove13 said:
Flashed via fastboot and setting up now. I will report back with initial results and fire away any question you may want specifically answered.
FYI, first boot took about 6 minutes...
Click to expand...
Click to collapse
I was just going to ask about the boot time lol taking forever

How do I change the radio and boot loader?

Go easy....
Wanting to flash some of the newer M ROMs.
Requirements are latest radio, boot loader and TWRP
How do I change those?
I'm root and twrp installed. Are there zips to flash in recovery 1st?
Steps or even a video would be HUGE, and thank you for helping.

The information is everywhere. You have to flash the radio/bootloader in fastboot mode. You can't flash them in recovery.

SirBindy said:
The information is everywhere. You have to flash the radio/bootloader in fastboot mode. You can't flash them in recovery.
Click to expand...
Click to collapse
I beg to differ :
http://forum.xda-developers.com/showthread.php?t=3066052
This is how i did it, in recovery.
It's all just an illusion

robfromga said:
Go easy....
Wanting to flash some of the newer M ROMs.
Requirements are latest radio, boot loader and TWRP
How do I change those?
I'm root and twrp installed. Are there zips to flash in recovery 1st?
Steps or even a video would be HUGE, and thank you for helping.
Click to expand...
Click to collapse
I was in a similar situation, I have MultiRom, and I wanted to preview M out without getting rid of PureNexus. So this is what I did
Download factory image for M
Make sure you have the latest android SDK!!!
extract the factory image
rename bootloader file to bootloader.img; rename radio file to radio.img
connect your device and reboot into bootloader
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
then reboot your phone, and you are good
if you are uncertain about it, take a look at flash-base.sh, or flash-all.bat, and follow those steps.

most bootloaders and radios ARE available via a flashable zips that can be flashed via twrp, you just have to look for them. otherwise, fastboot is very easy.

I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?

robfromga said:
I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?
Click to expand...
Click to collapse
If you flashed the marshmallow radio, the baseband should end in .27r.
It's all just an illusion

robfromga said:
I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?
Click to expand...
Click to collapse
i dont think you can flash the bootloader via flashify.

Does flashing marshmallow factory image not update the boot loader and radio with it ? Ie flashing marshmallow from NRT toolkit ?

bigup7 said:
Does flashing marshmallow factory image not update the boot loader and radio with it ? Ie flashing marshmallow from NRT toolkit ?
Click to expand...
Click to collapse
if you flash the whole thing it does.

simms22 said:
if you flash the whole thing it does.
Click to expand...
Click to collapse
Ahh great. Had me confused for a bit

bigup7 said:
Ahh great. Had me confused for a bit
Click to expand...
Click to collapse
if youre rooted, and dont want to go through the process again, and dont want to lose your data, all you have to do is flash the boot.img and the system.img to update the rom. and then reflash supersu in twrp

Right baseband?

robfromga said:
Right baseband?
Click to expand...
Click to collapse
That's what I have. You should be good.
It's was all just an illusion

Sweet!
So if I'm understanding everything, I'm now on the latest update of TWRP ,bootloader and radio....so its OK to flash M?

Yep
It's was all just an illusion

When will the Android One moto x4 get TWRP?

??

chandypandy said:
??
Click to expand...
Click to collapse
TWRP
https://forum.xda-developers.com/moto-x4/development/root-moto-x4-t3696180

icarolessa said:
TWRP
https://forum.xda-developers.com/moto-x4/development/root-moto-x4-t3696180
Click to expand...
Click to collapse
Tried, doesn't work for the google fi variant

chandypandy said:
Tried, doesn't work for the google fi variant
Click to expand...
Click to collapse
TWRP Official
https://dl.twrp.me/payton/twrp-3.2.1-0-payton.img.html

It doesn't work

Works for my Android One X4

I think it is probably better to start with
https://twrp.me/motorola/motorolamotox4.html

chandypandy said:
It doesn't work
Click to expand...
Click to collapse
What problem are you having? Did you enable usb debugging?

The hardware is the same.

Twski said:
The hardware is the same.
Click to expand...
Click to collapse
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error

icarolessa said:
What problem are you having? Did you enable usb debugging?
Click to expand...
Click to collapse
https://dl.xda-developers.com/4/4/6....png?key=wua4zgqvFDcsrdLnpuLl_w&ts=1522291710

Our devices don't have a recovery partition to flash to.
Read the install instructions correctly:
https://twrp.me/motorola/motorolamotox4.html
You should use "fastboot boot twrp-3.2.1-0-payton.img" instead.
Then, follow along:
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your password, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
Click to expand...
Click to collapse

chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
I think the right command is this:
fastboot flash boot [file name].img

No,
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image.
Click to expand...
Click to collapse

chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
I could be wrong but it seems like you are trying to flash TWRP to the recovery partition and there's no such thing on this phone. You have to temporarily boot TWRP and the keep following the instructions.

Is anybody able to backup / restore the phone with android one on encrypted file system??, im using the official twrp, but restoring backups just cause bootloops

is it necessary to unlock the bootloader before?

If you're asking if the bootloader needs to be unlocked to install magisk, absolutely!

Sorry for the dumb question but how do you unlock the bootloader on the Fi Android one Version?

Potential fix
chandypandy said:
https://dl.xda-developers.com/4/4/6....png?key=TLP9_o5Ecn2Dys5ZhIE3tw&ts=1522291461
This is the error
Click to expand...
Click to collapse
If you are still haven't fixed this yet the issue is you need to fastboot boot the boot twrp image and then flash the flash image inside twrp. The guide on TWRP official will give you a guide on how to do this, the files required are also there.

OPPO Reno - how to ROOT

Hello guys.
How can I root my device Oppo Reno?

Have you tried kingroot APK ?

Doesn't work

Possible root method
Anyone got a copy of boot.img for snapdragon 710 version as I have found a way to root

Do share with us.

Root
If someone has boot.img I can use magisk to root the IMG then flash it . Some tried on oppo find x and it worked

I have it.

SjDU said:
I have it.
Click to expand...
Click to collapse
pm it to @jsmith20094

Boot.img
SjDU said:
I have it.
Click to expand...
Click to collapse
Has anyone got a copy of boot.img for oppo Reno PCAM00 A.14 ?
THANKS

jsmith20094 said:
Has anyone got a copy of boot.img for oppo Reno PCAM00 A.14 ?
THANKS
Click to expand...
Click to collapse
you have PM

jsmith20094 said:
If someone has boot.img I can use magisk to root the IMG then flash it . Some tried on oppo find x and it worked
Click to expand...
Click to collapse
Isn't the bootloader locked and fastboot disabled? How would we be able to flash the new boot file?

wolfgart said:
you have PM
Click to expand...
Click to collapse
I have patched the boot.img but I can't go into fastboot mode it just reboots the OS any ideas I have already enabled oem unlock in dev settings ?

jsmith20094 said:
I have patched the boot.img but I can't go into fastboot mode it just reboots the OS any ideas I have already enabled oem unlock in dev settings ?
Click to expand...
Click to collapse
You were saying that in the same method someone gain root on Find X ?
Should be the same here

They did but I don't know how to unlock bootloader

jsmith20094 said:
They did but I don't know how to unlock bootloader
Click to expand...
Click to collapse
It seems that OPPO will release Deep Test for Reno too after 3 Months starting selling it in China ...

I don’t know what starts in the recovery. When you tap “Ver 1.2” for about 5 times. A pop up appears it say something like “ Test Case 1 .. it will cost about an hour”

Stock boot.img and patched magisk boot.img
Here I have provided the boot.img and Patched Magisk boot.img
Stock boot.img
https://drive.google.com/file/d/1-1suHaaCT-Sc3pSOb7Lh6_pRRXEnGlC7/view?usp=drivesdk
Magisk patched boot.img
https://drive.google.com/file/d/1-0Spo-IriS9PmMF82EkVA0vqyyBjfjSG/view?usp=drivesdk

jsmith20094 said:
Here I have provided the boot.img and Patched Magisk boot.img
Stock boot.img
https://drive.google.com/file/d/1-1suHaaCT-Sc3pSOb7Lh6_pRRXEnGlC7/view?usp=drivesdk
Magisk patched boot.img
https://drive.google.com/file/d/1-0Spo-IriS9PmMF82EkVA0vqyyBjfjSG/view?usp=drivesdk
Click to expand...
Click to collapse
do you have tested that ?

@jsmith20094
How to flash with locked bootloader as for now it's impossible to unlock? Thanks

At the moment we cant flash it but as soon as oppo launch the deep program for it you simply install there APK and it allows you to unlock fast boot . As soon as it launches I will post APK with instructions

Can't enter recovery to sideload OTA

Trying to sideload the December OTA. Rooted with Magisk. Boot into bootloader, select recovery, then I get the google logo (not the red exclamation mark, the Google logo) , but won't enter recovery, just hangs on the logo. Do I need to disable or uninstall Magisk?

Gloff said:
Trying to sideload the December OTA. Rooted with Magisk. Boot into bootloader, select recovery, then I get the google logo (not the red exclamation mark, the Google logo) , but won't enter recovery, just hangs on the logo. Do I need to disable or uninstall Magisk?
Click to expand...
Click to collapse
You need to uninstall magisk and then enable the stock boot.img which is where the recovery resides.

Badger50 said:
You need to uninstall magisk and then enable the stock boot.img which is where the recovery resides.
Click to expand...
Click to collapse
That's new, didn't have to do that with the 3 XL. Do I use the stock boot.img from the currently installed update (december)? Also, how to I flash the stock boot.img, through fastboot?

Gloff said:
That's new, didn't have to do that with the 3 XL. Do I use the stock boot.img from the currently installed update (december)? Also, how to I flash the stock boot.img, through fastboot?
Click to expand...
Click to collapse
Although I never do OTA's, I prefer fastbooting updates, most everything I've read is to uninstall magisk, then restore the stock boot.img which magisk will do for you. So it's either that is causing his problem, or he has an issue with his stock recovery.

Badger50 said:
Although I never do OTA's, I prefer fastbooting updates, most everything I've read is to uninstall magisk, then restore the stock boot.img which magisk will do for you. So it's either that is causing his problem, or he has an issue with his stock recovery.
Click to expand...
Click to collapse
You're talking to the OP. I couldn't update Magisk with the last update, it said installation failed. Should I just flash the stock boot.img?

Gloff said:
You're talking to the OP. I couldn't update Magisk with the last update, it said installation failed. Should I just flash the stock boot.img?
Click to expand...
Click to collapse
Yes

p70shooter said:
Yes
Click to expand...
Click to collapse
I assume the boot.img from December Update, yes?

Gloff said:
I assume the boot.img from December Update, yes?
Click to expand...
Click to collapse
Yes. fastboot flash boot boot.img :good:

Gloff said:
I assume the boot.img from December Update, yes?
Click to expand...
Click to collapse
Yea if you're flashing that one. I would just flash the whole December image using flash all, saves messing around with Ota then but that's me

p70shooter said:
Yea if you're flashing that one. I would just flash the whole December image using flash all, saves messing around with Ota then but that's me
Click to expand...
Click to collapse
I was always worried about wiping my devices, that's why I usually sideload the OTA rather than removing the -w flag.

Gloff said:
I was always worried about wiping my devices, that's why I usually sideload the OTA rather than removing the -w flag.
Click to expand...
Click to collapse
Ah that makes sense, I always double or triple check that I've removed the -w but I have forgotten before lol

p70shooter said:
Ah that makes sense, I always double or triple check that I've removed the -w but I have forgotten before lol
Click to expand...
Click to collapse
Hahahahahaha....I think I remember a couple of those! ?

The Guide should be updated for flashing both slots, I've never been able to get fastboot flash boot --slot all boot.img to work, so I've always flashed both slots individually using
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Is there a new command for flashing both slots simultaneously?

So when updating, do you guys just flash the entire updated factory image when a new update is released? No need to uninstall Magisk, so you don't have to flash the previous update's boot.img?
In other words do you flash new full factory image>patch boot.img>flash magisk_patched> done VS.
Flash old stock boot.img>OTA/Factory image>patch boot.img>flash magisk_patched>done?
This has never been clear to me as far as new updates go. I feel like the guide should have an "I'm rooted and just want to update to the latest security patch" section.

Gloff said:
The Guide should be updated for flashing both slots, I've never been able to get fastboot flash boot --slot all boot.img to work, so I've always flashed both slots individually using
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Is there a new command for flashing both slots simultaneously?
Click to expand...
Click to collapse
Might try this one. Always seems to work for me :good:
fastboot flash boot boot.img --slot=all
Then substitute magisk_patched.img for boot.img when you want to flash the rooted version of the kernel to both slots :good:

Badger50 said:
Might try this one. Always seems to work for me :good:
fastboot flash boot boot.img --slot=all
Then substitute magisk_patched.img for boot.img when you want to flash the rooted version of the kernel to both slots :good:
Click to expand...
Click to collapse
Will try this command after I finish updating to January. Who wrote the guide? They have it as: fastboot flash boot --slot all magisk_patched.img.
They should update it if the order is backwards, since it's never worked for me using the guide's script.
Edit: fastboot flash boot boot.img --slot=all did not work either. I used the boot_a/boot_ b method and it worked fine.

Gloff said:
Will try this command after I finish updating to January. Who wrote the guide? They have it as: fastboot flash boot --slot all magisk_patched.img.
They should update it if the order is backwards, since it's never worked for me using the guide's script.
Click to expand...
Click to collapse
There are few guides, depends on which one your referring too. It's actually not backwards as either will work. Probably just a syntax error or typo :good:

Badger50 said:
There are few guides, depends on which one your referring too. It's actually not backwards as either will work. Probably just a syntax error or typo :good:
Click to expand...
Click to collapse
This Guide: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
I attached my command window log.

Gloff said:
This Guide: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
I attached my command window log.
Click to expand...
Click to collapse
Maybe try the = sign between slot and all
Looks like the one I gave you works though :good:

Badger50 said:
Maybe try the = sign between slot and all
Looks like the one I gave you works though :good:
Click to expand...
Click to collapse
Tried that, middle of the attachment results in fastboot: unknonw option --slot=all