I've installed the wrong recovery by accident on my Vibe Z. Now it won't reboot in to recovery, it boots up fine but no recovery and I can't do a hard reset either. I've tried minimal adb, I can get it to fastboot mode but it says no permission to do anything with the phone
Any ideas would be greatly appreciated.
Related
I have this problem...
I have
ROOT
my fault is, I installed SPL for G1, Grrrr.
I touch 'back' to fastboot... and comands go.
I trying touch HOME to recovery mode, but 15sec and phone reboot
thats all
Pls help me, I need SPL for HERO, but which...
CAN I, load this??
forum.xda-developers.com/showthread.php?t=589095
Fastboot go well... this is my lucky...
Pls HOW to install
[recovery]
forum.xda-developers.com/showthread.php?t=561124&highlight=fastboot
I tryed,
fastboot boot recovery-RA-hero-v1.5.2.img
and all of them command is OKAY, but, load recovery again, from HOME... NO
its went gone, and fine... all is OK, reboot,
but recovery not going>>
CHANGE........
Ok,
now, I was trying and, throuth fastboot, I erase boot, and recovery,...
and boot, recovery.img... and now I have Recovery, but I dont know why I try run second recovery by HOME, and nothing... i dont know why
Thanks for all,
i don't exactly get what you are trying to say. is your problem that you can't boot into recovery by holding home and pushing power when the phone is off?
try this method: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
this installs the recovery image through fastboot. from what you say i understand that you are able to boot the recovery image by doing "fastboot boot recovery-RA-hero-v1.5.2.img", if so you should also be able to install it. follow the directions in that thread and report back.
Hi Guys,
I tried to update my TWRP, I think Modded 2.6.3.0 TWRP for KitKat from Voyager2k. But.. I didnt know, that there is a issue with password requirement. So i cant mount any partition, cant wipe or instal anything. Same time I got brick 1a, it always immediately reboot into recovery. No way to get into fastboot mode (power + vol Up). If I follow steps here http://forum.xda-developers.com/showthread.php?t=1514088 nothing happends. As well I attempted to use fastboot, erase, flash. WSG UnBricker doesnt work too. Everytime appears only "waiting for device". So I am stuck in TWRP, but cant do anything there.. Please tell me, it is not hard bricked..
Thanks for any help.
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??
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
Hi, I was just messing around my phone and installed five Magisk modules and then after reboot, my phone didn't want to turn back on. It was stuck at the boot animation and nothing else was happening. I kept it overnight plugged in to see if it turns on by any change. But on the next day, I found it to be super warm and it was still stuck at the boot animation.
Now all I have to do is, reboot to recovery mode, clear its whole data and reinstall the ROM (as I didn't make any backup).
But the main problem is that the Volume+ button in my phone is broken, and it does not work! Somehow I can still access the fastboot mode. I can use a command to delete all my data. As they're Magisk modules, clearing the data might not unbrick my phone (I'm not sure).
Is there any way I can reboot my phone into TWRP recovery through fastboot mode? Or can clearing the data in fastboot mode fix the problem?
SGoraiCS said:
Hi, I was just messing around my phone and installed five Magisk modules and then after reboot, my phone didn't want to turn back on. It was stuck at the boot animation and nothing else was happening. I kept it overnight plugged in to see if it turns on by any change. But on the next day, I found it to be super warm and it was still stuck at the boot animation.
Now all I have to do is, reboot to recovery mode, clear its whole data and reinstall the ROM (as I didn't make any backup).
But the main problem is that the Volume+ button in my phone is broken, and it does not work! Somehow I can still access the fastboot mode.
As they're Magisk modules, clearing the data might not save my phone. My phone's not going to turn on (I'm not sure).
Is there any way I can reboot my phone to TWRP recovery through fastboot mode? Or can clearing the data in fastboot mode fix the problem?
Click to expand...
Click to collapse
Two Methods.
1- Some phones actually respond to fastboot reboot recovery. This is quite natural given adb reboot recovery, but unfortunately is non-standard. I found lots of people suggesting this method so I offer it here in the hopes that it works for some, but it didn't for me.
2- Some phones will actually let you book into an image via fastboot without flashing it. This will allow you to load a recovery image without needing to reboot the phone at all. You need a copy of the recovery image on your computer, but running fastboot boot image.img should do the trick. I was able to load up TWRP using this method.
Sent from my Pixel 3 XL using Tapatalk