Database Info

HELP! My update to new official rom went wrong!

Hello all
I downloaded the new ROM from the TW HTC site some minutes ago and proceed with flashing some time thouought the FLASH the pfone gave an error "Checking Custom ID"
"Update Failed"
And Android Update says ERROR 131 CUSTOMER ID ERROR
Now I can do nothing! The phone goes into HBOOT 1.76.0007 and I have a big icon with a memory chip on the bottom of the screen!
Pleace help me restore the hboot and recovery roms! The rest I'll menage.

same error..

You cant flash the update, don't do it.
Eugene is having a 32B ROM done and i belive he is uploading it atm.
32A users will soon have a flashable ROM.

WebghostDK said:
You cant flash the update, don't do it.
Eugene is having a 32B ROM done and i belive he is uploading it atm.
32A users will soon have a flashable ROM.
Click to expand...
Click to collapse
And for the ones that did it?

Great, i flashed my 32A via fastboot, and now im stuck in some strange state... I think i might have gotten a corrupt radio on it somehow...

Epedemic said:
Great, i flashed my 32A via fastboot, and now im stuck in some strange state... I think i might have gotten a corrupt radio on it somehow...
Click to expand...
Click to collapse
Yup it seems that way, as it now always hangs when flashing radio (trying a official 2.17 upgrade) grr...

Epedemic said:
Yup it seems that way, as it now always hangs when flashing radio (trying a official 2.17 upgrade) grr...
Click to expand...
Click to collapse
Yes. Cause you flashed a new HBoot.
You should wait, while romcookers will find way to downgrade new hboot
or repacked rom to flash properly to all customers, not only taiwanese.

I think it is time to clear things out:
DO NOT FLASH / UPDATE THIS ROM TO YOUR DEVICES!!!! - This means: Wait for someone to release correct ROM Updates to your devices. This official update is ONLY for TW devices. When you decide to flash something to your devices you should be very sure that you are not doing a stupid move! If someone tells you not to do it then you should hear that! Flashing something isn't like dressing a tshirt, and this means that if you choose a wrong size tshirt you can always take it off and dress another that fits you right. Flashing something that doesn't fit your device can easily brick it! Be aware!

5[Strogino] said:
Yes. Cause you flashed a new HBoot.
You should wait, while romcookers will find way to downgrade new hboot
or repacked rom to flash properly to all customers, not only taiwanese.
Click to expand...
Click to collapse
Indeed. I thought i was safe cause i flashed the files (boot.img, radio.img and system.img (which failed) via fastboot... Guess not... So now im stuck at the same screen with the cross over the ram chip

joaosousa said:
I think it is time to clear things out:
DO NOT FLASH / UPDATE THIS ROM TO YOUR DEVICES!!!! - This means: Wait for someone to release correct ROM Updates to your devices. This official update is ONLY for TW devices. When you decide to flash something to your devices you should be very sure that you are not doing a stupid move! If someone tells you not to do it then you should hear that! Flashing something isn't like dressing a tshirt, and this means that if you choose a wrong size tshirt you can always take it off and dress another that fits you right. Flashing something that doesn't fit your device can easily brick it! Be aware!
Click to expand...
Click to collapse
Yes we already know this! But it is too late! So please tell us how to fix the mess we have created!

I agree don't do stupid things in excitement. If you have eng spl etc by flashing all imgs )boot, radio etc) you may brick your device, so please please be careful wait for a update.zip file from greats mods like drizzy, eugene etc.

Once again I want to point that the purpose of this thread is help theese of us that DID the flash NOT knowing that it will NOT work!

OrionBG said:
Yes we already know this! But it is too late! So please tell us how to fix the mess we have created!
Click to expand...
Click to collapse
In my understanding the only thing you can do is to wait the official htc EU flasher (HTC said around mid November) and see if it's able to replace everything loading a proper radio/spl on the bricked device, acting on a lower level.
Otherwise you would just keep that expensive plastic brick ...
I am sorry, i was also eager to upgrade, but if HTC let you download their flasher only with a proper TW serial number, and if they've already advertised that you need to wait 2 or 3 weeks more for european firmware, then there should be a reason: so I didn't.
Hope you will be able to fix, but I am not too confident: guess you will need service.

It's ALIVE!!!! I have no idea how or why, but after tons of failed attempts and failed fastboot commands i now have the 3.03 update on my scandinavian 32a which i thought was bricked!

Epedemic said:
It's ALIVE!!!! I have no idea how or why, but after tons of failed attempts and failed fastboot commands i now have the 3.03 update on my scandinavian 32a which i thought was bricked!
Click to expand...
Click to collapse
Good. Now please write everything, what you did to get device alive)

