Develop Bugs

Error [140]: Bootloader version error?

Hey all, I originally had Damage 3.2.2 installed, had wimax update, and the new radio, everything was fine, I am now trying to restore everything back to factory with the HTC Android ROM update utility, v1.0.2.10. I plug it in, go through the steps, it starts to wipe everything, then when it starts copying files it gives me this error. So when it canceled and the phone rebooted, it was just stuck on the white evo screen and loops. I figured it was just because of the new update and all, so I was still able, (thanks god) to flash over Bugless V03. Tryed to use the utility again, and still gives the error. Can anyone help get me back to factory please? thanks for the help I would like to go get my new EVO with out any worry.

So you still have root and access to the recovery console? Odd that you are having problems restoring. Instead of using the exe file, I believe you can flash the zip file using the phones built in hboot menu instead. I don't think it will check the software version first, it's worth a shot. I think you have to name it PC36IMG.zip I think. I would find the exact info but I'm not on a pc at the moment.
Edit:
Check here too, but it's not good:
http://forum.xda-developers.com/showthread.php?t=714157

Sirchuk said:
So you still have root and access to the recovery console? Odd that you are having problems restoring. Instead of using the exe file, I believe you can flash the zip file using the phones built in hboot menu instead. I don't think it will check the software version first, it's worth a shot. I think you have to name it PC36IMG.zip I think. I would find the exact info but I'm not on a pc at the moment.
Edit:
Check here too, but it's not good:
http://forum.xda-developers.com/showthread.php?t=714157
Click to expand...
Click to collapse
I didnt use the OTA update, I flashed Damage 3.2.2, it never effected my ROOT or NAND, I just need to get it back to factory so I can return my phone for a new one. They got one waitin on me to pick up tomorrow afternoon. I have to work all day so I have to either stay up, and figure this out or, if I cant figure something out then I will have to cross my fingers when I go up there tomorrow. I have already spoke with a rep in person, he seemed cool. He looked at my phone for a good minute, scrolled through a few things, I couldnt see what it was, but he just handed it back to me and told me to just come back tomorrow at the same time, and hell swap it. I didnt realize it but I was already on a list for the phone, so Im gettin it either way I guess. I just dont want anything to happen when I go up there. Even if I could just flash over something updated or not just looked "stock" maybe I can just slip in and out.

Ahh okay. Well, look around for the zip format of the exe file in the "how to go back to stock" thread a few posts down.

Sirchuk said:
Ahh okay. Well, look around for the zip format of the exe file in the "how to go back to stock" thread a few posts down.
Click to expand...
Click to collapse
I see that thread, but all I do see is just the .exe files, no zip. There isnt just a installer like with the old version, I have the older exe, before I flashed damage3.2.2 I could easily go back to factory by running that exe and goin through the steps

Alright, this is what I was talking about, I posted it in another thread:
I think he can try restoring to factory.
Download this:
http://www.joeyconway.me/evo/stock/R...253_signed.zip
Rename it PC36IMG.zip and put it on the root of the SD card.
Turn off the phone, hold volume down and turn it on, it should boot into hboot, sort of a factory recovery
It will automatically detect the zip file and ask if you want to apply it. Select yes, and it should restore to factory.
If you continue to have problems, then there is probably something wrong with the phone and it'll need to be returned.
Click to expand...
Click to collapse
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.

Sirchuk said:
Alright, this is what I was talking about, I posted it in another thread:
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.
Click to expand...
Click to collapse
Oops! The Page Can Not Be Found!
Well sorry if I am cluttering I didnt even know that the bootloader was changed which I guess is what the problem is. I guess this is what I get for being impatient. Thanks for the help chuk. If all ells fails cross your fingers for me.

Sirchuk said:
Alright, this is what I was talking about, I posted it in another thread:
You can give that a shot I guess. There are quite a few posts today in the Q&A section with problems, and they all have one thing in common: Damage Control ROM.
Click to expand...
Click to collapse
This guy is atroll
Bootloader was updated with nw ota. Ur applying an old ruu and getting an errir, that's 100% normal you can't roll.back with ruu. Search the board for ducks sake, look at all the threads about rooting nw ota. This is there problem. Just flash another update zip first then u can ruu back.

