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.
Related
Froyo SBF and Bootloader for Flipside MB508 AT&T USA
Bootloader: BL_917B_4G_sageemu_Consumer_replacer.zip
Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com
SBF Flash :
Android 2.2.2 ------ Blur_Version.2.159.17.MB508.ATT.en.US
SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz
Download SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz for free on Filesonic.com
WARNING: ONCE YOU FLASH THE FROYO SBF ANY ATTEMPT TO DOWNGRADE TO ECLAIR MIGHT RESULT IN A HARD BRICK !!!!!
These files are made available as a general courtesy and I assume no responsibilty for your own actions.
Thanks, I was just looking for this.. I did an update from eclair to froyo (2.1 - 2.2) and everything was fine until I did a hard reset and lost service and it kept crashing each time I would go into the settings and wireless/APN options. Wouldn't take ATT and TM sim cards.. Going to try flashing the SBF and see if this resolves it.
Edit: aaand, flashed and all fixed.
Great find, nice to have an option in case we screw something up. I wonder if there's any benefit to flashing the 2.2 sbf instead of flashing a clean 2.1 and updating to 2.2...
OH I HOPE THIS FIXES MY FREEZING ISSUE!!! Im so sick of having to take out the battery 10 or more times a day when this thing freezes, plus Im sure it does damage as hard shutting down a computer does. Ill let everyone know.
How would I flash the bootloader?
pre4speed said:
OH I HOPE THIS FIXES MY FREEZING ISSUE!!! Im so sick of having to take out the battery 10 or more times a day when this thing freezes, plus Im sure it does damage as hard shutting down a computer does. Ill let everyone know.
How would I flash the bootloader?
Click to expand...
Click to collapse
Ya know what...i'm not really sure how to flash it...or why it would be needed as opposed to a regular bootloader...
Got it flashed. Same way as you flash a rom. Like you tho, I havent a clue why. I also flashed the rom. Did NOT help with freezing, in fact seems worse now. Cant use my phone for more than 3-4 minutes before it freezes. Any idea who Id contact at Motorola to get assistance with this, because this is ridiculous. Thanks for posting this.
pre4speed said:
Got it flashed. Same way as you flash a rom. Like you tho, I havent a clue why. I also flashed the rom. Did NOT help with freezing, in fact seems worse now. Cant use my phone for more than 3-4 minutes before it freezes. Any idea who Id contact at Motorola to get assistance with this, because this is ridiculous. Thanks for posting this.
Click to expand...
Click to collapse
Hey check your SD card. My phone wasn't just freezing....it would completely just reboot and stay on the moto screen. I found out that i was my memory card. When I removed it, it worked fine and when I put it back in, it shut down automatically. Found out the problem was the 2nd partition I to use the link2sd...had to change it so that the 2nd partition was set to primary and its been working fine ever since. Not one single freeze or anything.
Dunno if that is going on with you but if it is I hope this helps
How do I set the second partition as primary? I've noticed also when anything gets linked, it goes to the first partition. First partition mem goes down, whereas second stays the same.
Sent from my MB508 using XDA App
I use something called 'EASEUS Partition Master 8.0.1 Home Edition' that I think I downloaded on google (I don't remember) but you can use it to change create and format partitions and you just gotta make sure you set it to 'primary' and not 'logical'. Try to see if you can find it and do it and let me know. If you can't find it let me know and I'll see if I can send you mine. And if you do and you still have trouble, detail to me what is going on and i'll walk you through it. It took me a lil while to figure it out.
So I could use minitool partition as well? That's the one I have. I will try that out. Phone hasn't froze today for a long time, but now that I said that, well you know. Lol I will keep you updated for sure. Thanks.
Sent from my MB508 using XDA App
Yep, that will work just fine.
JBallin4life27 said:
Ya know what...i'm not really sure how to flash it...or why it would be needed as opposed to a regular bootloader...
Click to expand...
Click to collapse
Found out why the need for the updated bootloader. Froyo does not support the Eclair version of the bootloader, so if you need to flash again, you would not be able to unless you update the bootloader. HTH
I'm honestly kinda a noob at this... never messed with anything like a bootloader. Can somebody explain to me how to do this? I'm wanting to flash back to a clean 2.2 and the post before mine sounds like that might be bad without updating boot loader first.
Also the rom, just install it with RSD?
boazjuggalo said:
I'm honestly kinda a noob at this... never messed with anything like a bootloader. Can somebody explain to me how to do this? I'm wanting to flash back to a clean 2.2 and the post before mine sounds like that might be bad without updating boot loader first.
Also the rom, just install it with RSD?
Click to expand...
Click to collapse
You will flash the bootloader the same as the froyo rom in RSD. Do the bootloader first. Then flash the froyo rom. Any questions, don't hesitate.
Sent from my MB508 using XDA App
pre4speed said:
You will flash the bootloader the same as the froyo rom in RSD. Do the bootloader first. Then flash the froyo rom. Any questions, don't hesitate.
Sent from my MB508 using XDA App
Click to expand...
Click to collapse
Phone fully on or update mode or what? For both?
USB Debugging on?
Version of RSD need to be up or still using 4.9?
I'm not 100% of this, as I don't have the MB508 as of the moment, but I believe once you flash the stock 2.2 rom or OTA you will loose root.
Someone correct me if I'm wrong, this is just intended for those who want to know info.
boazjuggalo said:
Phone fully on or update mode or what? For both?
USB Debugging on?
Version of RSD need to be up or still using 4.9?
Click to expand...
Click to collapse
When you flash you will need to go into bootloader mode. Power off phone, the use the proper key funtion (sorry don't remember what it is) to start bootloader. Then flash updated bootloader. When flashing via RSD, it doesn't matter about usb debugging because you aren't fully booted into the phone. I used version 4.9 and had no problems flashing both. Good luck.
Sent from my MB508 using XDA App
kaijura said:
I'm not 100% of this, as I don't have the MB508 as of the moment, but I believe once you flash the stock 2.2 rom or OTA you will loose root.
Someone correct me if I'm wrong, this is just intended for those who want to know info.
Click to expand...
Click to collapse
Yes this is correct. I belive this is the case anytime you flash using RSD. You can gain root again after using the most current version of superoneclick.
Sent from my MB508 using XDA App
This, along with a link to RSD Lite to install it, needs to be stickied! I was trying to upgrade a friend's Flipside following the directions on Motorola's website and it bricked the device. flashing the sbf file saved the day!
links death
any one can reupload the files?
the links are no more alive
Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters..... also i flashed twrp cause there was no OTA att update found (checked twice)
Dragonmaster0430 said:
Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters.....
Click to expand...
Click to collapse
1) Mods won't like you posting a question in the Dev thread... there are specific sections (general, firmware, etc) where you can post it...
2)Considering that your phone is practically new, if you only rooted it and haven't installed a custom recovery, you will be able to update your firmare (OTA) through the built in upgrade process on your phone. Once, that is done, root your phone and install a custom recovery like TWRP.
good luck
Deathsting_50cal said:
1) Mods won't like you posting a question in the Dev thread... there are specific sections (general, firmware, etc) where you can post it...
2)Considering that your phone is practically new, if you only rooted it and haven't installed a custom recovery, you will be able to update your firmare (OTA) through the built in upgrade process on your phone. Once, that is done, root your phone and install a custom recovery like TWRP.
good luck
Click to expand...
Click to collapse
1. SH!t sorry! I didn't realize ?
2. ...i already flashed TWRP,cause i checked twice for a OTA before hand and therr was no update found
Anyone got any ideas?
Dragonmaster0430 said:
Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters..... also i flashed twrp cause there was no OTA att update found (checked twice)
Click to expand...
Click to collapse
Yes, I sure do.
First of all, if you want the newest ViperOne, you'll want 5.0.1 firmware, at least.
Hook up to you PC. Get into ADB/fastboot, and issue the command fastboot getvar all.
Post the readout here, and I, or someone else, will point you in the proper direction to update your firmware.
Please make sure to delete the serial# and IMEI from the readout. Never post those in a public forum.
xunholyx said:
Yes, I sure do.
First of all, if you want the newest ViperOne, you'll want 5.0.1 firmware, at least.
Hook up to you PC. Get into ADB/fastboot, and issue the command fastboot getvar all.
Post the readout here, and I, or someone else, will point you in the proper direction to update your firmware.
Please make sure to delete the serial# and IMEI from the readout. Never post those in a public forum.
Click to expand...
Click to collapse
Ok sure!....how do I issue a command?
Dragonmaster0430 said:
Ok sure!....how do I issue a command?
Click to expand...
Click to collapse
Have you never used ADB or fastboot before?
Okay. This will update your firmware. Backup anything important to you, because this will wipe your phone.
Go here: http://www.htc.com/us/support/htc-one-att/news/
Scroll down to where it says "Manual system update instructions". Read what it says, then click the download link at the bottom.
xunholyx said:
Have you never used ADB or fastboot before?
Okay. This will update your firmware. Backup anything important to you, because this will wipe your phone.
Go here: http://www.htc.com/us/support/htc-one-att/news/
Scroll down to where it says "Manual system update instructions". Read what it says, then click the download link at the bottom.
Click to expand...
Click to collapse
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?
Dragonmaster0430 said:
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?
Click to expand...
Click to collapse
Yes, but that's easy. Unlock your bootloader, flash TWRP, and flash a rooted ROM, such as ViperOne.
Also, I recommend not using one click toolkit methods. They often cause problems, plus doing it manually is easy and gives you an introduction to ADB and fastboot, making it less intimidating.
I don't know how to do it manually =( last time I tried I hard bricked my m7
Dragonmaster0430 said:
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?
Click to expand...
Click to collapse
I get this when running the RUU from the link you sent...
Dragonmaster0430 said:
I get this when running the RUU from the link you sent...
Click to expand...
Click to collapse
what should i do now?
Dragonmaster0430 said:
I get this when running the RUU from the link you sent...
Click to expand...
Click to collapse
You need to re-lock your bootloader first if you are not S-Off.
Get back into fastboot and do fastboot oem lock, then leave your phone connected, and run the RUU again.
xunholyx said:
You need to re-lock your bootloader first if you are not S-Off.
Get back into fastboot and do fastboot oem lock, then leave your phone connected, and run the RUU again.
Click to expand...
Click to collapse
ok I did that my bootloader now shows
"*** TAMPERED***
*** RELOCKED ***
and i still am get the same error message that I posted the screenshot of before
Dragonmaster0430 said:
ok I did that my bootloader now shows
"*** TAMPERED***
*** RELOCKED ***
and i still am get the same error message that I posted the screenshot of before
Click to expand...
Click to collapse
You have an AT&T phone, right? That's what it says in the title. And that download link I gave you is from HTC's official website for the latest AT&T RUU.
xunholyx said:
You have an AT&T phone, right? That's what it says in the title. And that download link I gave you is from HTC's official website for the latest AT&T RUU.
Click to expand...
Click to collapse
Yup It is at&t
Dragonmaster0430 said:
Yup It is at&t
Click to expand...
Click to collapse
I don't know.
Maybe you don't have the drivers installed on your PC.
Go to Device Manager with your phone connected. You should see that your M8 is connected.
If you don't see it in Device Manager, download HTC Sync Manager and run it to install the drivers. After that, uninstall HTC Sync. It doesn't play nice with ADB and fastboot. The drivers will remain.
Then go to Device Manager and confirm that your phone is listed there when connected..
xunholyx said:
I don't know.
Maybe you don't have the drivers installed on your PC.
Go to Device Manager with your phone connected. You should see that your M8 is connected.
If you don't see it in Device Manager, download HTC Sync Manager and run it to install the drivers. After that, uninstall HTC Sync. It doesn't play nice with ADB and fastboot. The drivers will remain.
Then go to Device Manager and confirm that your phone is listed there when connected..
Click to expand...
Click to collapse
mine shows up under device manager as "MTP"
Dragonmaster0430 said:
mine shows up under device manager as "MTP"
Click to expand...
Click to collapse
I really don't know what's going on here.
I do know that if you were to go S-Off, updating your firmware is a piece of cake. You just need to find the firmware.zip and flash it.
xunholyx said:
I really don't know what's going on here.
I do know that if you were to go S-Off, updating your firmware is a piece of cake. You just need to find the firmware.zip and flash it.
Click to expand...
Click to collapse
how do i do all that?
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
I want to UNroot my phone/restore my phone due to the fact that I believe I may have done something wrong in the process. I am on 5.0.1
When I turn my phone on, I do get the welcome screen saying my phone's unlocked and all but when I try to use xposed installer it says that my device is not properly rooted?
Specifically it says " The latest version of Xposed is currently not active. Did you install the framework and reboot?" When I try to do this, it says
"Xposed is not (yet) compatible with Android SDK version 21 or your processor architecture (armeabiv7a)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by" /data/data/de.robv.android.xposed.installer/cache/app_process";
cause by library "libdvm.so" not found"
And I believe I had a very hard time (when rooting) copying and pasting the SuperSU to internal storage. Not all the files were actually being transferred over.
I pretty much want to restore my phone so that I can try to root it properly this time.
When the tutorial on how root our phones came out, I feel as though I rushed it from excitement without properly educating myself on what to watch out for.
Maybe I am only HALF rooted? lol sounds so stupid. but my greenify works and superSU grants access to everything. I just don't understand.
My last phone was iphone4 and jailbreaking that was easy. This is something else.
Can anyone help? Thank you for your time!
yungzhvo said:
I want to UNroot my phone/restore my phone due to the fact that I believe I may have done something wrong in the process. I am on 5.0.1
When I turn my phone on, I do get the welcome screen saying my phone's unlocked and all but when I try to use xposed installer it says that my device is not properly rooted?
Specifically it says " The latest version of Xposed is currently not active. Did you install the framework and reboot?" When I try to do this, it says
"Xposed is not (yet) compatible with Android SDK version 21 or your processor architecture (armeabiv7a)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by" /data/data/de.robv.android.xposed.installer/cache/app_process";
cause by library "libdvm.so" not found"
And I believe I had a very hard time (when rooting) copying and pasting the SuperSU to internal storage. Not all the files were actually being transferred over.
I pretty much want to restore my phone so that I can try to root it properly this time.
When the tutorial on how root our phones came out, I feel as though I rushed it from excitement without properly educating myself on what to watch out for.
Maybe I am only HALF rooted? lol sounds so stupid. but my greenify works and superSU grants access to everything. I just don't understand.
My last phone was iphone4 and jailbreaking that was easy. This is something else.
Can anyone help? Thank you for your time!
Click to expand...
Click to collapse
This may be of some help.
kkretch said:
This may be of some help.
Click to expand...
Click to collapse
Thank you for replying so quickly! :good:
Do you happen to know if this will automatically upgrade me to the newest OTA upgrade?
I want to stay on 5.1.1 so I can try to root it properly. And I've been delaying the OTA upgrade since day 1 and still doing so even with the supposed root I have on my phone right now.
yungzhvo said:
Thank you for replying so quickly! :good:
Do you happen to know if this will automatically upgrade me to the newest OTA upgrade?
I want to stay on 5.1.1 so I can try to root it properly. And I've been delaying the OTA upgrade since day 1 and still doing so even with the supposed root I have on my phone right now.
Click to expand...
Click to collapse
If you're going to root your phone, you don't want to take the OTA. You'll just have to downgrade to Lollipop anyway.
Use ODIN and flash the full firmware. 5.1.1 should be good. @hsbadr has a thread in the Development forum with all of the firmware that's available. It'll save you the slow download speed of Sammobile.
If when you go into download mode and you see "mode: developer," you're pretty close to root. Flash SuperSU and TWRP and you'll be there.
douger1957 said:
If you're going to root your phone, you don't want to take the OTA. You'll just have to downgrade to Lollipop anyway.
Use ODIN and flash the full firmware. 5.1.1 should be good. @hsbadr has a thread in the Development forum with all of the firmware that's available. It'll save you the slow download speed of Sammobile.
If when you go into download mode and you see "mode: developer," you're pretty close to root. Flash SuperSU and TWRP and you'll be there.
Click to expand...
Click to collapse
"If when you go into download mode and you see "mode: developer," you're pretty close to root. Flash SuperSU and TWRP and you'll be there."
Can you elaborate a little more on this for me? Because when I first rooted I made sure to do EVERY step. Read the forums and watched youtube videos directly linked from the forum.
The thing I just didn't know how to do correctly was flashing the SuperSU and TWRP (I THINIK)
I sincerely just remember trying to copy and paste some files into system storage? something like that... and not EVERYTHING was transferring over.
When I turn on my phone I get the welcome screen with the picture of the unlocked lock with "custom" underneath. So I know I must have done SOMETHING correctly.
Im just sincerely lost. It's quite infuriating .
yungzhvo said:
"If when you go into download mode and you see "mode: developer," you're pretty close to root. Flash SuperSU and TWRP and you'll be there."
Can you elaborate a little more on this for me? Because when I first rooted I made sure to do EVERY step. Read the forums and watched youtube videos directly linked from the forum.
The thing I just didn't know how to do correctly was flashing the SuperSU and TWRP (I THINIK)
I sincerely just remember trying to copy and paste some files into system storage? something like that... and not EVERYTHING was transferring over.
When I turn on my phone I get the welcome screen with the picture of the unlocked lock with "custom" underneath. So I know I must have done SOMETHING correctly.
Im just sincerely lost. It's quite infuriating .
Click to expand...
Click to collapse
Go into download mode. From phone off, hold the volume down, power and home buttons together. If it says "mode: developer" in the upper left hand corner when you get it in developer mode, your bootloader is unlocked. At that point you can pick up the instructions for flashing SuperSU and TWRP. You may need to flash the Emotion kernel... it's been awhile since I unlocked Lollipop.
douger1957 said:
Go into download mode. From phone off, hold the volume down, power and home buttons together. If it says "mode: developer" in the upper left hand corner when you get it in developer mode, your bootloader is unlocked. At that point you can pick up the instructions for flashing SuperSU and TWRP. You may need to flash the Emotion kernel... it's been awhile since I unlocked Lollipop.
Click to expand...
Click to collapse
I'm about to head home to try this out. maybe I'm just a step away from getting this whole thing to work!
Thank you for your help!! I will respond if I have any issues!
yungzhvo said:
Thank you for replying so quickly! :good:
Do you happen to know if this will automatically upgrade me to the newest OTA upgrade?
I want to stay on 5.1.1 so I can try to root it properly. And I've been delaying the OTA upgrade since day 1 and still doing so even with the supposed root I have on my phone right now.
Click to expand...
Click to collapse
As long as you use the stock firmware from SamMobile and follow the directions in the video, EXACTLY ......... don't take any shortcuts. You will need to join SamMobile to get the download but its simple and free.
kkretch said:
As long as you use the stock firmware from SamMobile and follow the directions in the video, EXACTLY ......... don't take any shortcuts. You will need to join SamMobile to get the download but its simple and free.
Click to expand...
Click to collapse
Hey! Thank you for the advice!
I downloaded the firmware from @hsbadr ! Will that work? Or is it better for me to download it from SamMobile? I want to make sure I don't do anything incorrectly.
p.s. have you already rooted your phone?
yungzhvo said:
Hey! Thank you for the advice!
I downloaded the firmware from @hsbadr ! Will that work? Or is it better for me to download it from SamMobile? I want to make sure I don't do anything incorrectly.
p.s. have you already rooted your phone?
Click to expand...
Click to collapse
SamMobile is very reliable but if you trust your source then you should be OK. I have done the root thing many times years ago but I'm happy with stock firmware and I need my devices to work without issue so I leave well enough alone.
For starters, I have an AT&T HTC M9. I unlocked the bootloader, and after a while, got TWRP 3.0.2.0 installed as the custom recovery. I decided to flash ARHD, since that's my personal favorite that I've used on my M7 and M8. After flashing and clearing cache, the phone optimizes apps, reboots, and then stays at the HTC screen for a bit. Finally, the screen will turn off as if it's booted in. I could then wake the device and adjust volume and such, but I still had the HTC logo covering what would be the UI. After a bit more time, the setup menu finally came up. I couldn't set up wifi, as it got stuck on the "connecting" screen. Wiped, re-flashed ARHD. Same thing. Finally got through the setup, and I had no service. What am I doing wrong? Do I need to install a corresponding firmware or something? This happens to me every time. Also the M9 had Android 6.0 with Sense 7.0, for the record.
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
shivadow said:
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
Click to expand...
Click to collapse
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
manlavi95 said:
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
Click to expand...
Click to collapse
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Edit: I've got an RUU that I was thinking of using and then just rooting the stock ROM and then going about my day. I'd be ok with that if I knew for a fact that it wouldn't remove TWRP. That and I was looking forward to the ARHD battery life.
manlavi95 said:
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Click to expand...
Click to collapse
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Flippy498 said:
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Click to expand...
Click to collapse
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
manlavi95 said:
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
Click to expand...
Click to collapse
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Flippy498 said:
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Click to expand...
Click to collapse
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
manlavi95 said:
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
Click to expand...
Click to collapse
Based on my previous experiences with the M9 I'd say yes.
Flippy498 said:
Based on my previous experiences with the M9 I'd say yes.
Click to expand...
Click to collapse
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
manlavi95 said:
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
Click to expand...
Click to collapse
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Flippy498 said:
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Click to expand...
Click to collapse
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Another edit: I also don't see SuperSU anywhere, and that's confusing me just a bit.
manlavi95 said:
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Click to expand...
Click to collapse
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Flippy498 said:
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Click to expand...
Click to collapse
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
manlavi95 said:
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
Click to expand...
Click to collapse
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Flippy498 said:
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Click to expand...
Click to collapse
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
manlavi95 said:
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
Click to expand...
Click to collapse
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Flippy498 said:
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Click to expand...
Click to collapse
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
manlavi95 said:
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
Click to expand...
Click to collapse
Flash it like any other rom. The aroma installer is actually pretty straight forward. Choose default since there is nor AT&T specific installation.
Just make sure that you read what it wants you to do. Sometimes it asks which apps you want to install and sometimes which you want to uninstall.