Database Develop

It is simply ridiculous that HALF of the Nexus One RAM is unusable in stock...

...so I am compelled to root. ALL I care about is unlocking that other 256 (himem, I think it's called) for use and apps2sd would be nice but not necessary. Any other practical enhancements would be welcome. I'm using build ERE27. So which ROM fits that description best and where are the easiest instructions with links to download? I have been all over this and other sites and there are so many tutorials and none seem identical. Try Youtube and you know what you get? The most popular root tutorial (by far) flat out tells you from the start "This is not for beginners". Well, where the **** is the one for the beginners? I've jailbroken Iphones and flashed ROM's on to WM devices but I've never seen a more convoluted method to implementing a ROM replacement for a phone. Step by step (with backup reminders at critical times during process) would be great.
For example (from CyanogenMod):
Before continuing, you should first copy all the necessary files to your SD Card. Doing so will make the entire process much easier and faster.
Files you will need:
Download the latest release of CyanogenMod for the Nexus One and the Google Addon from http://forum.xda-developers.com/showthread.php?t=623496
Download the latest release of Amon_Ra's Nexus One Recovery Image from http://forum.xda-developers.com/showthread.php?t=611829
Rename Amon_Ra's recovery file "Recovery.img", and copy all three files to the root of your SD Card
Click to expand...
Click to collapse
I'm sorry, did you not just provide me with 2 files to download? Where does the third come from? And why does every "Link" lead to a full page with 3700 more links rather than just a freaking file to download??
Even Droiddog uses a Mac during the process because a PC would have been far too convenient for the masses (Plus I don't want the Desire ROM-too borky).
Preparing myself beforehand (going through the motions of the root without rooting) led to me opening 7 windows instead of direct file downloads. 7 Windows. 7. Does it really have to be this arduous?
I'm sorry for the frustration but deciding to root was suppose to be the hard part. Now I'm just overwhelmed with the unnecessary difficulty of it all. In truth, I'll probably be posting "thanks" from a rooted N1 by tomorrow and wondering what was so hard about all of that.......or I'll be crying over a $530 brick in my hands.

I believe Cyanogen mod (latest version in the link) includes the himem by default, just install that and you'll get the more available RAM (unless there is more steps to the process), I do not use Cyanogen.
Please note this is not the iphone OS we are dealing with here, things will not be as simple as a button press.. I honestly do not know what a "noob guide" is when it comes to Android, it all seems so straightforward to me... If I rooted my G1 and I'm only 13, not even being a nerd at that (wouldn't care if I was though..), I would imagine it not being hard for anyone..

At least the ram thing can be fixed with an ota. It looks like the multitouch problem is hardware. I feel like the ram, choppy scrolling, weird picture quality and image issue should really be solved by now by official update. I can see stringing us along for software upgrades like cupcake, new market, etc...but software fixes should be released asap. Any eta on the nexus 2?

DMaverick50 said:
At least the ram thing can be fixed with an ota. It looks like the multitouch problem is hardware. I feel like the ram, choppy scrolling, weird picture quality and image issue should really be solved by now by official update. I can see stringing us along for software upgrades like cupcake, new market, etc...but software fixes should be released asap. Any eta on the nexus 2?
Click to expand...
Click to collapse
Choppy scrolling is just that launcher2, and has nothing to do with the actual phone hardware which is a good thing. I went back to an older 2.0 launcher that is MUCH MUCH faster with continuous scroll.
I will switch if continuous scroll is added to launcher2, but yeah that choppiness stinks

It's a bug the iPhone had its bugs too. One of the great things about rooting your phone is not having to wait for Google to fix bugs the devs here do it nice and quick. I waited a month then rooted my phone and I am happy I did.

Prod1702 said:
I waited a month then rooted my phone and I am happy I did.
Click to expand...
Click to collapse
Does the extra 256 of ram make a noticeable difference in the overall speed and experience of the device (you should know having gone a month with stock on it)?

I didn't know CM rom unlocked the RAM you are talking about. I thought we were still waiting on an update from google for that.

jz9833 said:
I didn't know CM rom unlocked the RAM you are talking about. I thought we were still waiting on an update from google for that.
Click to expand...
Click to collapse
Is this true?

CM mode unlocks a good upgrade portion of the ram, for example with 10 apps Open I used to have 60 or less MBS left of ram, after CM upgrade with Kspec theme, i have 10 similar apps open and have 200+mbs of ram left, dont believe me? I actually made a video while still pretty shocked, check it, might as well rate and sub. I think I had 230+mbs while 10-12 apps running
www.youtube.com/user/exclusivegslick = my only video.

Ok to answer a few of your questions:
Does CyanMod include more ram? YES. This bump up in ram is included in the Kernel, and all of the newest roms have this including the undervolted/overclocked kernel's as well.
You get about 400mbs after the free up.
The Three Files:
Google had to go after Cyanogen so he HAD to seperate "google apps addon" from his mod. OTHER ROMS will include Google apps in most cases. So CYanogenmod = 2 files.
Ok here is a quick summary that will hopefully help the other guides make more sense. USE THE OTHER GUIDES STILL this is a conceptual map.
1) Install Android SDK to your COMPUTER which gives you ADB and the windows drivers. The drivers can also be downloaded via another thread. Search drivers/sdk drivers/adb drivers etc..
2) Download/install Fastboot to your COMPUTER
3) Download Amon Ra Recovery 1.6.3 to your Fastboot FOLDER on computer
4) Download CyanogenMOD 5.0.4.1 to the ROOT(VERY TOP LVL) directory of your SD CARD.
5) In same post, Download Google APPS 36ERE thing to ROOT of your SD CARD.
*This gives you all of the proper stuff. Make sure you get ADB SDK drivers loaded I stumbled here and wasted a couple of hours*
6) Unlock bootloader via fastboot. This is a command given from your Computer in DOS prompt in the folder you created with fastboot stuff. Your phone is connected and you are in the BOOTLoader. READ the guides for exact directions or the androidandme video, or countless other things.
7) Install Amon Ra's Recovery while still in FASTBOOT from a command via your computer. Follow guides or even first post on Amon Ra's Thread.
8) Now that you are unlocked. Go into RECOVERY which is done via the bootloader. Guide will give exact direction.
9) **** MAKE A NANDROID BACKUP **** just get in the habit. It is your FAIL SAFE. This in theory makes a nandroid backup of your "stock but unlocked" setup. I always "RE" nandroid backup before making changes or when I "Like" my setup. Command is in recovery.
10) WIPE data via recovery command.
11) FLASH from ZIP - pick Cyanogenmod5.0.4.1 (file you dl'ed to your sd card)
12) Flash from ZIP - GAPPS(googleapps) (file you dl'ed to your sd card)
REBOOT the phone. VOILA. Your done.
Important notes. If you decide, IFFFF, to update the radio. NEVER EVER EVER EVER pull the battery. MD5CheckSUM the radio download. and Repeat NEVER EVER EVER EVER pull the battery until the radio is entirely installed. It can take awhile. This is how you BRICK your phone.
Anyways. that is a real high lvl overview but maybe puts things in perspective easier.

btw you actually have less than half of the total RAM & ROM usable on a stock n1.
I would love to post a cyanogen guide...but haven't rooted yet. I believe he has a wiki with steps too.

britoso said:
btw you actually have less than half of the total RAM & ROM usable on a stock n1.
I would love to post a cyanogen guide...but haven't rooted yet. I believe he has a wiki with steps too.
Click to expand...
Click to collapse
Same here. I'm temped every day to root and unlock the benefits, but I don't know if it's worth voiding my warranty :\

I know what you mean with the "this is not for beginners", it was annoying because, even cyanogen had to unlock his first android phone some time. I followed that guide anyway, after doing as much research as possible. It didnt work though, i could not go straight from unlocking the bootloader to installing amon_ra's recovery, i had to install superboot first. I was hoping for a 30 minute root job, but it ended up taking about 4 hours all up.
I think the stock android kernel is .29 Which only recognises 256mb ram, cyanogen's mod is on the .32 then the .33 kernel which is a highmem kernel, by flashing cyanogenmod you are automatically unlocking the extra ram, no other work is required.
Also, i would suggest sticking with the ERE27 radio, i personally have no problems with reception with it, also if you don't flash the radio, your chances of bricking your phone are very very very low. If you want to do the radio, you can flash it later, when you are more experienced.

seanowns said:
The Three Files:
Google had to go after Cyanogen so he HAD to seperate "google apps addon" from his mod. OTHER ROMS will include Google apps in most cases. So CYanogenmod = 2 files.
Click to expand...
Click to collapse
I downloaded the Android SDK
2) Download/install Fastboot to your COMPUTER
Click to expand...
Click to collapse
Where is fastboot?
Do I have to do this? : (from Cyanogen's Wiki)
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others) Latest windows version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may have changed. (sorry I don't know how to format this correctly!)
Run C:\AndroidSDK\SDK Setup.exe
If it gives you an error go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
I have Amon RA Recovery Image.
4) Download CyanogenMOD 5.0.4.1 to the ROOT(VERY TOP LVL) directory of your SD CARD.
Click to expand...
Click to collapse
Please go to the Cyanogen Page and tell me where that is. The only link that states CyanogenMOD 5.0.4.1 will lead to another tab opening with the exact same page as the one you just left. Check for yourself: http://forum.xda-developers.com/showthread.php?t=623496
5) In same post, Download Google APPS 36ERE thing to ROOT of your SD CARD.
Click to expand...
Click to collapse
Is this the file underneath the CyanogenMOD that is named Google ION? It does the exact same thing that the CyanogenMOD file does when you click it. Re-opens that same page in another browser.
I have no problem following the instructions once there is a clear link to the files one actually needs to complete this process. I'm not trying to be difficult, the ability to root to Cyanogen on xda developers is, right now, broken.

