[Q] Stuck HTC without Blinkfeed - Desire 816 Q&A, Help & Troubleshooting

I accidently froze/disabled HTC blinkfeed and now my phone will not load a Launcher. Can I flash the htc blinkfeed apk in recovery to fix this? I have a HTC Desire 816 running kitkat 4.4.2 and sense 6.0 (Stock)
Thanks

Check out this thread for nandroid backup
http://forum.xda-developers.com/desire-816/general/rom-backup-t2862959/post55146690#post55146690

edtrud said:
I accidently froze/disabled HTC blinkfeed and now my phone will not load a Launcher. Can I flash the htc blinkfeed apk in recovery to fix this? I have a HTC Desire 816 running kitkat 4.4.2 and sense 6.0 (Stock)
Thanks
Click to expand...
Click to collapse
Just curious, can you not go back and unfreeze using titanium backup by any chance ??

My phone was stuck on the HTC boot logo screen so no I can't

edtrud said:
My phone was stuck on the HTC boot logo screen so no I can't
Click to expand...
Click to collapse
You have two options now. Assuming your phone is rooted and you can access CWM recovery.
Installing Zeam Launcher via Custom Recovery.
1. Download the Zeam Launcher (file attached - probably very old version but doesnt matter, you need some launcher to get you out of bootscreen)
2. Put it on your sd-card
3. Go to cwm recovery
4. Flash that zip
5. Reboot the system - it should work now.
6. Either update the launcher or install whatever launcher you like until you found the blinkfeed launcher for your device.
OR
Installing the HTC Blinkfeed Launcher apk or any latest Launcher via adb push method.
1. Download the HTC Blinkfeed or any other launcher apk (like ADW launcher etc) of your interest from internet
2. Go to fastboot mode
3. Connect your phone to the computer
4. Once your phone is recognized - Goto adb folder (you would have used it when you rooted your mobile)
5. Open command prompt from that location (Shift + mouse rightclick) and type the following commands
adb remount
adb push HTC BlinkFeed-com.htc.launcher-658011553-v6.1.779245.apk /system/app
adb shell chmod 644 /system/app/HTC BlinkFeed-com.htc.launcher-658011553-v6.1.779245.apk
adb reboot
6. Unplug the phone from computer and try restarting it. It should work like a charm.
You can indeed change the file name of the launcher to something shorter and use the same if you find it difficult to type the long names.
Dont forget to hit thanks, if the above tutorial helps to bring your phone back to life.
All the best.

Worked perfectly thanks!

vbrsekhar said:
Just curious, can you not go back and unfreeze using titanium backup by any chance ??
Click to expand...
Click to collapse
edtrud said:
Worked perfectly thanks!
Click to expand...
Click to collapse
Glad to know that it worked. May I know which one did you follow ? Option 1 or 2 ?

vbrsekhar said:
Glad to know that it worked. May I know which one did you follow ? Option 1 or 2 ?
Click to expand...
Click to collapse
Also can you please change your query title from [Q] to [Solved] so that people would understand that your problem has a solution / fix. Thanks for your understanding.

Related

[HOW-TO] Simplified Root + Recovery + Custom ROM

This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition
titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too
help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.
Thanks a lot.Real helpful
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.
Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.
Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.
Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839
Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.

[Q] Android Revolution HD Sound bug...(htc one X)

