Database Info

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.

EK-GC120 Verizon Update

I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.

swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
Click to expand...
Click to collapse
I give up. How did you root this device in the first place?

perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.

Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app

perlmane said:
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.

swjpilot said:
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
Click to expand...
Click to collapse
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.

perlmane said:
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
Click to expand...
Click to collapse
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......

swjpilot said:
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
Click to expand...
Click to collapse
Since VZW does not support Kies firmware updates, I am afraid to try it. I will have to wait until someone finds the 4.1.1 release of this device and ODIN it.

Anyone still have the boot.img for the latest verizon? Even the full update will work to extract it. This is the only missing piece to extending the custom kernel to all variants.

perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
swjpilot said:
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Click to expand...
Click to collapse
If you are still around can you confirm you used the "Exynos" Abuse apk to root your Verizon GC120. The Samsung specs page for it aren't clear about whether it's an Exynos quad core using a qualcomm board or an entire qualcomm chipset/board. Thanks!
And if anyone Verizon has found a way to root the current Verizon version and/or the odin file for 4.1.1 please reply here or let me know! Thanks!

swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Click to expand...
Click to collapse
That link is dead end. Can you please repost that firmware update?

Another thing I learned while I had my ATT galaxy tab 8.9 was that Samsung likes to use the same hardware in their South Korean version of their devices with cellular and in their US devices with cellular. It's almost certainly because of the LTE requirement. Wouldn't you know that such is the case with the Galaxy Camera. The South Korean version of the camera has a Qualcomm board just like the Verizon one. Maybe the firmware for it, which can be found on Sammobile at the link below, can be helpful.
http://www.sammobile.com/firmwares/1/?model=EK-KC120S&pcode=0
EDIT: To clarify more, the Korean version uses a Qualcomm 9215 baseband board with Exynos 4412 while the Verizon version (based on Samsung own specs page) uses a Qualcomm 9615 which has it's own applications processor.

CPU Z says the Verizon GC120 DOES use the Exynos 4412 (smdk4x12). It makes no mention of the Qualcomm board on Samsungs' own specs page. They don't make this easy...
Still need any Verizon build anyone has (original 4.1.1 or 4.1.2 update which should be found in /cache).

Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update

twistedumbrella said:
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
Click to expand...
Click to collapse
I know you think no one else could possibly know better than you but the link in the op leads to nothing.

Jiggity Janx said:
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Click to expand...
Click to collapse
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Edit: Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.

twistedumbrella said:
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Click to expand...
Click to collapse
edited out...
You can still likely see what was written in your thread quote notification but it doesnt need to be hashed out here.

Jiggity Janx said:
My problem here starts and ends with you. You cant expect to come across the way you do belittleing or correcting everyone every chance you get and then wonder why someone responds that way to something that appears to be a comment directed at the very last thing stated in the post immediately before yours. You dont get to have it both ways and then act innocent and deflect when you are called out on it.
Click to expand...
Click to collapse
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.

twistedumbrella said:
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
Click to expand...
Click to collapse
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.

Jiggity Janx said:
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Click to expand...
Click to collapse
Look at the number of developers who have left xda butt-hurt about some comment a nameless, faceless text blob made about them because of how they read it. The device suffers, the users suffer, and some kid is up in his room crying about a hobby gone wrong.
As for the rollback, it was only theory anyway so if there is any doubt about what to change its better to find an alternative. If you could get images of the partitions from stock condition, it is possible to build the install. At least that is all done off the device where it won't corrupt anything. You could root, get the system, data, cache, and boot then merge those with the Korean release to fill in the missing parts. To the best of my knowledge, the bootloader and such are not region specific. That should be verified first, though, because you can't go back later.

ATT Un-Brick Method (Also International Debloat)

Hello, those of you who have soft bricked and can still access download mode, there is a method a user and I @giantpear discovered to bring your phone back to life by flashing the KDZ of the Peurto Rican 810.
Instructions can be found at this thread:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Kudos to @hyelton for his original thread
Note: Remember you are flashing the Puerto Rican Firmware for your phone, not the original stock US KDZ as there is not one yet.
Note: I am not the creator of this thread I am merely re-posting what we found through test in that thread tonight.
Note: I am not sure moving forward if you were to continue to try to root or flash what model method you would want to try. I would say we should wait for a TOT method before trying anything else.
On the positive note, I now have a heavily debloated phone with zero ATT apps on it.
Hope this helps any who have lost their phone attempting root these past few days.

I approve But yeah it should be posted here in the mean time. Until we do get an official A&T TOT.
But this is great for either needing to go back to stock due to soft-brick, or if you like that pure software feeling.

Please make it known that this method isnt compatible for Low Effort Root AT&T H810 10g. I just tried and failed. Reflash the kdz and it all went well. I already submitted a system dump file to #thecubed. Hope we can get a rooted system img shortly.

