Database Develop

[DEV][BRAINSTORM] Fully-working CWM Recovery

While the recovery we have at the moment, fruit of the hard work of xantaro, unclecracker and digitalfrost, is enough for most operations there are some things bugging me that is in our interest to fix with the ultimate aim of adding it to ROM Manager and thus get official support.
Current issues:
1. It isn't the latest version of CWM and isn't official.
2. It doesn't have USB mount working.
3. It doesn't have ADB working.
4. It doesn't support EXT4.
Now, I have tried to fix these but recoveries are a new domain for me and at a first attempt I couldn't bring some of these to work. Compiling the latest version was easy and an important first step towards official; however, all others I couldn't do it and I don't think we should talk with koush before fixing all this.
Here are my short attempts:
- For USB mount I defined on the BoardConfig the path for UMS lun0 file. The path seems to be correct and there's no other file in /platform/ as I've found out by running a ls -R. I have no idea why it's not working.
- For ADB, I made sure the persist.adb.service is set to 1 and the init.rc is starting it. This being said, I don't know what's missing. Perhaps this is of interest?
- For EXT4 support I thought it was just a matter of adding alternative FS to recovery.fstab. Seems I was wrong though.
So, does anyone want to join in and help?
This is really new territory to me and I have a quite faint idea of what I'm doing.
A few guidelines:
- Read this to get an idea.
- You'll need CM sources (repo init... repo sync...)
- The CWM recovery source is in /bootable/recovery
- Here is my device source and a patch file for some changes on recovery src *
- Run build commands (. build/envsetup.sh, lunch full_p970-eng, make -j4 recoveryimage)
* If you don't change what I did on the recovery source you won't have a key to select.
Also, I have CWM 4.x at the moment on my OB but since it does the same as the already posted 3.x I don't deem necessary to share it; but if anyone wants, I'll upload it.
I'll join the party when I come from the mini-vacations, hope there'll be some progress meanwhile!

Great
i'll try to do some help,maybe little

If anyone wants you can request a pull from my source.
Also, here's a flashing CWM 4.x. I renamed it Nova recovery for the lulz.
http://www.multiupload.com/R7WGNYTL7G

Changes on the Source to get selectbutton to work shouldn´t be necessary. Adding "BOARD_HAS_NO_SELECT_BUTTON := true" to boardconfig.mk suffices to get selectbutton to work.
EXT4 Backup and Restore worked for me after editing the fstab file.
For the ADB and USB mount problem i have no Idea what is missing. Like you said, adb daemon should get started througt the initscript.
BTW. seems like the Progressbar isn´t working on the newer Versions of CWM

xantaro said:
EXT4 Backup and Restore worked for me after editing the fstab file.
Click to expand...
Click to collapse
Could you release a new version or tell us how to do it? Thanks

To get EXT4 working in my O2X builds my /data line looks like this:
Code:
/data ext3 /dev/block/mmcblk0p9 NULL auto

xantaro said:
Changes on the Source to get selectbutton to work shouldn´t be necessary. Adding "BOARD_HAS_NO_SELECT_BUTTON := true" to boardconfig.mk suffices to get selectbutton to work.
Click to expand...
Click to collapse
I thought the flag wasn't suffice. Thanks.
Rusty! said:
To get EXT4 working in my O2X builds my /data line looks like this:
Code:
/data ext3 /dev/block/mmcblk0p9 NULL auto
Click to expand...
Click to collapse
Nice tip, I'll try.

