Database Develop

[ROM][ICS][AOSP] Lenovo Ideapad K1

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

About flash CMW V20A

Hello,
I had posted this in Frequently Asked Questions about the LG Optimus 4x HD but got no help so I post here for a last try.
Just followed all dexter's steps in this thread to flash CMW
http://forum.xda-developers.com/showthread.php?t=2180138
but I got stuck here. Tried to read 34 pages of the thread but still couldnt solve my problem
My LG was rooted and unlocked.
Any help? thanks
Ekio

The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/

AlderCass said:
The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/
Click to expand...
Click to collapse
Tried and still not such files and directory thx anyway

ekiong said:
Tried and still not such files and directory thx anyway
Click to expand...
Click to collapse
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...

Bogeyof said:
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...
Click to expand...
Click to collapse
Omg I already did
Look pics

ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...

RuedasLocas said:
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...
Click to expand...
Click to collapse
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"

ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
---------- Post added at 06:48 PM ---------- Previous post was at 06:40 PM ----------
ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
Did you do it in recovery mode from the start? When I did it it was when the phone was just switched on normally into the main OS.

ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
Click to expand...
Click to collapse
Where the hell did you found that path /mnt/sdcard/....... ???

Tutorial CWM
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:

RuedasLocas said:
Where the hell did you found that path /mnt/sdcard/....... ???
Click to expand...
Click to collapse
It's in the system root for me, it's a symlink. Though it didn't work for me in the cat command, which is why I suggested using /storage/external_SD/ instead which did work for me. It looks like the OP has the files in the right places, and the hash in the command line screenshot implies that SU is working correctly, so I'm all out of ideas now.
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
Click to expand...
Click to collapse
Little bit arrogant, we're all trying to help here, so I hope for your sake your way works for the OP

AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
Click to expand...
Click to collapse
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:
Click to expand...
Click to collapse
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.

ekiong said:
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.
Click to expand...
Click to collapse
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Dexter_nlb said:
......
GUIDE:
1. when you are running unlocked bootloader and is rooted goto step 2.
2. download attached zip files and extract content to internal sdcard location
3. use adb shell or terminal from market and execute the commands below
4. you are now running with native CWM recovery and unsecure boot, which enable adb root at boot instantly.
5. boot into recovery, by rebooting device and hold VOL-DOWN during bootup. (from power-off = keep holding vol-down during power on)
execute these 3 commands for recovery image install
Code:
su
cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
execute these 3 commands for unsecure boot image install
Code:
su
cat /mnt/sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
or see screenshot here
do this at your own risk, and do NOT try this on old 4.0.3, which is not with unlocked bootloader, and you are required to install KDZ again.
THANKS to:
skydev - for his continued effort in finding root and giving our device full freedom with boot/recovery.
Click to expand...
Click to collapse
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !

RuedasLocas said:
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !
Click to expand...
Click to collapse
Still no such file, I give up :angel:
Thx every one

ekiong said:
Still no such file, I give up :angel:
Thx every one
Click to expand...
Click to collapse
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."

RuedasLocas said:
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."
Click to expand...
Click to collapse
OH MY GOD I'm stupid, I copied files with ZERO byte.
sorry I used airdroid to copy them to my phone. But only their icons moved into my phone, not contents.
It works now THANKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS :laugh:
Close thread and my stupid problem :silly:

can anyone help me root my coolpad defiant?

Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!

rebz408 said:
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
Click to expand...
Click to collapse
Any luck?

Thank you very much

Jayfreshh said:
Any luck?
Click to expand...
Click to collapse
Did you ever find anything for this device?

remarkablecow913 said:
Did you ever find anything for this device?
Click to expand...
Click to collapse
Nothing as yet still searching, need to do some work on the phone but nothing to start with ?

Jayfreshh said:
Nothing as yet still searching, need to do some work on the phone but nothing to start with ?
Click to expand...
Click to collapse
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
remarkablecow913 said:
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
Click to expand...
Click to collapse
Have you tried unlocking bootloader? That's probly most important. If it's locked there is no point tying

remarkablecow913 said:
I know. I can't find Any resources for this phone. I might get brave And see if I can find twrp for same chipset and try.
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Have you tried unlocking bootloader? That's probly most important. If it's locked there is no point tying
Click to expand...
Click to collapse
Okay if anything works out when you try let me know
The bootloader can be opened in developer mode for this devise if I'm correct

You can unlock bootloader in developer options but from there. I'm stuck and really want to get root and see what "deleted" files I can recover from a factory reset. Anybody ever try twrp for same chipset like someone was talking about doing?

rebz408 said:
Hello guys im new to these forums an did not know where to post at, i got a coolpad defiant (Not the best phone) an i wanted to root it and was seeing if anyone here maybe able to help me out?? ive tried to use kingRoot but not luck on using that method if anyone got any suggestions id really like that, thanks again!
Click to expand...
Click to collapse
[Update Anyone?]
I picked up a Coolpad 3632a yesterday and I've been trying to ROOT it for quite a while nowl; trying Kingroot v5.3.7 without PC, and KingRoot 3.5 on PC both failed to ROOT. I've been out of the loop for quite a while regarding Android devices and OS - the last Android Phone i owned was the LG G3 if i remember correctly. According to the available info I've found searching for Rooting Options for the coolpad 3632a it all seemed almost %100 easily rootable with or without PC mainly using Kingroot.
If anyone was successful in rooting this device (Coolpad 3632a / Android 7.1.1) - please let me know, my main goal is to find a good custom ROM and load it replacing the Bloat/Malware filled phone!
Thanks again to anyone who has taken the time to read and respond with any news (good or bad) on getting this device successfully rooted.
-=Mac3lite=-

Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.

phonecapone said:
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
Click to expand...
Click to collapse
EDIT: I just obtained temporary root.. seeing if it sticks.

Root for Coolpad Devices
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk

Yeah that's already what I tried previous to your post. Had zero luck. =/ Also after that point forward for some reason when i try to fastboot i cannot issue any commands and it displays "Secure Phone" at the bottom left of the screen. Whether or not it was due to this I do not know for certain.

phonecapone said:
Yeah that's already what I tried previous to your post. Had zero luck. =/ Also after that point forward for some reason when i try to fastboot i cannot issue any commands and it displays "Secure Phone" at the bottom left of the screen. Whether or not it was due to this I do not know for certain.
Click to expand...
Click to collapse
Does fastboot detect your device ? Or just the commands fail even after detection ?
Also , when your phone boots , does MTKlogger automatically start ?

dwaipayan774 said:
Does fastboot detect your device ? Or just the commands fail even after detection ?
Also , when your phone boots , does MTKlogger automatically start ?
Click to expand...
Click to collapse
It gets detected just the commands fail. There is a white "Secure Phone" line of text across the bottom left. Im going to try loading an sdcard to see if it will auto update anything.
I can't even use Flash Programmer in QFIL or many other apps in QDLOADER 9008 mode. I know the firehose is the correct one yet it never wants to boot. I don't know why.
MTKLogger might have before unless i'm thinking of a different handset here. But as of the moment it doesn't.

No luck with the sdcard. I think it's about time to factory reset this device and put it up for sale. I'll post the firmware here shortly.

Here is the firmware - https://forum.xda-developers.com/android/general/rom-coolpad-defiant-3632a-stock-t3855692

Temporary Root
phonecapone said:
Bootloader Unlock = Not happening on this device. At least yet.
Development = Absolutely none. Means no TWRP/ROMS etc.
Root = Nothing as of 10/10/2018.
Click to expand...
Click to collapse
What did you do? I've been trying for months now.

dwaipayan774 said:
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Click to expand...
Click to collapse
Any chance on a repost of the file?

