as my title, while going to recovery and apply update.zip it's said that sdcard not mount => how come we can't run the update.zip via recovery???, and before this (first time reboot to recovery after flashing JPA) i can see the multi CSC error message as well. Maybe sth conflict between i5801 (origin firmware: I5801DXJG2) and Froyo europe Firmware (JPA, JPB...)?
Related
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
rogerodd said:
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
Click to expand...
Click to collapse
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
okantomi said:
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
Click to expand...
Click to collapse
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
rogerodd said:
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
Click to expand...
Click to collapse
The problem is that you can't flash anything from the external sdcard with v4.0.0.4. In rom manager, see if you can find"all clockwork recoveries" and find 3.2.0.0. If not, find 3.0.2.8 or 3.0.2.5 and flash one of them, preferably the latest of those I have listed. I think those will at least recognize your sdcard. If you can't do that, you will need to reflash the correct recovery the same way you did when you rooted. Remember, never flash a zip file through adb.
Good luck!
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
possible bad download... download again... also, don't think this would be an update... leave it as originally named, just choose the option to choose which zip file to install from the sd card
rogerodd said:
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
Click to expand...
Click to collapse
It sounds like you are flashing recovery ok, but you keep overwriting it with the stock recovery.
Here is some important information that should help a lot with making your new recovery "stick"and this was taken from the Idiot's guide to flashing...in the Development section, and originally written by publicanimal:
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
Boot into flash mode with 'adb reboot bootloader'
Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this section
Enter CWM with the following procedure
Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. If that happens, or if you see "starting fastboot protocol " your timing wasn't right and you need to reflash the recovery image and try it again.
See original post,below for more information.
http://forum.xda-developers.com/showthread.php?t=1130996
I'm quite new to all of this flashing stuff-- sorry if I sound like a complete newbie.
So I'm trying to get CyanogenMod on my Samsung Mesmerize (Galaxy S), though to no avail. I tried to follow the guide on the wiki located at http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide though it's not working. I can't even get CWM Recovery on it.
To get CWM Recovery, I'm following http://forum.xda-developers.com/showthread.php?t=734166 -- it says flash back to a stock kernel first, which I did via Odin and by following http://forum.xda-developers.com/showthread.php?t=881064 (I downloaded the "EC10 Full Froyo Restore Package"... not sure what the difference is between that one and EE19 but it seems to work.)
I'll go over my steps from the beginning, starting from when I'm flashing back the stock kernel on my phone:
Flash back stock kernel (EC10 Full Froyo Restore Package) using Odin (I've also tried flashing the EE19 one)
It starts up after this, however it briefly displays "FOTA wipe failed" in red and "wipe_data failed" in yellow (along with some other stuff too, but no other errors - when I use EE19 these errors occur as well)
It starts up into the default Android system recovery - I choose reboot system now
Root my phone using SuperOneClick ('yes' to install Busybox prompt)
Insert SD card, Download & install ROM Manager from the Market (following this guide which I linked up above)
Select "Flash ClockworkMod Recovery" (Current/Latest Recovery: ClockworkMod 2.5.1.2)
Select "Galaxy S i9000"
Superuser prompt appears, I click accept
ROM Manager freezes for a bit, then displays "Successfully downloaded ClockworkMod recovery!"
Choose "Backup Current ROM" - freezes for a bit, then phone begins to restart... enters default Android Recovery mode:
Install from package... Finding/opening/verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted.
When I reboot and enter the recovery mode by holding volume-power-home,
it displays "E:Can't mount /dev/block/mmcblk0p2 (No such file or directory)" at the bottom.
Also, when I try to "wipe data/factory reset" in the stock Android recovery mode, it gives this error:
E:Can't mount /dev/block/mmcblk0p3 (No such file or directory)
E:install_application_for_customer:Can't mount HIDDENSDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
I also know there's a "Manual Flash Overrride" option in ROM Manager - could I flash CWM Recovery manually and go that route somehow?
My final goal is to get CyanogenMod installed on my Mesmerize, though-- however, I need CWM Recovery to do that. Any ideas as to why CWM Recovery isn't getting installed, and how to fix the mmcblk0p2 error message in recovery mode (and if that's affecting anything)?
Thanks!
MOD EDIT:
FORUM RULES:
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Yes, and i will add ROM manager only works for Mesmerize MTD systems, and CM7 IS MTD. SO, technically you need to be on CM7 already to use ROM manager.
You don't need to use ROM Manager period.
I have to install LP1 version on my galaxy notes and since when I want to put a rom official since CWM i have the message "" Bootloader files have found. This app does not flash bootloaders. Usually bootloaders can safely be skipped. If not, likely you will be able to find a bootloader-only package on XDA to flash through ODIN" ...
I have this message after installation :
" E: Unknown volume for path [/preload]ncan't mount 'preload (file exists)"
Help me please...
I'm French sorry for error....
hi
I think i killed my note 3 neo (sm-n7505) by rooting attempt without getting proper education or necessary backup and tools!
If someone can help, pls....
i am not going to explain EVERYTHING what i did but important.(i think)
1 Rooted
2 Verified with ROOT CHECK
3 Installed BUSY BOX
5 TWRP installation failed. (Installed a Fake one!. It damaged everything)
4 NO BACKUP ( I made a backup but somehow it wiped away!) (forgot to double check!)
6 "NAND ERAZE ALL" CHECKED IN ODIN AND EXECUTED while CF-Autoroot! (wrong! wrong! wrong!)
CURRENT SITUATION/WHAT I HAVE NOW/WHAT CAN I DO ?
SYSTEM IS NOT DEAD COMPLETELY(?)
I CAN 'ON' IT BUT END WITH A BOOT LOOP
I CAN GO TO RECOVERY MODE
I CAN GO TO DOWNLOAD/ODIN MODE
I HAVE ACCESS IN EXTERAL SD CARD
EXTERNAL SD CARD HAS THE FOLLOWING:
CF AUTOROOT hllte-hlltexx-smn7505.zip
kyleopen-cwm-v3.tar.md5
Super SU V2.52.zip
BETA-SuperSU-v2.52.zip
SR3-SuperSU-v2.79-SR3-20170114223742.zip
---------------------------------------------------------------------
me.twrp.twrpapp-22.apk.md5
---------------------------------------------------------------
BOOT LOADER
SM-N7505-4.4.2.zip
SM-N7505_BOOT_5.1.1.ZIP
SM-N7505_BOOT_5.1.1.ZIP
-------------------------------------------------------------
StockROM and Custom ROM
Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip
Note-4-Mini10 N7505.zip
Note-5-ROM.zip
NoteRom V4 SM-N750 Only.zip
cm-12.1-20160809-UNOFFICIAL-hllte.zip
----------------------------------------------------------------------------
There is "full budle of the ANDROID SDK
(Android-studio-bundle-162.3871768-windows)
There is "minimal_adb_fastboot_v1.4.2_setup on my pc"
installed samsung usb driver
--------------------------------------------------------------------------------
I Cannot Successfully Execute ANY of the above in Recovery Mode
Here the the text at the top of the reovery Screen
[Andorid system recovery (3e> LMY47X.N7505POUDOK2 ]
and
Here is the info at the bottom
#MANUAL MODE #
--Applling Multi-CSC...
Applied the CSC-code : KSA
Successfully applied multi -CSC.
---------------------------------------------------------------
When i execute any zip, it end-up with some error messages
"Signature verification failed"
"footer is wrong"
and restart the device or bootloop!
-------------------------------------------------------------
CAN I FIX THE DEVICE? OR NO NEED TO WASTE MY TIME AND BUY A NEW ONE?
Thank you
Shihab
here is the link it lead me here
trendblog(dot)net(slash)fix-soft-bricked-android-device-first-aid-guide
@1978shihab
Hi
Try downloading your firmware from sammobile.com based on your country code and flash it with Odin while your phone in Download Mode, in Odin, check f.reset time and auto reboot, don't check any thing else.
The firmwares link:
https://www.sammobile.com/firmwares/sm-n7505/SM-N7505/
SAM MOBILES FILE FAILED BUT "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip "
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
1978shihab said:
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
Click to expand...
Click to collapse
Hi Mr-Shihab
To flash a zip with recovery, then it has to be a flashable zip, it should be built in a specific way so the recovery can work with it, and the zip you have is a normal compressed files, so it can't be flashed at all with recovery, also note that the zip you downloaded from sammobile might be corruptedly downloaded, because sammobile offer a clean roms, anyway, you can also use samsung-firmware.org, it's a trusted site as well.
Ps: that md5 file you got works the same as the 4 files you downloaded after.
God bless you too
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
RAZERZDAHACKER said:
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
Click to expand...
Click to collapse
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?! ?
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
MigoMujahid said:
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?!
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
Click to expand...
Click to collapse
There is a recovery mode (not the one where you flash your roms and replace with twrp) in kies (my bad for not saying that) that reflashes the whole phone, you could literally erase the recovery or the kernel and you'd still be able to recover it which you can check out here
Hi, I have a Galaxy S8+ from Germany (I think) and it has a problem where whenever you boot into recovery mode, there's an error at the bottom saying:
fail to open recovery_cause(No such file or directory)
Reboot Recovery Cause is [UNKNOWN]#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
After this, the only things that work are applying update from SD card and wipe data. If you try and use ADB or Boot into download mode, the phone itself reboots normally. Is there anyway to fix it?