Database Info

[OTA][KRT16S][GROUPER]signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip

This is just the Grouper KRT16S OTA package from Google. Bugfixes, 1.4Mb in size. ZIP file attached. I am not your tech support to get ADB working on you laptop or why your Nexus 7 does weird things after installing so don't be surprised if I ignore questions that can be answered by searching.
Original file name:
3aad414bf97cede8ecbc2027597e7f01bfe1ce47.signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
If you are stock and want to update from KRT16O then just drop the zip into your adb folder and sideload it in recovery:
Code:
adb sideload signed-nakasi-KRT16S-from-KRT16O-3aad414b.zip
Help this helps someone.

kpetrie77 said:
This is just the Grouper KRT16S OTA package from Google. Bugfixes, 1.4Mb in size. ZIP file attached. I am not your tech support to get ADB working on you laptop or why your Nexus 7 does weird things after installing so don't be surprised if I ignore questions that can be answered by searching.
Original file name:
3aad414bf97cede8ecbc2027597e7f01bfe1ce47.signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
If you are stock and want to update from KRT16O then just drop the zip into your adb folder and sideload it in recovery:
Code:
adb sideload signed-nakasi-KRT16S-from-KRT16O-3aad414b.zip
Help this helps someone.
Click to expand...
Click to collapse
I have a question. If this can be side loaded to recovery and I assume you mean twrp or cwm why can't it just be down loaded to device and flashed through recovery? Maybe I just don't understand what you mean by sideloaded. Thanks if you reply and if not I read the op and thanks for this
Sent from my HTCONE using Xparent Blue Tapatalk 2

Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.

ml_taz said:
Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.
Click to expand...
Click to collapse
Same for me, OTA went fine with TWRP

Received tonight at 02.30 cet!!! :good:

ml_taz said:
Also with unlocked Bootloader and TWRP I get this update OTA and installation went fine.
Click to expand...
Click to collapse
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Sent from my Nexus 7 using xda app-developers app

ianmedina said:
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
use adb sideload command, read the OP

ianmedina said:
How did you update via twrp?
Click to expand...
Click to collapse
I didn't update via TWRP! I get the update OTA! Also I have unlocked BL, Root and TWRP.
If you didn't get it via OTA you can sideload the Zip from Post #1.

ml_taz said:
I didn't update via TWRP! I get the update OTA! Also I have unlocked BL, Root and TWRP.
If you didn't get it via OTA you can sideload the Zip from Post #1.
Click to expand...
Click to collapse
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Sent from my Nexus 7 using xda app-developers app

ianmedina said:
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
platform-tools, SDK
View attachment 2404062

treIII said:
I have a question. If this can be side loaded to recovery and I assume you mean twrp or cwm why can't it just be down loaded to device and flashed through recovery? Maybe I just don't understand what you mean by sideloaded. Thanks if you reply and if not I read the op and thanks for this
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
The stock recovery does not look for a zip on the device without a command file telling it there is one present to flash.

ivn888 said:
platform-tools, SDK
View attachment 2404062
Click to expand...
Click to collapse
Thanks... But i think i'm gonna lose root?
Sent from my Nexus 7 using xda app-developers app

ianmedina said:
Thanks... But i think i'm gonna lose root?
Click to expand...
Click to collapse
No, doesn't touch su.
Sent from my HTC6500LVW using Tapatalk

kpetrie77 said:
No, doesn't touch su.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app

ianmedina said:
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......

What folder was this update downloaded too?

Re: OTA
bonzer2u said:
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......
Click to expand...
Click to collapse
The OTA process works with TWRP but reloads stock recovery AND removes root. No problem getting both back through the usual methods.

ianmedina said:
How about my twrp? I might lose it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It's a nexus. Its not hard to get back recovery and root.
Sent from my Nexus 7 using XDA Premium HD app

