Database Develop

Nexus 6 Reboot/Optimize Apps after 5.X update

Hey there,
I got quite a serious problem. Since i updated to 5.1 my phone sometimes suddenly restarts, followed by a message which says "optimizing apps", which ranges from 30 to 150 apps. At first, it was no big problem, now it occures nearly every 10 minutes, so currently i can't really use my phone.
What i tried to do:
Factory reset, reflash 5.0 - 5.1.1 (every single image available)
The problem is still there.
Now my question, is it a Softwareproblem, which will be updated soon (should i try Android M (what about the warranty?))?
Or is it quite a serious hardwareproblem (i read somewhere that it could be because of overused RAM modules)?
I tried to use the searchengine, but i didnt find a specific thread in this subforum.

The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though

danarama said:
The optimising is a software issue caused by a random reboots. The reboot itself could be caused by anything though
Click to expand...
Click to collapse
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.

Haabiii said:
Thank you for your quick reply. I continued reading and as it seems there are quite a number of users with the same problems as me. Although no one has gotten a solution till now. It doesn't matter if it's a Nexus 4, 5 or 6 but all the Nexusphones seem to be affected once updated to 5.1 or newer.
Unluckily sending it in to repair is not a good solution because they told me it would take 2-4 weeks which is not possible for me... How can Google not release a proper update after 5.1.1 which fixes it? Are they so focused about Android M? I still can't overcome myself to install the Android M because i fear to lose my warranty.
Click to expand...
Click to collapse
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.

Evolution_Tech said:
Dude, it's a Nexus. Warranty isn't an issue as long as you return to stock and relock before a warranty claim.
Click to expand...
Click to collapse
Thanks, I didn't know that.
Evolution_Tech said:
If flashing a factory image didn't fix it, either you're not wiping or formatting the cache correctly or you have a hardware issue.
Click to expand...
Click to collapse
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
Evolution_Tech said:
Don't be so quick to blame Google when thousands of others, myself included, have taken the update without issue.
Click to expand...
Click to collapse
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.

Haabiii said:
Thanks, I didn't know that.
I did the factoryreset via fastboot, also i used the nexus toolkit to do a proper stock reset so i don't quite get how it could be an incorrectly done reset. So the hardware just breaks during the updateprocess?
I am usually quite quick in blaming others if there are also many people with excactly the same problem, sudden reboots with app optimization right after the update to 5.1 or 5.1.1, some even before at 5.0 or 5.0.1.
I'm going to try the Android M Update, maybe that will help.
Click to expand...
Click to collapse
Personally, I'd boot to bootloader and do:
fastboot format cache

Evolution_Tech said:
Personally, I'd boot to bootloader and do:
fastboot format cache
Click to expand...
Click to collapse
Already done and i also reflashed the whole cache image. I hope the Android 6 Update will help solve my issues. The problem is, that i usually get really upset about little stuff like that just because i don't get why it's happening.

I updated monday evening to the Android M Preview, for now it only restarted once to, as it said, install a update (?), since then no reboot at all. It worked like a charm yesterday. I really hope the problem is fixed that way.
Just wanted to let you know if you have a same problem.

[Q] Android Process FCs and General Device Instability After Flashing MMB29V

