Database Develop

[recovery] cwm 5.0.2.7 + cwm touch **no vibration**

Hello!
After some time of searching in many forums all over the web, I FINALLY found a solution for all the users that experience vibration issues when going into recovery.
I must say this is not my work at all. Credits go to the developers at this forum, to trungkho for finding this forum and to Rusty!, for recompiling and changing the files to match our P990 O2x (this was originally made for the SU660).
It's been tested by me and some other members of XDA, and so far, so good.
Internal SD and external SD are recognized and mountable.
Needs testing for flashing various ROMS, so feedback is appreciated.
Enjoy!
CWM 5.0.2.7: http://www.mediafire.com/?8iqokc1xg73xe89
CWM Touch: http://www.mediafire.com/?y07ehwijm6kjg4h

Cool will download and test tomorrow...
Sent from my Optimus 2X using XDA

This is awesome! Finally i can flash a rom without annoying people around me and stop damaging my phone!

Hope you enjoy it and hope it works!

For anyone waiting for someone to post back about this, I would like to confirm I have installed this, and the vibration has indeed gone!
I'm going to do some flashing to make sure I don't get errors, but first impressions look good.
Thanks for solving this problem!
Charles

I have already made a backup and restored and installed a couple of roms. So for me it works.
Sent from my LG-P990 using Tapatalk 2

Thanks for this recovery. Now i wont hear the "zzzzzz" thing on my desk while doing backup

Well, Rusty did it again, this time recompiling CWM Touch version from the SU660 to the P990. Here is the download link for testing.

Good . One problem though... I like the way the buzzy recovery scares the hell outta you
Sent from my Asus Transformer TF201 Prime using XDA Premium HD app

Trolling level: 9000
Sent from my LG-P990 using XDA

korgndm said:
Well, Rusty did it again, this time recompiling CWM Touch version from the SU660 to the P990. Here is the download link for testing.
Click to expand...
Click to collapse
I've tried this. Vibration is gone ( finally ! ) and the recovery loads fine, but the touchscreen doesn't work at all... It's frozen. If I try the volume buttons they work, but as soon as I do that, recovery restarts. Grrr. So close.
Edit : Just tried 5.0.2.7 and that works perfectly ! Pity about the touch version, but the vibration on this phone was driving me crazy when flashing ! DONE WITH IT ! Thank you !
♪ヽ(´▽｀)ノ

Does the touch recovery works good? I thought we werent suppose to use it.

punyategar said:
Does the touch recovery works good? I thought we werent suppose to use it.
Click to expand...
Click to collapse
Touch recovery always worked well for me, never a problem. That said, many people have had problems with it, so it is recommended to play safe and stay with the previous, non-touch version.

