Database Users

[Q] Another JI6 Flop...

Ok, so I tried flashing the JI6 update and guess what... stuck at the Vibrant boot screen. I'm able to get into recovery and tried to restore an old nandroid backup to no avail.
The only thing that I have done to the phone is root and the GPS fix (in the Tips& Tricks Thread).
Any ideas on how to get a workable phone again?

How long did you let it sit at the Vibrant screen for? I remember mine taking a while. Maybe let it sit for 10 mins or so. If that doesn't work, an Odin flash should solve your issue.
Good luck.

Voodoo Disable/Enable then battery dies.

Ok, so here is the story.
I just cleared my battstats.bin with Voodoo off ran the battery down till it powered off, enabled Voodoo again before the battery went dead. When I plugged the phone in Voodoo started and completed the conversion while the phone was off and plugged in. Now that it is charged I can not get the phone to make it past the boot screen at all. I have attempted to just restore a CWM backup I had made but the MD5 is bad, when I restore one from a week earlier the phone just shuts itself off before even attempting to boot.
Not sure if this is a bug or a "feature" or if it has even been documented before.
So I guess what I am getting to the point of asking is what should I try next before I totally wipe the phone and start fresh?
****EDIT****
With the stock kernel I eventually get to a point where the screen is black and the softkey lights are on solid.

Hey there. I would try an odin flash at this point to get your phone back to stock and then you can go from there. Following the instructions on this post should help you. http://forum.xda-developers.com/showthread.php?t=782204
Good luck with everything.

Well I am in the process of trying from these posts to see if I can get things to at least make a phone call.
http://forum.xda-developers.com/showthread.php?t=804784
http://forum.xda-developers.com/showthread.php?t=782204
****EDIT****
Tried just the ODIN and still nothing.
****EDIT2***
JEEBUS H that was close. I think I might have learned my lesson. I had to ODIN restore everything including the recovery and then do yet another wipe to get things to boot up.
Think that maybe the Voodoo developers should know about enabling Voodoo and letting the battery drain then plugging it in, usually I wouldn't have done that at all but I was trying to calibrate the battery.

Sweet. Glad you got it working

[Q] Help

tried to install custom rom, didn't work out. tried to do a restore the phone gets to a point where it stops and says "lost+found" and won't go any further. any suggestions?
Thanks
Also when i try to reboot in recovery i get this "E:can't open/cache/recovery/log" and stops right there. Any ideas??

Odin is your friend look it up!!
Sent from my SPH-D700 using XDA App

Have odin and still can't get past the places on my previous post. Every time i try to reboot i get the "clockworkMod Recovery v2.5.1.0"
"E:can't open /cache/recovery/log"
just like that half way down the screen. won't go any further. need some serious help.

you shouldnt be using recovery mode, you need to be in download mode. power off your device then hold 1 and power on again. you should get a little android with a shovel. thats the mode your phone needs to be on in order to odin it back

Skrewup5 said:
you shouldnt be using recovery mode, you need to be in download mode. power off your device then hold 1 and power on again. you should get a little android with a shovel. thats the mode your phone needs to be on in order to odin it back
Click to expand...
Click to collapse
At this point the only way i can power it down is to remove the battery and even when i hold 1 and power back up it goes into clockwork recovery mode instead of download mode.

thats incredibly strange. ive had the same problem as you before when i installed a bunk rom but it didnt affect download mode. see if you can flash over stock dk28, after factory resetting 3 times, wiping cache and then dalvik. i think the reason its stuck on the samsung screen is because the last rom you installed is conflicting with something. but if you can get another to work, it may hopefully at least allow you to enter recovery so you can odin.
i may just be talking out my ass here, but its def a software issue, as opposed to hardware.
or it may even be a kernel conflict, make sure the one youre using is compatible with the rom

Skrewup5 said:
thats incredibly strange. ive had the same problem as you before when i installed a bunk rom but it didnt affect download mode. see if you can flash over stock dk28, after factory resetting 3 times, wiping cache and then dalvik. i think the reason its stuck on the samsung screen is because the last rom you installed is conflicting with something. but if you can get another to work, it may hopefully at least allow you to enter recovery so you can odin.
i may just be talking out my ass here, but its def a software issue, as opposed to hardware.
or it may even be a kernel conflict, make sure the one youre using is compatible with the rom
Click to expand...
Click to collapse
A friend at work, who has an EVO wanted to work on my phone while I was out of the office on business. He was able to finally get it to enter download mode, flashed odin and froyo DK28 and got me back up. Just a temporary glich that took several tries for some reason. Anyway I'm back on 2.2.1 and looking forward to rooting again but probably going to download a different rom. Thanks for help and advise. also good to have phone savy friends at work. Thanks Ashley.
Dana

