Just got this phone today so I could boot lineage to it. Everything was running alright till I tried to boot into recovery mode. I flashed my image after I unlocked the phone officially and now it's just stuck at the stock Motorola Logo.
yarlio:[root]:/home/yerm/Documents/Moto G100# fastboot flash boot lineage-19.1-20220427-recovery-nio.img
Sending 'boot_b' (98304 KB) OKAY [ 3.076s]
Writing 'boot_b' OKAY [ 2.074s]
Finished. Total time: 5.190s
Click to expand...
Click to collapse
Worried about a optential hard brick here because I can't copy ensure all my firmware partitions are consistent
yarlio:[root]:/home/yerm/Documents/Moto G100# adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
Click to expand...
Click to collapse
It automatically writes to boot_b and I don't know if that'll be a issue
Here are all the files I have
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here is the site I used: https://lineageosroms.com/nio/ It doesn't come with twrp so I am just kinda stuck using a linux terminal and the bootloader
Did you Enable ADB in Advanced menu?
If yes, you probably didn't choose 2nd option in LineageOS recovery ...?
IntinteDAO said:
Did you Enable ADB in Advanced menu?
Click to expand...
Click to collapse
I am not getting in prompts to do so on the device. Just: Start, Barcodes, Bootloader Logs, Power Off, Recovery Mode, and restart bootloader. Going into recovery gives me nothing but the blue moto screen.
yerm said:
I am not getting in prompts to do so on the device. Just: Start, Barcodes, Bootloader Logs, Power Off, Recovery Mode, and restart bootloader. Going into recovery gives me nothing but the blue moto screen.
Click to expand...
Click to collapse
Try the newest version of Recovery
https://mirrorbits.lineageos.org/recovery/nio/20220604/lineage-19.1-20220604-recovery-nio.img
So, when doing this, the most important thing is having a way to revert to stock everything, far more so than backing up. This usually consists of a "fastboot ROM" of your stock software on the offchance something does tits up. Check development to see if one for your model number is available.
A issue I see immediately is you flashed the recovery using the flash boot command, when the instructions say temp boot using the boot command. Always stick to the instructions for that particular thing you're doing to the letter, otherwise you might get lucky or you'll get a weird oddity that is difficult to troubleshoot.
The instructions say to temp boot, use the copy partitions script to but it on both slots, and then install lineage. Given there is no mention of a recovery zip getting lineage recovery permanent is just done by flashing the ROM. So if you can I'd revert everything back to stock if that's a thing on this device, then do the steps again.
loulondono said:
So, when doing this, the most important thing is having a way to revert to stock everything, far more so than backing up. This usually consists of a "fastboot ROM" of your stock software on the offchance something does tits up. Check development to see if one for your model number is available.
A issue I see immediately is you flashed the recovery using the flash boot command, when the instructions say temp boot using the boot command. Always stick to the instructions for that particular thing you're doing to the letter, otherwise you might get lucky or you'll get a weird oddity that is difficult to troubleshoot.
The instructions say to temp boot, use the copy partitions script to but it on both slots, and then install lineage. Given there is no mention of a recovery zip getting lineage recovery permanent is just done by flashing the ROM. So if you can I'd revert everything back to stock if that's a thing on this device, then do the steps again.
Click to expand...
Click to collapse
I figured I went wrong somewhere, mostly because I ran into this when trying to copy partitions:
debord:[yerm]:~/Documents$ adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am now worried I beat my system to death and now I can't revert any of my changes. Do You have a terminal command list to sort this out how is it something i have ot get done from the bootloader on my phone?
Also the model is a "XT2125-4" Which is a supported device according to this tutorial.
yerm said:
I figured I went wrong somewhere, mostly because I ran into this when trying to copy partitions:
debord:[yerm]:~/Documents$ adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I am now worried I beat my system to death and now I can't revert any of my changes. Do You have a terminal command list to sort this out how is it something i have ot get done from the bootloader on my phone?
Also the model is a "XT2125-4" Which is a supported device according to this tutorial.
Click to expand...
Click to collapse
Are you trying to sideload whilst in bootloader ( start, barcodes ect) or have you gotten into recovery?
loulondono said:
Are you trying to sideload whilst in bootloader ( start, barcodes ect) or have you gotten into recovery?
Click to expand...
Click to collapse
I am only able to jump between boot-loader and this powered by android Motorola screen. The only two places I can go
yerm said:
I am only able to jump between boot-loader and this powered by android Motorola screen. The only two places I can go
Click to expand...
Click to collapse
Yh sideload only works when booted into recovery, and having selected sideload ( seems to be renamed to apply update on lineage recovery) so that's a bust. You need to get into recovery. Any luck on finding a way to revert to stock? If not I would try the boot .IMG command from the instructions and see if that gets you into the recovery
loulondono said:
Yh sideload only works when booted into recovery, and having selected sideload ( seems to be renamed to apply update on lineage recovery) so that's a bust. You need to get into recovery. Any luck on finding a way to revert to stock? If not I would try the boot .IMG command from the instructions and see if that gets you into the recovery
Click to expand...
Click to collapse
No Luck, also getting this now:
debord:[yerm]:~/Documents$ fastboot flash boot lineage-19.1-20220427-nightly-nio-signed.zip
< waiting for any device >
Sending 'boot_a' (771805 KB) OKAY [ 20.216s]
Writing 'boot_a' (bootloader) Image size exceeds partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
And I had to change my device I was using to flash LineageOS. My PC kept hard crashing but that's a different issue
Start from installing recovery. Go to bootloader mode, download newest version of fastboot (31) and:
fastboot flash boot lineage-19.1-20220604-recovery-nio.img
IntinteDAO said:
Start from installing recovery. Go to bootloader mode, download newest version of fastboot (31) and:
fastboot flash boot lineage-19.1-20220604-recovery-nio.img
Click to expand...
Click to collapse
Still getting this error when I try to sideload
adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
Click to expand...
Click to collapse
I think boot_a and boot_b Might be occupied. (First attempt did b the first few times second kept flashing to a)
yerm said:
Still getting this error when I try to sideload
Click to expand...
Click to collapse
I understand that you were able to get LineageOS Recovery working?
IntinteDAO said:
I understand that you were able to get LineageOS Recovery working?
Click to expand...
Click to collapse
The img installs then I am still stuck in the Motorola powered by android when I try to get into recovery mode or restart the phone. I can only get into the standard android bootloader
To do a sideload, you must have LineageOS Recovery. I understand that your system loads over and over again?
IntinteDAO said:
To do a sideload, you must have LineageOS Recovery. I understand that your system loads over and over again?
Click to expand...
Click to collapse
Yeah It just gets stuck at the screen on recovery
yerm said:
Yeah It just gets stuck at the screen on recovery
Click to expand...
Click to collapse
When flashing recovery, does fastboot display any errors?
IntinteDAO said:
When flashing recovery, does fastboot display any errors?
Click to expand...
Click to collapse
It's been flashing fine when just flashing to boot_a
fastboot set_active a
<run recovery>
Is that works?
Related
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.
To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.
Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix
Linux_fart_18.3 said:
To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.
Click to expand...
Click to collapse
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
abasba said:
Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix
Click to expand...
Click to collapse
unfortunate for me ive tried all the above except locking bootloader before msm which i have also tried both separtatly but not in that order.
ab123pro said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command
Linux_fart_18.3 said:
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command
Click to expand...
Click to collapse
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root
ab123pro said:
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root
Click to expand...
Click to collapse
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.
Linux_fart_18.3 said:
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.
Click to expand...
Click to collapse
looks like your boot partition got corrupted some how im not sure tho
maybe try to flash one of those fastboot roms - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Hello , sorry for my bad english , i have a moto z3 play model xt1929-6 , i unlock the bootloader with program "minimal adb and fastbood", now i try to boot the img of recovery but the program say "
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.5.0_9-0-beckham.img
downloading 'boot.img'..." and stays there.. .
the command what i use is " fastboot devices----fastboot boot "boot.img or name of img".
pls help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try renaming twrp-3.5.0_9-0-beckham.img to a.img then place a.img into My Computer>Local Disk ( C: )
then type
Code:
fastboot flash boot C:\a.img
ADB hate spaces and symbol on .img files ...
ineedroot69 said:
try renaming twrp-3.5.0_9-0-beckham.img to a.img then place a.img into My Computer>Local Disk ( C: )
then type
Code:
fastboot flash boot C:\a.img
ADB hate spaces and symbol on .img files ...
Click to expand...
Click to collapse
still the problem , downloading boot.img
danilolegenda said:
still the problem , downloading boot.img
Click to expand...
Click to collapse
what error?
ineedroot69 said:
what error?
Click to expand...
Click to collapse
danilolegenda said:
View attachment 5241261
Click to expand...
Click to collapse
why you using
Code:
fastboot boot
and not
Code:
fastboot flash boot
are you trying to backup your partition before going full root??
don't do fastboot flash boot you will not have stock boot.img backup you can try
Code:
fastboot erase boot
fastboot boot a.img
ineedroot69 said:
are you trying to backup your partition before going full root?? don't do
fastboot flash boot you will not have stock boot.img backup you can try
Code:
fastboot erase boot
fastboot boot a.img
Click to expand...
Click to collapse
i try to boot the twrp for install this like a see in tutorial, try fastboot flash boot ?
i try to follow this tutorial
danilolegenda said:
i try to boot the twrp for install this like a see in tutorial, try fastboot flash boot ?
Click to expand...
Click to collapse
fastboot flash boot command is permanent (you will have permanent TWRP recovery installed on your phone)
fastboot boot command is temporary (It would just load TWRP temporary and used for mainly file recovery or backup)
it's depends on your decision
ineedroot69 said:
fastboot flash boot command is permanent (you will have permanent TWRP recovery installed on your phone)
fastboot boot command is temporary (It would just load TWRP temporary and used for mainly file recovery or backup)
it's depends on your decision
Click to expand...
Click to collapse
ahhh ok, then can I install the twrp using the img and the command "fastboot flash boot"? is it just to install the recovery? Sorry I haven't done these procedures for a long time.
that video is not full guide its does not show how to backup partition incase your phone does not boot anymore after installing TWRP ...
do you have stock rom of your phone just incase it does not boot again?
yes fastboot flash boot just make sure it's correct version of TWRP you are flashing
ineedroot69 said:
that video is not full guide its does not show how to backup partition incase your phone does not boot anymore after installing TWRP ...
do you have stock rom of your phone just incase it does not boot again?
yes fastboot flash boot just make sure it's correct version of TWRP you are flashing
Click to expand...
Click to collapse
i have a stock rom of android 9 but no have a back up of this, the file is corretly from this link "https://dl.twrp.me/beckham/twrp-3.3.1-0-beckham.img.html" I thought it was installed with the zip but in the video they show with the img.
ineedroot69 said:
that video is not full guide its does not show how to backup partition incase your phone does not boot anymore after installing TWRP ...
do you have stock rom of your phone just incase it does not boot again?
yes fastboot flash boot just make sure it's correct version of TWRP you are flashing
Click to expand...
Click to collapse
I have already tried to flash the recovery but it tells me that the file is too big to send it, the latest version of twrp weighs 33mb
danilolegenda said:
I have already tried to flash the recovery but it tells me that the file is too big to send it, the latest version of twrp weighs 33mb
Click to expand...
Click to collapse
Did it success? The biggest img file I fastboot flash is 2.4GB which is system.img. Just ignore the filesize warning
ineedroot69 said:
Did it success? The biggest img file I fastboot flash is 2.4GB which is system.img. Just ignore the filesize warning
Click to expand...
Click to collapse
i try with one command "fastboot flash recovery (and here the img file) with this say the file is so much bigger, I was scared by what you said that I could stay without starting the phone anymore D:
danilolegenda said:
i try with one command "fastboot flash recovery (and here the img file) with this say the file is so much bigger, I was scared by what you said that I could stay without starting the phone anymore D:
Click to expand...
Click to collapse
I agree with that mindset kinda risky also it's kinda terrible how to tell to your mother you broke your phone because you followed an Indian tutorial on youtube
thou like Adolf Hitler said " Your strength is only as strong as your commitment "
ineedroot69 said:
I agree with that mindset kinda risky also it's kinda terrible how to tell to your mother you broke your phone because you followed an Indian tutorial on youtube
thou like Adolf Hitler said " Your strength is only as strong as your commitment "
Click to expand...
Click to collapse
I can't agree with you so much
ineedroot69 said:
I agree with that mindset kinda risky also it's kinda terrible how to tell to your mother you broke your phone because you followed an Indian tutorial on youtube
thou like Adolf Hitler said " Your strength is only as strong as your commitment "
Click to expand...
Click to collapse
i try again but have the same problem look at this.
The problem has been solved , the problem is a windows 10 , i try with windows 7 pc and I was able to do the whole. procedure.
Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.
gokhanc5 said:
Spoiler: didnt want to clog the thread with repeats of your pics
Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.
Click to expand...
Click to collapse
id reflash the stock firmware and re-root from there should you choose to do so
Youdoofus said:
id reflash the stock firmware and re-root from there should you choose to do so
Click to expand...
Click to collapse
thank you you answered. I'm uploading boot.img and recovery.img via fastboot. it does not give an error but comes to the same screen again. where am I doing wrong. Can you tell me exactly how to do it one by one.
@gokhanc5
As I can see your phone stucks in Fastboot ( AKA Bootloader ) mode: in Android device's boot-mode is set by ro.bootmode property - what can be normal, recovery or fastboot - which is set in Android's system file named build.prop.
Simply flashing some images as you did doesn't cause this property gets reset.
Typically you reset device's boot-mode property by means of ADB and/or Fastboot commands
ADB
Code:
adb devices
adb reboot
Fastboot
Code:
fastboot devices
fastboot reboot
jwoegerbauer said:
[USER = 11583799] @ gokhanc5 [/ USER]
Telefonunuzun Fastboot (AKA Bootloader) modunda takıldığını görebildiğim gibi: Android cihazının önyükleme modu, Android'in build.prop adlı sistem dosyasında ayarlanan ro.bootmode özelliği tarafından ayarlanır - normal, kurtarma veya fastboot olabilir .
Yaptığınız gibi bazı görüntüleri basitçe yanıp sönmek, bu özelliğin sıfırlanmasına neden olmaz.
Genellikle aygıtın önyükleme modu özelliğini ADB ve / veya Fastboot komutları aracılığıyla sıfırlarsınız.
ADB
[kod]
adb cihazları
adb yeniden başlatma
[/ kod]
Fastboot
[kod]
fastboot cihazları
fastboot yeniden başlatma
[/ kod]
Click to expand...
Click to collapse
OEM lock is on.
I'm installing recovery.img in fastboot mode.
fastboot flash recovery recovery.img
then when I turn it off and on again it comes to the fast boot mode screen.
I tried all the recovery.img files.
but it didn't happen.
Fast Boot Mode screen
Start - restart booting failed
Power Of
Recovery Mode - restart booting failed
Restart bootloader - restart booting failed
Can you describe how to do it from the very beginning?
gokhanc5 said:
...
Can you describe how to do it from the very beginning?
Click to expand...
Click to collapse
Already told you what to do.
jwoegerbauer said:
Sana ne yapacağını zaten söyledim.
Click to expand...
Click to collapse
I cannot enter anywhere except fastboot.
I cannot install TWRP.
fastboot devices
fastboot reboot
I'm doing these things, nothing changes.
i'm a beginner
sorry
jwoegerbauer said:
Already told you what to do.
Click to expand...
Click to collapse
I tried what they said
usb debugging is turned off
What will I change in the build.prop file.
What should I do for ro.bootmode?
I will be glad if you answer
I tried a lot but couldn't find a solution.
my hope is you
You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.
jwoegerbauer said:
You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.
Click to expand...
Click to collapse
thank you for everything.
but I could not.
-------------------------
fastboot oem unlock
(bootloader) Bootloader is already unlocked.
OKAY [0.008s]
finished. total time: 0.008s
-----------------------------------------
fastboot devices
3CQ3400QG9 fastboot
-----------------------------------------
fastboot flash bootloader Bootloader_phobos_4.4.2.img
target reported max download size of 641728512 bytes
sending 'bootloader' (7137 KB) ...
OKAY [0.266s]
writing 'bootloader' ...
FAILED (remote: (InvalidState))
finished. total time: 0.422s
-------------------------------------------------- ------
thank you for your help
@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.
jwoegerbauer said:
@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.
Click to expand...
Click to collapse
gave the same error again.
I downloaded it from 3 different places, the same error in all of them.
fastboot flash bootloader command fails
fastboot flash boot command works but the problem is the same
I tried to install LineageOS on my OnePlus Nord following this thread:
[ROM][13][UNOFFICIAL] LineageOS 20 - microG [OnePlus Nord/avicii]
You care a lot about privacy and security? You want an up to date LineageOS build that will not hold you back in regards of user experience? Then LineageOS 20 microG edition is right for you! (Non-microG vanilla LineageOS version also available)...
forum.xda-developers.com
I successfully flashed the recovery.img (provided in the thread), and did a factory reset in recovery. However, I could not find the "Apply Update / Apply from ADB" option, so I though I'll just flash TWRP on there instead. But this bricked my phone. And I got this error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I hold vol-down + power button I was also able to reach fastboot mode.
I found MSMDownloadTool and this thread:
[OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
But whatever Firmware image I tried to use the result was always the same: "Device not match image".
(On the box that the phone came in it says "OnePlus Nord AC2003")
I tried different versions of Global, EU and India Firmware files.
I have also tried different versions of Qualcomm drivers (1.00.25 and 1.00.55)
And I have tried different cables, and USB ports.
So I tried to flash stock ROM using this thread:
[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com
It works fine in the beginning, but after the fastboot reboot fastboot step I start getting:
FAILED: Flashing is not allowed for Critical Partitions.
Also, If I do fastboot flashing unlock_critical it says the phone is already unlocked.
I have also tried fastboot boot recovery.img with different .img files (recovery.img provided in the first thread I linked, and also TWRP.img) but this just reboots the phone, and then it gets stuck at Oneplus logo reading "Fastboot Mode" below, until I restart and it gets into fastboot menu again.
I can only reach fastboot mode as shown in picture above, and EDL mode.
I have no clue on how to fix my phone. Any ideas?
Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps
sinkoo1979 said:
Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps
Click to expand...
Click to collapse
Thanks a lot for your reply!
You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.
What do you mean by change slots?
What is pronton lock off rom A13? Is it something I should use as well?
How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?
Thanks in advance!
sixtenson1 said:
Thanks a lot for your reply!
You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.
What do you mean by change slots?
What is pronton lock off rom A13? Is it something I should use as well?
How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?
Thanks in advance!
Click to expand...
Click to collapse
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.
Custom Rom
Don't know which android version you have
Use this link https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/
sinkoo1979 said:
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.
Custom Rom
Don't know which android version you have
Use this link https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/
Click to expand...
Click to collapse
Thanks for the additional information!
I started by checking what slot was in use:
fastboot getvar all
(bootloader) current-slot:a
I then changed slot to b:
fastboot --set-active=b
And then started following the link you provided.
However, running in to the same problem as before.
When running:
fastboot reboot fastboot
I get the following Error:
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And when trying to flash abl:
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot flashing unlock
fastboot flashing unlock_critical
both generate the same Error message:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
What could this be?
Thanks in advance!
sixtenson1 said:
Thanks for the additional information!
I started by checking what slot was in use:
fastboot getvar all
(bootloader) current-slot:a
I then changed slot to b:
fastboot --set-active=b
And then started following the link you provided.
However, running in to the same problem as before.
When running:
fastboot reboot fastboot
I get the following Error:
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And when trying to flash abl:
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot flashing unlock
fastboot flashing unlock_critical
both generate the same Error message:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
What could this be?
Thanks in advance!
Click to expand...
Click to collapse
Mine worked with that. Don't really know now. Hope you solve it.
sinkoo1979 said:
Mine worked with that. Don't really know now. Hope you solve it.
Click to expand...
Click to collapse
When I run:
$ fastboot oem device-info
I get the following:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Device does not seem to be critical unlocked. When I run:
$ fastboot flashing unlock_critical
Output is:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Does the device need to be critical unlocked? And if so, how can I unlock it?
I have noticed we have the same issue, easy fix !
I fixed it by following this simple guide -
* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).
* download the QUALCOMM driver(link in the YouTube video description).
* turn your phone off by pressing the power button and the + volume.
* when phone is turned off- press both volume buttons for 10 sec
* connect an original usb cable to your phone and to the 3.0 port on your pc.
* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)
* open msm tool and look if the device is recognized (COM4)
* if it is recognized change target to india and click start.
* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly
feel free to ask any questions, I know how frustrating it could be.
device used- one plus nord ac2003
ROM + MSM TOOL VERSION- avicii_14_I.13_210204
unbrickmee said:
I have noticed we have the same issue, easy fix !
I fixed it by following this simple guide -
* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).
* download the QUALCOMM driver(link in the YouTube video description).
* turn your phone off by pressing the power button and the + volume.
* when phone is turned off- press both volume buttons for 10 sec
* connect an original usb cable to your phone and to the 3.0 port on your pc.
* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)
* open msm tool and look if the device is recognized (COM4)
* if it is recognized change target to india and click start.
* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly
feel free to ask any questions, I know how frustrating it could be.
device used- one plus nord ac2003
ROM + MSM TOOL VERSION- avicii_14_I.13_210204
Click to expand...
Click to collapse
Thanks a lot for your answer!
I followed every of your steps, but I get the same result as I describe in the original post.
In MSMDownloadTool, in the "Status of Last Communication" column it says, in red:
"Device not match image".
Any idea how to fix this?
Try to reinstall correct drivers