yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] Mis012:
I've alraedy heard that fastboot boot XY doesn't work anymore :/ Otherwise you would be in droidboot and than twrp already :/ if you feel adbenturous and don't have a OTG Y cable lying around, you can compile a grub2 efi binary with embedded config and embedded kernel with initrd. Not sure if it's even possible though. The weird part would be getting initrd and kernel into binary and adressing it there. If you don't mind deletinh your data, serial number, MAC adress etc., I think you can just repartition.

---------- Post added at 10:24 PM ---------- Previous post was at 10:18 PM ----------

You seem to use "osloader" instead of the file name. P.S the insecure bootloader is verbose a bit, I recommend trying it again. You want the bootx64.efi file (use it instead of efilinux.efi)

If you have an Y OTG You can be the second person to boot grub on this, and the second person to boot recovery with it. And although I've alteady got it I would rather find a solution with no need for it.
[MeMO Pad 7 General] atomix85:
not sorry to delete all please tell me how should I do? what mind is to throw the tablet ... I have the cable otg ...

Edit: Now I try again .... y otg? mmmm ...

Inviato dal mio thl 5000 utilizzando Tapatalk
[MeMO Pad 7 General] daspex:
@thegreatn_

Hi,

i did what you told me via PM and that´s what i have

Finding update package...

Opening update package...

Verifying update package...

Installing update...

E:Error in /tmp/update.zip

(Status0)

E: fota_return_code 409

Installation aborted.

any suggestions?

thank´s in advance

---------- Post added at 22:59 ---------- Previous post was at 22:47 ----------

Hi,

could someone be so kindly to post a screenshot of the lp bootloader becouse i think it´s changed during the backup.if it is so,i could install a nandroid maybe from jerbear to get this thing running the LP.

thanks
[MeMO Pad 7 General] :
You can't update if you rooted, I suggest going way back to stock 193 or something kitkat and manually flashing everything, it might fix your camera and bluetooth too.
[MeMO Pad 7 General] atomix85:
hi

unfortunately stalemate even with BOOTX64.EFI same story droidboot image does not start nothing, I guess you just have to try the cable otg y (powered, right?)

can you please explain to me what you want to do with cable otg, to restore the tablet, before I throw it from the balcony :):laugh::eek::eek:
[MeMO Pad 7 General] intNERD:
Love my new battery life with the lite ROM

Gesendet von meinem K013 mit Tapatalk
[MeMO Pad 7 General] daspex:
[MENTION=7293167]thegreatn_[/MENTION]

Hi,

nothing works at all....attached twrp.log
[MeMO Pad 7 General] :
sir please, you can make it over 8 hours screen on time.
[MeMO Pad 7 General] Mis012:
First, connect power to the Y cable, connect a hub and connect it to the tablet.

You need to make an EFI bootable thumb drive with grub2, and connect it to the tablet along with USB keyboard. While powering on the tablet, repeatedly press F2 to get into UEFI (it's not BIOS). There, navigate to the rightmost screen and use boot override with your thumb drive. If it was set up correctly, it should boot you intu grub. Press "c" on keyboard and type 'ls (hd0,1)/'

It should give you list of files on the first partition of you thumbdrive. Now you can power off the tablet (disconnect everything first) and press and immediately relase the power button to let it actually turn off.

Now disassemble the twrp .img and copy the vmlinuz and initrd.gz to the partition of your thumb drive you listed in grub previously. Now again boot to grub, press "c" and type

---

vmlinuz (hd0,1)/vmlinuz

initrd (hd0,2)/initrd.gz

boot

---

And you should boot into recovery ;)
[MeMO Pad 7 General] Ruben Craveiro:
I found a kitkat cwm backup, is it possible to add the right drivers to kk boot.img and maybe boot?
[MeMO Pad 7 General] atomix85:
Try and reTry

Hello,

I did well to get a powered hub (attached), you think you can go well?

