Develop Bugs

Broke My Sprint Touch

Hello,
I saw on the htc site that an update for the Sprint HTC touch was available so i downloaded it and tried to load it on my phone.
It took a few tries to get it to connect and when it finally did it said there was an invalid command.
I thought it was because i upgraded my phone earlier to the titan rom and radio to get gps and rev a so i put it back to the factory settings.
Everything was normal.
I then tried the official htc software update again and it worked until it got to 10% and it said invalid command again and exited.
It is now stuck on the boot load screen and remains that way after numerous soft/hard resets.

To "unbrick" your phone, follow the steps in this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
In a nutshell:
You'll have to revert back to your carrier's ROM (by carrier, I mean a genuine, signed ROM) by extracting the ROM's exe file and renaming the .nbh file inside the archive to VOGUIMG.nbh.
Then, remove your Micro SD card and use a card reader** to put that file into the root - ensure that the card is formatted as FAT32 and that the card is not an SDHC (meaning any card that is 4GB+().
**card reader or any other device that has a microSD slot that operates as a USB mass storage device - I did the same procedure with an MP3 player... **
Insert the card and reboot the phone, it should go into the bootloader and update automatically.
Good luck

If you can get to the boot screen, chances are it is not bricked
Just download the original ROM and flash to that. Make sure to NOT use a virtual machine! You can only run the .EXE file in Windows XP natively, not in software such as Parallels or VM Ware.

TGHI said:
To "unbrick" your phone, follow the steps in this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
In a nutshell:
You'll have to revert back to your carrier's ROM (by carrier, I mean a genuine, signed ROM) by extracting the ROM's exe file and renaming the .nbh file inside the archive to VOGUIMG.nbh.
Then, remove your Micro SD card and use a card reader** to put that file into the root - ensure that the card is formatted as FAT32 and that the card is not an SDHC (meaning any card that is 4GB+().
**card reader or any other device that has a microSD slot that operates as a USB mass storage device - I did the same procedure with an MP3 player... **
Insert the card and reboot the phone, it should go into the bootloader and update automatically.
Good luck
Click to expand...
Click to collapse
I tried this maybe 5 times and i keep getting a communication error!

bpack428 said:
I tried this maybe 5 times and i keep getting a communication error!
Click to expand...
Click to collapse
If you are getting a communication error while trying to flash from the sd card, you've got some very serious problems. More than likely, if you are flashing from sd and get an error, it is probably not a communications error.
What letters are on the three-color boot-loader screen?
Best regards,
-boggsie

boggsie said:
If you are getting a communication error while trying to flash from the sd card, you've got some very serious problems. More than likely, if you are flashing from sd and get an error, it is probably not a communications error.
What letters are on the three-color boot-loader screen?
Best regards,
-boggsie
Click to expand...
Click to collapse
VOGU100 MFG
SPL-2.01.1000
CPLD-3
in the top right corner it says RUUNBH
bottom it says serial

I think im going to play dumb and get a new phone from sprint.

bpack428 said:
I think im going to play dumb and get a new phone from sprint.
Click to expand...
Click to collapse
This is a pretty simple fix. You need to stick your MicroSD card into your PC via card reader. Format the card to fat32. Re-Formating is important because even if your card is already fat 32 sometimes it still won't work until your re-format it. Then copy "any" compatible Vogue RUU file over to your card. Rename the file "VOGUIMG" without the quotes and stick it back into your phone in the root directory.. Hold down the power and camera button and reset the phone with the stylus. Once inside the bootloader follow the instructions on your screen. Reset when you are done and you should be good. THIS IS ASSUMING YOUR PHONE IS ALREADY UNLOCKED. If you go back to Sprint and they see why your phone isn't booting they may not honor your warranty.
GOOD LUCK....

ptfdmedic said:
This is a pretty simple fix. You need to stick your MicroSD card into your PC via card reader. Format the card to fat32. The copy "any" compatible Vogue RUU file over to yourt card. Rename the file "VOGUIMG" without the quotes and stick it back into your phone. Hold down the power and camera button and rested the phone with the stylus. Once inside the bootloader follow the instructions on your screen. Reset when you are done and you should be good. THIS IS ASSUMING YOUR PHONE IS ALREADY UNLOCKED. If you go back to Sprint and they see why your phone isn't booting they may not honor your warranty.
GOOD LUCK....
Click to expand...
Click to collapse
I have done this. It says loading... on my phone and then i try to load RUU_Vogue_SPRINT_WWE_1.12.651.1_2.13.00_SPC_NV133_Ship on my phone from my pc and i get a communication error

bpack428 said:
I have done this. It says loading... on my phone and then i try to load RUU_Vogue_SPRINT_WWE_1.12.651.1_2.13.00_SPC_NV133_Ship on my phone from my pc and i get a communication error
Click to expand...
Click to collapse
Let me clarify. Use any "Compatible" "Custom" Rom. I don't believe the Sprint Release off the HTC site will work with what you are doing. You need a Custom Rom.
I would suggest you visit: http://forum.ppcgeeks.com/forumdisplay.php?f=59
and just pick one and follow the instructions I gave eariler. I don't believe you can do this type of upgrade with the Sprint ROM you need to try with a custom ROM....
MAKE SURE YOUR PHONE IS UNLOCKED....

ptfdmedic said:
Let me clarify. Use any "Compatible" "Custom" Rom. I don't believe the Sprint Release off the HTC site will work with what you are doing. You need a Custom Rom.
I would suggest you visit: http://forum.ppcgeeks.com/forumdisplay.php?f=59
and just pick one and follow the instructions I gave eariler. I don't believe you can do this type of upgrade with the Sprint ROM you need to try with a custom ROM....
MAKE SURE YOUR PHONE IS UNLOCKED....
Click to expand...
Click to collapse
How do i know if my phone is unlocked?
All that i want to do it update it to the official htc rom

bpack428 said:
How do i know if my phone is unlocked?
All that i want to do it update it to the official htc rom
Click to expand...
Click to collapse
Have you ever loaded a custom ROM?... You said you loaded a Titan ROM? I believe you had to have your phone unlocked for that and that was just for the Radio and it was not a full OS flash. So if you did that then hopefully your phone is unlocked.
If your phone is unlocked you will see the following on you bootloader:
VOGU100 MFG
SPL-2.31.Coke
CPLD-3
What do you have listed.
Let me know and maybe I can help.

He posted the information earlier in the thread:
VOGU100 MFG
SPL-2.01.1000
CPLD-3
Click to expand...
Click to collapse
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie

boggsie said:
He posted the information earlier in the thread:
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie
Click to expand...
Click to collapse
I have no idea if i can or cannot do that.

boggsie said:
He posted the information earlier in the thread:
His phone is not unlocked and he cannot get back into Windows Mobile so he cannot unlock it at this point.
His only option is to load the RUU/WWE from Sprint (presuming that is his carrier) as I don't think (I'm probably wrong) that the stock boot loader will flash from sd card.
Best regards,
-boggsie
Click to expand...
Click to collapse
Hye Boggsie,
Didn't COKE release a version of his unlocker that was flashable via SD card. I know that I flashed extracted the .nbh from the .exe and renamed it and flashed. It worked but I only did this because I running Vista 64 and couldn't get it to work from Vista. I will look and see if I can remember how I did it. The op said he flashed a titan rom to get the radio or something. I would guess that might play a part in this.
I agree that the Sprint.exe would be his only option but I will see if I can locate what I did. That may also work........
Thanks for the reply...

Here is the link to the 2.31 unlocker: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker_MFG_2.31.exe
Here is the link to the thread over on PPCGEEKS:
http://forum.ppcgeeks.com/showthread.php?t=20370
What I did was to extract the .nbh and rename it to VOGUIMG. I flashed that from my SD card and unlocked my phone. I don't believe this is a supported method. I don't know how good of an idea it is. But it seems that you have tried everything else already. I would READ the thread VERY CAREFULLY before deciding to try this. I Must be VERY CLEAR. DO THIS AT YOUR OWN RISK. AGAIN READ THE INSTRUCTIONS IN THE THREAD FIRST. I only did this because when I was newer I made a mistake and found myself in a similar position as you. I knew my phone was dead and figured I had nothing left to lose. I take no responsibility for this as I am sharing information that I have from my own experience. I don't think that this is really suppossed to work but it did for me. It has been a while since I fixed mine, and I have flashed to many times to remember. So I am reasonably sure this is what I did.
Good Luck......
Update:
Read this thread:
http://forum.ppcgeeks.com/showthread.php?t=24906
This should help you fix this.
UPDATE 2:
Rename the .nbh to VOGUIMG not VOGUIMG.nbh the .nbh is the file extension and not part of the renaming process. If you include .nbh in the name it will not work.....
OK. GOOD LUCK

ptfdmedic said:
Hye Boggsie,
Didn't COKE release a version of his unlocker that was flashable via SD card. I know that I flashed extracted the .nbh from the .exe and renamed it and flashed. It worked but I only did this because I running Vista 64 and couldn't get it to work from Vista. I will look and see if I can remember how I did it. The op said he flashed a titan rom to get the radio or something. I would guess that might play a part in this.
I agree that the Sprint.exe would be his only option but I will see if I can locate what I did. That may also work........
Thanks for the reply...
Click to expand...
Click to collapse
He did, but only for the Titan or Kaiser ... probably the Titan.
AFAIK, he doesn't have a replacement Vogue, yet.
Best regards,
-boggsie

boggsie said:
He did, but only for the Titan or Kaiser ... probably the Titan.
AFAIK, he doesn't have a replacement Vogue, yet.
Best regards,
-boggsie
Click to expand...
Click to collapse
Hey I took the plunge.
I relocked and and then unlocked right from my sd card. It does work. Only recommended if there is no other way. But it does work. It is just like flashing a custom rom from your sd card but it only takes a few seconds.....

ptfdmedic said:
Hey I took the plunge.
I relocked and and then unlocked right from my sd card. It does work. Only recommended if there is no other way. But it does work. It is just like flashing a custom rom from your sd card but it only takes a few seconds.....
Click to expand...
Click to collapse
Wow ... a bit of a gutsy move; yours are bigger than mine, my friend.
Although, I wonder why / how it works? I mean, flashing a bootloader from SD is facilitated through the existing bootloader. So the existing bootloader is being overwrittern by the new bootloader, but the existing bootloader is performing the write / update process, so how can it possibly be overwritten?
This is why the bootloader process from the pc needs activesync; so that a temporary bootloader can be run in memory and then used to write the new bootloader over top of the existing one.
Oh well, who cares why I can't understand it ... it works. Good find!
Best regards,
-boggsie

boggsie said:
Wow ... a bit of a gutsy move; yours are bigger than mine, my friend.
Although, I wonder why / how it works? I mean, flashing a bootloader from SD is facilitated through the existing bootloader. So the existing bootloader is being overwrittern by the new bootloader, but the existing bootloader is performing the write / update process, so how can it possibly be overwritten?
This is why the bootloader process from the pc needs activesync; so that a temporary bootloader can be run in memory and then used to write the new bootloader over top of the existing one.
Oh well, who cares why I can't understand it ... it works. Good find!
Best regards,
-boggsie
Click to expand...
Click to collapse
Boggsie,
Check out this thread. It explains it all.
http://forum.ppcgeeks.com/showthread.php?t=24906
I agree it shouldn't work. But it does. Coke says it should be a last resort. But is actually works....

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.

Unroot T-Mobile G2

i need to unroot my phone and flash the stock rom back because i am sending my phone back to tmobile for warranty so i was wondering how do unroot and flash the stock rom back to it.

1) Search
2) read the sticky in the Development forum. There is a step-by-step guide for unrooting.
3) ask questions here if you have a specific question about unrooting.
On a personal note, I used the method found HERE to unroot my device and send in for warranty repair. Worked like a champ.

