Database Users

Possibly problem while downgrading.. help please?

I would post my question in the thread that I'm using the guide from, but I don't have enough posts to post in the development section. Embarassing.
Anyway, I'm trying to downgrade using this guide, and 'm at the final section where it should be downgrading. I've created a goldcard and everything has worked perfectly up until this point.
I ran this command: "> fastboot-windows flash zip StockRom.zip"
and it's just said "sending 'zip' ( 291477 KB)..." with the blinking cursor for like 45 minutes. Should it be taking this long? When I first tried to downgrade without the goldcard this entire process from sending to failing took about 7 minutes, this seems entirely too long. I can't write anything in the screen because it's still blinking.. can I safely unplug my phone and try again? Or will that break it? Should I just leave it overnight and see what happens?
Any help would be appreciated... ahh being an android noob is awful.
ETA: I decided to go for broke and unpluuged the phone, because I didn't think it was flashing as it said it was still sending data. After I pulled the phone it gave me a "fail (too many links)" error in ADB. I used the fastboot to reboot it and it's still on 2.3.3. Can anyone tell me why it won't send the file and try to downgrade?

As an update, I tried again and it still won't send the file to the phone using the fastboot code. Is there a way I can put the file on the phone without this code so it will be there already and just flash it?
I'm so frustrated with this, I've been trying to downgrade it for 2 days and I'm about ready to give up. Any help would be much appreciated!

Try put the rom on your sdcard, named PC10IMG.zip
then reboot to bootloader by turning phone off and holding volume down when turning on. that should scan and prompt to update.
-Nipqer

thank you so much!! that did the trick for me, it's back at 2.2!

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

HELP: boot, system and vendor partition flashes failing!

I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.

MRR0GERS said:
I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.
Click to expand...
Click to collapse
Don't flash using the script. Flash them yourself with the commands from the script "fastboot flash system system.img" etc.

crixley said:
Don't flash using the script. Flash them yourself with the commands from the script "fastboot flash system system.img" etc.
Click to expand...
Click to collapse
That's what I did. I've never liked or trusted the scripts from those. I'm back to my Nexus 6 for now till I can hopefully fix the Essential.

Actually I've met this things yesterday when I was trying to flash the DP 3 for my phone. At the first time I stucked when flash the system image and I restarted to bootloader, after reboot I saw a strange serial number doesn't start with PM1LH, and got the no such partition error when I try to flash everything. I googled a lot and no miracle cames, so I just use the command that specified slot (which means I go over all the commands with specifying the slot a at first time and with slot b at second time) , it seems that all images can be flashed into slot a and b at this way except system image, but I re-flashed the system image to slot a and b successfully after flash all other images. And now I get my phone at DP 3, all functions work fine except the serial number is still a strange one. Hope this is useful to help you since I know it is really a bad feeling when the phone seems bricked. Also a hint is when you flash the image with specifying the slot, you may also get the error which says error remote flashing (maybe not accurate), I just re-ran the command and it works. Since English is not my native language, if any thing has grammar error please just ignore it.

MRR0GERS said:
I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.
Click to expand...
Click to collapse
It seems I have the same problem. After flashing the latest Android P beta DP3 through fastboot, some images like system and vendor didn't flash on the first attempt for me. After multiple bootloader reboots I managed to flash everything one by one, but phone's serial number is completely messed up. At first I didn't notice this and continued to configure and use the phone for half a day since I'm on wifi, but then I realized the network is not working either. That is, it shows either no network or zero bars and I cannot place calls or use data. The situation with the network was the same when I flashed Oreo images. I checked my sim card works with another phone, and a sim card from my friend also didn't work with my phone. Could it be due to a weird serial number? If so, how do we revert it back?

What exactly is the error message when you flash those partitions? AFAIK those partitions are the big ones that give a warning about sparse header size which should just be ignored

craznazn said:
What exactly is the error message when you flash those partitions? AFAIK those partitions are the big ones that give a warning about sparse header size which should just be ignored
Click to expand...
Click to collapse
I honestly don't recall what the exact error was.. That being said, there was a new release of the platform tools after I had posted so I installed those, tried again and successfully restored the device to working order!

