Adobe Flash Player (as shipped) -- US-CERT Security Advisory - Samsung Galaxy S (4G Model)

At least on my stock SGS4G, the stock version of Flash is 10.1.92.8.
com.adobe.flashplayer 10.2.156.12 is available in the Market (as of 2011/03/21)
From US-CERT advisory (emphasis mine):
Adobe Releases Flash Player Update
Original release date: March 21, 2011 at 2:22 pm Last revised: March 21, 2011 at 2:22 pm
Adobe has released an update for Flash Player to address multiple vulnerabilities. These vulnerabilities affect Adobe Flash Player
10.1.102.64 and earlier versions for Windows, Macintosh, Linux, and Solaris, and Adobe Flash Player 10.1.106.16 and earlier versions for Android. Exploitation of these vulnerabilities may allow an attacker to cause a denial-of-service attack or execute arbitrary code.
US-CERT encourages users and administrators to review Adobe Security Advisory APSB11-02 and apply any necessary updates to help mitigate the risks.
Relevant Url(s):
http://www.adobe.com/support/security/bulletins/apsb11-02.html
====
This entry is available at
http://www.us-cert.gov/current/index.html#adobe_releases_flash_player_update​

Related

Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump

Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump​
For the past few hours, I've been observing a curious case of Jeff Williams on Google+. Jeff posted a screenshot of what he claimed was a Nexus 4 he bought from a Googler... with a build of Android 4.3 on it. The same build, JWR66N, that we saw leaked earlier on a Galaxy S4 GPE by SamMobile.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In disbelief, some have called him a hoaxer, but a number of resourceful folks decided to get Jeff on IRC (channel #Android43 on freenode) and worked with him for hours, trying over and over to get the magical system dump that would prove Jeff's story to be real.
The system dump, which we have since confirmed as legitimate and along with dozens of other IRC members mirrored to multiple destinations, indeed belongs to a Nexus 4 (mako), and the build number is indeed JWR66N. The radio and bootloader are missing right now - Jeff promised them tomorrow - so I have my doubts about a working port to other Nexus 4s for the time being.
In the meantime, the system dump itself is ready to go, and Ron and I are ripping through it as we speak. We'll have a teardown ready for you soon if we do dig something up, and by the looks of things, there's enough for a post.
I'd like to thank Jeff for his persistence as well as IRC users efrant, gravufo, Jason__, vividboarder, Introspection, and everyone else who drove this one to the finish line.
Update: There's chatter on IRC that restoring the backup via TWRP recovery seems to work. We haven't tested this, so if you do decide to proceed, do so with caution and after making a full backup of your entire system.
AP mirror #1
AP mirror #2
AP mirror #3
AP multi-mirror
Even more mirrors (by hackthevoid)
Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nexus 7, Nexus 10​
exus owners may have a reason to stay up tonight, as a couple of Reddit users report that Android 4.2.2 has begun rolling out to the GSM Galaxy Nexus and the Nexus 7.
There's not much word regarding what the update (which carries build JDQ39) includes just yet, but readers may remember that Google promised a Bluetooth A2DP audio streaming fix in the "next release" of 4.2 after 4.2.1.
At the moment it would seem that Reddit users in the thread linked below are the only ones reporting success at grabbing the update, so it's hard to judge the thread's veracity. If 4.2.2 has hit your device, though, let us know in the comments below.
Update: It looks like the update is rolling out after all. We've received confirmation from a number of users on Google+, including Marco Duran, who kindly provided some shots of the 47.6MB download from the Nexus 10.
Source: Android Police
4.2.2 nexus 7
NEED OTA LINK FOR NEXUS 7:laugh::laugh:
Here's The Android 4.2.2 JDQ39 Update For The GSM Galaxy Nexus
Here's The Android 4.2.2 JDQ39 Update For The GSM Galaxy Nexus [Manual Installation Instructions]​
A couple of hours ago, Google started rolling out the Android 4.2.2 update to a very limited subset of Nexus devices (build JDQ39). At this point, almost nobody can get the OTA pulled by going through the Settings screen, but don't worry - one of our loyal readers extracted the OTA url for the Galaxy Nexus and sent it over to us (great work, Daniel Koch!).
For now, we only have the link for the takju Galaxy Nexus variant, i.e. GNex handsets bought from the Play Store. Once we get the yakju build, we'll update this post.
Note: Every Custom ROM flashing May have risk. So, please do it at your own Wish.
If you're not sure whether you have a takju or yakju variant, download Nexus Update Checker from the Play Store and see what it says.
Click to expand...
Click to collapse
What's New?
We don't have any reliable information at this point because Google hasn't pushed the 4.2.2 files to AOSP yet or published any changelogs. We suspect the Bluetooth bug has been fixed, but are unclear what else has changed right now.
There is a new radio in this OTA.
Prerequisites
Your device should be running build JOP40D before trying to install the update manually. If you for some reason don't have JOP40D, Google has it available in factory image form here.
For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual
have the stock recovery, keep the zip file on your computer and follow a few easy instructions below
Manual Instructions
Step 1.
Reboot your Galaxy Nexus, holding the Volume Up and Volume Down buttons while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, press Volume Up and the Power button together, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
Connect your Galaxy Nexus to your computer with a USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file you've downloaded.
Type in the following:
adb sideload 472aafeb9fe3.signed-takju-JDQ39-from-JOP40D.472aafeb.zip
Click to expand...
Click to collapse
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
Reboot and enjoy! You are now running Android 4.2.2 on your Galaxy Nexus.
Download
Here's the OTA, hosted on Google's servers: takju build JDQ39.
AP mirror just in case it goes down: AndroidFileHost.
MD5: d37cd3aeeacc0d25a523acbebb5557f4
File size: 46.4 MB (48,672,997 bytes)
Source: Android Police
Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder
Re: Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nex
Good update
Sent from my GT-I8150 using xda app-developers app
soder said:
Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder
Click to expand...
Click to collapse
Try to flash using CWM buddy. Also are you applying the commands..??
soder said:
Shouldn't this file word being updated from recovery the normal way to?
I'm on Galaxy Nexus takju with TWRP recovery, and my updated failed..
EDIT: I get this error. assert failed: apply_patch _check ("system/lib/li
E: Error in /sdcard/filename.zip
(status7)
Error flashing zip
Updating partition details
/Söder
Click to expand...
Click to collapse
Dude it's not a regular flashable zip. You need a takju stock recovery.
m.kochan10 said:
Dude it's not a regular flashable zip. You need a takju stock recovery.
Click to expand...
Click to collapse
But, as I remember it, the 4.2.1 update was that kind of that kind of zip to?
And I was told I could flash it in a custom recovery? Or do I remember it wrong?
EDIT: This is where I got that info I think
http://forum.xda-developers.com/showthread.php?p=34706283#post34706283
and also from here
http://forum.xda-developers.com/showthread.php?t=1592689&page=84
Also:
"For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual"
EDIT2: I now remember that I might have edited my gps.conf, and created a new file. That might have anything to do with it? How do I get back an "untouched" version? I go have a backup of the stock rom, but how do I get the file back untouched?
/Söder
Re: Breaking: Android 4.2.2 (Build JDQ39) Update Rolling Out To GSM Galaxy Nexus, Nex
Now the source needs to be updated so I can get it on my Samsung galaxy s1
Sent from my SCH-I500 using Tapatalk 2
Android 4.2.2 (JDQ39) Source Has Started Pushing To AOSP
Android 4.2.2 (JDQ39) Source Has Started Pushing To AOSP [Updated]​
It's begun - the newest version of Android, 4.2.2, is being pushed to AOSP right now. We saw the accompanying Nexus OTA rollout start last night, with update files slowly springing up thereafter. Right now, 4.2.2 builds can be downloaded for the Takju Galaxy Nexus, Nexus 7 (Wi-Fi), and Nexus 10.
The build number is JDQ39 and the tag in AOSP is android-4.2.2_r1. Here are a few of the many directories that have been updated:
/device/common/+/android-4.2.2_r1
/platform/dalvik/+/android-4.2.2_r1
/platform/build/+/android-4.2.2_r1
While the push has just started this morning, source will likely continue to show up throughout the day, and we'll update this page as that happens. The Android Building Google Group should have a post by JBQ when the push is complete.
Update: It appears the push has finished, all Android 4.2.2 code should be in AOSP now.
They're working on compiling a full developer changelog right now, and once we've done that, we'll try to come up with a more human-readable one.
[Developer Changelog] Here's What's New In Android 4.2.2 (JDQ39)​
Following yesterday's Android 4.2.2 OTAs to various Nexus devices, Google today followed up with the push of all 4.2.2 open source code changes to AOSP. There is a lot here to parse through this time around compared to the minor 4.2.1_r1.2 commit from 10 days ago.
We've already identified some obvious user-facing changes, which we'll post about separately soon to keep it clean and organized. The purpose of this post is, as before, to find the low-level changes that may not be obvious. So move the beard out of the way and dig in.
Update: Ron detailed some new things here: New Android 4.2.2 Features: Toggle From Quick Settings, Better App Download Notifications, and Some New Sounds!
What's New?
Things we've discovered so far, in brief:
Play Store downloads now show time left to download.
Long-pressing Wi-Fi and BT now toggles them in the notification Quick Settings.
More secure ADB thanks to the new whitelist.
BT bug fixes? I've seen conflicting reports whether this is fixed - citation needed if anything's been done to it. Can you spot the right commits?
Update #1: Play a tone when wireless charging begins (if below 95% battery). Use new low battery and wireless charging sounds on Mako. Here are the new sounds: WirelessChargingStarted.ogg and LowBattery.ogg.
Here is the list of developer commits in 4.2.2 (AOSP tag android-4.2.2_r1, JDQ39) compared to 4.2.1's latest revision (AOSP tag android-4.2.1_r1.2, JOP40G).
Note: For whatever reason, some of these we may have seen before - perhaps someone who understands the intricacies of AOSP's git structure can explain why they're getting included in the diff, but for the most part, this is all new stuff.
Code:
Project name: /platform/development
•Chris Banes - Update bitmapfun sample to call recycle()
•Dirk Dougherty - Add redirect for removed file.
•Dirk Dougherty - Minor updates to keep androiddevdocs redirect in sync with devsite version (in frameworks/base)
•Adam Koch - Bitmapfun Sample: Fix bug where background image loading could hang
•Chet Haase - Cherrypick from Change-Id: I4ae984cf776604cede32b98db6b1eb3cb6c59c7e
•Adam Koch - Bitmapfun Sample: Change cache memory calculation to use maxMemory()
•Adam Koch - Bitmapfun Sample: Fix inSampleSize selection and update dependencies
•Katie McCormick - Network sample: fix typo in manifest
•Xavier Ducrohet - Update platform tools rev to 16.0.2
•Dirk Dougherty - Add ko and ru to validLangs.
•Joe Malin - Android Training: Threads sample app
•Dirk Dougherty - Add redirect for IAB v3 restructure.
•Dianne Hackborn - SDK Only: Fix search interaction with various samples.
•Dirk Dougherty - Redirects /guide/google to /google/.
•Xavier Ducrohet - Move plat-tools SDK component rev to 16.0.1
•&& repo sync -j8 - Doc change: sample app for Notifications class
•Scott Main - docs: update redirects for articles
•Scott Main - docs: add redirects for best practices pages that moved to training
•Scott Main - docs: a few bonus redirects for dac
•Andy Stadler - Cleanup eclipse .classpath for Gallery2
•Scott Main - docs: redirect next steps to building first app class
Project name: /platform/cts
•Leo Liao - DO NOT MERGE Add missing features of JB and JB MR1
•Leo Liao - Add missing features of JELLY_BEAN to feature list
•Brian Muramatsu - Updated Holo test assets for JB MR1
•Nick Kralevich - FileSystemPermissionTest: add directories
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier to R4
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier to R5
•Laurent Tu - Restore CtsVerifier rate for passive updates
•Brian Muramatsu - Some Holo Test Improvements
•Nick Kralevich - Try reading every file on /sys
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version again
•Marco Nelissen - Improve testSetNextMediaPlayer test
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version to 4.2 R3
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier version to 4.1_R4
•Laurent Tu - Assert mean and stdev of update deltas
•Nick Kralevich - Add CVE to Exynos vulnerability test.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.1_R3
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•steven_huang - DO NOT MERGE Filter out the overdue location cases in GPS test
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.2_r2
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.2_r2
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•Brian Muramatsu - DO NOT MERGE Update CTS Verifier Version to 4.1_R3
•Laurent Tu - DO NOT MERGE Relax LocationVerifier assertions.
•steven_huang - DO NOT MERGE Filter out the overdue location cases in GPS test
•Nick Kralevich - Add Exynos vulnerability tests.
•Adam Momtaz - CTS tests for UiAutomator at API 17
•Marco Nelissen - Add test for MediaScanner misbehavior
•Andreas Huber - Add a CTS test that iterates through all codecs using MediaCodecList and
•Andreas Huber - Adds a CTS test verifying audio encoder functionality. (AAC, AMR-NB, AMR-WB)
•Adam Momtaz - Fixed a mistakenly deleted line from the last submit
•Marco Nelissen - Fix ringtone test
•Brian Muramatsu - Update BuildVersionTest to support 4.2.2
•Fabrice Di Meglio - Fix bug #7664208 android.widget.cts.TextViewTest#testResetTextAlignment failures on JD
•Eino-Ville Talvala - CTS Verifier: Fix Camera Formats preview orientation.
•Fabrice Di Meglio - Fix bug #7664305 android.widget.cts.TextViewTest#testResetTextDirection failures on JD
•Adam Momtaz - UiAutomator test APK and Tests for CTS
•Fabrice Di Meglio - Add more CTS tests for the reset of RTL properties
•Keun young Park - DO NOR MERGE make reboot default in CTS (merge from mr1)
•Keun young Park - add log to print time-out when time-out happens
•Nick Kralevich - Add more tests for restricted broadcasts.
•Keun young Park - add 4.2.1 to version list
•Svetoslav Ganov - Cannot move edit text cursor to first position using character granularity.
•Keun young Park - change all file writes to random access with O_SYNC
•Brett Chabot - Add UiAutomator test skeleton to CTS.
•Svetoslav Ganov - Fix the shell commands used to clean up after the accessibility tests.
•Svetoslav Ganov - Add NumberPicker CTS tests.
•Nick Kralevich - FileSystemPermissionTest: Expand block device tests.
•Keun young Park - force reboot after accessibility test
•Guru Nagarajan - Version number for CTS 4.2 modified: tools/tradefed-host/src/com/android/cts/tradefed/build/CtsBuildProvider.java
•Brian Muramatsu - Report suite name to result server
•Igor Murashkin - Camera: New test to check app firing intent after capturing picture/video
Project name: /platform/prebuilts/sdk
•Ying Wang - Drop official SDK 17
Project name: /platform/prebuilts/misc
•Brett Chabot - Manually update tradefed prebuilt from jb.
•Xavier Ducrohet - Update Layoutlib_api to API 9. do not merge.
Project name: /platform/hardware/libhardware
•Mathias Agopian - Fix HWC documentation.
Project name: /platform/hardware/libhardware_legacy
•Eric Laurent - audio policy: notification delay - DO NOT MERGE
•Eric Laurent - audio policy: fix volume problem - DO NOT MERGE
•John Grossman - audio policy: fix dynamic parameter - DO NOT MERGE
•Jason Simmons - audio policy: direct output fix - DO NOT MERGE
•Irfan Sheriff - Fix stop supplicant api
Project name: /platform/hardware/ril
•Wink Saville - Update documenation for DATA_REGISTRATION_STATE
remaining Can be view here -> [URL="https://gist.github.com/archon810/4772945#file-changelog_android-4-2-1_r1-2_android-4-2-2_r1-txt"]ile-changelog_android-4-2-1_r1-2_android-4-2-2_r1-txt[/URL]
Detailed Changelog
Full_changelog_android-4.2.1_r1.2_android-4.2.2_r1.txt
Source: Android Police
Thanks for change log, I have not yet received the update but know that flashing will be good to get a fresh start.
nexus4?
Android 4.2.2 adds new sounds and notification toggles
Android 4.2.2 adds new sounds and notification toggles​
Why just the other day, we told you that Android 4.2.2 was being sent out to the Google Nexus 10, Google Nexus 7 and the Samsung GALAXY Nexus. While there has not yet been any changelist, we do have some information from those who have installed it on their tablet or phone. First of all, there is a new notification bar that shows you the time remaining and the percentage left of an in-progress app download. A change to Quick Settings lets you long press on the Bluetooth or Wi-Fi square to turn them into toggle switches. Now here is where it gets confusing. The Airplane Mode box is a single press toggle while some boxes do not change any settings.
Calculate speed of in-progress downloads and estimate time remaining until completion. Uses a moving average that is weighted 1:1 with the most recent 500ms sample. Funnels timing data to notifications through DownloadHandler."-How Google calculates the time remaining of an app download
Click to expand...
Click to collapse
Android 4.2.2 also brings a couple of new sounds, The two short bursts that tell you that your battery is low has been replaced while there is now a sound for wireless charging. Previously, the latter had no sound at all.
It should be interesting to see how the Android 4.2.2 update affects the next distribution data from Google. Also, we could see Android 4.0 drop more as some devices get updated to Android 4.1. The large chunk of Android users sporting a device powered by Gingerbread is only going to dissipate slowly as those owners start to upgrade once their 2-year contract expires. Those Android 2.3 phones will be replaced by Android 4.1 by the time the updates are in full swing, providing another reason to expect Ice Cream Sandwich to continue to melt.
If you have installed the Android 4.2.2 update on any of your devices, drop us a comment with some of the other changes that you might have noticed.
Source: PhoneArena
The Nexus 4 Finally Gets Android 4.2.2 (JDQ39) As Well - Here Are Instructions For In
ctakah27 said:
nexus4?
Click to expand...
Click to collapse
The Nexus 4 Finally Gets Android 4.2.2 (JDQ39) As Well - Here Are Instructions For Installing It Manually​
Good news, everyone! The Nexus 4 Android 4.2.2 OTA (JDQ39) is finally here, surprisingly late in the update cycle, following the Nexus 10 and older Nexus devices, such as both variants of the Nexus 7 and both variants of the Galaxy Nexus. Chances are you probably don't have the coveted update notification just yet, but who wants to wait if you can sideload it manually? Rooted, unrooted, stock or custom recovery - it matters not.
What's New?
To see what's new in Android 4.2.2, see New Android 4.2.2 Features: Toggle From Quick Settings, Better App Download Notifications, and Some New Sounds!
Code:
[B]Heads up:[/B] There is also a new radio in this update.
Prerequisites
Your device should be running build JOP40D before trying to install the update manually. If you for some reason don't have JOP40D, Google has it available in factory image form here.
For those ready to download and install manually, the process is easy. If you
have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual
have the stock recovery or a custom recovery that supports sideloading, keep the zip file on your computer and follow a few easy instructions below
Manual Instructions
Step 1.
Reboot your Nexus 4, holding the Volume Down button while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, hold Power and press Volume Up a few times, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
Connect your Nexus 4 to your computer with a USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file you've downloaded.
Type in the following:
Code:
adb sideload de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
Reboot and enjoy! You are now running Android 4.2.2 on your Nexus 4.
Download
Here's the OTA, hosted on Google's servers: build JDQ39.
MD5: 1c752738f65acfd48f2d3b6e6e11a654
File size: 51.0 MB (53,529,568 bytes)
Source: AndroidPolice
Thank You
Thanks for change log!
rishabhgangwar said:
Thanks for change log!
Click to expand...
Click to collapse
Pressing thanks button can speak louder then words in Xda buddy..
question
do we need to wipe data to complete this action? is there any problem could face SDCARD folder?
New 4.3 Update found Check the OP.:good:
Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump
Disturbed™ said:
New 4.3 Update found Check the OP.:good:
Breaking: Android 4.3 For Google Nexus 4 Leaks (JWR66N) - Here's The System Dump
Click to expand...
Click to collapse
thanks for the convincing statements :good:

Offline system images & packages installation unsuccessful [Eclipse/Android SDK/Java]

Offline system images & packages installation unsuccessful [Eclipse/Android SDK/Java]
I am currently setting up Android SDK, eclipse and Java JDK for app development. Am fairly new to it so am not familiar with very technical jargons. I have managed to successfully setup Java JDK offline and eclipse partially. I say partially because I have been able to get it to recognize platforms, platform tools and build tools by creating recognizable folders and extracting the zip contents into them. I have not succeeded for the system images as I don't know what folder naming is requires for them to be recognized as installed in the android-sdk folder. My pc is currently located in a area where there is no cable or broadband internet since the facility is fairly new but 4G data is available but very expensive.
I tried the tutorial where you create a temp folder in android-sdk, then connect to 4G just to get the SDK manager to read the necessary packages, then disconnect, then run install packages so that it now sources them locally from the temp folder but it fails to install.
The packages I need installed but dont have their zips for offline installation are:-
- Android SDK Build-tools, revision 23.0.1
- Documentation for Android SDK, API 23, revision 1
- SDK Platform Android 6.0, API 23, revision 1
- Samples for SDK API 23, revision 2
- Android TV ARM EABI v7a System Image, Android API 23, revision 2
- Android TV Intel x86 Atom System Image, Android API 23, revision 2
- ARM EABI v7a System Image, Android API 23, revision 3
- Intel x86 Atom_64 System Image, Android API 23, revision 3
- Intel x86 Atom System Image, Android API 23, revision 3
- Google APIs, Android API 23, revision 1
- Google APIs ARM EABI v7a System Image, Google Inc. API 23, revision 7
- Google APIs Intel x86 Atom_64 System Image, Google Inc. API 23, revision 7
- Google APIs Intel x86 Atom System Image, Google Inc. API 23, revision 7
- Sources for Android SDK, API 23, revision 1
- Android Support Library, revision 23.0.1
- Google USB Driver, revision 11
Can anyone provide me with these zips and what folders to create in the android-sdk folder to get them installed?
offdroid
Hi
not sure what your operating system is, but I've built an offline installer for android sdk which works best on linux (it can be used on W*ndows too, provided that it has cygwin installed.) you might want to check it out at github.com/icefapper/offdroid.
my two cents.

[Completed] Csploit new penetration test tool

cSploit
The most complete and advanced IT security professional toolkit on Android.
cSploit target
The final goal is to write an application that is able to:
- enumerate local hostsdone
- find vulnerabilitiesdone
- find exploits for these vulnerabilitiesdone
- use those exploits to gain access to the targetdone
- crack wifi passwords
- install backdoors for later access
settings
Portability
Thanks to the new core, cSploit will be easily portable.
Basically it can run on any UNIX-based system, but for now only Android is supported. When I reach a beta-state version I will consider working on iOS, OSX, GTK+ and QT.
requirements:
•rooted device
•busybox installed
I tested on A500FU running on 5.0.2 lollipop
chance to support marshmallow
Features:
WiFi Cracking(not working)
RouterPWN
Trace
Port Scanner
Inspector
Vulnerability finder
Login cracker
Packet forger
Man in the middle
Simple sniff
Password sniff
Session Hijacker
Kill connections
Redirect
Replace images
Replace videos
Script injector
Custom filter
the most stable version of csploit is 1.6.6 RC2
Thread closed as this is not what Assist is here for
Learn how to use Assist here
http://forum.xda-developers.com/showthread.php?t=2764768

[OTA] [Fastboot] [QFIL] Nokia 7 Plus OTA and Fastboot Collection

Nokia 7 Plus OTA & Firmware Collection​Tested on the following variants: TA-1046, TA-1055 & TA-1062​You can contribute by giving us the OTA link in my 3rd post below.​
Join our Telegram Group:https://t.me/Nokia7PlusGlobal​
Disclaimer:​​Anyone can try those zip files below but I am not responsible for bricking up your phone.
Android One\International ROM​OTA
Stable Channel:
Android Q 10:
00WW 4.15D SP03 July 2020 ROM (B2N-415F-0-00WW-B01-B2N-415E-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../5aa10fea5836fb87441559a8d40969283e7c41c2.zip
00WW 4.15D SP01 June 2020 ROM (B2N-415E-0-00WW-B01-B2N-415D-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../20212da589a195ab10e0e80379620de23a3a5e71.zip
00WW 4.15D May 2020 Full ROM (B2N-415D-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../5cee5d357ef514301a4e8def6f81ad0947a353fe.zip
00WW 4.10C SP04 April 2020 (B2N-410G-0-00WW-B01-B2N-410F-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../be4f2daa18a46b2150d0ab03216ec4a72ecfc3e9.zip
00WW 4.10C SP03 March 2020 (B2N-410F-0-00WW-B01-B2N-410E-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../eb9b1556b0429a56e3eb4d31d285430d942b2f1d.zip
00WW 4.10C SP02 Febuary 2020 (B2N-410E-0-00WW-B01-B2N-410D-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../44266b71672c8bf00750e11f26c7f5444ae52e93.zip
00WW 4.10C SP01 January 2020 (B2N-410D-0-00WW-B01-B2N-410C-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../44f7f4cc20c6e70b8f71469d4b2b9f8be467249c.zip
00WW 4.10C December 2019 Full ROM (B2N-410C-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../afd338bfb14d447b716c220424b2ad2c66213183.zip
Android Pie 9.0:
WW 3.22C September 2018 (B2N-322C-0-00WW-B01-222I-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../105d70f18f853101a4e4d47f66b60a97318bc589.zip
WW 3.22C SP01 October 2018 (B2N-322D-0-00WW-B03-322C-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../d734e46db890dc1ca67009c7341f0c2b5da22e87.zip
Skip This->WW 3.22C SP02 November 2018 (B2N-339F-0-00WW-B03-322D-0-00WW-B01-update.zip)<-Skip This
Skip This->https://android.googleapis.com/pack.../816108503981dd04377461eaa968901495ad5302.zip<-Skip This
WW 3.39B November 2018 (B2N-339B-0-00WW-B03-322D-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../72426218bf9f8a4a5da6798ae7341e45a3c00540.zip
WW 3.39B November 2018 (B2N-339B-0-00WW-B03-222R-0-00WW-B01-update.zip) Full ROM from Android 8.1 Oreo to Android 9.0 Pie
https://android.googleapis.com/pack.../8e46fce41f211c1b68e14c7873e9b575a0ea596b.zip
Skip This->WW 3.22C SP03 December 2018 (B2N-322G-0-00WW-B03-322F-0-00WW-B01-update.zip)<-Skip This
Skip This->https://android.googleapis.com/pack.../66c4163cb48341557ca23395ebc380c9cdf83edb.zip<-Skip This
WW 3.39B SP01 December 2018 (B2N-339D-0-00WW-B03-339B-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../0f62e4e3a82403e1cc58cce9dad8e5dd1a75994e.zip
WW 3.39B SP02 January 2019 (B2N-339F-0-00WW-B01-339D-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../93147f19920a9992b6b10fb17bc0240377e8a818.zip
WW 3.22C SP04 January 2019 (B2N-322G-0-00WW-B01-322H-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../268791c280f3353d984a7bf4991f4e91fac2686c.zip
WW 3.39B SP03 February 2019 (B2N-339H-0-00WW-B01-339F-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../2e261c4a857f22078ba77bb94307e9871bed90e2.zip
WW 3.22C SP05 February 2019 (B2N-322H-0-00WW-B01-322I-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../bd26ab0627c7d5fd9de14e81c1433f5723b8c9ee.zip
WW 3.51F March 2019 (B2N-351F-0-00WW-B01-339H-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../736a15596b93225ce4e13e5b955bf82921da5ca3.zip
WW 3.51F March 2019 Full ROM (B2N-351F-0-00WW-B04.zip)
https://android.googleapis.com/pack.../5255f45225061bdc1c3525a32cf7361480e45ea3.zip
WW 3.51 SP01 April 2019 (B2N-353A-0-00WW-B01-351F-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../d2ba0e86a2dc9c5f8244493d09298e3e2f19b73a.zip
WW 3.51 SP02 May 2019 (B2N-353B-0-00WW-B01-353A-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../089329b82ba74379c35b535b2784db6355a3cdbc.zip
00WW 354E June 2019 (B2N-354E-0-00WW-B01-353B-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../d756ac9a0167ff93407107f9962d913e861ab528.zip
Correct me if the filename is incorrect.
00WW 354E June 2019 Full ROM (B2N-354E-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../a3fdf9a7be3548459a79e62f3726edc6bf94cbe4.zip
00WW 354H July 2019 (B2N-354H-0-00WW-B01-353E-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../c6fe0da461cfe59665278c4cff041071040a3fe9.zip
00WW 354H July 2019 Full ROM (B2N-354H-0-00WW-B01-update.zip)
https://android.googleapis.com/pack.../3f78de06f86cc03da028648341aa1987fe33b2df.zip
00WW 354H SP01 August 2019 (B2N-354J-0-00WW-B01-354H-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../1bae52f6dacdd7c098ae2fe596a02912c1498eee.zip
00WW 354H SP02 September 2019 (B2N-354M-0-00WW-B01-354J-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../c6c47fa410816d191be909a1dcda9473c80d04cb.zip
00WW 354H SP03 October 2019 (B2N-354N-0-00WW-B01-354M-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../a3fa7664a3d1f834dc34baabc3a4c73c3e622a0b.zip
00WW 354H SP04 November 2019 (B2N-354P-0-00WW-B01-354N-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../f4ac5a5755297d0a66bacfd22fe8caed7dbb7f88.zip
Android Oreo 8.1:
WW 1.32E>WW 2.13B April 2018 (B2N-213B-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../7ce972aed10569e082cf5c0d2336120a892f2cd5.zip
WW 2.13B>WW 2.22A May 2018 (B2N-222A-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../fdef9a60c63265213f69ddda8eecf4829816d233.zip
WW 2.22A>WW 2.22A SP01 June 2018 (B2N-222B-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../93da3854a945dd4983aa8ec6121751345494eac3.zip
WW 2.22A SP01>WW 2.22A SP02 July 2018 (B2N-222F-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../29a06b8105e817828fb3403265a92489a7b681a0.zip
WW 2.22A SP02>WW 2.22A SP03 August 2018 (B2N-222G-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../90e5a1ffe64c9dcd8b0a4d1da4095d32572fa10e.zip
WW 2.22A SP03>WW 2.22M August 2018 (B2N-222I-0-00WW-B05-update.zip) WW 2.22M August 2018 (B2N-222I-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../e8e501e4c4b78a42d433311bfdb2657948e45390.zip
You can skip to Android 9.0 Pie afterwards
WW 2.22M August 2018>WW 2.22M SP01 September 2018 (B2N-222O-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../f81ac3b5c38819499165f45ac45c49d7cbf7cd21.zip
WW 2.22M SP02 October 2018 (B2N-222R-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../4d971c2b5136ecb8bd78d8206cce42f35b96c4d9.zip
The following OTA's are coming from FIH server & not yet Officially Announced as they will make your device unstable (For example Google Play Protect Certification: Device is not certified)
WW 3.51A January 2019 (B2N-351A-0-00WW-B01-339F-0-00WW-B01-update.zip) - Unofficially Announced via FIH Servers
https://androidfilehost.com/?fid=11410963190603898477
WW 3.51B February 2019 (B2N-351A-0-00WW-B01-351B-0-00WW-B01-update.zip) - Unofficially Announced via FIH Servers
https://www.androidfilehost.com/?fid=11410963190603904798
Android Pie 9.0 Developer Preview:
Developer Preview 1 WW 3.050 (B2N-3050-0-00WW-B01-update.zip)
https://androidfilehost.com/?fid=890278863836296143
Rollback WW 2.13B Android 8.1 April 2018 (B2N-213B-0-00WW-B05-update.zip)
https://androidfilehost.com/?fid=962339331459002457
Developer Preview 2 WW 3.08B (B2N-308B-0-00WW-B01-update.zip)
https://www.androidfilehost.com/?fid=818222786056041049
Rollback WW 2.13B Android 8.1 April 2018 (B2N-213B-0-00WW-B05-update.zip)
https://www.androidfilehost.com/?fid=890278863836296092
Developer Preview 3 WW 3.110 (B2N-3110-0-00WW-B03-update.zip)
https://android.googleapis.com/pack.../41ecea512d7a15091a378566346e747800c719df.zip
Rollback WW 2.13B Android 8.1 April 2018 (B2N-213B-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../86beeb23d88118fc9882ddcd1c0a6f2a039e6e33.zip
Developer Preview 4 WW 3.150 (B2N-3150-0-00WW-B04-update.zip)
https://android.googleapis.com/pack.../e4ad542b9127ab27ea330d3995fd05c55bbdf8f5.zip
Rollback WW 2.22A SP02 Android 8.1 July 2018 (B2N-222F-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../9e799aa4a14726ef3a4906e75ae07372338b1041.zip
Developer Preview 4.1 WW 3.190 (B2N-3190-0-00WW-B03-update.zip)
https://android.googleapis.com/pack.../dbd66f48d0b2cd840ae50d561bffcb3818642e96.zip
Rollback WW 2.22A SP03 Android 8.1 August 2018 (B2N-222G-0-00WW-B05-update.zip)
https://android.googleapis.com/pack.../52193f24d82456b9a365417bab0f357fa20de741.zip
Rollback WW 2.13B Android 8.1 April 2018 (B2N-213B-0-00WW-B05-update.zip)
https://www.androidfilehost.com/?fid=1322778262904009092
Firmware​Disclaimer:​​For Bootloader Unlocked Devices. I am not responsible for bricking up your phone.
Note: CN=Chinese Firmware, WW=International Firmware
QFIL
TA-1046-B2N-132E-0-00WW-B07-QFIL
https://www.androidfilehost.com/?fid=5862345805528055766
NB0
TA-1046-B2N-132E-0-00WW-B07-NB0
https://www.androidfilehost.com/?fid=5862345805528055765
Credits:
Nick Hunn @Jesery
WestFly(via Telegram) @Cathair2906
@und3fined​
China ROM
OTA
Android 8.1 Oreo
B2N-213C-0-00CN-B04-132E-0-00CN-B08-update.zip - May 2018
Original: https://ota-filesite.c2dms.com/SWUpdate/500001364
Mirror: https://www.androidfilehost.com/?fid=11410963190603871594
B2N-213E-0-00CN-B04-213C-0-00CN-B04-update.zip - June 2018
Original: https://ota-filesite.c2dms.com/SWUpdate/500001519
Mirror: https://www.androidfilehost.com/?fid=11410963190603871571
B2N-233A-0-00CN-B03-213E-0-00CN-B04-update.zip - July 2018
Original: https://ota-filesite.c2dms.com/SWUpdate/500001691
Mirror: https://www.androidfilehost.com/?fid=11410963190603871570
B2N-233C-0-00CN-B01-233A-0-00CN-B03-update.zip - August 2018
Original: https://ota-filesite.c2dms.com/SWUpdate/500001765
Mirror: https://www.androidfilehost.com/?fid=11410963190603871573
B2N-242C-0-00CN-B01-233C-0-00CN-B01-update.zip - September 2018
Original: https://ota-filesite.c2dms.com/SWUpdate/500002039
Mirror: https://www.androidfilehost.com/?fid=11410963190603871573
B2N-242C-0-00CN-B02-242C-0-00CN-B01-update.zip - August to August #2 2018
Original: https://ota-filesite.c2dms.com/SWUpdate/500002058
Mirror: https://www.androidfilehost.com/?fid=11410963190603871568
B2N-242F-0-00CN-B01-242C-0-00CN-B02-update.zip - August 2 to September 2018
Original: https://ota-filesite.c2dms.com/SWUpdate/500002294
Mirror: https://www.androidfilehost.com/?fid=11410963190603871572
B2N-242H-0-00CN-B01-242F-0-00CN-B01-update.zip - October 2018
Original: https://ota-filesite.c2dms.com/SWUpdate/500002447
Mirror: https://www.androidfilehost.com/?fid=11410963190603871575
Android 9.0 Pie
B2N-337A-0-00CN-B04-update.zip - November 2018
Original: http://ota-filesite.c2dms.com/SWImage/500002005
Mirror: https://www.androidfilehost.com/?fid=11410963190603861750
B2N-3460-0-00CN-B01-337A-0-00CN-B04-update.zip - December 2018
Original: http://ota-filesite.c2dms.com/SWUpdate/500002816
Mirror: https://www.androidfilehost.com/?fid=11410963190603871604
B2N-347C-0-00CN-B04-update.zip - January 2019
Original: http://ota-filesite.c2dms.com/SWImage/500002276
Mirror: https://www.androidfilehost.com/?fid=1395089523397953719
B2N-347D-0-00CN-B02-347C-0-00CN-B04-update.zip - March 2019
Original: https://ota-filesite.c2dms.com/SWUpdate/500003202
Mirror: https://www.androidfilehost.com/?fid=1395089523397927809
B2N-347H-0-00CN-B03-347D-0-00CN-B02-update.zip - May 2019
Original: https://ota-filesite.c2dms.com/SWUpdate/500003398
Mirror: https://www.androidfilehost.com/?fid=6006931924117911655
B2N-347I-0-00CN-B02-347H-0-00CN-B03-update.zip - July 2019
Original: https://ota-filesite.c2dms.com/SWUpdate/500003456
Mirror: https://androidfilehost.com/?fid=6006931924117920906
Firmware
Disclaimer: For Bootloader Unlocked Devices. I am not responsible for bricking up your phone.
Note: CN=Chinese Firmware, WW=International Firmware
QFIL
TA-1062-B2N-132E-0-00CN-B08-QFIL
https://www.androidfilehost.com/?fid=5862345805528055768
NB0
TA-1062-B2N-132E-0-00CN-B08-NB0
https://www.androidfilehost.com/?fid=5862345805528055764​
Tutorial
How to apply OTA
Via Phone
The package "com.evenwell.OTAUpdate" has been deleted since November 2018 Update, this means, the *#*#874#*#* method, is no longer available
Prerequisites
Your charged phone
No PC & SD Card needed
Directions
1. Download the OTA zip file from this page first.
2. Go to download folder and rename the package to the corresponding zip name.
Example: B2N-322C-0-00WW-B01-update.zip
3. Place it to root directory of internal storage.
4. Open Phone App and dial *#*#874#*#* to update.
5. Wait for the update to finish and restart when prompted.
Via Recovery
Prerequisites
To update a device using a downloaded image, you will need the latest adb tool on your computer. You can get this from the Android SDK Platform-Tools package, which can be downloaded from here.​
1. Ensure to modify the environment variable which includes the PATH where the adb executable can be found.
2. Ensure you've set up USB access for your device, as described in Run Apps on a Hardware Device (may have to remove hyperlink).
Download the build and flash your device
1. Ensure your device is up to date by going to Settings > About phone > System updates
2. Download the required image from the download button below.
3. With your device powered on and USB debugging enabled, execute: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can alternatively use the following procedure:
A. Power off device, and insert USB to enter power off charge mode.
B. Press the Power key and Volume Up keys together for about 10 seconds.
C. Release both keys when the device vibrates.
D. After the Android screen, you should now be in Recovery Mode, indicated by the Android Warning logo and "No command".
E. Select the Recovery option from the bootloader menu and you should now be in "Recovery Mode" (confirmed by Android logo & red exclamation mark).
4. Hold the Power button and press Volume Up once, and a menu will appear:
Option 1: Via SD Card
Select the option “Apply update from SD Card” from the recovery options. Navigate to the OTA update zip and select it. Confirm installation.
Option 2: Via ADB
A. Select the option "Apply update from ADB".
B. Run the following command: adb devices and confirm your device displays "sideload".
C. Run the following command: adb sideload ota_file.zip - where "ota_file.zip" is the name of the downloaded file.
5. Once the update has finished, reboot the phone by selecting "Reboot system now".
6. For added security, you should consider disabling USB debugging when the device is not being updated.
How to Capture OTA Link
Requirements
1. You will first need to enable USB debugging on your Android phone.
2. Also, set up ADB and Fastboot on your PC.
3. If you have rooted your device using SuperSU or Magisk or installed TWRP recovery, then you will not be able to install the OTA update. However, the OTA notification will still be intact.
4. Make sure that the OTA update notification has arrived on your specific device. Do not download or install it just yet.
Method 1: Capture OTA Update URL using PC
1. Connect your phone to the PC using the USB cable.
2. Go to C:\adb on your PC. This is the folder where all the ADB and Fastboot binaries are present.
3. Hold the SHIFT key and right-click on an empty space inside this folder. Or type "CMD" in the Windows explorer's address bar where the adb is located.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Select ‘Open Command window here’ or ‘Open PowerShell window here’ option.
5. The command-line window shall open up on your PC.
6. Enter the command to capture OTA update URL on Windows:
adb logcat > ota.txt
7. As soon as you execute this command, grab your device without disturbing the USB connection.
8. Open the system update window and start downloading the update. After 10-15 seconds, pause/cancel the download.
9. Go back to the command-line screen and press the Ctrl + C key on your keyboard.
10. Now go to C:\adb and open the ‘ota.txt‘ file.
Search (Ctrl + F) the text file for this link:
Code:
https://android.googleapis.com/packages/ota-api/nokia_b2nsprout_onyx00ww/
Using these keywords, you shall be able to locate and capture OTA URL. Once you have the URL, paste in your browser’s address bar and download the file.
Rooted users can simply use a terminal emulator to capture OTA update URL. Simply install a terminal emulator (Termux) on your phone. And then use the ‘logcat > /sdcard/ota.txt‘ command to capture a full logcat of the system. Remember, only push the download button when you have executed the command. The ota.txt file will be placed on the root of your device’s storage. Note that this method only allows you to capture Android OTA URL. You wouldn’t be able to sideload the .zip file on a rooted device.
Method 2: Capture OTA Update URL using ‘Take bug report’ Option
1. First, enable ‘Developer options‘ and install Solid Explorer on your phone.
2. Go to the system updates and start downloading the new update.
3. Quickly go to ‘Settings’ -> ‘Developer options’ and tap on ‘Take bug report’.
4. When prompted, select ‘Interactive report’.
5. Finally, tap on ‘REPORT’ to capture OTA update URL of the latest firmware.
6. The feature will automatically take a capture a complete log of your system.
7. You will be able to see the progress in the persistent notification.
8. Once complete, tap on the notification to share the bug report.
9. Tap on ‘Solid Explorer’ in the share menu and save the bug report to the storage.
When the report has been saved, open the file and search the text file for this link:
Code:
https://android.googleapis.com/packages/ota-api/nokia_b2nsprout_onyx00ww/
You shall easily be able to capture Android OTA update URL in the file.
If you have been able to capture OTA update URL for your Android device, then kindly share it with us through the comments. It would be nice to help each other, right? Stay tuned while we get more tips to ease out your Android experience.​
Attention TA-1062 CN ROM users interested to convert to WW ROM​
You can convert from CN ROM to WW ROM by following the instructions "in order" from @hikari_calyx:
1. How to convert a Nokia 7+ from China Variant to Global
2. How to root your AB partition scheme based Nokia Android Devices
3. How to change SKUID to Worldwide or China (Root required)
4. Flash full OTA Firmware (Developer Preview 4.1 WW 3.190 if you're using Android 8.1 and Rollback WW 2.22A SP03 Android 8.1 August 2018 if you're using Android Pie 9.0 DP4.1)
5. OPTIONAL: Relock your bootloader.
thanks for sharing
Is the ota update downloaded from 1046 or 1062?
Are there any baseband difference,since 1062 support lesser band and is Asia specific model ,1046 is an international model.thanks
sameermehta2 said:
Is the ota update downloaded from 1046 or 1062?
Are there any baseband difference,since 1062 support lesser band and is Asia specific model ,1046 is an international model.thanks
Click to expand...
Click to collapse
Yes, they are for both TA-1046 & TA-106. I don't think there are differences between the 2 variants besides of being a 4GB RAM on the TA-1046 & 6GB RAM on the TA-1062. Both of them are also an "International Model" since the TA-1062 was also released but is limited in Taiwan & Hong Kong.
do you have a full .img of android 8.0 for ta 1046? I need this .img
schizmatyk said:
do you have a full .img of android 8.0 for ta 1046? I need this .img
Click to expand...
Click to collapse
You can check @blackpanther0582 post here:
https://forum.xda-developers.com/no...kia-7plus-official-firmware-mar-2018-t3768494
edwaine said:
You can check @blackpanther0582 post here:
https://forum.xda-developers.com/no...kia-7plus-official-firmware-mar-2018-t3768494
Click to expand...
Click to collapse
yeah i have this file but app says this system is to old...I spoke with one guy about this problem and he can help mi but later. Now i have to wait
schizmatyk said:
yeah i have this file but app says this system is to old...I spoke with one guy about this problem and he can help mi but later. Now i have to wait
Click to expand...
Click to collapse
OP updated. But I doubt that those files you downloaded are the same as I have. I think you should wait for a new NB0 file to be released.
edwaine said:
OP updated. But I doubt that those files you downloaded are the same as I have. I think you should wait for a new NB0 file to be released.
Click to expand...
Click to collapse
I have to downgrade system if I want to use custom ROM. After 10pm I should start working on this with this guy from Twitter who's unlock bootloader.
schizmatyk said:
I have to downgrade system if I want to use custom ROM. After 10pm I should start working on this with this guy from Twitter who's unlock bootloader.
Click to expand...
Click to collapse
You can ask @HikariCalyx in Telegram. He unlocks HMD Bootloader.
edwaine said:
You can ask @HikariCalyx in Telegram. He unlocks HMD Bootloader.
Click to expand...
Click to collapse
I allready have a unlocked bootloader...but every custom rom makes bootloop. So I need to downgrade firmware but not to latest 8.1 but older.
is it safe to downgrade or flash an older version OTA/firmware? worrying i would brick my phone
what is QFIL and NB0... ?
wildplace said:
is it safe to downgrade or flash an older version OTA/firmware? worrying i would brick my phone
what is QFIL and NB0... ?
Click to expand...
Click to collapse
If youre using a TA-1046 or TA-1062 it is safe. QFIL & NB0 are firmware files for those who unlock their bootloader.
Can I flash 1062 firmware to my 1046....will it boot?
how to flash qfil firmware?
schizmatyk said:
yeah i have this file but app says this system is to old...I spoke with one guy about this problem and he can help mi but later. Now i have to wait
Click to expand...
Click to collapse
If you want latest full image supported for ost i will upload tomorrow . Just remind me if in case i forgot.
blackpanther0582 said:
If you want latest full image supported for ost i will upload tomorrow . Just remind me if in case i forgot.
Click to expand...
Click to collapse
No, thank you. I need to downgrade system, and I do it today morning. Now I'm on RR but I don't know why I'm not happy enough. Anyone know better ROM working fine on 7 plus?

PSA: March 1 security patch is possibly vulnerable to privileged code execution

What this means is that we may be able to take advantage of this to gain root access long enough to boot twrp and root it permanently, so anyone who knows enough, can you please work to make this possible?
Nokia just pushed out the April security patch.

Categories

Resources