However, I can not do as you say, as soon as I press the keyboard power in the tablet is not activated, my tablet's display turns on and turns off the backlight after a second. Maybe I should disassemble it and charge the battery before? if only I could ...:highfive:
[MeMO Pad 7 General] atomix85:
then? What do you recommend to do?
[MeMO Pad 7 General] Ruben Craveiro:
hmm what im trying to do has nothing to do with your problem.
[MeMO Pad 7 General] atomix85:
okok :angel::p
[MeMO Pad 7 General] Mis012:
Your problem is powered hub is not otg Y cable :/

You could disassemble it and connect +5 and GND of power to the +5 and GND of usb going into tablet, instead of how it's now.

Or buy real Y otg ($1 from ebay)
[MeMO Pad 7 General] atomix85:
OK I can do it ...

Inviato dal mio thl 5000 utilizzando Tapatalk
[MeMO Pad 7 General] Mis012:
It's actually a wire instead of resistor I think, this is for enabling charging (not tested on this tablet, probably won't work)
[MeMO Pad 7 General] social-design-concepts:
U need a custom kernel for OTG + Charging to work,
[MeMO Pad 7 General] atomix85:
hello, I made a otg- Y cable from a otg classic that I had at home attached photos :)

the problem is that it does not change anything ..... The tablet is as if he could not leave ... except that I was wrong to take the cable ... but I do not think, I watched a video on the tube with the whole process to step passage . at this point I do not know what to think ....:confused::confused:

good :D how do I load it into my tablet :D;)
[MeMO Pad 7 General] Mis012:
First make sure it's turned of, then turn on while pressing F2 on keyboard. What exactly happens then?
[MeMO Pad 7 General] atomix85:
hi,

just touch the power button flashes and the display goes out again, this is what happens, it seems that the keyboard does not power arrivals ... while the mouse turns on its optical small light, it seems that as soon as I press power does not start anything, but what You will ever be? I thought, there is a physical way in the motherboard to report the efi options to the factory settings ?? is not nothing else I can think of !!
[MeMO Pad 7 General] social-design-concepts:
it depends on the devices default settings, most baytrail tablets use the main battery to provide cmos power, on my lenovo i had to disconnect the battery press and hold power to completely discharge the unit and then reconnect the battery and my cmos would reset to defaults.
[MeMO Pad 7 General] atomix85:
ok I just did dismounted, removed the battery, I held down power for about twenty seconds, I hung up the battery, but unfortunately nothing has changed, it is as if you did not want to start :rolleyes::eek:
[MeMO Pad 7 General] Mis012:
OK, try the DNX thing again, and spam F2 everytime it seems it may be rebooting.

If it doesn't work, you may try using grub efi binary as osloader (and eventually pass some random.img thing). I recommend downloading this http://murga-linux.com/puppy/viewtopic.php?p=818727#818727 and using refindx64 or something found there (it's actually renamed grub, look at the readme file to be sure).
[MeMO Pad 7 General] atomix85:
Hello :cowboy:

the first method has not been successful .... :(

I downloaded refindx64'm ;) doing the tests but at the moment I have this error (attached) ... there are many .efi file, I'm trying them all see what happens, even if the file is important for me is grub2.efi (readme file) thank for all man ;):laugh::good::good:
[MeMO Pad 7 General] Ruben Craveiro:
Do you guys think that maybe hes doing something wrong with the powered otg hub? or maybe he simply doesnt have the ESP partition or UEFI isnt allowing him to go there. It has happend to me that i couldnt get into UEFI i had to reinstall ESP partition soi could open it (but it was working i just couldnt access it)
[MeMO Pad 7 General] Mis012:
[QRCODE][/QRCODE]

