Hi, i share my personnal experience, struggled to figure out what was wrong after flashing OB2 but it seems it's all good now.
Did this from OpenBeta2, no specific firmware required i guess as long as the tool we will use is there to erase everything.
I used the official 3.2.3.0 twrp to avoid strange encryption thing (link here)
a user reported this bug because of a custom recovery
1. Download MSMDownloadTool. The 4 files in the MEGA links seems to be requrired so download as zip the whole thing.
2. Follow the guide i quoted then check my instructions
credit to @Fivegates
Guide how to revive your op6:
First of all, you need to access to fastboot mode, if you can't , contact Oneplus support, then have a windows computer and download these file and drivers qualcomm ( https://androidfilehost.com/?fid=24052804347798730) and extract in one folder.
After you have all the file ready, plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug.
Now you have to go in Windows test mode to not let him install default drivers, so:
windows key (on keyboard) + X, windows powershell (or normal prompt) administrator and write and enter: bcdedit /set testsigning on ( you will repeat the same process with "off" to stop the test mode after you will finish to do all the things).
Reboot the system and you could see in bottom right corner the test mode, now you are ready to install properly drivers.
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process (https://www.youtube.com/watch?v=PpLvmID1wdI)
Right click con US8_BULK in device manager and update drivers by system files (go to the folder's drivers you had extracted before).
Now you should see qualcomm drivers under port (COM).
You are ready to let the tool to do all the stuff, so let plugged the phone, always powered off, right click on msmdownloadtool and execute as administrator.
You should see your device and click start to begin the process; if it gives you some error (like sahara or something else), unplug, power on, power off and the plug it again, now it should be fine.
And that's it, the tool will do all the work and, at the end, you will have like a brand new phone ready to a new setup.
EDIT: if you are stucked in bootloader, you have only to power off and continue with the part: ... hold for 5 seconds vol up... (it happened in page 4)
Click to expand...
Click to collapse
lil shortcut guide (might be wrong lol check @Fivegates post if scared)
# go to Device manager, delete your op6 drivers
# enable the test mode with
Code:
bcdedit /set testsigning on
(don't forget to turn off when you're done)
# reboot your pc
# open msmdownload
# power off phone, press vol up and connect phone to pc
# upgrade mode ticked, click once on the only line you see and hit START
# wait
# unplug when it's done
3. Once process is over the phone is back stock 5.1.5 with locked bootloader
4. update to OB2 via local update in settings
Comprehensive guide to update manually
5. unlock your bootloader
6. you should be able to boot on OB2 without that red annoying popup, flash a twrp and magisk whatever
Useful Guide to Unlock Bootloader, Flash TWRP, Root and more
VISUAL GUIDE
Tell me if it works for you too, personnally i've been able to unlock bootloader, flash the latest twrp and magisk
I am living along with corrupted device no problem at all.
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Toni Moon said:
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Click to expand...
Click to collapse
Same here for me. I tried the method mentioned in the op too. It gives the same error once I update to pie. The error is still there for hydrogen and oxygen. Dp3 doesn't have that issue
Toni Moon said:
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Click to expand...
Click to collapse
Yeah that "issue" is terrific :crying:
Did you try this way ?
80s Baby said:
Same here for me. I tried the method mentioned in the op too. It gives the same error once I update to pie. The error is still there for hydrogen and oxygen. Dp3 doesn't have that issue
Click to expand...
Click to collapse
you tried this and it fails ?
Neil_Armstrong_ said:
you tried this and it fails ?
Click to expand...
Click to collapse
Yes it does fail for me. It clears that warning when it's downgraded but once updated to any version of pie. The warning comes back again
80s Baby said:
Yes it does fail for me. It clears that warning when it's downgraded but once updated to any version of pie. The warning comes back again
Click to expand...
Click to collapse
Huh
Did you unlock bootloader before or after updating to Pie ? I honestly don't know what/where the wolf is
Neil_Armstrong_ said:
Huh
Did you unlock bootloader before or after updating to Pie ? I honestly don't know what/where the wolf is
Click to expand...
Click to collapse
Before..I guess right around the first update 5.1.6 or 7. That's when I bought the phone
80s Baby said:
Before..I guess right around the first update 5.1.6 or 7. That's when I bought the phone
Click to expand...
Click to collapse
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Neil_Armstrong_ said:
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Click to expand...
Click to collapse
Yes, this is the way
Neil_Armstrong_ said:
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Click to expand...
Click to collapse
Can I root my device after updating? Coz that's when the issue normally comes in as well
80s Baby said:
Can I root my device after updating? Coz that's when the issue normally comes in as well
Click to expand...
Click to collapse
Hi
I did exactly the same process as mentioned above and I have no problem with root
I first unlocked bootloader then fastbooted twrp + installer.zip
Then I flashed magisk and tons of stuff no red warning
Keep me updated
Neil_Armstrong_ said:
Hi
I did exactly the same process as mentioned above and I have no problem with root
I first unlocked bootloader then fastbooted twrp + installer.zip
Then I flashed magisk and tons of stuff no red warning
Keep me updated
Click to expand...
Click to collapse
Tried this last night it is still the same. Everything went well until I flashed magisk. That's when I got the warning this time.
Did you flash blu spark twrp?
This method works to me..
80s Baby said:
Tried this last night it is still the same. Everything went well until I flashed magisk. That's when I got the warning this time.
Click to expand...
Click to collapse
Toni Moon said:
Did you flash blu spark twrp?
This method works to me..
Click to expand...
Click to collapse
Yes, I haven't tried the official one yet..should I try that out instead?
80s Baby said:
Yes, I haven't tried the official one yet..should I try that out instead?
Click to expand...
Click to collapse
Official TWRP
I had the same error when I dirty flashed from 5.1.11 to the official 9.0. The method from OP fixed it. I'm back to 9.0 with TWRP, Magisk, and custom kernel without the annoying message.
Thanks a lot!
sasho36 said:
I had the same error when I dirty flashed from 5.1.11 to the official 9.0. The method from OP fixed it. I'm back to 9.0 with TWRP, Magisk, and custom kernel without the annoying message.
Thanks a lot!
Click to expand...
Click to collapse
can I still use the bluspark twrp or no?
R0ttenB4ndit said:
can I still use the bluspark twrp or no?
Click to expand...
Click to collapse
just read bro used official twrp 3.2.3
Related
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Edit: CHECK THE COMMENTS FOR SOLUTION
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Ok, stop freaking, this is very fixable. Assuming you have the Google version, or the Verizon version unlocked.
Short answer, we are going to get it into fastboot mode and we are going to flash you back to stock and probably save your data.
First, we need to make sure you have the correct version of Fastboot/ADB. It must be from GOOGLE.
https://developer.android.com/studio/releases/platform-tools.html
Unzip that onto a spot on your desktop.
Then go here and download the latest image for the Pixel. I am assuming you are in the US, get 7.1.1 (NOF26V, Feb 2017) for the Pixel.
https://developers.google.com/android/images#sailfish
Unzip that into a the Platform folder you made above with the fastboot tools. When you are all done it should look like the picture below. The highlighted items are the items that came from the Factory Image you extracted in step two. Everything else is from the platform tools.
Now RIGHT click 'flash-all.bat' and edit it. Near the end...look for the -w and take it out and save it. Removing that is what is going to save your data.
Power down your phone, restart it in bootloader mode. Power and Vol Down. Connect it to your computer and then double click 'flash-all.bat'.
That will take you back to stock unlocked and all your data and settings will be there.
Get past that and let us know. Then we will get you properly rooted. Yea, you used the wrong root process.
I love you <3
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
AlexCoetzee said:
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
Click to expand...
Click to collapse
You are most welcome. Do you need help rooting now?
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
No thank you! I figured that out pretty quickly with TWRP and I am happily rooted now Quite a different process after jailbreaking iOS for 8 years. Thanks for your help!
Misterxtc said:
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
Click to expand...
Click to collapse
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Tulsadiver said:
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Click to expand...
Click to collapse
Good to see you here too. It feels great to be free of TouchWiz!!
Misterxtc said:
Good to see you here too. It feels great to be free of TouchWiz!!
Click to expand...
Click to collapse
And how. I'm done with Samsung.
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
stpbby said:
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
Click to expand...
Click to collapse
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Thanks! That worked.
I need help with unlocking bootloader and rooting phone
TonikJDK said:
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Click to expand...
Click to collapse
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If your on Verizon, no, you can't unlock the bootloader
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If it is a Verizon phone, no you can't unlock it. If it is a Google phone to unlock...below is a decent link on how to. Except use the ADB Fastboot tools I link to in the third post of this thread.
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
And be aware, when you unlock it...it will wipe all the data on your phone.
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
moeREM said:
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
Click to expand...
Click to collapse
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
TonikJDK said:
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
Click to expand...
Click to collapse
I think so, but am not 100% sure. Was bought unlocked from a retail shop. (Sorry, am a bit of a newb!)
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
TENN3R said:
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
Click to expand...
Click to collapse
I'm having bootloops at the initial white google logo screen with SR3-SuperSU-v2.79-SR3-20170114223742.zip flash method on 7.1.2-May
Re: https://theunlockr.com/2017/02/01/root-google-pixel-pixel-xl/2/
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
Use bluespark or black themed twrp
https://forum.xda-developers.com/showpost.php?p=77748695&postcount=7
another member is having the same issue, here's my recommendation. let me know if it helps please.
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
Same situation, same problem. I tried:
Code:
fastboot boot twrp-3.2.3-x_blu_spark_v9.85_op6.img
and still I end up in CrashDump Mode.
mackler said:
Same situation, same problem. I tried:
and still I end up in CrashDump Mode.
Click to expand...
Click to collapse
Use v9.86
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Works. Thank you!! :victory:
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Same, that was the issue, thanks!
Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
actually, now my phone wont get past those spinning circles when it starts up. I can get into recovery. What can i do to fix this?
EDIT: I restored my old bootloader, but now my phone isn't rooted. I have twrp recovery. i tried flashing magisk 17.1, is there something here i shouldn't have done?
Giodude12 said:
actually, now my phone wont get past those spinning circles when it starts up. I can get into recovery. What can i do to fix this?
EDIT: I restored my old bootloader, but now my phone isn't rooted. I have twrp recovery. i tried flashing magisk 17.1, is there something here i shouldn't have done?
Click to expand...
Click to collapse
if you are on stock firmware, why do you want twrp? Unless you are going to aosp rom or want to decrypt the phone, twrp is not needed then.
MrSteelX said:
if you are on stock firmware, why do you want twrp? Unless you are going to aosp rom or want to decrypt the phone, twrp is not needed then.
Click to expand...
Click to collapse
Just looked into it. For whatever reason it doesn't work on Android p unless I run the uninstaller first. Thanks for the help though, I'm all good.
Use v9.86 of ... ??
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Use v9.86 of what ??
dash_z1 said:
Use v9.86 of what ??
Click to expand...
Click to collapse
Blu spark twrp..
Thank you
whizeguy said:
Blu spark twrp..
Click to expand...
Click to collapse
thank you just reialized that i`m supposed to use blue spark version of twrp for my op6 although they provided the original twrp links which was misleading in the root post
So I just picked up a Pixel 3 while on sale to replace my failing Nexus 5 that was literally falling apart. I managed to unlock the bootloader easily. Used a USB C to USB A cable from my Nintendo Switch used for charging the controller for unlocking the bootloader. Next step was to install TWRP and eventually Magisk.
So I followed the instructions to install TWRP from the TWRP website and grabbed the latest image and zip. Initially when I ran the command to boot the image, I would get a "too many links" error. Everything I found in relations to this said I needed a better cable. Odd but okay. I had planned to pickup a new one anyways for transferring music and pictures and such. Got it today, reboot into fastboot and now the command completes successfully with no error. Unfortunately instead of booting into TWRP temporarily as per the instructions, to then install the ZIP for TWRP, the phone boots straight into Android. I have tried the following commands. The first being from the official TWRP guide, and the second being from another guide I had found.
fastboot.exe boot twrp-3.2.3-0-blueline.img
fastboot.exe boot recovery twrp-3.2.3-0-blueline.img
Obviously both result in the same issue. Namely the phone simply reboots right into Android. I am using the latest Platform SDK tools from google, and am using the most up to date drivers for the phone. I am at a loss of what I might be missing. I do see info about boot slots A and B (My phone is B), but nothing in relation to that as far as installing TWRP is concerned. Any help would be appreciated!
What Android version is your Pixel 3 device running?
BobPony said:
What Android version is your Pixel 3 device running?
Click to expand...
Click to collapse
Android 10. Latest OTA.
Ultratails42 said:
Android 10. Latest OTA.
Click to expand...
Click to collapse
Twrp doesn't work on 10. Maybe it will some day but not now.
jd1639 said:
Twrp doesn't work on 10. Maybe it will some day but not now.
Click to expand...
Click to collapse
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Ultratails42 said:
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Click to expand...
Click to collapse
If you want, you can downgrade to Android 9 using the factory images with the flash-all script. But, it requires to have the bootloader unlocked.
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.
Dear members plz suggest me a best solution for this problem plz
I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images
But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now
Theracerlucky said:
Dear members plz suggest me a best solution for this problem plz
I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images
But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now
Click to expand...
Click to collapse
The error is telling you exactly what you need to do - you need to update bootloader to the required version. If you are attempting to flash the factory firmware, the required bootloader and baseband files should be included in the zip file.
V0latyle said:
The error is telling you exactly what you need to do - you need to update bootloader to the required version. If you are attempting to flash the factory firmware, the required bootloader and baseband files should be included in the zip file.
Click to expand...
Click to collapse
I don't understand properly can you brother tell me with more details plz i tried already to flash sum upper versions bootloader factory images but showing this errors continue
Theracerlucky said:
I don't understand properly can you brother tell me with more details plz i tried already to flash sum upper versions bootloader factory images but showing this errors continue
Click to expand...
Click to collapse
The screenshot you posted describes the problem. When you flash a factory image, it first checks the device bootloader and baseband versions to make sure they are up to date. If they are out of date, you get the error as shown:
Device bootloader version is 'mw8998-002.0059.00'
Update requires 'mw8998-002.0076.00'
You need to update the bootloader and possibly the baseband version.
The absolute easiest way to flash the factory firmware is with the Android Flash Tool. Leave your device connected to your computer, and go to this link. Allow ADB keys access when requested. Before you flash, make sure you click the pencil icon to choose options, as the tool selects Wipe Device and Lock Bootloader by default.
If you are still trying to flash your device manually, make sure your Platform Tools are up to date.
V0latyle said:
The screenshot you posted describes the problem. When you flash a factory image, it first checks the device bootloader and baseband versions to make sure they are up to date. If they are out of date, you get the error as shown:
Device bootloader version is 'mw8998-002.0059.00'
Update requires 'mw8998-002.0076.00'
You need to update the bootloader and possibly the baseband version.
The absolute easiest way to flash the factory firmware is with the Android Flash Tool. Leave your device connected to your computer, and go to this link. Allow ADB keys access when requested. Before you flash, make sure you click the pencil icon to choose options, as the tool selects Wipe Device and Lock Bootloader by default.
If you are still trying to flash your device manually, make sure your Platform Tools are up to date.
Click to expand...
Click to collapse
But bro when I trying to flash with Android flash tool showing this errors
Theracerlucky said:
But bro when I trying to flash with Android flash tool showing this errors
Click to expand...
Click to collapse
I haven't seen that error before. Your bootloader is unlocked, right?
Theracerlucky said:
But bro when I trying to flash with Android flash tool showing this errors
Click to expand...
Click to collapse
"FAILED (remote: Command Flash Error)" -- When flashing bootloader
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader: sending 'bootloader_a' (38728 KB)... OKAY [ 2.095s] writing 'bootloader_a'...
forum.xda-developers.com
V0latyle said:
I haven't seen that error before. Your bootloader is unlocked, right?
Click to expand...
Click to collapse
Yes properly unlocked bro
Theracerlucky said:
"FAILED (remote: Command Flash Error)" -- When flashing bootloader
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader: sending 'bootloader_a' (38728 KB)... OKAY [ 2.095s] writing 'bootloader_a'...
forum.xda-developers.com
Yes properly unlocked bro
Click to expand...
Click to collapse
Bro can you please read this post for me i think it's the same like my issues but i don't understand this things properly what i do
Theracerlucky said:
Bro can you please read this post for me i think it's the same like my issues but i don't understand this things properly what i do
Click to expand...
Click to collapse
I don't say this to be rude, but if you don't know what you're doing, nor understand the basic concepts at play here, you shouldn't be tinkering with your phone.
It looks like the user who posted that thread was able to fix his issue by sideloading the OTA. Do you have a custom recovery such as TWRP installed, or is everything stock?
I can provide instructions on how to sideload the OTA later today, but I must emphasize how important it is for you to understand what you are doing, because doing something wrong could result in bricking your device.
Lastly, please don't call me "bro".
V0latyle said:
I don't say this to be rude, but if you don't know what you're doing, nor understand the basic concepts at play here, you shouldn't be tinkering with your phone.
It looks like the user who posted that thread was able to fix his issue by sideloading the OTA. Do you have a custom recovery such as TWRP installed, or is everything stock?
I can provide instructions on how to sideload the OTA later today, but I must emphasize how important it is for you to understand what you are doing, because doing something wrong could result in bricking your device.
Lastly, please don't call me "bro".
Click to expand...
Click to collapse
Ok sir i don't installed any custom recovery now my devices all things is stock
Alright. Here's how to sideload the OTA.
Connect your device to your PC.
Download Pixel 2 December 2017 OTA. You can also try the December 2020 OTA. Do not unzip or extract these files, you will use them as-is.
In bootloader mode, use the Volume + and - buttons to select Recovery Mode, then press the Power button.
You will arrive at a screen with a green Android and "No command". Hold down the Power button and click the Volume Up button.
You will now be in the recovery menu. Use the Volume buttons to select Apply update from ADB, then press the Power button.
On your PC, open a command window in Platform Tools. Use this command: adb sideload, insert a space, then drag and drop the OTA file you just downloaded into the command window.
Press Enter. The sideload process will begin. Once it finishes, you will be taken back to Recovery Mode. Select Reboot now.
Your device should boot into Android. At this point you should be able to reboot to bootloader and use the Android Flash Tool to flash your desired update.
V0latyle said:
Alright. Here's how to sideload the OTA.
Connect your device to your PC.
Download Pixel 2 December 2017 OTA. You can also try the December 2020 OTA. Do not unzip or extract these files, you will use them as-is.
In bootloader mode, use the Volume + and - buttons to select Recovery Mode, then press the Power button.
You will arrive at a screen with a green Android and "No command". Hold down the Power button and click the Volume Up button.
You will now be in the recovery menu. Use the Volume buttons to select Apply update from ADB, then press the Power button.
On your PC, open a command window in Platform Tools. Use this command: adb sideload, insert a space, then drag and drop the OTA file you just downloaded into the command window.
Press Enter. The sideload process will begin. Once it finishes, you will be taken back to Recovery Mode. Select Reboot now.
Your device should boot into Android. At this point you should be able to reboot to bootloader and use the Android Flash Tool to flash your desired update.
Click to expand...
Click to collapse
Sir i know this process but my tension is this process work properly or i brick my device
Theracerlucky said:
Sir i know this process but my tension is this process work properly or i brick my device
Click to expand...
Click to collapse
Sideloading the OTA is actually the safest way to update, and the least likely of bricking your device.
As long as you're able to access bootloader, your device isn't truly bricked.
I understand your consternation, especially as it appears you're fairly inexperienced regarding this. Simply follow my instructions and you'll be fine. I'm trying to make this as easy and foolproof as possible for you.
V0latyle said:
Sideloading the OTA is actually the safest way to update, and the least likely of bricking your device.
As long as you're able to access bootloader, your device isn't truly bricked.
I understand your consternation, especially as it appears you're fairly inexperienced regarding this. Simply follow my instructions and you'll be fine. I'm trying to make this as easy and foolproof as possible for you.
Click to expand...
Click to collapse
Sir can I download this ota file for sideload or other versions
Theracerlucky said:
Sir can I download this ota file for sideload or other versions
Click to expand...
Click to collapse
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Sir you busy now ??
When you free sir reply me i have one more last question answer me plz after that i try to sideload the ota
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
I see a video on YouTube ithink that is the same issues
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
Whe
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you
Click to expand...
Click to collapse
V0latyle said:
Yes, that is the file I linked. Download it and follow the instructions I provided to sideload it.
If you don't follow instructions I don't know how else to help you.
Click to expand...
Click to collapse
When I comented this Youtuber brothers he told me to sideload the latest ota file he created the video on 4 year ago but the latest ota is now Android 11 what can I do sir plz help i am confused he doesn't reply me after this comment reply