whodatfever said:
I downloaded the Android SDK
Where is fastboot?
Do I have to do this? : (from Cyanogen's Wiki)
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others) Latest windows version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may have changed. (sorry I don't know how to format this correctly!)
Run C:\AndroidSDK\SDK Setup.exe
If it gives you an error go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
I have Amon RA Recovery Image.
Please go to the Cyanogen Page and tell me where that is. The only link that states CyanogenMOD 5.0.4.1 will lead to another tab opening with the exact same page as the one you just left. Check for yourself: http://forum.xda-developers.com/showthread.php?t=623496
Is this the file underneath the CyanogenMOD that is named Google ION? It does the exact same thing that the CyanogenMOD file does when you click it. Re-opens that same page in another browser.
I have no problem following the instructions once there is a clear link to the files one actually needs to complete this process. I'm not trying to be difficult, the ability to root to Cyanogen on xda developers is, right now, broken.
Click to expand...
Click to collapse
Cyanogen has moved the download to the CyanogenMod web page.
If you have sdk, and fastboot, on you machine and you have already put on amon-ra recovery, then you should be set to go.
Go to Cyanogen Mod.com and click the link to download the latest stable release. If you are in the US. I recommend that you get the new ERE36B radio. You should flash it as well. Just read up on flashing radios and plug in your phone, dont pull the battery during the radio flash and always md5sum a radio image no matter what. The radio is the only area where flashing has the potential to be dangerous.
Good luck and welcome to the Cyanogen World, you will never go back!

Gr8gorilla said:
Cyanogen has moved the download to the CyanogenMod web page.
If you have sdk, and fastboot, on you machine and you have already put on amon-ra recovery, then you should be set to go.
Go to Cyanogen Mod.com and click the link to download the latest stable release. If you are in the US. I recommend that you get the new ERE36B radio. You should flash it as well. Just read up on flashing radios and plug in your phone, dont pull the battery during the radio flash and always md5sum a radio image no matter what. The radio is the only area where flashing has the potential to be dangerous.
Good luck and welcome to the Cyanogen World, you will never go back!
Click to expand...
Click to collapse
What is the difference between the Cyanogen's N1 Addon which I am getting from this tutorial:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
and the ROMS available on this page (and which one do I download. There's a dozen!)
http://www.cyanogenmod.com/downloads/rom
Where do I download the radio and why is ERE36B better in the USA? A poster above said I should stay with the one I have (27).

addon - vs mod
whodatfever said:
What is the difference between the Cyanogen's N1 Addon which I am getting from this tutorial:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
and the ROMS available on this page (and which one do I download. There's a dozen!)
http://www.cyanogenmod.com/downloads/rom
Where do I download the radio and why is ERE36B better in the USA? A poster above said I should stay with the one I have (27).
Click to expand...
Click to collapse
The add-on was what Cyanogen made before google released the source code for android 2.1. It is not a full custom rom.
The ROM's ie. 5.0.4.1 is all the Cyanogen tweaks, highmem etc. 360 degree rotation (left right and upside down if you enable it) and all sorts of stuff.
You really should try both radios and see which one works better for you. Some people have better results with one and some the other. I have the best continuous 3G/HSPDA signal with the ERE36B radio.
On Cyanogen mod forum, go to nexus one and there is a link to get the latest stable ROM 5.0.4.1 that is what you want. You have to also download the Google add-on.
Cyan used to include them but got a nice letter from google telling him he was not allowed to "optimize" their stuff. So he puts it in a separate package as is, and you have to flash it after you flash his rom to get the google apps.
Google apps will be called: gapps-passionERE36B(2) or something very similar.
I am willing to answer any questions you have just send me a pm.

andythefan said:
Same here. I'm temped every day to root and unlock the benefits, but I don't know if it's worth voiding my warranty :\
Click to expand...
Click to collapse
there is a thread here about your warranty and as long as you have a problem that is a legit hardware defect HTC has been replacing them, dust under screen bad battery, and a few other things.

GR8Gorilla. Thank you for all of this. It was a convoluted mess trying to decipher some of the tutorials. I am very grateful and am starting the process in a few minutes. I'll let you know how it goes and thank you again.

whodatfever said:
GR8Gorilla. Thank you for all of this. It was a convoluted mess trying to decipher some of the tutorials. I am very grateful and am starting the process in a few minutes. I'll let you know how it goes and thank you again.
Click to expand...
Click to collapse
Remember if and when you flash the radio, plug in phone, and whatever you do, do not pull the battery while it is doing the radio. That is the biggest NO NO. It can make a nice nexus One paperweight. As long as you dont pull the battery you will be fine. I have flashed mine about 4 or 5 times....and I have flashed roms about 1000 times.
The phone is going to reboot a couple of times during a radio flash, be patient.

[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

[DUAL-BOOT][RECOVERY] Ouya Boot Menu for Support of Kernel Image Chain-loading

Hello everyone! Just like others here, I've been somewhat spooked by our inability to enter Ouya's Recovery partition at the earliest stage of booting, meaning a bad flash of the Boot partition would leave the device inoperable. When I heard that Ouya's stock firmware updates were possibly bricking a few units out there, I decided to block updates on mine and see if I could transform the Boot partition such that it would become a logical extension of the bootloader. What I ended up with is something close to the "Ouya Safe Recovery" project, where a user should only need to flash Boot one additional time, along with chain-loading support as well.
Chain-loading in this case refers to the booting of ROM kernel images that reside as regular IMG files under the /sdcard and/or /system filesystems. With this capability it is possible to choose an image to run when the Ouya turns on. As an example, one may wish to set up a 2nd/test kernel+ramdisk image to use with your installed ROM, or he may wish to run Tuomas Kulve's Debian project from time-to-time without having to set up the USB cable for Fastboot mode. When dealing with distinctly different ROMs (not just alternate kernels), only one of them may install to the Ouya's built-in storage (e.g., /system); others must have been designed/created to use external storage.
An image for the Recovery partition is available along with the Boot. The former may be helpful if you wish to try out the boot menu before performing the flash of the Boot partition, or are generally okay with bouncing to Recovery before invoking a chain-load. Either of these may be tested from Fastboot mode, but do note that a successful chain-load requires that the image actually be flashed to the Ouya. (Otherwise it just reboots.) The ClockworkMod (CWM) recovery application is available on both images and is accessible from the boot menu.
Additional Information
There are a few things to consider when deciding if this approach makes sense for you:
- Users of the "Ouya Safe Recovery" project may want to stay put unless the dual-boot aspect is of interest. If so then it would be cleanest to choose my Boot image; the Recovery partition (your ROM image) could be left alone.
- The images here are not compatible with Ouya's stock firmware, due to the auto-update nature of Ouya's ROM. Either your flashed Boot image would get overwritten, or an installed non-Ouya Recovery might cause that update to hang. Therefore, you should be prepared to switch to one of the ROMs here at XDA. If you're currently on stock and don't want to switch right away, that's fine; we'll go over how to block updates for the time being.
- The Ouya CM10 ROM is nice in that it provides the IMG file separately, allowing us to handle it as we wish. However, the other ROMs end up placing their boot.img in the main ZIP. This is standard practice for other devices, but we need to be careful ensuring our Boot partition doesn't get reflashed as part of the ROM installation. Therefore, it would be necessary to investigate repackaging the ROM with an alternate updater-script prior to installation. See my StockPlus post on page 2 for more. (This shouldn't affect those who've opted for my Recovery image.)
This feature is based on CWM's initial ramdisk, and includes a new boot menu application that comes up prior to CWM itself. Basically, CWM shows up later if the menu application exits for any reason. The Ouya stock kernel (561) has also been compiled with HDMI's copy protection turned off, and includes two patch sets:
- KExec-HardBoot is the key to chain-loading on our platform. It overcomes standard KExec's lack of hardware reset (and thus failed execution) by triggering a reboot in the middle of the preparation of the new kernel. This ingenious system has been developed by Tasssadar and others over in the Nexus forums. (Be sure to enable CONFIG_TEGRA_HARDBOOT_RECOVERY if interested in compiling a Recovery kernel.)
- HDMI visual stability has been improved with a little hack of mine: a significant relaxing of a timer in the driver. (The latest Android source has corrected the instability with a significant design change, but my hack seems fine enough for this project.) Also picked up specific Android fixes in the area of Framebuffer double-buffering, as that needs to be working for CWM usability.
Installation
If you're on Ouya's stock firmware, then you should make sure that any future updates do not get applied. There is a project here ("Mod Collection For Ouya") that should help. I personally side-loaded the Baxy custom launcher to avoid Ouya's update environment. It is also likely necessary to stay out of the Ouya/Discover store if going the custom launcher route as I believe the store app can trigger an update.
At this point you can download your chosen image (Boot or Recovery) and unzip to get the IMG file. Boot your Ouya to a working Root/BusyBox environment (ROM or Recovery), and then transfer the IMG to the Ouya. (An example using ADB would be "adb push boot102513.img /sdcard/boot102513.img".)
Bring up the Ouya command prompt (e.g., "adb shell") and run these commands to get started:
su [command not present on CWM - that's okay]
cd /dev/block/platform/sdhci-tegra.3/by-name
ls
You should see the various 3-letter partition names from that last command. Your command prompt should also contain the "#" character to denote root-level access. This next step will save off your current ROM image, both because we may end up overwriting it, and because the saved file will end up as your main bootable kernel for the chain-loader. Run:
cat LNX > /sdcard/kernel.img
(If configured for "Ouya Safe Recovery," then replace the preceding "LNX" with "SOS".)
We are near the flashing stage. Check to make sure your Ouya has a reliable source of power, preferrably from an uninterruptable power supply. Recall that a bad flash of my boot image can leave the device inoperable, but I feel the risk is very low provided the following directions are heeded. Fortunately the flash process only takes a few seconds.
For the Boot image option, verify by running:
md5sum /sdcard/boot102513.img
Do not proceed unless you get "e4b1b1ad553e55ad0b2ce3fb8f5bf623".
Again for the Boot image option, flash to the Ouya by running:
dd if=/sdcard/boot102513.img of=LNX
For the Recovery image option, verify by running:
md5sum /sdcard/rcvy102513.img
Do not proceed unless you get "dda0811a7e8e82a7d4ad3fa4c3ae35e4".
Again for the Recovery image option, flash to the Ouya by running:
dd if=/sdcard/rcvy102513.img of=SOS
You may optionally verify (post-flash) by running "md5sum" on the partition name. Finish up with these commands:
sync
reboot
Usage / Configuration
The menu should come up, defaulting to "kernel.img" for the Boot image and "CWM" for Recovery. That default will then launch after ten seconds of inactivity. You may also briefly press the Ouya power button during the wait to advance through the options. The option list is 1) kernel.img, 2) kernelA1.img, 3) kernelA2.img, 4) CWM, and 5) Recovery Partition.
The defaults from above should be fine for most everyone, but it is possible to fine-tune them. An optional configuration file (/sdcard/bootmenu_b.cfg for Boot, /sdcard/bootmenu_r.cfg for Recovery) may be established to specify the default menu entry as well as the inactivity timeout. As an example, the following command would make Recovery start kernelA1.img after five seconds:
echo "2 5" > /sdcard/bootmenu_r.cfg
It is hoped that the menu would never hang. If it does, then waiting a full minute should allow CWM to start. Otherwise, it may be necessary to attach a wired/USB keyboard and type in the Alt-SysRq-X sequence, similar to Ctrl-Alt-Delete on a PC. The sequence might have to be done early on in the menu startup process, and should blink the Ouya light and place it in Fastboot mode.
The menu may unexpectedly place you in CWM, which would indicate an issue with a chain-load. The reason may be due to a missing or corrupt IMG file. Otherwise you should be able to determine why by checking /tmp/bootmenu.log against the attached source code.
---
I hope this project will be of help to others!
An additional support forum that everyone should be able to post at is available: http://forum.xda-developers.com/showthread.php?t=2450711.