Hi there,
I'am searching if there was any bugs reported on the HTC One X(on Android Revolution HD) when change volume for the stock sounds or recording something and when play back the phone dies!?
It seems like every sound i play the phone dies on my except on the Alarm and Notification sounds.. Does anyone had this problem to ?
Please let me know because it very annoying because when someone calls.. my phone dies if i have the sound on.
Thanks already.
Reflash boot image. Sounds like you didn't flash the latest boot image for the Rom
Sent from my HTC One X using xda premium
Reflash boot image,
hi
Since im very new to Android.. following every tutorial there is.. is there a tut for reflashing the boot image.. what do you mean with it? is it just downloading a new Revolution HD again and reflashing it or do i need to do anything else?
Thanks for the help already..
Mike.
iDsigns said:
hi
Since im very new to Android.. following every tutorial there is.. is there a tut for reflashing the boot image.. what do you mean with it? is it just downloading a new Revolution HD again and reflashing it or do i need to do anything else?
Thanks for the help already..
Mike.
Click to expand...
Click to collapse
There is a script in ARHD thread you flash the Boot.img. Run the batch file it flashed the Boot image and clears the cache.
ShyamSasi said:
There is a script in ARHD thread you flash the Boot.img. Run the batch file it flashed the Boot image and clears the cache.
Click to expand...
Click to collapse
ok this is very unclear.. can you clear that up for me please.
iDsigns said:
ok this is very unclear.. can you clear that up for me please.
Click to expand...
Click to collapse
Download this, extract the files anywhere, open up the Android Revolution HD update.zip (the one you flashed) and move the boot.img to the same folder you extracted the above files to.
Then follow these steps. This is taken from the readme included in the above .rar:
1. Turn OFF the device
2. Turn ON the device in bootloader mode (hold power + vol down)
3. Enter fastboot mode using navigation keys
4. Connect the device to PC via USB cable
5. If you are running Windows OS then double click on 'install-boot-windows.bat'. If you are running Linux or Mac OS then select 'install-superboot-linux.sh' or 'install-superboot-mac.sh'
6. Done, now enter recovery and flash Android Revolution HD ROM
Click to expand...
Click to collapse
I don't think step 6 is necessary if you are already running ARHD but I could be wrong.
Super, its runnig.. and sounding Ty..
Link
The link does not working.
Which is the correct file?
Thanks

[ROOT][TUTORIAL] Easy Root & ADB Driver

