Related
I am in a really bad spot, my Shift is stuck in a boot loop.
Before this happened, I booted into recovery, made a new backup, and then booted back up, mounted the sd card, and copied a previous backup into the folder. Rebooted into recovery and restored the backup from a couple weeks ago that I just copied over.
Now the phone wont boot, I get a buzz and the white HTC screen, then black, then back to the starting buzz again and the white HTC screen again, then back to recovery.
I've searched through this forum, but I didn't see anything that sounded like a similar problem. What could have happened?
I would just RUU back to factory and re-root, but I can't get the phone booted to a high enough state for the RUU to work.
Any ideas? I really need to get this figured out before work tomorrow.
I have tried flashing the latest version of ClockworkMod Recovery, that didn't seem to help
I was on 2.5.1.8 and now CWM is 3.0.1.4
I tried reflashing the engineering hboot, that didn't work either
I can't get a logcat
I've also tried reflashing the original hboot, I see the switch to S-OFF, but that doesn't change the bootloop
Have I bricked my phone?!!
How could restoring a nandroid do that?!!
I was finally able to run the RUU using fastboot, I'll update once it completes
Edit: Ok, so using Fastboot and running the RUU I was able to get back to a working bootable state.
This time I'm going to try out the guide from the CM wiki http://wiki.cyanogenmod.com/index.php?title=HTC_Evo_Shift_4G:_Full_Update_Guide
quixotiCfluX said:
I have tried flashing the latest version of ClockworkMod Recovery, that didn't seem to help
I was on 2.5.1.8 and now CWM is 3.0.1.4
I tried reflashing the engineering hboot, that didn't work either
I can't get a logcat
I've also tried reflashing the original hboot, I see the switch to S-OFF, but that doesn't change the bootloop
Have I bricked my phone?!!
How could restoring a nandroid do that?!!
I was finally able to run the RUU using fastboot, I'll update once it completes
Click to expand...
Click to collapse
IF you could get into fastboot you could have accessed recovery. Could you not do anything there?
riggsandroid said:
IF you could get into fastboot you could have accessed recovery. Could you not do anything there?
Click to expand...
Click to collapse
Nope, I would get put into recovery on every boot attempt, and couldn't get past it.
Also, I think there are some errors in the steps over on the CM wiki, so I don't recommend anyone try that process until it gets corrected.
quixotiCfluX said:
Nope, I would get put into recovery on every boot attempt, and couldn't get past it.
Also, I think there are some errors in the steps over on the CM wiki, so I don't recommend anyone try that process until it gets corrected.
Click to expand...
Click to collapse
With s off and fastboot working, and it booting to recovery why didn't you just wipe then reflash?
Sent from my PG06100 using Tapatalk
quixotiCfluX said:
Nope, I would get put into recovery on every boot attempt, and couldn't get past it.
Also, I think there are some errors in the steps over on the CM wiki, so I don't recommend anyone try that process until it gets corrected.
Click to expand...
Click to collapse
cm wiki?
links?
strapped365 said:
With s off and fastboot working, and it booting to recovery why didn't you just wipe then reflash?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Tried that multiple times, always got kicked back to recovery. Even tried wiping each partition individually. Had to RUU to factory then start over, thankfully I had just finished a complete Titanium Backup of my system, so everything was waiting for me on my sd card.
riggsandroid said:
cm wiki?
links?
Click to expand...
Click to collapse
Link in the second post:
quixotiCfluX said:
This time I'm going to try out the guide from the CM wiki http://wiki.cyanogenmod.com/index.php?title=HTC_Evo_Shift_4G:_Full_Update_Guide
Click to expand...
Click to collapse
quixotiCfluX said:
Tried that multiple times, always got kicked back to recovery. Had to RUU to factory then start over, thankfully I had just finished a complete Titanium Backup of my system, so everything was waiting for me on my sd card.
Click to expand...
Click to collapse
Yeah I'm not sure you know what recovery is....recovery is clockwork 3.0.1.4 which clears data cache makes backups and flashes roms themes mods tweaks....bootloader is the white screen that shows s-off and if you use the volume keys and power button you could have booted into recovery and wiped your data cache and dalvik cache than fresh flash instead of unrooting
Sent from my PG06100 using Tapatalk
strapped365 said:
Yeah I'm not sure you know what recovery is....recovery is clockwork 3.0.1.4 which clears data cache makes backups and flashes roms themes mods tweaks....bootloader is the white screen that shows s-off and if you use the volume keys and power button you could have booted into recovery and wiped your data cache and dalvik cache than fresh flash instead of unrooting
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I am aware of the difference between the bootloader, fastboot, and recovery. In the OP, i gave the versions of clockwork I had been using, thanks for playing though.
quixotiCfluX said:
I am aware of the difference between the bootloader, fastboot, and recovery. In the OP, i gave the versions of clockwork I had been using, thanks for playing though.
Click to expand...
Click to collapse
alright cool your jets, we're just trying to help. Your wording in the post, makes it sound odd.
come into IRC
http://forum.xda-developers.com/showthread.php?t=909398
riggsandroid said:
alright cool your jets, we're just trying to help. Your wording in the post, makes it sound odd.
come into IRC
Click to expand...
Click to collapse
His wording makes it sound like he is stuck and don't know how to flash anything my thought are you made a back up with 2.5 whatever and it won't work with 3.whatever
Sent from my PG06100 using Tapatalk
strapped365 said:
His wording makes it sound like he is stuck and don't know how to flash anything my thought are you made a back up with 2.5 whatever and it won't work with 3.whatever
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
seems like he got it working
ok n/m dont come in IRC
Sorry for the strange wording, I was a bit frantic when I started the thread.
quixotiCfluX said:
Sorry for the strange wording, I was a bit frantic when I started the thread.
Click to expand...
Click to collapse
Okay are you picking reboot recovery after Nand restore or picking reboot system now
Sent from my PG06100 using Tapatalk
strapped365 said:
Okay are you picking reboot recovery after Nand restore or picking reboot system now
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
right now neither, because I've just finished up re-rooting after RUU
I was picking reboot system, and it would go through the start of a boot cycle, but then die prior to the 4G boot animation starting and then start back over but kick me back into recovery.
quixotiCfluX said:
right now neither, because I've just finished up re-rooting after RUU
I was picking reboot system, and it would go through the start of a boot cycle, but then die prior to the 4G boot animation starting and then start back over but kick me back into recovery.
Click to expand...
Click to collapse
Well hopefully that's an isolated incident and something just went goofy I would have tried to wipe everything and flash a fresh Rom but that's me, anyways your fixed now, newkidd has a one zip back to stock s-on file in the development section check it out its great to have in a pinch cause its a zip that runs from bootloader great for on the go unroot
Sent from my PG06100 using Tapatalk
strapped365 said:
Well hopefully that's an isolated incident and something just went goofy I would have tried to wipe everything and flash a fresh Rom but that's me, anyways your fixed now, newkidd has a one zip back to stock s-on file in the development section check it out its great to have in a pinch cause its a zip that runs from bootloader great for on the go unroot
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip, I'll have to go grab that just in case I get this kind of weirdness again
I recovered back to froyo from cm7 7.0.3 thinking I would give the gingerbread update a try. After seeing what bugs they had on gingerbread I went back fresh to cm7. I have cm7 7.0.3 on it no problem but when I try to put the newest nightly on it it does'nt do anything. It will download the nightly but when I tap it to install it say it will boot into recovery but dose'nt. I've tried it with 86,87 nightlys and it has done the same thing. Any help would be nice. Thanks.
Im guessing you are using ROM manager. If you are, dont. Just download the nightly zip from the thread on here for cm7, place on your sd card, reboot into recovery, nandroid, wipe cache and dalvik, and flash.
sitlet said:
Im guessing you are using ROM manager. If you are, dont. Just download the nightly zip from the thread on here for cm7, place on your sd card, reboot into recovery, nandroid, wipe cache and dalvik, and flash.
Click to expand...
Click to collapse
This. ROM manager, while convenient, is kind of a plague to us. This is because people learn to do all of their recovery based work through it and never learn how to work with the recovery (obvious by the fact that you haven't just booted into recovery and done it yourself, OP).
So do as this smart poster says.
Sent from my PC36100 using XDA App
SoraX64 said:
This. ROM manager, while convenient, is kind of a plague to us. This is because people learn to do all of their recovery based work through it and never learn how to work with the recovery (obvious by the fact that you haven't just booted into recovery and done it yourself, OP).
So do as this smart poster says.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have done that in the past. It's just much easier to do it through rom manager. Used it several times before with no problems.
dvrdwn said:
I have done that in the past. It's just much easier to do it through rom manager. Used it several times before with no problems.
Click to expand...
Click to collapse
Have you tried clearing the data and cache with ROM manager and trying again?
dvrdwn said:
I have done that in the past. It's just much easier to do it through rom manager. Used it several times before with no problems.
Click to expand...
Click to collapse
Well now you ARE having a problem. And it's really not that much easier. Again, download zip, reboot to recovery, nandroid, clear cache and dalvik, and flash. Literally takes maybe 10 seconds more than Rom manager.
So, I'm new to the world of tablets - the only interaction with them being some light use on my mom's tablet (including rooting it via Iconia Root and installing Acer Recovery Installer v2.54) I was curious about updating via ARI (since she's rooted and being plagued by OTA popups). Back when she first got the tablet, she tried to update and it would stop mid-download, giving no error, and just sit there until she cancelled it (this was before the root). So, basically, my question is: Is it possible to run a stock update (Ie "Stock 3.1 4.010.42_EMEA_GEN3") without having to wipe during install? I have a backup via ARI and also Titanium backup installed but I'd really like to not have to re-install all the apps/set up the homescreen (she's on stock) and stuff. I know on my OG droid that when I installed CM7 I had to do a wipe for it to even get past the boot screen but I figure with this being a stock update maybe it's different...
If not is there some way that I can install an update while keeping the root/system data?
AliceInUnderland said:
So, I'm new to the world of tablets - the only interaction with them being some light use on my mom's tablet (including rooting it via Iconia Root and installing Acer Recovery Installer v2.54) I was curious about updating via ARI (since she's rooted and being plagued by OTA popups). Back when she first got the tablet, she tried to update and it would stop mid-download, giving no error, and just sit there until she cancelled it (this was before the root). So, basically, my question is: Is it possible to run a stock update (Ie "Stock 3.1 4.010.42_EMEA_GEN3") without having to wipe during install? I have a backup via ARI and also Titanium backup installed but I'd really like to not have to re-install all the apps/set up the homescreen (she's on stock) and stuff. I know on my OG droid that when I installed CM7 I had to do a wipe for it to even get past the boot screen but I figure with this being a stock update maybe it's different...
If not is there some way that I can install an update while keeping the root/system data?
Click to expand...
Click to collapse
No. If you run the OTA, you WILL lose root. Not to mention I don't have a lot of faith in any device OTA updates. Prior experience, and hanging around various forums, well, you can read the horror stories.
I would advise, if you want to upgrade her OS and get rid of the "pesky" update notifications, is to flash one of the Stock rooted roms available. Or maybe a stripped down version of a Stock rom.
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
get and flash one of the honeylicious rom from the dev area .. good rom very basic apps.. but has a update to get the acer apps back.. and bunch of other cool mods.. the dev is also . kinda trustworthy..
Giggles.. ok he is kewl for a guy yukeeee guys smell..
good luck .. read read read read before you flash anything and of course back up and back up your backups .. then back them up again
cruise350 said:
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
Click to expand...
Click to collapse
Well... if the person was going to do an update to the exact same rom (different version) I would say ok.
But... if you are going to go to a totally different Rom, you NEED to wipe User Data.
Or, does anybody want to tell me you never have to?
3 Wipes. Mandatory when switching between roms, unless you are a dev and know exactly what you are doing.
Or.... you can forget about the safe side of things, and just flash away, and hope luck is with you.
The Market, SHOULD, allow you to re-download apps based on the market version you previously used. If not, it's a good time to clean house of the useless apps.
Moscow Desire said:
No. If you run the OTA, you WILL lose root. Not to mention I don't have a lot of faith in any device OTA updates. Prior experience, and hanging around various forums, well, you can read the horror stories.
I would advise, if you want to upgrade her OS and get rid of the "pesky" update notifications, is to flash one of the Stock rooted roms available. Or maybe a stripped down version of a Stock rom.
Click to expand...
Click to collapse
I wasn't talking about an OTA, I was talking about the stock 'rom' updates via recovery. I've had experiences with phones that have been rooted and accidentally updated via OTA, it's not fun. My phone was actually put into something I like to refer to as the Root limbo lol, bricked it for a small period of time - that was fun fixing it. I didn't have a nandroid at the time so I had to start from scratch...
cruise350 said:
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
Click to expand...
Click to collapse
So if I find a rooted version of stock OTA I can install it and only wipe Dalvik? I won't get stuck in a bootloop if I don't wipe data?
AliceInUnderland said:
So if I find a rooted version of stock OTA I can install it and only wipe Dalvik? I won't get stuck in a bootloop if I don't wipe data?
Click to expand...
Click to collapse
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------
erica_renee said:
get and flash one of the honeylicious rom from the dev area .. good rom very basic apps.. but has a update to get the acer apps back.. and bunch of other cool mods.. the dev is also . kinda trustworthy..
Giggles.. ok he is kewl for a guy yukeeee guys smell..
good luck .. read read read read before you flash anything and of course back up and back up your backups .. then back them up again
Click to expand...
Click to collapse
Hey I resemble....or is it resent that remark! lol
kjy2010 said:
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
I can't seem to find any pre-rooted stock Roms on the Developers forum. Links? I know I'm probably being a pain in the ass but I really don't want to get something by mistake and start with scratch on my mom's tablet - if it were mine I wouldn't care. lol
Click to expand...
Click to collapse
The link in the post above yours in this thread. Is a link to the rom scroll up one post
Giggles
AliceInUnderland said:
kjy2010 said:
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
I can't seem to find any pre-rooted stock Roms on the Developers forum. Links? I know I'm probably being a pain in the ass but I really don't want to get something by mistake and start with scratch on my mom's tablet - if it were mine I wouldn't care. lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
Oh my god you rock, thanks so much!
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Oh my god you rock, thanks so much!
Click to expand...
Click to collapse
Yw
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
Okay, this sent her into a bootloop so I had to nandroid. I wiped dalvik cache before installing this. Put it in the root of my SD card and installed via CWM in recovery. what am I doing wrong?
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Okay, this sent her into a bootloop so I had to nandroid. I wiped dalvik cache before installing this. Put it in the root of my SD card and installed via CWM in recovery. what am I doing wrong?
Click to expand...
Click to collapse
I've never heard of the A500 going into a bootloop simply from flashing one rooted stock ROM to another, but then again most people do all the necessary wipes when they do. Did you wipe dalvik and battery stats? That's about as minimal as you're going to get. If that doesn't work, you'll just have to flash the proper way. Instructions here complete with a video tutorial on how to flash by yours truly:
http://forum.xda-developers.com/showthread.php?t=1390860
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
I've never heard of the A500 going into a bootloop simply from flashing one rooted stock ROM to another, but then again most people do all the necessary wipes when they do. Did you wipe dalvik and battery stats? That's about as minimal as you're going to get. If that doesn't work, you'll just have to flash the proper way. Instructions here complete with a video tutorial on how to flash by yours truly:
http://forum.xda-developers.com/showthread.php?t=1390860
Click to expand...
Click to collapse
Nevermind, I fixed it XD I wiped dalvik and battery/partition and it worked fine lol.
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Nevermind, I fixed it XD I wiped dalvik and battery/partition and it worked fine lol.
Click to expand...
Click to collapse
Uh huh....you're welcome!
Click to expand...
Click to collapse
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Try adding "Factory reset" to that list and flash this one: http://forum.xda-developers.com/showthread.php?t=1563137
If it works fine, try another (prior wiping caches + factory reset...)
Raiden619 said:
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Click to expand...
Click to collapse
Make sure the kernel you using supports cm
Dasanko said:
Try adding "Factory reset" to that list and flash this one: http://forum.xda-developers.com/showthread.php?t=1563137
If it works fine, try another (prior wiping caches + factory reset...)
Click to expand...
Click to collapse
Alright downloading now, hopefully this will work.
Edit:
Didn't work for me, I never saw a boot logo/animation.
fanaticprakash said:
Make sure the kernel you using supports cm
Click to expand...
Click to collapse
What kernel do you recommend?
I actually have the same problem. This CM9 rom works, but its the only one that does. The others don't load for some reason. It almost always freezes in the bootanimation at some point. If it ever gets past the bootanimation it will freeze at "Verifiying apps"
I've been having the same problem for two weeks now, if anyone can solve this I would really appreciate it
Sent from my Kindle Fire using XDA
kwheel596 said:
I actually have the same problem. That unofficial CM9 rom works, but its the only one that does. The others don't load for some reason. It almost always freezes in the bootanimation at some point. If it ever gets past the bootanimation it will freeze at "Verifiying apps"
Click to expand...
Click to collapse
I actually had it load completely after verifying apps, but once I rebooted it always froze at the boot animation.
Raiden619 said:
Hey all,
Well title pretty much says it all, whenever I try install any CM9 based roms they always freeze while booting.
CM7 roms install and work fine but I would prefer to install a CM9 rom.
Am I missing something?
Does anyone have any thoughts on why this is happening?
I am wiping dalvik, cache and data.
Thanks
Click to expand...
Click to collapse
Have you checked the check sum of the downloaded ROM?
Sent from my Amazon Kindle Fire using Tapatalk
Wipe dalvik, cache, factory reset
Then go to mounts, format everything there except for your SD card (this is from memory just doing it once on the KF so don't wipe anything else that might be important).
THEN instill the rom.
erikikaz said:
Wipe dalvik, cache, factory reset
Then go to mounts, format everything there except for your SD card (this is from memory just doing it once on the KF so don't wipe anything else that might be important).
THEN instill the rom.
Click to expand...
Click to collapse
This doesn't work either :/
Sent from my PC36100 using xda premium
I have the same problem too, all the ics roms do not work except for the one stated in this thread previously and the Hellfire ics rom.
It gets stuck at the boot screen.. I have tried wiping everything including sdcard..
And also, my kindle hangs frequently when running 3d games and I have to hold the power button to force shutdown it..
Is it a problem with the kernel?
The notifications button at the bottom right corner is also very unresponsive, I have to press it several times to open the menu..
ammubarak said:
Have you checked the check sum of the downloaded ROM?
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
I second this. Redownload the file. This is only if you've formatted EVERYTHING as previously stated.
Just curious, what recovery are you guys using? If you're not on CWM I'd switch over and give it a go. Maybe you're getting improper wipes.
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
DJLamontagneIII said:
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
Click to expand...
Click to collapse
About 10 minutes or so, I even let it one time go for 30mins.
It still didn't work.
Raiden619 said:
About 10 minutes or so, I even let it one time go for 30mins.
It still didn't work.
Click to expand...
Click to collapse
man thats so strange... cwm or twrp? when you flash it dose it flash really fast
DJLamontagneIII said:
how long are you guys waiting till you say its freezing most roms while booting up for the first time the boot animation isnt long enough for the installation process and will stop but if you wait a few min it will boot right up... that first boot is when it builds its cache and davlik cache so it takes some time
Click to expand...
Click to collapse
Its not that I'm not waiting long enough for the boot animation or anything. For example it will load up some the first time and get all the way past the spinning circle on the CM9 boot animation and get stuck on the "verifying apps" screen. Other times that i try to boot it it will get stuck with just the little android and the circle around him, not even 2 full seconds into the boot animation.
The "Verifying apps" afaik should not be showing up on a fresh install. That only happens to me when I upgrade to a comparable rom I.e. one cm9 rom to another cm9 rom. Correct me if I'm wrong but what that sounds like is the os is choking on some left over apps.
Sent from my SPH-D700 using Tapatalk
sej11 said:
The "Verifying apps" afaik should not be showing up on a fresh install. That only happens to me when I upgrade to a comparable rom I.e. one cm9 rom to another cm9 rom. Correct me if I'm wrong but what that sounds like is the os is choking on some left over apps.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Nice first post!
All signs are pointing to a ****ty wipe. The recovery's fault, so long as you didn't forget to wipe everything under mounts.
erikikaz said:
I second this. Redownload the file. This is only if you've formatted EVERYTHING as previously stated.
Just curious, what recovery are you guys using? If you're not on CWM I'd switch over and give it a go. Maybe you're getting improper wipes.
Click to expand...
Click to collapse
i have switched over from twrp to cwm.. waited for at least 15 mins, but its still stuck at the bootscreen..
Pretty sure this would help alot of people, can someone try and solve this?
Sent from my Amazon Kindle Fire using xda premium
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.