I dunno what went wrong here...
1) I have GT-I9505 (SSN: -I9505GSMH). I installed Galaxy S4 toolkit
2) Reboot into download mode. Used toolkit/Odin to root phone. Boots up. See SU.
3) Reboot into download mode. Used toolkit/Odin. Flashed TWRP Recovery
4) Phone boots up normal. Reboot into TWRP recovery. Did a factory Reset. Format.
5) Installed Zip (Latest Omega 9.0 ROM), unchecked the things I didn't want to install. Completed install, no errors reported. Rebooted.
6) Phone stuck on Samsung boot screen. I left it overnight thinking sometimes it may take 15 mins to boot system after new install.
7) Woke up, battery dead. Tried to charge phone. No charging indicators when plugged in. With whatever juice I had left I booted into TWRP recovery, it starts to charge again as I see the % batter increase after 5 mins.
-=-=-=-=- Did the Following to try to repair
a) Reinstalled Omega, this time leaving alll options on. Rebooted, stuck in Samsung boot
b) Flashed Phil CWM touch recovery, did complete wipe to install new ROM. Rebooted into Phil recovery. Flashed OMEGA. Reboot, stuck in Samsung boot.
c) Rebooted into Phil recovery, installed echo ROM, rebooted. Black screen. Rebooted into Phil. This time cannot get into recovery.
d) Started panicking, used Odin flashed TWRP. Would not flash. Something displayed about PIT error. Flashed Phil again. Reboot into recovery, WORKS! (recovery only). Went back into Download mode flashed TWRP. Rebooted, also WORKS!. Did a factory wipe. During wipe there was an error. Format, factory reset, error during wipe. Flashed OMEGA. Reboot. Stuck on samsung boot loop.
e) Downloaded official Samsung kernal for i9505 thinking it was the full flash rom. Flashed with ODIN (hoping to put everything back to factory). Completed flash, phone boots. I get OMEGA ANIMATION!!! Waited for 15 mins. Stuck on Animation. Reflashed TWRP. Rebooted, installed OMEGA...again. Stuck on samsung boot screen.
-=-=-= Kinda frustrated. What did I do wrong in the beginning?
There are so many official roms for the S4 based on region. What can I do to put it back to factory again? I purchased phone in Australia @ Samsung store. I figured download the Australia ROM but there are like 5 of them 4 being network branded roms I think. THe other one XSA is unbranded?
I tried searching for help but so far nothing works.
omega ROM or any other custom ROM uses single CSC so before booting into system you must boot into stock recovery to apply CSC of that ROM, download stock recovery of that firmware the ROM was built from
after applying CSC it will work if not flash Omega 9.0 again , it will work :good::good:
arnob_xperia said:
omega ROM or any other custom ROM uses single CSC so before booting into system you must boot into stock recovery to apply CSC of that ROM, download stock recovery of that firmware the ROM was built from
after applying CSC it will work if not flash Omega 9.0 again , it will work :good::good:
Click to expand...
Click to collapse
Thanks for responding
So I take it when I did the full factory wipe and FORMAT the formatting part erased the CSC?
The steps are:
1) Find stock recovery of the original ROM OMEGA was built on. Use odin, flash that specific recovery. ( I might as well do a complete flash of the original stock firmware)
2) Use odin, replace recovery with TWRP, flash Omega this time no formatting
Reboot should be ok?
kabloomz said:
Thanks for responding
So I take it when I did the full factory wipe and FORMAT the formatting part erased the CSC?
The steps are:
1) Find stock recovery of the original ROM OMEGA was built on. Use odin, flash that specific recovery. ( I might as well do a complete flash of the original stock firmware)
2) Use odin, replace recovery with TWRP, flash Omega this time no formatting
Reboot should be ok?
Click to expand...
Click to collapse
first use CWM or TWRP or whatever you want and format everthing
flash a fresh firmware(latest i prefer)
then flash stock recovery via odin of the built version what v9 was used, simply reboot to recovery and it will say MULTI CSC APPLIED from fresh frimware you used
then flash TWRP/CWM and flash v9
again simply reboot to recovery and it will say MULTI CSC APPLIED from V9
it will reboot, you must need to apply CSC to boot your phone
I can confirm this!
I was trying to flash Omega 9 on top of jamal's 4.3 and my phone always booted to recovery. So I restored my stock touchwiz (no custom recovery or even root) nandroid backup and applied Omega 9: it worked!
douglascamata said:
I was trying to flash Omega 9 on top of jamal's 4.3 and my phone always booted to recovery. So I restored my stock touchwiz (no custom recovery or even root) nandroid backup and applied Omega 9: it worked!
Click to expand...
Click to collapse
thats right stock recovery boot is needed to apply CSC
problem
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
macoy_412 said:
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
Click to expand...
Click to collapse
Do you have an IMEI showing on your phone? What recovery did you use to flash Omega?
It matters, because some recoveries will screw it up.
Do you try to install with Philz recovery?
Sent from my GT-I9505 using xda premium
macoy_412 said:
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
Click to expand...
Click to collapse
At this point I think it is the CSC issue arnob-xperia mentioned.
This is how I corrected my issue.
1) Omega v10 uses newer base FW. In their description it tells u. (ex: ver 9 uses XUBMG5). Search on the i9505 forums here. I can't link for some reason I can't see any of the stickied threads, especially the one listing all avail stock firmwares.
Flash into Philz or TWRP do a complete wipe of everything including data. etc.
You MUST download the full firmware, Not just the smaller kernel and recovery or csc. The full stock fw is usually over 1.6 GB. Anything around that range and u got the right one for Odin flash with the md5. Use Odin to flash. I used 1.85 and it was fine.
2) Once done it will reboot and in theory you are stock everything. At this point, for me somehow the phone got stuck in fricken boot loop. I pulled out battery, reboot into stock recovery and made sure I saw the multicsc. Rebooted. Still boot loop.
After hours of doing all sorts of things and putting the phone aside for a day. Came back, flashed the stock fw again using Odin. Reboot into recovery. Check the multi csc. Reboot. Stuck in boot loop. Reboot to download mode. Then I decided to ROOT the phone for ****s and giggles. This worked!
Phone booted.
3) Now you have stock (for that specific OMEGA fw) w/ the matching CSC. From here on follow OMEGA flash instructions for the specific things it tells u to wipe. DO NOT DO A FULL WIPE/FORMAT like I did (what got me in the mess to begin with).
** For Galaxy S3s, S4s, for some reason I've always had problems with TWRP. I had better luck using Philz. Everyone's personal experience varies on this one.
** I think the problem has to do with the CSC which handles specific region phone and carrier modes. This doesn't mean that it won't work if you use a diff region CSC. Just that it has to match the FW base you are using otherwise you have all sorts of problems. After that you can go in android and setup your APNs etc if you have probs with data. I didn't have this problem and was testing using the UK fw base on AU network sim.
*** Why does Samsung make things so damn complicated. I remember way back in 2k3 using fricken ODIN (samsung flashing utitility) to flash **** and it was the same setup as now. This whole crap about CSC pairing is a bit annoying. It is bad enough there are 6+ variations of S4s lol...
Hope this helps.
wifi problem
kabloomz said:
At this point I think it is the CSC issue arnob-xperia mentioned.
This is how I corrected my issue.
1) Omega v10 uses newer base FW. In their description it tells u. (ex: ver 9 uses XUBMG5). Search on the i9505 forums here. I can't link for some reason I can't see any of the stickied threads, especially the one listing all avail stock firmwares.
Flash into Philz or TWRP do a complete wipe of everything including data. etc.
You MUST download the full firmware, Not just the smaller kernel and recovery or csc. The full stock fw is usually over 1.6 GB. Anything around that range and u got the right one for Odin flash with the md5. Use Odin to flash. I used 1.85 and it was fine.
2) Once done it will reboot and in theory you are stock everything. At this point, for me somehow the phone got stuck in fricken boot loop. I pulled out battery, reboot into stock recovery and made sure I saw the multicsc. Rebooted. Still boot loop.
After hours of doing all sorts of things and putting the phone aside for a day. Came back, flashed the stock fw again using Odin. Reboot into recovery. Check the multi csc. Reboot. Stuck in boot loop. Reboot to download mode. Then I decided to ROOT the phone for ****s and giggles. This worked!
Phone booted.
3) Now you have stock (for that specific OMEGA fw) w/ the matching CSC. From here on follow OMEGA flash instructions for the specific things it tells u to wipe. DO NOT DO A FULL WIPE/FORMAT like I did (what got me in the mess to begin with).
** For Galaxy S3s, S4s, for some reason I've always had problems with TWRP. I had better luck using Philz. Everyone's personal experience varies on this one.
** I think the problem has to do with the CSC which handles specific region phone and carrier modes. This doesn't mean that it won't work if you use a diff region CSC. Just that it has to match the FW base you are using otherwise you have all sorts of problems. After that you can go in android and setup your APNs etc if you have probs with data. I didn't have this problem and was testing using the UK fw base on AU network sim.
*** Why does Samsung make things so damn complicated. I remember way back in 2k3 using fricken ODIN (samsung flashing utitility) to flash **** and it was the same setup as now. This whole crap about CSC pairing is a bit annoying. It is bad enough there are 6+ variations of S4s lol...
Hope this helps.
Click to expand...
Click to collapse
I did flash the Omega v9.1 and applied the wifi fix but the wifi is still broken. I tried unrooting it by flashing the original rom and formatting the data but the wifi is still broken. I can't turn it on. Thanks for the instructions anyways. ))
no pit partition
also, when i tried to root it again, it fails and says there is no PIT partition..
Where is the csc in TWRP so I can so what ones on the phone..??
What stock firmware can I use for a Orange Network in the UK.
GT-i9505 stuck on boot when upgraded from omega v16 to v21
Hello guys,
Well, I followed all the instructions and flashed new bootloader and new modem and after that I installed omega v21 with Full swipe. After that I ended up stuck in boot animation. :s What to do? I already tried to re-flash modem and bootloader, updated CWM and tried to re-install that v21 and after that I flashed twrp over cwm and tried to re-install v21 but always I ended up stuck in that boot animation. :S All installs were successful, but it just wont boot.
What to do?
Hopefully you understand my problem.
Cheers from Finland!
Nico
EDIT:
Ok, I flashed omega rom v19 with full wipe and tried to boot. Didnt work, but then I installed Kies to my computer, opened Kies, Plugged USB in and started my phone and then Kaboom! It booted. What exactly happened there?
BizK1d said:
Hello guys,
Well, I followed all the instructions and flashed new bootloader and new modem and after that I installed omega v21 with Full swipe. After that I ended up stuck in boot animation. :s What to do? I already tried to re-flash modem and bootloader, updated CWM and tried to re-install that v21 and after that I flashed twrp over cwm and tried to re-install v21 but always I ended up stuck in that boot animation. :S All installs were successful, but it just wont boot.
What to do?
Hopefully you understand my problem.
Cheers from Finland!
Nico
EDIT:
Ok, I flashed omega rom v19 with full wipe and tried to boot. Didnt work, but then I installed Kies to my computer, opened Kies, Plugged USB in and started my phone and then Kaboom! It booted. What exactly happened there?
Click to expand...
Click to collapse
Hi, I am having the same problem. First I installed the new firmware (NA5) and modem, tested it with the Omega ROM v21 and boot caught on so now tested the rom Fox Hound 4.1 and am having the same problem.
Kies tested this option but have not had the same luck as you. = /
Anyone know the reason? The rom Google Edition Jamal runs on my phone.
i9505
I'm not having much success in switching to a 4.3 rom. I would appreciate any feedback I can get. I have repeated these steps multiple times including re-flashing twrp with no luck.*
SGS4 L720 4.2.2 MF9
CF autoroot
GooManager -> TWRP v2.6
Factory reset
Wipe data, cache, dalvik & system
Install pa_jfltespr-3.98.zip
Install pa_gapps-full-4.3.zip
Reboot system and I'm still in *4.2.2 with all data intact.*
TWRP is not wiping or installing but at each step it says successful. What am i missing?*
Try installing twrp 2.5.0.2 here http://forum.xda-developers.com/showthread.php?t=2361378 . Alot of people are reporting problems with 2.6...
Thanks for the quick response. Ok, I downloaded and used Odin to install TWRP 2.5.0.2
I again went through the steps outlined above - wipe, and install but no joy.
I still have all my files intact - nothing was wiped and 4.3 was not installed.
This is so bizarre I have to assume I am royally screwing something up.
I can't seem to find anyone else having a similar problem so that further confirms it must be operator error. But I can not figure it out!
Again, all suggestions would be much appreciated!!!
I just tried flashing cwm in recovery without success. Still stumped.
I have used all available custom recoveries and I stay on 4.3 much of the time. I've had the best luck with latest cwm recovery. I have not had any wipe issues that I know of but what I have had is I do get stuck on Samsung screen after I reboot from time to time on various 4.3 roms. I was told by Cordell to just hold power down, reboot and that has been how ive gotten around that. Currently using Slim Bean beta 3 and have NOT had the issue since updating. I was also told its not rom related but I don't quite understand as beta 3 slim is fine but 2 outa 3 reboots on beta 2 would have me stuck on Sammy screen until another reboot... Glad it hasn't been.an issue since beta 3 for whatever the reason.. anyway thats what my issues have been with 4.3.. I know the 1st thing to go when a phones been flashed too much is recovery but I've been crackflashing since 2010 (daily, sometimes multiple times one day..;o ) and never had a phone crap on me yet. (KnockonWood) Hope you get this resolved.
I suggest maybe odining back and catching ETAs to mf9 then flash supersu and see if that changes anything for you. Just try things and maybe something will fix it. Looking forward to twrp update. I used 2.5.0.2 for a while with no probs but if it is a recovery issue some are having i believe DTroy will address it and either him or Koush would probably know the answer.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Solved!
Thanks for the advice!
Odin to MDC
Forced OTA to MF9
Rooted& TWRP 2.5.0.2
Success!
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Try going here
Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
you need to try to install the Triforce MJA/4.3.1 kernal/MJA modem all at the same time. IDK what happened on the first try to boot loop you but once you updated the modem to mja you can't flash MF9 modem/kernel on top of it. Try that and let me know.
Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
You cant go from aosp to tw. You need to go back to stock. Just odin back to mj9 stock. Then reroot and use that rom with philz rec
Sent from my SPH-L720 using xda app-developers app
I seem to have bricked my phone. I flashed a couple roms and was having some random reboot problems (see http://forum.xda-developers.com/showthread.php?t=2651923).
Long story short, I've odin'd the stock MK2 tar, trying to get it to stock to accept the NAE update. I can't seem to get it past the "Android is upgrading.... Starting apps." screen.
Yes, I wiped everything, and even did a hard factory reset. I re-rooted, and odin'd Philz Touch 6 recovery. I would assume I could flash a rom, but when I transfer a rom to my SD card to flash -- it's never there. I download rom (just tried stock(ish)v06) and mount USB in Philz, copy to sdcard1, and after about 3 minutes, the file looks like it's there. When I try to flash from Philz recovery, I do not see the zip file to flash it. I tried copying it to another directroy -- still no file.
Is it time to accidentally back over my phone with my car and call my insurance agent?
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 <