Due to concerns about the security of a previously shared program, I've pulled the link and info. Please use the following that was shared out from jcase (for some reason it won't let me mention).
If you need to root your stock ROM, please use the method that was posted by in this thread: http://forum.xda-developers.com/showthread.php?t=2539930
Here's the quote about the information there:
jcase said:
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Click to expand...
Click to collapse
Install the app that's attached (also from jcase's thread).
Run the apk, then wait a minute.
Go to the Play Store and download SuperSU.
Go into SuperSU and make sure you have root permissions. Test an app or two.
Remove the app from your phone when you get a chance.
Use the adb command "adb uninstall com.qualcomm.privinit" without the quotes.
You can use also remove it manually a few ways without adb.
--
You can also flash a ROM (even stock ROM) with TWRP and it will ask you if you want to root it. You can select to root with it and then you'll be fine without any need for installation yourself. When I used that method on my last install, I had to reboot my phone to get root to show up. It told me that I wasn't rooted on first boot. Just a simple reboot fixed the problem.
-------------------------------------------------------
Windows ADB Driver:
If you haven't installed ADB drivers for your N1, you can find them here:
https://dc381.4shared.com/download/AVr-h5Lt/adb_driver_windows.zip
Download, extract the folder, and then point your drivers to the android_winusb.inf. Then you should be setup for ADB.
** I will update this as needed. Please let me know if I forgot/missed anything, or if you have anything to add. This requires very little knowledge of Android, and you don't even need the Android SDK installed.
-------------------------------------------------------
Updates/changes:
2013.12.10 - Removed link and information to a program. Updated information reflect other method.
2014.01.30 - Changed link to Windows ADB driver. Oppo took their link down yesterday.
Good stuff and can't wait to get mine soon
Sent from my GT-I9505 using XDA Premium 4 mobile app
I don't trust this, some pics would be nice... kinguser is installed by kingoroot... a VERY suspicious software VERY suspicious
dank101 said:
I don't trust this, some pics would be nice... kinguser is installed by kingoroot... a VERY suspicious software VERY suspicious
Click to expand...
Click to collapse
Feel free to use other methods if you don't trust this one. I wouldn't share it if it was unsafe.
Also, with a custom recovery you could just flash a different ROM or SuperSU directly.
Sent from my N1 using Tapatalk
it just seems like kingoroot too much, main suspicion
jcase posted an apk that provides root without needing a computer that is probably much safer than this. The stock recovery provides a rooted shell out of the box. It would be easy to use that to install SuperSU or something. You can also flash & boot TWRP then hit reboot system and let TWRP install SuperSU & root your device. No need for installing a somewhat suspect root application like this.
Dees_Troy said:
jcase posted an apk that provides root without needing a computer that is probably much safer than this. The stock recovery provides a rooted shell out of the box. It would be easy to use that to install SuperSU or something. You can also flash & boot TWRP then hit reboot system and let TWRP install SuperSU & root your device. No need for installing a somewhat suspect root application like this.
Click to expand...
Click to collapse
I agree, and it seems to much like kingoroot
I've updated the OP and pulled the information about the suspicious app. I personally think that it's fine, but if there is suspicion, I would rather be safe and remove it.
I've used the information the @jcase posted instead. The adb drivers are still there though. :good:
I should have backed up the stock recovery image, I didn't. Anyone happen to have it?
I do have the stock recovery image, and I'm also about to post a how-to for installing CM on TWRP. :good:
Edit: The thread is here - http://forum.xda-developers.com/showthread.php?t=2553165
question show to root cm edition
Any suggestions on how to root n1 cm edition?
giuliano rigon said:
Any suggestions on how to root n1 cm edition?
Click to expand...
Click to collapse
Install or flash SuperSU?
How to root CyanogenMod edition? Oppown won't install at all...
Sent from my N1 using XDA Premium 4 mobile app
m2b999 said:
How to root CyanogenMod edition? Oppown won't install at all...
Sent from my N1 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Make sure the SuperSU file is already on your phone.
Flash TWRP Recovery through Fastboot (vol up + power) with
Code:
fastboot flash recovery your_recovery_filename.img
after it flashes reboot
Code:
fastboot reboot
from there turn off your phone and boot into recovery (vol down + power)
Navigate to where you put the SuperSU.zip file and flash it. Once you do that. Wipe Dalvik Cache and Cache before you reboot the phone into the OS.
After it loads up go to the SuperSU app. Locate the setting where it preserves CM root and uncheck that.
You should have root access now.
Oppown doesn't work on CM.
Espada04 said:
Make sure the SuperSU file is already on your phone.
Flash TWRP Recovery through Fastboot (vol up + power) with
Code:
fastboot flash recovery your_recovery_filename.img
after it flashes reboot
Code:
fastboot reboot
from there turn off your phone and boot into recovery (vol down + power)
Navigate to where you put the SuperSU.zip file and flash it. Once you do that. Wipe Dalvik Cache and Cache before you reboot the phone into the OS.
After it loads up go to the SuperSU app. Locate the setting where it preserves CM root and uncheck that.
You should have root access now.
Oppown doesn't work on CM.
Click to expand...
Click to collapse
Many thanks! Worked like a charm!
a better adb driver
m2b999 said:
Many thanks! Worked like a charm!
Click to expand...
Click to collapse
I am rooted OK.. On omnirom. But when i attach my phone my computer cannot see the file system.. Is there a better adb driver somewhere? Thanks giuliano rigon
giuliano rigon said:
I am rooted OK.. On omnirom. But when i attach my phone my computer cannot see the file system.. Is there a better adb driver somewhere?
Click to expand...
Click to collapse
The computer should only show the storage (onboard sdcard) part, or do you mean your adb isn't working properly?
Can you please explain what is showing what, and what you want to see?
Sent from my N1 using Tapatalk
i cannot see sdcard
Harfainx said:
The computer should only show the storage (onboard sdcard) part, or do you mean your adb isn't working properly?
Can you please explain what is showing what, and what you want to see?
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
I want to see files and copy them to my PC using the inner memory ad external storage.. I thought that adb might nave some problems.. I can flash the phone so communication is working.. Bit i do not see the fila system of the phone.. Help..
giuliano rigon said:
I want to see files and copy them to my PC using the inner memory ad external storage.. I thought that adb might nave some problems.. I can flash the phone so communication is working.. Bit i do not see the fila system of the phone.. Help..
Click to expand...
Click to collapse
Are you able to see the sdcard portion? That should be all that you can see when you mount the phone to your PC.
Harfainx said:
Are you able to see the sdcard portion? That should be all that you can see when you mount the phone to your PC.
Click to expand...
Click to collapse
So how do i access files on my phone.. I am copying them with dropbox bit it is getting stale

[Q] New user rooted unworking phone