Which platform tools did you get? Mine are all dated 5/22/2018 after I updated... but for some reason I had to manually flash both sides... for some reason, I get an error trying to flash like this:
fastboot flash nvdef nvdef.img
The error looks like this:
Writing 'nvdef__a' FAILED (remote: No such partition.
But this works for me:
fastboot flash nvdef_a nvdef.img
fastboot flash nvdef_b nvdef.img
If a new/different set of platform tools fixes this, that'd be great.

Has anyone found a solution to this? Namely, did you manage to change back your serial number? I still have no network on my phone, I don't know if it's related.

[help] My Chinese Nokia X6 either is or appears to be rooted out of the box.

I bought a Nokia X6 from China and the phone appears to be rooted. The play store app System info says that I have all the correct specs but also tells me the phone is rooted. Additionally, when booting my phone gives me a message that says: Your device has loaded a different operating system. I have pretty much no idea what to do and honestly just would want a normal stock phone so any help would be very much appreciated.

Same here, except I have no issues with it saying its rooted
just the boot message

If you want a normal stock phone then don't buy Chinese oem devices. They have to add tons of tracking and spying software that is required by the Chinese government. You can research it. Many are even banned in many countries due to their back ally tactics

Darth_revan_returns said:
Same here, except I have no issues with it saying its rooted
just the boot message
Click to expand...
Click to collapse
I managed to solve the problem. If you don't have a lot of experience with Android, you'll have to do a bunch of research, but you should manage. Very roughly, I pretty much flashed a new operating system on the phone. I found the correct os rom from here: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657. I'm definitely a novice in doing weird **** with androids so don't consider me an expert or anything, but I did get my phone to work.
If you don't know what to do here's a rough guide.
1. Get adb to work
Adb is basically a way for your computer to tell crude instructions to your phone and all kinds of random ****. The very very first thing you should do is unlock developer options and turn on developer options by going to settings->system->about phone and click on build number something like 7 times and then go back to system, where developer options have appeared and turn on OEM unlocking and usb debugging. You should be able to find some type of adb installer installer simply by googling how to install adb or something, I can't remember at all where i found mine from, but there are certainly a lot of guides online. It really doesn't matter that much if it's from a few years back, as long as adb works. Your phone should install all correct drivers from your phone simply by connecting it, but you may need to download qualcomm drivers online, I don't really know because I downloaded every random driver online until finally it worked. All I can say that to finally get it to work I connected my phone to my computer via cable with usb debugging enabled and clicked the windows message so that the phone agreed to the final necessary drivers and amazingly it worked. To make sure that everything you need is in working order type the following commands into adb:
First "adb devices" if it says something like device found, DRG...., everything's good so far
Then "adb reboot bootloader" and "fastboot devices", if it says the same thing again, adb is completely installed.
I found this to be by far the hardest part in the whole operation, because the Nokia X6 is such a new phone that there are no real guides or official drivers online. Don't be discouraged if it takes some time to get through this part!
2. Unlock your bootloader
Nokia is pretty cool and all, but that they are pretty restrictive with their phones so that you actually have to pay to a third party to be able to unlock your bootloader. You need to buy a bootloader unlock key from this place: https://www.techmesto.com/buy-nokia-bootloader-unlock-key/. I know it seems super shady, but it at least worked for me so there's that. I wouldn't really buy the unlock key before getting adb to work, though. After that, you'll probably be best off following this guide to unlock the bootloader: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
3. Install the nokia online service tool and nb0 unpacker
The Nokia OST you can find here: https://www.theandroidsoul.com/download-nokia-online-service-tool-ost/, and I think the guide there is pretty self-explanatory, so just follow that. The nb0 unpacker you can find here: https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464. This one should be very simple to install.
4. Download the Nokia X6 operating system and unpack it so you can flash it with the online service tool.
The nokia X6 operating system can be found from the google drive link in this post: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657, and be sure to pick the on mentioned in the post, the one labeled "DRG-229E-0-00CN-B01". After downloading it, you should be able to find a .nb0 file in the zip. Extract it somewhere nice and then use the nb0 unpacker you installed to unpack it. After this, open the mlf-file in the unpacked nb0 folder and follow the following instruction found on the download post i linked before:
"Modify *.mlf file, line 7 ~ 9;
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001" @Xkernels
5. Flash the os on your phone
Make sure to delete everything from your phone before doing this, because every guide I've seen instructs to do this. This may not even be necessary as the OST setting you'll check later indicate that everything will be erased anyways, but idk what could happen so better safe than sorry. You can do this probably in many ways but one way i found is to go to recovery (type "adb reboot recovery" on your pc and then press the power and vol up button at the same time), and factory reset. Then go to the bootloader from there and type "fastboot erase system". A bunch of text should appear and you should be set to flash. Now with your phone connected to your pc, open the Nokia OST and "Select *.mlf files and tick "Normal Download", "Erase user data", "Erase error data", begin to flash." @Xkernels.
6. Your phone should be ready to use, though it will probably need some configuring
The first things you'll probably want to do is use the browser to download a google play apk online after which you can use the play store and download all necessary apps from online. I couldn't find netflix from the appstore but I simply downloaded the apk online and it works too. I had problems with the stock keyboard so I installed Gboard, but all apps should be in working order and my phone works without a hitch now!
For the record if you manage to brick your phone during the process, don't hold me liable. If you followed this guide, you probably bought a chinese random phone and it didn't work like you wanted it to and wanted to fix the problems by installing an operating system from online, using a guide from a person you didn't know at all. All I can say is that what I did worked for me and I simply wanted to help strangers on the internet and this worked for me. So if, because of this guide, everything is ****ed with your phone and your computer is full of viruses, I will most likely be glad to help and you can blame me by yourself, but I definitely would appreciate if you would simply be civil and not tell me how I'm an awful person, because once again, I'm just a Finnish guy, who himself bought a Nokia for 200€ from eBay and had to spend hours upon hours of my own time trying various methods of getting my phone to work and learning how to use adb and how to flash roms on my phone. Honestly the experience was pretty fun for me, because I like to do random **** like this and learning new things, but I did have other things to do with my time like study physics and even now I wrote this, in my own biased opinion pretty good, guide using my own time, simply because knowing I did something good brings joy to my heart.

vostok_amphibia said:
I managed to solve the problem. If you don't have a lot of experience with Android, you'll have to do a bunch of research, but you should manage. Very roughly, I pretty much flashed a new operating system on the phone. I found the correct os rom from here: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657. I'm definitely a novice in doing weird **** with androids so don't consider me an expert or anything, but I did get my phone to work.
If you don't know what to do here's a rough guide.
1. Get adb to work
Adb is basically a way for your computer to tell crude instructions to your phone and all kinds of random ****. The very very first thing you should do is unlock developer options and turn on developer options by going to settings->system->about phone and click on build number something like 7 times and then go back to system, where developer options have appeared and turn on OEM unlocking and usb debugging. You should be able to find some type of adb installer installer simply by googling how to install adb or something, I can't remember at all where i found mine from, but there are certainly a lot of guides online. It really doesn't matter that much if it's from a few years back, as long as adb works. Your phone should install all correct drivers from your phone simply by connecting it, but you may need to download qualcomm drivers online, I don't really know because I downloaded every random driver online until finally it worked. All I can say that to finally get it to work I connected my phone to my computer via cable with usb debugging enabled and clicked the windows message so that the phone agreed to the final necessary drivers and amazingly it worked. To make sure that everything you need is in working order type the following commands into adb:
First "adb devices" if it says something like device found, DRG...., everything's good so far
Then "adb reboot bootloader" and "fastboot devices", if it says the same thing again, adb is completely installed.
I found this to be by far the hardest part in the whole operation, because the Nokia X6 is such a new phone that there are no real guides or official drivers online. Don't be discouraged if it takes some time to get through this part!
2. Unlock your bootloader
Nokia is pretty cool and all, but that they are pretty restrictive with their phones so that you actually have to pay to a third party to be able to unlock your bootloader. You need to buy a bootloader unlock key from this place: https://www.techmesto.com/buy-nokia-bootloader-unlock-key/. I know it seems super shady, but it at least worked for me so there's that. I wouldn't really buy the unlock key before getting adb to work, though. After that, you'll probably be best off following this guide to unlock the bootloader: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
3. Install the nokia online service tool and nb0 unpacker
The Nokia OST you can find here: https://www.theandroidsoul.com/download-nokia-online-service-tool-ost/, and I think the guide there is pretty self-explanatory, so just follow that. The nb0 unpacker you can find here: https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464. This one should be very simple to install.
4. Download the Nokia X6 operating system and unpack it so you can flash it with the online service tool.
The nokia X6 operating system can be found from the google drive link in this post: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657, and be sure to pick the on mentioned in the post, the one labeled "DRG-229E-0-00CN-B01". After downloading it, you should be able to find a .nb0 file in the zip. Extract it somewhere nice and then use the nb0 unpacker you installed to unpack it. After this, open the mlf-file in the unpacked nb0 folder and follow the following instruction found on the download post i linked before:
"Modify *.mlf file, line 7 ~ 9;
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001" @Xkernels
5. Flash the os on your phone
Make sure to delete everything from your phone before doing this, because every guide I've seen instructs to do this. This may not even be necessary as the OST setting you'll check later indicate that everything will be erased anyways, but idk what could happen so better safe than sorry. You can do this probably in many ways but one way i found is to go to recovery (type "adb reboot recovery" on your pc and then press the power and vol up button at the same time), and factory reset. Then go to the bootloader from there and type "fastboot erase system". A bunch of text should appear and you should be set to flash. Now with your phone connected to your pc, open the Nokia OST and "Select *.mlf files and tick "Normal Download", "Erase user data", "Erase error data", begin to flash." @Xkernels.
6. Your phone should be ready to use, though it will probably need some configuring
The first things you'll probably want to do is use the browser to download a google play apk online after which you can use the play store and download all necessary apps from online. I couldn't find netflix from the appstore but I simply downloaded the apk online and it works too. I had problems with the stock keyboard so I installed Gboard, but all apps should be in working order and my phone works without a hitch now!
For the record if you manage to brick your phone during the process, don't hold me liable. If you followed this guide, you probably bought a chinese random phone and it didn't work like you wanted it to and wanted to fix the problems by installing an operating system from online, using a guide from a person you didn't know at all. All I can say is that what I did worked for me and I simply wanted to help strangers on the internet and this worked for me. So if, because of this guide, everything is ****ed with your phone and your computer is full of viruses, I will most likely be glad to help and you can blame me by yourself, but I definitely would appreciate if you would simply be civil and not tell me how I'm an awful person, because once again, I'm just a Finnish guy, who himself bought a Nokia for 200€ from eBay and had to spend hours upon hours of my own time trying various methods of getting my phone to work and learning how to use adb and how to flash roms on my phone. Honestly the experience was pretty fun for me, because I like to do random **** like this and learning new things, but I did have other things to do with my time like study physics and even now I wrote this, in my own biased opinion pretty good, guide using my own time, simply because knowing I did something good brings joy to my heart.
Click to expand...
Click to collapse
Thanks man, now that the 6.1 plus is coming soon I think we'll be able to put it on using this guide!

vostok_amphibia said:
I bought a Nokia X6 from China and the phone appears to be rooted. The play store app System info says that I have all the correct specs but also tells me the phone is rooted. Additionally, when booting my phone gives me a message that says: Your device has loaded a different operating system. I have pretty much no idea what to do and honestly just would want a normal stock phone so any help would be very much appreciated.
Click to expand...
Click to collapse
Same here, so anyone help us to solve this problem?

Question Nothing Phone (1) Brick Recovery lost and "No such file or directory"

So guys,
I got my nothing phone 1 three days ago and I absolutely love it. Then yesterday I tried to root it. I thought it would be easy since I´ve rooted three phones already (older ones like oneplus 2)
I unlocked the Bootloader and it worked fine. Then I researched how to root with magisk and found out that you dont get the boot.img anymore just like that and have to "payload-dump" i tried this for around two hours with every method i could find but it just wouldnt work.
Then I found an already patched boot file and flashed directly out of joy. Then the bootloop hits the Phone.
I forgot to check the versions and the boot.img was version 1.5.3 and my phone was already running newest 1.5.4
fastboot is still totally fine and I can use every command
I cant access the recovery. When I do fastboot reboot recovery it just gets back into bootloop
I thought okay it shouldnt be that hard to flash the stock image but I was so wrong.
Everytime I try to flash something it says "fastboot: error: cannot load '.\images\boot.img': No such file or directory"
and I really dont know how to correct that.
Read something about fastbootd but when I do "fastboot reboot fastboot" it gets back into a bootloop"
I would really appreciate help, since I need this phone for work in some time and of course would reward i anyone can help me.
ps yeah I know it was stupid to do this on my future work phone but I really thought I knew what I was doing
the complete output I get from the phone 1 tool by sh4tteredd is in the screenshots since I dont know how to extract it as a text
but I think the main problem is that it always says "No such file or directory"
also!: it also says "No such file or directory" when I try to manually flash command by command or a "Flash_all.bat"

Try to Flash the stock 1.5.4 stock boot image.... from fastboot... and let me know what happened.. this link might be help you https://forum.xda-developers.com/t/nothing-phone-1-rom-ota-nothing-os-repo-of-nothing-os.4464039/

Make sure use Android Platforms 33.0.3 since the latest verson is riddled with bugs.

soltion:
honestly idk, but i tried flashing an very old stock rom (from when roms were still split and i think I even used the wrong one) but that seemed to brake the system so hard that i eventually was able to just flash the newest stock rom and even root it with a patched file I found online (this time the right verion of course haha)