knzo said:
While the recovery we have at the moment, fruit of the hard work of xantaro, unclecracker and digitalfrost, is enough for most operations there are some things bugging me that is in our interest to fix with the ultimate aim of adding it to ROM Manager and thus get official support.
Current issues:
1. It isn't the latest version of CWM and isn't official.
2. It doesn't have USB mount working.
3. It doesn't have ADB working.
4. It doesn't support EXT4.
Click to expand...
Click to collapse
Hey,
I know this is an old thread but still if u have not resolved the problem with ADB and USB follow these instruction:
Before we start:
My mobile is Spice Mi-410 (Qualcomm made), also known as Cherrymobile magnum, Wellcomm, Motorola triumph in different countries. So may be these tweak will not work with your device. (But you can give it a try )
I hope you know how to unpack recovery.img of your device (or boot.img if your recovery ramdisk is stored in boot.img like Xperia Arc) if not then follow this guide to unpack recovery.img and extract recovery ramdisk into a folder.
Tweak
For ADB: Open init.rc file from recovery ramdisk/initram using any editor of your choice
Put this line at the end of "on init" section
Code:
write /sys/module/g_android/parameters/product_id ####
where #### should be replaced by your device's product id.
(if you dont know what it is then connect your mobile to PC and issue "lsusb" command in ubuntu terminal, you should see something like this
Bus 001 Device 027: ID 0489:c000 Foxconn / Hon Hai
Here c000 is my devices product id and Foxconn is my device's manufacturer)
Though /sys/module/g_android is not present in our device but this worked for me.
Please note that the device id is case sensitive, so write what you see on PC
For USB: For this add following line at the end of "on boot" section in init.rc file
Code:
echo 1 > /sys/class/usb_composite/usb_mass_storage/enable
For your device first confirm the location of /sys/class/ ###### / ####/usb_mass_storage/enable
Since this location vary from device to device.
This should enable usb storage mounting from recovery.
Best of luck!!

One option for load rootfs image in native mode is necesary
enviado

[RECOVERY] CWM Touch 5.8.1.3 for SU660

Herro
By request I have (hopefully) ported the European O2X touch recovery to the SU660. I don't have one of these to test, so on your own head be it etc etc
Other ports I've done have worked (O2X => G2X, SU660 => P990), so I don't see why this shouldn't, but you know the drill.

Thanks Rusty!
Just to be sure before I dive in...are the backups made in prior CWM version (e.g. 5.0.2.7) compatible with this version?

As far as I know, yes.
But I've never tried

Hi Rusty,
Wanted to report back. I haven't got a chance to test it out myself because of my usb cable giving up its spirit and dying.
BUT, I did have some friends try it out on theirs and they are having issues. Installed fine but have "cannot mount" errors.
EDIT:
Got myself a new cable and flashed it. I also get the same errors. I cannot access the log file either. The error messages are hidden behind the recovery menu, but the lines I do see are as following:
Code:
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
When attempting advanced--report error, I get
Code:
E:unknown volume for path [/data]
Sounds like cannot mount because of wrong partition assignments. Any thoughts?

Interesting, I've had a look and I've used the right partition layout. Only other changes were default.prop (which doesn't contain any references to partitions) and the kernel (which should be interchangeable as I've used the SU660 on on P990 recovery and used a P999 one to get the touch recovery working).
Colour me confused (for now).

If i sent you the latest working cwm image file (5.0.2.8), would that help?
Sent from my LG-SU660 using xda premium

It might, it might not lol
But I can stick bits from it in the touch version and see if it makes any difference.

here's the img file. I think wkpark and others put it together for the su660 based on your earlier work.
I also noticed that the fastboot.bin that I used for my su660 may be different than what you posted before. I'm attaching that as well in case it might help too.
Thanks!

Any luck Rusty??
Sent from my LG-SU660 using xda premium

I had forgotten

Rusty! said:
I had forgotten
Click to expand...
Click to collapse
Thanks, but still no luck. Similar mounting errors as before. This time, the Advanced-Show log did manage to give an output:
Code:
event: 228 451
event: 228 451
up
failed to open /sys/class/android_usb/android0/state: No such file or directory
Does that mean anything to you?

Not a thing I'm afraid.

Well, too bad but thanks anyway. Appreciate your kind attention and help!
Sent from my LG-SU660 using xda premium

i not undersent to use it

[ROM] [4.2.2] [1/7/13] CyanogenMod 10.1 - Google Edition!

BUILDS FOR THE SD VERSIONS OF THE G9 ONLY, NOT THE HARD DISK VERSIONS!
Welcome to CyanogenMod 10.1, the first 4.2 ROM with everything (or almost) working!
What works?
Everything
What doesn't
GPS is a bit weird
BIG THANKS TO Quallenauge FOR BUILDING THE FIRST BOOTING CM10.1 FOR THE G9, as well as trevd for this builds!
Features
Downloads and install methods
FAQ
Got a bug? Learn how to report it here
Kernel Sources
​

Features
- Fast
- Stable
- 4.2.2
- Almost everything works
- Phablet UI (like the Nexus 7 or Nexus 10)
- Linaro built
- OTA updates via Goo.im
- Google Edition Style
Download and install
Download the latest ROM to the device's internal memory, the external SD, whatever you're doing. You can get it from here:
Select the latest ROM from this page - Look at the dates!
You also will need the latest gapps for CM10.1 here:
Gapps at Goo.im
Coming from non-CM10.1 builds
You must be rooted and have SDE before this
THIS WILL WIPE YOUR INTERNAL SD, AFTER YOU HAVE FLASHED THE ZIPS
1.) Download this zip: cwm-g9 to your PC
2.) Extract it
3.) Turn off your G9
4.) Power on whilst holding volume down, it will boot Archos recovery mode
5.) Select (Recovery System) > Developer Options > Flash initramfs and zImage (or similar)
6.) Plug your device into a PC, and a drive will appear
7.) Copy the extracted zImage and initramfs from the above zip
8.) Unmount the drive and press POWER to select OK on the device, it will flash the kernel
FROM THIS POINT YOUR DEVICE WILL NOT BOOT, BUT IT WILL BOOT INTO CWM
9.) Press OK to reboot, it will boot into CWM
10.) Select flash zip from sdcard, and select the ROM you downloaded
11.) Reboot your device
12.) When it has booted, copy the Gapps again to the internal memory
13.) Reboot back into recovery - This will be TWRP now
14.) Flash the gapps as you did before with the ROM, through Install and navigating the menus
NOTE: If your SD is your external SD, go back, select Mounts, then tick /data, then go to Install and navigate up and then into /data/media, this will be your internal SD
15.) Reboot, you are done
Coming from an old CM10.1 build
THE LATEST BUILD WIPES THE INTERNAL SD!
1.) Download the update to your device and the Gapps to your PC
2.) Boot into CWM/TWRP (Depends on version)
3.) Select Install, and flash the update
4.) Reboot your device
5.) When it has booted, copy the Gapps to the internal memory
6.) Reboot back into recovery - This will be TWRP now
NOTE: If your SD is your external SD, go back, select Mounts, then tick /data, then go to Install and navigate up and then into /data/media, this will be your internal SD
7.) Reboot, you have the latest CM10.1

