Database Develop

[ROM & Kernel] Aurora 1.0.0 Beta - Tutorial now included

Please note that this ROM is intended for the S5830i only! Flash at your own risk!
If you like Aurora just press the thanks button!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Contents
Quote 1: Introduction
Quote 2: Features and Credits
Quote 3: Download Link and Installation Instructions
Quote 4: Known Issues
Quote 5: Screenshots
Quote 6: Other Information
2nd Post: Android Shell Environment Information and Tutorial​
1. Introduction
I've been working on this for a couple of months now and this is a very stable ROM that I hope you will agree, has some great features (see below). It doesn't try to act like any particular later version of Android, I've just gone for what looks best in each individual case. I am experiencing almost no force closes whatsoever and no forced reboots at all. Hopefully others will confirm the same. I have declared this first version a beta as I haven't tested it on every firmware and one person can only test for and eliminate so many bugs. It should run fine on all firmwares. I would be grateful if you could report any bugs or issues in this thread.
Click to expand...
Click to collapse
2. Features and Credits
Core System Features
Prerooted with su binary and Supersu root access management tool
BusyBox v1.20.2-linusyang - Fully working - the latest and best version.
ROM deodexed by me
Rafael.Baugis kernel E3 rev. 201212101860
Android (Bash) Shell Environment (original thread) with many great features including:Bash shell v4.1.11(2)
Custom login screen
Multi-session command history
Tab auto-completion
Colour coded ls output
Nano text editor - fully working!
Dropbear secure shell (ssh) server
adbwifi script - surprisingly it allows you to connect to adb over wifi
reboot script - reboot, reboot recovery, soft/hot reboot, power off device
remount script - easily remount /system as re-writable / read-only​AdAway hosts file - blocks advertisements - install Adaway to remove/update
ROM based on XXLI1 - Was thinking of upgrading it to latest firmware but there has been issues with that particular firmware
Apps Features
Bloatware deleted
Chrome as default browser
Total Commander as default file manager
ICS Gallery as default gallery
No-Frills CPU Control
DroidWall firewall
Latest Play Store
Slightly modded Terminal Emulator included with Bash as default shell (Hacker's Keyboard recommended)
Zipaligned all apps for optimized performance
Still 62.3MB free on /system
Theming Features
Xperia S Launcher
SkyRaider boot animation
15 Toggles and 6 Lockscreens Mod
Lidroid Preferences
Almost all icons of all apps changed for custom hand-picked ones
1% Battery Mod
Light blue right-hand status bar icons - personally redesigned some of the icons
Light blue status bar clock
Themed status bar drop-down
Jellybean menu sound
Aurora-coloured overscroll
Aurora landscape wallpaper
Other minor theming stuff
Credits
Rafael Baugis for his excellent kernel
SenseiSimple for Android Shell Environment
Alucard1989pl for 15 Toggles and 6 Lockscreens
bijoy91 for camera settings small fonts fix
UOT kitchen for some of the theming
dsixda's Android Kitchen to deodex the ROM
Anybody else that I've accidently missed out!
Click to expand...
Click to collapse
3. Download Link and Installation Instructions
Download Link (Click Here)
1. Download Aurora's zip file.
2. Put Aurora's zip file in "/sdcard".
3. Reboot into recovery.
4. If you have stock recovery, select "apply update from sdcard" and use this zip file (put it in /sdcard) to open CWM recovery.
5. Once in CWM recovery, select "wipe data / reset" > "Yes"
6. Now select "install zip from sd" > "choose zip from sd card" > "aurora<version>.zip" > Yes
7. Wait for installation to finish, press the back button and select "reboot system now"
The phone will now reboot into Aurora. The first boot will take around two minutes, during which the screen will go blank for around one minute, so no need to panic! Subsequent boots will be much quicker.
Note: When you install this ROM, you will get e3 (stock) recovery. If you need the permanent version of CWM (because and only if you have an ext4 filesystem), then simply flash Rafael's CWM boot.img after flashing Aurora's zip file.
Click to expand...
Click to collapse
4. Known Issues
An icon of an app that is stored on the SD card that has been placed on the home screen / desktop occasionally dissapears after rebooting. This is a bug in the Xperia S launcher and there is not an awful lot I can do about this personally. There are a couple of workarounds however.
Workaround 1: The obvious, move the app to the phone's internal memory
Workaround 2: Place apps stored on the SD card in a folder on the home screen / desktop and they will not dissapear after reboots.
Click to expand...
Click to collapse
5. Screenshots
Click to expand...
Click to collapse
6. Other Information
You may use and/or redistribute my work but please give me credit. If redistributing this ROM, please link to this thread.
By the way this is my first ROM, thought I'd sneakily leave that until last
Click to expand...
Click to collapse

Android Shell Environment Information and Tutorial
Android Shell Environment Information and Tutorial
You may want to read through the original thread first.
Android Shell Environment Aurora Specific Information
​
The main difference between the original version of Android Shell Environment and the one included in Aurora is that all files are stored on the /system partition except for a couple of configuration files.
Take a look in /system/sbin for the useful utilities mentioned in the original thread
Scripts are in /system/bin (along with a lot of other Android system files).
Most of the configuration files are in /system/etc although a couple are in /data/local
In Aurora, unlike the original version, there is no option to make Bash the default shell. Firstly, this causes a bootloop on the S5830i and secondly it is pretty pointless anyway because Bash doesn't load its configuration files when set as the default shell which removes much of its functionality.
The binaries htop, scp, ssh and vim have been removed because they do not work. For all of these, there are working alternatives. For htop, use top instead, for scp use rsync, for vim use nano, for ssh use adbwifi. The text editor Joe does not work properly but has been included. Either use Nano instead or if you can get it working then please tell me how you did it!
Click to expand...
Click to collapse
Android Shell Environment Tutorial​
How To Use Bash​To start Bash:
ADB: From your PC command line, type 'adb shell' <enter>, then type 'bash' <enter>. Do not type 'adb shell bash' all in one go, this will cause problems.
Terminal Emulator: Bash loads automatically.​
Command History - Press the <UpArrow> and <DownArrow> keys to scroll through your command history. Use Hacker's Keyboard to do this in Terminal Emulator.
Auto Completion - Start typing the name of a file, folder or command, then press <Tab> to have Bash automatically complete the rest of the text. If nothing happens when you press <Tab>, then there may be multiple options, double press <Tab> to see the multiple options.
For auto-completion in Terminal Emulator, I have set a default preference so that when the phone's back key is pressed it send's out the keyboard <Tab> key. Note that this means that you cannot close Terminal Emulator using the back key, you have to enter the 'exit' command. You can change this preference in the app's settings.
To leave Bash: - Enter the command 'exit'
Click to expand...
Click to collapse
How To Use Nano Text Editor​
Nano is a user friendly command line editor. To start nano and create a new file simply type 'nano'. To start nano and open a specific file for editing type, e.g. 'nano /system/build.prop'.
If you are editing on the system partition then make sure you enter the command 'remount rw' before starting nano to mount /system as re-writable.
When you are finished editing, to exit nano enter the key combination <Ctrl>+<X>. If you have modified the file, nano will ask you if you wish to save it and request that you enter a file name.
That's basically all there is to it when it comes to the basics of this program.
Click to expand...
Click to collapse
How To Use the Reboot Command​I have rewritten the original reboot script to include a couple more parameters. Reboot now accepts the following options:
reboot - normal reboot
reboot recovery - obvious
reboot hot - hot/soft/quick reboot, restarts the Android runtime
reboot off - powers off the device, alternatively you can use the command 'halt' to acheive this
Click to expand...
Click to collapse
How To Use The Sudo Command​sudo is a well known Linux feature that runs a single command as root, useful if you generally want to work as a normal user for safety/security.
An example of this would be 'sudo adbwifi on'
Click to expand...
Click to collapse
How To Enable/Disable ADB Over WiFi​Do NOT do this from ADB shell, do this from Terminal Emulator.
Enter the command 'adbwifi on'
Follow the prompts on-screen, it tells you the rest.
To disable use 'adbwifi off'
Click to expand...
Click to collapse
How To Demote Yourself To Normal User In ADB Shell​Note: Do not do this from Bash because it doesn't work, either run it before you start bash or type 'exit', run the command, then start Bash again.
By default, ADB shell logs you in as root because Rafael's kernel has an ADB 'root mod'. This is generally very handy but sometimes, working as root is not ideal because it's very easy to brick your phone. Thankfully it is actually possible to be demoted to normal user status with the following command:
'su shell'
If you wish to return to root user, enter the command 'exit'
Click to expand...
Click to collapse
How To Use DropBear Secure Shell Server​
Dropbear allows you to login to your phone's shell (i.e. like adb shell / terminal emulator) from another device such as a PC or phone using, for example, WiFi.
To start Dropbear with the password 'pickledjelly' enter the command:
/system/sbin/dropbear -A -N root -U 0 -G 0 -C pickledjelly -r /system/etc/dropbear_rsa_host_key -b /system/etc/.dbbanner
To login from another Android device you can use e.g. Connect Bot,
use ssh protocol and in the text box enter [email protected]
Replace x and y with your phone's IP address from your WiFi router (you can get this with the command 'ifconfig')
To login from a PC running Linux enter the command:
ssh 192.168.x.y
To stop the Dropbear server issue the command 'killall Dropbear'
Click to expand...
Click to collapse

gud work man......i think this rom can have great future.....

make it final.

great job dude..:good:. now trying to combined with cronmod script by styrke...(only this way to solve our internal memory issue)
well done... all working with cronmod...

Glad some like it, cheers :good:

your rom sounds great! but is there really no way to get it based on xxlk3 (ins) ?

HeathenMan said:
your rom sounds great! but is there really no way to get it based on xxlk3 (ins) ?
Click to expand...
Click to collapse
Hi HeatherMan, I have held back on upgrading the ROM to XXLK3 so far because there were issues with IMEI numbers going awol when combining XXLK3 ROMs with custom kernels. I'll look at this again at some point though.
Aurora does work perfectly fine on XXLK3 firmware though, I currently have XXLK3 UK myself.

hi. why u don't use hell_lock kernel? thats might be better.i guess so.

SemBoyHehe said:
hi. why u don't use hell_lock kernel? thats might be better.i guess so.
Click to expand...
Click to collapse
hell_lock? wtf it is pre alpha and not stable with less features, what kind of better is THAT ?!?

HeathenMan said:
hell_lock? wtf it is pre alpha and not stable with less features, what kind of better is THAT ?!?
Click to expand...
Click to collapse
hey bro. u se ' I GUESS SO' u see that many people have trouble on that ketnel like dont have imei, earphone prob n etc. that why i guesd so

I chose Rafael's kernel because it has the most features and is currently quite stable. Hells Fusion does not presently have full IP tables needed for firewalls and has no governors or schedulers other than the standard ones.
When testing the XXLK3 IMEI issue I found that it occurred in Hells Fusion kernel as well as Rafael's. I also encountered the headphone problem at one point and found that it was because I'd flashed the boot.img but did not have the kernel modules installed.

SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows

The SoupKit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Credits:
Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2

Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.​ ​
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires.
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* Dees_Troy - for Team Win Recovery
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe

Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release

I actually wish I needed this because god damn this is a sexy piece of kit.

Thanks soup
Sent from my Amazon Kindle Fire2 using xda app-developers app

Awesome. So glad to see the kf1 devs working for us over here!
I'll probably never need this, but there are MANY who will find this useful.
Thanks soupmagnet!
--
Sent from my Kindle Fire 2, CM 10.1

Wilkinsss said:
this is a sexy piece of kit.
Click to expand...
Click to collapse
Oh, I see what you did there...

soupmagnet said:
Oh, I see what you did there...
Click to expand...
Click to collapse
Well I don't need it I have adb and fastboot running fine on linux already but I still downloaded it anyways, just because I can.

Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install

I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks

2strokenut said:
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks
Click to expand...
Click to collapse
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?

soupmagnet said:
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
Click to expand...
Click to collapse
That worked like a charm! Thanks for all you do!
---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------
I hate to be such a noob, but, I got the thing rooted and now trying to install the bootloader and TWRP, this is as far as I have gotten. Hasn't done anything in about 10 minutes. I've toggled ADB.
Verifying MD5 Checksum...
blaze-stack.img: OK
Checksum matched
Installing stack...
95 KB/s (4096 bytes in 0.041s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Rebooting...
< waiting for device >
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
I exited the terminal and re-ran option 6, this is what it gives me now:
blaze-stack.img: OK
Checksum matched
Installing stack...
93 KB/s (4096 bytes in 0.042s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
failed on '/system/etc/install-recovery.sh' - No such file or directory
Rebooting...
< waiting for device >

There may be something off with the timing. In original testing on my KFHD 8.9, that was caused from the script entering the command to reboot too fast. I had the script pause for a second or two before rebooting which seemed to help (or I thought I did). I'll look into it a little further to see if I can make it work better. The error you get on the second time you run the script is because the first time you ran it, that file was renamed so it wouldn't exist the second time around.
[Edit:] Just hold the power button to shut down and then reboot while the script is sitting at "waiting for device"

Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.

empoy78th said:
Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
Click to expand...
Click to collapse
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.

soupmagnet said:
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
Click to expand...
Click to collapse
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
---------- Post added at 11:39 AM ---------- Previous post was at 11:22 AM ----------
empoy78th said:
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
Click to expand...
Click to collapse
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!

empoy78th said:
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
Click to expand...
Click to collapse
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.

3-16-2013: Fixed issue with permissions on the rootplus script

soupmagnet said:
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
Click to expand...
Click to collapse
You understood it. Good to know. Thanks!
soupmagnet said:
3-16-2013: Fixed issue with permissions on the rootplus script
Click to expand...
Click to collapse
Do I download both soupkit and rootplus for updates? Sorry for the noob question.

In rootplus, options 1 and 5 worked for me. However, on option 6, I stay at <waiting for device>. Done it twice and also held the power button to no avail.

[Universal] [Flashable] [Logcat] [Guide] So your test ROM build didn't boot

Hello all,
I've noticed the lack of a guide for pulling ADB logs for developers. Being a developer, I wanted a quick link to send people to, rather than reexplaining.
If you are looking for a GENERAL explanation on how to get a logcat, or setup your computer for pulling a logcat, look at this amazing guide here:
http://forum.xda-developers.com/showthread.php?t=2274119
Consider this guide an extension for the above thread, making an easy how-to for developers to point people to.
What this guide is NOT:
- A guide on how to pull a logcat in general
- A guide on how to setup adb on a computer
This guide is/will:
-Assume you know how to connect via adb
-Assume you have installed drivers and adb
-A way to show common users to get the logs the developers need
So I personally build for devices I don't own. A LOT. So, should it bootloop(specifically this) or not boot at all, I NEED these logs to help fix the problem. Most users are willing to do so..... as long as you teach them. So this is my one-size-fits-all guide to this.
Note: Later, I will do a write-up on how to pull kernel logs as an extension to this in the second post
To pull a logcat during a bootloop, you need to have adb permissive. This can be done several ways. I have added to the build.prop manually before but that was in TWRP and is a pain to guide users on. It's SUPPOSED to be done with the ramdisk, but I can't ask users to pull their ramdisk and edit it and reflash. So I have made a flashable zip to extract ramdisk and add a permissive adb property to default.prop
The zip will be in the downloads below, all you need to do is flash it when you see a ROM is bootlooping.
Note: Some kernels may not work with this, and it's based off of Anykernel. If the zip fails, don't worry, it has a fallback that it will add same thing to build.prop, and that should usually work.
After flashing, hook the phone/tablet up to your computer and run this in your Terminal:
On Linux:
Code:
adb logcat > ~/log.txt
That will store logcat into your home folder.
On Windows:
Code:
adb logcat > %UserProfile%/Desktop/log.txt
That will store logcat on your Desktop.
How do I stop logging?
You can either stop logging by hitting [CTRL] + C in the terminal or by unplugging device.
How do I know when to stop logging?
Usually, you can safely stop logging after about one minute for MOST problems, BUT I believe 5 minutes of logging would be the best bet to stop logging, so all the errors are caught.
How do I get the log to the developer?
You can get a log to a developer by Dropbox, Google Drive, or a file sharing site, but personally I like pasting sites like hastebin.com, pastebin.com, or paste.ubuntu.com. This is a developers/users personal preference though. Personally, I really, really like hastebin. For a pasting site, just open it in your browser and open the log with notepad or equivalent, and do [CTRL] + A and [CTRL] + C to copy the whole log, then paste onto the site. Then share the link the site gives you with the developer.
How do I get the log, when I didn't even get to the boot animation?
Usually, this is a kernel problem, and is almost deserving of it's own write-up, and instructions will be available in the second post.
Thank you all, and should you see a problem, or need more questions answered, please tell me so in replies.
Keep it cool,
Jacob(USA-RedDragon)

So your kernel didn't boot. Well dang. This can be one of the worst problems. So, I'm going to HOPE you have TWRP, since CWM is pretty much dead.
This is more advanced, because you have to use Terminal command in TWRP.
Now, don't be daunted by this, since it's terminal commands, it's quite easy.
As a general rule of thumb(there are different devices with different kernel logs, though), 3.10 kernels(pretty much anything in the last 2 years) have a log in /sys/fs/pstore/console-ramoops and 3.4 and prior kernels have /proc/last_kmsg.
You can see kernel version in Settings -> About Phone
So to pull these logs, you need to be in TWRP DIRECTLY after a failed boot.
Go to Advanced->Terminal Command and type these commands in. One will fail the other will work. Should both of them fail, restart and try to boot again, then go back to TWRP.
Code:
cp /proc/last_kmsg /sdcard/kernellog.txt
Code:
cp /sys/fs/pstore/console-ramoops /sdcard/kernellog.txt
Now you can restore your backup and boot normally. Once you've booted up, you can either share the files with Google Drive or Dropbox or whatever in Android, or you can pull them to your computer with these Terminal commands:
On Linux:
Code:
adb pull /sdcard/kernellog.txt ~/kernellog.txt
That will store log into your home folder.
On Windows:
Code:
adb pull /sdcard/kernellog.txt %UserProfile%/Desktop/kernellog.txt
That will store log onto your Desktop.
Then share log like you would in the above post

FAQs:
None at this time

when I execute the command, it says waiting for device.
I have a galaxy s5
and the monitor, my device is offline

@Gayos24 what command did you type??? OP and 2ND post show numerous commands. Nobody can help if you don't give details.
The monitor says device offline...is the screen turned on??

HasH_BrowN said:
@Gayos24 what command did you type??? OP and 2ND post show numerous commands. Nobody can help if you don't give details.
The monitor says device offline...is the screen turned on??
Click to expand...
Click to collapse
i type this command adb logcat > %UserProfile%/Desktop/log.txt
yes the screen turning on.

@Gayos24 you use that AFTER you run a logcat, there is a link in the OP on how to do that.

HasH_BrowN said:
@Gayos24 you use that AFTER you run a logcat, there is a link in the OP on how to do that.
Click to expand...
Click to collapse
yes

I flashed logcatflasher zip via twrp and connected my device. I wrote command for windows but there was no logging in the terminal

But the adb via usb need an authorization to enable,how to get pass when bootloop?
Sent from my MI 2C using XDA-Developers mobile app

Sun Shower said:
But the adb via usb need an authorization to enable,how to get pass when bootloop?
Sent from my MI 2C using XDA-Developers mobile app
Click to expand...
Click to collapse
use adbd

Gayos24 said:
use adbd
Click to expand...
Click to collapse
Thank you to answer me,is there any thread or guide can help me,I don't know how to use it.

Sun Shower said:
Thank you to answer me,is there any thread or guide can help me,I don't know how to use it.
Click to expand...
Click to collapse
just donwload the file and extract adbd in system/xbin (rom)
and the command is the same as normal logcat
sorry for my english

awsome, just awsome

what command did you type?

I am currently testing out Custom ROMs for DEVs and I cannot find how to take a Log if I cannot Boot the device or get into TWRP. With newer devices, for example, I am currently working on a OnePlus 6, with A/B Partitions. If the device does not boot on A, it is supposed to Boot on B, so with this application, how to take a Log before the device switches Partitions and Boots on the Partition that CAN Boot?

I tried the adbd archive but there is no xbin folder for me, I just put in sbin folder. I cant get a logcat from boot because it says waiting for device the code i'm trying is this one adb logcat > logcat.txt

USA-RedDragon said:
So your kernel didn't boot. Well dang. This can be one of the worst problems. So, I'm going to HOPE you have TWRP, since CWM is pretty much dead.
This is more advanced, because you have to use Terminal command in TWRP.
Now, don't be daunted by this, since it's terminal commands, it's quite easy.
As a general rule of thumb(there are different devices with different kernel logs, though), 3.10 kernels(pretty much anything in the last 2 years) have a log in /sys/fs/pstore/console-ramoops and 3.4 and prior kernels have /proc/last_kmsg.
You can see kernel version in Settings -> About Phone
So to pull these logs, you need to be in TWRP DIRECTLY after a failed boot.
Go to Advanced->Terminal Command and type these commands in. One will fail the other will work. Should both of them fail, restart and try to boot again, then go back to TWRP.
Code:
cp /proc/last_kmsg /sdcard/kernellog.txt
Code:
cp /sys/fs/pstore/console-ramoops /sdcard/kernellog.txt
Now you can restore your backup and boot normally. Once you've booted up, you can either share the files with Google Drive or Dropbox or whatever in Android, or you can pull them to your computer with these Terminal commands:
On Linux:
Code:
adb pull /sdcard/kernellog.txt ~/kernellog.txt
That will store log into your home folder.
On Windows:
Code:
adb pull /sdcard/kernellog.txt %UserProfile%/Desktop/kernellog.txt
That will store log onto your Desktop.
Then share log like you would in the above post
Click to expand...
Click to collapse
sorry but in my device wasn't have this "/sys/fs/pstore/console-ramoops" I was browse, and did not found it... only have "sys/fs/..." if I try, still work it or not?

I have a couple of questions and I'm hoping that this forum can provide a response.
1. adb logcat not found
I have a linux laptop and have installed platform tools and have used fastboot, adb sideload quite a bit. But adb logcat just does not work.
see below while inside TWRP
5x $ adb devices
List of devices attached
00ca0a5e7fe31c03 recovery
5x $ adb logcat
/sbin/sh: exec: line 1: logcat: not found
5x $ adb shell
~ # logcat
/sbin/sh: logcat: not found
whats missing?
2. When should adb logcat be run if I wanted to capture logs when my phone keeps spinning on google animation? Can i run adb logcat > foo while I'm in recovery and then reboot from recovery or is there a different method?
thanks

I was hoping that someone could respond to the right way to capture logs during bootloop.
My problem:
Trying to capture logs on a bootloop of andrid 10 pixel experience on nexus 5x.
What I have do so far?
Flashed the ROM and zip and rebooted. No logcat seen.
My specific question.
OP says this.
After flashing, hook the phone/tablet up to your computer and run this in your Terminal:
On Linux:
Code:
adb logcat > ~/log.txt
My problem is that when the phone is rebooting, adb devices does not show anything and thus adb logcat always displays a <waiting for device> message. Thus, how can any log be captured to debug the problem?

[TUT] Easily remove Amazon's firelauncher and use any launcher (NO ROOT 5.3.1)

EDIT 09/23/16
I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Thanks for your support guys, I love android!
EDIT:
I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done
I'm new to the whole Android scene, and recently I had acquired an Amazon Fire HD 8. The only complaint about this tablet is the lack of Google Play and the horrible firelauncher. There is currently no root options available for the Fire HD modles 8 & 10, so I have spent the time to develop a temporary workaround.
Please take a quick look at the developmental thread I previously created so we can collaborate to make a more efficient version of this:
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
Disclaimer:
If you plan on installing new applications/packages while this script is running you may have a hard time. Installing packages may take 2-10 minutes, or maybe not at all!
If you experience any problems you can undo everything by running the undo script attatched (unix), or by typing "adb shell ps | grep /system/bin/sh", you will see anywhere from 2-10 processes listed. For each type "adb shell kill -9 <pid>", pid would be the process ID, should be the first number you see on each line.
There is a small chance when you press the home button that it will load the regular firelauncher, do not fret, try again and it will go to whichever launcher you previously selected.
Performance may be slightly altered, if it becomes too bad to use try adjusting the script and change the interval at which it loops (set to 20 by default).
This is an alpha experiment, and I am a noob with Android so please bare with me
This is a noobish approach to disabling the firelauncher (com.amazon.firelauncher.apk), please do not judge it, this is also my first time releasing something for Android.
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Automatic Tool (easy, linux, mac only)
Step One:
Download the two script attachments:
remove_default_launcher.sh - disables amazon's firelauncher
re-endable_firelauncher(undo).sh - reverts the process, if you have any issues
Step Two:
Run the following commands to make the scripts executable:
Code:
chmod +x remove_default_launcher.sh
chmod +x re-endable_firelauncher(undo).sh
Run the tool to remove amazon's nasty launcher!
Code:
./remove_default_launcher.sh
Step Three:
The script should automatically do everything, when it's done, check your Fire. Keep pressing the home button and switching between applications until you get the "Change default launcher" dialogue, make sure you have an alternative launcher installed beforehand or else you won't have a launcher! When it's all working how it should be go to step four!
Step Four:
Simply exit out of your terminal window, do not type anything, just exit ADB. The script will continue running!
This is what a successful window looks like, whenever you have confirmed it is working, close out of the ADB window and end that process.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Manually (harder, windows)
Step One:
Open up a new ADB shell window and type
Code:
adb shell
Step Two:
Once you are in the shell window, simply copy and paste this line of code and press return. It is just a simple bash script that loops the command "install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"" which will reinstall the firelauncher repeatedly, which temporary uninstalls it.
Code:
#!/system/bin/sh
nohup
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
After pressing enter, you can watch it go to work, or you can close out of the adb window and unplug your device, it will continue to run until you kill the shell processes or reboot the device. Make sure you have an alternative launcher already installed so it can easily be set as default. EDIT: Reboot may not reset it, which is cool but could be annoying. To turn off this wonderful feature open up adb shell and use "ls | grep shell" and kill using "kill <pid>" all releated processes to /bin/shell or whatever. It may take up to a minute to reset.
If you have any issues at all please comment and I will send you a private message with detailed instructions catered to your specific issue!
If you are a dev, take a look at my unix auto-install script, it may help you figure it out yourself as well. I need someone who understands batch to help me write a windows version .
I literally spent about 45 minutes working on this noobish approach, so if you find bugs or want to modify the script, simply post in the comments your version and why you think it is more efficient. If you want to help make a dedicated and more efficient approach to this, check out the development thread here (there are alternative methods here too):
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
This appears to be a very stable system actually, I recommend everyone does this to the Fire HD tablets!
I hope this helps someone, if this helps you please give me a thanks so I know it

Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.

Pond-life said:
Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.
Click to expand...
Click to collapse
I was not sure whether it was the correct forum actually, it is stable enough to use for all versions of Fire now, so I posted for users who do not want to root their device, but hate the launcher. If you think it is in the wrong place I will remove it promptly. I actually did post this in the wrong spot.. It is in development instead... At least there will not be any flaming here
I have also noticed 6x more downloads in 1/5 of the time this thread has been posted compared to the other.

I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done

Good job on this!

glitch3yf0x said:
Good job on this!
Click to expand...
Click to collapse
No problem, hopefully I will find some more time to work on this in the future .
I am glad you like it.

nyln said:
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Click to expand...
Click to collapse
If you're still in need, I'd be happy to help port it to windows!

as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher

This is one of the best thread for Fire OS world! Can't wait for you to perfect this.
P.S: Plz, someone here port it to Windows.

Does it work on Fire 5.3.1 ?

Please message me if you want me to keep working on this. After the root I stopped.

working great. And how to restore in the laucher back?
I am in Win10

update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?

ttcontributor said:
update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?
Click to expand...
Click to collapse
I will do some work on it. I am not an android developer, so maybe i will write a python application.

nyln said:
I will do some work on it. I am not an android developer, so maybe i will write a python application.
Click to expand...
Click to collapse
It's great to hear you still have your hands on this

nerakkaren said:
as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher
Click to expand...
Click to collapse
If I am not mistaken, this will only bennefit those who have a rooted device. Fire 7 and HD 8 got updated via OTA removing my root. I am now working on a better way right now .
Please PM or Thank me if you're interested in this, it'll come out faster if I know people are waiting

I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
Thanks for your support guys, I love android!

Here is a teaser of my application:

[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher

ahac85 said:
[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher
Click to expand...
Click to collapse
You are already inside adb shell, type exit then type it again silly

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.