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.
Related
Hello everyone. I have some issues with Fastboot. whenever I try to flash recovery.img i get this error. my device is Cherry Mobile Touch xl 2 with android 6.0 and mt6580.
C:\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot flash flash recovery.img
target reported max download size of 134217728 bytes
sending 'flash' (10678 KB)...
OKAY [ 0.266s]
writing 'flash'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.281s
When I try to just boot into custom recovery, everything goes well except that the phone just reboots. it does not boot into custom recovery. I heard it from somewhere that fastboot boot recovery.img command did not work anymore. Is this true?
C:\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.281s]
booting...
OKAY [ 0.063s]
finished. total time: 0.344s
Thank you for your help.
Hi there!
I followed this guide to the letter: https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
When I try to reboot from flashing the recovery I get this:
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11248 KB)...
OKAY [ 0.354s]
writing 'recovery'...
OKAY [ 0.212s]
finished. total time: 0.568s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.354s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.388s
I've searched around the forums (official and here) and there are some random threads with links that are either out of date or broken and don't work. I've tried like 10 different recoveries and every single one gives me this error.
Halp?
I've come from a fully updated 6.0.1 OPX
Bolded text seems to be the root cause and I can't find ANYTHING to solve it.
EDIT: I followed this thread > https://forum.xda-developers.com/xperia-z2/help/guide-idiots-guide-to-root-twrp-t3534647
And it worked perfectly. This thread is solved
So I got a hold of a z2 running MM and I'm trying to install twrp using linux shell.
So first I got this apparently installed right.
Code:
fastboot flash recovery twrp-3.0.1-0.img
sending 'recovery' (11558 KB)...
OKAY [ 0.365s]
writing 'recovery'...
OKAY [ 0.774s]
finished. total time: 1.139s
But then when I try to get to the recovery, this happens...
Code:
fastboot boot twrp-3.0.1-0.img
downloading 'boot.img'...
OKAY [ 0.365s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.417s
Does anyone know what the fix is for this? It's probably something simple that I'm just unaware of.
Thanks for your replies.
The cruel irony about it all, is that right after I got everything set to switch it over to being my main phone, as I inserted the sim card, the sim card slot broke inside
**************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...
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.