Related
Hi all,
Looking for help because I have 2 problems I can not seem to find the solution.
The two problems are "bound" in the sense that even if I change ROM , FULL WIPE , formatting or DATA SYSTEM , with or without the GAPP , or SHIFT Kernel Boot Loader and with or without SuperSU they come back directly .
1) When I go to Settings and then click Security - > Application "Settings" stopped.
2) When I try to uninstall an app - > Reboot the phone ...
Do you know where to look ?
This happens with every ROM you have tried?
audit13 said:
This happens with every ROM you have tried?
Click to expand...
Click to collapse
Yes.
On stock or custom. Lollipop or KitKat allways same :crying:
Does this still happen after doing a full wipe using fastboot commands?
audit13 said:
Does this still happen after doing a full wipe using fastboot commands?
Click to expand...
Click to collapse
Never try this.
I have do full wipe with TWRP and format manualy.
Can you tell me the command line?
If you are using a Windows XP or 7 computer, Install the the necessary Motorola drivers, install the necessary fastboot files, boot the phone into fastboot mode, open a command prompt, type "fastboot erase cache", press enter key, type "fastboot erase userdata", press enter, type "fasboot reboot", press enter.
audit13 said:
If you are using a Windows XP or 7 computer, Install the the necessary Motorola drivers, install the necessary fastboot files, boot the phone into fastboot mode, open a command prompt, type "fastboot erase cache", press enter key, type "fastboot erase userdata", press enter, type "fasboot reboot", press enter.
Click to expand...
Click to collapse
I'm on linux.
Code:
[email protected]:~$ sudo fastboot erase cache
erasing 'cache'...
OKAY [ 0.136s]
finished. total time: 0.136s
[email protected]:~$ adb reboot bootloader
error: device not found
[email protected]:~$ sudo fastboot erase cache
erasing 'cache'...
OKAY [ 0.075s]
finished. total time: 0.075s
[email protected]:~$ sudo fastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.988s
[email protected]:~$ sudo fastboot reboot
rebooting...
finished. total time: 0.001s
Boot in process...
Was the phone encrypted?
When flashing back to stock, were you able to flash gpt.bin?
audit13 said:
Was the phone encrypted?
When flashing back to stock, were you able to flash gpt.bin?
Click to expand...
Click to collapse
Phone not booting allway on boot image with loop animation and glitch on screen.
Phone never encrypted and never flash bin separate alwway flash rom directly.
Which phone do you have?
audit13 said:
Which phone do you have?
Click to expand...
Click to collapse
Motorola Moto G 2013 One Sim
Can't mount or format /data ... Seem's not good.
Hmm, weird. Maybe flashing a ROM caused a problem some how. For me and my xt1032 8 GB phone, I have always been able to solve any problems by flashing back to stock 4.4.4.
audit13 said:
Hmm, weird. Maybe flashing a ROM caused a problem some how.
Click to expand...
Click to collapse
How solve?
In recovery i can't do anything he can't mount.
You could download the stock ROM, unzip, and manually flash each partition using fastboot commands.
audit13 said:
You could download the stock ROM, unzip, and manually flash each partition using fastboot commands.
Click to expand...
Click to collapse
Realy ? No other option???
How to do the manip ? I will try tomorow (to day is over computer, my mind will explode).
darktweek said:
Realy ? No other option???
Click to expand...
Click to collapse
There may be other options that I don't know. I just know that the easiest for me is to flash the stock ROM.
Hi !
I have redo all manualy and it's done, I have a android boot
But still have same 2 problems... Any suggestion?
UP
Allway same problem. I have try with ADB and... Reboot again... :crying:
Everytime I try to boot twrp i get this message.
PS C:\adb> fastboot boot twrp-3.3.1-4-guacamole.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.324s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.331s
I am bootloader unlocked so I dont know why I am getting that message. Any help would be appreciated. Thanks
Try "fastboot flash boot [img name]".
The correct command is
Fastboot boot [drag and drop the img]
phenomenalblaze said:
Everytime I try to boot twrp i get this message.
PS C:\adb> fastboot boot twrp-3.3.1-4-guacamole.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.324s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.331s
I am bootloader unlocked so I dont know why I am getting that message. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Are you on Beta1, if so, you can't boot into recovery that way, you need to flash recovery using Magisk first.
No I'm not. I'm on 9.5.11
phenomenalblaze said:
No I'm not. I'm on 9.5.11
Click to expand...
Click to collapse
If you have root, try flashing the recovery installer with Magisk
smo69 said:
Try "fastboot flash boot [img name]".
Click to expand...
Click to collapse
This command is useless it won't work. Download the latest oxygen OS zip(full rom package not the incremental one), place it in your internal storage and update it via the local updater.
After the update is complete you can boot to fastboot and then the command will work i.e. fastboot boot imagefilename.img
Hope this helps
files are from current available factory image available. be sure to use latest available fastboot application.
1. reboot to fastboot
2. fastboot erase userdata (all data is deleted, have a backup)
3. fastboot reboot-bootloader
4. fastboot flash bootloader bootloader-sunfish-s5-0.2-6539975.img
5. fastboot reboot-bootloader
6. fastboot flash radio radio-sunfish-g7150-00018-200701-b-6643937.img
7. fastboot reboot-bootloader
8. fastboot update image-sunfish-rp1a.201005.006.zip
9. fastboot reboot-bootloader
10. choose recovery
11. on the android icon with the red warning shield hold power and press volume up
12. Stock recovery appears. Choose wipe data / factory reset
if in any case the fastboot command gets stuck, replug the device and/or restart bootloader. BE CAREFULL WHEN DOING THIS WHILE RUNNING fastboot flash bootloader !!!!BRICK POSSIBLE!!!!!
After that you can boot up and see its working.
if everything is right, you should flash both slots before
relocking bootloader
so repeat above steps and do point 4. and 6. fastboot flash with
fastboot flash --slot all
from above steps. Check phone boots on both slots. Active slot can be switched via
fastboot --set-active=a
verify it boots then
fastboot --set-active=b
verify again it boots
then proceed with
fastboot flashing lock
(data will be wiped)
If you're doing it this way you should flash the images to both slots.
Fastboot flash bootloader --slot all (image)
Reboot bootloader
Fastboot flash radio --slot all (image)
Reboot bootloader
Then
Fastboot update (extracted sunfish folder)
Let it do its thing.
Incase there's any doubt on both slots being stock you can just adb sideload the OTA after you boot
Edmontonchef said:
If you're doing it this way you should flash the images to both slots.
Fastboot flash bootloader --slot all (image)
Reboot bootloader
Fastboot flash radio --slot all (image)
Reboot bootloader
Then
Fastboot update (extracted taimen folder)
Let it do its thing.
Incase there's any doubt on both slots being stock you can just adb sideload the OTA after you boot
Click to expand...
Click to collapse
indeed that is correct , ill add this to the post though in case something goes wrong i normally only affect active slot to reduce brick possibility
Is it safe to downgrade from 11 to 10 this way?
forty-second said:
Is it safe to downgrade from 11 to 10 this way?
Click to expand...
Click to collapse
Yes, just keep in mind whenever rolling back asb or android versions you'll have to format data.
You can do this in a more simple way by flash the stock image via official website from android, just click and follow the instruction
forty-second said:
Is it safe to downgrade from 11 to 10 this way?
Click to expand...
Click to collapse
from stock to stock its easier
I9602283 said:
You can do this in a more simple way by flash the stock image via official website from android, just click and follow the instruction
Click to expand...
Click to collapse
if that would be the case i would not have written this guide
It'll be nice when we have a working TWRP, then you can format data and flash/sideload an OTA if needed.
Edmontonchef said:
It'll be nice when we have a working TWRP, then you can format data and flash/sideload an OTA if needed.
Click to expand...
Click to collapse
Seems unlikely; lots of challenges getting custom recoveries working w/A11+
guide
r0tt0r said:
if that would be the case i would not have written this guide
Click to expand...
Click to collapse
Did you ever look at factory packs? It has flash_all scripts for Linux and Windows and its do all steps as needed.
Or I'm wrong?
boomo15 said:
Did you ever look at factory packs? It has flash_all scripts for Linux and Windows and its do all steps as needed.
Or I'm wrong?
Click to expand...
Click to collapse
go and unlock ur phone, flash superiorOS fe. (that was the one i was on) then go back to stock.
tell me if it was all so easy. this guide is meant if you run into issues like i did and i wanted to not have you struggle through the same.
if you think running "bat" without seeing any output of what is happening and sit for an hour without anything has happened at all cause fastboot is stuck, then do so and skip this thread.
Edmontonchef said:
If you're doing it this way you should flash the images to both slots.
Fastboot flash bootloader --slot all (image)
Reboot bootloader
Fastboot flash radio --slot all (image)
Reboot bootloader
Then
Fastboot update (extracted taimen folder)
Let it do its thing.
Incase there's any doubt on both slots being stock you can just adb sideload the OTA after you boot
Click to expand...
Click to collapse
Im confused when you mentioned "Fastboot update (extracted taimen folder)" taimen?
thanks is advance
mauri311 said:
Im confused when you mentioned "Fastboot update (extracted taimen folder)" taimen?
thanks is advance
Click to expand...
Click to collapse
Sorry I meant sunfish (brainfart)
When you extract the factory image a second folder will show up. It'll say image.sunfish.
You can type in the terminal ( fastboot update ) then drag and drop that folder. Works the same way as flash-all. Just update bootloader and radio first.
Not enough space
Hello,
I end at point 8:
error: failed to load 'image-sunfish-rp1a.201005.006.zip': Not enough space
How can I fix the problem ?
foxxof said:
Hello,
I end at point 8:
error: failed to load 'image-sunfish-rp1a.201005.006.zip': Not enough space
How can I fix the problem ?
Click to expand...
Click to collapse
it should be fixable by
fastboot erase system_a
or
fastboot erase system_b
depending on your current active slot.
r0tt0r said:
it should be fixable by
fastboot erase system_a
or
fastboot erase system_b
depending on your current active slot.
Click to expand...
Click to collapse
fastboot erase system_a
output :
erasing 'system_a' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.138s
fastboot erase system_b
output :
erasing 'system_b' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.147s
:crying:
i downloaded the latest sdk. (r30.0.5 not 30.0.4)
now it works!
foxxof said:
fastboot erase system_a
output :
erasing 'system_a' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.138s
fastboot erase system_b
output :
erasing 'system_b' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.147s
:crying:
i downloaded the latest sdk. (r30.0.5 not 30.0.4)
now it works!
Click to expand...
Click to collapse
btw the message partition should be erased in fastbootd is as far i know the recovery fastboot not the one coming at first (boot recovery, at little android press power+vol)
Partition should be erased in fastbootd
foxxof said:
fastboot erase system_a
output :
erasing 'system_a' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.138s
fastboot erase system_b
output :
erasing 'system_b' . . .
FAILED (remote: Partition should be erased in fastbootd)
finished. total time: 0.147s
Click to expand...
Click to collapse
adb reboot bootloader
fastboot reboot fastboot
fastboot erase system_a or system_b
---------- Post added at 02:45 PM ---------- Previous post was at 02:16 PM ----------
r0tt0r said:
go and unlock ur phone, flash superiorOS fe. (that was the one i was on) then go back to stock.
tell me if it was all so easy. this guide is meant if you run into issues like i did and i wanted to not have you struggle through the same.
if you think running "bat" without seeing any output of what is happening and sit for an hour without anything has happened at all cause fastboot is stuck, then do so and skip this thread.
Click to expand...
Click to collapse
Way! Why so much emotions over simple suggestion? You where unlucky and give people a guide in case which is replicate all commands from scripts. Good!
And for record my experience with this device in short!
Received – setup – Android 11 – OTA to 006 – Canary – root – boot – check all stuff – install my apps – check again – pm list for bloatware
flash superiorOS – make notes not working stuff – root – check again – same not working stuff
flash factory android 10 with flash_all – boot – check
flash CalyxOS – check – root – worked – back to stock with flash all Android 10 – check – all good
flash RR – check – root – buggy for me
flash Android 11 with flash_all – flash GrapheOS -- root -- some apps not working
flash SuperiorOS – root – flashed blu-spark kernel – remove unneeded stuff – restore backup – same bugs
flash factory – root – blu-spark – debloat – working on stock now.
All time I used flash-all and no any problems. And thank you for your suggestion to skip this tread!:good:
Awesome guide - Thank you!
FYI - To lock the bootloder, I had to use " fastboot flashing lock "
Hello, friends. So I am here following this exact tutorial :
How to Restore OnePlus Nord Back to Stock OxygenOS Software - A Complete Guide
In this guide, we will show you how to restore the stock OxygenOS software on the OnePlus Nord by flashing the factory image/Fastboot ROM. Things like custom ROMs, TWRP, and Magisk root are pretty…
www.thecustomdroid.com
I currently am stuck there
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (1996 KB)...
OKAY [ 0.055s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.057s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock_critical
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
Click to expand...
Click to collapse
I just simply do not understand what could be wrong here.
In fastoot mode I get "device - State unlocked"
As you already saw, it seems the device is completely unlocked. What could be wrong ?
Also, some steps before, I get that :
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
I suspect switching to the automated in Windows won't change much.
It is strange because I am able to perform these steps without problems, ones the ones after seem to not work :
./fastboot flash boot boot.img
./fastboot flash dtbo dtbo.img
./fastboot flash modem modem.img
./fastboot flash recovery recovery.img
./fastboot --disable-verity flash vbmeta vbmeta.img
./fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
My phone is a Oneplus Nord and I am using the advised Oxygen OS ROM provided in the tutorial I linked at the beginning of my message.
I hope you'll be able to get me out of this as I unfortunately can't figure out how to solve this problem on my own.
Best regards
krakard said:
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Yes, that makes sense.
Fastboot should be located at /usr/bin/fastboot. Since you're not in that directory, ./fastboot won't work. (This ./ means: "Look at the current working directory for the command fastboot." If it cannot find fastboot there or it isn't a shell command, it will throw an error.)
However, since you didn't install fastboot globaly, you have to address its exact path inside your platform-tools folder. If fastboot is not in Partition-image folder, ./ won't work.
Can't help you with your main issue though.
Edit: You seem to have fastboot installed globally though:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
So my first explaination is valid.
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
krakard said:
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
Click to expand...
Click to collapse
You're welcome.
BTW:
krakard said:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
There is no "fastboot" to boot into. Instead, type
Code:
fastboot reboot bootloader
I didn't mention that yesterday for some reason.
Guys, here is where I am at now. Still struggling but I feel I am very near ! Some help maybe ?
https://forum.xda-developers.com/t/...your-device-to-oxygenos.4148415/post-85022511
best regards
SOLVED
krakard said:
SOLVED
Click to expand...
Click to collapse
How did you fixed this? I'm currently stuck at the same point as you with a oneplus 8
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
mbootsman1 said:
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
Click to expand...
Click to collapse
I found the solution, you have to do fastboot reboot fastboot which reboots you to fastbootd instead of fastboot. There you can flash critical partitions without issue.
Hi,
As the command recommanded everywhere :
Code:
fastboot flashing unlock_critical
had never worked for me in the bootloader environment,
I have to reboot i my rom embedded recovery in order to flash the file (apply update menu) through the :
fastbootD
To sum up :
#From Android (while having all prerequisite done ie bootloader unlocked...)
Code:
adb reboot bootloader
#From the bootloader I choose to boot to recovery and I get to the rom custom recovery
#In the custom recovery, I choose the menu "apply update" that will lead me to the fastbootD mode
#I type the appropriate command to flash the persist partition
Code:
fastboot flash persist "c:\your_path_to_your_persist_file\persist.img"
#Then I simply reboot the phone
Code:
fastboot reboot
PS : Initially flash the OxygenOS (OOS) 11, then apply the CRdroid Android v8 custom rom (based on Android 12)
I did it similar like solid-snake:
In my case I also had no access to fastbootD
The solution came randomly when I flashed back the first part from my lineageOS package:dtbo.img, vbmeta.img and the recovery.img --> after that my phone naturally booted in a fastbootD mode from the lineageOS package.
I modified the flash-all.bat from the stock ROM fastboot flash package:
I removed the line with the reboot command, because I'm already in the fastbootD mode.
Then I ran the modified flash-all.bat and everything went well.
If anyone else struggles (like I did) to get the phone in EDL mode, or the "Flashing is not allowed for Critical Partitions" error ,even if the "fastboot flashing unlock_critical" cmd was executed, here are some hints that might help.
I tried forever on a Linux computer without any luck, so I ended up installing Windows 10 on actual hardware to finally unbrick my One Plus Nord (Avicii). Here are the most important steps, YMMV, execute at own risk:
bcdedit.exe /set nointegritychecks off run this cmd as admin in terminal, toggle to "on"
then install edl drivers as admin, This is where I struggled the most, I finally found an .exe file(QDLoader HS-USB Driver_64bit_Setup.exe) that I just installed and then phone showed up as it should in device manager. ("Qualcomm HS-USB QDLoader 9008," not "QUSB_BULK")
install adb and fastboot. (platform-tools)
install MSM-Download-Tool
download stock OS for use in MSM-Download-Tool program
open msm tool, if phone is not recognised try turning on and holding power pluss both volume, or just one of the volumes.
uncheck the "sha hash check" box
flash
if you get the "Sahara Communication Failed", just try again, it worked for me.
wipe
erase Windows 10 and replace with any Linux distro, tell your PC it will never happen again.
enjoy
Here are link to the EDL-drivers that worked for me. Or just do a web-search for "QDLoader HS-USB Driver_64bit_Setup.exe"
The flashing process will take over 300 seconds, be patient.
hi, name's Josh, i was trying to downgrade my moto g8 plus, but i had this issue with "please lock bootloader" loop so i tried locking it, but now i cannot even pass from bootloader:
"no booteable A/B slot
failed to boot linux, falling back to fastboot
fastboot reason: Fall-through from normal boot mode"
i've tried to fix it with the rescue and smart assistant but it keeps failing, i also tried flashing it with fastboot but i get the message "failed to identify current slot", when i try to "--set-active=a" it shows (either for b):
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.172s
And when i type "fastboot getvar current-slot" i get this:
current-slot:
finished. total time: 0.064s
I don't really know what to do now, even recovery mode won't prompt, it just restarts bootloader, does anyone have a solution for this? i never had this kind of issue with samsung devices, this is my first motorola and since i bought it i had problems with touch being laggy so i was trying to downgrade android 10 to 9 but i was unable, and now i can't even use it at all, i would really apreciate if somebody could help me, in advance thanks for your time and attention
Can you unlock the bootloader again?
gfrank227 said:
Can you unlock the bootloader again?
Click to expand...
Click to collapse
when i try "fastboot oem unlock" it just says:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.190s
darkhonor said:
when i try "fastboot oem unlock" it just says:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.190s
Click to expand...
Click to collapse
If you're really desperate, you can try this. I can't vouch for its success rate. Be careful.
Moto G8+ Fix/Repair Hard Brick Tutorial
hello everyone i hard bricked my moto g8 plus the other day it was totally dead it couldnt power on there was no sound no vibration my pc couldnt recognise it when connected with usb cable, But i managed to fix it and get it working again the...
forum.xda-developers.com
gfrank227 said:
If you're really desperate, you can try this. I can't vouch for its success rate. Be careful.
Moto G8+ Fix/Repair Hard Brick Tutorial
hello everyone i hard bricked my moto g8 plus the other day it was totally dead it couldnt power on there was no sound no vibration my pc couldnt recognise it when connected with usb cable, But i managed to fix it and get it working again the...
forum.xda-developers.com
Click to expand...
Click to collapse
Since you are able to get into fastboot, perhaps you should start with a blankflash from lolinet and do not take your phone apart quite yet.
When you say you tried to downgrade did you flash the previous version bootloader and partition table? You should never do that, but it sounds like you need to try and flash a blankflash like mentioned above.
One other thing you can try to do, although I doubt it would work since it can't determine the active slot is download the firmware from lolinet then fastboot boot boot.img to try and boot the kernel, which will boot the system. If that does work then you can go into dev settings and check the allow bootloader unlock option.
gfrank227 said:
Since you are able to get into fastboot, perhaps you should start with a blankflash from lolinet and do not take your phone apart quite yet.
Click to expand...
Click to collapse
ok so i tried to blankflash it but i got this error i guess is time to say goodbye jajaj
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM7
[ 0.005] Detecting device
[ 34.666] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.666] Check qboot_log.txt for more details
[ 34.666] Total time: 34.668s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
CodyF86 said:
When you say you tried to downgrade did you flash the previous version bootloader and partition table? You should never do that, but it sounds like you need to try and flash a blankflash like mentioned above.
One other thing you can try to do, although I doubt it would work since it can't determine the active slot is download the firmware from lolinet then fastboot boot boot.img to try and boot the kernel, which will boot the system. If that does work then you can go into dev settings and check the allow bootloader unlock option.
Click to expand...
Click to collapse
well im uncertain of how that is made, i just followed up a tutorial , downloaded official firmware and flashed it with fastboot comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
and yeah i tried flashing the newest official firmware that rescue and smart assistant showed, but since i cannot determine slot it says "failed to identify current slot"
Yeah it looks like that would have flashed the previous version of androids parttition table for that device from the commands you ran and that's usually a rip.
CodyF86 said:
Yeah it looks like that would have flashed the previous version of androids parttition table for that device from the commands you ran and that's usually a rip.
Click to expand...
Click to collapse
So there's no other way to fix it?