dwaipayan774 said:
Root for Coolpad Devices
NOTE: I have not tried this on your device but I have tried it on my Coolpad Mega 2.5 D , Coolpad Mega 3 and Coolpad Note 5 lite. You might try to see if this works on your Coolpad Device.
Requirements :
A working ADB setup
Procedureownload the Given Zip File and Extract Them in a folder.
CONNECT YOUR DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
OPEN THE FOLDER WHERE YOU EXTRACTED THE FILES AND RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE IN ADB ....
Or RUN THE SCRIPT IN THE GIVEN FILE
Quote:
adb wait-for-device
Quote:
adb install magisksu.apk
Quote:
adb install rootcheck.apk
Quote:
adb install root.apk
Quote:
adb shell monkey -p com.yulong.openrp -v 500
Quote:
adb reboot
WAIT TILL THE DEVICE BOOTS
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
Quote:
adb shell mount -o remount,rw /system
NOW :
Quote:
adb push magisk /system/bin
IF SUCCESSFUL, TYPE:
Quote:
adb shell magisk su
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
Quote:
adb shell magisk su
OR
Update magisk for permanent root.
Download::::::::
https://drive.google.com/file/d/1e1atRg7PQ2JyI8W88g1E9L9NihdGEjqO/view?usp=drivesdk
Click to expand...
Click to collapse
hey the link is dead. could you make a new link?

ADB commands not working

Has anyone gotten the ADB commands to work? I'm trying to see if I can get by without root, so I want to enable the enhanced battery stats in GSam battery. It doesn't work for me. I'm using the latest platform tools, and I have the USB file transfer checked.
Does anyone have any suggestions that I can try?
Thanks.

Have you enabled "USB debugging" in developer options? Cause ADB definitely works here, and i haven't done anything special to get it working. Steps i'd personally take if it wouldn't work are:
Make sure USB debugging is enabled and USB is physically plugged in.
Make sure everything is ok with the ADB drivers, double-check the device manager.
Check if the device appears in "adb devices", make sure its authorized on the device.
Try actual adb shell and other relevant adb stuff.
BTW, if you seem to have troubles with ADB drivers, you can try wireless ADB instead. It is only available without root on Android 11 and does require the absolute latest SDK platform tools, but hey, i've tested it, it works, and it doesn't require any special USB drivers. Follow the "Connect to a device over Wi-Fi" steps from https://developer.android.com/studio/command-line/adb to try that.

InfX said:
Have you enabled "USB debugging" in developer options? Cause ADB definitely works here, and i haven't done anything special to get it working. Steps i'd personally take if it wouldn't work are:
Make sure USB debugging is enabled and USB is physically plugged in.
Make sure everything is ok with the ADB drivers, double-check the device manager.
Check if the device appears in "adb devices", make sure its authorized on the device.
Try actual adb shell and other relevant adb stuff.
BTW, if you seem to have troubles with ADB drivers, you can try wireless ADB instead. It is only available without root on Android 11 and does require the absolute latest SDK platform tools, but hey, i've tested it, it works, and it doesn't require any special USB drivers. Follow the "Connect to a device over Wi-Fi" steps from https://developer.android.com/studio/command-line/adb to try that.
Click to expand...
Click to collapse
Thanks!
I had already done everything you suggested, but can't get the battery stats to work. I even tried it using wireless ADB, but had the same results. I get no indication that my command was accepted . I've never enabled permissions like this before, just used root, so I don't know if anything is even supposed to come up.

What command are you trying to use exactly?

InfX said:
What command are you trying to use exactly?
Click to expand...
Click to collapse
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.

EMcTx said:
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
Click to expand...
Click to collapse
These work for me.
Sent from my Pixel 5 using XDA Labs

EMcTx said:
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
Click to expand...
Click to collapse
The first command supposed to grant a specific permission (BATTERY_STATS) to a specific app, i am unfamiliar with the second one (it turns a system setting named 'hidden_api_policy' on, but i have no idea what this setting is). I have no idea if those work as expected on Android 11, and Google loves changing stuff like that.
In any case, first, make sure you don't just run those commands from start->run or equivalent, but from a command line window, so if there are any errors you have a chance to read them. And finally, don't forget to force close and restart the app in question.
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
ridobe said:
These work for me.
Click to expand...
Click to collapse
Then the OP just doing something trivial wrong, which is a good thing, since it can be fixed

