"Please insert SIM to make calls" - Hero, G2 Touch Q&A, Help & Troubleshooting

hi guys,
been doing a lot of reading & kind of exhausted and the head is hurting
hope someone can help me...
i had a HTC hero on orange UK brought down to India.
Trying to unlock & load a random ROM but having the bizzarest of issues.
the hero is running on stock 1.5 build 2.73.61.66
i downgraded to 2.73.61.5 assuming that would be a better way to go...
anyways the process went well... BUT..
it starts up and goes into the "first setup" page where it asks for language & then asks me to insert the sim card to make calls...
I have NO ORANGE SIM Card.
There is no way i can enter into the phone now. i could do it earlier, the phone would boot without the sim & i used it to play music & stuff.
Now decided to use the phone for wat it is meant for, but stuck in that stage.
Can anyone help me out please.
or direct me in the right direction....
is there a way to get past this and actually come to the home screen so i can continue with everything such as unlocking the phone & loading a different rom?
Await & appreciate any response

If you just want "your phone" back I think you should be able to find the official way of restoring it to default (even upgrade to HTC's android 2.1) here:
http://www.htc.com/europe/supportdownloadlist.aspx?p_id=283&act=sd&cat=all
if you get the green android robot and starts to ask you for google login etc you can click the four screen corners to go directly to Home. Like this:
23
14
afaik Android wasn't built for use without a sim - I've wondered why too. It's complicated using it with no sim. Here's what I found on google:
http://e.ntangled.net/content/howto-set-android-dev-phone-without-sim-card
Perhaps it's because it isn't activated (with your google login) and it was earlier with a sim card but now you can't because you have no working sim card
MP3 files
If you've installed a boot loader like Amon's RA Tool v1.7 (that starts instead of Android when you hold Home and Power/hang up-button 10 seconds at boot) it might give you access to the SD-memory card and your MP3s.
I think The official HTC ROMs can only be installed (the official way) using USB and a flash-programming tool from HTC on your PC.
The Android SDK software - if I remember correctly - allows you to program the phone's recovering boot ROM (a small boot ROM - not the big phone/android OS) and once you've installed a new recovery boot ROM like Amon RA tool you can install any Android ROM directly from the SD card (ROMs in a zip file) without ever needing the PC again. You can even backup the entire phone ROM to the SD card using Amon RA tool's Nandroid backup feature and restore the ROM again if a new custom ROM is bad.
> So you are telling me that I can install Amon Ra directly
> from the PC, without having any interaction with the Phone?
Yes, I think that's probably the ONLY way actually (for the recovery boot tool).
> do you think i would be able to install a new rom and
> probably get past this screen (and probably jailbreak the phone as well)??
Hmm I'm pretty sure that most custom ROMs (I can recommend a few for htc Hero GMS) let's you go directly past the startup procedure.
> btw Thanks so much for your patience dvfk
No problem.
Here's a test how to install the Amon tool using the USB command line/shell to the phone:
http://forum.xda-developers.com/showthread.php?t=561124
If you have htc Hero GSM the newest Amon RA tool is available there. Do you know about the ADB shell that comes with the SDK to control the phone over USB?
btdag:
You can't install AmonRA without root permissions, you can't get root unless you get into android. My advise - downgrade to a different rom: ftp://xda:[email protected]_2.73.405.5_WWE_release_signed_NoDriver.exe
If that boots then you should be able to gain root using my guide:
http://forum.xda-developers.com/showthread.php?t=645253
If not why not install an orange rru exe from HTC support? That might work.
Click to expand...
Click to collapse

Currently one of the most popular ROMs is CyanogenMOD and the newest version (with android 2.2) is here - they're not 100% stable though (and camera can only shoot video in build 08312010 - I now see build 09012010 is just out but I haven't tried it):
http://mirror.kanged.net/cm/nightly/hero
When it's stable it will be moved to .../cm/stable and /hero I guess.
It lacks Gmail and other closed source google apps. They can be found here and should also be installed using Amon RA recovery boot tool after the full CM6 ROM is installed:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps_for_HDPI_devices_2
(Hero works nicely with the HDPI version of Google apps for high-res displays)
I've found another ROM, though, called FroydVillain v1.4.4 to be more stable and cam working. It's a modified copy of the CM6 and includes the google apps from the start. However to get the newest version you currently need five zip files and install them all in the number order (FroydVillain 1.4.0 - 1.4.1 and 1.4.1 - 1.4.2 etc on to 1.4.4).
Links can be found here:
http://forum.xda-developers.com/showthread.php?t=762206

