What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Downgrade to 902 - No app or data loss

Yes, I got the message that stated it had copied and the hash check had matched.

I have some files in the root of the sdcard-ext named: Blur_Version.5.9.905.to.6.7.232.XT875...:blush:

OOPS, my bad... there it is! Seems my file manager was truncating the file named: Blur_Version.5.9.905.XT875.Verizon.en.US(67242).zip

I apologize for not being more thorough and for wasting your time. Mea culpa...

The 232 file you clearly downloaded from me... I named it that way exactly because of truncation.... But Lord Samuri likes his filename lol

Have to get mine where I can brother (SamuriHL)

Love,
Obsidian

Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
 
The 232 file you clearly downloaded from me... I named it that way exactly because of truncation.... But Lord Samuri likes his filename lol

Have to get mine where I can brother (SamuriHL)

Love,
Obsidian

Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2

ROFLMAO! I name them as I do for a good reason. I can't help it if people use crappy file managers that truncate filenames! :D (It's a joke, people...calm down! :D)
 
ROFLMAO! I name them as I do for a good reason. I can't help it if people use crappy file managers that truncate filenames! :D (It's a joke, people...calm down! :D)

I mainly use File Manager and had it in Grid Mode. When it finally dawned on me that I might see more of the file name if I used List, the damage was done-I'd exposed my ignorance. And mid-typing the file names I could "see" at that!

I'm still a bit embarrassed over it, but I'll survive... :) I've been in the business of chasing 1s and 0s around in machines for over 40 years and should have known better. It just goes to show that if one is lucky, one will learn something new every day.

Thanks again to all on the forum for their help.
 
I mainly use File Manager and had it in Grid Mode. When it finally dawned on me that I might see more of the file name if I used List, the damage was done-I'd exposed my ignorance. And mid-typing the file names I could "see" at that!

I'm still a bit embarrassed over it, but I'll survive... :) I've been in the business of chasing 1s and 0s around in machines for over 40 years and should have known better. It just goes to show that if one is lucky, one will learn something new every day.

Thanks again to all on the forum for their help.

No need to be embarrassed or concerned. You figured it out quick enough and there was no harm. I was telling Obsidian the reason for me naming them like that. Back in the 5.7.893 days I was off the OTA path. Someone devised a method for getting back on the OTA path by using some *SERIOUSLY* dark magic that involved bricking the phone in an ugly way. (basically replacing the boot partition with another image using dd) So I was one of the very first people to try it. Unfortunately, I had a couple different updates on my phone that weren't named very well. I flashed the wrong one and bricked the phone so bad that it took 36 hours of intense community help to fix it. Timmy10shoes ultimately got me unbricked using an RSD script. The HoB exists today because of that experience (and a little push from Timmy to make it happen :)). I wanted to give back to the community that helped me. But, I also made it my mission to create a better naming standard for the updates so people didn't flash the wrong one. Imagine thinking you're flashing 232, which allows you to FXZ back to 905, and accidentally getting the 235 update instead. Yes, it happened to someone in this thread that didn't use the HoB. That'd suck...
 
I'm trying to go from 232 to 242. To the best of my knowlage everythign is setup correctly, but when I go to push the update to the sd card it freezes at *Daemon started successfully*.
I used HoB to upgrade to 232 quite a while back, but I had manually loaded the files, and rebooted in fastboot. I had a similar issue back then when I tried to root where it would just freeze and nothign would happen.
Any suggestions?
 
Get a new phone? :D LOL! If it's not finding your device there can be a multitude of reasons for that. Here are a few:

-USB 3.0 port
-Bad moto drivers
-Haven't installed ADB drivers....boot into AP Fasboot, connect the phone, allow windows to see the phone, reboot both phone and windows
-Enable USB debugging mode on the phone
-Enable MTP mode on the phone
-Use USB cable that came with the phone

If you've done all that, I've been told by Matt that basically you have corrupt system data that prevents ADB from seeing the phone. That pretty much sucks. A factory data reset usually fixes it. Otherwise, manually copy the 242 update to your phone and verify the md5 hash manually. (Most file explorer programs allow you to get the hash of a file by going to properties, and hashtab on the windows side will give you the md5 of the file in the HoB dir. Verify they match.) Then manually reboot into AP Fastboot and start on option 3 of the second menu (after choosing the INSTALL 242 option on the first menu).
 
Thanks Samuri.
I thought for sure the ADB drivers were the problem, but no luck. I'm guessing it must be something corrupt.
I was able to manually update successfully.
FYI, I gave up and went to 242 because I was having issues with 232. About 3-4 times I received a call and the phone just instantly shut off. After it would power back up it would be fine, but I'm hoping it's resolved in 242.
Thanks again for all your help.
 
As long as you read and understood my warnings about 235+ (which clearly includes 242) FULLY, all should be well.
 
. Imagine thinking you're flashing 232, which allows you to FXZ back to 905, and accidentally getting the 235 update instead. Yes, it happened to someone in this thread that didn't use the HoB. That'd suck...

That's why anytime I shared 235, 238 or 242 I had added in the to 6.7.XXX to the file name. I then told them not to rename it or share it and definitely not to do both... If I was an ass I could have screwed everyone by switching my links. I mean how many of you actually check your version number...


Sent from my XT875 using Xparent SkyBlue Tapatalk 2
 
Well this is why I distribute my updates the way I do. Someone would have to remake my build script to screw with people. Just not worth it.
 
Thanks Samuri.
I thought for sure the ADB drivers were the problem, but no luck. I'm guessing it must be something corrupt.
I was able to manually update successfully.
FYI, I gave up and went to 242 because I was having issues with 232. About 3-4 times I received a call and the phone just instantly shut off. After it would power back up it would be fine, but I'm hoping it's resolved in 242.
Thanks again for all your help.

Was that while running stock 232 or a rom? And had you restored any system data? That is usually caused by restoring contacts/call log or any of the dialer components... if not cool but the 232 software isn't the culprit... there are at least a couple hundred of us running it stock and otherwise and that is not an issue that has shown its face...just sayin like the OG version of Ice Cube said "chickety-check yo self before you wreck yo self"

Sent from my XT875 using Xparent SkyBlue Tapatalk 2
 
Last edited:
Well this is why I distribute my updates the way I do. Someone would have to remake my build script to screw with people. Just not worth it.

Yeah adding in that extra little check was a good idea... damn I almost said what the check was and then I realized that would be a little counter productive lol

Sent from my XT875 using Xparent SkyBlue Tapatalk 2
 
Back
Top