Why Do I keep having issues when Im trying to flash ROM updates. Once I boot into recovery the tablet always gives me errors that it cant mount cache, etc.. so the only way I can get the system to ever boot again is to flash back to stock and start from scratch.
Ive had this issue with multiple roms
yamaha_wins said:
Why Do I keep having issues when Im trying to flash ROM updates. Once I boot into recovery the tablet always gives me errors that it cant mount cache, etc.. so the only way I can get the system to ever boot again is to flash back to stock and start from scratch.
Ive had this issue with multiple roms
Click to expand...
Click to collapse
Which recovery are you using? TWRP, CWM? And what version of said recovery?
philz touch is what its called im pretty sure. Ive been updating the omni rom a few times now. this made about the 5 update before it happened again.
You could try TWRP. Its what I've used as long as I've owned my Nexus 10.
I've attached a flashable copy if you want to give it a shot.
thanks. I'll give it a try.
Related
ive tried a whole bunch of roms and the behavior seems to be very consistent.
Here's the scenario, same for every rom:
-boot into TWRP, advanced wipe -> wipe everything
-flash rom over adb sideload
-reboot system
-rom comes up just fine the first time, log into google, restore apps
-any time i reboot after, it sits on "Galaxy s4" boot screen, if I then reboot into recovery, TWRP asks for password because it can't mount partitions.
-only way ive found to get out of this is to format data, then reflash.. only until the first reboot again.
stock rom works flawless, the only custom rom that also worked flawless was task650's AOKP 4.2 rom, which was strange but i used it for couple months. now since i i updated to his latest 4.3 release the same issue came up, so i tried again a number of different roms.. no luck
ive exausted my google-fu and these forums, can someone please help... is this a kernel issue? bad hardware? am i just doing something very simple very wrong?
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
jd1639 said:
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
Click to expand...
Click to collapse
same thing, except this time it didnt even boot once, stuck on "galaxy s4" logo, then rebooting back into TWRP prompted a password coz it couldnt mount anything...
i think it gets stuck on boot logo because it cant mount partition same way TWRP cant, but i have no idea why it wouldnt be able to after a reboot or what could be screwing it up
Why don't you try flashing a new recovery?
Having some issues getting a recovery to be flashed on this new device, I am not use to a phone that when rooted doesn't have some stock recovery that actually works. And by that I mean, allows me to install zip from file. All I get is the option to reboot, flash from adb, install from external, wipe factory reset, wipe cache, and install from cache.
Sorry if this has been asked a few times before, but with my searching I didn't find any one answer that solved my problem. Tried flashing a recovery via odin but it said Auth fail for the recovery. Going to try a few other things and see what I can come up with.
Thanks in advanced!
What recovery are you trying to flash? I believe the closet thing we have to a custom recovery is safestrap. Is that what your trying to install?
Ysosrslawl said:
Having some issues getting a recovery to be flashed on this new device, I am not use to a phone that when rooted doesn't have some stock recovery that actually works. And by that I mean, allows me to install zip from file. All I get is the option to reboot, flash from adb, install from external, wipe factory reset, wipe cache, and install from cache.
Sorry if this has been asked a few times before, but with my searching I didn't find any one answer that solved my problem. Tried flashing a recovery via odin but it said Auth fail for the recovery. Going to try a few other things and see what I can come up with.
Thanks in advanced!
Click to expand...
Click to collapse
It sounds like you flashed philz touch recovery witch will not work with the VZW S5 you need to flash SafeStrap Recovery. You might need to Odin back to stock and re root your device to get it back to normal first.
chrisbass said:
What recovery are you trying to flash? I believe the closet thing we have to a custom recovery is safestrap. Is that what your trying to install?
Click to expand...
Click to collapse
I didn't flash anything when I first started rooting the phone I just used towelroot, then when the OTA messed it up I went and did the NCG to NE9 method using odin and towelroot. But every time I went into recovery, it has been the same. It wasn't until I used the toolkit from the forums that installed safestrap and busybox did I actually get a different recovery, but even if I reboot into recovery it still takes me to the stock one first and then on reboot i can access safestrap.
Yes, that's how safestrap works, through a process called "bootstrapping". It never replaces your stock recovery so when you boot into recovery it'll always be stock but upon boot you'll be presented with the safestrap option.....totally normal
On another note, my Supersu binaries wont update so I'm going back to stock anyway. I think I may leave it at stock for a while until I see some more ROMs come out.
Ysosrslawl said:
On another note, my Supersu binaries wont update so I'm going back to stock anyway. I think I may leave it at stock for a while until I see some more ROMs come out.
Click to expand...
Click to collapse
Your other option is what I have done. I first went the safestrap route but installed rom on rom slot before finding out about the bugz in safestrap. So I odined back to stock. Instead of installing something with bugz in it I rooted, installed supersu and Xposed framework with some modules. Wanam module gives you most of the customizations found in custom roms. Tons of other modules for pretty much anything you want to tweak. Works like a champ on stock system.
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
wasa67 said:
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
Click to expand...
Click to collapse
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
blusydays said:
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
Click to expand...
Click to collapse
I did all that before, and it still didn't work.
I think your problems are related to flashing the recovery, did you try to revert back the the old one ?
It first started this morning when my phone suddenly started rebooting while I was using it. Then I thought it as a ROM issue and flashed a new ROM over it. Everytime I try to flash something on system. TWRP Hangs and the phone restarts itself.
Tried repairing data, system partitions from TWRP, same thing happens. Bootloops when I try to repair data partition
Tried restoring nandroid backup. When it says flashing data, TWRP freezes and the phone starts bootlooping.
Can anyone help?
I have tried doing the EFS flash via adb from PC.
I'm stuck with the exact same problem since months.
CallMeAldy said:
I'm stuck with the exact same problem since months.
Click to expand...
Click to collapse
No luck?
Have you tried Claiming Warranty?
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
StarRavier said:
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
Click to expand...
Click to collapse
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
TJ_bab said:
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
Click to expand...
Click to collapse
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
StarRavier said:
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
Click to expand...
Click to collapse
Doesn't crash during backup but crashes during restore.
TJ_bab said:
Doesn't crash during backup but crashes during restore.
Click to expand...
Click to collapse
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
StarRavier said:
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
Click to expand...
Click to collapse
it doesn't boot at all.
It bootloops
I have the exact same problem. Last week upgraded to 7.0, root, stock room, viper4arise audio and EX kernel and that's it. while taking pictures it froze then that boot loop, somehow I managed through a combination of flashing factory image through fastboot, locking, unlocking, reflahsing, to get it to boot normally, then yesterday I was taking pictures again and it refroze then bootloops. Now I am able to fastboot factory images but it doesn't get me out of the bootloops, and in TRWP same as you, I cannot flash anything on data or system. Repairing the file system doesn'T change anything, I did like on other threads also and flashed factury, restored nandroid then flash factory but the restore on TRWP always hangs up.
I was wondering if there is someone knowing the adb dd commands to impose the raw copying back of the restore ? Maybe that would work.
Did you try wiping system under wipe > advanced in TWRP?
In twrp, can you open a terminal and check the results of this (basically, doing a full read-only test of your flash)
Code:
dd if=/dev/block/mmcblk0 of=/dev/null
Hi, today i just played with file systems today and now i can't install any other roms excepting supermanrom. So i think i have a problem with file systems. Which file system does s7 edge using for default? Can any master help me? After im installing any rom it's stuck at bootloop
Which one should i use for example system and data file? ext4 or f2fs or any other?
Can you give us some more information?
if your stuck in boot loop? can you not boot into twrp?
Did you turn off OEM unlocking in developer options?
If you can load twrp? lots of info on returning to stock on here
just use search for installing to stock after bad flash.
Or other option would be flash another custom Rom.
Or are you saying you cant do any of the above?
If so what errors are you getting? it may help others that know more on
returning to stock.
I only flashed my first Rom to my S7E a few days ago after two bad flashing and had to have phone fixed in shop
to be honest I just did not read every thing and missed out apart and got stuck in boot loop.
but this time did the same but had twrp installed and just kept reading up on errors i was getting and in the end
i got it sorted.
May not of been much help but hope you get it sorted.
Good Luck
leggoman said:
Can you give us some more information?
if your stuck in boot loop? can you not boot into twrp?
Did you turn off OEM unlocking in developer options?
If you can load twrp? lots of info on returning to stock on here
just use search for installing to stock after bad flash.
Or other option would be flash another custom Rom.
Or are you saying you cant do any of the above?
If so what errors are you getting? it may help others that know more on
returning to stock.
I only flashed my first Rom to my S7E a few days ago after two bad flashing and had to have phone fixed in shop
to be honest I just did not read every thing and missed out apart and got stuck in boot loop.
but this time did the same but had twrp installed and just kept reading up on errors i was getting and in the end
i got it sorted.
May not of been much help but hope you get it sorted.
Good Luck
Click to expand...
Click to collapse
I can boot into twrp but i cant flash stock frimware with odin. It's giving FAIL error to me immidietly when im trying to do. And yes, OEM was open before
Now i flashed stock rom via odin, but when i install twrp again on my device it stucking at boot loop. Why?
Then i realized something that whatever i flash something via odin or something else, its stucking at bootloop
sdiown said:
Hi, today i just played with file systems today and now i can't install any other roms excepting supermanrom. So i think i have a problem with file systems. Which file system does s7 edge using for default? Can any master help me? After im installing any rom it's stuck at bootloop
Which one should i use for example system and data file? ext4 or f2fs or any other?
Click to expand...
Click to collapse
Format all with ext4 (in twrp). Especially the system. Because all touchwiz cusrom can only run on ext4. After all normal, you can just format to f2fs for data and cache