ianmedina said:
How did you update via twrp? I'm having bluetooth.apk error. It always fail. =(
Click to expand...
Click to collapse
ianmedina said:
Whefe can i find the adb folder? Sorry about the question..
Hopefully you can walkthrough me or tell me the step by step.
Click to expand...
Click to collapse
ianmedina said:
Thanks... But i think i'm gonna lose root?
Click to expand...
Click to collapse
ianmedina said:
How about my twrp? I might lose it.
Click to expand...
Click to collapse
I'm going to say some things not to be mean or rude but to keep you out of trouble. It is not installing because you do not know what you are doing and have not taken the initiative to learn some basics for yourself. Except for the fact you are not on the correct ROM to install this update in the first place, I would say losing root and TWRP would be the best thing for now.
You are going screw up your device and have no idea how to fix it yourself or even what information to provide for others to help you fix it. Your best bet would to be restoring to stock with a factory image and not screw around until you are up to speed.
There are ton of FAQ's and guides on this site in the general sections. Learn how to install and use ADB and fastboot. Read up on the different types up zip files and how they are installed. If you are using a one click, understand what ADB or fastboot commands are going on behind the scenes and exactly what it is pushing to your device.
Once you have a general understanding of things, please come and play around as much as you want. If you do something that causes a bootloop you will at least know how to recover your device.
bonzer2u said:
I believe the stock recovery will be installed with the update? but you can always reinstall TWRP with flashify......
Click to expand...
Click to collapse
ChauncyG said:
The OTA process works with TWRP but reloads stock recovery AND removes root. No problem getting both back through the usual methods.
Click to expand...
Click to collapse
A 5.4Mb recovery is not going to fit in a 1.4Mb zip file. Also see post 3, 4 and 8. Root and TWRP or CWM will remain intact. Bad information is worse than no information.

"Once you have a general understanding of things, please come and play around as much as you want. If you do something that causes a bootloop you will at least know how to recover your device.A 5.4Mb recovery is not going to fit in a 1.4Mb zip file. Also see post 3, 4 and 8. Root and TWRP or CWM will remain intact. Bad information is worse than no information."
Not trying to give bad info just relating my personal experience. You are correct that a full recovery image file at 5.4mb could not fit, even zipped, in a 1.4mb update, however, a full recovery image file is not needed to change the behavior of things. Root and the ability to boot back into TWRP were lost during my update process. It was easily corrected but it did happen. Others have reported a different experience. That was mine.
A good scientist reports ALL observations and reserves judgement until a complete data set is established.

[Q]Reflash stock rom

Is there any tool that will reinstall the stock rom on a Nexus 5 with LOCKED bootloader? Something like emergency reflash from LG Support Tool.

LG Support Tool? There's something LG Flashtool and that works.

albwh said:
Is there any tool that will reinstall the stock rom on a Nexus 5 with LOCKED bootloader? Something like emergency reflash from LG Support Tool.
Click to expand...
Click to collapse
If you have to reinstall the stock firmware why do you care? Just unlock the bootloader, you're going to lose everything anyway.
What situation are you in. There may be ways to save your data
Sent from my Nexus 5 using XDA Free mobile app

The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.

albwh said:
The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.
Click to expand...
Click to collapse
If you're rooted but otherwise completely stock, you should get OTA updates no problem.

albwh said:
The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.
Click to expand...
Click to collapse
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
There's a whole sticky on returning to stock so you can get OTAs. </thread>

If you're able to flash the stock ROM, you should be past the point where you need to worry about being able to get any updates.

Yeah. I'd highly recommend just flashing a prerooted busybox stock ROM. You can always do a dirty flash over stock ROM and still keep data.

jd1639 said:
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You do get the OTA, but if you modify /system/ or something else, the OTA won't install.

It takes 10 minutes to return to stock for an OTA. Just do what you want with the phone now and enjoy!
The next OTA will be months from now. Return to stock then.

You dont need any tool. Download factory image and flash that by executing flash-all.bat (for windows, if you use linux execute flash-all.sh). Flash a custom recovery. Then remove hidden tampered flag by flashing tampered flag remover zip. Then flash stock recovery and lock bootloader by typing fastboot oem lock.

yashade2001 said:
You dont need any tool. Download factory image and flash that by executing flash-all.bat (for windows, if you use linux execute flash-all.sh). Flash a custom recovery. Then remove hidden tampered flag by flashing tampered flag remover zip. Then flash stock recovery and lock bootloader by typing fastboot oem lock.
Click to expand...
Click to collapse
You can do the last 2 steps using bootunlocker from play
Sent from my Nexus 5 using Tapatalk

rootSU said:
You can do the last 2 steps using bootunlocker from play
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes that is an awesome app.

yashade2001 said:
Yes that is an awesome app.
Click to expand...
Click to collapse
Yeah agreed. I use it to keep my bootloader locked but so I can unlock it without a wipe on the fly.

rootSU said:
Yeah agreed. I use it to keep my bootloader locked but so I can unlock it without a wipe on the fly.
Click to expand...
Click to collapse
Why do you keep your bootloader locked?

yashade2001 said:
Why do you keep your bootloader locked?
Click to expand...
Click to collapse
So no one can get my data