Wow, really great. Thanks a lot for your effort
Gesendet von meinem One X+ mit Tapatalk

nchantmnt said:
Wow, really great. Thanks a lot for your effort
Click to expand...
Click to collapse
My pleasure, nchantmnt. Hope your new Ouya is helping you feel at home!

Yes im happy it already arrived, but after a second miscarriage and lots of stress because of a lawsuit with our neighbour i didn't have time nor nerves to play or code. Seriously this year sucks
Gesendet von meinem One X+ mit Tapatalk

nchantmnt said:
Yes im happy it already arrived, but after a second miscarriage and lots of stress because of a lawsuit with our neighbour i didn't have time nor nerves to play or code. Seriously this year sucks
Click to expand...
Click to collapse
Gosh, I'm very sorry to hear that. Do think ahead to the upcoming holiday season, and may it be a time to reflect and anticipate a fruitful 2014.

@Hal9k+1 - THANK YOU!
I was so nervous flashing CWM and StockPlus as there is no real way to fix things if something goes wrong. This should give people more confidence when flashing their Ouya.
I understand the process using ADB...my question is: can this be used from CWM somehow?
PS. I assume new kernel will always be flashable from CWM, the hack does not require 561 specifically.

Ipse_Tase said:
I understand the process using ADB...my question is: can this be used from CWM somehow?
Click to expand...
Click to collapse
Hi Ipse_Tase - I do hope the feature will be helpful to you and others.
As I think about your question, I suppose I could have have created a ZIP that would have been installed by CWM. Similarly I could have worked through some form of installation shell script. But for an important operation such as flashing, I prefer the one-at-a-time approach of the interactive shell.
Note that CWM does have an ADB service running with it. Your Ouya would show up as a different device while in CWM, so you'd need to enter Device Manager (Windows) and point the unknown device to the same ADB driver as used for the main ROM.
Alternatively you could skip ADB for this Ouya Boot Menu installation and set up an SSH server on your main ROM. I personally have installed "SSH Server" (Ice Cold Apps). I recall two screens to set up (does require the trackpad in cases), where I enabled automatic start on both, and also set the port number to 2222. After an Ouya reboot I had SSH/SCP capability and could use PuTTY/pscp from Windows.