i have tried to unroot but i get main version is older what do i do now?

Can anyone help me out

What is wrong with the phone? Do you have the $5.99/month extended warranty?

alpharomero said:
What is wrong with the phone? Do you have the $5.99/month extended warranty?
Click to expand...
Click to collapse
Not sure what the warranty has anything to do with it. Whether you have the extended warranty or not you need to unroot to send in for repair. If they find that you've tampered with it they'll charge u full price for a replacement/repair, and if you have handset insurance you'll be charged the deductable. Charges you can sometimes avoid by unrooting.
But yes, OP, exactly which method did you try, and where are you held up? gotta be more specific man...

im using the method that you said worked for u. When the zip file runs after i put the phone in bootloader it get the s-on but it says main version is older! update failed

did you properly edit the line with the hex editor and make the miscnew.img to put on your SDcard?

yes i did the correctly

ok i got it the problem was that i have the original misc.img and miscnew.img on the memory card i deleted misc.img and a left miscnew.img on the there and it worked. Thanks for your help martonikaj

ruffrider5956 said:
ok i got it the problem was that i have the original misc.img and miscnew.img on the memory card i deleted misc.img and a left miscnew.img on the there and it worked. Thanks for your help martonikaj
Click to expand...
Click to collapse
Yep I figured it was something to that effect. I think it tells you to remove the old one, because if the phone uses that instead of the one you edited, the unroot process doesn't work.
glad i could help.