FAQ & Kernel Source
FAQ
How can I use the 3G (back) USB Port?
Download a Terminal Emulator
Open it and gain root by executing su (then enter)
Type one of the two following commands, followed by pressing enter
To turn it on:
Code:
echo "1" >/sys/class/rfkill/rfkill0/state
To turn it off:
Code:
echo "0" >/sys/class/rfkill/rfkill0/state
How can I get the Archos stock apps back?
The video player is on the play store here
I'm putting together a thread with APKs for the others
How can I calibrate my touch screen?
1.) Power off the device
2.) Power on whilst holding volume down > it will boot archos recovery
3.) Select Repair System > Force touchscreen calibration
4.) Follow instructions
How can I hide the signal icon?
From the Status Bar:
1.) Open the Settings app
2.) Tap "System" under customizations
3.) Tap "Status Bar"
4.) Select "Signal Status Style"
5.) Select "Hidden"
From the Quick settings pulldown:
1.) Open the Settings app
2.) Tap "System" under customizations
3.) Tap "Quick settings panel"
4.) Tap "Tiles and layout"
5.) Tap and drag "MOBILE DATA" to the delete icon
How can I report a bug?
The best way to report a bug is with a PC and adb.
1.) Connect your device to your PC
2.) Open a terminal/command prompt
3.) Execute this command:
adb shell logcat -c
4.) Execute this command:
adb shell logcat > /sdcard/log.txt
4.) On the device do what causes the bug
5.) When you have done that, press Ctrl + C (Command + C on mac) and it will return to the terminal
6.) Pull the file using this command:
adb pull /sdcard/log.txt
7.) Post the log.txt file attached to a post with the following info:
Device - 101G9? 80G9?
RAM
Processor (Speed and 4430/4460)
What you did to make it do that
Kernel Source
https://github.com/Quallenauge/kernel-archos/tree/trevd_expirimental
Use this to clone:
Code:
git clone https://github.com/Quallenauge/kernel-archos.git -b trevd_expirimental
The config can be pull from /proc/config.gz on the device

