Related
Amon_RA/Koush,
Would it be possible for you to integrate PSFreedom into your recovery image as a selectable option?
So theoretically you can have all the recovery features with the option to run PSFreedom.
Anyone else please feel free to post your thoughts and comments.
Thanks
N0ble
n0ble said:
Amon_RA,
Would it be possible for you to integrate PSFreedom into your AmonRA recovery image as a selectable option?
So theoretically you can have all the recovery features with the option to run PSFreedom.
Anyone else please feel free to post your thoughts and comments.
Thanks
N0ble
Click to expand...
Click to collapse
I'm pretty much sure that's possible. Guess we should ask Koush too
Sent from my HTC Desire using XDA App
I'm waiting for this great feature too.
Sent from my HTC Desire
If someone could get this working it would be great.
I've never used USB mount in recovery. If this feature is lost its a worthy sacrifice.
as far as it looks like , he stoped the support for his recovery image ...
mercianary said:
If someone could get this working it would be great.
I've never used USB mount in recovery. If this feature is lost its a worthy sacrifice.
Click to expand...
Click to collapse
AFAIK, you also lose ADB
I would really like this too.
I can understand that we would lose ADB and USB mount when in recovery but it would be allot more convenient. I imagine it won't be too much further down the line until someone figures out a mod in the kernal of the ps3 itself to boot unsigned code, now we have the ability to dump and write it.
Sent from my HTC Desire using XDA App
You do loose ADB & Mass Storage in the recovery image, also a toggle between PSFreedom & ADB etc is not possible, as ADB... can not be built into a kernel module.
Fake-Flash will also not re-enable these features for you as it does not contain a kernel in itself.
It would be a nice feature, but after talking with AmonRa and exploring the possible routes to doing this, it simply is not possible as it is.
Later today or early tomorrow I will release a updated pack that does not have the OD 4.0.4 requirement, it will however still have AOSP as a requirement until HTC release kernel source.
Is a dual boot not possible? mount an img file as a virtual drive and boot from it?
can be a stripped down kernel with just psfreedom in it!!!
AmunRA already did this with his, you have to permanently flash it but it works.
neoKushan said:
AmunRA already did this with his, you have to permanently flash it but it works.
Click to expand...
Click to collapse
No, the question was for a recovery with a toggle, that's not possible.
Nice so it now seems that AmunRA and Klutsh have both made recovery images with ADB and USB working with a PSFreedom toggle.
Thats excellent work!
yyou guys are way too late google amon ra recovories google might just have a gift 4 you
turtleiscool said:
yyou guys are way too late google amon ra recovories google might just have a gift 4 you
Click to expand...
Click to collapse
Did you even bother to notice that this thread was month's old!!!
Rogue XM Touch Recovery v1.5.0-R1
(CWM-based Recovery v5.0.2.8)
For the Asus Transformer TF101
First off, thank you to...
Team Rogue
Koush
CyanogenMod Team
j-r0dd
Solarnz
Roach2010
All I did slap together all their hard work to make it work on the TF101.
Sources
Rogue Recovery
The source and more info for Rouge Recovery is available in the Xoom release thread from Team Rogue. I have not made any modifications to it to work with the TF101. You can find that thread here:
http://forum.xda-developers.com/showthread.php?t=1235170
The discussion of the touch release in that thread begins here:
http://forum.xda-developers.com/showthread.php?t=1235170&page=13#123
Recovery Kernel
I used the kernel from Roach2010's ClockworkMod Recovery 3.2.0.1 release here:
http://forum.xda-developers.com/showthread.php?t=1213723
Device Tree
Mostly based on AOKP's TF101 device tree, just picked out the parts needed to compile the recovery. Particularly BoardConfig.mk:
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly
Updates
[2012-05-25] 1.5.0-R1 (5028-based)
Updated to Rogue XM Recovery v1.5.0 which is touch-enabled with the same features as before. See the Xoom release thread for more information on Rogue Recovery:
http://forum.xda-developers.com/showthread.php?t=1235170
Can also finally use the boot to recovery option available in some ROMs thanks to the recovery boot loop fix from Roach2010 from here:
http://forum.xda-developers.com/showthread.php?t=1213723
Workaround for small menu targets
http://forum.xda-developers.com/showpost.php?p=26142147&postcount=151
If I can figure out a way to just make the menu items taller, I'll make an update. Otherwise I'm waiting for Rogue to implement it first.
[2012-01-14] 1.3.0-R1 (5027-based)
Original release, non-touch
Info
Mounting as USB storage does not work. (Accessing the tablet or SD card from your computer when plugged in via USB)
Installation
I tested this the best I could, but use at your own risk. I am not liable for data loss, spontaneous combustion, temporal anomalies, or anything in between.
Just flash the attached zip from CWM.
There's also an nvflash version that has the recovery.img in it and will only flash the recovery if you prefer that method. Or just so you don't have to unpack the blob file if you need the recovery.img.
Misc:
I did this because I thought it'd be nice to have a newer recovery for our TF101s, but also because I want to learn to do some sort of development even if it's just building for similar devices. I'm still new to using anything like git or using C/Java like this so don't expect miracles right away if bugs come up! I have some experience with other languages, but not in this kind of application.
Thank you, looks nice. Doing a nand backup right now with it.
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
baseballfanz said:
Thank you, looks nice. Doing a nand backup right now with it.
Click to expand...
Click to collapse
Awesome!
will8578 said:
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I saw that post! I've been watching that thread and trying it out when there's an update.
80slovechild said:
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
To do that, you have to extract the zip and then unpack the blob file... but I updated the OP with an extra nvflash version that flashes just the recovery and gives you the recovery.img.
Finally...a relatively current back up for the TF!!
THANK YOU!!
Backing up with 3201, then installing this.
Beautiful work!! Works flawlessly!
Finally! A 5.x.x.x CWM recovery
Does this allow flashing from both internal and external?
On my Galaxy Nexus, they also have a touch softkey mod that has softkeys for up, down, back, and select. Not a big deal but something cool to look into if you get bored.
LTE EX Galaxy Nexus - CM9 AOKP
Asus Transformer - Revolver
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
luna_c666 said:
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
Click to expand...
Click to collapse
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Worked for me. Way way way better color scheme and it booted quick! Thanks!
wackydroid said:
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Click to expand...
Click to collapse
its definitely not the same as v3.x.... that being said however, simply look at the android_bootable_recovery github to see the differences since v3.x
I think with the latest versions its even possible to use the mount usb with the tablets own MicroSD card where-as in the v3.x tree it wasnt (thanks to v5.x's inclusion of dual mount support, specifically done to support devices with large internal storage)
Still, i have to agree with everyone else, its REALLY nice to finally see a v5.x CWM... using it on my HD2, Evo Shift, and HeroC, it really was a surprising difference from when I was sticking with v3.x
Just awesome!!! Thanks so much!
this needs to be moved to the dev section, but great job!
Sent from my Transformer TF101 using xda premium
Thanks! Installed successfully on two separate rooted B60 TF101's(ARHD 3.2, and Krakd 1.4.2)without any issues. Works great nice job!
New recovery works great!
Just flashed this without any issue. Nice look and feel. Are there more options available under the 'wipe' option, such as ability to wipe only cache or Dalvik cache like the 3.2.0.1 had? I haven't had a chance to look yet and didn't want to chance inadvertently wiping my device. Thanks.
[EDIT] I've now had time to look around and answer my own question. Yes, the other wipe options are there under the wipe menu item. Good to not see that sd card error all the time. So far it seems pretty flawless and better looking, too. I had to reflash my ROM last night and got to put it through it's paces.
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
I also did a back up and restore and my Wifi is fine.
I did not do the advance backup just the regular backup.
Someone else reported this wifi problems using Roach's 3.2.0.1 CWM also.
jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
Hmm, weird, I'm not sure why the recovery would break that unless it's failing to restore something or possibly failed to back something up. I did several backups and restores when I was checking to see if everything worked and never encountered that. Maybe try restoring the one giving your trouble a couple of times to see if it comes back?
hachamacha said:
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
Click to expand...
Click to collapse
Looks like somewhere around CWM 4 is when the switch to tar was made. It has better the speed along with the ability to back up and restore the correct filesystem. Sounds like the progress thing was added somewhere around then as well.
[ Found here: https[colon]//plus.google[dot]com/103583939320326217147/posts/G4VQuCpR25y Sorry, can't make outside links yet. ]
Looking at a kernel zip, it uses dd to put the blob in /dev/block/mmcblk0p4, which is also where the recovery goes... I clearly need to learn more about what's going on here when flashing a kernel or recovery to the same thing and what the function of the blob is.
Looking in the nandroid backuip system tar though, it grabs the /system/lib/modules folder which some kernel zips add to, so the nandroid is backing that up. I'm not sure if nandroid, at least in its current state, is able to back up or restore the kernel itself because of the whole blob thing?
Hmm, perhaps I should make a feature list instead of just saying look at the Xoom release thread!
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Asus Transformer Prime TF700T (tf700t)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
Will give it a test run.
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Frostbiter said:
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Click to expand...
Click to collapse
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Phil3759 said:
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Click to expand...
Click to collapse
Ah okay, well so far that's the only bug in the recovery I noticed, and I wouldn't have even noticed it if I had remembered to put the kitkat gapps on my device before wiping it. Haha
Really nice job though, I'm glad you brought it over since I've had issues with plain cwm in the past and twrp doesn't seem to be getting updated at the moment I thank you for bringing this to my tablet.
Thank you so much for this nice tool and give us choices. I flashed it and the UI is just beautiful. Now I'll go test all its functions.
:good:
Nice
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
lj50036 said:
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
Click to expand...
Click to collapse
Just tried this out using your zip to install. Works great. Recovery is nice and easy to navigate. Thanks to Phil and LJ.
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Thank you so much Philz!
I was dreaming about this, is not a joke, I've been using your amazing recovery in my jfltexx since always because it's the best.
I would be glad to help you.
Lord_Towers said:
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Click to expand...
Click to collapse
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
soyusado said:
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Lord_Towers said:
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Click to expand...
Click to collapse
LOL, i remember when i discovered that too face palm.
Is Philz touch coming to a 701t Near you?
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
SlappyWag said:
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
Click to expand...
Click to collapse
Open Terminal Emulator and enter this command
su
dd if=/storage/sdcard0/download/philz_touch_6.19.3-tf700t.img of=/dev/block/mmcblk0p4
Link is dead !
Another link ?
bump
Anyone got another link to this please?
This should probably go in some general Q&A forum, but this is by far the most helpful community I've come across so I wanted to try here first. I've finally got my Ubuntu box up and running again (upgrading to 14.04 wasn't pretty) and was able to build for both my 700t and my n5 without error, but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen? I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible. Any insight you may have would be most appreciated.
Thanks in advance!
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
psudeke said:
but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen?
Click to expand...
Click to collapse
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
psudeke said:
I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible.
Click to expand...
Click to collapse
That's normal - ARM devices are just too different, and the emulator is just another different device.
psudeke said:
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Click to expand...
Click to collapse
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
_that said:
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
That's normal - ARM devices are just too different, and the emulator is just another different device.
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
Click to expand...
Click to collapse
Thanks _That, I appreciate your help! After reading your post and the f2fs post, i thought i was in the clear, but i still managed to screw something up. i'm unable to get the tablet to boot off of external, regardless of whether its my ROM or CROMBi. I see a "segmentation error" listed in the output from the the preinit, and then it always boots to internal. I thought maybe i got the mount points reversed in recovered, so i reflashed recovery, but no luck. i also tried deleting the preinit script and then reinstalling CROMBi, but i still get the same error. any thoughts?
psudeke said:
I see a "segmentation error" listed in the output from the the preinit
Click to expand...
Click to collapse
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
You still get that fault with a static busybox but it seems to copy files fine.
@psudeke you can compile the static busybox yourself simply with make static-busybox in your build folder - or just steal mine from /system/boot
sbdags said:
You still get that fault with a static busybox but it seems to copy files fine.
Click to expand...
Click to collapse
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
it comes from the ls -l /init* which indeed doesn't have the busybox prefix but if I do it gives some other error I forget now
Anyway it doesn't harm the boot process - just an error message
_that said:
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
Click to expand...
Click to collapse
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
psudeke said:
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
Click to expand...
Click to collapse
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
sbdags said:
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
Click to expand...
Click to collapse
Ahh, thanks sbdags! that fixed the issue with ROM2SD. i got that impression when i pulled the preinit and saw it only had an entry for internal. but, i'm still very much in a learning phase so i didn't want to jump to a conclusion.
and after getting crombi to boot on external, i swapped sd cards and my build of CM11 actually booted! now the real learning process begins as i figure out how to customize it.
Thanks again to both you and @_that, you guys are the best:good:
@sbdags and @_that
Just wanted to thank you both again for your help. After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
https://www.dropbox.com/s/khq17h04b715eyd/C11%20Benchmark%20ART.png
Hats off to both of you! :good:
--- Guess I can't insert an image directly from my DropBox, link is to a screenshot of my score ---
psudeke said:
After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
Click to expand...
Click to collapse
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
_that said:
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
Click to expand...
Click to collapse
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
psudeke said:
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
Click to expand...
Click to collapse
Just ask away and congrats! :good:
sbdags said:
Just ask away and congrats! :good:
Click to expand...
Click to collapse
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
psudeke said:
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes your unwanted apps
note apps can be installed into 2 folders /system/app or /system/priv-app
similarly you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
sbdags said:
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes you unwanted apps
note apps can be installed into 2 folders /system/app or /systempriv-app
similar you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
Click to expand...
Click to collapse
Thanks again! i can see how this becomes addicting fast :fingers-crossed:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
psudeke said:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
Click to expand...
Click to collapse
just zip the /meta-inf folder, and flash that to test. obviously comment out any format commands as they will fail. That is what I do.
Hey @psudeke you ever need any help with anything to do with source or git let me know
I am also willing to help out
and just a FYI be careful of @sbdags :cyclops: LOL
Just kidding....
Let me know thx Josh
Hey ME301 users.
I have decided to move this information over to a Q&A thread so we don't bung up CROMBI thread with this. It seems that there is something that is not letting ME301 users install and run the latest 4.4.3 version of CROMBI and of course we are hoping to do something about that.
I will post a few test zips to try and see if they can allow you to boot on to CROMBI.
As the users who are testing this out there are a few things that I ask of you when troubleshooting:
When installing CROMBI, please make sure you do a factory reset wipe in TWRP and also wipe cache and dalvik cache
Please do not choose any options in the installer for running data2sd, rom2sd or f2fs. If you have f2fs on your internal /data I could possibly make up a test for that. I am going to stick to EXT4 for now.
Make sure you choose ME301 in the installer, and choose do not install a kernel
Flash one of the test zips provided below once you finish installing CROMBI and before you reboot your tablet
If it fails to boot, please indicate whether it boot loops at black Asus logo screen or at the bootanimation
If it is bootlooping at the bootanimation, then please send me a logcat as well as a last_kmsg and attach it to this thread. If you do not know how to do this there are many guides on XDA that can explain it much better than I can.
That should be about all for now. Let the testing begin!
EDIT/UPDATE - Tests 1-4 = FAIL, how about test 5?
hardslog said:
Hey ME301 users.
I have decided to move this information over to a Q&A thread so we don't bung up CROMBI thread with this. It seems that there is something that is not letting ME301 users install and run the latest 4.4.3 version of CROMBI and of course we are hoping to do something about that.
I will post a few test zips to try and see if they can allow you to boot on to CROMBI.
As the users who are testing this out there are a few things that I ask of you when troubleshooting:
When installing CROMBI, please make sure you do a factory reset wipe in TWRP and also wipe cache and dalvik cache
Please do not choose any options in the installer for running data2sd, rom2sd or f2fs. If you have f2fs on your internal /data I could possibly make up a test for that. I am going to stick to EXT4 for now.
Make sure you choose ME301 in the installer, and choose do not install a kernel
Flash one of the test zips provided below once you finish installing CROMBI and before you reboot your tablet
If it fails to boot, please indicate whether it boot loops at black Asus logo screen or at the bootanimation
If it is bootlooping at the bootanimation, then please send me a logcat as well as a last_kmsg and attach it to this thread. If you do not know how to do this there are many guides on XDA that can explain it much better than I can.
That should be about all for now. Let the testing begin!
Click to expand...
Click to collapse
Test 1 & 2 both bootloop at the bootanimation Crombi-KK logo. I cannot pull logcat or last_Kmsg as my command prompt shows device as "offline" and after entering the commands it just reads "waiting for device".
DrBeaker said:
Test 1 & 2 both bootloop at the bootanimation Crombi-KK logo. I cannot pull logcat or last_Kmsg as my command prompt shows device as "offline" and after entering the commands it just reads "waiting for device".
Click to expand...
Click to collapse
If you reboot into TWRP, you can go into 'advanced' and then 'file manager' and then go into the 'proc' folder and in there you can find the last_kmsg. If you select it, it will allow you to copy it to your sd card.
hardslog said:
If you reboot into TWRP, you can go into 'advanced' and then 'file manager' and then go into the 'proc' folder and in there you can find the last_kmsg. If you select it, it will allow you to copy it to your sd card.
Click to expand...
Click to collapse
I have attached zip that contains test 1 and test 2 results.
DrBeaker said:
I have attached zip that contains test 1 and test 2 results.
Click to expand...
Click to collapse
Uploaded test 3 and test 4 to the OP
hardslog said:
Uploaded test 3 and test 4 to the OP
Click to expand...
Click to collapse
@hardslog thank you for your continued attempts to get this moving.
I have tried 3 and 4 with same results. Boots to Crombi bootanimation and remains there.
Attached is zip of Last_Kmsg for zips 3 and 4.
I hope they are helping.
DrBeaker said:
@hardslog thank you for your continued attempts to get this moving.
I have tried 3 and 4 with same results. Boots to Crombi bootanimation and remains there.
Attached is zip of Last_Kmsg for zips 3 and 4.
I hope they are helping.
Click to expand...
Click to collapse
Is it possible that instead of zipping the files, to rename them to a .txt and upload them uncompressed? It seems that when they get zipped the encoding gets messed up.
Test 4 stuck at Crombi-KK bootanim. Last_kmsg is 0 kb ?
hardslog said:
Is it possible that instead of zipping the files, to rename them to a .txt and upload them uncompressed? It seems that when they get zipped the encoding gets messed up.
Click to expand...
Click to collapse
I found the same thing myself, was hard to view.
I have taken the files, copied to SD then simply added .txt to the end of the file.
Attached are the results.
Let me know what i can do to assist further.
OK,
Here is what I need....
Someone with a me301t that boots, turn on adb either in rom or boot into recovery and run this command
Code:
adb pull proc/config.gz
Upload the file somewhere so I can download it......
Thx Josh & Team CROMBI
lj50036 said:
OK,
Here is what I need....
Someone with a me301t that boots, turn on adb either in rom or boot into recovery and run this command
Code:
adb pull proc/config.gz
Upload the file somewhere so I can download it......
Thx Josh & Team CROMBI
Click to expand...
Click to collapse
I cannot get ADB function to initialize while instlaling this rom. It boot loops at Crombi logo, and ADB indicates "device offline" and will not accept any commands.
While in recovery, ADB mode does not seem to be enabled. Best we can do at this time is browse to folders on the tab using the advanced/File Manager.
I have pulled that file and attached in its raw format and a copy with .txt on the end (which appears unreadable).
Any progress on the logs or attempts at ME301T tab?
DrBeaker said:
Any progress on the logs or attempts at ME301T tab?
Click to expand...
Click to collapse
not really. We are pretty stumped on this one right now, sorry to say.
hardslog said:
not really. We are pretty stumped on this one right now, sorry to say.
Click to expand...
Click to collapse
Do we need any more logs of something?
- I just got back from a vacation and now have access to a computer again so I could probably do some tests with my tablet while in front of the tv enjoying the World Cup
(thought this thing with adb would be some real scary **** from my linux netbook instead of my Windows partition but it turned out to be easier than I thought to get it set up)
/gosa
DrBeaker said:
Any progress on the logs or attempts at ME301T tab?
Click to expand...
Click to collapse
hardslog said:
not really. We are pretty stumped on this one right now, sorry to say.
Click to expand...
Click to collapse
Test 5 up in the OP. You know the drill. :laugh:
Result from test 5. Still stuck on boot logo (CROMBi-KK) .
Uploading last_kmsg taken from twrp. (take away .txt)
On my way out, so adb logcat will have to wait a bit more.
-Thanks for working on this!
hardslog i got it working ...
Test 1: failed (Rom booted but much of error's ,fc and apps stopped working.)
1. flashed the new version and selected in aroma installer tf300.
2. Flashed without kernel and flashed "[Kernel][ME301T] KitKat Compatibility Pack V2.5 [May 13 2014]"
Test 2: succes booting and working :laugh: :good:
1.Flashed the new verson (4.4.4) and selected in aroma installer tf300.
2.Flashed without kernel and with your test5.zip
I can confirm latest version with test 5 works.
archspijkenisse said:
I can confirm latest version with test 5 works.
Click to expand...
Click to collapse
Good to know that we have it working again. Now I can look into restoring overclocking and all that fun stuff
Great work guys. It's running very smooth.