Related
So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.
Hi All,
Would really appreciate some help. Tried flashing a 4.3 ROM and had some troubles deleting apps (kept rebooting when It tried uninstalling). So I went back to Omega, but found that it would let me install the rom but when I reboot it hangs at the splash screen. I have tried factory reset, format data, cwm, twrp, philz touch and get the same outcome. I have tried fixing permissions after formatting the data as well. Anyone got any ideas how I can get my phone to reboot after installing or recovering would be really really welcome.
Thanks for any help,
Mike.
Mykew said:
Hi All,
Would really appreciate some help. Tried flashing a 4.3 ROM and had some troubles deleting apps (kept rebooting when It tried uninstalling). So I went back to Omega, but found that it would let me install the rom but when I reboot it hangs at the splash screen. I have tried factory reset, format data, cwm, twrp, philz touch and get the same outcome. I have tried fixing permissions after formatting the data as well. Anyone got any ideas how I can get my phone to reboot after installing or recovering would be really really welcome.
Thanks for any help,
Mike.
Click to expand...
Click to collapse
Hi,
Look HERE
Thanks for taking time to answer. You think I need to go back to stock? What will that change, that flashing other ROMs and recoveries hasn't? Could my boot loader be corrupted?
Sent from my GT-I9505 using Tapatalk 4 Beta
Will give it a try when I get back from work... Thanks.
Sent from my GT-I9505 using Tapatalk 4 Beta
Mykew said:
Will give it a try when I get back from work... Thanks.
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi,
Yes.
Return to stock, and then, try flashing again.
For the latest 4.3 ROMS , you need the latest recoveries,otherwise they just give errors.
Also for deleting unwanted apps and other junk, try ROM CLEANER
Mykew said:
Hi All,
Would really appreciate some help. Tried flashing a 4.3 ROM and had some troubles deleting apps (kept rebooting when It tried uninstalling). So I went back to Omega, but found that it would let me install the rom but when I reboot it hangs at the splash screen. I have tried factory reset, format data, cwm, twrp, philz touch and get the same outcome. I have tried fixing permissions after formatting the data as well. Anyone got any ideas how I can get my phone to reboot after installing or recovering would be really really welcome.
Thanks for any help,
Mike.
Click to expand...
Click to collapse
im having same trouble except i have had the trouble ever since i installed TWRP 2.6, stalling on splash screen, i it usually fixes itself after a 10 second hold of the power button but it is annoying. Any solution arise at all?
malybru said:
Hi,
Yes.
Return to stock, and then, try flashing again.
For the latest 4.3 ROMS , you need the latest recoveries,otherwise they just give errors.
Also for deleting unwanted apps and other junk, try ROM CLEANER
Click to expand...
Click to collapse
I'm flashing the stock home.tar file but still getting stuck at samsung flash screen. Even stock isn't getting me past this! Still able to flash and boot once of the flashed roms or recoveries though. Anyone got any ideas for me please???
Hello everyone. I recently rooted,unlocked bootloader and installed a ROM on my N4. Everything was fine until I decided I wanted the stock image back on my phone. Then someone weird started happening after I flashed the Google 4.3 Stock ROM, my phone would get stuck on the x logo, forever.
I tried sideloading different roms & kernels but it would keep getting stuck forever on the ROM boot animation logo. I tried googling the issue and looking all around to no avail. I have tho,discovered. That if I wipe my Dalvik cache right after an install it would boot but would yet again get stuck on the "Android is Upgrading" starts apps... message.
If anyone has any idea or solution for my problem I would be incredibly grateful. Thank you very much in advance everyone. :fingers-crossed:
How did you flash the stock images?
Chromium_ said:
How did you flash the stock images?
Click to expand...
Click to collapse
Using The Nexus Root Toolkit 1.72 the first few times. Then I tried using fastboot individually.
Xraze0 said:
Using The Nexus Root Toolkit 1.72 the first few times. Then I tried using fastboot individually.
Click to expand...
Click to collapse
Try flashing them manually again. Use this guide and make sure you follow each step carefully.
Well, I did everything the thread said. I'm still stuck at the X logo. ( Yes, I have wiped my cache and done a factory reset via recovery ) Do you maybe have any other suggestions? Thanks.
Xraze0 said:
Well, I did everything the thread said. I'm still stuck at the X logo. ( Yes, I have wiped my cache and done a factory reset via recovery ) Do you maybe have any other suggestions? Thanks.
Click to expand...
Click to collapse
Weird, unfortunately I'm pretty much out of ideas. Maybe its worth a try to flash the stock images of a different android version. (ie: if you flashed the 4.3 stock images, try flashing the 4.2 stock images)
EDIT: It worked, thank you so much man. Saved me from replacing it! One last question tho, I seem to have no Wifi? It can't turn wifi on.
Chromium_ said:
Weird, unfortunately I'm pretty much out of ideas. Maybe its worth a try to flash the stock images of a different android version. (ie: if you flashed the 4.3 stock images, try flashing the 4.2 stock images)
Click to expand...
Click to collapse
EDIT: It worked, thank you so much man. Saved me from replacing it! One last question tho, I seem to have no Wifi? It can't turn wifi on.
Last night my phone wanted to update to 4.4.4 because it's been wanting to for a while, but I know it wouldn't work because my phone is rooted. It had tried this at least 3 times before and everything was fine; download update, tries to install, fails, boots right back up. I wanted to get rid of the Update notification in the top bar, so I just ran it again thinking it'd be okay. Well, this time it bricked my phone, leaving me at a neverending loop at the boot animation. I first tried to wipe the cache and dalvik cache, which did nothing. Then I tried a factory restore, which also did nothing. Then I reinstalled the stock 4.4.3 rom I had been using, which did nothing. Then I wiped the SD card completely and reinstalled a stock 4.4.4 rom through sideload, which has done nothing. My phone just sits at the boot animation and taunts me. Worse yet, I have a 16-hour drive tomorrow and my phone was going to be the majority of my sanity during that time.
What should I do?? Is there anything I can do? Normally I would just contact Google to get a replacement (I've done this before when the 4.2 update was causing a lot of bricks,I think it was 4.2 anyway, I forgot) but I'd like to have a working phone for my 16 hour trip..... if possible. Any help would be greatly appreciated! Thank you.
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
CCody said:
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
Click to expand...
Click to collapse
I had a Vanir 4.4.3 rom on my phone that I tried to flash as well, but for some reason it went right into "Optimizing Apps" after the first boot, something I hadn't seen before. Then it got stuck at "Starting Apps...", then after a restart, it too was stuck at the boot animation.
I can boot into recovery luckily, but that's all I can do. I have CWMR v6.0.3.5. I've tried just about everything I can think of. [edit] I was able to contact Google for some live chat support and am now #2 in the queue. Hopefully they can either help me or get a replacement going. Either way, I'd still love any help you guys can give me, I'd really like to get it fixed rather than waiting for a replacement.
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
CCody said:
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
Click to expand...
Click to collapse
I've done that already, Factory Reset + wipe cache + wipe dalvik cache + format system/data/cache/sdcard/data/media. The phone was completely bare and that's when I sideloaded the stock 4.4.4 rom (otherwise it's stuck at the Google boot screen). I'll try it again, though.
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
RawrNate said:
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
Click to expand...
Click to collapse
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
CCody said:
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
Click to expand...
Click to collapse
Yeah haha, it's really really strange. I appreciate you trying to help me, though! Lucky for me I'm getting a "One-time exception replacement" since my warranty is expired but they must be super stumped with the issue as well xD
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
CCody said:
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
Click to expand...
Click to collapse
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Wait, how do I flash the binaries since they're .tgz files?
RawrNate said:
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Click to expand...
Click to collapse
This is really strange man. Flashing stock ROM is the last resort but even that seems to be failing for you.
Have you tried downloading the stockRom again (just to make sure it isn't corrupted). Also, maybe you can try using TWRP instead of CWM this time.
Good luck.
RawrNate said:
Wait, how do I flash the binaries since they're .tgz files?
Click to expand...
Click to collapse
No need to flash them, since you are on a factory image, sry.
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
RawrNate said:
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
Click to expand...
Click to collapse
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
CCody said:
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
Click to expand...
Click to collapse
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
RawrNate said:
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
Click to expand...
Click to collapse
Jesus!
What about custom ROM? Cyanogenmod maybe? Make sure to downlaod the M7-Release.
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
RawrNate said:
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=tZbvuikfnks
CCody said:
https://www.youtube.com/watch?v=tZbvuikfnks
Click to expand...
Click to collapse
Oh good that was easier than I thought xD
I recently tried to run ART instead of delvik and now my phone freezes just after the Samsung and Verizon boot screens. The screen reads "Android is upgrading... optimizing app 1 of 1". The phone will stay on this screen until the battery goes dead. I've already tried recovery mode and wiping the cache partition, but to no avail. Any advice or guidance to help me get my phone back in working order would be greatly appreciated.
dvsdave214 said:
I recently tried to run ART instead of delvik and now my phone freezes just after the Samsung and Verizon boot screens. The screen reads "Android is upgrading... optimizing app 1 of 1". The phone will stay on this screen until the battery goes dead. I've already tried recovery mode and wiping the cache partition, but to no avail. Any advice or guidance to help me get my phone back in working order would be greatly appreciated.
Click to expand...
Click to collapse
Reinstall whatever ROM you were on. That's the only thing that worked for me. There might be another solution, but this is what I used to work. I did everything you did and it still wouldn't boot until I did a clean flash of my ROM. Hope this helps.
flash rom = factory reset?
jagrave said:
Reinstall whatever ROM you were on. That's the only thing that worked for me. There might be another solution, but this is what I used to work. I did everything you did and it still wouldn't boot until I did a clean flash of my ROM. Hope this helps.
Click to expand...
Click to collapse
Thanks jagrave! I guess I neglected to mention that my s5 is completely stock, so I don't have a custom ROM. Will a factory reset do the same thing?
dvsdave214 said:
Thanks jagrave! I guess I neglected to mention that my s5 is completely stock, so I don't have a custom ROM. Will a factory reset do the same thing?
Click to expand...
Click to collapse
Yes a factory reset from recovery will set it all back to stock/normal, including which runtime your using back to stock dalvik.