Quinny899 said:
Made a thread dedicated to 10.1, will become release thread when it becomes ready for general use:
http://forum.xda-developers.com/showthread.php?p=36836691
Looking into things like Bluetooth, Storage and app installing now. I have a feeling Bluetooth is just a simple lib swap, maybe not so for the storage and app installing
Click to expand...
Click to collapse
Great! I adapted my repository and added your file recommendations, so anyone can build a CM10.1 release.
But I see, that Phone.apk isn't crashing - what did you there? (I would take this also into the repository).
Regards to the bluetooth stack, when compiling I see this message. Maybe someone can explain this:
external/bluetooth/bluedroid/Android.mk:8: NO BOARD_BLUETOOTH_BDROID_BUILDCFG_INCLUDE_DIR, using only generic configuration

Re: [DEV][4.2] CyanogenMod 10.1
Quallenauge said:
Great! I adapted my repository and added your file recommendations, so anyone can build a CM10.1 release.
But I see, that Phone.apk isn't crashing - what did you there? (I would take this also into the repository).
Regards to the bluetooth stack, when compiling I see this message. Maybe someone can explain this:
external/bluetooth/bluedroid/Android.mk:8: NO BOARD_BLUETOOTH_BDROID_BUILDCFG_INCLUDE_DIR, using only generic configuration
Click to expand...
Click to collapse
I did nothing, I'm using the default ext4 you uploaded, I had no phone.apk issues. Only mobile configuration force closes on boot
Sent from my ARCHOS 80G9 using Tapatalk HD

Quinny899 said:
I did nothing, I'm using the default ext4 you uploaded, I had no phone.apk issues. Only mobile configuration force closes on boot
Sent from my ARCHOS 80G9 using Tapatalk HD
Click to expand...
Click to collapse
Really weird! Ah, I see! Phone.apk2 is not loaded - so no crashes
As for the camera, maybe it is possible to use the camera wrapper from the samsung piranha branch. I will try that.

Any idea why storage is failing btw? It mounts to /data/media and does nothing after that

gonna download and help out with the test front.

Re: [DEV][4.2] CyanogenMod 10.1
I managed to make an app install! I made the folder /data/app-lib with full permissions and it worked
Sent from my ARCHOS 80G9 using Tapatalk HD

fresh build
I made a build tonight, sdcard not mounting, no hq video, camera not working. The image I downloaded is missing framework2.jar, if you still have it most things are working. I am missing a bunch of apps so going to try to find out why they didn't build. I used the latest JB rather than jellybean-stable if that makes a difference.
Edit I see there is a new image up, will wait on new one with hq video working though.

Re: [DEV][4.2] CyanogenMod 10.1
stevemp said:
I made a build tonight, sdcard not mounting, no hq video, camera not working. The image I downloaded is missing framework2.jar, if you still have it most things are working. I am missing a bunch of apps so going to try to find out why they didn't build. I used the latest JB rather than jellybean-stable if that makes a difference.
Edit I see there is a new image up, will wait on new one with hq video working though.
Click to expand...
Click to collapse
I described how to get video working here: http://forum.xda-developers.com/showthread.php?p=36836817
Sent from my ARCHOS 80G9 using Tapatalk HD