C:\shttps\nvflash>install-cwm-su660-windows.bat
1967 KB/s (4904960 bytes in 2.435s)
/dev/block/mmcblk0p7: cannot open for write: Permission denied
what am I doing wrong?
edit: replaced the script line with one found on the internet, and it worked (dont know why it doesn't work off hand)
adb-windows shell "/system/xbin/su -c 'dd if=/data/local/cwm-su660.img of=/dev/block/mmcblk0p7'"
edit 2: it no longer vibrates!!! FINALLY!!! HUGE THANKS!!

Ultramanoid said:
Touch recovery always worked well for me, never a problem. That said, many people have had problems with it, so it is recommended to play safe and stay with the previous, non-touch version.
Click to expand...
Click to collapse
I always prefered the "standard" version. The touch version's graphic interface is kind of lousy, and it's not as practical as the normal version. But every person is different, and might prefer other things...

Is this "better" compared to the past version 5.0.2.8 (which is i am currently using)? Its kinda annoying that your phone is vibrating when flashing something.

The past version was made for the 2X, but many people like myself had problems because when you entered recovery mode, the phone would turn into a dildo. The version posted in this thread was recompiled based on the SU660, which doesn't appear to have any issues among users. Even though it's 5.0.2.7, sometimes older is better...
So, to answer your question, if 5.0.2.8 makes your phone vibrate, but 5.0.2.7 doesn't, and they both do the same thing with no problems, then 5.0.2.7 is the way to go.
I don't know if Rusty is willing to make an updated version of this recovery. But, to me, and at this point, it doesn't really make a difference.

I'm still using 5.0.2.0, you shouldn't have a problem with 2.7
Sent from my LG-P990 using XDA

mrQQ said:
C:\shttps\nvflash>install-cwm-su660-windows.bat
1967 KB/s (4904960 bytes in 2.435s)
/dev/block/mmcblk0p7: cannot open for write: Permission denied
what am I doing wrong?
edit: replaced the script line with one found on the internet, and it worked (dont know why it doesn't work off hand)
adb-windows shell "/system/xbin/su -c 'dd if=/data/local/cwm-su660.img of=/dev/block/mmcblk0p7'"
edit 2: it no longer vibrates!!! FINALLY!!! HUGE THANKS!!
Click to expand...
Click to collapse
I had the same problem, permission denied. I don't use Windows. I put the recovery in the SD card and from a terminal in the device used dd to copy/install it.
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17
As indicated by Paul from MoDaCo, Rusty! etc.

I've used 5.0.2.7 since release and can confirm it have worked on all my flashes...

[WIP] Building CM 10.1

Granted, it has been a while since I've built CM, and never ported it to a new device, but figure this might give some smarter people a head start or at least provide a place for others to collaborate.
I've not gotten very far past the initial vendor setup per http://wiki.cyanogenmod.org/w/Doc:_porting_intro.
A lot of the work is based off the similar ASUS TF700T, https://github.com/CyanogenMod/android_device_asus_tf700t.
I've not messed with the kernel at all at this point, https://github.com/ouya/ouya_1_1-kernel.
I've uploaded everything so far to github, https://github.com/vinny75/android_device_ouya_ouya_1_1

Packages included with official build:
OUYA Framework, Launcher, and Store
Code:
app\OUYAKeyboard.apk
app\OUYALauncher.apk
app\OUYAOOBE.apk
app\OUYAWallpaper.apk
app\ouya-framework.apk
note: some media files I haven't list
CWiid for Android: http://cvpcs.org/projects/android/cwiid4android and https://github.com/cvpcs/android_external_cwiid[.
Code:
bin\wminput
lib\libcwiid.so
etc\acc_led
etc\acc_ptr
etc\buttons
etc\gamepad
etc\ir_ptr
etc\neverball
etc\nunchuk_acc_ptr
etc\nunchuk_stick2btn
Sixpair for PS3 controllers http://www.blog.kaiserapps.com/2012/10/setting-up-sixaxis-controller-android.html.
Code:
/bin/ps3service
/bin/sixpair

I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Sent from my Nexus 7 using xda premium

mybook4 said:
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Click to expand...
Click to collapse
Thanks, appreciate the help, hopefully, we'll have a working build soonish

If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!

Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"

mybook4 said:
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
Click to expand...
Click to collapse
I started out with Method 1 then moved over files and settings from the ASUS TF700T.

professorpoptart said:
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Click to expand...
Click to collapse
Yes, building the new device tree has been... uhm... educational... and I am still learning. If I don't make any headway on 10.1, I might drop back to 10 - at least most of the legwork will be done.

Ok, so I'm in the middle of a build
Have a vendor tree on my git and I forked Vinny75's device tree, modified it some
Also a kernel tree up there, which is required for my device tree (prefer to build the kernel myself =) I've booted a custom-built kernel on it already, so that shouldn't be an issue)
I'm nervous to flash this though. I did a bit of searching but couldn't come up with a way to get back into recovery should this thing not boot. You guys know of anything?

Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium

mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yea, that's what I'm seeing.
So here's my 'solution'
Since we have fastboot, we can boot a boot.img without having to worry about flashing it.
I've successfully booted my cm boot.img, with ro.secure=0 and ro.adb.secure=0, I can adb reboot it when it fails miserably to boot
Quick and dirty script to unsecure a boot.img:
http://pastie.org/8033076
It assume that unpackbootimg and mkbootimg are in your path, you can get them here: http://invisiblek.org/mkbootfs_tools.zip
Getting closer...

THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?

dibblebill said:
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
Click to expand...
Click to collapse
Yeah, I think that is the same solution posted earlier:
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Click to expand...
Click to collapse
THis might be another option too:
tylerwhall said:
I started looking into bootloader-level recovery tonight before messing with the file system too much and potentially getting into a bad state. I couldn't find this information anywhere else.
Bootloader strap
On the back of the board in the center, there is an unpopulated button (U33). When jumped while the power button is pressed, this appears to put the bootloader into USB recovery mode. It enumerates with an nvidia vendor id. Presumably nvflash or tegrarcm could be used to unbrick the device.
I haven't done anything with the bootloader recovery since I haven't yet made a backup. I'm not sure how much of the functionality is allowed given the state of the production fuse, but I would think we could use this to at least get back to a stock state.
Click to expand...
Click to collapse

Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium

mybook4 said:
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ah he makes it sound like it puts you in USB recovery mode fo you could ADB in to push an update.

Just wanted to say I'm totally stoked on this guys! Can't wait to see what you do with this. Wish I could help, but I'm really not a developer.

i agree with rebel! but when you guys have it readyish ill test flash it and tell you what happens!!

So, OUYA isn't really as interested in being an open console as they suggest.
I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode

That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...

sonofskywalker3 said:
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
Click to expand...
Click to collapse
I'd check with invisiblek about how to avoid bricking the OUYA. Apparently his is bricked. It's stuck in nvflash mode. I think it was a kernel written with a bad init.rc that did it. not sure though.
Sent from my Nexus 7 using xda premium

[L5] **** Guide for running CM10.1/CM10.2/CM11 on the Canadian E617G ****

The LG L5 E617G variant can certainly be rooted, have an unlocked bootloader, as well as run CyanogenMod. The Bell variant can use a custom kernel.
Firstly:
- Root the device using the guide in this thread.
- Verify that you have a SuperUser app installed, and you're able to achieve root status. The best way to check is by downloading SuperSU, and updating the binaries.
Secondly:
- Unlock the bootloader by downloading emmc_appsboot_617_truncated.zip in this thread. (Thanks Skellums!)
- Turn on USB Debugging in Developer Options, (if you can't see Developer Options in the settings menu, continuously tap on Build Number in About in Settings).
- When you plug in your device, if you have an SDCard, you should see two storage spaces within the LG L5 MTP. Place the bootloader file in root of the phone storage (which the devices sees as the SDCard). The actual SDCard is the external SDCard which ADB has trouble seeing on occasion.
- Plug in your device to the PC, and make sure its loaded into Android.
- Download the fastboot/adb files here, and extract them to C:/fastboot/. Open the command prompt in windows, and type:
Code:
cd C:/fastboot
then...
Code:
adb devices
...and make sure you see your device, then...
Code:
adb shell
su
dd if=/dev/block/mmcblk0p5 of=/sdcard/emmc_appsboot-backup.bin
dd if=/sdcard/emmc_appsboot_617_truncated.bin of=/dev/block/mmcblk0p5
reboot
- Now, you should have an unlocked bootloader. If you get any "file not found errors", you placed the emmc file in the wrong directory
Thirdly:
- You now need a recovery, so let your phone reboot, and when its back to the main screen, make sure the device is plugged in, open the command prompt, and follow the instructions here.
Fourthly:
- Any CyanogenMod works very nicely on the L5 E617G. You can get CM10.1 along with gapps here or CM10.2 here or the amazing CM11 here. Before heading back to recovery, you will need the CM10.1 ROM, GAPPS, v20 BaseBand, and WakeWithHomeAndPower_signed.zip (Optional) and v10 Baseband (For restore purposes if something goes wrong).
- Copy all those zips to the root of your external SD, and then run the command:
Code:
adb reboot recovery
- Before anything, create a NANDROID BACKUP! Make sure to backup to the external SD, as you probably would have more space to work with.
- Then, factory reset your device in recovery. You can now flash CM10.1, by choosing "install zip from external sd card". Flash the v20 baseband, then the ROM, then gapps, then the wake with home fix.
Done!
- Upon reboot, you should have CM working very well on your LG L5 E617G!
Note: You can also get to recovery with the L5 but holding down Vol Down and Home, while pressing the power button for 2 seconds.
Disclaimer: I wrote this article because I, myself, had quite the experience in getting CM10.1 running on this L5 variant, and I wanted to show that it's certainly possible, thanks to the hard work by all the devs here! Good luck!

Thank you, good sir! I have now installed CM10.1!
I ended up running the recovery twice - after the first time, during the reboot, it just hung at the LG logo so I turned it off and back on and then repeated the recovery install steps and it was fine after the second time (now that I think about it I should've just tried issuing the "adb reboot recovery" command again instead).
Phone definitely much snappier and I haven't had any problems so far! Thank you again!

It's been a couple of days now and all seems to be running smoothly!
The only issue I have with CM on my L5 is that the video seems to cause issues - it'll work the first time but then hangs afterwards and subsequent attempts just give an error. Rebooting is the only cure. Not a huge deal for me though.
The rest of the phone runs great, definitely smoother and snappier than stock.

Now my camera/video recording is working just fine today. Go figure.
Loving the speed vs the stock stuff!

koimr said:
Now my camera/video recording is working just fine today. Go figure.
Loving the speed vs the stock stuff!
Click to expand...
Click to collapse
I've noticed the same thing. Once and a while, the video camera will freeze, and then force close. Reopening it causes "Gallery has stopped.". It's really finicky, but a reboot usually does the trick. Not sure if it's a ROM issue or a E617G issue, but you're not alone!
Pictures seem fine, I would suggest staying away from the video recording for now.

BuffMcBigHuge said:
I've noticed the same thing. Once and a while, the video camera will freeze, and then force close. Reopening it causes "Gallery has stopped.". It's really finicky, but a reboot usually does the trick. Not sure if it's a ROM issue or a E617G issue, but you're not alone!
Pictures seem fine, I would suggest staying away from the video recording for now.
Click to expand...
Click to collapse
I seem to recall having these issues a long time ago with the stock ROM too, now that I think about it. Not a big deal for me, easier to just avoid using the video camera.
I've even gone and flashed the latest (as of today) beta 5 of CM 10.1 as well - works just great as well!

koimr said:
I seem to recall having these issues a long time ago with the stock ROM too, now that I think about it. Not a big deal for me, easier to just avoid using the video camera.
I've even gone and flashed the latest (as of today) beta 5 of CM 10.1 as well - works just great as well!
Click to expand...
Click to collapse
Great! I'm going to try the kernel that was also posted and attempt to overclock.
Sent from my HTC One using Tapatalk 4

BuffMcBigHuge said:
Great! I'm going to try the kernel that was also posted and attempt to overclock.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Oh wow! Post your results if it all works out!

koimr said:
Oh wow! Post your results if it all works out!
Click to expand...
Click to collapse
I have successfully flashed lge-e610-v3.4.0-13-08-2013_20-59.zip and overclocked the device to 1000Mhz!

BuffMcBigHuge said:
I have successfully flashed lge-e610-v3.4.0-13-08-2013_20-59.zip and overclocked the device to 1000Mhz!
Click to expand...
Click to collapse
Same here now! Whoohoo!!

Thank you, good sir! I have now installed CM10.1

I've installed beta 6 and now the video is working just fine (no hangs!).
I did find that I wasn't able to boot into recovery - I had to reflash recovery from ROM Manager.
I then tried to flash the custom OC kernel and that resulted in a blank screen, so back into recovery and reflash beta 6 again.
So I've lost the overclock but meh, I'm ok with waiting for an updated kernel.

New kernel was posted, I've flashed and it works - OC is back! :good:

fastboot adb files
Hey is it possible to re up the fastboot adb files i get a "file not found" ....or is it just the general adb install for android, if so i already have it from when i did my atrix. but if i need certain files then it would be great if someone could tell me, thx bunches

spuzzum said:
Hey is it possible to re up the fastboot adb files i get a "file not found" ....or is it just the general adb install for android, if so i already have it from when i did my atrix. but if i need certain files then it would be great if someone could tell me, thx bunches
Click to expand...
Click to collapse
A quick Google search usually gets what you need.
http://d-h.st/5Xy

Thx , searched the forums to see if there were special files or if it was just adb.I found nothing concrete and I already had adb installed so I just ran it and it worked so I know now.
sorry about getting back late to edit the post.

Does this Unlock Network?
My phone is LG E617G It's Canadian phone which locked to Bell Mobility.
Does this ROM work on that model? and does it unlock the network(sim)?

altltkrk said:
My phone is LG E617G It's Canadian phone which locked to Bell Mobility.
Does this ROM work on that model? and does it unlock the network(sim)?
Click to expand...
Click to collapse
It does not unlock the SIM, however, you can get your SIM unlocked by using a service such as this: http://dollarunlock.com/lg-e617g-optimus-l5-unlock-code.html

Good
Inviato dal mio LG-E610 con Tapatalk 2

Thank you, for this how to.
I've been searching everywhere for this info.
--------------------------------------------------------------------
I've installed CM and it seem to be working well, but there's a problem with the gapps install.
com.google.process.location
recherche google
picasa uplauder
google play store
All keep crashing on launch and do not work at all. SO I can't do any search on the phone and google play store isn't working at all.
Is this a know problem or did I do something wrong with the install?
Is there a way to fix this? I've tried to redoanload de gapps and do a factory restor but for now no changes.

[Recovery][05.04.2014][tf701t] CWM 6.0.4.7 Advanced Edition / PhilZ Touch 6.25.9

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
WARNING...
VERY IMPORTANT:
Some people were having SOUND ISSUES since flashing the new touch recovery mentioned later below. If you do not want to risk having what MAY BE PERMANENT sound issues it is better to not flash this.
Here is an updated philz touch advanced recovery 6.59.0/6.0.5.1 (fully working with touch afaik,no longer officially supported)
Possible past sound issues hopefully unrelated. Here is an updated philz touch advanced recovery 6.59.0/6.0.5.1 (fully working with touch afaik,no longer officially supported)
WARNING:
Possible past sound issues.
Seems to be unrelated.
Sound is ok here.
Read the thread. Decide for yourself.
https://www.dropbox.com/s/6n91kqmwzwe7wdw/philz_touch_recovery.img?dl=0
Thanks to all who helped.
USE AT YOUR OWN RISK.
To reboot into bootloader:
adb reboot-bootloader
To try the recovery before flashing:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Thanks goes to Phil3759. pershoot
https://www.dropbox.com/s/6n91kqmwzwe7wdw/philz_touch_recovery.img?dl=0

Thanks a lot! Every feature work correctly. I needed custom restore, and in this recovery it to be!

I really want to get f2fs support with touch

I would settle for ANY recovery with touch support
Sent from my K00C using Tapatalk

berndblb said:
I would settle for ANY recovery with touch support
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Me Too...i have CWM/Philz with touch on my Note 8.0 and it is very cool but with all the extra features it would be a little tedious to navigate.

Nicely done!!!
Sent from my SGH-T889 using XDA Premium 4 mobile app

Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper

Trel725 said:
Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper
Click to expand...
Click to collapse
Very interesting and the holy grail of the 701! :laugh:

sbdags said:
Very interesting and the holy grail of the 701! :laugh:
Click to expand...
Click to collapse
Just flashed it Thats absolutely fantastic! And they said it couldn't be done!

YayYouFixedIt said:
Just flashed it Thats absolutely fantastic! And they said it couldn't be done!
Click to expand...
Click to collapse
I am SO psyched about this! Can we now get a TWRP for our tablet? We should be able to integrate touch drivers using the same principle into TWRP!

michaave said:
I am SO psyched about this! Can we now get a TWRP for our tablet? We should be able to integrate touch drivers using the same principle into TWRP!
Click to expand...
Click to collapse
It may happen

Trel725 said:
Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper
Click to expand...
Click to collapse
What a relief! THANKS! :victory:

Sigh.
To good to be true?
I did some tests on the Philz recovery, did a nandroid then a factory reset followed by a restore and ended up with pretty distorted speaker sounds. Now, this COULD be unrelated, but I wonder....
Decided to dirty flash CROMi-X 7.0.3 and Aroma completely froze halfway through the installation screens....
I'm back on CWM.... :crying:

berndblb said:
Sigh.
To good to be true?
I did some tests on the Philz recovery, did a nandroid then a factory reset followed by a restore and ended up with pretty distorted speaker sounds. Now, this COULD be unrelated, but I wonder....
Decided to dirty flash CROMi-X 7.0.3 and Aroma completely froze halfway through the installation screens....
I'm back on CWM.... :crying:
Click to expand...
Click to collapse
Sound seems to be pretty good here. Might be unrelated. Maybe Give noozxoide a try to see if that helps belt it out. Tested with speakers, line out, netflix and music

http://forum.xda-developers.com/showthread.php?t=2039716
That is not a root app. Just seems to make the sound clearer and open it up a little.

My recovery is just a demo! I don't have enough knowledge in android recoveries, so I just include rm-wrapper and necessary libs (in /touch_libs). Also /system/bin/linker needed for correct works. Be careful now, and maybe someone else will make really good recovery.

Trel725 said:
My recovery is just a demo! I don't have enough knowledge in android recoveries, so I just include rm-wrapper and necessary libs (in /touch_libs). Also /system/bin/linker needed for correct works. Be careful now, and maybe someone else will make really good recovery.
Click to expand...
Click to collapse
Proof of concept is all we really needed to take off on this! Thank you!
I'm unfamiliar with /touch_libs... Where is that?
Also, which other libs ended up being required?

Maybe the touch recovery is affecting the sound eventually. You wouldn't think but to be safe maybe hold off til the problem is found. Could it be something else. Find out a bit later if it is something else like maybe it is one of the ROMs or a setting. My sound is good afaik.

michaave said:
Proof of concept is all we really needed to take off on this! Thank you!
I'm unfamiliar with /touch_libs... Where is that?
Also, which other libs ended up being required?
Click to expand...
Click to collapse
It is in recovery's root. Extract recovery.img by abootimg and then initrd.img by cpio.

I reinstalled CROMi-X 7.0.3 totally clean, formatted everything but /boot and ext-sd (data/media/ needed a cleanup anyway, he, he), still the same. The speaker seems to be shot. But how installing or using Philz would cause this is beyond me. It's gotta be unrelated....

[Q] Workaround/repair for broken volume up key

So my volume up key is totally busted. Not the biggest deal, most of the time. It's totally workable. But when flashing Crombi-KK, it uses the AROMA installer which doesn't cycle through selections using the volume down key. Instead of cycling through, it goes down until the end of the list and stops, and there's a few points in the install where you *need* to hit up to select options.
So I guess my question is, how repairable is this tablet's parts? I normally go to iFixit for teardowns, but this tablet has minimal support from those kinds of tech sites. Is there an alternative for me when installing a ROM?
I would've asked in the Crombi thread, but XDA doesn't let me post there.

MilesWilford said:
So my volume up key is totally busted. Not the biggest deal, most of the time. It's totally workable. But when flashing Crombi-KK, it uses the AROMA installer which doesn't cycle through selections using the volume down key. Instead of cycling through, it goes down until the end of the list and stops, and there's a few points in the install where you *need* to hit up to select options.
So I guess my question is, how repairable is this tablet's parts? I normally go to iFixit for teardowns, but this tablet has minimal support from those kinds of tech sites. Is there an alternative for me when installing a ROM?
I would've asked in the Crombi thread, but XDA doesn't let me post there.
Click to expand...
Click to collapse
Well I can't fix CWM unfortunately - we are locked into button driven menus as the android touch drivers that asus require will not fit into the 8MB recovery partition.
So you have no choice - you need to get them fixed or stick to roms that don't use Aroma .... sorry

sbdags said:
Well I can't fix CWM unfortunately - we are locked into button driven menus as the android touch drivers that asus require will not fit into the 8MB recovery partition.
So you have no choice - you need to get them fixed or stick to roms that don't use Aroma .... sorry
Click to expand...
Click to collapse
It's quite unfortunate because CWM is fine, but Aroma doesn't have list cycling. If just it would work like the rest of CWM I'd have no trouble.

MilesWilford said:
It's quite unfortunate because CWM is fine, but Aroma doesn't have list cycling. If just it would work like the rest of CWM I'd have no trouble.
Click to expand...
Click to collapse
I have tested a build of TWRP that worked with a usb mouse ......

sbdags said:
I have tested a build of TWRP that worked with a usb mouse ......
Click to expand...
Click to collapse
Could you post that TWRP build?

ariadnejro said:
Could you post that TWRP build?
Click to expand...
Click to collapse
Sorry I deleted it a long time ago - it was also to big for the partition but worked as a boot flash....