Develop Bugs

[TUT][DUMP] DUMP Stock ROM (SYSTEM/BOOT/etc) | OneX_SEA_WWE_1.26.707.2_SYSTEM + BOOT

Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
[WITHOUT ROOT ACCESS]
Currently only /system is usable
1) Android SDK (just need adb)
2) Download busybox
3) Command prompt :
> adb push busybox /data/local/busybox
> adb shell
> cd /sdcard/
> chmod 755 /data/local/busybox
> /data/local/busybox tar cvf sysdump.tar /system
4) Ignore tar: error exit delayed from previous errors'. Is done correctly.
----------------------------------------------------------------------
Just finished dumped my semi-virgin One X system partition from SEA WWE stock ROM .
The file would be OneX_SEA_WWE_1.26.707.2_SYSTEM_DUMP.zip 558.3 MB

Hi,
can you tell me how to dump mine? My phone arrives tomorrow.
Thanks in advance...

@anko
Thread updated with guide.

so, is it true that i can simply download the system dump from the link your provide, and flash it via recovery if i want to go back to stock SEA rom?
by the way, i am using a SEA htc one X too.

ck_looi said:
so, is it true that i can simply download the system dump from the link your provide, and flash it via recovery if i want to go back to stock SEA rom?
by the way, i am using a SEA htc one X too.
Click to expand...
Click to collapse
not sure & never try
it was dumped before i unlock my device.
see here if u want unlock & backup ur stock rom including boot image. do nandroid backup after flashing Interim CWM. Then only restorable. (boot .img still hv to flash thru fastboot to restore or use new method by blubbers)

my current stock is 1.26.707.4
will i be able to flash this and then get update to 707.4 OTA? Just want to make sure i got the right stock rom for my one x.

Picked mine up today going to do system dump of mine its on t-mobile software is 126.110.5
Sent from my HTC One X using XDA

monx® said:
Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
Click to expand...
Click to collapse
i just dump boot (mmcblk0p4) and system (mmcblk0p12). is that good enough? (maybe recovery partition) I assume i would use fastboot flash to flash this image if I want to revert to stock?

zenkinz said:
i just dump boot (mmcblk0p4) and system (mmcblk0p12). is that good enough? (maybe recovery partition) I assume i would use fastboot flash to flash this image if I want to revert to stock?
Click to expand...
Click to collapse
Yes but RUU 1.26.707.4 is available (at least for our region). better extract *.img directly.

monx® said:
Yes but RUU 1.26.707.4 is available (at least for our region). better extract *.img directly.
Click to expand...
Click to collapse
ok thanks.

I've done Paul's procedure to Unlock + Interim CWM + SU, so now I'm rooted with S-On. After which I've done full backup thru interim CWM recovery prior to uninstalling bloatwares and I'm still now on stock ROM.
How different is this backup then? Back to stock?
Sent from my HTC One X using xda premium

Gday, now this looks like it spits out a tar file, I assume this is flashable through fastboot? I'm just trying to put together a fastboot flashable img of my providers stock rom for another user...
Edit, I might be being stupid, but shouldn't adb pick up the stock rom when connected and booted into rom? Put usb connection into usb host mode...
M.

2nd method works great...
monx® said:
Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
[WITHOUT ROOT ACCESS]
Currently only /system is usable
1) Android SDK (just need adb)
2) Download busybox
3) Command prompt :
> adb push busybox /data/local/busybox
> adb shell
> cd /sdcard/
> chmod 755 /data/local/busybox
> /data/local/busybox tar cvf sysdump.tar /system
4) Ignore tar: error exit delayed from previous errors'. Is done correctly.
----------------------------------------------------------------------
Just finished dumped my semi-virgin One X system partition from SEA WWE stock ROM .
The file would be OneX_SEA_WWE_1.26.707.2_SYSTEM_DUMP.zip 558.3 MB
Click to expand...
Click to collapse

Does this work on other models?
helloansuman said:
2nd method works great...
Click to expand...
Click to collapse
Hi, I was curious if this worked on other models specifically the xperia arc so-01c. I wish to dump a japanese docomo rom that I guess is pretty rare for English websites. Thanks in advance. AJ

I already have my boot.img and what not just need to dump my boot.img-kernel... How to?

2nd method works great on other phone thankx man!
just tell us one more thing that how to dump boot/kernel in the same is it possible or not ??

[Q] fastboot karnal problem

hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!