stevemp said:
I made a build tonight [...] I used the latest JB rather than jellybean-stable if that makes a difference.
Click to expand...
Click to collapse
Do you used my repo? I was able to build the apps...
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Then download the file local_manifest.xml.bak
and put it as file to ".repo/local_manifest.xml" .
Then perform the build as usual. You should get an build similar to my preview.

ParanoidAndroid
Quinny899 said:
I described how to get video working here: http://forum.xda-developers.com/showthread.php?p=36836817
Sent from my ARCHOS 80G9 using Tapatalk HD
Click to expand...
Click to collapse
I'll get back to it after compiling ParanoidAndroid, hope it builds this time.
This is from a i9100g, what changes do I need to make for the G9?
Code:
## CONFIGURATION
%revision=1
%rom_dpi_min=160
%rom_dpi_max=320
%rom_default_dpi=320
%rom_default_layout=360
## CONFIGURATION
%hybrid_mode=1
%system_default_layout=0
%user_default_layout=0
%system_default_dpi=0
%user_default_dpi=0
## WORKSPACE PREFERENCES
android.dpi=0
android.layout=0
android.colors=NULL|NULL|NULL|NULL|NULL
com.android.systemui.dpi=%rom_default_dpi
com.android.systemui.statusbar.dpi=100
com.android.systemui.navbar.dpi=100
com.android.systemui.layout=%rom_default_layout
com.android.systemui.colors=NULL|NULL|NULL|NULL|NULL
com.android.launcher.mancol=1
com.android.launcher.appdrawer=NULL|NULL|NULL|NULL|NULL
## SYSTEM PREFERENCES
com.android.vending.dpi=%rom_default_dpi
com.android.vending.layout=%rom_default_layout
com.android.phone.dpi=%rom_default_dpi
com.android.phone.layout=%rom_default_layout
com.android.chrome.dpi=%rom_default_dpi
com.android.chrome.layout=%rom_default_layout
com.android.contacts.dpi=%rom_default_dpi
com.android.contacts.layout=%rom_default_layout
com.android.settings.dpi=245
com.android.settings.layout=720
com.android.calendar.dpi=260
com.android.browser.dpi=260
com.android.browser.layout=600
com.android.calculator2.dpi=160
com.android.calculator2.layout=600
com.android.email.dpi=230
com.android.email.layout=600
com.google.android.gm.dpi=250
com.google.android.gm.layout=600
com.google.android.apps.docs.dpi=240
com.google.android.apps.docs.layout=600
com.noshufou.android.su.dpi=240
com.noshufou.android.su.layout=600
com.noshufou.android.su.large=1
com.paranoid.preferences.dpi=290
com.paranoid.preferences.layout=600
---------- Post added at 12:14 PM ---------- Previous post was at 12:12 PM ----------
Quallenauge said:
Do you used my repo? I was able to build the apps...
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Then download the file local_manifest.xml.bak
and put it as file to ".repo/local_manifest.xml" .
Then perform the build as usual. You should get an build similar to my preview.
Click to expand...
Click to collapse
I used your old local_manifest.xml, guess it time for a fresh repo.