Im glad it was all resolved haha. try the new bonsai4all 2.0. its very easy to install

[Q] How to remove One Click Root...with a twist...

Ok, so before I get flamed, let me say that I did do a search and did see that there are ways to unroot the phone...however, I have what I believe to be a bit of a different case here and am just looking for info before trying any of them.
Background...(this is for a friends phone, not mine, or I would just Odin and call it good. He however does not want to loose any of his settings blah blah blah so doesnt want to go that route unless necessary)...Buddy got his first Epic and had me root it for him (One Click Root 2.5.1), that phone took a **** and had to be replaced. When he took it to Bestbuy (I think there, could be the sprint store, dont know that it matters) they hooked it up to their little file transfer machine, let it do its thing and gave him his new phone. Now, after doing that, it still shows as having Clockwork Mod installed, and you can boot into CWM, but none of the functions work, which I found out when I tried to install EC05 on his phone. I installed the zip to his sd card, rebooted into CWM and selected to install zip from sd...nothing happened...just went to a blank screen and locked up and I had to pull the battery. Rebooted the phone and it went straight to CWM without the three finger grip, I selected to just reboot the phone, lock up and battery pull required. Long story short (I know, too late for that) I tried several options and all of them resulted in a lock up and wouldn't let the phone boot normally...I was really feeling bad thinking that I had actually managed to brick his phone...last thing I tried was the advanced menu and selected to reboot recovery and luckily, that actually worked and booted me into sammys stock recovery mode and I was able to run the zip. Had to reboot several times, but it took and his phone is running well now on EC05.
So now to my question. Since CWM is obviously corrupted on his phone from that transfer and not being properly installed on this phone (I was actually blown away that it transfered in the first place) in order to correct that, do I just apply the newer CWM like its a stock phone and let it try to write over those corrupted/missing files or do I need to try to uninstall what is there first or is he going to be stuck having to Odin and take whatever losses he gets?

Thats actuarry an interesting diremma...
Does the phone show up in adb? Can you SU
Sent from my SPH-D700 using XDA Premium App

If you are rooted still, run MyBackup Root for him and then run Odin. If you're not, run the One Click Root 2.5.5 and then use MyBackup Root.

No, its not still rooted, just showing CWM. Thanks, I will try running 2.5.5 over it. I just wasnt sure if that would cause any problems...will let you know how it goes.

I've had a similar thing happen to me when updating a kernel. Reinstalling the same CWM right over the top worked for me.

I thought mine just died on me, help in need of answers

Please someone help me or tell me who I can PM to help please.
Yesterday my razR M was just randomly rebooting, it stop doing this after about 5 reboots. I then proceeded to fully charge my phone twice to do the radiocomm edit and root, using DROID RAZR M Utility 1.20 since i'm on 4.1.2 *I did not factory reset*, the phone so that the battery wouldn't die while doing either and mess up the phone. I was trying to do the entitlement edit with all free file managers with root permissions which didn't work and I realized my phone was freezing while doing simple tasks (during boot animation, inputting password to unlock phone, switching between homescreens and opening app drawer) and rebooting.
It wasn't turning on or showing any indication of being plugged in, but while I was writing this it just magically went to the battery percentage indicator and I was able to turn it on and after about 20 seconds of being booted the led indicator is flashing green again.
I can't have this happen next week when I'm on my trip, I won't have the time and my access to computers and internet will be limited. If anyone knows what could be causing this and or how to fix it PLEASE TELL ME
Update (3:25 AM): IT HAPPENED AGAIN, ready to cry want to try to flash back to stock but don't know how
Update #2 (4:13AM): So after a lot of button pressing I got it stuck on the red m then eventually into the bootloader; saw that the random reboots is not unusual for razr hd/maxx hd users on 4.1.2 with the only way to fix being to flash to CM10. Also realized that i'm not the only one whose phone requires a soft reset to charge/boot, no longer contemplating flashing back to stock seeing as i'll probably still have the reboots

