Database Users

Bricked Vibrant, Assistance greatly appreciated

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

0.00 internal memory, not Voodoo related

So I tried installing the new ASOP rom, and was getting a bunch of force closes. I tried using CWM to revert to a previous backup, unfortunately the force closes continued in the backup. So I want into ODIN to get back to stock. I loading the stock files, did a factory reset, and everything seemed to be fine. However when I went into the market to reinstall appbrain and get my programs back, I kept getting an Out of Space error. I checked the internal memory and sure enough it says 0.00.
I've never installed Voodoo on my phone, because I was trying to avoid issues just like this one. I read over the a similar thread on this issue, but that fix isn't working for me. I tried to reroot, but the SU apk's don't have any place to go, since the phone says there is 0 internal memory.
Luckily I can still use my phone, but every time it turns off it resets, and I can't load my apps back on. Anyone got any suggestions?

The fix should still work for you. I would suggest flashing stock rom, kernel, pit, and cwmrecovery thru odin. After that you can follow the instructions posted on how to completely remove voodoo. Main thing is you need to get the original mbr to your phone.

Well he said he never installed voodoo so he shouldn't have to go through the steps to remove something he never installed in the first place
Sent from my SCH-I500 using XDA App

ckochinsky125 said:
Well he said he never installed voodoo so he shouldn't have to go through the steps to remove something he never installed in the first place
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hmm I read that part too, but if he follows adrynalyne instructions he should be fine. It is taking care of the same problem. Corrupted rfs. The op just achieved it in a different way. If that does not work for him then maybe some dev will be able to figure out another way to fix the problem.

I'd be curious to see mount results.
Run it from adb shell.

So the short story is I fixed my phone, from force close and zero memory hell.
I noticed when booting into recovery I was getting an error related to /dev/block/mmcblk0. I used the adb code to install the MBR file. Went in CWM and flashed the stock.zip kernel, restarted and got a ton of force closes. Went to the "How to escape the force close loop of hell" thread over at androidcentral, flashed the stock nandroid image, and someway, somehow the android gods took pity on my poor soul and my internal memory partition was restored.
I don't understand exactly how I fixed my phone, and I'm relatively new to this so I'm a little concerned. I'd like to learn from these mistakes, so does anyone understand what I did to fix my phone?

Sounds like it was the nandroid image that did it.
It is, effectively, the same issue the voodoo users have seen.
My "easy" fix was almost exactly the same as yours.
replace mbr, flash stock, revert to backup (which is basically what nandroid is).
I used my original CWM backup instead, and that worked for me. (I now have this stored on several drives/devices)
I also went back in to Root Explorer and nuked the "databases" folder in /dbdata and then wiped cache/data (CWM, then "settings"). Pretty much fixed it all for me.
Couldn't update to D101 for some reason after that, but the unsigned apk for that did the trick nicely. I suppose I'll have to retry the "odin to stock" bit if the 2.2 update fails the same way on me. Not looking forward to that one...

Phone Totall Messed Up

Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.

Jeff5886 said:
Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Click to expand...
Click to collapse
Jeff,
See this post for returning to stock http://forum.xda-developers.com/showthread.php?t=782204. I would do this as a last resort only.
Good Luck!

that is what got me to this problem. there are multiple files there what one do i use?

You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?

I was having the same issues with USB cable looking like it was plugged in so I couldn't reboot unless it was plugged. I tried the voodoo uninstall and screwed up my data partition.
I ended up restoring the CWM_Kernel and Di01 Stock update which brought me back to stock with root and OTA update from Verizon BUT my Data partition is screwed and I have no internal app memory. Also, I have an Nandroid backup that I tried to install but that causes the FC issues that you mentioned. My guess is that my nandroid backup will work once I fix the data partition.
Later tonight, I'm going to try to put the stock MBR back onto the phone which I think you need to do as well.
However, it sounds like you didn't complete the whole recovery process and only applied one file. I'm an android newby so you can't take my advice to the bank but I think you need to restore all the files if you're going to flash with Odin per those instructions.
For me, I had CWM loaded so I just wiped the kernel and put back the DI01 ROM which put me back to stock albeit with some work to do to get my data partition back in shape. I hope this helped, for what it's worth.