5[Strogino] said:
Good. Now please write everything, what you did to get device alive)
Click to expand...
Click to collapse
yes yes post it please

i have no idea what actually did it, but it is possible that it was because i did a adb logcat command while the 3.03 update was running..
I can see that i have the 1.76 spl, and the new radio (which kept failing on me before)

i have try now to do adb logcat while update is running, but adb continuos stay in waiting for device, or say adb server is out to date ecc

Epedemic said:
i have no idea what actually did it, but it is possible that it was because i did a adb logcat command while the 3.03 update was running..
I can see that i have the 1.76 spl, and the new radio (which kept failing on me before)
Click to expand...
Click to collapse
Strange thing... adb logcat simply outputs log into console... How outputing logs can affect to flashing properly?
p.s. please post your full SPL-info too.
p.p.s. I think we need get right order to flashing this update. You tried to flash images via fastboot. What order do you have at first (boot - 1, radio - 2, system -3)?
What did you do at last?

i can't accesso to fastboot mode beacuse the phone stay in RUU USB ..

Issue manually updating Nexus One

When I try to manually update my Nexus One with the newer non-OTA update. Everything is fine until I get to the section where you can use the trackball. From there I get, "E:Can't open /cache/recovery/command" Later, after trying to verify the package I get, "E:signature verification failed" and aborts the install. Tried someone's advice about taking the battery out and putting it back in but still nothing. Please advise.

I assume your bootloader is unlocked. What recovery are you using? Amon_RA's?

My bootloader is not unlocked, but will be today. I was under the impression that as long as the file was named "update.zip" it could be done without it. Ah well. So today I am going through the steps to put the desire rom on the phone.

Dainian said:
When I try to manually update my Nexus One with the newer non-OTA update. Everything is fine until I get to the section where you can use the trackball. From there I get, "E:Can't open /cache/recovery/command" Later, after trying to verify the package I get, "E:signature verification failed" and aborts the install. Tried someone's advice about taking the battery out and putting it back in but still nothing. Please advise.
Click to expand...
Click to collapse
I'm having the same issue, also not rooted. Its really annoying me and I'm quite worried about it since I'm not receiving the 2.2.2 OTA and I'm worried I won't be able to install 2.3 when it arrives.
If anyone knows a fix please reply!

This is some really good progress.

unamusedpunk said:
This is some really good progress.
Click to expand...
Click to collapse
lol do i detect some sarcasm? I guess i shouldve checked how old this post was before posting for help on it.

help please

so i flashed a rom i think its called provisions on my nexus but.it.seems its the only one i can flash ...im not.new to.flashing by any means but.idk.whats going on i keep getting a status 7 error When i try to flash any other rom i tryed an oldsr recovery but no.dice any feed back would be great

come on guys 70+ views and no reply has no one run into this problem

sergioperalta81 said:
come on guys 70+ views and no reply has no one run into this problem
Click to expand...
Click to collapse
Try updating your recovery. And be patient.
Maybe post the full error message too, that could help.

polobunny said:
Try updating your recovery. And be patient.
Maybe post the full error message too, that could help.
Click to expand...
Click to collapse
thanks for the response Ive used the latest recovery and all it does is attempt to install it then it shows the path of the file installation aborted error status 7

The ROM zip is most probably corrupted or incomplete. It does happens often.
Try flashing your current ROM zip. If it flashes without issues then I am 101% sure that the error is due to corrupted or incomplete .zip

sergioperalta81 said:
so i flashed a rom i think its called provisions on my nexus but.it.seems its the only one i can flash ...im not.new to.flashing by any means but.idk.whats going on i keep getting a status 7 error When i try to flash any other rom i tryed an oldsr recovery but no.dice any feed back would be great
Click to expand...
Click to collapse
What ROM were u one before this happened?
And RU flashing via recovery or ROM manager app?
What do u format / clean up before u flash any ROM?
And u were a flashaholic in the past, the u could have some unwanted or useless files in ur SD card that could be causing the error.
So ID recommend cleaning up or reformating ur SD card and just put back the necessary files to flash. Then once ur back up, put back all ur files that u want or need(media, games, pics...etc)
Thx
Vs Nexus S4G using tapatalk2

sergioperalta81 said:
so i flashed a rom i think its called provisions on my nexus but.it.seems its the only one i can flash ...im not.new to.flashing by any means but.idk.whats going on i keep getting a status 7 error When i try to flash any other rom i tryed an oldsr recovery but no.dice any feed back would be great
Click to expand...
Click to collapse
Make sure you're wiping everything. And also, more importantly, that the rom is for your variant of the Nexus.
If you have Nexus S 4G from sprint, you use Crespo4g, if not, use the Nexus S. or Crespo.
Edit: Apologies, I thought you said you WERE new.
I'll just leave this post in case anyone new stumbles up on this thread.