Hello all. Generally I've been able to troubleshoot all my Android issues on my own. Most of the time someone has had the same problem (amirite?!). However, I'm stumped and could use a little help from the community.
I've been going along on Marshmallow with FK as my kernel. Generally, waiting a bit to take an update til SuperSU was confirmed all working correctly and that there wasn't any surprises. I had been putting off the MMB29V update for a bit just because everything was running fine and I had no real reason to upgrade. Well, one day I started getting a few FCs and things seemed a bit off performance wise so I decided that I'd go and move on to the next release.
Now, since I've had my N6 I really haven't had the need to run a custom ROM which is completely unlike my old habits on the S3. I decided that it's been a while since I've checked out AOSP so I flashed MMB29V using the batch file with no issues and then DU and their recommended GApps. Here's the first hint of an issue. When I loaded up the OS for the first time I got acore and phone FC's constantly. I instantly thought that I didn't wipe something or that I had a bad zip. I re-downloaded everything and checked MD5s. Everything looked good and after the flash I was able to get through the setup wizard without any issues. As I was sitting there checking out the tweaks and options available I started getting FCs again. It seemed related to Google apps. I did the whole process a second time and still had the same issues. Basically it seemed like at some random point in time the FCs would come and then shortly after the device would be highly unstable. I'd get random reboots, etc. Looking at the stack traces the errors seemed like odd NPEs and native errors.
I decided that AOSP wasn't going to cut it right now if I was going to have a relatively unstable phone and went to flash completely back to stock. Much to my surprise I still got the same errors! Apps like Feedly would never even be able to open. They would just FC on launch. The device hot reboots. The phone process seems to crash during most calls. I triple checked my MD5 on the download from Google. Made sure I wasn't doing something super stupid. I even tried doing the factory flash, booting to the welcome screen, then powering down, going to stock recovery, and factory resetting before continuing. All the same errors.
I've flashed back to complete stock a few times before without any issues. I've been able to flash system.img without any issues. Now it seems like the phone is completely unstable no matter what I do. I get the "Your device is corrupt. It can't be trusted and may not work properly." (red) message when doing a cold boot.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?
I've burned through two backup cards of Google 2-Step backup codes! I'd really like to figure this one out!

mikejr83 said:
.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?!
Click to expand...
Click to collapse
You could read the OP of the following thread and flash a debloated and prerooted ROM.
http://forum.xda-developers.com/showthread.php?t=3059493

I guess I'll try that. I'm still scratching my head why a flash from the factory image is still suffering from FC's and general instability. It also concerns me that I get the corrupted message at boot. It would be one thing if I flashed factory, then put a recovery, kernel, and rooted, but I haven't done that.
Hopefully I'll get a chance to try that this evening. Thanks for the link to that image. It's pretty much what I run when I take an update.

N, n, ne, necromancy!
I brought this thread back to life because I've never been able to solve the instability issues since my last post back in March.
Having some free time lately I decided to nuke my device and start again. I first grabbed the latest stock image and flashed stock. Then I downloaded the latest TWRP and Dirty Unicorns and decided that I'd give it a whirl again. I had FC issues right after the first go at it. I decided to try another GAPPs and do it again. I was able to get through setup. It took a few hours but the FCs started again.
I decided that I would try factory resetting the device and then starting a setup. I remembered that on my previous devices that I sometimes would have to do an immediate factory reset after flashing.
Well that did crap. FCs are random. The device is stuck booting now after a hot reboot.
How can I debug this? What do I need to grab from a logcat? Is there a way to run something like memtest to see if there is a bad section of RAM and something against storage to see if there is a bad sector?
This is frustrating as hell!

Moto X always boots into recovery unless I manually choose normal startup each time

