From a developer: http://xdaforums.com/showpost.php?p=35429627&postcount=2
It is still binary problem...
Asus MeMO 7 (me176cx)
- Thread starter shawnsac2000
- Start date
From a developer: http://xdaforums.com/showpost.php?p=35429627&postcount=2
It is still binary problem...
i forgot the meta inf folder i downloaded had a arm updater binary ... ill retry again with .36 updater binary if doesnt work ill try with original .182
I found an easy way to install xposed/update
1= install xposed framework from the link below
2= open it
3= set the package to x86 and reboot to recovery (permanent or temp)
4= on recovery, flash the package located somewhere on a folder with the name xposed in internal storage
5= reboot and done
This xposed is easier to select package and install them and it has material design
Link: https://github.com/DVDAndroid/dvdan...ks/XposedInstaller_by_dvdandroid.apk?raw=true
Thread: http://xdaforums.com/xposed/material-design-xposed-installer-t3137758
1= install xposed framework from the link below
2= open it
3= set the package to x86 and reboot to recovery (permanent or temp)
4= on recovery, flash the package located somewhere on a folder with the name xposed in internal storage
5= reboot and done
This xposed is easier to select package and install them and it has material design
Link: https://github.com/DVDAndroid/dvdan...ks/XposedInstaller_by_dvdandroid.apk?raw=true
Thread: http://xdaforums.com/xposed/material-design-xposed-installer-t3137758
I called it an "unlock" in that post to avoid confusion, since it functions exactly like an unlocked bootloader.
Most people trying to unlock this tablet wouldn't look up "replace with insecure bootloader", they'd look up "unlock bootloader"
its still hard cuz it only shows unlock petitions and not the thread you made... and also i wonder why droidboot still says secure boot is on
Last edited:
D
Deleted member 5764078
Guest
I got some backups - 3 to be exact, .33 rooted with no xposed, .33 rooted with xposed, and .36 with xposed. Would you like me to upload? But you have to tell me where are the databases stored and app data and everything, I kinda don't want everyone to have "my tablet", just the system
I found a lite & clean version of .36 FW without Asus bloatware at 4pda.ru, it does keep custom bootloader and recovery
https://cloud.mail.ru/public/EfuY/81Nk2HGTB
Credits goes to nfs911 from 4pda.ru
https://cloud.mail.ru/public/EfuY/81Nk2HGTB
Credits goes to nfs911 from 4pda.ru
Last edited:
One way could be restoring a kk system and boot lmage backup. I don't know if kk will work with uefi....
I got some backups - 3 to be exact, .33 rooted with no xposed, .33 rooted with xposed, and .36 with xposed. Would you like me to upload? But you have to tell me where are the databases stored and app data and everything, I kinda don't want everyone to have "my tablet", just the system
just backup system partition
---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------
the problem is the boot.img sdc said it was problably going to need to be changed because the kk boot.img runs on 32bit and this device is now on 64.bit, im gonna try to do that cuz i already know how to unpack/repack kernel
---------- Post added at 02:56 PM ---------- Previous post was at 02:51 PM ----------
[/COLOR]
I can't see why it would help, the problem is most likely caused by some change between commands used in binary between kitkat and lollipop.
EDIT: maybe, just try it
But I still don't see why you cannot just flash the partitions over with twrp (either using that zip/img switch or with dd while nothing mounted) and see what happens? Theoreticaly
If that damn RAM was bigger (it's 1024MB according to Aptio Setup Utility) I could just make a ramdisk with /system already inside, but unless you have a good Idea how to make the system really small.. I may try to let it mount system from sdcard ober weekend, with twrp I have a fast starting system with all I need to get the rid of errors (I doubt thre will be any, just stuck forever in grub at "booting xy" or bootanim, the second may be too nice to happen)
i tried flashing boot.img of kk it didnt boot
There are too many parameters. Uefi should support both 32 and 64 bit. Boot image as well should be compatible with uefi and should support both 32 and 64 bit roms. Afterwards Rom should be compatible with the kernel and uefi.
Developing aosp sounds easier...
I'm downloading that lightweight firmware now. Hopefully it's a change for the better.
EDIT: Downloaded, making a backup then installing now. If this works it'll be my main until CyanogenMod or AOSP is ported.
EDIT 2: ...bootloop. Yay. I'm reflashing the file, and this time not rooting it.
EDIT: Downloaded, making a backup then installing now. If this works it'll be my main until CyanogenMod or AOSP is ported.
EDIT 2: ...bootloop. Yay. I'm reflashing the file, and this time not rooting it.
Last edited:
There are too many parameters. Uefi should support both 32 and 64 bit. Boot image as well should be compatible with uefi and should support both 32 and 64 bit roms. Afterwards Rom should be compatible with the kernel and uefi.
Developing aosp sounds easier...
ive actually seen a kitkat backup somewhere on this thread would it work?
I THINK I got that lightweight ZenUI build to work.
The problem was that in the updater-script /system wasn't being wiped so I did it myself. Looks like it worked- the zip took significantly longer to install this time around, the boot animation is different, and the other times I had tried flashing this lightweight build it's just been the ASUS animation. It actually took so long I adb shell'd in during the installation and made sure /system was actually getting populated
It'll take a while to boot since one of the things I tried was a factory reset. Hopefully I'll report back with good news.
The problem was that in the updater-script /system wasn't being wiped so I did it myself. Looks like it worked- the zip took significantly longer to install this time around, the boot animation is different, and the other times I had tried flashing this lightweight build it's just been the ASUS animation. It actually took so long I adb shell'd in during the installation and made sure /system was actually getting populated
It'll take a while to boot since one of the things I tried was a factory reset. Hopefully I'll report back with good news.
LIGHT VERSION OF .36
DO NOT UPDATE FROM .33 - YOUR CAMERA AND BLUETOOTH WILL NOT WORK. Update only from stock .36. Flashes via TWRP
Download
Instruction:
Included apps:
Addons:
Last edited:
i didnt said it didnt needed either.. im only talking about restoring system partition and then flashing the edited boot.img
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10me176c
its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
2. turn on usb debuging
3. download ww rom and rename it update.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. open ADB and type line by line:
adb remount
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
after this your device will reboot to recovery and automaticly instal ww rom.9
I originally wrote an script/update.zip that is ran through the tethered twrp that generates an emergency PFT (Phone Flash Tool) package, then installed the .efi bootloader into the esp partition, and then would generate a twrp recovery from the devices stock recovery and then flash the generated twrp.img.
unfortunately some devices / some versions of the tethered recovery concept didn't like the scripting and would error on md5 checking so i scrapped that and am working on making it into an actual app that will also check if a device meets the requirements of the insecure bootloader to try to make it as safe as possible for unconfirmed devices.
if you want i can send you a update-binary script that will do the flashing of the images through the tethered recovery instead of having to manually dd the images. i would like to eliminate and chance of bricking a device.99@jerbear294 I think hope to and really hoping to have something to test by the end of the weekend latest.
After tonights build I should have a better idea.8