ccdsatt said:
Please someone help me or tell me who I can PM to help please.
Yesterday my razR M was just randomly rebooting, it stop doing this after about 5 reboots. I then proceeded to fully charge my phone twice to do the radiocomm edit and root, using DROID RAZR M Utility 1.20 since i'm on 4.1.2 *I did not factory reset*, the phone so that the battery wouldn't die while doing either and mess up the phone. I was trying to do the entitlement edit with all free file managers with root permissions which didn't work and I realized my phone was freezing while doing simple tasks (during boot animation, inputting password to unlock phone, switching between homescreens and opening app drawer) and rebooting.
It wasn't turning on or showing any indication of being plugged in, but while I was writing this it just magically went to the battery percentage indicator and I was able to turn it on and after about 20 seconds of being booted the led indicator is flashing green again.
I can't have this happen next week when I'm on my trip, I won't have the time and my access to computers and internet will be limited. If anyone knows what could be causing this and or how to fix it PLEASE TELL ME
Update (3:25 AM): IT HAPPENED AGAIN, ready to cry want to try to flash back to stock but don't know how
Update #2 (4:13AM): So after a lot of button pressing I got it stuck on the red m then eventually into the bootloader; saw that the random reboots is not unusual for razr hd/maxx hd users on 4.1.2 with the only way to fix being to flash to CM10. Also realized that i'm not the only one whose phone requires a soft reset to charge/boot, no longer contemplating flashing back to stock seeing as i'll probably still have the reboots
Click to expand...
Click to collapse
not sure if your situation has been resolved, but it appears that the battery just drained all the down. from that point, you need to plug in your phone (into an outlet, not computer), and leave it alone for a good 30 minutes (don't even look at it).
from that point, you should be able to enter the Rom by powering up or recovery via volume up + volume down + power.
if you are still having troubles, you might be best to simply perform a hard reset (I think you can do that from the stock recovery menu).
after you are able to do that, I would suggest to root, unlock bootloader, install TWRP. then setup your phone settings to your liking, then go back into recovery and make a backup. i have soft-bricked my phone several times, and entering TWRP recovery and restoring my previous setup has helped every time.

Its OK now
jco23 said:
not sure if your situation has been resolved, but it appears that the battery just drained all the down. from that point, you need to plug in your phone (into an outlet, not computer), and leave it alone for a good 30 minutes (don't even look at it).
from that point, you should be able to enter the Rom by powering up or recovery via volume up + volume down + power.
if you are still having troubles, you might be best to simply perform a hard reset (I think you can do that from the stock recovery menu).
after you are able to do that, I would suggest to root, unlock bootloader, install TWRP. then setup your phone settings to your liking, then go back into recovery and make a backup. i have soft-bricked my phone several times, and entering TWRP recovery and restoring my previous setup has helped every time.
Click to expand...
Click to collapse
My phone was always 100% percent charged as I wanted to do stuff with the utility. After getting it into safemode, where it still froze and rebooted twice each time I booted into the mode, I got to power off then turn off then back on the regular way and left it on and has been fine since then. I currently have safestrap and cm10 zip on the phone in the event it acts up again. I backed up using safestrap like suggested. I haven't unlocked the bootloader yet, I have the app installed though, as I saw something from one of the devs for my previous moto device that said that if your bootloader is unlocked and we get another OTA and install* it our phones could get messed up.
*I know I can just install a stock 4.2 ROM*

ccdsatt said:
My phone was always 100% percent charged as I wanted to do stuff with the utility. After getting it into safemode, where it still froze and rebooted twice each time I booted into the mode, I got to power off then turn off then back on the regular way and left it on and has been fine since then. I currently have safestrap and cm10 zip on the phone in the event it acts up again. I backed up using safestrap like suggested. I haven't unlocked the bootloader yet, I have the app installed though, as I saw something from one of the devs for my previous moto device that said that if your bootloader is unlocked and we get another OTA and install* it our phones could get messed up.
*I know I can just install a stock 4.2 ROM*
Click to expand...
Click to collapse
well, most folks are going via the TWRP recovery route now (and I believe that all custom ROMs going forward will be flashable this way only, and not SS).
you will find that using TWRP is much easier than SS

jco23 said:
well, most folks are going via the TWRP recovery route now (and I believe that all custom ROMs going forward will be flashable this way only, and not SS).
you will find that using TWRP is much easier than SS
Click to expand...
Click to collapse
I realized that while looking at roms this afternoon. Before I go down the custom route though do you know if it affects the usage of gsm there are no CDMA carriers in Jamaica so I can't flash to anything?
Sent from my XT907 using xda app-developers app

ccdsatt said:
I realized that while looking at roms this afternoon. Before I go down the custom route though do you know if it affects the usage of gsm there are no CDMA carriers in Jamaica so I can't flash to anything?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Most of the ROMs need a gsmfix zip flashed, but they'll work on GSM with that
Sent from my Nexus 7 using Tapatalk HD