Related
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
I got impatient waiting
I followed all the documented procedures.
You apply this exactly like ZV5 Root. This is only for LS991 (Sprint).
I've tested Root Explorer and WIFI Tether Router. It hesitated a little on the first attempt to grant root, I was probably rushing.
Once you apply this image on first boot it will want to upgrade Super User and you have to use "Normal".
YOU MUST BE ON ZV6 before you use this.
http://softronix.com/g4/Rooted.LS991.System.ZV6.zip
Not responsible for any bricking. I followed all procedures posted and I'm not gonna replicate it here.
Make sure you backup your unrooted ZV6 System image. I diffed my backup with the one uploaded by another developer and they are different.
I also tested rerooting a ZV5 stock image and it is different than the one uploaded in the ZV5 Root thread.
Oh, I should mention, I restored my ZV5 image first.
Then tried to take the ZV6 OTA update. It just stayed stuck "Now Rebooting". Tried manually rebooting. And it just went back to ZV5 boot.
So then I tried applying the update through the SD Card. That failed too, I guess it doesn't like my format of SD Card (didn't want to wipe that).
I suspect if I factory Reset ZV5 the AV6 OTA would have been fine, but I didn't want to do that.
So I noticed the ADB Sideload upgrade option in Recovery and tried that and it worked fine.
It even gave you the command syntax for ADB sideload. I had to upgrade ADB to make it work (adb sideload told me the verision I had was too old, which came from the LG_Root.Zip).
I have not done a lot of testing. I can't say tomorrow that LG didn't add some sneaky app that removes root or something. But at this moment it seems fine.
Feel free to mirror it.
How has this been working for you so far?
No problems. Even tethered while roaming with Wifi Tether Router.
Thanks for this!
I picked up a G4 a couple weeks ago for a basically a song. After reading that one thread you wrote, I figured.. why not give it a shot?
Which post, moving from M9 to G4?
Don't wanna sound stupid but how do I install this? I'm new to rooting.
votefortrump said:
Don't wanna sound stupid but how do I install this? I'm new to rooting.
Click to expand...
Click to collapse
Never mind I found the root tutorial you were referring to...but at what part of the tutorial do I use the image file you attached in the post? Once again sorry if I seem to be lacking common sense (because I am).
You do exactly what the ZV5 root thread(s) do. But you need to be on ZV6 and then use this rooted ZV6 image instead of being on ZV5 using Rooted ZV5 image.
Can someone provide the link on how to backup current stock system.img? I can't seem to find it.
mswlogo said:
You do exactly what the ZV5 root thread(s) do. But you need to be on ZV6 and then use this rooted ZV6 image instead of being on ZV5 using Rooted ZV5 image.
Click to expand...
Click to collapse
Oh ok, so in this tutorial http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765 I just replace 'system.rooted.phonemodel.img' with 'rootedsystem.LS991.ZV6.img' and I'm good?
Yes, just make you do a backup first and you are on ZV6.
Backup is in 2nd post by autoprime.
Also be careful when copying dd comands from the web page that you copy the whole command.
note the horizontal scrollbar.
ZV6.img flash over ZV5?
I know the post said I have to be on ZV6, but I don't want to loose the ability to flash tot(I've bricked my phone before). Has anyone tried this? I've read other posts that say you can't reflash tot after taking the update, and nothing about updating through this method. Would this brick my phone, should I try it?
Corrupt file .zip?
I have already tried both WiFi and Phone network, but when I finally download the zv6.img file it says is corrupted and doesn't let me extract it. I don't know what is the problem please help me.
TxShack said:
I have already tried both WiFi and Phone network, but when I finally download the zv6.img file it says is corrupted and doesn't let me extract it. I don't know what is the problem please help me.
Click to expand...
Click to collapse
You don't extract the .img file. Just throw it in the sdcard directory root.
G41LAH said:
I know the post said I have to be on ZV6, but I don't want to loose the ability to flash tot(I've bricked my phone before). Has anyone tried this? I've read other posts that say you can't reflash tot after taking the update, and nothing about updating through this method. Would this brick my phone, should I try it?
Click to expand...
Click to collapse
I was able to flash the ZV6 TOT with no issues after updating to ZV6
misteroh said:
You don't extract the .img file. Just throw it in the sdcard directory root.
Click to expand...
Click to collapse
When you download the file it comes in a .zip file. That's what I meant to say when extracting and qhen I did didn't work. Anyways thanks, found another rooted ZV6 .zip on another post and that one let me extract the file in my phone. Don't know why this one won't let me.
Has anyone else had success with this?
A whole bunch of folks are rooted on ZV6. There is also a pseudo custom ROM based on ZV6 called Ultra Pop.
Read through the threads in Development.
http://forum.xda-developers.com/sprint-g4/development
Hello everyone. I just got a Sprint LG G4 today. I would like to root my G4 but not exactly sure how to do it. I have done some rooting in the past so I am a little familar with it. My software version is LS991ZV6, security software version MDF v1.1 Release 5. From what I read, the rooting process is for zv5, is this correct? Is there a rooting process for my software version, and if so, is there a tutorial for it? Does this also install a custom recovery or is there a different process for that? I know this is probably not the place to ask but since I am enquiring, are there any roms for the sprint ls991, ex mm rom, etc? Also, how can I find the files to disable OTA updates. I have googled it and it says to disable sprintinstaller apk but I cannot find that file in settings- apps-all. Also, I read to do a backup before trying to root. I am on stock recovery and when I go into that, there is no option to backup, am I doing something wrong. Thanks again for your feedback.
Going to try it now! Looking forward to trying out xposed! I really don't want to flash an actual ROM because I love the stock camera app way too much.. And the tweaks look awesome.
Hi im on zv9 but want to go back to zv6. Preferably a zv6 rooted. Which guide is the best to follow? If anyone who frequents here could link it would be greatly appreciated.
Thanks
Hoping I'm not totally screwed here, but here goes. I'm swapping from one Nexus 6 to another. On stock 5.0.1 (still), rooted, and unencrypted. I made my Titanium Backups (always as a precaution) then booted to TWRP and made a nandroid backup. I was too tired to command line myself so I decided to use the Skipsoft Toolkit to pull my data. I got curious about a full backup option on there so I tried it out. First thing it did was boot an unsecured boot.img. Phone then boots back up and begins the encryption process. I knew I didn't want encryption, so I powered off mid-process. (Kicking myself for that now...) Now when I boot back up, I get the "Encryption Unsuccessful" message telling me that my data is unusable and that I must do a phone reset.
I can still get to the bootloader and boot into TWRP, but it can't see any of the data on the device--including the TWRP backup I made earlier today. Seeing as I didn't get any of my backups off before this happened, I need that TWRP or I will lose everything since my last backup on 11/6. Is there ANY way to still pull data from a partial but failed encryption? Please help!
wizard5007 said:
Hoping I'm not totally screwed here, but here goes. I'm swapping from one Nexus 6 to another. On stock 5.0.1 (still), rooted, and unencrypted. I made my Titanium Backups (always as a precaution) then booted to TWRP and made a nandroid backup. I was too tired to command line myself so I decided to use the Skipsoft Toolkit to pull my data. I got curious about a full backup option on there so I tried it out. First thing it did was boot an unsecured boot.img. Phone then boots back up and begins the encryption process. I knew I didn't want encryption, so I powered off mid-process. (Kicking myself for that now...) Now when I boot back up, I get the "Encryption Unsuccessful" message telling me that my data is unusable and that I must do a phone reset.
I can still get to the bootloader and boot into TWRP, but it can't see any of the data on the device--including the TWRP backup I made earlier today. Seeing as I didn't get any of my backups off before this happened, I need that TWRP or I will lose everything since my last backup on 11/6. Is there ANY way to still pull data from a partial but failed encryption? Please help!
Click to expand...
Click to collapse
You most likely corrupted all the data on the device.
Not sure why you thought powering off during encryption would stop it and not cause corruption.
Also dont even think about restoring a nandroid on a new device.
zelendel said:
You most likely corrupted all the data on the device.
Not sure why you thought powering off during encryption would stop it and not cause corruption.
Also dont even think about restoring a nandroid on a new device.
Click to expand...
Click to collapse
Because I wasn't thinking... I know--stupid. Is there no shot at recovering anything?
I'm switching from one Nexus 6 to another. Can I not restore a nandroid to an identical device?
wizard5007 said:
Because I wasn't thinking... I know--stupid. Is there no shot at recovering anything?
I'm switching from one Nexus 6 to another. Can I not restore a nandroid to an identical device?
Click to expand...
Click to collapse
No, no you can not. A nandroid has device spicific files in it like GPS and IMEI info. Restoring it is just asking for trouble. Only restore USER apps and data everything else is off limits.
How did you fix the issue?
zelendel said:
No, no you can not. A nandroid has device spicific files in it like GPS and IMEI info. Restoring it is just asking for trouble. Only restore USER apps and data everything else is off limits.
Click to expand...
Click to collapse
So what specifically is in /system or /data that would be so dangerous?
Have you ever actually done this, or are you just saying stuff you have read but don't fully understand?
If you backed up every single partition its a bad idea to restore to another phone... But simple backups are fine to restore cross device if you aren't including efs
scryan said:
So what specifically is in /system or /data that would be so dangerous?
Have you ever actually done this, or are you just saying stuff you have read but don't fully understand?
If you backed up every single partition its a bad idea to restore to another phone... But simple backups are fine to restore cross device if you aren't including efs
Click to expand...
Click to collapse
You do know who your talking to right? I don't read things. I do them. Been doing this for over 10 years now. So just maybe you might want to know who you are talking to first.
zelendel said:
You do know who your talking to right? I don't read things. I do them. Been doing this for over 10 years now. So just maybe you might want to know who you are talking to first.
Click to expand...
Click to collapse
Nope, no idea who you are.
All I know is how many times I have seen twrp backups restored on a phone it wasn't taken on with out issue?
Maybe you should actual read things and you wouldn't have an issue with it either?
Or... Care to actually explain the danger rather then just puffing your chest out because you have played with android smart phones for ten years (apparently since before it was released?)
lol!
ok, both @zelendel and @scryan are right..
its highly not recommended to restore a nandroid onto a different phone if it contains system apps. that said, theres also a chance that it would be fine as well. its just that the system apps could not be supported(or could be) by the 2nd device. but even if they arent supported, it wont really harm your device, as you can fix whatever issues by just switching out the apps that are causing issues(then reboot).
scryan said:
Nope, no idea who you are.
All I know is how many times I have seen twrp backups restored on a phone it wasn't taken on with out issue?
Maybe you should actual read things and you wouldn't have an issue with it either?
Or... Care to actually explain the danger rather then just puffing your chest out because you have played with android smart phones for ten years (apparently since before it was released?)
Click to expand...
Click to collapse
Well let's start out with the fact that when system apps are loaded the data loaded to is set to one device. By restoring that to another device messes it up and causes all types of issues with the app and system.
Also as stated above not all apps are compatible across devices. Could lead you to an endless bootloop.
See you have me twisted. I don't have to read about it as I do it everyday. As each device is different there is no telling that one thing will work for one but not the other.
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
I was modding devices before the first smartphone was even released. Then I became a moderator here. Which is requires a whole lot of learning. Like reading the source and knowing what does what.
Now you are more then welcome to flash someone else's backup, that is up to you but I will tell you that no one that knows what they are doing will do that.
zelendel said:
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
Click to expand...
Click to collapse
the Dream(G1) was Googles android developer phone before the Nexus. while a lot of people did use and mod the HD2, the G1/Dream was getting most of the developer support.
simms22 said:
the Dream(G1) was Googles android developer phone before the Nexus. while a lot of people did use and mod the HD2, the G1/Dream was getting most of the developer support.
Click to expand...
Click to collapse
I wouldn't say most. But it was close indeed. I had them both but focused on the hd2 mostly. God I miss truly open bootloader lol.
zelendel said:
....focused on the hd2 mostly.
Click to expand...
Click to collapse
I remember the HD2 as one of the best phone ever made.
zelendel said:
Well let's start out with the fact that when system apps are loaded the data loaded to is set to one device. By restoring that to another device messes it up and causes all types of issues with the app and system.
Also as stated above not all apps are compatible across devices. Could lead you to an endless bootloop.
See you have me twisted. I don't have to read about it as I do it everyday. As each device is different there is no telling that one thing will work for one but not the other.
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
I was modding devices before the first smartphone was even released. Then I became a moderator here. Which is requires a whole lot of learning. Like reading the source and knowing what does what.
Now you are more then welcome to flash someone else's backup, that is up to you but I will tell you that no one that knows what they are doing will do that.
Click to expand...
Click to collapse
Just wanted to chime in here and say, I agree 1000% that I would never restore a backup from one phone to another, unless I knew for a fact I could "rescue" the phone if it locked up/got fried/ruined from the restore..
And, I have been playing with cell phones since November 1983, the first day cell service became widely available in Chicagoland, and I have been modding/tweaking/hacking them pretty much since then, so I too have "extensive" experience about what may or may not work when doing something like this..
To each his own, but I would never do this..
Hey everybody,
I was on CM14.1, no issues, but decided to flash back to 6 and made the stupid mistake of trying to go straight with the standard motorola image. Now I am able to load the bootloader mode but cant do much after that. None of the partitions work, nor I can get data from bootloader info (tried retreieving flashing info to no avail). I am trying to find something I can use. Anyone has a suggestion?
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
zstricky said:
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
Click to expand...
Click to collapse
Sure!
- Got unlocked bootloader and installed cm14.1
- Decided to revert back to stock so downloaded 6.0 system image.
- instead of deleting the got.bin line from flashfile.xml I went to rsd and tried flashing it. It errored out and this took me where I am.
There is a flashable stock rom zip, but assuming you want to just use the official image that you already have you'll need to flash with fastboot. I saw that you posted on the thread 'return to stock etc'. Follow those fastboot steps, but be aware that there is a major omission: the instructions only go to system.img_sparsechunk.8, but there are 9 of those files and the phone will not boot if you only flash 8. As you go through fastboot flashing I think there will be a couple files that will give errors. Do an internet search on the error output line, but if I remember correctly the files that won't flash are no big deal and didn't affect my phone when I went ahead and ignored the errors.
I did man... The problem is... Something trully god messed up here. I am now getting hard stops related to aboot failures. I saw something similar on the xt1033 forums but we miss those same files.
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
rp201 said:
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
Click to expand...
Click to collapse
Howdy! Sorry it's taken three months for your question to get any attention. Bionic forum's pretty dead, eh? I'm amazed it's still an officially supported Lineage device. Go team!
Sadly, the no one ever found a bootloader unlock, as a fellow informed me here two years ago. Unless some clever hacker happens upon a Bionic and decides to crack it for kicks, it's not likely to happen. But at least we have SafeStrap and Lineage!
You may know this already, but you didn't mention it in your post, so I'll go ahead and say: when installing a ROM like Lineage on the Bionic with SafeStrap, you need to install it on ROM Slot 1, not the Stock ROM Slot. I imagine that might be why you bricked your phone (I've done it myself a few times too ).
Now that I've given you the skinny on the Bionic's limitations, let's see if we can't get you back afloat. Whenever I bricked mine, I never used RDS Lite—I found a utility called House of Moto. You can find the home page here, but you'll need to create an account to see the important stuff and the downloads (you'll also need to install Java). But if you're more familiar with RDS Lite, feel free to use that instead
System images for the Bionic are hard to find nowadays. I seem to have found one link to an article with a direct download link to an update file at the bottom, which I'll link to here. Whether the update file is the same as an FXZ file RDS Lite/House of Moto requires, I'm not sure. Give it a try and see how it goes! If not, I may have a copy of the file on my old computer at my parents' house. If the linked update file doesn't work, I'll see if I can't get ahold of my image file.
Finally, if you do happen to get things up and running happily, I've got a list of optimizations that help Lineage run more smoothly.
Best of luck! :good: