Related
I've not found any usefull manual to skip the android logo after booting (android 1.5), I'm stuck, can I install another bootloader without root (guess not) ? Maybe I'll better sell the phone, with cm I never had this kind of problems.
You could try flashing an upgrade/downgrade in fastboot(power + camera); you could root it afterwards.
Decimae said:
You could try flashing an upgrade/downgrade in fastboot(power + camera); you could root it afterwards.
Click to expand...
Click to collapse
ori bootloader: couldn't do that.
I got past the homescreen:
on adb: am start -a android.intent.action.MAIN -n com.android.settings/.Settings
robuser007 said:
ori bootloader: couldn't do that.
I got past the homescreen:
on adb: am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Click to expand...
Click to collapse
Maybe you should spell out what, EXACTLY, you have on it and how it got there.
lbcoder said:
Maybe you should spell out what, EXACTLY, you have on it and how it got there.
Click to expand...
Click to collapse
really don’t you just have to:
1. go to rc29
2. on “click android” part setprop persist.service.adb.enable 1
3. on adb: am start -a android.intent.action.MAIN -n com.android.settings/.Settings
1. Just put in whatever SIM you are using, then on the activation screen, hit Menu then click on APN. Click add APN and put your company’s internet settings in (ask your provider for these settings). Then add the data plan to your account for the day and remove it after you have activated the phone OR get a friend with a data plan to activate it for you.
The following procedure can be used if none of the above are available to you…
I. Getting Back to RC29
1. This procedure requires you to be on an old version of Android (RC29 aka Android 1.0) so you must use our unroot procedure first and get to RC29, DO NOT DO THE STEP THAT TAKES YOU BACK TO CUPCAKE, skip it and come back to here once you are on RC29.
How To Get Back to RC29
2. You also need a WiFi connection to do this procedure.
II. Setting Up ADB
1. After you are back to RC29, follow our How To Setup ADB procedure EXACTLY as it is written. Once you are able to see your phone’s serial number after typing ADB devices in the command prompt, then come back to this procedure.
IIIa. Activating the Phone Over WiFi WITHOUT a SIM.
1. Borrow someone’s SIM card then procedure to Section IIIb.
IIIb. Activating the Phone Over WiFi WITH a SIM but No Data Plan.
1. Turn on the phone, you will get a Touch Here to Begin Screen.
2. Open the phone’s keyboard and hit enter once then type the following on the phone’s keyboard:
setprop persist.service.adb.enable 1
3. Then hit enter.
4. Hit enter AGAIN and type the following on the phone’s keyboard:
telnetd
5. Then hit enter.
6. With the phone still plugged in and the command prompt still up on your computer screen from the ADB process, type the following in the command prompt on your computer with hitting an enter at the end of each line:
cd\
cd c:\AndroidSDK\Tools\
adb devices
*this should bring up a serial number if your phone is connected, if not then redo the setup ADB process.
7. Now, in command prompt on your computer, type the following with hitting enter at the end of each line:
adb shell
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
8. On your phone should pop up the Android Settings screen, you can now choose a Wifi network to connect to then hit back and finish the activation process over Wifi. Enjoy!
So we have all done a factory reset and watched in horror as the Setup Wizard loads up all the crapware that Lenovo packed in. Well now that you have Root and CWR, go ahead and do a Wipe Data and Wipe Cache, then Advanced ->Wipe Dalvik Cache.
Then when it reboots, go through all the initial setup steps until you get to that last screen that has the "Done" button in the bottom right.
Instead, touch the bottom-right corner of the screen to bring up the settings and go into Applications -> Development and enable Debugging.
Now:
Code:
adb shell
su
#mount -o rw,remount /system
#cd /system/app
# mv PreInstall.apk PreInstall.apk.bak
# mv PreInstall.odex PreInstall.odex.bak
Now feel free to touch that Done button and the wizard will close out without installing all that Bloat!
YMMV
This is a wonderful tip! Thanks
Sent from my Nexus S using XDA App
you can top it off a notch by going to /system/build.prop and change the setup wizard to optional
now, no more cheezy lenovo install screen and just the standard android setup wizard
explain how, I'm new...!
They just did.
Read the first post.
If you still do not understand then be more specific, what is that you do not understand.
What is missing from the first post is that after you enable Debugging in Applications -> Development, you have to connect your tablet to the computer, and you must have adb on the computer.(but this is kind of obvious for most people).
then from the shell you enter those commands.
In windows you open the command prompt by holding the shift key in your adb folder then right click with the mouse and choose open command prompt here.
than enter the commands from post 1.
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
I got my phone unlocked and rooted. I installed CWM than I attempted to S-OFF.
First attempt - realized I had 2 problems.
1) I had HTC Sync Manager Installed
2) MY PC cmd/adb is wonky. It was constantly unable to recognized internal/external command. I checked my enviormental variable path and all that jazz and didn't find no solution. (WIN XP) I tried shift-right clicking on the folder and I do not have that option. I attempted to install a program that does that shift-right click feature and it didn't work. I went to Start>Run>cmd and input the entire path and it didn't work. I tried dragging the platform-tools folder into the cmd and it didn't work, HOWEVER when I dragged the adb.exe file on the cmd it ran.
So I began following the instruction.
a) (((Drag adb.exe into cmd window))) [creating the path/director] devices
[adb deamon server starts than device is found]
b) (((Drag adb.exe into cmd window again))) reboot
[phone reboots]
c) (((Drag adb.exe into cmd again))) wait-for-device push firewater /data/local/tmp
[different results from file not found, error command, wrong syntax, unrecognized batch
I attempted to do the same above with firewater.bin - file not found, doesnt exsist type of error.]
ragequit
ROUND 2
re-read guide and realize I had HTC sync manager installed. So I uninstalled it.
During this go around - it seemed to have gotten worse, multiple errors and headaches, I did click YES to everything during the htc syn unintallation so I might have uninstalled the drivers (it showed it was there, but the installer image looked blanked instead of the typical exe image). But I eventually I managed to push the firewater normally before failing on the adb shell command. I probably have pushed this file into data local tmp MULTIPLE TIMES
ragequit after many attempts
ROUND 3
uninstalled all HTC from my PC, unplugged USB, revoke usb priv, reconnect phone to pc - installed manager, waited 30 min, uninstall only the manager and kept the drivers and this time it looked normal and not a blank image. Had to repeat the same steps as Round 1, constantly moving my adb.exe into the cmd window.
a) (((Drag adb.exe into cmd window))) [creating the path/director] devices
[adb deamon server starts than device is found]
b) (((Drag adb.exe into cmd window again))) reboot
[phone reboots]
c) (((Drag adb.exe into cmd))) wait-for-device push (((drag firewater.file into cmd))) /data/local/tmp
[installed]
[During this time, my phone is going crazy - mounting/dismounting, htc manager trying to install, the stupid sync folder pop up multiple times..... Several times, I just ignored it and tried to continues, other times I wait until it's stable.. but at this point, I am not sure if I ****ed up]
d) (((Drag adb.exe into cmd))) shell
[The command went through but my phone never recieved a shell prompt as I have seen in a youtube video, I continued anyhow]
e) something something m8: [already there after I hit enter from shell command] su
[During, Before and/or After - my phone is still mounting/dismounting sometimes, I have waited patiently at times, and other times, I would try rush through all of this step impatiently, I was in hour 4 at this time, frustrated]
f) su
g) Here is where I had more issues, after SU, sometimes the pre-installed path/command is there for me to input chmod 755, sometimes it goes back to my default C:document.\etc\etc and I would either start from a or attempted to run adb shell, while my phone harassing me with the mount/dismount.
sometimes, I am able to type in chmod 755 /data/loc before I get booted back to the C:docu/etv/etc
other times it goes through fine but does that same ****.
ragequit
Round 9,000 (today)
I was calm, I waited until the mount/dismount stopped and it showed my phone was connected. I've done this 2 ways (htc syn usb mode and mount as disk drive)
I manage to get all the way to the end, typed in "Yes".... WHELP, can not install... T_____T
*epic ragequit*
So now, I am sure, I may have corrupted or dmg my data/local/tmp folder?????
What I am curious now is:
A) Can I do a Factory Reset?? Will I loose my Root and/or re-lock bootloader? Soft-brick?
B) If I can't Factory Reset, what can I do?
C) I also tried to OTA the system update and CWM is tellling me installation abort (no error code)
Also, I ran my Titanium backup to see if that would fix any corruption I may have done during the adb fiasco, attempted to install the OTA and still failed/aborted.
I just want to go back to Factory and use twrp/weaksauce or as I read, use another ROM (forgot whom) to get S-off as it worked for others. I can't Flash the current Sinister/Stock Rom since they are on the new 1.54.651.8 while I am on 1.12.xx.x....
frustrated and ready to ragequit again lol
Hi all,
Found my old Kindle Fire2 lying around so thought i'd have a go at building whatever I can for it. Seems like there was already source code in the repo's for CM 12.1 but nobody had built it. Well I've built it and it seems to work fine!
Only had to fix a script which had broken since CM 11 for wifi and all seems good.
NOTE RE MAC ADDRESS
FYI your MAC address will now get randomly generated at first boot. If keeping your existing MAC address is important, don't flash this.
I can't take any responsiblity for this, I've purely built it and fixed a couple of issues. Please thank whoever contributed to the source in the repo's.
I've only installed from a complete wipe. Don't try it unless you're prepared to wipe your device.
Enjoy...
ROM
cm-12.1-20170728-UNOFFICIAL-otter2.zip
Open Gapps pico for 5.1
http://opengapps.org/?download=true&arch=arm&api=5.1&variant=pico
Going to have a go at building CM13 next. Tried 14.1 but got hung up on selinux issues so going to take a step back to CM13.
Original link fixed
I need to fix the wifi script at boot. Currently if you install the rom you'll need to open a terminal and run:
/system/bin/fix-mac.sh
Wifi should start shortly after...
works perfect.
also perfect timing. i picked the otter2 yesterday from my dads house, who didnt use it anymore, because he switched to an galaxy tab long time ago.
I am currently having trouble with the Wi-Fi
It just hangs at Turning on Wi-Fi!
I have tried to clear cache and dalvik cache after installing gapps and lineage
I also performed a full wipe before flashing the rom
EDIT: Sorry didn't read further down
I am having an interesting problem with this ROM. It appears stable until I install any app, either from APK or play store. afterward everything force closes and will not work again until data is wiped or permissions repaired. when the permissions are repaired, any installed apps from APK or play store vanish like they were never installed. copying anything to /system/app works fine, but that is not a long term solution.
Raised a couple of threads about the wifi issue for a bit of help but nobody had replied. I'll have another look when I have time. Can't say i had any issues after installing app's though.
Think I might have fixed the selinux policy as i misread the neverallow rule and didn't realise it actually excludes sdcards from remount, so I can explicitly allow it.
Hopefully new fixed build to come soon.
Hi, I know a few people have asked about the Wi-Fi issue, but im not aware of how to open a terminal once everything is installed. the only terminal I can find is in the recovery mode but it wont find the file you mentioned
I just flashed and executed /system/bin/fix-mac.sh after installing "super su", but still WIFI does not start. Any additional hints? Thank you very much for the efforts.
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
guys do you have the latest twrp for kf2? all links are dead on other threads.
Apologies if this is obvious - but how did you install the latest SuperSU without Wi-Fi? Is it a case of downloading the apk and transferring via adb?
Is the build working otherwise? The old CM one is beyond repair - works for a couple days and then gets itself into boot loop.
Thanks!
androidbenutzer said:
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
Click to expand...
Click to collapse
---------- Post added at 09:30 AM ---------- Previous post was at 09:21 AM ----------
[/COLOR]
androidbenutzer said:
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
Click to expand...
Click to collapse
not work:crying:
rapmen said:
---------- Post added at 09:30 AM ---------- Previous post was at 09:21 AM ----------
[/COLOR]
not work:crying:
Click to expand...
Click to collapse
Same here... all steps ok, but Wi-Fi still won't turn on. Heart-breaking! Build working fine otherwise...
nebula_rider said:
Same here... all steps ok, but Wi-Fi still won't turn on. Heart-breaking! Build working fine otherwise...
Click to expand...
Click to collapse
I bricked my Otter2 today, so I had to restart all over:
1. Flash the Android-Image in TWRP
2. Flash the GAPPS-Pico-Image in TWRP
3. Flash the SuperSU-Image in TWRP
4. Allow the Terminal in the Android developer settings
5. Open the terminal and execute "su 0 setenforce 0"
6. Allow "root" in the appearing popup.
7. Execute "/system/bin/fix-mac.sh"
8. Activate WIFI
9. Done
This works!
androidbenutzer said:
I bricked my Otter2 today, so I had to restart all over:
1. Flash the Android-Image in TWRP
2. Flash the GAPPS-Pico-Image in TWRP
3. Flash the SuperSU-Image in TWRP
4. Allow the Terminal in the Android developer settings
5. Open the terminal and execute "su 0 setenforce 0"
6. Allow "root" in the appearing popup.
7. Execute "/system/bin/fix-mac.sh"
8. Activate WIFI
9. Done
This works!
Click to expand...
Click to collapse
Ok so I gave this another go - thanks for the encouragement androidbenutzer! - and can confirm that it does, indeed, work!
My problem was with step number 7. This is going to sound so so lame, but I was just typing "system/bin/fix-mac/sh" on Terminal (without the quotes). It looked like Android was trying to run fix-mac.sh, but failing to mount something. For the fellow rookies out there, you first need to navigate to /system/bin. I'm sure there's a very simple way to do this, but since I know no better, this is how I did it:
cd\
cd system
cd bin
THEN type "fix-mac.sh" (without the quotes).
Wi-Fi switched on and remained on.
Thanks dom_b and androidbenutzer! So glad to have the wee otter2 up and running again!
nebula_rider said:
Ok so I gave this another go - thanks for the encouragement androidbenutzer! - and can confirm that it does, indeed, work!
My problem was with step number 7. This is going to sound so so lame, but I was just typing "system/bin/fix-mac/sh" on Terminal (without the quotes). It looked like Android was trying to run fix-mac.sh, but failing to mount something. For the fellow rookies out there, you first need to navigate to /system/bin. I'm sure there's a very simple way to do this, but since I know no better, this is how I did it:
cd\
cd system
cd bin
THEN type "fix-mac.sh" (without the quotes).
Wi-Fi switched on and remained on.
Thanks dom_b and androidbenutzer! So glad to have the wee otter2 up and running again!
Click to expand...
Click to collapse
I tried all the steps, and still no luck.
pakidermo5000 said:
I tried all the steps, and still no luck.
Click to expand...
Click to collapse
Actually you wouldn't get too far even if you could turn the wi-fi on. The build is plagued with the "Trebuchet has stopped" error, which apparently is common in CM. I tried every fix recommended online, without success.
I didn't read the entire thread but here's a super easy way to fix the wifi issue. Connect a USB cable from the Otter2 to your computer. Make sure you have adb installed. Open a command prompt and type:
adb.exe /devices
Now look at the security message on the tablet. Click yes
adb.exe shell
At the shell prompt, type the following:
[email protected]:/ # /system/bin/fix-mac.sh
---------- Post added at 02:42 PM ---------- Previous post was at 02:05 PM ----------
SuperSu is here:
http://rootmygalaxy.net/download-latest-supersu-v2-82/