I have a Razr HD (my dad's) he took the newest update last week and now he is stuck at the boot logo.(I have told him to not do it) ADB screen is telling me it is unlocked at stats code 3, (I think a dev edition, he bought it used) now I can't get it to take a recovery to flash stock 4.4.2. I tried this script here (http://forum.xda-developers.com/showthread.php?t=2474393) but it wouldn't restore it to stock and let me use the phone.
Any ideas from the android gurus.
Latheman said:
I have a Razr HD (my dad's) he took the newest update last week and now he is stuck at the boot logo.(I have told him to not do it) ADB screen is telling me it is unlocked at stats code 3, (I think a dev edition, he bought it used) now I can't get it to take a recovery to flash stock 4.4.2. I tried this script here (http://forum.xda-developers.com/showthread.php?t=2474393) but it wouldn't restore it to stock and let me use the phone.
Any ideas from the android gurus.
Click to expand...
Click to collapse
is this a 926 or 925
if 926
use rsd lite and this guide form @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 i would recommend the full script since you are already unlocked and it was a used phone
if 925
same procedure but with the correct sbf from http://sbf.droid-developers.org/
I did this earlier. Same problem
Latheman said:
I did this earlier. Same problem
Click to expand...
Click to collapse
try this utility. it is a special version to fix certain issues that cant be fixed with fastboot and rsd.
watch the dialog and let me know if any operations fail, or copy and paste the output here for me to see.
i may have to update it for you if a couple specific things fail.
windows or linux?
Latheman said:
windows or linux?
Click to expand...
Click to collapse
windows only
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Latheman said:
windows or linux?
Click to expand...
Click to collapse
flash in fastboot same as the rest.
OK thanks. give me 10 minuets
this phone has the 9/9/14 update that won't be a problem right? just making sure
Latheman said:
this phone has the 9/9/14 update that won't be a problem right? just making sure
Click to expand...
Click to collapse
it wont be a problem, but some parts will fail. im downloading the files now to compare the parts i would like to see work.
either way, try that for now and let me know how it goes. there should be no added danger, the trust zone and partition files are what could fail, neither can be downgraded, so i dont see it making things worse if it doesnt work.
the phone says update gpt-main partition failed then the terminal end is FAILED (remote failure)
here is the output on the computer, sorry it is so long
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.156s
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.187s
sending 'sbl2' (126 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.172s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.370s
sending 'rpm' (140 KB)...
OKAY [ 0.029s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.315s
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.200s
sending 'aboot' (256 KB)...
OKAY [ 0.039s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.346s
sending 'modem' (30720 KB)...
OKAY [ 2.299s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.464s
sending 'fsg' (165 KB)...
OKAY [ 0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.187s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.083s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
sending 'logo' (854 KB)...
OKAY [ 0.083s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.238s
sending 'boot' (10240 KB)...
OKAY [ 0.781s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.929s
sending 'recovery' (10240 KB)...
OKAY [ 0.805s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.969s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
sending 'system' (30720 KB)...
OKAY [ 2.357s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 2.447s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.188s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.009s
Hit ENTER to return.
Latheman said:
here is the output on the computer, sorry it is so long
Click to expand...
Click to collapse
dammm
my file is almost done, let me compare a couple md5's from the old update and ill get right back to ya with what it looks like.
---------- Post added at 06:35 PM ---------- Previous post was at 06:24 PM ----------
@Latheman
ok, they changed the partition table again, not saying the phone is fixable, but this is the best chance i could have wanted to fix it.
its going to take me 1/2 hour to fix the script, and an hour (barring issue) to upload it.
ill send it over as soon as its done, if not tonight, then tomorrow.
Thank-you
Latheman said:
Thank-you
Click to expand...
Click to collapse
test flash on my updated phone, only tz failed because i removed it, but will be in your version as you already took it.
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.015s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.859s]
finished. total time: 0.874s
sending 'sbl1' (101 KB)...
OKAY [ 0.019s]
writing 'sbl1'...
OKAY [ 0.648s]
finished. total time: 0.668s
sending 'sbl2' (127 KB)...
OKAY [ 0.183s]
writing 'sbl2'...
OKAY [ 1.033s]
finished. total time: 1.216s
sending 'sbl3' (512 KB)...
OKAY [ 0.052s]
writing 'sbl3'...
OKAY [ 1.113s]
finished. total time: 1.165s
sending 'rpm' (140 KB)...
OKAY [ 0.023s]
writing 'rpm'...
OKAY [ 0.473s]
finished. total time: 0.496s
error: cannot load 'tz.mbn'
sending 'aboot' (256 KB)...
OKAY [ 0.193s]
writing 'aboot'...
OKAY [ 1.594s]
finished. total time: 1.788s
sending 'modem' (30720 KB)...
OKAY [ 2.320s]
writing 'modem'...
OKAY [ 2.680s]
sending 'modem' (19212 KB)...
OKAY [ 3.845s]
writing 'modem'...
OKAY [ 1.095s]
finished. total time: 9.944s
sending 'fsg' (165 KB)...
OKAY [ 0.027s]
writing 'fsg'...
OKAY [ 0.855s]
finished. total time: 0.882s
erasing 'modemst1'...
OKAY [ 1.698s]
finished. total time: 1.699s
erasing 'modemst2'...
OKAY [ 1.232s]
finished. total time: 1.232s
sending 'logo' (854 KB)...
OKAY [ 0.076s]
writing 'logo'...
OKAY [ 1.955s]
finished. total time: 2.032s
sending 'boot' (10240 KB)...
OKAY [ 0.784s]
writing 'boot'...
OKAY [ 5.946s]
finished. total time: 6.730s
sending 'recovery' (10240 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 4.749s]
finished. total time: 5.530s
sending 'system' (30720 KB)...
OKAY [ 2.324s]
writing 'system'...
OKAY [ 2.254s]
sending 'system' (30720 KB)...
OKAY [ 5.467s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.717s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.697s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.707s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.223s]
writing 'system'...
OKAY [ 0.015s]
sending 'system' (30720 KB)...
OKAY [ 4.727s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.707s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.712s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.983s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.718s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.729s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.646s]
writing 'system'...
OKAY [ 0.023s]
sending 'system' (30720 KB)...
OKAY [ 5.097s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 5.140s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.697s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.662s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.712s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.067s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.677s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.682s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.696s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 5.232s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.717s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.636s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.703s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.750s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.715s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.701s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.703s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 5.604s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.694s]
writing 'system'...
OKAY [ 0.018s]
sending 'system' (30720 KB)...
OKAY [ 4.708s]
writing 'system'...
OKAY [ 0.018s]
sending 'system' (30720 KB)...
OKAY [ 4.710s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.034s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.686s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (21722 KB)...
OKAY [ 4.040s]
writing 'system'...
OKAY [ 1.323s]
finished. total time: 285.670s
erasing 'tombstones'...
OKAY [ 2.049s]
finished. total time: 2.049s
erasing 'cache'...
OKAY [ 2.632s]
finished. total time: 2.632s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.005s
Hit ENTER to return.
so what should I do? remove a file from the folder you sent me?
Latheman said:
so what should I do? remove a file from the folder you sent me?
Click to expand...
Click to collapse
no, i was just showing you the new version is built, tested, working and uploading now.
so, when i post it later for you to try, this is pretty much a last resort script. if it doesn't work for you, the phone is likely gone.
---------- Post added at 07:42 PM ---------- Previous post was at 07:05 PM ----------
Latheman said:
so what should I do? remove a file from the folder you sent me?
Click to expand...
Click to collapse
ok she is done
http://www.mediafire.com/download/5mmd0jv84c51rvt/DROID_RAZR_HD_Utility_1.4gpt-2a_KK.rar
edit: just changed the download link to another version containing the tz file i forgot to replace, for whoever might need it in the future.
Thanks I'll try it soon.
Latheman said:
Thanks I'll try it soon.
Click to expand...
Click to collapse
i forgot to drop the tz file back in before i uploaded it, its no big deal and shouldnt matter, but you should drop this into the directory in the rare event it becomes needed.
https://www.dropbox.com/s/f27cfsjyewlnlu4/tz.mbn?dl=0
I tried it, and no soap, I think this one is a loss . (first one of every phone I have worked on). the BL is still unlocked so if anybody ever comes up with something in the future, or I can put something together I might be able to restore it.
Did you try to flash stock with rsd 6.1.5 and editing xml file, say removing tz line
Related
Hi,
my NSdoesnt boot and I cant flash another ROM because my NS cant mount SD anymore, so I tryed to restore it back to stock and flash the .imgs with fastboot. Boot.img, recovery.img, userdata.img, without problems, but the system.img gives me the message "write failed" or something. Tryed it multiple times with the Gingerbread system.img, and ICS system.img, same problem.
I can boot into recovery, but the phone doesnt recognize the SD and also the system partition.
Any solutions?
Sorry for my english.
What recovery you using?
Sent from my Nexus S using xda app-developers app
Tried 2 different CMW Recoveries, it's not a recovery problem. My System and SD storage is corrupt or something, I think.
It can't be all that corrupt as you are able to install boot loader and recovery. Try and adb sideload CyanogenMod 10.1. Once you got a booting phone, things tend to play nicely.
Sent from my Nexus S using xda app-developers app
Just tried the adb sideload method.
"Installing update..." for 5 Minutes now. I think it cant write on /system.
I've also tried to erase /system partition via fastboot it gives me also the "failed" message.
system.img write fail error
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
I've had a similar experience when installing stock ROMs after installing cwm and cm 10. Can you guys not even install cm10?
Sent from my Nexus S using xda app-developers app
Deus Tempestas said:
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
Click to expand...
Click to collapse
Same problem here! Did u find solution?
Code:
C:\Users\metroPCS01\Desktop\adb>fastboot flash modem NON-HLOS.bin
sending 'modem' (56369 KB)... OKAY
writing 'modem'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (295 KB)... OKAY
writing 'sbl1'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash dbi sdi.mbn
sending 'dbi' (11 KB)... OKAY
writing 'dbi'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
sending 'aboot' (376 KB)... OKAY
writing 'aboot'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash rpm rpm.mbn
sending 'rpm' (185 KB)... OKAY
writing 'rpm'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash tz tz.mbn
sending 'tz' (283 KB)... OKAY
writing 'tz'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash LOGO logo.bin
sending 'LOGO' (9591 KB)... OKAY
writing 'LOGO'... OKAY
C:\Users\metroPCS01\Desktop\adb>
C:\Users\metroPCS01\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bi
sending 'oppostanvbk' (10240 KB)... OKAY
writing 'oppostanvbk'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash boot boot.img
sending 'boot' (5956 KB)... OKAY
writing 'boot'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash cache cache.img
sending 'cache' (10432 KB)... OKAY
writing 'cache'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash recovery recovery.img
sending 'recovery' (7854 KB)... OKAY
writing 'recovery'... OKAY
C:\Users\metroPCS01\Desktop\adb>fastboot flash system system.img
sending 'system' (844889 KB)... [B]FAILED (remote: data too large)[/B]
I am trying to flash m-11.0-XNPH05Q-bacon-signed-fastboot.zip but I keep encountering this error. Now I am stuck on the android logo. Any help would be really appreciated. Thanks
You need to update your adb/fastboot, how did you install it? If you didn't install it with the Android SDK you need to uninstall it and then install it with the Android SDK.
Transmitted via Bacon
Same problem!
hi i got the same problem! seacrhing topics, trying but nothing work:
sending 'modem' (56369 KB)...
OKAY [ 3.610s]
writing 'modem'...
OKAY [ 1.026s]
finished. total time: 4.637s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'sbl1' (295 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.011s]
finished. total time: 0.029s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.006s]
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'aboot' (376 KB)...
OKAY [ 0.023s]
writing 'aboot'...
OKAY [ 0.024s]
finished. total time: 0.047s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'rpm' (185 KB)...
OKAY [ 0.011s]
writing 'rpm'...
OKAY [ 0.008s]
finished. total time: 0.019s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'tz' (283 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.014s]
finished. total time: 0.030s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'LOGO' (9591 KB)...
OKAY [ 0.557s]
writing 'LOGO'...
OKAY [ 0.190s]
finished. total time: 0.747s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.669s]
writing 'oppostanvbk'...
OKAY [ 0.207s]
finished. total time: 0.876s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 15ee5ede
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot' (5956 KB)...
OKAY [ 0.346s]
writing 'boot'...
OKAY [ 0.114s]
sending 'recovery' (7854 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.156s]
sending 'system' (844889 KB)...
FAILED (remote: data too large)
finished. total time: 1.168s
install android-sdk from site working onlinux mint 17.1 javajdk7 what i can do
Hi there,
First, sorry for my english.
I'm not a newbie in rooting, but it's the first time i've got a N5. So, after getting my N5, the phone update to 4.4.4, after to 5.0.1 and after to 5.1.1.
After that, i've flash CWM, but i don't know why but this method give me many error (like the /sdcard cannot be mounted, etc) and i'm in a bootloop. So i've install TWRP, and i've see something weird, it's like all the folder /system, /data, etc cannot be mount because is not there.
So, i'Ve decide to download the factory image 5.1.1 (LMY48B) of the N5, and execute the "flash-all.bat", but it's stock to "writing 'system' ...
sending 'bootloader' (3119 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
OKAY [ 0.500s]
finished. total time: 0.719s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
sending 'radio' (45425 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 3.235s]
finished. total time: 4.797s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: (sorry it's personal)
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.109s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8980 KB)...
OKAY [ 0.501s]
writing 'boot'...
OKAY [ 0.766s]
sending 'recovery' (9696 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 0.798s]
sending 'system' (1021744 KB)...
OKAY [ 32.562s]
writing 'system'...
Click to expand...
Click to collapse
What's the problem????
Try flashing the individual files separately
Sent from my Nexus 5 using Tapatalk
Today I tried to install lineageOS on my Oneplus nord, without succeeding. In addition to failing, I caused some problems.
What I did
1: fastboot flashing unlock
2 twrp: https://forum.xda-developers.com/t/...ficial-twrp-for-oneplus-nord-testing.4142149/
3: i tried to install the official lineage os without succeeding. to try to succeed i reset the phone from twrp, but nothing. it gives errors
4: rebooting, the phone no longer has a room and starts twrp. doing several tests I lock and unlock the device.
5: then i tried to reinstall oxugenOS with twrp, but nothing it gives the same errors as when i tried with lineage os
6: i tried and install oxugenOS like this (with ubuntu) https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/ but it gives the following errors:
Spoiler
Sending 'boot_b' (98304 KB) OKAY [ 2.920s]
Writing 'boot_b' OKAY [ 0.473s]
Finished. Total time: 3.466s
Sending 'dtbo' (8192 KB) OKAY [ 0.233s]
Writing 'dtbo' OKAY [ 0.025s]
Finished. Total time: 0.276s
Sending 'modem_b' (153804 KB) OKAY [ 4.486s]
Writing 'modem_b' OKAY [ 0.724s]
Finished. Total time: 5.263s
Sending 'recovery' (102400 KB) OKAY [ 2.977s]
Writing 'recovery' OKAY [ 0.540s]
Finished. Total time: 3.588s
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.017s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.012s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 7.838s
< waiting for any device >
Sending 'abl_b' (1996 KB) OKAY [ 0.057s]
Writing 'abl_b' OKAY [ 0.016s]
Finished. Total time: 0.079s
Sending 'aop_b' (192 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.005s]
Finished. Total time: 0.014s
Sending 'bluetooth_b' (220 KB) OKAY [ 0.007s]
Writing 'bluetooth_b' OKAY [ 0.006s]
Finished. Total time: 0.016s
Sending 'devcfg_b' (44 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.004s]
Finished. Total time: 0.009s
Sending 'dsp_b' (65536 KB) OKAY [ 1.914s]
Writing 'dsp_b' OKAY [ 0.399s]
Finished. Total time: 2.355s
Sending 'featenabler_b' (88 KB) OKAY [ 0.004s]
Writing 'featenabler_b' OKAY [ 0.005s]
Finished. Total time: 0.012s
Sending 'hyp_b' (404 KB) OKAY [ 0.012s]
Writing 'hyp_b' OKAY [ 0.006s]
Finished. Total time: 0.021s
Sending 'imagefv_b' (524 KB) OKAY [ 0.018s]
Writing 'imagefv_b' OKAY [ 0.007s]
Finished. Total time: 0.028s
Sending 'keymaster_b' (232 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending 'logo_b' (6532 KB) OKAY [ 0.188s]
Writing 'logo_b' OKAY [ 0.060s]
Finished. Total time: 0.258s
Sending 'oem_stanvbk' (2108 KB) OKAY [ 0.060s]
Writing 'oem_stanvbk' OKAY [ 0.017s]
Finished. Total time: 0.083s
Sending 'odm' (916 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.005s]
Finished. Total time: 0.011s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz_b' (3104 KB) OKAY [ 0.096s]
Writing 'tz_b' OKAY [ 0.024s]
Finished. Total time: 0.126s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.005s]
Finished. Total time: 0.013s
Sending 'xbl_b' (3256 KB) OKAY [ 0.098s]
Writing 'xbl_b' OKAY [ 0.067s]
Finished. Total time: 0.171s
Sending 'xbl_config_b' (80 KB) OKAY [ 0.003s]
Writing 'xbl_config_b' OKAY [ 0.008s]
Finished. Total time: 0.014s
Invalid sparse file format at header magic
Sending sparse 'system' 1/4 (523157 KB) OKAY [ 16.625s]
Writing 'system' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/3 (519986 KB) OKAY [ 16.454s]
Writing 'vendor' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/3 (523058 KB) OKAY [ 16.814s]
Writing 'product' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.051s
in a nutshell it can't read the partition: odm, system, vendor, product
Someone help me i dont know what to do.
It seems you fixed it yourself trying using the unbrick tool, congratulations
solved: https://forum.xda-developers.com/t/...vice-to-oxygenos.4148415/page-4#post-85282065
Hello, Im relatively new to this kinda things, but i wanted to flash my Moto g8 plus to run LineageOS. saddly I have not gotten it to work, and now I want to reflash it with the original rom. I got the needed files, but now It won't flash anything.
My device is shown by fastboot.
[email protected]:~/Android/Sdk/platform-tools$ sudo ./fastboot devices
ZY227BZ9Q8 fastboot
here for example Im trying to flash the bootloader, I get the same error for anything that I try to flash
[email protected]:~/Android/Sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) FAILED (Write to device failed (No such device))
fastboot: error: Command failed
Does Anybody has a good Idea what I can do next?
Its the next day and for no reason flashing works again, but I think it doesnt work completly because I dont have the Right image
[email protected]:~/Android/Sdk/platform-tools$ ./flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.005s]
Finished. Total time: 0.005s
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.343s]
Finished. Total time: 0.345s
Sending 'bootloader' (14204 KB) OKAY [ 0.362s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 1 vs 15
OKAY [ 0.009s]
Finished. Total time: 0.010s
Sending 'modem_a' (81040 KB) OKAY [ 1.955s]
Writing 'modem_a' OKAY [ 0.349s]
Finished. Total time: 2.305s
Sending 'fsg_a' (10936 KB) OKAY [ 0.264s]
Writing 'fsg_a' OKAY [ 0.105s]
Finished. Total time: 0.370s
Sending 'bluetooth_a' (744 KB) OKAY [ 0.019s]
Writing 'bluetooth_a' OKAY [ 0.056s]
Finished. Total time: 0.075s
Sending 'dsp_a' (32768 KB) OKAY [ 0.792s]
Writing 'dsp_a' OKAY [ 0.174s]
Finished. Total time: 0.967s
Sending 'logo_a' (2864 KB) OKAY [ 0.070s]
Writing 'logo_a' OKAY [ 0.052s]
Finished. Total time: 0.122s
Sending 'boot_a' (65536 KB) OKAY [ 1.585s]
Writing 'boot_a' OKAY [ 0.769s]
Finished. Total time: 2.387s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.197s]
Writing 'dtbo_a' OKAY [ 0.097s]
Finished. Total time: 0.295s
Sending 'system_a' (524284 KB) OKAY [ 12.641s]
Writing 'system_a' OKAY [ 0.001s]
Finished. Total time: 12.642s
Sending 'system_a' (524284 KB) OKAY [ 12.689s]
Writing 'system_a' OKAY [ 0.001s]
Finished. Total time: 15.106s
Sending 'system_a' (524284 KB) OKAY [ 12.664s]
Writing 'system_a' OKAY [ 0.001s]
Finished. Total time: 14.815s
Sending 'system_a' (489100 KB) OKAY [ 11.837s]
Writing 'system_a' OKAY [ 0.001s]
Finished. Total time: 13.967s
Sending 'system_a' (522304 KB) OKAY [ 12.571s]
Writing 'system_a' OKAY [ 0.002s]
Finished. Total time: 14.566s
Sending 'system_b' (524284 KB) OKAY [ 12.636s]
Writing 'system_b' OKAY [ 0.001s]
Finished. Total time: 14.795s
Sending 'system_b' (95452 KB) OKAY [ 2.302s]
Writing 'system_b' OKAY [ 0.002s]
Finished. Total time: 4.617s
Sending 'oem_a' (11940 KB) OKAY [ 0.291s]
Writing 'oem_a' (bootloader) WARNING: oem_a anti rollback downgrade, 1 vs 15
(bootloader) WARNING: oem_a anti rollback downgrade, 1 vs 15
OKAY [ 0.099s]
Finished. Total time: 0.802s
Sending 'oem_b' (7504 KB) OKAY [ 0.181s]
Writing 'oem_b' (bootloader) WARNING: oem_b anti rollback downgrade, 1 vs 15
(bootloader) WARNING: oem_b anti rollback downgrade, 1 vs 15
OKAY [ 0.112s]
Finished. Total time: 0.294s
Sending 'vendor_a' (461332 KB) OKAY [ 12.436s]
Writing 'vendor_a' OKAY [ 2.036s]
Finished. Total time: 14.479s
Erasing 'modemst1' OKAY [ 0.040s]
Finished. Total time: 0.040s
Erasing 'modemst2' OKAY [ 0.040s]
Finished. Total time: 0.040s
Erasing 'carrier' OKAY [ 0.041s]
Finished. Total time: 0.041s
Erasing 'userdata' OKAY [ 0.084s]
Finished. Total time: 0.085s
Erasing 'ddr' OKAY [ 0.044s]
Finished. Total time: 0.044s
Sending 'fsg_a' (10936 KB) OKAY [ 0.267s]
Writing 'fsg_a' OKAY [ 0.099s]
Finished. Total time: 0.367s
Sending 'bluetooth_a' (744 KB) OKAY [ 0.019s]
Writing 'bluetooth_a' OKAY [ 0.072s]
Finished. Total time: 0.091s
OKAY [ 0.002s]
Finished. Total time: 0.002s
Ok flashed another image, and got nor errors this time, but sadly it will only show the battery loading screen
My Phone was just lying around and randomly is Trying to boot
it works!-