Related
I'm rooted and originally de-crapped my phone which kept the first update from installing. However, with some help from posters here I was able to find the missing file, get it properly replaced and the update then worked.
I assumed that would mean I would be good from then on and kept everything intact. Now the latest update is out and I once again cannot update but it's been long enough that I'm now not sure about the process for getting this working.
Any help would be appreciated.
Agrajag27 said:
I'm rooted and originally de-crapped my phone which kept the first update from installing. However, with some help from posters here I was able to find the missing file, get it properly replaced and the update then worked.
I assumed that would mean I would be good from then on and kept everything intact. Now the latest update is out and I once again cannot update but it's been long enough that I'm now not sure about the process for getting this working.
Any help would be appreciated.
Click to expand...
Click to collapse
Come on guy, there is like 10 other threads over here talking about not being able to install the update. Anyway, there is a thread right here that has all of the apk files of the device. I cant find it now cause im on my cell. Ifyou cant find it by the time I finish work I'll post the link. that didnt work for me so I fastbooted my phone with the factory image, rooted, protected root, unrooted,install one update, installed the latest update, and restored root. good luck.
I actually looked but didn't notice others having an issue so I might have just missed it. I assumed, like last time, others would have the issue so I was actually surprised not to find 10 threads with people talking about it.
I couldnt find the thread i was talking about cause my stupid self was too lazy to click one button to add it to my favorites but it looks like this could work for you.
http://forum.xda-developers.com/showthread.php?t=1362956
Yesterday I wasted a significant amount of time trying to update my stock AT&T branded HTC Titan from 7.1 (7720) to 7.8. I figured I would provide what I learned in order to get it working.
1. Backup your phone.
2. If you haven't updated your bootloader from the one that shipped with the phone, you need to do so. You'll get an error otherwise.
Instructions and download link here. I had to factory reset my phone before the HTC update program would recognize that the Titan was connected to my PC.
3. Follow the standard instructions from here: http://forum.xda-developers.com/showthread.php?t=1306415, choosing everything from 7720 (7.0.7403.0 - 7.10.8107.79) to the recent 7.8 cabs. I only needed the English language files for my update to work. You can put them all in the root folder for WP7 Update Cab Sender. Hit send.
4. Wait patiently.
5. Setup your phone again.
6. Enjoy.
I'm not responsible if this doesn't work for you, or if it messes up your phone. I just thought it might be helpful to someone not looking to waste their time.
outismetis said:
Yesterday I wasted a significant amount of time trying to update my stock AT&T branded HTC Titan from 7.1 (7720) to 7.8. I figured I would provide what I learned in order to get it working.
1. Backup your phone.
2. If you haven't updated your bootloader from the one that shipped with the phone, you need to do so. You'll get an error otherwise.
Instructions and download link here. I had to factory reset my phone before the HTC update program would recognize that the Titan was connected to my PC.
3. Follow the standard instructions from here: http://forum.xda-developers.com/showthread.php?t=1306415, choosing everything from 7720 (7.0.7403.0 - 7.10.8107.79) to the recent 7.8 cabs. I only needed the English language files for my update to work. You can put them all in the root folder for WP7 Update Cab Sender. Hit send.
4. Wait patiently.
5. Setup your phone again.
6. Enjoy.
I'm not responsible if this doesn't work for you, or if it messes up your phone. I just thought it might be helpful to someone not looking to waste their time.
Click to expand...
Click to collapse
Upgrade your bootloader to what; the HTC update to 2.6.160015.3 or Cotullah's HSPL? If you opt to use Cab Sender you may update from 7720 to 7740 to 8107 to 8112 to 8773 one build at a time or if you set it up correctly all of the incremental builds in order. I'm assuming you tacked on 8858 to the list or did it separately. I'm curious to know if there is anything different at the core of the "official" update than what currently is available on custom ROMs but for those of us who are HSPL and using 7.8, we'll patiently wait until chefs here take a look at it and deploy their magic.
berrywr said:
Upgrade your bootloader to what; the HTC update to 2.6.160015.3 or Cotullah's HSPL? If you opt to use Cab Sender you may update from 7720 to 7740 to 8107 to 8112 to 8773 one build at a time or if you set it up correctly all of the incremental builds in order. I'm assuming you tacked on 8858 to the list or did it separately. I'm curious to know if there is anything different at the core of the "official" update than what currently is available on custom ROMs but for those of us who are HSPL and using 7.8, we'll patiently wait until chefs here take a look at it and deploy their magic.
Click to expand...
Click to collapse
Yes, in order to do the cab method on the ATT Titan, you do need to upgrade to the 2.6 bootloader. -don't really know why though. As several Titans could not go through the full cab upgrade process to Tango without it.
Upgraded to 7.8
I used the jaxbot Seven-Eighter app on windows phone hacker website (its a name not a hack) and it worked like a charm. I have (had) a locked 7720 ATT Titan (1) and used first jaxbot's updater to make sure the phone had 7720, then upgraded thru all the intermediate releases to 8858. Yeah it took some time, maybe 5-7 minutes per build, but after 30 minutes I was done with no loss in already installed apps, texts, phone calls, passwords or....
8858 is not such-a-much in the "bells and whistles" department; in fact, the only changes I saw (as expected) were the ability to small size the tiles and have more and starker background colors. I am sure there are lots of under-the-covers changes and bug fixes that are not so obvious. But after failing to upgrade my Titan while trying debranding, CABing to gold carding over the past year, all to no avail, it sure was nice to smoothly go to 7.8.
And what a rush. After a year of no ROM loads on the Titan, compared to having averaged 1 new flash PER WEEK on my Fuze, Tilt I, Tilt II, and HD7S - wow what a fix.
derylmccarty said:
I used the jaxbot Seven-Eighter app on windows phone hacker website (its a name not a hack) and it worked like a charm. I have (had) a locked 7720 ATT Titan (1) and used first jaxbot's updater to make sure the phone had 7720, then upgraded thru all the intermediate releases to 8858. Yeah it took some time, maybe 5-7 minutes per build, but after 30 minutes I was done with no loss in already installed apps, texts, phone calls, passwords or....
8858 is not such-a-much in the "bells and whistles" department; in fact, the only changes I saw (as expected) were the ability to small size the tiles and have more and starker background colors. I am sure there are lots of under-the-covers changes and bug fixes that are not so obvious. But after failing to upgrade my Titan while trying debranding, CABing to gold carding over the past year, all to no avail, it sure was nice to smoothly go to 7.8.
And what a rush. After a year of no ROM loads on the Titan, compared to having averaged 1 new flash PER WEEK on my Fuze, Tilt I, Tilt II, and HD7S - wow what a fix.
Click to expand...
Click to collapse
You're Air Force? I'm a former weather forecaster now in college full-time majoring in mathematics (calculus) to compliment my meteorology training. HSPL is by no means an easy task though I successfully did it twice but each very different experiences. Prior to HSPL the devices I incrementally added those builds too via Cab Sender. I'm not aware the official release is any different than those of us custom flashing our devices; the build we're using is also 8858.136 and as you know when it boils down to the OS it's mostly cosmetics though I saw some security updates and Bluetooth compatibility but like 7.x and 8.x you still can't use a Bluetooth keyboard on the Titan. What drove me nuts about Windows Phone is the inability to side load apps which I think is just ridiculous. There is an incredible amount of apps out there not on any the varying Marketplaces which again seems stupid to me but by far Nokia has a good selection of apps though many are redundant among the other device makers. I loved my Rhodium (Touch Pro 2/Tilt II) which I flashed the hell out of that thing and continue to use it as a GPS device and backup phone. I have an HD2 that like many here I've done about everything with and it runs Windows Phone 7.8 flawlessly though at the moment I have Jellybean on it.
berrywr said:
Upgrade your bootloader to what; the HTC update to 2.6.160015.3 or Cotullah's HSPL? If you opt to use Cab Sender you may update from 7720 to 7740 to 8107 to 8112 to 8773 one build at a time or if you set it up correctly all of the incremental builds in order. I'm assuming you tacked on 8858 to the list or did it separately. I'm curious to know if there is anything different at the core of the "official" update than what currently is available on custom ROMs but for those of us who are HSPL and using 7.8, we'll patiently wait until chefs here take a look at it and deploy their magic.
Click to expand...
Click to collapse
but my device is error HSPL.i update your bootloader to 2.6,but it isn't succesfull.HElP ME!
thuan92xd said:
but my device is error HSPL.i update your bootloader to 2.6,but it isn't succesfull.HElP ME!
Click to expand...
Click to collapse
naw, try seven eighter..and see if that works first...
derylmccarty said:
I used the jaxbot Seven-Eighter app on windows phone hacker website (its a name not a hack) and it worked like a charm. I have (had) a locked 7720 ATT Titan (1) and used first jaxbot's updater to make sure the phone had 7720, then upgraded thru all the intermediate releases to 8858. Yeah it took some time, maybe 5-7 minutes per build, but after 30 minutes I was done with no loss in already installed apps, texts, phone calls, passwords or....
8858 is not such-a-much in the "bells and whistles" department; in fact, the only changes I saw (as expected) were the ability to small size the tiles and have more and starker background colors. I am sure there are lots of under-the-covers changes and bug fixes that are not so obvious. But after failing to upgrade my Titan while trying debranding, CABing to gold carding over the past year, all to no avail, it sure was nice to smoothly go to 7.8.
Click to expand...
Click to collapse
Is there a difference between upgrading to 7.8
- via the seven eighter or
- via the official at&t update (that is not available yet)?
It's probably a stupid question as at&t doesn't have anything for the Titan, but I'm wondering if there are differences usually?
Different marketplace? Different drivers? Different ringtones? Anything?
Update: I see it doesn't change anything, which is pretty cool!
mreaglejr said:
Is there a difference between upgrading to 7.8
- via the seven eighter or
- via the official at&t update (that is not available yet)?
It's probably a stupid question as at&t doesn't have anything for the Titan, but I'm wondering if there are differences usually?
Different marketplace? Different drivers? Different ringtones? Anything?
Update: I see it doesn't change anything, which is pretty cool!
Click to expand...
Click to collapse
There "might"/should be a new bootloader -seeing the ATT Titan is still at stock SPL ..."IF" ATT does push out the update. But seeing that T-Mobile skipped the official 7.8 update for their devices, my reassurance that the ATT Titan will actually receive an official update is somewhat diminishing now.
But honestly, everyone is better off just doing the cab method...or attempting the unlock process. Grandma death will be knocking at your door if you end up waiting for an official update from our stupid carrier.
xconomicron said:
There "might"/should be a new bootloader -seeing the ATT Titan is still at stock SPL ..."IF" ATT does push out the update. But seeing that T-Mobile skipped the official 7.8 update for their devices, my reassurance that the ATT Titan will actually receive an official update is somewhat diminishing now.
But honestly, everyone is better off just doing the cab method...or attempting the unlock process. Grandma death will be knocking at your door if you end up waiting for an official update from our stupid carrier.
Click to expand...
Click to collapse
Completely agree with that last sentiment; twice promises were made and twice broken and now there is this stupid law in regards to carriers and subsidy "locked" devices.
berrywr said:
Completely agree with that last sentiment; twice promises were made and twice broken and now there is this stupid law in regards to carriers and subsidy "locked" devices.
Click to expand...
Click to collapse
Give a cookie to the carriers...the next thing they want, the entire batch.
same error with seven eighter on my titan, now i tryed on cingular rom, update from 8112-8773 shows the error, i slected corresponding language,what is problem?
nikola92 said:
same error with seven eighter on my titan, now i tryed on cingular rom, update from 8112-8773 shows the error, i slected corresponding language,what is problem?
Click to expand...
Click to collapse
interesting, I used seven eighter on a half-bricked ATT titan (stuck on the euro 1.9 rom). the only errors I got were after the update process...with certain languages not installed -causing applications to not respond. I flashed via goldcard to the 1.9 rom after and redid the update process with the correct languages and everything worked.
I know you have been half-bricked for awhile nikola, is it possible for you to flash via goldcard to a euro rom? IF so you would most likely get the 7.8 update through zune (which I was actually working for me until I decided to just do the seven eighter app).
its like u said install spl 2.6 and we roll now i have wp 7.8
I am on HSPL and for some reason I cannot upgrade to SPL 2.6. It loads fine via RUU but the SPL never changes to 2.6, stays stuck on 2.5 even though I have HSPL. Beccause of this I guess I cannot get 7.8 update either
nikola92 said:
its like u said install spl 2.6 and we roll now i have wp 7.8
Click to expand...
Click to collapse
lund123 said:
I am on HSPL and for some reason I cannot upgrade to SPL 2.6. It loads fine via RUU but the SPL never changes to 2.6, stays stuck on 2.5 even though I have HSPL. Beccause of this I guess I cannot get 7.8 update either
Click to expand...
Click to collapse
It will never change to SPL 2.6 after flashing the 2.6 SPL. -simply because you are stuck.
However, for some reason, it will let you upgrade to 7.8 if you do flash 2.6 (even though it did not change)
true +1
Great Info on upgrading HTC Titan to Windows 7.8
Thanks a million. I had wasted a couple of evenings trying to upgrade and keep getting error messages. I followed your recommendation and updated my bootloader from the HTC website and used the Sharp&7Loader and that was it. After about one hour I have 7.8 on my HTC Titan phone.
outismetis said:
Yesterday I wasted a significant amount of time trying to update my stock AT&T branded HTC Titan from 7.1 (7720) to 7.8. I figured I would provide what I learned in order to get it working.
1. Backup your phone.
2. If you haven't updated your bootloader from the one that shipped with the phone, you need to do so. You'll get an error otherwise.
Instructions and download link here. I had to factory reset my phone before the HTC update program would recognize that the Titan was connected to my PC.
3. Follow the standard instructions from here: http://forum.xda-developers.com/showthread.php?t=1306415, choosing everything from 7720 (7.0.7403.0 - 7.10.8107.79) to the recent 7.8 cabs. I only needed the English language files for my update to work. You can put them all in the root folder for WP7 Update Cab Sender. Hit send.
4. Wait patiently.
5. Setup your phone again.
6. Enjoy.
I'm not responsible if this doesn't work for you, or if it messes up your phone. I just thought it might be helpful to someone not looking to waste their time.
Click to expand...
Click to collapse
Sorry if this is already answered, but I searched around and couldn't find it.
I tried to flash to CM12, but I have too old of a bootloader.
I reverted everything to stock, but I have never been able to get any OTA updates.
I downloaded the 322 update from huawei's site (from her http://consumer.huawei.com/us/support/downloads/detail/index.htm?id=52043) but when I try to install it from my SDCard I get the following error:
oemsbl version list check error!
'E ,write data error
Error:update.app is a invalid package
Error:SD card update failure,SD card update abort!
My end goal is to get on CM12 or some other rom that lets me get rid of all of the stock rom craziness.
Any ideas or can someone point me in a direction?
Thanks in advance!
bot2600 said:
Sorry if this is already answered, but I searched around and couldn't find it.
I tried to flash to CM12, but I have too old of a bootloader.
I reverted everything to stock, but I have never been able to get any OTA updates.
I downloaded the 322 update from huawei's site (from her http://consumer.huawei.com/us/support/downloads/detail/index.htm?id=52043) but when I try to install it from my SDCard I get the following error:
oemsbl version list check error!
'E ,write data error
Error:update.app is a invalid package
Error:SD card update failure,SD card update abort!
My end goal is to get on CM12 or some other rom that lets me get rid of all of the stock rom craziness.
Any ideas or can someone point me in a direction?
Thanks in advance!
Click to expand...
Click to collapse
Does your phone really have B146 or do you have B148 or B126?
You're on the right path. You must first successfully install B322 before you can install CM or any other non-stock ROMs.
Make sure you follow the Huawei B322 upgrade instructions very carefully.
See http://forum.xda-developers.com/asc...icial-b322-available-public-download-t3193929
divineBliss said:
Does your phone really have B146 or do you have B148 or B126?
You're on the right path. You must first successfully install B322 before you can install CM or any other non-stock ROMs.
Make sure you follow the Huawei B322 upgrade instructions very carefully.
See http://forum.xda-developers.com/asc...icial-b322-available-public-download-t3193929
Click to expand...
Click to collapse
Your edit is looking at the same thing I was looking at I had followed those directions but it looks like the issue is that I am on b146. The build number that shows up on my device is MT2-L03V100R001C642B146.
I guess I need to poke around and see if I can get it on B148 first, then try the update again, but B148 might have a prereq of B126
Madness!
Either way it is late, so I might just leave it be until tomorrow and pick back up. Thanks for the help!
Edit:trying to download B148 now, they are both 4.3, so who knows how this is going to go
I know Huawei has files and instructions to go from B322 back down to B148. I don't know anything about B146.
The B322 instructions reference B126 and B148, but no mention of B146.
divineBliss said:
I know Huawei has files and instructions to go from B322 back down to B148. I don't know anything about B146.
The B322 instructions reference B126 and B148, but no mention of B146.
Click to expand...
Click to collapse
Yep, I am downloading B148 and am going to try to install it. If that doesn't work, I will probably follow the soft bricked instructions to force wipe it back to B126 and then roll forward from there.
Good times!
B146 is Consumer Cellular phone. Not stock mate 2.
After all the madness, I hope you are not like some who don't like the new stuff and end up downgrading ... Time for me to zzzzzzz.
divineBliss said:
After all the madness, I hope you are not like some who don't like the new stuff and end up downgrading ... Time for me to zzzzzzz.
Click to expand...
Click to collapse
I was able to successfully install B126, but it is time for zzzz's here too. I doubt I will want to downgrade, my biggest complaint is the alternate default apps that Huawei uses cause some weird behaviors with bluetooth integration. Especially with my car, my headphones and the Pebble. And even if I use the normal apps (music etc) the integration doesnt work at all since their rom doesnt see them as the default system app.
Plus I have used CM on some other devices and always liked it
Moody66 said:
B146 is Consumer Cellular phone. Not stock mate 2.
Click to expand...
Click to collapse
I might have accidentally installed it at some point returning to stock. My phone is on of the sim unlocked phones from Walmart (not the prepaid, just the unlocked).
User error on my part Thanks for the info!
bot2600 said:
I was able to successfully install B126, but it is time for zzzz's here too. I doubt I will want to downgrade, my biggest complaint is the alternate default apps that Huawei uses cause some weird behaviors with bluetooth integration. Especially with my car, my headphones and the Pebble. And even if I use the normal apps (music etc) the integration doesnt work at all since their rom doesnt see them as the default system app.
Plus I have used CM on some other devices and always liked it
Click to expand...
Click to collapse
That awesome.... Should be downhill now.
I suggest you consider skipping CM and install PACROM or Carbon, which are both based on CM. I prefer PACROM. You should also consider Dual Boot / Multiboot - I use it to run multiple ROMs. You could install all three and see which one you like the best.
divineBliss said:
That awesome.... Should be downhill now.
I suggest you consider skipping CM and install PACROM or Carbon, which are both based on CM. I prefer PACROM. You should also consider Dual Boot / Multiboot - I use it to run multiple ROMs. You could install all three and see which one you like the best.
Click to expand...
Click to collapse
Thanks for the suggestion, I will definitely try all three. I am running around all day getting ready for Halloween so it probably won't happen today though, but I agree, things should be relatively straightforward from here
bot2600 said:
Thanks for the suggestion, I will definitely try all three. I am running around all day getting ready for Halloween so it probably won't happen today though, but I agree, things should be relatively straightforward from here
Click to expand...
Click to collapse
I'd personally recommend you install PACROM first ('cause you might like it so much, you won't bother with the other two ) , then once you are comfortable that you have a solid installation, after a few days go install Dual Boot/Multiboot : http://forum.xda-developers.com/ascend-mate2/themes-apps/patcher-multi-boot-t3222899/page1 in order to install some other ROMs.
divineBliss said:
I'd personally recommend you install PACROM first ('cause you might like it so much, you won't bother with the other two ) , then once you are comfortable that you have a solid installation, after a few days go install Dual Boot/Multiboot : http://forum.xda-developers.com/ascend-mate2/themes-apps/patcher-multi-boot-t3222899/page1 in order to install some other ROMs.
Click to expand...
Click to collapse
Thanks, I think I have just hosed it at this point. B126 still works, but it sees no OTA updates and won't take B148, B309 or B322 (guessing on the version numbers I tried). It continues to get the same error. I've reset the phone a couple times, wiped cache etc, but something somewhere makes it sad.
Thanks for the guidance and ideas, but I think the powers that be are telling me to get a new phone. I am trying to decide between the note 5, nexus 6p or wait for the new windows phone (950 xl). I could just buy another MT2L03, but if I am going to spend money on another phone, I might as well get one that I dont have to muck about with to clean up all of the forced apps etc
bot2600 said:
Thanks, I think I have just hosed it at this point. B126 still works, but it sees no OTA updates and won't take B148, B309 or B322 (guessing on the version numbers I tried). It continues to get the same error. I've reset the phone a couple times, wiped cache etc, but something somewhere makes it sad.
Thanks for the guidance and ideas, but I think the powers that be are telling me to get a new phone. I am trying to decide between the note 5, nexus 6p or wait for the new windows phone (950 xl). I could just buy another MT2L03, but if I am going to spend money on another phone, I might as well get one that I dont have to muck about with to clean up all of the forced apps etc
Click to expand...
Click to collapse
You have to go through the CC conversion. You can't just flash a different version to it.
Moody66 said:
You have to go through the CC conversion. You can't just flash a different version to it.
Click to expand...
Click to collapse
Thanks, I know somewhere along the line I must have flashed CC to it when I was restoring it (did a lot of tinkering when I first got it), but I am pretty sure it wasn't originally a CC phone. I picked it up from this link: http://www.walmart.com/ip/HUAWEI-As...M-4G-LTE-Android-Smartphone-Unlocked/42287058 which I read as just being unlocked, not being on any prepaid network.
Like I said earlier, I think it ending up with a CC rom on it somewhere along the way was just user error on my part
bot2600 said:
Thanks, I know somewhere along the line I must have flashed CC to it when I was restoring it (did a lot of tinkering when I first got it), but I am pretty sure it wasn't originally a CC phone. I picked it up from this link: http://www.walmart.com/ip/HUAWEI-As...M-4G-LTE-Android-Smartphone-Unlocked/42287058 which I read as just being unlocked, not being on any prepaid network.
Like I said earlier, I think it ending up with a CC rom on it somewhere along the way was just user error on my part
Click to expand...
Click to collapse
Use Xordos post for repairing a bricked phone. It will get you to b148.
Moody66 said:
Use Xordos post for repairing a bricked phone. It will get you to b148.
Click to expand...
Click to collapse
Ah, I used that post already but grabbed a B126 build instead. I will flip my recovery back and restore to B148 instead, good idea
Don't know what I was thinking at the time to go to B126, but it was really late, so that's my excuse
Edit: I see why I ended up on B126, he says to use the file TWRP_BACKUPS_stock-system-with-root.zip to restore the system partition, that file takes you back to B126, not B148.
Second Edit:I went back to see what files he had in his little area and saw there was a full B148.zip, so I flashed it with TWRP. I might try to update again from there, I assume I can't flash any higher as the B3xx builds the partitions changed, right?
I might have an answer, it looks like this version of the phone might not be supported, though its a bit unclear from the thread, but it does reference the phone that I have.
https://community.gethuawei.com/devices/mate_2/f/2/t/2672
Oh, and it looks like it did come with B146, I think its just time to get a new phone, thank you all for the time you spent though
bot2600 said:
I might have an answer, it looks like this version of the phone might not be supported, though its a bit unclear from the thread, but it does reference the phone that I have.
https://community.gethuawei.com/devices/mate_2/f/2/t/2672
Oh, and it looks like it did come with B146, I think its just time to get a new phone, thank you all for the time you spent though
Click to expand...
Click to collapse
I thought you said you have an MT2-L03 ....... does that not imply it's 16GB flash memory/ROM?
Did you put he B126 recovery back on the phone with your B126 ROM? My phone (non-CC) came out of the box with B148, then I went to B322, then PACROM, then Dual Boot, etc, etc.
Hopefully, you can get this to work ....... even if your heart is sent on a new phone. Then you can sell this one or give it to family, etc, etc .... maybe get some money out of it . Good luck.
divineBliss said:
I thought you said you have an MT2-L03 ....... does that not imply it's 16GB flash memory/ROM?
Did you put he B126 recovery back on the phone with your B126 ROM? My phone (non-CC) came out of the box with B148, then I went to B322, then PACROM, then Dual Boot, etc, etc.
Hopefully, you can get this to work ....... even if your heart is sent on a new phone. Then you can sell this one or give it to family, etc, etc .... maybe get some money out of it . Good luck.
Click to expand...
Click to collapse
Looks like I was wrong, mine is 16 gig, so ignore that link
I am not set on a new phone, but I am set on being done mucking about, I have a couple apps like RSA token things etc that are a pain when I wipe my phones. I am pretty sure I bought mine before B148 came out, but who knows, it all melts together. I write mobile apps for work so I have a bunch of random iphone, android phones and even a couple windows phones lying around, but this one has me so spoiled by its big screen, that I can't imagine going back to anything 5" or smaller, and the wife claimed the 6S plus, so what are you going to do
I might mess around with this a bit more, but Monday fast approaches and it is time to be productive again
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
I downloaded the image yesterday but going to delete it.
The update was actually pushed to my device today by Google... but it won't install due to an E3005 error related to the modem. I'm not sure, though, if the issue is with this update or if it's something specific to my device.
SpookyTunes said:
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
Click to expand...
Click to collapse
Thanks for the heads up. Have you flashed it?
new update was sucessfully installed on my nexus via official ota update
tropical cactus said:
Thanks for the heads up. Have you flashed it?
Click to expand...
Click to collapse
Not yet without knowing what the issue with it is. I may get brave on the weekend though
SpookyTunes said:
Not yet without knowing what the issue with it is. I may get brave on the weekend though
Click to expand...
Click to collapse
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
It appears to have a new radio 3.87 , maybe there are some problems with that
tropical cactus said:
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
Click to expand...
Click to collapse
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Ofrine said:
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Click to expand...
Click to collapse
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
rhardy613 said:
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
Click to expand...
Click to collapse
So you installed the may update?,how is it so far.
side-loaded the may ota file via adb and it seems to work a-ok so far... i had installed opm5 before as well via this method so perhaps there is some under the hood issue nobody has noticed yet...
Not Yet Available
If you go to the Android News blogspot it states that the Nexus 6P update is "Not Yet Available" ...
I'd post the link, but it says new members are not allowed for 10 days or something like that, sorry!
Installed may update using flashfire.seems fine to me so far.seems little faster,but could be cause of clean install,rooted and debloated also.when Google releases new update I will probably install that too.just curious why it was pulled,a bug,or was there something we got that we weren't supposed too??
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
VersusMe_ said:
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
Click to expand...
Click to collapse
So far still running good for me,no message when I reboot either.
I just realized that the power save mode is not functioning on my 6P and was before may OTA ( cannot be toggled and does not turn on below 15%) not a game-changer but could be why it was pulled or it could just be a hiccup on an aging device
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
[email protected] said:
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
Click to expand...
Click to collapse
My phone says it has the OTA, but as I did some system modifications, I need the factory image, which yet has to appear.
Have any of you installed from the first link? If so, how did that go? I wan to do the OTA, but I am a bit worried it will be corrupt or that it isn't the correct file.
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
LaMontreBelge said:
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
Click to expand...
Click to collapse
RSD lite doesn't work with most Windows 10 machines, use Windows 7. http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
If you want to save data you need to modify the .XML file if using RSD Lite
Lots of issues can cause a boot loop, bad battery, bad app, bad hardware... even a bad charger or USB cable.
Try [Utility] - = MotoFlashPro =
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
LaMontreBelge said:
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
Click to expand...
Click to collapse
Hi again, quick update, I plugged it into my Windows Xp machine as I do not have a windows 7 computer, and it appeared. Also, could you please tell me what to change in the xml file in order to keep the data ?
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
LaMontreBelge said:
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
Click to expand...
Click to collapse
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Smu1zel said:
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Click to expand...
Click to collapse
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Also, I just checked in the other file I found, for an english-languaged model this time, it does have these lines, but is only 560mb instead of the 800 something of my french file
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at. But I doubt it's corrupt.
Smu1zel said:
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at.
Click to expand...
Click to collapse
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
LaMontreBelge said:
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
Click to expand...
Click to collapse
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Smu1zel said:
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Click to expand...
Click to collapse
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
LaMontreBelge said:
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
Click to expand...
Click to collapse
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Smu1zel said:
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Click to expand...
Click to collapse
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
LaMontreBelge said:
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
Click to expand...
Click to collapse
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Okay, i just took a look at the doc linked, and I have no idea how you found it, but it is mind boggling. All the roms, listed, just like that. Thank you so much. And yes indeed the bootloader is different, and I wouldn't risk it. I'll keep looking for the 2.3.5 ROM, but for now it seems like a lost cause. Perhaps they have it over on the Motorola forums. I'll make a thread later today.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Smu1zel said:
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Click to expand...
Click to collapse
This thread does indeed help a little bit, but the firmware center link does not, as it is where i got my 2.3.6 ROM from, and as far as I know, is the only french one. Honestly I do not care if it's an English one, I just want to make sure that it won't mess up the phone
LaMontreBelge said:
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Click to expand...
Click to collapse
Yeah I think those links might be out of date. Go under "XT910" and look at some of the links. Also I found that doc under that section.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
I hope I'm not leading you down a wrong path, hopefully he responds soon. Maybe the bootloader doesn't matter, I don't know.