You're flashing the wrong ROM.
Maybe you have mistaken "Nexus" for "Nexus S"

[Q] Flashing bootloader locked Cricket Moto G/LTE to retail firmware

I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!

macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"

macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...

Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.

macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.

RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.

macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.

RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!

macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.

RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse

macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.

RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?

no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.

RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.

RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?

macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.

It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....

The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.

I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.

That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!

Help rooting cricket s7 g930az

I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!

Jay351 said:
I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!
Click to expand...
Click to collapse
When you say flashing, fhalsing what exactly got you the bootloop? Was it flashing the engineering Boot.img through Odin or the fix S7 zip through Flashfire... Or something else?
I don't have a Cricket branded S7, but always offering to help you research.
Sent from my SM-G930P using Tapatalk

POWerSUrgeSW3 said:
When you say flashing, fhalsing what exactly got you the bootloop? Was it flashing the engineering Boot.img through Odin or the fix S7 zip through Flashfire... Or something else?
I don't have a Cricket branded S7, but always offering to help you research.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Thanks for the help it was https://youtu.be/KawiIZ4bAV8
As soon as I got to the boot.img and downloaded it to my phone that when it started.

Jay351 said:
Thanks for the help it was https://youtu.be/KawiIZ4bAV8
As soon as I got to the boot.img and downloaded it to my phone that when it started.
Click to expand...
Click to collapse
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
Have you tried downloading the image again? I invite you to check out a thread I'm part of if you want another location to download the S7 engineering boot image, that thread located here and the boot image file can be downloaded directly from here

POWerSUrgeSW3 said:
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
Yes and I tried the original also
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
Correct s7 for s7
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
Yes
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
I made sure it was still a tar file.
Thanks for your help I'll check it out
Click to expand...
Click to collapse

Jay351 said:
POWerSUrgeSW3 said:
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
Yes and I tried the original also
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
Correct s7 for s7
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
Yes
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
I made sure it was still a tar file.
Thanks for your help I'll check it out
Click to expand...
Click to collapse
You're welcome, just trying to figure it out. Though I see this is a common thing, so I wonder what is different with the Cricket version?
And you're rooting the Nougat version of the phone? This seems to be a topic floating around with no one explaining it. I've tried looking to see if maybe the processor might be somehow a "reduced" version of the 820 compared to the others... but everything makes it look like it should work.
Only other thing I would say is go back through all the steps, and make sure you're not accidentally skipping one. I did that a bunch of times when I first started off. I ended up printing off instructions and making note edits. Took me a few different sets of instructions until I found a formula that worked for my G930P
Click to expand...
Click to collapse

POWerSUrgeSW3 said:
Jay351 said:
You're welcome, just trying to figure it out. Though I see this is a common thing, so I wonder what is different with the Cricket version?
And you're rooting the Nougat version of the phone? This seems to be a topic floating around with no one explaining it. I've tried looking to see if maybe the processor might be somehow a "reduced" version of the 820 compared to the others... but everything makes it look like it should work.
Only other thing I would say is go back through all the steps, and make sure you're not accidentally skipping one. I did that a bunch of times when I first started off. I ended up printing off instructions and making note edits. Took me a few different sets of instructions until I found a formula that worked for my G930P
Click to expand...
Click to collapse
I'm sorry no we haven't received the update yet I'm still on 6.0.1. Do you mean like mixing up the steps and finding which worked with your phone?
Click to expand...
Click to collapse

Jay351 said:
POWerSUrgeSW3 said:
I'm sorry no we haven't received the update yet I'm still on 6.0.1. Do you mean like mixing up the steps and finding which worked with your phone?
Click to expand...
Click to collapse
Oh I'll have to go back and do some rereading then, because I thought I saw some websites saying that phone was already on Nougat. If you're still on MM this should be easier I would think... hmmm
For me, it took me about 4 or 5 different threads of talking about how they rooted their Sprint S7 phone, for me to find the right instructions for myself to root my phone. But I know along the way I would miss a step, then my phone wouldn't boot or bootloop like yours. That's why I went back and printed out instructions and checked off to make sure I didn't skip anything. After awhile I could wrap my head around it.
Just saying we are all human, so it's easy to skip a step. Though it doesn't seem like you're the only one having this problem. But if all the branded US phones are pretty much rooted one way or another, I don't see why yours would be any different.
Click to expand...
Click to collapse

