Database Develop

HTC one (sprint) accidentally flashed a 4.2.2 rom

So I have screwed up pretty bad and now tried fixing the problem myself before asking for help.
Earlier I flashed Android Revolution HD 12.3 to finally realize that I didnt work with sprint, however I forgot to make a back-up for my phone. I have tried using adb sideload to install viper's rom v1.1.0 via TWRP. After the flash is complete and I click reboot, I get an error saying "No OS installed! Are you sure you want to reboot?"
If I swipe to reboot, I end up with a black screen with a toolbar at the top. I am totally lost and have been searching to forums for hours on end. Any help would be greatly appreciated.
Edit: I have been able to get viperROM to boot to the startup screen, however with a minute or so I get an error which states "Precess system is not responding, would you like to close it?" Then my phone restarts to the black screen.

You messed up your partitions by flashing that rom. From bootloader select factory reset to get your partitions back and then sideload your sprint rom and you should be set.
Or this method will work too.
http://forum.xda-developers.com/showthread.php?t=2321685

Konfuzion said:
You messed up your partitions by flashing that rom. From bootloader select factory reset to get your partitions back and then sideload your sprint rom and you should be set.
Or this method will work too.
http://forum.xda-developers.com/showthread.php?t=2321685
Click to expand...
Click to collapse
I tried the first method and didnt have any luck. I did notice that when looking through the install folder, the .zips are no longer listed. However, when the phone turns on for a few seconds and I am able to open files through my PC, they are listed there.
Second method got me to the startup screen. As I attempted to connect to wifi, I had no phone service and also there was an error connecting to wifi due to "temporarily avoiding poor connection". Then the phone instantly restarted back to a black screen.

[SOLVED]
I followed instructions on:
http://forum.xda-developers.com/showthread.php?t=2390821
followed by
http://forum.xda-developers.com/showthread.php?t=2250904
Which fixed all of my problems. Now im back to square 1

You're lucky the partitions aren't aligned in a way that your hboot was overwritten. Otherwise you'd have a brick instead of a phone.

CNexus said:
You're lucky the partitions aren't aligned in a way that your hboot was overwritten. Otherwise you'd have a brick instead of a phone.
Click to expand...
Click to collapse
I know, I really lucked out. Took a solid 14+ hours of research and trial and error to figure out how to fix it. I had rooted my old evo 4G a few times thinking I still knew what I was doing, but that was a while ago. I should have definitely took some extra time to do some more research before I flashed.

This is why i don't flash roms from another section even though some have sprint version i just don't trust them

YoungCorruptionV2.0 said:
This is why i don't flash roms from another section even though some have sprint version i just don't trust them
Click to expand...
Click to collapse
I flashed viper's sprint version of his ROM and havent been receiving text messages or phone calls. I think its time to just give up on keeping my phone rooted. I havent had any favorable results yet.

So I ran a RUU to get everything back to stock as described above, however I am no longer receiving text messages or phone calls. I can send them though. Would anyone know why?

message deleted

flsurf7 said:
So I ran a RUU to get everything back to stock as described above, however I am no longer receiving text messages or phone calls. I can send them though. Would anyone know why?
Click to expand...
Click to collapse
did you try to update the profile and PRL? otherwise you might have to call sprint and manually program using your MSL through the ##DATA# menu

http://forum.xda-developers.com/showthread.php?p=29331038
Sent from my HTCONE using xda app-developers app

I'm having a similar problem but I can't sideload anything because adb can't find my device.