It seems his power sequence is bad :/
[MeMO Pad 7 General] Ruben Craveiro:
I need help, i have Kitkat System Partition in a cwm backup (i think its yours mis012), anyway i need to unpack kk boot.img but it doesnt work... ive tried several tools to unpack-repack boot.img and they dont work.. they only work to unpack the lollipop boot.img... does this boot.img need something special to be unpacked?

EDIT: I changed with a hex editor, the first line to say "ANDROID!", it was almost able to unpack but it didnt unpacked ramdisk, it says Compression Used: Empty and then Error, its only being able to unpack split_img

[IMG="Error Unpacking boot.img Kitkat"]https://fv3.failiem.lv/thumb_show.php?i=bffyjgm3&view[/IMG]
[MeMO Pad 7 General] Mis012:
You can use this (attachment) with terminal emulator on android.

./unpackbootimg

gives you help so you will know which arguments to supply.
[MeMO Pad 7 General] Mis012:
You can try renaming it to efilinux.efi

What happens if you connect charger?
[MeMO Pad 7 General] tim_h:
Problems updating to v36

Hi all,

I am one of those guys who updated from Lollipop v24 to v33 using the stock system image provided by [MENTION=5479482]jerbear294[/MENTION] in an earlier post. (The regular OTA to v33 failed because I had rooted.)

Now I thought, being back to complete stock, I could take the regular OTA from v33 to v36. Unfortunately, the OTA from v33 to v36 failed. So it seems something was still not fully stock.

Is there an easy way to update to stock v36 in this situation?

If it's complicated, I am not sure it's worth the effort, though. As far as I have heard the bad memory management and battery drain are still present in v36. First moment there is a CM ROM I am anyway going to kick the ASUS ROM.

Cheers,

Tim
[MeMO Pad 7 General] thegreatn_:
Hey, I would like to suggest you install insecure bootloader and permanent TWRP recovery. With help of this, you can install repacked version of .33 (for TWRP), update to .36 from it and install light version of .36, where battery life was improved. Links and instructions below.

How to install repacked rom:

1. Put your file into sdcard

2. Wipe System (only)

3. Install the package

4. Do factory reset

5. Reboot

Bootloader | Repacked .33 | Lite .36 | How to install lite .36
[MeMO Pad 7 General] tim_h:
Hi thegreatn_,

Thanks a lot for the info and the links! Just wondering: How can I update from the repacked v33 to v36 (before installing v36 lite)? Through OTA? Shouldn't work with permanent TWRP installed, right? Or do I go directly from repacked v33 to v36 lite? (I saw someone reporting camera and bluetooth not working when you install the v36 lite over a v33 installation.)

Cheers,

Tim
[MeMO Pad 7 General] thegreatn_:
You can download official rom file from ASUS website, and, after reboot, tablet will suggest you to update himself. I don't know works OTA with permanent TWRP or not, sorry.

Yes, bluetooth and camera doesn't working if you update from .33 to .36
[MeMO Pad 7 General] tim_h:
Thanks for replying! I still have some questions, though ... sorry. ;)

In principle my tab is still on v24, except that I installed the v33 nandroid system image of [MENTION=5479482]jerbear294[/MENTION]. Is there a stock v24 system image around anywhere? If I had that, I could go back to complete stock v24 and then take the regular OTAs to v33 and v36 from there, I guess.

If not, how do I install the official Asus ROM images? I could go back to my modified v24 (before installing the v33 system image) and then use the official ASUS v33 ROM, I guess? Or will it not work because my v24 system image is modified. Once I have installed that, I can take the OTA to v36 and then install the v36 lite.

And one more question: What is special in the repacked v33? How is it modified from stock?
[MeMO Pad 7 General] thegreatn_:
Are you looking for a zip-file of stock .24? You can find all official roms here

About repacked .33, it's a clean stock, but it installs via TWRP. Nothing else
[MeMO Pad 7 General] tim_h:
Hi again,

Ok, great! So I guess it should work to install the repacked v33 via temp TWRP and then OTA to v36 from there. I'll try that. If it works, afterwards I will go for the v36 lite.