mmoti6 said:
hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!
Click to expand...
Click to collapse
Have you tried Flashing Stock Firmware?
Here is a Thread where you can download Official Stock Firmwares for the Xperia Play(Post #2):
Xperia Play Index - ROM'S, FIRMWARE, KERNEL'S, GUIDE'S, THEMES, MOD'S

mmoti6 said:
hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!
Click to expand...
Click to collapse
TheScriptKitty said:
Have you tried Flashing Stock Firmware?
Here is a Thread where you can download Official Stock Firmwares for the Xperia Play(Post #2):
Xperia Play Index - ROM'S, FIRMWARE, KERNEL'S, GUIDE'S, THEMES, MOD'S
Click to expand...
Click to collapse
i download r800a_N.A+Generic_4.0.A.2.368.rar ---- r800a stock firmware
and i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
And when I do that it tells me "flash operation complete" but still he didnt work....
in FlashTool is tell me
"FAILED (remote: Image won't fit, partition too small!)"
help plizz

mmoti6 said:
i download r800a_N.A+Generic_4.0.A.2.368.rar ---- r800a stock firmware
and i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
And when I do that it tells me "flash operation complete" but still he didnt work....
in FlashTool is tell me
"FAILED (remote: Image won't fit, partition too small!)"
help plizz
Click to expand...
Click to collapse
Are you trying to Flash it via Fastboot Mode?
You have to change the File Extension from .rar to .ftf , and then Flash it via FLASH MODE (NOT Fastboot Mode) in FlashTool.

pliz help
TheScriptKitty said:
Are you trying to Flash it via Fastboot Mode?
You have to change the File Extension from .rar to .ftf , and then Flash it via FLASH MODE (NOT Fastboot Mode) in FlashTool.
Click to expand...
Click to collapse
ok i change to Official Stock Firmwares for the Xperia Play (i think i chose the right one...)
but still tells me "flash operation complete"
but he didnt change the karnal
NexPlay_rk1_GSM/semc-kernel-msm7x30-jellybean
pliz help....
And model of cell phone is R800a
And he shows me "INFO - Current device : R800i - CB5A1GM5GZ - 1247-8563_R13D - 1245-8821_4.0.2.A.0.79 - VFE-1-8_4.0.2.A.0.79"
y?

mmoti6 said:
ok i change to Official Stock Firmwares for the Xperia Play (i think i chose the right one...)
but still tells me "flash operation complete"
but he didnt change the karnal
NexPlay_rk1_GSM/semc-kernel-msm7x30-jellybean
pliz help....
And model of cell phone is R800a
And he shows me "INFO - Current device : R800i - CB5A1GM5GZ - 1247-8563_R13D - 1245-8821_4.0.2.A.0.79 - VFE-1-8_4.0.2.A.0.79"
y?
Click to expand...
Click to collapse
If you Flashed the Stock Firmware for your phone and you say that the kernel has not changed how are you able to see what kernel you have if the phone should not be able to boot(Because it would be like trying to use a Costume ICS kernel on the Stock GB ROM)???

help pliz
TheScriptKitty said:
If you Flashed the Stock Firmware for your phone and you say that the kernel has not changed how are you able to see what kernel you have if the phone should not be able to boot(Because it would be like trying to use a Costume ICS kernel on the Stock GB ROM)???
Click to expand...
Click to collapse
if i Flashed the Stock Firmware for my phone the phone shows me this
(sony logo in boot screen)
and the phone is good and working
but then i Flashed a kernel like this
(LuPuS logo in boot screen)
but it still shows me this
(sony logo in boot screen)
and the phone is stuck on it
y?

mmoti6 said:
if i Flashed the Stock Firmware for my phone the phone shows me this
(sony logo in boot screen)
and the phone is good and working
but then i Flashed a kernel like this
(LuPuS logo in boot screen)
but it still shows me this
(sony logo in boot screen)
and the phone is stuck on it
y?
Click to expand...
Click to collapse
Have you flashed a Custom ROM?
If you have, please specify exactly what version of the Lupus Kernel and what ROM you are using.
And if you have not flashed a Custom ROM, as I said before trying to use a Custom Kernel on the Stock ROM will not work(it will not boot in most cases), you need to Flash a Custom ROM that is compatible with the Lupus Kernel you are using.

TheScriptKitty said:
Have you flashed a Custom ROM?
If you have, please specify exactly what version of the Lupus Kernel and what ROM you are using.
And if you have not flashed a Custom ROM, as I said before trying to use a Custom Kernel on the Stock ROM will not work(it will not boot in most cases), you need to Flash a Custom ROM that is compatible with the Lupus Kernel you are using.
Click to expand...
Click to collapse
you can recmmnded on a Firmwar?
i use to root the phone whit superonclick and this is what i get:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$
export TEMPRANDOM=65947;export PS1=END:$TEMPRANDOM;getprop ro.build.version.release
export PS1=""
$ 2.2.1
END:65947
export TEMPRANDOM=87695;export PS1=END:$TEMPRANDOM;getprop ro.product.manufacturer
export PS1=""
LGE
END:87695
export TEMPRANDOM=35445;export PS1=END:$TEMPRANDOM;getprop ro.product.model
export PS1=""
LG-P500h
END:35445
export TEMPRANDOM=50395;export PS1=END:$TEMPRANDOM;getprop ro.build.version.incremental
export PS1=""
eng.donghyun.seo.20110215.151731
END:50395
export TEMPRANDOM=25205;export PS1=END:$TEMPRANDOM;ls -l /system/xbin/su
export PS1=""
/system/xbin/su: No such file or directory
END:25205
export TEMPRANDOM=29466;export PS1=END:$TEMPRANDOM;ls -l /system/bin/su
export PS1=""
-rwsr-sr-x root root 380532 2012-08-07 13:01 su
END:29466
export TEMPRANDOM=48004;export PS1=END:$TEMPRANDOM;chmod 755 /data/local/tmp/busybox
export PS1=""
END:48004
export TEMPRANDOM=92630;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/boomsh
export PS1=""
rm failed for /data/local/tmp/boomsh, No such file or directory
END:92630
export TEMPRANDOM=17806;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/sh
export PS1=""
rm failed for /data/local/tmp/sh, No such file or directory
END:17806
export TEMPRANDOM=60041;export PS1=END:$TEMPRANDOM;chmod 700 /data/local/tmp/zergRush
export PS1=""
Unable to chmod /data/local/tmp/zergRush: No such file or directory
END:60041
export TEMPRANDOM=98014;export PS1=END:$TEMPRANDOM;cd /data/local/tmp/
export PS1=""
END:98014
export TEMPRANDOM=32459;export PS1=END:$TEMPRANDOM;./zergRush
export PS1=""
./zergRush: not found
END:32459
Click to expand...
Click to collapse
how i install the zergRush?
tnx
editing
i Flashing Stock Firmware r800i 4.0.2.A.0.62 firmware (but my phone is r800a...)
i use to root the phone whit superonclick and this is what i get:
$TEMPRANDOM;getprop ro.build.version.release
2.3.4
END:97116export PS1=""
export TEMPRANDOM=37017;export PS1=END:$TEMPRANDOM;getprop ro.product.manufacturer
Sony Ericsson
END:37017export PS1=""
export TEMPRANDOM=31785;export PS1=END:$TEMPRANDOM;getprop ro.product.model
R800i
END:31785export PS1=""
export TEMPRANDOM=65498;export PS1=END:$TEMPRANDOM;getprop ro.build.version.incremental
wf_v3w
END:65498export PS1=""
export TEMPRANDOM=13472;export PS1=END:$TEMPRANDOM;ls -l /system/xbin/su
/system/xbin/su: No such file or directory
END:13472export PS1=""
export TEMPRANDOM=80897;export PS1=END:$TEMPRANDOM;ls -l /system/bin/su
/system/bin/su: No such file or directory
END:80897export PS1=""
export TEMPRANDOM=71628;export PS1=END:$TEMPRANDOM;chmod 755 /data/local/tmp/busybox
END:71628export PS1=""
export TEMPRANDOM=96072;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/boomsh
rm failed for /data/local/tmp/boomsh, No such file or directory
END:96072export PS1=""
export TEMPRANDOM=66092;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/sh
rm failed for /data/local/tmp/sh, No such file or directory
END:66092export PS1=""
export TEMPRANDOM=93376;export PS1=END:$TEMPRANDOM;chmod 700 /data/local/tmp/zergRush
Unable to chmod /data/local/tmp/zergRush: No such file or directory
END:93376export PS1=""
export TEMPRANDOM=27821;export PS1=END:$TEMPRANDOM;cd /data/local/tmp/
END:27821export PS1=""
export TEMPRANDOM=97862;export PS1=END:$TEMPRANDOM;./zergRush
./zergRush: not found
END:97862export PS1=""
Click to expand...
Click to collapse
y?

mmoti6 said:
you can recmmnded on a Firmwar?
i use to root the phone whit superonclick and this is what i get:
how i install the zergRush?
tnx
editing
i Flashing Stock Firmware r800i 4.0.2.A.0.62 firmware (but my phone is r800a...)
i use to root the phone whit superonclick and this is what i get:
y?
Click to expand...
Click to collapse
Okay first of all, I don't think you understand the difference between a ROM, Kernel, and Firmware so I'll explain that first:
A ROM (In Android) is basically like the OS, it contains all the software you see and use on the phone. The kernel would be what connects the ROM (the OS) with the phone's hardware. A firmware would be a combination of both a Kernel and a ROM and its most commonly used to describe the Original ROM and Kernel of the phone (Stock Firmware). Please confirm that you Understand.
Now, I have never used SuperOneclick to root the Xperia Play so I really can't tell you what you are doing wrong. If you want, use zergRush. You don't have to install it, here is the basic procedure:
download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
[04/Jan][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v4.0](zergRush Exploit)
I don't think you will have any problems if you Flashed a R800i Firmware on a R800a, but just to be sure use Firmware made for your phone.
And if what you mean by "what Firmware I recommend" is what ROM do I recommend, here it is:
If you want Gingerbread(Android 2.3): Gin2KitKat
If you want ICS(Android 4.0): Xperia Play Z
If you want Jellybean(Android 4.1.2): Racing SPEED EDITION EOL or Super Lite Jelly Bean
For each ROM you have to install the Kernel it tells you to(Read instructions). I also want to add that their is no such thing as a best ROM, each ROM has its Pros and Cons, and what might appeal to me might not to you. I would recommend for you to try different ROMs and see what suits you.
And last, Please Click on the Thanks Button
.
.

TheScriptKitty said:
Okay first of all, I don't think you understand the difference between a ROM, Kernel, and Firmware so I'll explain that first:
A ROM (In Android) is basically like the OS, it contains all the software you see and use on the phone. The kernel would be what connects the ROM (the OS) with the phone's hardware. A firmware would be a combination of both a Kernel and a ROM and its most commonly used to describe the Original ROM and Kernel of the phone (Stock Firmware). Please confirm that you Understand.
Now, I have never used SuperOneclick to root the Xperia Play so I really can't tell you what you are doing wrong. If you want, use zergRush. You don't have to install it, here is the basic procedure:
download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
[04/Jan][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v4.0](zergRush Exploit)
I don't think you will have any problems if you Flashed a R800i Firmware on a R800a, but just to be sure use Firmware made for your phone.
And if what you mean by "what Firmware I recommend" is what ROM do I recommend, here it is:
If you want Gingerbread(Android 2.3): Gin2KitKat
If you want ICS(Android 4.0): Xperia Play Z
If you want Jellybean(Android 4.1.2): Racing SPEED EDITION EOL or Super Lite Jelly Bean
For each ROM you have to install the Kernel it tells you to(Read instructions). I also want to add that their is no such thing as a best ROM, each ROM has its Pros and Cons, and what might appeal to me might not to you. I would recommend for you to try different ROMs and see what suits you.
And last, Please Click on the Thanks Button
.
.
Click to expand...
Click to collapse
ok
new i get this
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1407 KB/s (23060 bytes in 0.016s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2949 KB/s (1075144 bytes in 0.356s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
107 KB/s (439 bytes in 0.004s)
df: /mnt/secure/asec: Permission denied
export: 65964: bad variable name
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
y?

mmoti6 said:
ok
new i get this
y?
Click to expand...
Click to collapse
It look like it failed to Root the device at the beginning, so it fail to do the rest of the stuff.
Are you sure you did all this?:
Make sure u have installed adb drivers for ur device
Enable "USB DEBUGGING" from (Menu\Settings\Applications\Development)
Enable "UNKNOWN SOURCES" from (Menu\Settings\Applications)
[OPTIONAL]Increase screen timeout to 10 minutes
Connect USB cable to PHONE and then connect to PC
Skip "PC Companion Software" prompt on device

TheScriptKitty said:
It look like it failed to Root the device at the beginning, so it fail to do the rest of the stuff.
Are you sure you did all this?:
Make sure u have installed adb drivers for ur device
Enable "USB DEBUGGING" from (Menu\Settings\Applications\Development)
Enable "UNKNOWN SOURCES" from (Menu\Settings\Applications)
[OPTIONAL]Increase screen timeout to 10 minutes
Connect USB cable to PHONE and then connect to PC
Skip "PC Companion Software" prompt on device
Click to expand...
Click to collapse
yes i am wure...

Zergrush can't root .62 (and above) firmware. Only .42 and bellow

Bakisha said:
Zergrush can't root .62 (and above) firmware. Only .42 and bellow
Click to expand...
Click to collapse
but onli the North America firmware is 42 and i am not from North America...
what i can do?

mmoti6 said:
but onli the North America firmware is 42 and i am not from North America...
what i can do?
Click to expand...
Click to collapse
It doesn't matter, it works fine with it.

TheScriptKitty said:
It doesn't matter, it works fine with it.
Click to expand...
Click to collapse
i dont see the firmware in the flashtool tool
i change it to ftf and i have 2 firmware
1.R800a_2.3.4_North America Generic (1)
2.R800a_4.0.2.A.0.42_North America
i cant see them....
you can recmmnded what to do?
i must to flash anther firmware ?
or i can only to flashe rom and carnal to get 42 or bellow firmware?

mmoti6 said:
i change it to ftf and i have 2 firmware
Click to expand...
Click to collapse
I recommend unpacking those two rar files to get ftf files, not renaming them from rar to ftf

Bakisha said:
I recommend unpacking those two rar files to get ftf files, not renaming them from rar to ftf
Click to expand...
Click to collapse
i still dont show tham on the flash tool
1.R800a_2.3.4_North America Generic (1) - i unpacking to ftf file
2.R800a_4.0.2.A.0.42_North America - i renaming from rar to ftf
i cant see them....
you can recmmnded what to do?
i must to flash anther firmware ?
or i can only to flashe rom and carnal to get 42 or bellow firmware?
tnx

Use latest version of flashtool http://flashtool.net
Find ftf firmware files at http://forum.xda-developers.com/showthread.php?t=2184897
Make sure you download correct firmware for your model (r800i/a/x)
The easiest way to get root on stock r800i
1: flash .42 firmware and root it with zerg-rush
2: flash .79 firmware and flash doomlord gb kernel
Sent from my R800i using XDA Free mobile app

Marshmallow Images

If someone who is on Marshmallow with root could provide the system.img boot.img and recovery.img i´d be appreciated.
All you have to do is
> adb shell
$ su
# de if=/dev/block/bootdevice/by-name/system of=/data/local/tmp/system.img
# chmod 0644 data/local/tmp/system.img
# exit
$ exit
> adb pull data/local/tmp/system.img
and the same for boot.img and recovery.img
best regards.

Which one G8 do you have. I can extract RIO-L01 single SIM

krispin said:
Which one G8 do you have. I can extract RIO-L01 single SIM
Click to expand...
Click to collapse
i have the dual sim version.... :crying:
but you should submit them here for further info...

I am trying to extract system.img, but getting error: sush: de: not found

krispin said:
I am trying to extract system.img, but getting error: sush: de: not found
Click to expand...
Click to collapse
Nope, is not "de" but "dd"
"# dd if=/dev/block/bootdevice/by-name/system of=/data/local/tmp/system.img"
Please, maybe you can extract also modem image from M, even if your device is single sim :
> adb shell
$ su
# dd if=/dev/block/bootdevice/by-name/modem of=/data/local/tmp/modem.img
# chmod 0644 data/local/tmp/modem.img
# exit
$ exit
> adb pull data/local/tmp/modem.img
Thank you very much in advance

You´ll get it in half an hour. Tomorrov will upload system.img too. But I already deleted some google apps and games. One question, why TB didnt work for uninstalling system apps? It wrote uninstall succesfull, but after a while they reappeared. I had to manualy delete them with root explorer.
link: https://mega.nz/#!zUc1iKhR!AgsYaj1gmQo5uUsmirg8WOjNV_nGeu4dNvMocJ8uwXo

krispin said:
You´ll get it in half an hour. Tomorrov will upload system.img too. But I already deleted some google apps and games. One question, why TB didnt work for uninstalling system apps? It wrote uninstall succesfull, but after a while they reappeared. I had to manualy delete them with root explorer.
link: https://mega.nz/#!zUc1iKhR!AgsYaj1gmQo5uUsmirg8WOjNV_nGeu4dNvMocJ8uwXo
Click to expand...
Click to collapse
can you upload the system and recovery and boot imgs please?!

Cannot boot to system - Always boot to TWRP

I've recently tried out some Generic System Images (or Project Treble ROMs). I did this by flashing the system.img and then doing a factory reset after every image. Some images later I wanted to go back to my daily system.img but It stopped working.
I don't know which step cause this error, but since I flashed my daily system.img again and wanted to boot it, it would always boot into TWRP.
I really don't know how to handle this error since I don't have the knowledge but I'll try to supply as much information as possible, starting with TWRP Logs
One strange thing I noticed is this:
Code:
ro.product.name=omni_berlin
ro.product.board=hi6250
ro.product.brand=Honor
ro.product.model=HONOR-6X
ro.product.device=berlin
ro.product.locale=en-US
ro.product.platform=hi6250
It says Honor-6X although I'm using the 7X and didn't flash anything for the 6X, but it seems like I must have overlooked something...
recovery.log
dmesg.log (1/2)
dmesg.log (2/2)
I'll provide any information needed as soon as possible and I'll be very thankful for any help!
Edit: I usually use [ROM][8.1][OpenKirin's RROS Oreo v6.0.0 - For Honor 7X], but today I've tries these:
[8.1.0][TREBLE] Pixel Experience [AOSP][r26][2018/05/27]
[Resurrection Remix] [Unofficial] [2018-05-19] Phh-Treble
[Lineage] [Unofficial] [2018-05-19] Phh-Treble

supervis0r said:
I've recently tried out some Generic System Images (or Project Treble ROMs). I did this by flashing the system.img and then doing a factory reset after every image. Some images later I wanted to go back to my daily system.img but It stopped working.
I don't know which step cause this error, but since I flashed my daily system.img again and wanted to boot it, it would always boot into TWRP.
I really don't know how to handle this error since I don't have the knowledge but I'll try to supply as much information as possible, starting with TWRP Logs
One strange thing I noticed is this:
Code:
ro.product.name=omni_berlin
ro.product.board=hi6250
ro.product.brand=Honor
ro.product.model=HONOR-6X
ro.product.device=berlin
ro.product.locale=en-US
ro.product.platform=hi6250
It says Honor-6X although I'm using the 7X and didn't flash anything for the 6X, but it seems like I must have overlooked something...
recovery.log
dmesg.log (1/2)
dmesg.log (2/2)
I'll provide any information needed as soon as possible and I'll be very thankful for any help!
Edit: I usually use [ROM][8.1][OpenKirin's RROS Oreo v6.0.0 - For Honor 7X], but today I've tries these:
[8.1.0][TREBLE] Pixel Experience [AOSP][r26][2018/05/27]
[Resurrection Remix] [Unofficial] [2018-05-19] Phh-Treble
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/lineage-phh-treble-t3767690
Click to expand...
Click to collapse
The recovery was borrowed. or ported from Honor 6x, so that line is not a concern.
As far as the logs, I browsed through them. Nothing jumps out to me. There is some selinux permissive = 0 type errors, but dont think that is causing your problem.
I had to use stock recovery to do wipes (factory reset) between different treble rom installs. Without i had bootloop. I never had forced boot to recovery. .
as long as frp is not locked i would suggest flashing stock recovery to try a reset. And if it boots, put twrp back.

mrmazak said:
The recovery was borrowed. or ported from Honor 6x, so that line is not a concern.
As far as the logs, I browsed through them. Nothing jumps out to me. There is some selinux permissive = 0 type errors, but dont think that is causing your problem.
I had to use stock recovery to do wipes (factory reset) between different treble rom installs. Without i had bootloop. I never had forced boot to recovery. .
as long as frp is not locked i would suggest flashing stock recovery to try a reset. And if it boots, put twrp back.
Click to expand...
Click to collapse
Thanks for your fast response.
I've tried installing the stock recovery but I either get a 'Software install failed!' message and can only choose to reboot out of the recovery or it fails to flash through fastboot with this error message 'FAILED (remote: partition length get error)'
I've tried the recovery I can download through the Huawei Multi-Tool 8.0.4.9 'SR_BND-L21_B3xx_EMUI8.img' <- This flashed successfully but I get the Software install failed message.
And I've tried the recovery from this Google Drive folder 'BND-RECOVERY-NoCheck.img' but here I'll get the partition length error while trying to flash it through fastboot.
I think I caused the Software install failed through trying to reset my phone using these instructions
Code:
- Type in these commands:
dd if=/external_sd/BND-RECOVERY-NoCheck.img of=/dev/block/bootdevice/by-name/recovery
dd if=/external_sd/BND-RECOVERY-NoCheck.img of=/dev/block/bootdevice/by-name/recovery2
- If those went well type these as next:
echo --update_package=/sdcard/update.zip > /cache/recovery/command
echo --update_package=/sdcard/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/update_full_BND-L21C_hw_eu.zip >> /cache/recovery/command
I've replaced 'external_sd' and 'sdcard' with 'usbotg' since I had the files on a usbotg device and not on an external sd card.

supervis0r said:
Thanks for your fast response.
I've tried installing the stock recovery but I either get a 'Software install failed!' message and can only choose to reboot out of the recovery or it fails to flash through fastboot with this error message 'FAILED (remote: partition length get error)'
I've tried the recovery I can download through the Huawei Multi-Tool 8.0.4.9 'SR_BND-L21_B3xx_EMUI8.img' <- This flashed successfully but I get the Software install failed message.
And I've tried the recovery from this Google Drive folder 'BND-RECOVERY-NoCheck.img' but here I'll get the partition length error while trying to flash it through fastboot.
I think I caused the Software install failed through trying to reset my phone using these instructions
Code:
- Type in these commands:
dd if=/external_sd/BND-RECOVERY-NoCheck.img of=/dev/block/bootdevice/by-name/recovery
dd if=/external_sd/BND-RECOVERY-NoCheck.img of=/dev/block/bootdevice/by-name/recovery2
- If those went well type these as next:
echo --update_package=/sdcard/update.zip > /cache/recovery/command
echo --update_package=/sdcard/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/update_full_BND-L21C_hw_eu.zip >> /cache/recovery/command
I've replaced 'external_sd' and 'sdcard' with 'usbotg' since I had the files on a usbotg device and not on an external sd card.
Click to expand...
Click to collapse
I have been trying to get usbotg to work, with that method. Twrp recognize s it but the no-check recovery does not.
And the partition you are calling for recovery are wrong for emui8
Both the recovery file you are using and the partition name are nougat.
Oreo partition name is "recovery_ramdisk"
Do not do it to recovery2, "erecovery". It is not needed, or advised.
I have made this manual install process into an install zip. For twrp.
You can see it here
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649

mrmazak said:
I have been trying to get usbotg to work, with that method. Twrp recognize s it but the no-check recovery does not.
And the partition you are calling for recovery are wrong for emui8
Both the recovery file you are using and the partition name are nougat.
Oreo partition name is "recovery_ramdisk"
Do not do it to recovery2, "erecovery". It is not needed, or advised.
Click to expand...
Click to collapse
Just before I read this message I retried it, I used these commands through TWRP
Code:
echo --update_package=/sdcard/update.zip > /cache/recovery/command
echo --update_package=/sdcard/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/update_full_BND-L21C_hw_eu.zip >> /cache/recovery/command
and then flashed the recovery through Huawei Multi-Tool on recovery_ramdisk.
After a reboot the stock recovery showed up, and did something like verifying the update package (i couldn't read it since it passed very fast) and then stayed at 5% installing.
I now managed to get eRecovery to work but when i choose 'Wipe data/factory reset' it reboots back into eRecovery where it stops at exactly 5%, showing Reset failed!
Edit: I am now downloading a FullOTA-MF-PV for BND-L21 8.0.0.330(C432CUSTC432D2) and will try to follow your tutorial for updates while on Oreo.

supervis0r said:
Just before I read this message I retried it, I used these commands through TWRP
Code:
echo --update_package=/sdcard/update.zip > /cache/recovery/command
echo --update_package=/sdcard/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/update_full_BND-L21C_hw_eu.zip >> /cache/recovery/command
and then flashed the recovery through Huawei Multi-Tool on recovery_ramdisk.
After a reboot the stock recovery showed up, and did something like verifying the update package (i couldn't read it since it passed very fast) and then stayed at 5% installing.
I now managed to get eRecovery to work but when i choose 'Wipe data/factory reset' it reboots back into eRecovery where it stops at exactly 5%, showing Reset failed!
Click to expand...
Click to collapse
Did install go past 5% ?
If not did you force it reboot to get out.
Do you have those update files on your sdcard?
If you have those files are they the correct ones for your region device?

mrmazak said:
Did install go past 5% ?
If not did you force it reboot to get out.
Do you have those update files on your sdcard?
If you have those files are they the correct ones for your region device?
Click to expand...
Click to collapse
I was thinking about forcing it to reboot since it stayed at 5% for some time, but eventually it rebooted by itself but as it did that it was still at 5%.
I might have used the wrong files since I already tried out a lot of things and didn't organize all those files at all :/
I will now retry this using the files I have stated in the update of my previous post and also using your zip file.
I put the files into the root directory of my sd card. So the root directory looks like this
Code:
PS J:\> ls
Verzeichnis: J:\
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 29.05.2018 22:09 21276664 update_data_full_public.zip
-a---- 29.05.2018 22:18 1834159779 update.zip
-a---- 29.05.2018 22:11 715530773 update_full_BND-L21C_hw_eu.zip
-a---- 29.05.2018 22:08 37144576 BND-RECOVERY-NoCheck.img
-a---- 06.04.2018 09:37 33554432 SR_BND-L21_B3xx_EMUI8.img
-a---- 29.05.2018 22:36 15024128 complete_twrp_ramdisk.img

supervis0r said:
I was thinking about forcing it to reboot since it stayed at 5% for some time, but eventually it rebooted by itself but as it did that it was still at 5%.
I might have used the wrong files since I already tried out a lot of things and didn't organize all those files at all :/
I will now retry this using the files I have stated in the update of my previous post and also using your zip file.
I put the files into the root directory of my sd card. So the root directory looks like this
Code:
PS J:\> ls
Verzeichnis: J:\
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 29.05.2018 22:09 21276664 update_data_full_public.zip
-a---- 29.05.2018 22:18 1834159779 update.zip
-a---- 29.05.2018 22:11 715530773 update_full_BND-L21C_hw_eu.zip
-a---- 29.05.2018 22:08 37144576 BND-RECOVERY-NoCheck.img
-a---- 06.04.2018 09:37 33554432 SR_BND-L21_B3xx_EMUI8.img
-a---- 29.05.2018 22:36 15024128 complete_twrp_ramdisk.img
Click to expand...
Click to collapse
They need to be in folder "HWOTA8" on sdcard

mrmazak said:
They need to be in folder "HWOTA8" on sdcard
Click to expand...
Click to collapse
Thank you
Edit: I now installed TWRP and copied the files onto the SD Card
The directory now looks like this
Code:
PS J:\HWOTA8> ls
Verzeichnis: J:\HWOTA8
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 30.05.2018 13:54 82757105 update_data_full_public.zip
-a---- 30.05.2018 13:59 769778671 update_full_BND-L21C_hw_eu.zip
-a---- 30.05.2018 14:02 1803590616 update.zip
-a---- 23.05.2018 02:42 1241 hwota8_update-auto-rename.zip
-a---- 15.04.2018 22:22 26314752 RecoveryNoCheckOreoHi6250.img
Update 1: EMUI Recovery is now 'Installing update...' at 25% and rising. This really looks promising! Im so hyped right now
Update 2: Honor Boot animation came up and now I'm waiting for the first use setup to prompt me.
Update 3: So I was at the first use setup but I couldn't activate Wifi and my internal memory was 0B. I'm now doing another Factory Reset from eRecovery
I am now back at EMUI 8 with the Build-Number BND-L21 8.0.0.330(C432) but I'm still unsure if C432 is from my device or from the files I flashed.
Nevertheless my phone is now working again and I am very happy about that! Internal storage is showing up correctly and I can use mobile data as well as WiFi.
Thank you so much for your help!

How to remove data encryption on emui 9.1 stock roms and root

Im Using C432 .. Rom 9.1.0.147 Newest Stock Update Here In Denmark
First Unlock Bootloader : flash oem unlock ********code******
Enter Bootloader Again, Now Flash Modded_recovery_ramdisk : fastboot flash recovery_ramdisk r.ram.mod.img
And Flash Erecovery_ramdisk with TWRP.img From kilroystyx
Do NOT Remove USB Cable But Hold Power Untill You See Black Screen
Then Quickly Pres And Hold VOL + Untill You Read "Your Device Is Booting Now..."
Now You Should See/Enter Your TWRP Recovery , Now Wipe And Format Data, Then Reboot Recovery "Force Close With Power" .. Again When You See Black Screen Then Quickly Pres And Hold VOL + Untill You Read "Your Device Is Booting Now..."
And You Should ReEnter TWRP Again.. now Mount Vendor then Start Terminal In Recovery under advanced
In Terminal Type :
mount -o remount,rw /dev/block/mmcblk0p55
mount -o remount,rw /dev/block/mmcblk0p37
mount -o remount,rw /dev/block/mmcblk0p53
"patition name/table layout of editable partitions from recovery"
cust = mmcblk0p53
vendor = mmcblk0p55
modem_fw = mmcblk0p37
erecovery_ramdisk = mmcblk0p29
recovery_ramdisk = mmvblk0p33
Now Use File Manager In Recovery Under Advanced To Copy fstab.modem , fstab.hi6250 And recovery.fstab From /vendor/etc/ to /sdcard/ And from /sdcard/ Over To a PC .. Edit fstab.* With Notepad++ One By One Remove The Word "verify" including the comma and replace ALL "ro" with "rw" Also Remove The Words With fileencryption***************** Including The Comma ...
Do This in ALL 3 Files When Done Copy Back The 3 Files To Sdcard And Use File Manager To Move The Edited Files Back To /vendor/etc/ Overwriting The Old Files Now Do The Same With The 2 Files In The Root /fstab.hi6250.data And /fstab.hi6250
THEN FROM RECOVERY Select REBOOT And RECOVERY .... AND YOUR DONE .. You Should Now Automaticly Enter The Rom..
YOU ARE NOW MAGISK ROOTED "Use 19.3 Stable Settings In Magisk Only" Dont Directly Update Magisk ! Clear Repo!
From Now On To Enter The TWRP You Need To Put The USB Cable In The Phone And Hold VOL- And Power To Enter Bootloader From Here Force Power Off " Hold Power Untill Black Screen Then Quickly Hold VOL+ Alone Untill You Read "Your Device Is Booting Now..." Only Way To Enter TWRP Using "ERECOVERY_RAMDISK" Partition.. And Always Use Reboot Then Recovery to Enter Rom From TWRP .. If Not You Need To Reflash recovery_ramdisk with r.ram.mod.img
Now You Can Backup Data And Restore Data With Out Fork Errors We Should Also Be Able To Both Backup/Restore Cust , Modem_fw And Vendor. But We Only Need Data, System , Erecovery_ramdisk And Recovery_ramdisk To Get A Good Complete Backup.
Peace MarsDroid/BrokenWorm

Unlock Bootloader
First Unlock Bootloader : flash oem unlock ********code******???????
The question is, will it unlock the bootloader? . This is what i need, plis

KenynTM said:
First Unlock Bootloader : flash oem unlock ********code******???????
The question is, will it unlock the bootloader? . This is what i need, plis
Click to expand...
Click to collapse
Becoes your new ill be nice.. but plz dude.. u got to read more before you use this guide or you will end up with a pretty door stopper.
To unlock your bootloader use this DC UNLOCKER CLIENT : https://www.dc-unlocker.com/downloads
This is the 1 and only solution .

I cant flash Erecovery, i got
Writing 'Erecovery_ramdisk'
FAILED (remote: Comand not allowed)
My bootloader is unlocked, please help

I'm also stuck here^^^

Flash erecovery_ramdisk from twrp recovery... Sry forgot to mention that..
I recomend following or reading this post i wrote .. https://forum.xda-developers.com/showpost.php?p=80044263&postcount=9 .. about the same stuff

Welp, i managed to flash twrp to Erecocery, it's pretty easy
1 download twrp and patched recovery_ramdisk (i strongly recomend to extract the one from update.app with huawei firmware finder and huawei firmware extractor and pacth it with magisk manager)
2 copy twrp.img into your minimal adb folder and copy twrp and patched recovery_ramdisk into your micro sd
3 connect p20 lite (in fastboot Mode) to pc and open minimal adb and fastboot (cmd here) and flash twrp (fastboot flash recovery_ramdisk twrp.img)
3 Disconect and force power off, turn p20 lite and boot into recovery (power off and vol +) it Will boot into twrp
4 go to install and go to external storage, also select "Install image"
5 select your twrp.img, it will you ask where to Install, select "Erecocery_ramdisk" and Install it
6 repeat step 4 and now select your patched recovery_ramdisk.img and Install it on "recovery_ramdisk"
7 ???
8 profit
And now i'm stuck with the fstabs, i do all the steps on first post but when i try to move the modified ones shows an error, so what now?

RyogaIgnored said:
Welp, i managed to flash twrp to Erecocery, it's pretty easy
1 download twrp and patched recovery_ramdisk (i strongly recomend to extract the one from update.app with huawei firmware finder and huawei firmware extractor and pacth it with magisk manager)
2 copy twrp.img into your minimal adb folder and copy twrp and patched recovery_ramdisk into your micro sd
3 connect p20 lite (in fastboot Mode) to pc and open minimal adb and fastboot (cmd here) and flash twrp (fastboot flash recovery_ramdisk twrp.img)
3 Disconect and force power off, turn p20 lite and boot into recovery (power off and vol +) it Will boot into twrp
4 go to install and go to external storage, also select "Install image"
5 select your twrp.img, it will you ask where to Install, select "Erecocery_ramdisk" and Install it
6 repeat step 4 and now select your patched recovery_ramdisk.img and Install it on "recovery_ramdisk"
7 ???
8 profit
And now i'm stuck with the fstabs, i do all the steps on first post but when i try to move the modified ones shows an error, so what now?
Click to expand...
Click to collapse
i would try remounting the partitions rw

brokenworm said:
i would try remounting the partitions rw
Click to expand...
Click to collapse
Hi. The code I wrote from the twrp terminal window gives an error.
mount -o remount,rw /dev/block/mmcblk0p55
mount: can't find /dev/block/mmcblk0p55 in /proc/mounts

akif688 said:
Hi. The code I wrote from the twrp terminal window gives an error.
mount -o remount,rw /dev/block/mmcblk0p55
mount: can't find /dev/block/mmcblk0p55 in /proc/mounts
Click to expand...
Click to collapse
When you enter "ls -l /dev/block/mmcblk*" in the terminal, what does it say then?

I want to transfer this procedure to Honor 7X. Can someone please send output from the following commands (first to get list of names of partitions, second to get list of mounted filesystems) executed via adb shell on the P20 lite:
ls -l /dev/block/by-name
mount
Thanks a lot in advance.

ZB2016 said:
I want to transfer this procedure to Honor 7X. Can someone please send output from the following commands (first to get list of names of partitions, second to get list of mounted filesystems) executed via adb shell on the P20 lite:
ls -l /dev/block/by-name
mount
Thanks a lot in advance.
Click to expand...
Click to collapse
the partitons change from rom build to rom build and is useless. ..
i moved on to new device sry ..
but this is the partitions i was playing with :
"patition name/table layout of editable partitions from recovery"
cust = mmcblk0p53
vendor = mmcblk0p55
modem_fw = mmcblk0p37
erecovery_ramdisk = mmcblk0p29
recovery_ramdisk = mmvblk0p33
im guessing this answers your question

brokenworm said:
the partitons change from rom build to rom build and is useless. ..
...
im guessing this answers your question
Click to expand...
Click to collapse
perfect! Thanks a lot!

Does anyone have a working link to the r.ram.mod.img file?
EDIT: Nevermind... figured out I had to extract it from my firmware.

Guys tell me how to decrypt huawei p20 lite, i.e. turn off encryption.
and this parameter is not quite clear what it is and how - disable verity.
The device - the data folder is already encrypted, of the more comprehensible methods are of interest to me these two
this 1) "https://forum.xda-developers.com/t/...tion-on-emui-9-1-stock-roms-and-root.3953946/"
and this 2)
"https://forum.xda-developers.com/t/...-mediapad-t3-10-ags-w0.3843728/#post-78558329 "
but the first method does not show what to do after you mount it
In Terminal Type :
mount -o remount,rw /dev/block/mmcblk0p55
mount -o remount,rw /dev/block/mmcblk0p37
mount -o remount,rw /dev/block/mmcblk0p53
"name/table layout of editable partitions from recovery"
cust = mmcblk0p53
vendor = mmcblk0p55
modem_fw = mmcblk0p37
erecovery_ramdisk = mmcblk0p29
recovery_ramdisk = mmvblk0p33
i don't know if it's necessary to go through these commands, when i can copy these files, edit them and replace them back via TWRP, do i understand correctly that these commands will unlock the partition to overwrite the files inside it?
but i don't know if this method will work with emui 9.1 yet and the links to img are broken. + i'm afraid to overwrite TWRP with erecovery, because i figured out that i can't flash emui from fastboot erecovery, it is closed for him, only with TWRP and i'm not sure if i can? "+ it's not clear, replaced the files and that's it? "
the second way I stopped
I don't understand why I can't see the boot img from the extracted firmware Anne-L01 9.1.0.370(C432E7R1P7T8)
Is it locked or what? but i saw verity in FASTBOOT.img - or should i edit it to disable verity? and the question is different things recovery and boot? so i doubt in the correct execution.
and in this video i saw how to remove veirty, but what is it ?
as i understand this will not remove the forced encryption , but as i understand this will move me one step closer to the goal of disabling all verity and encryption too.
I don't understand what vbmeta is either, do I have to dig around in my target just to remove this forced encryption or is it an extra parameter, I mean vbmeta ?