Develop Bugs

[Q] Flashing with Linux

Hi there!
I am completely new to Android. I don't use Windooze (and won't do ), so i am not able to upgrade the arc's Firmware with "Flashtool".
Sadly i have not found a lot information about ".ftf-Files" and the way Flashtool works.
Code:
[email protected] ~/X/LT15i_4.0.1.A.0.283_Generic Global>
file LT15i_4.0.1.A.0.283_Generic\ Global.ftf
LT15i_4.0.1.A.0.283_Generic Global.ftf: Zip archive data, at least v2.0 to extract
extracted, i found a kernel.sin and a system.sin.
I succesfully flashed them with
Code:
fastboot -i 0x0fce flash boot kernel.sin
fastboot -i 0x0fce flash system system.sin
But What about the other files inside of this firmware-archive?
Code:
[email protected] ~/X/LT15i_4.0.1.A.0.283_Generic Global> ls inhalt/
adsp.sin fota0.sin LT15i_4.0.1.A.0.283_Generic Global userdata.sin
amss_fs.sin fota1.sin META-INF/
amss.sin kernel.sin simlock.ta
cache.sin loader.sin system.sin
Is there an image to upgrade that "baseband/radio" thing?
I guess "cache.sin" is the android cache partition and "userdata.sin" is the user partition...
is loader.sin a new Bootloader i should flash?
Greeting
matto

Wine?
Sent from my MT15i using Tapatalk

taaviu said:
Wine?
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
Thanks for your quick replay. I think i have read in the "[TOOL] [UPDATE 14/08/2011] Flashtool version 0.3.0.0" - thread,
http://forum.xda-developers.com/showthread.php?t=920746
that flashtool will launch, but flashing is not working.
I am really not sure if i should give it a new try, wine is known to crash a lot. crashing while flashing a new bootloader might brick the phone...
isnt there anywhere some documentation about those ".ftf firmware containers" and its content?
after some internet research i would guess amss.sin/amss_fs.sin could be the fm-radio rom
http://en.wikipedia.org/wiki/Amplitude_modulation_signalling_system
....

flash amss.sin
Has anyone ever tried
Code:
fastboot -i 0x0fce flash amss amss.sin
or
Code:
fastboot -i 0x0fce flash radio amss.sin
?
I will try this, if someone tells me he could unbrick my phone or tell me how to unbrick it when the arc bricks

muell_matto said:
I am really not sure if i should give it a new try, wine is known to crash a lot. crashing while flashing a new bootloader might brick the phone...
Click to expand...
Click to collapse
I'm also using Linux and I tried running flashtool in Wine. I wasn't able to get it to recognise the phone when I plugged it in so I finally gave up and used my Windows 7 computer at work to flash....
I think that's the safest choice, as I don't think ftf files were meant to be flashed with fastboot. You can, however, use img files with fastboot (unlocked bootloader). Like the 2.3.4 one in this thread, for instance:
http://forum.xda-developers.com/showthread.php?t=1269937

Or you can use vmware to install win 7 within linux...!!! That is the way I flash my phone...!!!
Sent from my LT15i using XDA Premium App

so ... sadly i need to get myself windows ... only to flash my phone. (Dammit )
thanks anyway
ps: I will tell you if i decide to do a risky fastboot baseband update, at last, that is the only missing part of the update.
for other readers who foud this thread using the search function:
Don't get it wrong, you can flash a new firmware with fastboot (linux, mac, whatever-platform the official sdk/platform-tools will be ported to), but without the baseband, which works great for me. how? see the first post.

tried this way and didnt work for me.
first, i lost my baseband.
second, when i tried to flash userdata.sin to userdata, got my phone bricked. any suggest?

blackbiron said:
tried this way and didnt work for me.
first, i lost my baseband.
second, when i tried to flash userdata.sin to userdata, got my phone bricked. any suggest?
Click to expand...
Click to collapse
Hi!
What exactly did you do?
(Do you remember the outout or ... maybe saved it?)
regarding "userdata.sin"-brick , have you tried
Code:
fastboot -i 0x0fce erase userdata
and
Code:
fastboot -i 0x0fce erase cache
?
greetings

risky fastboot baseband update
muell_matto said:
ps: I will tell you if i decide to do a risky fastboot baseband update, at last, that is the only missing part of the update.
Click to expand...
Click to collapse
If someone is interested:
I tried to apply the remaining part of the update with fastboot...
It seems like
[a] It is not possible
or
SE chooses weird, hard to guess partition-names​
Code:
[[email protected] inhalt]$ fastboot -i 0x0fce flash amss amss.sin
sending 'amss' (17612 KB)... INFOUSB download speed was 2003916kB/s
OKAY
writing 'amss'... INFOFlash of partition 'amss' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash amss_fs amss_fs.sin
sending 'amss_fs' (62 KB)... INFOUSB download speed was 9166kB/s
OKAY
writing 'amss_fs'... INFOFlash of partition 'amss_fs' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash adsp adsp.sin
sending 'adsp' (5287 KB)... INFOUSB download speed was 9334kB/s
OKAY
writing 'adsp'... INFOFlash of partition 'adsp' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash fota0 fota0.sin
sending 'fota0' (1470 KB)... INFOUSB download speed was 9353kB/s
OKAY
writing 'fota0'... INFOFlash of partition 'fota0' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash fota1 fota1.sin
sending 'fota1' (1470 KB)... INFOUSB download speed was 125493kB/s
OKAY
writing 'fota1'... INFOFlash of partition 'fota1' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash loader loader.sin
sending 'loader' (98 KB)... INFOUSB download speed was 8382kB/s
OKAY
writing 'loader'... INFOFlash of partition 'loader' requested
FAILED (remote: Partition not found)

