Related
Hi,
I have the Samsung Galaxy S Wifi 3.6 YP-GS1 European model. I've tried to root it using SuperOneClick, and some others but to no success!
Especially when using SuperOneClick, it hangs at Step 7.
I should note that I have Android 2.3.6 and am I right in saying that the zergRush exploit does not work?
Info about device
Model No - YP-GS1
Android - 2.3.6
Kernal Version - 2.6.35.7-CL712316 [email protected] #1
Build Number - Gingerbread.XXKK3
Correct, the zergRush hole has been patched.
The process for rooting phones that have been "patched up" is much harder - it requires flashing a prerooted system image or insecure kernel in Odin.
Creating one of these can be difficult - unless someone has already published stock firmware (zImage and factoryfs.rfs) somewhere, getting a complete firmware pull requires two devices. "flying blind" (trying to create an insecure kernel without a good zImage dump) is a high-risk activity for even an experienced developer.
I wasn't even aware they had released the 3.6 yet, just goes to show how good samsung's marketing for the galaxy players is, lol! Wow, what a model number too - imagine how many people are going to confuse YP-GS1 with YP-G1 - great job Samsung!
BTW: superoneclick always hangs at step 7, you have to unplug then replug your device in. Try that before you loose all hope!
@nathan2226
Sorry off topic but I see you own the Galaxy S wifi 3.6 like too and I was beginning to think I was the only one on the planet who owned one. Anyway the problem is that when I use Music Player or watch video when I adjust the volume from level 16 to level 30 there is no difference in volume. However when I pause the music and replay it the volume is now noticeably louder at the maximum volume of 30.
Do you have that problem too?
iJimaniac said:
I wasn't even aware they had released the 3.6 yet, just goes to show how good samsung's marketing for the galaxy players is, lol! Wow, what a model number too - imagine how many people are going to confuse YP-GS1 with YP-G1 - great job Samsung!
BTW: superoneclick always hangs at step 7, you have to unplug then replug your device in. Try that before you loose all hope!
Click to expand...
Click to collapse
I will give that a go now, and will let you know what happens.
Yeah I know, I think that model is only released in Europe
Entropy512 said:
Correct, the zergRush hole has been patched.
The process for rooting phones that have been "patched up" is much harder - it requires flashing a prerooted system image or insecure kernel in Odin.
Creating one of these can be difficult - unless someone has already published stock firmware (zImage and factoryfs.rfs) somewhere, getting a complete firmware pull requires two devices. "flying blind" (trying to create an insecure kernel without a good zImage dump) is a high-risk activity for even an experienced developer.
Click to expand...
Click to collapse
Has there been any previous kernal/firmwares released?
Could be as simple (or not so simple?) as flashing a kernal via Odin and rooting using SuperOneClick, like the S II ?
Artmuzz said:
@nathan2226
Sorry off topic but I see you own the Galaxy S wifi 3.6 like too and I was beginning to think I was the only one on the planet who owned one. Anyway the problem is that when I use Music Player or watch video when I adjust the volume from level 16 to level 30 there is no difference in volume. However when I pause the music and replay it the volume is now noticeably louder at the maximum volume of 30.
Do you have that problem too?
Click to expand...
Click to collapse
I have posted you a PM reply
iJimaniac said:
I wasn't even aware they had released the 3.6 yet, just goes to show how good samsung's marketing for the galaxy players is, lol! Wow, what a model number too - imagine how many people are going to confuse YP-GS1 with YP-G1 - great job Samsung!
BTW: superoneclick always hangs at step 7, you have to unplug then replug your device in. Try that before you loose all hope!
Click to expand...
Click to collapse
Thought I give you an update - This didn't work due to the zergRush exploit getting patched up
nathan2226 said:
Has there been any previous kernal/firmwares released?
Could be as simple (or not so simple?) as flashing a kernal via Odin and rooting using SuperOneClick, like the S II ?
Click to expand...
Click to collapse
Sometimes stock initial firmware for a device shows up on the leak sites, sometimes it doesn't, seems to be a crapshoot.
The "hard way" to root a device, which requires two devices for a clean dump, is:
Path 1:
a) It's possible to dump 90% of so of the files of an initramfs without root - do this, try to fill in the holes, and build an insecure kernel using this dump. Use that to get a clean system dump.
b) Use the clean system dump to develop a prerooted system image that can be flashed to a second device to get a clean stock kernel
Path 2:
a) You can get 80% or so of /system without root - dump it, fill in holes, make an Odin-flashable image that has su binary added.
b) Flash this and get a clean zImage dump
c) Use that dump to develop a custom kernel that is flashed to a second device to get a clean /system dump
We got lucky on the SGH-I777 (USA AT&T GSII)- International kernels were functional enough to get a full /system dump, and I was able to use that dump to develop a prerooted system image which I used to extract the stock kernel image from my device.
Entropy512 said:
Sometimes stock initial firmware for a device shows up on the leak sites, sometimes it doesn't, seems to be a crapshoot.
The "hard way" to root a device, which requires two devices for a clean dump, is:
Path 1:
a) It's possible to dump 90% of so of the files of an initramfs without root - do this, try to fill in the holes, and build an insecure kernel using this dump. Use that to get a clean system dump.
b) Use the clean system dump to develop a prerooted system image that can be flashed to a second device to get a clean stock kernel
Path 2:
a) You can get 80% or so of /system without root - dump it, fill in holes, make an Odin-flashable image that has su binary added.
b) Flash this and get a clean zImage dump
c) Use that dump to develop a custom kernel that is flashed to a second device to get a clean /system dump
We got lucky on the SGH-I777 (USA AT&T GSII)- International kernels were functional enough to get a full /system dump, and I was able to use that dump to develop a prerooted system image which I used to extract the stock kernel image from my device.
Click to expand...
Click to collapse
I am technically minded, but not that advanced enough to produce something like that 'the hard way'.
I guess I will have to sit it out to see if someone will leak out stock firmware to allow me to root it
Hi Nathan,
Do you have any news about root your device? I am looking for Roms/ FW too, but I haven´t got lucky yet.
Please, if you find any solutions, could you publish here? I will do the same!
Thanks in advance.
Hi,
Nope, not found anything yet unfortunately
Hello again!
I´ve trying with new versions of:
- Superoneclick (v2.3.2 / v2.3.3) with gingerbreak exploit but no succes because program frozes always. Never goes beyond step #5
- Unlockroot 2.2: at compability list of this version, model yp-gs1 is listed, but it doesn´t work. I have emailed at support asking..
And Log reveals:
Kill adb server
Starting adb server...
Get online devices
push file to device : rootutility
push file to device : busybox
push file to device : su
chmod file 755 busybox
Try to get shell root permission may take several minutes...
chmod file 755 rootutility
Try to get shell root permission may take several minutes...
Failed to get shell root !
hello i have also tried to root this device no succes with unlock root 2.3 it doesnt just like you i get the message failed to get shell root pls can someone root this device
i normally have the 8gb version of the samsung galaxy s wifi 3.6, but actually i got like 6.7gb storage, is that normal?
abduleno said:
hello i have also tried to root this device no succes with unlock root 2.3 it doesnt just like you i get the message failed to get shell root pls can someone root this device
Click to expand...
Click to collapse
Hi,
I'm one more who want to root his YP-GS1.
I also tried the various methods listed above with no results.
Can anyone help in this regard.
Thanks
Entropy512 said:
Sometimes stock initial firmware for a device shows up on the leak sites, sometimes it doesn't, seems to be a crapshoot.
The "hard way" to root a device, which requires two devices for a clean dump, is:
Path 1:
a) It's possible to dump 90% of so of the files of an initramfs without root - do this, try to fill in the holes, and build an insecure kernel using this dump. Use that to get a clean system dump.
b) Use the clean system dump to develop a prerooted system image that can be flashed to a second device to get a clean stock kernel
Path 2:
a) You can get 80% or so of /system without root - dump it, fill in holes, make an Odin-flashable image that has su binary added.
b) Flash this and get a clean zImage dump
c) Use that dump to develop a custom kernel that is flashed to a second device to get a clean /system dump
We got lucky on the SGH-I777 (USA AT&T GSII)- International kernels were functional enough to get a full /system dump, and I was able to use that dump to develop a prerooted system image which I used to extract the stock kernel image from my device.
Click to expand...
Click to collapse
Hello ntropy512!
Please can you help rooting the YP-GS1, I found that samsung has released some firmware for YP-GS1 on this link:
https://opensource.samsung.com/index.jsp;jsessionid=270954CEE97EBDDA2FF300E0504BF9A1
Maybe you can create an insecure Kernel or something to unprotec the dammed GS1? I have no sufficient skills to do that...:-(
It will be a great help for all YP-GS1 owners...
YP-GS1
Android: 2.3.6
Kernel vertion:[email protected] #1
Build number.XXLA1 (After Kies actualisation)
Thank in advance,
Antonio Pinto
ampinto said:
Hello ntropy512!
Please can you help rooting the YP-GS1, I found that samsung has released some firmware for YP-GS1 on this link:
https://opensource.samsung.com/index.jsp;jsessionid=270954CEE97EBDDA2FF300E0504BF9A1
Maybe you can create an insecure Kernel or something to unprotec the dammed GS1? I have no sufficient skills to do that...:-(
It will be a great help for all YP-GS1 owners...
YP-GS1
Android: 2.3.6
Kernel vertion:[email protected] #1
Build number.XXLA1 (After Kies actualisation)
Thank in advance,
Antonio Pinto
Click to expand...
Click to collapse
Creating an insecure kernel requires modifying the initramfs, which is not provided by the samsung open source releases. You would need to dump the kernel and extract the initramfs from it, and dumping the kernel requires root.
Sent using Tapatalk
Rooting samsung yp-gs1
Rooting Samsung yp-gs1 player ...
go to unlockroot.com
Download & install unlockroot v2.3.1
go to samsung.com/uk/support/model/YP-GS1CB
Download & install kies v2.0
Let it upgrade.
switch on usb dev debugging, stay awake & allow mock locations under settings / applications / development
connect your device to your pc
run unlockroot & click root if drivers from kies installed, you should see a popup box with your device
Select device & in a couple of mins program may ask you to install Super power save (means rooted successfully)
I know it works, as I have just rooted mine (got at gadget show, yesterday from PC World for £99.99)
i just saw your post but it doesnt work on my galaxy player 3.6 i also have upgraded it but just tells me failed to get shell root my player is international version so galaxy s wifi 3.6 pls help
job done with superonclick
hey gvoute pls tell me how you root you player with superoneclick i tried it hundred time but it always hangs at step 7 i did the kies update but it just wont work you are the second who have rooted the phone but cant pls help me
UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi again
As I wrote recently - I was working on automatic tool for Sony Tab community,
to get 'rescue-backoor' (in case of bootloop), and get proper OTA update zips.
It took me a lot of effort to get everything to work as it should,
...but I think that it was worth it..... you tell me
OK... let's get to the point - MULTI-TOOL, it has 3 main functions:
build.prop modification - bootloop protection
ota zip autodownloader
disable/enable ota updates and notifications
It does all the things which was described in [GUIDE-IMPORTANT!] "rescue-backdoor" thread.
ALL THE THINGS GOES FULLY AUTOMATIC !!!!!!!!!!!
ROOT and ADB are required.
What exactly does the tool step by step?
[part1: build.prop modification - bootloop protection]
makes backup of current build.prop (to /data/local/tmp/ and PC /backups/)
gets value of sony.build.incremental
reduces sony.build.incremental value by 1
dynamicaly modifies build.prop to correct value(-1)
makes backup of new build.prop (to /data/local/tmp/ and PC /backups/)
reboots and checks if modification is correct
[part2: ota zip autodownloader]
waits for user to click "Download" on ota notification
waits till ota update is fully downloaded
automatically recognizes newly downloaded ota update zip
makes backup of new ota (to /sdcard/ota-updates/ and PC /backups/)
[part3: disable/enable ota updates and notifications]
[optional] it asks if user want to disable ota system updates and notifications
to enable it back just rerun tool - it will ask in the begining of work
Any questions, suggestions - just ask !
Please post results, all the info is much appreciated!
br
condi
condi said:
Hi again
As I wrote recently - I was working on automatic tool for Sony Tab community,
to get 'rescue-backoor' (in case of bootloop), and get proper OTA update zips.
It took me a lot of effort to get everything to work as it should,
...but I think that it was worth it..... you tell me
OK... let's get to the point - MULTI-TOOL, it has 3 main functions:
build.prop modification - bootloop protection
ota zip autodownloader
disable/enable ota updates and notifications
It does all the things which was described in [GUIDE-IMPORTANT!] "rescue-backdoor" thread.
ALL THE THINGS GOES FULLY AUTOMATIC !!!!!!!!!!!
ROOT and ADB are required.
What exactly does the tool step by step?
[part1: build.prop modification - bootloop protection]
makes backup of current build.prop (to /data/local/tmp/ and PC /backups/)
gets value of sony.build.incremental
reduces sony.build.incremental value by 1
dynamicaly modifies build.prop to correct value(-1)
makes backup of new build.prop (to /data/local/tmp/ and PC /backups/)
reboots and checks if modification is correct
[part2: ota zip autodownloader]
waits for user to click "Download" on ota notification
waits till ota update is fully downloaded
automatically recognizes newly downloaded ota update zip
makes backup of new ota (to /sdcard/ota-updates/ and PC /backups/)
[part3: disable/enable ota updates and notifications]
[optional] it asks if user want to disable ota system updates and notifications
to enable it back just rerun tool - it will ask in the begining of work
Any questions, suggestions - just ask !
Please post results, all the info is much appreciated!
br
condi
Click to expand...
Click to collapse
Nice! Condi comes through again simplifying the process. I have already made a backup with the manual method but I want to give this a try when I get home so I can turn off the update part. Once I have created this new backup file should I discard the old file because of possible install issues with build.prop? I guess what I am getting at is that since I have already lowered the build.prop once this will lower it again making my download from the manual backup no good? Sorry for the long question. Thanks again!
Judah001 said:
Nice! Condi comes through again simplifying the process. I have already made a backup with the manual method but I want to give this a try when I get home so I can turn off the update part. Once I have created this new backup file should I discard the old file because of possible install issues with build.prop? I guess what I am getting at is that since I have already lowered the build.prop once this will lower it again making my download from the manual backup no good? Sorry for the long question. Thanks again!
Click to expand...
Click to collapse
Hi, your 'old copy of ota zip' will work just fine. The tool will decrease your build.prop value by 1, it will work without any issues
Both update zips will have higher value, than one in your device = both will work!
Don't forget to post results
condi said:
Hi, your 'old copy of ota zip' will work just fine. The tool will decrease your build.prop value by 1, it will work without any issues
Both update zips will have higher value, than one in your device = both will work!
Don't forget to post results
Click to expand...
Click to collapse
Ok perfect thank you. When I get home tonight I will give it a shot and post my results. I will just edit this post to keep the clutter down in this thread.
Judah001 said:
Ok perfect thank you. When I get home tonight I will give it a shot and post my results. I will just edit this post to keep the clutter down in this thread.
Click to expand...
Click to collapse
There was small typo - bad syntax in 1.0, it will make no harm, but will exit when will arrive ota download. Just redownload - v1.1
Awesome, condi~! No more worries to root my STS. Gonna try root and install this tonight.
I ran two separate tests. Both times build.prop was lowered by one with successful reboot. The issue I had both times was with my wifi after reboot. It stated that my wifi was connected but when checking my browser I was unable to pull up a page. So I disconnected and then reconnected to my wifi. I have been having this issue since rooting already on reboot so I don’t believe it was an issue with Multi-Tool. Once wifi connection was established the first test did not auto populate there was an update so I manually went to system updates to downloaded it. The second test did auto populate after a minute or two. After the update downloaded the script ran and copied all files to both of the correct locations each time. Both the first and second time the updates were successfully turned off. When plugging in on the second test I was prompted to turn the updates back on and it did so with no issues proceeding to download the update. If anyone else is having issues with wifi please let me know. Thanks again Condi for all your hard work!
zaynal said:
Awesome, condi~! No more worries to root my STS. Gonna try root and install this tonight.
Click to expand...
Click to collapse
Great happy to kick your worries out
Judah001 said:
I ran two separate tests. Both times build.prop was lowered by one with successful reboot. The issue I had both times was with my wifi after reboot. It stated that my wifi was connected but when checking my browser I was unable to pull up a page. So I disconnected and then reconnected to my wifi. I have been having this issue since rooting already on reboot so I don’t believe it was an issue with Multi-Tool. Once wifi connection was established the first test did not auto populate there was an update so I manually went to system updates to downloaded it. The second test did auto populate after a minute or two. After the update downloaded the script ran and copied all files to both of the correct locations each time. Both the first and second time the updates were successfully turned off. When plugging in on the second test I was prompted to turn the updates back on and it did so with no issues proceeding to download the update. If anyone else is having issues with wifi please let me know. Thanks again Condi for all your hard work!
Click to expand...
Click to collapse
So in summary:
everything works correctly,
WiFi issue IS NOT related to multitool.
Im glad
Hi Condi,
I guess a new issue comes up in Germany (only in Germany?).
I heard yesterday evening from a user that he bricked his Tablet S and re-installed his downloaded zip file (~ two weeks old downloaded version 3.2.1R2).
Now he got Kernel build#10 and is now not able to root his device.
(security hole is closed in this version)
Did you tried OTA RootKeeper and did it works after re-install firmware?
Otherwise we running in the risk to lose all opportunities to root the device after re-installation of latest firmware 3.2.1R2.
If OTA RootKeeper works well, we could implement the easy steps in your script for a "second chance for rooting".
Details on German Community:
http://www.android-hilfe.de/root-ha...ablet-s/201625-how_to-root-6.html#post2756883
obicom said:
Hi Condi,
I guess a new issue comes up in Germany (only in Germany?).
I heard yesterday evening from a user that he bricked his Tablet S and re-installed his downloaded zip file (~ two weeks old downloaded version 3.2.1R2).
Now he got Kernel build#10 and is now not able to root his device.
(security hole is closed in this version)
Did you tried OTA RootKeeper and did it works after re-install firmware?
Otherwise we running in the risk to lose all opportunities to root the device after re-installation of latest firmware 3.2.1R2.
If OTA RootKeeper works well, we could implement the easy steps in your script for a "second chance for rooting".
Details on German Community:
http://www.android-hilfe.de/root-ha...ablet-s/201625-how_to-root-6.html#post2756883
Click to expand...
Click to collapse
hi friend,
thanks for posting this info - its very important to stay rootable..
about OTA RootKeeper - i've got it installed and got 'protected root'.
Got to check if it works ok in details.
As far as I remember - it worked, but not from the beginning.
I've already reflashed with rootkeeper,
su-backup stays, after reflash you need to reinstall Superuser app.
Will try that when I get back home later evening.
BTW - I think I could get some other, 'extra rootkeeper' for us,
as far as I remember - with some proper permissions we could get
unwritable build.prop - then we could have opportunity to reflash
older 'rootable' zip, if another ota would lock the exploit vulnerability.
I had this one time - reflashed new ota, and build.prop remained untouched
br
condi
My friend,
I guess the magic command should be 'chattri +i'.
This is the way how Root Keeper works.
It should be possible to use the same to protect the build.prop too.
But please consider, to install an older version of update.zip, we need a much lower value in the build.prob. I have two files on my sd card (update.zip) ..
For example .. if my build.prop = 123456789, I got the last version with
123456788 and a older one (e.g. 3.2) with 103456789
Therefore we should increase build.prop for the first step (download latest version) with one and should increase a higher digit for protection as a backup.
Hi Condi:
I have boot Loop, I run the bootloop protection, but still having bootloops, Any sugestion?
Thank you
What do you mean with "I run the bootloop protection"?
Did you reinstall the ota firmware zip via recovery menu?
If yes and if it was successful the boot loop should be gone.
If you try do start boot loop protection script after getting boot loop ...
its to late ... :-(
rfreeman said:
Hi Condi:
I have boot Loop, I run the bootloop protection, but still having bootloops, Any sugestion?
Thank you
Click to expand...
Click to collapse
Code:
pro·tec·tion [pruh-tek-shuhn]
noun
1.
the act of protecting or the state of being protected; preservation from injury or harm.
You get 1000 of viruses, hard disk damaged. And then you buy antivirus software and want pc to work?
You cant protect something, that has already been done.
Now you can FIX, REPAIR, not protect!
I used your "all in one" "Install "rescue-backdoor" - anti-bootloop protection, gives opportunity to reflash current firmware
if something goes wrong with modifying system things."
But after the first step I tried to download the system update, but bootloop come again.
please tell me What can I do?.
Thank you and sorry for my english.
rfreeman said:
I used your "all in one" "Install "rescue-backdoor" - anti-bootloop protection, gives opportunity to reflash current firmware
if something goes wrong with modifying system things."
But after the first step I tried to download the system update, but bootloop come again.
please tell me What can I do?.
Thank you and sorry for my english.
Click to expand...
Click to collapse
Hello,
Bootloop can't come after trying to download ota zip.
Bootloop can't come after using rescue-backdoor thing.
Its made to protect, not to damage. Its just one value change.
Describe all the things you've done before using multitool,
there you should search for the mistake.
Do you have adb access?
condi said:
Hello,
Bootloop can't come after trying to download ota zip.
Bootloop can't come after using rescue-backdoor thing.
Its made to protect, not to damage. Its just one value change.
Describe all the things you've done before using multitool,
there you should search for the mistake.
Do you have adb access?
Click to expand...
Click to collapse
I think your first assessment was correct. It sounds like he already had a bootloop and is now trying to use protection to fix it....
BTW Thanks for the awesome tool. I've had my tablet for about a week but haven't gotten up the nerve to try and root it yet lol =D
Hi all,
I am using AiO 5.2 and I have the following configuration:
SGPT111CH/S
Android version 4.0.3 (release1a)
Kernel 2.6.39.4 [email protected] #1
Build number TISU0R0150110
Recovery .30<3e>
When trying to root using AiO I get both permissions check and the VpnFaker injection successful but the script fails 3 times at the terminal phase.
I've tried wiping, factory reset but nothing works.
I also have a problem with the update decryption. When I launch it I get a build error and a Status 7 and it doesn't go any further. If at the recovery menu I try to launch the install.zip file it fails too.
At this point I am completely lost, I must say that I'm also a little confused. Is my hardware/software combination a problem ? Is the script not working for this device ? I'm more than willing to try any manipulations you want
Cheers,
Serge
bhillou said:
Hi all,
I am using AiO 5.2 and I have the following configuration:
SGPT111CH/S
Android version 4.0.3 (release1a)
Kernel 2.6.39.4 [email protected] #1
Build number TISU0R0150110
Recovery .30<3e>
When trying to root using AiO I get both permissions check and the VpnFaker injection successful but the script fails 3 times at the terminal phase.
I've tried wiping, factory reset but nothing works.
I also have a problem with the update decryption. When I launch it I get a build error and a Status 7 and it doesn't go any further. If at the recovery menu I try to launch the install.zip file it fails too.
At this point I am completely lost, I must say that I'm also a little confused. Is my hardware/software combination a problem ? Is the script not working for this device ? I'm more than willing to try any manipulations you want
Cheers,
Serge
Click to expand...
Click to collapse
1) root - you have to keep on trying...
2) update decryption - you have to be rooted already! - back to 1) !
condi said:
1) root - you have to keep on trying...
2) update decryption - you have to be rooted already! - back to 1) !
Click to expand...
Click to collapse
Hi condi,
Thanks for your reply. Despite many attemps I didn't manage to use version 5.2 to root the tablet, but then I tried this method :
http://forum.xda-developers.com/showthread.php?t=1886460
And use the script there and despite a few errors this worked. I then used your script to "root" again since I noticed that the script I used didn't seem to install busybox and I was concerned it wouldn't be compatible with the environment you setup.
For the update decryption, I had previously rooted the tablet with the manual root procedure and despite that it didn't work. I'll try again now that I have root on the tablet after a full wipe.
Best regards,
Serge Huber
bhillou said:
Hi condi,
Thanks for your reply. Despite many attemps I didn't manage to use version 5.2 to root the tablet, but then I tried this method :
http://forum.xda-developers.com/showthread.php?t=1886460
And use the script there and despite a few errors this worked. I then used your script to "root" again since I noticed that the script I used didn't seem to install busybox and I was concerned it wouldn't be compatible with the environment you setup.
For the update decryption, I had previously rooted the tablet with the manual root procedure and despite that it didn't work. I'll try again now that I have root on the tablet after a full wipe.
Best regards,
Serge Huber
Click to expand...
Click to collapse
Ok after looking at the script I noticed you were waiting for the recovery device. That's when I noticed that my recovery driver was not properly installed. Installing it solve the problem and I got shell access to the recovery !
Maybe this was also causing the issue with the rooting ? Is that possible ?
Best regards,
Serge Huber
Ok I managed to create a custom update but when I try to flash it with AiO everything seems to work fine until the reboot where it just gets stuck on the Sony logo. If I stop the tablet by pressing over 10 seconds on the power button and start it again I get back into my normal system. I also tried your custom prerooted ROM but the same thing happened. Any clues as to what is wrong ?
Cheers and again thanks for all the help,
Serge
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?!
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