Yup, that would do it. Hope you can get it worked out before you take it back.

fallentimm said:
This guy is atroll
Bootloader was updated with nw ota. Ur applying an old ruu and getting an errir, that's 100% normal you can't roll.back with ruu. Search the board for ducks sake, look at all the threads about rooting nw ota. This is there problem. Just flash another update zip first then u can ruu back.
Click to expand...
Click to collapse
I still have the the PCIMG zip from when I nand rooted, would that work? flash that then run the exe?

BAleR said:
I still have the the PCIMG zip from when I nand rooted, would that work? flash that then run the exe?
Click to expand...
Click to collapse
If you still have recovery flash dc 3.2. This should rest you bootlegger.
Then run a ruu.

Nooo, I think that is a different file. You can try searching for the link i tried go link that doesn't work, but I doubt it will work if you updated the boot loader. The method I was suggesting would have restored to stock, but with a newer bootloader I'm not sure what to do exactly.
Edit:
If damage control 3.2 has an older bootloader it should work, give it a go.

fallentimm said:
If you still have recovery flash dc 3.2. This should rest you bootlegger.
Then run a ruu.
Click to expand...
Click to collapse
I had a nan backup of 3.2 but I erased it like a dumbo after I was comfy with 3.2.2

If you still have NAND unlock, then try this starting at step 2. This will enable you to downgrade.
http://forum.xda-developers.com/showthread.php?t=701835 <---link

Yeeeah.... Flashed 3.2 and sent me into boot loops. I dont understand why bugless v3 would work, but not this one?

Your not nand unlocked anymore mostlikely.
Did u wipe between newer and older rom

nunyabiziz said:
If you still have NAND unlock, then try this starting at step 2. This will enable you to downgrade.
http://forum.xda-developers.com/showthread.php?t=701835 <---link
Click to expand...
Click to collapse
I dont know how to use adb, I used terminal to nand root, are you basically telling me to re-nand root?

BAleR said:
I dont know how to use adb, I used terminal to nand root, are you basically telling me to re-nand root?
Click to expand...
Click to collapse
most important part is to enable downgrade

nunyabiziz said:
most important part is to enable downgrade
Click to expand...
Click to collapse
well I am re rooting it is updating now.

BAleR said:
well I am re rooting it is updating now.
Click to expand...
Click to collapse
If it started the update without failing then you are in great shape.

Flash phone from Pocket back to Sprint

So I purchased an Evo online, first mistake, and found out it is tied to Pocket Wireless. The phone has a clear ESN, and sprint has added it back to my account, and I am trying to flash Sprints stock RUU. But I keep getting Error 171, and I have tried it on 2 different computers. What other advice can someone give me to get around this? Thanks

wpsr2005 said:
So I purchased an Evo online, first mistake, and found out it is tied to Pocket Wireless. The phone has a clear ESN, and sprint has added it back to my account, and I am trying to flash Sprints stock RUU. But I keep getting Error 171, and I have tried it on 2 different computers. What other advice can someone give me to get around this? Thanks
Click to expand...
Click to collapse
find out your HBOOT version and flash either
http://www.multiupload.com/P4QL4DC90E
for 2.02
or
http://www.multiupload.com/VLFJ3L99PE
for 2.10
that should restore it 100% back to sprint if its rooted you will lose it and have to re-root
Links obtained from: http://forum.xda-developers.com/showthread.php?t=829045

I am assuming I need to load this onto my SD Card, and flash it that way?? Also, don't I have to rename the file, so HBOOT will use it?? Thanks for your help

wpsr2005 said:
I am assuming I need to load this onto my SD Card, and flash it that way?? Also, don't I have to rename the file, so HBOOT will use it?? Thanks for your help
Click to expand...
Click to collapse
pc36img.zip
and yes put it on your SD card