Thanks also for the links to the official firmware ZIPs. Can those be installed via TWRP? And what's the difference between the files named -user.zip and _KK-user.zip?

Cheers,

Tim
[MeMO Pad 7 General] thegreatn_:
Yes, through temp TWRP it works, I know.

No, via TWRP we can only install repacked rom. We have repacked .17, .24, .33 and .36 (do you need a link?). The difference is in install, -user for Lollipop, _KK-user - for Kit Kat.

---------- Post added at 05:19 PM ---------- Previous post was at 04:45 PM ----------

Some addons for lite .36

Flashes via TWRP

Contacts fix:

Download

Can be installed on current system without reinstalling

Fixes operability of contacts (who uses it on the tablet? xD)

Contacts app must be installed separately, link

New apps remover:

Download

Can be installed on current system without reinstalling

Deleted: My Tracks, My Maps, Google Keep. Google Translate not touched

Integrator of updates for system apps:

ONLY FOR LITE .36!

Download

This app allows you integrate updates of system apps to system (for 8gb version might be helpful). It frees some space.

Requirements:

Root

BusyBox (installed by default)

.NET Framework 4.5

Win7+

Installed ADB drivers

Enabled USB Debugging

Instruction:

Connect the tablet via USB

Launch K013_LP_FW_LITE_UPDATE_TOOL.exe

Press "Scan"

Press Apply

Wait for value 0 in "Updates"

Reboot
[MeMO Pad 7 General] dareas:
Hey guys!

Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?

Also does updating to LP enables 64bit capability on the Z3745?
[MeMO Pad 7 General] thegreatn_:
Hello, about 64bit capatibility I don't know. About LP, you must try lite version of .36 from this post. It's more quickly than stock and battery life aslo improved.
[MeMO Pad 7 General] dareas:
[/COLOR]

Well thanks, but I prefer to download the zip from the Asus website and debloat the rom myself.
[MeMO Pad 7 General] thegreatn_:
Your welcome.
[MeMO Pad 7 General] tim_h:
It would be great if you could also provide links to repacked v24 and v36, too. Thanks!
[MeMO Pad 7 General] thegreatn_:
Ok, v24 and v36. Repacked .36 also can be used to return stock rom from lite .36
[MeMO Pad 7 General] Ruben Craveiro:
it doesnt work, i really need to unpack this boot.img.... this boot.img has so many weird stuff... all unpack-reapck tools cant find zlimage and all that stuff, at least i fixed the error about not having magic word
[MeMO Pad 7 General] Mis012:
Are you sure it's not corrupted? For example Zarchiver removes beginning of every file extracted from iso. The !ANDROID should be somewhere near start of the file already, it doesn't need to be on top. Also if you look at the file as plain text (predarably with hex editor) you should see also the plain text header, which is used to extract everything. So I really think it's corrupted.
[MeMO Pad 7 General] Ruben Craveiro:
I know how to edit the boot.img header... Without any changes, the boot.img starts with magic word $OS$, i changed it with a HEX Editor to ANDROID! and after doing that i pasted onto the computer and tried to unpack, didnt work, tried another tool didnt work either, and then i tried another bunch of tools and they all didnt work, they only work on the lollipop boot.img
[MeMO Pad 7 General] social-design-concepts:
There are several tools available for unpacking the osip formated boot.img
[MeMO Pad 7 General] Ruben Craveiro:
links? thanks..
[MeMO Pad 7 General] social-design-concepts:
https://github.com/social-design-concepts/xFSTK-ImageTools

https://github.com/social-design-concepts/xbootimg_intel

https://www.androidfilehost.com/?fid=95864024717073970

https://www.androidfilehost.com/?fid=95864024717071926

haven't tested :

https://github.com/shakalaca/ZenFone2-boot-tools

https://github.com/shakalaca/ZenFone-boot-tools

haven't tested maybe for packing only :

