Sorry for long post but I've tried to provide a sufficient level of detail. If the answer is in another thread let me know. I've read quite a few of them now!
I've had my flyer for a short time and was loving it until I tried to mod it.
I installed CWM and Superuser root and had it "S-Off". I tried to flash the Leedroid HC rom. It seemed to be dead on re-boot just the HTC screen. I did a restore from CWM and got Gingerbread back. Some apps like default browser did not work though.
Now I had a mostly working system I followed the O'brian (think' that correct name) including using official HTC unlocker as was in instructions. Tried to use another HC rom and the ARU wizard. I got an error 155 and an RUU failure msg on device. Not sure what to do know. I have download this file "Best RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed". Nothing much happens when I run it other than seeing the install screen, then it exits. I really need some help to get back to some kind of working system.
Been through thread "[GUIDE][Flyer+View]Gingerbread S-
OFF/Recovery/Permaroot"
Can't follow post 17 to get S-Off as device will not boot into android!
From CWM Backup, the external SD card I used seem to have got corrupted. This could have been root of problems
data.img - file error
cache.img - file error
nandroid.md5 - file error
Boot.img, recovery.img and system.img files seem ok...
Got this msg from "revolutionary.exe" when tried to get -"S-Off" again.
Found your device: /sbin/sh: getprop: not found (/sbin/sh: getprop: not-/sbin/sh
: getprop: not, Android: /sbin/sh: getprop: not, ROM version: /sbin/sh
Your device: /sbin/sh: getprop: not, with HBOOT /sbin/sh: getprop: not is
not supported at this time.
Here are my device details:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0011
INFOversion-baseband: 3822.10.08.07_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 2.23.405.4
INFOserialno: HT15WT403213
INFOimei: xxxxxxxxxxxxxxxx
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__054
INFObattery-status: good
INFObattery-voltage: 4143mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: f0e1145e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have hboot 1.11.0011 with CWM and access via ADB
Your help appreciated, at end of my tether!
allot to take in but best I could tell you were on gingerbread and maybe tried to flash Lee Droid HC version so that would not work. So then you followed an old thread to update to HC using Paul Obrien's method whcih requires HTC Dev unlock of the boot loader. At this point in time you can not flash any roms via recovery and your system will not boot into android.
Please confirm if I am following what happened to you and if while in your hboot screen it says Unlock up top.
Thanks for replying.
In summary that's correct.
If I hold down the vol-down button I get the screen that says:
"*** UNLOCKED ***"
"flyer PVT SHIP S-ON RL
HBOOT-1.11.0011
Micro P-0950
Radio 3822.10.08.07_M
eMMc-Boot
I still have USB access to it via fastboot I think
ok so here we go
no hc rom will just directly flash and boot because you can not overwrite the boot.img via recovery with HTC dev unlock. If you wanted to flash say Leedroid you would have to pull the boot.img from the rom package then fastboot flash it first then back to recovery and flash the rom. This is a hacky way to do it and to be honest every time you flashed a rom you would have to do the same. Here is what I suggest:
follow this thread here to downgrade
http://forum.xda-developers.com/showthread.php?t=1307759
you may likely be able to skip the misc version part. Hopefully you are aware of what your stock ruu is. If you tried running it before and it failed it was because you did not relock the boot loader prior to trying as is described in the thread I linked
Once, hopefully, you are back on GB, I would run this method to get to HC
http://forum.xda-developers.com/showthread.php?t=1358758
now, if you flashed a hc rom on your device and it will not boot, just as mentioned flash the boot.img via fastboot from the rom and it should boot. This is if you are looking for the easy fix, and assuming I understand everythign you have done to this point
I have downloaded this file to use as my stock RUU
"RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_relea
se_204108_signed.exe".
I will go through steps 1 to 8 of the thread and the rest if I can. I am not sure about step 8, it says boot to android. Are you saving if I managed to get that far I will have some kind of working system back before I proceed further?
I will have a go now and let you know how I get get long.
Cheers!
as I stated you may not need to do the misc version part. and you do not need to flash recovery and su if you already have both
I followed the steps and apllied the HTC unlocker again, then flashed the recover.img with no error messages and put the Super User zip on my external SD card. I used the CWM install from zip option, seemed to proceed, no errors reported. When I re-booted the tablet I just have an empty black screen and nothing else. Should I proceed with the RUU or stop and try something else?? If I turn it off it immediately comes back on again to blank screen. The only way to keep it turned off is to use the power down option on hboot menu.
you were unlocked
you already had recovery
you already had super user
you did not have to repeat any of these steps
if you can get into hboot then follow the instructions to revert assuming you have the three things mentioned above. You can likely skip the misc-version step. If you get a message while flashing the ruu that states older version you will have to do the misc-version step which since you can not boot into android can be done in recovery as adb will see your device in recovery
I do not really think you are in too bad of a way right now, but without meaning to offend you, you scare me with not paying attention to what is being said. One concern I have is to make sure you have enough battery life left. If you hit less than 30% you will not be able to run the RUU. If you are confident that you have that much continue. If not power down through fastboot and charge for a couple of hours.
Please read, read, read, and do nothing unless you are atleast 50% confident that you understand
Hi
I really appreciate the help you are giving me. The only did all the steps just in case as I am paranoid about missing something important. I do think I have enough battery so I will see if I can use the RUU I downloaded
Thanks
I am now running the RUU, it says "updating rom image". It is showing a black screen with the letters HTC in white in the middle. I hope this works.
Thanks for your help.
Comment has been edited, sorry for silly question, answered in thread you mentioned
that is normal
My god, I am so relieved. To tired to be estatic. It's taken me 24 hours and only two hours sleeps to get back to Stock! You save my bacon Mcord! The battery after flashing was nearly 100%. Thankfully I kept it charging even though it was bricked in an attempt to increase the rescue time I had. The only downside is I missed a ski class I'd paid for and having to pay the "Filefactory" company for a subscription so I could reliably download the RUU.
I've learnt the hard way for sure. Anybody else reading this don't assume that just reading the instructions is enough. My SD Card had corrupt backup recovery files on it. How often do we double-check the integrity of our backups? the SD card may have also mean that the rom loaded onto it was corrupt as well. I should have checked the MD5 of all the files.
Thanks again!! I think I'll pause a bit before Honeycomb and def backup!
happy your back up and running. your problem was just not fully understanding the differences between GB and HC and S off and HTC Dev unlock. the thread I linked you is the one to use going forward if moving to HC and looking to run custom roms. As I mentioned before read, read, read.
What if in addition adb don't work ?
Hello,
I tried to downgrade, but the adb command don't work : device not found response...
So I connot follow the process explained http://forum.xda-developers.com/showthread.php?t=1307759
Second the CWN is broken too... Is that a problem ?
Thanks
Related
Greetings!
I've inherited a EVO 3D that has issues. I'm new at this, but had 3 other old HTCs. I read a lot that i could for the last 12 hours in various forums and made a few mistakes/discoveries. I tried a few but i think i am stuck and i couldnt see anything else that can help so here i am. groveling for help. My first post too!
The 3D when turned on shows the HTC with white background splash screen for maybe 30-45 secs and blanks out. then reboots again ad nauseaum. In short, the phone cant boot to Android.
when plugged into the usb, seems to heat up under the camera area but not the battery, it actually drained the battery (or so i think ) because i was able to boot it before, and after i left it plugged in for an hour, it was hot and will not charge (red light blinks) i found out later voltage was below 3.0v used my old raphael to charge the batt (that works) so i can continue working on the 3D.
- i found the hboot power+vol down and was able to get into fastboot usb.
- was able to unlock using htc method
- tried loading cwm 4.0.1.4 - says success but wont enter recovery mode - just same splash screen
- tried loading cwm 5 (latest) says success but wont enter recovery mode - same as above
- found out about the RUU method. flashed back stock recovery and locked again and using the PC86IMG.zip method in hboot and a sd card. new 2.08.651.3 stock RUU was loaded successfully. but alas, still stuck in reboot/splash page.
edit: i noticed it "bypassed" one of the TP. not sure what that meant. when i was installing the stock RUU.
i dont know about the S-on or off, cant see it from hboot. can i?
i dont know if this has been rooted but the previous owner said no. it was still locked until i unlocked it.
so now, when i try recovery or factory reset, it immediately reboots and show splash screen only ad nauseaum. ( i waited as much as 5 reboots )
Help please? let me know if u have any questions.
Thank You!
CK
U should use the latest cwm not the touch one.an push it via fastboot read up on it on website below
www.rootofallevo.com
Sent from my PG86100 using XDA App
Go get flash image gui from the market. Put your recovery of choice on your SD card and flash it via flash image gui. Hboot 1.5 recovery partition is marked as "read only" hence the s-on, which can be seen in bootloader. The way around it is to fastboot into your device and flash zips that way or flash kernels and recoveries via flash image gui app.
Thanks Jwolf1,
I did try both CWM 4 and latest CWM 5 that is 3D specific. but it just reboots immediately and cycles over and over again and wont go into recovery. But! I may be missing a step or two. I havent found a post yet or a faq where there are more detailed steps to do this. maybe you can point me to one thats EVO 3D specific?
I tried the link but unfortunately, all it shows is the domain name is for sale.
CK
Thanks Jabawockee,
would i be able to use Flash image gui even if i cant get get the phone to boot aside from getting into hboot? if its possible, please let me know where i can find the instructions so i can read up.
CK
Oops that was on my part wrong link here's the right onewww.therootofallevo.com
Sent from my PG86100 using XDA App
Thanks jwolf1
I went to the site but i dont see anything that could help my case.
do you have other suggestions?
it seems that everyone expects recovery to fire up after a fastboot boot or a pc836img.zip boot from sdcard. i just cant seem to get to that page
I was observing that everytime i run a fastboot flash recovery something, i see it being loaded, but i dont see it being "written" (the progress bar on the right hand side is just a blip. no color) but when i try a recovery.img that is with the stock rom i have. i do see color in the progress bar when writing. not sure if that means anything.
I'm trying to find out if i can wipe cache and dalvik without going into recovery (since i cant boot the phone properly) but so far, all indications is ... no.
also, is there a way to peek inside the phone to see if the partitions are corrupted?
Thank You.
Ck
Is ur phone unlocked becuase if not this could be a problem if its locked
Sent from my PG86100 using XDA App
OP: You have my big thanks for trying to find an answer by yourself BEFORE you ask for it. A simple rule that n00bs are constantly failing to comprehend.
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk
Hi Jwolf1,
yes, I unlocked my phone with the HTC method.
CK
Thanks Terepan,
still hoping to figure this out...
CK
new info...
I think i may have found the issue...
while trying over and over again, i notice i wasnt getting consistent responses to a certain command. in particular,
fastboot getvar all
on most cases, i get the following response on the cmd line
getvar:all FAILED (Status read failed (Too many links))
but once in a while i get
(bootloader) version : 0.5
(bootloader) version-bootloader: 1.50.0000
(bootloader) version-baseband: 0.97.10.0808
.
.
.
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
So i think the problem is, when i try writing to recovery, the message may say OKAY. but i am not sure that its being written in.
when i try a "fastboot erase recovery"
i always get "FAILED (Status read failed (Too many links)) "
another problem could be that the boot-mode is FASTBOOT
Is this the same as the one that we are suppose to turn off in the settings?
if yes, since i cant get in the phone settings. how do i turn it off?
if no, then it doesnt matter?
and is the security: on an issue? maybe why i cant erase recovery or load recovery ? i do noticed a difference in the screen on the phone when i load a "signed" recovery vs CWM and TWRP.
Anyone? help?
Thanks.
CK
Is it correct to.say you have a Sprint Cdma 651.3 hboot 1.50 based Evo3D?
When u enter hboot/bootloader you should see either "s-on" or "s-off" near the top and either "locked, unlocked, or relocked".
I had a problem with that Ruu.zip file Mr.Esp posted, maybe a bad download. Find another link (i did) or.run the 651.5 based Ruu for the updated radio (i did).
Note: you have to relock before running the Ruu.
See this:
http://forum.sdx-developers.com/index.php?topic=18852.0
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12)
I don't know if.it will help you or not but I had some issues getting certain recovery files loaded & booting to them afterwards to flash files from. I have the details & step by step scenarios of what I did that may help if you are overlooking a step. See the ROM/recovery issues thread in my signature.
Here (posts 1 & 10th ) :
http://forum.xda-developers.com/showthread.php?t=1450466
[Solved]Hboot 1.5 Rom/Recovery install issues (fastboot/FlashimageGui/RomMgr) 2-4-12
It sounds like the kernel/boot.img may not be correctly loaded after a ROM flash, but I'm not sure.
Sent from my "up all night, sleep all day" Evo3D!
mpgrimm2,
Thanks for the help! Thanks for inspiration!
i ended up inadvertantly fixing the damn thing. it was a hardware issue but i dont know which one.
I got fed up of 4-5 nights of not sleeping and got myself another "broken" evo 3d.
It had a broken digitizer so i was going to perform the swap. as i disassembled the first 3vo. i had the mainboard out and i figure, why not test it? hooked it up to the usb and hand held a batter and lo and behold i saw "normal" recognition pattern by the pc!
I slowly assembled it again, testing it at each and every connection to see if everything is still the same or maybe some other component may be causing the issue, and i finally have a whole 3vo working! booting! now i can even fastboot boot cwm ! damn! no more boot loops!
i am not sure if its was me pressing on the mainboard and maybe a chip got a connection back or maybe just one of the cable has a loose connection but now its fully functional again. (i'm thinking more of the former than the latter)
reason why is because of the heating issue it has. i wont be surprised if the issue comes back or if others has the same issues.
so for others with the same symptoms, try disassembling it and pressing down on the part where it heats up. one of those with the heat shields (using only finger and thumb!) good luck!
CK
My evo 3d is exactly the same problem. I have disassembled and reassembled it, also pressed down the part with heat shields, but no lucky to me:-(
xdapyro said:
I think i may have found the issue...
while trying over and over again, i notice i wasnt getting consistent responses to a certain command. in particular,
fastboot getvar all
on most cases, i get the following response on the cmd line
getvar:all FAILED (Status read failed (Too many links))
but once in a while i get
(bootloader) version : 0.5
(bootloader) version-bootloader: 1.50.0000
(bootloader) version-baseband: 0.97.10.0808
.
.
.
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
So i think the problem is, when i try writing to recovery, the message may say OKAY. but i am not sure that its being written in.
when i try a "fastboot erase recovery"
i always get "FAILED (Status read failed (Too many links)) "
another problem could be that the boot-mode is FASTBOOT
Is this the same as the one that we are suppose to turn off in the settings?
if yes, since i cant get in the phone settings. how do i turn it off?
if no, then it doesnt matter?
and is the security: on an issue? maybe why i cant erase recovery or load recovery ? i do noticed a difference in the screen on the phone when i load a "signed" recovery vs CWM and TWRP.
Anyone? help?
Thanks.
CK
Click to expand...
Click to collapse
I never have erased a recovery I have flashed over the old one... Seems to overwrite that part the recovery is stored...
Haven't had any issues doing it this way...
Subaochen,
Try plugging the mainboard while disassembled, just mainboard and battery. thats how i found out mine works. then you can slowly reassemble step by step. if yours doesnt connect normally during that time, check the board over. if you can identify which part overheats then you know where to press...
Good Luck!
CK
reaper24,
I have tried "fastboot flash recovery any.img" multiple times without success, until i disassembled it and then, everything was just normal. could also be a dirty connection for me. altho when i run the RUU, it "seems" to work properly since i was able to upgrade to latest stock ROM.
I do have S-ON so i guess i would never be able to erase recovery nor boot.
hopefully everyone have the patience to troubleshoot their unit. i had to learn patience with mine.
boot loops are really the discouraging to say to least.
Sincerely,
CK
xdapyro said:
Subaochen,
Try plugging the mainboard while disassembled, just mainboard and battery. thats how i found out mine works. then you can slowly reassemble step by step. if yours doesnt connect normally during that time, check the board over. if you can identify which part overheats then you know where to press...
Good Luck!
CK
Click to expand...
Click to collapse
Thanks xdapro first!
I have tried again but not lucky:-(
Maybe my situation is not the hardware failure, just the wrong kernel or boot? When I accepted the OTA while the phone was rooted and after have a full reboot, the phone just stuck at the htc splash screen and boot loop.
I guest that, when I accepted OTA, the bootloader was updated to Hboot 1.5. But because the phone is rooted, kernel or boot partition is not updated by OTA, so the security signature is not the same between the new bootloader and the old kernel, so the boot loop.
I have tried RUU and all custom recoveries I can find, all failed, the recovery seemed installed ok, but can not boot into recovery. Also, I have tried fastboot boot recovery.img, just directly boot into the HTC splash screen and boot loop.
Anyone can give any hints? thanks a lot in advance!
Just a heads up, you have to "relock" the phone before flashing the Stock RUU's.
From "fastboot USB" Type: fastboot oem lock
It will erase the recovery in the process. I have had bad ruu downloads before. If the exe doesn't work, get the zip version.
Okay, I have what looks to be like a very nice stock gingerbread HTC flyer with Demo.apk and DemoRecovery.apk installed to it. (No, you can't just uninstall them**.) The long and short of this is that no matter what you do to this thing, as soon as it reboots, it wipes out all changes and restores it to the original stock gingerbread with demo. I'll put all the Flyer specifics at the bottom of the post, but here's a short list of what I've tried so far (there's more; this is just the big stuff):
Revolutionary: works fine until the very last step, which is a reboot. Then fails. As I understand it, I can't install CWM recovery until I'm s-off.
Running the stock Bightstar RUU: Copies over fine, says it's rebooting to do the actual flash, and boots directly into Android, wipes out all the files and fails.
HTC bootunlocker fails with a command error (and since I copied and pasted it into the command line, I'm pretty sure I got that part right).
I have adb and fastboot working.
Before I waste any more time trying to reinvent the wheel, I'm just going to ask. Is there any way to flash this thing without rebooting it at any point before it completely finishes? I'll take any help offered because at this point, it's a very pretty paperweight.
Specs:
CID: BS_US001
Flyer PVT Ship S-on RL
HBOOT: 1.10.0000
Microp: 0850
Radio: 3809.85.04.10_m
eMMC: boot
May 4 2011, 11:04:45
**There is a way to stop the demo from starting automatically, but it a) requires a phone keyboard and b) apparently doesn't do a thing to reverse the changes made when you install the demorecovery.apk.
Well you could go through the process of rooting and installing cwm to it and upgrading to HoneyComb. Also if you can get it rooted you could delete the demo.apk and demorecovery.apk from system files.
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0
Hello all!
First of all, I think this website is awesome, lots of usefull stuff and information, you guys doing a great job. By guides on this site I was able to unlock my phone, root it and install all kinds of different ROMS. With those guides it was very easy! However now I seem to stupid to restore my HTC ONE (TMO-101) back to stock. What I exactly want? Just completly restore it to default. After hours of doing and reading stuff, I just gave up. I think I made it even worse as before. I used and restored an backup (old one) from original state. But! I cannot update with the OTA pushed. Seems I first have to put back the original recovery and unroot the device. I thought that an RUU would be the solution, however I cannot find any for my version or in other words one that actually works for me! Then I thought ok lets try the backups made by someone else and restore those, recovery tool is not working anymore... If you could provide me with the correct steps and tools to perform this, I would be very thankfull! Because I'm totally lost....
My HTC ONE current state:
***TAMPERED***
***RELOCKED***
***SECURITY WARNING***
M7_UL PVT SHIP S-ON RH
HBOOT 1.44
Android version 4.1.2
* Used Clockmod recovery before but it does not seem to work anymore, so basically no recovery atm.
Thanks in advance for looking in to my issue!
Hanzz2013 said:
Hello all!
First of all, I think this website is awesome, lots of usefull stuff and information, you guys doing a great job. By guides on this site I was able to unlock my phone, root it and install all kinds of different ROMS. With those guides it was very easy! However now I seem to stupid to restore my HTC ONE (TMO-101) back to stock. What I exactly want? Just completly restore it to default. After hours of doing and reading stuff, I just gave up. I think I made it even worse as before. I used and restored an backup (old one) from original state. But! I cannot update with the OTA pushed. Seems I first have to put back the original recovery and unroot the device. I thought that an RUU would be the solution, however I cannot find any for my version or in other words one that actually works for me! Then I thought ok lets try the backups made by someone else and restore those, recovery tool is not working anymore... If you could provide me with the correct steps and tools to perform this, I would be very thankfull! Because I'm totally lost....
My HTC ONE current state:
***TAMPERED***
***RELOCKED***
***SECURITY WARNING***
M7_UL PVT SHIP S-ON RH
HBOOT 1.44
Android version 4.1.2
* Used Clockmod recovery before but it does not seem to work anymore, so basically no recovery atm.
Thanks in advance for looking in to my issue!
Click to expand...
Click to collapse
I was in the same boat as you last night, I thought I bricked my phone, but thanks to this post, I was able to do it. http://forum.xda-developers.com/showthread.php?t=2496074
First you have to relock your bootloader, it's quite easy. Go to your fastboot folder on your computer (the same one you used to unlock your phone) open command prompt there (Shift + right click) then type fastboot oem lock then run that RUU that I posted and it will restore you to 100% stock, like you just took it out of the box.
Thanks!!
Gonna try this right away:good:
It's not working. Model-ID error (130). Had this one before, it's the US version. But, I got the TMO101 (DE). This is the model also sold in the Netherlands.......
Any RUU available for this as well? Couldn't find it or
Other options?
Thanks!
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
chilort said:
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
Click to expand...
Click to collapse
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
es0tericcha0s said:
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
Click to expand...
Click to collapse
I'm going to bring some of this to you in pieces so I may edit this post for more info to answer your questions (I have a toddler running around and it is dinner time).
I do not know my firmware version. Under relocked my phone says:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.29.40g.00.19
OpenDSP-v19.2.0268.0927
OS-4.13.502.3
eMMC-boot 1024MB
Jul 11 2014,20:49:19.0
I cannot hotlink but the one in this thread (http://forum.xda-developers.com/showthread.php?t=2777778) is one of the RUUs I tried. I tried others but in my haste to try to get this thing running again I didn't exactly take good records.
After running getvar all
version: 0.5
version-bootloader: 2.22.0000
version-baseband: 1.29.40g.00.19
version-cpld: None
version-microp: None
version-main: 4.13.502.3
version-misc: PVT SHIP S-ON
serialno: HT385WA00294
imei: 356482050078674
meid:
product: m4_ul
platform: HBOOT-8930
modelid: PO5822000
cidnum: CWS__001
battery-status: good
battery-voltage: 4314mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e1af350
hbootpreupdate: 11
gencheckpt: 0
Edit:
Okay, when trying the RUUs I get Error 155: Unknown error.
My PC is a an old Core 2 Duo and crashed a few times just trying to load the RUU. The RUU then asks to go through a recovery mode. It shows a picture with four exclamation points in the corners of the screen on the phone. My phone does not have the exclamation points. I've tried the recovery process a few times and it doesn't do anything.
The error about something being too long was when I was trying to load a .zip using fastboot from my Mac.
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
es0tericcha0s said:
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
Click to expand...
Click to collapse
Thank you for the help! I am not at all opposed to a custom rom (I thought going backward might be easier than forward). But that goes beyond what I've read so far. I know I could Google it, but would appreciate any links, pointers, or other primers.
Stock + root is what I was trying to achieve.
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
es0tericcha0s said:
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
Click to expand...
Click to collapse
The version of TWRP on my phone is 2.6.0.0. This is not version listed in the link you posted. They list 2.7.0.5. Will this be problematic?
I went ahead and gave it a try. I loaded TWRP and went into the adb sideload feature. The screen for sideload listed the following:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Running boot script ...
Finished running boot script.
E: TWFunc::Copy_Log -- Can't open destination log
E: Unable to mount '/cache'
Starting ADB sideload feature ...
I saved the rom as rom.zip to make things easier as suggested. In my terminal window I typed the command as listed (ADP and the rom are in the same folder). In the terminal window I received:
error: closed
error: closed
You will definitely need the newer TWRP before it will work. But you don't use adb sideload. As long as the PC recognizes the phone correctly, then you just need to open the Command Prompt, change directories to the folder where adb and rom.zip are store and then copy and paste the command into it and hit enter. It should start to send. It will take awhile and there is no timer so just go grab a sandwich or drink or something and be patient.
You can use this video for reference:
https://www.youtube.com/watch?v=Hn4E3fKX7WM
It's a different device, but the same exact steps. He does state that he puts the name of the rom after /sdcard/ in the command, but it's not necessary. Won't make a difference for this.
Okay. That was somewhat helpful. I couldn't find TWRP 2.7.0.5, but I did get 2.7.1.1 and I got it loaded.
I've tried the adb command. It sits there for a long time, then the phone reboots into TWRP. I get no messages back in the terminal window and nothing is loaded into the /sdcard directory (or anywhere else as far as I can tell).
Edit: wait. Formatted it and am going to try again.
Edit 2: loading rom!!!
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
es0tericcha0s said:
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
Click to expand...
Click to collapse
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
chilort said:
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
Click to expand...
Click to collapse
:good::highfive::victory:
es0tericcha0s said:
:good::highfive::victory:
Click to expand...
Click to collapse
Thank you again for walking me through this. It is nice to have my HTC back. My slow, piece of junk work phone can now go back to running BOINC.
No problem. It's how I give back to the community.