Related
Crsdr37 said:
Alright Guys in the USA. I will be posting the .img files to fix your device or update your device to 1.141.07 if you have either used the chinese update fix or some other various fix that left you with a different boot image. The instructions are simple.
1. Connect your tablet to the computer via USB. Put the boot.img and the system.img on your SD Card. Also put the Update.zip then use a file explorer to move the update.zip to the root of your SD card. Which is external SD. If you use Astro. (Alternatively you can just take your SD card out and put it in your computer to put the update.zip.)
2. You need to first push the boot.img
-Open ADB type su then hit enter. (your device will prompt for superuser you must select allow) Then enter the command below.
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2 (hit Enter)
3. Then push the system.img
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
4. Force shutdown your device when those finish (as your screen may not turn on.)Then hold volume - and the power button "until the green android comes up very important do not let them go just because the device turns on" to start the update.zip. Let it finish (Your device will reboot when it completes.
5. Enjoy the fact your device is back to stock and you can now update when future updates release.
To push the files you will need adb shell. If you dont know what that is look it up, It is part of the android development kit. Second these 2 commands will push the files to their proper mount block. You must push the boot.img first then the system.img These files are for the USA update 1.141.07
http://www.megaupload.com/?d=TNDCAYC8 - System.img -MD5-2b4e2fea567ac883bb483fc96b1fdc9d
http://www.mediafire.com/?7b5llkk8bnmnd23 -Update.zip
http://www.mediafire.com/?3qahjh3twi6jc9t -Boot.img -MD5-4477d6739dd1e3b3ba1dbf94be7fe8f0
Here are 2 Mirrors To download the boot.img you will need to download both as the uploader made it a 2 part file making it easier for some countries to download. Give thanks yo ardatdat if these came in handy.
http://www.zshare.net/download/91195486183633a0/
http://www.zshare.net/download/9119547812fdf5fa/
I will check periodically on this thread if anyone has questions or needs Help. Guve a huge shout out to deckofficer54 as he is a co-worker and friend that dumped these files for me when I screwed my system up.
Click to expand...
Click to collapse
** Alright guys I am just posting this link for when you just do the update.zip because you are already on 1.104.05_COM_GEN1 and you have a different kernel then the update.zip, What will happen is when you reboot the tablet from just doing the update.zip you may have WIFI error. These files should resolve that issue. Once again they are only if you have WIFI Error on reboot. To install these you will need some type of file explorer that has rw access to the file system. I rec. Root Explorer. To install these follow these instructions.
1. Copy both modules to your SD card does not matter where.
2. With your File Explorer/Manager Copy both of these files. (Root Explorer will let you multi-select if you hit the menu button.)
3. Navigate to System/Lib/Modules.
4. **This step is very important- You must Mount your System for RW access. If you don't they will not copy. Once you have RW just hit the paste button and then reboot your device.
5. **This step is for anyone still having wifi error after reboot. (Stop being lazy lol and just do all the steps. From the top by mounting the boot.img and system.img that way your device is 100% stock there for no checksum issues.
http://forum.xda-developers.com/attachment.php?attachmentid=601473&d=1305842073 - This is the wifi modules Download Link.
Thank you thor2002ro for posting these on your kernel modules thread. Which is found here for anyone having any other issues.
http://forum.xda-developers.com/showthread.php?t=1058713
Happy Updating
Alright guys here is the list of supporters thus far for the unbricking and or updating of your tablet. If I missed someone let me know.
Supporters:
Euclid's Brother -Awesome tool to flash the images Making your lives easier one click at a time. If you want an easier way download these images and use this app https://market.android.com/details?id=com.interphaze.Acer_ROM_Flasher
bhageman -Donation
aerichards1977 -Donation
Sent from my PC36100 using XDA Premium App
thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
EDIT1: I even not lost my settings and can set the language to German too!!
EDIT2: Root gone (as expected), used Gingerbreak (tab version) and everything works fine.
phone.ds said:
Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
Click to expand...
Click to collapse
Your Very Welcome. Took me some time to get all the files but this **** works like a frickin charm. I wish it wasnt such a pain in the ass but hey its fixed.
ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
well the only thing I can think of it either the lib modules for wifi are messed up in which case I can post a link with them or the kernel is different. I would use the 2 .img that I posted then use the update zip. That way the images replace your kernel which is always the root cause of wifi errors.
here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
http://www.megaupload.com/?d=OKU671AP
futty said:
thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?
Click to expand...
Click to collapse
Yes you are now stock and able to update when they release 3.1
dont we need to flash flexrom.img to be 100% stock?
The flexrom was flashed with the update zip
Sent from my A500 using XDA Premium App
confirmed working as well.
Crsdr37 said:
here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
Click to expand...
Click to collapse
Am I missing something or did you maybe forget the link =P
Ah **** lol give me 1 second
http://www.megaupload.com/?d=OKU671AP
Sent from my A500 using XDA Premium App
Did those libs help at all?a like I said if they don't the only fix I I now would be to go back to the german or chinese update then flash both. Img then update.
Sent from my A500 using XDA Premium App
Image updates
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.
You get that only when do don't do all three'. Once you reboot after pushing the 2 images. You have to hold down the volume - and the power button it will then run the update zip to complete.
Sent from my A500 using XDA Premium App
Crsdr37 said:
Yes you are now stock and able to update when they release 3.1
Click to expand...
Click to collapse
thanks so much again. you are a god i bet you helped millions by doing this
That was my intentions I came from the evo forums. Everybody there helps each other. Im just hoping people here pick it up and start helping when people have questions.
Sent from my A500 using XDA Premium App
ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
Did you ever get wifi working
Sent from my A500 using XDA Premium App
tomlogan1 said:
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.
Click to expand...
Click to collapse
Were u able to get past the checksum error?
Sent from my A500 using XDA Premium App
UPDATED XOOM FLASHING GUIDE 02/02/12
I recently bought a US Xoom MZ604 and had trouble flashing it initially. I came to a realization that the newer models of Xoom reinstalls the Stock Recovery after you flash a custom Recovery (eg. CWM, Rogue Recovery etc). This is uber frustrating for newer Xoom owners, especially those who are new to the flashing community, simply because you don not know exactly what's going on.
Also, I could not find any proper, full and updated guide to flashing your Xoom. So i decided to take the initiative to do so.
WARNING: I DO NOT TAKE ANY RESPONSIBILITY IF YOUR XOOM TURNS INTO A USELESS BRICK. BY FOLLOWING THIS GUIDE, YOU WILL VOID YOUR XOOM WARRANTY WITH MOTOROLA. YOU HAVE BEEN WARNED TO EXERCISE CAUTION WHILE FOLLOWING THIS GUIDE. STRICTLY FOLLOW THIS GUIDE AND I ASSURE YOU, NOTHING WOULD GO WRONG.
In order to follow this guide, you need fundamental knowledge of ADB and Fastboot for Android. Search around the forum for this knowledge.
STEP 1: Obtaining Required Materials
a.) Download the latest version of Android SDK from HERE and install it into your the root of your C: drive.
b.) Download the latest version of Java SE from HERE and install.
c.) Download and Install the latest version of Motorola USB Drivers from HERE.
STEP 2: Unlocking your Bootloader
What is a Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. Source: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
Click to expand...
Click to collapse
1.) Make sure your Xoom is turned on. Connect it to your PC via USB.
2.) On your PC, open up File Explorer and Browse to:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
3.) In that directory, make sure nothing is selected, SHIFT+Right Click into empty space and select "Open command window here".
4.) Command Prompt will open up. Type the following command:
adb reboot bootloader
Click to expand...
Click to collapse
Your XOOM will reboot into the bootloader showing "Starting Fastboot Support Protocol".
6.) Type the following command into the Command Prompt to unlock your bootloader:
fastboot oem unlock
Click to expand...
Click to collapse
7.) Read the warning and follow the instructions on the Xoom Tablet itself from this point onwards. Use the Volume Down key to navigate to 'Accept' the agreement and press Volume Up to select.
8.) Once selected, your Xoom will now unlock and format itself, meaning, all data will be cleared and you will back to a factory rest.
9.) Reboot your Xoom with the following command:
fastboot reboot
Click to expand...
Click to collapse
10.) Exit Command Prompt.
STEP 3: Rooting your Xoom
1.) Download the latest version of "Universal Xoom Root" from this thread. Place the .ZIP file into the root of your SD card.
2. Download this version of "ClockworkMod Recovery - Modified for Motorola Xoom" and place it into this directory:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will your new Recovery. MAKE SURE THAT IT IS IN .IMG FORMAT.
2.) With your Xoom still connected to your PC, type the following commands into Command Prompt (open up using the same method as STEP 1) to install your new Recovery.
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
3.) Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery. If you miss this window and somehow end up booting your Xoom normally, repeat from STEP 3, section 2 onwards again. DO NOT CLOSE THE COMMAND PROMPT WINDOW.
4.)To root your Xoom, please perform the following:
"install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Click to expand...
Click to collapse
After the root flashes itself, DO NOT REBOOT YOUR XOOM!
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
6.) Reboot with CWM. Let your Xoom boot normally.
To test whether the root and flashing of CWM has been successful, type the following into your command prompt:
adb reboot recovery
Click to expand...
Click to collapse
If you are able to access the new Recovery, CONGRATULATIONS, you have successfully UNLOCKED & ROOTED your Xoom.
I would like to thank the Xoom Android community for your valuable commitment to into Xoom Android Development. Without you guys, the Xoom wouldn't feel much powerful in terms of usage. Also, I'd like to extend my gratitude to okantomi for his help when I first started out.
Those those experienced users of Xoom, please kindly help the newbies like me answer their questions in this thread. Could I also request the mods to sticky this thread for reference.
NOTE: For users who would like to revert to the original recovery, type the following into ADB: (tip provided by wontoniii)
adb shell mv /system/recovery-from-boot.p.old /system/recovery-from-boot.p
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
Reference Threads:
1.) [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
2.) [ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)
3.) [Root] Universal Xoom Root - ANY XOOM ANY UPDATE
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
This can be easily reverted with:
adb remount
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
Click to expand...
Click to collapse
In case someone could want the old recovery back without flashing anything
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I believe your method is better, at least there's still a recovery to revert to in case something goes wrong. I'll add it to the guide. Thanks for the suggestion!
Sent from my Xoom using Tapatalk
My tool can do it automatically, check on the signature LordAIOTool, and if you guys can please test and tell me the results
---------- Post added at 08:57 PM ---------- Previous post was at 08:39 PM ----------
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I liked your idea too, will put on my tool (can I?)
XxLordxX said:
I liked your idea too, will put on my tool (can I?)
Click to expand...
Click to collapse
Sure, no prob
Thread moved to General.
This seams to be a good guide can anyone tell me if it works it is more detailed than the other guide ???? and why was it moved to general
This guide is great and easy and very updated i dont know why other people dont use it. One thing tho you should be more clear on how to reboot into recovery tell them to press volume up + power then let go then wait three seconds and after logo and press only the volume down
Having a problem with using your guide
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
dstruble said:
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Click to expand...
Click to collapse
kewlguru said:
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
Click to expand...
Click to collapse
That did the trick I figured it was something simple like that. Thanks for the help.
Superb Guide!
Many thanks, I spent the best part of a day trying various methods but found this to be the most n00b friendly
1 point it may be worth adding is to use adb you must have java installed on your pc, without you get error "adb.exe is not a valid win32 application"
first time root/flash rom question
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Don_Don said:
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Click to expand...
Click to collapse
Ihave similar story m8. I spent the majority of yesterday reading and learning how to root. This is by far the easiest guide to follow to ulock and root your xoom.
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
At which point do I back up data already on Xoom? Will there be any data loss?
Don_Don said:
At which point do I back up data already on Xoom? Will there be any data loss?
Click to expand...
Click to collapse
You have to backup your data before unlocking the bootloader, which is the VERY FIRST step.
gbenj said:
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
Click to expand...
Click to collapse
Yes you are right. Thanks for pointing that it, it could have confused some. I'll rectify that right away.
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
TADitto said:
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
Click to expand...
Click to collapse
Yes, this process will work regardless of your OS.
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Restore your Nandroid.
Edit: just saw that you said you didn't make one. Lesson learned, I guess. You can adb sideload files from within recovery. Do this, sideload a stock rom, flash it, and it will give you a normal build.prop.
Sent from my iPad 4
Use adb to push the backup build.prop and overwrite the current one.
I'm assuming that u have the backup on your PC? If not, then download the stock ROM and extract the build.prop from /system.
Use the following command to push it:
Code:
adb push /path/to/build.prop \system
Sent from my HTC Desire using xda app-developers app
megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
If it's stock android, you could actually just wipe /system , then using adb in recovery you can push up a zip of the stock 4.2.2 isntall, and just flash that.
If build.prop is all you changed in /system then that should be fine to do, which will be especially easy if you can just grab a pre-rooted flashable zip of 4.2.2 stock.
megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?
megaman1574 said:
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?
Click to expand...
Click to collapse
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
Where should I look to get a stock rom?
megaman1574 said:
Where should I look to get a stock rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4
mitchdickson said:
just saw that you said you didn't make one. Lesson learned, I guess.
Click to expand...
Click to collapse
Yes, definitely. I can't remember why I didn't make a backup...
mitchdickson said:
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4
Click to expand...
Click to collapse
Ok, if I can't fix it by tonight I'll download this and flash it (My download limit during the day is too small to download it. That's why I'm trying to fix it without doing that)
kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
I'm not that good with Android, how and when do use this "logcat"?
megaman1574 said:
I'm not that good with Android, how and when do use this "logcat"?
Click to expand...
Click to collapse
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.
kbeezie said:
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.
Click to expand...
Click to collapse
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.
megaman1574 said:
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.
Click to expand...
Click to collapse
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).
kbeezie said:
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).
Click to expand...
Click to collapse
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.
megaman1574 said:
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.
Click to expand...
Click to collapse
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31
kbeezie said:
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31
Click to expand...
Click to collapse
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?
megaman1574 said:
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?
Click to expand...
Click to collapse
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).
Ok... I had managed to move the backup of build.prop into system using TWRP's file manager but after THAT it wouldn't even show the Nexus logo. Hence the reason I said nothing about this (I thought it to be a dead end). Just as I was about to give up, I was reading an obscure post on Androidforums.com and came across a post telling the guy to pull build.prop, edit it, push it back, and chmod it to 644. I haven't the FAINTEST clue what the hell that is, but I remembered that "chmod" and "chmod 755" were two options when you tap on a file in TWRP's file manager. So I raced back in there, deleted the broken build.prop, moved the backup into system, tapped on it and pressed "chmod 755" rebooted and it worked! Anyone have any idea what is was that I did? What is chmod? But basically:
I FIXED IT YAY!!!
Thanks everyone for your help. I've been desperate to fix it, in fact, when I broke it was an hour before I had to leave for a weekend trip, so I had no phone.
kbeezie said:
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).
Click to expand...
Click to collapse
My Nexus 7 is rooted with TWRP and it received an OTA update. But anyway, if you refer to my last post I fixed it.
Edit: However, it did unroot it. (not hard to reroot though)
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's two different methods to disable it entirely. You could also extend these to replace the sound with one of your own.
1. Alter the xml file that references the sound file
Pre-requisites:
Handset is rooted
Root-enabled file manager app installed (e.g. Total Commander)
Howto steps:
Detailed in this post later in the thread.
2. Remove/hide the startup sound file
Pre-requisites:
Handset is rooted and has a custom recovery partition (e.g. TWRP or CWM)
ADB install and working on desktop computer
Howto steps:
1. Put your phone into recovery
2. Open adb shell
3. Mount /system
4. Change directory to /system/customize/resource
5. Rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Thanks for this, worked a charm and didn't need to S-OFF!
Helpful! thank you very much bro.
Helpful! thank you very much bro.
dr_diem said:
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's how to disable it entirely:
Pre-requisites:
Handset is rooted
Put your phone into recovery
Get a working adb shell
1. Mount /system
2. change directory to /system/customize/resource
3. rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Click to expand...
Click to collapse
Brilliant thank you. Will do this soon.
dr_diem said:
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's how to disable it entirely:
Pre-requisites:
Handset is rooted
Put your phone into recovery
Get a working adb shell
1. Mount /system
2. change directory to /system/customize/resource
3. rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Click to expand...
Click to collapse
"Get a working adb shell" meaning what? Having a working fastboot? could you please explain?
M_Shaaban said:
"Get a working adb shell" meaning what? Having a working fastboot? could you please explain?
Click to expand...
Click to collapse
Do some searching here on the forums - adb stands for Android Desktop Bridge and is freely downloadable as part of the Android SDK. It enables you to access your Android device in various ways from your desktop computer. adb shell is a way to open an interactive shell (a 'command prompt') on the Android device. There are howtos on these forums (and indeed all over the 'net) that'll explain how to get ADB set up for your desktop OS.
Ian
dr_diem said:
Do some searching here on the forums - adb stands for Android Desktop Bridge and is freely downloadable as part of the Android SDK. It enables you to access your Android device in various ways from your desktop computer. adb shell is a way to open an interactive shell (a 'command prompt') on the Android device. There are howtos on these forums (and indeed all over the 'net) that'll explain how to get ADB set up for your desktop OS.
Ian
Click to expand...
Click to collapse
I did do that and I could reboot to recovery by entering command "adb reboot recovery" but then when I enter adb shell, it says device not found. What should I do? Could there be a quick video tutorial on how to do so?
M_Shaaban said:
I did do that and I could reboot to recovery by entering command "adb reboot recovery" but then when I enter adb shell, it says device not found. What should I do? Could there be a quick video tutorial on how to do so?
Click to expand...
Click to collapse
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
dr_diem said:
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
Click to expand...
Click to collapse
OK will try and do that. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added 16th December 2013 at 12:00 AM ---------- Previous post was 15th December 2013 at 11:35 PM ----------
dr_diem said:
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
Click to expand...
Click to collapse
@dr_diem adb shell works fine with phone is on. Now time to find a solution to be working on recovery. My phone is rooted but I flashed stock recovery back after rooting. Is that OK? Or must it be done via custom recovery? Did it do it via stock or custom recovery? Also my Windows is 8.1 but I can access fastboot (commands and all) without a problem. On stock recovery >adb shell > device not found!
M_Shaaban said:
OK will try and do that. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added 16th December 2013 at 12:00 AM ---------- Previous post was 15th December 2013 at 11:35 PM ----------
@dr_diem adb shell works fine with phone is on. Now time to find a solution to be working on recovery. My phone is rooted but I flashed stock recovery back after rooting. Is that OK? Or must it be done via custom recovery? Did it do it via stock or custom recovery? Also my Windows is 8.1 but I can access fastboot (commands and all) without a problem. On stock recovery >adb shell > device not found!
Click to expand...
Click to collapse
I've just done some quick Googling and indeed yes a custom recovery is required to use adb whilst in recovery (according to this page that seems pretty sure of itself). Apologies that my howto didn't make that clear (that being because I didn't know about the requirement at the time!); I'll update it in that regard now.
Ian
dr_diem said:
I've just done some quick Googling and indeed yes a custom recovery is required to use adb whilst in recovery (according to this page that seems pretty sure of itself). Apologies that my howto didn't make that clear (that being because I didn't know about the requirement at the time!); I'll update it in that regard now.
Ian
Click to expand...
Click to collapse
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
M_Shaaban said:
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
Click to expand...
Click to collapse
I'm sorry but I am out of ideas on this I can only suggest you do some extended web and/or xda-developers searching to learn reasons for this error. I'm quite sure you'll find the answer given the size of our community; please do post back here when you find it.
Good luck!
Ian
M_Shaaban said:
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
Click to expand...
Click to collapse
Since this guide requires root anyway, I'm going to assume you already have Root access. If so, just install a root file manager (I like Root Browser), navigate to /system/customize/resource, and rename HTC_Sense5_Boot.mp3 to anything else. As long as it's not called HTC_Sense5_Boot.mp3, it won't play. Save and reboot. If you'd like to disable it altogether, navigate to /system/customize/resource/CID and open default.xml. Find:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" audio="/system/customize/resource/HTC_Sense5_Boot.mp3"/>
</BootConfiguration>
and remove the last part so it looks like this:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" />
</BootConfiguration>
Now save and reboot.
homeslice976 said:
Since this guide requires root anyway, I'm going to assume you already have Root access. If so, just install a root file manager (I like Root Browser), navigate to /system/customize/resource, and rename HTC_Sense5_Boot.mp3 to anything else. As long as it's not called HTC_Sense5_Boot.mp3, it won't play. Save and reboot. If you'd like to disable it altogether, navigate to /system/customize/resource/CID and open default.xml. Find:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" audio="/system/customize/resource/HTC_Sense5_Boot.mp3"/>
</BootConfiguration>
and remove the last part so it looks like this:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" />
</BootConfiguration>
Now save and reboot.
Click to expand...
Click to collapse
I used Root Browser. I edited the XML file and worked like a charm. But seems like it's taking a bit longer to boot, could editing boot configuration cause this?
Sent from my HTC One using XDA Premium 4 mobile app
M_Shaaban said:
I used Root Browser. I edited the XML file and worked like a charm. But seems like it's taking a bit longer to boot, could editing boot configuration cause this?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I certainly wouldn't think so. I've been disabling bootsounds this way since my Inspire
homeslice976 said:
I certainly wouldn't think so. I've been disabling bootsounds this way since my Inspire
Click to expand...
Click to collapse
Ah OK. Thanks a lot anyway
Sent from my HTC One using XDA Premium 4 mobile app
Hi, I tried to change this with root explorer. First i renamed the audio file. But it was restored after reboot. Then i changed in the xml file. same here restored? wtf? Have just got the latest sense 6 if that can have something to do with Thierry.
Edit: worked from recovery. But still, strange that root explorer didn't work?
You saved me. I was going crazy ... all tips I could find were for Android 2, or were turning sound off at shutdown => does not work after crash.
Thankss
Thnaks for the info
Do I need to be S-OFF to perform that?
Because when I restarted my phone after edition of the XML config file the changes we gone. Original file remains.
Hello everyone, I recently purchased the Desire 816 for Virgin Mobile, and could not find anything on rooting this device.
So... I figured it out on my own! I decided to write out a tutorial since there isn't anything out there about rooting this phone!
I'm also including a nandroid backup of my stock rooted rom if you don't want to go through all of the steps. You will still need custom recovery.
1. Unlock your bootloader, install custom recovery, and flash superuser. I used v_superuser's guide for this, so thanks to him!
Use his guide to install custom recovery and root: http://forum.xda-developers.com/showthread.php?t=2775801
The custom recovery he links to isn't made for the VM variant of this phone, but it works!
Now you can restore my clean install, rooted nandroid backup (link at end of post) if you don't want to do the following steps and still have full root.
2. Hopefully you were able to successfully install custom recovery and root.
Now this part is a bit tricky. Even with root HTC is stopping us from writing to system. For this we need to apply the wp_mod.ko module.
Download it here: http://forum.xda-developers.com/showthread.php?t=2707378
Copy this file to the root of your internal storage.
Now download Terminal Emulator from play store, run it and enter the following commands (you only need to do this once):
su
insmod /sdcard/wp_mod.ko
Once you do this go into your favorite root explorer and mount as R/W. Copy the wp_mod.ko file to /system/lib/modules
Now go to /system/etc and find install-recovery.sh. Open it with a text editor and add a new line at the end with the following:
insmod /system/lib/modules/wp_mod.ko
Reboot! If all went well the wp_mod module will run at boot every time so you won't have to do it manually each time!
Congratulations, you now have a fully rooted Desire 816!
Download my nandroid backup here (place the contained folder into the CWM backup directory):
https://drive.google.com/uc?id=0B0bhyG2E55hXaWtpeGVQaEpOVzA&export=download
Hope this helped anyone wondering how to root the device!
I just get md5 mismatch error when I try to restore
Never mind found out my phone wasn't downloading the whole back up
jcrt2000 said:
I just get md5 mismatch error when I try to restore
Click to expand...
Click to collapse
I'm not trying to offend with my answer. Just going for the easiest solution first...
Did you unzip the backup nandroid onto your PC? I imagine he zipped the actual Nandroid folder as it would have a date and time as the name.
If you unzip VM_HTC_Desire_816_Rooted_NandroidBackup.zip you SHOULD see a folder with a date and time. That is the actual nandroid that you'd copy to your Clockwordmod backup folder.
sirrx7 said:
I'm not trying to offend with my answer. Just going for the easiest solution first...
Did you unzip the backup nandroid onto your PC? I imagine he zipped the actual Nandroid folder as it would have a date and time as the name.
If you unzip VM_HTC_Desire_816_Rooted_NandroidBackup.zip you SHOULD see a folder with a date and time. That is the actual nandroid that you'd copy to your Clockwordmod backup folder.
Click to expand...
Click to collapse
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Kontrary said:
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Click to expand...
Click to collapse
It does work. I had to download on my pc to get the whole file downloaded.
jcrt2000 said:
It does work. I had to download on my pc to get the whole file downloaded.
Click to expand...
Click to collapse
Oh nice! Glad you got it working.
Kontrary said:
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Click to expand...
Click to collapse
Also...
The act of unlocking the phone clears out your data so you might notice that your flashlight and calculator apps are missing. For some reason HTC didn't make those 2 system apps.
If you'd like them back, here you go.
http://forum.xda-developers.com/showthread.php?t=2699906
sirrx7 said:
Also...
The act of unlocking the phone clears out your data so you might notice that your flashlight and calculator apps are missing. For some reason HTC didn't make those 2 system apps.
If you'd like them back, here you go.
http://forum.xda-developers.com/showthread.php?t=2699906
Click to expand...
Click to collapse
Thank you, I sold the phone but never noticed that.
Thanks for this, I had deleted my stock backup
problems with the mod.ko
everything works until I get to the wp_mod.ko command when using the terminal command. It just says cannot open. I tried countless times but it says the same thing. Is there any other way?
dwest3784 said:
everything works until I get to the wp_mod.ko command when using the terminal command. It just says cannot open. I tried countless times but it says the same thing. Is there any other way?
Click to expand...
Click to collapse
If you're having too much trouble and are about to give up you can always download Kontrary's Nandroid backup. I didn't use it but I did look through it and it looks like he already did the write protect mod in it.
Just unzip it on your PC and put the dated folder in your clockworkmod/backup folder. Boot into CWM recovery and restore from his nandroid.
Out of curiosity... Are you hitting enter after SU and before insmod???
Also...
The command insmod /sdcard/wp_mod.ko is only good if you have wp_mod.ko sitting on the root of the internal sd. If its on your micro sd card you'll obviously have to change the path after insmod or just move it to the internal sd..
thanks
sirrx7 said:
If you're having too much trouble and are about to give up you can always download Kontrary's Nandroid backup. I didn't use it but I did look through it and it looks like he already did the write protect mod in it.
Just unzip it on your PC and put the dated folder in your clockworkmod/backup folder. Boot into CWM recovery and restore from his nandroid.
Out of curiosity... Are you hitting enter after SU and before insmod???
Also...
The command insmod /sdcard/wp_mod.ko is only good if you have wp_mod.ko sitting on the root of the internal sd. If its on your micro sd card you'll obviously have to change the path after insmod or just move it to the internal sd..
Click to expand...
Click to collapse
Thanks I figured it out last night. I put in the internal memory and it worked but thanks for the reply!
dwest3784 said:
Thanks I figured it out last night. I put in the internal memory and it worked but thanks for the reply!
Click to expand...
Click to collapse
Right on. Glad you got it working.
driver issue
ive downloaded and installed and uninstalled and rebooted and done everything i can think to do...ive tried on my PC and on my laptop...ive tried with every usb cable i have...including the one that came with the phone...i can not get windows to recognize my phone...so i cant even unlock the bootloader to begin this process...any suggestions or hints on what i could try?
any help??
dragonclaw88 said:
ive downloaded and installed and uninstalled and rebooted and done everything i can think to do...ive tried on my PC and on my laptop...ive tried with every usb cable i have...including the one that came with the phone...i can not get windows to recognize my phone...so i cant even unlock the bootloader to begin this process...any suggestions or hints on what i could try?
Click to expand...
Click to collapse
i really really need to get this phone rooted any help??
dragonclaw88 said:
i really really need to get this phone rooted any help??
Click to expand...
Click to collapse
Have you plugged it in while in Fastboot? Which OS are you running? I'm on Win 7 x64 and have it set to download drivers from Windows update, I didn't have any problems going that route.
Have you downloaded HTC Sync Manager? It has the drivers required for your PC to recognize your phone.
Kontrary said:
Download my nandroid backup here (place the contained folder into the CWM backup directory):
https://drive.google.com/uc?id=0B0bhyG2E55hXaWtpeGVQaEpOVzA&export=download
Hope this helped anyone wondering how to root the device!
Click to expand...
Click to collapse
I installed your CWM Backup after I couldn't figure out your steps... but now there's an ANNOYING notification that says, "Smith disabled... Click here to open." I open it, and no matter what settings I choose, this notification keeps POPPING UP! Is this your doing, or a known issue with this "Mod." All I wanted to do was uninstall all the Google/VM Bloatware. Now going back to stock might be the only fix... ????
That Smith app is a problem for most recent HTC phones. It has nothing to do with the CWM backup. It happens with the M8 and our 816.
I just long press the notification, click App Info and force close. It's usually good until you reboot your phone.
Either HTC or Sprint is supposed to be looking for a fix but who knows.
https://community.sprint.com/baw/thread/169142?start=0&tstart=0
jayblaze406 said:
I installed your CWM Backup after I couldn't figure out your steps... but now there's an ANNOYING notification that says, "Smith disabled... Click here to open." I open it, and no matter what settings I choose, this notification keeps POPPING UP! Is this your doing, or a known issue with this "Mod." All I wanted to do was uninstall all the Google/VM Bloatware. Now going back to stock might be the only fix... ????
Click to expand...
Click to collapse
I was able to stop this annoyance by simply going to Titanium Backup (root needed) and freezing the process.
I typed in Smith in the search bar of TB and it came back with this process/app called
"Smith 4.21-plat_4.4.2-KOT49H"
I believe it happens to come up when a specific "bloatware" app is unaccessible by the device when removed but I have not singled out which app is it so far.
I backed up the app first then froze it and it stopped the Smith popup error permanently even after reboots and power offs.
(You could possibly delete it but until the stock bloatware app that causes this pinpointed i wouldn't recommend it.)
Tested running everything is good no errors rebooted fine checked bootloader and recovery and both are fine as well.
Sent from my 710C using XDA Free mobile app