Related
Okay, today I was about to flash a new rom so I attempted to wipe, but I got an error that the phone could not mount the cache (and later couldn't mount data). It says "E:Can't mount CACHE:recovery/command" on the next line "E:Can't mount CACHE:recovery/log" and the next "E:Can't open CACHE:recovery/log". So I have tried reflashing recovery to fix it and it did not work. I cannot flash any rom without an error or restore my nandroid backups. I am in the process of trying to restore the nandroid backups throught fastboot. Can anyone give me any help on this?
SOLUTION: blancoisgod recommends formatting the cache partition to fix this problem
Did you pull the battery and retry?
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
toby4059 said:
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
Click to expand...
Click to collapse
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
No man dont turn it into tmobile. Now everyone is gonna ride you because you broke it and your going to return it because of what you have done,not the manufacturer.
Go ahead and turn it in, but please read around a bit before you do this again.
CBConsultation said:
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
Click to expand...
Click to collapse
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
toby4059 said:
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
Click to expand...
Click to collapse
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
CBConsultation said:
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
Click to expand...
Click to collapse
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
toby4059 said:
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
Click to expand...
Click to collapse
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
CBConsultation said:
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
Click to expand...
Click to collapse
Okay I will give that a try thanks.
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
blancoisgod said:
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
Click to expand...
Click to collapse
Did you do that and did it fix? I did that through adb and thats when it stopped booting, although I think the boot issue is unrelated to my current problem.
i did it via clockwork
Alright, I will try this if I can ever get my phone started again.
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Flash a different kernel.
Period
your welcome
TehZam said:
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
Click to expand...
Click to collapse
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
KonoeKyon said:
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and post back to you!
TheAxman said:
Flash a different kernel.
Period
your welcome
Click to expand...
Click to collapse
If you don't mind me asking, what kernel are you using?
mixlex said:
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
Click to expand...
Click to collapse
I have used the Touchwiz kernal.
blyndfyre said:
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
Click to expand...
Click to collapse
Tried that and done that, no go.
________________________________________
Thank you everybody for the help.
what procedures are you using for all of this? is there a specific guide you are following?
xBeerdroiDx said:
what procedures are you using for all of this? is there a specific guide you are following?
Click to expand...
Click to collapse
So at first I used this [ROOT] Root Samsung Galaxy S4 with Motochopper. Same problem.
Went back to stock and used this
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13. Same problem encountered.
Went back to stock and did it again using Same problem with this one as well.
It happens with every custom rom besides the stock rom and Cyanogenmod Rom. I can't even reboot to do anything .
Thanks for the help guys, I greatly appreciate it.
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
TheAxman said:
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
Click to expand...
Click to collapse
Yes, I do have a backup. It happens to every custom ROM that I have encountered with.
Stock & Cyanogenmod roms work fine when rebooting.
Would you mind sharing what kernel you are using? I jused used faux kernel. Same thing.
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
xBeerdroiDx said:
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
Click to expand...
Click to collapse
Sorry for the confusion, I used your guide!
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
TheAxman said:
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
Click to expand...
Click to collapse
yep I am that sure haha.
jetlitheone said:
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
Click to expand...
Click to collapse
Your method worked! Thank you very much, I greatly appreciate it.
hey guys,
Im curious to why my phone is constanly soft bricking after flashing a rom, ive tried:
- Pure google,
- Pacmac
- Foxhound
and they have all bricked my device, the only one i have gotten to run is Omega.
I do exactly as it says to do yet it is still bricking my device, I have a Samsung galaxy s4 i9505.
If anyone could enlighten me and tell me what i am doing wrong it would be alot of help.
qwwrr said:
hey guys,
Im curious to why my phone is constanly soft bricking after flashing a rom, ive tried:
- Pure google,
- Pacmac
- Foxhound
and they have all bricked my device, the only one i have gotten to run is Omega.
I do exactly as it says to do yet it is still bricking my device, I have a Samsung galaxy s4 i9505.
If anyone could enlighten me and tell me what i am doing wrong it would be alot of help.
Click to expand...
Click to collapse
i suggest to wipe system, flash rom, wipe data and cache, reboot.
Supposedly twrp has a bug in it..try cwm.
twrp crap was causing the same thing to my phone. screw that crap and flash real recovery, cwm!
faiyo said:
Supposedly twrp has a bug in it..try cwm.
Click to expand...
Click to collapse
Im using CWM recovery though
What do you call a brick. Does it boot and hang on a logo or only boot to recovery etc?
Sent from my GT-I9505 using Tapatalk 4
andyjg247 said:
What do you call a brick. Does it boot and hang on a logo or only boot to recovery etc?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
It get to the samsung galaxy s4 i9505 screen then it doesnt go any further
qwwrr said:
It get to the samsung galaxy s4 i9505 screen then it doesnt go any further
Click to expand...
Click to collapse
Do you do the wipes, particularly data, before flashing the rom?
My phone does the same thing, but It gets to the google emblem and just keeps repeating the 4 coloured cirles for ages
if you flash to stock and it still happens than its probably your battery
haldi15 said:
if you flash to stock and it still happens than its probably your battery
Click to expand...
Click to collapse
Im running stock at the moment, it works fine until i put a custom rom onto it
I already post to wipe system with recovery, flash custom rom, wipe data and cache AFTER flashing rom, reboot!
Hello,
I don't know why this is happening to my phone. I recently got this phone. I rooted it but it is a stock flash. I only keep apps that I need and disable everything else. However, about 50% of the time, any calls that I get, as soon as I accept it, it's restarts. Also, Whenever I am making a call, the phone goes dark, never comes back on to cancel a call or something and restarts if no one picks up. If someone picks up, the screen goes back on.
What gives?
rationalthinker1 said:
Hello,
I don't know why this is happening to my phone. I recently got this phone. I rooted it but it is a stock flash. I only keep apps that I need and disable everything else. However, about 50% of the time, any calls that I get, as soon as I accept it, it's restarts. Also, Whenever I am making a call, the phone goes dark, never comes back on to cancel a call or something and restarts if no one picks up. If someone picks up, the screen goes back on.
What gives?
Click to expand...
Click to collapse
Most probably ROM problems. Try changing the ROM.
abaaaabbbb63 said:
Most probably ROM problems. Try changing the ROM.
Click to expand...
Click to collapse
But it's a stock ROM. I didn't even install any other ROM.
rationalthinker1 said:
But it's a stock ROM. I didn't even install any other ROM.
Click to expand...
Click to collapse
Yeah, but system errors can occur, like a file being corrupted. This is solved by reflashing the system partition.
abaaaabbbb63 said:
Yeah, but system errors can occur, like a file being corrupted. This is solved by reflashing the system partition.
Click to expand...
Click to collapse
Hey, can you provide me a link or a tutorial on how I can do that?
Thank you.
rationalthinker1 said:
Hey, can you provide me a link or a tutorial on how I can do that?
Thank you.
Click to expand...
Click to collapse
You just take your ROM (Be sure it's the exact version you have installed), and flash it from recovery, without wiping anything.
Today and after deciding to simply restart my Nexus 6P, it booted into TWRP menu, I tried to reboot again, but no luck. can someone please help?
is there a way to get off the TWRP menu and boot my phone normally?
Note: The root used to simply work fine for about a month now.
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Gytole said:
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Click to expand...
Click to collapse
Rooted my phone, and it was working fine for about a month, I done nothing unusual, All i did is restart my phone and it went to the TWRP menu, thats all. Im stuck there now.
I don't recall doing an update or whatever. Im using "BETA-SuperSU-v2.67-20160121175247.zip"
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
MahmoudEMH said:
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
Click to expand...
Click to collapse
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Heisenberg said:
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Click to expand...
Click to collapse
Yes to each one of those questions.
MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
I will have to call you out here buddy. If you have indeed tried to flash all factory images, you won't even have TWRP in the first place.
Go to this wonderful guide by the wonderful @Heisenberg, and scroll down to "10. How To Flash The Factory Images (And Return To Stock)". You will find very clear instruction on how to return your phone to its factory stock state. This will most likely get rid of the problems you're facing.
MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
If you had flashed the full factory images I don't see how it's possible at all to be in your current situation. Explain how you flashed them, and exactly what you flashed please.