Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
I was thinking of buying N7P instead of Xiaomi Redmi Note 5,but I read that Nokia doesn't allow users to unlock the bootloader, so no custom ROMs, no TWRP and no root. That is a big no for me personally.
How did you root your phone? Care to share some info?
_Raziel666 said:
I was thinking of buying N7P instead of Xiaomi Redmi Note 5,but I read that Nokia doesn't allow users to unlock the bootloader, so no custom ROMs, no TWRP and no root. That is a big no for me personally.
How did you root your phone? Care to share some info?
Click to expand...
Click to collapse
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.
hikari_calyx said:
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.
Click to expand...
Click to collapse
I didn't know that prototypes have their bootloader unlocked!
Hopefully, by the time it hits European stores, the Chinese who got it first might have figured something out. Or maybe, as it's part of Android One, it will be obligatory to allow users to unlock the bootloader.
hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
I have the firmare will upload it tomorrow. Is there a forum created for Nokia 7+ already ??
Thank you, if root will be avaible I'll definitely consider buying the phone.
What do you think of the phone? Quality of screen, performance, battery...
How were you about to get a prototype device? What about the retail chinese phones? I was thinking about importing them from ebay/aliexpress but im not sure if they'll be able to have their bootloader unlocked, no one has tried so far to my knowledge.
reeved said:
How were you about to get a prototype device? What about the retail chinese phones? I was thinking about importing them from ebay/aliexpress but im not sure if they'll be able to have their bootloader unlocked, no one has tried so far to my knowledge.
Click to expand...
Click to collapse
I still have no idea of if the bootloader on China Variant is unlockable.
But, if you're going to buy Nokia 7+ from China, here's some warning:
1. Only Chinese (both Simplified and Traditional) and English is available on the phone.
2. You can install Play Store manually, but you must told the seller that preserves everything on stock to prevent from tampered system.
3. If the system got damaged, you have to find someone who can provide service support to flash your phone. I don't know if you can flash Android One firmware for global release since I don't have one.
hikari_calyx said:
I still have no idea of if the bootloader on China Variant is unlockable.
But, if you're going to buy Nokia 7+ from China, here's some warning:
1. Only Chinese (both Simplified and Traditional) and English is available on the phone.
2. You can install Play Store manually, but you must told the seller that preserves everything on stock to prevent from tampered system.
3. If the system got damaged, you have to find someone who can provide service support to flash your phone. I don't know if you can flash Android One firmware for global release since I don't have one.
Click to expand...
Click to collapse
Thanks for that info, on point 2 regarding play store does that extend to Google services also? Wifey is holidaying in China and just bought one and thought to buy another for me but I'm holding her off until I can be sure as I rely on Google services a great deal. Also why must the seller be informed, is that a warranty issue or software update issue?
And on point 3, presuming she brings the phone back to New Zealand is there a way I can help the community to explore flashing Android One global release firmware?
maomaoliu-bright said:
Thanks for that info, on point 2 regarding play store does that extend to Google services also? Wifey is holidaying in China and just bought one and thought to buy another for me but I'm holding her off until I can be sure as I rely on Google services a great deal. Also why must the seller be informed, is that a warranty issue or software update issue?
And on point 3, presuming she brings the phone back to New Zealand is there a way I can help the community to explore flashing Android One global release firmware?
Click to expand...
Click to collapse
If you can buy it from China directly, informing seller is not necessary. For example, if you can buy it from Jing Dong or Suning, you needn't to worry about tampered OS, and that means you can receive further updates.
If you buy it from eBay or AliExpress, the system is probably tampered by seller which you can't get further updates.
As for install Play Store, it's really easy - just find Play Store APK from APKPure, APKMirror whatever and install it on the phone, this will allow you to get access to Play Store. Then you can install any other Google Apps on Play Store manually. You needn't to root your phone and install opengapps.
Since Android One firmware hasn't released yet and the bootloader isn't unlockable, you can't flash it right now.
Nokia 7 plus is available on Amazon europe sites like Germany and Italy and others and also ships worldwide and release date showing 12 to 14 or 15 april
hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
pls pls pls
Post system image of oreo 8.1
thank you!
Big question here! I am going to europe and want to buy this phone there, the problem is that the model they are selling don't have band 4 (1700/2100) and i need it in my country. Is there a way to fix this? Is a model in europe with band 4? Can i flash the modem with band 4? Thanks a lot!
As the phone should be available, are there any news about the firmware of Europe phones? Is the bootloader unlocked / unlockable?
flo.ei said:
As the phone should be available, are there any news about the firmware of Europe phones? Is the bootloader unlocked / unlockable?
Click to expand...
Click to collapse
According to this post, the official bootloader unlocking from HMD themselves is imminent.
I heard the Chinese Firmware supports navbar gestures where you can disable navbar and use gestures and this isnt available in Global version
That SUCKS! its such a good feature NOKIA give it to all!
varun.gid said:
I heard the Chinese Firmware supports navbar gestures where you can disable navbar and use gestures and this isnt available in Global version
That SUCKS! its such a good feature NOKIA give it to all!
Click to expand...
Click to collapse
Try searching in settings for 'nav'. It will reveal the Navigation key of fingerprint setting.
TA-1046, Android 8.0
hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
How you dumped emmc of nokia 7 plus oreo 8.1.0 ?
Does anyone have the build.prop from the Nokia 7 Plus they can post?
hikari_calyx said:
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.
Click to expand...
Click to collapse
Bro can we dump emmc of ta-1046 by using same method
Having unlocked bootloader???
i have a pixel 3a unlocked bootloader and running android 10 {hate it} trying to roll back with no luck also i have no recovery installed maybe its me phone is fine i want to install twrp but the biggest thing is i want to roll back to android 9 because of cell service problems this is harder then my pixel 2xl and 2 also are there any roms for this i only see two thanks
Wrong forum
Pixel 3a does not support twrp on android 10 yet afaik, https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
If you want to revert back to Android 9, download a Factory Image for your device from here https://developers.google.com/android/images, extract, boot phone in to bootloader and run the flash-all.bat. Make sure to back everything up first as this will wipe your device.
i have looked everywhere.
i am trying to find the stock recovery for oneplus 7 pro
- t-mobile version (if required)
10.0.1 oos
Honestly this phone has been the worst experience ever.
From t-mobile not allowing me access to files to fix my device, to forums being dead, sluggish and from several developers not caring about the issues others experience. to a single phone with 7 different variations. and the one I'm stuck with has 0% help.
ive seen multiple request for these files to go look and see "nvm i just flashed international rom..."
honestly it should be illegal for companies to not provide these files.
ivoe said:
i have looked everywhere.
Click to expand...
Click to collapse
That is because you are looking for something that does not exist. This phone doesn't have a recovery partition. On A/B partition devices, the recovery resides on the boot.img partition (along with kernel and ramdisk). The A/B partition scheme is very confusing if it is new to you (as it is to a lot of folks). You can possibly fastboot flash the stock boot.img partition, depending on what exactly you are trying to accomplish.
I don't buy carrier branded phones anymore, for some of the reasons you are experiencing. Converting the T-Mob 7 Pro to be "international", seems to be a pretty popular thing.
This device is far from being "dead" the most common thing to do with the T-Mo version is to flash the international ROM. The only thing people do on the T-Mo ROM is to SIM unlock, thus allow bootloader unlocking, then go right back to the international ROM.
CosmicInsight said:
This device is far from being "dead" the most common thing to do with the T-Mo version is to flash the international ROM. The only thing people do on the T-Mo ROM is to SIM unlock, thus allow bootloader unlocking, then go right back to the international ROM.
Click to expand...
Click to collapse
i have had to many issues with international that i msm back to tmobile.
i just didnt want to lose everything over an over doing this when things go wrong
i believe i have dumped the boot.img
i just hope it works when i do need it again.
Here's what I did whenever T-Mobile update to Android 10.0.1 I downloaded the OTA Update from off the internet then extracted it on my desktop then I used the payload-dumber-win64 to get the recovery and boot.img to use Incase I needed them. I used the extracted boot.img from the payload-dumber-win64 and followed instructions on how to use magisk patcher to patch my own boot.img. search Google for the T-Mobile update then use the tools to extract the whole thing.
Booted up a oneplus 9 pro boot image, it fixed my phone being stuck in fastboot because I didn't have stock image.
Now updates don't work.
Oneplus 9 T-Mobile, stock rom, pro boot image, unlocked bootloader, unlocked sim - Any help would be appreciated.
Was thinking MSM tool but unsure what one to use.
I'm in a similar situation but I can't get out of fastboot. What OnePlus Pro boot image did you flash to your phone and what firmware are you on?
I gave the pro boot.img a try and it worked!
I grabbed it from this post: https://forum.xda-developers.com/t/...t-keep-root-oos-12-c-48.4252373/post-87096189
I want to back a few things up before tinkering anymore but will report back on how I try to fix it.
Thinking ahead, did Oxygen Updater not allow you to change your device back to a OnePlus 9, download the software update, flash and revert back?
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Harley1979 said:
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Click to expand...
Click to collapse
Are you using Oxygen Updater or the native update tool?
If the latter I would try the former.
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
No I'm on a t-mobile oneplus 9 with android 12.
Soooo have you tried Oxygen Updater?
No it doesn't work for my version of this phone.
Thanks though
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Harley1979 said:
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Click to expand...
Click to collapse
If your bootloader is unlocked and Google Play is telling you that your device is not supported, it's because of the unlocked bootloader most likely. Are you successfully passing both basic and CTS safetynet profiles?
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Harley1979 said:
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Click to expand...
Click to collapse
I think your problem is that your bootloader is unlocked and it needs to be locked in order to pass safeynet. More and more apps are not allowing for detected unlocked bootloaders in which makes safetynet fail.
Wish I knew how to relock it... Little reluctant to use a random site's information... Xda probably has information on relocking it, wish I had a link to a good post.
Could it possibly brick my phone if I'm using a pro boot image an try to lock bootloader?
Any advice or help would be much appreciated thanks for your time.
I will follow-up more later as I'm walking out the door. I'm not convinced that we are on a different or should I say, incompatible boot.img. When I get home I need to do some research to see what is actually different in the boot.img when being compared each other (C.61 boot.img on OP9 and OP9 Pro).
Back history for anyone following along... I was unlocked, rooted, Google Play certified and on C.48. I upgraded via OTA, no reboot and chose an inactive slot. It did not work and soft bricked slot a. I lost root, was on C.48 still but on slot B. I successfully upgraded to C.61 but didn't have root. I could not find a good boot.img or patched_boot.img. I tried a stock OP9 Pro image and that got me working. That same user provided a patch img too so I tried that and obtained root as well.
Soooo what is the difference between the boot images on C.61 pro and non-pro OP9 models?
Stay tuned....!
Thanks I'll keep checking back on this
Unfortunately the difference is that the pro version is available to tinker with and the non pro version isn't. Sorry to state the obvious.
My phone so far is working fine on the OP9 Pro kernel. C.61 is rooted and Google Play is certified. All my previous Magisk config is there as well and modules. I'm not sure what the difference between the kernels are at this point but also not a kernel expert either.
Once the next full release comes out for OP9, I will swap it out.
@Harley1979 I got your PM and will follow-up with you there.
Hello, I've been searching and lurking.. I've unlocked the bootloader on my Pixel 3a. I've rooted before, restored before, nandroids etc etc. So I've been in the game for a little while. (all the way back to my LG Ally!) Anyways. I was wondering what would be the best method of Rooting and installing TWRP on the Pixel 3a at this point in time, and if TWRP is even possible at this point. (September 2022) Should I use Magisk? NetHunter seems to rely on the device having TWRP in order to flash the kernel. (but we don't NEED it to flash the kernel do we?) I keep coming across old posts which do not apply to the build of my phone and I'm feeling very lost. This phone is not my daily driver, and I am confident when it comes to restoring a soft-brick. It's a Google Fi pixel, bought from the google store, maybe that helps.
Android 11, RQ2A.210405.005 (info from recovery)
BL Version : b4s4-0.3-7062600 (fastboot)
Baseband Ver: g670-00105-210113-B-7078968 (fastboot)
Secure Boot - Yes (fastboot)
HW Ver - MP1.0 (fastboot)
EDIT: Rooted phone successfully using Magisk/patched boot.img.
NEW ISSUE! : The phone is showing up as a Pixel 5 now. In rootchecker, my first successful root shows Pixel 3a as the device. This has never happened to me before. Any input would be greatly appreciated!