Related
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.
Ok, I rebooted into recovery last night and I got a 5 vibrates and a green blinking light.
I can get my phone to go into android if i have it pluged into usb but sd support is disabled. If i unplug at any time, it reboots into 5 vibrates. Battery pull.
I can get it ino recovery sometimes but nothing from sd card can be accessed.
I can get it into bootloader but it says s-on for some reason and nothing is flashable from bootloader including ruu's or radio upgrades etc...
The phone is not communicating with pc or pc with phone
Adb is not functional either.
Ive tried everything that i can think of to unroot etc..
Any help would be greatly appreciated. Im desperate.
Thanks,
Incubus
Your sd card may be corrupt. First, back it up, then format it to fat32 in windows. Then put the PB31IMG.zip file on the root of your sd: http://www.megaupload.com/?d=9Q4CNAGX
Put the sd card back in the phone and do a battery pull. When you put the battery back in, hold the volume down key for a few seconds if the phone is plugged in. If it isn't plugged in, hold the power button and the volume down key until the bootloader comes up. It should eventually ask you if you want to update, and press volume up.
If you can't get to the bootloader, then you are most likely bricked. Talk to verizon about a replacement.
Also, before this happened, were you flashing any radios via bootloader?
Well if you got S-ON, I would just take it to VZW and say this **** is messed up get me a replacement, unless you didnt originally buy the phone from them.
I'd try a different SD card formatted to Fat 32 with the RUU on it, unless you already tried that.
but i cant even flash an ruu from my pc either. That has nothing to do with the sd does it? Also, if i put anything on my sd card to flash in bootloader. It just says its checking file and never asks me if i want to install it like it used to.
Does an sd card have to be in the phone in order to flash a ruu from the pc?
incubus26jc said:
but i cant even flash an ruu from my pc either. That has nothing to do with the sd does it? Also, if i put anything on my sd card to flash in bootloader. It just says its checking file and never asks me if i want to install it like it used to.
Does an sd card have to be in the phone in order to flash a ruu from the pc?
Click to expand...
Click to collapse
Don't think so, but I think it has something to do with HBOOT or Radio version that's in the RUU, so if the one that is on the phone now is higher then the RUU, it wont update. Maybe if its the same version as well it wont update. Dont think you need the SD card to run RUU from PC.
So I assume that since you are trying to fix it, there is no way you can get a warranty replacement?
TNS201 said:
Don't think so, but I think it has something to do with HBOOT or Radio version that's in the RUU, so if the one that is on the phone now is higher then the RUU, it wont update. Maybe if its the same version as well it wont update. Dont think you need the SD card to run RUU from PC.
So I assume that since you are trying to fix it, there is no way you can get a warranty replacement?
Click to expand...
Click to collapse
didnt I ruin my chances of a warranty by rooting it?
incubus26jc said:
didnt I ruin my chances of a warranty by rooting it?
Click to expand...
Click to collapse
Totally, if there is any trace of root or customizing of the software in any way your warranty will be voided.
Sent from my SPH-P100 using XDA App
incubus26jc said:
didnt I ruin my chances of a warranty by rooting it?
Click to expand...
Click to collapse
Well if it says S-ON then you are OK. Does it have stock recovery or clockwork on it, if even accessible? If you call in, they will send you a new/refurb model, then you send it back in. They wont even bother checking. I would suggest calling over going to a store. You get better service and more convenient. All I would say that your phone does this and that and wont boot and they will probably try to tell you to do a few things, but if you can't get into the OS, I don't see your phone call being long.
AlpineM3 said:
Totally, if there is any trace of root or customizing of the software in any way your warranty will be voided.
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Only if he goes to the store. If he calls and gets it taken care of, they will send him a phone, then he sends it back. I believe all they check is that there was no water damage and cracked screen and other physical damage.
can i just say i lost it?
incubus26jc said:
can i just say i lost it?
Click to expand...
Click to collapse
If you got insurance on your policy,then yes, you can say it was lost/stolen. You just pay the $90 deductible or whatever for the new phone.
But if you don't have insurance then you're screwed on that approach, also if you call for warranty replacement they just check for any physical damage, but they do try to boot it
Sent from my HTC Incredible
yeah, it looks like im going to pay the fee
incubus26jc said:
yeah, it looks like im going to pay the fee
Click to expand...
Click to collapse
Oh well at least its cheaper then paying full price.
you should be ok. try flashing stock rom through hboot (pb31img file). you can find one posted in the get back to stock thread. if you can't find it let me know and i'll get it for you.
did you try flashing recovery through hboot as well? i can send you a pb31img with clockwork 2.5.0.5 if you want to try but i think you need a signed image.
incubus26jc said:
Ok, I rebooted into recovery last night and I got a 5 vibrates and a green blinking light.
I can get my phone to go into android if i have it pluged into usb but sd support is disabled. If i unplug at any time, it reboots into 5 vibrates. Battery pull.
I can get it ino recovery sometimes but nothing from sd card can be accessed.
I can get it into bootloader but it says s-on for some reason and nothing is flashable from bootloader including ruu's or radio upgrades etc...
The phone is not communicating with pc or pc with phone
Adb is not functional either.
Ive tried everything that i can think of to unroot etc..
Any help would be greatly appreciated. Im desperate.
Thanks,
Incubus
Click to expand...
Click to collapse
Verizon will cover this under the one year warranty. Thankfully I thought I was the only one, this happened to me twice.
Inc,
What were you doing at the time? Did you flash an incorrect hboot? I'm really surprised it can't be recovered if you can access the bootloader. Did you try another card just to rule it out?
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....
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...
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