Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000
taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Malybru, i do have a router but my wifi wont turn on so i cant connect to it.
T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves
ta gane shp, this is a good place with good people
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.
Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.
malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though
Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up or go to recovery… well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, have found a way to unbrick your device! after bricking my phone and finding different ways how to do it...
Because we are not able to swap or get the sdcard out from the phone, it makes it difficult on how to add a ROM.zip and re-install. Another issue I found is that CWM will not be able to read the sdcard if you do an adb push ROM.zip /sdcard/ROM.zip or by mounting the sdcard adb shell mount /sdcard . If you have this issue will explain later
So let's get started.
Step 1: Turning Off Your Phone and Reboot to Boot-Loader
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to turn off by pressing the volume down + power button until the phone shuts off then turn on to boot-loader by pressing volume down and press for 3 seconds the power button. once in boot-loader select fastboot.
Step 2: Adb push to SD card
I assume that you have install CWM, if you don't you can download it from HERE. Once downloaded install CWM fastboot flash recovery CWM.TOUCH.5.8.3.1.img, where your done go back to boot-loader and select recovery. Once in recovery do an adb push of a ROM, in this example I used "Energy ROM" you can get the ROM from HERE. Once you have your ROM rename ROM.zip and push adb push ROM.zip /sdcard/ROM.zip, you will get a message stating the size of the the push.
If you can't do a push because you got an error message will explain later.
Step 3: Wipe The Phone
Make sure to do a Factory Reset / Wipe before installing ROM
Step 4: Reboot back to fastboot
Once you install the room you will need to make sure you have a boot.img for the ROM your using.
adb reboot bootloader
fastboot flash boot Recoveries/boot.img
YOUR DONE
If your the unlucky one's that can't do an adb push to the SD card do the following.
- Reinstall STOCK Recovery fastboot flash recovery recovery.img
- Lock OEM fastboot oem lock
- Unlock OEM fastboot flash unlocktoken Unlock/Unlock_code.bin
- Reinstall CWM Recovery fastboot flash recovery CWM.TOUCH.5.8.3.1.img
That should fix the problem on how to push back to the sdcard
If you have other methods post them below...
Sticky!!
But this won't work if you flash a wrong radio, will it? I thought that if you flashed a wrong radio, you couldn't get anything done, even not booting into bootloader, because it boots the radio first?
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
This tutorial already exists as a sticky in the Q&A section:
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC VLE_U using Tapatalk 2
Nice writeup.
For every new Phone I own, the first thing I do after flashing a Custom Recovery is Making a Nandroid Backup of the stock Rom. If something goes wrong after flashing a bad rom I just restore to Stock rom.
A real life Saver for me.
snwman said:
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
Click to expand...
Click to collapse
It worked for me when I bricked my phone and had to find ways how to be able to load a ROM back to the SDcard and reflash it...
This is a combo of a tutorial cannondale wrote and one I wrote myself.
His is stickied in Q&A section, mine is in Android Dev section...
Not sure why this is here lol.
i get the error 155 when trying to install the RUU
420haxr said:
i get the error 155 when trying to install the RUU
Click to expand...
Click to collapse
Try to relock your bootloader first.
In fastboot:
fastboot oem lock
Sent from my HTC One S
Issue
Ok, still running into an issue. No errors when I push, I locked, unlocked, tried everything again. Reset everything, installed fresh CWM, tried it all over...
What's happening is that it's saying it pushed the file over, but I can't find it anywhere after it's done. This happened the first time I installed custom...I just can't remember what I did to get it to work...
Anyone has the link of stock recovery for HTC One S z560e(ville c2)?? i get error 155 when i try to install with RUU.
After i flash the cwm touch recovery I cant boot into recovery... my phone is stuck on the HTC boot logo with the red text underneath. Is it a problem with recovery or should i try install an RUU. My phone is HTC One S villec2 (S3).
I am hoping that I can find help out there. My phone will not load past the splash screen.
Over the last few days I have been trying to install a custom rom on my phone. I thought I was on the right track and now I have flashed it but it will not go past the splash screen. I would be grateful for any advice on how to get my phone back functioning. I would even be happy to have it back stock.
So my movements over the last few days have been as follows:
1) HTC DEV unlocked the bootloader
2) Used Hasoon2000's HTC Sensation 4G all-in-one to flash CWM.
3) Then the same tool to copy Prem Root onto the SD card and installed it via CWM.
4) Then used this post here to install JB Miui - http://miuiandroid.com/community/threads/how-to-update-upgrade-miui.15424/
Then when I rebooted it is stuck on the Miui splash screen.
At every stage I felt like things worked well and now I have that sad feeling in my stomach because I have just realized how vital my phone is.
Any help would be greatly appreciated.
Did u flash boot.img after u flashed the rom? Did u full wipe before flashing the rom? Also with s-on users its recommended to use 4ext recovery and in recovery, enable smartflash.
Where can I find information about boot.img - so that is a no. I am installing 4ext now.
jmcclue said:
Did u flash boot.img after u flashed the rom? Did u full wipe before flashing the rom? Also with s-on users its recommended to use 4ext recovery and in recovery, enable smartflash.
Click to expand...
Click to collapse
ok, so I have been looking at the boot.img part and I found this video: http://www.youtube.com/watch?v=5xVl2dBTnmI
I have followed it but still am not having any luck.
Still very lost.
LiamRutherford said:
ok, so I have been looking at the boot.img part and I found this video: http://www.youtube.com/watch?v=5xVl2dBTnmI
I have followed it but still am not having any luck.
Still very lost.
Click to expand...
Click to collapse
open rom.zip and search for the boot.img
probably it is located in the kernel folder
place it in the folder where you have adb and fastboot files
now boot your device to the bootloader and connect it to pc via usb(in the hboot screen it should say fastboot usb)
in the folder where you have adb and fastboot files open a cmd window and do this command
fastboot flash boot boot.img
then
fastboot reboot
done
rzr86 said:
open rom.zip and search for the boot.img
probably it is located in the kernel folder
place it in the folder where you have adb and fastboot files
now boot your device to the bootloader and connect it to pc via usb(in the hboot screen it should say fastboot usb)
in the folder where you have adb and fastboot files open a cmd window and do this command
fastboot flash boot boot.img
then
fastboot reboot
done
Click to expand...
Click to collapse
Thanks - this did the trick. Now to hunt out roms.
LiamRutherford said:
Thanks - this did the trick. Now to hunt out roms.
Click to expand...
Click to collapse
as suggested before it is better to have 4ext recovery
and before flashing any rom enable smartflash from it(for S-ON devices)
smartflash it does exactly what i said above
Hello,
I have a big problem with my old HTC Sensation.
I tried nearly everything out of other topics, but nothing worked....
The story: Suddenly my Sensation rebooted and from then on it is stuck in an endless bootloop.
The bad thing is, that it was stock/S-ON at this moment.
Informations about the phone:
***UNLOCKED***
Pyramid PVT Ship S-ON RL
HBOOT: 1.27.0000
Radio: 11.24A.3504.31_M
-> I am able to install RUUs (3.33), but after installation i am still in the bootloop
-> I am able to unlock/relock the bootloader
-> I can install a recovery via fastboot, but can't boot into it => bootloop
Maybe you have got a hint to bring the Sensation back to life.
Thank you!
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
kevinspl2000 said:
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
Click to expand...
Click to collapse
actually he can't even boot to the recovery in order to flash any rom
so what's the point of flashing the boot.img manually?
You can use Sensation all in one kit v3 to unlock boot loader, read this thread for more detail
http://forum.xda-developers.com/showthread.php?t=1497404
after unlocking boot loader, then go to this thread to download 4EXT recovery then use kit to flash recovery, remember to download image file, not zip file
http://forum.xda-developers.com/showthread.php?t=1377759
boot to recovery, then enable smart flash and flash any cook ROM you want. Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
stripeqn said:
Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
Click to expand...
Click to collapse
actually first has to wipe and then enable smartflash
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
BrainyTheKing said:
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
Click to expand...
Click to collapse
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
kevinspl2000 said:
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
Click to expand...
Click to collapse
I erased the cache before and after flashing recovery.
No success ...