ridobe said:
These work for me.
Sent from my Pixel 5 using XDA Labs
Click to expand...
Click to collapse
Did you get any text after you entered the commands that indicated you were successful? I've tried it multiple times without success. I may try to clear the data on the app and try again.

InfX said:
The first command supposed to grant a specific permission (BATTERY_STATS) to a specific app, i am unfamiliar with the second one (it turns a system setting named 'hidden_api_policy' on, but i have no idea what this setting is). I have no idea if those work as expected on Android 11, and Google loves changing stuff like that.
In any case, first, make sure you don't just run those commands from start->run or equivalent, but from a command line window, so if there are any errors you have a chance to read them. And finally, don't forget to force close and restart the app in question.
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
Then the OP just doing something trivial wrong, which is a good thing, since it can be fixed
Click to expand...
Click to collapse
I am using the ADB shell in the platform tools folder. Yes, I'm sure I am making some stupid mistake . I had no problem rooting my Pixel 2Xl, so I'm hoping I can figure this out. I'll just keep trying.

EMcTx said:
I am using the ADB shell in the platform tools folder. Yes, I'm sure I am making some stupid mistake . I had no problem rooting my Pixel 2Xl, so I'm hoping I can figure this out. I'll just keep trying.
Click to expand...
Click to collapse
When you do a "adb devices" do you see your phone and are you getting any prompts on your phone?

Tel864 said:
When you do a "adb devices" do you see your phone and are you getting any prompts on your phone?
Click to expand...
Click to collapse
Yes, I do see my device, and I got a prompt on my phone the first time I connected.
I have managed to adjust my AOD brightness with ADB, so it must be something I'm doing wrong with the battery stats. I'm still waiting to see if the developer can give me any pointers. If I can't figure it out, I'll find another battery app.

I finally got it to work. The developer emailed me and told me that since I had the pro version, I needed to add pro after bbm.
Thanks for all the input!

I clearly remember you mentioning getting the package name wrong... the forum migration didn't exactly go smooth for xda, i guess :-/
Edit: WTF, now i see that last post, AFTER posting this one.

I'm having a similar problem.
Typing "adb reboot bootloader" using Windows Powershell, put my USB connected tablet into bootloader mode.
However when then typing "fastboot flash twrp.img" the command line returns "waiting for device" and appears to hang.
I definitely have Debugging ON, and "twrp.img" is in the adb folder.

AussieNordo said:
I'm having a similar problem.
Typing "adb reboot bootloader" using Windows Powershell, put my USB connected tablet into bootloader mode.
However when then typing "fastboot flash twrp.img" the command line returns "waiting for device" and appears to hang.
I definitely have Debugging ON, and "twrp.img" is in the adb folder.
Click to expand...
Click to collapse
fastboot flash boot twrp.img to install twrp, fastboot boot twrp.img to boot twrp

Got it eventually.

Troubleshooting random reboot problems on S2 exynos5433 tablet ONLY discussion for users running any version of Android 10