rootSU said:
So no one can get my data
Click to expand...
Click to collapse
How someone can get my data if i have a unlocked bootloader?

yashade2001 said:
How someone can get my data if i have a unlocked bootloader?
Click to expand...
Click to collapse
Locking the bootloader isn't enough on its own.
Android: adb pull data, MTP (Screen lock can prevent)
Custom recovery: adb pull data, flash zip to turn off android lock screen (Recovery lock can prevent)
Lock bootloader: Prevent replacing locked recovery with unlocked recovery,

[Q] Help for Rooting.

Hi all.
Can anyone lend a hand to help me get my phone rooted again? I had originally rooted it when it first turned up, by using the guide on these forums. Since then I (stupidly) did the OTA upgrade not thinking about losing root. I went from 33r to 38r. The first I knew was when Titanium back up wouldn't back up.
My problem is that neither of my computers (desktop - XP) (Laptop - Windows 7) will now see my phone. They will both make a sound when connecting via the USB cable but neither of them show the phone via My Computer. I've un-installed/installed the drivers again and I have tried putting the phone in Fastboot and clicking on Unlock Bootloader, via the Toolbox V3, but the phone will only "reboot" to the home screen. I'm needing a bit of help from someone who knows what they are doing
Thanks in advance for any help... Foz

Once you unlock the bootloader, I don't think you need to unlock it again. If you lose root after an OTA, I think all you need to do is reflash superuser from recovery. And don't touch those toolboxes. They don't help you learn to solve these problems by yourself.
Sent from my A0001 using XDA Free mobile app

I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
OKay
reboot system, back to my normal settings/homescreen.
I have SuperSu on my phone BUT get the warning that no binary is installed and I need to re root, hencmy posting here.

adamfoz said:
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
Click to expand...
Click to collapse
If re-downloading the zip doesn't work you should try a newer SuperSU version.

meekrawb said:
If re-downloading the zip doesn't work you should try a newer SuperSU version.
Click to expand...
Click to collapse
I believe I have the latest version from the play store ( 2.14).

adamfoz said:
I believe I have the latest version from the play store ( 2.14).
Click to expand...
Click to collapse
Should have clarified, you should try a newer version of the zip.
download.chainfire.eu/supersu

Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys

adamfoz said:
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
Click to expand...
Click to collapse
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.

sparkdroid said:
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
Click to expand...
Click to collapse
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app

adamfoz said:
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
no flash twrp or any custom recovery in adb and then you can flash the root zip.

I'm following this guide for rooting http://forum.xda-developers.com/showthread.php?t=2788632 .
I'm assuming that I'm doing things ok to a point, as the CMD prompt is saying adb version is 1.0.32 but when i put the phone in fast boot, and type "fastboot devices" the phone will show up in the cmd prompt. Its when I "fastboot oem unlock" and"fastboot reboot", the phone will reboot as normal. No setting up of the phone. All my apps and settings are still there, indicating to me that something is wrong :/
I'm assuming that my drivers are ok otherwise I wouldn't be seeing the above in the cmd prompts but...
Can someone tell me if my mobile should show up in "my computer" ? it has in the past, but no longer does. and I'm wondering if this could have someing to do with my problems??
Thanks again..Foz

If your rooted, you have already unlocked the boot loader unless you relocked it. Did you? If not don't worry about unlock and flash custom recovery and flash supersu zip

I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk

adamfoz said:
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
All you need to do is flash SuperSU again. It's normal to lose root during an OTA update.
EDIT: didn't read properly. Have you gotten TWRP to flash yet?
Transmitted via Bacon

Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app

adamfoz said:
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon

timmaaa said:
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
Click to expand...
Click to collapse
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app

adamfoz said:
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader shouldn't lock again unless you do it yourself. The recovery (unnecessarily because you can uncheck the 'update cm recovery' option in Developer Options to keep your custom recovery) and root (no way around it) are lost during the OTA but the bootloader should remain unlocked. What response do you get when issuing the following command?
Code:
fastboot oem device-info
Please paste the results here.
Transmitted via Bacon

As soon as I'm home, I'll let you know.....
Thanks
Sent from my A0001 using XDA Free mobile app

Is there any way to root without using a pc like I did with my G3 using Stumproot?

Tried to lock bootloader and now can't boot.

