Tired, frustrated and out of ideas. (m7spr) - Sprint HTC One (M7)

Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.

Super_Annoyed said:
Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.
Click to expand...
Click to collapse
Did you try the latest RUU? No need to root etc...Just download the file, run the setup and you're good to go!
http://forum.xda-developers.com/showthread.php?t=2658910

Super_Annoyed said:
Okay let me preface this post by saying, I did a good deal of research before I began this process, and was confident that I knew the steps sufficiently, and also the "plan B" recovery options.
Every video I watched on YouTube, every guide I found on various forums, and everyone I talked to made this process seem like cake. I have grown to disagree.
I am not a moron, nor am I incapable of following instructions. Every time I had a problem, I consulted with Google/YouTube/Forums, and researched how to fix it. I generally consider myself tech literate, but this is new to me. As such, I find it quite astonishing that, after so many years of development/home projects/general interest, there is NOT A SINGLE valuable 'getting started' guide. Granted, this is probably considered an advanced process, but even *nix development has more information than this FFS.
Anyway.
My task was simple; I wanted to update My GF's HTC One (m7spr) from 4.06xx to 4.4x. (Way overdue)
First things first; Settings -> About Phone -> Update -> Download it -> Install
Somehow this process got botched??? And the phone refused to accept 4.4, despite it being officially supported for several months.
Phone stuck at 4.06. Google had no information on failing to update, nothing relevant/useful anyway.
After dealing with that for 2 weeks, with zero progress, I decided to try the Root+Custom ROM process. That was, I believe, my only mistake.
The steps I followed, not necessarily in order*** :
-Install TWRP (so many problems with this, can't even find the words)
-Root phone (didn't work after multiple attempts, despite following directions perfectly, finally got it to work, and it didn't accomplish anything?!)
-Attempted to install SLIMkat ROM (took several attempts, finally got it running) This ROM was --no offense to the developer(s)--, for my purposes, disfunctional/broken, decided to attempt to rid myself of it
-Followed guides on YouTube to remove a ROM // flash stock
-Found several RUU's (all claimed to be valid, functioning and "simple solutions". None of which worked, and in every case, my device would 'lock' at the white screen/fastboot menu, and rebooting was a serious problem. During one failed attempt, my device would not reboot, causing me to be forced to let the battery drain before attempting again. (Hence the significance of removable batteries, but that's a whole other matter)
This is where it gets interesting
-SOMEHOW(???) "Chameleon OS" was attempting to be installed on the device. I had never heard of it, I had never seen it, I had no prior knowledge of it, I had not intentionally or even unintentionally collected this ROM, and surely did not have any intention of installing it. I wish to warn the community of potential maliciousness on the part of Chameleon OS. I did not give it permission to install, I was not even aware of its existance until the animated Chameleon came up, upon boot. I could not exit the install process, and it never finished booting. I had to simply let the battery die before I could re-enter the boot console/white screen. To be clear, I am not accusing the developers of anything malicious, I am simply pointing it out that this happened and the community should be aware of it.
Moving on.
-Using TWRP, I reset data, then factory reset the phone, then used the backup function, to boot into stock 4.06x Official.
-At this point, every time I restart the device, trying to enter TWRP, I can only access the white screen/fastboot menu -- I consider this to be progress, although it created a new problem; I am able to see the 4.4x update, and after it downloads, it asks me to restart the device so it can install. In doing so, it does NOT apply the update, however it stalls at the white screen/fastboot menu. I can reboot device and get back into Android, and the process repeats.
-
Allow me to sum up my current state;
-Device is fully functional within 4.06x, but for intents and purposes this is unacceptable
-Device can not be updated to newer version of Android, stuck at 4.06x
This process has been so long and drawn out, I am completely turned around with what problem requires what solution, and frankly I am exausted of trying to figure it out.
The real problem at hand is that the people who create guides/tutorials expect you to know certain things, and if you don't know certain things, they expect you to pause the video you're watching, go watch another video they made (irritating way to make your channel look like it has more traffic), and then resume what you were watching. As a first-time ROOTer, you're expected to pick up a ton of information that is not properly laid out in chronological order. Terms are not defined, and you're expected to just go with it.
This is why I did so much research beforehand. I was under the impression that the process was as simple as follows:
-ROOT device
-Install recovery option
-Create backup
-Install ROM
-Enjoy
Guides/forums/videos make it seem like a 10 minute proceedure. Lolnope. Going on several days of dealing with the current state. I waited so long to post because I was sure I was missing something, or messing it up. But I'm out of ideas now. :/
*** = Please understand that the process became frustratingly convoluted with various "I have B* problem, so I have to google the answer, which led me to learn about Y* treatment/process, and to complete Y* steps I needed Z* program, and to get Z* program I had to find Q* obscure information about my device, which requires me to go into BLUE* menu...and so on" ... it's irritating, to say the least.
I am frustrated, stuck and confused. The process is way more complex than the guides led on, and I have no idea what my next move should be. I'm humbly asking for help.
I would be more than glad to offer any non-personal information about my device's current state, in order to help you help me. Although as it stands I don't know what you need. Just ask. All I want to do is make the device COMPLETELY STOCK/FACTORY 4.4
Please forgive me if this post sounded ranty/salty. I'm honestly just tired of dealing with it, and I'm hoping to find some help from the people who know what they're doing.
Please and thank you.
Click to expand...
Click to collapse
if you are s-on you need to relock your bootloader, you also need to flash stock recovery for the ruu you are using, also if ypu are s-on you'll need the latest ruu, will not let you downgrade,

