Database Users

Free 50 GB Box Account HELP

I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?

yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?

bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.

bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.

ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.

This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.

be careful, backup buid.prop and restore it after creating Box account.

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse

I am having no luck finding a way to get root access from a computer.

deleted post
user error

The tumbleweeds are big around here

There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/

But is there an app to copy my file over from my computer?

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug

I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.

yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.

jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...

its taking forever to install SDK

This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.

yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?

[Q] HUGE problem! >:_(

Hi,
I was going to install a ROM on my Nexus, so I made a backup and wiped EVERYTHING. Including the SD card so now in clockworkmod
it can not mount the SD card, I cannot mount it to my computer... I am shaking and my hands are cold... I cant flash any rom HELP NOW!!!! ((((
thanks

No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium

nodstuff said:
No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a factory image please tell me how'd I do that in fastboot! (only if they had a begging at knees thing)

ok i will write you some step by step functions to follow in order to get yourself a rom onto your device
Info that is Needed!
Do You Already Have ADB functioning on your Computer
If Yes - Skip to Step 2
If No Proceed from Step 1
----STEP 1----
install the ADB drivers for your device
im going to assume you have a windows machine here so the followthrough will be for windows (i use Win7 but it should be the same)
BOOT YOUR DEVICE INTO RECOVERY WHILE PLUGGED INTO YOUR PC BUT DO NOT CLICK ON ANYTHING
1. Download These Google Drivers for Nexus Devices http://www.themoviedb.org/movie/15092-crank-ii-high-voltage
2. extract the folder
3. press the start button
4. right click on "Comptuer" or "My Computer (XP)
5. Click on Manage
6. in the new window press "Device Manager" on the left
you should see in the tree on the right (a device with a yellow exclamation mark ! probably called nexus)
7. right click it and press update driver software
8. press browse my computer for driver software
9. press let me pick from a list of device drivers on my computer
10. press have disk
11. press browse
12. on the new window navigate to the folder you extracted earlier and select the android_winusb.inf
13. press ok
14. there will either be 1 or 2 options to choose - click Android Composite ADB Interface and then press next
15. tick always trust software from google inc. and then install
your device should now have ADB capablilities
Proceed to step 2
----STEP 2----
this will use adb to push a file to your device while it is in recovery mode which you can then flash
1. Download This - http://www.mediafire.com/?50baad8rykng2j0
these are adb & fastboot binaries which will allow your pc to send files to your nexus via ADB
2. extract the downloaded archive to somewhere easy to remember ( i suggest C:\fastboot )
3. rename your downloaded custom rom to rom.zip (for simplicity) and copy it to the extracted directory (the one with adb.exe & fastboot.exe)
4. bring a command prompt to this directory
- in the directory you extracted (c:\fastboot) hold shift and right click in a blank area of the main window
- click "open command window here"
or
- Windows Key & R
- in the new box type cmd then press enter
- type cd c:\fastboot (where c:\fastboot is the directory where you extracted)
now to push it over
5. in the cmd window type adb devices and make sure your device is listed
your should see something like
list of attached devices
XXXXXXXXXXXXXXXX Recovery
where XXXXX is your devices serial number
6. in your cmd window type adb push rom.zip /sdcard/
this will take a while to complete but once it is down go back to your device and try to install a rom as you usually would
you should see the file in your internal memory to install now

^^ I was too slow!
First install the android SDK (Google it) then you need to put fastboot in your path you need to open my computer, system properties, advanced system settings, environment variables button at the bottom, then in the bottom window scroll down til you see find path and edit it and add the path to the android SDK and in particular the platform-tools folder.
So if you download the android SDK to your C drive, the path you will be adding will be like ";C:\android-sdk\platform tools" (note the semi colon at the start, important to separate entries)
Once the path is set up you can use fast boot in cmd just by typing fastboot xxxxx rather than typing C:\android-sdk\platform-tools fastboot xxxxx every time.
So next thing is to extract the images to somewhere.
Inside the zip is another zip called image-nakasi-jzo54k,
unzip that til you have .IMG files, system.img, boot.img etc.
then once they are extracted you use cmd to CD to that folder where you have the images and you can start to flash them.
fastboot flash system system.img
fastboot flash boot boot.img
You could just use flash-all.bat but and that will flash them all automatically but will wipe your internal SD.
Sent from my Nexus 7 using xda premium

If you JUST read that, I figured it out, and if I can flash all the partitons correctly, I will punch the thanks button.

cburk01 said:
yay new problem
Ok, so I unzipped it, extracted the thing inside, but it was it a weird format Windows recognized as "file". So, I added .zip to the end. WinRAR opened it, I saw the files, began to extract when an error popped up about the archive being damaged. WTF.
Click to expand...
Click to collapse
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium

nodstuff said:
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Now I REALLY DO have a problem. I flashed boot.img, system.img, userdata.img, everything to the right partitons and still have a problem. Boot loop. Sticks on Google logo. Why? I did everything right. I even tried fastboot boot boot.img, no luck. I saw some people having boot loop problems, too on 4.1.2. So now, until you reply, I am going to try a custom kernel. Scratch that I'm using ToolKit to download and install 4.1.1.

If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium

nodstuff said:
If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*facepalm* with the SD I already wiped that before I flashed. And I didnt run flashall.bat or what ever its called so I am going in to try that. Ran flashall got some weird radio flashing error so now continuing with ToolKit.

Flash-all.bat just automatically flashes all the images by running one command, it simplifies the process.
It just isn't ideal if you wanna keep your SD contents.
that's why you flash images separately, so you don't flash userdata.img but since you already wiped it then you're good to go.
Sent from my Nexus 7 using xda premium

WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*

Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?

cburk01 said:
WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*
Click to expand...
Click to collapse
Your backup is most likely gone, its stored on the SD card and that is wiped. Unless you have it on your computer, then you are all good.
Glad its back to life and now you know how to fix it if anything goes wrong.
What you learned today is very valuable to know.
It's nearly impossible to kill a nexus device (from a software perspective)
Sent from my Nexus 7 using xda premium
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
cburk01 said:
Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?
Click to expand...
Click to collapse
Update first
Sent from my Nexus 7 using xda premium

Yes, I have my backup on my Macbook (running Windows 7). Thanks for all the useful advice. lol about the Nexus devices are hard to kill thing, I imagined a cockroach. And about the valuable lesson thing, I learned fastboot commands and adb stuff all when I was messing with (then soon after fixing) my HTC EVO 3D. Oh, I love XDA. Thanks again.
-cburk

Can't flash KRT16S (from KRT16O)

Hi everybody
When the factory images came out, I flash my N4 with the stock factory images that we used to find here : https://developers.google.com/android/nexus/images#occamkrt16s because it is now the KRT16S build
After a few days, when the KRT16S build came out, I was proposed in my phone to update it. I downloaded it, tried to flash it but nothing worked, I'm still on KRT16O and the OTA doesn't appear anymore... Then I remembered that I flashed a mod found here : http://forum.xda-developers.com/showthread.php?t=2527525 (that's a great mod btw) so I guessed that I could reflash the undo file available on the thread, flash the ota file dl mannually (I attached it in this thread) which I did through TWRP. Then I was able to see the problem, it told me that, from what I remember, Agenda.apk was missing (I think it's diary in english, not sure) then I remembered that I manually deleted some apps I never use (diary is one of them...)
So, what's next, shall I reflash the gapps to finally update my phone
Thanks for your help :laugh:

Are you using latest TWR? I did it ok
Sent from my Nokia 3210

howard bamber said:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
Click to expand...
Click to collapse
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]

azertguigui said:
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
Click to expand...
Click to collapse
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.

taodan said:
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
Click to expand...
Click to collapse
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try

azertguigui said:
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
Click to expand...
Click to collapse
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"

MameTozhio said:
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
Click to expand...
Click to collapse
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-

UP

azertguigui said:
UP
Click to expand...
Click to collapse
**

azertguigui said:
UP
Click to expand...
Click to collapse
azertguigui said:
**
Click to expand...
Click to collapse
Not sure what you're trying to say here..
azertguigui said:
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
Click to expand...
Click to collapse
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!

try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.

Ibrahim.Rahman said:
Not sure what you're trying to say here..
Click to expand...
Click to collapse
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Ibrahim.Rahman said:
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I'll give a try
saifulh2304 said:
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
arffrhn said:
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Click to expand...
Click to collapse
thanks guys, I'm gonna find tutorials on the web like the one you pointed to me

azertguigui said:
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Click to expand...
Click to collapse
Haha right!
Sent from my Nexus 4 using xda app-developers app

[me176c/x] [K013] Collection of ROMs and Updates

[me176c/x] [K013] How to Root and update from .182 to Lollipop release
Stock ROMs up to v.182, all languages
ASUS' Download Center for the MeMo Pad 7 Link is now inaccessible as ASUS has redesigned their site. Even the support page for this tablet no longer has any links to download ROMs/updates. Sad panda. However, the ones below (ASUS' direct links included) still work! I am also in the process of reuploading/rehosting all of these as well, so stay tuned! So far everything is rehosted on Google Drive, and I plan to add more mirrors in the next couple of days. Pleasse bear with my snarkiness, I have been up late and it's now 4am. I must crash now.
Anyway........ Enjoy!!
WW 182 Full ROM
ASUS
Google Drive
WW OTA 191
ASUS
Google Drive
Google Drive (alt)
WW OTA 198
Google Drive
WW OTA 199
Mediafire
Google Drive
WW OTA 201
Google Drive
Zippyshare (ew)
WW Lollipop release
Mediafire
Google Drive
If you have other links to share, especially direct links from ASUS or non-GDrive hosts, please feel free to post them and I will credit you!
(Manually) Flashing Updates
Sometimes (read: often) an update will fail to install and reboot, and then the tablet will claim you're up to date when you check for updates (and we know it's full of crap). So you'll have to manually update yourself, and often, if only works if you start from .182 (or above), and flash each file in consecutive order. So here's how it works. Be sure to read over this before starting, to get an idea of what's in store for you. And to be safe, read it again. And to be doubly-sure, read it AGAIN (I cannot stress this enough).
Obligatory warnings:
Your warranty (expired by now, for sure) is now null and void. Regardless of whether you do this, it's no longer valid either way! :laugh:
I am not liable for any damages to your device (or your brain) that this process may cause. What you do to your device is on you, but if you play it safe and read this all carefully (and read it again! And AGAIN!), you shouldn't have any trouble.
Instructions:
First things first, install your drivers if you haven't already, and set up the Android Platform Tools (adb and fastboot exes and such, also attached to this OP). I highly suggest trying the Latest ADB Fastboot and USB Driver installer tool for Windows by @fawazahmed0 (or the various attached drivers below, if you still somehow have trouble with getting your PC to recognize this dinosaur of a device).
Next, before we continue, make sure USB debugging is enabled on your tablet. Go to Settings > About tablet, and tap on Build Number 7 times, and you'll see a toast, "You are now a developer!" Back out once and scroll down a bit, you'll now see Developer Options. Enter, and near the top you'll see an option for USB debugging, so check that box. Plug in your tablet to the PC, then open a command line interface (Hit Windows Key + R, then type in "cmd" and press enter). Type in "adb devices" (without quotes) and look at your tablet's screen for a prompt. Check the box and tap OK. Now. back in the command prompt, press up and enter on your keyboard (which will repeat that last command), and you'll see your tablet's serial number (a string of letters/numbers) and the word "device" if you did it correctly. Now you're ready for the next part.
1. Install the "RootZenFone-1.4.6.8r.apk" (attached to this OP, below) and run it. Beware, it may have some Chinese text/Engrish. It's fairly simple to figure out though, thankfully.
2. Turn on USB debugging if you haven't already (didn't you read this first? You're already slacking!).
3. Download the zip file(s) you need and rename it update.zip and transfer it to your tablet. Or copy all files to the tablet and rename them (with a file manager of your choice, see next step) as you go.
4. Download a file manager that has root access (such as MiXplorer or Root Browser).
5. Go to / (root) and manually copy your update.zip to the /data folder.
6. Download this command file (also attached below, in a zip) and copy it to the /cache/recovery folder. This must be present each time you install an update via this method, so leave a copy on your device.
7. Back to Windows Command Prompt, run the command, "adb shell" (without quotes, as before), wait a moment for it to reload the server, then type, "su" (again, without quotes). When you type in the "su" command for the first time, it will prompt for SuperSU access on your tablet, similar to how it requested the RSA perms with adb debugging. You must allow this root permission, or the following won't work!Now, type line by line (or better yet, copy and paste into the command prompt (a right click automatically pastes copied text into it, btw):
Code:
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
In brief, what this means is that you just ordered the "command" file to boot as a "recovery" in order to flash the update package you copied and renamed previously. Thus, the tablet will reboot and commence flashing. At least, I think that's what's happening here. Sorry, I'm no rocket surgeon. All I know, is that it works. However, if you are getting an error during the update process, as mentioned above, you will likely have to flash the next incremental update (the one just above your current version) instead and go from there, flashing each OTA in order using the coded commands above every time. Be sure to rename EACH ZIP to "update.zip" as you do this or the command cannot find the file! Yes, this sounds like a pain, and it is! But this has worked when the direct approach had failed.
Archive folder of everything needed, on Google Drive
ROOT ZenFone FAQ has a translated guide on how to fix ptotential issues with the root process.
Credits:
@plopingo and @jerbear294 for some of the links.
@lethardicus for finding most of the OTA zips again when one weirdly went missing @fawazahmed0 for the driver installer tool
@slayeralive for providing the basis for these instructions

Nice work sub

No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery

@GuyInDogSuit
Update
mirrored OTA 191, 198, 199, 201 & RootZenFone-1.4.6.8r apk => https://drive.google.com/folderview?id=0B5G23fyE72tnLS0yaXlUamVmcXc&usp=sharing#list

@GuyInDogSuit @slayeralive
I've try to update manually but it failed
how to flash .182 if I'm already in .191 ?

slayeralive said:
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
Click to expand...
Click to collapse
You don't have to do all the typing anymore?

GuyInDogSuit said:
You don't have to do all the typing anymore?
Click to expand...
Click to collapse
I've try, the tablet show android logo with no command on the screen after reboot without entering command

you did something wrong. command file is just txt file , and echo command in terminal is used for writing text in txt files.try to copy command file and reboot to recovery from terminal emulator with reboot recovery command. I created this method mainly for unbricking read post
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049

GuyInDogSuit said:
Thanks to @plopingo and @jerbear294 for some of the links.
Click to expand...
Click to collapse
OMG, I can't believe I JUST found this thread.
I have two of these tablets that I use as wall-mounted controllers for HA. One of them accepted the OTA updates and I was able to get it to .201 and keep it rooted. The other one, no matter what I tried, would not pull down anything above the .182 it was running.
This post has EVERYTHING you need to go from whatever all the way to .201 quickly and very easily. I installed 15 Second ADB, the ASUS ADB drivers, and ran through all of the updates. This, my friends, is awesomesauce.
HUGE THANK YOU to @GuyInDogSuit, @plopingo, and @jerbear294!

No luck
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast

peldo123 said:
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
Click to expand...
Click to collapse
It could. I have made that last year and end up with a bricked tablet...
I had to make a complete reset.
I made a few tries until I get it right and found out that using certain terminal apps don't allow spaces between commands whilst others do... Try commands without breaks if you're using a terminal app. Or try temp cwm to update all the updates at once.

Can't get it to work
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!

kdlannoy said:
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
Click to expand...
Click to collapse
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!

This fixed it! That was a stupid mistake

kdlannoy said:
This fixed it! That was a stupid mistake
Click to expand...
Click to collapse
I'm glad it worked. I once made the same mistake.

I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?

mrseverin said:
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
Click to expand...
Click to collapse
Should be safe. I had a recovery folder, but nonetheless I don't see why it would harm anything.

I've had several Android devices. That was the easiest root I've ever done.

bravesoul said:
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
Click to expand...
Click to collapse
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.

regele said:
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
Click to expand...
Click to collapse
"/root" isn't a folder. It's the source. For example. When you copy something to a hard drive you are copying to the root of that hard drive. The same goes with the root of the android. So. Copy the unzipped .zip file to root and to inside data folder. Rename it into update.zip and run the commands.
I realise you got it to work, but since this is a community I have explained to others.

*UPDATED**UNLOCK TOOL (4-2019) for ALL Versions of BLU R1-HD

BLU R1-HD bootloader unlock script tool, and TWRP install tool.
Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat
The included files and folders are set to hidden, in effort to keep them safe from accidental delete.
Must have adb+fastboot + drivers installed and setup prior to using tool
Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"
LINK==>ADB+FASTBOOT
It is for windows
In linux :
"sudo apt-get install android-tools-adb"
"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"
"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)
Using Tool
On Windows?
Unzip the downloaded file to a new folder, open new
folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"
Do the steps in order (1-2-3-4) to be unlocked, then
Step (5) to get to second page where step (1) is root
The rest is optional
On Linux?
Unzip downloaded file to new folder folder .
Open folder. Then open R1-Linux-tool-v2 folder
Open terminal from that folder and type
" . R1-HD-TOOL.sh "
Same order of steps (1,2,3,4) step (5) for extra
Steps (1 on second menu) for superSU root.
Second menu steps (2,3,4,5,6,7,8) are optional.
**Linux Note**
The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.
The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize
this command. But "apt-get install fastboot" updated some version and then the command was recognized.
******OTHER NOTES****
--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----
--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"
--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.
CHANGE LOG
V1:. Initial release : removed
V2:. : fixed typos preventing proper function
V3:.: switch file verification to md5 check instead of "ls-l" comparison.
V4: current version: add extras page, add SU flash, de-bloat script, Added Fm Radio, Added pre-loader roll back
V5: Fixed wrong loop "goto" line that made preloader rollback do "MTK_BLU Debloat v2" instead
V6: Added manual pause to script for mods that need recovery (Extra's 5) . Added redundent recovery flash command .
Few reports of recovery "not Sticking" and needed to run the flash commands manually one by one. Maybe the redundent
flash will make it survive. If still having problem with recovery "staying install" try manually flashing
here is link to the steps needed. FLASH RECOVERY
V7 Improved logs Added line to make batch run as sub-process so if error occurs , will not close
V7.1 : Updated the fm radio install zip and include the needed selinux mode changer app
V8: fixed dependency of needing to be unzipped to location w/o spaces in name. (when used from location with spaces, tool used to fail to push needed files).
.. added more time to allow dirtycow to "spawn" its root shell. Recent testing has shown sometimes it takes longer than the 60 seconds allowed in the script. Now it is looped 3 times.
V9 Added full path to abd push lines for recovery flash files. included fastboot.exe file to address some version issue where user s version would not output text file I coded into script for a verification ( included file is called by script, no need to do anything different with it)
V10: Moved zip file to included folder to help preserve locations when unpacked, added device check before running tool; So tool not used on wrong device, Rearranged order of operations on extra's page. (recovery installed options) Push files while in android before rebooting to recovery( should improve reliability for multiple reports of not automatically installing options for some)
******I have received some reports that some devices are reporting "ro.build.product =R1_HD and not "BLU_R1_HD" like mine, so the added device check is blocking tool from starting If this happens to you , you can make edit to the .bat file like below.
Change this line
Code:
:next_check
find "BLU_R1_HD" "%~dp0workingproduct.txt"
To this
Code:
:next_check
find "R1_HD" "%~dp0workingproduct.txt"
it is line #23
V11: Updated device model verification lines
MTK-SU: Replaced all dirty-cow part with New MTK-SU binary(elf) from @diplomatic
source
Click to expand...
Click to collapse
Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.
DOWNLOAD LINK
Preferred to use the Downloads tab of this thread.
Archived downloads on android file host also == link
XDA:DevDB Information
R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD
Contributors
mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,
Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD
Version Information
Status: Testing
Current Stable Version: V11
Stable Release Date: 2017-04-11
Current Beta Version: MTK-SU
Beta Release Date: 2019-04-14
Created 2017-02-22
Last Updated 2019-04-18

Reserved
Items planed to be addressed in next release:
--Add few more file integrity checks to the extra's page
--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file
--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)
--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above
--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )
--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.

Reserved

Works great on OEM 6.6, thanks for the tool!

So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function

theredbaron1834 said:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
Click to expand...
Click to collapse
thank you for your input.
As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.
The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.
The lines with only 2 "::" are standard windows comment / remark line entries
The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for

Does Works to unlock 7.4.2?

khyr said:
Does Works to unlock 7.4.2?
Click to expand...
Click to collapse
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.
The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.

edit:
I have the linux version ready.
-the first step, (ADB Push) is ready. including md5 file checks
-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device
-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check
I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison
-step 4 is ready .--flash twrp
Finished 90% of tool.
still need to tweek the log feature.
I ran tests on the lop back to menu and test ran
1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass
2. run dirty cow commands and md5 verification on resulting file. ==pass
3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass
4 . flash twrp --installed both version i have, both install fine ===pass
5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass
(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)
6. instruction ====not written yet
7. exit yes it closes == pass
8. logs --- needs completeing

I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.

torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system

mrmazak said:
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
Click to expand...
Click to collapse
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.

OOPS
found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"
fixed and still reading and re-reading to search for errors.
This looks bad.
The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.
re-posted V5 combined with linux V2--

torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you

gabriel986 said:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
Click to expand...
Click to collapse
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.

mrmazak said:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
Click to expand...
Click to collapse
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
In case it's needed, my R1 HD is running on
BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38

gabriel986 said:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
Click to expand...
Click to collapse
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.

mrmazak said:
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
Click to expand...
Click to collapse
trying again....
for how long should I press the volume up key?

gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on

mrmazak said:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
Click to expand...
Click to collapse
ok.. trying again
---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
it beat me!
I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.