Jay227 said:
I'm having a similar problem but I can't sideload anything because adb can't find my device.
Click to expand...
Click to collapse
PM me teamviewer id (I'm bored. Gonna fix as many people's phones as I can
http://teamviewer.com/download

Indirect said:
PM me teamviewer id (I'm bored. Gonna fix as many people's phones as I can
http://teamviewer.com/download
Click to expand...
Click to collapse
You should add the teamviewer link to your sig

[Q] Can't send/receive calls or texts after screwing with PRL

Running Beanstalk.
Have been having intermittent issues with mobile data, so I'm sadly familiar with toggling Airplane mode, changing the CMDA subscription, rebooting, etc. in order to jog mobile data into working again. Lately have been having a weird, sporadic problem with people I call only hearing static on my end, so I chatted with Sprint, got to the point where they suggest typing the code to reset/update PRLs into the dialer, and bailed.
Then, in my infinite wisdom decided to try flashing a Sense ROM, proceeding with the manual PRL update/reset, and then wiping and restoring my Beanstalk nandroid.
Now I can't make or receive calls or texts at all, no matter what I do. Have tried all the old toggles. Have tried a complete reflash of Beanstalk. I'm beginning to worry I seriously borked something up.
Is anyone familiar with this kind of situation? Did I screw up, and if so, how bad? Any solutions anyone can think of? I'd be most grateful for any and all help. Thanks guys.

Reinstalling ROM from scratch and if that doesn't work then running ARU.

EPayne123 said:
Reinstalling ROM from scratch and if that doesn't work then running ARU.
Click to expand...
Click to collapse
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.

thedodus said:
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
Click to expand...
Click to collapse
Okay here is what you can do, there is an app floating around these forums that can allow you to manually write the prl, find that, and then use a stock prl for sprint. I believe this post will help:
http://forum.xda-developers.com/showthread.php?t=2296167
Let me know if that helps.
Oh and also yeah flashing a different rom wouldnt help because they do not contain any of that information, in fact i think all the carrier information is stored in a different partition for this exact reason -so they cant be easily overwritten.

I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS

BMP7777 said:
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
Click to expand...
Click to collapse
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.

Yes, it should as long as everything worked then. Driving right now. Try it and let me know. When I get home I'll help however I can.
Sent from my One using XDA Premium 4 mobile app

thedodus said:
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Click to expand...
Click to collapse
Your welcome and yeah it should defintely work, just make sure you use the right prl

Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!

thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
More than welcome. Glad you're up and running.:highfive:

thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
Your welcome glad you got everything straightened out
Sent from my HTCONE using Tapatalk

[Q] Having trouble upgrading to 4.4.2 stock on Verizon

I have a Moto X Developer Edition rooted on Verizon with TWRP 2.6.3.1 and stock Android 4.4 on it. I have been trying to upgrade to 4.4.2 without doing the OTA, and without having to reflash TWRP.
So far, I have been unsuccessful.
I have tried Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip (approximate file size 150MB) from multiple sources as all the posts I read keep saying that is what works. I have also tried a ~650MB version I found somewhere. In addition, I tried the upgrade located here: sbf.droid-developers.org/phone.php?device=0 which is called VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip (It's the 4.4.2 upgrade listed under Verizon US).
All of these fail. In TWRP, about 2-3 steps after it verified md5, it simply says "Failed" with no explanation as to why.
Here is my question:
How can I upgrade to 4.4.2 without a data wipe, and without having to reflash TWRP?
I have no interest in going to a ROM, I want to stay stock, and if I must, I will reflash the recovery if I have to, but I *really* don't want to.

Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.

tcrews said:
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
Click to expand...
Click to collapse
I was hoping to avoid that (Yep, I really am that lazy...) but that's what I was going to do tonight if I couldn't get my hands on a .zip to flash.
Ironically, I bought the Dev Edition specifically so things like this would be easy.

It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.

tcrews said:
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
Click to expand...
Click to collapse
Oh, that last bit is good to know! Well, I think even if it did remove root, getting it back is easy on the DE.
I think you're right though, I probably won't install TWRP again, I specifically got the Moto X because I was tired of messing around with stuff when I all I want is a rooted, stock Android experience.

So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.

Taegost said:
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Click to expand...
Click to collapse
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.

kj2112 said:
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
Click to expand...
Click to collapse
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.

Taegost said:
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Click to expand...
Click to collapse
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.

kj2112 said:
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
Click to expand...
Click to collapse
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).

Taegost said:
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Click to expand...
Click to collapse
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!

kj2112 said:
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
Click to expand...
Click to collapse
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.

Taegost said:
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Click to expand...
Click to collapse
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.

kj2112 said:
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
Click to expand...
Click to collapse
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*

Taegost said:
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Click to expand...
Click to collapse
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.

if using fastboot/mfastboot, I would still erase cache, as it doesn't touch your data/apps/config.
Another tip, use this mfastboot -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
or you can use RSDlite to flash the SBF, but there is a corresponding line for "erase data"
Two helpful links that will help explain what you saw...
Taking the OTA -> http://mark.cdmaforums.com/MotoX-OTA.html
various ways to Return to stock -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html

kj2112 said:
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
Click to expand...
Click to collapse
Alrighty, well I was able to successfully flash to 4.4.2 using the Fastboot instructions. Flashed TWRP afterwards and got root right back. Now that I know, this won't be a trial in the future (fingers crossed!)
Thanks for your help and patience

[Q&A] Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.

[Q&A] Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.
Q&A for Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?

Biffins said:
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Click to expand...
Click to collapse
Same thing for me...
Sent from my Droid Turbo

Biffins said:
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Click to expand...
Click to collapse
getupandbeit said:
Same thing for me...
Sent from my Droid Turbo
Click to expand...
Click to collapse
At the recovery which reads "no command" hold power and press volume up.

Works on

What's going to happen if I push 5.1 and Android M comes out officially?
Am I better off holding until that time or is there a way to get there once I do all of this

Hello, Ive been reading on here about mofo for the last month, and Ive been waiting to see how lollipop goes over. After reading all the success stories, I bought mofo.
My phone has never been rooted, is there a specific guide for going to computerfreek274's loliipop image from a stock kitkat ? All the guides seem to assume Im already rooted on kitkat. Or should I root on kitkat first?
thanks

In the fastboot commands for this update, I notice that the command to flash radio.img is missing. Is this an oversight or is a flash of the radio partition not needed?
Thanks for all that you and Computerfreek274 contribute to this forum!!!

turpindm said:
In the fastboot commands for this update, I notice that the command to flash radio.img is missing. Is this an oversight or is a flash of the radio partition not needed?
Thanks for all that you and Computerfreek274 contribute to this forum!!!
Click to expand...
Click to collapse
The instructions in the main thread have were changed to reflect the latest files (you'll be flashing modem and a few others instead of radio). If you're using the guide that was linked, it hasn't been updated with the latest instructions yet.

firstEncounter said:
The instructions in the main thread have were changed to reflect the latest files (you'll be flashing modem and a few others instead of radio). If you're using the guide that was linked, it hasn't been updated with the latest instructions yet.
Click to expand...
Click to collapse
I am up an running I started experiencing data and voice signal issues - RIght now I have advanced calling I can talk and surf but the option is not in my Advanced Calling settings menu - but testing to see if the device holds signal for 1x communication. It keeps dropping the signal and never gets it backs a signal so I have been using my back up device for days now.

turk2333 said:
I am up an running I started experiencing data and voice signal issues - RIght now I have advanced calling I can talk and surf but the option is not in my Advanced Calling settings menu - but testing to see if the device holds signal for 1x communication. It keeps dropping the signal and never gets it backs a signal so I have been using my back up device for days now.
Click to expand...
Click to collapse
Make sure you haven't disabled the My Verizon app in order for the Advanced Calling menu to work correctly.
For radio issues, make sure you've downloaded the latest 5.1_images_v3.zip and used the fastboot commands in the main thread. You can run all those commands without reflashing your system.img just to make sure everything's up to date. If you're still having issues, I'm not sure what else you can try other than backing up everything and trying a data wipe.

firstEncounter said:
Make sure you haven't disabled the My Verizon app in order for the Advanced Calling menu to work correctly.
For radio issues, make sure you've downloaded the latest 5.1_images_v3.zip and used the fastboot commands in the main thread. You can run all those commands without reflashing your system.img just to make sure everything's up to date. If you're still having issues, I'm not sure what else you can try other than backing up everything and trying a data wipe.
Click to expand...
Click to collapse
seems stable now - I did two data wipes - was so many issues with the radio and I was like no way this cannot be fixed. I have nto left my office yet which will be the real test but right now all seems good.

turk2333 said:
seems stable now - I did two data wipes - was so many issues with the radio and I was like no way this cannot be fixed. I have nto left my office yet which will be the real test but right now all seems good.
Click to expand...
Click to collapse
I've had my phone get stuck on 1x a few times when using 4.4, so it's possible it's just a bug in the actual firmware.

firstEncounter said:
I've had my phone get stuck on 1x a few times when using 4.4, so it's possible it's just a bug in the actual firmware.
Click to expand...
Click to collapse
This is not being stuck this was no service at all would to G then I could not make calls or anything - totally screwed up - I have a new phone on the way from Assurion if this keeps happening. As I posted - I flashed all commands per instructions and that seem to do the trick I hope.

Thanks to everyone who keeps the updates updated... 23.11.39 Root went well... Thanks again!!!

Fastboot Command
Could someone please show me an example on how to flash files on the command prompt with adb. How do I direct it to the file location that I want to flash. Screen shot would be very helpful. Thank you for your time in advance.

Hi,
Can someone please explain something to me?
If the BL is locked on xt1254 but mofo somehow gets around it to enable flashing of rooted images.. What is stopping us from flashing a modified cyanogenmod or equivalent over?
Why do we need an unlocked bootloader if we can already flash modified images? Is there some check in place that prevents this? Or is this wip?
I'm obviously missing something!
Thanks guys
Sent from my Nexus 5 using XDA Free mobile app

Quick question
I am on stock 4.4.4 do i need "5.1 upgrade images (v3)" or "Rooted 5.1 system image (v2)" to get myself to 5.1 with root? And wifihotspot is enabled on all these images correct?

SkiiinZ said:
Hi,
Can someone please explain something to me?
If the BL is locked on xt1254 but mofo somehow gets around it to enable flashing of rooted images.. What is stopping us from flashing a modified cyanogenmod or equivalent over?
Why do we need an unlocked bootloader if we can already flash modified images? Is there some check in place that prevents this? Or is this wip?
I'm obviously missing something!
Thanks guys
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
because mofo can't write the kernel/boot partition
Sent from my XT1254 using Tapatalk

Tap053 said:
I am on stock 4.4.4 do i need "5.1 upgrade images (v3)" or "Rooted 5.1 system image (v2)" to get myself to 5.1 with root? And wifihotspot is enabled on all these images correct?
Click to expand...
Click to collapse
Either one should work if you follow the instructions but only the "extra" versions have tethering enabled. At this point, I'd use the image labeled "Extras 5.1 system image (rooted v2 + extras v4)". You can always start with the stock rooted, then dirty flash the extras version with mofo.
Sent from my XT1254 using Tapatalk
---------- Post added at 01:34 AM ---------- Previous post was at 01:29 AM ----------
Rag Man said:
Could someone please show me an example on how to flash files on the command prompt with adb. How do I direct it to the file location that I want to flash. Screen shot would be very helpful. Thank you for your time in advance.
Click to expand...
Click to collapse
Nowhere in the OP for this ROM does it mention flashing files with ADB. You can only flash the system image with the mofo tool. We do not have a custom recovery on the Turbo so you cannot flash ZIP files. We do not have a writable system partition so you cannot push files to it via ADB.
Fastboot is used to upgrade some of the other partitions to the 5.1 versions and is described in the OP.
Sent from my XT1254 using Tapatalk

Root and flash Custom Rom without PC

Hi,
I have an unbranded and unlocked nexus 6. I wanted to root and install twrp so I can begin flashing custom roms... Only problem is, I don't have a pc at home to ADB flash twrp, etc.... Is there any method to flash custom rom without having a machine at home? I have absolutely no need for a pc at home, until this precise moment when I get a new phone and I want to start flashing, lol. Im gonna assuming the answer is NO, im thinking there may be some OTG method with files from a thumb drive, but I'll wait to hear from the experts. Thanks in advance.

I have been wondering that very question myself. I really doubt it's possible, but since I have had my N6 and LG G Pad, I don't ever use my antique Pentium 4 Dell PC hardly at all.
Sent from my Nexus 6 using Tapatalk

It's totally possible but highly recommended against. There is an app to root, which then you use flashify to flash recovery but if you ever have a problem, you won't be able to fix it because you need a PC to get a rom back on your phone if you accidentally wipe the os or do some other mischief that prevents you booting, you wont be able.to unlock your bootloader which means you won't be able.to.flash stock or return for warranty purposes either, so as.much as you want to do this, it would really put you in an awful position and you'd be screwed if something goes wrong, which the chances are, it will.

danarama said:
It's totally possible but highly recommended against. There is an app to root, which then you use flashify to flash recovery but if you ever have a problem, you won't be able to fix it because you need a PC to get a rom back on your phone if you accidentally wipe the os or do some other mischief that prevents you booting, you wont be able.to unlock your bootloader which means you won't be able.to.flash stock or return for warranty purposes either, so as.much as you want to do this, it would really put you in an awful position and you'd be screwed if something goes wrong, which the chances are, it will.
Click to expand...
Click to collapse
I have no issues with the first potential problem you mentioned (having to get a rom back on phone using a pc) because I have a backup phone, plus if it gets to that stage, I can use a friends computer if I really need to. But the last comment you made about the chances of an error occurring and saying that it most likely will and i'll be unable to get it back to stock scares me. Is this method really that unreliable? I will read up on it more, and search through the forums.
If you can provide details of the app to root, that would be great. Also, how reliable is the app to root alone by itself? Minus the flashify portion...

nseriessaga said:
I have no issues with the first potential problem you mentioned (having to get a rom back on phone using a pc) because I have a backup phone, plus if it gets to that stage, I can use a friends computer if I really need to. But the last comment you made about the chances of an error occurring and saying that it most likely will and i'll be unable to get it back to stock scares me. Is this method really that unreliable? I will read up on it more, and search through the forums.
If you can provide details of the app to root, that would be great. Also, how reliable is the app to root alone by itself? Minus the flashify portion...
Click to expand...
Click to collapse
It's not the method that's unreliable the app "kingroot" (I believe it is called) works fine. The issues occur with everything and anything else root users do. Flashing a rom, a mod, wiping the os via recovery etc.
Then if anything hardware goes wrong, returning the device for repair under warranty will likely be rejected if its not stock.

danarama said:
It's not the method that's unreliable the app "kingroot" (I believe it is called) works fine. The issues occur with everything and anything else root users do. Flashing a rom, a mod, wiping the os via recovery etc.
Then if anything hardware goes wrong, returning the device for repair under warranty will likely be rejected if its not stock.
Click to expand...
Click to collapse
Gotcha, so maybe I can just root and install apks of apps I really want like adaway, etc... then I should be fine as long as im not using the flash method correct?

nseriessaga said:
Gotcha, so maybe I can just root and install apks of apps I really want like adaway, etc... then I should be fine as long as im not using the flash method correct?
Click to expand...
Click to collapse
I'm not going to commit to an answer there
One thing I will say though, you'll never be able to update with an OTA, so if you're going to root, have a custom recovery,. Allow.oem unlock and have an unlocked bootloader.
Best bet is to do the proper.routing and unlocking using your friends of as a one off. You can then safely.maintain the phone without a pc and use the pc in am emergency. Not unlocking the bootloader from the beginning is.asking.for.trouble
Man I need a new keyboard

danarama said:
I'm not going to commit to an answer there
Click to expand...
Click to collapse
lol I understand.. thx m8

nseriessaga said:
lol I understand.. thx m8
Click to expand...
Click to collapse
Edit above

danarama said:
I'm not going to commit to an answer there
One thing I will say though, you'll never be able to update with an OTA, so if you're going to root, have a custom recovery,. Allow.oem unlock and have an unlocked bootloader.
Best bet is to do the proper.routing and unlocking using your friends of as a one off. You can then safely.maintain the phone without a pc and use the pc in am emergency. Not unlocking the bootloader from the beginning is.asking.for.trouble
Man I need a new keyboard
Click to expand...
Click to collapse
k, I already used the kingroot method and verified using root checker. Installed adaway and everything seems to work perfectly (so far anyway). Uninstalling Kingroot unroots the phone from my quick series of test that I've run so OTA updates doesn't seem like it'll be a problem.
I agree though, if I really want to do any rom flashing, ill just unlock, root, and flash using "proper methods".
Appreciate all your help man.

nseriessaga said:
k, I already used the kingroot method and verified using root checker. Installed adaway and everything seems to work perfectly (so far anyway). Uninstalling Kingroot unroots the phone from my quick series of test that I've run so OTA updates doesn't seem like it'll be a problem.
I agree though, if I really want to do any rom flashing, ill just unlock, root, and flash using "proper methods".
Appreciate all your help man.
Click to expand...
Click to collapse
Uninstalling Kingroot removes root but does not uninstall all modified files. Will show as modified and thus no OTA updates. Another thread on same thing here somewhere. Have to flash system back to stock with PC for any updates.
---------- Post added at 11:13 AM ---------- Previous post was at 11:01 AM ----------
It's also not safe to update without bootloader unlocked anyway. Too many reported bootloops with OTA.

prdog1 said:
Uninstalling Kingroot removes root but does not uninstall all modified files. Will show as modified and thus no OTA updates. Another thread on same thing here somewhere. Have to flash system back to stock with PC for any updates.
---------- Post added at 11:13 AM ---------- Previous post was at 11:01 AM ----------
It's also not safe to update without bootloader unlocked anyway. Too many reported bootloops with OTA.
Click to expand...
Click to collapse
Exactly this. All root methods edit.existing files but do not restore them after unroot. So the system is modified. We're.100% certain there will be no OTA.
Unlock the bootloader and do it properly.

Ok thanks guys. I guess eventually I'll have to get my hands on a PC lol. Thanks again