i have received another moto razr maxx hd and willing to ask everyone who has the same device. if you don't mind, please generate razr xt926 scatter file and post here (the generated file isn't big).
how to generate scatter:
1. plug device
2. open adb, and type:
adb shell
Code:
cat /proc/mtd
or
Code:
cat /proc/emmc
to save it into yours sd-card, type :
Code:
cat /proc/mtd > /sdcard/firmware.info
or
Code:
cat /proc/mtd > /sdcard/firmware.info
I have the same problem but with xt907 can i use the same code to get the scatter
:good:
TOYEP said:
i have received another moto razr maxx hd and willing to ask everyone who has the same device. if you don't mind, please generate razr xt926 scatter file and post here (the generated file isn't big).
how to generate scatter:
1. plug device
2. open adb, and type:
adb shell
Code:
cat /proc/mtd
or
Code:
cat /proc/emmc
to save it into yours sd-card, type :
Code:
cat /proc/mtd > /sdcard/firmware.info
or
Code:
cat /proc/mtd > /sdcard/firmware.info
Click to expand...
Click to collapse
I HAVE THE SAME PROBLEM BUT WITH XT907 CAN I USE THE SAME CODE TO GET THE SCATTER :good:
Related
well i am on nmv 2.11.30(ics) rom nw, and i went ino recovery to do a nandroid restore of nmv 1.11.30(gb) and im getting this error - MD5 MISMATCH ..
help plz
i did rename tht folder but that cant be the reason rite
if i dnt get it back then ics bcums my daily rom !!! ..
Make a new MD5 hash, from here:
http://forum.xda-developers.com/showthread.php?t=976453
adb shell
# cd /sdcard/clockworkmod/backup/yourbackupfilefolder
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse
Greetz
sorry i dint understand how to do it, dnt knw wher to type this _ adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
Make sure the name of the backup has no spaces and no special characters beside a:
-
rrohanjs said:
sorry i dint understand how to do it, dnt knw wher to type this _ adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse
You have to connect your device to your PC and boot into recovery.
Then, open up a Windows command prompt (assuming you use Windows, otherwise a Linux terminal) and navigate to the folder were the adb.exe (or adb for Linux) is stored.
Since you have rooted and unlocked your phone I assume you downloaded the Android SDK. This means that generally the adb.exe will be found in C:/android-sdk/platform-tools (or well, wherever you installed it).
Once you've navigated to the correct folder you can input those commands in the command prompt.
"adb shell' will start a shell running on your Nexus which you can control through your computer. The following commands are Linux commands to:
a) change directory to where your backup is saved
b) rm (remove) the existing .md5 file
c) create a new md5 hash
Good luck,
Greetz
I have tried following command on ADB to extract partition, but failed.
source:fciotti.com/2017/02/26/clone-android-memory
Code:
chmod +r /dev/block/mmcblk0
returns
Code:
Bad mode
Code:
adb pull /dev/block/mmcblk0 "mmc.img"
returns
Code:
remote permission denied
I have post a question on stack exchange, and found a command working but failed after dumping 4gb on sdcard (not directly to pc) because of file system.
source:android.stackexchange.com/questions/185433/problem-with-coping-mmcblk0-to-pc?noredirect=1#
Code:
adb exec-out "su -c 'cat /dev/block/mmcblk0'" > mmc.img
but it create a 0kb img file.
Please anyone help.
I soft bricked my tablet trying to change the boot splash on the tablet. I need the stock param.bin to flash back onto the tablet to get it to boot again. I can only get into download mode at this point.
To do this, first we have to find where the param.bin file resides, so fire up a terminal:
Code:
su #gain root
cd /dev/block/platform #this will take us to the folder we need the name of to run the dd command later
ls #copy the output of this command and cd in the next command
cd *pastethefolder* #the folder copied from previous command
cd by-name # change into by-name dir
ls #you will see PARAM in the output of ls
pwd #the output of this command will give us the absolute path of the param file
#copy the output of pwd
#now we can run the command to pull the param.bin file with the path copied from previous pwd command
dd if=/dev/block/platform/********/by-name/PARAM of=/sdcard/param.bin bs=4096
#this will give you a copy of the stock param.bin.
I really appreciate anyone who would possibly take the time to do this and get it to me sometime soon.
Is this what you're after?
Yes and it's now fixed you are awesome
1. On your computer, convert the mp3 file to a 3gp file with a particular file name:
Code:
laptop $ ffmpeg -i path/to/some/music.mp3 -ar 8000 /tmp/pending_voicemail_greeting.3gp
2. Push that file to your phone and cleanup:
Code:
laptop $ adb push /tmp/pending_voicemail_greeting.3gp /sdcard && rm /tmp/pending_voicemail_greeting.3gp
3. Open the Google Fi app and record a new voicemail containing whatever garbage you want. (It won't be used.) It will show you the screen to preview it before committing to it. DO NOT COMMIT TO IT. Instead, just leave that screen open.
4. Overwrite the preview file with your file:
Code:
laptop $ adb shell
phone $ su
phone # cat /sdcard/pending_voicemail_greeting.3gp > /data/data/com.google.android.apps.tycho/files/pending_voicemail_greeting.3gp && rm /sdcard/pending_voicemail_greeting.3gp
5. Press "keep" in the Fi app to upload the preview as your new voicemail.
zte nubia z5s mini nx406e - version android 4.4.4
Greetings, could someone guide me ?
I want to be able to update this device,
to an android version a little more current,
if I have a copy of the system made with twrp recovery,
starting from there, how can I extract everything to be able to develop.
I know that everything that is needed is within the system itself,
I would appreciate any guidance.
Please do not block what I write again, like the one here
I just tried to explain myself in a way that they could understand me better, excuse my bad english.
Procedure performed to extract .img
adb version: Android Debug Bridge version 1.0.32 - > files used: googledrivers
adb>adb devices
List of devices attached
0123456789 device
previously rooted device -> with this version of the super su -> files here SuperSu
adb shell
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 9 12288 mmcblk0p9 -> boot
179 24 1280000 mmcblk0p24 -> system
[email protected]:/ # cat /dev/block/mmcblk0p9 > /sdcard/boot_pull.img
[email protected]:/ # cat /dev/block/mmcblk0p24 > /sdcard/system_pull.img
[email protected]:/ # exit
[email protected]:/ $ exit
adb>adb pull /sdcard/system_pull.img stock_system.img
2773 KB/s (1310720000 bytes in 461.535s)
img to download from here: stock_system.img
adb>adb pull /sdcard/boot_pull.img stock_boot.img
2792 KB/s (12582912 bytes in 4.400s)
img to download from here: stock_boot.img
Procedure to extract kernel
1.- Download the tool: android bootimg tools
2.- Extract the file using: tar xvzf android_bootimg_tools.tar.gz
It contains two binaries:
unpackbootimg
mkbootimg
3.-Then run: ./unpackbootimg -i boot.img -o unpack
./unpackbootimg -i <filename.img> -o <output_path>
It will contain:
boot.img-base
boot.img-cmdline
boot.img-pagesize
boot.img-ramdisk.gz ----> ramdisk
boot.img-zImage ----> kernel
archive: boot-img-zImage
to extract: boot.img-ramdisk.gz
use command: gunzip -c boot.img-ramdisk.gz | cpio -i
I'm looking at how to extract kernel sources from: boot.img-zImage