Related
ZE551ml "continue the fastboot process" prompt in fastboot,can't boot into recovery
I tried to go back to stock rom from CM 14.1 Unofficial following this youtube tutorial : https://www.youtube.com/watch?v=inzG5MLS2y4
I downloaded 2.20.40.196(Latest Android L) but couldn't find appropriate recovery for it.So I searched xda and got one.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post.
Should use Asus flash tool. http://forum.xda-developers.com/showthread.php?t=3452082
Sent from my Zenfone 2 using Tapatalk
debopriyobasu said:
I tried to go back to stock rom from CM 14.1 Unofficial following this youtube tutorial : https://www.youtube.com/watch?v=inzG5MLS2y4
I downloaded 2.20.40.196(Latest Android L) but couldn't find appropriate recovery for it.So I searched xda and got one.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B72QQTXqZSRwcXlwS0s5emlaOVk
down load zip file and extract it. place extracted files in adb fastboot tool folder. in empty place right click and open command window here. now run the following commands
fastboot flash splashscreen black_splashscreen_551.img
fastboot flash token bom-token_ze551ml_2.20.40.184.bin
fastboot flash dnx dnx_ze551ml_2.20.40.184.bin
fastboot flash ifwi ifwi_ze551ml_2.20.40.184.bin
fastboot flash fastboot droidboot_2.20.40.184.img
fastboot reboot-bootloader
after it reboots to boot loader run the following command
fastboot flash recovery recovery_sign.bin for stock recovery
or
fastboot flash recovery TWRP-3.0.2-Z00A.img for TWRP
after flash now use volume key to navigate options at top of the screen and select recovery mode and reboot to enter recovery mode. ( you may see android logo with error. When you see that screen. Press and hold power button then click volume up of down button and release both button)
now you can update stock via adb sideload
sukhwant717 said:
https://drive.google.com/open?id=0B72QQTXqZSRwcXlwS0s5emlaOVk
down load zip file and extract it. place extracted files in adb fastboot tool folder. in empty place right click and open command window here. now run the following commands
fastboot flash splashscreen black_splashscreen_551.img
fastboot flash token bom-token_ze551ml_2.20.40.184.bin
fastboot flash dnx dnx_ze551ml_2.20.40.184.bin
fastboot flash ifwi ifwi_ze551ml_2.20.40.184.bin
fastboot flash fastboot droidboot_2.20.40.184.img
fastboot reboot-bootloader
after it reboots to boot loader run the following command
fastboot flash recovery recovery_sign.bin for stock recovery
or
fastboot flash recovery TWRP-3.0.2-Z00A.img for TWRP
after flash now use volume key to navigate options at top of the screen and select recovery mode and reboot to enter recovery mode. ( you may see android logo with error. When you see that screen. Press and hold power button then click volume up of down button and release both button)
now you can update stock via adb sideload
Click to expand...
Click to collapse
Why go through all of this when you can just use the flash tool and reboot into stock?
Sent from my Zenfone 2 using Tapatalk
kenbo111 said:
Why go through all of this when you can just use the flash tool and reboot into stock?
Sent from my Zenfone 2 using Tapatalk
Click to expand...
Click to collapse
cool down buddy. it was for informational purpose only. he was already using commands to do so. i just told him the correct way.
second for using AFT he have to download raw firmware. which is more than 1 Gb of data which will be costly if he is using mobile data to download. as he mentioned he already downloaded LP firmware from asus. with above method. he will be able to install the earlier downloaded zip file without any additional firmware download.
third as he mentioned he was on CM. i doubt installation with AFT might not be successful. he may have to flash stock ifwi and recovery and boot etc...
sukhwant717 said:
cool down buddy. it was for informational purpose only. he was already using commands to do so. i just told him the correct way.
second for using AFT he have to download raw firmware. which is more than 1 Gb of data which will be costly if he is using mobile data to download. as he mentioned he already downloaded LP firmware from asus. with above method. he will be able to install the earlier downloaded zip file without any additional firmware download.
third as he mentioned he was on CM. i doubt installation with AFT might not be successful. he may have to flash stock ifwi and recovery and boot etc...
Click to expand...
Click to collapse
It was just a question.
Sent from my Zenfone 2 using Tapatalk
I can't thank you how much you helped me!!! I just recovered my half-dead phone!!!
You are awesome man! Thanks a lot! My device is alive again and can boot into recovery! I'm adb sideloading now
debopriyobasu said:
I can't thank you how much you helped me!!! I just recovered my half-dead phone!!!
You are awesome man! Thanks a lot! My device is alive again and can boot into recovery! I'm adb sideloading now
Click to expand...
Click to collapse
Good to know that was helpful.
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (WARNING : According to 5m4r7ph0n36uru, you can't flash vbmeta via fastboot if your device isn't S-OFF, you have to use TWRP, but I don't know how, so ask someone who knows! I will update my tutorial once I see instructions.)
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello, which GSI did you tried from the list? If you tried more then one, which is the one that runs better?
Thank you
Hi!
I have tried AOSP 10.0 v206 system-quack-arm64-ab-gapps.img. v208 is out now.
I still have to try others.
Let us know if you find one working better than others!
i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.
mientus25 said:
i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.
Click to expand...
Click to collapse
Hi mientus25! I'm sorry if you bricked your smartphone trying to flash it. I think the --disable-verity option not working was a matter of platform tools (adb) version.
My htc have actually hard brick. I will try to send it to the service(warranty). Will tell you what comes of it.
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked
xreeman said:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked
Click to expand...
Click to collapse
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.
5m4r7ph0n36uru said:
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.
Click to expand...
Click to collapse
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much
GaetanoS.89 said:
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much
Click to expand...
Click to collapse
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.
5m4r7ph0n36uru said:
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.
Click to expand...
Click to collapse
All right, would you please write a message over with all the steps here? Thank you
GaetanoS.89 said:
All right, would you please write a message over with all the steps here? Thank you
Click to expand...
Click to collapse
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Code:
adb reboot bootloader
Delete the system and data partition by
Code:
fastboot erase data
and
Code:
fastboot erase system
Flash the nonverity vbmeta image via
Code:
fastboot flash vbmeta nameofvbmeta.img
(the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via
Code:
fastboot flasch system nameofgsi.img
(the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu
https://www.xda-developers.com/goog...al&utm_source=twitter.com&utm_campaign=buffer
Wiil this work with the U12+???
It may work for GSIs with a fixed verity status. Thus it doesn't work for some Android 10 GSIs without flashing a noverity vbmeta as. Thus I decided long ago, to never recommend such tools, and not to help people who used one, as those using such tools most of the time didn't even care learn the basics of adb and fastboot. I can't remember anyone, who used a tool, who's ever been fully capable to identify potential problems and errors, let alone how to solve them. And the latter is the baseline to start modding a device.
Sent from my Pixel 4 XL using XDA Labs
5m4r7ph0n36uru said:
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Delete the system and data partition by and
Flash the nonverity vbmeta image via (the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via (the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu
Click to expand...
Click to collapse
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?
Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello I am trying to follow all the steps on the guode, but when I have to flash the vbmeta file from Bootloader Mode I am getting this:
C:\Users\User\Desktop\ADB2>fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Not allowed on PRODUCTION device')
fastboot: error: Command failed
If I try to install the vbmeta from Download Mode I am getting this error
GaetanoS.89 said:
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?
Click to expand...
Click to collapse
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.
5m4r7ph0n36uru said:
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.
Click to expand...
Click to collapse
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?
GaetanoS.89 said:
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?
Click to expand...
Click to collapse
Which software version are you running!?
Sent from my Pixel 4 XL using XDA Labs
5m4r7ph0n36uru said:
Which software version are you running!?
Click to expand...
Click to collapse
I was running Android 9 stock. After a few trials I have been able to install and boot the Pixel Experience and the permessiver and everything seems to work without flashing the vbmeta file
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9)
Requirements:
* Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and fastbootd.
* LMSA. You can get full ROM matched with your phone build number as well as required drivers
Working USB cable. Except you want to backup, restore, or rescue, close LMSA after ROM downloaded
* ADB debug is on and your host computer is trusted
* Your phone should be at least 60% battery. Manual flashing can take time
Are you ready?
1. Your phone should be in bootloader mode. Turn your phone off. Press and hold volume down and turn it on. You should see bootloader screen. Connect your phone to host computer.
2. Open LMSA and enter rescue in order to get full ROM. Go to the downloaded folder and go to ROM file. Watch the progress if you want to grab zip files. Copy it to somewhere you know. The zip file will be removed after unpacked by LMSA. However, all files you need are in the unzipped folder
3. Open command window and go to adb folder
4. Flash the following in bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash radio radio.img
fastboot flash logo logo.bin
5. Now toggle to fastbootd
Code:
fastboot reboot fastboot
6. Flash the following
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash super super.img.sparsechunk.x
All sparsechunk must be flashed by numeric order from zero
7. Toggle back to bootloader. Do the following:
Code:
fastboot reboot bootloader
fastboot erase carrier
fastboot erase ddr
(Optional except you want to wipe) fastboot erase userdata
8. Flash patched boot to root
Code:
adb reboot fastboot
fastboot flash boot patched_boot.img
fastboot reboot
That's it. Make sure you check Magisk Manager to check for hide as well as systemless host
i cant seem to toggle to fastbootd. when i put in the code i get the really long list of codes. And if i go into recovery and use power+vol up to get to fastbootd that way, if i try to flash anything, it fails and says no file or directory found
ok so my first root. took awhile, didnt know where to get the patched boot.img. figured it out though. thanks, it was simple
babyj3sus said:
ok so my first root. took awhile, didnt know where to get the patched boot.img. figured it out though. thanks, it was simple
Click to expand...
Click to collapse
Where? Or it becomes clear as-you-go ?
mingkee said:
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9)
Requirements:
* Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and fastbootd.
* LMSA. You can get full ROM matched with your phone build number as well as required drivers
Working USB cable. Except you want to backup, restore, or rescue, close LMSA after ROM downloaded
* ADB debug is on and your host computer is trusted
* Your phone should be at least 60% battery. Manual flashing can take time
Are you ready?
1. Your phone should be in bootloader mode. Turn your phone off. Press and hold volume down and turn it on. You should see bootloader screen. Connect your phone to host computer.
2. Open LMSA and enter rescue in order to get full ROM. Go to the downloaded folder and go to ROM file. Watch the progress if you want to grab zip files. Copy it to somewhere you know. The zip file will be removed after unpacked by LMSA. However, all files you need are in the unzipped folder
3. Open command window and go to adb folder
4. Flash the following in bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash radio radio.img
fastboot flash logo logo.bin
5. Now toggle to fastbootd
Code:
fastboot reboot fastboot
6. Flash the following
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash super super.img.sparsechunk.x
All sparsechunk must be flashed by numeric order from zero
7. Toggle back to bootloader. Do the following:
Code:
fastboot reboot bootloader
fastboot erase carrier
fastboot erase ddr
(Optional except you want to wipe) fastboot erase userdata
8. Flash patched boot to root
Code:
adb reboot fastboot
fastboot flash boot patched_boot.img
fastboot reboot
That's it. Make sure you check Magisk Manager to check for hide as well as systemless host
Click to expand...
Click to collapse
is there an way without using LMSA, i cant download it cus i have linux
When flashing patched_boot.img I get this
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.420s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.428s
I'm not new to rooting i'm familiar with rooting Motorola phones... I just can not figure out what I'm doing wrong. Please any help would be amazing.
NEVERMIND i figured it out lol
In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.
In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.
abgrady said:
In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.
Click to expand...
Click to collapse
Yes, same here. What's the point to post incomplete guide? It just creates more problems for those, who don't know what he's doing.
I've rooted various phones in the past, each model is a different process, so complete and exact guide is a must. I guess this guide is missing Magisk part, which could be found somewhere. But isn't it to hard to put everything in one place?
I bought a g power a month after you wrote this guide - and I used this guide one time, thanks for that. I do it a little differently.
Flashing this phone is pretty easy, like walking in a straight line easy. Rooting is just as easy. Your vendor doesn't want you to do any of this. All vendors are different. They have their tricks and whatnot and in the game, those tricks must be found and gotten around. Thanks to those digging around....making things possible.
Why are yo flashing your phone? It's already got an OS, firmware. It's already doing what it does and it's what you bought. Aren't you happy? For fuk's sakes, Karen, you bought it!
There are reasons to flash your device. You might think - I'm just buying the hardware, and, that's cool. I get it, I do it...
Go get the firmware - lolinet. Find it - know what you are looking for. Don't brick your phone. Nobody is twisting your arm to do this.... Seriously, look in your settings - about phone - know what you are doing. Now, go get your firmware. Have you enabled developer mode? Debugging....
This guide is for Linux people.
Fire-up a terminal
sudo apt-get install android-tools-adb android-tools-fastboot
Reboot your phone to bootloader and plug your phone into your computer.
IN your terminal cd into the extracted firmware directory, run:
Code:
fastboot devices
You see a number returned? Good, proceed.
Let's put a copy of the boot.img into an archive right now because magisk will need it later (to spit a file out that you won't be able to find....baaaa ha ha haaaaa).
Code:
tar -cvf bootimg.tar boot.img
Flash it....run each line, or, make a script:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0 && fastboot flash super super.img_sparsechunk.1 && fastboot flash super super.img_sparsechunk.2 && fastboot flash super super.img_sparsechunk.3 && fastboot flash super super.img_sparsechunk.4 && fastboot flash super super.img_sparsechunk.5 && fastboot flash super super.img_sparsechunk.6 && fastboot flash super super.img_sparsechunk.7 && fastboot flash super super.img_sparsechunk.8 && fastboot flash super super.img_sparsechunk.9 && fastboot flash super super.img_sparsechunk.10 && fastboot flash super super.img_sparsechunk.11 && fastboot flash super super.img_sparsechunk.12 && fastboot flash super super.img_sparsechunk.13 && fastboot flash super super.img_sparsechunk.14 && fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Your phone will reboot into initial setup. Set it up. Cool, have fun with your phone, I guess. If you want root, read on. Don't take the 11 update. Sheesh! EDIT: I flashed my g power, stock 10, took the update, it's on 11 now. I rooted it, no sweat, lolinet has the firmware. Once you go root, there's no more taking updates - be cool with that, or, find a way.
Stop.
Do you really want root? Why are you rooting? For viper? Pffft. Rooting has trade-offs and you don't get to ***** about it later, fool; ain't nobody twisting your arm. You really want to root, 'cause you're ready.
Root is a sexy-fine chunk of plump lovin', awwwww, man. Just back it up one time, oh yeah, that's right.....but, **** comes out of it! Big smile, high-five. Welcome to the show.
That's right. THat's root. There's risk. You want root? Because the phone isn't yours until you have it. In fact it's actively working against you until you do. Let's go ahead and get root. You can handle a little ****, right? I mean, potentially.
Copy that bootimg.tar archive you made earlier onto your phone. Go get the magisk apk and install it.
Go enable developer mode on your phone. Enable usb debugging.
In magisk -
top section, top choice - touch the word: install. Touch it! Choose: select and patch file. Obviously.
Now is when you need that archive - you just copied it onto your phone, show magisk where it is.
Magisk will output a new boot image so you can root. Wicked. Go find it on your phone - it's not hiding. Where do apps put data on your phone? Copy that file to your computer.
Now - in orter to flash this new boot image file to your phone you must be in fastbootd. Take a breath. Reboot your phone into the stock recovery - just hold down power and voldwn for about 11 seconds - you should be at 'start'. Go into recovery.
Stock recovery is a barren wasteland of nothing - right on, let's go into fastbootd.
hold down the power button for 3 seconds, one onethousand, two one thousand....after 3 one thousand press the volup key as well - keep holding the power button down. after 5 one thousand, release the buttons. You should see a new menu. IF you don't, repeat the process until you do. THis is how, get it to work.
In the menu, voldwn to enter fastboot. It does not say fastbootd, but, it is. Choose it, and voila - you are now in fastbootd and in this screen it tells you as much.
ON your computer flash the new boot image:
Code:
fastboot flash boot NEWIMAGE.IMG
After, type:
Code:
fastboot reboot
When your phone boots up, it may loop for a few minutes or loop at the next reboot - go finish setting up magisk.
You are rooted.
Lemme ask you something - why are you rooting stock? If you want root then you want control - if you want control you know you aren't going to get it from stock - there's a ton of stuff going on there. Why not install a custom rom? Just food for thought. I root stock on my g power and run lineage on my edge, also rooted. I don't normally use my g power, though.
I hope my biting cynicism and step-by-step account of flashing firmware and rooting your shiny new g power is helpful. I'm not your dad - I could care less if you brick your phone. Don't cry to me if it doesn't work, because this does. It's a flick of the wrist, but, it's not for everybody. It's especially not for people, maybe like you, that hear a new thing and wanna jump right on it. Nobody in the world cares at all if you break your phone. Nobody is forcing you to do this, nobody forced you to buy this phone, to step left instead of right, to like red better than blue - it's all you. Own that because it's beautiful.
bronkish said:
I bought a g power a month after you wrote this guide - and I used this guide one time, thanks for that. I do it a little differently.
Flashing this phone is pretty easy, like walking in a straight line easy. Rooting is just as easy. Your vendor doesn't want you to do any of this. All vendors are different. They have their tricks and whatnot and in the game, those tricks must be found and gotten around. Thanks to those digging around....making things possible.
Why are yo flashing your phone? It's already got an OS, firmware. It's already doing what it does and it's what you bought. Aren't you happy? For fuk's sakes, Karen, you bought it!
There are reasons to flash your device. You might think - I'm just buying the hardware, and, that's cool. I get it, I do it...
Go get the firmware - lolinet. Find it - know what you are looking for. Don't brick your phone. Nobody is twisting your arm to do this.... Seriously, look in your settings - about phone - know what you are doing. Now, go get your firmware. Have you enabled developer mode? Debugging....
This guide is for Linux people.
Fire-up a terminal
sudo apt-get install android-tools-adb android-tools-fastboot
Reboot your phone to bootloader and plug your phone into your computer.
IN your terminal cd into the extracted firmware directory, run:
Code:
fastboot devices
You see a number returned? Good, proceed.
Let's put a copy of the boot.img into an archive right now because magisk will need it later (to spit a file out that you won't be able to find....baaaa ha ha haaaaa).
Code:
tar -cvf bootimg.tar boot.img
Flash it....run each line, or, make a script:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0 && fastboot flash super super.img_sparsechunk.1 && fastboot flash super super.img_sparsechunk.2 && fastboot flash super super.img_sparsechunk.3 && fastboot flash super super.img_sparsechunk.4 && fastboot flash super super.img_sparsechunk.5 && fastboot flash super super.img_sparsechunk.6 && fastboot flash super super.img_sparsechunk.7 && fastboot flash super super.img_sparsechunk.8 && fastboot flash super super.img_sparsechunk.9 && fastboot flash super super.img_sparsechunk.10 && fastboot flash super super.img_sparsechunk.11 && fastboot flash super super.img_sparsechunk.12 && fastboot flash super super.img_sparsechunk.13 && fastboot flash super super.img_sparsechunk.14 && fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Your phone will reboot into initial setup. Set it up. Cool, have fun with your phone, I guess. If you want root, read on. Don't take the 11 update. Sheesh!
Stop.
Do you really want root? Why are you rooting? For viper? Pffft. Rooting has trade-offs and you don't get to ***** about it later, fool; ain't nobody twisting your arm. You really want to root, 'cause you're ready.
Root is a sexy-fine chunk of plump lovin', awwwww, man. Just back it up one time, oh yeah, that's right.....but, **** comes out of it! Big smile, high-five. Welcome to the show.
That's right. THat's root. There's risk. You want root? Because the phone isn't yours until you have it. In fact it's actively working against you until you do. Let's go ahead and get root. You can handle a little ****, right? I mean, potentially.
Copy that bootimg.tar archive you made earlier onto your phone. Go get the magisk apk and install it.
Go enable developer mode on your phone. Enable usb debugging.
In magisk -
top section, top choice - touch the word: install. Touch it! Choose: select and patch file. Obviously.
Now is when you need that archive - you just copied it onto your phone, show magisk where it is.
Magisk will output a new boot image so you can root. Wicked. Go find it on your phone - it's not hiding. Where do apps put data on your phone? Copy that file to your computer.
Now - in orter to flash this new boot image file to your phone you must be in fastbootd. Take a breath. Reboot your phone into the stock recovery - just hold down power and voldwn for about 11 seconds - you should be at 'start'. Go into recovery.
Stock recovery is a barren wasteland of nothing - right on, let's go into fastbootd.
hold down the power button for 3 seconds, one onethousand, two one thousand....after 3 one thousand press the volup key as well - keep holding the power button down. after 5 one thousand, release the buttons. You should see a new menu. IF you don't, repeat the process until you do. THis is how, get it to work.
In the menu, voldwn to enter fastboot. It does not say fastbootd, but, it is. Choose it, and voila - you are now in fastbootd and in this screen it tells you as much.
ON your computer flash the new boot image:
Code:
fastboot flash boot NEWIMAGE.IMG
After, type:
Code:
fastboot reboot
When your phone boots up, it may loop for a few minutes or loop at the next reboot - go finish setting up magisk.
You are rooted.
Lemme ask you something - why are you rooting stock? If you want root then you want control - if you want control you know you aren't going to get it from stock - there's a ton of stuff going on there. Why not install a custom rom? Just food for thought. I root stock on my g power and run lineage on my edge, also rooted. I don't normally use my g power, though.
I hope my biting cynicism and step-by-step account of flashing firmware and rooting your shiny new g power is helpful. I'm not your dad - I could care less if you brick your phone. Don't cry to me if it doesn't work, because this does. It's a flick of the wrist, but, it's not for everybody. It's especially not for people, maybe like you, that hear a new thing and wanna jump right on it. Nobody in the world cares at all if you break your phone. Nobody is forcing you to do this, nobody forced you to buy this phone, to step left instead of right, to like red better than blue - it's all you. Own that because it's beautiful.
Click to expand...
Click to collapse
How about flashing it upgraded to Android 11?
When the 11 firmware becomes available I'll do the exact same thing. Wouldn't you?
What I meant is: how is flashing LineageOS 17 on Moto G8 Power which was upgraded to Android 11. The guide states it works for Android 10. If downgrade from 11 to 10 is a must, in order to successfully flashing LO17 then what's the best way of doing it? LMSA only downloads the latest version of Android.
alpheus said:
What I meant is: how is flashing LineageOS 17 on Moto G8 Power which was upgraded to Android 11. The guide states it works for Android 10. If downgrade from 11 to 10 is a must, in order to successfully flashing LO17 then what's the best way of doing it? LMSA only downloads the latest version of Android.
Click to expand...
Click to collapse
OK, so, this is my 5th or so edit. Heh. You took the update to 11 and now you want lineageos? Right on, Lineage lets you breathe a little easier, sho' nuff. This phone is probably not popular enough for 18.1 to ever see it, which is built on android 11. Back when android 7 came out, on my phone then, it was a new modem and that changed all the things. It was a pain in the ass to go back to 6 and 7 with custom roms was a matter of either having your cake or eating it, too. And right now you're at 11 wanting that sweet sweet Lineage....I get it.
I might just root 11 and see what I could do with it afore I flashed 10 back onto it. That's me, I like to tinker, and can be ok with a decision, because old and no fuks...You might be in a hurry, I dunno...root it. get with sd maid and appmanager, a firewall, do your thing...fx for a file manager is mui bueno - you can do a lot with root to the stock rom motorola gives you - still, there's a ton of google all over it, even after shutting things down, removing, blocking, et al...
Flash 10 - go ahead. Do it. DO it now. Flash 10 and then do the lineage thing, I hear you. Go get and do it. It won't take long and you'll be happy. Rock on. Sure, I would do it. Why the hell not?
nevermind
bronkish said:
OK, so, this is my 5th or so edit. Heh. You took the update to 11 and now you want lineageos? Right on, Lineage lets you breathe a little easier, sho' nuff. This phone is probably not popular enough for 18.1 to ever see it, which is built on android 11. Back when android 7 came out, on my phone then, it was a new modem and that changed all the things. It was a pain in the ass to go back to 6 and 7 with custom roms was a matter of either having your cake or eating it, too. And right now you're at 11 wanting that sweet sweet Lineage....I get it.
I might just root 11 and see what I could do with it afore I flashed 10 back onto it. That's me, I like to tinker, and can be ok with a decision, because old and no fuks...You might be in a hurry, I dunno...root it. get with sd maid and appmanager, a firewall, do your thing...fx for a file manager is mui bueno - you can do a lot with root to the stock rom motorola gives you - still, there's a ton of google all over it, even after shutting things down, removing, blocking, et al...
Flash 10 - go ahead. Do it. DO it now. Flash 10 and then do the lineage thing, I hear you. Go get and do it. It won't take long and you'll be happy. Rock on. Sure, I would do it. Why the hell not?
Click to expand...
Click to collapse
Hey, thanks for the reply. Yes, rooting G Power is not my interest, Id rather flash LineageOS without any Gapps and fu....g shmuggle. Would you please point out the best way to flash previous Stock 10 on G Power with current 11 installed? The phone was upgraded to 11 when I got it.
See post #10. Just flash 10 ☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠, and then flash lineage 17.1. DOn't forget to flash copy-partitions before lineage. You gotta do it the 1st time you flash a custom rom over stock.
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
Lineage is not official for this phone.
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
Hello guys does anyone know how I can get back to stock??? It seems whenever I reboot I keep getting bootloader with the dead android. I tried connecting my device to my laptop and using LMSA. I get a message saying the firmware doesn't match even though I input the right IMEI. Even after putting in the correct model of the phone. Any solution? I would really love to go back to stock. Thanks guys
Mkami said:
Hello guys does anyone know how I can get back to stock??? It seems whenever I reboot I keep getting bootloader with the dead android. I tried connecting my device to my laptop and using LMSA. I get a message saying the firmware doesn't match even though I input the right IMEI. Even after putting in the correct model of the phone. Any solution? I would really love to go back to stock. Thanks guys
Click to expand...
Click to collapse
Is your bootloader unlocked?
You can download the stock firmware from: https://mirrors.lolinet.com/firmware/moto/
Once you've downloaded the files you need just install them using ADB Platform Tools on Windows: https://developer.android.com/studio/releases/platform-tools
Also, if you can't even get it to boot to unlock the bootloader then I would download the firmware from the above lolinet site and then transfer the folder into LMSA on Windows under this path:
C:\ProgramData\LMSA\Download\RomFiles
You'll need to enable hidden items under the view tab in File explorer
Once you've moved the correct firmware into the RomFiles folder then go back to LMSA and have it check for the firmware and it will recognize the firmware you moved into RomFiles.
shylonite said:
Is your bootloader unlocked?
You can download the stock firmware from: https://mirrors.lolinet.com/firmware/moto/
Once you've downloaded the files you need just install them using ADB Platform Tools on Windows: https://developer.android.com/studio/releases/platform-tools
Also, if you can't even get it to boot to unlock the bootloader then I would download the firmware from the above lolinet site and then transfer the folder into LMSA on Windows under this path:
C:\ProgramData\LMSA\Download\RomFiles
You'll need to enable hidden items under the view tab in File explorer
Once you've moved the correct firmware into the RomFiles folder then go back to LMSA and have it check for the firmware and it will recognize the firmware you moved into RomFiles.
Click to expand...
Click to collapse
Thanks so much for your information! My phone is back to its originally stock and working 100%
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Windwell said:
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Click to expand...
Click to collapse
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
Hey mate,
Thanks for responding. Sorry for the late reply.
From what you had suggested, I did "fastboot --set-active=a" , "fastboot flash boot boot.img", and "fastboot reboot" (with the stock unpatched boot.img) the commands were successful once again, but there were no effective changes.
Afterwards, I did "fastboot --setactive-b", "fastboot flash boot boot.img", and "fastboot reboot" the commands were successful once more, and this time, I was finally able to go into recovery mode. On the other hand, in recovery mode I wiped the cache and erased everything, but unfortuantely I still could not boot into Android, even though I tried to flash boot the image once more.
Thank you for these commands, as I was at least able to recover recovery mode.
Any other suggestions maybe?
Hello,
Use this tool and it will fix it, I had the same problem. Just download the software and flash it in Qualcomm EDL mode.
MSMDownload image needed
Hello guys, I managed to flash the wrong image to OnePlus NORD N100 BE2013, I overlooked for the first time what I'm doing and messed it up Now it's in Qualcomm EDL mode and I need and image to flash it to bring it back do life, anyone I can...
forum.xda-developers.com
I alsp posted boot.img which is compatible you can flash it. Link is in the comments.
Thanks
Boot.img from nord n100 in this thread, I exctracted and rooted it myself.
I WHANT RECOVERY Boot.img FOR ROOT MY ONEPLUS NORD N100
I unlock bootloader and i whant to root with magisk my phone, i need boot.img for rocovery..I try anather boot.img from One plus nord, etc, i sucessfull flash this recovery's with command in windows but is no go in recovery, stay in bootloop..Can...
forum.xda-developers.com
Hello,
I used the tool MSMDownload but unfortunately I was unable at all to boot into Qualcomm Edl mode, even though I have installed correctly all the drivers for Windows Qualcomm, and OnePlus USB drivers, and used the correct method (Volume Button UP and Down at the same time whilst connecting the phone via USB). I tried flash booting with the boot.img you gave me, but still no changes. I am still stuck in Fastboot.
If you had encountered the same issue back then, can you tell me the excat procedure you did please?
Thank you so much.
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
oh
thts ok man
بلوک سبک
I will try to make a fastboot image for OnePlus NORD N100 BE2013 with 10.5.5 and upload it to mega, I'll send you the link. If you are in fastboot mode you will be able to flash it I believe, let me have a look.
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
motovnet said:
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
Click to expand...
Click to collapse
For some reason Qualcomm Mode Edl does not launch whatsoever.
motovnet said:
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
Click to expand...
Click to collapse
Thank you that's very kind of you. I think the only way to fix it by flash boot.img, but I have doubts because it does not work.
The only commands I am doing are "fastboot devices", "fastboot flash boot boot.img"
With the fastboot image you will be able to flash everything, it contains not only boot.img but system and etc. I managed to boot mine and bring it back to life by reflashing everyhing.
So the only thing I need to do is "fastboot flash boot ''.img" right?
Where can I get all the nesscary files?
And how did you manage to root it?
The fastboot image flashes all partitions, not just boot with stock Oxygen OS 10.5.5
What you need to do is run flash-all.bat from the archive and it will flash the entire os not just boot.img.
If you can't get to EDL mode, fastboot flash is the only solution. What model does it say in the back? This one was EUROPE BE2013.
Is your EU or Global device?
Archive is uploading still.
Thanks
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
2.55 GB file on MEGA
mega.nz
This is a fastboot image for OnePlus NORD N100 EU BE2013 device.
Extract it to a new folder, it contains fastboot in it.
Right click flash-all.bat and run as admin.
You can open the flash-all.bat file with notepad to check yourself there is nothing strange in it. I used a bat file from the forum that was fastboot image for OnePlus NORD and changed it to use the .img files for OnePlus NORD N100.
Contains Oxygen 10.5.5, once you bring it back to life (IF YOU HAVE THIS MODEL), you can use magisk to patch the boot.img and flash it via fastboot.
This is how I rooted it and it worked properly.
Please use it with caution and ensure your model matches! I can not guarantee it will work on other devices.
If you can't go to EDL mode, this is your way to go, but I don't know if flashing GLOBAL version will work.
Thanks
Windwell said:
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
Click to expand...
Click to collapse
I would guess BE2013 is the EU one, as this worked on mine.
motovnet said:
I would guess BE2013 is the EU one, as this worked on mine.
Click to expand...
Click to collapse
Okay thank you for helping me. I will try this later and keep you in touch.
Windwell said:
Okay thank you for helping me. I will try this later and keep you in touch.
Click to expand...
Click to collapse
Thanks, let me know if it works for you. If you're unable to flash it via fastboot, only EDL will help.
I installed Linux by a mistake into my Nokia 3.2 which led me here, I am stuck in fast boot mode I tried multiple solutions like scratching the edl trigger, going to recovery mode, and restarting the bootloader. it only vibrates and reopens the fastboot menu, I cannot install, or perhaps I don't know how to install the default OS, IMG, or whatever you call it I am really new to this kinda stuff, sorry, and I appreciate your help.
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
MRza3ter said:
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
Click to expand...
Click to collapse
to download the stock ROM just search Nokia 3.2 stock rom