Related
I press and hold the [home] and [power] keys and it boots to nothing, even tried the [camera] and [power] keys on my G1, nothing. Current rom/SPL posted below, is it possible there's a changed key setting for the rom?
Rom: CaNNoN202-CompleteEclair-v2.0
SPL: Danger
Firmware version 2.1
Baseband Version 62.50S.20.17U_2.22.19.26I
Kernel 2.6.29.6-bfs-Firerat
Build Complete Eclair 2.0
Try reflashing the recovery image via terminal
$su
#flash_image recovery /sdcard/recovery.img "assuming your recovery image is n root of sdcard and you renamed the recovery image as recovery.img"
#reboot recovery
See if that boots to recovery
How can you get to the terminal if the phone won't boot past the first screen?
camera+power goes to the first screen, home + power goes to the first screen, trackball + power doesn't load a screen, but turns a blue led on.
I have adb. How can I do it using that??
techn0crat said:
How can you get to the terminal if the phone won't boot past the first screen?
camera+power goes to the first screen, home + power goes to the first screen, trackball + power doesn't load a screen, but turns a blue led on.
I have adb. How can I do it using that??
Click to expand...
Click to collapse
Does adb see your device?
At cmd prompt type
adb devices
If it shows up type
adb remount
If that works...
adb shell
You will have
#
Type the commands in the post above after putting a recovery image on your sd card.
If the first step does not work, you may be bricked.
techn0crat said:
How can you get to the terminal if the phone won't boot past the first screen?
camera+power goes to the first screen, home + power goes to the first screen, trackball + power doesn't load a screen, but turns a blue led on.
I have adb. How can I do it using that??
Click to expand...
Click to collapse
Just to clarify, the phone does boot up, and is fully functional aside from the [home] key working. I assume if I follow those directions, I could possibly use the android default img, and restore that, and unroot the phone for return possibilities?
rootlinuxusr said:
Just to clarify, the phone does boot up, and is fully functional aside from the [home] key working. I assume if I follow those directions, I could possibly use the android default img, and restore that, and unroot the phone for return possibilities?
Click to expand...
Click to collapse
From cmd prompt type
adb reboot recovery
See what it does.
I tried to type that and now my E, and R keys are dead...I even tried purchasing Better Terminal Emulator on the news that I can use the virtual keyboard and/or copy paste text. While this works, it allows SU, but when I type
PHP:
adb reboot recovery
it says "sh: adb: not found" So what I figured I'm stuck doing is to restore it to non-root status, or is there a way I can run commands on it from my laptop? The phone itself works great, makes calls, sends txt messages, just won't let me press the [home] key, and now apparently the E, and R keys.
EDIT:
I installed JDK, and the ADB packages, and can get it to the recovery screen from that menu, but I've run into another issue in regards to installing any update.zip through the cyanogen recovery menu. That being that you have to press [home] to confirm you want to do any action...
rootlinuxusr said:
I tried to type that and now my E, and R keys are dead...I even tried purchasing Better Terminal Emulator on the news that I can use the virtual keyboard and/or copy paste text. While this works, it allows SU, but when I type
PHP:
adb reboot recovery
it says "sh: adb: not found" So what I figured I'm stuck doing is to restore it to non-root status, or is there a way I can run commands on it from my laptop? The phone itself works great, makes calls, sends txt messages, just won't let me press the [home] key, and now apparently the E, and R keys.
EDIT:
I installed JDK, and the ADB packages, and can get it to the recovery screen from that menu, but I've run into another issue in regards to installing any update.zip through the cyanogen recovery menu. That being that you have to press [home] to confirm you want to do any action...
Click to expand...
Click to collapse
adb is ran from your computer, not terminal.
and yes, your home key not working means you won't be flashing a new rom through recovery anytime soon.
Once I figure out how to push an update package(rc33) and upgrade to cupcake/donut, will it be effectively unrooted(for purposes of sending it back)?
rootlinuxusr said:
Once I figure out how to push an update package(rc33) and upgrade to cupcake/donut, will it be effectively unrooted(for purposes of sending it back)?
Click to expand...
Click to collapse
you don't push it. and you don't technically "upgrade" to cupcake. you downgrade.
however, yes, it will be ok to send back.
here's how:
http://forum.xda-developers.com/showthread.php?t=491350
This is the bug fixed version of the “v4a” kernel that should work for all Android distributions for Kovsky (Xperia X1).
Change log:
+ Upgraded to GIT commit e83e7c3fccf8423bd0cf489f852f830ca6e80259
+ Kernel debugging and certain associated options for OS compatibility
Release Notes:
I’m providing two versions of “v4b” for regular and advanced users. At this time the only difference is the keyboard and buttons driver either being build inside the kernel (regular version) or outside in the modules (advanced version). In future versions there may be additional differences, but they will be detailed in my release notes.
Keyboard and buttons modules HOW-TO has been explained in other threads, if you’re thinking to yourself that you have no idea what I’m talking about I suggest sticking to the “regular version”.
Known Issues:
You will require the November 29 3D driver found at this thread: http://forum.xda-developers.com/showthread.php?t=852937. If you don’t install this your device will function completely normal outside of 3D games and applications. IMPORTANT NOTE: don’t install the gralloc driver as it will cause the screen driver to eventually lockup (otherwise known as SoD).
The camera has been fixed in the kernel source code, but the libraries in Android have no support for it. It’s not an easy fix, and it’s not going to be fixed anytime soon so support has not been built into the kernel.
Keyboard and buttons will eventually fail, this isn’t new but using a method posted in this forum for reloading the drivers (advanced version only) works!
The battery driver is very accurate up until about 50% left being reported in Android. After which it becomes somewhat unstable, reports incorrectly and may force shutdown (softly) your device. My best suggestion; consider 40-50% left as 0.
Smart feedback is appreciated.
thanks alot i will tested and back with feedback soon
are android camera libraries particular to each device or can we use libraries from other devices?
Here is the guide for advanced kernel, which allows you to wake keyboard with 1 click instead of rebooting the device. Guide is for freshly installed android (so no just updating the kernel).
1. Extract autostart.sh from the included archive and place it to your SD card
2. Install android like normal.
Until step 9, keys won't work, except for camera and power button. If you screw up, press camera button to return to the home screen.
3. If you don't have it in your release, install "Terminal Emulator" from market
4. Launch "Terminal Emulator". Soft keyboard should pop up.
5. Type "su" (everything without quotes from now on). Press enter. Symbol on the left should change to #.
6. Type "mkdir /data/opt" and press Enter.
7. Type "mv /sdcard/autostart.sh /data/opt" and press Enter.
8. Type "chmod 777 /data/opt/autostart.sh" and press Enter.
9. Type "sh /data/opt/autostart.sh" and press Enter. Software keyboard should disappear now and keys should be working.
10. Go into the market and search for "Autostart (Root)". Install that application
From here, your android is working. If you wish to add 1-click keypad fix, then continue reading, otherwise you can close this page.
11. Install application "GScript Lite" from market.
12. Open GScript Lite.
13. Press left softkey (menu) and select "Add Script".
14. Type any name, like "Fix Keyboard".
15. Tick "Needs SU?" and press "Load File".
16. Type this into bottom window:
Code:
#!/bin/sh
rmmod microp-keypad
rmmod microp-ksc
insmod /lib/modules/microp-ksc.ko
insmod /lib/modules/microp-keypad.ko
17. Press save.
18. Return to the homescreen
19. Hold your thumb to get "Add to home screen" menu.
20. Select Shortcuts --> GScript Lite --> Script that you just created.
And now, each time your keyboard or front keys stops working, simply press camera key and tap on that icon you've just created
P.S.: this is not my work, i have just adapted what users seandean and yaana created. All credits go to them.
For the kernel, first impressions are OK. Testing with release "Only T E S T E R S [New CM6.0 Full + Barebone][29-11-2010]" release + nov29 3D driver. Artefacts still present when turning device on. I will report more after testing it out a bit more.
Camera Libraries
CowMix said:
are android camera libraries particular to each device or can we use libraries from other devices?
Click to expand...
Click to collapse
HTC Touch Diamond Camera library is pefect.
http://gitorious.org/~jbruneaux/linux-on-qualcomm-s-msm/linux-msm-home-work
http://www.youtube.com/watch?v=vhz0sPjT2UA
Im testing it now on CM6.1 Barebone with 3D drivers and autostart.sh
Wifi works
GSM works
fps2d: 28FPS
Neocore-no sound: not tested
Camera is not working
3G works
Bluetooth not tested
GPS works
Notification leds work with charge state (when start android attached charger)
i cant use this kernel..
when run haret, it comes error and then boot to WM back..
it said "can't mount fs......"
help me..
is it something wrong??
im using CM6.1
are you using windows 7 OR vista ?
if use this OS , you need to remove SD card and use card reader then recopy the kernel files , use v4b advnaced with autostart.sh
regards
im using ubuntu 10 and win xp..
i try to port it same as i port the other kernel..
but the other kernel work and not getting error when running haret,but with this one i got error..
thanks for quick reply..
matejdro said:
Here is the guide for advanced kernel, which allows you to wake keyboard with 1 click instead of rebooting the device. Guide is for freshly installed android (so no just updating the kernel).
1. Extract autostart.sh from the included archive and place it to your SD card
2. Install android like normal.
Until step 9, keys won't work, except for camera and power button. If you screw up, press camera button to return to the home screen.
3. If you don't have it in your release, install "Terminal Emulator" from market
4. Launch "Terminal Emulator". Soft keyboard should pop up.
5. Type "su" (everything without quotes from now on). Press enter. Symbol on the left should change to #.
6. Type "mkdir /data/opt" and press Enter.
7. Type "mv /sdcard/autostart.sh /data/opt" and press Enter.
8. Type "chmod 777 /data/opt/autostart.sh" and press Enter.
9. Type "sh /data/opt/autostart.sh" and press Enter. Software keyboard should disappear now and keys should be working.
10. Go into the market and search for "Autostart (Root)". Install that application
From here, your android is working. If you wish to add 1-click keypad fix, then continue reading, otherwise you can close this page.
11. Install application "GScript Lite" from market.
12. Open GScript Lite.
13. Press left softkey (menu) and select "Add Script".
14. Type any name, like "Fix Keyboard".
15. Tick "Needs SU?" and press "Load File".
16. Type this into bottom window:
Code:
#!/bin/sh
rmmod microp-keypad
rmmod microp-ksc
insmod /lib/modules/microp-ksc.ko
insmod /lib/modules/microp-keypad.ko
17. Press save.
18. Return to the homescreen
19. Hold your thumb to get "Add to home screen" menu.
20. Select Shortcuts --> GScript Lite --> Script that you just created.
And now, each time your keyboard or front keys stops working, simply press camera key and tap on that icon you've just created
P.S.: this is not my work, i have just adapted what users seandean and yaana created. All credits go to them.
For the kernel, first impressions are OK. Testing with release "Only T E S T E R S [New CM6.0 Full + Barebone][29-11-2010]" release + nov29 3D driver. Artefacts still present when turning device on. I will report more after testing it out a bit more.
Click to expand...
Click to collapse
you can skip the steps 14 to 16 by downloading the attached file and pressing load file when you are in the new script page. so instead of typing all those comands you can just load this file and save it.
I have tried that, but for some reason it showed me blank screen instead of script file browser.
matejdro said:
I have tried that, but for some reason it showed me blank screen instead of script file browser.
Click to expand...
Click to collapse
it works for me most of the times but it sometimes restart the device maybe typing it out is the best way
im testing the android right now and it is a good one but i got one problem.
when i unlock my screen i got a rare screen sometimes whit green dots and sometimes whit stripes. anyone knows how to fix that?
xorium said:
im testing the android right now and it is a good one but i got one problem.
when i unlock my screen i got a rare screen sometimes whit green dots and sometimes whit stripes. anyone knows how to fix that?
Click to expand...
Click to collapse
its a known issue no it hasnt been fixed yet this problem started from v4a
kerfooly said:
its a known issue no it hasnt been fixed yet this problem started from v4a
Click to expand...
Click to collapse
okey tanks for the info
how van i connect from in android to my pc for data exchange between my sd card?
when i plug it in my computer says that i dont have the driver?
Hi!
I have been testing Android and various Kernels for a while. And I have got no good answer to a question I have. I cant get bluetooth headset to work. Cant pair them. The answer I got is that its not fixed and that it is kernel issue. Bluetooth seems to work but not to connect pheriperals.
Is there a plan for this to work or is it a thing for the future?
Its the one thing before it can actually be used for day to day work. Lotus Traveler is now released for Android so sync should work.
today i got a isseu i runned android from yesterday evening until this afternoon that my buttons dont work again. only the camera button. how can i fix this? or is it retyping the codes again?
Here working very good on CM6.1
During boot there is a line containing something like:
[KOVSKY]: is ac online == 0
or (if charger is plugged in)
[KOVSKY]: is ac online == 1
Maybe it is possible to set this parameter to be '1' at boot? So the charger would work either it is connected or not while runnig 'haret.exe'
why its not going to work for me!!!!!?????????
why it is so hard to port????
its say cannot mount partition,cannot mount fs....bla...bla...bla...
HELP ME PLEASE WITH THIS V4B KERNEL..
IM STUCK AT HARET AND THEN BOOT TO WINMO BACK..
TRYING 10000000000000 TIMES TO PORT IT..
After installing CM9, I found the menu came with long pressing the power button was gone... Any idea how to get it back?
Also how can I take screenshot under CM9?
Kisses99 said:
After installing CM9, I found the menu came with long pressing the power button was gone... Any idea how to get it back?
Also how can I take screenshot under CM9?
Click to expand...
Click to collapse
The 4-way reboot menu hasn't been implemented into the builds yet. Until it's built in you can either use a 3rd party app, type 'reboot recovery' in terminal or reboot manually. To take a screen shot just hold power and volume down.
crump84 said:
The 4-way reboot menu hasn't been implemented into the builds yet. Until it's built in you can either use a 3rd party app, type 'reboot recovery' in terminal or reboot manually. To take a screen shot just hold power and volume down.
Click to expand...
Click to collapse
nice tip，screenshot works Thank you!
what command is it if I want to reboot to webos? - teaching me how to hunt - where can I find all the reboot parameters?
Kisses99 said:
nice tip，screenshot works Thank you!
what command is it if I want to reboot to webos? - teaching me how to hunt - where can I find all the reboot parameters?
Click to expand...
Click to collapse
Open terminal type 'su' (without quotes) then enter
Then type 'reboot recovery' enter
This will take you into moboot where you can choose an OS.
crump84 said:
Open terminal type 'su' (without quotes) then enter
Then type 'reboot recovery' enter
This will take you into moboot where you can choose an OS.
Click to expand...
Click to collapse
got it, thanks!
I noticed the extended power menu appears if you set the dpi to a higher setting, to match a phone. When I played with HDPI, to get the status bar on the top I noticed it also enabled the extended power menu with the different (than GB) sound options. This also completely hid the soft keys. So the menu is in there, probably some mod or code needed to enable it all time.
I'm a little confused ... why do you need an option to reboot into recovery? Every time you power cycle you get moboot.
Sent from my Galaxy S II (i777)
quarlow said:
I'm a little confused ... why do you need an option to reboot into recovery? Every time you power cycle you get moboot.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
I agree, there's no real need for it other than its a little quicker.
Sent from my PG06100 using Tapatalk
This is a 100% AOSP ICS build for the Lenovo Ideapad K1. It will wipe your entire system. You will lose all data except what is stored on the EXTERNAL sdcard.
Includes
Android ICS 4.0.4
ClockworkMod Recovery 6.0.1.0
Google Apps
Rooted version includes Superuser and busybox
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Downloads
As always flash at your own risk. I'm not responsible for your device.
Nvflash versions
K1_ICS_AOSP_Rooted_R2.zip
dfddf13bf51e357a4964a11a8adbfd53
Mirror
K1_ICS_AOSP_Stock_R2.zip
b359ec6a06289ccf8c6b83f07346be17
Mirror
CWM versions
CWM_K1_ICS_AOSP_Rooted_R2.zip
90341324a0927f3035e92dc81ffb9416
Mirror
CWM_K1_ICS_AOSP_Stock_R2.zip
c026beb4dc2a11defbc3c3bcbec041cc
Mirror
Instructions
Nvflash version
1. Download one of the packages above and extract it to a directory
2. Power off device
3. Press and hold both the Vol + and Vol - buttons
4. While holding both Volume buttons power the tablet on
5. The screen should go black and the two front LED's should remain lit. You are now in APX mode
6. Connect your device to USB
7a) Windows: Install the APX drivers from the 'drivers' folder
Double click the 'flash-windows.bat' file
7b) Linux: run 'chmod +x flash-linux.sh && sudo ./flash-linux.sh' from the extracted directory
CWM version
1. Download one of the CWM_K1_*.zip versions and move to external sdcard
2. Reboot into recovery
3. Install zip from sdcard
4. Choose zip from sdcard
5. Flash the update.
How to boot into recovery
Non-rooted version
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Rooted version
From a Terminal Application
Run the follow two commands
Code:
su
k1recovery
From adb
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Changelog
Code:
8/11/2012 R2
-Fixed external sdcard permissions
-Fixed keylayout
-Modifed build.prop to spoof Moto Xoom (App compatibility)
7/31/2012 R1
-Initial Release
Source Code
http://github.com/khanning
So from now on we will be able to flash future updates through recovery without wiping everything?
So from now on we will be able to flash future updates through recovery without wiping everything?
Click to expand...
Click to collapse
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
khanning88 said:
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
Click to expand...
Click to collapse
I dont know if it's me or because of the ROM. WIth the rooted ROM before AOSP, I was able to install Chrome with a APK downloaded from mobilism but sometimes the pages are fine then just rendered white , for all tabs.
Does anybody use SKYPE ? When I do video chat, my broadcast picture stretched vertically when I broadcast-only (no picture feed from the other side), the picture my friend saw is fine though.
Many thanks for your hard work.
That is the main thing that i hate about Lenovo's Factory ICS image, i still cant install Chrome or Evernote, or many of my NEEDED apps. I hope that you get this working soon. or at least a temp fix.
Just flashed the rooted aosp, the boot animation is a nice touch. The app compatibility issue seems fully resolved outside of Chrome, pointed out already, which is no biggie for me atleast. I still can sideload Chrome and runs perfectly. Also, so far the dictionary miss-spell issue doesnt seem to be a problem anymore. Maybe its just me but touch responsiveness seems a little better/quicker with this build. Just tried using the command 'k1recovery' to boot into recovery and it keeps giving me an error relating to permissions, saying it cant create /dev/block/mmcblk0p5. Seems like I just need to change the permissions of the /block folder but wasnt sure if I was just not doing something right.
Massive improvements from Lenovo's vanilla ICS still, thanx khanning!
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
@Khanning88 Can you provide a mirror please? Goo.im is down and shows "Internal server error".
Never mind. It's up again.
me_is_rushin said:
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
Click to expand...
Click to collapse
Yup the screen flashes when switching orientations, for a split second...
That's great. thanks for share.
Flashed this one and works wonderful.
Rebooting to recovery didn't work 1st, but then mounted filesystem as rw and tried the command and could get to recovery.
Got an error "Can't mount backup path" when trying to make a backup. Is it because I didn't have an external sd card.
If yes, is there a way to take a nandroid backup to internal memory?
BTW, thanks again for providing this ROM.
Thanks khanning88 for giving this fabulous AOSP ROM
Does this ROM support the Wifi+3G version?
I found some issues installing apps, including some games, Zinio magazine reader, google earth, etc, all saying incompatible with my device.
I experienced alot of freezes while restoring my backup with titanium backup.
I keep testing if it also occurs in normal use.
Installed AOSP-Rooted. So far, Chrome (already noted as issue in OP), and POGO Games showing up as Incompatible.
Other than that, and possible other apps being incompatible, looks great and installed as easy as can be.
Thanks Khanning!
-Cybie
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
several more freezes. obviously not depending on any special app..
erickwan said:
Does this ROM support the Wifi+3G version?
Click to expand...
Click to collapse
I'm not sure if 3G works since I have a Wifi version, but if someone with a 3G version could meet me in freenode IRC room #ideapad-k1 I would be happy to work on it. If you aren't familiar with IRC just go to this link and join the chat.
http://webchat.freenode.net/?channels=ideapad-k1
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
Click to expand...
Click to collapse
From a terminal app type:
Code:
su
k1recovery
Or from adb type:
Code:
adb shell k1recovery
Either method will reboot the device into recovery. I will work on adding the power menu options later.
several more freezes. obviously not depending on any special app..
Click to expand...
Click to collapse
I haven't experienced any "freezes" but when it happens to you could you please document what you were doing and take a logcat to help debug.
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/
Here is a very simple way to reboot into khanning's CWM recovery.
1. Playstore --> Download/Install aShell app
2. Run App
3. Select Checkbox for "Root" (In Settings, you can set app to start Root as Default)
4. type "k1recovery" into textbox
5. press "start command" button.
Simple, no need to be in "true shell" mode. This app allows you to run shell commands without the terminal. Great for newbies, quicker for anyone.
Hope this helps!
-Cybie
Here is a quick fix for the hardware keys. Just flash the .zip file from recovery. Updated first post with more detailed booting into recovery instructions.
K1_keylayout_fix.zip
Is there a way to reboot this thing without root. All the apps seen need root. Why isn't it available with the power button anyway? Am I missing something?
PolishPoet said:
Is there a way to reboot this thing without root. All the apps seen need root. Why isn't it available with the power button anyway? Am I missing something?
Click to expand...
Click to collapse
Root access is needed but the only way I know how to do it without root is with a computer via usb connection; install minimal adb and fastboot by shimp 208 and run through command prompt. Make sure you have updated motorola drivers and connect your phone, run command prompt and change directory to wherever you have adb installed; type "adb reboot" (without quotes, you may include -bootloader or -recovery to go into either of those); to install, go here.
http://forum.xda-developers.com/showthread.php?t=2317790
I've just moved to this phone from my S3, and it seems I have been spoiled by CM through the years, as the first thing I noticed about the OS was all the features I frequently used -- including a "reboot" menu item, which I wouldn't have considered a "feature" until now. The best part: when I first turned the thing on, it tried over and over to activate itself but failed, with the error message telling me it would try again the next time I reboot the phone. And how would you suggest I perform that reboot? This one I'm sure is trivial to most by now who have been using this phone for a while, but it just blows my mind.
Is shrimp's adb fastboot accepted as a recommended and reasonable workaround for this?
BTW, what other "features" am I going to notice are missing soon (and any recommended apps/methods to replace them)?
Thanks.
Doesn't just holding the power button a few seconds "reboot" the phone...or is that not really a reboot?
wjdunn3 said:
Doesn't just holding the power button a few seconds "reboot" the phone...or is that not really a reboot?
Click to expand...
Click to collapse
More of a hard power-off and back on than a clean reboot, and you would lose state and cached data, which to me isn't worth the risk.