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.
Hey I am hoping someone can help me. My friend recently bought an HTC One s off of craiglist and it was rooted with a rom by "Team Venom" immediately after purchasing it started acting up and now it is stuck on the boot screen. I can get into the bootloader but then it only starts in to "team win recovery project" and it will not mount. Where can i go from here? Any info would be great.
What version of team win? Is he s off? You may be able to push for via adb. I can never remember how so you'll have to Google it.
In some versions of team win you can push via the advanced menu.
Sent from my HTC One S using xda app-developers app
npiper05 said:
What version of team win? Is he s off? You may be able to push for via adb. I can never remember how so you'll have to Google it.
In some versions of team win you can push via the advanced menu.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It's team win Recovery v2.1.7
And I believe the S is on
The phone reads:
*** TAMPERED ***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.17.31501S.10_S
OpenDSP-v28.1.0.32.0504
eMMC-boot
In the advanced menu I have four options Copy Log to SD, Fix Permissions, Partition SD Card, File Manager
Thanks in advance
Seems like the kernel (aka boot.img) is corrupted.
Mainly you should try to reflash the kernel in recovery. As far as I understand your post, you can't mount the sd-card in recovery. Correct me if I'm wrong.
The first thing to do is to flash an actually working recovery. You can find an overview here, simply download TWRP 2.3.3.0 in the S4 section. As there is no Viper rom available for the S3 I simply assume you got an S4 device.
Boot your phone into fastboot mode and flash the openrecovery-twrp-2.3.3.0-ville.img file by typing 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from within your Android sdk workfolder (platform-tools). You should be able to boot into TWRP 2.3.3.0 afterwards and check, if sd-card can be mounted. You should see a mount button in the menu...
Also you should do a nandroid backup of this device at this point. You'll find backup in the menu.
If this is working, you'll need the kernel. Corresponding to your bootloader version and your radio I think we need the ICS version of the Viper rom. You can find it here #6. Download it, unzip the file boot.img into your workfolder, then type 'fastboot flash boot boot.img' in fastboot mode from terminal/cmd prompt.
Try to restart the phone and wait some time. If it is the wrong kernel simply download the JB version of Viper from here and follow the instructions above.
Flashing the wrong kernel (ICS <-> JB) won't affect your device as long as it is for the S4 device. It simply doesn' boot or work correctly. Reflashing the right one fixes that.
If none of the above helps, I'd simply suggest to restart from scratch with Viper 2.1.0 #6.
rootrider said:
[..]If none of the above helps, I'd simply suggest to restart from scratch with Viper 2.1.0 #6.
Click to expand...
Click to collapse
Since the device is not new, I would suggest to start from scratch anyway, just to be as clean as possible.
Run the oldest RUU that you can with your hboot version. (I think hboot-1.13 is RUU-1.78.401.2 but make sure..) Then clear storage, factory reset in bootloader, then flash a custom recovery (TWRP-2.3.3.0 or latest CWM), root your OS, and get S-Off. At this point you can format everything including sdcard (in recovery) and you're ready to push your new custom ROM and do a completely clean install.
-Jobo
Hey all. Recently used AAHK (yes, I know now) to root this phone. Bootloader reports the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
.eMMC-boot
Question: In order to flash ROMS while "S-ON" I need to extract and separately flash boot.img included in ROMs after flashing ROM? If so, can boot.img be flashed from sdcard, or just via PC using adb?
Question: Can I get "S-OFF" after the fact, thus eliminating additional boot.img flashing.
This is my second Inspire/DHD. With my first, AAHK worked fine and I think I was "S-OFF" when rooted. I know I was able to flash ROMs to my hearts content (w/o ever flashing boot.img), until I bricked it (after flashing quite a few ROMS, figured procedure was same for last one I grabbed; silly me for not reading install instructions. Recovery help post for that issue forthcoming)
TIA
IC1NYC said:
Hey all. Recently used AAHK (yes, I know now) to root this phone. Bootloader reports the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
.eMMC-boot
Question: In order to flash ROMS while "S-ON" I need to extract and separately flash boot.img included in ROMs after flashing ROM? If so, can boot.img be flashed from sdcard, or just via PC using adb?
Question: Can I get "S-OFF" after the fact, thus eliminating additional boot.img flashing.
This is my second Inspire/DHD. With my first, AAHK worked fine and I think I was "S-OFF" when rooted. I know I was able to flash ROMs to my hearts content (w/o ever flashing boot.img), until I bricked it (after flashing quite a few ROMS, figured procedure was same for last one I grabbed; silly me for not reading install instructions. Recovery help post for that issue forthcoming)
TIA
Click to expand...
Click to collapse
IF your bootloader says S-ON you can unlock it and flash a custom recovery. Then, yes you need to flash the boot.img of the rom each time you flash a rom in fastboot.
For further help use the guide on my signature...you also have an script to unlock, flash recovery and root.
Thanks for the response.
I just ran the tool that is no longer supported again and all is well.
As for the original, mucked-up unit, using adb I am able to get to bootloader, recovery and can flash, but phone never boots. Tried appropriate PD98IMG on root of SD; tried applying same file as "update.zip and tried straight custom ROM. Right now stuck at CM10's animated boot screen. Guess I have to do some more skim....uh...reading.
IC1NYC said:
Thanks for the response.
I just ran the tool that is no longer supported again and all is well.
As for the original, mucked-up unit, using adb I am able to get to bootloader, recovery and can flash, but phone never boots. Tried appropriate PD98IMG on root of SD; tried applying same file as "update.zip and tried straight custom ROM. Right now stuck at CM10's animated boot screen. Guess I have to do some more skim....uh...reading.
Click to expand...
Click to collapse
Is it S-On?
bananagranola said:
Is it S-On?
Click to expand...
Click to collapse
Both units are S-OFF.
Issue resolved with effed-up unit. I flashed latest CM nightly, then flashed boot.img from that release, and (as Kelly Bundy would say) vy-o-la, working phone.
Initially found with my previous attempts at flashing (w/o flashing boot img) that phone stayed on ROMs boot spalsh. Also, found at times that phone would boot straight into recovery, but with blank screen. Only way to tell phone was powered was by the illuminated keys (Home, Menu, etc). And with no VOL- key, only way to move and select items was by using the Menu key, with screen blanking out after each key press.
BTW, how I initially effed-up this unit was by flashing http://forum.xda-developers.com/showthread.php?t=2204384 without reading install instructions. I'd just flashed the zip same as I've been doing with previous ROMs I've tried. :silly: :
IC1NYC said:
Issue resolved with effed-up unit. I flashed latest CM nightly, then flashed boot.img from that release, and (as Kelly Bundy would say) vy-o-la, working phone.
Click to expand...
Click to collapse
If it's S-Off, you shouldn't need to flash the boot.img.
bananagranola said:
If it's S-Off, you shouldn't need to flash the boot.img.
Click to expand...
Click to collapse
It is s-off; was when initially rooted way back when AAHK was still active and still is. However, after multiple attempts at recovery flashing ROMs, this last time I flashed boot.img as well and it booted correctly. Note that ROMs I tried were stock, rooted stock and most recently CM7 and CM10 based.
IC1NYC said:
It is s-off; was when initially rooted way back when AAHK was still active and still is. However, after multiple attempts at recovery flashing ROMs, this last time I flashed boot.img as well and it booted correctly. Note that ROMs I tried were stock, rooted stock and most recently CM7 and CM10 based.
Click to expand...
Click to collapse
That's bizarre...
How to remove
"ViperS 3.12 - Kernel Flasher for S-ON users with 1.0.2 kernel"
from this thread
http://forum.xda-developers.com/showthread.php?t=2216858
or how to overwrite it with standard/stock kernel please ?
birkopf said:
How to remove
"ViperS 3.12 - Kernel Flasher for S-ON users with 1.0.2 kernel"
from this thread
http://forum.xda-developers.com/showthread.php?t=2216858
or how to overwrite it with standard/stock kernel please ?
Click to expand...
Click to collapse
WTF?
ivicask said:
WTF?
Click to expand...
Click to collapse
+1
i don't understand your request
rzr86 said:
+1
i don't understand your request
Click to expand...
Click to collapse
In order to flash ViperS 311 on HTC Sensation you have to flash kernel
311 which is included in the downloads section for vipers 311 (link
provided above).
Unfortunately, this "kernel updater" is making changes which are
preventing some programs to work. I want to remove ViperS and flash
other rom,
Unfortunately x2 this kernel updater made changes which are preventing
flashing other roms. In fact - I am struggling to boot 4ext
Therefore I want it out and revert to the software which I had on my
sensation before installing kernel updater.
birkopf said:
In order to flash ViperS 311 on HTC Sensation you have to flash kernel
311 which is included in the downloads section for vipers 311 (link
provided above).
Unfortunately, this "kernel updater" is making changes which are
preventing some programs to work. I want to remove ViperS and flash
other rom,
Unfortunately x2 this kernel updater made changes which are preventing
flashing other roms. In fact - I am struggling to boot 4ext
Therefore I want it out and revert to the software which I had on my
sensation before installing kernel updater.
Click to expand...
Click to collapse
actually you didn't flash kernel updater
kernel updater is being using to flash the boot.img of the rom so you can boot the rom after installation(if you are facing bootloops)
what to do now
flash another rom as you know
after that put the boot.img of the rom in your adb and fastboot folder and flash it via fastboot command(i assume you know how to do that)
if you need anything else report
edit:what did you mean by ''this "kernel updater" is making changes which are
preventing some programs to work''
rzr86 said:
actually you didn't flash kernel updater
kernel updater is being using to flash the boot.img of the rom so you
can boot the rom after installation(if you are facing bootloops) what
to do now flash another rom as you know
after that put the boot.img of the rom in your adb and fastboot folder
and flash it via fastboot command(i assume you know how to do that) if
you need anything else report edit:what did you mean by ''this
"kernel updater" is making changes which are preventing some programs
to work''
Click to expand...
Click to collapse
Well, now I'm totally confused so let's start from the beginning:
1. I had some customised rom and decided to flash ViperS 3.1.1.
Flashing 3.1.1. is impossible unless you use this "kernel flasher" which
is included in downloads on the official ViperS311 thread. After
running this kernel flasher I managed to install ViperS311 but for
example LBE Privacy isn't working, my SatNav program isn't wokring,
other software isn't working as well.
2. Yesterday I got a message on my phone that there is an update from
ViperS 3.1.1 to ViperS 3.1.2 which I installed. Unfortunately, after
updating to 3.1.2 the wifi isn't working. I want to remove ViperS and
revert to other Rom like Asianic or any other. Now this is impossible
because of the changes that kernel flasher from ViperS made to my
device.
3. I want it out and get my phone back as I need it.
4. I have just flashed stock kernel and managed to install Asianic, but
after booting into the system and installing ES File Manager, it went
into a boot loop. Is starts and reboots non-stop.
5. I did used ADB but really long time ago so I don't remember all. I
also use mainly linux so I will prefer to revert it to the previous
version without the need for Windows use.
birkopf said:
Well, now I'm totally confused so let's start from the beginning:
1. I had some customised rom and decided to flash ViperS 3.1.1.
Flashing 3.1.1. is impossible unless you use this "kernel flasher" which
is included in downloads on the official ViperS311 thread. After
running this kernel flasher I managed to install ViperS311 but for
example LBE Privacy isn't working, my SatNav program isn't wokring,
other software isn't working as well.
2. Yesterday I got a message on my phone that there is an update from
ViperS 3.1.1 to ViperS 3.1.2 which I installed. Unfortunately, after
updating to 3.1.2 the wifi isn't working. I want to remove ViperS and
revert to other Rom like Asianic or any other. Now this is impossible
because of the changes that kernel flasher from ViperS made to my
device.
3. I want it out and get my phone back as I need it.
4. I have just flashed stock kernel and managed to install Asianic, but
after booting into the system and installing ES File Manager, it went
into a boot loop. Is starts and reboots non-stop.
5. I did used ADB but really long time ago so I don't remember all. I
also use mainly linux so I will prefer to revert it to the previous
version without the need for Windows use.
Click to expand...
Click to collapse
can you post your bootloader details now and what asianic rom did you install?
rzr86 said:
can you post your bootloader details now and what asianic rom did you install?
Click to expand...
Click to collapse
This is the Asianic: http://forum.xda-developers.com/showthread.php?t=1586753
What do you mean by bootloader details and where I can find it ?
birkopf said:
This is the Asianic: http://forum.xda-developers.com/showthread.php?t=1586753
What do you mean by bootloader details and where I can find it ?
Click to expand...
Click to collapse
switch off the device and remove battery
reinsert it
press and hold together power button and volume down until it gets you to the bootloader
post everything it says at the top
rzr86 said:
switch off the device and remove battery
reinsert it
press and hold together power button and volume down until it gets you to the bootloader
post everything it says at the top
Click to expand...
Click to collapse
Apology. Here it is:
*** UNLOCKED ***
Pyramid PVT SHIP S-ON RL
HBOT-1.27.0000
eMMC-boot
Jan 13, 2012, 17:33:34
I am S-On but with 4EXT option for SmartFlash I can flash various ROMs
birkopf said:
Apology. Here it is:
*** UNLOCKED ***
Pyramid PVT SHIP S-ON RL
HBOT-1.27.0000
eMMC-boot
Jan 13, 2012, 17:33:34
I am S-On but with 4EXT option for SmartFlash I can flash various ROMs
Click to expand...
Click to collapse
ok
can you boot now in the asianic rom?
if not then follow these steps
1)boot the device to the bootloader
2)connect it to pc via usb(in the hboot screen must say fastboot usb)
3)now extract the boot.img from the asianic rom and place it in the folder where you have adb and fastboot files
4)open in that folder a cmd window and do fastboot flash boot boot.img
5)then do fastboot reboot
see then if it boots to the rom
Is superwipe recommended while coming from stock ICS or I should format all partition except SD Card? I am S-Off and 3.33 firmware.
Sent from my HTC Sensation Z710e
rzr86 said:
ok
can you boot now in the asianic rom?
if not then follow these steps
1)boot the device to the bootloader
2)connect it to pc via usb(in the hboot screen must say fastboot
usb) 3)now extract the boot.img from the asianic rom and place it
in the folder where you have adb and fastboot files 4)open in that
folder a cmd window and do fastboot flash boot boot.img 5)then
do fastboot reboot
see then if it boots to the rom
Click to expand...
Click to collapse
Thanks for that rzr86, I'm starting to understand that now. It seems
that Kernel Flasher from ViperS 311 is a boot.img file with simple
program made by ViperS group that does what you mentioned, but without
the need for using adb and command line.
- However, I still don't understand what changes they made to that
boot.img to cause such complications... ?
Asianic installed correctly but than started crashing and booting in
loop so I replaced it with "Sense-o-Maniac" and this seems to be
working fine.
It doesn’t have any previous problems that I was experiencing on other
rom's.
I will report if any problems arise. So for so good.
I got bit shaky when I couldn't boot into 4EXT but it was just temprary
MrJukeHardbane said:
Is superwipe recommended while coming from stock ICS or I should format all partition except SD Card? I am S-Off and 3.33 firmware.
Click to expand...
Click to collapse
Superwipe is basically wiping all partitions except of SD Card. Always recommended :highfive:
birkopf said:
Superwipe is basically wiping all partitions except of SD Card. Always recommended :highfive:
Click to expand...
Click to collapse
All kernel flasher does is "fastboot flash boot boot.img" NOTHING ELSE, and u can use it to actually flash any other kernel you want on ANY device!
Using kernel fasher
Hi ! I just joined this forum and might be this is my first question
I am quite interesting to install this ROM (viper) and would like to take a shot. But, I worry about this "kernel flasher" issue.
Here is my sensation status :
-HBOOT 1.29
-Firmware 3.33.707.151
-Radio 1176A.3504.OOU_1124A.3504.31_M
-S-ON
-Bootloader unlocked
-Rooted
I would to confirm some questions :
1. If I want to install this ROM can't I just simply install it to the latest version of ViperS 3.1.2?
2. Which one will come first flashing kernel (using kernel flasher) or installing ROM?
3. Will it be working using my current firmware?
Sorry for this noob question. Really appreciate your help, guys.
odnamra87 said:
Hi ! I just joined this forum and might be this is my first question
I am quite interesting to install this ROM (viper) and would like to take a shot. But, I worry about this "kernel flasher" issue.
Here is my sensation status :
-HBOOT 1.29
-Firmware 3.33.707.151
-Radio 1176A.3504.OOU_1124A.3504.31_M
-S-ON
-Bootloader unlocked
-Rooted
I would to confirm some questions :
1. If I want to install this ROM can't I just simply install it to the latest version of ViperS 3.1.2?
2. Which one will come first flashing kernel (using kernel flasher) or installing ROM?
3. Will it be working using my current firmware?
Sorry for this noob question. Really appreciate your help, guys.
Click to expand...
Click to collapse
1)simply install viperS ROM 3.1.2.use 4ext recovery and before flashing enable smartflash from 4ext
2)just flash the rom and do as i said in first answer.if you have bootloops after installation then use the kernel flasher or
do it manually by extracting the boot.img of the rom,place it your adb and fastboot folder and type the command to cmd window
fastboot flash boot boot.img
note: connect the device to pc into fastboot mode(in the hboot screen should say fastboot usb)
3)yeap
rzr86 said:
1)simply install viperS ROM 3.1.2.use 4ext recovery and before flashing enable smartflash from 4ext
2)just flash the rom and do as i said in first answer.if you have bootloops after installation then use the kernel flasher or
do it manually by extracting the boot.img of the rom,place it your adb and fastboot folder and type the command to cmd window
fastboot flash boot boot.img
note: connect the device to pc into fastboot mode(in the hboot screen should say fastboot usb)
3)yeap
Click to expand...
Click to collapse
Hi again !
Really appreciate ur fast answer
I'm currently using TWRP for my recovery, should I change it?
odnamra87 said:
Hi again !
Really appreciate ur fast answer
I'm currently using TWRP for my recovery, should I change it?
Click to expand...
Click to collapse
i suggest to change it:good:
rzr86 said:
i suggest to change it:good:
Click to expand...
Click to collapse
Hi ! Would like to ask few questions again..
How to properly change from twrp to 4ext?try to search but have no confidence on it.what about my nandroid back up that I did with twrp?will it be readable with 4ext or should I make another one with 4ext once it's been intalled?
Hope u.can help me with this.thanks so much.