ruffrider5956 said:
ok i got it the problem was that i have the original misc.img and miscnew.img on the memory card i deleted misc.img and a left miscnew.img on the there and it worked. Thanks for your help martonikaj
Click to expand...
Click to collapse
ok so i got to the part at the end with my phone flashing the PC10IMG.zip file, and while this was happening, my phone says "Update Fail!" "Press Power to reboot", yet i fixed the thing in hex editor... Here's the guide im following :http://forum.xda-developers.com/showthread.php?t=831398
However, i dont have the old misc.img on my sdcard, only the miscnew.img. Can anyone help?

how u got ur phone to work any help i will apreciated and any links too

Help please flashing to boost

Ok, Im trying to flashing my EVo 4G to boost mobile. Im following the guide that eljean posted. I got all the way up to step 5 on the guide and got stuck. Heres how im stuck it says to download autoroot w/2.15.00.11.19 which i did then it say make sure you have a sd card in your evo which I do. then it say to duble click autoroot.bat and i do... it starts and this is where i get stuck it look like it start rooting then it say the ADB shell does not heve root permissioms and then it say FAILED TO GET A ROOT SHELL PLEASE RESTART YOUR PHONE AND TRY AGAIN. can somebody plz help me it making me a very angry person

can someone help pleaseee

aldog25 said:
Ok, Im trying to flashing my EVo 4G to boost mobile. Im following the guide that eljean posted. I got all the way up to step 5 on the guide and got stuck. Heres how im stuck it says to download autoroot w/2.15.00.11.19 which i did then it say make sure you have a sd card in your evo which I do. then it say to duble click autoroot.bat and i do... it starts and this is where i get stuck it look like it start rooting then it say the ADB shell does not heve root permissioms and then it say FAILED TO GET A ROOT SHELL PLEASE RESTART YOUR PHONE AND TRY AGAIN. can somebody plz help me it making me a very angry person
Click to expand...
Click to collapse
so you're trying to root? go here http://forum.xda-developers.com/showthread.php?t=1218386
..then go back to the original guide to complete