https://github.com/venue3x40-dev/android_device_dell_venue3x40-common/tree/twrp/mkosimage
[MeMO Pad 7 General] Ruben Craveiro:
please tell me you still havent updater to lp, please make a nandroid backup on twrp of System partition and upload it somewhere please. thanks
[MeMO Pad 7 General] intNERD:
Any new update about custom roms?

Gesendet von meinem K013 mit Tapatalk
[MeMO Pad 7 General] dareas:
I still haven't updated to LP. Still on KK .201.

I'd make a nandroid tomorrow morning. May I ask why you need it? Is it possible to downgrade from LP to KK with a nandroid?
[MeMO Pad 7 General] Ruben Craveiro:
it might be if i edit the kitkat boot.img with the updated modules (drivers). but in order to see if it works i need a nandroid

---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------

andimgtool file how do i repack? i could only unpack by dropping boot.img into andimgtool.exe
[MeMO Pad 7 General] Mis012:
You actually want to repack it as a normal boot.img, so you can use any classical tool.
[MeMO Pad 7 General] tim_h:
Ok, little update: I had serious problems with the repacked firmware zips. I first installed the repacked v24 using temp TWRP, did a factory reset, then tried to reboot system, but the tablet would not boot up (it remained on the boot screen for a very long time and then I gave up). I retried several times, from various states restored from nandroid backups. During the later tries of installing the repacked v24 actually TWRP recovery crashed reproducibly and the tablet rebooted spontaneously. I also tried the repacked v33 and had recovery crashes as well. Strange.

I then went on to restore my v24 nandroid backup (with root, so modified system image) and install the original ASUS v33 ZIP by placing it in the root of internal storage and waiting for the install message after bootup. The ASUS v33 zip installed just fine, in spite of modifications to the sytem image. I then tried to get an OTA to v36, but it would not show up. I did a factory reset, but the v36 OTA did still not show up. Strange, at that point everything should have been completely stock v33, why does it not offer the v36 OTA? (Does ASUS check on the server side if a certain device had already tried an unsuccessful OTA and then does not offer it again?) So I moved on and installed the original ASUS v36 ZIP. That worked fine again. And from there I now moved on to install the v36 lite. I hope this will finally make the tablet more usable. Still hoping someone comes up with a CM12.1 build, though. :)

One more update: So, I have the lite v36 up and running. So far it looks very snappy. I hope the battery life in standby is also good. Does the lite v36 have a known memory leak (as apparently the original ROM has)? If so, someone wrote that this can be fixed with xposed. Which xposed version would I need and how would I fix the memory leak? Cheers!
[MeMO Pad 7 General] :
Xposed with fix memory leak module, also, about the battery life , I get about 7-10 hours screen on time, 10 when I only browse the web, 7 when I watch movies or somrthing.
[MeMO Pad 7 General] tim_h:
So the memory leak definitely is there also on v36 lite?

Which version of xposed do I need? x86 is clear, but sdk 21, 22 or 23?
[MeMO Pad 7 General] thegreatn_:
Memory Leak is on all Android 5.0.x+ ROMs... sdk21
[MeMO Pad 7 General] :
xposed-v80-sdk21-x86
[MeMO Pad 7 General] dareas:
I uploaded System+system image TWRP backup here (MEGA) from .201 WW_KK firmware . I can upload System partition only backup (without System image), full nandroid or whatever you like. Please take in mind that I have my tablet rooted, many built-in apps are deleted and I also have Xposed installed. I also used temporary TWRP (if matters).
[MeMO Pad 7 General] tim_h:
Ah ok, so this one is on Google - not ASUS - for a change. ;) Installing xposed now, thanks!
[MeMO Pad 7 General] rodrengo:
I tried but the stock .36 didn't work either camera and the bluetooth...is there any complete image of the .36 rom with which one can i restore system, drivers, and internal memory?
[MeMO Pad 7 General] jerbear294:
The problem's a bootloader/firmware mismatch.

