I have a Samsung Galaxy S Relay 4g, and I followed this guide to root it, using the files provided: http://forum.xda-developers.com/showthread.php?t=2256821 It seemed to work perfectly.
Then I backed up the factory (4.0.4/touchwiz) rom, used the recovery to wipe user data, cache partition, and dalvik cache, and then tried installing the stock kitkat zip. It got a little way into the process and then stopped, saying "Install aborted". It was able to boot into the stock (4.0.4/touchwiz) rom after that, so I did some googling and tried again with a version of Liquidsmooth specifically for the device. Same problem, except it said "Error 7" this time. I fixed that, tried again, and the "Error 7" message went away, but the "Install aborted" message stayed.
Now whenever I try to start it up, it boots straight into recovery mode. I tried restoring from the backup I made at the beginning, and it says "md5 mismatch". I've considered trying to flash the rom with Odin, but 1) the files aren't md5s/tars? and 2) I'm hesitant to do anything that may damage my phone further.
I've also tried googling around, with a lot of not-quite-helpful results. Any help would be amazing and highly appreciated.
Thanks!
XDA Visitor said:
I have a Samsung Galaxy S Relay 4g, and I followed this guide to root it, using the files provided: http://forum.xda-developers.com/showthread.php?t=2256821 It seemed to work perfectly.
Then I backed up the factory (4.0.4/touchwiz) rom, used the recovery to wipe user data, cache partition, and dalvik cache, and then tried installing the stock kitkat zip. It got a little way into the process and then stopped, saying "Install aborted". It was able to boot into the stock (4.0.4/touchwiz) rom after that, so I did some googling and tried again with a version of Liquidsmooth specifically for the device. Same problem, except it said "Error 7" this time. I fixed that, tried again, and the "Error 7" message went away, but the "Install aborted" message stayed.
Now whenever I try to start it up, it boots straight into recovery mode. I tried restoring from the backup I made at the beginning, and it says "md5 mismatch". I've considered trying to flash the rom with Odin, but 1) the files aren't md5s/tars? and 2) I'm hesitant to do anything that may damage my phone further.
I've also tried googling around, with a lot of not-quite-helpful results. Any help would be amazing and highly appreciated.
Thanks!
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
First, please create an account so you can post in other forums.
Here is your device's main forum area:
(You should bookmark this)
http://forum.xda-developers.com/galaxy-s-4g
After creating your account, please ask your question here:
http://forum.xda-developers.com/showthread.php?t=1494423
The experts for your device are located there and will be able to help.
Good luck!
Related
I have an Inspire 4G. I've been running AndroidRevolution 5.6.2 for awhile now, probably 6 months. It's been running great so I haven't had any reason to mess with it. Today it locked up for no reason (no changes, no new apps, etc). It wouldn't boot beyond the "HTC Quietly Brilliant" splash screen.
I jumped into HBoot and then into CWM (version 2.1.3 RC2). I tried wiping Cache and Dialvik cache and rebooting with the same results.
I then tried a "Fix Permissions" with the same results.
I then tried a "Factory Reset". This time it seemed to give the same results, but when I tried to go back into CWM it loops... it loads the file system list at the bottom below the menu, flashes black, then does it again over and over again. I can control the menus (vol up/down, power) for the split second that they are available but then CWM just restarts, over and over again.
I was going to try Gene Poole Factory Reset tool, but it states that the /cache need to be EXT3 and mine is EXT4.
Is there any hope for me? How can I either get back to stock or at least a working CWM (3.0.2.6 or newer) to load AndroidRevolution 6.3.1?
Please help!
shopkins82 said:
I have an Inspire 4G. I've been running AndroidRevolution 5.6.2 for awhile now, probably 6 months. It's been running great so I haven't had any reason to mess with it. Today it locked up for no reason (no changes, no new apps, etc). It wouldn't boot beyond the "HTC Quietly Brilliant" splash screen.
I jumped into HBoot and then into CWM (version 2.1.3 RC2). I tried wiping Cache and Dialvik cache and rebooting with the same results.
I then tried a "Fix Permissions" with the same results.
I then tried a "Factory Reset". This time it seemed to give the same results, but when I tried to go back into CWM it loops... it loads the file system list at the bottom below the menu, flashes black, then does it again over and over again. I can control the menus (vol up/down, power) for the split second that they are available but then CWM just restarts, over and over again.
I was going to try Gene Poole Factory Reset tool, but it states that the /cache need to be EXT3 and mine is EXT4.
Is there any hope for me? How can I either get back to stock or at least a working CWM (3.0.2.6 or newer) to load AndroidRevolution 6.3.1?
Please help!
Click to expand...
Click to collapse
Download the Ace hack kit and take the CWM image in the folder tools/recovery. Rename it PD98IMG.zip and then copy it to the root of your SD card. Boot into Hboot and when prompted press volumen up. That will flash a new recovery image. Then try flashing a new Rom from the CWM...
You shouldn't have made a factory reset without flashing a new Rom.
Sent from my Inspire 4G using XDA App
In the Inspire 4G General forum there is a thread right at the top that explains how to deal with this type of problem. Marsdta also provides links to a Recovery img already in PD98IMG.zip format as well as flashable stock RUUs. That should get you back up and running.
I got a good Recovery installed (CWM 5.0.2.6). From there I ran SuperWipe which completed fine. Next I tried installing the AndroidRevolution 6.3.1 ROM and it failed with "Insallation Aborted" and "Status 7". After that, trying to Super Wipe or install the ROM fails and reports "Status 1". I'm trying to re-format the SD card and re-download the ROM right now. Any other tips?
Thanks in advance!
shopkins82 said:
I got a good Recovery installed (CWM 5.0.2.6). From there I ran SuperWipe which completed fine. Next I tried installing the AndroidRevolution 6.3.1 ROM and it failed with "Insallation Aborted" and "Status 7". After that, trying to Super Wipe or install the ROM fails and reports "Status 1". I'm trying to re-format the SD card and re-download the ROM right now. Any other tips?
Thanks in advance!
Click to expand...
Click to collapse
Try flashing some other rom. Maybe the file is corrupted...try installing RCmix3D or Coredroid or maybe some other rom and see what happens.
I'm getting a lot of errors in CMW along the lines of "E:Can't Mount /cache/recover/log" and "E:Can't Open /cache/recovery/log". When I try to run Super Wipe I also get "(cache is unmounted alread)". Is there some problem with how my cache is formatted, mounted, or something like that? When I try to Mount /cache manualy I get "Error mounting /cache!".
Thanks again.
shopkins82 said:
I'm getting a lot of errors in CMW along the lines of "E:Can't Mount /cache/recover/log" and "E:Can't Open /cache/recovery/log". When I try to run Super Wipe I also get "(cache is unmounted alread)". Is there some problem with how my cache is formatted, mounted, or something like that? When I try to Mount /cache manualy I get "Error mounting /cache!".
Thanks again.
Click to expand...
Click to collapse
Don't run the superwipe....flash the recovery and don't wipe anything. Just flash the rom...
Tried that just now. Got as far as
>>> Flashing boot.img
assert failed: write_raw_image("/tmp/boot.img" . "boot")
E:Error in /sdcard/Android_Revolution_HD-4G_6.3.1.zip
(Status 7)
Installation aborted.
Is there anything special I need to do in regards to formatting the SD card beyond FAT32 and full format (not quick)?
shopkins82 said:
Tried that just now. Got as far as
>>> Flashing boot.img
assert failed: write_raw_image("/tmp/boot.img" . "boot")
E:Error in /sdcard/Android_Revolution_HD-4G_6.3.1.zip
(Status 7)
Installation aborted.
Is there anything special I need to do in regards to formatting the SD card beyond FAT32 and full format (not quick)?
Click to expand...
Click to collapse
Do the following....try to change SD card, and don't flash Android Revolution...try to flash this:
http://rcmix3d.blogspot.com/2011/11/rcmix3d-runny-v40.html
Flash that rom to see what happens. Two options, or the zip file you are trying to flash is corrupted or the SD card is having issues...try the rom I posted, if is not working then try with another SD card....that should solve the problem
Formatting the SD card is a possible way of solving corrupted patitions....
Tried this. Flash of the rom seems to have completed but wouldn't boot beyond white HTC screen. Rebooted and still wouldn't boot past white HTC screen. Re-entered CWM, cleared data, tried flash again. This time the flash seemed to load correctly but now I can't even power on... complete brick...
Is there any chance to save my phone?
shopkins82 said:
Tried this. Flash of the rom seems to have completed but wouldn't boot beyond white HTC screen. Rebooted and still wouldn't boot past white HTC screen. Re-entered CWM, cleared data, tried flash again. This time the flash seemed to load correctly but now I can't even power on... complete brick...
Is there any chance to save my phone?
Click to expand...
Click to collapse
Ummmm...things are not good. But I heard that if the partitons are corrupted then you are lost. Try leaving the phone with no battery for a while. Then try to boot it...and see what happens. If it boots butvis still stuck in hboot, then return to stock with Gene Pole's tool and make a warranty claim. If you cannot even turn it on...then do the same. But if your carrier finds out you jhave been messing with your cell then you won't get much...
Sent from my Inspire 4G using XDA App
Total brick. Had to be hardware failure that initiated the downward spiral. Luckily I have an ATT DCS Center nearby and the swapped the phone out with a new(ish) one within about 3 minutes of troubleshooting. Thanks again for all the help. Not sure what ROM to flash to the new phone, though all I really want is tethering... Is there anything else out there as "stock" as Android Revolution HD 6.3.1?
shopkins82 said:
Total brick. Had to be hardware failure that initiated the downward spiral. Luckily I have an ATT DCS Center nearby and the swapped the phone out with a new(ish) one within about 3 minutes of troubleshooting. Thanks again for all the help. Not sure what ROM to flash to the new phone, though all I really want is tethering... Is there anything else out there as "stock" as Android Revolution HD 6.3.1?
Click to expand...
Click to collapse
Well you can just root the phone and maintain the stock rom...or there is ERBUS ROM that is just stock but without ATT bloatware and some other stuff...anyway you can just check some other roms and decide by yourself...there is no correct answer for that!! glad u solved it.
I have a Samsung Conquer 4g and I have ran into a huge problem as the title tells itself. I tried flashing the new FC17 2.3.6 update for it and now the phone shows the first start up screen than immediately goes to clockworkmod recovery. I tried restoring a backup of the whole phone I made a couple of days ago and that still doesn't work. Than I also tried extracting the .img files from the backup and tried pushing those folders into the phone but it still doesnt work. Any help? I will also provide with any other information needed. Thanks.
itzdarockz said:
I have a Samsung Conquer 4g and I have ran into a huge problem as the title tells itself. I tried flashing the new FC17 2.3.6 update for it and now the phone shows the first start up screen than immediately goes to clockworkmod recovery. I tried restoring a backup of the whole phone I made a couple of days ago and that still doesn't work. Than I also tried extracting the .img files from the backup and tried pushing those folders into the phone but it still doesnt work. Any help? I will also provide with any other information needed. Thanks.
Click to expand...
Click to collapse
check the kernal first...is it the correct kernal for that?
do one think...got cwm
wipe data/factory reset
wipe cache
goto advanced>>wipe dalvic cache
wipe battery status...!!
I tried that but still no luck this is very odd maybe there is a file doing this?
Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!
toiel said:
Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!
Click to expand...
Click to collapse
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.
Same problem here
gooniegoogoo2 said:
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.
Click to expand...
Click to collapse
Same problem here... I can't properly do some of the advanced wipes in the process of trying to install omni.
I did as you suggested and tried wiping them individually but to no success.
I am definitely not as fluent in this stuff as a lot of you on here are, but I am competent/confident enough to follow good instructions.
Somebody help please!
Cant install KitKat Roms
I am having the same issue and have done the same thing. Tried installing both CM and OMNI with no success. the recovery is telling me the came thing that it cannot mount E:\ 'cache' and other files i need to wipe.
Some one please help.
i was wondering...
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?
But it worked before
ohDevious said:
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?
Click to expand...
Click to collapse
I'm getting the same "can't mount cache" error when converting to Big Part - I had previously been running several Big Part roms, and had no problem with the conversion at that time - I then reverted back to stock (using VZW OTA's) for awhile, but want to give the Big Part roms another shot - I've tried several methods of reverting to stock, then coming back to install a 10.1 ROM, which is successful, but when I flash the Big Part TWRP and try the conversion, I get the cache mount error every time - I can revert to the "normal" TWRP, reformat, and re-install non-big part roms without a problem - help us Obi Wan! WTF?
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
Click to expand...
Click to collapse
I forgot to mention click the format data tab under wipe and type yes.
I just had this same experience. I think the directions are somehow missing a step or we're misreading it.
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
I forgot to mention click the format data tab under wipe and type yes.
Click to expand...
Click to collapse
A day not spent well
I am having the same issue all of you guys are having. I had 10.1 stingray (4.2.2) running well and thought it was time to try Kit Kat. Both the ROMs wind up the same way, a loooong running splash screen (over an hour before I manually rebooted). Over and over no mater how many ways I tried to wipe the XOOM I kept getting the Can't mount the cache message. I was able to revert back to 10.1 but I can't figure why others can make the install and we cannot. I have asked others on the forum but no one can answer the question?
Anyone? Thanks! Paddy
I was finally able to figure this out last night. I was looking at my cache and data formats and both were formatted as f2fs. I believe it's under wipe in the latest TWRP (2.7.1.0), there's an option on the left that shows you the format type of your drives. On non BigPart TWRP I changed the cache and data to ext4. Rebooted back into recovery, and followed the guide posted here to apply BigPart to my Xoom: http://forum.xda-developers.com/showthread.php?t=2506997 :: Then I was able to load Omni BigPart edition with no issues at all. I'd be happy to give more details if anyone wants. I'm in the office now, otherwise I'd post some snap shots. I'll update this when I get home.
has anyone recovered from the "unable to mount cache" error? I have followed all the information in this thread, checked out the relevant links all to no avail.
The only additional data I can provide is that when I go into the wipe menu (TWRP 2.7.1) / advanced / select cache / and "repair or change" I have all 0's for the cache size MBs. Repairing the cache or changing file system claims to be successful, but it's always 0 MBs. For grins I tried all of the above with TWRP 2.6.3 and had no better results.
Thanks in advance.
Recovery of J700T from "Device storage corrupt you must factory reset" error
Time to talk to the XDA brain trust before I make matters worse. I had rooted my J700T and all was well, also using link2sd. Unfortunately, I made a fatal error by attempting to use FolderMount (rather than creating the links myself), ending up in the Samsung "/data corrupt you must factory reset" error. Also unfortunately, when I earlier flashed TWRP (and then flashed SuperSU via TWRP) I did not choose to wipe the phone at that point to give /data & /system access, so I can't access them through TWRP's adb access. The "reset phone" option on the "you must factory reset" page fails of course, since it tries to boot into recovery which is TWRP not stock. I tried to do a typical TWRP wipe (I can still boot into TWRP of course, and into the download screen), but the result is that when the phone is started normally it continuously loops with the Galaxy J7 splash screen on and off at about seven second intervals (only stopped by pulling the battery).
So the question is, what's the best way to proceed? I saw another page here with the four ODIN files to flash back to stock, but the dropbox account is suspended due to overuse. Ideally, something I could do through TWRP would be even better, and this time I'd like to do the full reset and turn off the crypto so that in the future TWRP has full access to the internal phone data, not just the SD card.
Any guidance would be much appreciated. Thanks!
Can I Restore the Samsung 700t1 withowithout pc
Jersto said:
Can I Restore the Samsung 700t1 withowithout pc
Click to expand...
Click to collapse
If you mean completely back to stock (day one out of box), no.
sent from this device on this app....
So you had twrp as your recovery, you decided to mess with your system partition, you don't have free access to a PC yet it seems you neglected to do the one thing that would have got you out of this mess in a pinch?
That is spending literally 2 minutes to make a nandroid backup?
The main reason really for having a custom recovery. ?
Your only option now is to flash the stock firmware and FORMAT DATA.
Okay guys. Now we got that out of our systems, let's work on some solutions.
All good?
sent from this device using this app....
Thread cleaned up. Please stay on topic.
Regards
Vatsal,
Forum Moderator.
Model: Galaxy Fit S5670
I wanted to install unofficial cm11 to it and so I rooted it, however in some steps i messed it up and now I have what I believe is claled a hardware lock. So basically it won't boot, go to recovery as it will show a phone-->Yellow Triangle--> PC but it will go in download mode.I have tried with different versions of ODIN and different firmwares(one package) and ops but I always find myself stuck at flashing system.It just stays there forever and won't go on. I even let it for 45 minutes and didn't do anything. Any help is appreciated as I have read many forums and guides but I cannot seem to figure this out. Note: It is an old phone so no warranty.
EDIT: After multiple tries I managed to flash it with cooper_v1.ops and with Indian firmware from sammobile. However now I came back to my original issue. I have now rooted my phone through this guide: https://theunlockr.com/2012/11/22/h...fit-gt-s5670-running-android-2-3-gingerbread/
and flashed cwm recovery version v5.0.2.7 through this guide: https://theunlockr.com/2012/11/22/how-to-install-custom-recovery-on-the-samsung-galaxy-fit-gt-s5670/
but after I wipe data/ reset and cache, installation of cyanogenmod11 gets aborted and doesn't work. I've heard this may be due to old version of cwm but I have no idea. Any help would be appreciated. Also note, I have tried cm11 from here: https://forum.xda-developers.com/showthread.php?t=2581415 and can't find any other unofficial cm11 or even cm10 with a working link. Also, the error showing when I try to install cm11 is "set_metadata_recursive: Some changes failed" "E:Error in /sdcard/cm-11-2014-0116-NIGHTLY-beni.zip" "Status 7" Installation aborted. I also noticed that when I wipe data / reset it says "Formatting /data.... Formatting /cache... Formatting /sd-ext... and E:format_volume: make extf4fs failure on /dev/block/mmcblk0p2 Formatting /sdcard/.android_secire/ Data wipe complete." The failure could be linked to the abort of the installation but I have no knowledge on it.
EDIT 2: I messed up something, and when I try to flash it with the same odin exe, same BENI_v1.0.ops and same one package it will get stuck at system but like once does work once in 50 times??? I honestly am confused and don't understand why. And it wasnt the first time I did it that it worked either.