Database Users

Please Help may have accidently wipe stock ROM without a restore point.

1) Used the toolKit to unlock Bootloader
2) install twrp using Toolkit
3) transfered AOKP rom to device using airdroid
4) Went to TWRP, System Wipe 3 times, Clear cache 3 times
5) attempt to flash AOKP ZIP
6) ZIP failed to install no idea why
7) Tried to restart and now stuck at the GOOGLE logo
Please help is there anything i can do?
Hmm could i use the toolkit to flash an img file? Im dling a stock img atm.

First off.. Don't panic ... It wasn't your fault it failed ... I know because it happened to me . don't get it from "downloads" or goomanager .. Get it from the second post I. That thread on the latest date
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Sent from my Nexus 4 using Tapatalk 2

italia0101 said:
First off.. Don't panic ... It wasn't your fault it failed ... I know because it happened to me . don't get it from "downloads" or goomanager .. Get it from the second post I. That thread on the latest date
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I did get it from the second post though, and how can i load into ADB?

italia0101 said:
Second . I don't think otg works in twrp so you will have to use adb to load the ROM
Click to expand...
Click to collapse
OTG does work in TWRP. I have found that it doesn't like some flash drives - no idea why. I've tried quite a few, some of mine work all the time, other just won't work.

adoute said:
OTG does work in TWRP. I have found that it doesn't like some flash drives - no idea why. I've tried quite a few, some of mine work all the time, other just won't work.
Click to expand...
Click to collapse
Ok went to twrp and used the ADB sideload feature but it said OTG cable fail to mount.

FIXED
WOOO FIXED IT NVM! Mod please delete thanks for help guys

Someone with more experience correct me if I'm wrong, but shouldn't we be avoiding wiping system in TWRP prior to flashing ROMs? I believe I read a thread (probably on RootzWiki) that said wiping system messes things up as you lose the ability to flash a ROM in the "traditional" manner. I wipe cache, dalvik, then click factory reset. I leave system alone and I've never had a problem with flashing ROMs.

[Q] doing something wrong?

Ok I clearly must be doing something wrong when it comes to flashing ROMs as the only I used to be able to install them was through Odin on my old gs2 and so far have been unable to install one via recovery on my new s4.
I follow the instructions exactly but yet find my self either bootloop(rarely) or most of the time stuck at the screen with white text of "Samsung Galaxys4 gt-i9505" on screen.
I have waited up to 30 mins on this screen as I have read first boot can take some time but 30mins should be enough?
Eventually I have to flash stock via odin to have my phone back working.
Loosely step by step this has been my process.
1)flash a recovery with odin(whichever recovery rom author recommends)
2)boot into recovery
3)full wipe
4)install zip from ext card
5)select rom
6)wait till installed it then asked me to install root, have tried both install and not install root
7)phone reboots, stuck on Samsung Galaxys4 gt-i9505 screen.
This is the same with omega,foxhound and wanamlite, clearly I am missing something here for it not to install correctly.
If it matters I am on t-mobile UK.
I have tried rooting the stock rom first before installing anything still no difference.
Thanks for reading

sometimes mine gets stuck on that screen as well after flashing something... i just hold the power button to restart the phone and then generally it boots up fine...
also I'm assuming you have an i9505?
Sent from my GT-I9505 using Tapatalk 4 Beta

Yes i9505, I have tried long holding power button but just goes back to that screen. Just finding it quite frustrating now it must be something simple I'm missing.

igrieve said:
Ok I clearly must be doing something wrong when it comes to flashing ROMs as the only I used to be able to install them was through Odin on my old gs2 and so far have been unable to install one via recovery on my new s4.
I follow the instructions exactly but yet find my self either bootloop(rarely) or most of the time stuck at the screen with white text of "Samsung Galaxys4 gt-i9505" on screen.
I have waited up to 30 mins on this screen as I have read first boot can take some time but 30mins should be enough?
Eventually I have to flash stock via odin to have my phone back working.
Loosely step by step this has been my process.
1)flash a recovery with odin(whichever recovery rom author recommends)
2)boot into recovery
3)full wipe
4)install zip from ext card
5)select rom
6)wait till installed it then asked me to install root, have tried both install and not install root
7)phone reboots, stuck on Samsung Galaxys4 gt-i9505 screen.
This is the same with omega,foxhound and wanamlite, clearly I am missing something here for it not to install correctly.
If it matters I am on t-mobile UK.
I have tried rooting the stock rom first before installing anything still no difference.
Thanks for reading
Click to expand...
Click to collapse
After flashing the ROm from recovery did u wipe cache & dalvik from recovery and reboot ?
If not pls try once and see it should work

123hiten said:
After flashing the ROm from recovery did u wipe cache & dalvik from recovery and reboot ?
If not pls try once and see it should work
Click to expand...
Click to collapse
just tried for omega and foxhound and no difference just going to try the last one now.