stevemp said:
I'll get back to it after compiling ParanoidAndroid, hope it builds this time.
This is from a i9100g, what changes do I need to make for the G9?
Code:
## CONFIGURATION
%revision=1
%rom_dpi_min=160
%rom_dpi_max=320
%rom_default_dpi=320
%rom_default_layout=360
## CONFIGURATION
%hybrid_mode=1
%system_default_layout=0
%user_default_layout=0
%system_default_dpi=0
%user_default_dpi=0
## WORKSPACE PREFERENCES
android.dpi=0
android.layout=0
android.colors=NULL|NULL|NULL|NULL|NULL
com.android.systemui.dpi=%rom_default_dpi
com.android.systemui.statusbar.dpi=100
com.android.systemui.navbar.dpi=100
com.android.systemui.layout=%rom_default_layout
com.android.systemui.colors=NULL|NULL|NULL|NULL|NULL
com.android.launcher.mancol=1
com.android.launcher.appdrawer=NULL|NULL|NULL|NULL|NULL
## SYSTEM PREFERENCES
com.android.vending.dpi=%rom_default_dpi
com.android.vending.layout=%rom_default_layout
com.android.phone.dpi=%rom_default_dpi
com.android.phone.layout=%rom_default_layout
com.android.chrome.dpi=%rom_default_dpi
com.android.chrome.layout=%rom_default_layout
com.android.contacts.dpi=%rom_default_dpi
com.android.contacts.layout=%rom_default_layout
com.android.settings.dpi=245
com.android.settings.layout=720
com.android.calendar.dpi=260
com.android.browser.dpi=260
com.android.browser.layout=600
com.android.calculator2.dpi=160
com.android.calculator2.layout=600
com.android.email.dpi=230
com.android.email.layout=600
com.google.android.gm.dpi=250
com.google.android.gm.layout=600
com.google.android.apps.docs.dpi=240
com.google.android.apps.docs.layout=600
com.noshufou.android.su.dpi=240
com.noshufou.android.su.layout=600
com.noshufou.android.su.large=1
com.paranoid.preferences.dpi=290
com.paranoid.preferences.layout=600
Click to expand...
Click to collapse
Change every layout= to 360 to layout=720 and every dpi=240 to dpi=160
Change the default_dpi and default_layout to match this also

Just a small sidenode:
Found out that the sdcard binary from stock is not compatible since version 4.2.1. Have to use the one from CM10.1.
Also vold mounting looks at /etc/fstab.vold instead of /etc/fstab.ArchosDeviceID.vold.
Now there are permission failures
Looking further then...

sdcard
Quallenauge said:
Just a small sidenode:
Found out that the sdcard binary from stock is not compatible since version 4.2.1. Have to use the one from CM10.1.
Also vold mounting looks at /etc/fstab.vold instead of /etc/fstab.ArchosDeviceID.vold.
Now there are permission failures
Looking further then...
Click to expand...
Click to collapse
Edit See you did that already, same as you permission failures.

Re: [DEV][4.2] CyanogenMod 10.1
So if internal storage is working, revised list:
Works:
App install
Internal storage
WiFi
GPS
Video (HQ & LQ)
Audio
Not working:
SDcard
Bluetooth
Camera
This is almost a release version
Sent from my ARCHOS 80G9 using Tapatalk HD

Quinny899 said:
So if internal storage is working, revised list:
Works:
App install
Internal storage
WiFi
GPS
Video (HQ & LQ)
Audio
Not working:
SDcard
Bluetooth
Camera
This is almost a release version
Sent from my ARCHOS 80G9 using Tapatalk HD
Click to expand...
Click to collapse
does the hq and lq video cover netflix do you know?

Re: [DEV][4.2] CyanogenMod 10.1
y2grae said:
does the hq and lq video cover netflix do you know?
Click to expand...
Click to collapse
Should do, I think it worked on TV Catchup, so it should work with Netflix
Sent from my Galaxy Nexus using Tapatalk HD

many thanks to u guys working so hard!!! waiting for ur awesome rom for g9!!!

[ROM][JB 4.2.2][CM10.1] for Lenovo Ideapad K1 3G+Wifi

