I'd like to wipe the Delvik cache... Is there any way to do this in ODIN? I DO NOT HAVE RECOVERY.
I've been doing some research and if I can wipe the cache, the boot load would have to rebuild. Killing the apk that is freezing my S4.
Can someone confirm this? Or did I just confused myself even more...
you've given us almost nothing.
are you i337 or i337m? what firmware build? why arent you able to access recovery? are you rooted? what apk did you install?
sincity said:
I'd like to wipe the Delvik cache... Is there any way to do this in ODIN? I DO NOT HAVE RECOVERY.
I've been doing some research and if I can wipe the cache, the boot load would have to rebuild. Killing the apk that is freezing my S4.
Can someone confirm this? Or did I just confused myself even more...
Click to expand...
Click to collapse
You might be able to use ADB to wipe it, but you will have to do some research to find if it is possible or what the commands would be. And, as always, there is a chance of making things worse. ODIN is a tool for flashing, it is not a recovery substitute. I've never read about anyone ever using ODIN to wipe memory without replacing it with something else (ROM, Kernel, etc...). Maybe someone knows more about it though. So, good luck with your searching and reading. If you decide to check out ADB, you can search for tutorials here at XDA and on Google.
xBeerdroiDx said:
you've given us almost nothing.
are you i337 or i337m? what firmware build? why arent you able to access recovery? are you rooted? what apk did you install?
Click to expand...
Click to collapse
I337 Rooted MF3 --- Chainfire3D
scott14719 said:
You might be able to use ADB to wipe it, but you will have to do some research to find if it is possible or what the commands would be. And, as always, there is a chance of making things worse. ODIN is a tool for flashing, it is not a recovery substitute. I've never read about anyone ever using ODIN to wipe memory without replacing it with something else (ROM, Kernel, etc...). Maybe someone knows more about it though. So, good luck with your searching and reading. If you decide to check out ADB, you can search for tutorials here at XDA and on Google.
Click to expand...
Click to collapse
No luck with ADB because it doesn't full boot. I have trouble with the MTP driver loading... and I don't know if that is the problem either.
At this point maybe flashing anything to clear the cache... LOL!
Impossible to flash anything on MF3. C'mon people, we know this.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
The phone does not boot. Terminal emulator is a no go.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
08j3ct1v3 C said:
Ah, misread, my mistake.
Does it boot into "download mode"?
Click to expand...
Click to collapse
Yessir...
Terminal emulator is a no go.
When you say you don't have access to recovery....did you try to flash a custom recovery on the MF3 version and lose it that way?
---------- Post added at 05:18 AM ---------- Previous post was at 05:17 AM ----------
08j3ct1v3 C said:
Ok well the solution there is pretty simple then. Odin flash a recovery tar file that is compatible with your device. Then yank the battery after it completes and tries to reboot (unsuccessfully)...
Don't pull the battery until it tries to boot tho.
Hold the volume up, home, then power button to boot into recovery.
Not sure why you are dead set in wiping dalvik cache, to be honest. But that is how you could probably do it successfully.
I would just push an entire image back to the device and start from scratch, but that's just me.
Good luck
Click to expand...
Click to collapse
How do you suggest pushing an image back to the device on the MF3?
Related
I read where they're building these with Loki already installed now. Is this true? I tried to install the latest ROM awhile ago in TWRP, and it failed about as soon as it began. Any suggestions?
Have the driver's install
Place your phone into USB Debugging and hook it up
Use this to install another recovery
Flash properly as in Full reset, Wipe both caches, and format /system before flashing, unless you are on an older nightly, then skip the Full reset, and try and dirty flash with the other steps.
LostInMyHead said:
Have the driver's install
Place your phone into USB Debugging and hook it up
Use this to install another recovery
Flash properly as in Full reset, Wipe both caches, and format /system before flashing, unless you are on an older nightly, then skip the Full reset, and try and dirty flash with the other steps.
Click to expand...
Click to collapse
Could you explain this in some more depth please? I'm a total noob and am not understanding. Sorry.
bfishy22 said:
Could you explain this in some more depth please? I'm a total noob and am not understanding. Sorry.
Click to expand...
Click to collapse
PM me
same problem
I have the same problem I tried to install 3 different roms and get the fail message and then when I reboot have to re-root and I just don't know what I'm doing wrong. I have followed all steps given and still same problem if you can help me with this I would really appreciate it.
Honestly I think there is a problem with these nightly ROMs because when I install one, and reboot, I just get a black screen.
Sent from my GT-I9505 using xda app-developers app
This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.
Try flashing a different compatible kernel.
ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app
I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!
Glad it's working out for you.
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.
Alright so here's what I did, and how I got to my current situation and what the situation is.
What I did:
Had CM10.2 working fine on my rom. Recovery was TWRP (latest). Decided to flash PAC 4.3 cause I really like that rom. Flashed PAC 4.3. Worked fine, decided I wanted to restore titanium backups. Read in a few places that I needed to flash the SuperSU zip from chainfire. Downloaded the latest version from him and flashed in TWRP. TWRP took a -really- long time to flash the zip. After it finished I restarted the phone Wouldn't get past the samsung screen. Uhhh okay no problem.
I still have access to TWRP right? Yup, Still do. Do a full wipe and flash PAC 4.3 and Gapps. Flash is taking forever again. PAC gives no information at all (none of the usual ASCII artwork or anything). GApps loads the installer script but I get a can not mount /data and can not mount /system error.... Oh ****. Now I'm worried.
Download the PDA file from the sticky in the general section. (I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5) Pop the phone into download mode, and flash the PDA file via odin. Great, everything's going well. It flashes System, Flashes recovery, and everything else. Get a message saying All threads completed, Succeeded 1/failed 0. Awesome Right? No....
Phone restarts, goes into the stock recovery screen while something happens and restarts again. Now the phone's stuck on the samsung screen again. I can still access download mode and still access recovery (stock). When I access stock recovery it says "failed to mount /data (stale NFS file handle).... can't mount /data (stale NFS file handle)... E: failed to mount /data (stale NFS file handle).
Now what?... What can I do to fix this?
**EDIT**: Just did format on /data on stock recovery and it seems to have booted... False alert guys. Soft bricked, but nothing else.
Did you try a factory reset in stock recovery?
Sent from my SGH-M919G using XDA Premium 4 mobile app
Blaze9 said:
Alright so here's what I did, and how I got to my current situation and what the situation is.
What I did:
Had CM10.2 working fine on my rom. Recovery was TWRP (latest). Decided to flash PAC 4.3 cause I really like that rom. Flashed PAC 4.3. Worked fine, decided I wanted to restore titanium backups. Read in a few places that I needed to flash the SuperSU zip from chainfire. Downloaded the latest version from him and flashed in TWRP. TWRP took a -really- long time to flash the zip. After it finished I restarted the phone Wouldn't get past the samsung screen. Uhhh okay no problem.
I still have access to TWRP right? Yup, Still do. Do a full wipe and flash PAC 4.3 and Gapps. Flash is taking forever again. PAC gives no information at all (none of the usual ASCII artwork or anything). GApps loads the installer script but I get a can not mount /data and can not mount /system error.... Oh ****. Now I'm worried.
Download the PDA file from the sticky in the general section. (I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5) Pop the phone into download mode, and flash the PDA file via odin. Great, everything's going well. It flashes System, Flashes recovery, and everything else. Get a message saying All threads completed, Succeeded 1/failed 0. Awesome Right? No....
Phone restarts, goes into the stock recovery screen while something happens and restarts again. Now the phone's stuck on the samsung screen again. I can still access download mode and still access recovery (stock). When I access stock recovery it says "failed to mount /data (stale NFS file handle).... can't mount /data (stale NFS file handle)... E: failed to mount /data (stale NFS file handle).
Now what?... What can I do to fix this?
Click to expand...
Click to collapse
Did you try factory restore / reset in recovery?
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
goobieracing said:
Did you try a factory reset in stock recovery? Or maybe try odining the pit file also that somewhere on the forum. Maybe your partitions got corrupt flashing some how.
Sent from my SGH-M919G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
Blaze9 said:
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
Click to expand...
Click to collapse
It sounds like to me you need to do a lot more reading and learning before you do anything else. It has been a well known fact, and widely discussed in the AT&T S4 forums that a factory reset needs to be done after flashing firmware in ODIN in order for the previous data to be wiped from the phone and for it to boot up again.
goobieracing said:
Did you try a factory reset in stock recovery?
Sent from my SGH-M919G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
scott14719 said:
Did you try factory restore / reset in recovery?
Click to expand...
Click to collapse
scott14719 said:
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
It sounds like to me you need to do a lot more reading and learning before you do anything else. It has been a well known fact, and widely discussed in the AT&T S4 forums that a factory reset needs to be done after flashing firmware in ODIN in order for the previous data to be wiped from the phone and for it to boot up again.
Click to expand...
Click to collapse
Ah, I never had to use ODIN on the S4 before. Didn't know that. On my S2 I didn't have to wipe after flashing via ODIN.
Good to know, anyway. Thanks.
Blaze9 said:
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
Click to expand...
Click to collapse
I had to do a stock reset recovery the other day for something like this. Probably just left over files from previous stopping it from booting.
scott14719 said:
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
Click to expand...
Click to collapse
Sorry I learned something new today. Back in the infuse 4g days whenever I'd odined back to stock I always used the pit. I was under the influence that set everything up the way it came stock. Hope to see some of your work coming to sthe s4. Maybe you help the sense port going on in the international thread lol. Not trying to add work to ur day but I OK know if u, jt, and entropy can bring ICS to a out dated phone u might have the skills to ad your 2 cent.
Sent from my SGH-M919G using XDA Premium 4 mobile app
---------- Post added at 02:18 AM ---------- Previous post was at 02:01 AM ----------
Blaze9 said:
Ah, I never had to use ODIN on the S4 before. Didn't know that. On my S2 I didn't have to wipe after flashing via ODIN.
Good to know, anyway. Thanks.
Click to expand...
Click to collapse
I had to Odin to stock the first time two days agao but mine booted and I only had stock recovery. When it started up the ROM everything was crashing and that's what fixed it. Glad you fixed it though.
Sent from my SGH-M919G using XDA Premium 4 mobile app
Pretty much got the same problem. Seems that somehow my device encrypted itself and since I didn't know...I don't have a password to give it. So I got a encrypted device that can't be decrypted, thus, I can't format, install, wipe, etc. Not sure if you got the same, but mine is about the same symptoms.
But is it ok to flash "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5" on mine? Kinda confused with all this MDL, MDB, and MF3 stuff. Mine was an MDL. So is flashing MDB stock ok anyway? Or should I find the stock for MDL?
EDIT: Just flashed MDL stock anyway. Worked fine and now I'm starting from scratch. No more problems so far. I might stay away from TWRP for a bit now though. Surprised there isn't a guide or warning for this problem though.
gerard0986 said:
Pretty much got the same problem. Seems that somehow my device encrypted itself and since I didn't know...I don't have a password to give it. So I got a encrypted device that can't be decrypted, thus, I can't format, install, wipe, etc. Not sure if you got the same, but mine is about the same symptoms.
But is it ok to flash "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5" on mine? Kinda confused with all this MDL, MDB, and MF3 stuff. Mine was an MDL. So is flashing MDB stock ok anyway? Or should I find the stock for MDL?
EDIT: Just flashed MDL stock anyway. Worked fine and now I'm starting from scratch. No more problems so far. I might stay away from TWRP for a bit now though. Surprised there isn't a guide or warning for this problem though.
Click to expand...
Click to collapse
The PW TWRP asks for? IT's just TWRP, if I remember correctly.
I have had several custom roms using TWRP with no problems. Today I decided to try pacman rom and nandroid backed up my negalite wonderom. downloaded pacman to external card, rebooted to TWRP. I formatted internal storage and did full wipes on everything but external sd. I tried installing pacman zip and get FAILED unzipping and updating partition. so I then try flashing my old rom and get same error. I then nandroid back to previous rom and boots as expected. If i reboot again, I get stuck on samsung galaxy s4 boot screen. I've tried repeating all these steps but now I am without a phone until one of you nice people help me. What can I do? Please help.
csrredcoat said:
I have had several custom roms using TWRP with no problems. Today I decided to try pacman rom and nandroid backed up my negalite wonderom. downloaded pacman to external card, rebooted to TWRP. I formatted internal storage and did full wipes on everything but external sd. I tried installing pacman zip and get FAILED unzipping and updating partition. so I then try flashing my old rom and get same error. I then nandroid back to previous rom and boots as expected. If i reboot again, I get stuck on samsung galaxy s4 boot screen. I've tried repeating all these steps but now I am without a phone until one of you nice people help me. What can I do? Please help.
Click to expand...
Click to collapse
Odin back to stock.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Odin back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I did odin back to stock, ut i am stuck on galaxy s4 boot screen. What can I do to fix? Thanks
During this whole ordeal, I was trying to install CWM over TWRP and accidentally checked repartition in ODIN, it didn't seem to do anything ..just hanged and I pulled battery. I am now wondering if this screwed anything up and if so, what can I do?
csrredcoat said:
I did odin back to stock, ut i am stuck on galaxy s4 boot screen. What can I do to fix? Thanks
Click to expand...
Click to collapse
Take out battery. Put in back in. Go to stock recovery (by pressing volume up and power button and letting go when you see tiny blue letters) from there just do a factory reset then reboot. Dont worry if you a dead android its ok. Then you should be ok.
---------- Post added at 11:28 PM ---------- Previous post was at 11:12 PM ----------
csrredcoat said:
During this whole ordeal, I was trying to install CWM over TWRP and accidentally checked repartition in ODIN, it didn't seem to do anything ..just hanged and I pulled battery. I am now wondering if this screwed anything up and if so, what can I do?
Click to expand...
Click to collapse
Well from my understanding we should not have repartition checked. Dont know the outcomes tho but im pretty sure now you need pit files for gs4 sprint to remap the partitions for your phone back the way it was. Should be here in xda but if you cant find them then just odin again a stock tar and do a factory reset in stock recovery. See if that works.
Back to Stock but have a question
So I was able to successfully odin back to stock. I am confused about format data vs wipes. I had some issues on a ROM and someone in a forum advised to format to truly erase any junk left behind by other roms. I did this in TWRP and installed a rom and it fixed the former issues I had on that rom. So I thought I had a new strategy, to format not just wipe.
So now I have CWM and don't even see the option to format data. If I want to make sure I erase everything, how do I ? Just doing factory reset, wipe data, cache and dalvik seems to leave files behind including personal files on internal storage. Just want to learn the best practices to avoid issues. I am kinda glad this happened, been a learning lesson. Thanks to all!
Software/Baseband Version MDC to MF9
After ODIN back to stock I am on MDC and want to get back to MF9. This is the procedure I used a few months ago HERE Is this the best way? Thanks.
csrredcoat said:
So I was able to successfully odin back to stock. I am confused about format data vs wipes. I had some issues on a ROM and someone in a forum advised to format to truly erase any junk left behind by other roms. I did this in TWRP and installed a rom and it fixed the former issues I had on that rom. So I thought I had a new strategy, to format not just wipe.
So now I have CWM and don't even see the option to format data. If I want to make sure I erase everything, how do I ? Just doing factory reset, wipe data, cache and dalvik seems to leave files behind including personal files on internal storage. Just want to learn the best practices to avoid issues. I am kinda glad this happened, been a learning lesson. Thanks to all!
Click to expand...
Click to collapse
Im not so sure on CWM since ive been using twrp so I can help you there.
csrredcoat said:
After ODIN back to stock I am on MDC and want to get back to MF9. This is the procedure I used a few months ago HERE Is this the best way? Thanks.
Click to expand...
Click to collapse
Its better if you just accept ota (*optional* do a factory reset when already at mf9.) Or just get the mf9 stock tar and just odin that when you have problems
You can download the mf9 tar here
http://forum.xda-developers.com/showthread.php?t=2375523
ROMANTiC KiD said:
Im not so sure on CWM since ive been using twrp so I can help you there.
Its better if you just accept ota (*optional* do a factory reset when already at mf9.) Or just get the mf9 stock tar and just odin that when you have problems
You can download the mf9 tar here
http://forum.xda-developers.com/showthread.php?t=2375523
Click to expand...
Click to collapse
OK, I am confused but eager to learn. I just did a ODIN back to stock, I am now unrooted. I did a factory reset in stock recovery. Now I think I should be able to click update firmware to get to MF9 but it says no updates found or I am up to date. I don't get this. Why is it not finding any updates?
Even More Confused!
edit
Ok, it is downloading MF9 in background now. Not sure why it initially said no updates found. I should be good now. Thanks!
Hi I'm having a problem with my phone right now. I have it rooted with team win recovery and super su installed. I downloaded the new 4.4.2 update but it wont work. It will only boot me into recovery and when ever i restart it will power off again into recovery. Is there anyway to stop this?
im in the same boat. well, was.
to stop the loop, simply go to TWRP and clear your cache.
then you're back at step 1.
now the question is, do we need to un-root, uninstall TWRP and go back to stock recovery, or both?
and how?
Which section is wiping the cache in?
legohood said:
Which section is wiping the cache in?
Click to expand...
Click to collapse
Wipe?
Or clear.
Just check a couple of them, it's fairly easy to find. It says "Clear cache/dalvik?" just wipe them out.
*OR* go to File Manager, go to /cache and remove the .zip file.
R3dbeaver said:
Wipe?
Or clear.
Just check a couple of them, it's fairly easy to find. It says "Clear cache/dalvik?" just wipe them out.
*OR* go to File Manager, go to /cache and remove the .zip file.
Click to expand...
Click to collapse
I mean clear, I can't find the actual button to do it are you positive that using filemanager is completely safe?
legohood said:
I mean clear, I can't find the actual button to do it are you positive that using filemanager is completely safe?
Click to expand...
Click to collapse
yup. just delete the f.zip under (root)/cache and ur good.
Do you mean wipe Dalvik Cache and the Cache in advanced wipe?
legohood said:
I mean clear, I can't find the actual button to do it are you positive that using filemanager is completely safe?
Click to expand...
Click to collapse
Try fastboot erase cache ,yes you need to be 100% stock, stock recovery and unrooted, so you need to flash the stock recovery with fastboot but at this point just wait for the sbf 4.4.2 rogers firmware to show up and flash with rsdlite. If you make any stupid panicky flashes without knowing what you are doing you'll hard brick your device .
It has happened so many times after a new update comes up
Sent on my Lenoto X
flashallthetime said:
Try fastboot erase cache ,yes you need to be 100% stock, stock recovery and unrooted, so you need to flash the stock recovery with fastboot but at this point just wait for the sbf 4.4.2 rogers firmware to show up and flash with rsdlite. If you make any stupid panicky flashes without knowing what you are doing you'll hard brick your device .
It has happened so many times after a new update comes up
Sent on my Lenoto X
Click to expand...
Click to collapse
When whatever that is comes out do you mind walking me through it, I'm kind of clueless with what I'm doing right now
legohood said:
When whatever that is comes out do you mind walking me through it, I'm kind of clueless with what I'm doing right now
Click to expand...
Click to collapse
Yah, do you or have you ever used fastboot ( android sdk tools) ? Pm me if you need help. Just be very careful, hard bricking is quite easy if you flash the ota after certain conditions
Sent on my Lenoto X
legohood said:
Do you mean wipe Dalvik Cache and the Cache in advanced wipe?
Click to expand...
Click to collapse
Yes.
Sent from my XT1058 using xda app-developers app
Thank you both so much I can use my phone again!