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.
hi everyone, add me to the list of idiots that shouldn't be doing things like this...
i bought an xtc2clip and should have stopped there, without using it. i had trouble writing files to the chip through their software (latest 1.18). but while poking around, i got s-off. so far so good. when i tried to copy the files over to unlock the bootloader, it kept giving me an error, so i gave up on the xtc2clip (yes, i changed the ribbon cable many times...).
so just after getting s-off, i was able to install TWRP through fastboot. keep in mind, my phone was still s-off, but bootloader locked. i booted TWRP several times just to check things out... all seemed OK.
i then installed SuperSU, using TWRP. i downloaded the 2.46 zip, placed it on my SD card and installed from within TWRP.
i rebooted, and the phone hung on the red verizon screen... i left it like that for at least ten minutes. i was able to reboot through adb, but it never progressed beyond the red verizon screen.
i did some reading, and found other users in a similar state flashed a new ROM to get around that. i then flashed adnybones' Stock Deodexed *Official* -- 3.10.605.7 i found here on XDA.
now - my phone had updated to the latest firmware - so per andybones' instructions, i flashed the 3.10.605.7 linked from his howto.
the flash went OK. i installed the ROM, that seemed to go OK. i rebooted and observed different boot animation - that was a good sign. then the phone hung for over 10 minutes again, never loading the OS.
now, i can reboot to fastboot or download, but cannot boot the OS. the phone goes immediately to fastboot, and will not boot to recovery. it will boot to download, but not recovery...
so i can't get into TWRP and i can't get into the OS.
help?!?!??!?
I have actually used the clip to s-off a VZW M9. It wasn't able to unlock the bootloader at the time, but I was able to flash TWRP and install SU on the stock OS. I then used the shell command to unlock the bootloader.
You stated that your bootloader was never unlocked, and you flashed a custom rom. If that is the case then you need to unlock the bootloader and reflash your custom rom. You will probably need to flash the same VZW stock rom you had prior to flashing a custom rom.
Here is the link to unlocking the bootloader if you are s-off:
http://forum.xda-developers.com/showthread.php?t=3092036
[how to] lock/unlock your bootloader without htcdev(s-off required)
Doesn't the clip now support unlocking VZW M9? Update the xtc software and try again maybe?
If not you will need to flash a stock rom, install SU, and follow the instructions from the link above for unlocking. Once you are unlocked you can start flashing roms.
This is all based on the assumption that your bootloader is locked.
If I misunderstood or you are actually unlocked and forgot to mention it, please disregard everything above.
Sent from my HTC One_M8 using XDA Free mobile app
c5satellite2 said:
I have actually used the clip to s-off a VZW M9. It wasn't able to unlock the bootloader at the time, but I was able to flash TWRP and install SU on the stock OS. I then used the shell command to unlock the bootloader.
You stated that your bootloader was never unlocked, and you flashed a custom rom. If that is the case then you need to unlock the bootloader and reflash your custom rom. You will probably need to flash the same VZW stock rom you had prior to flashing a custom rom.
Click to expand...
Click to collapse
the xtc2clip has two methods to unlock the bootloader. neither will work for me... the "bootloader unlock" tab throws an error when i try to copy the files over the the sd card (i've tried multiple cables and repeated many, many times - something isn't right with this hardware). the newer method, in the "special unlock" tab appears to work, but my phone did nothing after booting with the card installed. and yes, i've seen the other discussions, videos and pics of how to install the sd card. i was able to verify the phone sees the card in the OS, and i'm using the sdcard cradle that came with the phone.
the bootloader status consistently read *** LOCKED *** - so there is no doubt about it.
c5satellite2 said:
Here is the link to unlocking the bootloader if you are s-off:
http://forum.xda-developers.com/showthread.php?t=3092036
[how to] lock/unlock your bootloader without htcdev(s-off required)
Click to expand...
Click to collapse
yes - the problem is that i need root in order to follow those... the problem started after flashing SuperSU. i cannot follow that guide unless i have SU working and an adb shell open to the phone. installing SuperSU is what landed my in fastboot-only land.
c5satellite2 said:
Doesn't the clip now support unlocking VZW M9? Update the xtc software and try again maybe?
If not you will need to flash a stock rom, install SU, and follow the instructions from the link above for unlocking. Once you are unlocked you can start flashing roms.
Click to expand...
Click to collapse
xtc2clip says it does, and i'm certain people can use it to do so... but i've only gotten errors when it tries to write to the sd card. i have manually copied files to the sdcard in the xtc2clip - that's how i got s-off and supercid. i've had nothing but problems trying to use the xtc2clip, and now with s-off, i'm hoping there is a simpler way to do this through adb / fastboot shell. is there?
c5satellite2 said:
This is all based on the assumption that your bootloader is locked.
If I misunderstood or you are actually unlocked and forgot to mention it, please disregard everything above.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
yeah - that's all correct. bootloader is locked, s-off, will boot only to fastboot.
where is the original ROM that came with this phone?? i'll try reflashing that...
pwhitt said:
the xtc2clip has two methods to unlock the bootloader. neither will work for me... the "bootloader unlock" tab throws an error when i try to copy the files over the the sd card (i've tried multiple cables and repeated many, many times - something isn't right with this hardware). the newer method, in the "special unlock" tab appears to work, but my phone did nothing after booting with the card installed. and yes, i've seen the other discussions, videos and pics of how to install the sd card. i was able to verify the phone sees the card in the OS, and i'm using the sdcard cradle that came with the phone.
the bootloader status consistently read *** LOCKED *** - so there is no doubt about it.
yes - the problem is that i need root in order to follow those... the problem started after flashing SuperSU. i cannot follow that guide unless i have SU working and an adb shell open to the phone. installing SuperSU is what landed my in fastboot-only land.
xtc2clip says it does, and i'm certain people can use it to do so... but i've only gotten errors when it tries to write to the sd card. i have manually copied files to the sdcard in the xtc2clip - that's how i got s-off and supercid. i've had nothing but problems trying to use the xtc2clip, and now with s-off, i'm hoping there is a simpler way to do this through adb / fastboot shell. is there?
yeah - that's all correct. bootloader is locked, s-off, will boot only to fastboot.
where is the original ROM that came with this phone?? i'll try reflashing that...
Click to expand...
Click to collapse
Follow this
:http://forum.xda-developers.com/verizon-one-m9/general/ruu-vzw-3-10-605-7-0pjaimg-signed-t3277629
Mr Troop said:
Follow this
:http://forum.xda-developers.com/verizon-one-m9/general/ruu-vzw-3-10-605-7-0pjaimg-signed-t3277629
Click to expand...
Click to collapse
well... i did everything to the letter, and the phone doesn't install the image. in download mode, the phone displays a message at the bottom that the sd card isn't mounted. i tried to check the sd card from within download mode, and it displayed something about smart sd card not found, or something similar.
the sd card is formatted exFat, so maybe i need to format it fat32? it's a 128gb card, i can try again with an 8gb fat32, but i thought exFat was supported...
for the record, i did everything to the letter - even copied the file name from the site to avoid typoing the name... it's a zero, not an O, that sort of thing.
i'll post more information when i have time.
any other help??
pwhitt said:
well... i did everything to the letter, and the phone doesn't install the image. in download mode, the phone displays a message at the bottom that the sd card isn't mounted. i tried to check the sd card from within download mode, and it displayed something about smart sd card not found, or something similar.
the sd card is formatted exFat, so maybe i need to format it fat32? it's a 128gb card, i can try again with an 8gb fat32, but i thought exFat was supported...
for the record, i did everything to the letter - even copied the file name from the site to avoid typoing the name... it's a zero, not an O, that sort of thing.
i'll post more information when i have time.
any other help??
Click to expand...
Click to collapse
Yes format to Fat 32 and it is a zero,also make sure its the only file on the sd card and no bigger than 32gb card
OH! well then, i'll give it another go when i get back to it.
Thanks a lot!
Mr Troop said:
Yes format to Fat 32 and it is a zero,also make sure its the only file on the sd card and no bigger than 32gb card
Click to expand...
Click to collapse
Mr Troop, you're a life saver - thank you very much.
Now if I may be a pest, how do i unlock the bootloader? I keep finding this howto:
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
which is what c5satellite2 pointed me too as well, but this won't work for me since i don't have working SU.
it seems like i need root to unlock the bootloader, but i need to unlock the bootloader (apparently) to get SU...
i have read about 50 different threads spanning the last year+, and I'm not having a lot of luck...
your help is greatly appreciated!
pwhitt said:
Mr Troop, you're a life saver - thank you very much.
Now if I may be a pest, how do i unlock the bootloader? I keep finding this howto:
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
which is what c5satellite2 pointed me too as well, but this won't work for me since i don't have working SU.
it seems like i need root to unlock the bootloader, but i need to unlock the bootloader (apparently) to get SU...
i have read about 50 different threads spanning the last year+, and I'm not having a lot of luck...
your help is greatly appreciated!
Click to expand...
Click to collapse
Well done :good:
Yes i have used this or theirs htcdev
dont forget to change title to solved
https://www.htcdev.com/
Mr Troop said:
Well done :good:
Yes i have used this or theirs htcdev
dont forget to change title to solved
https://www.htcdev.com/
Click to expand...
Click to collapse
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
Just looked and i dont think you can unlock the bootloader by htcdev
will keep looking
Mr Troop said:
Just looked and i dont think you can unlock the bootloader by htcdev
will keep looking
Click to expand...
Click to collapse
right! that's the whole problem. verizon has locked the bootloader, and HTC isn't unlocking verizon phones...
this is killing me. i pay hundreds of dollars for a product, and it's loaded with their bloatware and i can't run an adblocker???
it's insulting.
pwhitt said:
right! that's the whole problem. verizon has locked the bootloader, and HTC isn't unlocking verizon phones...
this is killing me. i pay hundreds of dollars for a product, and it's loaded with their bloatware and i can't run an adblocker???
it's insulting.
Click to expand...
Click to collapse
HTC does not allow devices with a Verizon CID to be unlocked.
Your S-Off, You would need a way to switch to superCID (or any other nonVerizon CID) in order to oem unlock.
but not 100% sure so i would leave it and do some research check back tomorrow :good:
I was able to write the super cid, but I can't get the device string ........ Adb barfs, because oem unlocking can't be enabled.
Edit: n/m, saw you tried this already.
I know there's a way to do this, but you'll have better luck asking in the Verizon M9 forums. Many, many people have unlocked their bootloaders, HTC and Verizon notwithstanding.
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
From what I can recall, I did exactly that. Installed twrp, and had it install su. Then I unlocked boot loader. It doesn't make sense, but it worked.
Sent from my HTC One_M8 using XDA Free mobile app
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
Twrp 2.9.0.1 and supersu 2.65. Only that combo seems to work. That is how mine and many others are set up.
Htcdev to unlock bootloader but you need oem unlocking ticked in the rom.
If adb doesn't work its because you dont have usb debugging enabled in the rom. You only have fastboot access for now. But thats ok because thats all you need to flash twrp 2.9.0.1 and supersu 2.65.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Twrp 2.9.0.1 and supersu 2.65. Only that combo seems to work. That is how mine and many others are set up.
Click to expand...
Click to collapse
I have been using 3.0.0.0 and 2.65 since upgrading to MM and have had zero problems.
Hey Folks
I have a slight issue, I had a rooted HTC 10(UK EE) phone running firmware 1.80.91.1, which I wanted to update so I flashed a back-up from TWRP to restore OTA functionality, however, this backup was corrupted and the phone got stuck in a boot loop with no OS, hurrah!
I've sorted that however, by locating a TWRP backup of 1.21.91.4, which was the only one I could find for the CID EVE__001, this file was just a boot and sys.img no recovery, now I still can't get OTA updates as I'm getting the file system is corrupted error when trying to download the updates.
So I've hunted and hunted either to find a full back-up, recovery or RUU that will work with my CID as I'm S-on, I have had no luck, so I can no longer get updates for the phone.
So, does anyone have a stock recovery they could upload for either 1.21.91.4, or even better a full back-up of any of the x.xx.91.x firmware? I've been tearing my hair out trying to find anything above 1.21.91.4 and even that was just a partially back up.
Any help is muchly appreciated.
Hi, I am om EE uk but my CID is HTC__001.
I HAVE A FULL BACKUP DONE IN TWRP, WHICH YOU CAN HAVE. I WILL SORT IT OUT AND SEND YOU A LINK. DONT KNOW IF IT WILL WORK BECAUSE OF DIFFERENT CID, BUT YOU CAN GIVE IT A GO.
GIVE ME A DAY OR SO.
Sorry to resurrect the thread, @si86 I've having trouble restoring radio signal on my HTC 10 after flashing an incorrect ROM, I'm on EE also- I'd really appreciate a copy of your TWRP backup to try on my handset if you are able to supply, would be very appreciated! I'm able to change the CID to match, having been through them all recently! My bootloader is unlocked and I'm S-Off. Thanks.
@Tuesg Were you able to rectify your situation?
SailorJerry01 said:
Sorry to resurrect the thread, @si86 I've having trouble restoring radio signal on my HTC 10 after flashing an incorrect ROM, I'm on EE also- I'd really appreciate a copy of your TWRP backup to try on my handset if you are able to supply, would be very appreciated! I'm able to change the CID to match, having been through them all recently! My bootloader is unlocked and I'm S-Off. Thanks.
@Tuesg Were you able to rectify your situation?
Click to expand...
Click to collapse
I am uploading the copy to my g_drive now. It is around 6.5Gb. Sent me your email so I can give you access to the folder so you can download it.
Sent from my HTC 10 using XDA-Developers Legacy app
you legend. will pm you now. Thanks.
SailorJerry01 said:
you legend. will pm you now. Thanks.
Click to expand...
Click to collapse
I've just hunted high and low to try and figure out why nothing will flash successfully to my HTC 10.
turns out to be this same issue, I'm showing as CID - EVE_001 on an MID 2PS62000
Any chance you could send me that link as well so that I can at least try and get the phone back to a usable state instead of being stuck in either bootloader, download or recovery.
My phone is Bootloader unlocked, but still S-On as I hadn't got that far yet.
Will i need to flash a stock recovery? and lock the bootloader again to get this to install properly?
It's really proving tricky as hell.
I got caught out a bit here as I was half way to using sunshine to s_off, and then I accidentally triggered an OTA update to Nougat 7.0.......
It never restarted properly after that and i've been unable to get it back to 6 or any other ROM at all as they all fail.
I managed to fix it, but only by switching to s-off and installing the EU edition software, I'm a tad concerned now though as I've yet to get the roll out of the 7.0 update, not sure if that's because of installing a different firmware or whether it hasn't been rolled out yet.
@si86 Many thanks for your assistance and sharing the files, I was unable to fix my phone after trying various avenues (100+hrs) so I swallowed my pride and went the insurance route, not worth spending more time on getting to work and I now have a rather nice device, yet unusable call/texts wise to play with alongside my nice shiny new one running 2.41.91.3 - I've rooted and S-off with sunshine, just trying to decide whether i'm going to play with some more custom ROMS again! Of course I am!
@Tuesg Kudos on fixing your issue!
guys can you please help me, my HTC 10 is EVE_001 i want to unroot how do i do that? i bought it off gumtree and cant get banking app to work due it being rooted.
faceman123 said:
guys can you please help me, my HTC 10 is EVE_001 i want to unroot how do i do that? i bought it off gumtree and cant get banking app to work due it being rooted.
Click to expand...
Click to collapse
You can usually do it straight from the SuperSU app itself.
silegeek said:
You can usually do it straight from the SuperSU app itself.
Click to expand...
Click to collapse
how can i do that, im really noob to this, thanks
faceman123 said:
how can i do that, im really noob to this, thanks
Click to expand...
Click to collapse
Along with superuser usually comes with an app for configuring it, depending on how it was rooted. SuperSU is usually the most common although I much prefer magisk.
It will be obvious what it's called, either superuser, SuperSU, etc. SuperSU contains within it the ability to fully unroot.
If there's no app, and if it is a stock rom, and not a custom one, a factory reset will remove it. If not, you will probably need to either do some adb commands to remove it, or remove it using the recovery.
silegeek said:
Along with superuser usually comes with an app for configuring it, depending on how it was rooted. SuperSU is usually the most common although I much prefer magisk.
It will be obvious what it's called, either superuser, SuperSU, etc. SuperSU contains within it the ability to fully unroot.
If there's no app, and if it is a stock rom, and not a custom one, a factory reset will remove it. If not, you will probably need to either do some adb commands to remove it, or remove it using the recovery.
Click to expand...
Click to collapse
you sir are my hero, i will try when i get home !!
silegeek said:
Along with superuser usually comes with an app for configuring it, depending on how it was rooted. SuperSU is usually the most common although I much prefer magisk.
It will be obvious what it's called, either superuser, SuperSU, etc. SuperSU contains within it the ability to fully unroot.
If there's no app, and if it is a stock rom, and not a custom one, a factory reset will remove it. If not, you will probably need to either do some adb commands to remove it, or remove it using the recovery.
Click to expand...
Click to collapse
In short terms, yes that might work for banking apps but it won't work for future Android updates. You need a completely stock (untouched) system and SU changes that even if you choose to unroot via the application.
hi when i i tried that super user unoot it goes to Twrp bootloader and nothing in there says unroot or uninstall twrp bootloader
Hey guys Google pay still doesn't work says phone has been modified I am eve_001 software number 1.80.401.1 what can I do to make phone stock again
faceman123 said:
Hey guys Google pay still doesn't work says phone has been modified I am eve_001 software number 1.80.401.1 what can I do to make phone stock again
Click to expand...
Click to collapse
I've had that issue with both Viper and Maximus. Removing root doesnt seem to totally remove it, and certain apps still pick up ... something.
Going back to total stock condition is a huge pain in the unmentionables. Because quite a lot of phones don't actually have an RUU for thier CID (for instance mine, H3G__001) has no RUU. So complete stock, even from TWRP backup was never an option for me. Even though ROOT wasnt an issue, things like OTA problems persisted no matter what.
I had to S-OFF (worth it in general tbh) in order to go back to a complete stock condition using the HTC WWE version (HTC__001). In the end I just decided to stick with the ROM I have now, LeeDroid. It has the option to be installed without root from the get go, but these days I just use Magisk. It is so simple to hide from banking apps and even things like pokemon go, that it doesnt do any harm having root there.
si86 said:
Hi, I am om EE uk but my CID is HTC__001.
I HAVE A FULL BACKUP DONE IN TWRP, WHICH YOU CAN HAVE. I WILL SORT IT OUT AND SEND YOU A LINK. DONT KNOW IF IT WILL WORK BECAUSE OF DIFFERENT CID, BUT YOU CAN GIVE IT A GO.
GIVE ME A DAY OR SO.
Click to expand...
Click to collapse
Hey si86,
wondering if I can get a link to your backup too!!
Thanks man!
PM me your email and I will send you a link.
Sent from my HTC 10 using XDA-Developers Legacy app
---------- Post added at 09:44 PM ---------- Previous post was at 09:40 PM ----------
Jon Olita said:
Hey si86,
wondering if I can get a link to your backup too!!
Thanks man!
Click to expand...
Click to collapse
Send me your email, and I will send you a link
Sent from my HTC 10 using XDA-Developers Legacy app
si86 said:
Hi, I am om EE uk but my CID is HTC__001.
I HAVE A FULL BACKUP DONE IN TWRP, WHICH YOU CAN HAVE. I WILL SORT IT OUT AND SEND YOU A LINK. DONT KNOW IF IT WILL WORK BECAUSE OF DIFFERENT CID, BUT YOU CAN GIVE IT A GO.
GIVE ME A DAY OR SO.
Click to expand...
Click to collapse
Hi there,
I'm in the exact same spot as the guy above. I restored the backup he mentioned, but don't have the Recovery. Therefore my phone is telling me I need to enter decryption password and won't boot past it.
Would you be able to give me that backup too?
Thanks.
Update: The guys at Razer are just about as clueless as a retail phone carrier. They told me to do the exact same thing, the factory reset and all that, but they don't know what they're doing.
So FYI: IF YOU'RE BOOTLOADER IS LOCKED AND YOUR OS WON'T START, YOU'RE SCREWED.
Okay so I rooted the phone on Oreo, the second to last update, and tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again.
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it.
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader.
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
Dashaquavius said:
Okay so I rooted the phone on Oreo, the second to last update, sand tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again..
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it..
Click to expand...
Click to collapse
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Roxas598 said:
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader
Click to expand...
Click to collapse
iliais347 said:
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
Click to expand...
Click to collapse
waiflih said:
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Click to expand...
Click to collapse
1. I didn't flash TWRP with the bootloader in the locked state, it was while it was unlocked.
2. Out of desperation, after flashing the stock images multiple times (while it says errors and maximum download reached and stuff) I re-locked the bootloader with the command thinking it would finally at least boot into the OS, to no avail.
3. Factory images didn't flash without some kind of error.
4. I'm unable to run any kind of commands, it says it's not allowed.
5. I've flashed multiple times, flashed the previous updates and the latest updates, and there's always some kind of error or it's not allowed.
I'm just gonna contact Razer. Apparently, I can't flash anything if the bootloader is locked? And the phone won't even boot into the OS to let me tick the option? I think I'm screwed.
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
waiflih said:
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
Click to expand...
Click to collapse
It says flashing is not allowed for everything.
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
waiflih said:
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
Click to expand...
Click to collapse
I just got off with Razer support, they're just gonna send me a new one.
And apparently, absolutely NO OTG support!
Let this thread serve as a warning..
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
parky169 said:
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
Click to expand...
Click to collapse
Interesting. I sent 2 phones with speaker issues and they offered a replacement for both and gave me shipping labela.
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone
rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?
Well not really. But I follow many instrucciones from differents post and nothing
rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:
I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.
Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/
Ok., I will let you guys know thank you
Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.
You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.
@rectangularspace Link to the standalone platform tools HERE. This is all you need.
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.
I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.
rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good: