Database Info

[Q] [Solved] Keep getting error message "Unfortunately, HTC Sense has stopped"

[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

[Q] Root and Recovery

hi guys, someone can make a little Detailed guide to root and install the recovery on the htc one mini ? the only that i find on XDA was too difficolt for me, please help me

Don't do it if you don't feel comfortable.
1. Unlock your bootloader here. Select "All Other Supported Models" and follow the instructions.
2. Download the Rom, Kernel, and a recovery, verify the MD5 checksums, and then copy the rom and kernel zips to your internal SD card. I'd recommend one of the WWE versions as they don't have a lot of the AT&T bloat.
3. Boot into the bootloader (it says how in the guide showing you how to unlock your bootloader)
4. Select fastboot, plug your phone into your computer.
5. Type "fastboot devices" to make sure it's connected, then type "fastboot flash recovery whateverrecoveryyouused.img".
6. Boot into recovery. Make a backup. Then wipe system, data, cache, and dalvik cache.
7. Reboot into fastboot, then type "fastboot flash boot boot.img" using the boot.img from the Rom you downloaded.
8. Reboot into recovery and install the rom zip using TWRP/ClockworkMod.
9. Reboot into fastboot and type "fastboot flash boot boot.img" using the boot.img from the kernel.
10. Reboot into recovery and flash the kernal zip.
11. Start up your phone, if you flashed a DeOdexed Rom it'll take a little while to boot up.
I'm not sure if you have to flash the boot.img from the rom, then flash it, then flash the boot.img from the kernel and then flash it, but it's best to follow the directions and avoid potentially causing problems.

thanks a lot ! But now i have a problem, when i install the rom , afther flashing it , the phone works correctly, but when i power off it, it doesn't works. when i power on it go in a loop ( the only way to start again the phone is do a "fix permission"). There is a way to slove the problem? ( i i have installed the rom Deoxed that you are posted up, whitout intall the kernel, can be this the problem?
If i install the odex version?
there is any ufflicial rom from htc ?
Please help me guys !

it works even when I enable th option "fast boot" in the " alimentation" menu ..
I looked for the ruu ufficilale but could not find it on the Internet.
I feel so stupid.. and sorry for my English

i have tryed even with flash the kernel, and flash the odex version.. nothing... help :crying:

Think you're gonna have to do what I did. If you're S-OFF you can relock the bootloader and you will get rid of the bootloops
Sent from my HTC One mini using XDA Premium 4 mobile app

So if i relock the bootloader the bootloop gonna end?
But i have a costom rom rooted installed on the phone.
Can you make a list of the things i have to do? Thankyou
Sent from my HTC One mini using xda app-developers app

matty121 said:
So if i relock the bootloader the bootloop gonna end?
But i have a costom rom rooted installed on the phone.
Can you make a list of the things i have to do? Thankyou
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
Yes but it requires you to be S-OFF first Are you able to get booted into the OS at all?
Sent from HTC One Mini using the XDA Premium 4.
S-OFF
Jmz Rom and kernel
---------- Post added 22nd September 2013 at 12:01 AM ---------- Previous post was 21st September 2013 at 11:57 PM ----------
matty121 said:
So if i relock the bootloader the bootloop gonna end?
But i have a costom rom rooted installed on the phone.
Can you make a list of the things i have to do? Thankyou
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
Oh don't relock your bootloader unless you're S-OFF or completely back to stock cuz you'll run into other nasty problems then or could be I should say
Sent from HTC One Mini using the XDA Premium 4.
S-OFF
Jmz Rom and kernel

How can i know if i have S-OFF or S-on?
What i have to do if i have S-OFF?
And what i have to do if i have S-ON?
The phone work the frist time i power on it,but if i power off the phone ,it dont start (it goes in loop,and i must reflash the rom)
Thanks guys.
My phone is in out hands
Sent from my HTC One mini using xda app-developers app

matty121 said:
How can i know if i have S-OFF or S-on?
What i have to do if i have S-OFF?
And what i have to do if i have S-ON?
The phone work the frist time i power on it,but if i power off the phone ,it dont start (it goes in loop,and i must reflash the rom)
Thanks guys.
My phone is in out hands
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
To see if you're S-OFF or S-ON you need to boot into your bootloader by holding the power button + volume down button until you see a white screen with some information on it. See the attached pic Something tells me that you're S-ON cuz you would know if you were S-OFF!
{
"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"
}
Read about how I did in this post http://forum.xda-developers.com/showthread.php?t=2442043
I honestly know how frustrating this is for you right now cuz it wasn't long ago I was in the exact same situation as you are right now! If you choose my path as I did it in the linked post then you probably need to consider power the device off and then start it back up again instead of rebooting.
When you're S-OFF you can safely relock your bootloader and to do that you need to get into your bootloader (hold power button + volume down) and select fastboot. Connect your phone to your computer and run following commands
fastboot devices
(should return a list of connected devices and you should see your device there)
fastboot oem lock
(To relock)
Oh and one super important thing is to take it easy and read everything thoroughly and make sure you understand what this and that will do that's gonna help you a lot. Don't start doing things because you panic lol!
The jmz roms are all here in the HTC one mini Xda forums and the revone is also in the xda forums http://forum.xda-developers.com/showthread.php?t=2314582 Read the OP carefully on this one
HTC One Mini
S-OFF

Does it matter which recovery I pick? Could I also go for the ClockworkMod Recovery Touch 6.0.3.6 one? nvm, I didn't read

XclusionNL said:
Does it matter which recovery I pick? Could I also go for the ClockworkMod Recovery Touch 6.0.3.6 one? nvm, I didn't read
Click to expand...
Click to collapse
That one should work as well
HTC One Mini
S-OFF

I Can download the revone that you're post me in the Link ?
Can you tell more dettalied the point
"14" and "15" of your guide ?
Tomorrow i will try your soluotion !
Thank you very lot!
Sent from my HTC One mini using xda app-developers app

matty121 said:
I Can download the revone that you're post me in the Link ?
Can you tell more dettalied the point
"14" and "15" of your guide ?
Tomorrow i will try your soluotion !
Thank you very lot!
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
Yeah sure! Sorry it's a bit blurry in that post
After you've downloaded the revone it's gonna be in your download folder on your sd card and you need to move revone from that folder to /data/local/tmp/ using a root file explorer like "root explorer" then do the following
- open a terminal emulator (downloaded from play store)
- run the following commands
1. su (enter) (grant the terminal root access when super SU asks for it. A window will pop up asking you this)
2. cd /data/local/tmp/ (enter)
3. chmod 755 revone.bin (if you didn't change the name of the file)
4. ./revone.bin -P (prepare for s-off)
5. The above will probably return something like "failed.....error code 2" I read somewhere here on xda that this error code most likely meant that revone had succeeded and that's why I tried the following
6. Reboot (I could turn off and turn back on again to reboot. If I did the actual reboot command I'd stuck in a bootloop)
7. When you're back up and running meaning you're seeing your home screen again you open the terminal emulator again and type the following commands
8. cd /data/local/tmp/
8. su (enter)
9. ./revone.bin -s 0 -u (that's a zero)
10. Revone should return success and you can reboot safely and go into bootloader and see that you're actually s-off which will allow you relock your bootloader and you'll get rid of the bootloops
To remove the tampered flag just run the command ./revone.bin -t
Hope this works for you. I actually saw someone posting a link to a video somewhere here! I'm gonna try to find it again
EDIT: here's the video http://www.youtube.com/watch?v=J4BWxtjaamM&sns=em showing you how to run the commands. This video is made for the HTC one and the one mini seem to have a problem with rebooting occasionally
HTC One Mini
S-OFF

Ecstacy42 said:
3. Boot into the bootloader (it says how in the guide showing you how to unlock your bootloader)
Click to expand...
Click to collapse
How exactly do you do this step, i can't find the answer anywhere..

Matf661 said:
How exactly do you do this step, i can't find the answer anywhere..
Click to expand...
Click to collapse
Hold power button and volume down button while rebooting or when starting up.
HTC One Mini
S-OFF
Kernel: 3.4.49 jmz stock
Rom: 1.22.401.1
OS: 4.2.2

Hi there!
I have a HTC One Mini, its locked to Orange network (UK). I've tried a load of companies to try and get it unlocked with no luck at all.
So I see the only way is to root the phone, does the method in this thread allow me to get the phone network unlocked so I can use a 3 "Three" sim in it?

No, this is a different type of unlock.

It's worked perfectly,now there anen'r bootloops anymore. You are a genius!
One last question:
When i power on the phone,appears a red write under the htc logo by htc developer, is there a way to remove it?
Now can i install every type of ROM on the phone without problems?
Thank you again !
Inviato dal mio HTC One mini usando XDA Premium HD app

19ninety said:
Hi there!
I have a HTC One Mini, its locked to Orange network (UK). I've tried a load of companies to try and get it unlocked with no luck at all.
So I see the only way is to root the phone, does the method in this thread allow me to get the phone network unlocked so I can use a 3 "Three" sim in it?
Click to expand...
Click to collapse
At first glance this thread is about unlocking the bootloader so that you can install a new recovery (then root)
As of yet there appears to be no use for the recovery OTHER than to get root/su installed (no ROMs or kernels or anything!) Colour me quite depressed.
Removing network locks is a different matter entirely, generally requiring s-off (which appears to be possible for early adopters) then a lot of tinkering.
General rule of thumb: if the phone offers you an update. DO NOT ACCEPT!
Over the years there have been thousands of people that accepted manufacturer updates only to discover the sole purpose of those updates was to patch security holes that would have allowed them to s-off, root, debrand, etc....
Again:
DO NOT ACCEPT OTA UPDATE WITHOUT S-OFF!
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 11.0
ElementalX 5.4

SD Card ejected?

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

T-Mobile Alcatel Pixi 7 (9006w) - What is safe to keep from ota.zip?

I captured the URL for today's OTA update on the T-Mobile Alcatel 9006w via logcat
Code:
wget -O 9006W-2ATBUS1-ota-update.zip http://g2slave-us-east-01.tctmobile.com/19d1572684cd9a2cfee8b0389e135120c36553fe/f74753b81536196fc732138ea00da035c00b8280/105022/69647
I want to use this and a system dump to create a stock rooted .zip, and possibly a separate firmware update.
I am pretty sure I can handle getting /system into a flashable .zip, but I have no idea where to start with a flashable firmware update. I have no clue where to start in order to make sure we don't break fastboot and/or TWRP.
Does anyone have any experience pulling the good stuff out of an OTA?

We should first get a flashable stock .zip. Then a flashable update .zip. We can always make a flashable firmware .zip later.
Sent from my T-Mobile LG G3, SlimLP 5.1.1 beta 0.7

Im currently working on a modified update.zip for us. I should know in a little bit how it all goes.

aclegg2011 said:
Im currently working on a modified update.zip for us. I should know in a little bit how it all goes.
Click to expand...
Click to collapse
Hope it goes well. Keep us posted
Sent from my SM-N910T3 using Tapatalk

tone602 said:
Hope it goes well. Keep us posted
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Ill know in a couple minutes here. You'll need to flash back to stock before doing the update.zip though. You can do the update through twrp np. Keep your fingers crossed.

Nah, no go.
Sent from Tmobile G3, SlimLP 5.1.1 beta v0.8

Dam. Hopefully we can get something soon. Wish I had one that was stock so I could see if ota breaks fastboot
Sent from my 9006W using Tapatalk

So I took the plunge. I fastbooted stock recovery and stock system.img. downloaded the update and installed it. I still had fastboot, was able to flash twrp and get root with the new update!
{
"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 Tmobile Alcatel OneTouch Pixi 7

aclegg2011 said:
So I took the plunge. I fastbooted stock recovery and stock system.img. downloaded the update and installed it. I still had fastboot, was able to flash twrp and get root with the new update!
View attachment 3490826
Sent from my Tmobile Alcatel OneTouch Pixi 7
Click to expand...
Click to collapse
Weird how I couldn't get the stock image and recovery on to get the update. Did you use the files on this post? Something I did wrong?
Sent from my 9006W using Tapatalk

tone602 said:
Weird how I couldn't get the stock image and recovery on to get the update. Did you use the files on this post? Something I did wrong?
Sent from my 9006W using Tapatalk
Click to expand...
Click to collapse
Nah, just did..
Fastboot -I 0x1bbb flash recovery stock_recovery.img
Fastboot -I 0x1bbb flash system stock-system.img
Reboot to stock, accept the update and download. Install. Reboot to stock recovery. Boot into bootloader. Flash twrp. Itll ask to root and youll be good to go.
Sent from my Tmobile Alcatel OneTouch Pixi 7

aclegg2011 said:
Nah, just did..
Fastboot -I 0x1bbb flash recovery stock_recovery.img
Fastboot -I 0x1bbb flash system stock-system.img
Reboot to stock, accept the update and download. Install. Reboot to stock recovery. Boot into bootloader. Flash twrp. Itll ask to root and youll be good to go.
Sent from my Tmobile Alcatel OneTouch Pixi 7
Click to expand...
Click to collapse
When I tried that I downloaded update then hit install. It just reboots to bootloader and not the system. Did yours hang where you have to hold the up and power button to reboot?
Sent from my 9006W using Tapatalk

tone602 said:
When I tried that I downloaded update then hit install. It just reboots to bootloader and not the system. Did yours hang where you have to hold the up and power button to reboot?
Sent from my 9006W using Tapatalk
Click to expand...
Click to collapse
No. You have to reflash the stock recovery else the update won't start. Or it'll go to twrp and do nothing.
Sent from Tmobile G3, SlimLP 5.1.1 beta v0.8

aclegg2011 said:
No. You have to reflash the stock recovery else the update won't start. Or it'll go to twrp and do nothing.
Sent from Tmobile G3, SlimLP 5.1.1 beta v0.8
Click to expand...
Click to collapse
Sweet ! Looks like it worked now ,
Thanks
Sent from my SM-N910T using Tapatalk

Anyway of making a video about how to do this?

I recently got a notification to download a newer update. I'm in the process of reverting to stock and allow the update to proceed. I would like to get a stock system image once that has completed. Please advise the best way to do this so that I can share it.
Thanks.

this thread has been moved to:
https://plus.google.com/communities/...32099448652441

Can anyone upload the stock firmware or any working firmware for this pixi 7 tablet that at least work in the ADB sideload recovery... plz...

Update problem

A few months before I was eager to update and I did a manual update. Everything on the device is completely stock. Now I can't receive updates. What can I do about that? I'm attaching 2 photos below View attachment 4631951
{
"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 U11 using Tapatalk

I think you are at the latest version?.

vchristod84 said:
A few months before I was eager to update and I did a manual update. Everything on the device is completely stock. Now I can't receive updates. What can I do about that? I'm attaching 2 photos below View attachment 4631951View attachment 4631952
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Htc model version? DUGL , UHL or other?CID?
take a look here--->https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
or here-->https://androidfilehost.com/?w=files&flid=183870

fabrizio b92 said:
Htc model version? DUGL , UHL or other?CID?
take a look here--->https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
or here-->https://androidfilehost.com/?w=files&flid=183870
Click to expand...
Click to collapse
HTC 034
Sent from my HTC U11 using Tapatalk

vchristod84 said:
HTC 034
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Ok , are you dugl,uhl or other?Emea or brand?
Reboot in download mode
Follow these steps:
Ensure the phone is turned off.
Press and hold the VOLUME DOWN button and Power button
Continue to hold VOLUME DOWN until the Download mode is displayed.

fabrizio b92 said:
Ok , are you dugl,uhl or other?Emea or brand?
Reboot in download mode
Follow these steps:
Ensure the phone is turned off.
Press and hold the VOLUME DOWN button and Power button
Continue to hold VOLUME DOWN until the Download mode is displayed.
Click to expand...
Click to collapse
I'm DUGL. I have downloaded the ota archive, should I rename it after I get into download mode to start updating?
Sent from my HTC U11 using Tapatalk

vchristod84 said:
I'm DUGL. I have downloaded the ota archive, should I rename it after I get into download mode to start updating?
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Perfect like my htc u11 dugl Emea dual sim. Last firmware is 2.33.401.19
To flash it follow this instruction
-Rename file to 2PZCIMG.zip
-transfer the “2PZCIMG.zip” to the root of the SD card. By root, we mean outside all the folders.
- reboot your HTC U11 into Download mode
-Your device will automatically detect the RUU zip. So, tap the Volume Up button to flash the file
-Once the file has been flashed, your phone will reboot
IMPORTANT: Remember to make a files backup, like photos, videos or other

fabrizio b92 said:
Perfect like my htc u11 dugl Emea dual sim. Last firmware is 2.33.401.19
To flash it follow this instruction
-Rename file to 2PZCIMG.zip
-transfer the “2PZCIMG.zip” to the root of the SD card. By root, we mean outside all the folders.
- reboot your HTC U11 into Download mode
-Your device will automatically detect the RUU zip. So, tap the Volume Up button to flash the file
-Once the file has been flashed, your phone will reboot
IMPORTANT: Remember to make a files backup, like photos, videos or other
Click to expand...
Click to collapse
Am I doing something wrong?
Sent from my iPad using Tapatalk

vchristod84 said:
View attachment 4633395
Am I doing something wrong?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
have you unlock bootloader or twrp?
Try to re.downlaod ota update here: https://androidfilehost.com/?fid=1322778262904002993
Or
if you have a twrp recovery installed, you can downlaode and restore backup last firmware relaese from this link--> https://androidfilehost.com/?fid=1322778262904011693

fabrizio b92 said:
have you unlock bootloader or twrp?
Try to re.downlaod ota update here: https://androidfilehost.com/?fid=1322778262904002993
Or
if you have a twrp recovery installed, you can downlaode and restore backup last firmware relaese from this link--> https://androidfilehost.com/?fid=1322778262904011693
Click to expand...
Click to collapse
I’m completely stock, I re-downloaded the file but still didn’t have any luck, same result...
Sent from my iPad using Tapatalk

Can you flash ota files without ota?

Downgrade your os version,then update ota your os. It is work for me.
You can follow instructions from ziand in this thread https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048

kiroen said:
Downgrade your os version,then update ota your os. It is work for me.
You can follow instructions from ziand in this thread https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
Click to expand...
Click to collapse
I think the wrong that I did was that in the Google spreadsheet I was downloading the ota file and I should have downloaded firstly the ruu... Will try it and report back
Sent from my HTC U11 using Tapatalk