OP3 bootloops - posibility to unlock bootloader without ROM? - ONE Q&A, Help & Troubleshooting

[EDIT: Oh ****, shame on me, i really posted it in the wrong Sub-Thread, can someone pls move it to the right one? I'm sorry ]
Hello Guys i am fixing some software issue related phones. Have 2 OP3 here with bootloops, one is almost fixed (has only the dm-verity problem and the focussing issue, hope RMA will fix it, its out of warranty)...
... and one which don't want to live
Issue: Only booted into recovery, after several unbrick methods and after some random reboots i managed the phone to boot into android but with a lot of random reboots and messages like "android.phone.system" stopped working. The problem is, i forgot to check "OEM unlock" in the settings. Now the phone won't boot into android and i am not able to unlock the bootloader. I think there is something messed up with partitions and the whole file system.
I already flashed the ROMs in the unbrick guides and flashed over the newest Version (8.0.0). Does anyone know how to unlock the bootloader without booting into Android? I would like to erase everything on the phone and flash everything into a clear one, hope its not a hardware related issue.

Related

One plus get stuck in bootloop

Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Odysseus1962 said:
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Click to expand...
Click to collapse
Hi, i dont know what happened before because the Phone is not mine, is of the gf of a friend. I can reach fastboot and recovery and I also changed the recovery to twrp and installing a new rom, but bootloop still is running. What can i do else?
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Kevin1705 said:
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Click to expand...
Click to collapse
I dont have a backup, so i also tried yet everything you said. I dont have to save datas, so i flashed everything new, but still dont work. I also tried to flash everything from oneplusrecoverytool that in any difficult situations helped me, but in this case it did not worked. Is there any radical solution to get this Phone working? (i can install twrp and reach fastboot, but after installing something, it's always in bootloop. ?
i have the same problem , don't know what to do , i even used the tool to return to stock
maybe an overheat problem? i don't know
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Odysseus1962 said:
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Click to expand...
Click to collapse
i tried your solution but nothing changed i also tried this procedure http://forum.xda-developers.com/one...lusrecovery-tool-v1-0-restore-t2991851/page23 , the process is success but at the reboot the phone is always in bootloop
still same problem here =/
Download the latest fastboot image from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 follow step #8

In a right mess trying to return to stock

Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?
What Firmware did your XT1032 originally come with? or which Carrier?
Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !
I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​
Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !
Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?
OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!
@aneng64 - You have not done what I told you to do. Read my post again.
Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.

[Completed] HTC One M9 Major Issue

I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed

How to downgrade HTC U11+ from Android Pie?

I have HTC U11+ TW version. Ever since I got the Pie update, my phone is freezing a lot. I need to force restart it 10+ times a day. I tried factory reset, clear cache, etc. Nothing works. I did not have any experience with flashing, but I have been reading a lot. I have my bootloader unlocked with S-ON.
My current build number is 2.15.709.1, since I wanted to downgrade, I tried flashing stock image HTC_U11+_TW_1.24.709.999_Images_OTA using fastboot (no TWRP). My phone went into a bootloop when I did that. I think this is because I can only flash an image with the same build number? Anyway, I flashed a HTC_U11+_TW_2.15.709.1_Images_OTA image and my phone is back to where it was, Android Pie (no bootloop), but still freezing a lot.
I found the HTC_DevInfo_Tool.zip tool on this thread https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481, but I am not sure if it will work on my phone.
Can someone advise what should I do to downgrade? Also did anyone face a similar problem after the update?
this is a U11 forum, you might ask in the respective forum for your phone
Yes i have similar problem .please advice this topics

How to downgrade HTC U11+ from Android Pie?

Already created thread in the wrong place https://forum.xda-developers.com/showthread.php?t=3952280
I have HTC U11+ TW version. Ever since I got the Pie update, my phone is freezing a lot. I need to force restart it 10+ times a day. I tried factory reset, clear cache, etc. Nothing works. I did not have any experience with flashing, but I have been reading a lot. I have my bootloader unlocked with S-ON.
My current build number is 2.15.709.1, since I wanted to downgrade, I tried flashing stock image HTC_U11+_TW_1.24.709.999_Images_OTA using fastboot (no TWRP). My phone went into a bootloop when I did that. I think this is because I can only flash an image with the same build number? Anyway, I flashed a HTC_U11+_TW_2.15.709.1_Images_OTA image and my phone is back to where it was, Android Pie (no bootloop), but still freezing a lot.
I found the HTC_DevInfo_Tool.zip tool on this thread https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481, but I am not sure if it will work on my phone.
Can someone advise what should I do to downgrade? Also did anyone face a similar problem after the update?
I found someone tried what I wanted to do here
https://forum.xda-developers.com/htc-u11/help/error132-signature-error-downgrade-htc-t3948079
Looks like it wont work?

Categories

Resources