Database Info

[Q] Can't receive update to 8.4.4.11

I rooted my transformer using the pure root method in the development transformer forums for devices that already received 3.1. People have said that they receive their update and unroots their device, but I haven't even received the FOTA. I only rooted my device; without clockwork or a custom rom. I did delete some pre installed programs (bloatware) with titanium backup but I re installed them. Not sure if the damage has been done but I want someone to confirm if that can be the issue and how do I go about to properly reinstall the bloatware.

I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....

Danny80y said:
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Click to expand...
Click to collapse
I am having the exact same problem and a lot of people will. Once you root and try to unroot it appears you cannot receive anymore OTA or make them work for that matter. I have found how to get the notification telling me that the .11 update is available for me. (Place the update file in sdcard/asus/update/) and then rename it US_epad-user-8.4.4.11.zip and rebooting. After this you can choose to make the update but it will not work. It will just go to the stock recovery with the android and the exclamation after a one second loading appearing that it will work. After you turn it off and back on it will tell you (System Update Failed Error (12) )Still trying to figure out why it is not accepting the update.

You can get the update in the "Just got an OTA update" thread.

Thank you for that valuable information. It worked like a charm. Now I just need the original update for the dock.
Sent from my Nexus S 4G using Tapatalk

...................

martijua said:
You can get the update in the "Just got an OTA update" thread.
Click to expand...
Click to collapse
I guess I'll have to manually install. Let's see how it turns out...

for just patiently wait for FOTA or rooted repack... The improvements are not HUGE.

TheIneffable said:
I guess I'll have to manually install. Let's see how it turns out...
Click to expand...
Click to collapse
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms

TheIneffable said:
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
Click to expand...
Click to collapse
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk

Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Guess I'll wait for a rooted 3.2 to come out.

You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.

It's weird because, I downloaded the txt, and rename it, placed it on the root of the so card and the update passed flawlessly.
Sent from my Transformer TF101 using Tapatalk

Fixter said:
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
"Then press volume up when you see the text on the top left of the screen"
I did it just how the instructions stated but I never saw the text on the top left of my screen. It just boots up normally with stock boot animations. The update notification is not present either. I guess I'll try and see if not renaming it might help. Even though I don't think leaving the file extension to just "file" will help. I'll try...

Digiguest said:
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
Click to expand...
Click to collapse
hmm...Probably because you extracted the .zip to the SD card. It just stated to move the .zip to the sd card. Maybe extracting might work.

None of the methods worked. Guess I'll be installing roms. I guess when I deleted some of the preinstalled apps, my device became disqualified for any sort of updates.

I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?

superevilllama said:
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Click to expand...
Click to collapse
Read the first post of this thread to properly flash the update when renamed to ep101_sdupdate.zip:
http://forum.xda-developers.com/showthread.php?t=1171116

Carl LaFong said:
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
Click to expand...
Click to collapse
haha. Who's *****ing? My transformer still works great. Just wanted to diagnose why I wasn't getting an update so I can be more informed about it and see if I should just stick to installing roms or unroot.

Right. That says exactly what I just said, and did. Anyway.. I eventually got it to work. I had to go compeletly back to stock as apparently deleting stuff from the stock rom altered it enough that the update didn't see it as the same rom.
Tried to root after and got froze up at the boot screen like everyone else. Been playing with this too long. Understanding that we risk messing up our devices by rooting and such.. other issues that are in complete control of Asus such as build quality... IE light bleed, bezel issues, freezing, touch screen not sensing touch are making me rethink this product. Sigh. Sucks too because the idea is awesome. Just wish the build quality was there.

[Q] Motorola Xoom Tablet 3G + WiFi needs upgraded, rooted, and unlocked

Hi there XDA community,
I would like to know if there is an up-to-day tutorial that has working file links? I would like to upgrade, root, and unlock my Xoom. I just bought a Motorola Xoom from 1saleaday.com the Model is an MZ601 and says "approved by IDA for use in Singapore" it is currently just as is and is not unlocked or rooted. I would like to get it upgraded, unlocked, and rooted so I can use it for what I got it for. It has WiFi and Data service that supports WCDMA 850/900/1900/2100, GSM 850/900/1800/1900, ATO_ITEM: AP1520AD3X3. It is currently running on Android Honeycomb 3.0.1, build number H.6.1-38-9. If you any ideas, files, links, tutorials (up-to-day), or can help, that would be great!
Thanks InfiniteImmortal.
P.S.
Here are the configurations;
Model Number: MZ601
Android version: 3.0.1
Firmware: GAS_ASIA_USAEVRSTURTIRD_P016
Baseband version: N_014.83.28P
Baseband configuration: UCAEVEUB1B8EU034.0R
Kernel: 2.6.36.3 [email protected] #1
Build Number: H.6.1-38-9
More specs will be provided if they are needs, thanks again II!

