[Q] [Solved] Keep getting error message "Unfortunately, HTC Sense has stopped"
Hi everyone, I recently bought a second hand HTC One X locked to Rogers. It already had SuperUser and the HBOOT had "Tampered" and "Unlocked" at the top. I managed to install Hatka XL ROM with the help of tutorials and ROM Manager. When I finally boot into the home screen and setup the basics like WiFi, a message pops up saying some process has stopped, which was soon followed by "Unfortunately, HTC Sense has stopped". This message keeps popping up and I'm not sure what to do next. I've cleared the cache and factory resetted (as some search results suggested) and reinstalled the ROM as well.
It's still S-on, can't check Jelly Bean version since the pop up stops me from getting anywhere on the screen.
I don't think this issue is inherent to Hatka ROM, but I'm already thinking of trying a different ROM just in case.
Anyway, I reinstalled Hatka twice, each time clearing the cache and factory resetting. I chose AOSP over Sense for keyboards, lockscreens, etc. I might try going stock with everything. I also looked into the touchscreen firmware downgrade option: http://forum.xda-developers.com/showthread.php?t=2159863 in case that has something to do with it.
Any advice would be great, thanks in advance!
Updated: Tried all stock Sense with Hatka ROM to no avail, same message pops up.
Did you do a full wipe before flashing the ROM? Just wiping cache and dalvik isn't enough.
Sent from my Evita
I selected the wipe data/factory reset option in the attached image. Thanks for the help, if there's another/better way please let me know.
It wouldn't hurt to try wiping system as well before flashing a ROM.
Sent from my Evita
dncrgl said:
I selected the wipe data/factory reset option in the attached image. Thanks for the help, if there's another/better way please let me know.
Click to expand...
Click to collapse
You should wipe cache, also.
Since you are S-on, are you remembeing to flash boot.img seperately via fastboot, every time you flash a new ROM?
redpoint73 said:
You should wipe cache, also.
Since you are S-on, are you remembeing to flash boot.img seperately via fastboot, every time you flash a new ROM?
Click to expand...
Click to collapse
I didn't do that separately on command prompt for the previous attempts. I usually just did it through CWM.
The next thing I tried was installing TWRP 2.6 and I have HBOOT 2.14. I tried flashing Rebel ROM which froze at the X logo splashscreen. I did however flash it through command prompt using fastboot and its boot.img.
Currently, I reinstalled HatkaXL thinking it was the one that worked in the first place using TWRP this time instead of CWM. The issue now is that it boot loops from HTC screen to Hatka's splashscreen then repeats to HTC.
Thanks for the help though
dncrgl said:
I didn't do that separately on command prompt for the previous attempts. I usually just did it through CWM.
Click to expand...
Click to collapse
With hboot 2.14 and S-on, its simply impossible for boot.img to be flashed from recovery. Not sure why Rebel ROM didn't work for you. But try a different ROM, and flash boot.img using fastboot.
redpoint73 said:
With hboot 2.14 and S-on, its simply impossible for boot.img to be flashed from recovery. Not sure why Rebel ROM didn't work for you. But try a different ROM, and flash boot.img using fastboot.
Click to expand...
Click to collapse
Just to clarify should I flash the ROM using TWRP then do I go back to HBOOT>fastboot >fastboot flash boot boot.img?
dncrgl said:
Just to clarify should I flash the ROM using TWRP then do I go back to HBOOT>fastboot >fastboot flash boot boot.img?
Click to expand...
Click to collapse
Exactly.. and I hit thanks button by mistake, so you got a freebie
Sent from my HTC One XL using xda premium
31ken31 said:
Exactly.. and I hit thanks button by mistake, so you got a freebie
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
You can un thank posts
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA Moderator
E.Cadro said:
You can un thank posts
View attachment 2156355
XDA Moderator
Click to expand...
Click to collapse
That info deserves a thanks lol. :beer:
Sent from my HTC One XL using xda premium
redpoint73 said:
With hboot 2.14 and S-on, its simply impossible for boot.img to be flashed from recovery. Not sure why Rebel ROM didn't work for you. But try a different ROM, and flash boot.img using fastboot.
Click to expand...
Click to collapse
Thanks, everyone!
Managed to get it to work with this ROM: http://forum.xda-developers.com/showthread.php?t=2293032
Instead of booting up the phone after flashing the ROM, went straight to the HBOOT and entered fastboot to do the fastboot command. But the first start showed the splashscreens then it boot-looped once before actually working. It was fortunate that I was busy searching other solutions thinking the phone was gonna keep boot-looping and that's when the home screen loaded =D
dncrgl said:
Thanks, everyone!
Managed to get it to work with this ROM: http://forum.xda-developers.com/showthread.php?t=2293032
Instead of booting up the phone after flashing the ROM, went straight to the HBOOT and entered fastboot to do the fastboot command. But the first start showed the splashscreens then it boot-looped once before actually working. It was fortunate that I was busy searching other solutions thinking the phone was gonna keep boot-looping and that's when the home screen loaded =D
Click to expand...
Click to collapse
First boot sometimes takes a while. Patience is a virtue. And glad your up ans running. Have fun
Sent from my HTC One XL using xda premium
I need help with my HTC One m8. I keep getting an error message unfortunately sense home has stopping working. I have tried to clear cache partition but I can only get as far as the red triangle. When I press the up volume button and power button the get in to clear cache is keeps looping and rebooting phone and I can't seem to get any further than the red triangle. Hope this makes sense and someone can help. I would love to try this before I do a factory reboot
Related
Okay very nervous that my phone hasn't booted, but trying to keep my cool. Well here's what happened:
1. On AOKP JB trying to boot to stock to backup my IMEI.
2. Odin restored fine, but would get stuck booting at the 4G LTE screen.
3. Flashed the stock bootloader found in the R&D thread.
4. Went back into download mode, tried to flash invisiblek's stock rooted.
5. Failed.
6. Tried to flash stock again. Failed.
7. Tried to boot up and got this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you can't read it, it says " Firmware upgrade encountered and issue. Please select recovery mode in Kies and & try again"
Any help?
Try setting it back to download mode and reflash recovery. If you can get to download mode its not really bricked. Just a soft brick.
Look for Qball77 link for how to root and how to unroot. All download files and instruction in his videos are super easy to follow.
Sent from my SPH-L710 using Tapatalk 2
jthrift said:
Try setting it back to download mode and reflash recovery. If you can get to download mode its not really bricked. Just a soft brick.
Look for Qball77 link for how to root and how to unroot. All download files and instruction in his videos are super easy to follow.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Flash a recovery? Should I go back to stock and use EZ recovery?
austin1227 said:
Okay very nervous that my phone hasn't booted, but trying to keep my cool. Well here's what happened:
1. On AOKP JB trying to boot to stock to backup my IMEI.
2. Odin restored fine, but would get stuck booting at the 4G LTE screen.
3. Flashed the stock bootloader found in the R&D thread.
4. Went back into download mode, tried to flash invisiblek's stock rooted.
5. Failed.
6. Tried to flash stock again. Failed.
7. Tried to boot up and got this
If you can't read it, it says " Firmware upgrade encountered and issue. Please select recovery mode in Kies and & try again"
Any help?
Click to expand...
Click to collapse
Maybe a stupid question but have you tried selecting recovery mode in Kies and trying again?
Relentless D said:
Maybe a stupid question but have you tried selecting recovery mode in Kies and trying again?
Click to expand...
Click to collapse
I honestly have no clue what Kies is.
austin1227 said:
I honestly have no clue what Kies is.
Click to expand...
Click to collapse
I don't mean to sounds like a jerk but this may help:
http://bit.ly/w1qkPe
Relentless D said:
I don't mean to sounds like a jerk but this may help:
http://bit.ly/w1qkPe
Click to expand...
Click to collapse
No offense taken, I googled " S3 kies vzw"
Was kind of jerky. But find a stock tar file and flash it using Odin.
Can you get back to Download mode? ~Volume Down home and power button all same time. Volume up to accept.~
Sent from my SPH-L710 using Tapatalk 2
jthrift said:
Was kind of jerky. But find a stock tar file and flash it using Odin.
Can you get back to Download mode? ~Volume Down home and power button all same time. Volume up to accept.~
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Wait should I flash the stock zip (I can get into download mode) or use kies first?
austin1227 said:
No offense taken, I googled " S3 kies vzw"
Click to expand...
Click to collapse
Did you factory reset in recovery after flashing the stock image? Use section 2 in this guide for returning back to stock. If all else fails, you can try this one.
http://forum.xda-developers.com/showthread.php?t=1840030
This is Verizon right?
Sent from my SPH-L710 using Tapatalk 2
PJnc284 said:
Did you factory reset in recovery after flashing the stock image? Use section 2 in this guide for returning back to stock. If all else fails, you can try this one.
Click to expand...
Click to collapse
No, but what should I do first, Kies or Odin?
jthrift said:
http://forum.xda-developers.com/showthread.php?t=1840030
This is Verizon right?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Yes.
Just booted again and no Kies screen, but stuck on the Samusng Galaxy S3 screen.
Also got into recovery and wiped, but still no luck.
Soft Brick
austin1227 said:
Yes.
Click to expand...
Click to collapse
Sounds like a Soft Brick if you can get into download mode. Been there several times but is fixable. Use Odin, never have used Kies. Stay calm read first.
http://forum.xda-developers.com/showthread.php?t=1840030
Follow this to the T.......................
Tried to flash the first bootchain in this guide, stuck on PIT mapping.
austin1227 said:
Tried to flash the first bootchain in this guide, stuck on PIT mapping.
Click to expand...
Click to collapse
What Windows OS are you using? Google has quite a few related result such as this. If it's early in the odin process like that thread, you can just unplug and pull the battery. Maybe try rebooting the computer and a different USB port?
PJnc284 said:
What Windows OS are you using? Google has quite a few related result such as this. If it's early in the odin process like that thread, you can just unplug and pull the battery. Maybe try rebooting the computer and a different USB port?
Click to expand...
Click to collapse
Doesn't matter anymore, I skipped that part mainly because it was optional. Still got a bootloop, maybe the bootchain was the cause?
Edit: still needed to do the recovery. booting now.
Thanks to all who helped. Got my phone booting! Honestly thank you a ton. I posted this first on Rootzwiki's panic room and didn't even get a reply. :laugh:
Hello. So, I did all right.
I have root, unlock boot and fastboot.
I got install TWRP but it shows me an error.
Look at the pictures
Installing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Error
Can someone help me ?
I followed this topic > http://forum.xda-developers.com/showthread.php?t=2302979
im assuming you have a xt925? where did you get a "17/10/2013" version for the 925?
i haven't seen any new versions, maybe i missed it.
The version doesn't matter because the problem is that you need to boot immediately into the custom recovery directly from boot loader the first time and disable the flash recovery script. The OS will overwrite the stock recovery every boot otherwise.
damn i missed that...knew that was stock and not an error, i fail lol
bweN diorD said:
im assuming you have a xt925? where did you get a "17/10/2013" version for the 925?
i haven't seen any new versions, maybe i missed it.
Click to expand...
Click to collapse
What ? I didn't understand your question.
cellzealot said:
The version doesn't matter because the problem is that you need to boot immediately into the custom recovery directly from boot loader the first time and disable the flash recovery script. The OS will overwrite the stock recovery every boot otherwise.
Click to expand...
Click to collapse
So. I need to disable unlock boot/fastboot ? And remake the process ?
RaR System said:
What ? I didn't understand your question.
So. I need to disable unlock boot/fastboot ? And remake the process ?
Click to expand...
Click to collapse
After you push/install the recovery you need to "reboot recovery" the first time, not reboot to system.
My comment is asking if you have the right recovery. I see the date on your recovery is new, I'm making sure you are not trying to flash a 926 recovery if you have a 925. You didn't say what model you have.
Sent from my XT926 using XDA Premium 4 mobile app
Hm. I understood. Then after I install recovery I need to write "reboot rexovery" right ? When I come back home I'll try !
A sure, I'm sorry I forget to say what is my version phone.
Sent from my XT925 using xda app-developers app
RaR System said:
Hm. I understood. Then after I install recovery I need to write "reboot rexovery" right ? When I come back home I'll try !
A sure, I'm sorry I forget to say what is my version phone.
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
I see now you have a 925 as I suspected, my concern was that you have the right recovery also. I haven't seen any new version for the 925, maybe I missed it. Just make sure you have a 925 recovery or it may not work right or at all.
The edit date in your script for the recovery was yesterday that's why I asked.
Sent from my XT926 using XDA Premium 4 mobile app
Alright. Well bbut come back to my problem do you know what I need to do and how I do ?
I want to test new roms in my razr. =]
Sent from my XT925 using xda app-developers app
RaR System said:
Alright. Well bbut come back to my problem do you know what I need to do and how I do ?
I want to test new roms in my razr. =]
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
i think you just need to put
fastboot reboot recovery
where you have fastboot reboot. you have to make it reboot directly into recovery, if it boots to system the new recovery is gone.
bweN diorD said:
i think you just need to put
fastboot reboot recovery
where you have fastboot reboot. you have to make it reboot directly into recovery, if it boots to system the new recovery is gone.
Click to expand...
Click to collapse
The command "fastboot reboot recovery" doesn't exists. And now ? What do I ?
RaR System said:
The command "fastboot reboot recovery" doesn't exists. And now ? What do I ?
Click to expand...
Click to collapse
sorry, it should be adb not fastboot.
adb reboot recovery
if you want a script that i know already works, here is one by tucstwo http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
just change the recovery img for yours.
bweN diorD said:
sorry, it should be adb not fastboot.
adb reboot recovery
if you want a script that i know already works, here is one by tucstwo http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
just change the recovery img for yours.
Click to expand...
Click to collapse
Wow, amazing ! It work very well !
My thanks !
Problem Solved :3
Glad you got it fixed
Sent from my XT926 using XDA Premium 4 mobile app
I was about to flash from CM10 to CM11, but before flashing a new ROM I was manually removing all my apps so I wouldn't forget anything.
Now, after a phone reboot I'm trying to access the SD Card via ES File Explorer. But it says my SD Card is ejected... How do I fix this issue? Tried booting into Recovery as well, but it just boots into CM10... Did I mess up something?
Tendency88 said:
I was about to flash from CM10 to CM11, but before flashing a new ROM I was manually removing all my apps so I wouldn't forget anything.
Now, after a phone reboot I'm trying to access the SD Card via ES File Explorer. But it says my SD Card is ejected... How do I fix this issue? Tried booting into Recovery as well, but it just boots into CM10... Did I mess up something?
Click to expand...
Click to collapse
Did you flash the correct hboot of cm11? Should be the 2.15 (official) version.
Did you flash CM11 with the correct recovery? 2.7.0.8 if using TWRP.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Did you flash the correct hboot of cm11? Should be the 2.15 (official) version.
Did you flash CM11 with the correct recovery? 2.7.0.8 if using TWRP.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I haven't flashed a new ROM yet, I was about to. But my SD Card can't be found anymore. About the HBOOT version, is it really required to have HBOOT 2.15 or higher? Because the CM wiki says:
http://wiki.cyanogenmod.org/w/Install_CM_for_ville
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444
EDIT:
Forget about the HBOOT, I'm running 1.13.. So yeah I will have to update, but first I need to get my SD Card back..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tendency88 said:
I haven't flashed a new ROM yet, I was about to. But my SD Card can't be found anymore. About the HBOOT version, is it really required to have HBOOT 2.15 or higher? Because the CM wiki says:
http://wiki.cyanogenmod.org/w/Install_CM_for_ville
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444
Click to expand...
Click to collapse
What recovery are you using?
Sent from my Nexus 4 using Tapatalk
nicknc said:
What recovery are you using?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
TWRP 2.7.0.0, while it says successful I can't run Recovery..
Tendency88 said:
TWRP 2.7.0.0, while it says successful I can't run Recovery..
Click to expand...
Click to collapse
All the latest nightlies for CM11 require flashing through TWRP 2.7.0.8 or higher. 2.7.0.0 simply will not work.
I would start there.
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Make sure to read the entire page, including the paragraph at the bottom. Download the non-dm version.
Sent from my Nexus 4 using Tapatalk
nicknc said:
All the latest nightlies for CM11 require flashing through TWRP 2.7.0.8 or higher. 2.7.0.0 simply will not work.
I would start there.
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Make sure to read the entire page, including the paragraph at the bottom. Download the non-dm version.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I get your point, I really do.. but that´s pretty much irrelevant at this point as I still can´t access my SD Card.
Tendency88 said:
I get your point, I really do.. but that´s pretty much irrelevant at this point as I still can´t access my SD Card.
Click to expand...
Click to collapse
You can fastboot, correct?
Sent from my Nexus 4 using Tapatalk
Yes I can.
EDIT:
Seems only fastboot works..
Tendency88 said:
Yes I can.
EDIT:
Seems only fastboot works..
Click to expand...
Click to collapse
ADB only works for me in MTP mode...maybe with your SD messed up, MTP mode is unavailable? If you type adb devices and get none found, that means your adb is messed up, not recovery.
Dumb question, but when you go to settings/storage, and scroll down...can you mount sd?
el_smurfo said:
ADB only works for me in MTP mode...maybe with your SD messed up, MTP mode is unavailable? If you type adb devices and get none found, that means your adb is messed up, not recovery.
Dumb question, but when you go to settings/storage, and scroll down...can you mount sd?
Click to expand...
Click to collapse
Settings of what exactly? I can't boot into recovery, and my previous CM (CM10.0) is stuck on the logo as well. I almost feel like flashing a RUU, and start all over.. This seems messed up to say the least.
Since I can't get into recovery nor boot into my ROM, I'm not able to select MTP mode.
Tendency88 said:
Settings of what exactly? I can't boot into recovery, and my previous CM (CM10.0) is stuck on the logo as well. I almost feel like flashing a RUU, and start all over.. This seems messed up to say the least.
Click to expand...
Click to collapse
Told you it was a dumb question. Flashing an RUU is a pretty good idea anyways...start from a clean slate with all the correct firmware in place.
Have you tried to enter recovery via bootloader? (vol down + power)
Sent from nowhere over the air...
Or just fastboot flash the correct recovery and then format data and internal storage via recovery.
This sounds a lot like the corrupted data partition caused by a bad update to 2.16. Something similar could be occurring here given the fstab updates in cm11.
You made it sounds like you are not on 2.15 or 2.16, is that correct?
Sent from my Nexus 4 using Tapatalk
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
Rapier said:
Have you tried to enter recovery via bootloader? (vol down + power)
Sent from nowhere over the air...
Click to expand...
Click to collapse
Remember you really have to mash that volume down button on some of these phones. I have to take mine out of the case.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Or just fastboot flash the correct recovery and then format data and internal storage via recovery.
This sounds a lot like the corrupted data partition caused by a bad update to 2.16. Something similar could be occurring here given the fstab updates in cm11.
You made it sounds like you are not on 2.15 or 2.16, is that correct?
Sent from my Nexus 4 using Tapatalk
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
Remember you really have to mash that volume down button on some of these phones. I have to take mine out of the case.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I never tried updating to 2.16 yet, so that can't be the problem.
Right now I flashed a ICS 4.0.3 RUU and everything is working great again. I just rooted the device again, went successful. After that I flashed recovery with fastboot, it said it was successful as well.
But when I access PWR BTN + VOL DOWN, and select Recovery, it simply turns black screen and boots my phone normally. Something else must be wrong, what could be keeping my phone from flashing into Recovery?
Tendency88 said:
I never tried updating to 2.16 yet, so that can't be the problem.
Right now I flashed a ICS 4.0.3 RUU and everything is working great again. I just rooted the device again, went successful. After that I flashed recovery with fastboot, it said it was successful as well.
But when I access PWR BTN + VOL DOWN, and select Recovery, it simply turns black screen and boots my phone normally. Something else must be wrong, what could be keeping my phone from flashing into Recovery?
Click to expand...
Click to collapse
Did you install TWRP 2.7.0.8? Boot loader unlocked?
And yeah, I know you didn't update to 2.16. I only pointed that out as a similarity in the symptoms of corrupted partitions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------
Tendency88 said:
I never tried updating to 2.16 yet, so that can't be the problem.
Right now I flashed a ICS 4.0.3 RUU and everything is working great again. I just rooted the device again, went successful. After that I flashed recovery with fastboot, it said it was successful as well.
But when I access PWR BTN + VOL DOWN, and select Recovery, it simply turns black screen and boots my phone normally. Something else must be wrong, what could be keeping my phone from flashing into Recovery?
Click to expand...
Click to collapse
OK, I see your screen shots now. Dude, go to hboot 2.15, it will help in ruling things out. Use the RUU in my downgrade 2.16 to 2.15 thread and it will put you on 2.15.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Did you install TWRP 2.7.0.8? Boot loader unlocked?
And yeah, I know you didn't update to 2.16. I only pointed that out as a similarity in the symptoms of corrupted partitions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------
OK, I see your screen shots now. Dude, go to hboot 2.15, it will help in ruling things out. Use the RUU in my downgrade 2.16 to 2.15 thread and it will put you on 2.15.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
It seems that it doesn't matter WHAT recovery I'm trying to flash, none of them work. The phone simply boots itself, instead of booting into Recovery.
I will try your 2.15 RUU, does it work for any HTC One S (ville) device?
Tendency88 said:
It seems that it doesn't matter WHAT recovery I'm trying to flash, none of them work. The phone simply boots itself, instead of booting into Recovery.
I will try your 2.15 RUU, does it work for any HTC One S (ville) device?
Click to expand...
Click to collapse
Just the US, krait version. Not the "C2", obviously.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Just the US, krait version. Not the "C2", obviously.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Something is really ****ing up things.. I just tried to run rumrunner_HTC_0.5.0 to get my device S-OFF, at the very end of the process it said my device is not rooted. I'm 100% certain I followed the steps exactly written at http://www.htcdev.com/bootloader/unlock-instructions/ it even said: successfully unlocked..
EDIT:
Makes sense, UNLOCKING is not the same as ROOTING, doh.. well I need to boot into Recovery and flash the SuperSU to get rooted, but since Recovery isn't working I'm quite lost here..
Tendency88 said:
Something is really ****ing up things.. I just tried to run rumrunner_HTC_0.5.0 to get my device S-OFF, at the very end of the process it said my device is not rooted. I'm 100% certain I followed the steps exactly written at http://www.htcdev.com/bootloader/unlock-instructions/ it even said: successfully unlocked..
What the hell..
Click to expand...
Click to collapse
I've been in a similar position during my first attempt at s-off, and later when going to 2.16 for a little bit.
Just use my guide to go back to 100% stock and slowly start over. It works well.
Sent from my Nexus 4 using Tapatalk
This is a very wierd problem I have experienced in my life with My senny.
I recently sold my sensation to my friend running 4.1.2 sense 5 viper 5.3.0.
it was clocked at 1.4 ghz so it was draining battery very fast, so my friend discussed this problem with me, so I under clocked it to 1180ghz using venom tweaks and I forgot to tick the option (apply changes at boot).
so he used the phone whole day after that when he reached home he powered off phone and left it for charging, after that when he switched on the phone get till boot animation and then it restarted and so this cycle continue going on and phone didn't booted up.
I re flashed rom but the problem still exist, I flashed kk and restored boot backup (which I made from 4ext recovery) so phone booted but the wifi and bluetooth doesn't turned on,
I again tried to flash viper 3.2.0 but the phone doesnt booted so I flashed its boot.img from linux using the command :sudo fastboot flash boot boot.img, it sent boot but still the phone didn't booted and restarted once the bootanimation was ending.
I flashed cm 11 kk again same issues exist there (bluetooth and wifi), then I flashed kk boot.img using linux but still the same issue exist.
now I want to know how can I get wifi and bluetooth back to work and boot other roms other than cm11 kk.
Whatshboot? N r u son or soff?
V u tried wi pop e evrything bt sd card?
N when restoring choose advance restore n dont restore cache, restore system, data n boot only.
BODY MECHANIC
I'm s-on
im using 4ext recovery latest version
my hboot is I guess 1.27 something
And I flashed cm11 as zip and restore boot from advance restore.with wiping everything except sd card
Mustafa Mubashir said:
I'm s-on
im using 4ext recovery latest version
my hboot is I guess 1.27 something
And I flashed cm11 as zip and restore boot from advance restore.with wiping everything except sd card
Click to expand...
Click to collapse
Can u update ur firmware, n try
Method is on forum, use rumrunner to soft, then try flashing ROM again
BODY MECHANIC
Link please?
And I appreciate your help. Thanks
abuulala said:
Can u update ur firmware, n try
Method is on forum, use rumrunner to soft, then try flashing ROM again
BODY MECHANIC
Click to expand...
Click to collapse
Link please?
And I appreciate your help. Thanks
read this bro
http://forum.xda-developers.com/showthread.php?t=2085025 and use this to fix ur
abuulala said:
read this bro
http://forum.xda-developers.com/showthread.php?t=2085025 and use this to fix ur
Click to expand...
Click to collapse
I'll try the wifi fix,
But I don't think it is useful for me,
Because I've flashed these roms with s-on device using 4ext and yes smart flashed was enabled I've also tried writing boot.img using fastboot from windows but still no luck,
Only 4.4.4 kk cm11 by sultan is booting no other roms are booting although the last working rom (before this problem) was viper 3.2.0
Sent from my GT-I9305 using XDA Free mobile app
Images of phone.
Only booting on kk any other roms are not working nor the boot.img via fastboot method working.
I don't know what to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9305 using XDA Free mobile app
First flash new 4ext recovery through fastboot, n then flash ur rom n flash that kernel via fastboot,
Try it from windows adb,
BODY MECHANIC
abuulala said:
First flash new 4ext recovery through fastboot, n then flash ur rom n flash that kernel via fastboot,
Try it from windows adb,
BODY MECHANIC
Click to expand...
Click to collapse
Okay
Sent from my GT-I9305 using XDA Free mobile app
abuulala said:
First flash new 4ext recovery through fastboot, n then flash ur rom n flash that kernel via fastboot,
Try it from windows adb,
BODY MECHANIC
Click to expand...
Click to collapse
hey i flashed new 4ext recovery from windows and also flashed the same kernel (i.e sultan cm11) on my sensation but still wifi and bluetooth not working.
what should i do next?
Is there anyway to get to stock ics?
Mustafa Mubashir said:
hey i flashed new 4ext recovery from windows and also flashed the same kernel (i.e sultan cm11) on my sensation but still wifi and bluetooth not working.
what should i do next?
Is there anyway to get to stock ics?
Click to expand...
Click to collapse
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
rzr86 said:
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
thank you for this but i already visited this thread yesterday and i planned to go back to stock on my senny.
Hey guys
Today I flashed no wipe firmware 2.33.401.10 from maximus hd page on my htc u11 dual sim and everything on my phone erased and I'm having a bad partition error perhaps.
I donno what should I do really.
Watching below pics may guide you to help me.
Thanks in advance
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One M8 using Tapatalk
And this
Sent from my HTC One M8 using Tapatalk
arses said:
And thisView attachment 4378398
Sent from my HTC One M8 using Tapatalk
Click to expand...
Click to collapse
From what I can see ,, I would download the correct ruu that matches your cid, place it on your external sd and go to download mode and flash it. Hth
First off read page 30 of the TWRP thread. As far as I can tell you should format data and reboot to recovery to resolve the mount problem regarding data partition.
Second firmware zips are never flashed in Recovery. Why are you even trying this?
Third what theater above me wrote.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
First off read page 30 of the TWRP thread. As far as I can tell you should format data and reboot to recovery to resolve the mount problem regarding data partition.
Second firmware zips are never flashed in Recovery. Why are you even trying this?
Third what theater above me wrote.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thanks
I flashed firmware via fastboot and what is in pics it's just an attempt for nothing.
Sent from my HTC One M8 using Tapatalk
You flash the zip via Download mode, not recovery.
You can flash via fastboot but more than likely it fails. Just use the external sd card method.
shivadow said:
You flash the zip via Download mode, not recovery.
You can flash via fastboot but more than likely it fails. Just use the external sd card method.
Click to expand...
Click to collapse
Dear
First time that I flashed firmware I was in download mode and I have tried several times after erasing my whole phone.
When I couldn't fix this problem I just gave it a try of installing everything via twrp recovery.
I relocked my phone and unfortunately it won't unlock again [emoji24] [emoji24] [emoji24] [emoji24]
Sent from my HTC One M8 using Tapatalk
So how far did you get flashing the ruu zip from sdext?. Did you name the file correctly?. Did it begin or did it error out?. Did you check the md5 hash to make sure the file is complete?.
Once you've unlocked the bootloader there is absolutely no reason to lock or relock it.
If the phone boots to os you'll be best purchasing s-off for $25 so that you can flash whatever you need unhindered by security.
If the phone doesn't boot to os then the ruu is the only way forward. If that doesn't work then the phone is bricked.
Hi, have you tried installing the Rom Maximus HD 3.1.0? It could solve the situation ...
Copy the Rom to the External SD and enter TWRP and run a Full Wipe and Format Data, then install the Rom ... you should at least be able to unlock the situation ...
shivadow said:
So how far did you get flashing the ruu zip from sdext?. Did you name the file correctly?. Did it begin or did it error out?. Did you check the md5 hash to make sure the file is complete?.
Once you've unlocked the bootloader there is absolutely no reason to lock or relock it.
If the phone boots to os you'll be best purchasing s-off for $25 so that you can flash whatever you need unhindered by security.
If the phone doesn't boot to os then the ruu is the only way forward. If that doesn't work then the phone is bricked.
Click to expand...
Click to collapse
I can't re-unlock again and think that it should be flashed with riff box or...
I have tried several boot.img and recovery.img but I had no success.
Sent from my HTC One M8 using Tapatalk
paulpier007 said:
Hi, have you tried installing the Rom Maximus HD 3.1.0? It could solve the situation ...
Copy the Rom to the External SD and enter TWRP and run a Full Wipe and Format Data, then install the Rom ... you should at least be able to unlock the situation ...
Click to expand...
Click to collapse
I did the same with Viper rom but it seems that the partitions have damaged seriously.
Now I'm waiting to repair boot with the riff box or other methods.
I hope Saturday they give a good news.
Sent from my HTC One M8 using Tapatalk
I actually need 2.33.401.10 ruu which doesn't exist
Sent from my HTC One M8 using Tapatalk
arses said:
I actually need 2.33.401.10 ruu which doesn't exist
Sent from my HTC One M8 using Tapatalk
Click to expand...
Click to collapse
It likely will show up here - https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Thanks to devs who give their spare time to us.
michaelbsheldon said:
It likely will show up here - https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Thanks to devs who give their spare time to us.
Click to expand...
Click to collapse
Thanks.
I've checked this page before but 2.33.401.10 doesn't exist.
Sent from my HTC One M8 using Tapatalk
michaelbsheldon said:
It likely will show up here - https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Thanks to devs who give their spare time to us.
Click to expand...
Click to collapse
Yes it will if and as it gets available for download.
arses said:
Thanks.
I've checked this page before but 2.33.401.10 doesn't exist.
Click to expand...
Click to collapse
As the OTA is mit Release yet this will need time. My guess is that the RUU will leak approximately two weeks after release of the OTA.
on the other hand it might be wise to try to format all partitions with TWRP, try to install an actual Oreo ROM with root, run SunShine for temp S-OFF and downgrade to 1.27.401.x for the time being.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
Yes it will if and as it gets available for download.
As the OTA is mit Release yet this will need time. My guess is that the RUU will leak approximately two weeks after release of the OTA.
on the other hand it might be wise to try to format all partitions with TWRP, try to install an actual Oreo ROM with root, run SunShine for temp S-OFF and downgrade to 1.27.401.x for the time being.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thanks but when I don't have OS, twrp and relocked bootloader nothing can be done.
Sent from my HTC One M8 using Tapatalk
arses said:
Thanks but when I don't have OS, twrp and relocked bootloader nothing can be done.
Click to expand...
Click to collapse
Well didn't see the relocked mention. Sorry mate.
Sent from my HTC U11 using XDA Labs
Waiting for RUU
CLOSE THIS TOPIC PLEASE
Sent from my HTC One M8 using Tapatalk