Related
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup
abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....
heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.
Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))
Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
I have the same problem but with a different firmware.. now only thing i can do is use dc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
MobileTechArena said:
I have the same problem but with a different firmware. now only thing i can do is usedc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
Click to expand...
Click to collapse
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
barnabaXXX said:
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
Click to expand...
Click to collapse
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Thanks for making it clear. Please tell me if it worked or not. Thanks.
barnabaXXX said:
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
Click to expand...
Click to collapse
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
barnabaXXX said:
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
Click to expand...
Click to collapse
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
barnabaXXX said:
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
Click to expand...
Click to collapse
Unfortunately I can't help you further than what I already posted.
But keep updating in case someone more knowledgeable peeks in.
similar problem....I was fairly good but play store was stuck in pending download....
I did a wipe in TWRP, and ended with a black screen...
I can boot to eRecovery, but it fails.and also to TWRP.
when attached to PC it keeps being seen and unseen as if its stuck in a power on cycle
Any help would be greatly appreciated.
Already Tested
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Hello did you already test ???
Here is the solution for every PRA-LX1: [http : // www . htcmania . com / showthread . php ? t=1326478] (sorry for the spaces, but I don't have enough posts written to post external links )
Unfortunately, it's from a spanish forum. I didn't found any problem to follow this tutorial, but maybe for someone it could be a little difficult.
Anyway, it works!
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Where did you find the C432 firmware? I can't succees to find it
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Iocere said:
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Click to expand...
Click to collapse
Yeah, that's the way! It worked for me too!
juanmemo said:
Yeah, that's the way! It worked for me too!
Click to expand...
Click to collapse
Also i noticed everytime a OTA fails you get the full version offered on next boot. So you should get a full B164 aswell after it failed
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
how can you boot into recovery ? i can only boot into twrp or fastboot & rescue or if i plug the huawei to the pc erecovery ???
---------- Post added at 12:16 AM ---------- Previous post was at 12:13 AM ----------
i have an huawei pra-lx1 c530 it used to boot into pra-lx1c530b111 rooted and twrp but now it doens't boot anymore, i'd like to flash to c530b160 but i can't find the firmware images
tiagoggama said:
Hello did you already test ???
Click to expand...
Click to collapse
Thanks men
I CONFIRM IT WORK PERFECTLY
For the second part go to this link for more detail :
https://boycracked.com/2016/03/14/h...-unbrick-firmware-any-huawei-android-devices/
**URGENT** i have my p20 pro 6/128 with 9.0 last version ROOTED somehow i found a article.. the root was success. Tried to flash official twrp with twrp app and then everything was like HELL.
If i let my phone boot says error! func no: 10 boot image. error no :2 load failed. i faced something simillar when trying to get into recovery sometimes.
I can get into erecovery cant format or download official firmware. I can get into fastboot, download mode. I am gonna tell you everything . every program i tried AND FAILED!
TRIED: multi tool for huawei ( i download a version i think its 165 something when i press flash selected the program closed)
TRIED: to FLASH like 10 times ramdisks, recoverys, CANT FIND BOOT.IMG.
TRIED: Re-flash 9.0 says missing zip files THATS IMPOSIMPLE NOTHING IS MISSING I AM SURE
TRIED: a guide that said to download firmware and i would find a folder named DLOAD. i did everything. COULDNT FLASH SOMETHING ON DOWNLOAD SAYS ERROR
TRIED: ALMOST EVERYTHING
PLEASE HELP ME, HOW TO FIX IT? its very important for me and for everyone who is facing the same problem
Phone infos From Multi tool program http://prntscr.com/min398
and the firmwares i tried 1) http://prntscr.com/min3tn
2) http://prntscr.com/min40j
SEE SOME POSTS BELLOW TO SEE HOW I FIXED IT SUCCESS AFTER MANY ERRORS
1 found this post, and flashed all of them BUT there is not ramdisk on the files. i looked on two different firmwares which should i flash over ramdisk which doesnt exist?
first i run the command fastboot flash kernel kernel.img and i could boot into TWRP for first time. now i cant.
there are not errors for now. only if i boot my phone says phone keeping booting.
when i got to twrp and tried to reboot into system said there is no OS.
How and which os i should flash? since Multi tool program kicks me
HELP
https://forum.xda-developers.com/honor-9/help/help-softbricked-h9-oreo-t3750282
So you're typing a little erratic.
Can you get to eRecovery? This is your best option..
If not then you'll need to reflash all the parts of the OS back to the phone manually..
Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.
dladz said:
So you're typing a little erratic.
Can you get to eRecovery? This is your best option..
If not then you'll need to reflash all the parts of the OS back to the phone manually..
Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.
Click to expand...
Click to collapse
i can get into erecovery i cannot download the official and flash it throught there says error.. what else i can do
I cant understand what yyou saying here Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.
I get into Erecovery if i press download latest version and recovery after some times when i put the wifi pass says error. Error i got also on HIsUite when i tried to format from there and download the latest versio. So we go manually but HOW? i tried almost everything
i tried this https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
success all command went trhough the phone
the problem is i cannot flash twrp
my phone has unlocked bl
well i did a lot of search if you ask me i download 5-7 different programs that can flash stock firmware. ONE seems to be legit for 9.0 RE-flash 9.0 which has commands on its script like this guy says and he helped me too
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
also if someone cant boot into twrp after the frist steps and see the erecovery just format everything from erecovery and then it will boot to twrp.
also now says installing update.
i hope imeis serial numbers etc wont lost..
Thats the script i found i dont remeber where
http://prntscr.com/mitvum
but i can upload somewhere the files
if you run FLASH.bat and says MISSING ZIPS then remove the update."zip" {ZIP PREFIX FROM THE NAME OF THE FILES ONLY} and run again the bat
the procedure may take 10-30 mins
What about the otg method?
Also I would never use a tool like this.
StonebridgeGr said:
**URGENT** i have my p20 pro 6/128 with 9.0 last version ROOTED somehow i found a article.. the root was success. Tried to flash official twrp with twrp app and then everything was like HELL.
If i let my phone boot says error! func no: 10 boot image. error no :2 load failed. i faced something simillar when trying to get into recovery sometimes.
I can get into erecovery cant format or download official firmware. I can get into fastboot, download mode. I am gonna tell you everything . every program i tried AND FAILED!
TRIED: multi tool for huawei ( i download a version i think its 165 something when i press flash selected the program closed)
TRIED: to FLASH like 10 times ramdisks, recoverys, CANT FIND BOOT.IMG.
TRIED: Re-flash 9.0 says missing zip files THATS IMPOSIMPLE NOTHING IS MISSING I AM SURE
TRIED: a guide that said to download firmware and i would find a folder named DLOAD. i did everything. COULDNT FLASH SOMETHING ON DOWNLOAD SAYS ERROR
TRIED: ALMOST EVERYTHING
PLEASE HELP ME, HOW TO FIX IT? its very important for me and for everyone who is facing the same problem
Phone infos From Multi tool program http://prntscr.com/min398
and the firmwares i tried 1) http://prntscr.com/min3tn
2) http://prntscr.com/min40j
SEE SOME POSTS BELLOW TO SEE HOW I FIXED IT SUCCESS AFTER MANY ERRORS
Click to expand...
Click to collapse
dladz said:
What about the otg method?
Also I would never use a tool like this.
Click to expand...
Click to collapse
like i said in the first post the otg method with the dload folder failed.
Why you wouldnt try it?
StonebridgeGr said:
like i said in the first post the otg method with the dload folder failed.
Why you wouldnt try it?
Click to expand...
Click to collapse
Because I've got no need to mate, manual is always safer.
Have you asked in the thread where you got the tool?
I'm not sure what else to suggest pal
dladz said:
Because I've got no need to mate, manual is always safer.
Have you asked in the thread where you got the tool?
I'm not sure what else to suggest pal
Click to expand...
Click to collapse
now everything is fine but i cant root..
StonebridgeGr said:
now everything is fine but i cant root..
Click to expand...
Click to collapse
Everything is fine? What did you do?
With root Judy follow the instructions that have worked for other people. Don't rush things.
dladz said:
Everything is fine? What did you do?
With root Judy follow the instructions that have worked for other people. Don't rush things.
Click to expand...
Click to collapse
i post i early post a link that helped me a little bit i think i edited the .bat script
also i made a video and post about rooting and everything is fine.
the problem is you can have twrp and magisk root both:/
either you have root and not twrp or either you have twrp and not root
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
pastorbob62 said:
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
Click to expand...
Click to collapse
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
Thanks KtownJeff, that does sound much easier. Why aren't others posting this much simpler solution? Has anyone else tried this?
I haven't tried it yet as it looks like they may be about to figure out the low call volume issue in custom ROMs and then these OTA updates won't be necessary anyway? I'll wait and see what happens over the next week or so.
I'm wondering why it's necessary to wipe the data though. Why isn't uninstalling Magisk and booting with the original kernel enough?
JerseyChewi said:
Yeah the calling issue is just a lineage thing...and lineage is so generically lame. mokee or corvusos are my favs. Most of the custom Roms work well.... and there is a lot more ROMS for our device that is not on XDA.... The Data may be fine Just back it up first....and I put this on telegram and if you haven't checked it out there is five channels for our phone with tons of stuff.....more ROM builds We also have Pitch Black Recovery now available which is twrp with a cleaner UI and lots more options
Click to expand...
Click to collapse
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
WHHAAAT?? I got a few questions...
Why is it important not to have the copy-partitions.zip installed?
Why you should be on slot _a?
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
WoKoschekk said:
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Click to expand...
Click to collapse
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
WoKoschekk said:
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
Click to expand...
Click to collapse
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
JerseyChewi said:
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
Click to expand...
Click to collapse
Assuming this is not your first time flashing the firmware and you already have a flash script/.bat file:
1. run the script
Done! One command and 5 min later you are on the latest firmware.
JerseyChewi said:
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
Click to expand...
Click to collapse
Motorola provides you OEM signed images and a .xml sheet with proper commands to flash them as a .zip file. I've never heard that someone bricked his device by using the manufacturer's recommended way. I think it's risky to use your own workaround just because you're nervous about it.
Even if you unplug the device in the middle of the flashing process you won't face any trouble. Every single flashing command loads the image into your device's RAM before it gets written to the device.
fastboot oem fb_mode_set = no matter what reboot command you run your device boots into bootloader
Why are you nervous about it?
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary.... so that way when OTA comes it will move to the B partition the way that it was intended to.....but the boot-loader is unlocked now both slots start with a boot-loader, bootloader_a and bootloader_b.. .and the on board preboot chip will trip the first flag that communicates with stock flashed boot image which also holds the recovery and the kernel... even if its backed up stock.img with magisk, it will break the next flag on the device along with the custom logo.bin.... now the custom logo if it is cloned with a moto signature official it wont matter and the only one Im aware is logo.bin for the TMOBILE REVVLY variant.... when you boot not flash the stock boot.img it bypasses the security chain until reboot.... I've flashed b slot on accident and then booted several GSI and other lake Roms and at some point ill notice on the bootloader screen that maybe i have April 2020 when Im running July 2020 version....which is headache to fix and i booted to b slot flash stock as normal let boot to the setup wizard then reverse to a and do it again because it brings it back together... now the mapping for the AB partition with duel slots t is standard for all ARM64 AB devices Bootloader a and b Boot a and b Radio a and b which is (firmeware) slot Vendor a and b System a and b....
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
the reason why I wrote it the way that I did was because I tried everything to OTA back and this was the only way it worked for me.... and trust me I stayed up for weeks trying to break it or fix it....I finally I came across a moto g6 thread where some one relocked there bootloader and didnt have the oem unlock set and they couldnt do anything to unlock it again using fastboot because the switch was grey out on developer options which means they couldnt root to fix..., I believe it was Sd_shadow that recommended trying to boot the boot.img like how we boot the twrp.img because it bypasses the security flag... well my first attempt it didn't work which led me to the mismatched boot-loaders and I kept at it and by process of elimination and fully learning the way these partitions communicate..... which is totally backwards from the way it used to be... If u leave data then flash back stock, the boot-loader thinks its fresh but finds its not......so boot-loop... tried it cussed and tried again and screamed but now its automatic. for me because of trial and error... I've been at this a few years now and I'm learning something new all the time and most of time when people don't post is because they either don't know or don't wanna give wrong info or maybe nobody showed them. There kinda is an unwritten bylaw at XDA (tough love)... you gotta learn by experience that way when get an opportunity to help or find a new way it makes it worth the stress
That is why I wrote it the way I did step by step in the easiest way possible because of my experiences and headaches...If it don't work you didn't follow directions.... Now I'm gonna tell you I re-locked my bootloader too and was not able to flash back ota don't even try its a waste of time because the only way to get that flag back is to re ball a chipset, or replace the motherboard, or buy a new phone....
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
KtownJeff said:
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary....
Click to expand...
Click to collapse
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
BTW: You can call me what you want but that doesn't make your statements right either.
WoKoschekk said:
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
Click to expand...
Click to collapse
KtownJeff said:
Yes correct it easier to flash rom after it is available for download with a month behind....
Click to expand...
Click to collapse
You should check your sources.
KtownJeff said:
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
Click to expand...
Click to collapse
I also want to leave my device in oem_locked state and not in flashing_locked
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
pastorbob62 said:
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
Click to expand...
Click to collapse
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
WoKoschekk said:
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Click to expand...
Click to collapse
I'm thinking not, since this was the first thing I tried when I got the notification for the update. And the update still failed.
WoKoschekk said:
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
Click to expand...
Click to collapse
Telegram didn't have it when I installed the update. LMSA kept giving me a "Decompression failed" error message. So I just reinstalled the stock version I was already on and allowed the update to complete. Then reinstalled TWRP and Magisk without any issues once I had all of my apps and data restored.
Not taking any offense here, but I am not a noob and while I didn't give all of the details to what I had tried I also didn't want to reinvent the wheel. I didn't think about eliminating the line "erase userdata". Since it was very simple with previous devices to do it I knew there had to be an easier way. By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
pastorbob62 said:
Telegram didn't have it when I installed the update.
...
By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
Click to expand...
Click to collapse
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
WoKoschekk said:
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
Click to expand...
Click to collapse
That's nice. But the one for my phone was not available on tracker until the day after I updated via OTA.
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
Click to expand...
Click to collapse
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
[email protected] said:
I tried this to go back to stock rom from LOS17.
I've never seen that error before have you tried google search for the error?
Click to expand...
Click to collapse
[email protected] said:
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
Click to expand...
Click to collapse
Don't know what your error means, but flash the stock ROM and it should be fine.