I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
You can either odin stock. It's about a 1.8gb file.
Or you can get a known working ROM on your sd card, factory reset wipe, wipe preload, wipe system, install known working rom+gapps+whatever, wipe cache and wipe dalvik. Reboot. If it sticks at the samsung logo pull the battery and then try to reboot again. Sometimes first boot can take a while. I'd give it 10 minutes before throwing in the towel lol
I bricked my phone by updating Hyperdrive (which I will never (curse words... lots of them) use again. Can someone tell me where to find this stock file? I've been searching long enough to get frustrated and delete several less diplomatic posts, settling with this one.
hey guys, I am a little confused. I just came to the S4 from a galaxy nexus, and I previously used CWM as my recovery option when doing clean install of new ROMS.
When I rooted my S4, I installed TWRP (via goomananger, version 2.5.0.2) because of people saying its much better (on the galaxy nexus forums). However, I keep reading issues of people being stuck in bootloops for TWRP when wiping data.
My question is -- what is this issue? Are you not supposed to clean flash with TWRP?? Or do you only do "factory reset" option in TWRP and not wipe the data?
As I am a little confused on this issue, is it more safe to just install most recent CWM and use that as recovery instead?
Thanks alot
No worries
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
cidorov said:
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
Click to expand...
Click to collapse
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Surge1223 said:
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Click to expand...
Click to collapse
Just to follow up, that's what I ended up doing. I used the "No-wipe" factory image, odin'd it, re-rooted (I don't know if I had to do that step, but I did), and then loaded my ROM of choice and it works perfectly now. Thanks!
I recently formatted my internal storage because I felt like I needed a clean wipe. After doing so, flashing anything and rebooting into it will make it hang on the Samsung logo. I flash everything through TWRP v2.5.0.2 and I never had problems until I formatted. Now to get anything to work, I have to "format data" through TWRP and flash after that in order to boot into anything (every single time). And even after booting into it, I can't flash anything (or even simply reboot) without having to see the stuck screen again. Any ideas? My phone is MDK.
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
WhoNeedszzz said:
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
Click to expand...
Click to collapse
Thanks! I think that worked
Ok... So...
I installed fulmics through TWRP and all worked great
After that, I installed a v30 Rom also with TWRP and that worked great, too, but i decided i like fulmics more and wanted to go back
Retried TWRP and kinda worked, but some errors were popping up all the time, so i decide to reinstall it
Now here i am. When it boots, goes straight in TWRP. I tried a stock zip to flash with TWRP, no luck.
When in TWRP I can see the phone on pc, internal storage in empty.
Fastboot works.
When i load up LGUP, under the version tab, it shows fulmics mod and i can't take any action
How fried is it?
Roti23 said:
Ok... So...
I installed fulmics through TWRP and all worked great
After that, I installed a v30 Rom also with TWRP and that worked great, too, but i decided i like fulmics more and wanted to go back
Retried TWRP and kinda worked, but some errors were popping up all the time, so i decide to reinstall it
Now here i am. When it boots, goes straight in TWRP. I tried a stock zip to flash with TWRP, no luck.
When in TWRP I can see the phone on pc, internal storage in empty.
Fastboot works.
When i load up LGUP, under the version tab, it shows fulmics mod and i can't take any action
How fried is it?
Click to expand...
Click to collapse
Try doing a complete wipe, wipe cache, Dalvik, data, system. Then wipe internal storage via the format data option and reboot recovery. I am guessing that you're on the h850 variant so Flash the 20s complete firmware zip then flash SuperSU or magisk. See if it boots into system.
I do still suggest hooking it up to your PC and flashing stock firmware kdz 20s using uppercut. If if it is recognizing fastboot commands then you should have no issue flashing a new recovery image after you load the stock kdz, you may even be able to flash a new recovery image instead of going through all the other steps that I listed. Which may some your issue. But it's best to format data entirely before flashing anymore ROMs, and use lgup via uppercut to flash stock firmware and let it boot entirely before reflashing fulmics.
But formatting data is key to reset the system folders which were leftover from other ROMs and likely the cause of the issues you experienced.
Hi,
My current problems are: my internal storage is completely deleted somehow and when I try to start the device it's bootlooping.
What happened before that was:
1. I was in MIUI 10 globe rom and had the regular TWRP (before treble thing I think)
2. I installed orangefox recovery so I could install a treble RR rom.
3. I backed up my MIUI rom and installed the RR rom without problems
4. Then I wanted to go back to MIUI rom
5. First I installed normal TWRP img into my recovery, because I couldn't recover the MIUI rom in orangefox (couldn't find the file)
6. Then I tried to recover the MIUI rom, but I didn't factory reset before i recovered. I thought that would happen anyway if i recovered a rom. But my recovery file didn't include bootloader and firmware. I had 2 recovery files in my internal storage. One of everything except the bootloader and firmware and the other recovery file was of the bootloader and firmware (i forgot to include them the first time i backed up)
7. So anyway, I recovered the first file and everytrhing was fine, but then immediately i also recovered the second file (the bootloader and firmware only). But the second file failed to recover.
8. I tried to boot the device, but it bootlooped at the MI globe image, then went back to MI logo, then mi globe image, etc. And finally it goes back to TWRP automatically.
9. Went back to recovery to see what's wrong. First I did a normal factory reset (only system, cache and dalvik, no internal storage) so I could install the RR rom I still had in my storage
10. Suddenly I see NOTHING in my internal storage in TWRP. Shows 0 gb.
So can anyone tell me what went wrong??? I never touched the 'format internal storage/data' thing in TWRP, but somehow it deleted it??? Wth happened?
And more importantly, what do I do now? Do I treat this as a bootloop or a bricked device? I know I have to use ADB and stuff to reset the device, right? Or Do I have to do something else?
Anyway, thanks in advance!
Edit: wait, i formatted /data now in TWRP and it booted into MIUI 10 after but with internal storage gone now of course. But I'd still like to know what went wrong.
hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore