Related
Alright... where to begin? Lets start at what happened around yesterday. Prior to the whole weekend, I had CyanogenMod 10.1 installed on my rooted S4. Come Friday, I start to miss some of the stock Samsung features such as Air Gestures, Smart Stay, the stock Samsung camera, and all that. So, I install WanamLite (a custom rom) on my phone. It's good and all but for some reason, the Smart Stay isn't working. To fix this, I go online and start digging; I find people saying "yo, revert back to the original firmware and re-install the Rom, that should fix your LTE problem." I think to myself, "maybe this could help me too." And that's exactly what I do. I go online to SamMobile and download this ROM (http://www.sammobile.com/firmwares/?page=1&model=SGH-M919V&pcode=0#firmware). It installs with Odin and I was able to get back to the Stock Samsung firmware. I then proceed with my plan and install WanamLite; that also worked. So I'm all happy and stuff 'cause Smart Stay finally works but, shortly after fiddling with the re-stocked device, I get bored again. So, I start searching the forums for another rom to replace WanamLite (it was a good rom, but I wanted to try something else before settling down on it).
I find this ROM in the XDA-Developers S4 forum: http://forum.xda-developers.com/showthread.php?t=2303239. I try installing it; it works fine. But then, I notice that half my SD card is used up. So, I go into TWRP and click on Format Data (I'm not too sure about the name, I had CWM prior to the re-installation of Samsung stock firmware). After resetting the Data, I boot back into the phone and notice that the default layout is Easy Mode. (On the bright side, I freed 4 GB from my SD card). Easy Mode's incredibly annoying, so I wrestle with the phone for a while to change the launcher to Nova launcher, but to no avail. In the end, I decide to reflash the FoxHound ROM. I place the rom on my phone and boot into TWRP. That's where the problem comes. I selected: wipe cache, wipe delvic cache, wipe data. Then I wiped the cache and data, flashed the rom and, after that is when the phone started refusing boot up. From then on, it just displayed Samsung Galaxy S4 logo on the screen whenever I tried to start it.
What I tried to fix the issue: Re-installing the stock samsung firmware. (I think I ended up screwing up the phone even more with this. Before, I had TWRP installed but I couldn't boot into it, now I don't have any custom recovery installed and I still can't boot into the phone).
I can access the Download Mode and use Odin. I cannot boot into the recovery. When I hold Volume Up + Power + Home, it just says recovery in blue above the logo, and then, the phone reboots.
So, any ideas on how to fix it?
TL;DR: Tried installing FoxHound Rom. I wiped Delvic Cache, Cache, and Data, and after flashing the rom, the phone refused to boot up; it gets stuck on the Samsung logo. Before flashing, I did Format Data. After being unable to boot into the phone, I tried to flash the Stock Samsung Firmware on my S4. Nothing worked. Any ideas on how I should proceed?
splitinferno said:
So, any ideas on how to fix it?
Click to expand...
Click to collapse
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"
psycovirus said:
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"
Click to expand...
Click to collapse
I've already tried flashing the Stock Samsung Firmware using Odin, it didn't work. Also, I'm having no luck with Kies; it won't connect. Any other suggestions? :/
EDIT 1: Okay, so here's the deal right now: I was able to flash TWRP using ODIN. This granted me access to my recovery, somehow. So right now, I have the FoxHound_GearEngine0.2 ROM installation files on my SD card and I am booted into the recovery. What should I do? Should I try flashing again? For now, I'll just wait for a response.
EDIT 2: Out of curiosity and impatience, I tried flashing FoxHound but got an error:
Updating Partition Details
E: unable to mount data
E: unable to mount internal storage
TWRP v. 2.5.0.3
Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else
maazali said:
Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else
Click to expand...
Click to collapse
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.
UNBRICKED
splitinferno said:
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.
Click to expand...
Click to collapse
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.
Hahah nice job
Sent from my GT-I9505 using xda premium
splitinferno said:
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.
Click to expand...
Click to collapse
Next time don't wipe data in custom recovery because it will corrupt your data which would most probably end with not booting past the Samsung logo, if you want to wipe in a custom recovery for now you have to manually wipe system, cache and dalvik cache located in mounts in cwm recovery (not sure where to find it in twrp).
You should read a little before messing with things in recovery.
Ahahah that's funny because something similar happened to me. And I was going to suggest doing a factory reset via recovery because that's how I resolved my problem, then I see you did just that! (Y)
Sent from my GT-I9500
Hello,
Longtime flasher here, but not as familiar with gs4.
My girl has a sgh-i337 that has been boot loader unlocked since day one. It's been on TWRP and slim rom the whole time too.
I was wiping Cache, Dalvik Cache, and System (so no more rom to boot to) prior to doing a rom update and TWRP glitched out while updating partition after the final wipe operation. Screen went black and unresponsive.
Now, the phone boots to download mode only.Will not boot rom (as system was wiped) but shows the samsung custom unlocked logo. When in download (odin) mode, I see product name: sgh-1337, Current Binary: Samsung Official, System Status: Custom CSB_OEM_LSB: 0x30 Write Protection: enable
Universal android toolkit will not show device connected so Installation of custom recovery through toolkit fails.
oddly, ADB will not show device connected so cannot flash rom or recovery via adb though all drivers were updated.
ODIN will show device connected, though (blue Com 4 appears in ODIN when connected).
To recover with odin, can I flash the I337UCUAMDL from sammobile and retain unlocked bootloader?
Thanks for any and all help.
shiftystylee said:
Hello,
Longtime flasher here, but not as familiar with gs4.
My girl has a sgh-i337 that has been boot loader unlocked since day one. It's been on TWRP and slim rom the whole time too.
I was wiping Cache, Dalvik Cache, and System (so no more rom to boot to) prior to doing a rom update and TWRP glitched out while updating partition after the final wipe operation. Screen went black and unresponsive.
Now, the phone boots to download mode only.Will not boot rom (as system was wiped) but shows the samsung custom unlocked logo. When in download (odin) mode, I see product name: sgh-1337, Current Binary: Samsung Official, System Status: Custom CSB_OEM_LSB: 0x30 Write Protection: enable
Universal android toolkit will not show device connected so Installation of custom recovery through toolkit fails.
oddly, ADB will not show device connected so cannot flash rom or recovery via adb though all drivers were updated.
ODIN will show device connected, though (blue Com 4 appears in ODIN when connected).
To recover with odin, can I flash the I337UCUAMDL from sammobile and retain unlocked bootloader?
Thanks for any and all help.
Click to expand...
Click to collapse
Yes. After you flash MDL firmware using Odin, you can still root and flash custom recovery.
Welp, installed that .tar through odin seemingly successfully. I still see the Samsung/custom/unlock boot screen but it hangs at the ATT boot screen (I let it sit for 20 mins). Any thoughts?
shiftystylee said:
Welp, installed that .tar through odin seemingly successfully. I still see the Samsung/custom/unlock boot screen but it hangs at the ATT boot screen (I let it sit for 20 mins). Any thoughts?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset. It'll get you past the bootloop
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Boot into the stock recovery and do a factory reset. It'll get you past the bootloop
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ah, gotcha. That will not wipe SD Card will it? i.e. /data is different than /sd, correct? ...There are vacation pictures on there I haven't backed up yet.
Many thanks again.
If you boot it into MDL stock, you may want to be careful that it doesn't get an OTA update to NB4 and in the process locking the bootloader.
You might be best off flashing the latest TWRP and rom of your choice. Or your girlfriend's choice!
Marc
shiftystylee said:
Ah, gotcha. That will not wipe SD Card will it? i.e. /data is different than /sd, correct? ...There are vacation pictures on there I haven't backed up yet.
Many thanks again.
Click to expand...
Click to collapse
It won't wipe your external sdcard. It will wipe the internal but if you just odin'd the internal is gone already
Sent from my Nexus 5 using XDA Free mobile app
Thanks Marc,
I'm keeping an eye on it waiting for it to boot so I can turn off wireless and data and root/flash recovery/etc. asap but its not booting. (will factory reset/wipe Data if I can confirm that it won't wipe SD Card)
I tried to make a flashable .tar file from the twrp recovery image and flash with oidin, but it fails.
ADB doesn't seem functional without root (?) so I can't push, pull or flash anything with ADB. Any suggestions on how to flash recovery and rom from this state?
shiftystylee said:
Thanks Marc,
I'm keeping an eye on it waiting for it to boot so I can turn off wireless and data and root/flash recovery/etc. asap but its not booting. (will factory reset/wipe Data if I can confirm that it won't wipe SD Card)
I tried to make a flashable .tar file from the twrp recovery image and flash with oidin, but it fails.
ADB doesn't seem functional without root (?) so I can't push, pull or flash anything with ADB. Any suggestions on how to flash recovery and rom from this state?
Click to expand...
Click to collapse
The twrp Odin fails because the bootloader is locked. Use motochopper
Edit, I haven't tried it but it's possible you can use towelroot to root and then flash the twrp image in flashify from the play store
Sent from my Nexus 5 using XDA Free mobile app
Ok. factory reset. Got it to boot. You were right, though. Odin formatted internal SD card. Once in a lifetime photos gone. Live and learn i guess, but I don't recall Odin formatting the SD card on my captivate when I was flashing that thing. ROM Chefs must have written custom scripts.
Time to look into motochopper loki root and the rest.
Thanks for your help guys.
btw, I have recovered deleted tiles from my PC with a utility that makes use of the fact that, in windows, deleted files are not written over, merely marked that those segments on the drive are available to write over. Do you think the flash memory on the phone would work this way?
Edit: pretty sure root/flashify is how I did it the first time. Will attempt that again.
So after a week of just bootloop, black screen of death and hard reset my rooted s5 suddenly open again.
Now that its open again what can I do to fix this? Cause im afraid that if i'll restart my phone i will get stuck in the bootlooop.
Suggestions?
Just to give you an update my s5 has been rooted for the past 2 years ...its just now that it got stuck in the bootloop.. im not really sure what caused this cause havent installed any apps that could affect the system...
Any ideas how can I fix it while its working again?
Would help if you gave us the model S5 it is, which firmware it's running, recovery etc?
Its g900f using stock rom... stock recovery
Please see attached file
Thanks in advance.
Download stock ROM using samfirm (or sammobile .com)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Put phone in download mode
Connect to PC USB > add .MD5 ROM to AP section in ODIN 3.10.7
Flash
Boot to recovery > Factory reset
Any other fix without flashing?
Any other fix.. that doesnt require flashing?
kenchii17 said:
Any other fix.. that doesnt require flashing?
Click to expand...
Click to collapse
Why don't you want to reflash? If you're rooted you should have backups.
Ok I think I missed that part... ok so if I flash, everthing will be wiped out right?
How do I back it up?
kenchii17 said:
Ok I think I missed that part... ok so if I flash, everthing will be wiped out right?
How do I back it up?
Click to expand...
Click to collapse
No it won't, and for a proper backup you need TWRP recovery
If your phone is having problems like it is, you very likely need to flash
Just flash the stock ROM over the top and your apps and data will remain
But backup photos and important files first by connecting the phone to USB and copying to PC
Forget about apps, you can reinstall them if something goes wrong
Ok thanks im starting to understand it now.. i just need to confirm a few things before i start doing it...i have watched a few vids and ok i think i missed installing a custom recovery... ill install it later and go with cwm...
Flashing the stock.. means getting my firmware(which has the size of 1gig+) in sammobile ang flashing it using odin right?
Read my 2nd post
Thanks alot got it! One last question , suppose that im not going to lose my apps but am i going to lose root once i have flashed the stock rom?
Yep, just root again, instructions are all over the forum, easy to find
Because you're getting bootloops, I suggested factory reset too, that will wipe the device, the flash won't, the reset will
I assume here's the steps that i need to take
1. Back up through cwm
2. Flash stock rom through odin
3. Clear dalv cache
4. Factory reset through recovery or from the homescreen setting?(will this removed supersu?)
6. Root device again
5. Restore back backup from cwm recovery?
Better method:
Flash TWRP 3.0.2.0 (Much more powerful recovery)
Make full Nandroid backup in TWRP
Wipe everything apart from Internal and External storage
Boot into Download Mode
Flash stock ROM with ODIN 3.10.7
Reboot
Now boot back into download mode
Flash TWRP 3.0.2.0 again
Boot into TWRP
Flash systemless SuperSU 2.72 beta or whichever is the latest beta atm
Don't restore your backup or you could end up with the same problems as before, I recommend using TiBu to restore your apps and data from the backup you made in TWRP
*Detection* said:
Better method:
Flash TWRP 3.0.2.0 (Much more powerful recovery)
Make full Nandroid backup in TWRP
Wipe everything apart from Internal and External storage
Boot into Download Mode
Flash stock ROM with ODIN 3.10.7
Reboot
Now boot back into download mode
Flash TWRP 3.0.2.0 again
Boot into TWRP
Flash systemless SuperSU 2.72 beta or whichever is the latest beta atm
Don't restore your backup or you could end up with the same problems as before, I recommend using TiBu to restore your apps and data from the backup you made in TWRP
Click to expand...
Click to collapse
I have tried to flash twrp on my galaxy s5 (SM-G900V) and it did not work I am kinda stuck in the same problem. But I hit softbrick. Can you take a look at my post also?
jakeh9777 said:
I have tried to flash twrp on my galaxy s5 (SM-G900V) and it did not work I am kinda stuck in the same problem. But I hit softbrick. Can you take a look at my post also?
Click to expand...
Click to collapse
Verizon lock their bootloaders
*Detection* said:
Verizon lock their bootloaders
Click to expand...
Click to collapse
It's unlockable nowadays
*Detection* said:
Verizon lock their bootloaders
Click to expand...
Click to collapse
Can you check out my situation see if it is fixable without loading data? http://forum.xda-developers.com/galaxy-s5/help/how-recover-data-softbricked-galaxy-s5-t3382554
Rakuu said:
It's unlockable nowadays
Click to expand...
Click to collapse
Yep, but without unlocking it, he can't flash anything
jakeh9777 said:
Can you check out my situation see if it is fixable without loading data? http://forum.xda-developers.com/galaxy-s5/help/how-recover-data-softbricked-galaxy-s5-t3382554
Click to expand...
Click to collapse
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Unlock your bootloader and try again
so i was on stock rom and i rooted it and installed twrp 3.0.2-0 and then did a backup of the stock rom and unticked data because i already have a backup of everything that was on the galaxy s4 on my computer and then i installed google play edition untouched rom and i didn't like it so i restored my backup and now when i booted back in it says com.android.phone has stopped working and it keeps appearing, i restarted and i got the same error and somehow i got to write my pin code and when i went in it showed my google play edition wallpaper for some reason and when it kept on flashing the same error then settings has stopped working came up! help me please! Download mode is still working, when i try to boot into recovery it says something in red and then some white text below it and then it goes black and boots into galaxy s4 gt i9505 screen.
Help will be appreciated
Did you perform a full wipe in TWRP before restoring your backup?
audit13 said:
Did you perform a full wipe in TWRP before restoring your backup?
Click to expand...
Click to collapse
nope, i thought it did it by itself because it said wiping... when i hit the restore button
You may have to wipe system and format data before restoring.
,
audit13 said:
You may have to wipe system and format data before restoring.
Click to expand...
Click to collapse
but i don't think recovery is working anymore in the left top corner it says something in yellow at the top then red below that and then white below that. it justs boots in to the white samsung galaxy s4 gt i9505 screen and then proceeds to boot to android.
Maybe reflash TWRP using Odin in download mode, wipe, and restore?
audit13 said:
Maybe reflash TWRP using Odin in download mode, wipe, and restore?
Click to expand...
Click to collapse
ok thank you so much for the quick help
Good luck. If that doesn't work, I suggest flashing a completely stock ROM from sammobile.com, factory reset, reflash TWRP, and then try a restore.
audit13 said:
Good luck. If that doesn't work, I suggest flashing a completely stock ROM from sammobile.com, factory reset, reflash TWRP, and then try a restore.
Click to expand...
Click to collapse
glad i downloaded my stock firmware which has the right baseband and stuff that came with the phone.
audit13 said:
Good luck. If that doesn't work, I suggest flashing a completely stock ROM from sammobile.com, factory reset, reflash TWRP, and then try a restore.
Click to expand...
Click to collapse
Hey recovery is working! i didn't need to do anything! i just waited for 10 mins and now it works all of sudden
That's great! Hopefully, the restore process will be successful.
Hi everyone,
I hope that you all had/are having a lovely christmas. Unfortunately for my S4 christmas has been terrible. The phone has had low storage for a week now and was crashing as a result and I didn't have time to fix it. Yesterday the phone was running horribly and wasn't doing anything that I touched. So I rebooted which took way too long and when I did it again the phone now does not pass the galaxy s4 screen and also TWRP recovery will not pass its boot screen either.
I have attempted flashing stock recovery which said error mounting all partitions, afterwards a reboot allowed me to wipe cache thinking it would allow the phone to boot, but no change.
I am thinking to flash stock samsung rom through download mode since it is still functional so I can recover my data before moving to my new phone. Will this be a good idea considering that the Lineage OS rom is significantly smaller than the stock samsung rom or will it not worsen the situation?
Thanks for your help!
Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?
audit13 said:
Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?
Click to expand...
Click to collapse
Thank you for your response! I have tried flashing flashing both the same TWRP and different version which was in fact smaller. This saw no improvement in the condition and I still can not pass the TWRP boot screen.
What else do you suggest I try?
Thanks for your time!
Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.
audit13 said:
Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.
Click to expand...
Click to collapse
I am actually unable to flash anything without odin because I can't boot into my recovery which hangs on its twrp screen. Also if I have set my partitions to f2fs will this interfere with flashing the stock rom?
I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.
audit13 said:
I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.
Click to expand...
Click to collapse
Do you think it could possibly be a bootloader or kernel issue? Perhaps I could try flashing those first before a full factory firmware?
I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.
audit13 said:
I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.
Click to expand...
Click to collapse
So I took the plunge and installed the stock firmware now the phone boots and I'm greeted with a message asking to factory reset because encryption failed. I reinstalled TWRP and for some reason that still can't fully boot. I want to get it working so I can access the storage to remove the important files through either mtp or adb. There is some form of adb working whilst TWRP is booting but it can't access or see anything in the partitions or mount them even running as root.
Any ideas to get TWRP or any other recovery working on the phone? (The stock recovery booted just fine before I flashed TWRP)
Any help is much appreciated!
Kind Regards,
Crapping_Bricks
I think the stock Rom doesn't recognise the file system and thinks the encryption failed.
I'm not sure what else to suggest other than a factory reset since twrp doesn't allow pulling the data via adb or mounting the data partition.