Related
Hi all,
Sot of new to modding, think I screwed up and could use some help. Was doing this one click speed fix: forum.xda-developers.com/showpost.php?p=7587405&postcount=417
It didn't appear to work the first time, as I received a message and exited the application, however the symbol was still in the notification bar. Re-ran it, and it seemed to have worked, mostly, as the phone was blazing fast. Went immediately to run quadrant and check the benchmark, but it force closed every time it hit the i/o section. tried to go to market, foreclose every time. Figured it may need a reboot, powered off, and that's was all she wrote.
I can get into the battery charging screen and have been able to get to recovery, but nothing else. I haven't used adb or ODIN at all yet, but any assistance is greatly appreciated.
The phone was already rooted, and i have titanium back up and nandroid backups, but don't really know how to get to them.
If you did a nandroid backup, just go in recovery screen and restore backup. If not, flash back to stock rom.
well maybe i dont know what im talking about then. I guess I thought i did a nandroid.
When i go into recovery i get four options: reboot system now, reinstall packages, clear all user data, clear cache data.
none of them work
Did you install clock work recovery via Rom manager?
well it has turned on now. removed sim and memory card and hit reinstall packages. ive got the standard twlauncher running but, it repeatedly gives me force close notifications that android.process.media has stopped and i cannot access the menu
s15274n said:
Did you install clock work recovery via Rom manager?
Click to expand...
Click to collapse
yes, i did. i remember doing that precisely as shown in your tips and tricks thread
alright, so i got it into download mode, gonna reflash everything to stock and see where i went wrong as outlined here: http://forum.xda-developers.com/showthread.php?t=734475
Will update with results, but would be nice to figure out where i went wrong so as not to repeat the error.
If you can get into recovery just wipe and reflash eugenes vibrant4.zip.
Alright, back to stock. unrooted also? gonna mess some more and see if i can get my clockword recovery to restore everything.
okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Thats not all thats funny. i cant find the superuser app anywhere on here. also, i cannot install one from the market.
and im having issues with root explorer.
Civil Disobedient said:
okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Click to expand...
Click to collapse
DAKIDD236 said:
If you can get into recovery just wipe and reflash eugenes vibrant4.zip.
Click to expand...
Click to collapse
I would re-root and then follow the flash the ROM mentioned above. There is a thread in the DEV forum.
Civil Disobedient said:
okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Thats not all thats funny. i cant find the superuser app anywhere on here. also, i cannot install one from the market.
and im having issues with root explorer.
Click to expand...
Click to collapse
You need to root again to get the superuser on your phone. As for the one click lag fix, I used to original method and it went pretty well. No problems so far. I also flashed Vibrant4 by Eugene before doing the lag fix. Hope it helps
same thing happened to me. I'm stuck on the galaxy S boot screen. i can get into the samsung recovery screen but not the clockwork recovery. I backed up my nandroid and Rom but don't know how to get into the menu to restore. I only have the update.zip for the lag fix on the internal sd so can't restore that way. Any ideas? Much appreciated.
kwbdc said:
same thing happened to me. I'm stuck on the galaxy S boot screen. i can get into the samsung recovery screen but not the clockwork recovery. I backed up my nandroid and Rom but don't know how to get into the menu to restore. I only have the update.zip for the lag fix on the internal sd so can't restore that way. Any ideas? Much appreciated.
Click to expand...
Click to collapse
There may be other ways around it, but I restored fully to stock, then re-rooted. I'm back up and running no problem now. Had some issues with titanium backup but got around that and its batch restoring as i type.
Civil Disobedient said:
There may be other ways around it, but I restored fully to stock, then re-rooted. I'm back up and running no problem now. Had some issues with titanium backup but got around that and its batch restoring as i type.
Click to expand...
Click to collapse
Would you mind saying how you did that?
I tried wiping and flashing the stock via renaming it update.zip, and I'm still getting FC city. Mostly media, but, calendar, everything. I'm going to post a link to this in that thread, since many, it seems, were left hanging in a boot loop.
Janis said:
Would you mind saying how you did that?
I tried wiping and flashing the stock via renaming it update.zip, and I'm still getting FC city. Mostly media, but, calendar, everything. I'm going to post a link to this in that thread, since many, it seems, were left hanging in a boot loop.
Click to expand...
Click to collapse
Just follow what I did through the thread.
I did this http://forum.xda-developers.com/showthread.php?t=734475 to get back to complete stock, then i had to root it twice. Once did the one click, then the good root here http://forum.xda-developers.com/showpost.php?p=7150299&postcount=1
back up and running. had to research about titanium backup to get it up and running. I want to do the lag fix still, but im nervous from before.
Your nervous? I really would like to do this but i'm scared (cuss)less.
I've read what needs to be done and think that I've figured it out.
(pretty new to droid)... but, have also read the horror stories here
about bricking your phone...which nowadays can happen to any
phone you have....don't get me started on the apple pie!
But, really when it gets a simple as installing an .APK I'll be happy.
Damitu said:
Your nervous? I really would like to do this but i'm scared .......
Click to expand...
Click to collapse
The galaxy s seems pretty hard to brick. I'd say just go for the lag fix. Worse thing that happens is you have to take like 15min to download and use odin to reflash to stock. The lag fix seems pretty safe as long as you stay rooted
Sent from my SGH-T959 using XDA App
Vibrant Recovery Mode HowTo
THIS GUIDE WORKED ON USA T-MOBILE SAMSUNG VIBRANT BUT MAY VERY WELL WORK ON ALL SAMSUNG GALAXYS PHONES
After reading many XDA-Developers Forum Posts to try and figure out how to get into the Recovery Mode / Download Mode without any success, I gave T-Mobile Support a call.
After the usual noop run-down, "did you take the battery out" questions, I simply asked them how to get the Samsung Vibrant into recovery mode.
Unline the many tutorials that claim to require the Up or Down button pressed, along with the Home button then the Power, the true process is as follows:
1. Press the Up and the Down button at the same time (yes both). I too thought that button was a Toggle which only did either Up or Down, but found that in fact it does do both.
2. At the same time, press the power button.
3. As soon as the Samsung / Vibrant logo comes up on the screen, release the power button.
4. Release the Up and Down buttons.
5. PRESTO
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Android 17 said:
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Click to expand...
Click to collapse
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
mattykinsx said:
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
Click to expand...
Click to collapse
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Android 17 said:
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Click to expand...
Click to collapse
You could wipe /boot and /system as well and reflash and see if that fixes it.
mattykinsx said:
You could wipe /boot and /system as well and reflash and see if that fixes it.
Click to expand...
Click to collapse
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Android 17 said:
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Click to expand...
Click to collapse
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
mattykinsx said:
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
Click to expand...
Click to collapse
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Android 17 said:
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Click to expand...
Click to collapse
Sorry I took my Xanax to sleep or else I'd likely be able to think of some kind of solution.
Hopefully someone else can help you out.
I think in CWM if you mount System&Data /apps you could utilize adb pull..... Also did you set up any custom partitions, a2sd, data2ext, ect... ?
Sent from my HERO200 using XDA App
Actually thanks for the suggestions guys, I managed to dig up an older version of the rom saved on my downloads folder and flashed it and booted.
For some odd reason, an older release labeled as experimental works better than the 1.2 stable...
It's strange too because I looked around Deck's thread and no one else reported any problems similar to what I was having at all.
For all intents and purposes it appears to be very stable and functional for everyone BUT me
Thanks for the suggestions though. I guess I'll hold off on flashing any roms for a while or wait for a newer version and try flashing with a full wipe.
Cool glad you got her going.
Kaaameeehameeehaaaaaa!
I simply can't figure this out. I have an A500 that I have rooted successfully back a few months ago and installed HoneyVillain 1.04 ROM. It has worked flawlessly for months. Now I can't get root access with Titanium BU, BusyBox, Root Explorer or anything! I've tried re-rooting it using GingerBreak 1.2 with no success. I can access a backup that I made right after I rooted a few months ago, but that doesn't bring back root either. Can someone please tell me what to do before I make a 10.1" frisbee out of this thing. The tab's batery has been allowed to go completely dead once, but I don't think that would be the problem. I'd like to install the latest version of HoneyVillain if I can get root back. I sincerely appreciate anyone's help.
Sounds weird. You hadn't flashed anything else had you or installed a system update?
What's your kernel version & build number?
Have you tried using IconiaRoot?
Bubbamanlarry said:
I simply can't figure this out. I have an A500 that I have rooted successfully back a few months ago and installed HoneyVillain 1.04 ROM. It has worked flawlessly for months. Now I can't get root access with Titanium BU, BusyBox, Root Explorer or anything! I've tried re-rooting it using GingerBreak 1.2 with no success. I can access a backup that I made right after I rooted a few months ago, but that doesn't bring back root either. Can someone please tell me what to do before I make a 10.1" frisbee out of this thing. The tab's batery has been allowed to go completely dead once, but I don't think that would be the problem. I'd like to install the latest version of HoneyVillain if I can get root back. I sincerely appreciate anyone's help.
Click to expand...
Click to collapse
Did you by chance do a restore using cwm..? Every time I did a full restore I would loose root.
I haven't flashed anything and no system update. I'm about to try IconiaRoot 1.3. Still looking for the answer...I'll report back. Thanks!
I tried Iconia Root. It goes through the steps and says Done...Have Fun! Then a message says Iconia Root has been denied root privileges. I tried to unroot and it says something went wrong and I'm still rooted. I must be somewhere between rooted and unrooted! What now????
evangineer said:
What's your kernel version & build number?
Have you tried using IconiaRoot?
Click to expand...
Click to collapse
Kernel version is 2.6.36.4HoneyVillain-1.0+
Build number is HoneyVillain 1.04
Bubbamanlarry said:
I tried Iconia Root. It goes through the steps and says Done...Have Fun! Then a message says Iconia Root has been denied root privileges. I tried to unroot and it says something went wrong and I'm still rooted. I must be somewhere between rooted and unrooted! What now????
Click to expand...
Click to collapse
Don't use backup, reflash your rom and re root.
shaun298 said:
Don't use backup, reflash your rom and re root.
Click to expand...
Click to collapse
I'm giving that a go right now...
Bubbamanlarry said:
I'm giving that a go right now...
Click to expand...
Click to collapse
When that works I will give you the full story of what I found, if it works.
shaun298 said:
When that works I will give you the full story of what I found, if it works.
Click to expand...
Click to collapse
Well, you're right - it did work. I didn't even have to root again. Everything is back after the reflash of the ROM. Now tell me the full story. I'm wanting (I think) to try the latest HoneyVillain ROM.
By the way, thank you VERY much for you help.
Bubbamanlarry said:
Well, you're right - it did work. I didn't even have to root again. Everything is back after the reflash of the ROM. Now tell me the full story. I'm wanting (I think) to try the latest HoneyVillain ROM.
By the way, thank you VERY much for you help.
Click to expand...
Click to collapse
You must not have wiped anything...? (Not that that is bad just more tech info for me), still learning.
Anyway, I have used honey vill and taboonay many version and with different kernals and love both roms.
What happans to me is I use cwm after I get the tab set the way I want and then do a full backup using cwm. Then I always want to fire test my backups so I immediately do a full restore using cwm, soon after I start getting denials from super user..? And after checking using a app from the market to check root, I have now lost root and can't get back, same as you.
I now just reflash the rom and if I do full wipe I reroot and all is well.
So I went with a different rom, backup and immediately do full restore and now no root again.
It happaned with every rom I have tried. Someone told me to delete the android.secure.image folder from the backup set that cwm makes. I tried that and that did let the restore, restore the flex rom folder but had the same problem. I have two a500 and both do this. I don' t know if stock rooted will do this as I have not tried yet. So what good is a full backup if it fudges your system. Maybe someone has a answer, but I have not found one. Sorry if this ain't your problem at all, but might be related. Later
shaun298 said:
You must not have wiped anything...? (Not that that is bad just more tech info for me), still learning.
Anyway, I have used honey vill and taboonay many version and with different kernals and love both roms.
What happans to me is I use cwm after I get the tab set the way I want and then do a full backup using cwm. Then I always want to fire test my backups so I immediately do a full restore using cwm, soon after I start getting denials from super user..? And after checking using a app from the market to check root, I have now lost root and can't get back, same as you.
I now just reflash the rom and if I do full wipe I reroot and all is well.
So I went with a different rom, backup and immediately do full restore and now no root again.
It happaned with every rom I have tried. Someone told me to delete the android.secure.image folder from the backup set that cwm makes. I tried that and that did let the restore, restore the flex rom folder but had the same problem. I have two a500 and both do this. I don' t know if stock rooted will do this as I have not tried yet. So what good is a full backup if it fudges your system. Maybe someone has a answer, but I have not found one. Sorry if this ain't your problem at all, but might be related. Later
Click to expand...
Click to collapse
That's amazing. I want to move up to the new HoneyVillain, so I guess I can count on rooting again? Wow. I love my Iconia though. I just remembered that I recently had trouble with WIFI so I DID do a restore via CWM. I guess I just realized that things weren't rooted! Oh well, you have provided some much needed info for me. At least now, I will know what to expect. Thanks again. Have a blessed evening.
I also had the wifi problem, and that is what started the whole thing with the full restore. Have a good one.
The same thing happened to me. I just installed another ROM to fix it.
Kinda ridiculous though. At least we know how to deal with it.
Thanks for this thread -- confirmed my sanity when I lost root after a CWM restore. Does anyone know if the updated version (1.6) of CWM for the A500 fixed this problem?
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Jersey846 said:
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Click to expand...
Click to collapse
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
jco23 said:
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
Click to expand...
Click to collapse
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Jersey846 said:
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Click to expand...
Click to collapse
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
jco23 said:
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
Click to expand...
Click to collapse
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Jersey846 said:
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Click to expand...
Click to collapse
You never mentioned using TWRP 2.4. DEFINITELY replace that. Also, just a thought. If you haven't already done so, try using the option to fix permissions. I'm fairly sure its an option in TWRP.
Sent from my XT907 using xda premium
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
jco23 said:
- I use TWRP 2.3.2.3 (SS has been uninstalled via it's own app, not Tibu or the system awhile ago) - but TWRP 2.5 works just fine for others
- after downloading the ROM and GApps (or any file that I intended to flash for that matter), I always place the file on the mnt/external1 directory. I
m not sure if this will make a difference, but I recall it being an issue back on my Droid Charge days
- after flashing the files, does TWRP say successful?
- perhaps you do need to a double wipe of everything prior to flashing:
1) mount everything
2) wipe cache
3) wipe dalvik cache
4) wipe system
5) factory reset/wipe data
6) wipe internal storage (if you do this, make sure to change your TiBu backup folder to your external1 directory, or this will be gone too!!!!! also make sure that the system backup you made is on the external1 directory as well
7) reboot recovery
8) install ROM
9) install GApps
Click to expand...
Click to collapse
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Good for you bro! That stinking TWRP 2.4.0 is such a menace! Wish there was a way to have it yanked from circulation. Glad you're up and running!
Sent from my Droid Razr M using xda premium
Jersey846 said:
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Click to expand...
Click to collapse
glad you finally got it working - this is just the first step in becoming a crack-flasher....
jco23 said:
glad you finally got it working - this is just the first step in becoming a crack-flasher....
Click to expand...
Click to collapse
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
netizenmt said:
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
funny, and the goal is to find a ROM that you're happy with and don't need to flash.
but I've been on Carbon since 7/5, and very happy.
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.