I did that i redownloaded all the auto root files and still when i go to autoroot.bat it still say the same thing does any of this matter? Im running Android ver: 2.3.3
Baseband ver: 2.15.00.05.02
Build number: 4.24.651 L61076 release keys
Software number : 4.4.651.1
PRI ver:1.77_003
On that guide i think it say it only work for Software versions 1.32, 1.36, 3.29, 3.30 & 3.70 and hBoot Version .76, .93, .97, 2.02 & 2.10 and how do i even find out my hoot version?

I just tried the autoroot quick method and it said unknown bootloader version. Bootloader is the wrong version. Is there anyway i can change my bootloader version?

aldog25 said:
I just tried the autoroot quick method and it said unknown bootloader version. Bootloader is the wrong version. Is there anyway i can change my bootloader version?
Click to expand...
Click to collapse
Don't use autoroot, click the link i posted...use "revolutionary" Not autoroot
follow the link i posted line by line !!
NO AUTOROOT !

Thanks alot i got pass that step now lol im stuck one more time. Ok I found 9 msid's and zerod them and i found 11 esn's before i got done checking all the esn locations i had about 5 or 6 locations left to check but i didnt becouse it say theres only 9 meids and 11 esns, and now after i zero them all out and reboot my phone and press ##786# the msid and esn is not all zeros like it should say. What do i do now?

