hi everybody
well i have a problem with the recovery of mt3gs the message is this when i tried to put the option Apply sdcard:update.zip
E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
installation aborted
can you help me? please!
that means the stock recovery is rejecting the update.zip. Take the recovery image that I'm about to give you, then place it in the same directory as your fastboot. After this, boot into fastboot by either holding volume down + power or the back button + power, then press the power button again. Then go to your computer, and on the terminal or command prompt, type cd [the directory where fastboot is] and type fastboot flash recovery recovery.img! If it successfully flashes the recovery(which it should) then your recovery will be Clockworkmod.
Hitorijanae said:
that means the stock recovery is rejecting the update.zip. Take the recovery image that I'm about to give you, then place it in the same directory as your fastboot. After this, boot into fastboot by either holding volume down + power or the back button + power, then press the power button again. Then go to your computer, and on the terminal or command prompt, type cd [the directory where fastboot is] and type fastboot flash recovery recovery.img! If it successfully flashes the recovery(which it should) then your recovery will be Clockworkmod.
Click to expand...
Click to collapse
i don't know how can i use de adb?
i'm using the terminal and when i put
flash_image recovery /sdcard/recovery.img
the terminal said this:
mtd: read all-zero block at 0x0000000; skipping
error reading /sdcard/recovery.img
Have you installed the android sdk?
hey thanks guys for help me.
i was solved the problem, i install the spring file and the recovery appeared
Hitorijanae said:
that means the stock recovery is rejecting the update.zip. Take the recovery image that I'm about to give you, then place it in the same directory as your fastboot. After this, boot into fastboot by either holding volume down + power or the back button + power, then press the power button again. Then go to your computer, and on the terminal or command prompt, type cd [the directory where fastboot is] and type fastboot flash recovery recovery.img! If it successfully flashes the recovery(which it should) then your recovery will be Clockworkmod.
Click to expand...
Click to collapse
whats the version of this recovery img??
Help with my recovery
Please help me, I was trying to upgrade my mt3gs to ics so I flash a recovery on it, ever since then I can boot my phone into recovery mode. Please how can I solve this problem?.
EDIT: please delete! http://forum.xda-developers.com/showthread.php?p=44013269 a "Format data" was what I needed and an install of SuperSU.
Here's what I did:
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery ~/Downloads/openrecovery-twrp-2.6.0.0-flo.img
reboot, go into twrp, click reboot, yes to root. Now it's stuck at the splash screen (with the colorful logo, not the Google + open padlock)
If I go back into twrp and try to sideload SuperSU then I get "error: closed".
I can adb push UPDATE-SuperSU-v1.51.zip but trying to flash it fails.
On the mount screen it says: Storage: Internal Storage (0MB).
I do not see anything helpful in the recovery.log I pulled:
Code:
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
Error flashing zip '/sdcard/UPDATE-SuperSU-v1.51.zip'
Updating partition details...
I:Unable to mount '/usb-otg'
Not quite sure how to continue.
Tried flashing firmware upgrade on I747.
File corruption error occurs.
Log File from TWRP (1)
Running boot script...
I:/sbin/postrecoveryboot.sh process ended with RC=0
Finished running boot script.
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/ce166490'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:TWFunc::Fixup_Time: Setting time offset from file /data/time/ats_2, offset 1390591287137
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/I747_UCUFNE4_Base_Firmware.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/I747_UCUFNE4_Base_Firmware.zip.md5
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
I:read key e=3 hash=20
I:read key e=65537 hash=20
I:2 key(s) loaded from /res/keys
E:footer is wrong
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/I747_UCUFNE4_Base_Firmware.zip'
Updating partition details...
Iata backup size is 3245MB, free: 3053MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/I747_UCUFNE4_Base_Firmware.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/I747_UCUFNE4_Base_Firmware.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Log File from TWRP (2)
I747 UCUFNE4 Base Firmware
Preparing to Flash!
Extracting files and setting permissions...
minzip: Extracted file "/tmp/NON-HLOS.bin"
minzip: Extracted file "/tmp/aboot.mbn"
minzip: Extracted file "/tmp/dd"
minzip: Extracted file "/tmp/rpm.mbn"
minzip: Extracted file "/tmp/sbl2.mbn"
minzip: Extracted file "/tmp/sbl3.mbn"
minzip: Extracted file "/tmp/tz.mbn"
Verifying checksums...
FILE CORRUPTION DETECTED!!!
ABORTING FLASH.......
Cleaning up...
script result was [7]
Updating partition details...
Iata backup size is 3245MB, free: 3053MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Forgot to say the phone is an I747 ATT. Running TWRP 2.7.1
Did you check the md5sum on the download? The NE4 package has been confirmed working.
Yes. The md5 did check out. It was correct.
One other note. When trying to install on TWRP. I checked the zip signature box, and i did receive the error message zip signature failed.
...
Dumb question can I flash through mobile odin, using the OTA/update ZIP file option. All other options require a .tar file
Thanks for any help.
Currently I'm parsing the updater-script and rechecked all of the sha1 checksums and they are all processing correctly. At least on the pc they are.
So I checked the md5 on the pc transfered the file to the phone and rechecked the md5.
All is good. So I know the file on the phone is the same as the file on the pc. Hence the checksums on the phone are correct.
So it leads me to believe the problem could be in the directory or file permissions??
I'm relatively new to this field, but I can tell you with 100% definition that the checksums are correct and the md5 file is 100% correct. At least on the pc they are.
Try using twrp 2.6.3.1, or maybe philz recovery. Could be a compatibility issue between the recovery and update binary.
DocHoliday77 said:
Try using twrp 2.6.3.1, or maybe philz recovery. Could be a compatibility issue between the recovery and update binary.
Click to expand...
Click to collapse
OK. I have new information to report back. (To Repeat I've checked the md5)
I flashed
twrp 2.6.3.1 ->File Corruption Detected
Philz Recover ->File Corruption Detected
CWM 6.0.4.7 -> File Corruption Detected
However on CWM when I click show log
I get
Install from sdcard complete.
I:using /data/media for /sdcard/0/clockworkmod/.last_install_path.
I:Can't partition non mmcblk device:/devices/platform/msm_sdoc.3/mmc_host/mmc1
Just rechecked...
Received the same exact error message through Philz Recovery. (in the log)
I've also run the Fix Permisions Tool. (In case the problem was a permision) However same outcome.
Any other ideas greatly appreciated.
Thanks to Doc for all the help also.
Non mmcblk device?!!!? Never seen that before, and it is wrong! The S3 is an mmcblk device! If you use a root capable file manager you can browse to /dev/block and you will see all the different mmcblk0p* partitions.
I hate to say it but i have no idea what could be going on. I hope someone else might have an idea. I am sorry for all the trouble. Hopefully we will figure it out soon. Ill try to find a different update-binary to see if that might help...
Hi all,
I need some help.
My wife have an Samsung i747 phone which she used to store there all the pictures of our boys from the past 2 years. She never backuped the pictures.
Starting two weeks ago the phone got stuck very often, and became very hot. Last week the phone didn't power on anymore.
I could enter to download mode, but didn't succeed to go Recovery mode except of few times (I know it sounds weird, but I try a lot.. most of the times the text "Recovery Booting" for one second, and than I got the "Samsung S III" logo and the device shut down..).
So if I understood right, the was soft brick.
The few times i succeeded enter recovery mode it always print errors of something like "e: mount /system | /data | /cache failed".
I saw this thread and decide to give it a chance.
I didn't know what is the version of the bootloader (or anything else... my wife neither) so I go on the 4.3 bootloader.
I flashed the twrp 2.6.3.0 recovery and I saw there in backup section that the data is about 12giga. I couldn't make any backup of anything. I tried to reset to factory settings (without wiping the user data) and it failed(I even tried to backup the recorvery and boot partition that weights 10 mb and it failed).
I tried to flash from my sd card the:
d2att_I747UCUEMJB_bootloader
d2att_I747UCUEMJB_modem
d2att_Kernel_Stock_init.d_4.3_MJB_v1.0
AT&T_I747UCUEMJB
and everything worked but the AT&T_I747UCUEMJB.zip .
I tried flash newer twrp version, at first 2.6.3.1 and lastly 2.8.7.0. In all the same result - I can't flash the AT&T_I747UCUEMJB.zip file. the error says something about the updater (I can't read the whole error, the screen cutting the line).
Still when I open the recovery it says it couldn't load /system /cache /data partitions. I tried to change the fs type, wiping the partition, formatting - but nothing worked.
Can any one help me get the pictures out? They mean a lot to us, except the pictures from the I747 we only have a few pictures from the last 2 years.
Thanks!
p.s
I thinks that this is the log from twrp when I tried to install the AT&T_ rom:
Code:
Installing '/external_sd/AT&T_I747UCUEMJB.zip'...
Checking for MD5 file...
I:Cannot find file /external_sd/AT&T_I747UCUEMJB.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Creating filesystem with parameters:
Size: 1572864000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 6000
Label:
Blocks: 384000
Block groups: 12
Reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
error: file_write: write: I/O error
E:Error executing updater binary in zip '/external_sd/AT&T_I747UCUEMJB.zip'
Error flashing zip '/external_sd/AT&T_I747UCUEMJB.zip'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'flash_done'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'action_complete'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'clear_vars'
I:Set page: 'flash_done'
I:Set page: 'rebootcheck'
I:Set page: 'confirm_action'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'wipe'
I:Set page: 'advancedwipe'
I:Set page: 'wipe'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Did you try mounting that data partition in TWRP? I assume you did and that didn't work for you.
You mentioned that you tried chnaging the fs, wiping, formatting. Which partitions are you referring to?
audit13 said:
Did you try mounting that data partition in TWRP? I assume you did and that didn't work for you.
You mentioned that you tried chnaging the fs, wiping, formatting. Which partitions are you referring to?
Click to expand...
Click to collapse
I tried to mount the partitions. It didn't work. In the Mount section of twrp when I clicking the system and cache partition nothing happens. And in the backup section it shows that the size of system and cache partitions is 0MB.
I tried to change the /system /cache partitions. I didn't try the /data partition because I'm afraid losing all my data.
I forgot to mention that right now, the only way I can boot to recovery and download mode is by the sd card with the debrick image.
Since you can boot with the debrick image, did you try reflashing a bootloader or modem to the phone?
Sounds like you have the same problem as this XDA member: http://forum.xda-developers.com/galaxy-s3-att/help/failed-to-mount-data-frozen-factory-t3181035
audit13 said:
Since you can boot with the debrick image, did you try reflashing a bootloader or modem to the phone?
Sounds like you have the same problem as this XDA member: http://forum.xda-developers.com/galaxy-s3-att/help/failed-to-mount-data-frozen-factory-t3181035
Click to expand...
Click to collapse
If I understand correctly, its not the same problem. He couldn't mount just the /data while I can't /data /system /system. Another differnce is that his problems occured after he flashed things, mine was with the original recovery, and I can't do a factory reset.
Please tell me if I'm wrong.
The other user could only boot his phone using a debrick image in the phone. Will your phone boot without the sdcard?
The other user had to flash a bootloader in order to boot without the sdcard in the phone.
audit13 said:
The other user could only boot his phone using a debrick image in the phone. Will your phone boot without the sdcard?
The other user had to flash a bootloader in order to boot without the sdcard in the phone.
Click to expand...
Click to collapse
I can't boot when the sdcard isn't there.
Should I try to flash another bootloader? If so, can you tell me what bootloader should I install.
The most important thing to me right now is to get my pictures back, so currently I don't care booting with the sd card. After I get my pictures I would like to make the phone work without the sd card.
Thanks!
Do you know which bootloader was on the phone before you started flashing bootloaders?
I am not sure if flashing a bootloader and recovery will get you access to the pictures. I have never experienced a bricked s3.
audit13 said:
Do you know which bootloader was on the phone before you started flashing bootloaders?
I am not sure if flashing a bootloader and recovery will get you access to the pictures. I have never experienced a bricked s3.
Click to expand...
Click to collapse
I don't know. But what I do know is that the first time I used the debrick sd card it shows in the download mode the "warranty bit: 0" that wasn't there before. The second time I powered on the device it shows that the warranty bit is 1.
If thats help somehow recognizing the bootloader version.
I flashed (via recovery) the bootloader maximum 2 time, and via Odin few times (every time I tried another version of the recovery..something like 5 times).
I've notice that if I trying to get into download mode and release the buttons fast, the next time the device booting its showing this screen:
And when I'm going into Recovery mode its showing this screen:
Before I did the debrick the screen I has is the first one.
I thinks the second one is the debrick, because it always shows the first image for 1-2 seconds and it is rebooting and shows the second picture.
The screen without twrp is the first screen. The second screen is how the phone would look with twrp.
The fact that the warranty bit exists in download mode means the phone has at least a 4.3 bootloader.
If the phone had a kit kat bootloader before you flashed anything, flashing the mjb bootloader is probably what bricked the phone.
Are you able to confirm which rom version was on the phone before you flashed anything? This will help determine which bootloader and modem should be flashed to the phone.
audit13 said:
The screen without twrp is the first screen. The second screen is how the phone would look with twrp.
The fact that the warranty bit exists in download mode means the phone has at least a 4.3 bootloader.
If the phone had a kit kat bootloader before you flashed anything, flashing the mjb bootloader is probably what bricked the phone.
Are you able to confirm which rom version was on the phone before you flashed anything? This will help determine which bootloader and modem should be flashed to the phone.
Click to expand...
Click to collapse
I didn't have the warranty bit in download mode before I used the debrick image, and I didn't flash anything before, the warranty bit appears only after I used the debrick image. So I guess I had the 4.1.2 bootloader (I remmeber that we were updating the phone once using Kies..about 2 years ago or something like that..).
I never flashed anything to this phone before the twrp last week after the brick happened. And My wife was using the Stock rom.
But 2 days ago when I tried following this thread I do flash (using twrp install section) a bootloader.(when the sd card inserted). I took the bootloader he recommended:
Use this bootloader for the AT&T i747 ONLY https://www.dropbox.com/s/vbyeorrxapwrots/d2att_I747UCUEMJB_bootloader.zip the one in the tread where I got mine hasn't been working so use this bootloader it is the same one just hosted by a different person.
Click to expand...
Click to collapse
Thanks for trying helping!
It's also possible that the internal memory in the phone is damaged. It does happen on occasion.
Sorry, but I am out of ideas at this point.
audit13 said:
It's also possible that the internal memory in the phone is damaged. It does happen on occasion.
Sorry, but I am out of ideas at this point.
Click to expand...
Click to collapse
I thought damaged memory is the case at first, but if so the twrp 2.6.X version wouldn't recognize that my data is about 12 giga.
How can I assure this is the case?
A couple of ideas that may be of some help.
If you can boot into TWRP again you can go to >> Advanced >> Terminal Command >> Select
and enter these commands to determine current installed bootloader and modem
Code:
getprop ro.bootloader
getprop | grep version.baseband
Also, IIRC, once you are booted into your recovery, TWRP, you should be able to remove the sdcard with the debrick image and replace it with a blank card. Then, from with the Advanced menu of TWRP can you use the File Manager to copy folders/directories.
dawgdoc said:
A couple of ideas that may be of some help.
If you can boot into TWRP again you can go to >> Advanced >> Terminal Command >> Select
and enter these commands to determine current installed bootloader and modem
Code:
getprop ro.bootloader
getprop | grep version.baseband
Also, IIRC, once you are booted into your recovery, TWRP, you should be able to remove the sdcard with the debrick image and replace it with a blank card. Then, from with the Advanced menu of TWRP can you use the File Manager to copy folders/directories.
Click to expand...
Click to collapse
getprop ro.bootloader returns I747UCUEMJB (I thinks this is because I flashed the bootloader in @theramsey3 thread when I tried to follow his instrucions.)
getprop | grep version.baseband returns nothing. I tried "getprop | grep baseband" and it returns 2 result :
[ro.baseband]: [msm]
[ro.boot.baseband]: [msm]
I already tried the File Manager option. There is nothing in /data and /sdcard directories.
Thanks!
Sorry I wasn't of more help.
i believe TWRP (at least in version 2.8.x.x and newer) it will connect to your pc as a media device, which (at least on my i747) includes both the internal sd card (including the part i imagine your worried about, pictures and videos) as well as the external storage
at which point you should be able to copy files from your phone to your pc
logoster said:
i believe TWRP (at least in version 2.8.x.x and newer) it will connect to your pc as a media device, which (at least on my i747) includes both the internal sd card (including the part i imagine your worried about, pictures and videos) as well as the external storage
at which point you should be able to copy files from your phone to your pc
Click to expand...
Click to collapse
I thinks it called MTP. I don't have the internal sd card. I have the external sd card only, so I can't copy my files.
Do you have any other idea?
Added the log of twrp if it will help somehow.
reading the log, it complains about not being able to mount the data, system, and cache partition
which to me reads as the phones internal storage is dead or almost dead, or heavily corrupted.
while i'm no expert, you may have to go to an actual expert to get the data recovered, because if recovery can't mount it then i don't really know how you could get any consumer hardware to do so
i have a fully rooted and unlocked nexus 5x,
To Start of i rooted my phone and installed twrp custom recovery after this i proceded to try and install cm13 and gapps when my install came to a conclusion (of it bieng BROKE as Hell) i decided to boot back into recovery and restore a backup i did before installing cm13 (a full backup Boot, System, System Image, Data, EFS, Cache Ect).This worked fine
Then a new Rom came out that i like the look of and decided to see if my phone would accept it, haveing previously deleted the backup i had before i tryed to make a new one, i got this from the recovery log
I:Backup Name is: '2016-10-13--20-39-38_NRD90R'
I:Full_Backup_Path is: '/data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/'
I:Calculating backup details...
* Total number of partitions to back up: 10
* Total size of all data: 10899MB
* Available space: 16400MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/
Backing up Boot...
I:Reading '/dev/block/mmcblk0p37', writing '/data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/boot.emmc.win'
Iartition Backup time: 0
* Generating md5...
I:MD5 for /data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/boot.emmc.win: 11d56bb372a47552eb72ca57de7ac225 boot.emmc.win
* MD5 Created.
Backing up System...
Error opening: '/system/app/BasicDreams' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/006b8a96ed69b064/2016-10-13--20-39-38_NRD90R/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/006b8a96ed69b064/recovery.log
I:Set page: 'action_complete'
I: operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'backup'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
Click to expand...
Click to collapse
After this i researched the BasicDreams file and the error 225, as for the basicdreams file i tryed to delete it (in root browser) but instantly came back again, and i could only find post on error 225 when restoring a backup not making one.
Please if anyone as any idea what is happening help me out.
Ben