Locked out of vibrant...It only forcecloses - Vibrant Q&A, Help & Troubleshooting

ok soi as trying to flash new battery icons and when i rebooted the phone it dosnt start it just forcecloses my home screen and other ****...basically i cant get into my phone at all.
I went into adb typed recovery and it brought me to the stock recovery and not clockworks so i couldnt restore my backup so i wiped the phone with the stock recovery and it still boots up the same with the forcecloses. My phone is no longer read by my computer and when i type "adb devices" it no longer shows up.
I cant get into recovery mode manually because it just reboots.
I really need help.

Related

[Q] Download mode just fine via ADB, but not Recovery?

Softbricked my phone. I nandroided Fusion 1.1 then flashed Obsidian. Everything fine. But then i wiped and went to restore Fusion. Restored fine but now cant boot past Vibrant screen. I think its because i forgot to change the kernel. (Voodoo is not involved, i dont use voodoo)
So now im trying to get into recovery. I flashed the hardware-lock fix yet for some reason now i cant get into recovery via that method. I figured id try adb. Adb sees my phone and when i type "adb reboot recovery" the phone screen goes blank like its supposed to and then comes back on, but it still wont go past vibrant screen...wtf??
update: something else pretty interesting.....if i try to reboot into recovery via the 3-button combo, it just stays at vibrant screen, but then if i plug it in adb will see the device and it says "recovery" next to it....so im in recovery, but intsead of seeing the recovery menu, i see the Vibrant screen?
Have you tried using adb to reboot straight into recovery? Just type "adb reboot recovery". That should at least get you to the recovery menu on your screen.
Also, this is the technique I used to get my phone to boot into recovery using the three button method. It worked for me perfectly. http://forum.xda-developers.com/showthread.php?t=804305

Atrix Softbrick After Installing RomRacer CWM

Hello, im coming from Defy to Atrix, mine is Brazilian 2.3.6 Retail, and just unlocked the bootloader using Bell SBF. After installing RomRacer CWM (recovery-atrix5.img) using the fastboot method, my phone went in a continuous bootloop. Fastboot mode shows me an error something like FAILED TO EXECUTE COMMAND %e (a0cccx) that repeats and scrolls down the screen in red lines. I have to pull battery to stop this. RSD mode reboots the phone. Android Recovery shows me "Entering Android Recovery Mode" and after that phone hangs. To have the things worse, battery drained down.
After charging the battery using an universal charger, phone started, but when Android loaded, it hanged everything. I had to pull the battery. After that, phone went in bootloop again. I got into fastboot, wiped everything. After that i was able to get into Android Recovery, wiped everything again and tried to start the system, no luck. It went in bootloop again and the message in fastboot mode came on again.
One more point is, when the battery in on the phone, the phone is getting really hot.
I was using the phone for about 5 hours before messing the whole thing up, if i have it working again, i will stick with original firmware. No more customizing on this Atrix as long as its really easy to hardbrick. Im afraid that i did this to mine.
Defy is almost impossible to hardbrick. And its bootloader is locked. I see no goodness on having a phone that is that easy to kill... Please help me................
look into flashing an sbf on your atrix. puts it back to stock firmware.
if youre only soft bricked this will fix it. or try going to android recovery ( if it still has the original) and do a factory data wipe.
hope i helped!
I recommend you to download again RomRacer CWM
enter fastboot mode and flash again CWM (in case your download is corrupt)
type "fastboot devices" Press Enter.
type "fastboot erase recovery" Press Enter.
type "fastboot flash recovery recovery-atrix5.img"
if this didnt fix it
perform a full fastboot wipe
http://forum.xda-developers.com/showthread.php?t=1421261
and then try to reflash the recovery. if u cant fix it this way flash a sfb!

Cannot enter recovery?!

I kept getting the "set metadata error" on the latest Android Revolution HD rom so installed the latest version of CWM recovery but I kept getting the same error upon installing the rom. However, this time my phone is really screwed up. I cannot get back into CWM to restore my last backup, when I get the little "entering recovery" text on the top of my phone the screen goes black and then flashes something on the screen and that's it. I plugged the phone into my pc and followed the instructions for flashing TWRP recovery but again...when I try to enter recovery this time the TWRP log flashes and then it disappears. For some reason it also appears I am S-ON now as well! I can connect the phone and go to FASTBOOT USB and type "fastboot devices" and my phone shows up but no matter what I do I cannot get into TWRP to restore. What the heck do I do?!
type fastboot clear cache and try again

Can I flash a new recovery or edit build.prop or factory reset from ADB?

So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Fukesh said:
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Click to expand...
Click to collapse
Also, maybe there is a way to set up a VNC server of some sort to use the phone from the computer??

[Q] Oppo Neo 5 Softbricked

Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls

Categories

Resources