Brand new Pixel 2. Unlocked bootloader and rooted with Magisk with no issues. Decided to return the phone. Booted into fastboot and ran the command to lock the bootloader and got stuck in fastboot with an error that I forgot to write down. I tried to reboot and now I'm just stuck on the white screen with the Google logo and the loading bar going on the bottom. I am able to boot back into bootloader.
Any ideas?
Thanks

Flash factory image and make sure your platform tools is updated i.e. adb and fastboot.
Sent from my walleye using XDA Labs

dobbs3x said:
Flash factory image and make sure your platform tools is updated i.e. adb and fastboot.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.

Even trying to sideload the OTA I get an error that the bootloader is the wrong version.

Ok, so now tried unlocking the bootloader again but still the same error that it's the wrong bootloader version.

thenags said:
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.[/QUOTE
You should post those errors here, they will help.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse

dobbs3x said:
thenags said:
I'm trying that now. Platform tools are fresh but now I'm getting an error that the bootloader version isn't correct. Trying to get that ironed out now.[/QUOTE
You should post those errors here, they will help.
Sent from my walleye using XDA Labs
Click to expand...
Click to collapse
This is what I'm getting no matter what I do;
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
I'm currently trying this;
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse

The script from that thread actually got me booting again but with bootloader unlocked. Let's see if I can lock it without it breaking again.

Alright. Back in action.
Thanks dobbs3x for the moral support lol.
For anyone in the future with a similar issue go to this thread and follow the steps;
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Rooted, installed Magisk and now phone won't boot

So after I unlocked my bootloader I used the all in one tool to root and flash Magisk Seemed to go ok, but when I went to reboot I'm stuck at the G screen and then it goes back to twrp.
I flashed the patched boot image but it still isn't working.
What do i need to do?

mpetruzz said:
So after I unlocked my bootloader I used the all in one tool to root and flash Magisk Seemed to go ok, but when I went to reboot I'm stuck at the G screen and then it goes back to twrp.
I flashed the patched boot image but it still isn't working.
What do i need to do?
Click to expand...
Click to collapse
Flash the stock boot image to both slots.
Sent from my [device_name] using XDA-Developers Legacy app

I ended up going back to stock and then redoing the root/magisk process and everything worked ok. Must have been a weird issue, but it's working now.

mpetruzz said:
I ended up going back to stock and then redoing the root/magisk process and everything worked ok. Must have been a weird issue, but it's working now.
Click to expand...
Click to collapse
That works too. Glad you got it working. Did you use a tool or fastboot?
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
That works too. Glad you got it working. Did you use a tool or fastboot?
Click to expand...
Click to collapse
I flashed the factory image via the all in one tool, then rooted and flashed magisk via the tool as well.
The only difference step I took was that I decrypted twrp. Not sure if that was the issue but I'm all working now!!

mpetruzz said:
I flashed the factory image via the all in one tool, then rooted and flashed magisk via the tool as well.
The only difference step I took was that I decrypted twrp. Not sure if that was the issue but I'm all working now!!
Click to expand...
Click to collapse
If you didn't allow modifications when twrp first booted that is the issue.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
If you didn't allow modifications when twrp first booted that is the issue.
Click to expand...
Click to collapse
I allowed for modifications, but didn't enter my password so it didn't decrypt

same problem here
jd1639 said:
Flash the stock boot image to both slots.
I also have the problem, but when i try to flash magisk, It got bootloop. after that I flashed boot.img, system can boot, but there is no magisk authority.
Click to expand...
Click to collapse

Kongfihy said:
jd1639 said:
Flash the stock boot image to both slots.
I also have the problem, but I can not find an .img file in the offical firmware. I extracted it but only got these files:
META-INF
care_map.txt
compatibility.zip
payload.bin (size: 1.2G, the largest)
payload_properties.txt
I assume that payload.bin may contain something I need, but I can not open it.
Click to expand...
Click to collapse
That's not the factory image. It looks more like it might be a custom rom of some sort. Google pixel factory image. You need the full image, not the ota. Extract this. Inside is another zip file, extract that too. In there you'll find the boot image.
Edit, what you extracted is the ota. I've never extracted one before so didn't recognize it. There's never been a reason to extract it.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

mpetruzz said:
So after I unlocked my bootloader I used the all in one tool to root and flash Magisk Seemed to go ok, but when I went to reboot I'm stuck at the G screen and then it goes back to twrp.
I flashed the patched boot image but it still isn't working.
What do i need to do?
Click to expand...
Click to collapse
Need to flash factory image
Do your restore/account setup
Let it finish
Reboot bootloader
Boot TWRP
Flash magisk
Reboot

Pie not working?
mpetruzz how did u do it