Hey louforgiveno do you have a messenger aol msn yahoo or anything if so leave your screen name and log on i be on asap thanks

I just downgraded to 2.05.00.06.10 and used the revskills to try and zero meid/esn i ended up with a log file how do i write this to QXDM now?

i must be missing something cause everywhere i see it no one replies to this question or there is no answer...
after removing 0 and 1943, i can't ever commit the **** to the DIAG TX item... the DIAG RX item takes it just fine. I have been trying and re-trying for hours... thanks

You need the version of qpst listed In the guide....double check your version

I used the EFS Explorer to add and extract the files. Edit of course with Winhex. I bet the file is not saved properly if you've done this already.

louforgiveno said:
You need the version of qpst listed In the guide....double check your version
Click to expand...
Click to collapse
I have 2.7 v366, one guide didn't have a number beyond 2.7, another guide lists v355...
Dean_L said:
I used the EFS Explorer to add and extract the files. Edit of course with Winhex. I bet the file is not saved properly if you've done this already.
Click to expand...
Click to collapse
Makes sense. when you drag files back do they have the same look as the ones already in there? What i do notice is that all the other files have a consistent modified date, and there is also a batch of files that show mod dates that are more recent and don't have the red line through them (they look like txt file images on a windows pc). are these temp files that are perhaps messing with writing the ****?

woodz93 said:
I have 2.7 v366, one guide didn't have a number beyond 2.7, another guide lists v355...
Makes sense. when you drag files back do they have the same look as the ones already in there? What i do notice is that all the other files have a consistent modified date, and there is also a batch of files that show mod dates that are more recent and don't have the red line through them (they look like txt file images on a windows pc). are these temp files that are perhaps messing with writing the ****?
Click to expand...
Click to collapse
It's normal that they look different, don't know if you tried it yet, but you need to delete the 0&1943 from the phone before copying them back from pc.

louforgiveno said:
It's normal that they look different, don't know if you tried it yet, but you need to delete the 0&1943 from the phone before copying them back from pc.
Click to expand...
Click to collapse
i do delete them. but i also see a host of other files that are written on boot(or reboot), those are the ones i'm curious about. i also will downgrade qpst to 2.7.555 to see if that matters.
EDIT: Tried it to no avail. so infuriating... so close but so far...
EDIT: thanks to Klown80 - simple answer is it doesn't matter! there is a guide floating around that says it does, i just happened to end up with it. thinking that it was logical i wasn't going to deviate until i got it right... so unnecessary. so there it is, for those of you who are stumped by this issue...

[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