Welcome to the CM10.1 for the Lenovo Ideapad K1​
Legal disclaimer: I'm not responsible if you brick your tablet, or have other damages in the process.
Features:
Multi User support (max. 5 User)
WIFI
Overclocking ( max. 1,4 GHz)
GPS
Bluetooth
Camera front/back
HD video/audio
externe SD-Card
USB-Stick support
Gyro
Auto brightness (bugy)
Hardware / Software Rotation Lock
VPN Support
3G support
Home button
CWM 6.0.3.3
Install Procedure 1
You come from CM10, no wipe needed
1. Download Update and Gapps and save to SD card
2. Reoboot into Recovery Mode
3. Once in recovery, select the update file to be flashed
4. select the gapps file to be flashed
5. Reboot
Install Procedure 2
You come from a stock or other CM version
Full Wipe, all data will be gone
1. Download the nvflash and save it on your PC
2. Power down and enter APX mode on your tablet, with the USB cable connected to the PC
3. Run flash-win.bat or flash-linux.sh (depending on what your PC runs)
4. After table has booted, enter settings and select about tablet. touch 7 time on build number. Your developer option are visible.
5. Go to settings, Developer options and select Advanced reboot
7. connect your tablet to the pc and save gapps on your sd card. Or download gapps via liink.
6. Go in Recovery via long press of Power, and select "Reboot" then "Recovery"
5. Flash the gapps package that you downloaded in step 1.
6. Reboot
Downloads:
First update 3G Version or
NVFlash 3G or Mirror
First Update Wifi Version or
NVFlash Wifi or Mirror
Important. Only that Gapps version will work !!!
Google Apps alias GApps or Mirror
Current Releases (date 2013-09-26):
Wifi Version
3G Version
Bugs:
light sensor (never worked correct)
Wifi (works just with "keep Wi-Fi on during sleep, always")
Headset detection
Credits:
KHanning
Krook1
Breeder (Testing)
Koshu
and finally Codeworkx for so many tips !!! :good:
Info / Tips
- Developer settings: go in settings and select about tablet. Press 7 times on build number
Recovery Update
The Recovery will be updated with nightly version of the 18-07-2013.

Awesome work buddy !!. Downloading it. But will flash over the weekend.
Thanks for continuing work on this device.

Nice work! I've flashed it yesterday when you posted it on goo.im and it's running nice so far. Got sod but I put wifi to always on, anyways it doesn't seem to drain too much battery. Also maybe you should update the recovery as this one cause 0 folder nesting when flashing(I got emulated/0/0/0...) and this is repaired with newer recovery, I don't remind wich number. Everything else seem to be working perfectly, some little strange thing but I think it's due to CM nighlties and could be working correctly later. I'll thank you so much for keeping our device alive. Keep it going.
Edit: The recovery issue is fixed since cwm 6.0.2.3 and we got 6.0.1.1 so that's why it's nesting but that isn't dangerous or anything, it can be deleted and the data are simply at the bottom of the 0 folders tree.

kaschemme said:
Welcome to the CM10.1 for the Lenovo Ideapad K1​
Click to expand...
Click to collapse
Thank you, kaschemme! Will download and flash when I get home as my tablet does not have too much data. THANK YOU!!!
ti-pich said:
Nice work! I've flashed it yesterday when you posted it on goo.im and it's running nice so far. Got sod but I put wifi to always on, anyways it doesn't seem to drain too much battery. Also maybe you should update the recovery as this one cause 0 folder nesting when flashing(I got emulated/0/0/0...) and this is repaired with newer recovery, I don't remind wich number. Everything else seem to be working perfectly, some little strange thing but I think it's due to CM nighlties and could be working correctly later. I'll thank you so much for keeping our device alive. Keep it going.
Edit: The recovery issue is fixed since cwm 6.0.2.3 and we got 6.0.1.1 so that's why it's nesting but that isn't dangerous or anything, it can be deleted and the data are simply at the bottom of the 0 folders tree.
Click to expand...
Click to collapse
Where can I get this recovery file to flash on my tablet? Thanks! :good:

Mordred69 said:
Where can I get this recovery file to flash on my tablet? Thanks! :good:
Click to expand...
Click to collapse
It isn't made for our device yet so we can't flash it. It need to be updated and compiled from the rom source then it can be flashed so for now we have to live with this version.

Way to go!!

On goo.im for devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
"The file you requested was not found. Lets see if we can find that for you..."

Mordred69 said:
On goo.im for devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
"The file you requested was not found. Lets see if we can find that for you..."
Click to expand...
Click to collapse
There isn't nvflash folder in kaschemme. For me kaschemme/CM10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip download without any issue.

