tmobile htc one
So here goes.
i followed all the instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2268963) , no problem at all. i've rooted other phones so i sorta know the drill.
1.) unlock token - no problem done
2.) i installed the twrp recovery and got it working
3.) i downloaded the .zip of the super user, plugged phone into pc, created a folder called SU on my phone, flashed into recovery, installed the su file.
4.) im a tmob user so i went to install the kernals, i went to (http://faux.androidro.ms/m7/jb43/) but was unsure if i needed both of them or one, i downloaded ( m7-faux123-GE-005u.zip ) , installed that on a folder on my phone, rebooted into recovery, wiped and then flashed that.
however now the phone locks up on my splash screen (green htc letteers white back ground).
also of note:
while in recovery when i reboot system it says " No OS installed! Are you sure you wish to reboot?"
if i select yes then it says
"Your device does not appear to be rooted. Install SuperSU now? This will root your device."
regardless of whatever i hit weather to install or not install it goes to the HTC splash screen (htc in green, white background) and freezes, at bottom in red it says
"this build is for dev purposes only yadda yadda yadda"
it never advances from this screen.
i cant get my pc to recognize my phone while in recovery to copy over cyanogen 10.1 and gapps so that i can flash those. i am stuck.
anyone got any suggestions?
Hatebreeder5150 said:
tmobile htc one
So here goes.
i followed all the instructions in this thread (http://forum.xda-developers.com/showthread.php?t=2268963) , no problem at all. i've rooted other phones so i sorta know the drill.
1.) unlock token - no problem done
2.) i installed the twrp recovery and got it working
3.) i downloaded the .zip of the super user, plugged phone into pc, created a folder called SU on my phone, flashed into recovery, installed the su file.
4.) im a tmob user so i went to install the kernals, i went to (http://faux.androidro.ms/m7/jb43/) but was unsure if i needed both of them or one, i downloaded ( m7-faux123-GE-005u.zip ) , installed that on a folder on my phone, rebooted into recovery, wiped and then flashed that.
however now the phone locks up on my splash screen (green htc letteers white back ground).
also of note:
while in recovery when i reboot system it says " No OS installed! Are you sure you wish to reboot?"
if i select yes then it says
"Your device does not appear to be rooted. Install SuperSU now? This will root your device."
regardless of whatever i hit weather to install or not install it goes to the HTC splash screen (htc in green, white background) and freezes, at bottom in red it says
"this build is for dev purposes only yadda yadda yadda"
it never advances from this screen.
i cant get my pc to recognize my phone while in recovery to copy over cyanogen 10.1 and gapps so that i can flash those. i am stuck.
anyone got any suggestions?
Click to expand...
Click to collapse
Well did you flash a ROM or not? It says in Step 2 at the end you HAVE to flash a ROM
z0phi3l said:
Well did you flash a ROM or not? It says in Step 2 at the end you HAVE to flash a ROM
Click to expand...
Click to collapse
I don't see where you are reading that. step 2 is all about getting a recovery up and running. no i did not flash a rom which is why i am where i am. if i had a rom to flash i wouldnt get the "no os installed" message.
installed sdk and used adb push to force rom and g apps onto phone, flashed through recovery, all is well.
Related
Hey guys,
I am doing this rom flash for a mate of mine.
I am trying to flash the tastyginger rom, but i am having some real difficulties while flashing the rom.
He has a dutch htc hero from hi. He has the latest rom according to the update utility thingy. it is the 2.1-update1 version. i believe i've read something about nand locks, and i think his phone has exactly that. the first step to flash a new rom is to root the phone. Rooting the phone works, gives no errors.
But when i try to flash the recovery image, it says it cant find the flash_image file.
it is should be located in the system folder on the phone but it isn't. i've tried to install it with android sdk, but the thing just is really acting weird. htc sync isn't working with the phone. it says there isn't a phone in the usb.
Now to make it clear, can somebody give me a clear tutorial on how to flash the thing correctly? I've done this before on my hd2. i've flashed the cyanogen 2.6 rom to my phone.
have you tried rom manager to flash rom its the easiest way i know. the way i rooted was with universal androot apk then installed rom manager clicked on flash clockworkmod recovery then went to install rom from sd card in rom manager scrolled down to the rom i wanted to flash choice it and pressed ok i then select backup existing rom and wipe data and cache and pressed ok then it will ask reboot and install and press ok and let it do its thing then wait untill it reboots and it should of installed rom which you wait to boot should have a custom splash screen that comes up and wait until your prompted to input details and such. hope this helps.
hey, thanks for the advice.
i let him try this method, but when he chose the htc hero gsm to install the cwm, the app refused to install it and gave this error message:An error occured while attempting to run privileged commands.
I forget to mention that the method you posted, that we already tried it.
But thanks for the effort!
pretty certain this is the tut. i used, i also had to use the gold card method -.-;
http://forum.xda-developers.com/showthread.php?t=645253
rom manager has been down lately everyone has had trouble flashing clockwork recovery, but ra recovery second from bottom is a secondary choice however other features of rom manager might not work if you use this you will have to boot into recovery manually.you also need super user to use this as well.
http://zenthought.org/content/project/flashrec
Use this apk, i have always used this method!
Download clockwork or ra recovery rename it to recovery.img and copy to sdcard
Backup recovery with flashrec
then type sdcard/recovery.img
flash recovery and done!
I've done the recovery succesfully at the guys phone. It works bloody well. Thanks dudes! You can lock it up if you want to.
Sent from my HTC HD2 using Tapatalk
I have a slight problem with my phone right now. I got the great idea to try and build a rom just for myself in kitchen based off the Telus 1.15.661.11 base. Everything appeared to work correctly, I got my rom flashed and working fine, haven't had any problems with it besides a FC issue with the HTC Sense input but i just uninstalled it as i use swiftkey anyways.
The problem is I can no longer access TWRP, I can get into the bootloader fine just when i select recovery it shows the TWRP logo then goes to a black screen and then proceeds to boot into the system. I have no idea how to fix it and but here's what I've tried so fair:
-Reflashing the recovery via fastboot
-Flashing a rom via fastboot (Can't be done gives me some remote denied error, i assumed because its still s-on?)
-Reflashing boot.img via fastboot (Figured it was worth a attempt?)
-Trying to reboot into recovery (Same thing happened, went from black screen to boot. Also i should note I could not get the phone to reboot via adb but could via the cwm rom manager (I just used it to reboot nothing else))
-Factory Reset from bootloader (didn't appear to do anything)
The one thing I have not tried is an RUU, however this was because first off i had difficultly locating one (I had the link somewhere but lost it) and second I don't think there is one for Telus (Although i would assume an ATT one would work?). Also ill try to locate the rom that i flashed, and maybe someone would be able to look at it and see what went wrong. Any help/ideas would be greatly appreciated to try and help restore my recovery.
EDIT: So i ran the ATT RUU and it failed towards the end of the process and I went through the recovery process. Then i re locked and unlocked my bootloader and after that i went to reboot into recovery and it works again. So im not sure what happened but if anyone has some insight it would be nice to know for the future.
So I wanted to root my EVO 4G LTE, and I unlocked the bootloader, and then I did moonshine to get S-OFF. The ADB worked fine before that, but every rom I tried to flash didn't get past the boot screen. I looked on here for help and saw stuff about a boot img but since I couldn't get into the ADB I couldn't do anything. So, I decided to do use VipeRUU to get back to where I was in the beginning and try to get back to a stock rom. VipeRUU never could recognize my device so I had to do that bypass method, so I did get to S-ON and have the bootloader unlocked without saying tampered. Also, every time I try to connect my phone to my computer by USB I get the message saying USB Device not recognized. I don't know why that is happening. I can't get into the ADB, if I try to open it, it just flashes for a second running through some text and then instantly closes. Maybe I don't have drivers or something? However, I don't remember deleting anything of the sort.
Now I want to do either one of these things:
1. Just return the phone to how it was before I even tried to root it in the first place.
2. Help me get it back to a standard root that I can use and connect to my computer without issue and still get into my bootloader and potentially flash a decent rom.
I know a lot of these problems exist individually on here, but I feel like I have a specific issue, so I don't really know where to approach this from. All help is appreciated.
Download MeanBean ROM to your computer. Boot into recovery and hook your phone up to your PC. Use the mount setting in recovery to mount either your internal or external storage to your PC then put the ROM zip on your phone. Unmount once you finish transferring the file to your phone. Do a system wipe in recovery (if you're using TWRP 2.6.0.0 choose the Advanced wipe option and select cache, Dalvik cache, Data and System) then flash the MeanBean zip. Once it finishes choose the option to reboot your phone. The phone will boot to the HTC splash screen, then it will reboot into recovery mode. Flash the ROM zip again, and reboot. Let it do its thing and the phone should boot up in a few minutes. Also, check out the link in my sig-it has some useful information contained in it and even has links for the HTC drivers and an easy to follow guide on how to setup ADB on your computer. I also recommend getting S-off:thumbup:
Sent from my EVO using XDA Premium 4 mobile app
I decided to flash a factory image since the GPS was not working anymore with whatever ROM I tried, plus random problems. The phone was previously set up with CM10.1 and BMM.
Installed RSD Lite, Moto drivers, downloaded several stock ROMs.
From the factory recovery mode I cannot flash any of those zip files so I proceed with RSD lite. I flashed "9.8.2O-124_SPUEM-14_S7_USASPDRICS01O2UKE1007.0R_USASPDRJBO2GB_P013_A012_p2b_S1FF_fb.xml.zip" which is a retail UK JB image. The phone shows the very first boot screen (red logo) and then the screen goes blank. The computer still sees an MTP device, though only in device manager.
I've tried installing other images but they are an older type (ICS I guess, 01.6.7.2-180&01.6.5.1-167) and RSD shows an error while trying to flash the first file from the archive.
Oh, I still have the "Customer error: contact dealer" on the first boot screen, I think this was from a ICS to JB upgrade with CID deletion(?).
I've already flashed twice using RSD, deleted cache+data, rebooted and left the phone to start up for ten of minutes, don't know what to do. RSD lite reports that flashing was ok.
been there
brainwash123 said:
I decided to flash a factory image since the GPS was not working anymore with whatever ROM I tried, plus random problems. The phone was previously set up with CM10.1 and BMM.
Installed RSD Lite, Moto drivers, downloaded several stock ROMs.
From the factory recovery mode I cannot flash any of those zip files so I proceed with RSD lite. I flashed "9.8.2O-124_SPUEM-14_S7_USASPDRICS01O2UKE1007.0R_USASPDRJBO2GB_P013_A012_p2b_S1FF_fb.xml.zip" which is a retail UK JB image. The phone shows the very first boot screen (red logo) and then the screen goes blank. The computer still sees an MTP device, though only in device manager.
I've tried installing other images but they are an older type (ICS I guess, 01.6.7.2-180&01.6.5.1-167) and RSD shows an error while trying to flash the first file from the archive.
Oh, I still have the "Customer error: contact dealer" on the first boot screen, I think this was from a ICS to JB upgrade with CID deletion(?).
I've already flashed twice using RSD, deleted cache+data, rebooted and left the phone to start up for ten of minutes, don't know what to do. RSD lite reports that flashing was ok.
Click to expand...
Click to collapse
Did you erase CID?
if you did yo need to boot in a different way
U did a factory reset in stock recovery? U cannot flash a ics image after flashing jb via rsd. Try again jb EU image than go to stock recovery and perform the wipes
Tapped from my RazR
Got it "fixed", finally. I had to go back into the stock boot/recovery menu and choose "BP Tools", last option from the menu and then it booted normally.
I still have to do this after each reboot because it boots to the black screen: hold the three buttons together until it flashes (which means a hard reboot), let go of the power button, press power button again while the other two are still pressed.
On the plus side the GPS started working again after factory reflash which it was kind of expected since the same chip is providing also WiFi and bluetooth which were running fine.
I have a root question: the device was rooted with the virtual machine procedure but after a factory reset the root was lost. I had saved it using Voodoo RootKeeper and the app shows: superuser installed, device rooted, /system supports root protection, protected su available. The "root permission granted" checkbox is disabled though and no application is able to retrieve the root. The su binary is in both /bin and /xbin so I don't understand how it can not function.
Edit: ok, got it, the su binary has -rwsr-sr-x and the owner is root so random users cannot execute it. I also cannot change the permissions so I probably have to root again and figure out a way to keep the root after a factory reset. It makes sense to install BMM since it can take care of permissions.
Hello,
I come for you, because I am trying to install android 4.4 on my phone, because android 4.3 isn't compatible with pokemongo.
I have a galaxy s3 GT-I9300 from a few years, I've never rooted it and it runs on android 4.3.
I've been looking for guides that say that I need to install CWM recovery to then be able to install CyanogenMod.
So I've downloaded Odin, and CWM recovery, added the CWM recovery .tar in the AP box of Odin, put my phone on download mod, plugged it, and run Odin.
It appears that it works succesfully, but when I reboot my phone in recovery mode, I still have Android Recovery System <e3>, and I can't install zip from sdcards (if I understood correctly, <e3> doesn't support zip, whereas <e2> does, and CWM is supposed to put it to <e2>), so I can't install CyanogenMod.
Here is a screenshot of my Odin after running it: (I can't post the link since I'm a new user, so it's on imgur)
/87oPm2l
I can't think of any more information to provide for now.
Thanks for your help.
chocolote4444 said:
It could be permission issues. But try using a different cable.
Also, the recovery you are flashing has to support the model of the phone, otherwise, Odin will refuse to install it.
Click to expand...
Click to collapse
Thanks for the answer, I was not in root mode.
I fixed it and it now works, I have been able to install CyanogenMod from the zip in recovery.
Now I tried restarting my phone, and it's stuck in "Android is starting".
I have a little blue alien popping on my screen, then the screen turns off, then the screen turns on and says things like "starting applications, preparing settings, optimizing applications". But it seems to be doing it on repeat and it's been an hour. Is it normal that it takes so long? I haven't seen it mentionned anywhere from what I checked.