Links attached for those interested from Essential Web Site, and source.android.
https://support.essential.com/hc/en-us
https://source.android.com/source/running
The real question is kernel source. Not much reason to unlock the bootloader without that.
Goronok said:
The real question is kernel source. Not much reason to unlock the bootloader without that.
Click to expand...
Click to collapse
Exactly.
I'm not holding my breath.
I think I'm jumping ship.
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
gqukyo said:
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
Click to expand...
Click to collapse
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
drocny87 said:
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
Click to expand...
Click to collapse
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
Some people got the update today. If you happen to get it can you try to pull the boot?
I have the update waiting to be installed.
graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
in the build thread, a user was able to capture the OTA url. the only issue, the boot.img is stored in the payload.bin file. Are you familiar with this file and how to extract it?
So is this phone rootable?
Sent from my SM-G950U using XDA-Developers Legacy app
canynballa said:
So is this phone rootable?
Click to expand...
Click to collapse
At this time no. Hopefully soon that will change.
In the Andy Rubin AMA, the official Essential reddit account posted that the kernel and factory images would be released to the public "in the next few days". That probably means next week, business days and all, but it looks like they fully intend to support external development of this phone, and soon. Makes sense--why else would they allow a bootloader unlock from the get-go?
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Sarzeck said:
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Click to expand...
Click to collapse
You need to select correct driver in device manager, maybe even install different drivers
See
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my PH-1 using Tapatalk
Thanks buddy! It worked
i love unlocking bootloader on mine but for now until no ROM's mod i will stay locked mode. im a Android Pay dude lol
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Yeah, try another computer. Seriously, my main PC just didn't want to work with the phone. Used my laptop, worked fine. Can't think of anything different, both are Win10, both have the same drivers and sdks. Both work for my other phones, just not this one. Didn't hurt to try. Of course you'll need access to another computer but if you have one or more extras, worth a try. Worked for me.
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Did you reboot the computer? I've seen that help alot when device is not recognize
I'm having same issue, flashing unlock command do not work. I am on the oreo beta version. Someone help please.
Related
Mod was already available for the Pixel2.
If you don't know what Edge Sense Plus is, you can check it here: https://forum.xda-developers.com/pixel-2/themes/root-custom-active-edge-actions-edge-t3732368
Just curious but do we know it can be rooted?
krabman said:
Just curious but do we know it can be rooted?
Click to expand...
Click to collapse
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Will get pixel 3xl by November 8 9. I am willing to test it for you.
ill have mine by 18th or 19th ill help out if still needed.
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
j to the 4n said:
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
WisdomWolf said:
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
Click to expand...
Click to collapse
Doing this would be extremely unwise without a copy of the stock boot image. I would advise you to wait till the factory images come out. Which should be soon. If you bootloop, highly likely, you will have a unusable phone until the factory images get posted.
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Sent from my Pixel 2 XL using Tapatalk
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
WisdomWolf said:
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Click to expand...
Click to collapse
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
I have mine. I'm willing to test whatever/whenever it's safe to do so.
I did enable the "OEM Unlocking" in the developer settings. It didn't come with a USB-C to USB -A cable, so I cannot connect it to a PC anyway.
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Golf c said:
Your phone comes with a boot image.
Click to expand...
Click to collapse
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
lensgrabber said:
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
Click to expand...
Click to collapse
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
sd_matto said:
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
Click to expand...
Click to collapse
There is no "standalone" boot image yet. It comes with factory image. Which should be out soon. The boot image is in your device. You can patch the boot image with Magisk Manager or sideload the Magisk zip. I would not do either of those until you have the factory image. If you bootloop, your device will be useless without factory images
mattj949 said:
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
Click to expand...
Click to collapse
Did you use the "unlock_critical" version of the command or just "unlock"?
Golf c said:
You can patch the boot image with Magisk Manager.
Click to expand...
Click to collapse
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
sd_matto said:
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
Click to expand...
Click to collapse
No 2 the boot image in the device. Unlock bootloader.
Download Magisk Manager apk. Im about ready to unlock mine right now. In Magisk Manager select patch boot image file. It will save a copy to your device. Transfer to PC.
Fastboot flash boot image. You will bootloop im sure. AVB has changed with crosshatch.
DO NOT attempt this without factory image.
I will be doing this when factory image comes out.
nirenshah said:
Did you use the "unlock_critical" version of the command or just "unlock"?
Click to expand...
Click to collapse
Just "unlock" the other one is not valid for this one. Sorry, I should have mentioned that!
My apologies gentlemen. You do need a separate copy of the the boot image from the factory image to patch in Magisk Manager. Sorry for the wrong info. Actually it makes sense doesn't it.
Golf c said:
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
Click to expand...
Click to collapse
I got my Pixel 3XL last night. Excited to get things going on the Pixel 3XL, coming from a Nexus 6P.
I was sad that the factory image isn't immediately available on google's site for this phone, and I don't want to brick it trying to install Magisk without a factory image to fall back onto.
In any case, woot, woot! Phone looks great and I'm going to transfer over my line today.
Cheers,
B.D.
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
My understanding is it won't work on Android 10.
androiddiego said:
My understanding is it won't work on Android 10.
Click to expand...
Click to collapse
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
It sounds like they'll get there, just not quickly. If you read that link closely, this seems to apply to all phones shipped with android 10. So jumping to another phone is not necessarily a solution.
does anyone with a Moto G Stylus have a working stock recovery?
fronto said:
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
Click to expand...
Click to collapse
Did u unlock the bootloader
Sent from my moto g stylus using Tapatalk
When you go into recovery hit the + and - volume buttons together and it will pop up.
Yes their is recovery software. It's rescue mode.
fronto said:
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/mcp/service
twrp
why do you need a recovery when you can unlock the bootloader and use the factory recovery to flash what ever you want and they have a nice recovery option using the rescue and smart assistant software for pc mac or lin. i fail to see why you would want a custom recovery.
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
DMedina559 said:
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
Click to expand...
Click to collapse
How did you root? Are there instructions somewhere for Android 10 root?
cyrusalmighty said:
How did you root? Are there instructions somewhere for Android 10 root?
Click to expand...
Click to collapse
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
DMedina559 said:
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
Click to expand...
Click to collapse
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
I haven't kept up with the android modding scene for years so I'm kinda out of the loop, but the general rule of thumb is to not do ota updates unless you're flashing full images with fastboot or using an OEM recovery software (Lenovo\Moto have one here)
As for the patch, I got the boot.img from the recovery software I linked above and installed magisk manager on my phone to patch the img which I then moved to my laptop to flash in fastboot
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
Hi,
First download Rescue and Smart Assistant from Motorola website, make sure activate the developer options and usb debugging and download your phone's software with Rescue and Smart Assistant (it will find it automatically), find boot.img from inside the downloaded zip file and copy it to your phone, download Magisk Manager to your phone, and patch the boot.img with Magisk Manager, copy patched boot.img to your computer and flash it with adb.
If you have a desire to get TWRP, you should write to Telegram @mauronofrio and raise some donate to develop TWRP for this device.
Root Moto g stylus
fronto said:
does anyone with a Moto G Stylus have a working stock recovery?
Click to expand...
Click to collapse
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Luiszipatla said:
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Click to expand...
Click to collapse
Same issue, I've had the same provoking anger problem with this phone and previously a Moto e5 plus. It's rooted yet no Magisk module seems to work. This phone I can't even get lucky patcher to work. Android 10 sucks, I miss the good old days of Android 6 and 7.
Anyone else notice the modules not working at all but it's rooted?
Also to do a backup, adb backup and adb restore are your friends.
Rooted you can clone the device at least with adb commands. Slower but it's an exact copy at least.
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
vache said:
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
Click to expand...
Click to collapse
Going to flash the patched boot IMG once the firmware is done. Is there an app to catch the log or an adb command?
In trying to root my Nokia 3, I installed TWRP custom recovery but realised that I forgot to install magisk manager. Upon rebooting the phone out of TWRP recovery mode my Nokia 3 is now stuck in a boot loop such that whenever I turn the device off or reboot it, either from adb or TWRP, the device inevitably only reboots in fastboot mode. Even using the fastboot reboot command doesn't work and only boots it up again only for it to enter fastboot mode immediately.
This means that I can't access the phone as usual meaning I'm unable to download the magisk.zip file I need to install magisk. I tried cloning the git-master and sideloading that from my computer but it said invalid .zip format.
Any idea what I can do?
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Totalitor said:
I don't see how I might have done this seeing as I'd guess such a thing would only be possible if I had root on my device. I haven't rooted it yet.
But if I'm mistaken on that, using the TWRP file manager shows an empty /boot/ directory. Is there any way I can restore normal functionality to my device? I just need to be able to get magisk on there so I can install in through TWRP and then root the phone so I can get a custom ROM
Click to expand...
Click to collapse
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
andres_vacal said:
But, in TWRP, when you go to reboot section, does it says "No OS Installed"? ( in the upper side )
Click to expand...
Click to collapse
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Totalitor said:
It doesn't. I suppose the contents of /boot just isn't visible because I haven't rooted the phone yet?
Click to expand...
Click to collapse
idts, have you tried to wipe and install constum ROM again?
andres_vacal said:
idts, have you tried to wipe and install constum ROM again?
Click to expand...
Click to collapse
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Totalitor said:
No. I haven't installed a custom ROM. It was the default android 8.0 OS. I haven't been able to root the phone yet because I don't have magisk manager installed.
The only thing I've installed has been TWRP custom recovery. As I understand it, you can't even install custom ROMS unless the phone is already rooted.
Click to expand...
Click to collapse
No, you only look for the rom of your specific device, and then just flash it trought TWRP
andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
Ok then. I haven't actually been able to find any ROMS for the Nokia 3 other than the stock ROM.
Do you know of any custom ROMS for the device?
andres_vacal said:
No, you only look for the rom of your specific device, and then just flash it trought TWRP
Click to expand...
Click to collapse
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Totalitor said:
I ran adb sideload on the update.zip file downloaded from here.
It seems to have restored my nokia 3 device's recovery to a stock recovery.
Attempting to reboot the device merely reboots it to the stock recovery mode. I cannot seem to get it to reboot into the phone's normal state.
In addition, adb, even while running under root permissions, can no longer detect the device.
I have tried wiping the device, factory resetting it, but the device refuses to reboot into it's normal mode. I can only reboot it into stock recovery or the bootloader.
Click to expand...
Click to collapse
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
My phone randomly decided it'd revert back to TWRP custom recovery today but I still can't access the main operating mode of the phone. Do you know where I can find either a custom ROM for the Nokia 3 or the stock ROM? All instructions I find online seem to be in broken english so I'm having some difficulty following a lot of the guides as they're rather vague
andres_vacal said:
Make sure bootloader is unlocked. In fact if it turned back into stock recovery is because the ROM is already installed. Try to repeat the instalation process using TWRP and try to use another version of the stock ROM.
Click to expand...
Click to collapse
As mentioned in my previous post, my phone reverted back to TWRP custom recovery for some reason. I tried sideloading the Magisk.zip file and it said it successfully flashed it, but now my Android system has reverted back to the standard Android recovery, booting into it by default.
it says
"alps/NE1_00WW_FIH/NE1
7.1.1/NMF260/00WW_2_15A
/user/release-keys"
at the top.
Totalitor said:
The bootloader was unlocked at some point but I guess it must have locked itself again at some stage when I reset it. Though now that my phone seems to be stuck in bootloader mode and stock recovery mode exclusively, I'm not able to view the serial number in settings as that's something one may only do when the normal mode of the device can be accessed.
I'd use adb to retrieve the serial number of the device but adb doesn't seem to be able to detect my device. I have the necessary drivers on my computer and am running on root privileges but it seems it can't detect it if it's not in the normal operating mode. Any idea how I can get the serial number?
Click to expand...
Click to collapse
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
andres_vacal said:
I think before flashing magisk we should make sure the OS is ok, can you write the specific phone model?, "Nokia 3" is not an specific number. Then we should be able to find at least a stock ROM.
Click to expand...
Click to collapse
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Totalitor said:
It's a Nokia 3 TA-1032
Sorry, I should've specified.
Click to expand...
Click to collapse
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
andres_vacal said:
Okay man, I did some research and found out that there is not so much info about the specific model but there is some people with the same problem. Found this thread useful so let's try out that.
Nokia 3 official Firmware India/UAE Region [ Links updated with Flash tool]
Hi All, Nokia 3, 5, 6 & 8 Official Firmware flashing tool is Known as OST ( Online Service Tool) Download link Nokia 3 Firmware :- https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg----- latest for Nokia 3 is v 2.15H Nokia 5 Firmware :-...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Totalitor said:
Thanks, But all of the links on that thread to nokia 3 firmware are dead. In the meantime I used the adb push command to upload the magisk.zip file to my device as well as the Lineage 14.1 custom ROM which I got from here and tried installing both of them using TWRP. TWRP said both were successful but on reboot, my phone is once again stuck in the orange state at the boot screen.
Click to expand...
Click to collapse
Ow, I didn't check that, my bad. Have you tried to flash only LOS?, generally the problem with LOS is that you need to have installed the stock ROM for it to function well, if you wipe and then flash LOS it will say "successful" but it won't start.
Or at least at my experience
andres_vacal said:
Are you sure you haven't deleted the ROM by accident?, that same thing happened to me before.
Click to expand...
Click to collapse
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Totalitor said:
we've established that I must have somehow accidentally deleted the ROM in installing TWRP.
You mentioned you accidentally deleted the ROM. How did you go about fixing your problem?
I've looked everywhere online for Nokia 3 TA-1032 stock firmware but all I can find are dead google drive links. How did you fix your issue? Or was yours with a different model of phone?
Click to expand...
Click to collapse
Mine was with an Asus, and the only way I could fix the horrible bootloop was managing to install the stock un-official ROM made from a well known developer. I just did a short research on this case, and all the solutions on internet say you need the ROM like I just told you, so I think there is no way if we cannot find a ROM for the device.
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said