Hal9k+1...fast reply, thank you.
Just to put my ever-so-senile brain at ease: so I run StockPlus 519r1, and WHILE in the ROM, I start ADB and follow your instructions .
OR...I enter CWM, make sure I get the right ADB drivers installed for THAT instance and go from there.
For a developer, I'm sure it's easier and more familiar to run ADB commands - for people like me (5%-over-the average-user) a CVM option to flash a zip and do all this would be more in-line with the abilities to hack.
I have rooted 4-5 devices so far and the only time I type any ADB commands is at root/unlock time - sometimes not even then (Nexus 4 and the Root Toolkit).
So if you ever consider creating a recovery flashable file, it would help many. Probably not me, as by then I would have done the ADB trick

Sounds like great work! I was hoping to implement something like this myself, but I haven't made any more time for OUYA-related development in a while (due to positive life events/busyness)
I will definitely take a look at your work when I have time!
~Troop

Ipse_Tase said:
Hal9k+1...fast reply, thank you.
Just to put my ever-so-senile brain at ease: so I run StockPlus 519r1, and WHILE in the ROM, I start ADB and follow your instructions .
OR...I enter CWM, make sure I get the right ADB drivers installed for THAT instance and go from there.
Click to expand...
Click to collapse
You got it! You don't need to worry about booting to the other partition prior to flashing. That is a given partition (LNX/SOS) is no longer being accessed once the image is booted. For CWM's ADB, you'd simply point Windows to the same INF file that you originally used. Hope this helps.