The gnss hwbinder patch have been incorporated into the Aug 25 17.1 builds.
Please take 10 minutes to read all of post #1 and #2. DO NOT USE this thread to report any other problems, it's only for troubleshooting random reboots or reboots into TWRP for S2 exynos5433 tablet users. If this is unreasonable, then stop reading. Thank you.
If you cannot provide the logs below, please do not participate in this thread. Thank you.
I will take a look at all logs uploaded. The more the better to help find root cause or causes.
At this point, I have no solution to fix random reboots, but gathering data that might help narrow down which app or process is causing this.
Instructions
1. If you are experiencing random reboot or reboot into TWRP, you MUST supply tombstone logs. It's super easy and simple to do. Connect your device to PC using micro usb cable.
Make sure adb debugging is enabled in developer options. To enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
Bash:
adb root
adb shell
cd data/tombstones
ls -al
# if you see files tombstone_00, tombstone_01, etc then
exit
mkdir t
cd t
adb pull data/tombstones/
Zip all the files and upload here. Alternatively, you can send me the zipped logs via xda PM.
2. The better log would be adb logcat of the problem (random reboot, stuck at boot animation due to random restart) that just happened or happening.
Bash:
adb logcat > crash.txt
# wait 30 seconds then hit ctrl-c to stop capture
Please zip the .txt file before uploading. For some reason, I cannot see .txt files here.
FAQ
Q1. When will this random reboot be solved?
A1. Set your expectations that it will never be solved. At this point, I'm only gathering data to try and help. There may never be a fix if it's due to a proprietary Samsung blob that can never be updated. DO NOT ask when or if this can be fixed. It is not productive and I will completely ignore the question. Thank you.
Q2. Will you provide updates?
A2. I will only provide updates if I think we have found a solution. Otherwise, assume I'm not working on this problem because like you, I have other responsibilities and interests in life.
Q3. What will you do with the logs?
A3. I will look at every uploaded log and try to find a common pattern among them. If I find something that I think it's worth reporting, then I will post it here. If I need more information, I will revise the instructions and ask for more.
Q4. Why are you doing this?
A4. Let me be clear. I'm not experiencing any random reboots myself, I'm just trying to help if I can. The more logs you can provide, the more likely we can narrow down the problem. No logs from the commuity means the random reboot problems will never be fixed.
Let me be clear again, DO NOT ask when or if this can be fixed. Thank you.

Reserved.

Hi @retiredtab,
thanks for your offer to analyze the crash-logs!
I'm using a T810 Tab (gts210wifi) and are experiencing random reboots since updating to lineage-17.1 (ripee).
The reboots itself are of different types:
1) Stuck at bootanimation - only exit by three-button-reset.
2) Reboot to unlock-screen, but after unlock-code endless other unlock-screens come up - only exit by three-button-reset.
3) Reboot to unlock-screen, but after unlock-code the screen is empty and after some time (few minutes) it resets and ends in the same sequence - only exit by three-button-reset.
4) Reboot to unlock-screen, everything ok after unlocking.
For most of the reboots it was my observation, that there was an event, which did wakeup the tablet from deeper sleep (plugin to charger, switching on the screen, alarm, ...).
That caused me to write a small Tasker-app profile, which is pinging my dns-server all 2mins (to prevent a deeper sleep). With that profile active I did not experience any reboot for at least 2 months. Before that I had about one reboot per day.
To support your analysis, I disabled that Tasker-profile and the reboots are back.
During the last 24hours I had two reboots of type 4, and I was capturing the logcat and tombstones afterwards.
Looking into the captured data I got the impression that it might contain sensitive data (found my server-names, calender-events and so on) so I'm unsure if it can contain even more sensitive data like login-information or wifi-passwords.
So I'm hesitating to upload them to this public forum.
Would you agree to receive the zipped logs by PM instead?

Yogi555 said:
I'm using a T810 Tab (gts210wifi) and are experiencing random reboots since updating to lineage-17.1 (ripee).
The reboots itself are of different types:
1) Stuck at bootanimation - only exit by three-button-reset.
2) Reboot to unlock-screen, but after unlock-code endless other unlock-screens come up - only exit by three-button-reset.
3) Reboot to unlock-screen, but after unlock-code the screen is empty and after some time (few minutes) it resets and ends in the same sequence - only exit by three-button-reset.
4) Reboot to unlock-screen, everything ok after unlocking.
For most of the reboots it was my observation, that there was an event, which did wakeup the tablet from deeper sleep (plugin to charger, switching on the screen, alarm, ...).
That caused me to write a small Tasker-app profile, which is pinging my dns-server all 2mins (to prevent a deeper sleep). With that profile active I did not experience any reboot for at least 2 months. Before that I had about one reboot per day.
To support your analysis, I disabled that Tasker-profile and the reboots are back.
During the last 24hours I had two reboots of type 4, and I was capturing the logcat and tombstones afterwards.
Click to expand...
Click to collapse
Hi, @Yogi555.
Your reboot types 2 and 3 are interesting - I haven't seen them happen with my device. I only get types 1 and (occasionally) 4.
And type 5: reboot to TWRP. On my device this has happened more often than type 4, but both are much less common than type 1.
It does sound like the device waking from deep sleep could be triggering these events. Certainly, my device most often goes into type 1 when it's been left alone for a while, such as overnight (so my workaround has been to turn it off at night).
But I've also seen it drop into type 1 while I was actively using it, so waking up mustn't be the only trigger.