I rooted my XT1052 straight after updating to 5.1, a few years back. As a result I have never been able to install the OTA update (the one which fixed Stagefright, so far as I'm aware it's the only OTA Moto did after the 5.1 update.)
I've been unable to install a few apps recently due to SafetyCheck failing on the rooted phone, so yesterday I decided I would unroot and return to stock, which would also enable me to install the bugfix OTA. (And with Magisk, nowadays we can keep root access without a modified system partition.)
I didn't have a stock image (or I had an image of some sort on a hard drive but couldn't remember its provenance). Moto's download page has images for the XT1053 but not the XT1052… Eventually I found firmware.center, where (I thought) I found the right image.
However, when flashed it (following the step-by-step guides which are the same on various pages, including Moto's own instructions), it failed to flash the `system` image. I got messages about invalid block sizes (IIRC) and then an error saying the image was corrupt (it wasn't; I checked the MD5).
This left me unable to boot. So I downloaded LineageOS (I'd been considering switching to LineageOS anyway to get Android 6), and was able to flash it from TWRP without any issues (other than the fact that a newer version of TWRP is required than the one published on their website…)
All well and good – except that now, when I turn my phone on it goes straight into Recovery (TWRP). Initially I could only get System to boot by starting the bootloader (Pwr+VolDn) and selecting 'BP Tools', which would cause it to boot normally. (I found this by trial and error.) Now, after re-flashing the boot image, It also works if I select Standard Boot from the bootloader. But I still have to select it manually. If I just turn the phone on normally, with the power button, it always boots into Recovery. Also, all the 'reboot' options from fastboot/adb or TWRP all boot to Recovery.
Now, I think I know what I did wrong. The stock image I downloaded was 'XT1052_GHOST_RETGB_5.1_LPAS23.12-15.5-1_cid7_CFC.xml.zip', but my system version before was 5.1_LPA23.12-15.5. I just assumed that the 5.1_LPAS23.12-15.5-1 version was a minor update – likely with the Stagefright OTA installed – so I went for that. But probably I should have gone for the exact version I already had installed.
Searching these forums and the wider web, I haven't found anyone with the exact same issue. But from similar issues, I decided I needed to re-flash the partition table (gpt.bin). I took the gpt.bin image from an older 5.1 ghost ROM I had saved, but I'm not able to flash it – the bootloader shows security warnings when I try.
So I'm stuck now – I have tried pretty much everything I can think of.
If anyone has any ideas I'd be very grateful!

I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?

Alexjrbr said:
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Click to expand...
Click to collapse
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.

cmjs said:
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
Click to expand...
Click to collapse
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done

Alexjrbr said:
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Click to expand...
Click to collapse
Woohoo! Well done!
Look forward to seeing your solution

cmjs said:
Woohoo! Well done!
Look forward to seeing your solution
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644

Moto X 2014 XT1092
Alexjrbr said:
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Click to expand...
Click to collapse
Can this solution be used in my case. I have the same problem of the phone booting to recovery on start up...

OTA update endless fail loop PPWS29.69-39-6-4 on Magisk (un)rooted X4

I have two (identical) X4 1900-1 Android One phones , both were rooted with Magisk patched boot image on PPWS29.69-39-6-2. I was able to restore boot image with Magisk Manager on one and the January 1 PPWS29.69-39-6-4 OTA update completed successfully, I reinstalled Magisk per tutorial, root is present and Safetynet passed. The other one became stuck in a kind of updating loop for this OTA prior to restoring the image with Magisk, the update failed on "Step 3 of 6", then starts all over again, ad infinitum, causing battery drain and slowdown. It started this before I restored the boot image with Magisk but fail is continuing since doing so and after a reboot. Automatic updates were turned off in Developer Options, but it still tried to install the update before notifying me that it was available. One difference after restoring boot image with Magisk is that the phone is no longer showing the update progress page--when you tap System Updates the CHecking for Updates flashes briefly and then a toast says Software Update Unsuccessful. That message comes up every few seconds.
My past experience with failed OTA updates on other devices has been the update process stops with one failed update, never tries again and I had to flash manually. Wondering about the best way to address this issue is. One of these phones is my "backup" device, so I have some wiggle room on what to do. Should I (a) flash stock back on the problem phone and let it go through the several security updates, or could I possibly restore a TWRP backup from the updated phone on the problem one? I did a similar restore years ago from one Moto XT926 to another and it worked, but I believe the restored phone might have acquired the serial # of the donor.
I took logcats before and after unrooting, but had trouble uploading one of them. I'll try again.

I spoke a little too soon on the one that "successfully" updated. It is unable to complete phone calls with the same SIM that works in the one that keeps giving the failed update message. Calls just end as soon as send is pressed, or hang trying to connect. In Settings it shows the correct phone number etc., network settings are same as the working phone and this one worked with this SIM a few weeks ago. Some problems connecting to computer visa wifi as well. Beginning to wonder if this is a bad update? Could really use some help here as I don't have a fully functional phone now.

Turns out the "successfully" updated phone is pretty borked. Lots of strange behavior and black screen freezes. The modem/radio seem to have major problems. With no sim card in the phone, the LTE icon shows and indicates signal, but no connectivity. Freezes and blank screens when I hop around in Settings. Wifi connect is wonky. And no phone connectivity with SIM. Looking like I'm gonna have to go back to stock with PPWS29.69-39-6-2, the latest full FW I have.
Has anyone out there had problems with this OTA?
Where can I find the log file from the OTA update, to try and see what went bad?
On the "failed" phone, I was able to find the url for the OTA update (Blur_Version.29.461.4-29.481.10.payton_fi.google_fi.en.US.zip -- PPWS29.69-39-6-4) on the logcat and download it. I've uploaded it to Drive and here is the link is below if anyone needs it. There are lot of error and suspicious messages in one of the logcats from the failed one but interpreting them meaningfully is above my paygrade. I've attached another log to this post. Can someone tell me how to stop the endless updater loop until I can fix the other phone? I am unsure what app/service to disable. I read somewhere there is a way to delay updates on Pie, but it doesn't appear to be a toggle anywhere in Settings.
This is the Android One/Google Fi variant XT1900-1. Flash at own risk!
https://drive.google.com/open?id=151TRLKfmlROCT6f--U4PWRPqmkFyD0T9

The option to force updates is in Developer Options about 10 lines down.
Apparently it defaults to ON.
I have not tested that this would prevent updates since I leave it on, since I want updates.

Force Updates
KrisM22 said:
The option to force updates is in Developer Options about 10 lines down.
Apparently it defaults to ON.
I have not tested that this would prevent updates since I leave it on, since I want updates.
Click to expand...
Click to collapse
Thanks , however that option was turned OFF in Developer Options. Update still forced itself on both phones.

Oh well! It's all google's fault!

Back to stock working so far
KrisM22 said:
Oh well! It's all google's fault!
Click to expand...
Click to collapse
Appears so. Keep reading.
I flashed stock PPWS29.69-39-6-2 and so far things seem to be working--phone, data, wifi.
I'll give a full update on functionality and de-borking when the thing's finished its updates and app installs.
I did notice that in device setup, in the Google Terms the last item "Install updates and apps", states "This device may automatically download and install updates and apps from Google and your device manufacturer...." and there is no on/off toggle!!!! You are forced to accept this "setting", the only option is "Accept"!
Thanks again Google.
I suppose this means that the Developer Options setting is moot.
I would be interested to know if this "(it's not a bug it's a) Feature" is present in Oreo builds?

Remember that google doesn't write android so we can modify it - in fact, google goes WAY out of its way to prevent that - that is why there are so many releases of things like Majisk - google keeps blocking them.
Only a tiny tiny fraction of Moto X4 users attempt any modification of their phones.
You might succeed because you have not yet flashed a custom ROM and thus changed the bootloader and file system from the stock OTA'ed Pie setup. Those that have cannot return. Apparently ever.

KrisM22, would you say that the X4 is a less suitable device than others for rooting? And BTW appreciate your noob warnings, only wish they had appeared sooner. I had already rooted these earlier.
As a matter of practice, I never flash custom ROM or recovery on devices until after they've reached end of OEM support. Actually with the ability to boot TWRP via fastboot I don't see any advantage to installing it but numerous disadvantages. I have unlocked and rooted all my (unlockable) devices, but I may rethink that in light of these recent Android changes. For my next phone I would probably choose a more mod-friendly OEM, if such exists. One+ maybe?

a) you're welcome
b) don't mod this X4 in any way if you are OTA upgraded to Pie.
You might have been able to modify it if it was still on 7 or 8 but I have no idea what the devs are using for
1) bootloader
2)file structiure.
I think, if you have to root, go back to something like a G3, where the bootloader didn't change and the file structure didn't change. Even the Z play had probs around the Oreo bootloader change, but we still could use rsdlite to get back from most disasters.
iow, think pre/pre Treble in any form. It may be, in a couple more years, when Treble has stabilized, that we can get away with modifying things, but on a current phone I would avoid it, UNLESS others have already successfully/repeatedly done it.
I also feel that most of the reason for flashing a custom ROM are gone. People get there, spend a lot of time playing with updates and releases, and eventually go back to stock. There are always a few exceptions, but... As to the various reasons for "needing" root, I feel there are always alternatives. I use Block This! to keep ads out of Brave, BBC app, and APNews app. While there are occasions like can't-edit-build prop, I find I can live without it. It is an adjustment of attitude/expectation. Yes, I have had tons of fun and wasted tons of hours playing with my past phones, it happens I haven't missed it with this one, especially since the sec updates are so recent - I don't worry until it's a year or 2 past.
Once the X4 is on Pie stock, do not modify it in any way.
As to other phones, yes, if you really have to modify it, search the wealth of info that is XDA until you have found a phone that folks have been able to repeatedly get back to stock - be on the lookout for a trail of endless posts about bricked phones and blank flash stuff - a sure sign to avoid it. - This forum is littered with them!
If you have modified a phone: BEFORE taking an OTA, flash phone with latest stock, then let it take the OTA. I had to modify that - I have no idea if you can flash this thing once it is on Pie.