Which version of the ROM did you have before? You have to flash that version, and then work your way back up to .36 to restore camera and bluetooth.
[MeMO Pad 7 General] rodrengo:
Ok i had the .33, if i now install .33 repacked, it resolve?
[MeMO Pad 7 General] jerbear294:
Yeah, install .33 then .36.
[MeMO Pad 7 General] Ruben Craveiro:
i had the same problem... i only had to flash .36, and without leaving recovery i formated system, and reflashed lite, and restored data partition, and its working ..

---------- Post added at 11:24 PM ---------- Previous post was at 11:21 PM ----------

Ok, thanks, it wont really matter the apps as long as it works. Thanks Again :D
[MeMO Pad 7 General] Ruben Craveiro:
do you know what files need to be changed? i tried changing 182 bootimg but when i try to boot it, it gives an efilinux error saying about not being able to load boot partition or something... but when i try using 33 boot.img with 182 modules, it shows intel logo, then disapairs, shows again and boots to recovery? what do i need to change in .182 or maybe .33? to make it boot? and also, i cant seem to find the kernel of 182 boot.img only on .33
[MeMO Pad 7 General] social-design-concepts:
Upload and link both both kk and the lollipop boot.img
[MeMO Pad 7 General] rodrengo:
When i flashed repacked .33 the camera did work, then wipe system, install repacked .36, did a factory reset, and when reboot the camera, didn't worked again...

Was a problem with wipes?
[MeMO Pad 7 General] jerbear294:
Huh.

Sounds like the bootloader didn't update :L
[MeMO Pad 7 General] rodrengo:
Sorry, i don't understand. What do you mean with that? Can i find a solution for this problem?
[MeMO Pad 7 General] Ruben Craveiro:
Here it is: https://mega.nz/#!JBdHzICB its 182 and 33 boot.img

and also, the only tool that u gave me that worked, was AndImgTool, one of the others only extracted 2 files and they were weird, and the other just wrote a file called boot_ and nothing on it.
[MeMO Pad 7 General] jerbear294:
You could take the non-repacked .36 and try flashing that.
[MeMO Pad 7 General] tim_h:
Probably the system image was updated to v36, but the boot image was not. I suggest you take the official download from the ASUS webpage: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip

Put that into the root of internal memory and reboot the tablet. It should report that an update file was found. Open the notification and follow the install dialogue from there. That worked flawlessly for me.

Regardint v36 lite. It is very snappy and very well usable. However, battery life in standby is still bad. At first I had something like 1% per hour (WiFi off), so that would give you ~4 days in standby, which would be good. But after charging to 100% yesterday evening it greeted me with 50% battery this morning. So it will not even last a full day on standby. The kernel is the one eating the battery. Probably the CPU does not go to deep sleep. I had the same issues with the original ROMs. Too bad! :( So I can't wait for the CM build ...
[MeMO Pad 7 General] thebulletfromhell:
If you're expecting custom ROMs to have better deep sleep and battery, you're going to have a terrible time when it is released
[MeMO Pad 7 General] rodrengo:
i tried, but when i copy the firmware to the root directory, it stops, restarts and show me an error message:
[MeMO Pad 7 General] tim_h:
Why? I've seen it before (on various phones).

---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------

Hmmm, that's strange. You copied in the normal Android environment with some file manager? It reboots while copying?
[MeMO Pad 7 General] rodrengo:
Yes, i copied with root explorer and reboots while coping, at the middle of the process

if someone had a complete image with Russian rom .36, and i restore that image, works better?
[MeMO Pad 7 General] Ruben Craveiro:
the tablet "crashed" it happends a lot, random reboots are "crashes", sometimes when your playing, viewing a video, or even browsing..
[MeMO Pad 7 General] :
I didn't have one random crash since I used the russian .36, maybe its the device?