letmedanz said:
well, not so good
1) trying btdags advise -
> "You can't install AmonRA without root permissions, you
> can't get root unless you get into android. My advise -
> downgrade to a different rom:
> ftp://xda:[email protected]_NoDriver.exe"
i end up with error 131. i guess this means i need a gold card. just started reading about it
Click to expand...
Click to collapse
I think this is the newest guide to root/hack your Hero:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click
...but the link to Amon RA boot tool is outdated - there's a version 1.7 afaik (see in my earlier post).
If I remember correctly I used this old/obsolete version:
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero/
letmedanz said:
2) your suggestion:
> "I've found another ROM, though, called FroydVillain
> v1.4.4 to be more stable and cam working"
> as you should know by now, am completely new to
> this, so i tried the guide:
> http://www.villainrom.co.uk/forum/showthread.php?2054
i've just reached this step:
reboot into recovery (press Home and then power on the Hero, keep Home pressed) after copying 1.4.0 & 1.4.1, But when i hold home & power, it reboots & shows an exclamation mark within a triangle, next to a phone. supposing this is not right.
Click to expand...
Click to collapse
That's because as I said first VERY first think you need to do is install the Amon RA recovery tool - and make sure home + power boots into the RA tool.
letmedanz said:
i have no ideas on adb, trying to see if thats the way and i need to learn to use it..
Click to expand...
Click to collapse
When you install the Android SDK you get the ADB command line/shell and drivers for the phone. When the phone is plugged in (and usb phone drivers intalled) you can access the phone using ADB and do anything with it.
The old/obsolete verison of unlocking/rooting your Hero describes how you use ADB:
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero
...but it seems the new version of unlocking (one-click rooting) doesn't even need it.

dvfk said:
I think this is the newest guide to root/hack your Hero:
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click
Click to expand...
Click to collapse
well, that is where the problem started
Orange UK Users - Please downgrade your ROM version to 2.73.61.5 using this HTC Program. Then you can follow the rest of this procedure as it is written. Good luck!
i had the .66 version, after reading the above, i downgraded to the .5 version.
After the install, it boots, reaches the initial setup page.
First asks for language, next screen is "Insert sim to make calls"
so unable to proceed....

...and in this guide you get stock too?
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero
It mentions USB debugging must be on (so you need to access Settings I guess) but it's worth a try.

At work now.. so will need to try after heading home

Any progress?

well... just tried the obsolete htc hero root method
**How To: Gain Root Access on Your HTC Hero (OBSOLETE)**
Steps 1 to 10 are smooth, no issues
Step 11 . If the serial number and the word fastboot next to it popped up, then go back to the command prompt on the computer and type
fastboot boot cm-hero-recovery.img
here i get an error-
downloading 'boot.img'... FAILED <remote: not allow>
so stumped there..
checked in unlockr.com & they says to get past this stage i need to create a gold card...
which obviously is not possible i cant get into android...

Any suggetions/comments/help ???

Why not to flash a custom ROM?
Sent from my GT-S5660 using xda premium

Related

Trying to root/flash my Hero (Three UK) but nothing works