Kudos @giantpear

user787 said:
Kudos @giantpear
Click to expand...
Click to collapse
@user787 Thank you! Your KDZ link saved at least a dozen ATT 810s. Power to XDA!

This is awesome news! I wish I would have found @user787 post earlier! Hopefully all the other lost H810 souls will see this post soon.
If anyone discovers downsides of using this KDZ, please post what you find in this thread. I've got a replacement phone coming and need to decide if I should keep this one or the AT&T phone. So far I'm liking this variant much better!
You guys should enter donation information in your profile. I'll buy you a beer or two!

would be awesome to make a combo rom with this and root for stateside AT&T phones. A factory heavy debloat rom would be nice since you are guaranteed that the removed apps won't cause issues.

phineous said:
I've got a replacement phone coming and need to decide if I should keep this one or the AT&T phone. So far I'm liking this variant much better!
Click to expand...
Click to collapse
I am with you, I think I will be sending back the warranty replacement they are sending me!
Although the process of bricking and pulling back (thanks to you guys) was a pain in the ass! I really like this ROM. I like it better than the one that came with my phone and so far I have no issues. When this version gets root I think it is the best case scenario. Thank you again for helping us all out!

Next I need to decide if I should take the updates available for it. I see there are ones available but none are being forced.
Edit never mind just app updates.
Sent from my LG-H810 using XDA Free mobile app

keeper22 said:
When this version gets root I think it is the best case scenario.
Click to expand...
Click to collapse
There's a root script out we can run on our system.img file, it just needs to be run on Linux. I'll try to set up a machine tonight if someone doesn't beat me to it.

phineous said:
There's a root script out we can run on our system.img file, it just needs to be run on Linux. I'll try to set up a machine tonight if someone doesn't beat me to it.
Click to expand...
Click to collapse
That's over my head, but I looking forward to it. Let me know if there is anything I can do to help.

Has anyone checked to see if they get good 4G LTE speeds with H810PR? I don't have good 4G coverage (or much data left) to test on. I just ran an LTE speedtest and I maxed out at 11.35 Mbps.

phineous said:
Has anyone checked to see if they get good 4G LTE speeds with H810PR? I don't have good 4G coverage (or much data left) to test on. I just ran an LTE speedtest and I maxed out at 11.35 Mbps.
Click to expand...
Click to collapse
Testing just now

noamaniac said:
Note: I am not sure moving forward if you were to continue to try to root or flash what model method you would want to try. I would say we should wait for a TOT method before trying anything else.
On the positive note, I now have a heavily debloated phone with zero ATT apps on it.
Hope this helps any who have lost their phone attempting root these past few days.
Click to expand...
Click to collapse
Another soul back from the dead.
Has anyone re-tried the Low Effort Root again?

informpage said:
Another soul back from the dead.
Has anyone re-tried the Low Effort Root again?
Click to expand...
Click to collapse
I tried and failed. However i already send a system img of PR to thecubed so we can get root

I've tried low effort root on my H810 last night and it worked perfectly. I've already installed a bunch of root apps and everything is working great.
---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------
bobimbap said:
I tried and failed. However i already send a system img of PR to thecubed so we can get root
Click to expand...
Click to collapse
It worked perfectly fine for me on my H810. At what point did it fail for you?

keeper22 said:
I am with you, I think I will be sending back the warranty replacement they are sending me!
Click to expand...
Click to collapse
I got the warranty replacement phone today. It's brand spanking new with H81010b firmware. I may pull an image off it later in case someone needs it, but I still think I'm sending the phone back. My original works too well to take a chance with new hardware.

probaina said:
It worked perfectly fine for me on my H810. At what point did it fail for you?
Click to expand...
Click to collapse
You probably used the 10g file on 10g system. I tried the 10g root file on PR system since my phone bricked earlier. I had to flash PR kdz to bring it back to life

bobimbap said:
You probably used the 10g file on 10g system. I tried the 10g root file on PR system since my phone bricked earlier. I had to flash PR kdz to bring it back to life
Click to expand...
Click to collapse
Oh I see. Ouch. Yeah I do have 10G system but I see what you're saying now.

phineous said:
My original works too well to now to take a chance with new hardware.
Click to expand...
Click to collapse
It might be because it was dead and now anything is better than that, but I feel like my phone is running better than before I tried to run Low Effort Root!

Ahhh, Root! Sweet delicious Root! For H810PR only.

