i have sd version of rn3, can you share your device's persist partition backup?
before disable find my phone option and sign out from your mi accout.
adb shell
su
dd if=/dev/block/mmcblk0p26 of=/storage/sdcard0/mmcblk0p26
it will backup to phone storage, can you do this? my wifi and bt not working cause of this brick.
thanks.
Here it is.
Related
Hi,
Hope someone can help, about this problem. But I think all it's comes down to now is getting ADB access via Amon_RA recovery rom, as I've tried everything I can do... link to previous post here: http://forum.xda-developers.com/showthread.php?t=642468
I'm running Window 7 Pro x64, previously the ADB was working, but after setting up some ext partition option accidentaly, (I think that it's linked to that), i've tried all options I know of by trying to manually install the drivers and removing them completely etc...
Main points, I can still access recovery image, and also the bootloader. I've succesfully flashed custom roms etc... before. And phone does not boot to rom(that's because I think it didn't install correctly, not sure)
So, i'm sort of lost now, just wondering if any developers here would kindly help or put me out my misery!
re partition your ext(2/3 for Eris base rom) ext4 might not work on Eris.
if you still facing problem remove the swap & only remain the ext partition for A2SD.
edit: and please update to v1.6.2 for the recovery***
Thanks for you response but I can't do anything within the recovery image, some options keep saying please use adb to carry out the process, but I can't get adb to detect on the phone anymore. Also I can't update the latest recovery image, as i'd need adb access....
I can't see why this is happening... perhaps its the SD card that's messed up? I could repartiotion using linux using gparted or something, but I don't know how the Hero set's up the partion.
When I try to recover using nandroid I get messages like unable to mount E:SDCARD etc...
Any clues?
did you do a dalvik wipe? y not try remove the ext partition & try restore previous nandroid?
I'm trying to run the "unofficial alpha 3" rom again but think that I need to do the following but can't figure out how. I have the Thunderg recovery rom and from reading the text below I think it means to boot into the recovery console, mount the /system partition and format it but I don't see how to get to a shell prompt from there,
Sometimes Recovery can't format /system so you must remove all files before flashing zip (bug still here):
1. Mount /system in recovery.
2. adb shell rm -rf /system/*
You get 1 error. This is ok.
Will update if I found this bug.
Can someone help ?
Cheers
Keith
You have to use ADB. Read here on how to get ADB installed and working: http://forum.xda-developers.com/showpost.php?p=10372531&postcount=3
Can I do that using ONLY my mobile phone? for example using a terminal emulator? If so, how?
Thank you
On void I installed cm 7 a2 just with the simple procedure of flashing in recovery. Then updated to cm7 a3 easily. Then I went back to void to check the audio quality. Found the quality same and also realized equalizer app didn't install on void. So tried to flash back cm7a3. But bootloop occurred. Fortunately I had a nand backup of cm7a2. So restored it and updated to a3 flawlessly.
So two learnings:
1. Sometimes direct install of cm fails. Sometimes it works.
2. Nand backup is a very good thing.
Hi!
My brand new SGS2 quickly got bad blocks on the ... /efs partition.
Talk about bad luck, radio wouldn't work. Also, odin, etc wouldn't format that properly as EFS shouldn't be deleted (even "Phone EFS clear" does not work)
After tinkering around a while, granted that you DO HAVE a backup of the /efs (when you buy the phone and root it, for the love of whatever you believe in ALWAYS BACKUP EFS), I found a way to do it properly.
If you do not have a backup (ARE U NUTS?!) try this in adb shell as root:
# cp -r /efs /sdcard/efs
If there's no error, it might work. Even if there's errors, but /sdcard/efs is not empty, it might work. If you have ._nvdata kind of files that copied successfully, you might also be able to recover something. (post here for assistance if so, i guess)
Note that regular write/reads and regular dd'ing won't work.
Anyhow.
1: root the phone
2: coy your efs backup to your sdcard (eg as /sdcard/efs in my example)
3: adb shell to the phone, su if necessary (=be root)
4: # umount /efs
5: # dd if=/dev/block/mmcblk0p1 of=/dev/null bs=1
*wait a while*
Check the number of bytes it has read and copy it, normally it should be 20971520 (20 megs)
<size> is without the "<>" eg make_ext4fs -l 293938 -a ...
6: # make_ext4fs -l <size> -a efs /sdcard/efs_new.img /sdcard/efs
7: # dd if=/sdcard/efs_new.img of=/dev/block/mmcblk0p1 bs=1
*wait ages*
8: # mount -text4 /dev/block/mmcblk0p1 /efs
*check theres no error*
9: # reboot
10: # verify you have no I/O error in dmesg
Good luck!
And remember:
This voids your warranty.
This is at your own risk.
Making mistakes/typoes in the devices names can BRICK your device.
I am not responsible if anything wrong happen.
Thanks for the howto.
Have you any idea how you got those bad blocks in the first pkace ?
nope
i wasnt doing anything special, hard the phone only recently
at one reboot it didnt want to take my sim card pin anymore, then later radio wouldnt turn on at all (cause it couldn't read /efs)
That's pretty scary...:s
Send from my Galaxy S II running on VillainRom.
This happened to my samsung nexus s do you think there is a similar recovery for my device? i hhave some bad blocks
Any news for a nexus s bilboa I've got bad blocks :s and sometimes radio wont start and crash I have atm 8 badblocks, if it is not fixable can I make a workaround like on cm7 that original efs partition is untouched (in cm7 for i9000)
Thanks
Sent from my Nexus S using XDA App
You saved my life! My IMEI was completely lost and so I could recover it. Thank you very much for the guide.
I keep getting umount: not found when i try to unmount /efs. Whats wrong?
...and on the 8th day he created the SGS II!
What do i do if the EFS folder is completely empty??
you're screwed then sorry
Is your problem solved.. I am also facing same problem.
I lost my IMEI number.
Please help me out
Ok guys, your forum helped me a lot of tima, but now i'm in a big trouble....
This morning my S II decided to don't boot.... more precisely, it start booting, but never end.... i assure you that i've not installed nothing suspicius in the last days....
there is no problem in solving this.... Clockworkmod-->factory reset-->done.... but before this i want to save some very important data in my phone added recentely.... some contacts not saved in the sim card and some very important documents in the internal memory....
I mount a cyanogen 9, and my phone is rooted.
I'm able to use the clockworkmod without problems.
I googled a while and i fount that there is no way to read the internal memory of my phone if i'm not able to boot it....
So i found the adb fastboot program and it seems useful for a backup....
But the command "backup" need a confirmation from the device and for me is impossible.
the command "pull" return me that there are 0 files in the sdcard folder....
So what can i do?
There is some other way for a backup of my internal data?
Have you some advices to let me use the backup function with adb?
Please guys i need you help....
Thank you in advance....
So basically, twrp recovery was not mounting my internal memory(phone was perfectly working) and I made the crucial mistake of not backing up my stuff before following a guide to fix it which consisted going in twrp recovery and repairing/changing system files. That resulted in everything being gone. Now, i used my phone as little as possible and have tried using phone recovery programs like dr.fone without any success. I've tried by following this answer here: https://stackoverflow.com/a/41397418 and I got a mmcblk0p66.raw file which is userdata after i used the commands and is around 55gb and the whole mmcblk0.raw file itself which is around 61gb. All this by forwarding from a cygwin64 terminal to another cygwin64 terminal through adb.
Code:
adb shell
ls -al /dev/block/platform/*phoneSpecificFolder*/by-name
I've tried mounting it with osfmount and then using recovery programs and using linuxreader to mount it and no success. I'm baffled how this 55+ GB files contain either empty folders or no files found and such. Am i doing something wrong or is it just me that actually STUPIDLY deleted everything? Also, I would do
Code:
adb shell
su
dd if=/dev/block/mmcblk0p65 of=/sdcard/userdata.img
but I would effectively overwrite any remains of files left due to it being 55gb in space. Much thanks. Every answer is appreciated.
Note: I mainly care about recovering my photos,videos
Xiaomi Mi Max 2 64BG