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.
Hi,
a few days i deviced to manualy flash 5.0.2 an my old n7.
flashing 5.0 already made many problems.
so i hoped 5.0.2 would be easier.
i wasnt -.-
i can flash bootloader, recovery but not system. when i flash system (fastboot flash system system.img, all drivers corectly installed) it lasts ours until my pc says something new like "too many links" or so. but not every time it comes to an error message. sometimes nothing happens (waited 2 days!)
the n7 it selfs dont react then.
at flashing 5.0 it helped me to change the filesystem and change it back. at 5.0.2 nothing helps. also cant flash back 5.0
bootloader is 4.23.
has anybody an idea?
What filesystem are you trying to use? Keep it at ext 4 until you get the 5.02 system flashed. Try a fastboot format system before flashing again.
Sent from my Nexus 7 using XDA Free mobile app
I switched to ext3 and instantly back to ext4 . Never tried to flash on an other filesystem.
The format command I will try
i love you
this is embarrassing for me. i tried everything i knew. i also formated the system partiton in recovery. but to format it via fastboot doesnt come to my mind
So I take it that formatting system with fastboot allowed you to successfully flash system.img? I hope you have your N7 up and running on 5.02.
Yes you're right.
I flashed 5.0.2 . So far so good.
But it won't install apps. So I wiped the cache and now I have a bootloop today after work I will look after that. But I'm happy that I can flash normally
Hi Geeks,
Let me explain the Root cause for this problem, I tried to Root my device with CF Auto root and it works fine without any issues, later i found sometimes my mobile hangs and restarts (once in a week very Rare).
Later I installed twrp recovery and accidentally wiped /system /internal /dalvik /cache everything (My foolish)
in No OS situation i tried to install Marshmallow 6.0.1 stock ROM .
after Odin finishes up its work, the mobile restarts for first time and gone through installing updates.... later few minutes No command robot is appearing.
when we restart the mobile it looping in boot screen(restarting at Samsung logo continuously)
changed battery and tried (No luck)
changed different recovery mode(No luck)
tried several times in the past week and went to Samsung service center they did the same thing what i did and informed to change the board which nearly cost 18K
azarhsaf said:
Hi Geeks,
Let me explain the Root cause for this problem, I tried to Root my device with CF Auto root and it works fine without any issues, later i found sometimes my mobile hangs and restarts (once in a week very Rare).
Later I installed twrp recovery and accidentally wiped /system /internal /dalvik /cache everything (My foolish)
in No OS situation i tried to install Marshmallow 6.0.1 stock ROM .
after Odin finishes up its work, the mobile restarts for first time and gone through installing updates.... later few minutes No command robot is appearing.
when we restart the mobile it looping in boot screen(restarting at Samsung logo continuously)
changed battery and tried (No luck)
changed different recovery mode(No luck)
tried several times in the past week and went to Samsung service center they did the same thing what i did and informed to change the board which nearly cost 18K
Click to expand...
Click to collapse
You will have to flash the cf auto root file.
This will fix the bootloop issue.
If it still persists, then you will have to flash the full recovery firmware.
Let me know if you want the link.
Sent from my SM-N9200 using Tapatalk
yashthemw said:
You will have to flash the cf auto root file.
This will fix the bootloop issue.
If it still persists, then you will have to flash the full recovery firmware.
Let me know if you want the link.
Sent from my SM-N9200 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply yashthemw
I had wiped all the partitions including system and internal memory... this wont delete cf auto root??
and can you please give me the steps to do that if possible??
azarhsaf said:
Thanks for the reply yashthemw
I had wiped all the partitions including system and internal memory... this wont delete cf auto root??
and can you please give me the steps to do that if possible??
Click to expand...
Click to collapse
First of all there is nothing wrong if you wipe everything and flash stock rom.
Now, if it is bootlooping, that means, the partitions aren't correct. Therefore if you flash cf auto root file, it will reset all partitions.
Just simply flash the cf auto root file via odin.
Reporting Via N910G
yashthemw said:
First of all there is nothing wrong if you wipe everything and flash stock rom.
Now, if it is bootlooping, that means, the partitions aren't correct. Therefore if you flash cf auto root file, it will reset all partitions.
Just simply flash the cf auto root file via odin.
Reporting Via N910G
Click to expand...
Click to collapse
Tried flash CF auto root file via Odin... still same reboot issue and flashed again using stock ROM... same issue persists
[that is after odin flashed-> reboots entering recovery mode -> installing updates -> erasing -> installing app updates then reboots here (this happens while flashing stock rom)]
azarhsaf said:
Tried flash CF auto root file via Odin... still same reboot issue and flashed again using stock ROM... same issue persists
[that is after odin flashed-> reboots entering recovery mode -> installing updates -> erasing -> installing app updates then reboots here (this happens while flashing stock rom)]
Click to expand...
Click to collapse
Just flash the cf auto root file, nothing else.
Reboot the device after flashing cf auto root file.
Reporting Via N910G
yashthemw said:
Just flash the cf auto root file, nothing else.
Reboot the device after flashing cf auto root file.
Reporting Via N910G
Click to expand...
Click to collapse
sorry, the same problem again any other solutions for this issue ?
Can you please let me know what is the filesystem should be used for /system /internal and other partition...
because i changed to f2fs before and reverted back all to ext4 now (all partitions which is shown in twrp advance wipe).
any advise?
azarhsaf said:
Can you please let me know what is the filesystem should be used for /system /internal and other partition...
because i changed to f2fs before and reverted back all to ext4 now (all partitions which is shown in twrp advance wipe).
any advise?
Click to expand...
Click to collapse
I had tried ext2 once.
Reporting Via N910G
Can anyone please help to fix this issue???
yashthemw said:
I had tried ext2 once.
Reporting Via N910G
Click to expand...
Click to collapse
No luck yet
have you tried this:
https://www.androidfilehost.com/?fid=24411628330025773
Reporting Via N910G
You can try this:
Flash your latest official rom via PC Odin with option Nand Erase All.
Upon booting, if not going to start-up log-in screen, remove and put back battery. Then go to stock Recovery and Wipe cache and Wipe data/factory reset.
Be patient and wait several minutes as the first boot usually takes a long time.
This should fix your problem.
This is unfair... Changed my battery.. Now it is working perfectly... How the hell firmware update damaging battery..??
Any how i got redmi note 3 last week and now going to sell note 4
Thanks to all who helped here...
So i just did the new update on my V20 and it sent me straight to TWRP and i cant get out of it. It always boots into TWRP. What can i do? ive already tried a factory reset and restoring my back up and nada. Help please.
Its now looking for stock boot image which on yours is currently modified with system rooted.
Try using lgbridge to repairs your boot image or if you have it flash the stock boot image using fast boot command or do a factory reset while in twrp then flash entire stock image with lgbridge.
Sent from my LG-H990 using XDA-Developers Legacy app
somemadcaaant said:
Its now looking for stock boot image which on yours is currently modified with system rooted.
Try using lgbridge to repairs your boot image or if you have it flash the stock boot image using fast boot command or do a factory while in twrp then flash entire stock image with lgbridge.
Sent from my LG-H990 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah none of those work. The OS is setting off some sort of flag that states it must go into recovery and wont stop going into recovery until that flag is changed which I assume is done by the update. I tried updating with UPPERCUT/LGUP and it errors out at 4%. So right now it's still stuck
It didnt install the update
type
Code:
fastboot erase fota
from bootloader and see if it boots after that.
This will for sure fix you up...
https://forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
listen to me2151
delete fota and then pull battery and reboot.
ota's downloaded to the fota folder will cause endless twrp loop.
freeze ota in system/privapps to avoid this again.
Sorry to post on here, but maybe we can get a few tips from each other.
Im also stuck at TWRP. I installed a ROM and went back and forth between both ROMS. After about 4 times of going back and forth between ROMS, my pattern didn't recognize on boot with my original backup and daily. I tried my pattern over 10 times and it wiped everything on me. The strange part was I was swiping my pattern 100% and it failed. Also, my tries were going up and down. It would say I have 6 tries left before my phone wipes, then I would stop anjd turn the screen off, and the screen would say I have 3 tries left, then 5 tries left. My tries were inconsistent, and it finally wiped everything.
I am now stuck on TWRP with no luck of restoring. I flashed the vs995 boot image and system image and it goes back to TWRP. I factory reset, wiped everything, made sure the system folder was clean, then flashed both images again and the same thing, no luck.
I also tried to restore with LGUP, but keeps stopping at 9%. I extracted the dll and copied it into the common folder and I get the same thing.
Error: Error Code = 0x2000, Flashing Fail
When I plug the phone into my computer it shows us996 and not vs995. Strange.
Any help would be amazing.
EDIT: Figured it out!
So, I extracted the dll file from the kdz file and I had to replace it with the one in the common folder. My error was not renaming the file, so the LGUP would stop at 9%. Make sure you pull the file, rename it, remove the old file from the folder, and flash on LGUP.
leyvatron said:
Sorry to post on here, but maybe we can get a few tips from each other.
Im also stuck at TWRP. I installed a ROM and went back and forth between both ROMS. After about 4 times of going back and forth between ROMS, my pattern didn't recognize on boot with my original backup and daily. I tried my pattern over 10 times and it wiped everything on me. The strange part was I was swiping my pattern 100% and it failed. Also, my tries were going up and down. It would say I have 6 tries left before my phone wipes, then I would stop anjd turn the screen off, and the screen would say I have 3 tries left, then 5 tries left. My tries were inconsistent, and it finally wiped everything.
I am now stuck on TWRP with no luck of restoring. I flashed the vs995 boot image and system image and it goes back to TWRP. I factory reset, wiped everything, made sure the system folder was clean, then flashed both images again and the same thing, no luck.
I also tried to restore with LGUP, but keeps stopping at 9%. I extracted the dll and copied it into the common folder and I get the same thing.
Error: Error Code = 0x2000, Flashing Fail
When I plug the phone into my computer it shows us996 and not vs995. Strange.
Any help would be amazing.
Click to expand...
Click to collapse
why dont you try flash custom rom?
rowihel2012 said:
why dont you try flash custom rom?
Click to expand...
Click to collapse
Tried and no luck. Stuck in TWRP.
akobirovruslan said:
So i just did the new update on my V20 and it sent me straight to TWRP and i cant get out of it. It always boots into TWRP. What can i do? ive already tried a factory reset and restoring my back up and nada. Help please.
Click to expand...
Click to collapse
Have you tried booting into twrp manually and reflashing twrp again? Try that
THIS WILL FIX YOUR TWRP BOOTLOOP. Tried and true. Follow step-by-step.
https://forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
i did this it worked https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328