**************THE PROBLEM***************
Boot into recovery (twrp) - and flash Los 15.1 after formatting internal- then comes the *error 255* .
So I tried it with twrp treble and it flashed without any problems.
After flashing I clicked reboot and it rebooted into twrp again.
No matter how many times I try rebooting from system or twrp it boots into twrp itself. *Tried with many twrps*
But it boots into bootloader and from there I could click start to boot to system!
So I thought I would flash stock ROM (Oreo August) and I did. On rebooting, it went straight to stock recovery and I selected reboot to system and it didn't! It rebooted back to the recovery!
So I rebooted into the bootloader and clicked start and then it boots! And it shows encrypting and reboots to the setup area.
After setting up I rebooted the device ( normal way ) and again I found myself in the stock recovery!!
**************** THE SOLUTION **************
FLASH STOCK NOUGAT ROM (I FLASHED THE NOVEMBER BUILD)
Link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Since I was on Oreo downgrading was not directly applicable.. I flashed TWRP and formatted the phone then booted to bootloader and flashed the stock ROM!
Fastboot commands didn't work exactly ! So I followed this guide to get the servicefile.xml in the ROM zip to create a new .bat file that flashed the phone!
Link: https://youtu.be/njXQYn53SPc
OR
I've made an attachment of the .bat file that you can download and extract.
Bootloader was left unlocked!
OTAs were successful! No issues so far! Flashed November 2017 Fastboot ROM and updated to August 2018 Oreo via OTA!
Cheers People!! Happy Flashing!!
Oh! And as always! No one will take responsibility for your actions! You alone are responsible!! ? #standardprocedure
Hi, u wipe data and factory data in the recovery before installing stock? i had the same problem yesterday and I solved it flashing stock 7.1.1 (NPSS26.118-19-14 - November 2017)
SteveO-RG said:
Hi, u wipe data and factory data in the recovery before installing stock? i had the same problem yesterday and I solved it flashing stock 7.1.1 (NPSS26.118-19-14 - November 2017)
Click to expand...
Click to collapse
Thanks mate! It Worked Well! ??
Cheers!!
I have the same problem. I've tried TWRP 3.2.1_r12 and 3.2.3-0, in both cases the phone reboots to recovery and I have to reboot again to bootloader and from there to the OS. Any way to fix this without going back to stock ROM? It's no big deal, I reboot rarely, but still slightly annoying.
indrekh said:
I have the same problem. I've tried TWRP 3.2.1_r12 and 3.2.3-0, in both cases the phone reboots to recovery and I have to reboot again to bootloader and from there to the OS. Any way to fix this without going back to stock ROM? It's no big deal, I reboot rarely, but still slightly annoying.
Click to expand...
Click to collapse
I honestly tried many times to get it working normally without going back to stock ROM but couldn't!
Sorry bruv! I guess this is the only way! :angel:
the_phantom_97 said:
I honestly tried many times to get it working normally without going back to stock ROM but couldn't!
Sorry bruv! I guess this is the only way! :angel:
Click to expand...
Click to collapse
Bummer. Thanks anyway
DUDE!!!
I had an Issue yesterday while trying to downgrade and i ended having a custom ROM with the fingerprint sensor disabled i dont know why!
But today i followed this thread an solved the problem!!
A lot of thanks my friend! My eternal gratitude!!!
Thanks for this solution, but I still get BAD KEY message and I can't relock bootloader. Any advice to solve this problem? Thx
the_phantom_97 said:
**************THE PROBLEM***************
Boot into recovery (twrp) - and flash Los 15.1 after formatting internal- then comes the *error 255* .
So I tried it with twrp treble and it flashed without any problems.
After flashing I clicked reboot and it rebooted into twrp again.
No matter how many times I try rebooting from system or twrp it boots into twrp itself. *Tried with many twrps*
But it boots into bootloader and from there I could click start to boot to system!
So I thought I would flash stock ROM (Oreo August) and I did. On rebooting, it went straight to stock recovery and I selected reboot to system and it didn't! It rebooted back to the recovery!
So I rebooted into the bootloader and clicked start and then it boots! And it shows encrypting and reboots to the setup area.
After setting up I rebooted the device ( normal way ) and again I found myself in the stock recovery!!
**************** THE SOLUTION **************
FLASH STOCK NOUGAT ROM (I FLASHED THE NOVEMBER BUILD)
Link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Since I was on Oreo downgrading was not directly applicable.. I flashed TWRP and formatted the phone then booted to bootloader and flashed the stock ROM!
Fastboot commands didn't work exactly ! So I followed this guide to get the servicefile.xml in the ROM zip to create a new .bat file that flashed the phone!
Link:
OR
I've made an attachment of the .bat file that you can download and extract.
Bootloader was left unlocked!
OTAs were successful! No issues so far! Flashed November 2017 Fastboot ROM and updated to August 2018 Oreo via OTA!
Cheers People!! Happy Flashing!!
Oh! And as always! No one will take responsibility for your actions! You alone are responsible!! ? #standardprocedure
Click to expand...
Click to collapse
JRapsky said:
Thanks for this solution, but I still get BAD KEY message and I can't relock bootloader. Any advice to solve this problem? Thx
Click to expand...
Click to collapse
That is most probably because you're trying to flash an old firmware wherein your bootloader is already on the newer one! We'll try flashing with this December 2018 firmware linked below but don't use the zip in the thread... It is only for Nougat Firmware!
2018 December Firmware:-
https://androidfilehost.com/?fid=11410963190603890525
Fastboot command zip by @brunorochaa00 :- https://androidfilehost.com/?fid=13356325061477270130
this zip has the fastboot and the commands... Just extract the firmware to the folder where you extract the zip and flash any of the .bat files!!
i ran through all these commands but it still says no OS is installed in TWRP
trying to install custom rom give 255 ERROR'
do these logs look normal?
PS C:\adb> .\2-Instalador-Completo.bat
*************************************************
* Instalador Firmware *
* Moto Z2 Play Albus XT1710 *
* Script by Junior Passos *
*************************************************
"Desligue seu Moto Z2 Play e conecte-o no computador em Modo Fastboot."
"Aviso: Os arquivos no armazenamento interno serao totalmente deletados!"
Press any key to continue . . .
< waiting for device >
max-sparse-size: 268435456
finished. total time: 0.001s
...
OKAY [ 0.002s]
finished. total time: 0.002s
sending 'partition' (45 KB)...
OKAY [ 0.002s]
writing 'partition'...
Validating 'gpt.default.xml'
Security version downgrade
Image primary_gpt failed validation
Preflash validation failed
Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.076s
sending 'bootloader' (5115 KB)...
OKAY [ 0.116s]
writing 'bootloader'...
Validating 'bootloader.default.xml'
Committing 'bootloader.default.xml'
- flashing 'emmc_appsboot.mbn' to 'aboot'
- flashing 'rpm.mbn' to 'rpm'
- flashing 'tz.mbn' to 'tz'
- flashing 'devcfg.mbn' to 'devcfg'
- flashing 'cmnlib.mbn' to 'cmnlib'
- flashing 'cmnlib64.mbn' to 'cmnlib64'
- flashing 'keymaster.mbn' to 'keymaster'
- flashing 'prov.mbn' to 'prov'
- flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.526s]
finished. total time: 0.644s
sending 'modem' (71573 KB)...
OKAY [ 1.612s]
writing 'modem'...
OKAY [ 1.126s]
finished. total time: 2.761s
sending 'fsg' (4020 KB)...
OKAY [ 0.081s]
writing 'fsg'...
OKAY [ 0.126s]
finished. total time: 0.233s
erasing 'modemst1'...
OKAY [ 0.032s]
finished. total time: 0.032s
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.032s
sending 'dsp' (16384 KB)...
OKAY [ 0.370s]
writing 'dsp'...
OKAY [ 0.295s]
finished. total time: 0.668s
sending 'logo' (2192 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.098s]
finished. total time: 0.164s
sending 'boot' (16384 KB)...
OKAY [ 0.432s]
writing 'boot'...
Image signed with key bad key
OKAY [ 0.392s]
finished. total time: 0.840s
sending 'recovery' (20580 KB)...
OKAY [ 0.522s]
writing 'recovery'...
Image size exeeded partition limits
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.536s
sending 'system' (262141 KB)...
OKAY [ 6.039s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 6.058s
sending 'system' (255657 KB)...
OKAY [ 5.741s]
writing 'system'...
OKAY [ 3.393s]
finished. total time: 9.142s
sending 'system' (243061 KB)...
OKAY [ 5.673s]
writing 'system'...
OKAY [ 3.380s]
finished. total time: 9.058s
sending 'system' (260374 KB)...
OKAY [ 6.039s]
writing 'system'...
OKAY [ 3.955s]
finished. total time: 10.002s
sending 'system' (260395 KB)...
OKAY [ 6.005s]
writing 'system'...
OKAY [ 3.608s]
finished. total time: 9.629s
sending 'system' (242845 KB)...
OKAY [ 5.567s]
writing 'system'...
OKAY [ 3.173s]
finished. total time: 8.753s
sending 'system' (262140 KB)...
OKAY [ 5.994s]
writing 'system'...
OKAY [ 3.402s]
finished. total time: 9.402s
sending 'system' (262141 KB)...
OKAY [ 6.108s]
writing 'system'...
OKAY [ 3.620s]
finished. total time: 9.742s
sending 'system' (262142 KB)...
OKAY [ 5.885s]
writing 'system'...
OKAY [ 3.633s]
finished. total time: 9.531s
sending 'system' (262141 KB)...
OKAY [ 6.044s]
writing 'system'...
OKAY [ 3.412s]
finished. total time: 9.465s
sending 'system' (239056 KB)...
OKAY [ 5.488s]
writing 'system'...
Invalid sparse image data
Failed to flash sparse image
FAILED (remote failure)
finished. total time: 7.494s
sending 'system' (45248 KB)...
OKAY [ 1.018s]
writing 'system'...
Invalid sparse image data
Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.044s
sending 'oem' (155105 KB)...
OKAY [ 3.549s]
writing 'oem'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 3.562s
erasing 'carrier'...
OKAY [ 0.135s]
finished. total time: 0.150s
erasing 'cache'...
OKAY [ 0.008s]
finished. total time: 0.008s
erasing 'userdata'...
OKAY [ 0.128s]
finished. total time: 0.140s
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.002s
...
OKAY [ 0.002s]
finished. total time: 0.002s
"Arquivos instalados com sucesso!"
rebooting...
finished. total time: 0.001s
I tried installing custom ROM (viper OS) on my moto z2 play and it showed the same error. Updater process error 255 and after trying two more ROMs my phone is stuck in twrp mode. Why the error: 255 and how to fix it, is it that i can never install a custom ROM or what? and about downgrading it to NOUGAT i'm trying it now. I'll let you know if it works. but can you help me with the error 255!
FIX
Use this command on PC:
fastboot oem fb_mode_clear
https://forum.xda-developers.com/showthread.php?t=2774709&page=5
Works! But i lost my imei...
Related
Hi devs and helpers!!
this is only for indians but if you wish you can help
ok this is a long story let me explain
so first lollipop soak test released and i updated it via keeping the file in sd and phone memory and then i updated it till 22.27.1 then i found that i am stuck on that version i cant do anything so i flashed 5.1 firmware images and then on the bootloader says that hab check failed for system and failed to validate system image so i need the indian retail from flipkart stock 4.4.4 images only if they are 4.4.4 ! AND I CANT UNLOCK THE BOOTLOADER AS THAT IS ANOTHER LONG STORY SO NOW IF ANYONE HAS WHAT I WANT THEN PLZ GIVE AND DONT TELL TO UNLOCK THE BOOTLOADER AND I HAVE TRIED EVERY FIRMWARE EXCEPT (http://forum.xda-developers.com/showthread.php?t=2759495) , the link isnt working and i have also posted on that thread that the link isnt working , So can anyone help me plz???
THANKS!!
Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.
Droidriven said:
Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.
Click to expand...
Click to collapse
Thankyou very much for responding !! i will try it and tell u tommorow!!:laugh::good::good::good:
Droidriven said:
Hello,
Have you tried this?
http://forum.xda-developers.com/moto-e/general/xt1022-stock-indian-firmware-t2826480
I hope that helps. Good luck.
Click to expand...
Click to collapse
sorry doesnt work:crying:
i need Blur_Version.21.41.20.condor_retaildsds.retaildsdsall.en.03 something like that the xx.xx.xx is not correct:crying:
snehil_dps_6l said:
hi devs and helpers!!
This is only for indians but if you wish you can help
ok this is a long story let me explain
so first lollipop soak test released and i updated it via keeping the file in sd and phone memory and then i updated it till 22.27.1 then i found that i am stuck on that version i cant do anything so i flashed 5.1 firmware images and then on the bootloader says that hab check failed for system and failed to validate system image so i need the indian retail from flipkart stock 4.4.4 images only if they are 4.4.4 ! And i cant unlock the bootloader as that is another long story so now if anyone has what i want then plz give and dont tell to unlock the bootloader and i have tried every firmware except (http://forum.xda-developers.com/showthread.php?t=2759495) , the link isnt working and i have also posted on that thread that the link isnt working , so can anyone help me plz???
thanks!!
Click to expand...
Click to collapse
plzzz someone send firwares plzzzz
You cannot flash any 4.4.4 Firmware Image without Unlocking Bootloader. Follow Bootloader locking Tutorial: http://forum.xda-developers.com/showpost.php?p=52693419&postcount=2
Alternatively, forget about KitKat and flash latest XT1022 Lollipop 5.1 Firmware Image from here: http://forum.xda-developers.com/showthread.php?t=2755857
XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
You have to unlock the bootloader
MaddySayaji said:
You have to unlock the bootloader
Click to expand...
Click to collapse
if there is a corrupt firmware how can i unlock the bootloader
lost101 said:
You cannot flash any 4.4.4 Firmware Image without Unlocking Bootloader. Follow Bootloader locking Tutorial: http://forum.xda-developers.com/showpost.php?p=52693419&postcount=2
Alternatively, forget about KitKat and flash latest XT1022 Lollipop 5.1 Firmware Image from here: http://forum.xda-developers.com/showthread.php?t=2755857
XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Hi sir,
im very happy that someone is trying to help me out
all the commands were successful but i have a error "failed to validate system image" in purple color and plus ur older version of 5.1 firmware isnt working its saying (preflash validation failed) (XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.2_cid7_CFC.xml)
here are all the commands as asked (output from command prompt):
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.024s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.712s]
finished. total time: 0.741s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.088s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 2.071s]
finished. total time: 2.170s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (527 KB)...
OKAY [ 0.067s]
writing 'logo'...
OKAY [ 0.132s]
finished. total time: 0.205s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.396s]
writing 'boot'...
OKAY [ 1.573s]
finished. total time: 1.976s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.409s]
writing 'recovery'...
OKAY [ 1.575s]
finished. total time: 1.998s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (242987 KB)...
OKAY [ 8.533s]
writing 'system'...
OKAY [ 27.242s]
finished. total time: 38.026s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256539 KB)...
OKAY [ 9.150s]
writing 'system'...
OKAY [ 25.751s]
finished. total time: 34.909s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257126 KB)...
OKAY [ 9.087s]
writing 'system'...
OKAY [ 25.306s]
finished. total time: 34.406s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46232 KB)...
OKAY [ 1.667s]
writing 'modem'...
OKAY [ 3.940s]
finished. total time: 5.614s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.018s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.016s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (648 KB)...
OKAY [ 0.066s]
writing 'fsg'...
OKAY [ 0.130s]
finished. total time: 0.201s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.079s]
finished. total time: 0.082s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.271s]
finished. total time: 0.274s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\DELL USERS\Downloads\XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml>
@Snehil_DPS_6l - The solution is to unlock your Bootloader and try fastboot flashing again.
Hey guys, newbie to installing custom ROMs so be gentle with me.
Someone gave me a rooted Xperia Z Ultra at Android 4.3.1. I previously wiped the device back to factory settings because the previous user didn't want their old data on it.
I wanted to install the latest ROM for it, so I found this thread and decided to give it a go:
https://forum.xda-developers.com/xp...elopment/rom-marshmallow-6-0-z-ultra-t3224321
I downloaded the image files and booted into fastboot mode.
ran the fastboot commands to install each img file and reboot the device. See below:
=====================================================
fastboot flash boot boot.img"
sending 'boot' (9856 KB)...
OKAY [ 0.318s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 0.979s
fastboot flash cache cache.img"
sending 'cache' (5800 KB)...
OKAY [ 0.191s]
writing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.204s
fastboot flash system system.img"
sending 'system' (601241 KB)...
OKAY [ 18.878s]
writing 'system'...
OKAY [ 43.825s]
finished. total time: 62.710s
fastboot flash userdata userdata.img"
sending 'userdata' (137490 KB)...
OKAY [ 4.346s]
writing 'userdata'...
OKAY [ 9.231s]
finished. total time: 13.583s
=========================================================
Once it rebooted it never came back up again. I waited about 30 minutes just to be sure. The computer still recognizes it and I can boot into fastboot mode, but the phone never boots back into regular boot mode anymore.
Wondering if anyone has any thoughts on this?
Thanks
Bump!
deeeyewhy said:
Hey guys, newbie to installing custom ROMs so be gentle with me.
Someone gave me a rooted Xperia Z Ultra at Android 4.3.1. I previously wiped the device back to factory settings because the previous user didn't want their old data on it.
I wanted to install the latest ROM for it, so I found this thread and decided to give it a go:
https://forum.xda-developers.com/xp...elopment/rom-marshmallow-6-0-z-ultra-t3224321
I downloaded the image files and booted into fastboot mode.
ran the fastboot commands to install each img file and reboot the device. See below:
=====================================================
fastboot flash boot boot.img"
sending 'boot' (9856 KB)...
OKAY [ 0.318s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 0.979s
fastboot flash cache cache.img"
sending 'cache' (5800 KB)...
OKAY [ 0.191s]
writing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.204s
fastboot flash system system.img"
sending 'system' (601241 KB)...
OKAY [ 18.878s]
writing 'system'...
OKAY [ 43.825s]
finished. total time: 62.710s
fastboot flash userdata userdata.img"
sending 'userdata' (137490 KB)...
OKAY [ 4.346s]
writing 'userdata'...
OKAY [ 9.231s]
finished. total time: 13.583s
=========================================================
Once it rebooted it never came back up again. I waited about 30 minutes just to be sure. The computer still recognizes it and I can boot into fastboot mode, but the phone never boots back into regular boot mode anymore.
Wondering if anyone has any thoughts on this?
Thanks
Click to expand...
Click to collapse
If the ZU had 4.3 on it, its possible you have to flash the latest stock rom. I think I recall reading something about needing to flash the latest stock at least once before flashing any mm or nougat rom.
Flash the 4.4.4 ftf with flashtool. Then install xzu dual recovery by nut. After that install whatever ROM/mod you like.
I have been doing A LOT of research, reading, and experimentation to get an old Nexus 7 (2012 wifi) in working order for my 5 year old daughter. So far a took a barely functioning tablet, crippled with Lollipop 5.1.1 and turned it into a really nice, extra large coaster. I am attempting to roll the os back to some version of KitKat.
So far I have: Used the Nexus Root Toolkit v2.1.9 to unlock and install KitKat 4.4 (nakasi-ktu84p). That bricked it. Through other research I found that others have receive the same error messages as I have (writing 'bootloader'...FAILED (remote: (InvalidState))) - https://forum.xda-developers.com/showthread.php?t=2417097) so I tried their solution (installing nakasi-jwr66v). No luck. Same errors. The Nexus Root Toolkit forums are dead. I can still get it to the bootloader screen but not navigate to "Recovery" any longer.
I am a complete novice at this. Any help would be greatly appreciated. And if it doesn't work I can at least say I tried.
Here is a copy of the installation by the Nexus Root Toolkit that might mean something to you. Seems to be a lot of errors:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.067s]
finished. total time: 0.068s
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.106s]
finished. total time: 0.107s
erasing 'recovery'...
OKAY [ 0.026s]
finished. total time: 0.026s
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.080s]
finished. total time: 0.081s
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 4.917s]
finished. total time: 4.918s
target didn't report max-download-size
sending 'bootloader' (2100 KB)...
OKAY [ 1.481s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 1.615s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
target didn't report max-download-size
sending 'boot' (4896 KB)...
OKAY [ 0.653s]
writing 'boot'...
OKAY [ 0.204s]
finished. total time: 0.857s
target didn't report max-download-size
sending 'recovery' (5432 KB)...
OKAY [ 0.735s]
writing 'recovery'...
OKAY [ 0.226s]
finished. total time: 0.962s
target didn't report max-download-size
erasing 'system'...
OKAY [ 0.101s]
sending 'system' (529061 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 21.490s
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
rebooting...
finished. total time: 5.000s
Does any of this mean something to you? Thanks again.
OPTIONAL READING
Hi, let's go:
Scénario: you know nothing Jon Snow, but you want root, so you install fastboot, no matter which twrp, you follow a couple of tutorials you found in the wild and you play around with slot a -slot b twrp option. You find funny erase partitions, that way you have more internal space, maybe. You erase devil cache, and good boy cache and everything, because why not? You do not make backups, 'cause your not a coward, but a little nervous-impulsive. Magisk? it sound cool, I´ll take 4, thanks
Strange, things start going badly: The nokia 3.2 goes crazy and you just have fastboot. You manage to have twrp again thanks to the command fastboot flash boot twrp-3.2-dpl-00eea
Buuuuuuut you cannot install img nor zip files from sdcard using install options, then you discover that there is /sdcard an /external_sdcard¡¡¡ but it does not matter, file is corrupted, even drinking bleach does not improves the situation. Yo cannot install lineage-17.1-20200413-UNOFFICIAL-treble_arm64_avN. img or .zip (ahhhh it is RAR, so I have to change the extension to zip? maybe the system folder?) and you do not even know if you are arm64 a/b or just arm or legs.
You try to install system-quack-arm-ab-vanilla via adb push commands or fastboot commands, you fight with qualcomm drivers, the qfil tool, with not command found little android robot message, your system is corrupt message, go to see google nokia page (why? they are the enemy who bloats my phone!!!) you do not even know if you were in andorid 10 or 9 or 1909? You start filling up your desktop with images boot.img, .exe files OST LA bizarre programme... You try to open the nokia 3.2 to search 2 pins to enable eld supermode-mode with no chance 'cause you are not strong enough and it is really well ... glued? MAybe if I pay someone else tou fix it? 140 euros... 120 dollars, no, wait it is reaaaaaly expensive¡¡¡
REAL HINT
Have a try to download HMDSW_DPL_sprout-015B-0-00WW-B01 and search for boot vbmeta and other .img files and flash them manually via fastboot, if you are lucky as me, you may fix the self provocated prob:
PS C:\Users\ike\Desktop> cd platform-tools-new PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash boot \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\boot.img < waiting for any device >
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash boot \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\boot.img Sending 'boot' (65536 KB) OKAY [ 2.072s]
Writing 'boot' OKAY [ 0.620s]
Finished. Total time: 2.692s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash custom \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\custom.img Sending 'custom' (6204 KB) OKAY [ 0.203s]
Writing 'custom' OKAY [ 0.062s]
Finished. Total time: 0.282s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash persist \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\persist.img Sending 'persist' (32768 KB) OKAY [ 1.038s]
Writing 'persist' OKAY [ 0.315s]
Finished. Total time: 1.354s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash system \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\system.img Sending sparse 'system' 1/6 (523260 KB) OKAY [ 16.927s]
Writing 'system' OKAY [ 6.093s]
Sending sparse 'system' 2/6 (523260 KB) OKAY [ 16.899s]
Writing 'system' OKAY [ 6.657s]
Sending sparse 'system' 3/6 (523260 KB) OKAY [ 16.888s]
Writing 'system' OKAY [ 5.328s]
Sending sparse 'system' 4/6 (492416 KB) OKAY [ 15.869s]
Writing 'system' OKAY [ 6.127s]
Sending sparse 'system' 5/6 (502344 KB) OKAY [ 16.201s]
Writing 'system' OKAY [ 4.613s]
Sending sparse 'system' 6/6 (24680 KB) OKAY [ 0.793s]
Writing 'system' OKAY [ 1.132s]
Finished. Total time: 119.152s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash userdata \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\userdata.img Sending 'userdata' (1268 KB) OKAY [ 0.031s]
Writing 'userdata' OKAY [ 0.031s]
Finished. Total time: 0.079s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash vbmeta \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\vbmeta.img Sending 'vbmeta' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.016s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash vendor \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\vendor.img Sending 'vendor' (424560 KB) OKAY [ 13.363s]
Writing 'vendor' OKAY [ 3.931s]
Finished. Total time: 17.497s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot reboot Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
PS C:\Users\ike\Desktop\platform-tools-new>
I'm willing to help, as far as I have to stay home because of a biological hacking. And if you do not know what are you doing or you are not confident, do not do it. Thanks
hello
can you please explain step by step?
thank you
kntb said:
hello
can you please explain step by step?
thank you
Click to expand...
Click to collapse
First tell me what have you done so far
Hi
Thanks for guide
but I am unable boot after following all above steps
Just as a tip: I once got mine soft-bricked (that was a scary one. No partitions, can't flash, boot, or erase anything at all, even saw the linux penguin logo instead of "Android One"), but after lots of googling i decided to check my active slot, turned out it was something like "UNAVAILABLE" (or so)
So I just set my active slot to A (or B, doesn't matter) and I recovered everything.
Hi guys,
Recently after a
fastboot boot twrp-3.3.1-test43-hotdog-unified-mauronofrio.img
Click to expand...
Click to collapse
I'm stuck in a bootloop. I would like to specify that I ran the twrp checked if I was able to flash something but I saw that I was not able to flash anything because my phone doesn't have the root I rebooted the phone, and from that moment I cannot run the os at all. I'm able to go to the fastboot and I'm able to run the twrp and the recovery.
I tried to reflash the boot only but without success. At this moment I tried to reinstall all the system 10.0.9 but I received this message:
Do you want to wipe all the data ( Reccomended )[Y/N]?n
Sending 'boot_b' (98304 KB) OKAY [ 2.785s]
Writing 'boot_b' OKAY [ 0.468s]
Finished. Total time: 3.700s
Sending 'dtbo' (16384 KB) OKAY [ 0.473s]
Writing 'dtbo' OKAY [ 0.043s]
Finished. Total time: 0.621s
Sending 'modem_b' (166356 KB) OKAY [ 4.741s]
Writing 'modem_b' OKAY [ 0.686s]
Finished. Total time: 6.146s
Sending 'reserve' (250136 KB) OKAY [ 7.109s]
Writing 'reserve' FAILED (remote: '(reserve_b)
No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 2.794s]
Writing 'recovery' OKAY [ 0.353s]
Finished. Total time: 3.314s
Sending 'vbmeta' (8 KB) OKAY [ 0.013s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.039s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.034s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 9.956s
Sending 'abl_b' (1164 KB) OKAY [ 0.036s]
Writing 'abl_b' OKAY [ 0.013s]
Finished. Total time: 0.071s
Sending 'aop_b' (200 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.041s
Sending 'bluetooth_b' (828 KB) OKAY [ 0.025s]
Writing 'bluetooth_b' OKAY [ 0.011s]
Finished. Total time: 0.057s
Sending 'cmnlib_b' (384 KB) OKAY [ 0.012s]
Writing 'cmnlib_b' OKAY [ 0.008s]
Finished. Total time: 0.036s
Sending 'cmnlib64_b' (500 KB) OKAY [ 0.015s]
Writing 'cmnlib64_b' OKAY [ 0.009s]
Finished. Total time: 0.042s
Sending 'devcfg_b' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.006s]
Finished. Total time: 0.022s
Sending 'dsp_b' (65536 KB) OKAY [ 1.919s]
Writing 'dsp_b' OKAY [ 0.335s]
Finished. Total time: 2.553s
Sending 'hyp_b' (480 KB) OKAY [ 0.015s]
Writing 'hyp_b' OKAY [ 0.007s]
Finished. Total time: 0.041s
Sending 'imagefv_b' (20 KB) OKAY [ 0.001s]
Writing 'imagefv_b' OKAY [ 0.006s]
Finished. Total time: 0.022s
Sending 'keymaster_b' (248 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.007s]
Finished. Total time: 0.034s
Sending 'LOGO_b' (6540 KB) OKAY [ 0.195s]
Writing 'LOGO_b' OKAY [ 0.046s]
Finished. Total time: 0.284s
Sending 'multiimgoem_b' (16 KB) OKAY [ 0.001s]
Writing 'multiimgoem_b' OKAY [ 0.006s]
Finished. Total time: 0.030s
Resizing 'odm_b' OKAY [ 0.006s]
Sending 'odm_b' (912 KB) OKAY [ 0.028s]
Writing 'odm_b' FAILED (Status read failed (T
oo many links))
fastboot: error: Command failed
Sending 'oem_stanvbk' (876 KB) FAILED (Write to device faile
d (No such file or directory))
fastboot: error: Command failed
Sending 'opproduct' (612316 KB) FAILED (Write to device faile
d (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'qupfw' (72 KB) OKAY [ 0.012s]
Writing 'qupfw' OKAY [ 0.003s]
Finished. Total time: 0.042s
Sending 'storsec' (24 KB) OKAY [ 0.007s]
Writing 'storsec' OKAY [ 0.003s]
Finished. Total time: 0.032s
Sending 'tz' (3092 KB) OKAY [ 0.096s]
Writing 'tz' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.011s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.037s
Sending 'xbl' (3120 KB) OKAY [ 0.094s]
Writing 'xbl' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.014s]
Writing 'xbl_config' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 23.363s]
Writing 'system' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 23.425s]
Writing 'vendor' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785428 KB) OKAY [ 23.379s]
Writing 'product' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
Premere un tasto per continuare . . .
Click to expand...
Click to collapse
Unfortunately, all these attempts failed. In the past, I tried the rooting. After the first period, it worked properly but I was not able to re-install magisk boot file as it was not recognized by the magisk app. I don't remember if there were some magisk module.
I don't know if this helps, please assist. If the topic is in the wrong section, please move it.
Thank you in advance for your help.
Gorthan said:
Hi guys,
Recently after a
I'm stuck in a bootloop. I would like to specify that I ran the twrp checked if I was able to flash something but I saw that I was not able to flash anything because my phone doesn't have the root I rebooted the phone, and from that moment I cannot run the os at all. I'm able to go to the fastboot and I'm able to run the twrp and the recovery.
I tried to reflash the boot only but without success. At this moment I tried to reinstall all the system 10.0.9 but I received this message:
Unfortunately, all these attempts failed. In the past, I tried the rooting. After the first period, it worked properly but I was not able to re-install magisk boot file as it was not recognized by the magisk app. I don't remember if there were some magisk module.
I don't know if this helps, please assist. If the topic is in the wrong section, please move it.
Thank you in advance for your help.
Click to expand...
Click to collapse
Try to install again the rom, and when the device reboot itself in recovery don't reboot it
thanks so much for your reply.
I realized that with the twrp I selected the partition A and I reinstalled the rom again and the system restarted. Now I'll try to restore the partition B. (But in meantime I'm performing a backup all the data ).
Update: I reinstalled the system in the Partition B and works properly.
mauronofrio said:
Try to install again the rom, and when the device reboot itself in recovery don't reboot it
Click to expand...
Click to collapse
thanks so much for your reply. I followed your advice and actually helps.
I realized that with the twrp I selected the partition A and I reinstalled the rom again and the system restarted. I'll try to restore the partition B. (But in meantime I'm performing a backup all the data ).
Update: I reinstalled the system in Partition B and works properly.
Update 2: I finally spend a bit of time on the phone and I already rooted. Thanks to @mauronofrio for help.