StockPlus Installation
Well, I finally retired this old stock 393 ROM I was on, and moved to StockPlus 519r2. I was not able to install it the normal way given my Boot image is in place here. So I ended up modifying "updater-script" under META-INF/com/google/android, and then repackaged prior to running the install procedure. I'm attaching my changed version in case it helps anyone, and please note that it makes StockPlus the main image (kernel.img).
(You'll need to right-click to save the attachment. Once done it will need to be renamed such that it does not include the ".txt" suffix.)
The Windows "7-Zip" utility is helpful for packaging. You may start by right-clicking the downloaded ZIP, then 7-Zip --> Extract to "OUYA_[...]". Enter the newly created directory, get to the updater-script, and replace it with mine. Now back up to the area with META-INF, system, and boot.img, still in the new directory. Select all three under Windows (Ctrl+Click), right click that area, and then 7-Zip --> Add to "OUYA_[...].zip". Be sure this new ZIP is the one that makes it to the Ouya.

Still haven't tried this out yet, but I hope to soon.
I missed out on news over the holidays though and just noticed this:
Announcing Ubuntu and Android dual boot developer preview
http://developer.ubuntu.com/2013/12/announcing-ubuntu-and-android-dual-boot-developer-preview/
I'm curious of their dual boot implementation and how it compares and if we can synergize with their approach, but haven't looked into the details of how theirs works yet (its sounds like it uses a custom recovery image, and they have the ability to trigger it to reboot into Ubuntu from an Android app and vice versa, which is cool)
It'd be awesome to be able to multi-boot an Ouya ROM, an Android ROM (CyanogenMod), and Ubuntu with that kind of ease.
EDIT: This may be more our speed though: (MultiROM)
http://forum.xda-developers.com/showthread.php?t=2011403
(did you pull anything from there? Sounds like they have a modified TWRP that can flash zips to the other ROM slots, which is something I was also hoping to implement)
~Troop

Thanks, Trooper. Good to see Ubuntu moving further along in the mobile world.
I briefly looked at MultiROM since it originated from the KExec-HardBoot work, but decided not to go in that direction. The main reason is that I decided not to pursue the setup/learning of an Android build environment, but also because it wasn't clear how I'd deal with our lack of a touchscreen and lack of volume up/down buttons. I ended up creating a small application that fits within Ouya's CWM framework and starts up before CWM itself; it monitors the power button for click events and writes to the framebuffer memory region using regular Linux calls.
I'm not too concerned about the dual-boot aspect of this new Ubuntu, but the lack of touchscreen could be a hindrance if mouse/keyboard were not a viable substitute. Whether this Ubuntu is designed to work from external storage is another question, since our /system and /data would be occupied by Android. But in general I think we could boot it from my framework, and if my Boot image were selected over the Recovery one, then the Ubuntu kernel could reside in Recovery and also be bootable from the Android side with the "reboot recovery" command.
Best of luck, and hope you'll have a chance to try it all!

accidental post please delete

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)

NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM.
These devices cannot be unlocked using kamakiri.
These devices do not show up at all on USB when shorted.
After the old bootrom-exploit (amonet) we've been using for unlocking all these Fire-gadgets is closed in more recent Mediatek SOCs like the one used in the FireTV Stick 4K, @xyz` has done it again and found another bootrom-exploit.
Together we proudly present kamakiri for the FireTV Stick 4K.
Before proceeding make sure to read and understand this entire post.
Running this exploit requires a patched linux-kernel on the PC you are using.
We have put together a Live-ISO that already contains all prerequisites required for running kamakiri.
You can find the current version of the ISO at:
https://github.com/amonet-kamakiri/fireiso/releases
It can be burned to a CD or to a USB-flashdrive.
Current Version: kamakiri-mantis-v2.0.1.zip
You will need to open the device and remove the heatshield on the side without the antennas (2 square bricks).
NOTE: It is not required to desolder or force the shield off, it is just clipped onto a frame. (The attached picture may be a bit misleading, since it also has the frame removed)
You will need something for shorting (wire, aluminum foil etc.)
Boot the ISO
Download and extract the exploit package.
Open a terminal in the kamakiri directory
Run
Code:
./bootrom-step.sh
Short one of the points in the attached photo to ground (the cage of the shielding).
Ideally you want to use DAT0, since that is tiny it might be easier to short the point marked CLK instead.
It is very important that you use a piece of soft wire or aluminum foil or something similar for shorting. Don't use tweezers as that makes it incredibly easy to knock of the capacitor off the PCB and kill the board!
Connect the stick to your computer (while keeping it shorted)
The script should tell you to release the short and hit enter
Once finished run
Code:
./fastboot-step.sh
Your device will now reboot into TWRP
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).
It is still advised to disable OTA.
thanks to @hwmod for the picture
thanks to @Sus_i for providing an update.bin
thanks to @zeroepoch for developing aftv2-tools
Contributors
k4y0z, xyz`
Source Code: https://github.com/amonet-kamakiri/

There are three options for interacting with TWRP:
A mouse via USB-OTG
TWRP commandline via adb: https://twrp.me/faq/openrecoveryscript.html
Via /cache/recovery/command
Example for /cache/recovery/command:
Code:
echo "--update_package=/path/to/zipfile" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
Should you somehow end in a bootloop, TWRP contains a special boot menu that will be displayed when you boot the stick with an OTG-cable connected.
It will give you 5 seconds to hit cancel and stay in TWRP or reboot into the OS otherwise.
NOTE:This will only work if the boot-exploit is still there.

Changelog:
Version 2.0.1 (04.03.2022)
Fix Boot Menu on TWRP-Install
Version 2.0 (02.03.2022)
Update PL and TZ
Update TWRP to 3.6.1_9-0
Add support for boot-recovery and boot-fastboot
Add support for fused devices with FireOS < 6.2.8.7
Version 1.2 (20.10.2019)
Update TZ from 6.2.6.6
Add support for updating via TWRP
Version 1.1 (17.10.2019)
Add delay to properly flush data to EMMC

Yesss!!! Thanks.

Mother of GOD.
Can't believe.
And can't wait for a clean Android TV Rom.
It will be amazing since I need to use an American account to use this fire stick 4k in my country.

Complete, no issues... Great job! Thanks for the live USB, could not have made this easier!

@k4y0z I wonder why this cannot be done in Ubuntu?
I'm able to install pyusb with:
Code:
sudo apt-get install python-usb python3-usb
And then the scripts start. Is due the kernel patch?
BTW: good work I still looking at the exploit in github and looks awesome lol.

Rortiz2 said:
@k4y0z I wonder why this cannot be done in Ubuntu?
Click to expand...
Click to collapse
k4y0z said:
Running this exploit requires a patched linux-kernel on the PC you are using.
Click to expand...
Click to collapse
If you patch your kernel, there is no reason it wouldn't work on ubuntu.

I love the option to go into TWRP on boot with an OTG.... Fantastic!

Thanks to everyone involved. So happy to get some control over the 4k!

Can someone explain how to get the shield off?

rbox said:
Can someone explain how to get the shield off?
Click to expand...
Click to collapse
The heatsink and shield come off together, they are clipped on.
Start levering it up from the narrow side.

@k4y0z
Excellent work as always!!! :highfive::highfive::highfive::highfive::highfive:
Now, any chance that you can create a fastboot exploit such that there'd be no need to open the case? Same story with Fire TV2 (tank), fastboot exploit?
Keep the good stuff coming!!!

Is this something that Amazon can fix with future updates? I am holding off until we have a more refined rom..

rootuser11 said:
Is this something that Amazon can fix with future updates? I am holding off until we have a more refined rom..
Click to expand...
Click to collapse
No, the only way they can fix it is with a new hardware revision.

Does this permanently install anything? If I reboot after getting into TWRP the first time with fastboot the hacked fastboot splashscreen doesn't come back, it just boots FireOS normally with no options to boot TWRP.

Getting off the heatsink was a bit daunting especially because I didn't know there was also a sticky pad holding it on. Also spent ages trying to short the DAT0 point, got fed up and got it first time with CLK. Now I just need a rom to install!

iLLNiSS said:
Does this permanently install anything? If I reboot after getting into TWRP the first time with fastboot the hacked fastboot splashscreen doesn't come back, it just boots FireOS normally with no options to boot TWRP.
Click to expand...
Click to collapse
Everytime i boot from power off with a OTG it gives the option for TWRP. It installed TWRP recovery. From there you can install root.
Try
ADB reboot recovery

bibikalka said:
@k4y0z
Excellent work as always!!! :highfive::highfive::highfive::highfive::highfive:
Now, any chance that you can create a fastboot exploit such that there'd be no need to open the case? Same story with Fire TV2 (tank), fastboot exploit?
Keep the good stuff coming!!!
Click to expand...
Click to collapse
Unfortunately the fastboot bug cannot be used like that on the 4K or we probably would have done so from the start
I will look into the FireStick 2 when I get the time, but given the fastboot-bug is LK-Version specific and can be easily patched, I am unsure if it's worth the effort.

Michajin said:
Everytime i boot from power off with a OTG it gives the option for TWRP. It installed TWRP recovery. From there you can install root.
Try
ADB reboot recovery
Click to expand...
Click to collapse
I’m guessing I have to actually install TWRP once inside TWRP the first time? I don’t have an OTG cable so never did anything once inside the first time.

Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx)

Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! THIS ROM IS ONLY FOR THE EXYNOS VERSION !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
First I would like to thank NoKit, monich, elros34 and all the Sailfish OS porter guys who helped me to make this port.
Thank you very much guys!
News 05/03/2023: OTA to SFOS 4.5.0.18
26/10/2022: OTA to SFOS 4.4.0.72
14/07/2022: OTA to SFOS 4.4.0.68
08/06/2022: OTA to SFOS 4.4.0.64
30/05/2022: OTA to SFOS 4.3 & 4.4
22/02/2022: OTA to SFOS 4.2
16/10/2021: Waydroid on Galaxy Note4 (SFOS 4.1)
03/09/2021: OTA to SFOS 4.1
23/03/2021: OTA to SFOS 4.0
Requirements:
Before you start to download anything, please read all this through carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
Installation instructions:
1. Download all files, LOS14.1 zip, Sailfish OS zip and twrp2.8.7.img to the external SD card on the phone
2. Reboot into TWRP (Hold buttons: Power on + Home + Volume up)
At this point you should install TWRP 2.8.7 as the installation work the best with this recovery.​
Once you flashed TWRP 2.8.7, please reboot into recovery and continue the process.​
​3. Do a factory reset
4. Still in recovery, flash the LOS14.1 image
5. Still in recovery, flash Sailfish Os image
8. Reboot
9. Enjoy the latest (3.3.0.16) Sailfish OS on your Note 4 (treltexx).
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on LOS 14.1.
Downloads:
twrp2.8.7.img for Note 4 (treltexx)
LOS14.1 for Note 4 (treltexx)
Sailfish OS 4.5.0.18 for Note 4 (treltexx) - 05/03/2023
Sailfish OS 4.4.0.72 for Note 4 (treltexx) - 26/10/2022
Sailfish OS 4.4.0.68 for Note 4 (treltexx) - 13/07/2022
Sailfish OS 4.1.0.24 for Note 4 (treltexx) - 09/09/2021
Sailfish OS 3.3.0.16 for Note 4 (treltexx) - 09/10/2020
Boot logo updater for Note4 (treltexx)
kernel for lxc support (this kernel is only for sfos 3.3, the newer OTA updates all have this support!)
fix for 'Private number' calls
Problems/Solutions:
Problem: LXC container doesn't start on any of these two builds.
Solution: In TWRP install the kernel for lxc support. (This will be included into a later build.)
Problem: Incoming calls are not displaying the number only the 'Private call' text.
Solution: Install the fix for 'Private number' calls rpm. (This will be included into a later build.)
Some useful patches:
Patchmanager 3.0
More folder icons
Operator name at bottom (Stopped working on 3.3.0.16)
Silica mail (transparent background) - Well documented here
Apps from Openrepos
Apart from the Jolla store there are plenty of other, community made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
You can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Battery life
In my experience this build gives a very good battery life (I've tested with a new battery and it drops beteen 5% - 10% overnight with wifi on)
Changelog:
10.10.2020
=========
Custom (Sailfish OS) boot logo
09.10.2020
=========
Sound fix is included, it works out of the box
GPS fixed!
S-Pen works as a mouse! To make the cursor visible (thanks for elros34!) you need to install:
Patchmanager 3 from openrepos
mousetracker
amend '/var/lib/environment/compositor/droid-hal-device.conf' file, add the -plugin evdevmouse:abs:/dev/input/event3 to the end of LIPSTICK_OPTIONS. (That line should look like this:
Code:
LIPSTICK_OPTIONS=-plugin evdevtouch -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap -plugin evdevmouse:abs:/dev/input/event3
as final step apply the moustracker patch in Settings/Patchmanager, then restart the services (pulley menu in Patchmanager) or reboot, then pull out the S-Pen and use it as a stylus/mouse.
(Note: As patchmanager doesn't yet work when the default user is defaultuser, the instruction above works only on sfos 3.3.0.16 or the OTA updated 4.0.1.48. On fresh sfos 4.0.1.48 install you need to install mousetracker and manually apply the patch from it.)
28.09.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
GPS (The permanent solution will be included in a future build. Now, the workaround is (do it only once): as root delete the folder /data/system/gps and then reboot. GPS should start working)
Notification LEDs (white, green, blue, red)
Wifi
MTP
Bluetooth
Calls incoming/outgoing
Messages incoming/outgoing
Mobile data
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is the name of the sd card when it was formatted like 4B93-785B)
Home button and the Back soft button
Vibra
Pixel ratio and icons set to 2.00
Audio is routed to headphone if that presents
Camera front/rear
Video recording (only on the rear camera)
Jolla store (please skip the account creating/adding in the initial setup)
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
Sound - Please download the 'Sound fix script for Note4 (treltexx)' and save it into /home/nemo/Download, then give it executable permission and run as root or do the following:
Download the 'Sound fix script for Note4 (treltexx)' and save it into /home/nemo/Download
goto Settings/Developer tools, enter a Password and save it
start the Fingerterm app and within, issue the following commands
devel-su (press enter, then enter the password you set)
chmod +x /home/nemo/Download/soundfix-treltexx.sh
/home/nemo/Download/./soundfix-treltexx.sh
Do not work:
USB mode selection from Settings (workaround: as root run 'systemctl restart usb-moded' command)
Video recording on the front camera
Video playback in Gallery app (You can use Kodi for playing videos)
Internal SD card is not mounted to /android
S-Pen WIP
Extra 1: Change boot logo, Download warning image, Charring image and Download image for Sailfish OS like.
Simply download the Note4-Boot-Logo-Updater_by_edp17.zip from the download section and flash it with TWRP.
Important!: Once the zip is flashed, boot into recovery again, then you can boot into Sailfish OS.
To revert these images back to original:
Download the original param.bin and flash it with heimdal:
Code:
heimdall flash --PARAM param.bin
Inspired by this post
Extra 2: Desktop Linux distro install/run on the Note 4!
1. First flash the kernel from the Downloads section (in a later build this kernel will be included)
2. Install all the following packages:
lxc
lxc-templates
nemo-qml-plugin-dbus-qt5
sailfish-polkit-agent
python3-base
python3-gobject
dbus-python3
lxc-templates-desktop
qxdisplay
harbour-containers
mouse cursor support for SFOS and LXC
3. Once the packages are installed, fire up the LXC and install a distro into it (e.g. Debian SID)
On the Note 4 the harbour-containers GUI doesn't work properly. Fortunately the desktop distro installation can be done from a command line. Here are the steps:
sudo lxc-create -t sfos-download -n mycontainer
follow the instruction and set the distribution (e.g. debian) then the version (e.g. sid) then the architecture (armhf)
example command: sudo lxc-create -t sfos-download -n mycontainer -- --arch armhf --dist debian --release sid
sudo lxc-start -n mycontainer
sudo lxc-attach -n mycontainer
then within the container:
/mnt/guest/setup_desktop.sh
/mnt/guest/setups/debian.sh
4. Once the Desktop distro is installed you can start:
I recommend to use one of these scripts as they save a little time. (Note: You need sudo installed and configured for these scripts!)
Start LXC and desktop in landscape mode with mouse support: debian-mouse-landscape.sh
Start LXC and desktop in portrait mode with mouse support: debian-mouse-portrait.sh
Start LXC and desktop without mouse support: debian.sh
5. Enjoy.
6. More info about the Full linux distros on Sailfish OS.
Pictures:
{
"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"
}
Custom boot logo and other pictures:

Looks really good, have you posted the source on github or anywhere? I made a port of UT for the snapdragon note 4 and would like to make one for the exynos variant

tigerpro357 said:
Looks really good, have you posted the source on github or anywhere? I made a port of UT for the snapdragon note 4 and would like to make one for the exynos variant
Click to expand...
Click to collapse
Yes, all sources are available on github: here
Please let me know when the UT is available for this device! I'd like to try it.

calls not work

Oh, it's you again dude That is AWESOME

lee.wp14 said:
Oh, it's you again dude That is AWESOME
Click to expand...
Click to collapse
I am still chasing my n7000. Once I got that I will complete that port too. Will let you know.

usaman65 said:
calls not work
Click to expand...
Click to collapse
What variant of Note 4 is that? This port is for the European Exynos version (SM-N910C).

edp17 said:
What variant of Note 4 is that? This port is for the European Exynos version (SM-N910C).
Click to expand...
Click to collapse
test on n910c .sound also not work

usaman65 said:
test on n910c .sound also not work
Click to expand...
Click to collapse
Yeah, I installed the build again and tested these. I can confirm these do not work. Hmm, all those worked fine on all previous builds, so I am not sure why the stopped working. It seems permission issue to me. I double check and will come back with a solution. Thanks for reporting!

edp17 said:
Yeah, I installed the build again and tested these. I can confirm these do not work. Hmm, all those worked fine on all previous builds, so I am not sure why the stopped working. It seems permission issue to me. I double check and will come back with a solution. Thanks for reporting!
Click to expand...
Click to collapse
any patch possible for android apps ?

usaman65 said:
test on n910c .sound also not work
Click to expand...
Click to collapse
I have figured out a solution to the sound issue. It was me forgot to include this into this build. I will add it into a later one. Until then, please follow the instruction from the main post. (I added a script into the Download section and a comment how to apply it.)
For me, this fix solved the issues with calls and torch too.

edp17 said:
I have figured out a solution to the sound issue. It was me forgot to include this into this build. I will add it into a later one. Until then, please follow the instruction from the main post. (I added a script into the Download section and a comment how to apply it.)
For me, this fix solved the issues with calls and torch too.
Click to expand...
Click to collapse
thanks its fix now .tuch missing some time while tipping

who to install lxc for desktop linux .nothing find on google

usaman65 said:
who to install lxc for desktop linux .nothing find on google
Click to expand...
Click to collapse
How do you mean? There is instruction in the first post and there is a link to the main post of lxc (option 5).

edp17 said:
How do you mean? There is insttuction in the first post and there is a link to the main post of lxc (option 5).
Click to expand...
Click to collapse
there is a link but cannot find all required files .and how to fire lxc ...? cannot find harbour-containers .there is a link but cannot instaled it

usaman65 said:
any patch possible for android apps ?
Click to expand...
Click to collapse
No, none of the community ports have support for android apps. However you can install a desktop linux and can run desktop apps. (Although very few is touch control friendly.) Instruction for how to install a desktop distro on this device is available in the main post.

usaman65 said:
there is a link but cannot find all required files .and how to fire lxc ...? cannot find harbour-containers .there is a link but cannot instaled it
Click to expand...
Click to collapse
The link to the harbour-container is in the 'Extra: Desktop Linux distro install/run on the Note 4!' section (main post).
Although, here is how to install it, follow these steps:
download the 'harbour-containers-0.4-1.armv7hl.rpm' from this link.
open a terminal (Fingerterm)
type: devel-su (then press enter, then type your password and press enter again)
go to the library where you downloaded the rpm file
type: pkcon install-local harbour-containers-0.4-1.armv7hl.rpm (then press enter)
!Note: Before installing the harbour-container, you need to install ALL the other packages that are listed in the 'Extra: Desktop Linux distro install/run on the Note 4!' section (main post).
There is a full topic about all of this (also provided in the main post) here.

Does it work on note 4 n910v verizon?

Hola117 said:
Does it work on note 4 n910v verizon?
Click to expand...
Click to collapse
I think the N910V is not an Exynos but a Snapdragon device. This means, no, this port won't work on that. Sorry.

edp17 said:
I think the N910V is not an Exynos but a Snapdragon device. This means, no, this port won't work on that. Sorry.
Click to expand...
Click to collapse
you are correct, the 910V is a snapdragon device, its actually what I used to do my Ubuntu Touch port, BTW, I am still going to do a exynos note 4 UT port, just been busy