I also feel that most of the reason for flashing a custom ROM are gone.
Click to expand...
Click to collapse
I agree, especially for current devices that are still supported. I'll leave these stock at least until that ends. I actually though it had already reached EOS, so I was caught with my pants down. That said, these phones ran just as well stock/rooted as all of their predecessors I have owned, and as well as when unrooted--until the update fail happened. I may root one if I decide to keep using it beyond EOS. And it's true that most custom ROMs are rarely as smooth and reliable as factory.
Yes, I have had tons of fun and wasted tons of hours playing with my past phones
Click to expand...
Click to collapse
True Dat! But, a hobby is a hobby, and not everything hobbyists do in any field turns out stellar. One reason I always try to have have a decent running backup phone if I mess with a daily driver.
With an EOS device, the risk of a bad outcome is to a large degree mitgated by the greatly diminished value of the device. I have a Moto X 2015 Clark that I've been playing with Randomblame's LOS16 builds on, and it is very usable. Too bad that phone never had good battery life, I liked everything else about it. Might as well keep it rather than sell it for the maybe 50 bucks it might bring. Hell, I only cut my last XT926 loose early last year!

Everything's looking good. After flashing back to stock PPWS29.69-39-6-2, Phone updated OTA to PPWS29.69-39-6-4 and everything appears to be working well. So far no bad residue from past rooting etc.

