First download the leak using my torrent in attachments. You also need s-off and an eng bootloader
1. Extract to wherever you want.
2. Put radio.img, boot.img (rename boot_signed.img to boot.img) and system.img from the extracted zip on to internal or external depending what is the first mountpoint in recovery
3. Reboot to recovery
4a. Use superwipe script or wipe manually
4b. wait for reboot mount sdcard and all partitions in mounts and storage
5. Run these from recovery with your phone plugged in to computer
Code:
adb shell
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/system.img of=/dev/block/mmcblk0p29
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p22
reboot
Note flashing the radio is optional but not necessary to run the rom just allows better service and all that that normally comes with an updated radio
6. Flash superuser package http://androidsu.com/superuser/
7. Boot up and enjoy
This method won't change you're hboot or effect s-off or bootloader status
8. ??????
9. PROFIT!!!!!111!!!1
so this is the method for people without s=off? if so, YAY!
(i dont feel like s=off'ing just yet)
ziggy46 said:
so this is the method for people without s=off? if so, YAY!
(i dont feel like s=off'ing just yet)
Click to expand...
Click to collapse
well then you can't flash the boot.img this way but yes. you would have to fastboot flash boot boot.img just like you normally would
sportsstar89 said:
well then you can't flash the boot.img this way but yes. you would have to fastboot flash boot boot.img just like you normally would
Click to expand...
Click to collapse
do you need an external sd card
EclipzeRemix said:
do you need an external sd card
Click to expand...
Click to collapse
Not if you're using a recovery that mounts the internal
This is only for tmo though right
sportsstar89 said:
Not if you're using a recovery that mounts the internal
Click to expand...
Click to collapse
ok cool
Quick question:
Would fastboot flash boot boot.img, fastboot flash radio radio.img, and fastboot flash system system.img all achieve the same or does it have to be done by dd?
rbaruch said:
This is only for tmo though right
Click to expand...
Click to collapse
unless you have S-OFF and Super CID
Keylogger_0 said:
Quick question:
Would fastboot flash boot boot.img, fastboot flash radio radio.img, and fastboot flash system system.img all achieve the same or does it have to be done by dd?
Click to expand...
Click to collapse
Not as efficient and clean trust me just do it this way
sportsstar89 said:
Not as efficient and clean trust me just do it this way
Click to expand...
Click to collapse
i'm more comfortable doing it over fastboot compared to dd, because i know for a fact that if you mess up dd commands, it will permanently brick the phone. I remember reading where one guy forgot to put a number after the mmcblk0p and it broke the phone
Keylogger_0 said:
i'm more comfortable doing it over fastboot compared to dd, because i know for a fact that if you mess up dd commands, it will permanently brick the phone. I remember reading where one guy forgot to put a number after the mmcblk0p and it broke the phone
Click to expand...
Click to collapse
if thats the way you prefer go for it but im not responsible either way if you brick it
sportsstar89 said:
if thats the way you prefer go for it but im not responsible either way if you brick it
Click to expand...
Click to collapse
I'll just place all of the blame on you xD
Keylogger_0 said:
I'll just place all of the blame on you xD
Click to expand...
Click to collapse
ha it's a common theme when n00bs try to do something then there like my phone won't turn on your broke it lol
i keep on getting
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root>if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
C:\Root>if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root> if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
help
EclipzeRemix said:
i keep on getting
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root>if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
C:\Root>if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root>dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\Root> if=/sdcard/radio.img of=/dev/block/mmcblk0p17
of=/dev/block/mmcblk0p17 was unexpected at this time.
help
Click to expand...
Click to collapse
you didn't adb shell it's asking windows if in knows a linux command
Omg downloaded in less than a minute with the torrent!
i lost root after flash wtf...
Jetta2_MTL said:
i lost root after flash wtf...
Click to expand...
Click to collapse
Well it's a stock rom so that is to be expected and obviously you did not read the complete tutorial where it tells you to flash su
C:\Root>adb shell
~ # dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd: can't open '/sdcard/radio.img': No such file or directory
~ # dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd: can't open '/sdcard/radio.img': No such file or directory
~ # dd if=/sdcard/system.img of=/dev/block/mmcblk0p29
dd if=/sdcard/system.img of=/dev/block/mmcblk0p29
dd: can't open '/sdcard/system.img': No such file or directory
~ #
-_- help, and i know i put all three files in there and mounted sdcard
Related
Hey all
I'm asking for your help, because i can't boot on my S3 !
I have a reboot loop, and i want to reinstall stock rom throug Clockwork, but i can't mount my internal sdcard... and i have no external sdcard so i can't do anything !
So my problem is i can't move a rom from my PC to my phone because i can't access my internal storage...
Any tip ?
Thanks ! (Sorry i'm not english so... ahah)
Magickalash said:
Hey all
I'm asking for your help, because i can't boot on my S3 !
I have a reboot loop, and i want to reinstall stock rom throug Clockwork, but i can't mount my internal sdcard... and i have no external sdcard so i can't do anything !
So my problem is i can't move a rom from my PC to my phone because i can't access my internal storage...
Any tip ?
Thanks ! (Sorry i'm not english so... ahah)
Click to expand...
Click to collapse
If you want to install a stock ROM, why not just grab a firmware tar and flash with ODIN?
Anyway, assuming that you somehow have a CWM-flashable ZIP of the stock ROM and you're using a custom CWM recovery, you can push files through ADB:
Install Kies so that all the required drivers are installed;
Grab SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682 and extract the ADB folder;
Attach a USB cable to the phone and to the computer;
Use CWM to mount /sdcard;
Open a Command Prompt in the folder where you extracted ADB;
run "adb shell";
run "ls /sdcard" and verify that your internal SD card is mounted (are the files that are on your internal SD card in that list?);
if it is mounted, run "exit" and then type "adb push", and then a space, and drag the ZIP file to the command prompt, add another space and then add "/sdcard" and press enter so you have something like this:
"adb push AStockROM,zip /sdcard"
qwerty12 said:
If you want to install a stock ROM, why not just grab a firmware tar and flash with ODIN?
Anyway, assuming that you somehow have a CWM-flashable ZIP of the stock ROM and you're using a custom CWM recovery, you can push files through ADB:
Install Kies so that all the required drivers are installed;
Grab SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682 and extract the ADB folder;
Attach a USB cable to the phone and to the computer;
Use CWM to mount /sdcard;
Open a Command Prompt in the folder where you extracted ADB;
run "adb shell";
run "ls /sdcard" and verify that your internal SD card is mounted (are the files that are on your internal SD card in that list?);
if it is mounted, run "exit" and then type "adb push", and then a space, and drag the ZIP file to the command prompt, add another space and then add "/sdcard" and press enter so you have something like this:
"adb push AStockROM,zip /sdcard"
Click to expand...
Click to collapse
Thanks for your answer, but i already tried with adb shell.
When i go to the "sdcard" folder, it's empty !
Maybe I'll just have to buy a microSD tomorrow and then it'll work... But i don't want to wait until tomorrow :silly:
(On CWN, i have "Error mounting /sdcard" all the time... But it's because i only have my internal storage right ?
Thanks
Magickalash said:
Maybe I'll just have to buy a microSD tomorrow and then it'll work... But i don't want to wait until tomorrow :silly:
Click to expand...
Click to collapse
I know what you mean
(On CWN, i have "Error mounting /sdcard" all the time... But it's because i only have my internal storage right ?
Thanks
Click to expand...
Click to collapse
With CWM Recovery 5.5.0.4 (CF 1.5) I can do this to get to the internal SD card:
install zip from sdcard -> choose zip from internal sdcard
and the card should be mounted on /data/media
qwerty12 said:
I know what you mean
With CWM Recovery 5.5.0.4 (CF 1.5) I can do this to get to the internal SD card:
install zip from sdcard -> choose zip from internal sdcard
and the card should be mounted on /data/media
Click to expand...
Click to collapse
Dude, you just saved my night
Thanks <3
Get an SD card and backup the complete phone memory using CWM
qwerty12 said:
I know what you mean
With CWM Recovery 5.5.0.4 (CF 1.5) I can do this to get to the internal SD card:
install zip from sdcard -> choose zip from internal sdcard
and the card should be mounted on /data/media
Click to expand...
Click to collapse
I have the same problem as op in his first post as well as "Error mounting SD card". I tried the quoted instructions above and then the commands for adb, but on typying run adb shell and run ls /sdcard nothing happens. Could this be because I have jelly bean 4.1.2 and samsung removed the USB-mass torage feature in it for internal SD-cards?
I have the same exact CWM version.
If I type "run adb shell" (with the quotation) marks I get:
Run.exe
---------------------------
Error: Couldn't find adb shell anywhere.
I even looked in the PATH
I also tried appending the following extensions:
[1]: .exe
[2]:
run "ls /sdcard" gives:
Run.exe
---------------------------
Error: Couldn't find ls /sdcard anywhere.
I even looked in the PATH
I also tried appending the following extensions:
[1]: .exe
[2]:
Just to experiment I tried to mount sd card in cwm after choose zip - still get "Error mounting SD Card".
Also if I go into my data folder via CWM I don't have a media folder, but I guess that's because im inside the wrong partition.
And just to be clear about the command part. My ADB folder is located at C:\ADB
I opened elevated command prompt, typed "cd C:\ADB" (without quotation marks), then enter. Then i ran the adb shell and ls /sdcard commands.
I also restarted computer after installing KIES.
edit: my goal was to transfer nandroid backup to phone and do a restore, guess I'll have to go the odin route -> flash stock rom, then connect phone to windows and transfer the nandroid.
evilperro said:
I have the same problem as op in his first post as well as "Error mounting SD card". I tried the quoted instructions above and then the commands for adb, but on typying run adb shell and run ls /sdcard nothing happens. Could this be because I have jelly bean 4.1.2 and samsung removed the USB-mass torage feature in it for internal SD-cards?
I have the same exact CWM version.
If I type "run adb shell" (with the quotation) marks I get:
Run.exe
---------------------------
Error: Couldn't find adb shell anywhere.
I even looked in the PATH
I also tried appending the following extensions:
[1]: .exe
[2]:
run "ls /sdcard" gives:
Run.exe
---------------------------
Error: Couldn't find ls /sdcard anywhere.
I even looked in the PATH
I also tried appending the following extensions:
[1]: .exe
[2]:
Just to experiment I tried to mount sd card in cwm after choose zip - still get "Error mounting SD Card".
Also if I go into my data folder via CWM I don't have a media folder, but I guess that's because im inside the wrong partition.
And just to be clear about the command part. My ADB folder is located at C:\ADB
I opened elevated command prompt, typed "cd C:\ADB" (without quotation marks), then enter. Then i ran the adb shell and ls /sdcard commands.
I also restarted computer after installing KIES.
edit: my goal was to transfer nandroid backup to phone and do a restore, guess I'll have to go the odin route -> flash stock rom, then connect phone to windows and transfer the nandroid.
Click to expand...
Click to collapse
Try just typing "ls" to see what folders you have. If you type "ls /sdcard" it shows nothing because the /sdcard in root is not a real folder, it is a link. Try "ls", after that try "ls /storage". I know my internal sdcard can be shown if I do "ls /storage/sdcard0". Hope that helps.
wangdaning said:
Try just typing "ls" to see what folders you have. If you type "ls /sdcard" it shows nothing because the /sdcard in root is not a real folder, it is a link. Try "ls", after that try "ls /storage". I know my internal sdcard can be shown if I do "ls /storage/sdcard0". Hope that helps.
Click to expand...
Click to collapse
My reply is for posterity since I solved my problem by solution mentioned in edit. I don't require more assistance at this time, and will likely not answer if someone replies.
Using these commands still nothing happens in the command prompt.
evilperro said:
My reply is for posterity since I solved my problem by solution mentioned in edit. I don't require more assistance at this time, and will likely not answer if someone replies.
Using these commands still nothing happens in the command prompt.
Click to expand...
Click to collapse
Then you mark the topic as solved .
jje
JJEgan said:
Then you mark the topic as solved .
Click to expand...
Click to collapse
I doubt I can do that since I'm not OP or moderator?
Is there an Odin cm10? I ask because my friends sd card slot does not work. Thanks
wendellc said:
Is there an Odin cm10? I ask because my friends sd card slot does not work. Thanks
Click to expand...
Click to collapse
According to this::
http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android#ROM_update_without_SDcard
You can use this method:::
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finished, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip
::::
You can do a search for " zip to tar"
But its fairly involved,,, so try above method 1st
.
Sent from my SCH-I500 using xda premium
Yeah his card slot seems to be broken, thanks
Sent from my Galaxy Nexus using Tapatalk 2
Where are they located? like baseband, boot, system files. I can flash certain imgs but not others. I am using dell streak. It's broken and i can flash all images except system.img...
Mods please don't move this, it's an old device and I need some veterans on this forum. (dell streak board is dead).
Thanks
ineedhelpman said:
Where are they located? like baseband, boot, system files. I can flash certain imgs but not others. I am using dell streak. It's broken and i can flash all images except system.img...
Mods please don't move this, it's an old device and I need some veterans on this forum. (dell streak board is dead).
Thanks
Click to expand...
Click to collapse
System files can be found in the phones /system folder. Boot files can be found in the root directory ( / ) of the phones filesystem and will have names such as init.rc, etc. If your talking about dumping the boot.img file you will have to figure out what partition block the boot partition is by running the command from terminal emulator or ADB shell:
Code:
mount
Taking note what block the boot partition is then run the following command:
Code:
dd if=path/to/boot/partition of=mnt/sdcard/boot.img
This will dump your boot.img to your sd-card.
Baseband isn't something you can conventionally extract form the phone but similar to baseband is RIL which can be found in /system/lib with a name similar to dell-ril.so.
Sent from my SCH-I535 using xda premium
shimp208 said:
System files can be found in the phones /system folder. Boot files can be found in the root directory ( / ) of the phones filesystem and will have names such as init.rc, etc. If your talking about dumping the boot.img file you will have to figure out what partition block the boot partition is by running the command from terminal emulator or ADB shell:
Code:
mount
Taking note what block the boot partition is then run the following command:
Code:
dd if=path/to/boot/partition of=mnt/sdcard/boot.img
This will dump your boot.img to your sd-card.
Baseband isn't something you can conventionally extract form the phone but similar to baseband is RIL which can be found in /system/lib with a name similar to dell-ril.so.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks for your help. But are the files located in the innersd card? or actual hardware? My phone still boots with no innersd card, so I suspect it's located in the hardware? Does ADB give me access to the actual hardware? (something like BIOS). Thanks a ton.
Yes ADB does give you access to the actual hardware or where the system is mounted
Sent from my Vivid 4G using Tapatalk 4 Beta
ineedhelpman said:
Thanks for your help. But are the files located in the innersd card? or actual hardware? My phone still boots with no innersd card, so I suspect it's located in the hardware? Does ADB give me access to the actual hardware? (something like BIOS). Thanks a ton.
Click to expand...
Click to collapse
The files in the /system directory are located on the internal sd-card as part of the /system partition, so is the RIL. The boot.img partition is a part of the tablets internal file system. All of the above mentioned things can be acessed with ADB which gives your access to your devices file system. The reason the device will still boot without a system.img existing is because the device will go into fastboot mode (More integrated with the devices hardware) which is the phone's bootloader mode (Similar to BIOS). Fastboot mode, and the bootloader is separate from the regular Android file system (Semi similar to interfacing with hardware, fastboot is a lower level interaction with the devices file system, the accessing files on your device through ADB) containing boot.img, recovery.img, system.img, cache. img, you can interface with fastboot through fastboot commands and booting your device into fastboot mode or from adb running the command:
Code:
adb reboot-bootloader
That being said if someone were to mess up the PBL (Primary Bootloader), and SBL (Secondary Bootloader) partition on their device then fastboot mode would very likely no longer be accessible.
shimp208 said:
The files in the /system directory are located on the internal sd-card as part of the /system partition, so is the RIL. The boot.img partition is a part of the tablets internal file system. All of the above mentioned things can be acessed with ADB which gives your access to your devices file system. The reason the device will still boot without a system.img existing is because the device will go into fastboot mode (More integrated with the devices hardware) which is the phone's bootloader mode (Similar to BIOS). Fastboot mode, and the bootloader is separate from the regular Android file system (Semi similar to interfacing with hardware, fastboot is a lower level interaction with the devices file system, the accessing files on your device through ADB) containing boot.img, recovery.img, system.img, cache. img, you can interface with fastboot through fastboot commands and booting your device into fastboot mode or from adb running the command:
Code:
adb reboot-bootloader
That being said if someone were to mess up the PBL (Primary Bootloader), and SBL (Secondary Bootloader) partition on their device then fastboot mode would very likely no longer be accessible.
Click to expand...
Click to collapse
Thanks. That means if I can boot into fastboot then my hardware has no problem? Then I am wondering why would some image fail to flash? Since system.img is flashed onto the innersd card, then I would expect no problem in flashing it onto a working sd card, no?
ineedhelpman said:
Thanks. That means if I can boot into fastboot then my hardware has no problem? Then I am wondering why would some image fail to flash? Since system.img is flashed onto the innersd card, then I would expect no problem in flashing it onto a working sd card, no?
Click to expand...
Click to collapse
If you can get into fastboot mode then your device shouldn't have a hardware problem (But it is still possible for there to be a hardware problem with other parts of your phone). What system.img file are you trying to flash? Additionally system.img is flashed to the phones internal sd-card (NAND storage) on the phones internal file system not the phones external sd-card.
shimp208 said:
If you can get into fastboot mode then your device shouldn't have a hardware problem (But it is still possible for there to be a hardware problem with other parts of your phone). What system.img file are you trying to flash? Additionally system.img is flashed to the phones internal sd-card (NAND storage) on the phones internal file system not the phones external sd-card.
Click to expand...
Click to collapse
I am trying to flash the stock system.img that came with the recovery tool (I'm using dell streak). It fails if I manually flash it, and it fails with the tool. I assume that fastboot and qdl automatically directs it to its right place? I mean I just use "fastboot -i 0x413c (that's the vendor id) system system.img" and it fails. Everytime I test I use a fresh copy of the internal sd, so it should be just as it was out of the factory. Does flashing on a blank fat32 sd card work?
can you tell the exact error message it is printing when it fails?
what does your bootloader say when in fastboot mode?
it should say something like "FASTBOOT USB" and there should be some text above this line.
can you tell us this text?
flashing images over fastboot flashes always to internal flash memory not to sdcards, thats important to know.
so you cannot format your sdcard with fat32 and expect your fastboot command to write anything to it.
In addition to what eightysoft said make sure your also running the latest version of fastboot which should be version 1.0.3.1. Plus try running the fastboot flash command without supplying the vendor id (Make sure you have disconnect any other Android devices from your computer when doing this first).
hi guys,
I've been a fool and balls up a note 10.1 (n8010).
I've got a 2nd device and was wondering if I could simply do a
Code:
dd if=/dev/block/mmcblk0 of=/extSdCard/image.img
to get a complete image of ALL partitions on the device, then on the broken one do the restore
Code:
dd if=/extSdCard of=/dev/block/mmcblk0
?
Would this keep all partition table information?
I'm assuming it'll crate an exact clone of the 2nd device?
I've already done this for the efs partition as I over wrote it by mistake....
any thoughts?
thanks.
for google...
Yes I managed to fix my device.
From the working one, I opened a adb shell from CWM recovery and ran ls -l /dev/block/platform/{name}/by-name
this gave me a list of partitions and their names.
I then then did a dd (disk dump) of the partitions to a external sd card (had to mount the sd in recovery first). This gave me 7 .img files.
I then moved the sd to the broken device, booted to TRWP recovery and used the terminal to dd them the img files back into their respective partitions.
Long story short, she be working fine now
Hello dear friends! I installed ubuntu on a memory card, and then accidentally made "Wipe data", and now the tablet will not boot recovery and immediately begins to boot ubuntu is loaded and working properly. Please tell me if I can from under linux on the tablet restore Bootloader .
Found. If you are interested then:
Loaded on the tablet installed ubuntu, created in the root file system of Linux "sdcard" folder and placed in it "twrp-jb.blob".
1. In a terminal as root flashed recovery:
dd if=/sdcard/twrp-jb.blob of=/dev/mmcblk0p4
2. scored zeros mmcblk0p3:
dd if=/dev/zero of=/dev/mmcblk0p3 bs=16 count=1
after rebooting normally booted recovery !