Hey all,
I have a Hero on 3 UK network and since the stupid network dont seem to be releasing any updates for it, I want to root it and manually put 2.1/2.2 on there.
Problem is, NONE of the guides on how to flash it work.
Here's what I've tried so far:
Goldcard method - I have succesfully created a goldcard using a Kingston 1GB card (tested on a Desire and works). Trying to downgrade to the stock HTC ROM using HTC's RUU gives me error 140 (bootloader version error).
Rooting the phone - Phone is all hooked up to ADB, can poll it for information etc. Tried to boot it into a recovery image but get an error saying the following: "downloading 'boot.img'... FAILED (remote: not allow)"
Alternate rooting method - So I found out ROM version 2.73 or whatever it is has some kind of extra security on it. The guides are advising me to download flashrec.apk and install on phone to backup then flash the recovery sector of the phone. This doesnt work. I can neither backup nor apply the recovery images. Even if I override the backup part, it still wont work Just gives me yet another error.
Seems that my Hero is locked down with some impossible to break security. Anyone else having the same difficulty with Three UK? If so are there any other ways you guys may have come up with to root/flash your phone? I'm getting really pissed off with it and am probably going to do an insurance job on it if I cant flash it.
FYI, this phone has not been updated since August 2009. Everything on it is stock from Three UK.
Versions (if you think it's useful):
Firmware: 1.5
Build: 2.73.771.62
Baseband (radio): 63.18.55.06IU_6.35.08.22
Kernel: 2.6.27-430d1aea
Any help I shall be most grateful for!!
Follow my newbie guide. Should talk you through it step by step.
The bootloader error is probably a driver thing. Update your HTC Sync and it should update the drivers.
Sorry, just noticed the thread got moved, my mistake.
Anyone able to shed any more light on it?
I followed the noobie guide and it didnt work. I have the latest version of HTC Sync installed.
Insurance job looking more likely.
Still with error 140? Did you update the driver in fastboot / bootloader mode?
Alternatively try this: http://forum.xda-developers.com/showthread.php?t=726118
btdag said:
Still with error 140? Did you update the driver in fastboot / bootloader mode?
Alternatively try this: http://forum.xda-developers.com/showthread.php?t=726118
Click to expand...
Click to collapse
Which one is your noobie thread mate? I followed several threads off this forum all claiming to be noobie. TBH, they were all pretty straight forward enough, and worked when I helped my mate flash his Desire.
Min can be found here: http://forum.xda-developers.com/showthread.php?t=645253 (it's also in my signature )
Ok yeah, I'll just go over the points in your guide then explain how it failed...
Using Flashrec to backup and apply a recovery image...
Flashrec simply doesnt work on my phone (have tried about 3 different versions, including the very latest which is 1.13). No functions work. Cant even use the bypass backup button (hidden button to the right of backup button). That section ended there for me.
Goldcard method...
No matter what RUU I try to downgrade to, it does not work. Keep getting error 140 (incorrect bootloader version). The goldcard I made definitely works as we used the same one to downgrade my mates Desire today.
I found some other guides, which looked like they might help as they go a bit further, but ultimately every time I try and actually do something, it gets blocked, access denied or some other error.
Flashrec won't work if you're on the wrong version of android (i.e. not downgraded using goldcard).
Goldcard is fine it is most likely your drivers in your bootloader mode that are wrong - check them first.
Drivers were ok. I managed to downgrade using a newer version of the stock HTC ROM after scouring these forums for hours.
So in short... ALL GOOD.
Only problem I have now is that there is no manual update option on eclair (1.5). The 2.1 FOTA updates attempted to download before I setup the WiFi and now it wont come back.
If you want to stay official then you can put the month forward a few and the update should show up again.
Surely the point of this was to get root and a custom rom though no?
The point was actually to get Droid 2.1 'cos 3Uk are dragging their heels big time, but now opens up the options of loading custom ROM's.
TBH I'm happy just to have 2.1. Eclair was doing my head in with all its bugs.
Thanks for the tip with the date - it worked!
i wounder if you did it or not ? cuz o have the same demmn problem with my hero G2 touch t-mobile nothing work for me i try all methods i think last solution is to bring a big hummer and break it as i like (
Fellow 3 UK Hero Owner
I'd just like to add how angry I was when the 2.1 update failed to show up. The Goldcard method worked perfectly for me, then I looked at custom ROMs. I currently run Gingerbread and I have to say, not only is it SUPER fast and smooth but its way less buggy than the stock Hero ROMs.
I'm with the Cronos crew. To get the latest ROM, search for cronosproject (.org) and click forums. (cant post link because i haven't posted 8 times )
Seriously, you wont regret it
best way to fix this is...... make sure u have a file manager, download universal androot to your computer and then to your phone install through file manger and root phone then once rooted install rec image with rom manager from market.....there you go its rooted now follow my guide to flash custom roms properly and to root phones....
mayb its ur android version
may i please know it i can surely help you

[Q] problems downgrading Hero kernel

I have T-Mobile G2 touch that is running Android 2.1 and now I want to take it to Android 2.3
A friend of mine "debranded" it from T-Mobile and put a custom ROM on it for me over a year ago but not sure what procedure he used.
The phone doesn't seem to have been rooted.so I am first of all following the procedure I have seen all over these forums and various other sites which is to take it back to kernel 2.73.405.5 in order to root it then proceed from there
The procedure I am following is:
Get the SD card CID code using either ADB or the goldcardtool.exe
Calculate the reverse string using either a website tool or the goldcardtool.exe (tried both methods)
Get emailed the goldcard img file generated by the website
Format the SD card with fat32 and write the contents of the img file to it using either the goldcard tool or manually using a hex editor from sectors 000 to 170 (I have tried both methods)
Restart the phone (should something obvious happen at this point ?)
Thenwith the phone connected to the PC via HTC sync run:
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
After it goes through trying to install I get an error
Error (140) bootloader version error
I have also tried using RUU_HEROR_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe
With the same error.
My phone details are
Hboot 1.76.0007 (Hero10000)
Firmware version 2.1- update 1
Baseband version 63.18.55.06PU_6.35.15.11
Kernel 3.36.405.1
Software Number 3.36.405.1
Browser version webkit 3.1
Can anyone tell me where i'm going wrong please ?
thanks in advance
Glen
Harani said:
I have T-Mobile G2 touch that is running Android 2.1 and now I want to take it to Android 2.3
A friend of mine "debranded" it from T-Mobile and put a custom ROM on it for me over a year ago but not sure what procedure he used.
The phone doesn't seem to have been rooted.so I am first of all following the procedure I have seen all over these forums and various other sites which is to take it back to kernel 2.73.405.5 in order to root it then proceed from there
The procedure I am following is:
Get the SD card CID code using either ADB or the goldcardtool.exe
Calculate the reverse string using either a website tool or the goldcardtool.exe (tried both methods)
Get emailed the goldcard img file generated by the website
Format the SD card with fat32 and write the contents of the img file to it using either the goldcard tool or manually using a hex editor from sectors 000 to 170 (I have tried both methods)
Restart the phone (should something obvious happen at this point ?)
Thenwith the phone connected to the PC via HTC sync run:
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
After it goes through trying to install I get an error
Error (140) bootloader version error
I have also tried using RUU_HEROR_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe
With the same error.
My phone details are
Hboot 1.76.0007 (Hero10000)
Firmware version 2.1- update 1
Baseband version 63.18.55.06PU_6.35.15.11
Kernel 3.36.405.1
Software Number 3.36.405.1
Browser version webkit 3.1
Can anyone tell me where i'm going wrong please ?
thanks in advance
Glen
Click to expand...
Click to collapse
If your phone has a custom ROM on it then it will be rooted. And what you are doing is a method I'm not familiar with when rooting..
There are simple one-click root methods available in the form of;
z4root or androot.
Use one of them and you will find the process to be much simpler.
Sent from my Hero using XDA Premium App
Hi,
You are right I've just tried Androot and it reports that my phone is already rooted.
However i'm still having a problem that when I try to download and install a 2.3 ROM (Elelinux-7.1.0-Hero-v2.6) i copy it to the SD card rename to update.zip then when i try to enter the updater HOME+PWR i just get a picture of a phone with a red triangle with a red exclamation mark in it.
I had thought this was because i wasn't root which was why i was trying to get to a baseline to start from but it appears not.
I think this and the previous problem may be down to the bootloader version i have installed ?
Harani said:
Hi,
You are right I've just tried Androot and it reports that my phone is already rooted.
However i'm still having a problem that when I try to download and install a 2.3 ROM (Elelinux-7.1.0-Hero-v2.6) i copy it to the SD card rename to update.zip then when i try to enter the updater HOME+PWR i just get a picture of a phone with a red triangle with a red exclamation mark in it.
I had thought this was because i wasn't root which was why i was trying to get to a baseline to start from but it appears not.
I think this and the previous problem may be down to the bootloader version i have installed ?
Click to expand...
Click to collapse
No its because you dont a custom recovery installed, there are a couple guides in these forums which should tell you how to install one or download rom manager from the market and install one from there.
Sent from my Hero using XDA Premium App
Ok Thanks,
have already been trying to flash a custom recovery image but flashrec doesn't work for me. I keep getting "could not run command" the flashrec page http://zenthought.org/content/project/flashrec suggests this may be due to a patched ROM being installed which is part of the reason i was trying to downgrade the ROM in the first place.
I've also been trying to use ADB to flash the recovery image from my PC but i can never seem to get the SD card mounted via USB.
I'll try a market app and see how i get on
update:
downloaded "ROM manager"
When trying to Flash Clockworkmod recovery with it i get an error which says "an error occurred when attempting to run privileged commands"
this sounds like my phone is not rooted despite with androot says. (which fits with what i've read on these forums and also here http://theunlockr.com/2009/10/18/how-to-downgrade-your-htc-hero-so-it-can-be-rooted/
here that i need to go back to kernel 2.73.405.5 in order to root correctly.
I seem to be going round in circles :-/
it seems like i can't flash a custom recovery until i downgrade the ROM and Root it
and i can't downgrade the ROM until i have custom recovery installed
<bangs head against wall>
Did you get a prompt while trying to flash the recovery? ie; A prompt which asked you to allow ROM manager superuser access and you have a yes/no option.
Sent from my HTC Hero using XDA Premium App
Yes and i allowed it. i now have "superuser" running in the background with ROMmanager allowed superuser privileges
i did the first option in the menu which is to flash "clockworkmod recovery"
this time it didn't complain about privileges (Some progress !)
but I then told it to reboot into recovery mode but i still got a red triangle with an exclamation mark in it
then i tried it again and SUCCESS i now have a recovery utility
Off to try to install EliLinux 2.3 now.
Many thanks for the pointers !
it is very much appreciated.
No problem, its what I'm here for .
Sent from my HTC Hero using XDA Premium App

[Q] Rooting Galaxy Tab 10.1 I/O on 3.1 Honeycomb?

I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.

[Q] HTC One X + (boots to HTC white screen only)

Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...

[Q] Prompted daily for same OTA update?

I have a stock rom evo 4g LTE, rooted, with Android 4.0.3 on it.
I forget the root app I used, some one click thingy, I guess my bootloader is unlocked
because I get a boot menu every time I reboot, on that screen that says **TAMPERED**.
Anyway, I ignored the notification icon in my taskbar for OTA updates, for a very long time.
Since the day I bought it over a year ago.
Finally I decided "eh, screw it, why not." ...I'm sure I'll regret that.
I told it to do the OTA update, and it downloaded (I think??) and rebooted.
The icon went away. Seemed to be a done deal.
But once per day since then, my phone rings, and I see a prompt saying
there's an OTA update, and would I like to install it now?
I think it's the same OTA update being prompted repeatdly,
because the filesize is always the same (~42 megs).
What should I do? I can choose install, reboot, and be fine for the rest of the day,
or choose cancel, reboot, and be fine for the rest of the day.
Doesn't seem to matter. But would be nice to fix it for good.
Well, considering that you are about 4-5 OTAs behind the rest of the community, I would say that the notification is probably correct. HOWEVER, of you are not using the stock recovery, then the OTA did not flash. Yes, the phone rebooted, but that's because it is installed entirely through recovery, and the phone has to reboot to get into recovery mode in the first place.
Now, for the more important question at hand....why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted? As far as I'm concerned, the OTAs are actually necessary updates for the phone. I'm sure that you will love Jelly Bean if you have never used it before.
And please, for the sake of us all who are cringing at the sight of the first sentence....PLEASE UPDATE your phone! If you have a good reason not to, please share.
Hi, thanks for the reply... Maybe they were all different updates after all.
I haven't been prompted to update again since my post.
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
HOWEVER, of you are not using the stock recovery, then the OTA did not flash.
Yes, the phone rebooted, but that's because it is installed entirely through recovery,
and the phone has to reboot to get into recovery mode in the first place.
Click to expand...
Click to collapse
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted?
Click to expand...
Click to collapse
Well, I had no compelling reason to upgrade. I still don't really, the phone does what I want,
I just saw some of the features in the next version and thought "huh, that sounds pretty cool".
I'm rooted for all the usual reasons... I want to be able to browse, copy, move, rename files (including system files)
without incident... use nandroid for backups... wifi tether (still can't get that to work actually)... install unapproved apps...
tweak the OS, and so on.
Ok, my friend...let me educate you. Instead of giving you the simplest, fastest solution, I will actually try to answer all of your questions, since you did ask.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
Click to expand...
Click to collapse
To give a very superficial explanation of Jelly Bean, it is everything that ICS does, and more. It just does it smoother. It also brings Google Now, which was – and still is – the selling point of Jelly Bean. The Sense launcher got a few changes, too, but you will have to explore those changes on your own (mainly because I don’t remember them off hand, and this post is beginning to become lengthy).
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
Click to expand...
Click to collapse
If the first update didn’t update properly, then the phone is simply downloading and trying to install the same update over and over. When you boot back into Android after a successful update, you will be greeted by a welcome message congratulating you for installing the new version.
If you are rooted, odds are, you are using a custom recovery, such as TWRP or CWM. OTAs are only installed through the stock recovery & a locked bootloader. The stock recovery doesn’t make nandroids, or do anything of the sort. To install the stock recovery, go here:
http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
Click to expand...
Click to collapse
The stock recovery is located somewhere within the zip file.
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
Click to expand...
Click to collapse
You can flash install the stock recovery by using fastboot commands from the bootloader (which is the screen that shows the TAMPERED status on the top), or you can use Flash Image GUI. It is a paid app on the Play Store, or you can get it from XDA (the dev let XDA users download it for free…Google it).
Lastly, there are a few things that I suggest that you do. First, obtain S-Off (Google, Google, Google...very simple), so you can install the new firmwares directly, instead of using OTAs. Otherwise, if you accept the OTA, you will lose root, and you will have to root your phone again and again. Installing the firmware, then the new rom is the same as accepting the OTA, then rooting.
Another alternative is to get S-Off, then accept the OTA (after installing the stock recovery). Your bootloader does not need to be locked, and there are recovery zips floating around here that can be installed through the bootloader (therefore, you will not be stuck rooting the phone the hard way, just boot into recovery and flash SuperSU). I highly suggest achieving S-Off.
If you want to jump straight to the latest version (Android 4.3, Sense 5.0) by installing the RUU located somewhere in this forum. I actually suggest that you try Sense 4 with Jelly Bean first, but that is completely up to you. Keep in mind that using the RUU will wipe your internal memory, so back up what needs to be backed up. This doesn’t require you to be rooted, and the state of the bootloader does not matter. It will lock the bootloader, load the stock recovery, and you will lose root. You won’t be able to downgrade without S-Off.
Other Notes:
When using the 4.3 RUU, make sure that Android USB Debugging is enabled.
Bookmarking for later but I wanted to say thanks for the thorough reply!
I can confirm the update never worked, because I never got the confirmation message
and I got prompted again a few hours after I posted.
Are you willing to answer just a few more things?
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
- Get my phone into S-OFF status.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
Are you willing to answer just a few more things?
Click to expand...
Click to collapse
As always, I'm open for questions. Not to sound egotistic, but I enjoy sharing my opinion.
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Updating to the 4.3 firmware wipes your internal memory, not your sd card (although, that may be a very unfortunate circumstance, so it should be backed up as well). The other firmware updates do not affect your memory.
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Technically, yes they are "on the cloud." The fact that you paid is saved somewhere within your main Google account that you downloaded the app with. It is possible to pay for apps with your secondary gmail account, which can be switched within the Play Store app.
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Use Titanium Backup if you can't find the apks. I do save my apks that I download, and I also upload them to Google Drive, since I have multiple Android devices, and I also have a faulty micro sd card that I am yet to replace. I can lose my data at any given moment, but everything is backed up, so I'm not worried.
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
Everything within the /system folder is wiped when you flash new roms. That data is NOT backed up while flashing between roms. Also, since it is from an older Android version, it's best to leave them alone. You may back up the data if you like, but I would refrain from restoring the apks along with the data.
The /data directory may be wiped, depending on the dev who built the rom zip. If they added the superwipe script, then /data will be wiped as well. Most devs do not include this, since many people "dirty flash," which is flashing new roms or updates of the current rom without wiping /data first.
- Get my phone into S-OFF status.
You will save yourself a LOT of headaches in the future. It was my S-Off status that allowed me to reflash my firmware when I lost the function of my data/voice antennas while carelessly flashing a port of a phone on a different carrier. Also, if you feel curious to try AOSP roms, then you do not need to do any extra steps to flash them.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
Yes, the firmware handles manages how the hardware of the phone operates. Updating the rom changes how the software looks and behaves. The kernel is sort of a bridge between the firmware and the software, since it manages the firmware (like battery life, processor speed, antennas, etc.), but the kernel is dependent on the software version. The firmware is not dependent on the software version, just as the software version is not dependent on the firmware version.
The only exception of the firmware/software independence is the 4.3 update, which requires a complete update of the firmware, and the older software cannot run on the new firmware without being modded by a dev.
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
Your bootloader is the white screen that shows the TAMPERED status on the top, and little Androids on skateboards on the bottom. With the exception of the firmware information in the top left corner, this screen does not change...ever.
TWRP is your recovery image, which is accessible through the RECOVERY option in your bootloader, or you can boot directly into it through different apps in Android - Titanium Backup is one of them (yes, that's one of the options, even for the free version).
The only reason to return your recovery to stock is to accept OTAs, and also to bring your phone back to the complete factory settings, just as the day when it was first purchased (for the sake of selling the phone, or returning back to Sprint for service}. Otherwise, don't bother with it. You may want to update your version of TWRP, though. If you update to 4.3, you will have to update it. I'm not going to take the time to get into that right now. I've given you enough homework.
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
I am a very patient person. To me, exploring Android takes time. I enjoy reading before I test, and testing before I settle (which I'm yet to "settle"). All of that being said, I suggested Sense 4 before Sense 5 because I wanted you to experience the both of them. They are truly two different versions of Sense, which one might not realize, as their version numbers are differentiated by one integer (in other words, 4 to 5). Sense 3 was a small step above Sense 2, and Sense 4 was a bigger step from Sense 3. Sense 5 is a complete overhaul of the Sense UI, save the flip clock.
I just feel that skipping from 4.0 to 4.3 is missing out on a great experience, but that is mainly if you actually want to try out different roms. Until the Sense 5 RUU, I still visiting ICS on occassion, but I usually didn't last more than 3 hours before I jumped back to JB.
Click to expand...
Click to collapse
Whew...you're making me work. But I like it. Anymore questions? Feel free to ask.
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
CreeDo said:
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
Click to expand...
Click to collapse
Did you unlock your boot loader first? You don't need to be S-off to install a custom recovery. Unlock your bootloader at htcdev.com then install twrp.
Read here for more info:
http://forum.xda-developers.com/showthread.php?t=2420916
Also, I suggest learning how to use fastboot commands. Install twrp using fastboot.
Sent from my EVO using XDA Premium 4 mobile app
OK, so I'm semi-bricked but not panicking yet.
Here's where I'm at.
• Unlocked boot loader successfully
• Installed TWRP using fastboot.
• Followed instructions as closely as I could on moonshine.io to get S-OFF working.
Several times during the process I got "installing device driver software" in my win7 system tray.
Not sure if that's normal. But the drivers seemed to install fine. At first.
But then, during this part of the process:
Moonshining .................(1)
Windows prompted me that it was installing some drivers again, But it failed to install the MTP driver.
After ten tries with the "Moonshining" step, I got "ERROR: don't drink and moonshine!" or something like that.
So, it seems like I need to get this MTP driver going. First I tried solutions on the computer:
• Uninstalled all HTC software, unplugged phone, rebooted,
installed HTC Sync Manager (setup name setup_3.0.52.0_htc.exe), then uninstalled it...
because a tutorial said this would keep the drivers but remove the software. Still no luck on the MTP driver though.
• Found "Mass Storage Device" (my phone) under device manager, removed it, unplugged, rebooted, replugged.
• Plugged cord into back of PC, so I'm using USB 2.0 rather than USB 3.0.
• One suggestion said a certain registry section might have an upperfilter key that shouldn't be there.
But I don't have that upperfilter key so that's not the issue.
Some fixes require getting into my phone (one guy suggests turning off USB debugging)...
but I no longer have a working OS. I can get into my bootloader, I tried Factory Reset.
But after choosing this I go into TWRP and I have no TWRP backups that I can restore.
So my next guess is, I need to get a recovery ZIP (is that basically a ROM?) that TWRP can install.
If that's correct, what ZIP should I get? I was on Android 4.0.3 Sense 4.0, can I download jellybean with Sense 5.0,
and install it via TWRP?
That was my goal all along, but I'm determined to get S-OFF working, so if doing that means my phone gets wiped again,
I guess I just want whatever ROM/recovery/whatever that allows me to change this USB debugging setting,
and try other phone-related fixes to the MTP driver issue.
First of all, flash an ICS rom. I'm assuming that you are still using the same ICS firmware, and you will want to have your phone operational (to enable USB debugging). The link for MeanRom ICS still works. http://old.androidfilehost.com/main/EVO_3D_Developers/mikeyxda/LTEvo/MeanROM-ICS-v65-jewel-ltevo.zip
Ok....since you are on the old HBoot, I think that you need to use the older S-Off methods (LazyPanda or DirtyRacun), if I'm not mistaken. You can not download and flash Sense 5.0 through TWRP as of yet, because you need to be using the new firmware to do so. You may want to pay http://unlimited.io/jewel.htm a visit. Also, to use LazyPanda or DirtyRacun, you need to be using Ubuntu. Another option that you have is to use the regular RUU and update directly to Sense 5.0. You will be stock, unrooted, but you can easily use the latest S-Off method.
Lastly, for your rooting/S-Off needs, you can also use a handy-dandy toolkit from @WindyCityRockr that can handle everything that you need to do. I usually encourage manual labor, but there are some exceptions. http://forum.xda-developers.com/showthread.php?t=2436217
Thanks again for jumping in.
I'm getting somewhere, but still so many difficulties.
Fix one thing, break two more.
I finally have a new working rom, but almost against my will it ended up
being CyanogenMod.
The short version:
- unlocked bootloader, got TWRP going, finally got ADB working (don't think it's the right driver,
but whatever, ADB commands work fine), wiped everything... factory reset, Dalvik, external storage.
- Didn't wipe Internal storage, I wiped only /data/ per some post's recommendation.
- I used ADB PUSH to get a few possible roms onto /sdcard/
PJ75IMG_1.13.651.1.zip (failed with "unable to open zip")
(ROM)_Stock_Rooted_OTA_(3.16.651.3)V2.zip (failed with "unable to execute updater binary in zip")
cm-10.2.0-jewel.zip (cyanogenmod) - success!
So, the phone works. It appears to be at least based on android 4.3... and I'm guessing CM, which updates
frequently, has all those OTA updates bundled into it. Any downsides to CyanogenMod?
I could just proceed from here to reinstall my old apps etc.
I'm still not "S-OFF" which annoys me, but I read a post suggesting it's not really that necessary.
The way they put it is, s-off allows you to access partitions so they can be modded,
but nobody is developing anything interesting for those partitions. Like nobody's doing custom radios and such.
Should I still pursue S-OFF anyway?
If so, is there a way to do it with CyanogenMod?
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Should I still pursue S-OFF anyway?
Click to expand...
Click to collapse
Yes! Being S-On is a complete pain in the BUTT when switching AOSP roms. Have you tried to flash the rom that I posted, MeanRom ICS? I'm really trying to get you to stay on Sense, because S-Off and other different tools work so much better while using Sense. AOSP is better after S-Off. But that's up to you.
If so, is there a way to do it with CyanogenMod?
Click to expand...
Click to collapse
I am not sure. You can try if you have the time. I suggest making a nandroid of your CM rom, and try to flash a Sense ICS rom, not JB...yet.
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Click to expand...
Click to collapse
CM might be the issue here, as well as it might not.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Click to expand...
Click to collapse
Yes, TB will still work. There are some apps that might cause the restoration process to freeze, so I suggest killing TB and skipping over the app that froze the process when you return.
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Click to expand...
Click to collapse
If your keyboard preferences was not backed up, then no. If you were using the stock Sense keyboard, then that is a no as well. As long as your texting history was backed up, it can be restored. Texts are not like apps...their data is typically stored in XML files which are readable through any version of Android (2.3+).
I'm still soliciting my help if you need it.
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
CreeDo said:
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
Click to expand...
Click to collapse
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
CreeDo said:
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
Click to expand...
Click to collapse
Can't remember if it wipes or not. Best thing to do is make a backup with TWRP and keep the backup on your external SD card. If it wipes you can always restore your backup.
Sent from my HTC device
Thanks for the help so far guys. I am currently really enjoying Cyanogenmod. I suspect it's eating battery more,
but then against I am on the phone for hours redoing everything that got changed/removed.
Does anyone know if there's a simple way (or even a difficult way) to restore my texts?
Because the app is totally different, and the old text app was the one that came
with the stock rom, I cannot restore it in titanium. But if I could extract even the raw text that'd be helpful.
Get back to Sense, or get someone with Sense to restore it for you, and save it using a different app. Or maybe try using SMS Backup & Restore from the Play Store. I'm not sure if it can read the backups saved through Sense, but it's worth a try. You just have to navigate to the location of the old backup.
It looks like I can import an XML in this messaging app so maybe if sense offers an export to XML option, I'll be set.
Sense is sort of an OS on top of the OS, right?
Can sense be loaded without flashing a new rom? or is it too integrated with the OS?

Categories

Resources