redwoodie said:
Everything's looking good. After flashing back to stock PPWS29.69-39-6-2, Phone updated OTA to PPWS29.69-39-6-4 and everything appears to be working well. So far no bad residue from past rooting etc.
Click to expand...
Click to collapse
EXCELLENT!!! Great to hear!
Yes, always have a backup!!!
EOS: I was surprised by this update and am now guessing that we might even get one in Mar or Apr. We'll just have to see if that includes 10. But to me a phone is not really "EOS" until maybe a year or 2 after it stops getting updates. I haven't heard of anyone getting hacked. On any phone.
Great!!!

If you are willing, could you do a couple things:
Go to first post edit, go advanced and mark thread as SOLVED.
add a post about how you did it:
1) disclaimer: "Do at your own risk. I am not responsible for anything." or some such!
2. a sentence or 2 about how you did the flash.
3. attach a copy of the bat file you used for the flash.
I think only works if you haven't changed bootloader or file system - NO custom ROM.
Thanks!

Post issue solved etc.
I will happily do that once I've gotten the second X4 straightened out, at that point I'll feel confident it is really "solved".. Probably next week at soonest, I have a minor medical procedure today. I didn't use a .bat file, I fastboot flashed each .img, erase and sparsechunk the old school way. There was a flashall.bat I found on XDA but it was for Oreo builds, had a couple lines in it I was unsure about, and wasn't comfortable modifying it.

Many thanks! Hope all goes well with that today!
If you could provide a log, or list of commands used, that would help!

Update on flashing 2nd X4 back to stock...Flashed PPWS29.69-39-6-2 twice same results: I have wifi/LTE connectivity issues, the wifi constantly connects and disconnects and phone/LTE tries and fails.
There are a couple of threads that discuss similar probles with the X4 and offer various solutions. I may try those, or going back to original Moto Pie ROM or an intermediate build. I also was able to grab the latest Jan. 1 update ROM and that's another option.
The odd thing about this flash is that everything about the phone state was 100% identical to the other X4 that I successfully restored via exact same methods. It would appear that "your mileage may vary" applies. I'll update again when I have new info.

redwoodie said:
Update on flashing 2nd X4 back to stock...Flashed PPWS29.69-39-6-2 twice same results: I have wifi/LTE connectivity issues, the wifi constantly connects and disconnects and phone/LTE tries and fails.
There are a couple of threads that discuss similar probles with the X4 and offer various solutions. I may try those, or going back to original Moto Pie ROM or an intermediate build. I also was able to grab the latest Jan. 1 update ROM and that's another option.
The odd thing about this flash is that everything about the phone state was 100% identical to the other X4 that I successfully restored via exact same methods. It would appear that "your mileage may vary" applies. I'll update again when I have new info.
Click to expand...
Click to collapse
Thanks. modem problems? Dunno... Keep us posted! Thanks!