POWerSUrgeSW3 said:
Jay351 said:
Oh I'll have to go back and do some rereading then, because I thought I saw some websites saying that phone was already on Nougat. If you're still on MM this should be easier I would think... hmmm
For me, it took me about 4 or 5 different threads of talking about how they rooted their Sprint S7 phone, for me to find the right instructions for myself to root my phone. But I know along the way I would miss a step, then my phone wouldn't boot or bootloop like yours. That's why I went back and printed out instructions and checked off to make sure I didn't skip anything. After awhile I could wrap my head around it.
Just saying we are all human, so it's easy to skip a step. Though it doesn't seem like you're the only one having this problem. But if all the branded US phones are pretty much rooted one way or another, I don't see why yours would be any different.
Click to expand...
Click to collapse
Your probably right I'll try those steps again and see if anything changes. The only model I see that's close to g930az would be the at&t which is g930a. I know I got lucky with the last attempt to try with it in soft brick. I just don't want to try to many and it be completely screwed. Because on cricket you have to buy all of you phones up front well at least I had to with mine. I'll try it again and let you know if it worked or I have a paper weight haha. Thanks again
Click to expand...
Click to collapse

Jay351 said:
POWerSUrgeSW3 said:
Your probably right I'll try those steps again and see if anything changes. The only model I see that's close to g930az would be the at&t which is g930a. I know I got lucky with the last attempt to try with it in soft brick. I just don't want to try to many and it be completely screwed. Because on cricket you have to buy all of you phones up front well at least I had to with mine. I'll try it again and let you know if it worked or I have a paper weight haha. Thanks again
Click to expand...
Click to collapse
With following the steps you are and what you have happening, you should be OK with being able Odin back to factory firmware.
Yeah Cricket is kind of the double edge sword, you have to buy the phone up front, but they have CHEAP prices for good service. I had them when I first moved to Arizona and would have kept them, if I didn't travel so much.
Report back if anything changes.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse

Jay351 said:
I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!
Click to expand...
Click to collapse
hey can you help get my s7 g930az back to stock. i also happen to be stuck in a bootloop and i've searched everywhere and nothing

leonardo879 said:
hey can you help get my s7 g930az back to stock. i also happen to be stuck in a bootloop and i've searched everywhere and nothing
Click to expand...
Click to collapse
Do you have the stock firmware and Odin? Flash that will get you back to stock and functional. Does take awhile to flash the full imagine, but can pretty much fix any software brick issues.
Sent from my SM-G930P using Tapatalk

POWerSUrgeSW3 said:
Do you have the stock firmware and Odin? Flash that will get you back to stock and functional. Does take awhile to flash the full imagine, but can pretty much fix any software brick issues.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Yes i have the stock firmware and Odin but it always fails. is there any other way to fix it? i tried smart switch and it stops at 69% and it says error so idk what else to try.

leonardo879 said:
Yes i have the stock firmware and Odin but it always fails. is there any other way to fix it? i tried smart switch and it stops at 69% and it says error so idk what else to try.
Click to expand...
Click to collapse
What's the failure error? OEM Unlock in Android was turned on correct?
Sent from my SM-G930P using Tapatalk

POWerSUrgeSW3 said:
What's the failure error? OEM Unlock in Android was turned on correct?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
It says "Encrypt Error" in smart switch. What does OEM Unlock mean?

leonardo879 said:
It says "Encrypt Error" in smart switch. What does OEM Unlock mean?
Click to expand...
Click to collapse
By default the phones are locked so someone can't steal your phone and Reimage it. If you boot your phone up after trying to flash do you get an FPR or some sort of error like that?
Sent from my SM-G930P using Tapatalk

POWerSUrgeSW3 said:
By default the phones are locked so someone can't steal your phone and Reimage it. If you boot your phone up after trying to flash do you get an FPR or some sort of error like that?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
No it doesn't. The phone is just stuck in a boot loop after i tried installing a .tar file in Odin that i got from a youtube video showing how to root it but it doesn't work so now i'm stuck on he boot loop.

leonardo879 said:
No it doesn't. The phone is just stuck in a boot loop after i tried installing a .tar file in Odin that i got from a youtube video showing how to root it but it doesn't work so now i'm stuck on he boot loop.
Click to expand...
Click to collapse
Yes but if you try to Odin back to the stock firmware what happens then?
Sent from my SM-G930P using Tapatalk

POWerSUrgeSW3 said:
Yes but if you try to Odin back to the stock firmware what happens then?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
It says "Fail. Model Mismatch fail" something a long that

leonardo879 said:
It says "Fail. Model Mismatch fail" something a long that
Click to expand...
Click to collapse
I would recommend going to sammobile or updato to get the firmware for your phone. Sounds like you have the wrong model. If you need help I can help in an hour or so when I get home.
Sent from my SM-G930P using Tapatalk