All right you losers and screwups! Everyone who sucked hard at rooting has reason to rejoice!
Soft-bricking your phone may have been the best thing to happen to you.
Luck smiles on the unfortunate and the stupid today!​
Use a download manager to get these files, and check the MD5 of your downloaded file against AndroidFileHost.
Here's the latest rooted version from @diedemus
Here's the original rooted image for the H810PRa-310-410.
Know what you are doing before attempting to flash these files! Flashing the H810PR firmware is done mostly as a last resort for people who have bootlooping AT&T H810s.
Read all the instructions carefully, then follow the instructions in the root thread 1 through 6, except ignore the parts in step 4 where it mentions tar.gz and the filename since you have a rar file and already had to extract the image file from it and rename it to system.img.
You'll see that we have a different command to flash the H810PR compared to what was used on the H810. Here is the code to copy and paste at the # prompt in the command window:
Code:
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
Paste the above code in the command window, then hit enter and pucker your butt.
Wait for the # prompt to reappear.
Type LEAVE and hit enter.
Prepare to crap your pants again or savor the sweet taste of victory!
Good luck!
Feel free to ask questions, but try searching for an answer first please. XDA is loaded with information, but it's squirreled away deep in various threads. Learning to search XDA is a valuable skill. Even if you don't find an answer to your specific question, you'll learn something anyway.
H810PR is much better IMO than stock AT&T except for the danger of the green blob in the camera. There's hardly any bloat (like 100 less packages on the phone, seriously!), and no CarrierIQ to have to bother disabling. All the stuff AT&T broke is working too.
Cons so far:
Big ol' green dot in the camera. I wouldn't flash this rom unless I had to because of this issue.
No VoLte (voice over LTE). The phone drops to 3G in phone calls. Follow this post to enable LTE outside of a voice call.
Voicemail settings are grayed out. To set up, put your SIM in another phone or call ATT.
Editing options in camera are overwhelming! There's too many things you can change!
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 100 less.
The stuff AT&T removed or broke is not broke.
Editing options in camera are amazing! There's so many things you can change!
No CarrierIQ
Here's my H810 repository on Androidfilehost if you're looking for other H810 files.

This is pretty sweet! I always wanted to post in the dev folder, and make a reserve post. Not that I really did anything worthy of it, but I'm leaving the post here anyway.

Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.

It worked! It was a bumpy road, thank you for all your help! (oh sweet ad blockers, how I love you)

faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Yes to all your questions.
I repeated the code to flash here to make sure people noticed it was different for H810PR. It's the same in both posts.

Just noticed i no longer have volte with this image. (yes, i have lte)

faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance

user787 said:
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
Click to expand...
Click to collapse
Copy OP's code @up..for me i follow till step 9 from THIS then follow this PAGE from 6 to 9 then paste OP code to flash image root
Please read carefully before anything bad happened

faizalotai said:
Please read carefully before anything bad happened
Click to expand...
Click to collapse
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you

user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
No problem bud

user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
I edited the OP to make the instructions more clear. Hope it helps!

To be clear, this will work on an H810 US ATT that has the H810PR image on it now?

noamaniac said:
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
Click to expand...
Click to collapse
Yes.

What is the LTE icon for this build? I have the 4G icon, but not sure this means LTE.

what are the downsides to flashing this on the H810 stateside bloatware4days edition?

bobloadmire said:
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
Click to expand...
Click to collapse
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T (I don't know why I keep thinking this is possible, it isn't, bootloader is flashed by the KDZ and not compatible with the ATT versions anymore), but I'm going to stick it out on this image for awhile.
I'm keeping an updated list of the pros and cons in the OP.

phineous said:
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T, but I'm going to stick it out on this image for awhile.
Cons so far:
No VoLte (voice over LTE). The phone drops to 3G in phone calls.
Possible problems with voicemail.
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 150 less.
Click to expand...
Click to collapse
Would you Say the phone is snappier overall or is it mainly just to save storage?

bobloadmire said:
Would you Say the phone is snappier overall or is it mainly just to save storage?
Click to expand...
Click to collapse
I ran Debloater and blocked around 98 packages when I was on the AT&T H81010e non-root image. The phone was pretty fast, but something had a memory leak and I'd have to reboot it every morning. This image hasn't had that problem yet, but I've only been using it for a couple of days.
You might want to wait a little while for the people who had to use it to discover any more downsides. I think it'll be easy to switch back to an AT&T image, but I'm not 100% sure because I haven't tested it yet. (not possible till there's a TOT.)
In any case, I think it's a good idea to follow the instructions in the original root thread to extract an image of your working phone, name it something you'll remember, and keep it on the internal storage as an emergency recovery image.

Totes mah gotes. Thanks man.

Anyone that's on this Firmware having issues with voicemail? I can't seem to get google voice to work and when people call my regular voicemail it is saying i'm not available. I've tried entering the code into the dialer and i'm getting an error saying connection error or wrong MMI code.
I went into the forwarding settings in the phone and entered my GV # and received unexpected error from network.

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