Related
Hello,
I'm new to the XDA forums and hope you guys can help.
Last night, I came to the mind that I would flash my phone. I completed everything in torr's "[Tutorial] Root, Unlock, Recovery, and Flashing a Custom Rom" without any problems. First loaded Viper's Rom, no problems. Then I wanted to see how the other ROMs looked like so I proceeded to load Energy (had Wi-Fi connection issues), some of the "Without Sense" ROMs on Uwe303's, and finally tried to load BAKED Blackbean and hit a rock.
I'm stuck on the Recovery screen. I can't go into Fastboot either via the volume way, adb, or Hansoon200's AIO Kit. When I try to restart the phone, the red signal light goes on and off twice, screen blips twice, and goes back into recovery. I can't RUU, because I can't re-lock the Bootloader. I have been able to push other ROMs and flash them, but to the same results. Can someone help me?
Thank you.
mstrsage2 said:
Hello,
I'm new to the XDA forums and hope you guys can help.
Last night, I came to the mind that I would flash my phone. I completed everything in torr's "[Tutorial] Root, Unlock, Recovery, and Flashing a Custom Rom" without any problems. First loaded Viper's Rom, no problems. Then I wanted to see how the other ROMs looked like so I proceeded to load Energy (had Wi-Fi connection issues), some of the "Without Sense" ROMs on Uwe303's, and finally tried to load BAKED Blackbean and hit a rock.
I'm stuck on the Recovery screen. I can't go into Fastboot either via the volume way, adb, or Hansoon200's AIO Kit. When I try to restart the phone, the red signal light goes on and off twice, screen blips twice, and goes back into recovery. I can't RUU, because I can't re-lock the Bootloader. I have been able to push other ROMs and flash them, but to the same results. Can someone help me?
Thank you.
Click to expand...
Click to collapse
Sounds like you flash CWM which is buggy you want to flash TWRP. The trick to getting into the bootloader is to hold the Vol- as you turn the phone off while holding Vol- let go of power and press and hold again. Also the reason it didn't boot was that you didn't fastboot the boot.img.
Darknites said:
Sounds like you flash CWM which is buggy you want to flash TWRP. The trick to getting into the bootloader is to hold the Vol- as you turn the phone off while holding Vol- let go of power and press and hold again. Also the reason it didn't boot was that you didn't fastboot the boot.img.
Click to expand...
Click to collapse
I used Hansoon's AIO to flash the boot.img before every refresh and holding Vol- still brings me straight to CWM. I can't flash TWRP right now cause I can't get it to the bootloader.
mstrsage2 said:
I used Hansoon's AIO to flash the boot.img before every refresh and holding Vol- still brings me straight to CWM. I can't flash TWRP right now cause I can't get it to the bootloader.
Click to expand...
Click to collapse
You just have to keep trying and maybe tweak what I said because without getting into bootloader there nothing you can do but as soon as you do flash TWRP it will make it easier to get into the bootloader.
Darknites said:
You just have to keep trying and maybe tweak what I said because without getting into bootloader there nothing you can do but as soon as you do flash TWRP it will make it easier to get into the bootloader.
Click to expand...
Click to collapse
Thanks =] I'll keep trying then
Not sure exactly what you are doing on the "volume- way"
The only way I get to bootloader is to hold down vol- and pwr at same time for about 5-7 seconds, then release only pwr. Continue to hold vol- down till it boots. May take 20 seconds or so.
Were you wiping all including system before flashing these roms
You said you can adb push a rom then flash it, try that again with wiping all including system 2x
when you were in adb you tried to get to bootloader by typing "adb reboot bootloader" ? no quotes
just some ideas--not sure if you them all or not
rugmankc said:
Not sure exactly what you are doing on the "volume- way"
The only way I get to bootloader is to hold down vol- and pwr at same time for about 5-7 seconds, then release only pwr. Continue to hold vol- down till it boots. May take 20 seconds or so.
Were you wiping all including system before flashing these roms
You said you can adb push a rom then flash it, try that again with wiping all including system 2x
when you were in adb you tried to get to bootloader by typing "adb reboot bootloader" ? no quotes
just some ideas--not sure if you them all or not
Click to expand...
Click to collapse
Sometimes when you are in recovery with CWM you can also use "adb" commands. Connect your device when its in recovery to your pc via usb. Then try "adb reboot bootloader" as a command.
AKToronto said:
Sometimes when you are in recovery with CWM you can also use "adb" commands. Connect your device when its in recovery to your pc via usb. Then try "adb reboot bootloader" as a command.
Click to expand...
Click to collapse
Only issue with that is it will boot into CWM because of the USB cable.
same issue
hey guys,
I'm having the same issue of rebooting into CWM recovery and have no way out.
I've tried both the VOL DOWN option and the "adb reboot bootloader" option, and I am having no luck.
Can you please help me get OUT of CWM recovery????
Thanks!
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Hey ladies and gentlemen,
I am having a serious problem. I tried to root my Honor 6 (H60-L04). After installing Super User via TWRP my smartphone started a bootloop. After I waited a few hours it turned off and I tried to reload it for booting into the download mode (to flash a new firmware via Honor MultiTool). But it still showed me that there is an empty battery and didn't start. How can I unbrick it?
Thanks
Haeggis said:
Hey ladies and gentlemen,
I am having a serious problem. I tried to root my Honor 6 (H60-L04). After installing Super User via TWRP my smartphone started a bootloop. After I waited a few hours it turned off and I tried to reload it for booting into the download mode (to flash a new firmware via Honor MultiTool). But it still showed me that there is an empty battery and didn't start. How can I unbrick it?
Thanks
Click to expand...
Click to collapse
do u have solution for this??
To install a full stock firmware follow these steps, if the phone is not booting in bootloader mode try doing this: After a loop gets complete, quickly press Vol UP button and connect the phone to PC, you'll be in bootloader mode.
Download your latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
I had a similar problem with mine when updating to EMUI 4. What I did was:
- Hold Volume Down while rebooting and Connect USB. It should boot into Bootload mode.
- If you get the Error Screen, reboot the Phone.
- If it doesn't work, hold all three buttons. It should reset the phone.
This actually reset my phone and made it work again. Don't ask me why or how.
You should Unbrick with Honor Multitool. You get to still have your data intact when you do only the first step without the 3 button install. If you don't have a TWRP backup that is. Don't ever install SU or root from TWRP. Use KingRoot or Multitool
CplBasti said:
I had a similar problem with mine when updating to EMUI 4. What I did was:
- Hold Volume Down while rebooting and Connect USB. It should boot into Bootload mode.
- If you get the Error Screen, reboot the Phone.
- If it doesn't work, hold all three buttons. It should reset the phone.
This actually reset my phone and made it work again. Don't ask me why or how.
Click to expand...
Click to collapse
If the device is rooted then you'll get install failed when doing three button reset, hence the manual flashing is needed.
The three button reset also fails, if in anyway your system is modified.
DigiGoon said:
If the device is rooted then you'll get install failed when doing three button reset, hence the manual flashing is needed.
The three button reset also fails, if in anyway your system is modified.
Click to expand...
Click to collapse
Well, my system was modified, and after doing that Three-Button reset twice, it actually worked.
Don't ask me why, it just worked. And I'm actually glad it did haha.
CplBasti said:
Well, my system was modified, and after doing that Three-Button reset twice, it actually worked.
Don't ask me why, it just worked. And I'm actually glad it did haha.
Click to expand...
Click to collapse
Good for you then, maybe the UPDATE.APP adjusted itself.
DigiGoon said:
Good for you then, maybe the UPDATE.APP adjusted itself.
Click to expand...
Click to collapse
Haha, yeah, probably
I'm just happy that my phone is working now.
Yes, sometimes Android does things which we can't understand(or maybe we don't have enough knowledge), so its easy to just accept the outcome and enjoy..!!
Hi,
I am totally lost and need help to get my personal data (images, videos most important) back from my bootlooping phone.
I browsed the privacy guard settings and disabled some boot and caller rights for google services and google play (with the intention to prevent it from looking up for updates constantly and drain my battery).
Then it restarted itself as I plugged it in for charge and is bootlopping since.
I have no root, the latest official CM update and a the build in Cyanogen recovery, since it came out of nowhere no usb bugging enabled (I believe).
When I try to enter the phone via ABD sideload from the CM Recovery "pull" my folders it says error:closed. adb backup wont work either.
It tells me: adb: unable to connect for backup: closed
This whole topic is kind a new for me - I never was in that situation and for now all I want is my images and videos back from my phone at least. I will try any method to save them.
I hope some can help me - I don´t know what to do anymore
This should theoretically work.
Flash TWRP by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.
Thank you so much for this hint!
I will try that.
So I Just change my recoverer with this method right? This is possible without root and usb debugging?
Joshwin Aranha said:
This should theoretically work.
FlashTWRP] by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.
Click to expand...
Click to collapse
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?
Sore6 said:
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?
Click to expand...
Click to collapse
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.
Joshwin Aranha said:
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.
Click to expand...
Click to collapse
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Sore6 said:
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?
Click to expand...
Click to collapse
I was just about to say to try booting into the recovery, follow @nitrobg's instructions, get the recovery and instead of flashing the recovery, just try booting into it, command is
fastboot boot recovery.img
Hope it helps you, the pain of losing precious data isn't unknown to the best of us
EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that
EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that
Click to expand...
Click to collapse
I disabled some google play and google services from booting via the official cm privacy settings
Reason was to disable the battery drain by play when searching constantly for GOOGLE android updates...
Needed to disable that in cm12 back then and it helped.
nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
I will try that! Thank you.
I get back here with the result.
nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
Unfortunately it gives me this in the commandline:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.430s
That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.
nitrobg said:
That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.
Click to expand...
Click to collapse
Sadly no - all adb commands end in "error:closed"
Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.
nitrobg said:
Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.
Click to expand...
Click to collapse
Didnt work because as far as i know one has to be in the android ui - hold pwer off key and then hold the restart menu item and then the volume buttons + power buttons code should work.
Thanks anyway - i wiped it now.
it works but all data is gone
Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.
nitrobg said:
Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.
Click to expand...
Click to collapse
Honestly - I held it for 4 Minutes. There was a Vibrate Signal everytime it wanted to boot up into android but it didnt. Then it kept the cynogenmod loader til the next little vibration. It was a loop with no entry to android GUI
It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)
Joshwin Aranha said:
It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)
Click to expand...
Click to collapse
Thanks man - jeah I took care of such case beforehand now and rooted, bought titaniuam backup and enabled usb debugging instantly...
Also I am now using TWRP.
Lesson learned.
Thanks to you all for helping me!
I am really thankful for your effort.
Kind regards
Some kind thanks on my replies maybe ?
Haha, anyway. Take care.
I flashed TWRP to the device successfully, and proceeded to try to install Magisk 19.3 zip. It would begin to do a recovery bootloop. I fixed it using TWRP, and tried using the patched boot img from magisk manager instead. This is where things go wrong. After flashing boot.img, the phone refuses to boot, and asks me to do a factory reset. I did this twice, and the phone continued not to boot. I then tried installing the latest android Q factory image. The flash failed, and the phone stopped showing up when I do fastboot devices or adb devices. It is stuck in the bootloader telling me slot b is not bootable. I have tried different ports, but adb and fastboot are no longer responding.
Can't promise anything, but this might be a good spot to start
D3RP_ said:
Can't promise anything, but this might be a good spot to start
Click to expand...
Click to collapse
Unfortunately, this just tells me that it can't detect my device, even though it is plugged in. Its so weird that it makes it to the bootloader screen, but fastboot doesn't work.
skyward176 said:
Unfortunately, this just tells me that it can't detect my device, even though it is plugged in. Its so weird that it makes it to the bootloader screen, but fastboot doesn't work.
Click to expand...
Click to collapse
Have you tried just holding the volume up and power button for a good 30 seconds?
D3RP_ said:
Have you tried just holding the volume up and power button for a good 30 seconds?
Click to expand...
Click to collapse
Holding down the volume up and power buttons just restarts it repeatedly, and each time it restarts it tells me "ERROR: Operation Denied"
EDIT: OMG fastboot works! Let's see how this goes from here. TYSM!
ITS FIXED!! Thanks so much
skyward176 said:
ITS FIXED!! Thanks so much
Click to expand...
Click to collapse
Hello! I have exactly the same problem.
Can you explain step by step what you did after fastboot began to see your phone?
I held the vol up and power buttons. This allowed fastboot to see it, and let the flash all script from the stock boot image run. This gave an error, but after holding the vol. Up and power buttons again, the phone started right up.
skyward176 said:
I held the vol up and power buttons. This allowed fastboot to see it, and let the flash all script from the stock boot image run. This gave an error, but after holding the vol. Up and power buttons again, the phone started right up.
Click to expand...
Click to collapse
Ayyy! Good job!