Android 4.2.2
HTC Sense 5.5
Software number NuSenseONE-KitKat-m7vzw_RD.1.0_4.19.631.9
HTC ASK ALI level 5.68
Kernel Version 3.4.10-NUM3rn3l- kk-S55
Phone doesn't connect to moblie data .
Xposed installer not working
SuperSU binary not installed?
I just need my phone back to normal I'll figure out this SU and root thing later. Factory reset doesn't do anything. Screen says I'm running a developer version of the OS
Help thanks
Jamesdbritt said:
Android 4.2.2
HTC Sense 5.5
Software number NuSenseONE-KitKat-m7vzw_RD.1.0_4.19.631.9
HTC ASK ALI level 5.68
Kernel Version 3.4.10-NUM3rn3l- kk-S55
Phone doesn't connect to moblie data .
Xposed installer not working
SuperSU binary not installed?
I just need my phone back to normal I'll figure out this SU and root thing later. Factory reset doesn't do anything. Screen says I'm running a developer version of the OS
Help thanks
Click to expand...
Click to collapse
did you make a backup of your stock rom or the rom you had before you flashed the one you are currently having problems with?
nty123 said:
did you make a backup of your stock rom or the rom you had before you flashed the one you are currently having problems with?
Click to expand...
Click to collapse
I was not the one that flashed the rom. I bought the phone three days ago and it was already like this.
Jamesdbritt said:
I was not the one that flashed the rom. I bought the phone three days ago and it was already like this.
Click to expand...
Click to collapse
can you boot into recovery? either twrp or cwm
some updates.. I've been working on it.
Android 4.2.2
HTC Sense 5.5
Software number NuSenseONE-KitKat-m7vzw_RD.1.0_4.19.631.9
HTC ASK ALI level 5.68
Kernel Version 3.4.10-NUM3rn3l- kk-S55
???Phone doesn't connect to moblie data ???
Installed HTC Sync Manager to PC
on Device
Went into boot menu and went to recovery TWRP reinstalled SuperSU and Xposed installer
what is a ROM ? what do I do with the SDK bundle?
Jamesdbritt said:
some updates.. I've been working on it.
Android 4.2.2
HTC Sense 5.5
Software number NuSenseONE-KitKat-m7vzw_RD.1.0_4.19.631.9
HTC ASK ALI level 5.68
Kernel Version 3.4.10-NUM3rn3l- kk-S55
???Phone doesn't connect to moblie data ???
Installed HTC Sync Manager to PC
on Device
Went into boot menu and went to recovery TWRP reinstalled SuperSU and Xposed installer
what is a ROM ? what do I do with the SDK bundle?
Click to expand...
Click to collapse
a rom is a modified software of android from a developer that you can install on your phone through a recovery, it's good that you can boot into recovery but, I'm not completely sure what's going on, the rom that is currently on your device could have a problem and not able to connect to mobile data. you could download a different rom and flash it onto your phone and see if that fixes it, there are plenty of amazing ones to choose from on this forum http://forum.xda-developers.com/verizon-htc-one/development even though you have the mobile data problem on your current rom i would still make a backup of your current rom to go back to incase anything happens when (if) you flash a different one
nty123 said:
a rom is a modified software of android from a developer that you can install on your phone through a recovery, it's good that you can boot into recovery but, I'm not completely sure what's going on, the rom that is currently on your device could have a problem and not able to connect to mobile data. you could download a different rom and flash it onto your phone and see if that fixes it, there are plenty of amazing ones to choose from on this forum http://forum.xda-developers.com/verizon-htc-one/development even though you have the mobile data problem on your current rom i would still make a backup of your current rom to go back to incase anything happens when (if) you flash a different one
Click to expand...
Click to collapse
I am not sure how to flash roms is there a guide?
Jamesdbritt said:
I am not sure how to flash roms is there a guide?
Click to expand...
Click to collapse
there are many videos online but its pretty easy, find a rom and gapps (if its included with the rom) then download those two to your sd card( make sure they are in .zip format) once downloaded boot into twrp and choose the backup icon and swipe to backup. when that's done you will press the wipe icon and perform a factory reset(you lose all data so make sure you have contacts synced to google) when its done wiping your data go back and install zip and locate the downloaded rom and choose that then if you downloaded the gapps(google apps) choose add more zips near the bottom and find that .zip. when you have everything you will then swipe to flash. when its done tap reboot and it will load your new rom.
nty123 said:
there are many videos online but its pretty easy, find a rom and gapps (if its included with the rom) then download those two to your sd card( make sure they are in .zip format) once downloaded boot into twrp and choose the backup icon and swipe to backup. when that's done you will press the wipe icon and perform a factory reset(you lose all data so make sure you have contacts synced to google) when its done wiping your data go back and install zip and locate the downloaded rom and choose that then if you downloaded the gapps(google apps) choose add more zips near the bottom and find that .zip. when you have everything you will then swipe to flash. when its done tap reboot and it will load your new rom.
Click to expand...
Click to collapse
ok I am going to try ViperOne 5.0.0 | 4.19.401.8
ok so why backup the settings if they aren't working now?
Jamesdbritt said:
ok I am going to try ViperOne 5.0.0 | 4.19.401.8
ok so why backup the settings if they aren't working now?
Click to expand...
Click to collapse
Maybe this will save you some time.
Maybe not....
Did you put a working active Sim card of your own into the phone?
That ROM that's on the phone currently, works just fine for verizon cell and data services.
You're welcome to change the ROM to whatever one you want.
Just trying to help you find the actual root of your problem.
Sent from my HTC6435LVW using Tapatalk
Sounds like you're new to the world of modding which is perfectly fine because we all had to start somewhere. You want to familiarize yourself with the basics before you get too far over your head though. Here's a basic terminology guide that will help you right now: http://www.gizmodo.co.uk/2013/05/the-dummys-guide-to-android-rooting-everything-you-need-to-know/
I don't know what the person before you did, but as santod has explained NuSense has perfectly working data. I'm using it now and have never had issue. It's my personal favorite rom, but there are many out there right now you should be trying out for yourself and forming your own conclusions. Almost everyone will have a different opinion on the "best rom" which is why it's a question you'll see avoided around here. Personally, I would start on a "stock" rom like the one offered here: http://forum.xda-developers.com/showthread.php?t=2485319. That thread also includes very important instructions on how to update your firmware (for better radio performance among other things). Good luck and don't be afraid to ask questions before doing something you're not sure of.
No operating system
accidently wiped everything clean the PC cannot recognize the device says I need a driver. I still have twrp but the backup was wiped on accident what do I do to fix it?
I think you'll have to push a rom from your computer to the phone using ADB and then flash it in recovery. I've never had to do that so hopefully someone can chime in with more details.
You need the adb debugging tools installed on your computer. Plus HTC drivers. Once you have those installed, you can try flashing a RUU. Here's 4.2.2 RUU http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/ . This tells you how to setup adb http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ . To flash the RUU, place the RUU in the same folder as your adb tools, and rename it RUU.zip. In the command prompt type, fastboot oem rebootRUU , then hit enter. Then type, fastboot flash zip RUU.zip ,then hit enter. Afterit finishes you'll have to type fastboot flash zip RUU.zip one more time . Then after about ten minutes it will finish and you'll type fastboot reboot-hboot. Then restart phone.
joeymagnus1 said:
You need the adb debugging tools installed on your computer. Plus HTC drivers. Once you have those installed, you can try flashing a RUU. Here's 4.2.2 RUU http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/ . This tells you how to setup adb http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ . To flash the RUU, place the RUU in the same folder as your adb tools, and rename it RUU.zip. In the command prompt type, fastboot oem rebootRUU , then hit enter. Then type, fastboot flash zip RUU.zip ,then hit enter. Afterit finishes you'll have to type fastboot flash zip RUU.zip one more time . Then after about ten minutes it will finish and you'll type fastboot reboot-hboot. Then restart phone.
Click to expand...
Click to collapse
the howtogeek site will not come up it crashes IE everytime
the more I read , everything says I need HTC windows seven drivers where can I get them I can not find a reliable source
Read there are plenty of things on the net that will help you with your problems.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
http://vzw1files.dyndns.org/ADB/
bigjohn6582 said:
Read there are plenty of things on the net that will help you with your problems.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this did not help at all
cmlusco said:
http://vzw1files.dyndns.org/ADB/
Click to expand...
Click to collapse
Great link but does not at all address the question. this thread can be closed problem was solved by @clsA @alray and @nkk71