Hey, kaschemme, thanks so much for the update! I am looking forward to giving it a try, although I do use the USB Storage function a lot (it's the easiest way to copy movies onto my K1), so I might wait until after my vacation to do the update. I'd also like to see how the GPS functions are working, since I use my K1 a lot when I go geocaching. But it's wonderful to see that the K1 is still moving forward! :good:

K1Andy said:
Hey, kaschemme, thanks so much for the update! I am looking forward to giving it a try, although I do use the USB Storage function a lot (it's the easiest way to copy movies onto my K1), so I might wait until after my vacation to do the update. I'd also like to see how the GPS functions are working, since I use my K1 a lot when I go geocaching. But it's wonderful to see that the K1 is still moving forward! :good:
Click to expand...
Click to collapse
USB connection to a computer do work for me on ubuntu 13.04 better than it ever worked. I think by USB storage he is meaning USB OTG, like plugging a usb key directly in the K1 with the almost inexistant lenovo adapter.

ti-pich said:
USB connection to a computer do work for me on ubuntu 13.04 better than it ever worked. I think by USB storage he is meaning USB OTG, like plugging a usb key directly in the K1 with the almost inexistant lenovo adapter.
Click to expand...
Click to collapse
Right, USB host support (attaching a USB flash drive to the K1) is exactly what I mean, and what I use. I was fortunate enough to get one of those non-existent adapters.

ti-pich said:
There isn't nvflash folder in kaschemme. For me kaschemme/CM10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip download without any issue.
Click to expand...
Click to collapse
The problem is the NVFlash links.
The file is not at http://goo.im/devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
The file is at http://goo.im/devs/kaschemme/cm10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
Means it is inside the CM10 directory (linkage truncates whole sentence)
Thanks, ti-pich! Thanks Kaschemme!

K1Andy said:
Right, USB host support (attaching a USB flash drive to the K1) is exactly what I mean, and what I use. I was fortunate enough to get one of those non-existent adapters.
Click to expand...
Click to collapse
You are really lucky then, this is probably the only thing missing on this tablet, and that's why I'm waiting for google to release their nexus 7 full hd with a regular micro usb. Anyway, sorry I misunderstood what you said.

Kaschemme,
nvflash_CM10.1_Wifi_Kaschemme_v1.zip is corrupt. Downloaded 4 times.

Great job Kaschemme!
So far all my apps that I have reloaded are working. Thanks for your hard work.

Mordred69 said:
Kaschemme,
nvflash_CM10.1_Wifi_Kaschemme_v1.zip is corrupt. Downloaded 4 times.
Click to expand...
Click to collapse
I downloaded it, and it does appear to have the correct MD5 hash signature, but if I try to open or extract it using Windows Explorer, I also get a message that it is invalid or corrupted. However, if I use 7-Zip, it seems to open and extract with no problem. Perhaps it was built using some type of zip compression that isn't supported by the built-in Windows compression tools?

K1Andy said:
I downloaded it, and it does appear to have the correct MD5 hash signature, but if I try to open or extract it using Windows Explorer, I also get a message that it is invalid or corrupted. However, if I use 7-Zip, it seems to open and extract with no problem. Perhaps it was built using some type of zip compression that isn't supported by the built-in Windows compression tools?
Click to expand...
Click to collapse
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...

hei Kaschemme.
thanks u so much!!!
this rom run so well.. the performance got better from the previous one.
i dont found any bug yet, but i read ur first post, that there is a bug on Headset detection...
let me try when i got home
anyway, great job!
Edited :
i just try to plug my headset on my K1..
And it works well..
So up to now, i dont found a bug yet...
Cool!

Mordred69 said:
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...
Click to expand...
Click to collapse
Take a nandroid backup and try doing a clean flash (factory reset then flash), in case you did a dirty flash.

Mordred69 said:
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...
Click to expand...
Click to collapse
Would you please let me know which version of 7-zip you used to extract the files from nvflash archive?
I tried 9.20 and 9.30alpha and both give me 'unsupported compression method'
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2

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.