Hi, @Ipedia,
Maybe types 2 and 3 are somehow related to the individual homescreen app - I'm using Nova Launcher. Only guessing here.
Regarding type 5: Yes I did see it as well sometimes - but I'm not sure if it is a type of it's own. If I remember correctly type 1 - 3 are rebooting itself after some time of stalling. And - not sure here - after some unsucessful reboots in sequence we end up in TWRP. (In the embedded business where I'm working, it is the desired behaviour to jump to a flashing-bootloader after a number of resets within a certain time).
I've seen the reboots while busy using it as well some time ago, rare, but it happened - but when I activated my described tasker-profile, they were gone as well. I've no explanation for that.
At the moment I'm only facing type 4 resets. I did many changes, since I saw type 1 - 3 (update to latest 17.1 linageos, latest Magisk, exchange of the wifi-blobs) so not sure if any of this solved these reboots, or if they are yet to popup ...

Yogi555 said:
Would you agree to receive the zipped logs by PM instead?
Click to expand...
Click to collapse
@Yogi555 , you can send zipped logs using PM. Thank you.

can you help me to get logs? I receive this error message
Code:
c:\adb>adb root
c:\adb>adb shell
gts210ltexx:/ $ cd data/tombstones
gts210ltexx:/data/tombstones $ ls -al
ls: .: Permission denied

Max_C said:
ls: .: Permission denied
Click to expand...
Click to collapse
Maybe have a look how my adb root problems were solved in this thread: https://forum.xda-developers.com/t/...-version-of-andriod-10.4308193/#post-85353551
Worth a try, but maybe your issue is different

Yogi555 said:
Maybe have a look how my adb root problems were solved in this thread: https://forum.xda-developers.com/t/...-version-of-andriod-10.4308193/#post-85353551
Worth a try, but maybe your issue is different
Click to expand...
Click to collapse
i see, my device not rooted. I need install Magisk first, then enable rooted debugging. I have no rooted debugging in developer options

Magisk is hiding the option - without magisk you should see it - even with an unrooted device

Yogi555 said:
Magisk is hiding the option - without magisk you should see it - even with an unrooted device
Click to expand...
Click to collapse
oh. i see. I have no "rooted debugging" option in my developer settings in Havoc OS
another problem is i have old Android SDK on my PC. I installed latest one, and got this
Code:
c:\adb>adb root
ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options

I had exactly the same issue with magisk being the one hiding the setting. Are you sure that you are not having magisk installed? Don't know Havoc ...

Max_C said:
oh. i see. I have no "rooted debugging" option in my developer settings in Havoc OS
Click to expand...
Click to collapse
Boot into TWRP then. You can get the same data/tombstones from TWRP using the same commands.
If you have the SM-T710, you will need my TWRP in order for adb to work. The official ones posted on twrp.me don't work with adb or mtp.
retiredtab - Browse /SM-T710/TWRP at SourceForge.net
sourceforge.net
Mine works, but it takes 10 seconds before mtp and adb work after the TWRP home screen is shown.

retiredtab said:
You can get the same data/tombstones from TWRP using the same commands.
Click to expand...
Click to collapse
thanks! got it, please check attached

I have downloaded them, but will examine tomorrow. It's been a long day and it's 12:40 AM. Time for sleep.

After 17 days of gathering data and troubleshooting, we think we may have solved the random reboots. Huge thanks to @lpedia, @CuckooPenguin and @Yogi555 for testing the various gnss patches until we finally figured out the hwbinder solution.
Details at
https://github.com/universal5433/android_device_samsung_gts2-common/pull/4
If you are one of those people who experienced random reboots, it's not too late to submit your data/tombstones or check them yourself for the error message that I listed above. In particular, you are looking for
Code:
#0 pc 00056baa /system/lib/[email protected] (android::hardware::gnss::V1_0::BsAGnssRilCallback::requestSetIdCb(unsigned int)+450) (BuildId: 30ee8b14270ae2b3ae675a7f9b4de136)
#1 pc 0000e8dd /system/vendor/lib/hw/[email protected] (android::hardware::gnss::V1_0::implementation::AGnssRil::requestSetId(unsigned int)+32) (BuildId: d0033c7cb8d0d1a2c99f977719d0d967)
#2 pc 0000fb05 /system/vendor/lib/hw/gps.default.so (broadcom::GpsiClient::marshal_agps_ril_request_setid(broadcom::IpcIncomingMessage&)+160) (BuildId: fe39be024fc2f98450c8d2fc07cda956)
Once the git pull requested is approved, this patch should make it into the next August security patch build for all flavours of the tab S2 including all the variant OS.
Finally, a huge thanks to @ananjaser1211 for tips, suggestions, code and acting as a sounding board for ideas.

retiredtab said:
this patch should make it into the next August security patch build for all flavours of the tab S2 including all the variant OS
Click to expand...
Click to collapse
sorry, I'm not sure i understand how it works... Should I wait when my HavocOS ROM will be updated in this thread? Or there is another way how to apply the patch

Max_C said:
sorry, I'm not sure i understand how it works... Should I wait when my HavocOS ROM will be updated in this thread? Or there is another way how to apply the patch
Click to expand...
Click to collapse
We tried modifying the manifest.xml directly, but the results were inconsistent. On my t710 the instructions below worked, but 2 people with the t810 it resulted in a system not booting properly. These 2 had to reflash the rom to get a working system back. On the t810, the below changed had to be compiled into the code.
If you want to try, backup your data first and be ready to reflash the old rom in case it fails. If it fails, you will have to wait for a new Havoc build or build it yourself.
Bash:
# Turn off gps in OS before booting into TWRP
# boot into TWRP
adb root
# touch mount, system
adb pull /system/vendor/etc/vintf/manifest.xml
# use a text editor and look for this section of code
<hal format="hidl">
<name>android.hardware.gnss</name>
<transport arch="32">passthrough</transport>
<version>1.0</version>
<interface>
<name>IGnss</name>
<instance>default</instance>
</interface>
<fqname>@1.0::IGnss/default</fqname>
</hal>
# change passthrough to hwbinder like so
<transport arch="32">passthrough</transport>
to
<transport>hwbinder</transport>
# save text file
# now push file
adb push manifest.xml /system/vendor/etc/vintf/manifest.xml
# verify that line manifest.xml has changed in the gnss section
adb shell cat /system/vendor/etc/vintf/manifest.xml | more
# Important. Wipe dalvik/art cache and cache
# reboot into OS, enable GPS and make sure GPS works
# Note you may have to go into your setting, apps and wipe cache data as well if GPS doesn't work.

retiredtab said:
We tried modifying the manifest.xml directly, but the results were inconsistent. On my t710 the instructions below worked,
Click to expand...
Click to collapse
Thanks, on my SM-T815 all working fine, I followed your instructions, pushed revised manifest.xml, GPS is working fine. I will test if it helped to solve the problem and leave message here with result in several days.

Max_C said:
Thanks, on my SM-T815 all working fine, I followed your instructions, pushed revised manifest.xml, GPS is working fine. I will test if it helped to solve the problem and leave message here with result in several days.
Click to expand...
Click to collapse
Well, I'm surprised it worked on the t815 when it failed on the t810. That's why I stated it was inconsistent.
So if you were getting daily random reboots due to gnss crashing, then the gnss hwbinder fixes that. We have now had 2 testers go > 150 hours uptime with this patch. Before, they were getting daily reboots/crashes due to gnss (as shown in adb logcat and tombstones).
At first, we thought going 72 hours without a reboot would qualify as a successful fix, but we decided to extend it > 100 hours.
Again, the data/tombstones and adb logcats will show you which process/app is crashing. That's why it's important to view and share them otherwise we would have never figured this out.
Please report back if/when your device reaches 100 hours of uptime.