I loaded the file onto my SD card's root folder, and renamed it. But when I get to Hboot, it finds the file, then says no image or wrong name? But the name is correct???

wpsr2005 said:
I loaded the file onto my SD card's root folder, and renamed it. But when I get to Hboot, it finds the file, then says no image or wrong name? But the name is correct???
Click to expand...
Click to collapse
try it in caps, its been a minute and be sure its PC36IMG.zip
I havent personally done it in a while, gimmie a sec let me see if case matters to confirm
**EDIT** ya confirmed it has to be caps.
my mistake sorry

Yup, still not working. Its names PC36IMG.zip, and hboot is still telling me no image or wrong name. This is seriously frustrating.

wpsr2005 said:
Yup, still not working. Its names PC36IMG.zip, and hboot is still telling me no image or wrong name. This is seriously frustrating.
Click to expand...
Click to collapse
hmm frustrating indeed
you have got me stumped for sure.

Ok, Make sure you set up windows to show extension of known files, it is possible that you are renaming a known file (but hiding the extension) and the real file is PC36IMG.zip.zip or PC36IMG.zip.bin or something like that....

No service

I have 3g but I can't call or text?
Sent from my dinc.

schust3r5 said:
I have 3g but I can't call or text?
Sent from my dinc.
Click to expand...
Click to collapse
This post is about as helpful as
I have a can of beer, but its empty
Pls describe your issue:
rooted? s-on or off? rom? kernel? is your phone activated?

Dial *228 and select option 1

Yes I am rooted. I'm using cm9. s is on. my kernel is [email protected]#1fri oct 7 10:52:52: cst 2011 ,but yes I am activated I think on my verizon account it says that I have this phone but I don't have any service but I have 3g i dont get it...

