P Developer Preview 1 is here!
https://developer.android.com/preview/index.html
Keep in mind:
Performance and battery
System and app performance is known to be periodically slow and janky, and devices may become occasionally unresponsive. These problems may become more acute with prolonged use.
Battery life may be regressed in this early release for screen-on and screen-off use cases.
https://developer.android.com/preview/release-notes.html
I am not able to spend the time flashing DP1 at the moment, but if someone does, I would be extremely appreciative if they could let me know if the multi-touch bug introduced in Android 8.1.0 has been fixed! Thanks in advance... https://issuetracker.google.com/issues/70344455
Unless you don`t flash it on your daily driver i suggest to wait till the second version wich is ususaly more stable.
gee2012 said:
Unless you don`t flash it on your daily driver i suggest to wait till the second version wich is ususaly more stable.
Click to expand...
Click to collapse
Do the locked Verizon pixels have the ability to flash this? And if they do, can they flash back?
How did you guys flash Android P. i keep getting errors when i click flash all.bat
DaKoin said:
How did you guys flash Android P. i keep getting errors when i click flash all.bat
Click to expand...
Click to collapse
I had the same issue, I had to update my platform-tools through the sdk manager, and used the flash-all command from the cmd.
didnt work for me
Thanks for replying. I downloaded the latest platform tools as well. when you say you used the flash all command you mean the flash-all.bat file found in the goolge factory image zip file...i did that but it gave a few errors then booted back up and i was still on android 8.1.0.
renzo.olivares said:
I had the same issue, I had to update my platform-tools through the sdk manager, and used the flash-all command from the cmd.
Click to expand...
Click to collapse
Has anyone uploaded the notification sounds from Android P yet? If so, link me up! ?
Hmm looking at videos of it I'm not sure if I like the new notification panel/quick toggles but I do enjoy seeing all those good features they have put in hopefully more will come with future previews
And who knows maybe the new panel will grow on me like the lighter theme on oreo did lol
DaKoin said:
Thanks for replying. I downloaded the latest platform tools as well. when you say you used the flash all command you mean the flash-all.bat file found in the goolge factory image zip file...i did that but it gave a few errors then booted back up and i was still on android 8.1.0.
Click to expand...
Click to collapse
What I meant was I used the included flash-all.sh. So what I did was extract the factory images contents into the platform-tools folder. Then I navigated to the platform-tools folder using command prompt and then ran the "flash-all" command. Hope that helps
didnt work for me
that didnt work, it says at the end :
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0067.00'.
renzo.olivares said:
What I meant was I used the included flash-all.sh. So what I did was extract the factory images contents into the platform-tools folder. Then I navigated to the platform-tools folder using command prompt and then ran the "flash-all" command. Hope that helps
Click to expand...
Click to collapse
DaKoin said:
that didnt work, it says at the end :
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0067.00'.
Click to expand...
Click to collapse
Have you tried flashing the march image first, then the developer preview? That is also one of the steps i took when having problems but am unsure if that solved it.
Well it looks ugly as fcuk!
Bingley said:
Well it looks ugly as fcuk!
Click to expand...
Click to collapse
Yup, I don't like the settings icons at all
Do you have any screenshots to show what they are like?
Many thanks in advance
DaKoin said:
How did you guys flash Android P. i keep getting errors when i click flash all.bat
Click to expand...
Click to collapse
Which phone are you using? And is it operator locked?
Sent from my Pixel 2 XL using Tapatalk
---------- Post added at 04:38 PM ---------- Previous post was at 04:33 PM ----------
DaKoin said:
How did you guys flash Android P. i keep getting errors when i click flash all.bat
Click to expand...
Click to collapse
Also if you are using pixel 2 xl. You will have to unlock critical files after unlocking the bootloader. $fastboot flashing unlock_critical
Sent from my Pixel 2 XL using Tapatalk
Android P screenshots
had to resort to a custom script
I tried flashing march factory image it was giving problems just the same. i used toolkit that didnt help either what i tried was to use deuces toolkit and that worked and i flashed march update. then i tried to do Android P still wouldnt work. used Deuces toolkit with android p and it worked like a charm.
renzo.olivares said:
Have you tried flashing the march image first, then the developer preview? That is also one of the steps i took when having problems but am unsure if that solved it.
Click to expand...
Click to collapse
---------- Post added at 07:03 AM ---------- Previous post was at 06:56 AM ----------
I'm using Pixel 2 and it is not locked. I tried critical unlock, that did not work, so i just used regular "fastboot flashing unlock " i go tit to work in the end but i had to use Deuces custom script to flash the files.
arnavde said:
Which phone are you using? And is it operator locked?
Sent from my Pixel 2 XL using Tapatalk
---------- Post added at 04:38 PM ---------- Previous post was at 04:33 PM ----------
Also if you are using pixel 2 xl. You will have to unlock critical files after unlocking the bootloader. $fastboot flashing unlock_critical
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Which kernel version is used ?
I flashed it from Mac on pixel 2 from Google and had no issues. The settings UI is different but overall, pretty solid. Not had any issues so far.
One issue I experienced was not able to modify DND for car driving mode. I wanted to set it to priority and it stays in alarm only.
The options you see when you long press to get to launcher settings is always visible in a layer if you watch closely. This becomes more visible when you pull up the drawer.
Related
This is the same as any other Nexus device.
WARNING. As is normally the case, this WILL factory reset your device.
Install the Android SDK (and Google USB driver).
Android SDK
Google USB Driver (Windows)
Enable USB debugging on the Nexus 7.
Unlock Developer Options by going to Settings > About Tablet and clicking on the build number seven times.
Go to Settings > Developer Options and check USB debugging. Click OK on the warning.
Connect the Nexus 7 via USB and reboot the Nexus 7 into the bootloader.
Note: Users have reported failures and "Access is Denied" errors when connected via USB 3.0 ports so use USB 1.1 or 2.0 to be on the safe side.
Open a command line / terminal and navigate to your SDK platform-tools directory.
Enter
Code:
adb reboot bootloader
and hit enter.
Once the Nexus 7 boots to the bootloader, unlock it
At the command line / terminal enter
Code:
fastboot oem unlock
and press enter.
On the Nexus 7, use the volume up button to select 'Yes' on the 'Unlock bootloader?' screen.
Press the power button to save your choice and verify on the next screen that you see 'LOCK STATE - UNLOCKED' at the bottom.
Use your volume keys to select 'Start' and click the power button to factory reset and reboot.
Enjoy your unlocked bootloader!
Do you have the usb drivers installed? That happened to me ("old" n7) when I didn't have the usb drivers installed.
may need to update your drivers for it to be able to see the device.
when you try adb devices while it is on does it kick back the device id number?
i haven't tried yet as i knew the drivers out currently would be an issue.
gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?
gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.
mrancier said:
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?
Click to expand...
Click to collapse
I updated my SDK when 4.3 dropped but I did have to go snag the Google USB driver and install it to get the N7 to be recognized.
ATGAdmin said:
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.
Click to expand...
Click to collapse
1. You may be right (as far as my posts go) but how am I to ever make a dev post if I'm not allowed to make a first post in a dev forum?
2. This /is/ a dev-related post.
3. My feelings wouldn't be hurt if the mods felt the need to move the post.
Yeah I had to install the google usb drivers from the SDK in device manager of Windows to get the n7 recognized.
Thanx. Just got home with my new nexus 7....bootloader now unlocked :highfive:
Nevermind it literally is that as the command.
Sent from my Nexus 7 using Tapatalk 4 Beta
keynith said:
Can you update it with the commands? So people don't have to search
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The commands are there...
Also, unlocked mine not 5 minutes after opening on Ubuntu 13.10.
no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery
Worked great thanks!
---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------
smirkis said:
no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery
Click to expand...
Click to collapse
Make sure you update your files from the SDK Manager. It had updated USB driver which from there it would install the proper drive and then it worked form me.
The trick, as stated in the Nexus Toolkit after driver install, is that you need to change the tablets usb settings from MTP to PTP. Tablet was immediately seen using "old" nexus toolkit universal usb drivers (old = i did not download the new SDK). I choose toro 4.2.2 (because it doesn't matter for unlocking) and then told it to unlock. worked like a charm.
Now the question is ... how long does it take to reboot cause mine is taking forever!!!
OK it booted. So yeah the Nexus 7 Toolkit ver 5.0 worked just fine to at least unlock. I did not root (4.3 still too buggy) or install a custom recovery yet.
Stock recovery, pretty please?
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!
My body and my 7 are ready for a recovery!
Thank you!
treoo0_1 said:
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!
Click to expand...
Click to collapse
I'd be happy to, but am having a hard time finding the correct ADB command.
isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch
adb pull
jc monkeyballs said:
I'd be happy to, but am having a hard time finding the correct ADB command.
Click to expand...
Click to collapse
Can you use
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example:
Code:
adb pull /system/recovery.img C:\Android\Local
Thanks for offering to help!
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Lpuboy87 said:
isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch
Click to expand...
Click to collapse
Yep. Razor.
Branch = Razor
codename = Asus flo
Wifi Model: ME371K
followed the first post and it worked....used this for the commands
ADB Commands
---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------
treoo0_1 said:
Yep. Razor.
Click to expand...
Click to collapse
yeah thought so. :good::highfive:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
Assuming that the ROM is still there, you can dirty flash the ROM zip over it, and see if it works. There's no harm in trying that.
But "No OS Installed" simply means that your /system or /boot parition are not detected (means, they are empty). Now of course, the last resort is to flash the ROM all over again.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
You need to provide more information. Are you on the stock ROM or a custom ROM? Stock recovery or TWRP? Had you made any changes to the device recently?
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download any ROM ( like pure Nexus) and gapps
You can use USB otg to flash the ROM using twrp or transfer the ROM file from your PC to your phone in twrp (it supports mtp)
Simply flash ROM and gapps and viola
Sent from my Nexus 6P using XDA Labs
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
i42o said:
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Click to expand...
Click to collapse
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
StormCell said:
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
Click to expand...
Click to collapse
Please continue the discussion in the other thread that you posted this question in, as I said, let's not create duplicate discussions.
StormCell said:
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
Click to expand...
Click to collapse
Developer preview 3 is a Android N preview and it is very fluid, battery life is good on stock and reason I recommend this because it is simple to do, gives you good options within the ROM and is good overall but that's just my opinion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
Heisenberg said:
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
Click to expand...
Click to collapse
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
i42o said:
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
Click to expand...
Click to collapse
Lol. Maybe you missed the title under my name.
The dev preview isn't what he asked for, it isn't an easy solution, it isn't easy to come back from if he doesn't like it, it isn't even remotely what he needs. What he's looking for is a simple way to get his phone booted up and working again (a very simple request), and what you're suggesting is he install a beta OS (a complicated "solution").
If you really have a problem with a moderator requesting that a member posts in one place at a time (as per our rules), then I'm gobsmacked. If you'd care to look at the advice I gave him in the guide thread where he also posted you'd notice that I gave two solutions that:
A) Actually address the simplicity of his problem.
B) Give two simple, easy to execute, solutions that are the most common solutions you'll ever see anyone give a member in his situation. Solutions that don't involve having to install a developer preview that he never asked for.
I get that you're trying to help him, but the "solution" you provided him isn't right for his situation at all. There was no need to become defensive and aggressive when this was pointed out.
Vishal Vignesh said:
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
Click to expand...
Click to collapse
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
StormCell said:
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
Click to expand...
Click to collapse
Sure, this method is for those who do not wanna copy the zip package to the PC/don't have it
Sent from my GT-N7100 using XDA-Developers mobile app
I'm currently on Pure Nexus and would like return my phone to factory stock.
Reason being, my phone is almost useless for phone calls due to echoes on the other end, and I haven't found a working fix and am getting desperate.
I've backed up via TWRP and Titanium and am looking for the easiest procedure to go to stock (and then return to my nandroid backup later).
Thanks!
Mike
resarfekim said:
I'm currently on Pure Nexus and would like return my phone to factory stock.
Reason being, my phone is almost useless for phone calls due to echoes on the other end, and I haven't found a working fix and am getting desperate.
I've backed up via TWRP and Titanium and am looking for the easiest procedure to go to stock (and then return to my nandroid backup later).
Thanks!
Mike
Click to expand...
Click to collapse
https://developers.google.com/android/images
The easiest way is to download the factory image from Google, unzip the image, put your phone into bootloader and run flash-all.bat command in fastboot. Flashing each piece individually like XDA Guide suggests is not a good idea if you want to do a clean install and flash-all.bat works because it's too easy to miss a step and screw up something. I like flash-all.bat because it's designed to be idiot proof and it has worked every time for me. Some people prefer to make things more complicated than they need to be. Your bootloader will still be unlocked and its easy to flash custom recovery again if and when you want.
Will Flash-all.bat flash the userdata.img too? Because im on a 128gb Nexus 6p and i dont want to have a 32gb version..
kutinho said:
Will Flash-all.bat flash the userdata.img too? Because im on a 128gb Nexus 6p and i dont want to have a 32gb version..
Click to expand...
Click to collapse
Yeah, you'll have to format userdata to get your storage back... Or you can follow this guide:
This part: 11.https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
kutinho said:
Will Flash-all.bat flash the userdata.img too? Because im on a 128gb Nexus 6p and i dont want to have a 32gb version..
Click to expand...
Click to collapse
You will lose your actual user data but your phone won't lose any storage capacity. I have a 128gb version myself and have used flash-all.bat multiple times when I ran into issues and needed to return to stock and there's never been a problem where the storage space was reduced like you are concerned about.
jhs39 said:
You will lose your actual user data but your phone won't lose any storage capacity. I have a 128gb version myself and have used flash-all.bat multiple times when I ran into issues and needed to return to stock and there's never been a problem where the storage space was reduced like you are concerned about.
Click to expand...
Click to collapse
Hey... I'm really confused here... Please could you be kind enough to explain me which magic trick altered the userdata partition of a lot of people who complained having only a ~20gb userdata partition on a 64 or 128GB N6P after they have been using the flash-all method? Either in Q/A or in Heisenberg's thread in general section. You must be lucky. Have you modified the flash-all file maybe? Thanks...
5.1 said:
Hey... I'm really confused here... Please could you be kind enough to explain me which magic trick altered the userdata partition of a lot of people who complained having only a ~20gb userdata partition on a 64 or 128GB N6P after they have been using the flash-all method? Either in Q/A or in Heisenberg's thread in general section. You must be lucky. Have you modified the flash-all file maybe? Thanks...
Click to expand...
Click to collapse
I don't use Heisenberg's method which involves flashing everything separately. The flash-all bat command flashes everything automatically and does nothing whatsoever that changes your storage capacity . Maybe you should go to Google's download page and look at their instructions for flashing a factory image. There are no steps to using flash-all.bat to retain the proper storage capacity. I've encountered many, many people who have been confused by Heisenberg's ludicrously complicated flashing instructions, did everything separately like he suggested and then ended up screwing up their phone.
5.1 said:
Hey... I'm really confused here... Please could you be kind enough to explain me which magic trick altered the userdata partition of a lot of people who complained having only a ~20gb userdata partition on a 64 or 128GB N6P after they have been using the flash-all method? Either in Q/A or in Heisenberg's thread in general section. You must be lucky. Have you modified the flash-all file maybe? Thanks...
Click to expand...
Click to collapse
For what it's worth, I've never had an issue with storage size after using flash-all.bat on my 64gb 6P. Just make sure you use the most recent Platform Tools available here: https://developer.android.com/studio/releases/platform-tools.html
jhs39 said:
I don't use Heisenberg's method which involves flashing everything separately. The flash-all bat command flashes everything automatically and does nothing whatsoever that changes your storage capacity . Maybe you should go to Google's download page and look at their instructions for flashing a factory image. There are no steps to using flash-all.bat to retain the proper storage capacity. I've encountered many, many people who have been confused by Heisenberg's ludicrously complicated flashing instructions, did everything separately like he suggested and then ended up screwing up their phone.
Click to expand...
Click to collapse
Ah... Strange that flashing manually changes it to a 32gb model partition... I have never flashed using flash-all.bat, because there was several times where it bricked devices, so i've always flashed manually. Without userdata.img though, so i've never experienced this problem. Thanks..!
Pig Vomit said:
For what it's worth, I've never had an issue with storage size after using flash-all.bat on my 64gb 6P. Just make sure you use the most recent Platform Tools available here: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Yeah, it looks like only manual userdata flash changes its size in case the device is not a 32gb one... Thanks!
Pls help. When i choose flash-all.bat it gives me an "archive does not contain boot.sig and recovery.sig error.. whats that?
kutinho said:
Pls help. When i choose flash-all.bat it gives me an "archive does not contain boot.sig and recovery.sig error.. whats that?
Click to expand...
Click to collapse
Hey...
Is your phone properly detected in bootloader when you type:
fastboot devices
If you haven't yet updated ADB/fastboot, download the latest here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And retry maybe. Otherwise, there's a lot of results when you type:
"archive does not contain boot.sig" using Google.
Good luck...
5.1 said:
Hey...
Is your phone properly detected in bootloader when you type:
fastboot devices
If you haven't yet updated ADB/fastboot, download the latest here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And retry maybe. Otherwise, there's a lot of results when you type:
"archive does not contain boot.sig" using Google.
Good luck...
Click to expand...
Click to collapse
Thanks for your help but no luck so far... fastboot detects my Nexus and i got the latest adb/fastboot tools.. Will research a bit more
kutinho said:
Thanks for your help but no luck so far... fastboot detects my Nexus and i got the latest adb/fastboot tools.. Will research a bit more
Click to expand...
Click to collapse
Just try flashing manually... You can look at the link I gave you before... Just don't flash userdata.img... Let me know if it works...
5.1 said:
Just try flashing manually... You can look at the link I gave you before... Just don't flash userdata.img... Let me know if it works...
Click to expand...
Click to collapse
Try to do it manually, now its stucked by fastboot flash system system.img for 3 minutes and it does nothing..
---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------
okay, its doing its thing, but its way too slow.. on youtube the whole thing was 90 seconds or so, not 90 minutes
After succesfully flashing, it gives me an Android process stopped problem
Had to wipe data back to factory setting in recovery and it works now
Thanks man
5.1 said:
Hey...
Is your phone properly detected in bootloader when you type:
fastboot devices
If you haven't yet updated ADB/fastboot, download the latest here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And retry maybe. Otherwise, there's a lot of results when you type:
"archive does not contain boot.sig" using Google.
Good luck...
Click to expand...
Click to collapse
I get that all the time.
I just ignore it.
kutinho said:
Try to do it manually, now its stucked by fastboot flash system system.img for 3 minutes and it does nothing..
---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------
okay, its doing its thing, but its way too slow.. on youtube the whole thing was 90 seconds or so, not 90 minutes
After succesfully flashing, it gives me an Android process stopped problem
Had to wipe data back to factory setting in recovery and it works now
Thanks man
Click to expand...
Click to collapse
Wow... Finaly! I have never had a slow flash like that. Yeah it usually takes ~ 1 minute to complete. Strange. Anyway, you solved your problem.
Cheers...
5.1 said:
Ah... Strange that flashing manually changes it to a 32gb model partition... I have never flashed using flash-all.bat, because there was several times where it bricked devices, so i've always flashed manually. Without userdata.img though, so i've never experienced this problem. Thanks..!
Thanks for the reminder. It's been a little while and I forgot how easy the Heisenberg method is so I just flash-alled and got an endless boot animation. Caught your comment and remembered that doing it that way fixed this once before. Always seems like the flash-all should be fast and work well, but it doesn't do either in my experience.
Click to expand...
Click to collapse
August factory images
August full OTAs
Build NJH47F
NZH54D for DT
NHG47Q for Verizon
NKG47S for T-Mobile, Fi, Rogers
Bump, figured I'd "discuss" it here, rather than making a new thread. Does anyone know the differences between the factory images? Possibly radio/modems?
For example, I have a Google bought XL, switched from fi to Verizon, and I'll occasionally swap between the image specifically for Verizon to the generic build. I never notice any difference.
noidea24 said:
Bump, figured I'd "discuss" it here, rather than making a new thread. Does anyone know the differences between the factory images? Possibly radio/modems?
For example, I have a Google bought XL, switched from fi to Verizon, and I'll occasionally swap between the image specifically for Verizon to the generic build. I never notice any difference.
Click to expand...
Click to collapse
Almost always radio/modem changes and sometimes telephony changes for wifi calling
noidea24 said:
Differences between the factory images? Possibly radio/modems?
Click to expand...
Click to collapse
pcriz said:
Almost always radio/modem changes
Click to expand...
Click to collapse
For the August update:
NJH47F - radio 8996-012901-1702171013
NHG47Q for Verizon - radio 8996-012901-1703291803
NKG47S for T-Mobile, Fi, Rogers - radio 8996-012901-1705091348
I updated, no issues.
Flashall bat file after removing the -w. Then boot to twrp and install SU. All good.
TonikJDK said:
I updated, no issues.
Flashall bat file after removing the -w. Then boot to twrp and install SU. All good.
Click to expand...
Click to collapse
Hey TonikJDK,
so after doing the flashall.bat - TWRP is still installed for you? Or can you elaborate what you exactly mean with "boot to TWRP [and install SU]"?
niko26 said:
Hey TonikJDK,
so after doing the flashall.bat - TWRP is still installed for you? Or can you elaborate what you exactly mean with "boot to TWRP [and install SU]"?
Click to expand...
Click to collapse
fastboot boot
niko26 said:
Hey TonikJDK,
so after doing the flashall.bat - TWRP is still installed for you? Or can you elaborate what you exactly mean with "boot to TWRP [and install SU]"?
Click to expand...
Click to collapse
No, I don't install TWRP. If I had my method would certainly remove it.
After the flash boot to TWRP means I type
Fastboot boot TWRPfilename
And that boots the phone to twrp, then I select install from the twrp menu and install the SU zip that I previously copied to the phone.
TWRPfilename of course is the twrp rc1 img boot file. You type the whole filename.
I haven't gotten any update notification on my Pixel. I forced check, says up to date with July Update.
Guess update hasn't been pushed out via OTA yet...
TonikJDK said:
No, I don't install TWRP. If I had my method would certainly remove it.
After the flash boot to TWRP means I type
Fastboot boot TWRPfilename
And that boots the phone to twrp, then I select install from the twrp menu and install the SU zip that I previously copied to the phone.
TWRPfilename of course is the twrp rc1 img boot file. You type the whole filename.
Click to expand...
Click to collapse
Thanks! That info helped.
While we'reat the rc1 img file.. there is a newer rc2 file, but it is a zip file - how do we boot off this?
niko26 said:
Thanks! That info helped.
While we'reat the rc1 img file.. there is a newer rc2 file, but it is a zip file - how do we boot off this?
Click to expand...
Click to collapse
You don't. Even if you were going to install RC2 you would boot off the rc1 img file and then install the rc2 zip.
niko26 said:
Thanks! That info helped.
While we'reat the rc1 img file.. there is a newer rc2 file, but it is a zip file - how do we boot off this?
Click to expand...
Click to collapse
You can't. So if you for instance want to install magisk. You can't without installing rc2
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
speedingcheetah said:
I haven't gotten any update notification on my Pixel. I forced check, says up to date with July Update.
Guess update hasn't been pushed out via OTA yet...
Click to expand...
Click to collapse
Doesn't happen all at once. A few people have reported getting it OTA on Reddit.
pcriz said:
You can't. So if you for instance want to install magisk. You can't without installing rc2
Click to expand...
Click to collapse
I'm not sure if I understand you correctly. So how would I install RC2? Did someone "just forget" to create an img for RC2?
niko26 said:
I'm not sure if I understand you correctly. So how would I install RC2? Did someone "just forget" to create an img for RC2?
Click to expand...
Click to collapse
No need for a new img. If you want TWRP installed you copy the rc2 zip to your phone...boot to rc1 using the image and install the rc2 zip.
pcriz said:
You can't. So if you for instance want to install magisk. You can't without installing rc2
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Doesn't happen all at once. A few people have reported getting it OTA on Reddit.
Click to expand...
Click to collapse
Buddy of mine has gotten in on his 5in Pixel already...but no lock on my XL as of yet.
He is on VZW network...i'm on Sprint...so, not sure if that makes any difference cause they come from Google..
speedingcheetah said:
Buddy of mine has gotten in on his 5in Pixel already...but no lock on my XL as of yet.
He is on VZW network...i'm on Sprint...so, not sure if that makes any difference cause they come from Google..
Click to expand...
Click to collapse
VZ OTA's come from Verizon and they come out earlier in the day. VZ does it in the morning EST while Google is west coast.
so...i the build numbers confuse me. My phone is from Google and first activated it on Tmobile, but now am on Sprint.
There is no build specific to Sprint mentioned. But how do the builds differ from each other...exact same hardware right?
My Pixel XL says it is on NJH47D.
speedingcheetah said:
so...i the build numbers confuse me. My phone is from Google and first activated it on Tmobile, but now am on Sprint.
There is no build specific to Sprint mentioned. But how do the builds differ from each other...exact same hardware right?
My Pixel XL says it is on NJH47D.
Click to expand...
Click to collapse
If you're specific carrier isn't listed then use international. They make specific changes for carriers connectivity
speedingcheetah said:
so...i the build numbers confuse me. My phone is from Google and first activated it on Tmobile, but now am on Sprint.
There is no build specific to Sprint mentioned. But how do the builds differ from each other...exact same hardware right?
My Pixel XL says it is on NJH47D.
Click to expand...
Click to collapse
You'll probably end up getting the NJH47F OTA which is the generic one, unlike the others which are carrier specific.
Like I have for months now, I upgraded a Pixel XL and a Pixel using TWRP RC2 sideload, boot to RC1 and install RC2, Install SuperSU 2.79 RC3 (and let the playstore upgrade later... I have been having far better luck with that path than installing and of the 2.82 builds directly) and V8 signer for no reason except that it is a habit at this point just in case.
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
convolution said:
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
Click to expand...
Click to collapse
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
convolution said:
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
Click to expand...
Click to collapse
It has been awhile since I rooted any phone, but yes, pressing power to continue was what I remember. And, yes annoying, but not fatal !
Sent from my PH-1 using Tapatalk
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
GryphKid44 said:
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
Click to expand...
Click to collapse
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
I would think that would do the trick. In my case I knew the system was issue so I just flashed system. I find fastboot extra finicky on this phone. Did you happen to notice if something errored in the script?
convolution said:
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
Click to expand...
Click to collapse
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
wolfu11 said:
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
Click to expand...
Click to collapse
I do... but my wifi doesn't work as well, so I think I did something wrong.
convolution said:
I do... but my wifi doesn't work as well, so I think I did something wrong.
Click to expand...
Click to collapse
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
wolfu11 said:
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
Click to expand...
Click to collapse
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
convolution said:
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
Click to expand...
Click to collapse
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
wolfu11 said:
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
Click to expand...
Click to collapse
no need for twrp?
you follow this one?
convolution said:
no need for twrp?
you follow this one?
Click to expand...
Click to collapse
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
wolfu11 said:
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
Click to expand...
Click to collapse
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
convolution said:
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
Click to expand...
Click to collapse
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
spotmark said:
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
Click to expand...
Click to collapse
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
delete
If it works, you should worry about that message at all.
convolution said:
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
Click to expand...
Click to collapse
The slot thing is pretty new in general. This doc has some explanation for the architecture of our phones: http://mata.readthedocs.io/en/latest/
Once you get the hang of it, it's pretty simple to deal with.
BTW, awesome signature. PTL, SDG. :victory: