Related
Hello to all,
For some reason my HTC Sensation won't boot - it keeps on rebooting on the white htc screen.
It started doing this 1-2 weeks ago. Yesterday I managed to get inside the ClockworkMod Recovery somehow from HBOOT, and restored an old backup. Then I installed a newer radio and [ROM] Android Revolution HD 6.7.2 (the page recommended updating the radio). I also flashed the 4EXT Touch recovery, as it was required by this ROM, so I changed from Clockwork to 4EXT. The device worked for 1-2 hours, and then after one restart, it wouldn't boot again. This time I can't access anything but HBOOT and FASTBOOT.
Of course ADB doesn't work as I can't boot the device.
So the question is - what shall I update via fastboot "fastboot update update.zip" so that I restore my device? Or what file shall I put on the SD Card so that HBOOT can recover it (I have access to other devices, so I can place something on the SD card)?
I've been trying to flash various ROM's and RUU's but all of them give an error.
The configuration inside HBOOT says the following:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-v02.6.0.2226.00.0104
eMMC-boot
Jan 12 2012,17:33:34
I also tried flashing a few recoveries via fastboot (clockworkmod recovery.img and 4ext recovery.img), but could get inside them :/
Let me know what else could I do.
Thanks for the support!
I just managed to get to the ClockworkMod recovery and installed a new ROM - OpenSensation. It worked during the first boot, but then when I rebooted the phone - the same thing happens - it keeps on rebooting on the htc white screen.
Of course I can no longer go to the ClockworkMod recovery.
I also notice that when going back and fourth between HBOOT and FASTBOOT menus, at the top the version for RADIO appears and disappears.
I am not sure if all this is a hardware or software problem, but it is strange that from time to time I manage to get to a recovery and install a ROM which works for a while and then sends me back to this rebooting loop.
Any ideas?
Thanks!
Might be a hardware failure but.. First try ruu and restore to complete stock. Most of the times this fixes the issue..
For finding and flashing a ruu.. Look for ruu info guide by kgs1992 in sensation general section
Sent from my HTC Sensation 4G using xda premium
Thanks for the help. I managed to install successfully the following RUU:
RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed
but it didn't work... it installed successfully, but the phone keeps on restarting on the white htc screen.
I figured that might be because of the firmware installed (I was on Android 4.0.x), so maybe this RUU is older.
I am downloading right now:
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_R_Radio_11.69.3504.00U_11.22.3504.07_M_release_252064_signed.exe , which definitely must be Android 4.0.x so I hope it works.
Thanks for the help and thanks to kgs1992
Ruu is complete rom.. It has everything In it.. When you run ruu you shouldn't consider the firmware, recovery etc etc.. It has everything built in
So when you flashed the gb ruu.. It flash stock recovery, stock gb firmware and stock rom
So when you flashed gb ruu it has turned to complete gb rom.. Anyways less hope that the ICS ruu works fine
Sent from my HTC Sensation 4G using xda premium
Somehow I thought that the firmware is separate, although I wasn't sure.
Anyway - the fact is that after a successful RUU update, the phone keeps on rebooting and couldn't boot even once. I hope the next RUU fixes it.
thanks,
Anton
Still doesn't work after trying a second RUU: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.6_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_266171_signed.exe
The bootloader says:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
Any ideas?
thanks,
Anton
try a AOSP ROM/CM9/CM10 lot of people had these kind of issues and they can boot only to a non sense roms ..may be you could boot fine on non-sense roms too
How would I flash CM9 CM10 or any AOSP, when I have access only to "fastboot". So far I could only flash those RUU-s from a Windows machine, as I can't get to any recovery.
Would it work if I try "fastboot update cm9.zip" or something similar?
Thanks,
Anton
nonsens3 said:
How would I flash CM9 CM10 or any AOSP, when I have access only to "fastboot". So far I could only flash those RUU-s from a Windows machine, as I can't get to any recovery.
Would it work if I try "fastboot update cm9.zip" or something similar?
Thanks,
Anton
Click to expand...
Click to collapse
Fastboot update command won't work
As you are soff.. You can flash jbhboot or 3.33 universal firmware with every thing removed except hboot_xxxx.nb0 file.. And unlock the hboot first
Then flash a recovery (you can avoid hboot flash and try a PG58IMG.zip file of recovery) from fastboot
Then from.. Recovery flash the cm9 or any AOSP rom
If you can't boot to recovery even after flashing the recovery fine.. Then try this command
fastboot boot recovery.img
(it boots into recovery temporarily.
From there you will flash a rom)
Sent from my HTC Sensation 4G using xda premium
nonsens3 said:
How would I flash CM9 CM10 or any AOSP, when I have access only to "fastboot". So far I could only flash those RUU-s from a Windows machine, as I can't get to any recovery.
Would it work if I try "fastboot update cm9.zip" or something similar?
Thanks,
Anton
Click to expand...
Click to collapse
You can try using Fastboot Commnder
Instructions:
-download tool
-unpack zip and click on .exe application (is a stand alone app, so you have to click and confirm installation, that's all!)
-open tool
-put DHD in "Fastboot Mode"
-plug it to your pc usb
-Wait for "print of device succesfull"--(if fails, check your sdk driver)
-here you go to "misc"
-select: erase partitions (system,cache,userdata,boot) Don't select recovery
-click on "Erase chosen partition"
-Done
You can use this tool to flash a new ROM or even to flash a recovery.img
Your problems might also come from not flashing the correct recovery.
Make sure you have the latest version. Good luck
Hey you guys, my friend dropped her phone and it went into bootloop. She was using some old ARHD Rom. She then wiped her phone somehow (not sure what she did). I ended up installing the insertcoin 2.3 (sense 4) rom I am using on my phone but its still stuck in bootloop. I can access the 4ext recovery.
Bootloader info is:
Pyramid PVT Ship S-Off RL
HBOOT - 1.27.1100, Radio - 11.24A. 3504. 31_M
OpenADSP - v05.6.0.2226.0.0418
eMMC - boot.
Please any help on how to get it back to stock or any running rom would be much appreciated.
We need more details .....which kernels did you flash ??
I didn't flash any kernals separately, just the one that came with insertcoin 2.3.
http://insertcoin-roms.org/2012/08/insertcoin-evolution-sense-4-v2-3-sensation/
That has all the information about the rom I flashed.
sagarsaoji said:
I didn't flash any kernals separately, just the one that came with insertcoin 2.3.
http://insertcoin-roms.org/2012/08/insertcoin-evolution-sense-4-v2-3-sensation/
That has all the information about the rom I flashed.
Click to expand...
Click to collapse
Hi,
Try starting again from scratch.
Run a RUU.
Look HERE
malybru said:
Hi,
Try starting again from scratch.
Run a RUU.
Look HERE
Click to expand...
Click to collapse
I flashed a RUU through the rom.zip. The process seemed to be stuck at step [4] System for quite a while, kept unzipping and updating over and over again. It eventually completed but now I'm stuck in bootloop with a large BEEP sound after "htc simply brilliant" screen, then phone reboots and have to pull the battery out. PLEASE HELP ME
Did you install stock kernel ??
Because some roms need specific kernels which only work on the Rom and your going to stock so its not gonna boot
sagarsaoji said:
Hey you guys, my friend dropped her phone and it went into bootloop. She was using some old ARHD Rom. She then wiped her phone somehow (not sure what she did). I ended up installing the insertcoin 2.3 (sense 4) rom I am using on my phone but its still stuck in bootloop. I can access the 4ext recovery.
Bootloader info is:
Pyramid PVT Ship S-Off RL
HBOOT - 1.27.1100, Radio - 11.24A. 3504. 31_M
OpenADSP - v05.6.0.2226.0.0418
eMMC - boot.
Please any help on how to get it back to stock or any running rom would be much appreciated.
Click to expand...
Click to collapse
IS the Phone S-OFF?
This step is extremely important, because we are not s-off and there is a problem with creating the "boot.img". T-Macgnolia explained it nicely:
When you use HTC Dev to unlock your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read those partitions. But there 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 .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 the New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just what thee 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 something called a Linux kernel. This means that your bootloader boots the Linux kernel and the hardware of the device. The Linux kernel then boots the Android OS. The kernel is also the connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on the 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 the ROM or you will more than likely have troubles.
Click to expand...
Click to collapse
There are 2 ways to enable smartflash, one is a temporary way inside the 4EXT recovery itself (only for first time!) and the second way is permanent, through the 4EXT application.
The permanent way can only be enabled if your phone has ROOT! It's impossible to do it when you are going to flash a ROM for the first time.
Once you have flashed your ROM you have to install the 4EXT application and enable smartflash through it, which is explained in Step 5.
3A. Enable 4EXT Temporary smartflash
Enabling this is as simple is getting into the recovery and enabling it as an option.
NOTE: You only need to do this right before flashing your first ROM, so you should skip this step and come back here when the guide tells you to.
Disable "Fast Boot" on your phone.
Code:
Settings
Power
Untick "Fast boot"
Turn off your phone
Hold the Power AND Volume Down button until you see a white screen which says: "Fasboot".
Navigate to "RECOVERY" and select it, you should now boot into the 4EXT recovery
Select "Tools"
Scroll Down and select "Enable 4EXT SmartFlash"
Again, you only need to do this ONCE, once you have flashed your first custom ROM and enabled permanent smartflash, you don't need to this any more!
Click to expand...
Click to collapse
Source
Hope I am not talking nonsense
wetfoot said:
IS the Phone S-OFF?
Source
Hope I am not talking nonsense
Click to expand...
Click to collapse
The phone is S-Off but now it says "locked" on top in purple where as it used to not before. Also should I flash kernel before or after flashing RUU rom?
Sure thing .......
Do you know how to get the stock kernel from the ruu ?
sagarsaoji said:
The phone is S-Off but now it says "locked" on top in purple where as it used to not before. Also should I flash kernel before or after flashing RUU rom?
Click to expand...
Click to collapse
Hi,
The RUU contains a stock ROM ,recovery,kernel,firmware,and radio.
It should be the only thing you need to flash/run.
I do not know why the RUU did not work.
Now that it is "Locked", then you cannot flash an RUU with version less than your phone's current version.
The RUU should reset all your partitions,(Except s-off), and restore your phone to stock.
If your current version is the same as the RUU,try running it again by doing it manually (section 4 in the guide)
Section 4 of what guide (sorry for being this confused).
Also tried flashing other kernels and got assert failed: write_raw_image("/tmp/newboot.img", "boot") error
I ended up reinstalling CWM recovery, don't know how to get 4ext with just the bootloader...if there is any way possible I'd be willing to try the Smartflash option.
EDIT: just some further info...can't get adb to find device even though it is in fastboot usb mode..any way to get that working?
sagarsaoji said:
Section 4 of what guide (sorry for being this confused).
Also tried flashing other kernels and got assert failed: write_raw_image("/tmp/newboot.img", "boot") error
I ended up reinstalling CWM recovery, don't know how to get 4ext with just the bootloader...if there is any way possible I'd be willing to try the Smartflash option.
Click to expand...
Click to collapse
Hi,
The guide I mentioned in my first post ( HERE )
Flashing a kernel will not achieve anything.
Using smartflash if you are s-off,will not achieve anything.
malybru said:
Hi,
The guide I mentioned in my first post ( HERE )
Flashing a kernel will not achieve anything.
Using smartflash if you are s-off,will not achieve anything.
Click to expand...
Click to collapse
Still not booting, making a beep after "simply brilliant" screen and reboots constantly. I was able to get ADB to finally work. I also followed Step 4 from the guide but even after the RUU flashes completely the phone is stuck in bootloop.
Okay so here is what happened i unlocked my bootloader and rooted my phone using the all in one toolkit, i tried to flash a custom ROM using the GooManager app. This is where things went wrong. After flashing the ROM my phone shut off and would only turn on to the HTC Quietly Brilliant page at the beginning of the boot cycle, i made a backup but dont know how to find it. I somehow managed to wipe the entire phone and now i have no operating system. I had TWRP installed but cannot access it because i relocked the phone. Is there anyway to get this thing working again? any help would be much appreciated
here is what my fastboot screen reads:
***TAMPERED***
***RELOCKED***
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
brenntard said:
Okay so here is what happened i unlocked my bootloader and rooted my phone using the all in one toolkit, i tried to flash a custom ROM using the GooManager app. This is where things went wrong. After flashing the ROM my phone shut off and would only turn on to the HTC Quietly Brilliant page at the beginning of the boot cycle, i made a backup but dont know how to find it. I somehow managed to wipe the entire phone and now i have no operating system. I had TWRP installed but cannot access it because i relocked the phone. Is there anyway to get this thing working again? any help would be much appreciated
here is what my fastboot screen reads:
***TAMPERED***
***RELOCKED***
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
FASTBOOT
to previous item
to next item
to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
Since you are s-on, you need to fastboot flash boot boot.IMG from the ROM you want to use. While you're at it you may as well just s-off your device. It will make things simpler in the end. You're going to have to unlock the boot loader again to flash the boot image though. You will also want to flash recovery again via fastboot.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Since you are s-on, you need to fastboot flash boot boot.IMG from the ROM you want to use. While you're at it you may as well just s-off your device. It will make things simpler in the end. You're going to have to unlock the boot loader again to flash the boot image though. You will also want to flash recovery again via fastboot.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so much for the response...i have a couple questions. I am fairly new to android and these are the first real problems i have run into that i havent been able to solve on my own. how do i "fastboot flash boot boot.IMG"? i just want to use the stock ROM or CM10 which ever will get my phone running again. I have unlocked to bootloader again and now have access to TWRP
brenntard said:
Thank you so much for the response...i have a couple questions. I am fairly new to android and these are the first real problems i have run into that i havent been able to solve on my own. how do i "fastboot flash boot boot.IMG"? i just want to use the stock ROM or CM10 which ever will get my phone running again. I have unlocked to bootloader again and now have access to TWRP
Click to expand...
Click to collapse
Take a look at this thread
http://forum.xda-developers.com/showthread.php?t=2136172
It will answer many of the questions that you have and provides links to appropriate tools.
You should definitely s-off your device now. Just look for the question in the thread I linked for more detail. Bookmark it as well, or add it to your favorites, as it will provide a great reference point for future use.
Once you have s-off, you will just have to flash any ROM you want from recovery. It will make your life way easier.
If someone helps you, just hit the thanks button, or thumbs up from the xda app.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Take a look at this thread
http://forum.xda-developers.com/showthread.php?t=2136172
It will answer many of the questions that you have and provides links to appropriate tools.
You should definitely s-off your device now. Just look for the question in the thread I linked for more detail. Bookmark it as well, or add it to your favorites, as it will provide a great reference point for future use.
Once you have s-off, you will just have to flash any ROM you want from recovery. It will make your life way easier.
If someone helps you, just hit the thanks button, or thumbs up from the xda app.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In the rumrunner instructions to s-off my device it says i need to have fast boot unchecked in settings. I am pretty sure i have it checked but there is no way for me to tell for sure...since i dont have an OS installed is this an issue?
brenntard said:
In the rumrunner instructions to s-off my device it says i need to have fast boot unchecked in settings. I am pretty sure i have it checked but there is no way for me to tell for sure...since i dont have an OS installed is this an issue?
Click to expand...
Click to collapse
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
timmaaa said:
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
Click to expand...
Click to collapse
Okay I was able to flash the boot.img but can't figure out how to flash the rom.. Should I do it through recovery? Or through a fast boot command prompt like the one used to flash the boot.img
timmaaa said:
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
Click to expand...
Click to collapse
This may go with out saying but when I'm in recovery and hit the reboot button and try to select "system" it comes up with a message telling me I have no OS installed and asks if I want to continue anyway..
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
timmaaa said:
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
Click to expand...
Click to collapse
How do i get the ROM onto my phone? that might be a stupid question but i am stumped
brenntard said:
How do i get the ROM onto my phone? that might be a stupid question but i am stumped
Click to expand...
Click to collapse
Mount your sdcard through TWRP. You should then be able to drag and drop the file from your computer to your sdcard. It should go without saying that your phone needs to be connected to your computer.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Mount your sdcard through TWRP. You should then be able to drag and drop the file from your computer to your sdcard. It should go without saying that your phone needs to be connected to your computer.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i cant mount my sd card, i can put a little x by cache data and system but not sd card...
timmaaa said:
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
Click to expand...
Click to collapse
i was unable to do a wipe of my phone. in twrp i went to wipe and "swipe to factory reset" it ran through and came back as failed..
Try to format your sd then (from recovery)
Gesendet von meinem Xperia Neo V mit Tapatalk 2
What ROM did you flash with Goo Manager?
You mount the sd card by going into the mount menu, then using the mount usb storage option.
Sent from my Evita.
I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!
ps.christos said:
I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!
Click to expand...
Click to collapse
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita
timmaaa said:
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita
Click to expand...
Click to collapse
There are some changes of the planes and because of lack "playing" with my mobile i haven't reply you. So i desided to go for CyanogenMod 11.0 so instractions are:
" 1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU or later.
3.Flash a custom recovery (TWRP/CWM with SELinux capabilities).
4.Download latest nightly from http://download.cyanogenmod.org/?device=evita.
5.Locate 4.4 Gapps via a quick Google search.
6.Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
7.Reboot into recovery and install nightly and gapps."
Before the instraction i think i should root and unlock the bootloader, so i used "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" to unlock bootloader and root the phone. I have done this. I will (haven't do it yet) s-off and then flash custom recovery. Then it is the easy part i thing, (same as in every device, i have done it to htc desire).
So my question is am i rooted? Some apps like titanium backup and adfree gives me error, that is why i am thinging or i am not rooted or i have to "gain" su access through terminal. For flashing custome recovery i will use "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" and for s-off i will try to use this guide "[S-Off] Facepalm S-Off for HTC One XL" any easier suggestions about s-off??
So to make our life easier here is what i get form power button + volume down:
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita
timmaaa said:
Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita
Click to expand...
Click to collapse
I found what i did wrong so now i have root my mobile! The guide that you posted is very helpfull, thanks for that! One last question though (hopefully last) i still have to go s-off for flashing CyanogenMod 11.0 since it is in the installation procedure right?? Thanks again.
You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita
timmaaa said:
You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita
Click to expand...
Click to collapse
I have done everything exept s-off. So now what i get in the "info" screen is what i had before, but at the begging it says *** TAMPERED *** , root works as well. The thing is i tried s-off using this method "http://forum.xda-developers.com/showthread.php?t=2155071" and i had exactly what it says i mean both in screens and the 92 error, but i always was s-on when system boot to bootloader at the end. I tried more times and after a point i tried the toolkit, from that point error 92 turned to error 99 (unkown error). Now this holds for both ways that i try. Any ideas what i do wrong? By the way i made a backup before starting the whole procedure. Thanks again and sorry for asking, but everything else was solven by reading and i can not reach as many info about s-off as it was for root.
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just show the so wanted s-off. I read somewhere that error 99 will turn to "normal error 92" after rebooting. So yesterday i did 3 reboots and felt to sleep and today i tried the same procedure and now i am s-off! Sorry for the nagging!!
timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok i need your help again, if it is possible. I try to flash cm11 rom and i got the:
"E:error executing updater binary in zip ..........
E: error installing the zip file ......."
So i did my research and i thing the problem is due to recovery, right??
In this threat "[Q&A][CM 10.1][4.2.2] CyanogenMod 10.1 Questions and Help thread"
you have said: " Originally Posted by timmaaa View Post
No you can't use TWRP 2.6, you need to use the unofficial modified version of TWRP 2.6.3.0 from our Original Android Development section."
The thing is i am using TWRP 2.6.3.0 downloaded from here: "http://forum.xda-developers.com/showthread.php?t=1677447" should i go for "http://forum.xda-developers.com/showthread.php?t=2558503"??????
some more details (bootloader details):
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
e-MMC-boot
Thank you very much.
Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita
timmaaa said:
Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita
Click to expand...
Click to collapse
Do you know if there might be a problem with compatibility?? I mean if i try to restore back up made with TWRP 2.5 when i have the unofficial modified TWRP 2.6.3.0??i bet there is a backwords compatibility, right?
thanks again!
From all reports I've seen, they're not compatible. But even if you didn't want to flash KitKat ROMs you should never use TWRP 2.5 because it's super buggy and will cause issues. I'd say just flash the unofficial TWRP 2.6.3.0 and install the KitKat ROM of your choice. If you need to go back to stock there are other ways apart from a backup you can do it.
Sent from my Evita
Hi Guys.
I have a Problem with my HTC One S (ville).
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT 2-15.000
RADIO 1.11.50.05.28
After using the "unofficial" HTC Stock Rom 4.1 with root (Which works sometimes and sometimes not, dont ask me why...), i decided to upgrade.
First I tried Liberty Rom, but after installing my phone was in endless start loop.
So i tried CM (every Version i could find), but after flashing it hang at the HTC Start screen (The One with the Red text).
Then I Tried Viper One S. This was the only one i could start. It runs perfect, except the random reboots. Sometimes every 2 min, sometimes no reboot in one day.
I tried it with TWRP 2.6 and 2.7 and CWM and erverytime the same results: no running OS or a "rebooting-party-OS".
I installed everything with an USB drive connected to the phone via cable.
I tried to get HBOOT 2.16, didnt work.
I tried flashing via ADB, doesnt work. My Computer (win 7) doesnt find the devices.
I tried S-Off, but doesnt work because of ADB-Problem...
I read almost every thread here, but nothing helped...
The Backup of my HTC stock, doesn work. When I restore it, it starts and i have a black screen with only the notification bar and nothing works.
Going back to the orignial RUU's doesnt work. Trying to flash the zip gives me an error, and when i start the .exe the program doesnt find my phone.
So i decided to ask you guys, cause you know everything
peter13337 said:
Hi Guys.
I have a Problem with my HTC One S (ville).
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT 2-15.000
RADIO 1.11.50.05.28
After using the "unofficial" HTC Stock Rom 4.1 with root (Which works sometimes and sometimes not, dont ask me why...), i decided to upgrade.
First I tried Liberty Rom, but after installing my phone was in endless start loop.
So i tried CM (every Version i could find), but after flashing it hang at the HTC Start screen (The One with the Red text).
Then I Tried Viper One S. This was the only one i could start. It runs perfect, except the random reboots. Sometimes every 2 min, sometimes no reboot in one day.
I tried it with TWRP 2.6 and 2.7 and CWM and erverytime the same results: no running OS or a "rebooting-party-OS".
I installed everything with an USB drive connected to the phone via cable.
I tried to get HBOOT 2.16, didnt work.
I tried flashing via ADB, doesnt work. My Computer (win 7) doesnt find the devices.
I tried S-Off, but doesnt work because of ADB-Problem...
I read almost every thread here, but nothing helped...
The Backup of my HTC stock, doesn work. When I restore it, it starts and i have a black screen with only the notification bar and nothing works.
Going back to the orignial RUU's doesnt work. Trying to flash the zip gives me an error, and when i start the .exe the program doesnt find my phone.
So i decided to ask you guys, cause you know everything
Click to expand...
Click to collapse
By any chance, AFTER you flashed any of the above ROMs, have you also flashed boot.img of that ROM (kernel) separately from fastboot? Based on what you say, you have no working ADB so I could guess fastboot isn't working either, but I want confirmation. According to the symptoms, it looks like you have not flashed/have the proper kernel for the ROM...
Sent from nowhere over the air...
Rapier said:
By any chance, AFTER you flashed any of the above ROMs, have you also flashed boot.img of that ROM (kernel) separately from fastboot? Based on what you say, you have no working ADB so I could guess fastboot isn't working either, but I want confirmation. According to the symptoms, it looks like you have not flashed/have the proper kernel for the ROM...
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hey.
No I just flashed the installing .zip of the ROMs. Should I do that and yes, how does it go ?
When i connect my phone via USB with my PC (in Bootloader) it says fsatboot USB and i installed with that way TWRP and CWM Recovery...
peter13337 said:
Hey.
No I just flashed the installing .zip of the ROMs. Should I do that and yes, how does it go ?
When i connect my phone via USB with my PC (in Bootloader) it says fsatboot USB and i installed with that way TWRP and CWM Recovery...
Click to expand...
Click to collapse
It seems that even you read every thread, you missed some important things. First remember: if you're S-On, you MUST flash EVERY time after a ROM flash the corresponding kernel. Or else ROM won't boot. There are threads in which this is discussed but I'll summarize the steps:
1. Open (on your PC) the ROM zip and find inside the file called boot.img. Usually you'll find it in /system. If there are ROMs made for both 2.15 and 2.16 hboot (I know only one that's Liberty Max), it could be that the file is located in a /boot folder in the zip and the file name contains 2.15 or 2.16 to know for which hboot it is...for you it is the one having 2.15 in the name.
2. Copy the ROM zip onto your phone, enter recovery and flash it. I won't detail this step since you should know how to do it but I'll draw your attention upon one thing....BE SURE you have the correct recovery for the ROM you want to flash. That is, for most (or all) 2.15 ROMs you could flash the latest official TWRP 2.7.1.0 from HERE and for 2.16 ROMs you should flash the recovery recommended in that particular ROM thread
3. Having the boot.img file ready and copied on your PC in the location of ADB and fastboot (usualy where Android SDK is installed, in the platform-tools folder), first check that fastboot is working. To do that, after you flashed the ROM, reboot in fastboot mode (bootloader) from recovery and having phone connected on USB as you said before, open a command prompt in the ADB folder and issue the command: fastboot devices. You should get a result containing the S/N of your device...if you get an empty response, that means fastboot doesn't recognize your device. I am almost sure that it does tho, since you said you flashed this way the recovery (you couldn't do it otherwise)
4. Having fastboot working and boot.img in the same folder, issue the following command: fastboot flash boot boot.img
5. Reboot the device, the ROM should boot up and work