just download a pre-rooted stock, flash via odin, then flash a recovery via odin, wipe everything, format /system and then install a custon first boot takes around 3 minutes...

Have now managed to get wanamlite up and running using the wipe cache & dalvik after installing rom, I am still none the wiser as to why the other two wouldn't install.

igrieve said:
Have now managed to get wanamlite up and running using the wipe cache & dalvik after installing rom, I am still none the wiser as to why the other two wouldn't install.
Click to expand...
Click to collapse
It should work my friend give it a try again and which recovery are you using? Name
Sent from my GT-I9500 using xda premium

Maybe your base rom wasen't the same as the rom you tried to flash?
Sent from my GT-I9505 using xda premium

My friend has the exact same issue on his i9505 using twrp, he tried to flash various ROMs but not getting past boot screen, fortunately his back up worked but still no luck in getting a ROM to flash...very odd
Edit: he is running a 3 network supplied phone if that make any difference
Sent from my Nexus 4 using xda premium

I have exactly the same!
Formatted, factory reset, wipe cache/dalvik, stock firmware using Odin, Nothing is working so far..
$%^$%
Now trying to instal FoxHound 0.5.

Well still having problems lol no idea why but I can only install two ROMS but I am happy with the one I'm currently using but your always curious to see what the others are like.

If you guys are using twrp as your recovery and you format internal sd this will happen. It is a know issue with that recovery. It messes with the partition and you need to flash a different recovery. You may need to Odin back to stock to get the partition right and go from there. Hope this helps.
Sent from my GT-I9505 using xda app-developers app

Im currentl;y using philz_touch recovery, I have been having to go back to odin and flash stock rom just to get the phone running again after trying these roms. I havent tried any roms from the original android development forum so might see if I get any joy with them, I know it must be something silly I'm missing

It happens if the base ROM you are currently on isn't the same or similar to the ROM you're trying to flash. Maybe changelog of the ROM you're trying to flash is a lot higher tan your current ROM and things get mixed up. I have always had success by performing a factory reset after flashing the ROM.
I had the exact same problem going from MDE firmware to Omega V7. After flashing Omega again I did a factory reset and it was sweet
Sent from my GT-I9505 using XDA Premium HD app

[Q] flexrom - SOLVED-

I've been successfully using the new 4.3 ROM on my a500. After flashing the latest, it worked beautifully until I shut it down. Upon rebooting, it stays in a boot loop. I am able to get into TWRP 2.4.4, but cannot restore my backup or flash any ROM.
It looks like I accidentally deleted the flexrom folder from the tablet. I have not previously been successful flashing via USB. How can I recover my tablet?
Any ideas would be appreciated.

LPMatt said:
I've been successfully using the new 4.3 ROM on my a500. After flashing the latest, it worked beautifully until I shut it down. Upon rebooting, it stays in a boot loop. I am able to get into TWRP 2.4.4, but cannot restore my backup or flash any ROM.
It looks like I accidentally deleted the flexrom folder from the tablet. I have not previously been successful flashing via USB. How can I recover my tablet?
Any ideas would be appreciated.
Click to expand...
Click to collapse
seems a bit strange u cannot do anything from recovery...what happens when u do?
Do u still have Skrilax_CZ bootloader?
Think I'd reflash the v8 bootloader/recovery pkge and go from there
Sent from my GT-I9300 using Tapatalk 4 Beta

Managed to get apx working and flashed bootloader v9. Got to twrp 2.4.4 but could not flash a rom. Flashed an apx bundle with b/l v8 and Thors 1.7 cwm. Flashed a rom with aroma and it looked successful, but would not boot past the wifi screen. Says process failed.
The flexrom issue seems to be solved, but I had to repartition. Could that be it? Don't know what the proper partition sizes should be.
Sent From Here

LPMatt said:
... but I had to repartition. Could that be it? Don't know what the proper partition sizes should be.
Sent From Here
Click to expand...
Click to collapse
U dont need to know the partition sizes??
Just run babsector. rar it does it for u and will flash bootloader/recovery as well...its in the root guide in my sig
Which rom are u flashing?
Make sure u do a full wipe.
Sent from my GT-I9300 using Tapatalk 4

That did it! I'm back on 4.3 with the latest cwm for the a500. Wish I could use TWRP 2.6.1, but I still can't get that one to load. What I have is working great, though. Thanks for your help!
Sent From Here

That's awesome m8, sorry cant help with TWRP but glad you got yaself fixed up!!
Sent from my GT-I9300 using Tapatalk 4

After odin flash to stock firmware, Galaxy S4 can't mount '/data'