Since you've already got the original.mbr copied and the stock.zip flashed...
Boot into CWM recovery and wide data/cache.
If you have a CWM backup of your phone in a rooted state, restore that backup through CWM.
Reboot, and go into "settings" if possible at this point, and factory reset.
This got me back from market failure/0.00/fc hell after utterly failing to heed the voodoo warnings and trying to revert to stock without undoing the lagfix.
You'll likely need to use the unsigned d101 apk if your backup/flash is dh12. The OTA update did not work for me at that point.

phispher said:
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
Click to expand...
Click to collapse
My question is do i use the phone. pda or csc buttons for these files?

Ok in Odin use the PDA button for the /system
but what button do i use in odden to load the kernal.tar and recovery.tar
i loaded the pit, and installed all the files using the pda button one after the other. now my phone get no service and it still isnt wiped. what is going on? how do i get the phone back to out of the box condition.
also, now i cant do a factory wipe/reset, im getting the error message Can't mount /dev/block/mmcblk0p1

Gotta do the mbr fix from the 0.00 internal memory topic and then restore nandroid recovery.
Oh, and it is PDA for all three files, not just system.
Sent from my SCH-I500 using XDA App

i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??

trapstarr56 said:
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
Click to expand...
Click to collapse
Use the uninstaller form Here:
http://forum.xda-developers.com/showthread.php?t=804784
If that does not solve it, follow the steps here:
http://forum.xda-developers.com/showthread.php?t=782204
Read all pages of each topic completely prior to initiating *either* of them.

[Q] Root Noob needs help!

because i have no shame, i'll admit it. this is my second root ever. first was on my droid 2 r2d2 to remove the crap that wasnt necessary.
using this tutorial, just google samsung continuum froyo, and its on addictive tips. I followed the directions properly.
Basically, I used odin3 with a custom froyo rom, i did everything correctly, and i began to use titanium backup to remove some bloatware. what i removed was the GO Launcher stuff and now my homescreen is just a black screen. I've tried using recovery mode and restored that way. i've done that 10+ times. i cant get to any apps, only pressing the bottom ticker to access my text messages and notifications slide down bar. thats it. no apps. at all. can someone tell me how to revert back to the original software? then i will re-root again and this time NOT remove anything. or someone can show me properly how to remove it.
thanks. itll help a lot!

Go launcher (in most roms for the continuum) the ONLY launcher installed so when you got rid of it with TiB you screwed the whole UI. Try booting into Recovery wipe data fact reset wipe cache. then reboot. pull battery reflash on odin, make sure repartition is unchecked. let it reboot. should be back to normal.

can you explain that in a different way. i tried wiping in recovery mode it didnt work

Are you using <2e> recovery (samsung stock) or CwM?

You removed the launcher, this is why. You probably deleted a file called TouchWiz30Launcher.apk
You have a few options now, do you have CWM installed? If so go download another rom, put it on your sdcard some how then install it. It will save you much time and you don’t have to remove the bloat as it’s already removed.
If you aren’t familiar with CWM(clock work recovery) I would suggest researching it s you will be dealing a lot with it.
I would recommend reflashing via odin so that you have all files again. If you want to get rid of bloat, install nuckin or eco07-clean they both are good basic roms. I am currently working on a rom which is called miunia it is as minimalistic as I can make it. It is still in beta forms but it can be installed through odin. If you want the launcher I suggest flashing one of mine for the time being..
Thttp://dl.dropbox.com/u/11160512/launcher.zip
Thread link
http://forum.xda-developers.com/showthread.php?t=1311414

pattielipp said:
You removed the launcher, this is why. You probably deleted a file called TouchWiz30Launcher.apk
You have a few options now, do you have CWM installed?
Click to expand...
Click to collapse
yea i have clockwork mod, and i did remove that. i dont know what to do honestly im rerooting to see if that will work.

thanks everyone, i think i fixed it. never thought to reroot it, i really appreciate it, xda is a great place to go for help and to learn.

coreybrah said:
thanks everyone, i think i fixed it. never thought to reroot it, i really appreciate it, xda is a great place to go for help and to learn.
Click to expand...
Click to collapse
if you deleted the actual file, just rebooting the phone won't fix the issue. you will have to replace the launcher or factory reset.