Not sure if you tried this or not but what about looking in the META-INF directory? It could help...

adiktz said:
Or you can use vmware to install win 7 within linux...!!! That is the way I flash my phone...!!!
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
I have win7 on my vmware, and flashtools is reading the device but I got abort msg and wont flash any thing, can you help me how to configure it ?
(( xperia x8 )

sultan-mrm said:
I have win7 on my vmware, and flashtools is reading the device but I got abort msg and wont flash any thing, can you help me how to configure it ?
(( xperia x8 )
Click to expand...
Click to collapse
Use the latest flashtool or place Lt15 loader in the loader folder of the flashtools...!!!
Download nd extract the attachment...!!!
Post a screen shot please...!!! That would make helping you easy...!!!

adiktz said:
Use the latest flashtool or place Lt15 loader in the loader folder of the flashtools...!!!
Download nd extract the attachment...!!!
Post a screen shot please...!!! That would make helping you easy...!!!
Click to expand...
Click to collapse
I will try once get back my Laptop
Thanks man

@adiktz
it's not work
see attached screen shot.

muell_matto said:
If someone is interested:
I tried to apply the remaining part of the update with fastboot...
It seems like
[a] It is not possible
or
SE chooses weird, hard to guess partition-names​
Code:
[[email protected] inhalt]$ fastboot -i 0x0fce flash amss amss.sin
sending 'amss' (17612 KB)... INFOUSB download speed was 2003916kB/s
OKAY
writing 'amss'... INFOFlash of partition 'amss' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash amss_fs amss_fs.sin
sending 'amss_fs' (62 KB)... INFOUSB download speed was 9166kB/s
OKAY
writing 'amss_fs'... INFOFlash of partition 'amss_fs' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash adsp adsp.sin
sending 'adsp' (5287 KB)... INFOUSB download speed was 9334kB/s
OKAY
writing 'adsp'... INFOFlash of partition 'adsp' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash fota0 fota0.sin
sending 'fota0' (1470 KB)... INFOUSB download speed was 9353kB/s
OKAY
writing 'fota0'... INFOFlash of partition 'fota0' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash fota1 fota1.sin
sending 'fota1' (1470 KB)... INFOUSB download speed was 125493kB/s
OKAY
writing 'fota1'... INFOFlash of partition 'fota1' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash loader loader.sin
sending 'loader' (98 KB)... INFOUSB download speed was 8382kB/s
OKAY
writing 'loader'... INFOFlash of partition 'loader' requested
FAILED (remote: Partition not found)
Click to expand...
Click to collapse
thanks for this courageous test!:good:, I was wondering about this...
I still have another idea...
in my xperia neo v it seems that some so called "partitions" are not really partitions but areas maped in the hardware (Nand)ROM memory.
For example it is true for the "/boot" and kernel image that can't be found anywhere (at lest in my stock installation), but when you use "fastboot flash boot kernel.sin" it is able to find in the correct place to put the kernel image on the correct internal block of rom address.
So for the baseband, I was just wondering that maybe the solution would be concatenating the 03 sin files using something like the linux dd comand (no idea about the order of the sin files) into a unique image file, lets say "bb.img", and then flashing it using fastboot with a special name of baseband partition (something like radio, modem, baseband, who knows what this name could be?...:crying and then use a commmand like:
fastboot flash part_name bb.img
Sorry for not having an answer,
I'm just sharing my wondering because I saw that you are so curious about this stuff like me!!

[Q] Can't flash doomkernel, waiting for device

Hey all,
Just nuked my phone set up so I could install the latest doomkernel (first time wanted to try it out) on my GSM play running latest SE software, but it refuses to flash the boot.img file to the device.
I unlocked (after a re-lock a while ago) the boot loader and can access fastboot (blue LED on phone, "fastboot.exe -i 0x0fce getvar version" brings a version 0.3)
fastboot.exe flash boot boot.img ---> stuck on "< waiting for device >" message
I tried with the latest flashtool and I got this from the log:
Code:
05/046/2012 00:46:31 - INFO - Device connected in fastboot mode
05/046/2012 00:46:42 - INFO - Selected kernel (boot.img or kernel.sin): C:\boot.img
05/046/2012 00:46:42 - INFO - Flashing selected kernel
05/046/2012 00:46:43 - INFO - FASTBOOT Output:
sending 'boot' (7330 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
I then rooted the phone using zergrush and it's rooted properly, but I can't for the life of me figure out why I can't push the kernel, since I know the fastboot process is working because I used it to unlock the boot loader
Code:
C:\Users\Access\Downloads>fastboot.exe -i 0x0fce oem unlock 0x
< waiting for device >
... INFOUnlock phone requested
INFOErasing block 0x00000d00
INFOErasing block 0x00000e00
INFOErasing block 0x00000f00
Is there something I'm missing or will I never be able to have a custom kernel?
Any ideas and suggestions appreciated thanks

I have the exact same problem with my Arc S, can`t figure out why is getting stuck on "< waiting for device >"

Try fastboot -i 0x0fce flash boot boot.img

Michealtbh said:
Try fastboot -i 0x0fce flash boot boot.img
Click to expand...
Click to collapse
Thx alot man, it worked like a charm !
Code:
C:\Android>fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Android>fastboot -i 0x0fce flash boot boot.img
sending 'boot' (7922 KB)... INFOUSB download speed was 9187kB/s
OKAY [ 0.892s]
writing 'boot'... INFODownload buffer format: boot IMG
INFOFlash of partition 'boot' requested
INFOS1 partID 0x00000003, block 0x00000280-0x000002e3
INFOErase operation complete, 0 bad blocks encountered
INFOFlashing...
INFOFlash operation complete
OKAY [ 1.532s]
finished. total time: 2.424s

TWRP - Failed to mount '/firmware' (invalid argument)

I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!

gocks said:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
Click to expand...
Click to collapse
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.

dandrumheller said:
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
Click to expand...
Click to collapse
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??

gocks said:
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
Click to expand...
Click to collapse
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using
Click to expand...
Click to collapse
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.

gocks said:
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
Click to expand...
Click to collapse
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.

gocks said:
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
Click to expand...
Click to collapse
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!

gocks said:
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
Click to expand...
Click to collapse
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did exactly what you told me and this happened:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.683s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10820 KB)...
OKAY [ 0.235s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.235s]
finished. total time: 0.501s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257307 KB)...
OKAY [ 5.493s]
writing 'system'...
OKAY [ 3.985s]
finished. total time: 9.478s
The othes lines seems to be ok, but the phone continue stucked on the "Your device has been unlock...." and don´t reboot.

Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.

gocks said:
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
Click to expand...
Click to collapse
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.

gocks said:
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
Click to expand...
Click to collapse
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws

flashallthetime said:
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
Click to expand...
Click to collapse
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?

gocks said:
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
Click to expand...
Click to collapse
Which carrier are you with?
And don't sue me if things get worse

flashallthetime said:
Which carrier are you with?
And don't sue me if things get worse
Click to expand...
Click to collapse
Vivo, its a brazilian one.
Relax, if my phone bricks I wont sue you because my wife will kill me first!

I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat

gocks said:
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
Click to expand...
Click to collapse
Yes and it seems like you can't right to the system and or data partitions. There's more partitions but they're locked or hidden
Try to format your data in TWRP
and wipe system

Help - maybe I bricked my Hydrogen - don't dare to power on

Hi guys, I have just flashed a new TWRP from the command line and wanted to boot to it with fastboot using "fastboot boot recovery.img". Unfortunately I did not pay enough attention when recalled the original command from the CLI and issued "fastboot flash boot recovery.img" instead of the correct "fastboot boot recovery.img" command. The device is still in fastboot mode - how can I restore boot? This was the output of the command:
c:\Program Files (x86)\totalcmd\plugins\wfx\ADB\bin>fastboot flash boot e:\Letöltések\twrp_v3111_hydrogen-helium_nijel8-MOD_A7.1.2.img
target reported max download size of 536870912 bytes
sending 'boot' (16176 KB)...
OKAY [ 0.569s]
writing 'boot'...
OKAY [ 0.230s]
finished. total time: 0.803s
Any help is appreciated - I am scared ****less.
Edit: extracted boot.img from the flashable .zip of the ROM I originally wanted to flash and flashed it with fastboot, hope it works

Question [SOLVED]Mi 11 lte 5g ne bricked(?)

after an unsuccessful firmware of my device, it started to boot constantly in fastboot mode. when I try to restore via miflash and xiaomi tool v2, I get the error "Flash super error". how to solve this problem?
P.S. : sorry if something is written incorrectly, I wrote through a translator

Hi,
did you look at this topic ?

newbie_or_not_newbie said:
Hi,
did you look at this topic ?
Click to expand...
Click to collapse
yes, they advised me to install the xiaomi.eu firmware, but I get the error of flashing the partition (?) "super"
Sending sparse 'super' 1/9 (729624 KB) OKAY [ 16.439s]
Writing 'super' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing 'metadata' FAILED (remote: 'failed to check sparse crc')
fastboot: error: Command failed

try to delete shares and data from adb fastboot
fastboot erase recovery
fastboot erase system –w
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase cache
then flash the rom

WaldoVM said:
try to delete shares and data from adb fastboot
fastboot erase recovery
fastboot erase system –w
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase cache
then flash the rom
Click to expand...
Click to collapse
thats work!!
thanks bro