Muchas gracias amigos
indy1811 said:
Did you try the latest RUU? No need to root etc...Just download the file, run the setup and you're good to go!
http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
Aldo101t said:
if you are s-on you need to relock your bootloader, you also need to flash stock recovery for the ruu you are using, also if ypu are s-on you'll need the latest ruu, will not let you downgrade,
Click to expand...
Click to collapse
I greatly appreciate the responses.
I will try both and report back.

Super_Annoyed said:
I greatly appreciate the responses.
I will try both and report back.
Click to expand...
Click to collapse
LOG:
-RUU listed above was successful, booted into 4.06.651.4
-Attempting to update to 4.06.651.9
-Update unsuccessful, upon reboot, still 4.06.651.4, no error message
-Attempting to update to 4.06.651.9 again
-Update successful
-Attempting to update to 5.03.651.3
-Update successful (THANK YOU!)
Oh wow, such a huge relief. I feel a bit dumb having been so close to the actual solution, lol.
I would like to extend a huge helping of gratitude to both users indy181 AND Aldo101t.
Yall really knew what my problem was and how to fix it, so yall both have my gratitude.
I guess in my frustration I misunderstood the purpose of the RUU files, and ignored the version labels.
To a frustrated noob, the filename "1_29_651_10" has no real meaning. I suppose my research failed at this critical point.
It doesn't explain why the device failed to update in the first place, but since it's all set now it makes no difference.
Thanks so much, fellas!

worked like a charm)

Just a quick comment:
I didn't see any mention of HTC Dev unlock. Did you do that?

Did u ever get any offers from any publishers? Haha holy cow that was a long post! Glad u got straightened out!
Sent from my Nexus 7 using Tapatalk

Related

Problem when initially installing Android on HP Touchpad