For future reference, another option is to get on android market from your computer and download a launcher. It will send it to your phone and install automatically. Then, when you hit the home button, it should run the launcher.
sent from my gutted and modded continuum, courtesy of adrynalyne, imnuts, and trailblazer

Uh oh... Can I fix this? Rom Toolbox Pro error

Hey guys,
I tried using Rom Toolbox Pro to change my battery icon... after trying to install, the error "com.android.systemui has stopped working" continually popped up. I had to reboot by holding vol+, vol- and lock.
After rebooting, all soft buttons and the status bar are gone. I can't manage to get them back. I also can't manage to restore the battery icon - RTP prompted me to backup the icons before trying to install the new ones, and I did.
What have I done?

You've borked the system UI. Need to flash a new ROM or flash a factory image, I think.
Sent from my Nexus 7 using xda app-developers app

duloz said:
You've borked the system UI. Need to flash a new ROM or flash a factory image, I think.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow, that's so bull**** haha. Thanks for the quick reply

bulldozed said:
Wow, that's so bull**** haha. Thanks for the quick reply
Click to expand...
Click to collapse
So I went to restore my backup through CMW, it failed. Now I'm stuck on the Google screen. How do I flash it back to stock, in order to start all over again? I can get to the CMW page with the Android on his back, with "Start" up the top.
Appreciate any help!

bulldozed said:
So I went to restore my backup through CMW, it failed. Now I'm stuck on the Google screen. How do I flash it back to stock, in order to start all over again? I can get to the CMW page with the Android on his back, with "Start" up the top.
Appreciate any help!
Click to expand...
Click to collapse
That's not the clock work recovery. It's the bootloader. That's where you need to be to flash the image though.
First download the Nexus 7 image from https://developers.google.com/android/nexus/images#nakasijro03d
Once you have downloaded it extract the file twice until you see image-nakasi-jro03d.zip
Take that zip and move it to the directory where you have fastboot on your computer.
Open your command prompt pointing at that directory.
Then, type:
Code:
fastboot devices
if it returns a number you are good to go.
Next type:
Code:
fastboot -w update image-nakasi-jro03d.zip
This will wipe your user data and restore stock recovery. But you should be good to go.

geez, just reflash your rom, youll be ok.

El Daddy said:
snip
Click to expand...
Click to collapse
absolute legend. Thanks for the detailed reply, really appreciate it! I will give that a shot right now.
EDIT: haha took me five minutes to get it reflashed to stock. thanks again!
simms22 said:
geez, just reflash your rom, youll be ok.
Click to expand...
Click to collapse
haha sorry if my posts were a bit over the top, I was just sitting in bed having a play (with my Nexus 7........), then all of a sudden my tablet is seemingly wrecked simply from trying to change the battery icon... I FREAKED

Did something similar myself.
Just downloaded the factory image and flashed just the system.img file using fastboot and rerooted. A few system apps played up, most were fixed by wiping the cache but i had to delete all data from the contacts app, it resynced fine anyway.
To clarify extract the factory image to get the system.img and use the following
fastboot flash system system.img
Just rewrites the system partition.
Sent from my Nexus 7 using Tapatalk 2

The same thing happened to me trying to change the wifi icon. I guess Rom Toolbox doesn't play well with the Nexus 7?

Same thing on Galaxy Nexus... stumbled upon this thread searching for a solution. Was thinking we could restore from the backup that was made when swapping icons, but I guess that's not the case?