yeah, there are tons of tutorials, relatively up to date. Relatively, because the new method to root xyboards might work for classic xooms too. This method would not require you to unlock your xoom for rooting and thus allow titanium backup to backup all your data before unlocking and thus wiping your xoom.
Just from the first page in the Q/A- and Xoom-general forums:
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
Xoom root and bootloader unlock (a post by me)
and maybe this
[HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg

I order one from the same seller on E-bay today
and for sure need the same help
but I need some Q
is the seller ship the item quikly for you ?
is this come in sealed box ?
sorry but I'm afraid of them

Response to purity0flove
purity0flove said:
I order one from the same seller on E-bay today
and for sure need the same help
but I need some Q
is the seller ship the item quikly for you ?
is this come in sealed box ?
sorry but I'm afraid of them
Click to expand...
Click to collapse
It only took a week for me to get mine via UPS. The box came to my house sealed, it had never been opened. But I bought a new one, not a refurbished one. Hope this could help.
II

Response to llama-power
llama-power said:
yeah, there are tons of tutorials, relatively up to date. Relatively, because the new method to root xyboards might work for classic xooms too. This method would not require you to unlock your xoom for rooting and thus allow titanium backup to backup all your data before unlocking and thus wiping your xoom.
Just from the first page in the Q/A- and Xoom-general forums:
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
Xoom root and bootloader unlock (a post by me)
and maybe this
[HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg
Click to expand...
Click to collapse
Okay I will go and read these threads, but are you for sure they work on the EU models? I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore. This is one reason why I'm looking for an up-to-date threads that say they work with the EU models. If you could clarify more that would be great.
Thanks, II

InfiniteImmortal said:
It only took a week for me to get mine via UPS. The box came to my house sealed, it had never been opened. But I bought a new one, not a refurbished one. Hope this could help.
II
Click to expand...
Click to collapse
yes I ordered one from 1saleaday.com on E-bay .. this seller buy also on E-bay ... new not Refurbished ! and ship with UPS but didn't now still didn't ship and wait for him !

InfiniteImmortal said:
Okay I will go and read these threads, but are you for sure they work on the EU models?
Click to expand...
Click to collapse
Yes, the one post I have marked with "(a post by me)" is exactly how I rooted my xoom and that is a german MZ601. And it works, no brick
InfiniteImmortal said:
I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore.
Click to expand...
Click to collapse
That is weird. I have never read a thread about a brick that occured using the method I (and others) described. Could you maybe post a link to such a thread?
To Clarify this: the Unlock should impose absolutely no risk at all as it is a feature implemented by motorola. The recovery, even if it didn't work, wouldn't lead to a brick. And the universal xoom root should not do any magic either, it should only add two files to the filesystem (su and Superuser.apk) and remove those files that would make your new shiny recovery go byebye once booted
Ty my knowledge, only the "flashing a custom rom" part is a source of bricking. And that can easily be avoided by flashing a MZ601-rom instead of something else
That said, nobody can guarantee you that this is completely safe. There is a thread right next door with a poor guy whose xoom bricked itself overnight. That was a wifi-xoom, and so far no one knows why that happened. We're still working on a solution, though

InfiniteImmortal said:
Okay I will go and read these threads, but are you for sure they work on the EU models? I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore. This is one reason why I'm looking for an up-to-date threads that say they work with the EU models. If you could clarify more that would be great.
Thanks, II
Click to expand...
Click to collapse
tell me what way you chioce and made and the result .. cuz I will root my item when I recive
---------- Post added at 11:05 PM ---------- Previous post was at 10:54 PM ----------
If I root my xoom can I go back again on Original mood cuz I heard that if I rooted Xoom I will not be able to up-date it via OTA again !

purity0flove said:
If I root my xoom can I go back again on Original mood cuz I heard that if I rooted Xoom I will not be able to up-date it via OTA again !
Click to expand...
Click to collapse
yes, you will be able to go back to the original rom and lock your bootloader again. If you do that, you will be able to get ota updates (if you really want to do so, usually custom roms are ahead of the ota-updates)
You should make a backup of your xoom right after starting the new recovery, even before rooting. That will give you a set of files that, if you restore them, will reset your xoom back to stock, thus you'll only have to re-lock your bootloader to get ota-updates

Response to llama-power
llama-power said:
You should make a backup of your xoom right after starting the new recovery, even before rooting. That will give you a set of files that, if you restore them, will reset your xoom back to stock, thus you'll only have to re-lock your bootloader to get ota-updates
Click to expand...
Click to collapse
I'm now intrigued, I to would like to know how to do this. I'm all for safety measures when it comes to doing things that could damage my stuff.
II

Response to llama-power
llama-power said:
That is weird. I have never read a thread about a brick that occured using the method I (and others) described. Could you maybe post a link to such a thread?
Click to expand...
Click to collapse
Here are two of the links that I was telling you about
Motorola Xoom Root the Easy way
&
Xoom One-Click Root/Unroot
In the first one I found out about it in the comments sections. I read everything on the pages.
II

Custom ROM Files
Hey llama-power,
You say in your thread post that "If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file".
Do you by chance have the links to these files? I know I.C.S. is the latest one, but I'm happy with an old one if it is stable. Or if you have a custom ROM for the Xoom that would be great. I have a Samsung Captivate generation 1 that I use Firefly or Cognition on, along with the original stock ROM as backup just in case. Any links or files would be very cool!
II

Suggested Thread
Just to let you know your suggested thread "and maybe this [HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg" does not work on my Xoom, but thanks for your suggestion. I'll try the other ones you put up, so far I have read every page on every linked thread I've come across. Lots and lots of helpful info on those as well as your pages. But if you can respond to my three earlier posts that would be helpful too. Starting to get information overload, haha.
II

Response to llama-power
Just to let you know your instructions worked like a charm! Went step-by-step and everything worked with no problems at all.
A few more question, yes I know MORE questions! haha. Where is the backup I make stored at? I would like to put it in my backups folder for the Xoom under its drive in my computer. Currently the 3G data service is still not working on it, but is recognizing AT&T network. It says "Mobile Network State: Disconnected" just like before and suggestions? Other then that I also still don't have access to the micro SD card in Android, but can access it in the Recovery.
I now think its time for a new platform, NO more Honeycomb 3.0.1! If you have any suggestions your more than welcome to say or suggest just like for the other posts!
llama-power You ROCK!
Time for me to get some sleep! Been reading and doing Xoom stuff for hours now. I'll be on later to night to read your posts!
Sincerely, InfiniteImmortal

InfiniteImmortal said:
Here are two of the links that I was telling you about
Motorola Xoom Root the Easy way
&
Xoom One-Click Root/Unroot
Click to expand...
Click to collapse
Wow, wasn't aware of that. But these methods are really old. The method I mentioned is the universial root-method by solarnz which is supposed to work on every 'classic' xoom (despite the family edition with its locked bootloader)
InfiniteImmortal said:
You say in your thread post that "If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file".
Do you by chance have the links to these files?
Click to expand...
Click to collapse
I am using the team eos nightlies. Works really nicely except deep-sleep isn't working for me while wifi is enabled. Don't know if that is a rom-issue though, might be some app I use. Anyways, it's not really a problem to me, battery life is still more than sufficient.
You can get the team EOS nightlies for your xoom (MZ601 / umts_everest / EU-3G) from this thread. Download the latest nightly build and the latest G-Apps package (thats the Google Mail, Market, etc. apps) from the link in the same thread. Put those onto your sdcard and flash them from recovery. Wipe /data, /cache and dalvik-cache first, then install the rom, then the g-apps package and finally reboot. Do not reboot between the steps. When upgrading from one nightly to another omit wiping /data.
InfiniteImmortal said:
Just to let you know your suggested thread "and maybe this [HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg" does not work on my Xoom,
Click to expand...
Click to collapse
How did you determine that it didn't work? The only difference you should see is the new app "Superuser.apk". If it really didn't work: sad
InfiniteImmortal said:
Just to let you know your instructions worked like a charm! Went step-by-step and everything worked with no problems at all.
Click to expand...
Click to collapse
thanks, glad to read that
InfiniteImmortal said:
Where is the backup I make stored at?
Click to expand...
Click to collapse
on your sdcard: $SDCARD$/clockworkmod/backup/$DATE_AND_TIME_OF_YOUR_BACKUP$. just copy that entire folder, it contains many .img-files (one for each partition) plus another file for checksums. You will need all those files for a restore. You may, however, rename the directory.
InfiniteImmortal said:
I would like to put it in my backups folder for the Xoom under its drive in my computer.
Click to expand...
Click to collapse
great idea
InfiniteImmortal said:
Currently the 3G data service is still not working on it, but is recognizing AT&T network. It says "Mobile Network State: Disconnected" just like before and suggestions?
Click to expand...
Click to collapse
that is weird. What do you mean with "just like before"? As you haven't flashed another rom yet, nothing regarding connectivity should have changed so far. A few pointers to eliminate some errors: is Airplane mode off? Is mobile data enabled? Are you connected to a wifi-network? Did you set up your AT&T-apn correctly?
InfiniteImmortal said:
Other then that I also still don't have access to the micro SD card in Android, but can access it in the Recovery.
Click to expand...
Click to collapse
yeah, once you flash your new rom, you should be able to access that sd-card. As stated before, you are just rooted, that gives you the power to change things but if you didn't (like installing something that is supposed to give you access to your sdcard), nothing should have changed
InfiniteImmortal said:
I now think its time for a new platform, NO more Honeycomb 3.0.1! If you have any suggestions your more than welcome to say or suggest just like for the other posts!
Click to expand...
Click to collapse
see above, use team eos nightlies

Response to llama-power
llama-power said:
I am using the team eos nightlies.
You can get the team EOS nightlies for your xoom (MZ601 / umts_everest / EU-3G) from this thread. Download the latest nightly build and the latest G-Apps package (thats the Google Mail, Market, etc. apps) from the link in the same thread. Put those onto your sdcard and flash them from recovery. Wipe /data, /cache and dalvik-cache first, then install the rom, then the g-apps package and finally reboot. Do not reboot between the steps. When upgrading from one nightly to another omit wiping /data.
Click to expand...
Click to collapse
Okay I'll look into this one since I know you said it works for you.
llama-power said:
How did you determine that it didn't work? The only difference you should see is the new app "Superuser.apk". If it really didn't work: sad
Click to expand...
Click to collapse
I know you have already seen the other thread that I posted to, and about how I know it didn't work. You commented on the thread with your own post, thanks for backing me up.
llama-power said:
on your sdcard: $SDCARD$/clockworkmod/backup/$DATE_AND_TIME_OF_YOUR_BACKUP$. just copy that entire folder, it contains many .img-files (one for each partition) plus another file for checksums. You will need all those files for a restore. You may, however, rename the directory.
great idea
Click to expand...
Click to collapse
Thanks, I did the same thing on my Samsung Captivate and since my mother has the same phone I made it so it could be used on ether one, less file management for me. Haha
llama-power said:
What do you mean with "just like before"? As you haven't flashed another rom yet, nothing regarding connectivity should have changed so far.
Click to expand...
Click to collapse
You are correct on this, nothing has changed from before except becoming rooted and unlocked. I was hoping that just maybe a full system wipe might fix the connection issue I was having. I was being over optimistic!
llama-power said:
A few pointers to eliminate some errors: is Airplane mode off? Is mobile data enabled? Are you connected to a wifi-network? Did you set up your AT&T-apn correctly?
Click to expand...
Click to collapse
Yes airplane mode is off and Mobile data service is enabled. I have tried it with WiFi both on and off, before and after rooting and unlocking but still nothing. As for the AT&T-APN being setup correctly, I used the exact same settings that are being used in my phone with nothing different; but still to no prevail. Do you know if there is a settings list or configuration out somewhere for the APN?
llama-power said:
yeah, once you flash your new rom, you should be able to access that sd-card... if you didn't (like installing something that is supposed to give you access to your sdcard), nothing should have changed
Click to expand...
Click to collapse
Yeah I kinda guessed at that one, I remembered reading about the Honeycomb 3.1.0 update giving users the ability to use the micro SD cards today. That was before I read your post. lol You might know about this, Do you know where the repository of updates are located for the Motorola Xoom 'classic' model? I was thinking it would be a good idea to have all of them, if I ever wanted to use my warranty it would be good to have the latest stock ROM on it! It's better to be safe then up an icy creek in the Alps with a swim suit on!
II

InfiniteImmortal said:
Okay I'll look into this one since I know you said it works for you.
Do you know if there is a settings list or configuration out somewhere for the APN?
Click to expand...
Click to collapse
Just to let you know I'm using the ROM you recommended and I love it so far. As for the data service on the AT&T network it now works, after switching to the new ROM and it loaded the proper APN settings which were different from my phone. And of course with a new ROM the SD card now works as well. So my last and final question would be as stated before where can I find the oldest most up to date stock ROM?
Best regards, InternetImmortal
Sent from my MZ601 using XDA App on EOS

InfiniteImmortal said:
Just to let you know I'm using the ROM you recommended and I love it so far. As for the data service on the AT&T network it now works, after switching to the new ROM and it loaded the proper APN settings which were different from my phone. And of course with a new ROM the SD card now works as well.
Click to expand...
Click to collapse
glad you like it
InfiniteImmortal said:
So my last and final question would be as stated before where can I find the oldest most up to date stock ROM?
Click to expand...
Click to collapse
well, there are a couple of sources for a stock rom. For one, your sd-card should contain one (I restored my backup yesterday and yes, it even reset the recovery to stock)...
Also, motorola offers some filesystem images at http://developer.motorola.com/products/software/, but you'll need to register with them to get to the download (should be free, though)
Finally, it might be desirable to have some .sbf-file for your xoom. Those can be flashed using a software called rsd lite, even when you aren't able to enter your recovery system. Doesn't always work, so it's not more than a Hail Mary move... However, Motorola does a lot to keep these files from floating around the web, so I won't be able to provide you with a link.

As always thanks for the keen insight. Just came across a few threads that perked my interest. Have you ever tried to get working SMS text messaging and voice calling on the Xoom? Since I'm using the SIM from my phone to do the data I was hoping there might be a way. I haven't done a lot of reading on this yet but you seem to know everything.
Sent from my MZ601 using XDA App on EOS

InfiniteImmortal said:
Have you ever tried to get working SMS text messaging and voice calling on the Xoom?
Click to expand...
Click to collapse
nope. The sim inside my xoom is on the same contract as the sim in my phone and I had to pick one that would receive texts. Naturally, since I always carry my phone, that's where the texts go, so the xoom wouldn't ever receive a text ever anyways. Voice calling is currently not possible on the xoom. So the only upside of that would be that I could send texts using the xoom, but that isn't so much better than texting on my Desire HD. Plus, that would tear apart the messaging threads between my phone and the xoom.
However, there's a thread in the xoom development section where flashable zip-files are published for every eos nightly, you should be able to just flash that over your rom and thus enable texting.
Actually, I might try that some time, but right now I should really learn for that exam on friday:-/

Question about installing OTA

I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.

Hi. I don't suppose the end result would be different, whatever method you choose.

athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.

athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
AFAICT this seems true, you I could run a leak#2/soak based ROM as a second system (first system too?) with boot menu manager by following the guides:
http://forum.xda-developers.com/showthread.php?t=1779968
http://forum.xda-developers.com/showthread.php?t=1882335

jboxer said:
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
Click to expand...
Click to collapse
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc

alteredlikeness said:
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.

jboxer said:
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
Click to expand...
Click to collapse
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc

alteredlikeness said:
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.

Also I do not think you can be rooted to update the check will prevent you from updating, also you have to be as close as stock as you can..... Meaning all bloat must be unfroze.....
One more note there is a Q&A section now so try to post questions there.....

jboxer said:
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Click to expand...
Click to collapse
Can you share the link of the update file?
Thanks

jboxer said:
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Click to expand...
Click to collapse
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?

You can be rooted. The update asserts only check for the original system files to make sure they have not been modified or deleted. It does not check for extra files like superuser.apk or busybox. Rooting is not a problem. I set superuser to OTA protect and it worked. After the update my ICS was still rooted without me having to root it.
For the person that wants the leak the OTA is leak # 2. It is exactly the same. Just find thread with download link for leak # 2 and you are good to go.

Would installing beats audio drivers using the app be considered tampering with system files? And would it prevent me from receiving a ota?
Sent from my MB865 using xda premium

athani said:
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
Click to expand...
Click to collapse
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.

ramosquera said:
Can you share the link of the update file?
Thanks
Click to expand...
Click to collapse
The devs have confirmed that the soak test OTA is identical to ICS leak #2.

jboxer said:
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
Click to expand...
Click to collapse
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.

nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
You have to be someone that was invited and filled out a survey about six weeks ago. If you are you need to go to the Motorola Private forum. Go see how others are requesting it (not allowed to really talk about it). FDR means Factory Data Reset and it is an option in Privacy in Settings. It erases all your user settings, app data and you are back to square one like when the phone came out of the box. For many people it was required to get what they wanted.
If you were not invited don't worry. Usually the official rollout of the OTA will come within a week of a soak test if no problems are found. It is the same as leak # 2 so just look on this forum and you can install that manually. The release is solid so I see no reason the OTA won't be going live to all AT&T Atrix 2 devices very soon.

nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently

alteredlikeness said:
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
Click to expand...
Click to collapse
I hated doing it but it was necessary for some reason. Before it my phone was invisible to the update servers. After it was and I got a push notification to begin the download. Loving ICS.

Post your nougat update.zip!

Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!

billydroid said:
Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!
Click to expand...
Click to collapse
what is the root of the sd card?

I will if I get
Sent from my Samsung SM-G935T using XDA Labs

comptonhubbard said:
what is the root of the sd card?
Click to expand...
Click to collapse
Jsut not in a folder. But that really doesn't matter unless you are trying to flash it from your SDCard

billydroid said:
Jsut not in a folder. But that really doesn't matter unless you are trying to flash it from your SDCard
Click to expand...
Click to collapse
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??

I'm waiting for this too.
Sent from my SM-G935U using XDA-Developers mobile app

gaww said:
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??
Click to expand...
Click to collapse
Yeah no one has got it today. This is starting to look bad
I tweeted at @TmobileHelp, they say it's coming.

billydroid said:
Yeah no one has got it today. This is starting to look bad
I tweeted at @TmobileHelp, they say it's coming.
Click to expand...
Click to collapse
just got through to the galaxy beta program number 1-866-609-3271, currently on hold, all the representatives are currently assisting other customers guess everyone is calling lol ill post any information i get *fingers crossed*
---------- Post added at 09:01 PM ---------- Previous post was at 08:48 PM ----------
Dennis Frogman said:
just got through to the galaxy beta program number 1-866-609-3271, currently on hold, all the representatives are currently assisting other customers guess everyone is calling lol ill post any information i get *fingers crossed*
Click to expand...
Click to collapse
Alright just got off the phone with the customer service representative, they said that they are working with t-mobile as i type this message to get this issue resolved and yes we arev still getting the update. They also said that it's not an issue on Samsung side but rather a problem with t-mobile's server's so guess were gonna have to wait till they get thing's resolved. I asked if it would be fixed today and he said he can't give me a timeline of how or when it will be fixed so stay confident people we are getting it. If you'd like to hear this information with your own ears call the number your selves !!! 1-866-609-3271

gaww said:
Since it tried to register too late, I cant do this (would have done so otherwise - I have restored to stock and re-rooted so many times I could do it in my sleep).
Now I will be looking forward to getting my hands on the ODINable download. I will test it right off and contribute feedback here after.
PS - just looked at the terms and conditions - they wouldn't like this at all lol.
PS2 - maybe they have seen these posts and pulled the plug - server down and Beta call in number down also - have bad feeling about this - could that inadvertently been sending out unlocked bootloaders??
Click to expand...
Click to collapse
this exact post is in the Verizon variants xda page. they uploaded the package.zip file before the install. I don't see it being a problem on here. If it was leaked or something and Samsung didn't release it, then I could see someone being very upset

billydroid said:
Whoever gets the update tomorrow. PULL THE UPDATE ZIP!
If I get it I will and post it, for the flat variant. I have ready done this from my wife's sprint edge variant.
Here is how you do it:
You have to be on the latest firmware and not rooted.
If you get the update notification.
Download it, but do not install it.
Then root your device. DO NOT WIPE IT
The update.zip is located in /data/fota/update.zip
Pull it using adb or use root Explorer to move it to the root of your SDCard and then your pc.
Please wait for someone to verify it works before flashing the update or unroot.
Come on people, support the community!
Click to expand...
Click to collapse
I pull it and I followed the instructions but when I copy the file over to my SD card it shows 0 bytes any suggestions
Sent from my Samsung SM-G935T using XDA Labs

besttech1450 said:
I pull it and I followed the instructions but when I copy the file over to my SD card it shows 0 bytes any suggestions
Click to expand...
Click to collapse
Copy over to your external/internal SD card and move it to your pc. That is what I've done for the tmo flat s7
I was having the same issue. Maybe because the it's encrypted?

billydroid said:
Copy over to your external/internal SD card and move it to your pc. That is what I've done for the tmo flat s7
I was having the same issue. Maybe because the it's encrypted?
Click to expand...
Click to collapse
Ok I try thanks
Sent from my Samsung SM-G935T using XDA Labs

Based on what people from the nouget thread are saying.....we're SOL on getting a .zip file

So it looks like Samsung figured out everyone was sharing the files. For some reason the saved update.zip is failing to update the firmware when it is flashed. No fix yet.
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.

ShrekOpher said:
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.
Click to expand...
Click to collapse
Opinion

ShrekOpher said:
So it looks like Samsung figured out everyone was sharing the files. For some reason the saved update.zip is failing to update the firmware when it is flashed. No fix yet.
Also I got the beta software so far you aren't missing out on much. It's still not as good as the Note 7s firmware was.
Click to expand...
Click to collapse
Do you know for sure or are you just speculating wrong info?
Sent from my SM-G935U using Tapatalk

tengtengvn said:
Do you know for sure or are you just speculating wrong info?
Sent from my SM-G935U using Tapatalk
Click to expand...
Click to collapse
There are people in the beta forums talking about it and Samsung has referred to the Terms of Service saying users are "not supposed to share the beta software". My guess is that they don't have the servers setup to have TONS of people using the software and it feeding them log files etc. That's why they limited the beta to a set number of users. Also the Beta forums that you get access to as a part of the firmware are getting loaded up with comments from people, way more than Samsung staffed to handle.
Its not an assumption that they don't want everyone using it. It is an assumption that they changed the Tmobile firmware to make it so it couldn't be shared. Its a closed beta not open to all users restricting access is a part of a closed beta.
As for the next beta update. They will be making multiple changes over the coarse of the next month and there will be multiple firmware updates pushed out, per the text you receive when you look for a beta update. There is an additional beta setting to help users schedule the installations so they don't use up all their data. Since the tmobile firmware is locked down to specific devices that are a part of the beta program that practice will most likely continue in future beta updates.
If I had to take a wild guess my bet would be that if you are not a registered beta tester you won't get the next update at all and you won't be able to side load/flash it.

ShrekOpher said:
There are people in the beta forums talking about it and Samsung has referred to the Terms of Service saying users are "not supposed to share the beta software". My guess is that they don't have the servers setup to have TONS of people using the software and it feeding them log files etc. That's why they limited the beta to a set number of users. Also the Beta forums that you get access to as a part of the firmware are getting loaded up with comments from people, way more than Samsung staffed to handle.
Its not an assumption that they don't want everyone using it. It is an assumption that they changed the Tmobile firmware to make it so it couldn't be shared. Its a closed beta not open to all users restricting access is a part of a closed beta.
As for the next beta update. They will be making multiple changes over the coarse of the next month and there will be multiple firmware updates pushed out, per the text you receive when you look for a beta update. There is an additional beta setting to help users schedule the installations so they don't use up all their data. Since the tmobile firmware is locked down to specific devices that are a part of the beta program that practice will most likely continue in future beta updates.
If I had to take a wild guess my bet would be that if you are not a registered beta tester you won't get the next update at all and you won't be able to side load/flash it.
Click to expand...
Click to collapse
Its more than that. I got the beta. But i cant even flash the pulled update.zip from my own device. They did something that corrupts if trying to copy it.

Sounds like this is dead for TMo at this point ?

@billydroid and whoever has the update.zip and is rooted
Sounds like the nougat zip needs to be adb pulled from device instead of copying it that might make a differnce because your not copying it directly to sdcard or internal its getting pullled directly to pc thus it should stop it from getting corrupted but you will still need root to pull it from fota.
Sent from my SM-G935U using XDA-Developers mobile app

Repair firmwares??

So im wondering if anyone has repair firmwares for the USA SM_G955U. i recently installed a U2QK4 update OTAusing ADB from the ATT section and everything went bad from there. I was told i may not be able to downgrade but thats not the problem. I CANT DO ANYTHING WITH MY PHONE NOW! IT HAS NO RECOVERY AT ALL IT JUST FLICKERS THE BLUE SCREEN WITH THE ANDROID AND A TEXT APPEARS OCCASIONALLY ON THE FLICKERING SCREEN WITH A WHOLE BUNCH OF FAILS. THERE IS NO UPLOAD MODE AT ALL. I CAN ONLY ACCESS DOWNLOAD MODE WHICH MAKES NO SENSE TO FLASH ANYTHING CAUSE NOTHING WORKS. THE ONLY THING THAT IS FLASHABLE ON NON-MODDED AND MODDED ODIN IS CP! I DONT EXACTLY UNDERSTOOD WHAT HAPPENED. EVERYTHING WAS OPERABLE AND THEN THE PHONE ENCRYPTED ITSELF,REBOOTED ANDA BLUE SCREEN WITH A CARD WAS FLASHING AND ALL WENT TO HELL. TRIED REBOOTING AND THATS WHERE IT ALL BEGAN! I HAVE NEVER EXPERIENCED THAT ON A PHONE BEFORE!
ITS BEEN DAYS SINCE THIS HAPPENED AND I WAS TOLD THE FIRMWARE WAS BEING UPDATED FROM THE OP AND STILL NOTHING! I DONT THINK PEOPLE SHOULD POST THINGS TO FLASH WITH JUST A WARNING ON HERE, THEY SHOULD TEST IT BEFORE POSTING BECAUSE PEOPLE LIKE ME GET CURIOUS AND WANT TO FLASH THINGS,BUT, THE POSTER DOESNT HAVE ANY IDEA WHAT IT DOES!NOT HIS FAULT AS I AM TO BLAME,
ILL SAY IT HERE AGAIN SO PEOPLE DONT THINK IM BLAMING ANYONE,
I I AM TO BLAME!!!!
OKAY, BUT, NOW I AM STUCK WITH A $950 PAPERWEIGHT! AND HONESTLY I WANTED TO BRICK IT, BUT, I THOUGHT WARRANTY OR INSURANCE WOULD COVER IT IN WHICH THEY WONT BECAUSE ATT IS GETTING CRAPPY WITH THEIR CUSTOMER SERVICE. IT SEEMS I HAVE BEEN LEFT IN THE DARK WITH NO CLUES OR HELP.
SORRY FOR CAPITAL LETTERS FORGOT TO TURN IT OFF AND AM NOT ABOUT TO RE-TYPE.
IF ANYONE KNOWS WHAT TO DO OR HOW TO FIX THIS PLEASE HELP.
(AND GETTING A NEW PHONE WONT HELP, SO THAT RESPONSE IS SHOT)
LOOKING FOR A FIX. THANKS IN ADVANCE

Please, don't SHOUT!

dalanik said:
Please, don't SHOUT!
Click to expand...
Click to collapse
Haha I didn't know text could be so loud shoot I even hurt my ears while I typed this hahaha

podagee said:
Haha I didn't know text could be so loud shoot I even hurt my ears while I typed this hahaha
Click to expand...
Click to collapse
Few things:
U2QK4? I don't think that's a model number for a firmware... We certainly haven't seen a U2 g955/0u firmware yet...
And sammobile has it as u1aqk3 for vzw so tmb should be u1qk4.
Can you double check what you flashed?

podagee said:
So im wondering if anyone has repair firmwares for the USA SM_G955U. i recently installed a U2QK4 update OTAusing ADB from the ATT section and everything went bad from there. I was told i may not be able to downgrade but thats not the problem. {screaming redacted }
Click to expand...
Click to collapse
1. A good, new odin that will flash an official package.
https://odindownload.com/download/Odin3_v3.12.3.zip
2.Not the latest firmware, but a solid base (which you can then use to OTA updated to the latest patches)
https://www.sammobile.com/firmwares/galaxy-s8/SM-G955U/ATT/download/G955USQU1AQC9/129108/
Download both, use the former to flash the latter. Let us know how it goes!
EDIT: AND IF IT DOESN'T WORK! Please attach a screenshot of Odin and a picture of your phone (if you can). It'll help us get you squared away.

partcyborg said:
Few things:
U2QK4? I don't think that's a model number for a firmware... We certainly haven't seen a U2 g955/0u firmware yet...
And sammobile has it as u1aqk3 for vzw so tmb should be u1qk4.
Can you double check what you flashed?
Click to expand...
Click to collapse
I'm pretty sure norbarb, the provider of the U2BQK4 firmware knew that it was for the N950(note 8) and posted it in his adb update thread. I bought a new motherboard and will not ever update from that person again because of what has happened. I am not bashing him I just don't want to go through this mess again. and so far I've gotten a bootloader's to flash by using the.elf files from a u2b file from the note 8. Still no recovery and stuck at the bootloader's screen. Can still get into download mode.
The quickest fix I know is for a new motherboard.
Thanks guys

podagee said:
I'm pretty sure norbarb, the provider of the U2BQK4 firmware knew that it was for the N950(note 8) and posted it in his adb update thread. I bought a new motherboard and will not ever update from that person again because of what has happened. I am not bashing him I just don't want to go through this mess again. and so far I've gotten a bootloader's to flash by using the.elf files from a u2b file from the note 8. Still no recovery and stuck at the bootloader's screen. Can still get into download mode.
The quickest fix I know is for a new motherboard.
Thanks guys
Click to expand...
Click to collapse
You wouldn't be able to flash n8 firmware on a s8. Secure boot / Knox would stop you

partcyborg said:
You wouldn't be able to flash n8 firmware on a s8. Secure boot / Knox would stop you
Click to expand...
Click to collapse
Well idk know ALL I KNOW IS HE PROVIDED A U2BQK4 FILE AND I CANT FIND IT ANYWHERE ELSE EXCEPT ON A NOTE 8 !

podagee said:
Well idk know ALL I KNOW IS HE PROVIDED A U2BQK4 FILE AND I CANT FIND IT ANYWHERE ELSE EXCEPT ON A NOTE 8 !
Click to expand...
Click to collapse
Lol no need to capslock everywhere. Just download and flash stock and it will be fine. You can get to download mode right?
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
eregev said:
1. A good, new odin that will flash an official package.
https://odindownload.com/download/Odin3_v3.12.3.zip
2.Not the latest firmware, but a solid base (which you can then use to OTA updated to the latest patches)
https://www.sammobile.com/firmwares/galaxy-s8/SM-G955U/ATT/download/G955USQU1AQC9/129108/
Download both, use the former to flash the latter. Let us know how it goes!
EDIT: AND IF IT DOESN'T WORK! Please attach a screenshot of Odin and a picture of your phone (if you can). It'll help us get you squared away.
Click to expand...
Click to collapse
All due respect but aqc9 is ancient and full of bugs that will make your experience with your phone sub par. Just go to updato.com and download the latest version for your carrier and device. By default updato is slow but if you use a download manager it flies. I can get 3MB/s easily

i honestly dont think people read in these forums. But everyone surely knows everything.
I am starting to get annoyed with that. PLEASE READ CAREFULLY:
1. i have flashed a rom provided by norbarb in the AT&T forums(he took it down) G955USA1US2BQK4,
2. after installing that update, phone went haywire, encrypted and erased everything except download mode,
3. ABSOLUTELY NO RECOVERY AT ALL,
4. nothing will flash over, NOTHING!! phone error: SW REV ablFAILED 1>binary >2 ODIN error. FAIL(AUTH) and FAIL dismatch model in non-modded ODIN and modded odin.
5. i got a bootloader to flash using abl files from a U2b (meaning bootloader 2) from another file U2BQK5 provided from a third party pm.
6. stuck in a bootloop at bootloader screen,
7. STILL NOTHING FLASHES OVER.
8. EDL cable needed per eli, went ahead and ordered another motherboard.
IF ANYONE CARES OR DECIDES TO BADGER ABOUT REPAIR FIRMWARE, PLEASE CHECK OUT GSM FORUMS, THERE ARE OTHER FORUMS WITH USEFUL INFORMATION ABOUT REPAIR FIRMWARES.
thank you all for your help. i just went ahead and ordered another motherboard cause i found it easier and less stressful to deal with less people who do not read the OP.

partcyborg said:
Lol no need to capslock everywhere. Just download and flash stock and it will be fine. You can get to download mode right?
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
All due respect but aqc9 is ancient and full of bugs that will make your experience with your phone sub par. Just go to updato.com and download the latest version for your carrier and device. By default updato is slow but if you use a download manager it flies. I can get 3MB/s easily
Click to expand...
Click to collapse
yes i can but nothing will flash

podagee said:
yes i can but nothing will flash
Click to expand...
Click to collapse
My friend. You keep saying you download stuff from PM or from other sources yet it doesn't seem like you have bothered to try any of the links I or others on here have posted for you. Especially trying the latest Odin can help with software mismatch errors.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
partcyborg said:
Lol no need to capslock everywhere. Just download and flash stock and it will be fine. You can get to download mode right?
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
All due respect but aqc9 is ancient and full of bugs that will make your experience with your phone sub par. Just go to updato.com and download the latest version for your carrier and device. By default updato is slow but if you use a download manager it flies. I can get 3MB/s easily
Click to expand...
Click to collapse
No you're right it is ancient BUT it does have a direct update path straight to last month's security patch. And, maybe most importantly, OP could be using an older ODIN and hasn't tried the new one so I figured an older firmware has best shot at being compatible, he can OTA from there.

eregev said:
My friend. You keep saying you download stuff from PM or from other sources yet it doesn't seem like you have bothered to try any of the links I or others on here have posted for you. Especially trying the latest Odin can help with software mismatch errors.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
No you're right it is ancient BUT it does have a direct update path straight to last month's security patch. And, maybe most importantly, OP could be using an older ODIN and hasn't tried the new one so I figured an older firmware has best shot at being compatible, he can OTA from there.
Click to expand...
Click to collapse
hey bro, just to clarify with you i have flashed every file that there is from the links provided and from the forums i have about 8 copies of each file haha looks like i wont be running out soon. seems like the reason it crashed is the memory test that the rom i flashed inflated too much. i think it damaged my board which is okay i have another coming.

podagee said:
hey bro, just to clarify with you i have flashed every file that there is from the links provided and from the forums i have about 8 copies of each file haha looks like i wont be running out soon. seems like the reason it crashed is the memory test that the rom i flashed inflated too much. i think it damaged my board which is okay i have another coming.
Click to expand...
Click to collapse
Say what now? What made you think it was the memory test? What made you think it was the board or an actual hardware issue with the phone? A memory test can't 'inflate' anything much less can it damage your memory or the actual board.
I had a problem with my device from a badly restored backup where my modem would crash the machine to upload mode moments after booting on anything but a stock rom, and even that the radio didn't work and it would rebolt about 30 times to get to a state where it finished booting at all.
Needless to say I fixed it (I'm still here) but I essentially had to implement my own repair procedure and after about 30 hours total of working in it over two days I managed to get it working enough that I could get a rooted os booted and could then do another restore with a good backup.
If you problem sounds similar (iirc it was in the same general area) and it is then I'm afraid you wasted your money, as all you need is a restore of those partitions outside the rom part of your nvram.

partcyborg said:
Say what now? What made you think it was the memory test? What made you think it was the board or an actual hardware issue with the phone? A memory test can't 'inflate' anything much less can it damage your memory or the actual board.
I had a problem with my device from a badly restored backup where my modem would crash the machine to upload mode moments after booting on anything but a stock rom, and even that the radio didn't work and it would rebolt about 30 times to get to a state where it finished booting at all.
Needless to say I fixed it (I'm still here) but I essentially had to implement my own repair procedure and after about 30 hours total of working in it over two days I managed to get it working enough that I could get a rooted os booted and could then do another restore with a good backup.
If you problem sounds similar (iirc it was in the same general area) and it is then I'm afraid you wasted your money, as all you need is a restore of those partitions outside the rom part of your nvram.
Click to expand...
Click to collapse
I've been messaging with Eli and he said an EDL cable would fix the problem as it needs the deep flash. What would be your suggestion? I have been trying everything and I noticed somewhere saying windows 8 had problems with Odin software so I am currently installing a fresh copy of windows 10. Any suggestions would be appreciated

podagee said:
I've been messaging with Eli and he said an EDL cable would fix the problem as it needs the deep flash. What would be your suggestion? I have been trying everything and I noticed somewhere saying windows 8 had problems with Odin software so I am currently installing a fresh copy of windows 10. Any suggestions would be appreciated
Click to expand...
Click to collapse
Snapdragon right?

partcyborg said:
Snapdragon right?
Click to expand...
Click to collapse
Yes snapdragon G955U AT&T

podagee said:
I've been messaging with Eli and he said an EDL cable would fix the problem as it needs the deep flash. What would be your suggestion? I have been trying everything and I noticed somewhere saying windows 8 had problems with Odin software so I am currently installing a fresh copy of windows 10. Any suggestions would be appreciated
Click to expand...
Click to collapse
.
I thought windoze 10 was the "worst" because of the driver signing gotcha . This was true of me and my alibaba smart watch . For me, I had to resurrect an old h.d. with windoze 7 . . .

old_fart said:
.
I thought windoze 10 was the "worst" because of the driver signing gotcha . This was true of me and my alibaba smart watch . For me, I had to resurrect an old h.d. with windoze 7 . . .
Click to expand...
Click to collapse
Yeah windows 7 is the best but I kinda like the metro theme with 8 and 10, though 8 is bad........

partcyborg said:
Say what now? What made you think it was the memory test? What made you think it was the board or an actual hardware issue with the phone? A memory test can't 'inflate' anything much less can it damage your memory or the actual board.
I had a problem with my device from a badly restored backup where my modem would crash the machine to upload mode moments after booting on anything but a stock rom, and even that the radio didn't work and it would rebolt about 30 times to get to a state where it finished booting at all.
Needless to say I fixed it (I'm still here) but I essentially had to implement my own repair procedure and after about 30 hours total of working in it over two days I managed to get it working enough that I could get a rooted os booted and could then do another restore with a good backup.
If you problem sounds similar (iirc it was in the same general area) and it is then I'm afraid you wasted your money, as all you need is a restore of those partitions outside the rom part of your nvram.
Click to expand...
Click to collapse
still waiting on a reply from you