1st off i want to say i love these forums...
ok... ill start from the the beginning.
HTC vivid w/ stock ICS
my bootLoader WAS unLocked.
a message came across my phone stating there was an ATT upDate for my device (10.10). not remembering i had an unlocked bootLoader, i accepted the upDate. the phn reStarted. it attempts to update, then i get the dead android w/ the red Triangle... crucial, i know...
i figure no prob, ill just reLock the bootLoader and not accept upDate. well that's not working.
in the hBoot screen, the following msg appears:
***reLocked***
***security warning***
i attempted reBoot. my phn starts up as usual as if its going to work properly, however phn autoAttempts to update and restarts my phone. instead of upDating, it goes back to hBoot screen showing the same thing.
so basically i have a problem where when my phn starts up, it wants to complete the upDate initiated. when it reStarts it goes back to hBoot screen.
any help would be appreciated.
I have the same problem. how ever my bootloader was locked lol....
loominus said:
1st off i want to say i love these forums...
ok... ill start from the the beginning.
HTC vivid w/ stock ICS
my bootLoader WAS unLocked.
a message came across my phone stating there was an ATT upDate for my device (10.10). not remembering i had an unlocked bootLoader, i accepted the upDate. the phn reStarted. it attempts to update, then i get the dead android w/ the red Triangle... crucial, i know...
i figure no prob, ill just reLock the bootLoader and not accept upDate. well that's not working.
in the hBoot screen, the following msg appears:
***reLocked***
***security warning***
i attempted reBoot. my phn starts up as usual as if its going to work properly, however phn autoAttempts to update and restarts my phone. instead of upDating, it goes back to hBoot screen showing the same thing.
so basically i have a problem where when my phn starts up, it wants to complete the upDate initiated. when it reStarts it goes back to hBoot screen.
any help would be appreciated.
Click to expand...
Click to collapse
---------- Post added at 07:18 PM ---------- Previous post was at 06:57 PM ----------
Not sure if it will help you but i just went to HTC website and downloaded from there support page ICS and did a manual update. phone seems to be doing fine now
joker5656 said:
I have the same problem. how ever my bootloader was locked lol....
---------- Post added at 07:18 PM ---------- Previous post was at 06:57 PM ----------
Not sure if it will help you but i just went to HTC website and downloaded from there support page ICS and did a manual update. phone seems to be doing fine now
Click to expand...
Click to collapse
Tried this and this was the only thing that worked. Thank you for suggesting it!
joker5656 said:
I have the same problem. how ever my bootloader was locked lol....
---------- Post added at 07:18 PM ---------- Previous post was at 06:57 PM ----------
Not sure if it will help you but i just went to HTC website and downloaded from there support page ICS and did a manual update. phone seems to be doing fine now
Click to expand...
Click to collapse
you got a link wit that?
wife did same thing
Got to HTC.com go to there support page and select your phone then select the software tab on the the left and follow directions for manual update
wdkingery said:
you got a link wit that?
wife did same thing
Click to expand...
Click to collapse
a manual update will not solve the issue.
when my phone powers on, it immediately autoInitiates the update from 10.10 and proceeds to restart my phone.
after the phone has restarted, it immediately goes the hBoot screen.
i thought the problem was b/c my hBoot was unLocked, so i reLocked it.
displays as follows:
***reLocked***
***security warning***
when i hook up the USB, it recognizes its there b/c i see the following:
fastBoot USB
i've tried several things from the menu
- bootLoader > takes me to screen w/ more options
-- recovery > phone goes back to white 'HTC' ceen then goes back to bootLoader options
-- factory reset > does nothing, goes back to hBoot screen
-- clear storage > have not attempted
-- SIMLock > have not attempted
-- image CRC > have not attempted
- reBoot > reboots the phone, does the same thing
- reBoot bootLoader > ***security warning*** no longer shows, but ***reLocked*** remains
- power down > turns phone off
again any suggestions would be appreciated
i figure rooting my device may be a workAround to resolve my issue.
i've hunted for a clear, concise method for rooting my HTC vivid and the runaround these forums is someWhat painStaking. as if its some secret from the Gods. the holy arc if you would.
the vivid_all_in_one_kit looks good, however when i attempt to run vivid 2.2 my virus protection states that file is a no-no.
is there anyone that can provide a step-by-step tutorial, not missing a beat as to what i need to do?
here's what i have thus far:
i have unLocked/reLocked my bootLoader.
my screen displays:
***reLocked***
navigating away from this screen will have my phone displaying:
***reLocked***
***security warning***
the phone wont allow me to access anything but the hBoot screen freely. if i boot my phone normally, it autoInitiates the upDate and restarts my phone. doesnt update, and puts me right back at the hBoot screen.
i need assistance. step-by-step root instructions from start to finish. showing what i need to do and what i should see next.
ill settle for someone taking over my PC remotely and performing the root for me. that would be fantastic as well.
thank you.
i need assistance. step-by-step root instructions from start to finish. showing what i need to do and what i should see next.
ill settle for someone taking over my PC remotely and performing the root for me. that would be fantastic as well.
thank you.[/QUOTE]
Follow the superguide in the development forum. It is like the second or third post down, has every thing you really need to know about the vivid. Rooting, flashing, all the files you need. If i could do it...
Also, look around for the ATT RUU. it really should fix your phone and take it back to dead stock form. Also found in the superguide.
thanks for the suggestion.
i will attempt the superGuide's instructions and post my results.
problem is fixed, but phone not rooted.
attempting to complete s-Off.
is the only way to get s-Off on the htc vivid to do the wire trick? furtherMore, what type of wire is needed if its the only way?
if there's another way, please let me know.
i also want to get rid of the bloatWare on the phone. how do i go about achieving this?
Yes the wire trick is the only way. paperclip with tape wrapped around it as an insulator or pice of hook up wire from a hobby project with the ends striped back about 1/4 inch. The smaller the better. it's really easy.
You don't really need s-off for most things though. It is only used to flash kernels through recovery. you can fastboot flash the kernels with adb if you are still s-on. Its really easy too.
Remove bloatware = flash a custom rom. Holics, Dark Raider, Pegasus. they are all cool.
Read and follow the superguide. It really does tell you everything you need to know.
Fastboot for flashing kernels... Not arb
Sent from my HTC PH39100 using Tapatalk 2
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
And... For the guy who can't get past hboot...
Use fastboot to flash a new recovery like twrp... Then flash a new Rom...
Sent from my HTC PH39100 using Tapatalk 2
Right, what he said.
all this info is fantastic.
in reference to the superGuide, once i finished unlocking the bootLoader, the next step is to s-Off.
do i have to have s-Off to root the phone, if not, can i skip the s-Off step and continue from there to root device?
also, by applying the custom ROM, will i lose 'sense'? i guess it depends on the ROM i choose. i really just want a stock ROM w/o bloatWare, but w/ sense.
loominus said:
all this info is fantastic.
in reference to the superGuide, once i finished unlocking the bootLoader, the next step is to s-Off.
do i have to have s-Off to root the phone, if not, can i skip the s-Off step and continue from there to root device?
also, by applying the custom ROM, will i lose 'sense'? i guess it depends on the ROM i choose. i really just want a stock ROM w/o bloatWare, but w/ sense.
Click to expand...
Click to collapse
no you dont have to s-off. but if you dont you have to flash all kernels from fastboot.. etc. and try holics or wcx rom both are stock &&'d no bloatware
loominus said:
all this info is fantastic.
in reference to the superGuide, once i finished unlocking the bootLoader, the next step is to s-Off.
do i have to have s-Off to root the phone, if not, can i skip the s-Off step and continue from there to root device?
also, by applying the custom ROM, will i lose 'sense'? i guess it depends on the ROM i choose. i really just want a stock ROM w/o bloatWare, but w/ sense.
Click to expand...
Click to collapse
Like Slayer said, you don't HAVE to S-OFF, but for the 10 minutes it takes, it's worth it for convenience. You'll save yourself a ton of time down the road, especially if you do end up trying several roms.
Holics isn't a "stock" ROM, as it has a highly customized and optimized kernel (the best for this phone IMHO), and the ROM has been de-bloated, comes with the option of partial or full sense removal, the ability to choose from 3 different build props (basically zoning your phone for NA or EU), has LeeDroid Tweaks installed, and it comes pre-rooted with your choice of superuser app even.
WCX is the only ROM for Vivid I haven't tried. You can't find it on XDA. You must get it from the dev's forum where you must register, and somehow come up with 10 posts before you are allowed to download. If I signed up, I'd probably not make it to 4 posts before getting kicked off, as I'd likely try to start conversations about good ways to neglect house plants, or the best smelling paint job you've ever seen... YMMV.
Holics looks pretty much the same as stock without Marine's theme installed, but I personally love Marine's theme. Still full sense, just with some nice blue ICS accents.
My advice is try them all! If you're S-OFF, you can switch back and forth at your leisure. You can load your SD card up with all the ROMS, and then go have a picnic or put your bed up on cinder blocks and camp out under there for a few hours and flash away. With S-OFF done, you don't need to be near a computer for ABD or Fastboot. You can do everything from recovery. It's very handy.
first off, i wanna say thanks for all the help.
i didnt s-Off.
but i was able to put holics 1.3 official release on the device.
it works pretty well.
there are only a few minor things i dont like, so minor i dont feel the need to mention them.
for the most part i use goLauncher anyway.
i dont see me getting the ATT upDate anyMore that went out on 10.10 which was the whole reason for this thread.
again, thanks to everyOne that helped out.
loominus said:
first off, i wanna say thanks for all the help.
i didnt s-Off.
but i was able to put holics 1.3 official release on the device.
it works pretty well.
there are only a few minor things i dont like, so minor i dont feel the need to mention them.
for the most part i use goLauncher anyway.
i dont see me getting the ATT upDate anyMore that went out on 10.10 which was the whole reason for this thread.
again, thanks to everyOne that helped out.
Click to expand...
Click to collapse
Good stuff! If you're having battery issues, or random reboots, consider trying the slightly older Holics 1.2 kernel (kernel version 0730). There's a download link for it in the Holics thread, or in my signature. There's one for S-OFF and S-ON. The S-ON version is totally unmodified by myself. I just put the boot.img and the two kernel modules into a zip with instructions. If you're not having issues, and are happy, then no need to fix what ain't broken! Good luck!
Related
HTC has provided official tool to unlock Salsa bootloader, available at http://www.htcdev.com/bootloader/
Go to the website, sign up (if you havent done so), select Your device, Follow the instructions, and enjoy
Note : HBOOT update is required.
mate, let me know what is your RUU before doing the unlock. which part of download section did you take. Because mine, i got none. But i just continued to the fastboot oec, and simply send the code, and voila, its ***unlocked***
so i just wonder, why hboot updated is required since first, i dont get the update even i check it again and again, and second, it still can be unlocked without updating the firmware.
kanded said:
mate, let me know what is your RUU before doing the unlock. which part of download section did you take. Because mine, i got none. But i just continued to the fastboot oec, and simply send the code, and voila, its ***unlocked***
so i just wonder, why hboot updated is required since first, i dont get the update even i check it again and again, and second, it still can be unlocked without updating the firmware.
Click to expand...
Click to collapse
i didnt try it, i just posted the news...
but now i tried and couldnt update the hboot because i am on 1.12.720.3 and it says i need 1.12.720.5, i cant find the update anywhere.. so i just went on and tried the 'fastboot oem get_identifier_token' but i got a command error... i tried 'fastboot oem ?' but the command list didnt include 'get_identifier_token'
how did you do it?? which RUU are you on??
tried this, failed to update hboot, rom image error. basically im unable to update this hboot version.
this is the problem im having all round, i cannot update or revert from this chinese rom im using.
as for the fastboot, no point as i cannot get past stage one lol
why dont you try fastboot?? you might get lucky, kanded said he did it without updating... or is it that HTC is just bullsh**ing everyone bye saying it can be unlocked, but not providing the necessary updates for unlocking??
pachuau86 said:
why dont you try fastboot?? you might get lucky, kanded said he did it without updating... or is it that HTC is just bullsh**ing everyone bye saying it can be unlocked, but not providing the necessary updates for unlocking??
Click to expand...
Click to collapse
tried, i've actually just said, f*** it to it. stay with what we got till someone develops a way around it all.
it requires updating all round just to access the first part!
ic... so whats with kanded ?? how did he do it??? Seems i have to wait some more as i cant get my hands on a clip either.... bummer
pachuau86 said:
ic... so whats with kanded ?? how did he do it??? Seems i have to wait some more as i cant get my hands on a clip either.... bummer
Click to expand...
Click to collapse
don't know,
i do know u have to have all sdk parts installed as im unsure what it needs to run with, that took 2 hrs getting it all.
ive tried again, even skipping to fastboot, still nothing.
but ive already tampered with mine, already has cwm installed, s-off and rooted, with chinese uk o2 rom installed......so i wonder if he's using standard issue rom from scratch, but either way, it may not work on all salsa handsets.
but keep trying if you want. the option to send it us is still there!
man, i want to clarify.
the first time i bought this salsa, it is hTC Asia WWE, with S-ON of course.
there is no English language. fu** with it, so i tried to change into RUU O2 UK, by making my sdcard as a goldcard, and put the RUU files onto it.
Here i tell you the way, the RUU files is exe, right ? You can directly flash it as long as you got goldcard (its not hard to make it, everybody knows that)
Or, if that fail, there is still a way updating the stock rom with RUU. Install the exe, while its popping up in ur windows, open task manager, and you see RUU instalshield wizard is running, right ? now go to process, and see Aruwizard.exe
properties that aruwizard.exe, and open file location. you will see there is a zip "rom.zim"
rename that rom zip into PH11IMG.zip and put it into your sdcard that has been as a goldcard. now do the hboot, it will do the recovery itself. let me know if it works.
after that, go to htcdev, and then next step, no need to download for upgrading, bla bla bla, i got my bin_unlock by emails twice. hahaha.
get helped ? say thanks
---------- Post added at 07:18 AM ---------- Previous post was at 07:08 AM ----------
its for you bigbear, i read in any thread that you got problem with your rom right now, that you wanna go back to your stock from that chinese one rom, confirm me if im right.
you may try the way i've said above.
you know of course i also flash that custom rom you post, but i can get back to my before rom.
this is that we must be carefull. if you wanna get back to the last rom you have, you gotta do backup via recovery. there is a backup and restore section. do the backup, and save your backup (it is in clockwordmod folder) in the safest place.
lets say you wanna get back, just do the restore, and voila, you are in your home sweet home. no problemo at all altough you got big headache because of flashing the wrong rom
this is the way :
1) Format SD card as Fat32
2) Install HTC Sync Drivers. (available at htc.com)
3)Connect Your phone to PC. USB Debugging must on and usb connection type: Only Charging.)
4) Open SimpleGoldCard Tool as a admin
and follow procedure step by step at SimpleGoldcard tool.
works now, thanks to kanded and 0x.shivam.x0
BigBearEvo said:
tried this, failed to update hboot, rom image error. basically im unable to update this hboot version.
this is the problem im having all round, i cannot update or revert from this chinese rom im using.
as for the fastboot, no point as i cannot get past stage one lol
Click to expand...
Click to collapse
How did you get a custom rom running on your phone? I can't root my phone because I don't have access to the clip. Is there any other method?
By going to htcdev and getting my bootloader unlocked. From there its plain sailing
Sent from a 3.5 Sensed Salsa
Yeah i know how to do that. Got my incredible s rooted juwt like that. Rather i installed cm7 and then it got rooted. Do you have any link on hiw to proceed after unlocking the boot loader? Oh and could i have a list of roms for the salsa? Thanks in advance.
XDA FTW
jhon101 said:
Yeah i know how to do that. Got my incredible s rooted juwt like that. Rather i installed cm7 and then it got rooted. Do you have any link on hiw to proceed after unlocking the boot loader? Oh and could i have a list of roms for the salsa? Thanks in advance.
XDA FTW
Click to expand...
Click to collapse
www.wix.com/bigbearevo/salsa everything i know of is there
BigBearEvo said:
www.wix.com/bigbearevo/salsa everything i know of is there
Click to expand...
Click to collapse
Alright thanks man. Appreciated. And good stuff with the site. Lastly, would you happen to know what language should i learn to write a kernel and for a rom?
And yes i pressed the thanks button
To learn kernels and Roms its best to use Ubuntu Linux. And I found finding a Dev that could teach u what u need, I'm still learning but my Ubuntu is offline so I've not progressed any further yet.
Sent from a 3.5 Sensed Salsa
Tried it and its working fine. Thanks to BigBearEvo's site. i could easily flash a 3.5 rom
This is an update on a previous post, this time however you don't have to sieve through Chinese websites to get them....i have spent time to get them for you!
This Will revert your HTC Salsa to Stock
By using these you will wipe everything you have done. Recovery will be wiped, unknown about lock/unlocked boot-loader as i haven't attempted this with unlocked boot-loader before as.i had s-off at the time.
You do this at your own risk, i take no responsibility at all for anything that may or may not happen lol
Instructions for use.
HTC SYNC installed but not running, you want the cable driver mainly.
Instead of following on screen instruction via the RUU, set your phone into fastboot mode yourself then activate/run the RUU.exe you require, i would suggest run as administrator (right click on application)
This will take some time to install, i did it on 3rd attempt, first 2 were relying on the RUU to boot the phone for me...3rd i booted into fastboot/bootloader myself and away it went.
if for any reason it doesn't respond to you or it doesn't install stock or freezes, whip out the battery and do it all again!
Below are the RUU's please find the correct region your in and download accordingly. EU RUU is a common one if the others don't work. all roms are based of this version.
RUU_Icon_G_HTCCN_CHS_1.24.1400.4_Radio_47.14.35.3030H_7.47.35.17_release_204455_signed.exe
RUU_Icon_G_HTC_Europe_1.12.401.1_R_Radio_47.14.35.3030H_7.47.35.17_release_193257_signed.exe
RUU_Icon_G_O2_UK_1.18.206.2_Radio_47.14.35.3030H_7.47.35.17_release_198160_signed.exe
RUU_Icon_G_hTC_Asia_HK_1.16.708.3_Radio_47.14.35.3030H_7.47.35.17_release_197702_signed.exe
RUU_Icon_G_hTC_Asia_India_1.12.720.2_Radio_47.14.35.3030H_7.47.35.17_release_193467_signed.exe
RUU_Icon_G_HTC_TUR_1.18.468.2_Radio_47.14.35.3030H_7.47.35.17_release_199341_signed.exe
RUU_Icon_G_Hutch_AUS_1.18.861.1_Radio_47.14.35.3030H_7.47.35.17_release_197619_signed.exe
RUU_Icon_G_Voda-Hutch_AU_1.17.862.2_Radio_47.14.35.3030H_7.47.35.17_release_198433_signed.exe
RUU_Icon_G_Chunghwa_1.13.751.1_Radio_47.14.35.3030H_7.47.35.17_release_193940_signed.exe
RUU_Icon_G_hTC_Asia_WWE_1.12.707.2_Radio_47.14.35.3030H_7.47.35.17_release_193464_signed.exe
as the link in the lower post suggested you can also try this
*this wasn't provided by me please don't blame me if anything goes wrong*
1. Download your RUU
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.
Well it seems a lot of you shadows hiding away wanted these lol, as the downloads in 1 day surprised me lol.
BigBear is using Xparent Tapatalk Purple
I managed to revert back to stock using this method http://forum.xda-developers.com/showthread.php?t=1631121
Now I am running 2.3.3
Now i just want to update to 2.3.5 if possible, haven't been able to get OTA updates. Do you know how i can go about it?
CWM recovery is still intact.
Thanks
The salsa will never have 2.3.5 ota. HTC stopped at 2.3.3 and discontinued updates for us. well the stopped producing the salsa and totally dropped it.
that's why we have 2.3.5 roms that are not meant for us...ie no FB button that works correctly, no mirror or front facing camera.
and this is probably why noone is still running stock roms anymore
BigBear is using Xparent Tapatalk Purple
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Now I have relocked the bootloader and tried the Europe Salsa RUU.... It is giving me Error 140 now claiming the bootloader version is invalid.
HBOOT is updated and I notice that the Radio version mentioned on Fastboot Bootloader screen is different than mentioned in the RUU.
Mine says:
*** Relocked ***
ICON_G PVT SHIP S-ON RL
HBOOT-1.08.0000
MICROP-0558
RADIO-7.51.35.19
Dec 16 2011,16:12:07
razasohail said:
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Click to expand...
Click to collapse
Did you take a nandroid backup in recovery at all?, if so restore it.if recovery isn't there reinstall recovery and restore your backup.
BigBear is using Xparent Tapatalk Purple
Get the phone to Stock
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
arekapudi said:
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
Click to expand...
Click to collapse
this guide wasn't provided by me, i do know what this means but its hard to explain to a newbie...
for the more technical side of go here >http://forum.xda-developers.com/showthread.php?t=1631121, it may help you...
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Saturn007 said:
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Click to expand...
Click to collapse
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
BigBearEvo said:
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
Click to expand...
Click to collapse
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Saturn007 said:
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Click to expand...
Click to collapse
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
BigBearEvo said:
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
Click to expand...
Click to collapse
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
gagan313 said:
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
Click to expand...
Click to collapse
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
BigBearEvo said:
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
Click to expand...
Click to collapse
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
gagan313 said:
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
Click to expand...
Click to collapse
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
BigBearEvo said:
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
Click to expand...
Click to collapse
thats just the thing you see....
for some reason, if i try the stock.zip i always have wifi issues as well as facebook issues and well... i have tried all the facebooks from 1.9.9 to the black one and it dosnt seem to sign in... evern after i have unin installed and moved to sd card using links2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
gagan313 said:
that's just the thing you see....
for some reason, if i try the stock.zip i always have WiFi issues as well as Facebook issues and well... i have tried all the Facebook from 1.9.9 to the black one and it doesn't seem to sign in... even after i have uninstalled and moved to sdcard using link2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
Click to expand...
Click to collapse
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
BigBearEvo said:
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
Click to expand...
Click to collapse
ok ill give it a shot
Hey xda, im a but of a noob, so sorry if i did anythign stupid. Ok so a while back, I had rooted my HTC Incredible S and he phone was a
beast for me. It was fast no lag what so ever, the mods were sick and The kernel I had allowed me to orverclock. I was so happy! Until one day my USB port broke and I
wasnt able to charge the phone or connect it to my pc. So i had to find a way to unroot it so that I could bring it to my carrier and they will fix it, I was still under warranty.
So i Tired and tried and i was not able to fix it and then someone told me to use the TEMP UNROOT method im superuser and see what happens. I did so but I was still
S-OFF and could see so in the boatloader screen I believe its called. So I took it to a technician who fixed it for 20$, I was pretty happy because my phone was now working.
Now i found a way to unroot it, I had to download the stock carrier rom wich was Android 2.3, i had to download it, rename it to PGM32.zip or something like that and put it
on my SD CARD and there you go, my phone was back to stock. Now the problem is, I still have S-OFF. I cant even LOAD UP IN THE SCREE NWHERE YOU FLASH ROMS! I forgot the name of it , you guys should know what im talking about!
SO I came to XDA for help and someone said to me that i have to go back into the superuser settings and uncheck. Now when i go in the
settings, the box is not checked and i cannot check!
When I click on it, it doesnt do anything!
And whatever root app i use, It doesnt work it says there is no root access and also , Superuser keeps saying outdated binary file and i cant fix the problem -_-
Someone please help, I want to root it back because the phone works and Stock is very laggy! I want to flash roms like before and have a powerful phone! This thing sucks like this, someone please help, I will do anything!:crying:
Flash the recovery
GuyananV said:
Hey xda, im a but of a noob, so sorry if i did anythign stupid. Ok so a while back, I had rooted my HTC Incredible S and he phone was a
beast for me. It was fast no lag what so ever, the mods were sick and The kernel I had allowed me to orverclock. I was so happy! Until one day my USB port broke and I
wasnt able to charge the phone or connect it to my pc. So i had to find a way to unroot it so that I could bring it to my carrier and they will fix it, I was still under warranty.
So i Tired and tried and i was not able to fix it and then someone told me to use the TEMP UNROOT method im superuser and see what happens. I did so but I was still
S-OFF and could see so in the boatloader screen I believe its called. So I took it to a technician who fixed it for 20$, I was pretty happy because my phone was now working.
Now i found a way to unroot it, I had to download the stock carrier rom wich was Android 2.3, i had to download it, rename it to PGM32.zip or something like that and put it
on my SD CARD and there you go, my phone was back to stock. Now the problem is, I still have S-OFF. I cant even LOAD UP IN THE SCREE NWHERE YOU FLASH ROMS! I forgot the name of it , you guys should know what im talking about!
SO I came to XDA for help and someone said to me that i have to go back into the superuser settings and uncheck. Now when i go in the
settings, the box is not checked and i cannot check!
When I click on it, it doesnt do anything!
And whatever root app i use, It doesnt work it says there is no root access and also , Superuser keeps saying outdated binary file and i cant fix the problem -_-
Someone please help, I want to root it back because the phone works and Stock is very laggy! I want to flash roms like before and have a powerful phone! This thing sucks like this, someone please help, I will do anything!:crying:
Click to expand...
Click to collapse
You may need flash the recovery first.
---------- Post added at 03:31 PM ---------- Previous post was at 03:21 PM ----------
And take this as the reference:-
http://forum.xda-developers.com/showthread.php?t=2118187
You could try to reflash the superuser zip, worked for me
Sent from my HTC Incredible S using xda premium
Gizmo648 said:
You could try to reflash the superuser zip, worked for me
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
As another poster told you, you will first have to flash a custom recovery and then you will be able to flash either SuperSU to gain root on your current ROM or flash a new custom ROM.
iSeanzh said:
You may need flash the recovery first.
---------- Post added at 03:31 PM ---------- Previous post was at 03:21 PM ----------
And take this as the reference:-
http://forum.xda-developers.com/showthread.php?t=2118187
Click to expand...
Click to collapse
Ok just one question before doing this, im a noob lol
My HBOOT is 6.13.1002
can i still use this method?
Because the screen says revolutionary in pink, it says s-off and all that
but when i click recovery i get this picture of a phone and a red triangle and inside is a red exclamation point
thats why I came to you guys for help because I cant flash anything
so I am going to follow the thread you gave me but I just want to make sure I can follow the instructions even though my HBOOT is 6.13.1002
thank!
GuyananV said:
Ok just one question before doing this, im a noob lol
My HBOOT is 6.13.1002
can i still use this method?
Because the screen says revolutionary in pink, it says s-off and all that
but when i click recovery i get this picture of a phone and a red triangle and inside is a red exclamation point
thats why I came to you guys for help because I cant flash anything
so I am going to follow the thread you gave me but I just want to make sure I can follow the instructions even though my HBOOT is 6.13.1002
thank!
Click to expand...
Click to collapse
You need to reboot the phone to the HBOOT/bootloader screen and then put the phone in FASTBOOT USB mode.
From there you will be able to open a command window and type the following command:
fastboot flash recovery [name of recovery.img]
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
stanny2k said:
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
Click to expand...
Click to collapse
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
nkk71 said:
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
Click to expand...
Click to collapse
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
stanny2k said:
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
Click to expand...
Click to collapse
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
nkk71 said:
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
Click to expand...
Click to collapse
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
stanny2k said:
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
Click to expand...
Click to collapse
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
stanny2k said:
Oh, and have a "thanks"
Click to expand...
Click to collapse
Thanks, I like those
nkk71 said:
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Click to expand...
Click to collapse
Ok, I'll grab this!
nkk71 said:
Also, please follow the instruction properly, no jumping, skipping or adding steps
Click to expand...
Click to collapse
Will do! Don't worry, word for word!
nkk71 said:
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
Click to expand...
Click to collapse
Noted.
nkk71 said:
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
Click to expand...
Click to collapse
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
nkk71 said:
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
Click to expand...
Click to collapse
Appreciate it, thank you
stanny2k said:
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
Click to expand...
Click to collapse
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense
Perfect sense!
I'll have a bash at this tonight! Thanks a lot
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
stanny2k said:
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Click to expand...
Click to collapse
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
nkk71 said:
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
Click to expand...
Click to collapse
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
nkk71 said:
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
Click to expand...
Click to collapse
Yup, I did fastboot erase cache before and after flashing it, both were successful as well. I didnt check the MD5, I just installed it after I downloaded it.. it was midnight by the time I got that far! I was tired!
Yeah and thanks a lot for your help mate. Really appreciate it.
I'll let you know the outcome with HTC Hopefully they find nothing untoward!
stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
nkk71 said:
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
Click to expand...
Click to collapse
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
stanny2k said:
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
Click to expand...
Click to collapse
finger gymnastics :laugh:
stanny2k said:
Well, that was an eventful evening
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
Click to expand...
Click to collapse
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
nkk71 said:
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
Click to expand...
Click to collapse
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
stanny2k said:
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
Click to expand...
Click to collapse
problem is with the CWM i recommended, works just fine when flashed, but when using "fastboot boot CWM.img" looks like 6.0.3.2 doesnt work properly with adb, 6.0.4.5 on the other hand works with "fastboot boot"
I'll update my guide with some more "visuals" whenever I get a chance....
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!
Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Ok so Tuesday night I was going to bed (phone still on and working) and plugged my phone in to the charger to charge for the night as I usually do every night. Wake up in the morning and hit the power button to unlock the phone and to my surprise the display doesn't come on. As I said I've never dropped this phone in the entire 9 months I've had it, nor has it ever gotten wet.
This is NOT the first time this has happened either. I've had the phone display flicker on/off and after a couple times it will just stay on. It's also went off and I've fixed it by holding a light to the sensor in the top left and it came on. This time I'm not having any luck.
Please help! It's rooted, with custom ROM, and boot unlocked, therefore I cannot send it in for repair as warranty is voided. I've tried restoring it back to stock the best I can via mirror Android to PC program, but it's very difficult. I've restored it once before, I just don't get why it's not working again with me holding the light to the sensor. Any help and/or suggestions would be greatly aprreciated!! Thank you!
Click to expand...
Click to collapse
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.
Kev_McCall said:
Ok so before I begin, I've read everything online and cannot figure this out. I've searched the forums for hours and still no luck.
I have the HTC One M7 with T-Mobile
I've had it since December with no issues at all, and still in mint condition. Never dropped.
I have it rooted, with boot unlocked
ViperOne ROM Installed, stock kernel.
Click to expand...
Click to collapse
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.
zelendel said:
Well issues like this are common with custom roms. You would need to pull a log cat or DSM message and send it to the developers.
Click to expand...
Click to collapse
Thanks for the reply, so how would I go about pulling log cat and DSM?
majmoz said:
If you are not S-OFF, then you will have to relock your bootloader with this command: fastboot oem lock
Then run this RUU 5.14.531.11 That will put you back at stock and if you want to put a custom rom or root you can try it again.
Click to expand...
Click to collapse
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? Is it not possible to flash RUU with S-On? Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.
Kev_McCall said:
Thanks man! I've tried other RUU's with no luck. So just to be certain, in order to flash an RUU, you need S-Off wit Bootloader locked? No, if you S-OFF you can leave it unlocked.
Is it not possible to flash RUU with S-On? No, if S-ON you can only flash it if your bootloader is locked and the same OS version or higher.
Going to do this now. I'll let you know. I'll keep you guys updated. Feeling good about this.
Click to expand...
Click to collapse
See comments above.
majmoz said:
See comments above.
Click to expand...
Click to collapse
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz
Kev_McCall said:
Ok so I succesfully Installed the RUU and back to stock rom, but upon rebooting, my screen did not turn back on. I've read of dozens of other users who have experienced this same thing. I guess the next step would be to fully return it to stock, turning S-On, removing tampered, unrooting, etc, and just returning it for another phone. @majmoz
Click to expand...
Click to collapse
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.
majmoz said:
If you successfully ran the RUU, then you are stock with a relocked bootloader. The downside is you have to be S-OFF to remove the tampered and to change the "relocked" to "locked".
If you are S-OFF, then you would have to put TWRP 2.6.3.3 or 2.7.1.2 and install this Bootloader Reset Tool. Then flash a stock recovery. You are now completely back to stock.
Click to expand...
Click to collapse
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz
Kev_McCall said:
Yea. I turned S-Off before I even ran the RUU. So there's one thing I'm confused about. If I'm trying to return to complete stock state, why would I install Twrp or CWM if those don't come with it? Is there any other way to do this? As I have no back-light and it's been very hard to do all that I've done so far. Screen hasn't come on, so I'm working blind here. Lucky for me I remember where most of the buttons are at and with the help of ADB, I've gotten this far. @majmoz
Click to expand...
Click to collapse
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.
majmoz said:
Yes, look at nkk71 guide in my signature he has the steps in post 3 or 4. I'm away from the house so I can't post the link.
Click to expand...
Click to collapse
@majmoz
Hey bro thank you so much for the help so far, I really appreciate it. I just have one last problem. I've already talked with HTC and they're going to be sending me a replacement and I have to send my phone back in within 10 days but they said they would be checking for root.
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.
Kev_McCall said:
@majmoz
So question 1. When you restore phone to stock ROM via RUU it unroots the phone correct?
Second problem. Now that I've restored the stock rom, usb debugging isn't enabled and I can re-enable it due to not being able to see the screen. So because USB Debugging is not enabled ADB is no longer recognizing it when I run "adb devices"
Because of this I can't turn bootloader, tampered, and lock stats back on. I'm really nervous sending my phone back in like this. I hate to keep bothering you, but you seem to know your stuff a lot more than I, and I'd hate to start a new thread. Thanks again bro.
Click to expand...
Click to collapse
1. RUU unroots the phone.
2. Yes, you need USB Debugging enabled and a custom recovery (nkk71 uses CWM).
I have been racking my brain all night. This is a long shot, but if HTC is sending you a replacement before you have to ship yours back then here is an idea. With the replacement phone side by side; memic the commands to open Settings on both phones doing the replacement phone first, then the old phone. The location of the items should be in the same place on both screens. It may take a couple of tries but you seem adapt at reading blank screens. I'm still researching a way to turn it on remotely, but this is the only solution I could come up with presently.
When you get USB Debugging enabled, use nkk71's guide to install CWM on your phone. Then complete the manual steps to remove "Tampered" and to "Locked" the phone. Reboot the phone into bootloader per the instructions. Now we need to put the stock recovery back on the phone. You can get the stock recovery out of the last OTA. Download it to your PC, then open the zip file. Within the zip is the firmware.zip, open it and you will see recovery.img file this is the stock recovery. Just extract it and flash it like you did the custom recovery earlier. Going back to nkk71's guide, complete the fastboot command to return to S-ON. Now you are completely stock with no hint of root.
@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.
Kev_McCall said:
@majmoz
I'm beast! lol Ok so quick update to my problem. So I got the bright idea to use the Power+Volume Down to take screenshots of my display as I blindly tapped and used that as a guide and moved forward to unlocking developer options, then enabling USB debugging. I can now see my device in ADB once again. Should be pretty cake from here. Thank you so much bro! And also, HTC has agreed to send me a new phone, but I must first send mine in. They would have sent me one first and then I send mine in later, but they wanted to place a $600 credit hold on my card. **** THAT. The rep told me they would be checking for other damages as well as if it rooted.
Click to expand...
Click to collapse
You are a genius!!! I will have to remember that if this type of situation arises again.
@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.
Kev_McCall said:
@majmoz
Ok so I've been reading those sites and I know I'm so close to being back to 100% stock, but now I'm stuck. I'm confused as to what order to things.
I restore stock recovery, then lock bootloader, turn S-ON,and remove tampered and return to Locked status?
Here are my fastboot getvar details. Just trying to get this done as soon as possible as I'm also in the process of moving and wont have net here much longer. So as soon as I get this done I can send my phone back in and get the replacement. Really hate being without a phone.
Click to expand...
Click to collapse
Here I put them in your new post.
Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.
Kev_McCall said:
Alright cool thanks! I really shouldn't have created a new thread, but I wasn't sure if you would be on for much longer. Reading it now.
Click to expand...
Click to collapse
it doesn't take 5 threads to fix one problem does it ?
clsA said:
it doesn't take 5 threads to fix one problem does it ?
Click to expand...
Click to collapse
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.
Kev_McCall said:
Probably not, you're right. But when other people don't respond to my initial thread it's kind of hard. I'm still stuck And just trying to get this finished up. Would you care to help? It's not much.
Click to expand...
Click to collapse
we all have other lives besides XDA .. you have to be patient
I have a few min where are you now in the recovery process ?