Xposed Framework for One M8?

Anyone installed the Xposed Framework and got it working on an One M8 Rooted? Because tried to install it didn't work, the apk installs but when you try to do install/update it just reboots but the framework never installs???
Just install ARHD, it`s pretty much just an optimized stock rom, flash it, if you get a black screen at the end, hold vol up and power until reboot, initial boot may take 10mins, after that, install xposed through recovery method.
ryanjsoo said:
Just install ARHD, it`s pretty much just an optimized stock rom, flash it, if you get a black screen at the end, hold vol up and power until reboot, initial boot may take 10mins, after that, install xposed through recovery method.
Click to expand...
Click to collapse
Thanks I normally don't like using custom ROM's but as I like using xposed and if it's currently the only way to use it on the One m8 then maybe for the time being I will install ARHD, looking at the thread the feedback has been positive, again thanks for the heads up on flashing it.
I don't have an M8 but I'm lurking in the forums.
Try installing it with the recovery zip (available in 2.5).
I think S-On prevents /system from being written to
Sent from my C6903 using Tapatalk
With Xposed 2.5 you need to either
- Have a rom with system protection disabled
- Or choose to install via ZIP where it will copy an installer to your SDcard and you run it from recovery.
I am rooted on stock m8-
the easiest way to install xposed is by changing "install mode" under the framework tab to "Recvery (flash zip automatically". It'll do all the work for you, basically the way as described above.
You can also just flash a kernel with write protection turned off, and do it the old way.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
suprtrukr425 said:
You can also just flash a kernel with write protection turned off, and do it the old way.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the simplest way to do it, imo.
Last night i installed toolbox 6, the updated version and for some reason, it corrupted my xposed framework. I got a message that said it wasn't installed. So i tried to install it via "classical mode" and my phone restarts without installing the framework. I was on ARHD 5.0 with elementalX 0.9 installed. I then tried:
1. Uninstall and reinstall xposed on classical method again, it rebooted and it didn't install
2. Changed method to recovery install and didn't install (Got message "cp:' can't open '/system/bin/app_process': Read-only file system"
E: Error in /cache/recovery/xposed-installer-Recovery.zip
3. Reinstalled ElementalX and tried again via classical and Recovery method and it didn't install
4. Dirty flash ROM and ElementalX and tried again via classical and Recovery method and it didn't install
What else can i tried instead of doing a full wipe install of the ROM??
BTW Xposed was installed and working fine until i installed the updated version of toolbox 6 , the alpha version was working great already
Xposed doesn't work with ART, make sure you are using dalvik
Hey Guys,
I have soff, unlocked but stock recovery... will the xposed installer be able to install it via the stock recovery? (automatically as you described before)?
thanks
No.
Does it give the ability to double tap and then the phone goes to sleep ?
Or you just use GPE.
I have the GPE RUU and Xposed works beautifully
SilentHunter316 said:
Does it give the ability to double tap and then the phone goes to sleep ?
Click to expand...
Click to collapse
Now yet. It does have gestures tho. I set mine to swipe down to go to sleep. Lots and lots of other goodies in ROM toolbox 6
I'm running stock s-off and root with xposed 2.6.1 and have not had any issues at all. Right now I'm only using sense 6 toolbox and greenify. I have only had two problems and don't believe them to be related. The first is the stock message app FC on voicemail and the second was a soft brick related to freezing Blink Feed.
I installed Xposed from my sdcard as well as sense 6. Didn't run into anything. Double check as above stated and make sure you are no using ART and also check about your unknown sources. I also have USB Debugging on as well not sure it that will matter or not but helps if you use TB or Rom Toolbox.
EDIT: You really need to look into a custom recovery, I use philz and love it. Having root and S-off but not using a custom recovery is kinda like owning a Ferrari but you can't drive a stick.
I have rooted One m8 with TWRP recovery, but it's still s-on, does xposed work also on s-on smartphone?
aluli95 said:
I have rooted One m8 with TWRP recovery, but it's still s-on, does xposed work also on s-on smartphone?
Click to expand...
Click to collapse
Of course it will work.It has nothing to do with s-on or s-off.Remember with s-on you can change kernel and recovery partitions but with s-off you can do more like changing radio etc
some on help me HTC one M8
do any one hv any solution for this problem....
i tried many times.... but not abel to solve the problem.....
plz some one guide me what shall i do to solve this problem....
i hv already installed the Xposed Framework Installer (Flashable Zip) file v2.4.1
also updated under xposed installer many time but still this error coming n not abel to use it fully...
advance thanks for any one who could help me...
i tries so many times but all time i got the same msg attached screenshot..plz plz help
htc one m8
ROM - Android Revolution HD 8.1
chetan hingrajiya said:
do any one hv any solution for this problem....
i tried many times.... but not abel to solve the problem.....
plz some one guide me what shall i do to solve this problem....
i hv already installed the Xposed Framework Installer (Flashable Zip) file v2.4.1
also updated under xposed installer many time but still this error coming n not abel to use it fully...
advance thanks for any one who could help me...
i tries so many times but all time i got the same msg attached screenshot..plz plz help
htc one m8
ROM - Android Revolution HD 8.1
Click to expand...
Click to collapse
change installation mode to recovery

Categories

Resources