I rebooted my OnePlus One yesterday and found myself in a weird situation. The phone would go to the initial OnePlus logo then after, a smal android logo with a red warning sign appears for a split second, and I boot into the CM stock recovery. I can't turn it on or enter fastboot, nor can I turn on ADB Debugging on my phone and would really appreciate help as I do not want this phone to be gone. Pretty scared guys, help would be much appreciated!
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
badjoras said:
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
Click to expand...
Click to collapse
Thanks for the prompt response. I think you should also know that I attempted to put a custom recovery on my OPO, but after saying that it worked, I only loaded into the CM Stock Recovery. I do not, have my phone with me at the moment as I did not think it would be necessary to bring to school with me, but I will attempt everything you have said. Thanks for the help so far!
badjoras said:
I've never seen this problem before.
I supose you are bootloader unlocked, rooted and have costum recovery, right?
For fastboot, if it does not work normally, try: up button + power with the phone connected to the PC; if it does not work, try the same button combo + plug the phone to the pc while you are holding down the buttons.
Click to expand...
Click to collapse
I attempted both ways but nothing happens as I press the buttons. It will only boot in the CM Simple Recovery.
NizzleFish98 said:
I attempted both ways but nothing happens as I press the buttons. It will only boot in the CM Simple Recovery.
Click to expand...
Click to collapse
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
badjoras said:
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
Click to expand...
Click to collapse
Yes. It does.
Download the stock image. I'm sure it will be there somewhere in the forums.
Then go to recovery and do the following:
Select 'apply update'. Then you either have the option to apply update from Internal Storage or from adb.
Select adb and enter: adb sideload update_filename.zip
badjoras said:
I believe you messed it up for good, since you: can't get into fastboot; have no recovery; have no backups... If you could get fastboot to go you would only need to flash twrp and then sideload a rom =/
Does the stock recovery let you sideload?
Click to expand...
Click to collapse
assuming it's the stock android recovery, i'm pretty sure it allows for sideloading.
Def sounds like something got flashed to the wrong parition though
Related
hey today my phone switch off by it self so i recharged it and turn it on but it didnt load then i tried going on recover but it only flashes the screen black then it goes back to the same menu the recovery dont open i had CW recovery installed it says it the top
FASTBOOT MODE- NO BOOT OR RECOVERY IMG
i tried flashing cw recover by adb but it dont find the phone it the bottom of the screen it says
USB Control init
USB control init End.
anyone help?
sir ithink it is not yet bricked based on the description just make sure that all drivers for your phone is installed and flash the recovery again
hey thx for your quick respond i dont seem to find my device look at the printscreen attached.
the phone is underwarrenty can anyhouse lock the bootloader so i can sent it for repair? thx again
abdalah2004 said:
hey thx for your quick respond i dont seem to find my device look at the printscreen attached.
the phone is underwarrenty can anyhouse lock the bootloader so i can sent it for repair? thx again
Click to expand...
Click to collapse
Your adb setup isn't working. Have you booted your phone holding VOL+ and power? Are your ADB drivers installed?
It's either the first or the last one, check your stuff. I doubt it's bricked.
look thats what the phone do exactly when i restart it normal it keeps on the boot screen it just keep going on but when i boot with vol + i get into that menu not sure what its called where it say
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
not sure which driver i had but can u give me one to install just in case? thanks
PS. i just reinstalled the drivers from Android SDK still having the same problem
abdalah2004 said:
look thats what the phone do exactly when i restart it normal it keeps on the boot screen it just keep going on but when i boot with vol + i get into that menu not sure what its called where it say
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
not sure which driver i had but can u give me one to install just in case? thanks
Click to expand...
Click to collapse
I've never had good luck with the Android SDK driver, I use the PDANet driver instead.
http://junefabrics.com/android/index.php
That always got my phone to be detected after.
Edit: That's the fastboot screen. You should have used this when you rooted your phone, if you did it "manually".
You will use fastboot flash recovery recoveryimage.img
to flash a recovery. Recoveryimage.img will be the name of the recovery you're trying to flash.
i did and thats what i get when im trying flash the recovery
wow i restarted the phone and tried and it worked
abdalah2004 said:
i did and thats what i get when im trying flash the recovery
Click to expand...
Click to collapse
sir also try renaming the file so it will be easier to type...sir and it was flashed if it restarted in the recovery please let me know what happened
Hi,
I tried to restore my Nexus S (european, GT-I9023) which has a broken power button before sending it to Samsung for repair.
I just screwed my ROM flash using Clockworkmod and now my phone only shows a beautiful Google screen.
When I try to use fastboot screen (using vol+/vol-) nothing moves, and even if it moved I wouldn't be able select any option as my power button is broken. I can't also access Odin (vol+ and vol- pressed when the phone is off) as I can't turn off my phone.
What can I do to flash my rom? May I send it to Samsung anyway?
Thanks for your answers!
Txkw said:
Hi,
I tried to restore my Nexus S (european, GT-I9023) which has a broken power button before sending it to Samsung for repair.
I just screwed my ROM flash using Clockworkmod and now my phone only shows a beautiful Google screen.
When I try to use fastboot screen (using vol+/vol-) nothing moves, and even if it moved I wouldn't be able select any option as my power button is broken. I can't also access Odin (vol+ and vol- pressed when the phone is off) as I can't turn off my phone.
What can I do to flash my rom? May I send it to Samsung anyway?
Thanks for your answers!
Click to expand...
Click to collapse
I am also facing the exact same problem. Can someone kindly guide us please?
Switch off. Press Volume Up and plug in the charging cable. Now, see if you tackle with the Fastboot mode.
Sent from my Nexus S using Tapatalk 2
a2zRulz said:
I am also facing the exact same problem. Can someone kindly guide us please?
Click to expand...
Click to collapse
My power button is broken too.
I solved the problem flashing ClockworkMod Touch from Windows Terminal.
DJBhardwaj said:
Switch off. Press Volume Up and plug in the charging cable. Now, see if you tackle with the Fastboot mode.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
He might not be able to. When the power button breaks, it stays in a "on" state and that messed up fastboot as it doesn't let you scroll or initialize properly.
a2zRulz said:
I am also facing the exact same problem. Can someone kindly guide us please?
Click to expand...
Click to collapse
If your rom starts booting (you see a quick flash after initial Google logo) you might be able to ADB from there (while it's not booting and the rom logo is showing, I know weird but often works). Check it out.
Edit: Oh and if you get adb access, then what you want to do is "reboot recovery" to reboot to recovery, and then wipe/flash a rom and whatnot.
polobunny said:
He might not be able to. When the power button breaks, it stays in a "on" state and that messed up fastboot as it doesn't let you scroll or initialize properly.
If your rom starts booting (you see a quick flash after initial Google logo) you might be able to ADB from there (while it's not booting and the rom logo is showing, I know weird but often works). Check it out.
Edit: Oh and if you get adb access, then what you want to do is "reboot recovery" to reboot to recovery, and then wipe/flash a rom and whatnot.
Click to expand...
Click to collapse
You are absolutely right. The phone thinks that the power button is pressed and doesn't let us move up and down using the volume keys.
Also, even if I get adb access after the Google logo, how do I use fastboot mode? I actually wanted to flash a recovery as my Power button doesn't work even in the recovery. Moreover, I can boot into recovery without adb, from inside the rom power menu.
So adb doesn't help here
a2zRulz said:
You are absolutely right. The phone thinks that the power button is pressed and doesn't let us move up and down using the volume keys.
Also, even if I get adb access after the Google logo, how do I use fastboot mode? I actually wanted to flash a recovery as my Power button doesn't work even in the recovery. Moreover, I can boot into recovery without adb, from inside the rom power menu.
So adb doesn't help here
Click to expand...
Click to collapse
What recovery do you currently have? All custom recoveries enable you to scroll with menu and home key, go back with the back key and select with the search key. So if you can get adb while it's "not booting" and reboot to your custom recovery, then you can navigate, mount usb and transfer a rom if needed or flash one that is on your phone.
Edit: Also, I was under the impression you couldn't boot your ROM. If you can, what is it exactly that you are trying to do??
polobunny said:
What recovery do you currently have? All custom recoveries enable you to scroll with menu and home key, go back with the back key and select with the search key. So if you can get adb while it's "not booting" and reboot to your custom recovery, then you can navigate, mount usb and transfer a rom if needed or flash one that is on your phone.
Edit: Also, I was under the impression you couldn't boot your ROM. If you can, what is it exactly that you are trying to do??
Click to expand...
Click to collapse
I have ClockworkMod (CWM) 6.0.2.5 Non-Touch from this thread:
Code:
http://forum.xda-developers.com/showthread.php?t=2032337
I flashed this earlier when my power button was working. And I have tried all the capacitive buttons. None of them work with this recovery. That's why I was looking forward to flashing a touch based recovery.
a2zRulz said:
I have ClockworkMod (CWM) 6.0.2.5 Non-Touch from this thread:
Code:
http://forum.xda-developers.com/showthread.php?t=2032337
I flashed this earlier when my power button was working. And I have tried all the capacitive buttons. None of them work with this recovery. That's why I was looking forward to flashing a touch based recovery.
Click to expand...
Click to collapse
From the same thread you can simply download any of these (highly suggest ClockworkMod (CWM) 5.8.0.2 Touch, one if not the most reliable) and flash them from within your current CWM.
polobunny said:
From the same thread you can simply download any of these (highly suggest ClockworkMod (CWM) 5.8.0.2 Touch, one if not the most reliable) and flash them from within your current CWM.
Click to expand...
Click to collapse
Dear sir,
Please understand. That's what I am trying to tell you. I cannot use power button or any other button to select anything in the recovery. So how will I install this one?
a2zRulz said:
Dear sir,
Please understand. That's what I am trying to tell you. I cannot use power button or any other button to select anything in the recovery. So how will I install this one?
Click to expand...
Click to collapse
Ok let's get this right
What is your goal? Flash a different recovery? Then you can flash a recovery from within something such as ROM Manager if your rom still boots.
Yes sir, my goal is to flash a touch based recovery just so that I can flash new ROMs and kernels without the help of the power button.
Koushik charges for in-app flashing of CWM Touch which is otherwise free. So that's the main issue here. I guess I'll have to live with it
a2zRulz said:
Yes sir, my goal is to flash a touch based recovery just so that I can flash new ROMs and kernels without the help of the power button.
Koushik charges for in-app flashing of CWM Touch which is otherwise free. So that's the main issue here. I guess I'll have to live with it
Click to expand...
Click to collapse
Ok.
You can use this Flash Image GUI to flash a recovery of your choice from within Android then:
http://forum.xda-developers.com/showthread.php?t=1453617
It's free. Make sure to download the right recovery for your device and select recovery image in Flash Image GUI.
polobunny said:
Ok.
You can use this Flash Image GUI to flash a recovery of your choice from within Android then:
http://forum.xda-developers.com/showthread.php?t=1453617
It's free. Make sure to download the right recovery for your device and select recovery image in Flash Image GUI.
Click to expand...
Click to collapse
You sir, are my hero... Many thanks for this :highfive: :victory:
If you are flashing a touch version of CWM recovery, I highly suggest v6.0.1.0. The later version (up to 6.0.2.5) have a bug that will make you unable to mount the SD card within the recovery. Otherwise TWRP is very interesting, but backups made with CWM are not compatible with TWRP.
Thanks, I'll try TWRP this time
Hey All,
I know there are a lot threads like this on here, so I made sure I tried everything possible before asking for help.
First off, It is a MZ604 wifi version.
Ok, upon powering up my Xoom, it will get to the Motorola screen/ dual core and stall.
I am able to get into recovery, however the version I am running, 5.8.3.1 apparently does not allow sd card mounting, so I am unable to restore or flash a new rom.
A factory reset/ data wipe does nothing.
I have tried to flash a new rom via ADB, however my computer will not install the Xoom drivers. It will say "installing device drivers" for about 2 minutes or so before failing. I have tried using moto helper and the other Motorola usb drivers
I am unable to boot into android to enable usb debugging
I have tried all of the above on my laptop too and to the same result.
My question is, is this a brick? or can it be solved.
Thanks for your time
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Chaosgod27 said:
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Click to expand...
Click to collapse
Thanks for responding, I appreciate it. The thing is that my xoom cannot connect to my computer, and therefore and cannot use fastboot to send it the image correct?
I could fix all of this if I could just get the drivers to install, but because of my xoom's condition, the drivers cannot install no matter what.
Hmm usually fastboot drivers should automatically install. Does your recovery have an option to boot into fastboot? Once you're in fastboot it should automatically install the drivers, and in the android sdk folder in CMD (assuming you're running windows) put in this command: fastboot devices
It should show up your XOOM if not install this http://www.motorola.com/Support/AU-EN/Support-Homepage/Software-and-Drivers/USB-PC-Charging-Drivers
And try again
Hi all!
I got the same problem...
I can connect it to PC and do fastboot, I've flashed it many times, but it didn't affect my Xoom, i've reflashed the recovery to a lower version (tiamat rc4) but the recovery still shows version 5.8.3.1...
I even tried RSD, but it still the same...
no errors, and no effects...
is my Xoom bricked?
^I heard of this before, sounds like your new recovery image just gets overwritten by the current recovery. Though I thought it was only for stock recovery.
but, how can I overwrite it? it seems like they are read only...
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Chaosgod27 said:
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Click to expand...
Click to collapse
that's not the problem... of course I can access the recovery, fastboot and RSD, the problem is that I whatever I do to the xoom just don't work... and it reports no error at all... it's just succeed, but nothing happened... It's like a PC running windows with DeepFreeze installed...
Anyone got the same problem? can anybody help me?:crying:
No you're missing the whole point, after you flashed your new recovery it may get overwritten if you don't reboot into recovery straight way. It never happened to me but I have read that people has that issue.
Trying to install CyanogenMod for my razr maxx HD. Recently used RSDlite to install 183.46.10 after OTA KK update kept failing. Then used towelroot to root and motopocalype to unlock bootloader. Fastboot screen shows bootloader is unlocked with status code: 3.
I then followed the instructions on the CyanogenMod site to flash CWM 6.0.4.4 recovery using fastboot, and all appeared to work fine.
However, when I try to reboot into recovery, nothing happens. I get hung up on the motorola dual core flashscreen for about a minute or two, then the screen goes black, then the phone reboots normally.
I tried flashing a different copy of CWM, tried TRWP, and tried several third party apps from Google Play store to boot directly into recovery using software reboot instead of hardware keys - all with the same results. I even tried flashing custom CWM recovery using ROM Manager and Rashr, same result.
Do I have a corrupt recovery partition? Any suggestions for how to fix?
You need to install a recovery for that phone specifically.
http://androidhosting.org/Devs/Dhacker29/
Use the recovery files found here.
Edit: on the site I posted, browse to the msm8690 folder. There you will find the recovery files.
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Thanks, guys, total noob mistake. I knew the recovery needed to be specific for the phone, but didn't realize it varied depending on the bootloader. Will try again with the right recovery!
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
TheGman125 said:
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
iBolski said:
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
Click to expand...
Click to collapse
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
TheGman125 said:
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
Click to expand...
Click to collapse
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
iBolski said:
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. Have code 3 on the devices.
try and unplug from USB when you reboot
I've been trying to flash TWRP onto my Galaxy S3 and my Galaxy S9 for a few days now, and every time I try to do so, it flashes successfully, but then boots into stock Samsung recovery when entering recovery mode. I've used Odin on Windows and Heimdall on Linux, but both have the same issue. I tried different versions of TWRP as well.
If it helps, I'm pretty sure both phones are OEM unlocked. The S9 has the option in developer options, and says it it unlocked in download mode. The S3 doesn't have any option for this, and doesn't say anything in download mode about it.
Even though the S3 might not be OEM unlocked, it still doesn't explain the issue with the S9.
I'm also dual booting, so all attempts were from the same computer. It might be some issue with my computer, but I really don't have access to another one right now, so I was wondering if anyone had any other ideas or thoughts on the issue. Any help would be appreciated.
Did you check this?
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
https://twrp.me/samsung/samsunggalaxys3internationalexynos.html
I think for S3 it's
Vol up + Home + Power
Basically:
1. Flashing
2. Reboot into Recovery by keep pressing Vol up + Home + Power
3. Allow TWRP to become permanent
Perhaps you want to check/re-ask here as well:
https://forum.xda-developers.com/c/samsung-galaxy-s-iii-i9300-i9305.1563/
SigmundDroid said:
Did you check this?
https://twrp.me/samsung/samsunggalaxys3internationalexynos.html
I think for S3 it's
Vol up + Home + Power
Basically:
1. Flashing
2. Reboot into Recovery by keep pressing Vol up + Home + Power
3. Allow TWRP to become permanent
Perhaps you want to check/re-ask here as well:
https://forum.xda-developers.com/c/samsung-galaxy-s-iii-i9300-i9305.1563/
Click to expand...
Click to collapse
Holding the given buttons just brings me to default recovery, so I'm not sure what the proper recovery is. I've also tried Volume Up + Down + Home + Power.
Hmm, didn't flash an S3 for quite some time but I vaguely remember that I had similar problems during
"After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted"
and often missed or was too clumsy, too late or both
Would in fastboot the command
fastboot reboot recovery
work for you? Or does it still end up in stock recovery?
Perhaps it's really time to check in the s3 threads for further advice?
SigmundDroid said:
Hmm, didn't flash an S3 for quite some time but I vaguely remember that I had similar problems during
"After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted"
and often missed or was too clumsy, too late or both
Would in fastboot the command
fastboot reboot recovery
work for you? Or does it still end up in stock recovery?
Perhaps it's really time to check in the s3 threads for further advice?
Click to expand...
Click to collapse
Okay so turns out I needed to boot into recovery immediately after flashing TWRP on both phones because when booting into the system, the recovery is replaced. After doing this, everything worked fine and I was able to get custom ROMs working! I appreciate your help though