Are your two One fi, or regular - I bet the motherboards on the two are different, thus the different result.

Both One/Fi. Same baseband versionon both.
Just re-flashed NON-HLOS.bin ad fsg.mbn, same results.
I'm a little baffled by the script commands that follow these flashes to "erase modemst1/t2". One user on this thread claimed omitting (commenting out) those erase commands cured the problem https://forum.xda-developers.com/moto-x4/how-to/android-one-xt1900-1-wifi-sim-stock-t3941837.
I tried the modem flash mentioned above with out the erase commands. No change.
Another suggests:
My XT1900-7 had lost its IMEIs and Wifi connections, even after factory reset.
The solution:
Get XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from lolinet
if you are booting from slot _b, then go to fastboot and flash modem from this FI ROM:
Code:
fastboot flash modem_b NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
Thinking about flashing back to original stock Pie 29.69-26, or the latest 29.69-39-6-4.

Question Download Incomplete, Reboot every 60 Sec?

This was my first attempt at ever trying to put custom rom on a phone, so don't laugh too hard at me. I used the the twrp.img found in this forum, had it going right but when I did something trying to go back to stock for an update, it went into bootloader, but nothing else, no system no recovery. I tried to use the fastboot tool on here, and it reached this and stopped. Any help or is it done for?
PS, I did manage to follow one tutorial to a T, and did great my second time around.

btflyrose said:
This was my first attempt at ever trying to put custom rom on a phone, so don't laugh too hard at me. I used the the twrp.img found in this forum, had it going right but when I did something trying to go back to stock for an update, it went into bootloader, but nothing else, no system no recovery. I tried to use the fastboot tool on here, and it reached this and stopped. Any help or is it done for?
PS, I did manage to follow one tutorial to a T, and did great my second time around.
Click to expand...
Click to collapse
So your second round where you stuck at..?

Have your tried getting factory file...boot img..flashing boot img through fastboot..?

have you tried...fastboot boot " fastboot getvar current-slot " see what slot you on...change to other slot ...see if it boots up...?

What model do you have..?

the more details you give to more people can help you..just saying

I'm sorry, I've not been back online. Single mom, busy. Kids getting older, I have a little more spare time during school hours but this past week has been hectic.
I tried to flash the original boot.img with no luck. It goes black when it connects to a computer but vibrates but isn't recognized on my adb or the fastboot tool. So far nothing.
My second time was another phone, same phone though. OnePlus 10 pro NE2015 model.

The issue also could be that there are no real custom ROMs for this phone yet... you might have flashed a malicious file and killed the phone. Unless you were hopping to GSI. Only real suggestion is to try a complete flash from TWRP or pay for MSM.
If you can't get into recovery, can you flip the boot slot with the hardware combo and get in then? May be your last hope besides EDL/MSM.

This issues happend to Oneplus 9 series with bad update (F.19), but I see this issues for the first time on Oneplus 10 Pro. Is it really on OP10P?

Prant said:
The issue also could be that there are no real custom ROMs for this phone yet... you might have flashed a malicious file and killed the phone. Unless you were hopping to GSI. Only real suggestion is to try a complete flash from TWRP or pay for MSM.
If you can't get into recovery, can you flip the boot slot with the hardware combo and get in then? May be your last hope besides EDL/MSM.
Click to expand...
Click to collapse
How exactly do I do a flip? If it's even possible to get into recovery. So far, I've not had luck.

kouzelnik3 said:
This issues happend to Oneplus 9 series with bad update (F.19), but I see this issues for the first time on Oneplus 10 Pro. Is it really on OP10P?
Click to expand...
Click to collapse
Yes, it's the 10 pro. I was too eager to root a phone and must have missed something, or done something somewhere. I've done several tablets, but not any phone. I've always had Samsung phones through carriers, so I couldn't figure knox out. But I've been researching and reading for months about rooting a phone, and decided that the OP 10 pro would be my first try. I'm not sure where I went wrong. I managed to get a second one, and followed the guide again, and well, that is the one I'm on now, and it seems fine.

