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
Related
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.
Hi.
I was installing Clockwork Mod externally onto my Viewsonic G Tablet. It started to install and was taking awhile I left the room and when I came back the tablet was off. I turned it back on and now my tablet won't go into recovery mod. It opens just fine, but I can't get it to open into recovery mod or Clockwork Mod. Just freezes up when every I power and +.
How can I fix Clockwork Mod or remove Clockwork Mod?
X that. I thought I would give a factory reset a try. So I went into settings and factory reset the thing. Well it restarted and when it got to the viewsonic birds it says "booting recovery kernal image" and never change. I have some how bricked the unbrickable G Tablet. Only my luck. Murphy's Law.
No you haven't. Factory reset uses recovery mode to perform it's operation so if ClockworkMod didn't install properly it will just hang. You need to nvflash a good recovery partition image onto the tablet then the factory reset will be able to complete and things should be fine.
NVflash back to stock and start over.
Does Nvflash give any indication that it's working? I'm trying to load Clockworkmod after dorking it up with Rom Manager, and I get
"Nvflash started" and a blinking cursor on the next line as a result. I can't tell if it's doing anything, or just sitting there.
Edit: 2 hours later when I gave up, it did detect when I unplugged the USB cable.
K J Rad said:
No you haven't. Factory reset uses recovery mode to perform it's operation so if ClockworkMod didn't install properly it will just hang. You need to nvflash a good recovery partition image onto the tablet then the factory reset will be able to complete and things should be fine.
Click to expand...
Click to collapse
How do I do this? I did the nvflash, then the factory reset, installed clockwork, when I try to start in cw mode, it still says "booting recovery kernel image" under "detect a recovery key pressed", then has the update looking box, then boots right into stock rom. Please help!!!
EDIT: I think I got this figured out by following the instructions here (In case anyone else has this problem).
http://forum.xda-developers.com/showthread.php?t=1058649
Nvflash should give you plenty of feedback in the dos shell or terminal window you're running it in. If you aren't getting any then it isn't working properly. That could be a driver issue under windows or possibly the tablet not being in APX mode when you start the process.
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!
Alright guys, I need some help.
I tried installing twrp using adp / fastboot. I thought everything was going well. Everything came up as finish, the blue bar was full for a good 10 min, so I issued the restart command, and crossed my fingers it restarted.
I stared as I hoped I didn't screw something up.... android seemed to load fine and go to the lock screen. I was relieved. :
So, I tried rebooting (PWR + Vol Down) and choose RCK to load twrp. Now it just sits there, at " Booting recovery kernal image" and dosen't go anywhere.
Any ideas?
My goal is to flash AndroWook HairyBean.
Edit
Let me add that I am a novice at this at best. As far as I know, twrp may not have even took? But once I get twrp working, I can flash Hairybean, right?
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??