hi
how can i reset EFS poco x3 pro ?
device is rooted and twrp installed
this is my code i run that in twrp for reset efs but device not coming up after running this :
adb shell ls -l /dev/block/bootdevice/by-name/
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p46
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p47
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p45
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/fsg
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/fsc
adb shell reboot
Click to expand...
Click to collapse
I am also having the same issue with my poco m3. Have you fixed? Lets discuss... my telegram [email protected]_TEK
Just Read My Thread and Your Problem Will Be fixed
Download TWRP + EFS RESET tool From my thread Reqirement
I have explained all progress of this phone there
Link XDA
uncle.milad said:
hi
how can i reset EFS poco x3 pro ?
device is rooted and twrp installed
this is my code i run that in twrp for reset efs but device not coming up after running this :
Click to expand...
Click to collapse
When You Reset EFS Your Phone NV Data Goes Corrupt and When Reboots Each time You Power it
It Can Caused By two Problem
Firmware Security
RSA Encryption of IMEI
-------------
Read my Thread CareFully
Related
Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help
Why?
tjhooker73 said:
Why?
Click to expand...
Click to collapse
Do you have the middle eastern variant?
Sent from my Evita
tjhooker73 said:
Why?
Click to expand...
Click to collapse
timmaaa said:
Do you have the middle eastern variant?
Sent from my Evita
Click to expand...
Click to collapse
Someone in other thread tell that middle east version(ul flashed) can be fixed by those 3 blocks and radio block ofcours .. but do you have any suggestions for recover my misc partition .. if I was lucky and someone upload it to me .. do you think that adb can restore it ??
dr.scofield said:
Someone in other thread tell that middle east version(ul flashed) can be fixed by those 3 blocks and radio block ofcours .. but do you have any suggestions for recover my misc partition .. if I was lucky and someone upload it to me .. do you think that adb can restore it ??
Click to expand...
Click to collapse
What's wrong with your phone?
Need the imgs because no firmwares or ruu fo this phone .. and my utl flashed ul and bricked .. then relifed with evita-ul dll because no dll for it .. so since there no firmwares for it and I replaced mine .. I need it from any working phone by dumping it .. if you can help
Anyone??
Sent from my HTC One XL using XDA Premium 4 mobile app
dr.scofield said:
Anyone??
Click to expand...
Click to collapse
I upload these 5 files on my google drive
But I can't post the link
Send me you contact at "sladefoto" a t gmail
Sladefoto said:
I upload these 5 files on my google drive
But I can't post the link
Send me you contact at "sladefoto" a t gmail
Click to expand...
Click to collapse
Thanks .. i've managed these files and fixed this phone
dr.scofield said:
Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help
Click to expand...
Click to collapse
i have same problem and still my device (no service )not antenna after jtag with riff box
my device one xl (evita utl pj83500) s-off and super cid
i dumped this 5 files but i dont know how to solve my problem and flash misc.radio and hboot files ==> when i write fastboot flash radio radio.img say error : not allowed
how to eng-s-off this model to flash radio.img and hboot.img
pls help
How did you flash them?
I have the same problem but I don't know how to flash the partitions.
Thread Cleaned, there is no "trading", "selling" for device files or anything of that sort, of funds or gifts, as per Forum Rules.
dr.scofield said:
Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help
Click to expand...
Click to collapse
thanks god, could you tell me how did you do with 5 files, please share? we have the same problems, hope you help us? pls!
vincent844 said:
thanks god, could you tell me how did you do with 5 files, please share? we have the same problems, hope you help us? pls!
Click to expand...
Click to collapse
Do you have these 5 files If yes please please send them to me [email protected]
u will send for evita UTL?
and u have all the 5 files?
Hboot.img
Misc.img
Radio.img
Adsp.img
Wcnss.img
Can you send me these files please
I will also help you to flash them but please send them to me
Hi! Sorry for my very bad English =) This thread is a solution, if you have IMEI unknown and all instructions NOT working - read/write error etc.
1. root device
2. download attach zip. It is contains 3 partitions - mmcblk 12,13 and 16.
3. copy three this files to your phone.
4. enable diag mode (com port in windows)
5. Run adb, type adb shell, type su
before Restoring we have to make sure that the efs partitions are cleared and dont have previous data so follow this codes before restoring
dd if=/dev/zero of=/dev/block/mmcblk0p12
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p16
reboot
Copy the Code
Use the below mentioned codes to restore
dd if=/sdcard/mmcblk0p12 of=/dev/block/mmcblk0p12
dd if=/sdcard/mmcblk0p13 of=/dev/block/mmcblk0p13
dd if=/sdcard/mmcblk0p16 of=/dev/block/mmcblk0p16
Copy the Code
Now Phone would reboot, Your Imei is Fixed (Restored) - imei null =)
6. in EFS Professional write your IMEI =)
7. reboot and enjoy your working phone =)
i know its not the right section to post but i have very less post count
anyway my question
with ROOTED phone ,
I use this commands in adb :
adb shell dd if=/dev/zero of=/dev/block/sda1
adb shell dd if=/dev/zero of=/dev/block/sda2
adb shell dd if=/dev/zero of=/dev/block/sdd4
and works perfect
but I want something for UnROOTED phone
or is ther anything called temporary root?
when im about to remove the modem files like this from adb menu
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs2
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefs3
dd if=/dev/zero of=/dev/block/bootdevice/by-name/mdm1m9kefsc
im getting "write error: No space left on device" error.
how to fix this. or is there any other way to delete those files.
Those commands will overwrite the named block-devices with zeroes, they don't get deleted means it's not technically erasing.
jwoegerbauer said:
Those commands will overwrite the named block-devices with zeroes, they don't get deleted means it's not technically erasing.
Click to expand...
Click to collapse
ok, so is there a way to overwrite them? cos atm i cant with those commands
To overwrite you have to specify as infile an image ( .img ) and as outfile the block-device wanted
jwoegerbauer said:
Look inside here:
dd: No Space Left on Device | Beamtic
After running dd for a long time, it stops with an error saying no space is left on the device.
beamtic.com
Click to expand...
Click to collapse
would it also be fixed when i format the device and wipe all data?
Raw34 said:
would it also be fixed when i format the device and wipe all data?
Click to expand...
Click to collapse
Re-read my altered post above yours.
jwoegerbauer said:
To overwrite you have to specify as infile an image ( .img ) and as outfile the block-device wanted
Click to expand...
Click to collapse
can u give me an example for the command for adb menu?
i want to get rid of this file mi10orj.bin in the modem
What ADB are you using? AFAIK ADB hasn't a menu,
If device is rooted then you may run
Code:
adb devices
adb shell "stop"
adb shell "rm -f /vendor/mi10orj.bin"
adb shell "start"
if the .bin-file is located in vendor partition what IDK
jwoegerbauer said:
What ADB are you using? AFAIK ADB hasn't a menu,
If device is rooted then you may run
Code:
adb devices
adb shell "stop"
adb shell "rm -f /vendor/mi10orj.bin"
adb shell "start"
if the .bin-file is located in vendor partition what IDK
Click to expand...
Click to collapse
its called "minimal adb and fastboot tool".
yes the device is rooted. im gonna try this commands when im done with my working.
thx so much for your help and insight, so far.
Hello,
The question is pretty straightforward - is it possible to restore the data on the phone that had existed before the factory reset was made?
If I sell my phone on ebay can someone get any glimpse on what has been done with my phone?
e2com said:
The question is pretty straightforward - is it possible to restore the data on the phone that had existed before the factory reset was made?
Click to expand...
Click to collapse
It is still possible to recover much data after an factory reset. Unless you cleaned the drive properly. Fact is that there are user data still accessible on almost 40% of all phones bought at pawn shops.
To clean a drive you basically overwrite every single bit of the storage with an binary zero. This an very hard process to do manually therefore I would recommend using an data eraser tool such as:
Jihosoft Mobile Privacy Eraser - $49 /One-time
MobiKin Eraser for Android - $49 /One-time
Dr.Fone Data Eraser - $14.95 /Year or $19.95 /One-time
Or just use ADB to wipe all partitions you made changes to. As jwoegerbauer suggested.
e2com said:
If I sell my phone on ebay can someone get any glimpse on what has been done with my phone?
Click to expand...
Click to collapse
So short answer yes, it is very much likely that they can recover your data. Therefore I recommend wiping before selling it.
A sequence of 3 ADB commands is enough to unrecoverably wipe Android's user-data, provided the /data partition is mounted as RW
Code:
adb devices
adb shell "dd if=/dev/null of=/dev/block/bootdevice/by-name/userdata bs=4096"
adb shell "dd if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=4096"
jwoegerbauer said:
A sequence of 3 ADB commands is enough to unrecoverably wipe Android's user-data, provided the /data partition is mounted as RW
Code:
adb devices
adb shell "dd if=/dev/null of=/dev/block/bootdevice/by-name/userdata bs=4096"
adb shell "dd if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=4096"
Click to expand...
Click to collapse
I learned something new today.
jwoegerbauer said:
A sequence of 3 ADB commands is enough to unrecoverably wipe Android's user-data, provided the /data partition is mounted as RW
Code:
adb devices
adb shell "dd if=/dev/null of=/dev/block/bootdevice/by-name/userdata bs=4096"
adb shell "dd if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=4096"
Click to expand...
Click to collapse
Hello,
when I run adb shell "dd if=/dev/null of=/dev/block/bootdevice/by-name/userdata bs=4096"
I get this:
dd: /dev/block/bootdevice/by-name/userdata: Permission denied
even though I run the command as sudo and enter my admin password. Any idea what I am doing wrong?
Are you sure that /data is mounted as RW?
TrulyPain said:
Are you sure that /data is mounted as RW?
Click to expand...
Click to collapse
no. How do I check it please?
e2com said:
no. How do I check it please?
Click to expand...
Click to collapse
It is quite different whether which device and android version you have. But usually, you write cat /proc/mounts in ADB. Then you shall see whether /data are mounted as RO or RW.
TrulyPain said:
It is quite different whether which device and android version you have. But usually, you write cat /proc/mounts in ADB. Then you shall see whether /data are mounted as RO or RW.
Click to expand...
Click to collapse
Okay, just ran your command and could not find /data at all.
I can see /proc /dev /sys /run but not /data
Maybe it has not been mounted at all?
Sorry, I am not very experienced with this but I am familiar with the terminal
How do I mount /data partition ?
android smartphones are encrypted by default. simply factory reset is enough nowadays to render userdata unrecoverable. on factory reset, the encryption key is securely deleted. there is no way to recover encryption key, therefore no way to decrypt data.