Related
Hello all, I'm new to this site and I've never rooted a phone. Actually, the Eris is my first smartphone. I've read a lot of forums about rooting the Eris and from what I understand I shouldn't have installed the 2.1 ota update. I bought this phone soon after they were released so maybe I have a 1.47 hboot? I'm unsure how to check this, but if so does this mean I can root using the 1.5 method?
I just bought a class 6 8GB microsd card with the hopes of installing a custom rom, overclocking, and installing apps2sd. Now I'm getting very discouraged because it seems 2.1 can't currently be rooted.
Hopefully a senior user can help me out. Please put your response in lamens terms. I've seen some other forums where junior users are getting bashed for asking stupid questions so I'm putting it out there....please don't bash me for this one.
http://forum.xda-developers.com/showthread.php?t=684049
everything you need and more. To answer your next question. As long as your phone was never updated with leak, the process for root of 1.5 and 2.1 are the same.
happy rooting!
Thanks Spencer! If I root using the method at that page will I be able to flash other roms or will I be stuck with this 2.1 ROM? I'd like to install the evileris rom and (again I'm a newbie) I don't want to end up stuck like the people who installed the leaked 2.1.
you should be able to flash a custom rom to the phone as i believe you have to first load a custom recovery image to it. i could be wrong though just a guess.
SDK Not Working?
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Ok, maybe this is my problem...
Before the root, I could go into device manager from my computer and I got a yellow exclamation mark. After the root, I cannot find it. I can click on portable devices and it shows an Android Phone so I'm guessing my computer doesn't recognize it anymore. If that's the case I probably need to update the driver for SDK to work, but I need to find the device for that to work. I have USB debugging on. Any help is appreciated.
If it says android phone with no exclamation point that means it is recognized. Its when there is an exclamation point that means it is not recognized. I probably won't be able to help you further because I'm a rooting noob (I've only rooted my Eris and I had no problems) but I am a computer expert and I would suggest rebooting your computer and then trying it again... unless you already have.
-------------------------------------
Sent via the XDA Tapatalk App
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
What exactly do you mean when you say "I can't get the command prompts to work"?
joshw0000 said:
HELP!! I just rooted my phone, installed java, installed SDK and I can't get the command prompts to work. I followed the steps exactly (or so I think) and I'm opening sdksetup.exe. When I try to type I get nothing. Am I opening the wrong file or doing something wrong. I've not been able to install the recovery or custom rom to my phone yet, so I'm very vulnerable right now. Any ideas anyone?
Click to expand...
Click to collapse
Ok, calm down its not the end of the world, i ran into the same problem. What we need for us to help you, is at what point are you in trying to root your phone. Do you have SDK installed and updated?
I'm following the how to root instructions. I've completed I: Gaining Root and made it to 9. In II: Prerequisites. Java and SDK are both saved and extracted on my c: drive. I downloaded the USB drivers package in #6 of II. USB debugging was enabled and the phone was set to charge only. When I opened device manager on my pc, their was no yellow exclamation like the instructions indicated. I clicked on "Android Phone" and attempted to update the drivers found in SDK but Windows said they were up to date. I moved on to step III. Flashing a Custom Recovery and saved the zip file to my SD (should I save that to my c: drive?). I extracted it to tools in Android SDK and attempted to use the command prompt in SDK. It was unresponsive. It did not recognize my phone. I'm unsure if it does that automatically, if I need to take action, or if I should use the pc command prompt.
I went back to #9 of II and tried to troubleshoot. I tried every way I could think of to get the exclamation mark to show up in device manager so I could update the USB drivers. I hooked up my wife's unrooted Eris and it had the exclamation. I restarted my phone, restarted my computer, reflashed PB00IMG.zip and still had no luck.
Anybody had this probem? Any suggestions?
as the title asks, should I run the update I just got from AT&T? I read several differing opinions for different phones. some say don't, as it may relock the bootloader, others say it won't even let you complete the process if any /systems files are altered, some of mine are. Any input would be greatly appreciated.
ps it would suck if I lost root, as I can't establish a usb connection with my pc and wouldn't be able to reroot.
NoobDude said:
as the title asks, should I run the update I just got from AT&T? I read several differing opinions for different phones. some say don't, as it may relock the bootloader, others say it won't even let you complete the process if any /systems files are altered, some of mine are. Any input would be greatly appreciated.
ps it would suck if I lost root, as I can't establish a usb connection with my pc and wouldn't be able to reroot.
Click to expand...
Click to collapse
you will lose root. Just did it. I had to replace TWRP with stock recovery. However, i noticed speed improvements here and there. i have not really tested new radio yet... not enough time yet
thanks for the super speedy response, it's really appreciated! :good:
NoobDude said:
thanks for the super speedy response, it's really appreciated! :good:
Click to expand...
Click to collapse
i noticed my bootloader was still unlocked and i installed the cwm recovery,then booted into recovery. And when i went to leave recovery, it told me that my root may be lost and ask if i wanted to fix it. said yes and root appears to be back. then i installed latest TWRP(2.5) and all is ok! :good:
Edit:
after installing TWRP i did a backup (just in case). and after the back up it asked to fix permissions. said ok(as i thought maybe i lost root again) and it booted in android and root appears to be rooted. I tested with android terminal
a recovery can't be flashed in recovery with s-on** though, can it? To flash a new recovery you need to use adb no?
pardon my brain fart above..... so when you updated it erased your recovery? and the only way to install a recovery is via a usb connection? in other words, if I install the update while in my predicament, I'd loose recovery and root...
NoobDude said:
a recovery can't be flashed in recovery with s-on** though, can it? To flash a new recovery you need to use adb no?
pardon my brain fart above..... so when you updated it erased your recovery? and the only way to install a recovery is via a usb connection? in other words, if I install the update while in my predicament, I'd loose recovery and root...
Click to expand...
Click to collapse
you would boot into bootloader(fastboot) and flash the recovery:
$ sudo fastboot flash recovery <nameofrecovery>.img
edit: changed (hboot) to (fastboot) sorry if there was confusion, but it was late.
Orrrrr go and flash the AT&T update in it's Rom format. It's in Android Development.
can I flash the kernel in recovery though? I though with s on I had to do it from a computer using adb?
edit: ya there's no way I can flash the boot.img, that I know of at least, until I can get my usb connection working.
Are your drivers installed
yes and no. I installed HTC sync, the driver installer from Lucky 13s how to root post, and the ones from Hasoons tool. I tried installing then all separately, together, every which way. Currently all those programs are installed, yet in my device manager, nothing from HTC appears. It's like thy're installed but not. I backed up my phone right after I rooted it, nothing modified, its like it just came out the box only with root. I restored that "rom" and STILL it will not connect! I plug my phone in and NOTHING happens, it only charges. Tried different USB chords and plugged them into every USB port on the computer front and back, nothing , nadda, zip. I'm currently running vista, and am on the verge of dropping 100$ on Windows 7 and praying it fixes the problem. I've googled the CRAP out of this issue, and all i found are people who had FAILED installations. I've yet to get a failed message though. I swear i'm the only person with this issue. And its making me MAD... :crying:
NoobDude said:
yes and no. I installed HTC sync, the driver installer from Lucky 13s how to root post, and the ones from Hasoons tool. I tried installing then all separately, together, every which way. Currently all those programs are installed, yet in my device manager, nothing from HTC appears. It's like thy're installed but not. I backed up my phone right after I rooted it, nothing modified, its like it just came out the box only with root. I restored that "rom" and STILL it will not connect! I plug my phone in and NOTHING happens, it only charges. Tried different USB chords and plugged them into every USB port on the computer front and back, nothing , nadda, zip. I'm currently running vista, and am on the verge of dropping 100$ on Windows 7 and praying it fixes the problem. I've googled the CRAP out of this issue, and all i found are people who had FAILED installations. I've yet to get a failed message though. I swear i'm the only person with this issue. And its making me MAD... :crying:
Click to expand...
Click to collapse
do yourself a favor and get yourself a Live CD of Ubuntu. Ubuntu is free and the perferred OS for android. i swear by it. You can dual boot your vista and Ubuntu if you partition your hard drive. then after install and you boot into Ubuntu, hit ctrl-alt-t to open a terminal and type
Code:
sudo apt-get install android-tools-adb
when you type sudo you will have to enter your password, and it will not show it as you type
then
Code:
sudo apt-get install android-tools-fastboot
then restart the computer into Ubuntu
download the boot.img
press ctrl-alt-t
cd to the file directory (usually cd Downloads)
and type:
sudo fastboot flash boot <name of boot>.img
TheJokah said:
do yourself a favor and get yourself a Live CD of Ubuntu. Ubuntu is free and the perferred OS for android. i swear by it. You can dual boot your vista and Ubuntu if you partition your hard drive. then after install and you boot into Ubuntu, hit ctrl-alt-t to open a terminal and type
Code:
sudo apt-get install android-tools-adb
when you type sudo you will have to enter your password, and it will not show it as you type
then
Code:
sudo apt-get install android-tools-fastboot
then restart the computer into Ubuntu
download the boot.img
press ctrl-alt-t
cd to the file directory (usually cd Downloads)
and type:
sudo fastboot flash boot <name of boot>.img
Click to expand...
Click to collapse
Im very familiar with Ubuntu i have 12.04 dual booted on my acer chromebook and ran plenty of programs with terminal. Im going to take your advice right now and get cracking! Thanks a lot man!
ASUS MeMO Pad 8 (K011) ME181C Recovery Guide
The following is a list of what we can currently do with this tablet. It assumes firmware versions with the WW prefix (WW-3.1.23.1xx).
Root Status: Obtained
Bootloader: Locked
CWM Recovery Possible: Yes (Tethered)
Custom ROMS: None
The following information is for recovering your tablet and obtaining root only. The bootloader is locked on the device at this time.
Tethered CWM recovery
This is a temporary solution to unsigned loading. The bootloader on the device is currently locked, so after rebooting, it will revert back to standard recovery. Use this to restore to a stock firmware or to install SuperSU.
Download the official firmware and extract it.
Rename UL-K011-WW-3.1.23.172-user.zip to user.zip.
Copy user.zip to the root of your SD card.
Enable USB debugging on your tablet.
Run Launcher.bat.
Type ACCEPT.
Choose option T3.
This will reboot in to the Tethered Recovery.
Choose Install Zip from external SD card.
Choose user.zip
Reboot once finished.
Bootable Image for Recovery
This file is to be used if your system will not get past the Asus or Intel logo. Boot the system using Volume Up and Power. Once the logo appears, let go of power. Once in DroidBoot, use fast boot to flash the boot and system images. This is provided in case signature verification fails on the official images.
fastboot flash system system.img
fastboot flash boot boot.img
This file also contains adb and fastboot. If your tablet is not detected, try the Asus drivers.
Reboot the system and use the CWM tethered recovery to reinstall the official firmware.
OTA Updates
If you’ve recovered from the official firmware on the Asus site, you’re probably sitting at version WW-3.1.23.172. Here are the OTA updates to bring your system up to the current version of WW-3.1.23.189. There are two different OTA updates available here, so the process will need to be completed twice. Update 172 to 183 and Update 183 to 189.
Boot in to recovery, press the volume keys several times and install from ADB.
Extract the RAR file and rename the files update.zip.
On your PC, open a command prompt and change to the directory containing the update file
Assuming ADB is installed on the system, type: adb sideload update.zip
Once the process completes, reboot your system and update apps as needed.
Repeat this process for any additional update files.
Recovery image
This is the default recovery for the tablet. If you get adventurous and try to flash another one, this may come in handy.
can you explain
RemmyLee said:
All thanks to vampirefo for his work on this.
FB Tethered Recovery Launcher
Kind of curious if this method will work with the other versions of the tablet to allow SuperSU to be installed. Anyone want to try it?
Long story short, I screwed this thing messing with the framework. For some reason, the official firmware from the Asus site was failing signature verification when trying to reinstall. Someone managed to grab a stripped system image that at least gave me a launcher and USB debugging. This beauty allowed me to get the firmware installed and everything back to normal, as well as installing SuperSU.
If you have any trouble getting the tablet to show up in Windows, the Asus distributed drivers work like a charm.
Click to expand...
Click to collapse
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
1. https://cloud.mail.ru/public/2b47381cb37c/ADB.rar - This contains adb and fastboot if you don't already have them installed. This also contains the system image that we're going to use temporarily to get this thing restored.
2. Hook it up to your computer and load up Fastboot on the tablet (Volume+ and Power while booting. Let go of power after the logo shows up).
3. Flash the System image ( fastboot flash system system.img) followed by the boot image (fastboot flash boot boot.img)
4. Reboot.
5. https://www.androidfilehost.com/?fid=95857557620392052 - Next, we're going to use a temp version of CWM-Recovery to reinstall firmware. Enable USB debugging, run launcher.bat, type "ACCEPT" and choose T3.
6. You'll auto reboot into CWM-Recovery. Grab the official firmware from the Asus site and install the zip from SD. Once complete, you'll need to reroot the device most likely. If you have a SuperSU zip, install it after you've restored the system.
You're done. This also opens us up for just about anything. Go play with your system. As long as you don't mess up your boot loader, this should save you.
Sent from my K011 using XDA Free mobile app
Asus MeMo Pad 8 - Pro 7 Entertainment Pad
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
OTA update 172 to 183
OTA update 183 to 189
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
shadow2483 said:
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
Click to expand...
Click to collapse
If you need any more help than whats above, let me know.
fulishone said:
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
Click to expand...
Click to collapse
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
RemmyLee said:
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
Click to expand...
Click to collapse
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
fulishone said:
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
Click to expand...
Click to collapse
Yep. That'll get you updated to the current firmware. I contacted ASUS yesterday and sadly, there are no plans on bringing Lollipop to this thing, nor are they interested in giving us an unlocked bootloader.
As for the Intel Tether, where the bootloader is locked, we can use a tethering method to access CWM recovery, but once we reboot, it reverts back to the standard recovery. This prevents us from using custom roms at this time. When it reboots, it checks signatures. The official firmware was not installing using the standard methods, so I used CWM to reinstall. That's why I included it above.
BBY builds
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
et1ssgmiller said:
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
Click to expand...
Click to collapse
I'm curious to know if the tethered method would allow a temporary CWM session to install SuperSU on the BBY line. I haven't seen anyone try it yet. If USB debugging is enabled, the tethered restore should try to automagically do everything for you. If you boot in to recovery, can you do a fastboot devices?
Can´t mount external sd card anymore
After using CWM tethered recovery to backup my rom, i cant mount my external sd card anymore. Any ideas?
Updates
RemmyLee said:
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
URLS removed to post
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
tperki said:
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
Click to expand...
Click to collapse
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Success
RemmyLee said:
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Click to expand...
Click to collapse
Yeah, strange that it won't update over the air. But thanks to your assistance I am running build 189. It may just be wishful thinking, but the device does seem a bit peppier. Thank you RemmyLee!!!!
[Update] Since updating to build 189, the device is much more stable and snappier. This was definitely worth doing. I don't understand why ASUS would not be pushing this out to everyone with this device.
Just wanna say thanks to the OP. Got my tablet back from the service center and was wondering why some apps were missing. Sure enough I was on WW...179. Nice to have updates and recoveries in one place. Great work!
Thank you so much bro, I have been googling a lot trying to find a root method and just discovered that I can easily have recovery and flash supersu zip thanks to you!!
Me181c not working...
Hi guys, I was using SoftKeyZ for about 2 weeks, I wanted to set my navigation buttons to it's default, so I tried using Backup of the SoftKeyZ, but when it rebooted the tablet, I lost my navigation buttons and indeed my notification and status bar. It rebooted again automatically, and this time when it started, I got an error which says: "Unfortunately, KeyguardTestActivity haas stopped", the error prevents me from unlocking the tablet and using it, so I cannot use it at all. I don't know how to go to recovery mode on my tablet, I used the button tips but it didn't work for me. I've downloaded the official rom from asus.com . Pleeeeeeeeeeeeeeeeeeeeeease, I need your help guys, you're my last chance...
should I do a complete wipe ?
Hi,
Thanks for the help in this thread.
I followed the instructions and successfully flashed the update firmware file. I was expecting for the tablet to be reset to original factory condition but found that all my apps ect were still there. I guess the user.zip is an update rather that a full ROM or should I have wiped everything first ?
I am have problems with the tablet such as Bluetooth has stopped working and wifi will only connect to very strong signal, (as in touching the router) which is why I wanted to completely wipe the device a start fresh.
f I wipe everything will the firmware file be able to restore the system fully?
Is there a complete firmware image file that can be downloaded any where ?
Thanks in advance for any advice
update : so fed up with no Bluetooth so I took the chance and did a full factory wipe and the system restored ok with the firmware file. Bluetooth problem solved, (Wifi did not, probably Hardware issue)
Thanks again
Signature failure
Thanks to your instructions, I've successfully managed to update my device to build WW-3.1.23.172, however, when trying to install 172 to 183 update I get a signature verification failure message.
Any ideas why this is happening?!
My droid mini was accidentally factory reset this weekend. It was my primary camera for the past year that held over a thousand pics. I regrettably have no backup. I have searched the internet and tried numerous things to get them back. I've tried several photo recovery software packages but I either need to have my phone rooted or have USB mass storage. I tried kingoroot, towelroot, and pwnmymoto to root my phone with no luck. My phone has MTP and no USB mass storage. A restoration company told me today that even if I was able to root my phone and retrieve the files they would be encrypted and unreadable. They recommended that I shelve the phone, wait 3 months, and call them back to see if they have come up with a way to unlock the encryption. Any help would be so appreciated.
Here are my phone's details:
Android version 4.4.4
Build Date Friday Dec 12
You should try the Recuva software, Just download and install it then connect your cellphone with system.
Then run this software and check mark the your cellphone drive too and perform deep scan.
Maybe it will we work for you.
saarav242 said:
You should try the Recuva software, Just download and install it then connect your cellphone with system.
Then run this software and check mark the your cellphone drive too and perform deep scan.
Maybe it will we work for you.
Click to expand...
Click to collapse
I gave this a try, but my cell doesn't register to a drive so it wouldn't scan it. I have MTP storage so it shows up as a portable media device. Thanks for your suggestion. I think if there was a way to root a 4.4.4 droid mini, I may have a chance at using one of the other recovery apps. Any suggestions for rooting? Does anyone know if my files would be corrupted/ encrypted if I did recover them?
You should check this link for root your device : http://forum.xda-developers.com/showthread.php?p=45598648#post45598648
saarav242 said:
You should check this link for root your device : http://forum.xda-developers.com/showthread.php?p=45598648#post45598648
Click to expand...
Click to collapse
How do you run a command? This part confuses me:
Install PwnMyMoto by running:
Quote:
adb install -r PwnMyMoto-<version and model go here>.apk
PA girl said:
How do you run a command? This part confuses me:
Install PwnMyMoto by running:
Quote:
adb install -r PwnMyMoto-<version and model go here>.apk
Click to expand...
Click to collapse
For that you need SDK Bundle and Read more about it.
saarav242 said:
For that you need SDK Bundle and Read more about it.
Click to expand...
Click to collapse
Are you able to root without running a command? I tried installing pwnmymoto onto my device, but it said "application failed". Maybe I needed to run that first?
PA girl said:
Are you able to root without running a command? I tried installing pwnmymoto onto my device, but it said "application failed". Maybe I needed to run that first?
Click to expand...
Click to collapse
Yes, There are many softwares for rooting the device. Try with kingoroot if it's not working so try to root by Vroot.
I've been hacking on this on and off for days. Success. Basically the solution is a bait and switch.
I've tried so many things, this is recalled from memory and the following steps may be incomplete. I used the latest of ES File Explorer. SuperSU, etc.
Get angguesss' update.zip here: http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21 . Rename it to update zip and keep it safe.
Make sure you know how to root, get the proper Intel drivers, Phone Flash Tool Lite, etc.
OVERVIEW:
What is being done here is to prime the 7840 for an update by downloading the stagefright fix with a rooted device and swapping out that fix with angguesss' older update.zip. It's like starting over. Upon reboot the 7840 updates to angguesss' older update cleanly, paving the path for the stagefright fix to update successfully.
Special thanks to angguesss, Social Design and everyone who unknowingly provided little pieces of knowledge here and there.
CAUTION:
You might brick, wipe, lose root, lose customizations, void warranty, get frustrated, look at the device hatefully and all the standard caveats, no guarantees. Do at your own and the device's risk.
HERE IT IS:
This is the BAIT part:
1. Root the 7840
2. Download the stagefright patch (DO NOT REBOOT)
3. In an editor: Go To \data\data\com.dell.systemupdateota
4. Copy the patch somewhere safe (extsd, for example, just in case)
5. Review the properties of the update.zip in the com.dell.systemupdateota
6: Note permissions of RW- --- --- and the owner/group "u0_a29"
This is the SWITCH part:
7. Copy over to \data\data\com.dell.systemupdateota angguesss' update.zip here while renaming it update(1).zip
8. Change the permissions and owners of the update(1).zip to match the update.zip
9. Delete the downloaded update.zip (the stagefright download)
10. Rename update(1).zip to update.zip. angguesss' update will now be the update!
11. In \system\app delete the supersu folder (containing the supersu.apk)
12. in \data\data delete the eu.chainfire.supersu data folder
13. Press the on/off button, select reboot
14. Let the 7840 reboot
15. After a few seconds the 7840 will "figure out" there is an unused update and begin to shut down.
16. Wait out the shutdown (mine took about five minutes).
17. The tablet will begin to update in the usual fashion (Andy, the progressing blue line)
18. Let the update finish and allow to boot to completiton.
19. Go to settings->about tablet->update and download (yes, again) the stagefright fix.
20. Install, reboot (wait...) and upon reboot let the update proceed as normal. Should be no errors.
21. Hopefully, you now have a Stagefright updated 7840 5.1
Some steps may be unnecessary, redundant, etc. Now off to check out some things. Update later.
UPDATES:
The Dell Stylus still appears to work.
First attempt at re-rooting failed, TWRP recovery did not load/display.
Second attempt at re-rooting but using CWM worked. SuperSU installed.
There are still low level speaker "clicks" at boot time.
Update and clarifications to instructions steps 6, 12, 13
Hey, thanks for posting this. I am trying to accomplish the same thing you have done.
I followed your guide up through number 16, but the tablet never reboots and there is never any update screen.
If I boot up by pressing the power button I am still on 5.1 and the stagefright update still fails for me...
Is this a problem you encountered?
On step 16 I waited quite awhile and waited and waited. I was tempted to bail out but didn't. It might have been ten minutes.
TonyBigs said:
First attempt at re-rooting failed, TWRP recovery did not load/display.
Second attempt at re-rooting but using CWM worked. SuperSU installed.
There are still low lever speaker "clicks" at boot time.
Click to expand...
Click to collapse
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Mistype in row 12: not /data , its /data/data
Thanks, trying it now
Not worked for me, still error while flashing stagefrigt patch
E:Error in @/cache/recovery/block.map
(status 7)
Installation aborted
toxic_garden said:
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Click to expand...
Click to collapse
Rerooting using the venue_7840_droidboots using 1-502 then using IntelAndroid-FRBL-07-24-2015 selecting CWM and then T4. That was just my choice after installing the update to see what would happen and how the process would run, if at all. The main goal, however, was to get the stagefright fix installed.
toxic_garden said:
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Click to expand...
Click to collapse
olvrick said:
Mistype in row 12: not /data , its /data/data
Thanks, trying it now
Not worked for me, still error while flashing stagefrigt patch
E:Error in @/cache/recovery/block.map
(status 7)
Installation aborted
Click to expand...
Click to collapse
Thank you for the response, I'm in the process of trying the process all over again. Maybe I missed something.
Successful again. Note changes to steps 6, 12, 13
Today when updating from 5.0.1 to 5.1 I'm not sure what happened but I ended up with the stragefright ota also installed. At least I think it is. System update is no longer finding any available updates. I did lose root. The strangest part was that I was having trouble updating to 5.1 until I booted into tethered TWRP (Have only used cwm on this device in the past when flashing first 5.1 update). First time trying to boot into TWRP I just got a black screen after leaving the bootloader and having the white text populate on screen. Second attempt though TWRP loaded up and immediately began running a script, or flashing the update I suppose. Tablet rebooted automatically and I haven't lost any data. Everything works fine so far. How can I determine if the latest stagefright has been installed?
TonyBigs said:
Rerooting using the venue_7840_droidboots using 1-502 then using IntelAndroid-FRBL-07-24-2015 selecting CWM and then T4. That was just my choice after installing the update to see what would happen and how the process would run, if at all. The main goal, however, was to get the stagefright fix installed.
Click to expand...
Click to collapse
but the stagefright fix also comes with a new boot.img, so only part of the update is installed when you revert to 5.01 boot.img afterwards. :\
toxic_garden said:
but the stagefright fix also comes with a new boot.img, so only part of the update is installed when you revert to 5.01 boot.img afterwards. :\
Click to expand...
Click to collapse
I understand, so don't rerun the rooting process. It's the user's choice of what to do next after returning the 7840 back to a non-rooted state that will accept OTA fixes and updates.
TonyBigs said:
This is the BAIT part:[...]
This is the SWITCH part:
Some steps may be unnecessary, redundant, etc. Now off to check out some things. Update later.
Click to expand...
Click to collapse
i had some time on my hands today and tried it out by myself. You can in fact shorten the process pretty much.
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Obviously, you'll lose root with that and there's no option for the moment to regain it. Using the old method via 5.01 bootimg isn't something i would recommend. But for me, a fully functional and up to date system is more worth than a buggy rooted system.
toxic_garden said:
i had some time on my hands today and tried it out by myself. You can in fact shorten the process pretty much.
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Obviously, you'll lose root with that and there's no option for the moment to regain it. Using the old method via 5.01 bootimg isn't something i would recommend. But for me, a fully functional and up to date system is more worth than a buggy rooted system.
Click to expand...
Click to collapse
Does ambient display or Intel Sensing Assist work on your device? They've stopped working on mine since I updated and rooted. Would be willing to give up root to get that feature back.
jamebarron88 said:
Does ambient display or Intel Sensing Assist work on your device? They've stopped working on mine since I updated and rooted. Would be willing to give up root to get that feature back.
Click to expand...
Click to collapse
They both work fine. I can't say how it was before, because I never used Sensing Assist in the past. But for now, it works.
toxic_garden said:
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Click to expand...
Click to collapse
Do you have a link to a source for both the update 5.1.img as well as the stagefright image? All I have been able to find is the 5.01 update. I am in the same predicament, currently on 5.1, but even after removing root before my first attempt applying the Stagefright fix, the update fails. I have done a couple factory resets, but now the screen is constantly freezing, making the tablet unusable.
Thanks!
wayne710 said:
Do you have a link to a source for both the update 5.1.img as well as the stagefright image? All I have been able to find is the 5.01 update. I am in the same predicament, currently on 5.1, but even after removing root before my first attempt applying the Stagefright fix, the update fails. I have done a couple factory resets, but now the screen is constantly freezing, making the tablet unusable.
Thanks!
Click to expand...
Click to collapse
Yes where can we find the source. And how do we get to stock recovery if already rooted and used cwm tethered recovery.
first of all, here the links.
stagefright update -> http://forum.xda-developers.com/showpost.php?p=64183381&postcount=9
5.1 update -> http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15
Dell System restore files -> http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
5.01 system.img, boot.img and tools -> http://forum.xda-developers.com/showpost.php?p=62833258&postcount=4
What i've done so far, coming from a complete messed up installation. Just to be sure: if you need some data from your current installation, back it up to external SD first. Obviously, this procedure will wipe everything you got on it.
- copy 5.01 system.img mentioned above to the SD card. Also the stagefright fix and 5.1 update.
- use the Phone Flash Tool to flash flash-DDO_BB.xml from Dell's Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip. This will put the Tablet back in a flashable and clean state. (1)
- boot to CWM (1)
- open adb shell and dd the system.img to the tablet. (1)
- reboot to fastboot (1)
- install the boot.img via fastboot (1)
- boot to Android for getting the system up at least once (don't know if it's neccessary, but i just did it to be sure everything works fine)
- boot to CWM
- via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
- install the 5.1 update via CWM from SD-Card
- boot to Android to see if everything's fine
- now boot to REGULAR recovery. You'll see just the Android robot with no commands or whatever. Don't get confused by that. You'll have to press the power- and volume up button together twice. I always need 5-6 tries, but after some time you'll see the stock recovery menu.
- select "update from ADB sideload"
- for some reason, i had to install the 5.1 update again via sideload to get the stagefright fix working. So open a command window and "adb sideload <name of 5.1 update>.zip" to the device
- right after that, sideload the stagefright fix the same way
- reboot
-voilá
(1) those steps are already described in detail here: http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
As much as i love the build quality and overall design of the tablet, keeping it software-sides running really is a pain. But at least for now, i got a running, up to date 5.1 w/ stagefright and for the last few days, no issues like crackling sound or random reboots occoured. Yay!
toxic_garden said:
first of all, here the links.
stagefright update -> http://forum.xda-developers.com/showpost.php?p=64183381&postcount=9
5.1 update -> http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21
Dell System restore files -> http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
5.01 system.img, boot.img and tools -> http://forum.xda-developers.com/showpost.php?p=62833258&postcount=4
What i've done so far, coming from a complete messed up installation. Just to be sure: if you need some data from your current installation, back it up to external SD first. Obviously, this procedure will wipe everything you got on it.
- copy 5.01 system.img mentioned above to the SD card. Also the stagefright fix and 5.1 update.
- use the Phone Flash Tool to flash flash-DDO_BB.xml from Dell's Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip. This will put the Tablet back in a flashable and clean state. (1)
- boot to CWM (1)
- open adb shell and dd the system.img to the tablet. (1)
- reboot to fastboot (1)
- install the boot.img via fastboot (1)
- boot to Android for getting the system up at least once (don't know if it's neccessary, but i just did it to be sure everything works fine)
- boot to CWM
- via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
- install the 5.1 update via CWM from SD-Card
- boot to Android to see if everything's fine
- now boot to REGULAR recovery. You'll see just the Android robot with no commands or whatever. Don't get confused by that. You'll have to press the power- and volume up button together twice. I always need 5-6 tries, but after some time you'll see the stock recovery menu.
- select "update from ADB sideload"
- for some reason, i had to install the 5.1 update again via sideload to get the stagefright fix working. So open a command window and "adb sideload <name of 5.1 update>.zip" to the device
- right after that, sideload the stagefright fix the same way
- reboot
-voilá
(1) those steps are already described in detail here: http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
As much as i love the build quality and overall design of the tablet, keeping it software-sides running really is a pain. But at least for now, i got a running, up to date 5.1 w/ stagefright and for the last few days, no issues like crackling sound or random reboots occoured. Yay!
Click to expand...
Click to collapse
Thanks toxic_garden, as due to your input, I now have an up-to-date tablet that is not constantly freezing as well as the Stagefright update. I simply ADB sideloaded the 5.1 OTA over the messed up 5.1 system already on my tablet. Shortly after rebooting, the Stagefright update downloaded and successfully updated. I did use the 5.1 update posted by xBIGREDDx (Thank you!) at http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15, rather than the link shown in the quoted post above. Unless I messed up somehow, I believe the link shown above for the 5.1 update points to a link for 5.0.1. Anyway, I think I am not going to root this tablet again as long as it is on 5.1.
wayne710 said:
Thanks toxic_garden, as due to your input, I now have an up-to-date tablet that is not constantly freezing as well as the Stagefright update. I simply ADB sideloaded the 5.1 OTA over the messed up 5.1 system already on my tablet. Shortly after rebooting, the Stagefright update downloaded and successfully updated. I did use the 5.1 update posted by xBIGREDDx (Thank you!) at http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15, rather than the link shown in the quoted post above. Unless I messed up somehow, I believe the link shown above for the 5.1 update points to a link for 5.0.1. Anyway, I think I am not going to root this tablet again as long as it is on 5.1.
Click to expand...
Click to collapse
you're right, i should correct that in my description. Glad it worked for you. Personally, i only used root for removing McAffee and installing AdBlock. Well, McAffee is just frozen for now and adblocking happens on the router, so no big loss for the moment. The only thing i might miss is Titanium Backup. Helium does a good job, but is in no way comparable to the mighty power of Titanium. ^^
Link to 5.1 OTA is broken=( Cant open link, just gray circle on the screen
via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
Seriously? why not make a normal guide for those who havent done it before?
olvrick said:
Link to 5.1 OTA is broken=( Cant open link, just gray circle on the screen
Click to expand...
Click to collapse
seems like mega has some issues at the moment. Just drop me a PM if it's still broken in 1 hour or so, then i'll upload the zip somewhere else