I just bought ASUS Memo Pad 7 (ME572C)
but I can't find root message for google
It android kitkat 4.4.2
please help me~
thanks
woff said:
I just bought ASUS Memo Pad 7 (ME572C)
but I can't find root message for google
It android kitkat 4.4.2
please help me~
thanks
Click to expand...
Click to collapse
You're gonna have to wait for a while. It hasn't yet reached general availability. Currently I can only find it for sale on John Lewis in the UK. And they brag about it being exclusive to them.
I just got it at Best Buy, so they're out and available and just waiting to be rooted...
Im also thinking of getting this new Asus Memo 7. Is this new intel chipset rootable?
I just found this for it.
http://www.xxxxxxxxxxxxxxxxxxxxx
Don't know if it's real or not.
Moderator Edit: No it isn't - now obfuscated.
I am also the happy owner of an ASUS Memo Pad 7 (ME572C).
Before this one I had the Nexus 7 (2012), a great tablet. But it broke and I bought the ME572C, which is a kind of up upgraded nexus.
Also waiting for a way to root it, to use all the possibilities of this quick processor.
The link in the mesagge before looks like spam to me.
Anybody any idea when someone will find the way to root it??
I just got an Asus ME572C, I wanted the Nexus 7 (2013) but it was not in stock. And I have to say, that despite is not Google stock, this tablet is a kick ass device.
So I hope and it would be nice, to add a forum for this great tablet and see some development. I think is a great device to work on.
I dont have much time but I will try to do some stuff with It. O if someone do something and want people to test it. Here I'm
I search a way to root this beautiful tablet..... the processor 64 bits is the thing which is difficult to root ?
I'm surprise that dolphin don't run on.
found this, but I haven't try anything yet
Some information [MeMOPad] ME572C of
Talk about the boring part:
Intel Z3560 / Z3580's CPU, boot.img / fastboot.img / recovery.img of HEAD_PADDING back UNKNOWN_SIZE is 728 bytes, but BOOTSTUBSTACK_SIZE is 8192 bytes.
RootZenFone change it to use, and then release a small update late.
Inside sideload recovery is bad, adb port can not open, when to get there to do a software update or not repaired, guess should not want people to use it? fastboot there SD Download, it seems the future of factory image will be .raw format.
The more interesting part:
fastboot there is a small back door, can be used to do the root of the application:
fastboot oem mount <partition> <fs type>
The first instruction is to mount partitions on the phone, will be mounted at / mnt / <partition> data folder, so I'm going to mount the system is ext4 fastboot oem Mount system , that is, you want to mount userdata fastboot oem mount data ext4 can.
fastboot flash <path_to_phone> <path_on_local>
The second instruction is to update the information on the phone route, originally only update existing files , but here I do not know why is modified to replace the existing file or upload , it is very interesting, root application ready. Because it is 4.4 and there is open SELinux, so the best way to modify the existing shell file will be executed, when it related to root after the brush into the program to reboot automatically go into.
The idea is simple:
fastboot oem Mount system ext4
fastboot Flash / mnt / system / xbin / su su
Flash /mnt/system/etc/install-recovery.sh install-recovery.sh fastboot
fastboot Flash /mnt/system/Superuser.apk Superuser.apk
Then find a .sh file can be used to modify the plug plug back in the boot judgment if no /system/etc/.installed_su_daemon run the installation program, produced /system/bin/.ext/ , / system / bin /. ext / su , / system / xbin / sugote , / system / xbin / sugote-mksh , / system / xbin / daemonsu ...
Packaged on a free, self-interested hands.
-----------------------------------------------------------
gabriel-arg said:
found this, but I haven't try anything yet
Some information [MeMOPad] ME572C of
Talk about the boring part:
Intel Z3560 / Z3580's CPU, boot.img / fastboot.img / recovery.img of HEAD_PADDING back UNKNOWN_SIZE is 728 bytes, but BOOTSTUBSTACK_SIZE is 8192 bytes.
RootZenFone change it to use, and then release a small update late.
Inside sideload recovery is bad, adb port can not open, when to get there to do a software update or not repaired, guess should not want people to use it? fastboot there SD Download, it seems the future of factory image will be .raw format.
The more interesting part:
fastboot there is a small back door, can be used to do the root of the application:
fastboot oem mount <partition> <fs type>
The first instruction is to mount partitions on the phone, will be mounted at / mnt / <partition> data folder, so I'm going to mount the system is ext4 fastboot oem Mount system , that is, you want to mount userdata fastboot oem mount data ext4 can.
fastboot flash <path_to_phone> <path_on_local>
The second instruction is to update the information on the phone route, originally only update existing files , but here I do not know why is modified to replace the existing file or upload , it is very interesting, root application ready. Because it is 4.4 and there is open SELinux, so the best way to modify the existing shell file will be executed, when it related to root after the brush into the program to reboot automatically go into.
The idea is simple:
fastboot oem Mount system ext4
fastboot Flash / mnt / system / xbin / su su
Flash /mnt/system/etc/install-recovery.sh install-recovery.sh fastboot
fastboot Flash /mnt/system/Superuser.apk Superuser.apk
Then find a .sh file can be used to modify the plug plug back in the boot judgment if no /system/etc/.installed_su_daemon run the installation program, produced /system/bin/.ext/ , / system / bin /. ext / su , / system / xbin / sugote , / system / xbin / sugote-mksh , / system / xbin / daemonsu ...
Packaged on a free, self-interested hands.
-----------------------------------------------------------
Click to expand...
Click to collapse
thank you
I try it !
woff said:
thank you
I try it !
Click to expand...
Click to collapse
Please send some feedback about how it did go!!
---------- Post added at 06:33 PM ---------- Previous post was at 06:25 PM ----------
and have someone tried NFC on this tablet?
according to all web sites it has NFC, but I cant find any setting about NFC on the tablet.
Did anyone try rooting this device with the rooting tool of Asus Zenfone 5? I think I may work. Currently I don't have this device. I will buy it the next 2 days.
I tried the asus zefone 5 root apk but it says that is only for zenfone....
Root) http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
http://www.asuszenfoneblog.com/2014/10/download-rootzenfone-1464r-apk.html
Thanks a lot it works great
How does this work? Just download and install the apk?
Hello scritchs,
Good to hear it worked for you.
Wondering if it will also work for me...
You just downloaded the RootZenFone 1.4.6.6r, installed the apk and it is rooted now?
I like to know if ours ME572C have the same specs:
Modelnumber K007
Buildnr KVT49L.WW etc
Android 4.4.2
thanks
thanks a lot
I try it~
woff said:
thanks a lot
I try it~
Click to expand...
Click to collapse
Yes i get the apk and its automatic the tab reboot and the root is on.....
This tab is great.... nothing to say
---------- Post added at 09:25 AM ---------- Previous post was at 09:17 AM ----------
I get the apk from the first link 1.4.6.r.6 from asus webstorage all works fine. Thanks again
How about a custom rom to remove the asus bloatware and return to the pure stock android?
Related
Hello everyone!
I have a galaxy s i9000b with 8gb.
was using the Christian rom a gingerbread 2.3.3.
of a sudden he started to restart on lopping and ended up entering the system after some time. until it stopped booting the system permanently.
this is a recurring problem found much information on google about it!
solves the problem most easily by using the stock rom tim.
in my case.
after much research I learned to use the adb basically and was following a tutorial
parted on then it should go to the directory / dev / block and find mmcblk0.
but he was not there!
I tried to copy the etc / fstab file to a folder on your pc so I can read and see if mmcblk0 was listed there.
I used the command:
C: \ android-sdk-windows \ platform-tools> adb push / etc / fstab c :/
and I returned this:
can not stat '/ etc / fstab': No such file or directory
though I see him there in the adb shell browsing the folder / etc
finally began to get discouraged with the problem and for not having found the mmcblk0 there in / dev / block.
I'm beginning to think that with the 8GB internal memory of my beloved GS I9000B actually damaged.
Can someone help me confirm this or help me somehow?
just pointing out that the system does not start, but I have access to recovery mode and download
I'm using the recovery is the CMW RECOVERY v2.5.1.0 SPEEDMOD ULFK
to have access to the cell by adb!
sorry for bad english!
re:
Very sorry to hear this . You can try to find some solutions in this thread:
http://forum.xda-developers.com/showthread.php?t=845708
There are some more topics here on xda, try anything, before a year, i had one i9000 int dead, and there is no solution , hope your problem can be solved.
At the end if nothing helps, now we have some sort of fix, and this can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=973687&page=3
look at Catanni post, this must work if anything else fail. This is vold file needed for this.
Good luck.
hey! tanks man!
thanks for the reply! I'll read all these topics and then I see that fstab!
then write here what happened!
Thank you so!
bispoom said:
I tried to copy the etc / fstab file to a folder on your pc so I can read and see if mmcblk0 was listed there.
I used the command:
C: \ android-sdk-windows \ platform-tools> adb push / etc / fstab c :/
and I returned this:
can not stat '/ etc / fstab': No such file or directory
Click to expand...
Click to collapse
your command that you used above is incorrect.
To transfer from phone to computer use "pull"
To transfer from computer to phone use "push"
re: read this please
It is very important, before u start flashing and work with abd, to do backup your /efs folder if u dont have already. If your phone really have dead internal sd then is almost impossible to recover your imei if /efs folder become corrupted. This is covered by this thread:
http://forum.xda-developers.com/showthread.php?t=859914
After that you can try to flash some older firmwares, try with repartition, try to manually set up partitions, and u have full procedure in first link on my previous post.
You can try this command from adb:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
this command will mount your internal sd in windows, and then u can try to partition in windows
In second link, is procedure how to change internal and external sd, this is last that u can try (that mean that your internal sd is really dead). Attached fold.fstab will make your external sd to work like internal (this is not tested by myself, but a lot of people have succsess with this).
Bye and good luck, and please tell us how progress work.
hi!
result of command:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
is here
cannot create /sys/devices/platform/s3c-usbgadget/gadget/lun1/file: directory no
nexistent
to access the folder dev / block there is no a mmcblk0
and not one or the other as mmcblk0p1 or p2
and inside the folder / sys/devices/platform/s3c-usbgadget/gadget / folder does not exist lun1 / ...
sorry for bad English, and tanks for the help
re:
If mmcblk do not exist, best u can do is to try to flash with repartition in odin. If this does not help, always can try this
http://forum.xda-developers.com/show...=973687&page=3
Wish u best
broken link
hi!
man tanks for the help but this link
http://forum.xda-developers.com/show...=973687&page=3
is broken!!!
hi guys i am looking here for thread that will give tutorial on how are we going to back up the said EFS which is the very important file of the phone where IMEI resides, suddenly after searching for so many days still haven't found an answer. I already tried using EFS Pro 1.9.2 and it prompts that the said directory isn't there.. i checked it out on the root of my phone and found that EFS folder isn't there.. now my question is there any apps or tool that will backup our efs so that if incase we accidentally mess with our phone, it will be easy for us to revert back to the time when the phone is functioning well..
The EFS Partition is "stl5" .
So , for mounting the partition at boot , You need to unpack your boot.img, Open init.rc and add the following lines:
mkdir /efs
mount /dev/block/stl5 /efs
Click to expand...
Click to collapse
Then You have to repack the boot.img
----------------------------------------------------------------------------------------
We are done with the mounting part. |
----------------------------------------------------------------------------------------
Now , Flash the boot.img
Reboot Your phone
Connect it to your PC (Note : ADB must be enabled)
Run adb pull /efs command
................................
There might be a way using the "*#7284#" code . It creates a service com port on PC. (Stock Roms Only)
dev0xteam said:
The EFS Partition is "stl5" .
So , for mounting the partition at boot , You need to unpack your boot.img, Open init.rc and add the following lines:
Then You have to repack the boot.img
----------------------------------------------------------------------------------------
We are done with the mounting part. |
----------------------------------------------------------------------------------------
Now , Flash the boot.img
Reboot Your phone
Connect it to your PC (Note : ADB must be enabled)
Run adb pull /efs command
................................
There might be a way using the "*#7284#" code . It creates a service com port on PC. (Stock Roms Only)
Click to expand...
Click to collapse
hitted thanks...
this is a nice tutorial, but it will be very best if u can provide the complete step by step on how am i going to do this, and where to input the said line..sori for asking too much..just a noob one..hehe dont know much bout adb shell and commads not an advance user too..hehe
mizukage said:
hitted thanks...
this is a nice tutorial, but it will be very best if u can provide the complete step by step on how am i going to do this, and where to input the said line..sori for asking too much..just a noob one..hehe dont know much bout adb shell and commads not an advance user too..hehe
Click to expand...
Click to collapse
DON'T MOUNT EFS PARTITION!
You will most likely brick your phone.
Sent from my GT-S5830 using Tapatalk 2
(Frank) said:
DON'T MOUNT EFS PARTITION!
You will most likely brick your phone.
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
do u have any better idea on how are we going to save our efs partition so that we can revert back if we messed with our phone?flashing is risky especially for noobs..
hi everyone, i've a totally noobish and technologically dumb question, you know there are partitions in android like /system and /sdcard etc etc, now my question is that is the /system partition write protected on an unrooted phone? can /system files be modified on an unrooted phone? i have an unrooted phone and i can view the system partition via a file manager but i dont know if i can modify it or not. Does rooting the phone remove the write protection? plus, i have s off, can having s off disable the write protection, if there is any on the android /system partition? thanks in advance
muhammad.uzi1994 said:
hi everyone, i've a totally noobish and technologically dumb question, you know there are partitions in android like /system and /sdcard etc etc, now my question is that is the /system partition write protected on an unrooted phone? can /system files be modified on an unrooted phone? i have an unrooted phone and i can view the system partition via a file manager but i dont know if i can modify it or not. Does rooting the phone remove the write protection? plus, i have s off, can having s off disable the write protection, if there is any on the android /system partition? thanks in advance
Click to expand...
Click to collapse
pretty much NO, to all your questions.
what you need to be able to modify /system
1- a kernel with write-protection disabled
2- root access with /system mounted as read/write, you can achieve this in more than one way, two possible methods:
A) don't want to root the ROM?: flash a custom recovery, and use adb shell commands, a recovery file manager (TWRP has one), or Aroma File Manager
or
B) root the ROM
nkk71 said:
pretty much NO, to all your questions.
what you need to be able to modify /system
1- a kernel with write-protection disabled
2- root access with /system mounted as read/write, you can achieve this in more than one way, two possible methods:
A) don't want to root the ROM?: flash a custom recovery, and use adb shell commands, a recovery file manager (TWRP has one), or Aroma File Manager
or
B) root the ROM
Click to expand...
Click to collapse
once again, you summed it up really good, i understand the write protection thing now, so basically it depends on kernel and root access/custom recovery file manager
muhammad.uzi1994 said:
once again, you summed it up really good, i understand the write protection thing now, so basically it depends on kernel and root access/custom recovery file manager
Click to expand...
Click to collapse
yes stock kernel has write-protection enabled, so any changes you do with ROOT, will be gone as soon as you reboot.
nkk71 said:
yes stock kernel has write-protection enabled, so any changes you do with ROOT, will be gone as soon as you reboot.
Click to expand...
Click to collapse
i have stock kernel and i'm unrooted, i guess i cant make changes in /system at all. Well, everyday i learn something new about Android, i'll mark this thread as solved
nkk71 said:
.............
Click to expand...
Click to collapse
You seem to know much about android
1) Can tell me why a message is displayed on top every time I reboot or poweron (on the logo screen) "write protection : kernel".
2) Is it an indication that I have unlocked by bootloader ? While rebooting it stays on that screen for 60-65 sec since I did rooted with Magisk (usually takes 7 secs before doing with Magisk-[message wasnt there at that time] )
3) What does it mean ? It came after I rooted with Magisk....
4) Does it mean I wont be able to go back to stock in the future using odin.
Im using SM-G503FZ. (5.0.2), Grand Prime
---------- Post added at 04:10 PM ---------- Previous post was at 03:12 PM ----------
nkk71 said:
yes stock kernel has write-protection enabled, so any changes you do with ROOT, will be gone as soon as you reboot.
Click to expand...
Click to collapse
Please reply to my above post.
mdmaher said:
Im using SM-G503FZ. (5.0.2), Grand Prime
Click to expand...
Click to collapse
You should ask in your device forum, this is HTC One M7 forum.
Need assistance
I unlocked my asus zenfone max pro m1 , when restarted its stuck in boot logo so I tried to flash a recovery and also a custom rom but it says write protected. I erased system in fastboot mode but unable to do anything other than entering into fastboot mode. can anyone help me to bypass write protection and flash a new rom or recovery to get my phone back in to the working state. Any help would be appreciated. Thank you guys...
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
fran1563 said:
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Click to expand...
Click to collapse
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
fran1563 said:
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Click to expand...
Click to collapse
Just say what you do not understand, I can explain
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
Mis012 said:
Just say what you do not understand, I can explain
Click to expand...
Click to collapse
Thank you mate, I'm going to try. I'll write you wherever going to happens. I aprecciate!
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
christelle868 said:
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
Click to expand...
Click to collapse
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Mis012 said:
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Click to expand...
Click to collapse
i think he got lost on your tutorial XD
fastboot starting
Please, Please advice ..
And I'm one of those tablets which displays a message starting fastboot 1,2,3. I tried almost everything. Well at least I think that everything is okay or if vv. Please advice how to try it changed. Thank you in advance for answers
Hi. I've an unbranded chinese Headunit . With a rockchip px3 and i want to root it . i've folllow step . but now i've an issue . i need to instal supersu trought the recovery but the head unit dont have volume button . i've been able to reboot recovery trought window adb but no command window . only a dead Android with an exclamation .
Is there any body who has aldrealy root a px3 ?
Thx
How did you get Root? I have a chinese Headunit with px3 too.
Thx
Yes ! I've instal kingroot . and it did some magic
Another way is to get an update.img and root the image. That's what I did for pumpkin audio's Lollipop unit
uudruid74 said:
Another way is to get an update.img and root the image. That's what I did for pumpkin audio's Lollipop unit
Click to expand...
Click to collapse
Can you please explain in details how to get an update.img and root the image
Thanks
The images are on the pumpkin forums and in my case, I had a bunch of problems for which they kept saying "download this update and flash it and see if it works" ... and it didn't. So, I looked at it myself.
The images are in a format that is specific to Rockchip. You'll likely need a Linux box and some decent skill to manipulate the images. You unpack the image with 'imgrepackerrk' available on XDA. It makes a folder called update.IMG.dump and inside is things like update-script (I comment out the part that flashes recovery! I'm scared) and a folder called Image. Inside that are your partition images, including system.img!
You can just make a folder and mount that image to it. Then grab a copy of SuperSU and open it. You'll see it runs a shell script to manipulate the /system folder. I manually performed the commands at the Linux command line. However, you MUST know shell scripting. This isn't a simple file. Expect to screw it up a dozen times before you get all the permissions just right.
When done, unmount your image from the folder, repack using the same tool that packed it and stick it on a USB flash drive and take it out to the car. Do the magic dance to get to the recovery, and flash it.
Do not attempt if you can't get to recovery and make sure you comment out the part that flashes recovery since you don't EVER want to lose that recovery. It's your only way into the system if you mess up!
If you have the exact same model as me I can stick mine up somewhere, although its tricky to get the Settings changes working since I haven't re-signed the system apps ... basically, you load with the stock Settings app and then use root to copy my version in place. My version gives a 12 and 24 hr standby time options. Once copied, its good.
Sent from my ONEPLUS A3000 using Tapatalk