Related
hello xda. i need your help. im desperate. i dont know what else to do with my moto g here's what happened:
first of all, i dropped my moto g into the water.
right after i got it out, it startet bootlooping. then it turned off by itself after almost an hour had passed.
i put it in a bag full of rice for the rest of the night and almost the whole following day. then i plugged it into the wall charger, and it wouldnt charge at all. the only sign of life was the blinking led.
so i took it to Movistar-Peru for repair, and told me the obvious: water damage was not covered in the warranty, then my phone was returned to me.
so i decided to tear it down by myself.
everything was looking fine. the water indicators were red, but everything was clean except for the battery socket: there was mineral condensation around it. i wiped it out, cleaned it away and then the phone would actually charge the battery icon displayed normally.
so i let it charge for 3 hours and after it was completely charged i turned it on. just to run into a black screen after the bootnimation.
good news is it actually can boot into fastboot mode and can access recovery menu.
i did some research here, and seemed like my phone needed a full stock flash (that´s what i thought). i decided to unlock the bootloader, using motorola unique code. (i thought it may be needed for flashing, but it seems it is not necessary)
in recovery, my sdcard folders display normally, i can wipe data/factory reset it normally, BUT when i try to erase cache partition, the phone reboots.
so i started flashing my device through fastboot. i should mention that before i dropped it into the water, i had installed 4.4.2 ota update. but whenever i tried to flash a 4.4.2 rom, i got hab check failed for sysyem, for recovery and sometimes for boot.
now, i've tried several official motorola signed jelly bean roms (nextel br, movistar sp, claro ar, etc etc) including original Movistar Pe jb rom (which ive already flashed uncountable times) with no errors on flashing, but neither of them got me passed the black screen after bootanimation. (the phone is not off, cause the backlight remains on). the only way of getting out of it is rebooting into fastboot mode again (volume- and power).
i've also tried relocking the bootloader, and the process gives me no errors (the word "locked" displays by the end, though the phone then reboots into the "warning bl unlcked" screen) , but regardless of that and the relocking process turning out okay, status code 3 is displayed in menu, meaning the bl wasnt really relocked..?)
in short:
-dropped into water, started bootloop, then it turned itself off.
-next day it would display black screen after bootnimation, no matter what i did.
-if i choose wipe cache partition, the phone reboots.
-i've flashed it "sucsessfully" several times, still runs into a black screen after bootnimation.
-i've unlocked the boootloader
-if i try to reclock: process turns out okay("locked" word by the end), but status code remains being 3.
-i dont care about backups, i had nothing important in my phone (gdrive ftw)
my concearns are:
-possible hardware unrepairable damage
-bootloader got corrupted
-mineral condensation is still there deep inside the components
-maybe gpu? emmc corrupted? semi brick? idk..
my questions are:
-what can i do from now?
-i've read that a new bootloader can be flashed into the phone. risk of bricking my phone?
-if the bootloader is the problem, flashing a new one would solve it?
-in general, what am i doing wrong in all of this? has my phone any chance of functioning normally, at all?
please help me , i miss my phone, i got it for christmas, it is my first smartphone and i woudl like to bring it back to life if possible. thank you for reading.
I can help!
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Thank you for replying to my problem
i have already done your steps uncountable times.
every time i try to wipe cache, the phone reboots. it does not wipe anything at all, it just instantly reboots. then bootanimation, then black screen again, but nothing happens. not even after 2 minutes, after 5 or 10. nothing. just black screen until battery drains completely from continously powering the backlight. do you think maybe the water hardware-bricked my phone? also, im ocassionally getting blue screens out of a sudden, then the phone powers itself off.
Ah, ok, sorry my suggestion didn't help. I had exactly the same problem, so surprised this didn't help you. After being dropped in water, all I got was a black screen after the initial start animation. I don't really know much about phones tbh, I just managed to fix mine through trial and error. My girlfriends phone was initially sent to a shop for repair, and although the guy couldn't fix it, he said there was no signs of water damage. Not really sure then why the phone stopped working, but the method I suggested did work for me. I don't think there was anything else I tried. It's worth mentioning maybe that it took 6 weeks before I could fix the phone. Maybe it took that long to fully dry out? Straight after the accident though the phone was put in a bowl of rice for days so it should have been dried pretty quick. Don't really know what else to suggest, sorry I couldn't be more help. Have faith though, I reckon it'll come back to life soon
thank you for posting a reply and thank you for your advice. i appreciatte the attention given. i will further try some other methods in hope of a solution.
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
Click to expand...
Click to collapse
are you sure it has nothing to do with the bootloader? now that you mention this.. can a 4.4.2 bl load a 4.3 rom successfully? and moreover, if i flash another bl, it will overwrite my original one right? is there eny problem on that? i am asking because no matter what i do, regardless of the "locked!" message, the menu keeps showing code status 3.
what happens if i flash the recovery and cant mount or flash any rom? or if the black screen persist after that?
and i wish i had known the rice trick before, cause i kept the bag closed for almost a day :s
grahameaddicott said:
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Click to expand...
Click to collapse
It worked for me, Thanks
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Click to expand...
Click to collapse
ok i did what you said, i tried to flash cwm and fastboot presented no problems, (output is "okay"), but un the phone screen there's a message "mismatched partition size (recovery)", and when i enter recovery, it boots normal STOCK recovery!! i donw know whats happening. i renamed the cwm image to cwm.img and typed in these commands:
fastboot erase recovery
fastboot flash recovery cwm.img
then i clicked recovery option in the bootloader menu... but it booted into stock recovery!! this is so confusing
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
thank you i will proceed to try what you said. though i have a question: is it possible for the bootloader to be overwritten with a previous version?
and what does it mean when the phone outputs "hab check failed for boot/recovery/system (etc)" ? i sometimes get those errors when flashing other region (official) roms
liveroy said:
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
Click to expand...
Click to collapse
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
tenjou_89 said:
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
Click to expand...
Click to collapse
Hmm, maybe leave the recovery aside for now and try to boot a 4.3 ROM (stock one).
Also you cannot downgrade to bootloader afaik, but the newer ones work fine with 4.3 ROMs.
I don't think that the eMMC got damaged, cos nothing will work then.I really can't say if your problems are coming from the water dip or it's just the Moto G being stubborn if you do even one thing the wrong way.
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
what about the ram? a guy on some other forum said that maybe the ram got damaged to a point where only a part of it is now writable, and it gets flooded just before the complete boot up of the system, wichi is why the phone would then crash and display a black screen. what do you think about that theory?
i am going to try with 4.3 roms now. oficial and custom and post the results.
liveroy said:
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
Click to expand...
Click to collapse
yes, exactly that way.
edit: except i have images instead of bins, so:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot bootloader
Typo of mine, should be .img
About that RAM theory, it really doesn't sound viable to me, but who knows.
If I have to guess, I would say it's probably some crucial component failing to initialize properly and the kernel halts the system.
hmmm do you know of a method of checking for the conditions of individual hardware componets through a pc? like probing or running a full check of everything, not just the emmc..?
These seem not to work.
But if you find the correct details, maybe there is something to test in the service menu.
I have the same problem without water damage. I guess its the 4.4 OTA bug.
Tried reflashing the firmware i already have but of no use.
Mine shows the Blue Motorola logo and then doesn't show the boot animation.
Please can anyone help me out :'(
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Hey, I'm in a similar position to you. However, I went about it with a slightly different route. The chip used in this phone is the MediaTek 6582 (I think?). I downloaded some tools from a thread on here that includes the 320 rom and the necessary software for flashing. I've flashed MediaTek devices before, the Huawei Ascend G610 and G700, both successfully. This one is giving me headaches, the damn device keeps disconnecting. HOWEVER, if you're lucky and you don't have the same problem with disconnecting hardware, you should be able to flash a new rom via the software. It'll take a while though. Also, I don't know what'll happen to your IMEI afterwards, so that's another possible headache (both the G610 and the G700 lost their IMEI info, but I'd taken steps to back them up beforehand so I could just restore them; here, there's no option to backup).
Here's the thread: http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
Let me know if you need help. I'm screwed in that the damn phone keeps disconnecting. Similar to you, no fastboot either. Plus, no RUU for this HTC. Hell, the internet barely knows this flipping phone.
Cheers, and good luck.
blitz9826
0Camus0 said:
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Click to expand...
Click to collapse
Ditto!!!
Hey guys I am having the exact same issue, luckily for me it is my Mrs who done her phone in and not mine . She has the HTC Desire 320, I believe she tried to root it on her own without even asking for advice, I think she used the app Kingo Root, she said she went to remove the root but when she uninstalled the app it didn't remove it. (LOL I told her well perhaps that's because there will be some way of removing it, aside from just uninstalling the app), anyway she proceeded not to care and carried on using her phone as normal for maybe a week or two at most, then about midnight one night, came down and said to me,
"my phone had an update and on restarting I just get a dead android, if you press the power button you get some options so I clicked erase"
Click to expand...
Click to collapse
I was like nice so basically you F***ed it!!!!, and for about 2 weeks now I have been endlessly reading post after post, forum after forum, trying rom after rom, RUU, all kinds of things.
Here is the situation, the phone will boot as far as the HTC logo, it will get stuck in a short loop and reset itself 4/5 times repeating the HTC logo, eventually it will end up at the dead android pic (the android on his back with the red exclaimation mark triangle) with the words 'no command'. From here I can press the power button once to get a list/menu of items (What I assume to be the recovery menu). I can backup data, I can restore the backed up data (both of which do nothing as I guess there is nothing really to back up), There is an option to restore from sd card (which I have tried numerous roms and to no avail have any been successful), I can erase the cache and I can also erase everything and recover, the erase side works fine, I did notice in each of these menu that if you press volume up to activate them and then press the power button once, then the writing dissapears and the android proceeds to have his moving atom type thing in his belly, saying 'erasing..', however even with them completed successfully, it still does not restore.
NOTE!!! If you choose the erase and restore method, once activated with volume up, press the power button to get the spinning atom and erasing... message, when this finishes the phone will reboot, it goes to the htc logo, resets itself, goes to the logo again and then just stays at a black screen (almost like a frozen state, I left it for quite some time and it never changed).
I should also note, which I didn't to begin with, but no matter how long I hold the volume down and power button, there is no such hboot/fast boot menu at all, if you hold the volume down and power button even after it displays the htc logo, the phone just proceeds to endlessly reset and loop through the same process forever.
The only thing I can seem to access with little success, is the ADB CMD prompt through the Android SDK,
Code:
adb devices
will indeed return the device (a set of numbers with the word sideload beside it)
Code:
adb usb
Apart from the odd fluke, this has seemed to fail everytime with either an error about a protocol or an error stating 'closed'
Code:
adb sideload "ROM_FILENAME.ZIP OR .IMG
Occasionally this will throw the protocol error, but generally succeeds and displays the 100% most of the time, however the phone doesn't even try, it just almost instantaniously returns the error message :
Code:
[B][I]Installation Aborted (APPLY_ADB_SIDELOAD)[/I][/B]
NOTE!!! That the android lays on his back with this error, but it only says error below not no command.
I am pretty sure that I already came across a solution very similar to the one you posted above, and I just couldn't get it to recognise the phone, the only way the RUU would work, was by completely removing the battery and plugging in the usb, however without the battery in the phone, it just constantly beeps via usb, so I guess it turns on, then off, then on, then off, forever!!! So the RUU fails everytime, if I leave the battery in and try, the RUU program does nothing whatsoever! So I am at a complete loss with it now.
Cheers
GunnerJnr
Any luck with unbriking the HTC?
Maybe this is the solution, good luck.
Search: How to Unbrick every MTK China Phone ! Preloader / SP Flashtool Fix [HD] on Youtube
Responds please.
http://forum.xda-developers.com/showpost.php?p=64659997&postcount=16
I think that you no tell true because I tried this method with volume keys and nothing. Flash tool still show error. Its impossible to write android without battery. I think really put your phone to rubbish or sell as lcd+digitizer parts I think just we must waiting for new custom rom flashable via stock recovery. 320 is still new model and developers no moke any custom rom. So maybe only HTC service may help, only in HTC Factory peoples know how install android and bootloader on hard bricked device.
I was trying to root my Huawei Mate 9 using SuperU and TWRP, i got TWRP to work but when I put SuperU on the phone I couldn't find it (being first time ever rooting a phone) and somehow I came to the conclusion to go to wipe and wipe, i did that and restarted my phone and it was blank, it fully started up but only the bottom buttons were showing and if i changed the volume that would show but noithing else was there couldnt do anything but turn it on and off and change the volume, so now I'm trying to flash a firmware onto my phone so i can at least use it becasue I need it and nothing is working, ive put a update.app onto a sd card and tried using that and just I don't know what to do, I can load bootloader and get into TWRP and I can get into eRecovery but when I try download and recovery it just spits out an error saying 'getting package info failed'
Please help I'm not sure what other infomatiuon you need so just reply with anything and I'll reply right away thank you :c
Sirsyorrz said:
I was trying to root my Huawei Mate 9 using SuperU and TWRP, i got TWRP to work but when I put SuperU on the phone I couldn't find it (being first time ever rooting a phone) and somehow I came to the conclusion to go to wipe and wipe, i did that and restarted my phone and it was blank, it fully started up but only the bottom buttons were showing and if i changed the volume that would show but noithing else was there couldnt do anything but turn it on and off and change the volume, so now I'm trying to flash a firmware onto my phone so i can at least use it becasue I need it and nothing is working, ive put a update.app onto a sd card and tried using that and just I don't know what to do, I can load bootloader and get into TWRP and I can get into eRecovery but when I try download and recovery it just spits out an error saying 'getting package info failed'
Please help I'm not sure what other infomatiuon you need so just reply with anything and I'll reply right away thank you :c
Click to expand...
Click to collapse
You can start over by flashing the full update.zip.
What exactly did you wipe?
Anyway, you can flash back stock firmware using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Help Help Help :
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got TWRP cant install.Because. OEM locked.
It flashed. Great. But now IT STILL DOESNT BOOT. I'm stuck at NO COMMAND, it keeps restarting after 20-30 seconds of showing no command. and it's looping all over.*
i flashed stock firmware.It is flashed.Then reboot.Then install system update.Then Erasing.Then rebooting.Then NO COMMAND.Then reboot itselve recovery mode.Then i wiped factoory and cache.Then press rwboot to system.Then Samsung Galaxy S8 Plus.Then install system update.Erasing.No Command. etc. Keeps rebooting. its on NO command screen. It just restarts. Doesnt boot. I want to enable OEM Unlock. I installed combination binary. But not appear in Developer Mode.
i flash atock with Kies emergency.I flash different stock firmware from updato.com. But nothing happend.
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
JeffDC said:
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
Click to expand...
Click to collapse
KIES says that. (THR) Stock. i downloaded it and flashed with Odin. Then reboot. Then system install update. Then Erasing. Then reboot and No Command! 30 seconds keeps rebooting itself 30 seconds interval Random.
I did factory format, cache clear. then the same problem. i want to install twrp recovery with oden. It says Oem Lock. Not allowed. But i flashed Combinary file. I can get into system and i to developer mode but dosnt seem OEM UNLOCK that ll do enable it.
Ok mate, but if you press Vol- + Bixby + power for couple of seconds, can you access to download mode? If you can, I think you'll have to install the firmware all over again.
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Did OP find a fix to this problem?
I am experiencing a similar issue. Picked my phone up to find had randomly gone into a boot loop. Tried soft reset, cache wipe, factory reset - all successful but the phone would still reboot and be stuck on device model screen. Next I decided to flash the device with stock firmware. The flash passed in Odin, the phone then rebooted, loaded to device model screen, then a screen appeared saying "installing updates" which would make it to 25% then crash. After this the phone keeps booting, shows a screen with a dead android icon and says "no command" or "error". I have tried to flash the device using Oreo and Nougat firmware but have failed every time (although the flash did pass in Odin)
Any help would be greatly appreciated as I would rather not buy a new phone due to a random hardware fault which is out of my control.
southsideswaggar said:
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Click to expand...
Click to collapse
This is perfect if you have soft bricked your phone!
follow this video maybe it help you
https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395
https://www.youtube.com/watch?v=VTi3uBkpJic&t=155s
So I decided to upgrade to the Android P beta DP3 right from stock (most recent version) and all went seemingly well. I downloaded the ROM, installed it with the local upgrade, pressed the restart button that appeared (instead of manually shutting it down) and booted right into P.
I noticed that everything was still installed, and I'd rather start fresh, so I booted to recovery and selected the wipe data option, which removes all userdata, as suggested in the official installation guide.
After wiping I booted back into Android and got the normal popup to enter my pin, accept license agreement and accept/decline a bunch of things like notification offer and stuff. After this, however, I end up in the 'Checking for updates...' screen which is taking ages (25+ minutes) and never seems to finish.
At this point I don't really know what to do. I've tried both wifi and though the mobile network, neither seem to work. There also isn't a skip button or anything as far as I can see.
Given that all data is wiped debugging also isn't enabled so adb appears to be out of the question. Booting into recovery also doesn't appear to work, as I always end up just starting Android. And last but not least the bootloader was still locked as this wasn't needed for the P beta.
I've tried making a thread on the official OnePlus forums, but it seems I'm still lacking in rep over there.
Any suggestions?
and i m pretty sure before trying that u should have atleast enabled oem unlock just to be safe T_T
Yup, I guess so too. Ah well, I posted the issue in multiple places, including as a bug report on the OnePlus forums. I'll just wait a few more days to see if anyone has an idea and otherwise I'll send it back for repairs and see if they can do something.
Hi,
reboot into Recovery and wipe data.
After a further reboot follow the setup wizard to the point where you can login to your Google Acc. Skip everything from this point on and you will get to the Homescreen. Wait a couple of minutes an you will be asked to finish the setup wizard.
I always have this annoying bug, too...
Thanks for the suggestion. Unfortunately I can't seem to boot into recovery anymore. No matter what I do, no matter the order of volume down+power (volume first then power, power first then volume, or pressing them exactly at the same time), nothing seems to actually get me into recovery. In each and every case it just boots straight to the Android setup. It also doesn't appear that I'm doing anything wrong, because I've got a few older Android phones here and on each one of them I can easily get into recovery.
I've also made an official bug report, so lets see how that pans out. But if anyone has any other suggestions in the meantime, I'm all ears.
Xylon- said:
Thanks for the suggestion. Unfortunately I can't seem to boot into recovery anymore. No matter what I do, no matter the order of volume down+power (volume first then power, power first then volume, or pressing them exactly at the same time), nothing seems to actually get me into recovery. In each and every case it just boots straight to the Android setup. It also doesn't appear that I'm doing anything wrong, because I've got a few older Android phones here and on each one of them I can easily get into recovery.
I've also made an official bug report, so lets see how that pans out. But if anyone has any other suggestions in the meantime, I'm all ears.
Click to expand...
Click to collapse
U have corrupted u r data partition. You have to flash fastboot flashable rom via fastboot mode but u will loose u r all internal data too.
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/