I'm having the same problem with my htc incredible. I have 3G but can't make calls or send texts (can't receive calls or texts either). My phone is rooted and i had the evervolv rom installed on it for about 2 months now. I tried flashing another rom but I have the same problem (tried salvage-mod). I'm wondering if this had anything to do with some apps i removed (I used titanium backup to remove evervolvs email app, the evervolv browswer and evernolv news/weather). The phone worked fine for 3 or 4 days after i removed these apps and then this happened. But I don't think this is related but just thought i would mention it.

losthorizon777 said:
I'm having the same problem with my htc incredible. I have 3G but can't make calls or send texts (can't receive calls or texts either). My phone is rooted and i had the evervolv rom installed on it for about 2 months now. I tried flashing another rom but I have the same problem (tried salvage-mod). I'm wondering if this had anything to do with some apps i removed (I used titanium backup to remove evervolvs email app, the evervolv browswer and evernolv news/weather). The phone worked fine for 3 or 4 days after i removed these apps and then this happened. But I don't think this is related but just thought i would mention it.
Click to expand...
Click to collapse
I hate to be redundant but have you tried calling *228 and reprogramming the phone? If so and it didn't help anything, could you post a little bit of information about your phone? We know you are on evervolv and rooted and I'm guessing you're using clockworkmod recovery but what is your baseband/radio? Any other relevant information you can think of would also be helpful so someone can help you

Yeah I am running CWR.
Baseband: 2.15.00.07.28
Kernel version: 2.6.37.4-cyanogenmod+ [email protected] #27
Build number: GRJ22
I tried called *228 and reprogramming but it hasn't helped. I was thinking about going back to a stock rom and calling verizon.
When I try making a call, the green bars become grayed out. I will hear about 3 or 4 rings before I get a message from Verizon saying my call cannot be processed and they give me the following code: 11 switch? 179-3

losthorizon777 said:
Yeah I am running CWR.
Baseband: 2.15.00.07.28
Kernel version: 2.6.37.4-cyanogenmod+ [email protected] #27
Build number: GRJ22
I tried called *228 and reprogramming but it hasn't helped. I was thinking about going back to a stock rom and calling verizon.
When I try making a call, the green bars become grayed out. I will hear about 3 or 4 rings before I get a message from Verizon saying my call cannot be processed and they give me the following code: 11 switch? 179-3
Click to expand...
Click to collapse
You need to call verizion and have them reprovision your phone. I'm 90% positive its a problem on there end. I would go back to a stock rom first (RUU), but keep s-off or you will be in for a lot of work rerooting.

losthorizon777 said:
Yeah I am running CWR.
Baseband: 2.15.00.07.28
Kernel version: 2.6.37.4-cyanogenmod+ [email protected] #27
Build number: GRJ22
I tried called *228 and reprogramming but it hasn't helped. I was thinking about going back to a stock rom and calling verizon.
When I try making a call, the green bars become grayed out. I will hear about 3 or 4 rings before I get a message from Verizon saying my call cannot be processed and they give me the following code: 11 switch? 179-3
Click to expand...
Click to collapse
well, I don't think that this is necessarily the problem but you might want to consider upgrading your radio. It is easily flashable through hboot and can considerably improve your call quality. The one you're using now was designed for and released with froyo and when you downgraded to root you also downgraded the radio so perhaps that is a problem?
You can get the radios from this address:
http://dinc.does-it.net/Radios/
You probably want 2.15.10.07.07 as it is the newest radio that was designed for the dinc. (released with gingerbread 2.3.4)
Just make sure you check the MD5 before flashing because a bad radio file could brick your device.
EDIT: cmlusco is right, that is what you really need to do. I always avoid going to verizon myself because I have no interest in them trying to tell me how i somehow did something wrong by rooting it.

What do you mean by check the MD5?

losthorizon777 said:
What do you mean by check the MD5?
Click to expand...
Click to collapse
I still maintain that like cmlusco said you should go ahead and RUU back to stock and talk to verizon about it but it is still good to know what an MD5 sum is.
An MD5 Sum is a string of numbers that is unique to every file. You check the MD5 sum to make sure it matches the original MD5 Sum which is usually provided by the developer or host of the file. For example, in the case of the radio:
if you go to this page you will see two files: http://dinc.does-it.net/Radios/2.15.10.07.07/
One is called PB31IMG.zip and the other is called PB31IMG.zip.md5
If you click on PB31IMG.zip it will download the file to your computer and you can then transfer that file to the root of your SD card to be flashed.
If you click on PB31IMG.zip.md5 you will see a string of numbers/letters which make up the MD5 sum for the PB31IMG.zip file. For this file it is:
617E6969061DCBC3CA613FA6D02565F0
You then want to make sure that after you download the file or even better when it has been placed on your phone that the file has not been corrupted during downloading or during transfer to your phone. This can be done by using an MD5 checker which can be downloaded from many places online for your pc and there are several MD5 checkers available in the market. You basically just want to make sure the string of numbers found online on the dev site or the host site is the same as the one generated by the checker

So i tried the radio and it didnt help. I'm going to do the RUU now. Is this the link for that: http://forum.xda-developers.com/showthread.php?t=1227279

losthorizon777 said:
So i tried the radio and it didnt help. I'm going to do the RUU now. Is this the link for that: http://forum.xda-developers.com/showthread.php?t=1227279
Click to expand...
Click to collapse
Here is a link for the ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip
Also just fyi, a new radio was just released 2.15.10.12.20 you can get it here http://dinc.does-it.net/Radios/2.15.10.12.20/PB31IMG.zip

can i use any of those stock images or should i use 4.06.605.3?

losthorizon777 said:
can i use any of those stock images or should i use 4.06.605.3?
Click to expand...
Click to collapse
Should be able to use any of them. However they will prompt you with ota updates after you boot to get to either 4.08.605.2 or 4.08.605.15 if its been pushed to you yet, or mabey both.

So i flashed the RUU and called verzion. they refreshed something on their end and now i can make calls and send texts. thanks for all your help

The unrevoked3 recovery flash tool wont root my phone. Would going back to an older RUU like 3.26.605.1 help?
I made sure security was off (S-OFF) when i did the flash with the first RUU. Also hboot still says S-OFF so i dont think this is the problem.

losthorizon777 said:
The unrevoked3 recovery flash tool wont root my phone. Would going back to an older RUU like 3.26.605.1 help?
I made sure security was off (S-OFF) when i did the flash with the first RUU. Also hboot still says S-OFF so i dont think this is the problem.
Click to expand...
Click to collapse
If your s-off all you have to do to root is flash cwm recovery thru hboot http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip and then flash superuser through recovery http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip .

[Q] imei 0

Hey guys I bought my sg3 about 3 months ago from a friend who had cynogen mod on the phone and it worked fine but I had cynogen mod on auto update and now my imei shows as 0 via *#06# and I cant call or text etc. Unfortunately I do not have a backup from when the imei worked because I didnt expect it to do this. So far Ive removed cynogen mod and reset it to stock firmware but im having the same issue any suggestions?
Its the SGH1747 version

dolee said:
Hey guys I bought my sg3 about 3 months ago from a friend who had cynogen mod on the phone and it worked fine but I had cynogen mod on auto update and now my imei shows as 0 via *#06# and I cant call or text etc. Unfortunately I do not have a backup from when the imei worked because I didnt expect it to do this. So far Ive removed cynogen mod and reset it to stock firmware but im having the same issue any suggestions?
Its the SGH1747 version
Click to expand...
Click to collapse
Your baseband is probably corrupted. You may try reflashing a stock modem/baseband via recovery. I had a similar problem once, although I was on stock ROM, and re-flashing the modem zip worked.
I, however, tread very carefully here as I am aware the forum is wary about discussions relating to IMEI.

Larry2999 said:
Your baseband is probably corrupted. You may try reflashing a stock modem/baseband via recovery. I had a similar problem once, although I was on stock ROM, and re-flashing the modem zip worked.
I, however, tread very carefully here as I am aware the forum is wary about discussions relating to IMEI.
Click to expand...
Click to collapse
yeah im not trying to change it which isnt allowed just tryin to figure out how to do what you said could you list me some steps or link me how to do this?

dolee said:
yeah im not trying to change it which isnt allowed just tryin to figure out how to do what you said could you list me some steps or link me how to do this?
Click to expand...
Click to collapse
Don't know if you're willing to pay to have this repaired but here's a site that does it. I've done stuff with them before. Very good service.
(no, I don't work for them - just a happy customer.)
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-imei-efs-repair/

dolee said:
Hey guys I bought my sg3 about 3 months ago from a friend who had cynogen mod on the phone and it worked fine but I had cynogen mod on auto update and now my imei shows as 0 via *#06# and I cant call or text etc. Unfortunately I do not have a backup from when the imei worked because I didnt expect it to do this. So far Ive removed cynogen mod and reset it to stock firmware but im having the same issue any suggestions?
Its the SGH1747 version
Click to expand...
Click to collapse
You can look up peoplearmy's method (google it). You will not find help on how to fix IMEI on XDA. I had my IMEI wiped out a while back after flashing a bad rom. I had to get it put back, and then had to get LTE back.
Good luck.

dolee said:
yeah im not trying to change it which isnt allowed just tryin to figure out how to do what you said could you list me some steps or link me how to do this?
Click to expand...
Click to collapse
Can you go to Settings => About Device and see what you have under Baseband version? Whilst you are there, also check what Android version it says and the build number.

Larry2999 said:
Can you go to Settings => About Device and see what you have under Baseband version? Whilst you are there, also check what Android version it says and the build number.
Click to expand...
Click to collapse
android 4.3 base band 1747MVLUEMK5 build # JSS15J.1747MVLUEMK5

dolee said:
android 4.3 base band 1747MVLUEMK5 build # JSS15J.1747MVLUEMK5
Click to expand...
Click to collapse
Everything looks OK as your baseband version would likely read 'unknown' if it's bad. You may, however, still try re-flashing the modem via the method posted in the attached thread ... Please proceed at your own peril as I offer no guarantee that this will work or will not result in damaged phones,
http://forum.xda-developers.com/showthread.php?t=1831898
Please note you will need custom recovery (e.g. CWM or TWRP). You will find instructions for installing custom recovery at the bottom of the thread. If this doesn't work, then you may try doing a hard wipe from recovery and reinstalling everything including system ROM, modem and kernel.
Hope it works out for you.

Simple fix is to reinject imei which located behind the battery.. But sometimes for some reason if you do this, you'll stuck with edge network, can be fix though but you gotta go back to stock in order to do so
Sent from my SAMSUNG-SGH-I747 using Tapatalk

LARMYV said:
You can look up peoplearmy's method (google it). You will not find help on how to fix IMEI on XDA. I had my IMEI wiped out a while back after flashing a bad rom. I had to get it put back, and then had to get LTE back.
Good luck.
Click to expand...
Click to collapse
I'm in the same boat as you once were. I lost my imei and had to inject it back, now I have no LTE service anywhere.. It says LTE but no internet connection. Any help? Sorry if I threadjacked here but I've been dealing with this for a year now and I really need a solution...

karmasblade said:
I'm in the same boat as you once were. I lost my imei and had to inject it back, now I have no LTE service anywhere.. It says LTE but no internet connection. Any help? Sorry if I threadjacked here but I've been dealing with this for a year now and I really need a solution...
Click to expand...
Click to collapse
you will have to google peoplearmy imei lte and find the tutorial on how to restore imei and get LTE back.
You will not be able to find the thread on XDA because XDA deleted it sometime ago. I was like you and lost my imei. Once I re-injected it using a tutorial on XDA, I was stuck on edge. Then I finally found peoplearmy's tutorial, downloaded the programs and followed the steps to get LTE back. I got it back and haven't lost it since.

LARMYV said:
you will have to google peoplearmy imei lte and find the tutorial on how to restore imei and get LTE back.
You will not be able to find the thread on XDA because XDA deleted it sometime ago. I was like you and lost my imei. Once I re-injected it using a tutorial on XDA, I was stuck on edge. Then I finally found peoplearmy's tutorial, downloaded the programs and followed the steps to get LTE back. I got it back and haven't lost it since.
Click to expand...
Click to collapse
I can't find the link, can you PM me it?

I had that happen to me with a 0 on my phone and was able to get it back I had no backup either what I did is go on the NV Data restore or NV writer thread and downloaded the NV writer and put myself back on stock ...I went thru a few pages in the post and someone had a file where you could put your IMEI into that file maybe it was set up thru notepad but you could fill in the zeros with your IMEI and name it I think a txt.file after then open the NV writer and instead of backing it up cause you can't just restore that file where you fill in you're IMEI and it went right back into my phone. There also a video on that page how to do it. You just need basically that file to put your IMEI back in. I might still have it if not keep going thru the post took find it. There a picture of what it looks like to restore if you list it but every time I tried to open that link to restore it wouldn't let me. Hope it wasn't to confusing but it's basically a white box with a bunch of zeros and replace the zeros with your IMEI and save it as atxt. File I believe and just restore it as shown in the video for backing it up but just restore instead it does work cause I didn't have an IMEI on my phone it just had a zero
---------- Post added at 10:53 PM ---------- Previous post was at 10:48 PM ----------
http:// http://forum.xda-developers.com/showthread.php?t=1804117

NV writer
heres the NV txt file to write your IM?EI back to the phone.extract the zip.

britt21 said:
heres the NV txt file to write your IM?EI back to the phone.extract the zip.
Click to expand...
Click to collapse
could you link the video or the thread with the video?
instructions werent so clear

dolee said:
could you link the video or the thread with the video?
instructions werent so clear
Click to expand...
Click to collapse
I believe this is it. http://forum.xda-developers.com/showthread.php?t=1804117

karmasblade said:
I believe this is it. http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
?
I got a message saying failed phone did not answer when writing any ideas

[Q] ATT ZE500CL/Z00D Bricked After OTA Update - HELP (ZenFone 2E)

I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.

JRSouth said:
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
Click to expand...
Click to collapse
i have the exact problem since saturday, you have to use the ATT firmware but i couldnt find it anywhere

also
please pm me if u fixed yours

Lactaid said:
please pm me if u fixed yours
Click to expand...
Click to collapse
Still no luck. I'm sure if we could find the AT&T firmware we would be able to recover. Unfortunately it appears it is not available on ASUS support and AT&T doesn't even provide firmware. Our only hope may be from a backup of another device that isn't bricked.
Does anybody know if we could possibly use the temporary CWM recovery used in the root method to flash to another ROM that is compatible with this device? Any input would be greatly appreciated.

Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks

JRSouth said:
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
Click to expand...
Click to collapse
ive literally tried everything, my device has been bricked for like 3 weeks now

Lactaid said:
ive literally tried everything, my device has been bricked for like 3 weeks now
Click to expand...
Click to collapse
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.

JRSouth said:
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
Click to expand...
Click to collapse
i havent tried it yet, do you have a tutorial of it?

The truth hurts, your screwd. This is a budget phone. At&t will not support it. Throw away device my their standards.

http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps

http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
^^^This worked for me successfully!
Make sure to only restore system and disable MD5 Checksum Verification.

I have the same problem, what do I do with that file? How do I apply it through the SD, so I can apply update from SD? I forgot pin code to phone so i need to restore

need help
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
how do I flash this?

Hola, alguien lo consiguió hacer..???

Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
Im getting an error that day footer is wrong :/

m1chb3ltr3 said:
Im getting an error that day footer is wrong :/
Click to expand...
Click to collapse
Wait, are you bricked and tried using that as the fix? I cant post links but Check out Asus, They have Firmware, Kernel (havent checked but read it earlier today), and Boot Unlock that you can get right from (assuming you have an account) My Products.
Also... Has anyone used that method recently?
Cathaterfish said:
Sorry I will give credit to DavePmer for his guide in minute, but qouting him for some reason wouldnt let me post, even when I removed the links? anyways I'll edit and give credit I promise
So my phone is stuck on the Asus Logo, I downloaded all of this and followed the instructions all the way up to:
11) now the fun part. open your microsd card and check the folder TWRP\BACKUPS see if it has a folder named
01234567890123456789 if it does great if not, not a problem just copy all the system files from the folder
you extracted TWRP-zf2e-ATT_12.16.10.7 to your microsd card TWRP\BACKUP\01234567890123456789\ whatever folder you have next\ in other words, replace your system.ext4.win000 files with my system.ext4.win000 file.
Replace your system.ext4.win001 with mine, and replace system.ext4.win00.md5 with mine as well as system.ext4.win001.md5 when done safely dismount the microsd card.
It then occurred to me that i should be more careful this time around... This was from October and although I ran across links saying for the most part that this was a good shot for fixing my ZE500CL, Z00D or whatever. But things have changed since then and I was wondering if this is still the best/easiest/safe route. I learned pretty quick that over looking things like OTA/Root or in my case Making assumptions is a fast path to really doing a number on your phone. (Honestly I just started even giving thought to rooting my phone, just considered them back ups I kept in a box). I now have the itch to do this right so hoping to fix this and go about this the right way.
Thanks for any input.
Currently DLing RussaiNBeaR, went and bought a card reader/writer. I was going to Download the firmware, kernel and boot unlock tool but currently staying at a place where im getting 160kbs on my DL's. So if I can get away with davepmer's guide that would be great, or something other or smaller than downloading 4gbs on this Internet Connection.
EDIT: Forgot to add that I haven't completed this step yet because the wording kind of tripped me up. And I want to do this right. When he says "in other words replace your system.ext4.win000 files with my system.ext4.win000 file." and then goes on and 3 more to the list. Does that mean only copy and replace those 4? or does that include all system.(whatever).(extension) files? Im sure it sounds really dumb or noobish but the fact that the next step is using twrp to restore using system only makes me afraid to do this part wrong.
Click to expand...
Click to collapse

ayuda
ATT ZE500CL/Z00D rom