Develop Bugs

Infinite Rebooting

I went through the entire process for rooting the incredible 2 (tacoroot + revolutionary). At the very end I perform the final step (everything functioned/responded as expected), I get the following:
c:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 6.736s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 6.740s
--
Now Im trapped in infinite reboots. Please help!

Try renaming to PG32IMG.zip and push it to the root of your sdcard, then boot into the bootloader.
Sent from my Incredible 2 using Tapatalk 2

Thanks!
prototype7 said:
Try renaming to PG32IMG.zip and push it to the root of your sdcard, then boot into the bootloader.
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
Worked like a charm

fastboot oem rebootRUU, then flash the zip
Sent from my R800x using xda app-developers app

I desperately need a guide to flash ROMs and HBOOT Versions

Hi,
i am completely new to flashing ROMs like Android Revolution HD and on the One X. I am well versed and hacked all sorts of stuff on plenty other android devices but this process for the One X proves a bit complicated for me.
Here is my problem: I wish to flash Android Revolution HD which requires me to flash the appropriate firmware package.
So i downloaded SDK Tool from "developer.android.com/sdk/index.html", then i copied 'cmd.exe' and firmware version '3.14.707.24' into the 'platform tools' folder. I followed the guide from flow-wolf.net. But when i get to the part of flashing the firmware, this is what i get:
The system cannot find message text for message number 0x2350 in the message fil
e for Application.
The system cannot find message text for message number 0x2334 in the message fil
e for Application.
C:\Users\Kawshigan\Documents\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\p
latform-tools>fastboot flash zip 3.14.707.24.zip
sending 'zip' (12875 KB)...
OKAY [ 1.981s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.200s
C:\Users\Kawshigan\Documents\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\p
latform-tools>fastboot flash zip 3.14.707.24.zip
sending 'zip' (12875 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
C:\Users\Kawshigan\Documents\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\p
latform-tools>
I really do not know what i am doing wrong here. Anyways, i do not even understand whats going on and how i should flash a firmware. It would be very nice of the folks here if you can guide me.Thanks so very much
Cheers,
K

You need to rename the .zip to firmware.zip
Did you download the correct firmware from here and did you read the OP completely
http://forum.xda-developers.com/showthread.php?t=1957376
And you need to put the bootloader in the RUU mode before flashing the firmware
Fastboot oem rebootRUU

Hi thanks for the reply.i did download the correct firmware.anyways, i seemed to figure it out a few hours before your reply.but you kinda made me understand how the entire htc one x hackery works.now my phone goes as fast and smooth as my s3 with the custom rom.thanks alot for your time!
Sent from my EndeavorU using xda premium

kawshigan said:
Hi thanks for the reply.i did download the correct firmware.anyways, i seemed to figure it out a few hours before your reply.but you kinda made me understand how the entire htc one x hackery works.now my phone goes as fast and smooth as my s3 with the custom rom.thanks alot for your time!
Sent from my EndeavorU using xda premium
Click to expand...
Click to collapse
Ah oke, no problem mate. Glad you got it sorted
CASE CLOSED !
Sent from my GT-P5110 using xda app-developers app

[Q] remote: 02 data length is too large while downgrading my HTC Desire Z

C:\Users\SweetMum\Development diretory Android\adt-bundle-windows-x86_64-2013103
0\sdk\platform-tools>adb reboot bootloader
C:\Users\SweetMum\Development diretory Android\adt-bundle-windows-x86_64-2013103
0\sdk\platform-tools>fastboot devices
SH0ADR207405 fastboot
C:\Users\SweetMum\Development diretory Android\adt-bundle-windows-x86_64-2013103
0\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) erase sector 196609 ~ 197120 (512)
OKAY [ 0.473s]
finished. total time: 0.475s
C:\Users\SweetMum\Development diretory Android\adt-bundle-windows-x86_64-2013103
0\sdk\platform-tools>fastboot flash zip StockRom.zip
sending 'zip' (297545 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.004s
C:\Users\SweetMum\Development diretory Android\adt-bundle-windows-x86_64-2013103
0\sdk\platform-tools>fastboot flash zip StockRom.zip
sending 'zip' (297545 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.004s
C:\Users\SweetMum\Development diretory Android\adt-bundle-windows-x86_64-2013103
0\sdk\platform-tools>fastboot flash zip StockRom.zip
sending 'zip' (297545 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.004s
C:\Users\SweetMum\Development diretory Android\adt-bundle-windows-x86_64-2013103
0\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.360s

Check md5sum
Sent from my Nexus 4 using XDA Premium 4 mobile app

Hmm... and when they're O.K., then what?
Sent from my GT-I9305 using xda app-developers app

Link the guide you are following
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Link the guide you are following
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi. thanks for reply.
Well, I tried to merge guide mentioned here, I mean http://forum.cyanogenmod.com/topic/15623-how-to-fix-a-semi-bricked-g2/
with files from CM site http://wiki.cyanogenmod.org/w/HTC_Desire_Z:_Firmware_Downgrade_%28Gingerbread%29
and I've got reply from fastboot:
"FAILED (remote: 02 data length is too large)".
Shall I use other files or just flash hboot only with Your guide? http://forum.xda-developers.com/showthread.php?t=1728208

Can you write down all info on bootloader screen
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Can you write down all info on bootloader screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hello again!
Thanks for Your help. I used simply your guide about flashing hboot with fastboot. I used only a good hboot and it helped!
Thanks a lot again!

demkantor said:
Check md5sum
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got help from # g2root I was instructed to flash a ROM met for G2 not Desire Z as my phone is a G2 and will not accepts ROMs for Desire Z which are larger than G2 ROMs. It worked and now I'm happy. Thanks demkantor for taking interest in my case.

[DUMP][DEV][xt907] 4.4.2 OTA Partition Dump

DEVELOPMENT PURPOSES ONLY
183.46.10.XT907
>SYSTEM
>RECOVERY
>BOOT
>MODEM
>ABOOT
---------------------------------------------------------------------------------------
TO LIST PARTITIONS [DEV BLOCK] VIA ADB:
TYPE:
Code:
adb shell
Click to expand...
Click to collapse
THEN TYPE:
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------
IF YOU WANT TO PULL A PARTITION [DEV BLOCK]:
TYPE:
Code:
adb shell
Click to expand...
Click to collapse
THEN TYPE:
Code:
su
Click to expand...
Click to collapse
THEN TYPE:
Code:
dd if=[COLOR="Red"]/MountingPoint[/COLOR] of=[COLOR="SeaGreen"]/YourDestination[/COLOR][COLOR="PURPLE"]/PartitionType[/COLOR]
EXAMPLE - THIS IS THE SYSTEM BLOCK
Code:
dd if=[COLOR="Red"]/dev/block/mmcblk0p36[/COLOR] of=[COLOR="SeaGreen"]/sdcard[/COLOR][COLOR="DarkOrchid"]/system.img[/COLOR]
Click to expand...
Click to collapse

How to use? can flash fastboot will update 4.4.2 ?

Thanks! I've been needing the modem bin to fix my phone since I tried flashing the 4.0.4 modem lol. It ended up making the phone unusable.
Sent from my XT907 using Tapatalk

hungln03 said:
How to use? can flash fastboot will update 4.4.2 ?
Click to expand...
Click to collapse
Put system.img, recovery.img and boot.img to your fastboot folder and type when your phone is in fastboot mode:
fastboot flashall
Click to expand...
Click to collapse
Odesláno z mého XT907 pomocí Tapatalk

Klen2 said:
Put system.img, recovery.img and boot.img to your fastboot folder and type when your phone is in fastboot mode:
Odesláno z mého XT907 pomocí Tapatalk
Click to expand...
Click to collapse
im on 4.1.2 and OTA not showing any update, can i do this method to update???
fastboot flashall will update system.img, recovery.img and boot.img
and what about aboot and modem.bin????????????? please guide

Does anyone have any idea WHEN will be root exploit coming for locked BL?
Sent from my XT907 using XDA Premium 4 mobile app

l2adiant said:
im on 4.1.2 and OTA not showing any update, can i do this method to update???
fastboot flashall will update system.img, recovery.img and boot.img
and what about aboot and modem.bin????????????? please guide
Click to expand...
Click to collapse
Please do not flash these. They are for development purposes only. Head to this thread, grab the leak and continue reading through it for all of the instructions.

ATTACK said:
Please do not flash these. They are for development purposes only. Head to this thread, grab the leak and continue reading through it for all of the instructions.
Click to expand...
Click to collapse
i tried to install 98.30.1 using RSD and stuck on Fastboot :'(
please helppppppp
screenshot below

Try this: http://forum.xda-developers.com/showthread.php?t=2754082
Odesláno z mého XT907 pomocí Tapatalk

still stuck here, unable to flash system.img
please do something
now even its not flshing 4.1.2 system.img

Have you tried fastboot flash system system.img?
Sent from my XT907 using Tapatalk

thewraith420 said:
Have you tried fastboot flash system system.img?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'system' (30720 KB)...
OKAY [ 2.364s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.671s
yes, it failed, now im unable to goto fastboot too
i dont know what to do
it just show Moto logo for awhile and then black screen, no fastboot either

That's weird nothing you did should mess with your ability to get to fastboot
Sent from my XT907 using Tapatalk

thewraith420 said:
That's weird nothing you did should mess with your ability to get to fastboot
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
i dont know how but i managed to boot into fastboot, now m still unable to RSD back to 4.1.2 it stuck on 1st step gpt_main0 failed

In the development section i just noticed there's a unofficial fxz now to update to 4.4.2 you could try that with rsd
Sent from my XT907 using Tapatalk

thewraith420 said:
In the development section i just noticed there's a unofficial fxz now to update to 4.4.2 you could try that with rsd
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
link please
m getting this error
C:\Users\xxx\Desktop\VRZ>fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.789s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.097s

Well I was just going to post it but i also just noticed it's only for unlocked bootloaders
Edit can you post the results of fastboot getvar all
Sent from my XT907 using Tapatalk

thewraith420 said:
Well I was just going to post it but i also just noticed it's only for unlocked bootloaders
Edit can you post the results of fastboot getvar all
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
version-bootloader: 109B(*)
product: smq
secure: yes
mid: 0058
version: 0.5
serialno: TA22804O6K
qe: qe 1/1
unlocked: no
iswarrantyvoid: no
max-download-size: 31457280
emmc-size: 8GB
reason: Key pressed
revision-hardware: 0x82A0
cpu: MSM8960 CS
uid: C4B0BF0302000100000000000000
cid: 0x02
all:
finished. total time: 0.019s

Well you've definitely got the 4.4.2 bootloader what error message does fastboot flash system system.img give?
Sent from my XT907 using Tapatalk

thewraith420 said:
Well you've definitely got the 4.4.2 bootloader what error message does fastboot flash system system.img give?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
yes i think u are right
here is error
Preflash validation failed
how to get rid and got back to working 4.2.1 ?

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