Recently my Galaxy S4 was having boot problems. It wasn't able to get past the "Samsung: Custom" logo. I was using TWRP 2.6 and the CM 10.2 8-19 nightly. I tried to do wipe all data and cache then re-flash the rom, no difference I tried to flash CWM Touch, no difference. At this point I figured something just went wrong when I originally rooted and flashed TWRP. I decided that it would be best to start from scratch and flash to stock in Odin.
I download a file from stockroms.net (can't post the full link as I'm a new member, but its a pretty easy website to navigate)
When the file is unzipped it has a .tar md5 file in it. I factory reset, wipe cache, and go into download mode. I boot up Odin 1.85 and load the .tar file into the PDA line. I make sure that the phone is connected fine, and I hit start. Everything goes fine, it says it passes and on the phone it appears everything went fine. After it reboots though, It wont make it past the "Samsung: Custom" logo again. It wont even hang on the logo, it will just shut off after a few seconds of showing it. I'm thinking that it's trying to boot, but cant. So I boot into the stock recovery, and it gives me this text at the bottom:
# Manual Mode #
-- Applying Multi-CSC...
successfully applied multi-CSC
E: failed to mount /data (invalid argument)
can't mount '/data' (invalid argument)
E: failed to mount /data (invalid argument)
So it looks to me that the phone is just unable to access the /data folder to boot into, and it gets stuck. How can I fix this?
EDIT: Also want to say that "repartition" was not checked in odin.
EDIT2: It seems that I fixed the problem, thanks for the help guys!

Can you do a factory reset in recovery?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
Can you do a factory reset in recovery?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Yes I did

You'll want to flash a different recovery until you find one that can fix your /data issue.
I have great luck with TWRP 2.5.0.2, though some others have said it causes problems when formatting /data on TW ROM's.
I use AOSP and have not had a problem since I last used TWRP 2.6 and subsequently went back to 2.5.0.2.
2.6 and some other recoveries just kinda suck.
It's amazing that a phone as popular as the Galaxy S4 has gotten such slow development process from CWM and TWRP. S3 recoveries were all rock solid within a month or so of release. We're not what, FIVE+ months into release and TWRP still hasn't gotten it 100% right. And I don't remember what the deal was with stock CWM (not Phillz which I have no experience with).

CZ Eddie said:
You'll want to flash a different recovery until you find one that can fix your /data issue.
I have great luck with TWRP 2.5.0.2, though some others have said it causes problems when formatting /data on TW ROM's.
I use AOSP and have not had a problem since I last used TWRP 2.6 and subsequently went back to 2.5.0.2.
2.6 and some other recoveries just kinda suck.
It's amazing that a phone as popular as the Galaxy S4 has gotten such slow development process from CWM and TWRP. S3 recoveries were all rock solid within a month or so of release. We're not what, FIVE+ months into release and TWRP still hasn't gotten it 100% right. And I don't remember what the deal was with stock CWM (not Phillz which I have no experience with).
Click to expand...
Click to collapse
I would just flash the .img recovery file straight through Odin correct?
EDIT: Sorry, I meant the .tar file

You should not get any files from stockroms.net. I have seen many people including myself try their stuff and fail. Always get you stuff from XDA.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

graydiggy said:
You should not get any files from stockroms.net. I have seen many people including myself try their stuff and fail. Always get you stuff from XDA.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll try to remember that in the future. I actually just retried what I did with the stockroms.net file and the one that's in the sticky post here and it worked. I'm now back into TW and I'll be flashing a ROM in a bit. So thanks for the help guys, I guess I just needed to get my stuff from the right sources.

How did you fix it
Hello,
May I ask how did you fix the problem??
Thanks !

Fix #2
In my case rooting with CF-AUTO-ROOT fixed the data folder !

[Q] Cant mount sdcard, stuck without a ROM?

Hi, so I decided to install CM11 on my nexus 4, but before that I had to unlock the bootloader and root. Bootloader unlocked succesfully but I couldn't root or flash a ROM cus the zips are not in my sdcard and I'm stuck without a ROM (phone just plays boot animation continuously). So I searched about adb push command, tried that and according to my CMD window it works, but in CWM when I try to install from zip, the zip isnt there.
cwm is latest version so thats not the issue. Solutions proposed by other threads arent working either.
Any ideas?
Thanks in advance.
EDIT:
I have used the guide in this thread
http://forum.xda-developers.com/showthread.php?t=2266654
It seems like this person has run into the same problem as me, but no one answered on the thread either.
r8revealed said:
Kind of an urgent problem as well, A friend of mine has had a bootloop on the Nexus 4 using this guide.
Upon installing CWM, the phone fell into a bootloop (Superuser hasnt been installed yet). After that, just in case, we did a Wipe data factory reset, wipe cache partition, and then wipe dalvik cache and no luck. The device has an unlocked bootloader and everything else went flawlessly. What can be done now to get the phone rooted and up and running? (An unroot is a possible solution, but maybe something else can be done so that an unroot wont be necessary).
Click to expand...
Click to collapse

Guys I found a solution.
You can use a toolkit by wugfresh found at http://www.wugfresh.com/nrt/ to revert to stock.
thanks anyway!