My phone is a Samsung galaxy S3 SCH-S968c, Verizon Networked for Straight Talk. I ran into having my phone stall after the Samsung logos boot up and then the tracfone logo appears and stalls there. The issue started after i tried installing multiple tweeks using a popular app for rooted devices (i cant think of the apps name at the moment). I have a version of CWM on it. After reading threads here in XDA i found that my CWM will not work correctly on this phone. Retired Forum Moderator "edfunkycold" said "It's not really a bug with the recoveries which where modded. It's part of whatever Samsung has done to keep people from rooting and flashing roms." so i downloaded both CWM_mod2.img and TWRP_mod2.img.
So between the soft bricking and the usless cwm i cannot flash anything or access the internal or external sd cards. I tried using ADB and these commands:
adb push .img /sdcard/.img
adb shell
su
dd if=/sdcard/.img of=/dev/block/mmcblk0p18
I just get the Android Debugging Bridge version...............
I also tried other methods found in XDA using ADB.
I tried Samsung Kies, 4 versions of Odin, SkipSoft Android Toolkit and some other java executable program that didnt work.
I can boot into both recovery mode and download mode.
Recovery mode does nothing....
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /sdcard
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
.....etc. etc.
In Download mode, Odin recognizes that the phone is connected but when i try loading anything it wont connect. example: trying to load a bootchain file it says:
checking MD5 finished successfully..
Leave CS..
All threads completed. (succeed 0 / fail 0)
Other attempts show the RED FAIL square.
Im having trouble finding the correct Files to Flash. Im guessing the SCH-I535 is the non-straight talk equivalent to my straight talk phone so i have downloaded file: Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip
and Rom: Sons Of Android - cm-10.2-20130928-UNOFFICIAL-jewel.zip
Bottom line is I DONT CARE what version of android (stock or ROM) as long as it's compatible and need the correct flash files necessary. I THINK it originally has jellybean 4.2.2??? PLEASE help. ive been messing with this for 3 weeks now :crying:
Thanks
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
jbaker22 said:
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
Click to expand...
Click to collapse
ADB is not recognizing my phone. Odin still is. I tried to flash recovery with Odin last night. The process completed with success but when i restarted the phone i was not able to gain access back to the recovery. Now I can only get into download mode. Is this why ADB is not working, cuz it has to be in recovery mode?
Also I am confused on how the file structure should be when i put a rom on the sd card. I know they go in the root..... do i just extract them from the ZIP straight over to the SD? Is there a way to convert ZIP files to an Odin flashable file?
FIXED!!!! w/ Straight Talk Stock Firmware SCH-S968C
I FINALLY found a working download link for the correct firmware!!! Thanks to an old post by Kenny1974 who posted the name of the file. I googled it and found only one available!
https://www.dropbox.com/s/j2uc1hkm4...8CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
I Flashed with Odin and Presto!
If this link becomes invalid, p.m. me and i will send you a link or the file.
Related
Hi guys! I think I need your massive help...
What I did:
S-OFFed my Desire S with alpharevx - no problem
Rooted with Gingerbreak - no problem
Flashed ClockWorkMod Recovery with RomManager - no problem
Flashed Virtuos Unity ROM with ClockWorkMod - no problem
Tried to boot phone after flashing Virtuos Unity ROM - PROBLEM!
Phone stayed at VU bootscreen for about 30 minutes, not responding to anything.
Only thing to do was to remove battery. After that, it hung at HTC Bootlogo (green on white background), nothing happens.
So, I tried to enter CWM to flash my nandroid backup - wouldn´t accept it.
Tried to flash all other ROMs that I found - always error.
Entered CWM to try to wipe partitions.
First screen shows the menu and below that following message:
ClockworkMod Recovery v3.0.2.6
E:Can´t open /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Can´t open /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
I can still use the menu however.
Wipe data/factory reset is no problem
Wipe cache partition is ok, but makes the environment REALLY slow!
Always show errormessage when trying to install ROM, when it is trying to format /system, doesn´t matter if it is custom or my nandroid backup.
Errormessage is: Error formatting /system!
Sometime I had an (Status 1) message when trying to install a custom rom. It says that it is an error in the zip file. However, I tried several with the same result.
So, I thought, "Wrong CWM?". Let´s try 4EXTRecovery instead.
Beginning to flash:
assert failed: write_raw_image(“/tmp/recovery.img, “recovery”)
E:Error in /sdcard/4EXTRecovery_v2.0.2_RC2-saga.zip
(Status 7)
Installation aborted.
There´s no error in the file, I tried to download it from several sources.
I can reach the phone thru ADB and Fastboot. I tried a couple of commands I found on the net to wipe cache but only got an error. Don´t know what to type...
When trying to flash a newer Clockwork Mod Recovery with fastbootcommand, sending the file is OK, but when writing ´recovery´ it hangs, nothing happens for 20 minutes. When unplugging the USB cord I get an error (status read failed (Too many links)).
I also tried to flash my .android_secure.img, boot.img, cache.img, data.img, recovery.img and system.img from my nandroidbackup (ex. fastboot flash boot boot.img) with the same results: sending file is ok, when writing the file the phone stops responding until I pull the USB cable, then I get the "Too many links error".
So: Is there anything I can do?
I have all the files .android_secure.img, boot.img, cache.img, data.img, recovery.img and system.img on my computer if that is any good.
I can mount and access the sdcard thru ClockworkMod Recovery.
Both HBOOT (Bootloader?), FASTBOOT and CWMrecovery is responding on phone, there is a working link between computer (ADB and FASTBOOT command), however something seems to be broken as it stops responding.
Is there any command I can use? I really don´t know more than the FLASH and WIPE command so maybe i´m missing something?
I appreciate all your input!
Thanks!
kinda looks familiar...
compare your problem to this:
http://forum.xda-developers.com/showthread.php?t=1150917
F**k... Stupid me, I read that post when it was new. However, I didn´t have that problem myself then...
So, is there a command I can execute to see that the eMMC chip is really broken?
As in that thread, point 8, second infoscreen (DS Brick shows). Just to make sure, I think I have a friend that can replace it for me then...
Hi everyone,
First post (brilliant video!).
My tablet:
Asus Transformer Pad TF300 (rooted)
CWM 5.8.2
My problem:
- We decided to give our Transformer to my gf's dad for his birthday. I tried to backup using a later version of CWM (6 something) but it didn't work. I downgraded to 5.8.2 and it worked fine. I then did a factory reset (which I realise now was not the way to go).
- CMW bootloop : restored my backup, successful - still bootloop.
- Have spent the last 4 hours figuring out ADB and managed to push both a new recovery (rogue) and the latest ASUS firmware to the SDCARD. Despite it confirming the transfer from the cmd line I could not see the zip files in the directories. I tried several times to several different directories. On the last try before the SD card decided to go on vacation I did see one of the files in the root directory.
- Now, no matter what I do, I get a "can't mount /SDCARD" error. Trying to erase/format/factory reset the pad results in errors when trying to access DATA and SDCARD.
- I've located and tried several different scripts from different threads that supposedly create a fake SDCARD directory but nothing has worked
http://forum.xda-developers.com/showthread.php?t=1679274&highlight=encrypted&page=3
- I've also tried to run the install package remotely from ADB but the mounting problem reoccurs
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
It appears that many people have encountered similar problems but none of the recommendations have been successful for me so far.
There also seems to be a strange anomaly with the adb shell timing out before I can finish the command. Is this a cable issue?
I'd be super grateful to anyone that can help me sort this out.
Cheers
Sam
Anyone?
I should mention that I had installed Super SU / Super User on the tablet... if that makes any difference.
I woke up this morning and booted the tablet to get this:
E:can't mount /cache/recover/command
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
Error mounting /cache!
In addition to all the previous problems.
Super!
Nobody? Anybody?! Please help!
Hi,
If you have fastboot mode, try to inject twrp (the last 2.2.x.x or something like that) ...
--> read the way to do that on the http://teamw.in/project/twrp2/97
With last TWRP you can mount sd card (first download & extract stock rom .zip and put it on root of your sdcard)
After that, flash stock rom with TWRP ...
Choose fastboot method...be careful (there is 2 versions : JB or ICS)
SOFT BRICK fixable!!! although root repair not yet covered...
I seemed to have a simular problem on my tf300t.
tried to install a CM 9.1.0 (stable)
Stuck at asus cold boot screen.
Solution i found+
*download Fastboot and an adb.shell brigde if you dont already have it.
*place the downloaded systemware (AVALIBLE ON THE ASUS SUPPORT WEBSITE) you wish to install in the same folder you have fastboot. (example-US_epad_10.4.3.13.blob)[432.3MB]
*Boot tablet into CWM [NOTE: I used CWM-Touch. 6.0.3.1 or something along those lines] (TWRP- im unsure if the process is the same).
-from advanced settings at the bottom, wipe dalvik cache.
-no need to wipe your user data cache, but wipe other data cache.
-reboot to bootloader and select fastboot option. (3rd one with pic of usb) DO NOT PLUG IT IN YET.
*Back on your WIN pc open your windows explorer, find the folder containing the Fastboot.exe and hold shift and right click at the same time for an admin operations menu. You should see an option "Open Command Prompt Here". Click it to begin a Fastboot session.
*NOW CONNECT YOUR TABLET!!!
*TYPE THE FOLLOWING AS SHOWN! DO NOT DIVERT OR YOU SCREW UP-
fastboot -i 0x0B05 flash system blob
***NOTE THAT THIS METHOD WILL TAKE QUITE SOME TIME AND YOUR COMPUTER MAY EVEN LOOK LIKE ITS FROZEN...STOP! JUST LET IT DO WHAT YOU ASKED IT TO...THIS IS QUITE A LARGE TASK AND WILL TAKE TIME. MY PC IS AN OLD DELL E300 dem. I KICK THE PROCESS ATLEAST A DOZEN TIMES BEFORE I JUST LEFT IT ALOOOOONNNE and it worked...although i cant seem to figure out how to delete the old su binary i install so i could re-root it....ANYONE GOT ANSWER? PLEASE HELP. EMAIL IS ALWAYS UP.
IF THESE INSTRUCTIONS ARE UNCLEAR, OR YOU DONT UNDERSTAND SOMETHING, MESSAGE ME...
AND IF THIS HELPED YOU...SHARE THE LOVE-GIMME A THANKS!
Okay, let me explain the situation. I am no developer but I have some basic knowledge, so I can usually solve everything by myself. My friend handed me his bricked Galaxy 3 like a week ago for me to fix it, but it looks harder than I thought. First, I don't know if it needs different drivers, the ones installed on my computer are probably the ones from my Galaxy S3, but I don't know if they will work properly. On the other hand, the Device Manager window does not show any unrecognized device, and under "Universal Serial Bus Controllers" there is a "SAMSUNG USB composite device", and no signs of any specialized drivers for any phone I've connected to my computer. So, I guess they should do. I have Kies installed, and closed while using ODIN. The situation of the phone is a soft brick, infinite bootloop with accessible Recovery, Download and Forced Upload mode. When I access Recovery, I instantly get the following messages:
Code:
CWM FOR G3MOD KERNEL
E:Can't mount /dev/block/stl8
(File exists)
E:Can't mount CACHE:recovery/command
E:Can't mount /dev/block/stl8
(File exists)
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/stl8
(File exists)
From there, I can explore the menu as long as I want, but for example, when I try to flash a new ROM, I get this:
Code:
Installing: ANY-ROM.zip
Finding update package...
Opening update package...
Then, it starts installing the ROM normally, wipes data but then can not write on the phone's memory...
I can't mount USB storage, nor any other drive such as /system or stuff. Also, when I try to flash something over Odin, despite if it is either a ROM or a Kernel, it gets stuck on Setup Connection. I have searched over the internet, solutions like plugging the USB cable on another port doesn't work, neither does connecting the phone quickly after entering Download mode.
Any ideas?
Thank you very much.
Download a ROM and flash it through Odin.
Sent from my GT-I5800 using xda app-developers app
MicroGeek said:
Download a ROM and flash it through Odin.
Sent from my GT-I5800 using xda app-developers app
Click to expand...
Click to collapse
Read it all before posting...
Try wiping data/cache/dalvik cache etc. And then try flashing a new kernel and then a new rom through recovery?
Flash a new ROM
If you get the msg u got first, remove battery and re insert it
It should load on cwm.
Put your sd card in your phone before re inserting
Then wipe data,cache etc.
This worked for me.
Try and let me know
Sent from my GT-I5800 using xda premium
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Which ROM are u trying to flash anyway?
Sent from my GT-I5800 using xda premium
nico444164 said:
Read it all before posting...
Click to expand...
Click to collapse
You said you tried flashing a ROM through recovery not ODIN. You mentioned ODIN but the comment was vague therefore making it useless if I want to help you regarding it because I didn't understand what you meant...
Sent from my GT-I5800 using xda app-developers app
nico444164 said:
Okay, let me explain the situation. I am no developer but I have some basic knowledge, so I can usually solve everything by myself. My friend handed me his bricked Galaxy 3 like a week ago for me to fix it, but it looks harder than I thought. First, I don't know if it needs different drivers, the ones installed on my computer are probably the ones from my Galaxy S3, but I don't know if they will work properly. On the other hand, the Device Manager window does not show any unrecognized device, and under "Universal Serial Bus Controllers" there is a "SAMSUNG USB composite device", and no signs of any specialized drivers for any phone I've connected to my computer. So, I guess they should do. I have Kies installed, and closed while using ODIN. The situation of the phone is a soft brick, infinite bootloop with accessible Recovery, Download and Forced Upload mode. When I access Recovery, I instantly get the following messages:
Code:
CWM FOR G3MOD KERNEL
E:Can't mount /dev/block/stl8
(File exists)
E:Can't mount CACHE:recovery/command
E:Can't mount /dev/block/stl8
(File exists)
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/stl8
(File exists)
From there, I can explore the menu as long as I want, but for example, when I try to flash a new ROM, I get this:
Code:
Installing: ANY-ROM.zip
Finding update package...
Opening update package...
Then, it starts installing the ROM normally, wipes data but then can not write on the phone's memory...
I can't mount USB storage, nor any other drive such as /system or stuff. Also, when I try to flash something over Odin, despite if it is either a ROM or a Kernel, it gets stuck on Setup Connection. I have searched over the internet, solutions like plugging the USB cable on another port doesn't work, neither does connecting the phone quickly after entering Download mode.
Any ideas?
Thank you very much.
Click to expand...
Click to collapse
try to uninstall kies restart your computer reinstall kies and keep internet activate so that it downloads drivers for your samsung galaxy 3 then put your phone in download mode and run odin if odin detects phone first flash with zero fill for g3 of hillbeast which will delete cache files of older rom then flash which ever rom you like .
Hello,
I turned on my Xoom to see "Encryption Unsuccessful" tonight. If i boot into stock recovery and try to factory reset, it cannot mount Cache. If I plug the device into my computer, fastboot can find it but ADB cannot. I have the proper drivers installed. I can't get into my tablet to turn on USB debugging. I just bought an OTG cable to try to fix it, but cannot find the update.zip file that I need. If i try to fastboot oem unlock, it fails. I've tried everything I can find, I've done hours worth of playing/trial and error to no avail. Any help would be fantastic. Truly at a stand still. Please ask with any specifics needed to assist me.
Is it possible to flash to CWM recovery without being able to boot/find it in ADB?
Thank you,
Bradon
>.<
Nearly to the point of offering some sort of payment for assisting me. I'd rather not ship it out, but more than glad to work something out paypal or giftcard wise. This tablet is the only thing keeping my wife entertained, and another tablet is not in the budget.
But u can connect with fastboot to device ?
if yes this should help you
http://forum.xda-developers.com/showthread.php?t=1451655&page=7
http://forum.xda-developers.com/showthread.php?t=1049485
Probably you will lose all data on it ... Why u wanted to encrypt u device ...
I did it too but it was missunderstanding specialy when flashing a lot .
Alright so...
I've used fast boot flash user data, system, recovery and boot. Those are all successful, but if I reboot.. Nothing changes.
I've loaded many zips onto a flash drive with an otg cable, boot into the stock recovery and try to update, unable to verify signature.
Adv will not find the device, reinstalled drivers many times
Rsd will not find the device
Factory reset fails, cannot mount cache and about 10 other cache/recovery errors
Fast boot OEM unlock fails, unable to write a certain 3 letter file
I'm at work right now, so I can post specifics/pics later.
I didn't try to encrypt it, it seemed like a virus that my wife got. She clicks on advertisements, downloads sketchy files/apps.
It is unrooted, stock recovery.
20+ hours of research and trial.. No success.
Can u use this ?
http://forum.xda-developers.com/showthread.php?t=1074979
Use 2 method.
Write response what happend and it does flash recovery .
You have to unlock bootloader
look here simillar problem :
http://forum.xda-developers.com/showthread.php?t=1571827
http://forum.xda-developers.com/showthread.php?t=1952628
And u do not need any special otg cabel - use stock xoom from package. OTG is for host-usb.
Anyway u will have to do it with fastboot , probably /cache partialy encrypted.
Alright, I just followed the CWM recovery guide.
First off, ADB does not find my device, meaning I cannot reboot into the bootloader. I can flash the recovery only after flashing userdata for some reason. After flashing, it says complete though when I reboot nothing changes. The other 2 links, first one I can't use because adb doesn't find my device, and the 2nd one.. I don't think xoom has a "download mode".
Thanks
Ok, so when u push down button in booting u have only recovery ?
U should have fastboot too ... try to press up vol 1 s after booting, then connect to pc, and check in device manager rmb on "My pc"
And ? .... This must working ... Use fastboot.exe in cmd ( in windows 7 ) on Administrator User.
Also, when I first boot up recovery I get
E: failed to mount /cache (invalid argument.)
E: Can't mount /cache/recovery/command
E: Failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E: Failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_install
E:can't open /cache/recovery/last_install
E: Failed to mount /cache (invalid argument)
If i try to factory reset or clear the cache, I get the same message.
U do not understand what u reading, u cant do this from recovery ...
U have partialy crypted storage ... its normal!
1. download fastboot on windows
2. install drivers from
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
Click to expand...
Click to collapse
3. run fastboot protocol on xoom press down vol "find fastboot" if not press top vol in booting - should fastboot protocol ... in output
4. Use fastboot.exe from android sdk - run in in cmd ( Run ad Administrator , right click on cmd)
4. unlock bootloader
5. flash rom boot recovery in *.img format!
This must working...
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
bcwest said:
When I connect it to my PC in fastboot mode, it comes up as "Mot Single ADB Interface"
Click to expand...
Click to collapse
Is it bad ? - now when u show up "fastboot protocol ... " on xoom run fastboot from android sdk .
Fastboot ran from cmd with admin privileges.
fastboot oem unlock
used volume controls to select yes/i accept
Device unlock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:324 NvStorMgrFileOpen("UDA"):196624
ERROR: Failed to format UDA.
Error while unlocking device.
unplug mmc card from xoom and try again, where did u get files ... system.img ,recovery.img,boot.img ?
I've tried with both the mSD card in, and out. I got the boot/system/recovery/userdata from the stock image post from XDA.
ok, I didnt tryed this with stock rom, try to change recovery with http://forum.xda-developers.com/showthread.php?t=1074979
reboot and try to get to new recovery.
do this:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img <- from http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )
mx600 is the model that I have.
All of the flashing goes through fine
fastboot erase cache fails instantly (Failed to format PDB)
fastboot erase userdata fails instantly (Failed to format PDB)
fastboot reboot
volume down for recovery to see if CWM changes went through
stock android recovery
If I put my mSD card back into the unit, and try to do it all over again..
Flashes go through fine
Cache fails instantly, same error
Erase userdata causes my cmd to hang up, and the xoom sits at "StorMgr Formatting UDA STATUS: | | |"
5 minutes later, still sitting at that message.
Mx600, I restarted the device after flashing everything, If I let it go past the Dual Core Technology big red M, it boots into android but all that I get is the Encryption Unsuccessful screen. It says push restart, but it does nothing.
Which model of xoom u have ? Did u restart xoom after flashing ? Is there any output ? (without up,down vol )[/QUOTE]
Damn, that mean bootloader is locked or he have problem with gpt ?
ok... I'm not sure what will hapend but u can try to lock it again
fastboot oem lock
then reboot
fastboot oem unlock
output ?
Device Lock operation in progress...
Formatting UDA.
hardware/tegra/core/system/moto/fastboot_sparse.c:350 NvStorMgrFileWrite(ff, 0x00004000:00000000):196608
ERROR: Failed to format UDA
Device lock operation FAILED.
I have a J7 prime, on7xelte, g610f, oreo 8.1.0, stock firmware, no custom recovery. I wanted to root it and for that wanted to install twrp. I did NOT use Samsung Antiroot Removal Tool, RMM State Bypass zip, No Verify Encrypt zip. I tried to flash it using adb but no matter what it wont detect my phone in recovery/fastboot, only when its on or sideload. On sideload i got an error. So i tried to do it with odin, since odin detects my phone EVEN though windows doesnt. After doing that somehow my system got corrupted. i couldnt mount /data once in twrp and trying to boot it up caused bootloop. i couldnt get it to mount usb either. then i force restarted it into download mode and reinstalled stock firmware, retried the twrp .tar, and failed again. and again. then i saw a video rooting j7 prime with a root file The link to the video:
. the file was for g610fd, i thought the "d" was a typo and flashed it anyway. Now I boot up into the stock recovery with the exact following lines:
Installing system update (loading)
no command (exclamation triangle)
(after a while)
Android recovery
samsung/on7xeltedd/on7xelte
8.10/MIAJQ/G610FDDS1CTE3
user/release-keys
[the regular options here]
#fail to open recovery_cause(no such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File based OTA
supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
#MANUAL MODE V1.0.0#
Successfully verified dmverity hash tree
:/ so apparently at this point, only the volume buttons work. i mean i can only go up and down but not select a thing. its bad. so i tried force rebooting into the download mode. THERE, the VOLUME buttons dont work. means i cant confirm and proceed into the download mode fully. my pc doesnt recognize the device in either states so i cant command in adb. one thing is that even before this error my pc didnt notice my phone in either states. so i might be missing the right drivers. my wire isnt flawed, i have 3 wires. i have hand typed everything here so will be great if you take your precious time to type any advice here for this poor fellow who is scared of losing his only phone.