I have a soft bricked SGH-1337 from AT&T. I was running NJ4 firmware. I have installed Safestrap on it. I tried using SS to install a Touchwiz-based custom ROM, and it failed. Now if I try to boot the system by touching "continue" on the Safestrap boot screen, it just turns off and restarts (this is a boot loop, right?).
So basically, this is what I've tried. First I tried doing a wipe. I got this error
Code:
E : Unable to mount '/system'
. Then I tried doing an advanced wipe, same error. I tried format. Same error. I went to Mount and tried mounting /system, but it won't mount.
I tried using Safestrap to install the backup I made (with SS). No luck. Then I tried making a ROM slot (I had been using the stock slot) to see if that would work. It didn't. Then I tried using Odin to flash the NJ4 firmware. Nope. Then I tried flashing witha PIT file. All of them caused Odin to fail when "re-partition" was checked except the one I've attached. I tried flashing with just the PIT file, the PIT file and the stock NJ4, and with "re-partition" checked and unchecked. Nothing works. The phone keeps rebooting and failing to mount /system.
http://forum.xda-developers.com/galaxy-s4-att
Related
Hi,
I'm at my wits end. I had SlimRom installed for a week and all was fine, but I was curious about what new ROMs were out there so I backed up my phone using ROM Manager and did all the usual stuff to get a new ROM. I installed Gummy, but didn't like it; I installed one other ROM that I can't remember its name, but also didn't like that. I realized my comfy home of SlimRom was where I wanted to be, so I tried to flash the backup.zip that I had created but it kept saying installation aborted (Status 0).
After hours of countless attempts and just weird behaviour (sometimes boot loops, sometimes not booting into recovery, etc.) I finally got my phone back to stock.
I downloaded the latest SlimRom file 3 times to make sure it wasn't a corrupt zip (twice from my PC and once from my phone directly). Both the zip directly from Slim as well as the backup.zip that I made with ROM Manager give me the same installation aborted. The other error it gives is "E: Error in /data/media/0/slim....zip". I'm wondering if somehow my partition is screwed up. I tried using Odin's repartition, which just erased my recovery partition, but I got that back thankfully! When I wipe data/factory reset it says wipe complete (and the ROM does reset to factory) but it also says "E:unknown volume '/sdcard/.android_secure' "...I'm wondering if that relates to why the backup.zip file won't read properly. Maybe the partition got screwed up somehow?
I can flash a SU zip so it's not a flashing problem, per se. And thankfully Odin always works!
I think I may need the stock PIT file for the Telus S4 l337m
UPDATE:
I think I found the proper pit (SGS-I337_16GB) but my phone says "secure check fail: pit".
Hello, I rooted my sm-900v verizon note 3, installed custom jellybeans rom successfully, then I was going to install hyperdrive booted safestrap and wiped everything on the phone, for some reason I had to restart my phone, now I cant get it to boot up, tried using the recovery mode to install either jelly beans or hyperthread,
I wipe the cache
Then I wipe data/factory reset
Then I choose apply update fron external storage
Choose the custom rom fronm the root of the sd card
And I get an E: signature verification failed
Also tried using odin mode and odin 3.09v to install, unzipped the file and tried to load into odin, cant find the md5 file, some please help!
I did do a TWRP back up, but TWRP is not loading at boot up, nothing is, please help!
SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted
I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.
I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.
Any help and inputs would be greatly appreciated.
re: factory data reset
bcsiy said:
SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted
I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.
I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.
Any help and inputs would be greatly appreciated.
Click to expand...
Click to collapse
If you can get into recovery why not try to do a
"Factory Reset", it may solve your problems.
Good luck!
Misterjunky said:
If you can get into recovery why not try to do a
"Factory Reset", it may solve your problems.
Good luck!
Click to expand...
Click to collapse
I tried to do a factory reset in stock recovery, tried wiping the Dalvik cache as well but the problem is still there it just stays on the Samsung Galaxy Note 3 screen then turns off then turns back on and loops over and over.
bcsiy said:
I tried to do a factory reset in stock recovery, tried wiping the Dalvik cache as well but the problem is still there it just stays on the Samsung Galaxy Note 3 screen then turns off then turns back on and loops over and over.
Click to expand...
Click to collapse
Either nuke the phone via a totally fresh ODIN update or flash Philz recovery, when it loops on you, take out the battery, put it back in then go to recovery mode, wipe the usual dalvik/cache etc then boot up (it should in theory work) (and/or flash a custom ROM just to get it to boot properly)
radicalisto said:
Either nuke the phone via a totally fresh ODIN update or flash Philz recovery, when it loops on you, take out the battery, put it back in then go to recovery mode, wipe the usual dalvik/cache etc then boot up (it should in theory work) (and/or flash a custom ROM just to get it to boot properly)
Click to expand...
Click to collapse
Thanks for the input, the main issue why I need to flash the stock rom is because the phone doesn't boot and is looping in the Samsung Galaxy Note 3 screen then vibrates as if it turns on again and goes into a loop...
Question is can I flash a custom rom over it for example there's no firnware loaded on the phone or the firmware loaded is corrupted?
You can flash a custom ROM yes, so long as you boot Into your custom recovery, do the wipes. Then installing a custom fw should work OK, once you've done that you can go back to stock or change custom fw without issues
I'm UBER Paranoid
bcsiy said:
SM-N9005 is soft bricked, owner probably went OTA and interrupted the update now when you turn on the phone it goes to the Samsung Galaxy Note 3 logo then loops from there. I tried to flash official stock firmware downloaded from Sammobile (N9005XXUEND6_N9005OLBEND1_XTC) and it passed the flash in ODIN 3.09 then the phone automatically reboots into stock recovery and tries to update package but from I keep getting:
E: Unable to verify whole file signature
E: Signature verification failed
Installation aborted
I have been flashing firmwares on older Samsung via ODIN and as far as I know after flashing via ODIN the firmware is already written in the phone and it doesn't need to reboot into recovery and flash the update again but in NOTE3 it does this and now I'm stuck.
I tried flashing PhilZ custom recovery and disabled signature verification but when I flash the stock firmware via ODIN it overwrites the custom recovery back to stock recovery and then gets stuck again in the verifying signature thing.
Any help and inputs would be greatly appreciated.
Click to expand...
Click to collapse
The reason it wants to boot into recovery is to flash the csc. Make sure you get the correct firmware for your device and region from sammobile.com and odin again, let it do its thing. It sounds like the csc wasn't valid.
Sent from my leanKernel 2.5 powered stock 4.4.2 SM-N900T
I recently tried to reformat to ext 4 from f2fs, and now whenever I boot into my ROM it tells me "encryption failed". I even tried using the mf9 stock rooted one click odin exe, but got the same error message. How can I get my phone back?
In case anyone gets this error, what ultimately worked was installing CWM with odin and selecting "format /data" I was crapping my pants because even re-partitioning with odin didnt work
TWRP can't mount /system. Phone is a SM-G900T 16GB
- Running the latest version of TWRP I tried:
- Wiping, repairing, and reformatting from TWRP, also tried formatting data. I get a unable to mount '/system' error message every time.
- Using Odin and Heimdall to reformat using a downloaded .pit, neither works. I ran Heimdall in Windows and Linux (ran as sudo and admin). I re-downloaded the .pit multiple times and tried a couple different sources.
- Installing CWM using Heimdall, and ADB. In ADB and Heimdall I still have TWRP and in Odin it removes the recovery completely.
- Fix permissions gives the unable to mount '/system' error message.
- Installing ROM from Heimdall and TWRM
- Mounting /system with or without MTP
How it happened:
I was running Cyanogenmod 11 with encryption and updated to 12. CM12 was running great, flashed GApps, still running good. I signed in to my Google account and downloaded IPcamera. While running IPcamera I got an email, the screen started going crazy flashing between the alert and IPcamera screen, I couldn't do anything so I pulled the battery. When I rebooted it was stuck in a boot loop. I booted into recovery, it asked for my encryption password as usual. The password didn't work. I tried several times. I rebooted and tried again, still nothing. I rebooted again and this time hit cancel when asked for the password. I wiped everything and got the can't mount /system error. I tried everything above, nothing works.
I can't download my .pit so there is more wrong than just the data partition.
Any ideas? I would love this thing to no longer be a really expensive paperweight. I really can't afford to replace this thing right now
Thanks for your help.
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Commodore 64 said:
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Click to expand...
Click to collapse
That worked!! I don't know why the stock recovery can fix it when TWRM couldn't. It worked though. Thanks a ton!!
Commodore 64 said:
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Click to expand...
Click to collapse
This didn't work for me every time I wipe in TWRP it just never installs the packages, or upon restart it just doesn't mount system. Wipe repair on TWRP doesnt work either
egyptshun said:
This didn't work for me every time I wipe in TWRP it just never installs the packages, or upon restart it just doesn't mount system. Wipe repair on TWRP doesnt work either
Click to expand...
Click to collapse
I'm totally with you on wipes and package installs randomly failing on TWRP, but I have no idea why. Sometime in December, I made the switch to Philz CWM, and I haven't looked back since.
At any rate, it is always good practice to odin back to stock, use the stock recovery to do wipes (factory reset and wipe cache), and then odin Philz CWM or any recovery program of your choice.
If you're planning on loading Lollipop, then you might just download the latest from Sammobile, odin the stock and wipe, and then load your custom recovery.
Best of luck,
Commodore 64 said:
I'm totally with you on wipes and package installs randomly failing on TWRP, but I have no idea why. Sometime in December, I made the switch to Philz CWM, and I haven't looked back since.
At any rate, it is always good practice to odin back to stock, use the stock recovery to do wipes (factory reset and wipe cache), and then odin Philz CWM or any recovery program of your choice.
If you're planning on loading Lollipop, then you might just download the latest from Sammobile, odin the stock and wipe, and then load your custom recovery.
Best of luck,
Click to expand...
Click to collapse
I have a G900W8, there's no lollipop version for me. What phone FW can I flash and retain phone signals etc.
Captian Double post Double post here.
I'm going to snap my phone in half, it's been over 13 hours of trying to fix this. How does no one else have this problem?
EDIT: YAAAAAAAAAAAAAAAAAAAASSSSS I FINALLY GOT IT TO WORK > I HAVE NO CLUE HOW <