Late last night I went to fix a touchpad that was handed to me, was told that the Android install was started, but had messed up. If I fixed it I could keep the touchpad.
So, i wandered over here and followed RolandDeschain79's how to install android thread, using the novacom,exe route with ACMEUninstaller2 and ACMEInstaller5. After running both of these (and placing the Cyanogen9 Mod on the tablet... i followed the instructions to the T). I got Android to run on it. BUT there was a problem! I got a bunch of notices @ initial startup, (Like 3). I don't remember what the other 2 were, but the biggest problem was the android keyboard would not function. Thinking that it would fix it, I went ahead and re-did what I had already done, running ACMEUninstaller2 and ACMEInstaller5. When I was in the middle of doing this the battery died (wish the stupid thing would just feed off power from my PC when it's plugged into it but apparently not). Now, I'm stuck in a bootloop (i think).
what does it do?:
The WEBOS boot screen, the little circle w/ HP in it? It just sits there. Sat there the entire time it was plugged in, didn't show me it was charging or anything. When I force it to shut off (hold power button and home key) it'll sit there 4 10 seconds or so, then turn itself right back on. I CAN GET INTO RECOVERY MODE however.
What I have done since then:
1. left it sit on the charger for about 7 hours... should be fully charged I hope.
2. Re-ran ACMEUninstaller2
3. Re-ran ACMEInstaller5
my thoughts were that if I can get an older ROM to work on it, I can upgrade to the most current from there.
HELP!!!!
Any ideas would be appreciated. This is the first tablet I've messed with, actually the first tablet I've owned and I'd really like to fix it...
Thanks in advance!
The easiest and most simple means of installing Android is with TP Toolbox. Follow the advice and instructions in the developers forum, you will have to do some reading to understand what you are doing.
I also am listing a link that I think is clear on the install:http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
As for the ROMS, there are a number to choose from. I have jcsullins installed on several TP's as well as pac-man ROM on another. Please take your time to read and decide.
Also, using toolbox will require that you use the naming convention for gapps as outlined in the toolbox thread.
Thank you. I followed the instructions on that site and the touchpad is working excellent.... Minus one glitch thus far: the camera works on boot, but as soon as you go to take a photo the whole screen digitizes and the touchpad loses connectivity with the camera. Is there an easy fix for this?
What ROM are you using? Also, which gapps did you install? Please be as specific as possible.
The ROM I am using is cyanogen 11 and I downloaded the gapps from the same page. The tablet upgraded itself last night and after that everything works great. It said something like upgrading apps, and reinstalled all the apps I had put on it. I'm playing with it as much as possible, making sure it acts like it should.
Thanks 4 all the help thus far
more issues
okay guys I am using invisiblek's cyanogen 11 and gapps... still have an issue with the camera I randomly acting up. it will work and then it won't. I have no clue where to even start with this. the build is from June of 2014. I do have an update available, I don't know if that will fix it but I do not have my laptop available at this current moment, so I cannot try it. Any ideas?
Are you reading the posts in the forum thread for that particular ROM? Other people using it may have encountered and fixed the issue.
I would invite you to read information about the various ROMS in the developer section as issues such as you are describing are
usually addressed and fixes or work arounds are presented.
I do not use the particular ROM you have installed but run other ROMS on several touchpads and do not have the problem you describe.
like an idiot I have not read the other threads regarding this particular CyanogenMod... I will look into them.
Thank you.
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Greasemonkey50701 said:
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Click to expand...
Click to collapse
You can't bypass moboot, and what you're proposing is going to ultimately cause you problems. But if you must, the easiest way to do what you want is to reduce the moboot timeout so that it goes directly to boot quickly. Create (if it's not already there) or edit (if it is) a file named moboot.timeout and put the number of seconds you want moboot to wait before booting CM. You can do that with a root browser like ROM ToolBox lite, or you can do a terminal session and type in:
Code:
su
mount -o remount,rw /boot
cd /boot
echo "1" >/boot/moboot.timeout # will set timeout to 1 sec (defaults to 5)
sync
What problems would this cause? Call me stupid (and I am sometimes) but i really don't forsee any problems caused by doing this...
I think Shumash already answered your question.
You need moboot to boot into Android.
Android is Linux based and Linux requires the use of a bootloader.
The best you can do is to shorten the time out before it boots.
In spite of the best advice given to you...it is your touchpad and you are free to do what you choose.
Even if that means borking it for good.
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Greasemonkey50701 said:
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Click to expand...
Click to collapse
You were clear enough, but seem to have some misunderstanding of what the sequence is. On boot, moboot times for a default 5 seconds and then automatically boots into Android, unless you screw with it by touching buttons or making selections. If you want it to do that faster, change the timeout as I suggested. You do not need to take anything off of it, and in fact, doing so will cause you grief eventually. If you take CWM off, and want to update your ROM, create a nandroid backup, clear the caches, or do any other low level stuff, you won't be able to. If it's booting into CWM (which you haven't said it does yet), then the moboot.default file has been changed. It should contain the word "CyanogenMod" (w/o the quotes) to boot directly to CM/Android. Use a root browser to edit or recreate it.

Dead Turbo?

So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
When I had my Razr Maxx I had an issue that was similar and nothing I tried would fix it. Factory reset cache wipe flashing different roms nothing. Finally I decided to factory restore it with RSD Lite and after that the problem went away and I was able to do everything again like normal. I don't know why a factory reset wouldn't fix it and that did but it did.
Thanks. That is my next step. Do you know where I can find the RSD image?
Is this what I need? http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Do I need to worry about flashing radios and stuff back to 4.4.4?
Seems to be. Honestly I've used it on many Motorolas in the past but I haven't read much about using RSDlite on the turbo. I would just do some googling around I'm sure you'll find it
my2cents said:
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
Click to expand...
Click to collapse
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
my2cents said:
That makes sense. Like an idiot, after I finally got mine going, I updated Moto Actions and it crashed again. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Click to expand...
Click to collapse
I did get it booted again. I flashed the kitkat update (not the stock, stock update 1, which is what you should be on if you're using mofo) file on the firmware thread that was posted here using the version of RSDlite that was posted there. The key is just to wait a really, really long time. Even if the screen goes black, it could potentially still be booting, especially if the back of the phone gets warm. I left it plugged in, let it get to the boot animation and left the house for several hours, and when I got back it appeared to be functional, but things were slow and choppy at times and my home button didn't work. The settings menu from the pull down menu didn't work either. I had to access settings from the app drawer. I tried a factory reset from the settings menu, and that just re-broke everything. So now I'm back at square one. I re-flashed the same image using RSDlite again, and now I've waited about 10 minutes and I'm still looking at the boot screen, which at this point is normal since the problem occurred.
I got a hold of an old copy of the Motorola Sensor Services apk. As far as I can tell, this is the apk that is replaced by Moto Actions, which according to Google Play is only compatible with 5.0 and above. My plan for tonight is to wait until the thing decides to boot, attempt to start the stock Sensor Services app and get it to do the sensor firmware uninstall that I mentioned in my other post. If that doesn't work, I'm going to try to install the apk that I found and see if I have any more luck with that. I'll report back here when I get a chance to do that. Let me know if you figure out a solution.
---------- Post added at 03:48 PM ---------- Previous post was at 03:33 PM ----------
my2cents said:
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
Click to expand...
Click to collapse
Yeah, I used SU2-12.
I followed the procedure outlined here to go back to stock. https://www.youtube.com/watch?v=6avEPGWB8E0 I used the SU2-12 file, but I lost everything... Thanks for the help. I hope there is a fix for this soon! I'll test your idea about MOTO Actions and report.
Edit: Well, I thought my phone was booting when I wrote the above, but it has been 30 minutes and it has not booted...
So, I can get it to boot - although it is not easy and it takes me like 30 minutes and I haven't found a full proof method yet, but after it goes to sleep I have to start the process all over. It has been a frustrating 3 days.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
my2cents said:
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
Click to expand...
Click to collapse
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
TheSt33v said:
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
Click to expand...
Click to collapse
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
GeoFX said:
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
Click to expand...
Click to collapse
I agree. Either it was a corrupt driver installation that worked just well enough for the app not to realize it, or the firmware update happens silently only when requested (similar to Google play services), and we're all one chop chop flashlight away from a phone apocalypse. Hopefully it's the former.
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
my2cents said:
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
Click to expand...
Click to collapse
Good to know. I picked the $25 option specifically because the free one requires an inspection, but I'll probably update it anyway. I'm not surprised that it didn't solve the problem though. When we flash those upgrade/downgrade images, we're basically just doing manually what RSD lite/Verizon upgrade agent does automatically.
ctopher4
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUO​TE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUO​TE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
TheSt33v said:
ctopher4 said:
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
Awesome! Well I managed to fix it too, Moto functionality included!!!! I'll explain on my other thread.
Click to expand...
Click to collapse
What was the solution that found? I'm going through the same problem.

XT1254 won't boot to Android

Hi,
I preface this post by acknowledging that I'm not particularly good at working through issues with custom ROMs/recovery, even though I have enjoyed tinkering. Also, I don't mind putting the effort/research into solving my own problems, and hate to lean on the community to solve my problems for me. As it stands though, I have major life changes coming up within the next couple of weeks; it's a necessity to have a functional phone; and these issues have cropped up right at a time where I can't invest a ton of time fixing them. I may just have to bite the bullet and get a phone to get me through. I thought I would ask for input here in case some kind soul had a suggestion.
I have a Verizon Motorola Droid Turbo XT1254 that I rooted nearly 2 years ago with Sunshine. Since, I've tried a handful of ROMs. I have TWRP 3.0.2-0 for recovery, and have backup images of Lineage Nougat and the newer Resurrection Remix Oreo ROM. Over the past couple of weeks, I've had an increasing number of issues with the phone rebooting by itself, and/or taking a long time to boot, but I haven't had time to sit down and properly troubleshoot the issues. Finally, this weekend, the phone has taken itself out of commission. It decided to reboot, and now will not reboot to Android. It will reboot to the bootloader or TWRP. I have wiped everything, and restored from my backups, but the phone will still not boot a ROM itself. I have wiped everything and reflashed the original downloaded image I still had saved. No success with that either.
What do you think the issue is? Is this a setting that could have been accidentally changed in TWRP? Is this a hardware issue? Is there anything I can try to preserve this phone?
I've always used TWRP to bounce between ROMs. I'm open to any suggestion, but will need a good amount of guidance for some things. I've never used adb or pushed anything from PC, for example, nor updated the recovery or anything like that. If these things are necessary, that's fine, I just need a little nod to the right information on how to do it, or a good explanation.
If you need any additional information just let me know.
Thanks to anyone who can offer any advice.

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.

Categories

Resources