bulldozed said:
Hey guys,
I tried using Rom Toolbox Pro to change my battery icon... after trying to install, the error "com.android.systemui has stopped working" continually popped up. I had to reboot by holding vol+, vol- and lock.
After rebooting, all soft buttons and the status bar are gone. I can't manage to get them back. I also can't manage to restore the battery icon - RTP prompted me to backup the icons before trying to install the new ones, and I did.
What have I done?
Click to expand...
Click to collapse
Hello friends,
I am curious why, when such issues occured with your device, you did not contact Rom Toolbox Dev. to ask for help?
I am part of the support team from Rom Toolbox Pro, and I believe the post right before me is from someone who reached out to me to ask me about this, so allow me to explain the solution here real fast:
What happened is that when you changed the icon, it simply didn't work and messed up the UI. This occurs sometimes, and is the right time to restore a backup of the icons.
Problem is that now you can't restore, because the soft keys are all gone, and the Nexus 7 has no hard keys to do the dirty work.
So, here is the solution; you must use Root Browser to switch out the Systemui.apk and framework.apk files from the backup folder to the /system/app folder.
Where is the backup stored, you ask? Well, since it's very easy to break a rom by restoring the framework and systemui to the wrong rom, the backups are actually placed inside the app's data partition. This is to prevent tampering. If you are reading this post, then I assume you know what you're doing and are doing this with the EXACT same rom as the backups were created from.
The directory of the backups is /data/data/com.jrummy.liberty.toolboxpro/files/status_bar_backup/
Simply copy these over and paste them in /system/app, maybe renaming rather than deleting the old ones, just in case, then paste these and reboot your device.
And now your systemui and framework should be all restored.
Hope this helps! Be sure to contact the developer next time you need any help, We have arguably the best customer service of all the Play Store
And be sure to thank the one who referred me to this thread, if this helps!

Master Ramy said:
Hello friends,
I am curious why, when such issues occured with your device, you did not contact Rom Toolbox Dev. to ask for help?
I am part of the support team from Rom Toolbox Pro, and I believe the post right before me is from someone who reached out to me to ask me about this, so allow me to explain the solution here real fast:
What happened is that when you changed the icon, it simply didn't work and messed up the UI. This occurs sometimes, and is the right time to restore a backup of the icons.
Problem is that now you can't restore, because the soft keys are all gone, and the Nexus 7 has no hard keys to do the dirty work.
So, here is the solution; you must use Root Browser to switch out the Systemui.apk and framework.apk files from the backup folder to the /system/app folder.
Where is the backup stored, you ask? Well, since it's very easy to break a rom by restoring the framework and systemui to the wrong rom, the backups are actually placed inside the app's data partition. This is to prevent tampering. If you are reading this post, then I assume you know what you're doing and are doing this with the EXACT same rom as the backups were created from.
The directory of the backups is /data/data/com.jrummy.liberty.toolboxpro/files/status_bar_backup/
Simply copy these over and paste them in /system/app, maybe renaming rather than deleting the old ones, just in case, then paste these and reboot your device.
And now your systemui and framework should be all restored.
Hope this helps! Be sure to contact the developer next time you need any help, We have arguably the best customer service of all the Play Store
And be sure to thank the one who referred me to this thread, if this helps!
Click to expand...
Click to collapse
Hi Master Ramy,
I was the one who emailed JRummy.
I'm not sure I understand what you're saying actually. I guess your reply answers the OP's question - that is, in the event that we get the "com.android.systemui has stopped working" error , then we should do the stuff you said?
My issue is different... I hadn't swapped out my battery icons yet, cos I wanted to test the restore function in ROM Toolbox first before doing so. So I backed up both systemui and framework-res using ROM Toolbox, then simply tried to restore them using ROM Toolbox. But I got a toast notification saying "failed to get icons". I didn't get a big error like the OP's, but it was alarming enough that I didn't even try to change the icons in the end.
Are you saying that I should manually move my systemui and framework-res backups to system/app in order for ROM Toolbox to be able to restore them?

mlj11 said:
Hi Master Ramy,
I was the one who emailed JRummy.
I'm not sure I understand what you're saying actually. I guess your reply answers the OP's question - that is, in the event that we get the "com.android.systemui has stopped working" error , then we should do the stuff you said?
My issue is different... I hadn't swapped out my battery icons yet, cos I wanted to test the restore function in ROM Toolbox first before doing so. So I backed up both systemui and framework-res using ROM Toolbox, then simply tried to restore them using ROM Toolbox. But I got a toast notification saying "failed to get icons". I didn't get a big error like the OP's, but it was alarming enough that I didn't even try to change the icons in the end.
Are you saying that I should manually move my systemui and framework-res backups to system/app in order for ROM Toolbox to be able to restore them?
Click to expand...
Click to collapse
Yes, the post was in response to the OP talking about losing the soft keys and such Due to the different nature of your issue, I've sent you an email instead of responding here, so that we don't clog up this thread