So today has been.......Less than fun. Started off wanting to update my phone so i made a TWRP back up, downloaded the latest Oxygen OS and that's where my problems started. I accidentally flashed the Android 12 build. Immediately lost my data and TWRP recovery so I stupidly tried to flash it like I did before without stopping to think if there may be anything different in how it's done Android 12.....After it said it was successfully flashed I went and restated the phone.... and now It's stuck in crashdump mode or fastboot mode.
I originally I thought I would be fine. I've used the MSM download tool before and there were plenty of guides about this exact problem but for some reason it failed (my only guess is because I used the EU version and my phone was originally a T-mobile version that I converted to the EU version? I said that the Image didn't match so that was my best guess) and now the phone isn't even being recognized in ADB when in fastboot (I checked before I ran MSM) so I can't even try to flash the other one....
If anyone knows of ANYTHING that might work, that would be amazing!
P.s. Trust me, I KNOW this is all on me and I know I should've done more research before going through with it but I figured it would be just like every other dirty flash smh.
Blackest Pain said:
So today has been.......Less than fun. Started off wanting to update my phone so i made a TWRP back up, downloaded the latest Oxygen OS and that's where my problems started. I accidentally flashed the Android 12 build. Immediately lost my data and TWRP recovery so I stupidly tried to flash it like I did before without stopping to think if there may be anything different in how it's done Android 12.....After it said it was successfully flashed I went and restated the phone.... and now It's stuck in crashdump mode or fastboot mode.
I originally I thought I would be fine. I've used the MSM download tool before and there were plenty of guides about this exact problem but for some reason it failed (my only guess is because I used the EU version and my phone was originally a T-mobile version that I converted to the EU version? I said that the Image didn't match so that was my best guess) and now the phone isn't even being recognized in ADB when in fastboot (I checked before I ran MSM) so I can't even try to flash the other one....
If anyone knows of ANYTHING that might work, that would be amazing!
P.s. Trust me, I KNOW this is all on me and I know I should've done more research before going through with it but I figured it would be just like every other dirty flash smh.
Click to expand...
Click to collapse
You can't use TWRP on OOS 12, though you might be able to install the OOS 12 zip using TWRP if you're on OOS 11.
Check your drivers if you can't connect to the phone in bootloader mode. You might need to simply reinstall it (I've had to do this a number of times).
You might be able to switch active partition it might save you I had something similar happen changing partion helped me get back into adroid
Related
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
After searching around and not being 100% sure on how I should go about fixing this particular bootloop I decided to post a thread. Bootloader unlocked, phone unlocked, FRP unlocked, and TWRP installed. Can't seem to get the phone recognized when plugged in no matter where I'm at and hisuite recovery doesn't work, nor does the erecovery or whatever it's called. I had the phone running just fine with supersu but after installing my usual Xposed/Busybox and rebooting I got caught in a bootloop. (might have been caused by being on Oreo and having some problems with a version made for Nougat or something). I've seen there are various ways to exit the loop and at this point I'd be open to any but I do notice some posts saying they almost bricked their phone while doing so. Currently on my microSD I've got a hwota update I was going to try to use. I've got no backups in TWRP either because I'm irresponsible (my fault). What can I do to just wipe the phone, reinstall any version of android and get back to where I was at. I'm a little new to this as I've only ever rooted my tablet. Thanks for the help and all the info I've taken from this forum before and hopefully now. Forgot to mention I don't know my full device number only MHA-L29 in the US.
Ok Well after laying in bed and thinking about it I wound up running HWOTA8 from TWRP since I could access that. Seemed to just bring me back to eRecovery, and I factory reset my phone. I'll reinstall TWRP and flash supersu then make a backup and try again. Not sure what happened but I seemed to be in a pretty good spot since I could access TWRP even though my phone wouldn't show up on my computer while in fastboot/Recovery mode.
edit: oh I got a new problem now. I'm on testkeys firmware, camera, sim, and bluetooth work but I can't update from 7 back to 8. I'll do more testing around before bothering to unlock bootloader or install TWRP.
I've been trying to follow the guide in this thread but to no avail. I just get software install failed and then I have to start again.
Well another day of searching google and XDA trying to figure out guides and I don't think I'm any closer to a solution to getting off test-keys. Some seem to suggest that you need to go back to MM, some suggest running HWOTA, some suggest the three button recovery and others say that won't work at all. I'm not sure I've ever felt this confused haha. I'll keep at it but there has to be some way to get to a build that has the updater on it since that's all I seem to be lacking to get off test-keys. I can even search the settings for the updater but when you press it nothing happens. It's like they completely removed any sort of updating this build can do.
KittyCat5eUTP said:
Well another day of searching google and XDA trying to figure out guides and I don't think I'm any closer to a solution to getting off test-keys. Some seem to suggest that you need to go back to MM, some suggest running HWOTA, some suggest the three button recovery and others say that won't work at all. I'm not sure I've ever felt this confused haha. I'll keep at it but there has to be some way to get to a build that has the updater on it since that's all I seem to be lacking to get off test-keys. I can even search the settings for the updater but when you press it nothing happens. It's like they completely removed any sort of updating this build can do.
Click to expand...
Click to collapse
What is your full build number? Please, post screenshot.
5[Strogino] said:
What is your full build number? Please, post screenshot.
Click to expand...
Click to collapse
Model: MHA-L29
Build: NRD90M test-keys
EMUI version: 5.0.1
Android version: 7.0
I believe I was originally on some variant of MHA-L29C567 since I'm US based and its the dual sim version
I've tried using HWOTA a few times to either upgrade/update or rebrand and no matter what I choose when my phone restarts to install I just get software install failed. Usually I'll have to run through first time setup again. I've read that some people said this particular issue had to do with the update zips but mine seem to be named correctly so all I can think of doing is getting another firmware and trying again with that.
haha okay so I found out I was putting the update zips in the wrong folder. I fixed that and re ran HWOTA. update started/finished and my phone started booting and restarting a lot then went into erecovery. I'm downloading the update package right now and it's slow as hell but it's moving. And that failed leaving me to boot a few times and then get back to erecovery. I'll try getting into fastboot or recovery.
Edit: Well that seems to have resolved itself now. After having the erecovery fail I wiped/factory reset and booted the phone into oreo 8.0.0.321 with all the apps and updater. Thanks to everyone who dropped in and I'll be getting emails if someone replies that needs help too. I'm not very knowledgeable but I can give it a shot.
Does anyone know what changed regarding wifi in Android 8 or MIUI 10?
I was happily using LOS 14 for a while (after having officially unlocked my bootloader at some point in the past, but became curios and wanted to try out the new MIUI 10. While I could not find anything official, I did find this chinese dev ROM (I DO NOT RECOMMEND YOU FLASH THIS). I flashed it, wasn't that impressed and then decided to try LOS 15 based on Android 8.
That was a bit too unstable for me, so I tried reverting back to LOS 14.
I did so using a backup I made to my pc (I did `adb backup` while in TWRP and selected every partition I think). After booting into LOS14, things seemed to crash an awful lot.
At this point I realized wifi wasn't working. It showed a MAC Address of 02:00:00 I think, but no networks were found. I tried restoring my phone using MiFlash normally. I then tried restoring it using Qualcomm's download mode. Older MIUI versions would not boot anymore (although I did manage to boot an old version of TWRP made for the pre-Nougat bootloader). I tried LOS14 again, and attempted using fastboot to erase various partitions (such as the bluetooth and modem partition, and then manually flashed the image again. Still no wifi.
Does anyone know what could have happened? My bootloader is still unlocked, and even downgrading the device to an old version of MIUI using Qualcomm mode did not make it work again? How come LOS15 and MIUI 10 are able to use wifi without problems?
tl;dr WiFi stopped working on any rom other then Lineage OS 15 or MIUI 10.
I recently ran into the issue during custom rom work. I reflash the stock android ZIP, it starts booting, then I hard reset it with the power button and try to reach bootloader again. This, as it turns out, is terrible to do if you want a fast setup. The moment it starts and you reboot it, the boot image is corrupted (that's my guess) because escaping the boot screen during a clean flash bricks your phone. If you're reading this, it happened to you as well.
The answer is so flipping obvious and it took me an hour to figure it out - nowhere on the internet is there a "solution" for this problem, no matter how frequent it is. But there are lots of people who deal with this, whether still on their factory images (like the Pixel 3 EDL issue) or like me bouncing from custom to stock. So here's the answer:
ALL YOU HAVE TO DO IS SIDELOAD THE CURRENT SOFTWARE OTA OR A BETA OTA FROM ANOTHER FUTURE VERSION.
It doesn't recognize timestamps before your current software, so you'll need to assume you're on the latest of whatever you're on and do that. Future versions work as well, so if you wanted to reach 12 in one shot, your phone's bootloader would fully accept it as long as the file isn't corrupted. If you need a sideloading or flashing guide, here you go.
For me, I flashed the latest build of Android 11 (August patch) and rebooted during the boot up. What I did was download the OTA of the same exact file to my laptop, and entered adb sideload coral.xxx.x.zip. (The name of the file) It ran all the way through and it started up perfectly normal.
I hope this helps someone!
P.S. I don't have any pictures or tutorials, I only wrote this to help others understand what happened and how to fix it. Probably wouldn't have needed to say it if the forum for it existed.
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?