Related
Hi all
I have a G2 touch that was stock and got the OTA update to 2.1 (t-mobile). But i decided I wanted root, not for developing just to get rid of a few system apps like stock and peep.
so i followed a few guides read lots of things and ended up having the generic htc rom 1.5 and rooted after making a gold card and downgrading. The problem was the OTA upgrade to 2.1 wouldnt install. (no groans from those that know what they are on about i'm new to this and thought it would upgrade )
as i like 2.1 more i ended up reflashing the stock 1.5 htc rom without having root and the OTA upgrade worked fine.
Now ive played with the generic htc 2.1 i actually prefer the t-mobile rom as it seems to have more in it like g-sensor calibration etc.
ive read several pages on here and other forums and now im just confused as to how to get a rooted version of the t-mobile 2.1 rom.
is it even possible?
if not and i do the full gold card and downgrade procedure again Which ROM will give me rooted 2.1 that is the closest to the t-mobile stock so i can remove the stock apps i want rid of?
sorry if it seems like an obvious question but i really dont get all this kernel, radio flashing, kitchens and all of that stuff i just want a simple rom i can put in and everything works like normal except i have root
thanks for your help
stevegb666 said:
Hi all
I have a G2 touch that was stock and got the OTA update to 2.1 (t-mobile). But i decided I wanted root, not for developing just to get rid of a few system apps like stock and peep.
so i followed a few guides read lots of things and ended up having the generic htc rom 1.5 and rooted after making a gold card and downgrading. The problem was the OTA upgrade to 2.1 wouldnt install. (no groans from those that know what they are on about i'm new to this and thought it would upgrade )
as i like 2.1 more i ended up reflashing the stock 1.5 htc rom without having root and the OTA upgrade worked fine.
Now ive played with the generic htc 2.1 i actually prefer the t-mobile rom as it seems to have more in it like g-sensor calibration etc.
ive read several pages on here and other forums and now im just confused as to how to get a rooted version of the t-mobile 2.1 rom.
is it even possible?
if not and i do the full gold card and downgrade procedure again Which ROM will give me rooted 2.1 that is the closest to the t-mobile stock so i can remove the stock apps i want rid of?
sorry if it seems like an obvious question but i really dont get all this kernel, radio flashing, kitchens and all of that stuff i just want a simple rom i can put in and everything works like normal except i have root
thanks for your help
Click to expand...
Click to collapse
I'm not aware of any T-Mobile 2.1 ROMs, as everyone wants to rid their phone of branding normally.
But... here's the best method for you. Install your old official 1.5 ROM, and then do the OTA update to 2.1. Make sure you install your T-Mobile 1.5 to do this.
Then, go to http://www.villainrom.co.uk/viewtopic.php?f=110&t=2096 and follow that guide to get a custom recovery image onto your phone. From there, you can use adb to access your handset as root, and add and remove stuff as you please. ADB info is in that guide, and a guide to removing apps is at http://www.villainrom.co.uk/viewtopic.php?f=46&t=862
HTH
PS. This won't give you everyday root, for things like root apps, since your ROM won't itself be rooted. But if you look up "Superuser.apk" and push that to /system/app (you'll learn about pushing etc with adb or googling 'adb push'), along with the su binary, you can give yourself basic root, though it won't be perfect.
If anyone else wants to help out, what you'll need is the 2 superuser files i mentioned, and a modified boot image that has the changed hero.prop (i think it's called that), with ro.secure set to 0 in the ramdisk.
But don't worry about this later stuff unless you need to.
Hi thanks very much for the help
i get the idea right up until the basic root bit, so think i will get that far .....after that you lost me
will i be able to use apps for rooted devices if i just get the basic root working?
stevegb666 said:
Hi thanks very much for the help
i get the idea right up until the basic root bit, so think i will get that far .....after that you lost me
will i be able to use apps for rooted devices if i just get the basic root working?
Click to expand...
Click to collapse
Should be able to. Give it a go That last bit wasn't intended for you, more for anyone who tries this in future and wants adb root access.
i've managed to hit another problem....
i'm trying to install the adb drivers and having trouble. i have the normal usb drivers installed and have downloaded the drivers from villanrom (it wont let me post the link sorry)
but when i tell it to install them i get a window pop up saying the driver contains no information for my device.
ive uninstalled the my htc drivers and tried again but i never get an adb device appear.
am i missing something obvious?
im using windows xp and have the hero set to pc sync when connected.
thanks
stevegb666 said:
i've managed to hit another problem....
i'm trying to install the adb drivers and having trouble. i have the normal usb drivers installed and have downloaded the drivers from villanrom (it wont let me post the link sorry)
but when i tell it to install them i get a window pop up saying the driver contains no information for my device.
ive uninstalled the my htc drivers and tried again but i never get an adb device appear.
am i missing something obvious?
im using windows xp and have the hero set to pc sync when connected.
thanks
Click to expand...
Click to collapse
Hmm OK. I know the issue. Find the driver folder, and use this file as the ini file
http://dl.dropbox.com/u/7618177/android_winusb.inf
I had to hack the file to make it recognise the hero
this official update will lock your recovery options to flash custom roms!
so my recommendations is
AVOID OFFICIAL UPDATES, and you're safe
Its still ROOT'able, but no documentation atm, for how to revert back to a recovery, that works.. but if you can root,
the important part is to copy my "recovery.img" file to a location on your device ie. like /data/recovery.img
and from shell you execute
cat /data/recovery.img >/dev/block/mmcblk0p7
root works
hello, i little speak english...
PdaNet + SuperOneClick method works for root
Sorry double post...
for rooter, you must do this if the update took place from Service Station:
1. Start the Recovery -> Wipe Data / Factory Reset -> Reboot
2. Start normal and remove Toshiba Service Station and Market Place -> Turn off the Folio
3. Start the Recovery -> Wipe Cache -> Reboot
4. Start with the normal and new rooter SuperOneclick 1.6.5. - Turn off the Folio
5. Normal Start
guiooom said:
4. Start with the normal and new rooter SuperOneclick 1.6.5. - Turn off the Folio
Click to expand...
Click to collapse
other reported that it did not work on new updates. only on old stock before 0053.. so maybe someone can confirm this on new release.
Maybe you can do a 'safe' version of the new ROM for us that doesn't include the new lockdown? This is so tedious of Toshiba - I struggle to understand what they try to achieve by doing this.
I'm starting to think Toshiba deliberately want's to make this device useless.
Do they hate there first tablet so much they even punishing the people who bought it?
This new releases works 100%
This new releases works 100% (PdaNet + SuperOneClick)
gooooooo
enjoy
guiooom said:
This new releases works 100% (PdaNet + SuperOneClick)
gooooooo
enjoy
Click to expand...
Click to collapse
but can you flash a custom rom? its not much help if you need complex methods of installing / reverting back to another custom rom, so you recommendation might be users are stock on something they dont want..
AND!
users need to have a ADB connection to your folio, which again is not many regular users know how to do, so again making it much more complex to work with..
if will NOT RECOMMEND installing stock, for regular users.. you will spend hours on trying to get back to a custom rom, which is not needed at all.
Dexter_nlb said:
but can you flash a custom rom? its not much help if you need complex methods of installing / reverting back to another custom rom, so you recommendation might be users are stock on something they dont want..
AND!
users need to have a ADB connection to your folio, which again is not many regular users know how to do, so again making it much more complex to work with..
if will NOT RECOMMEND installing stock, for regular users.. you will spend hours on trying to get back to a custom rom, which is not needed at all.
Click to expand...
Click to collapse
Dexter, I'm confused. Or maybe I misunderstood. Why is it bad to flash to the new firmware when you can restore it back to factory settings? Coz once I can do that, I can get back my old firmware and flash custom mods again as before. Or would flashing to the new firmware make it the new default factory setting? Hmm....
SoJoS said:
I'm starting to think Toshiba deliberately want's to make this device useless.
Do they hate there first tablet so much they even punishing the people who bought it?
Click to expand...
Click to collapse
+1
This is such a bad move by Toshiba...at least make a proper product like Motorola then they can do these stupid stuffs
Oh no! I waited too long before ordering mine I've been told there's a new batch coming in March - obviously these will come with the new factory ROM!
Dexter, is there no way of putting on custom ROM's onto the device with this factory ROM pre-loaded?
That's part of the reason I ordered one - I like to tinker
jmgers said:
Dexter, is there no way of putting on custom ROM's onto the device with this factory ROM pre-loaded?
That's part of the reason I ordered one - I like to tinker
Click to expand...
Click to collapse
seems it can be root'd after all, so its not all locked down, but i hope someone will write the "howto" for doing it, because its no so simple to revert it, but is possible..
Hello
How can I root it after this update? SuperOneClick doesn't do it.
What's 'PdaNet + SuperOneClick' method? What should one do to gain the root privileges?
One should find a SuperOneClick Tutoraial on XDA & follow it.
Works like a charm once you installed everything prior rooting procedure.
http://forum.xda-developers.com/showthread.php?t=803682
After fooling around with UrukDroid 0.7 (installed to the internal storage), I've decided that I would like to go back to the stock Archos FW. How would I go about doing this?
You could just delete the partitions or you could completely wipe the Tablet from the boot menu.
Didn't think it would be that easy. I had a little hiccup when I saw the UrukDroid splash on the first boot and it had to rebuild rootfs, but now it seems to be working fine.
chiasticslide said:
After fooling around with UrukDroid 0.7 (installed to the internal storage), I've decided that I would like to go back to the stock Archos FW. How would I go about doing this?
Click to expand...
Click to collapse
just out of curiosity: why did you decide to go back to stock rom? i'll get my 101 in a few days and i'm still deciding whether to install uruk or not.
and another question: so you can just revert to the stock rom without any traces of custom rom being installed? i thought if you once installed sde from archos there's no going back to stock state and you can kiss your warranty goodbye???
thanks!
pirecrompir said:
just out of curiosity: why did you decide to go back to stock rom? i'll get my 101 in a few days and i'm still deciding whether to install uruk or not.
and another question: so you can just revert to the stock rom without any traces of custom rom being installed? i thought if you once installed sde from archos there's no going back to stock state and you can kiss your warranty goodbye???
thanks!
Click to expand...
Click to collapse
The SDE gives you the option to boot stock OR the dev environment, it does not remove the stock rom.
Sent from my Nexus S using XDA Premium App
krohnjw said:
The SDE gives you the option to boot stock OR the dev environment, it does not remove the stock rom.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
ok, thanks. but doesn't the installation of sde itself void the warranty? or could you go back to the stock rom from uruk, uninstall sde and let's say return the malfunctioning unit under warranty and archos wouldn't know you had sde installed? sorry for my "android-ignorance", i've been a years-long user of wm phones/handhelds and this will be my first android device ...
thanks
p.s.
nevermind, i found this on the archos page:
# Once the SDE firmware is installed on a device, this device will be watermarked and ARCHOS will be able to detect that this firmware has been installed once.
# Installing the SDE firmware is considered by ARCHOS as a voiding of the warranty and ARCHOS declines all liability and responsibility for any issues resulting from the installation of this SDE firmware.
so, if i understand correctly, once you've installed sde, you can never make a warranty claim of any kind, even if you've uninstalled sde and it's a hardware error or malfunction of the unit?
thanks
So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.
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?!