btflyrose said:
How exactly do I do a flip? If it's even possible to get into recovery. So far, I've not had luck.
Click to expand...
Click to collapse
AFAIK, according to @g96818 as well, you have to hold all three hardware buttons down, let it attempt to boot, continue holding the buttons and it should like shut off immediately right after the boot logo and switch to the other boot slot.
btflyrose said:
Yes, it's the 10 pro. I was too eager to root a phone and must have missed something, or done something somewhere. I've done several tablets, but not any phone. I've always had Samsung phones through carriers, so I couldn't figure knox out. But I've been researching and reading for months about rooting a phone, and decided that the OP 10 pro would be my first try. I'm not sure where I went wrong. I managed to get a second one, and followed the guide again, and well, that is the one I'm on now, and it seems fine.
Click to expand...
Click to collapse
Yeah, the key to this device is basically do not flash anything to it, just boot from images. You CAN flash TWRP but I would personally recommend against it for daily use right now until data decryption is fixed fully. Just BL unlock, root it, and play with some Magisk modules like V4A, that's all we got on 10Pro for now.

Just some pics of the device...
But @Prant I'm curious to know, what is the difference between having the TWRP and not having it installed regarding rooting? Luckily, OP makes rooting for easier with unlocking the BL. But honestly, the confusion I've had the most understanding in the rooting process at this point is the whole difference between having TWRP and not having it, while installing Magisk.
(Y'all have to excuse me for my not having as much knowledge. I'm just basically a bored at home Mom with kids getting older, and tries to find something to get interested in that wasn't so old lady like. I've never been one to enjoy sewing, knitting, gardening, etc... HA!)

btflyrose said:
But honestly, the confusion I've had the most understanding in the rooting process at this point is the whole difference between having TWRP and not having it, while installing Magisk.
Click to expand...
Click to collapse
This is a bit of a dated thing from 6-8 years ago or so, TWRP used to be the gold standard for recovery on a phone. However, nowadays companies have gotten smarter and want more control over their device, so they add things like Knox (in Samsung) to keep the device "safe." OPPO/OnePlus has started doing this with the OP9 and the OP10 is their first attempt at keeping the device "basically" locked.
Long story short, TWRP is useful to do backups but I've even seen cases of backups on this device in particular failing when restored. And it used to be the main entry point, the first step to rooting any android device. However in recent years, it's become less and less necessary as you can do almost everything you can do in TWRP, through ADB and fastboot. Flashing is still a no go (on this device, thanks to OPPO magic) , but booting a patched image works for now. In the next years I'm sure even that will be secured somehow.
And, haha, there's nothing wrong with getting into tinkering, it's a helluva rabbit hole that's for sure.
Good luck and feel free to reach out if you have any questions.

Prant said:
This is a bit of a dated thing from 6-8 years ago or so, TWRP used to be the gold standard for recovery on a phone. However, nowadays companies have gotten smarter and want more control over their device, so they add things like Knox (in Samsung) to keep the device "safe." OPPO/OnePlus has started doing this with the OP9 and the OP10 is their first attempt at keeping the device "basically" locked.
Long story short, TWRP is useful to do backups but I've even seen cases of backups on this device in particular failing when restored. And it used to be the main entry point, the first step to rooting any android device. However in recent years, it's become less and less necessary as you can do almost everything you can do in TWRP, through ADB and fastboot. Flashing is still a no go (on this device, thanks to OPPO magic) , but booting a patched image works for now. In the next years I'm sure even that will be secured somehow.
And, haha, there's nothing wrong with getting into tinkering, it's a helluva rabbit hole that's for sure.
Good luck and feel free to reach out if you have any questions.
Click to expand...
Click to collapse
Is there a reason that the OP10 doesnt have any roms but the OP9 has lots?

w_tapper said:
Is there a reason that the OP10 doesnt have any roms but the OP9 has lots?
Click to expand...
Click to collapse
Easiest answer is that there is no free / public MSM tool. Which means no way to recover from a bad flash without paying OPPO, essentially. That's not very developer friendly.