Database Develop

[ALPHA][ROM] Ideapad K1 ICS CM9 Port

Greetings,
Me and krook1 have been working on a CM9 port for the Lenovo Ideapad K1. This is an Alpha release as there is still a lot of work to be done. I have included instructions to either flash as an update.zip with CWM recovery, or if your still on stock you can use the nvflash package.
I have very limited time to invest to this project so if anyone would like to help please join us at freenode IRC room #ideapad-k1. The source code download link is posted below.
{
"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"
}
Working
-Touchscreen
-Wifi
-Bluetooth
-Accelerometer
-Rotation Lock
-Internal and External Storage
-Audio (thx Koshu and digetx)
-HW Acceleration (thx digetx for green overlay fix)
-CWM Backup/Restore - Fixed by using updated CWM below
Not Working
-GPS? appears to work but doesn't connect?
-HD Video Streaming
-Microphone
-Camera
Haven't tested HDMI out
Changelog
Alpha 1.6
- Fixed storage issue
Alpha 1.5
- Bluetooth fix (Audio doesn't work?)
- Full market compatibility
- Hardware buttons
- Rotation Lock Switch (Functions, but doesn't notify the SW layer)
- External SD mounted at /sdcard/external_sd and linked to /mnt/sdcard2
- goo.im app OTA update compatibility
- Synced with CM9
- New CM9 Bootanimation
- nvflash package includes updated CWM with working backup/restore
Alpha 1.0
- Initial Release
Downloads
As usual flash at your own risk
Gapps
http://goo-inside.me/gapps
CWM Package
update-cm-9.0.0-ALPHA1.6-k1-KANG-signed.zip
md5sum: 239091872daae568d7e9f1680ce49176
1. Place the update.zip on your external sdcard
2. Reboot into recovery.
3. Wipe data/Factory reset
4. Install .zip from sdcard
5. Choose the update.zip and say Yes
6. Flash gapps (optional)
Nvflash Package
K1_CM9_Alpha_1-5_nvflash.zip
md5sum: 7c34ec9242ab6ad4659b3bf310627ff4
Nvflash Windows Drivers
md5sum: 9aa3a4814ca63366329d85a22ed01f64
To boot into APX mode:
1. Power off
2. Hold down the Vol - and the Vol +
3. While holding the Volume keys down, Power on
4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode.
How to flash:
1. Extract the K1_CM9_nvflash.zip contents to a directory
2a. If using Windows, double click the "flash-windows.bat" file
2b. If using Linux, cd into the extracted directory and run either "sudo ./flash-linux.sh" or "./flash-linux.sh" from a root prompt
Source Code
http://github.com/khanning/android_device_ideapad_k1
-or-
git clone git://github.com/khanning/android_device_ideapad_k1.git
Special Thanks
The entire Cyanogenmod team and everyone that has contributed to CM
digetx
Koshu
Jon2555
All the developers that have made the source code for their device tree public. Thank you for helping to move the Android development community forward.

Thank you khanning88 and krook1 for releasing the first ICS rom for the K1!! Of course you had to upload this right before I leave for work, but thats okay! Now I have something to try out over break next week. Woohoo!!

thanks for another great rom ...even being alpha fast and smooth

Been running ice for around an hour now and no issues in performance
Glitches I've noticed
External SD shows being mounted but shows empty in total commander and es file explorer
and will not allow access
But other then the posted issues its running great
Sent from my K1 using xda premium

Just installed this, running great.
Installed Apex Launcher (smooth and fast)
link >>> Apex
Tried Chrome browser, kept crashing
Physical home button doesn't do nothing (no big deal, low priority)
Can't seem to get it connected to pc via usb port.
Storage > USB computer connection > MTP is checked.

After going through the Rom and I've noticed I can get to the external sd card if I go through. /mnt/sdcard2
But not through the regular way
I'm also going to make an update.zip for full screen nexus prime boot anim
Sent from my HTC Sensation 4G with Beats Audio using xda premium

This is excellent news.. ! Great to see progress on K1 custom ROMs!
Even though i have flashed custom roms on other android devices, i am a nOOB when it comes to K1 -- ie, should the tablet be rooted first before one can flash this ROM ? (using Root methods mentioned on other threads here?) or just do what is mentioned here ? -- Sorry.., but inputs here will help a lot of us.

djsat03 said:
Just installed this, running great.
Installed Apex Launcher (smooth and fast)
link >>> Apex
Tried Chrome browser, kept crashing
Physical home button doesn't do nothing (no big deal, low priority)
Can't seem to get it connected to pc via usb port.
Storage > USB computer connection > MTP is checked.
Click to expand...
Click to collapse
DISREGARD THE POST BELOW. BROWSER STILL CRASHES. BUT THIS ONE INSTALLS IF ANYOE WANTS TO PLAY AROUND WITH IT.
Chrome browser works. The problem is the same that all other unofficial ICS builds on other devices have. It has to do with the Device Id Check in the apk from the market. Download chrome from the link below and you are smooth sailing.
http://forum.xda-developers.com/showthread.php?t=1515900
Sent from my K1 using XDA

arjunprabhu said:
This is excellent news.. ! Great to see progress on K1 custom ROMs!
Even though i have flashed custom roms on other android devices, i am a nOOB when it comes to K1 -- ie, should the tablet be rooted first before one can flash this ROM ? (using Root methods mentioned on other threads here?) or just do what is mentioned here ? -- Sorry.., but inputs here will help a lot of us.
Click to expand...
Click to collapse
Like any Android device, flashing custom rom need custom recovery installed (ie CWM revovery).
And root is needed to install custom recovery !

Even the default browser for ICS crashed a lot. So far no problems with dolphin browser HD from market. Its fast and smooth browsing on there.

quyTam said:
Like any Android device, flashing custom rom need custom recovery installed (ie CWM revovery).
And root is needed to install custom recovery !
Click to expand...
Click to collapse
djsat03 said:
Even the default browser for ICS crashed a lot. So far no problems with dolphin browser HD from market. Its fast and smooth browsing on there.
Click to expand...
Click to collapse
I am not a NOOB, as I flash roms to my Droid Incredible all the time, but I have found the detail of instructions on flashing/root in the Idea K1 to be a bit confusing.
So any chance someone could add to the detail above, " if not rooted do install process #2 and follow these step by step"
Reads as if we can use the nvflash method, but no mention of rooting before, if that is the case great. I am looking forward to getting a new rom installed on my K1 as the stock is very buggy!

sorry, didn't see the nvFlash method. Not sur it need root or not (but think it's also needed)

quyTam:
Sorry for not getting back to you sooner. The CWM update.zip is used if you have already used my Honeycomb rom with CWM included. If you are on stock, or unsure, just use the nvflash method. There are no requirements to using the nvflash method because it reformats all the partitions. (root is not required, and it doesn't matter what build you are coming from)

ok, thanks for your reply.
didn't know the nvflahs method; it works on all Android device ?
ps: I don't have K1 but Thinkpad. Is it because Thinkpad doesn't have his bootloader unlocked, so it's not possible to use nvflash ?

khanning88 said:
quyTam:
Sorry for not getting back to you sooner. The CWM update.zip is used if you have already used my Honeycomb rom with CWM included. If you are on stock, or unsure, just use the nvflash method. There are no requirements to using the nvflash method because it reformats all the partitions. (root is not required, and it doesn't matter what build you are coming from)
Click to expand...
Click to collapse
Great to hear, is there any special needs for nvflash or is everything included in the nvflash method. I seem to remember in one of the rooting methods reading about installing drivers or related software necessary to use nvflash.

dc52317 said:
Great to hear, is there any special needs for nvflash or is everything included in the nvflash method. I seem to remember in one of the rooting methods reading about installing drivers or related software necessary to use nvflash.
Click to expand...
Click to collapse
i downloaded the nvflash zip file,.. and it talks about apx drivers.. and asks the user to have the tablet in apx mode --- where can one find that ?

arjunprabhu said:
i downloaded the nvflash zip file,.. and it talks about apx drivers.. and asks the user to have the tablet in apx mode --- where can one find that ?
Click to expand...
Click to collapse
That is exactly what I am trying to find out. I am planning on installing this when I get home in a few hours, but I am hoping that someone can add that detail to the post. I was looking a bit earlier, and found references to making sure you have these apx drivers installed for rooting etc, but no instructions.

Updated the nvflash section with the APX drivers and instructions.
Updated CWM recovery to 5.5.0.4 and fixed Backup/Restore. This will be incorporated into the next nvflash package. For now download the updated CWM recovery .zip in the 'Mods' section of the first post, and flash from recovery.

thank you..! Will try this out soon...
if i have to go back to stock rom from this ROM -- whats the process/steps?
Also, before I do this, is there a way for me to do a nandriod backup of the existing rom from within CWM ?

arjunprabhu said:
thank you..! Will try this out soon...
if i have to go back to stock rom from this ROM -- whats the process/steps?
Also, before I do this, is there a way for me to do a nandriod backup of the existing rom from within CWM ?
Click to expand...
Click to collapse
if you are not rooted and don't cwm on it already. Then just do the nvflash package instructions posted in the op.

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX
Works with HTC Unlock Method:
Tested after using htcdev.com's bootloader unlock method.
Please see the guides at the bottom of this post!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directoy, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: Sprint HTC One, T-Mobile HTC One, HTC EVO 4G LTE, One S, EVO 3D CDMA and GSM, One XL, Droid DNA, Amaze, Vivid/Holiday, EVO 4G, EVO Shift, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Will continue to test kernels as they are released to ensure compatibility!
YouTube Install Video:
http://www.youtube.com/watch?v=9aqnhFxb__k
Thanks @wwjoshdew !
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No. Use Kernel Manager!
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using the HTC method and gain root access.
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, wipe data as ROM requires and load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including WiFi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Unlock using the HTC method and gain root access.
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate the kernel zip file is contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

I actually used this app the other day I used on my evo lte a lot before s-off. Also makes flashing kernels and recoveries a breeze
Sent from my HTCONE using xda premium

This is a great app. Been using it for a while....thanks.
via phONE.

For the guys who never used it,it works great. Forgot how much it was but it was worth every dime.
Just an amazing app.
Sent from my HTCONE using Tapatalk 2

I made a video showing how to update/install custom recovery using your app! Thanks @joeykrim!
http://www.youtube.com/watch?v=9aqnhFxb__k

wwjoshdew said:
I made a video showing how to update/install custom recovery using your app! Thanks @joeykrim!
http://www.youtube.com/watch?v=9aqnhFxb__k
Click to expand...
Click to collapse
Excellent! I've added a link in the OP. Thanks!

App didn't seem to like philz_touch_5.08.5-m7spr.img wouldn't work for me, verified md5 downloaded it twice wouldn't work, then I renamed it to TWRP.img and finally it work and would allow me to hit the Flash Image button.

im0rtalz said:
App didn't seem to like philz_touch_5.08.5-m7spr.img wouldn't work for me, verified md5 downloaded it twice wouldn't work, then I renamed it to TWRP.img and finally it work and would allow me to hit the Flash Image button.
Click to expand...
Click to collapse
The error message that occurs each time you select a file that doesn't fit the naming criteria says, for a boot.img file, it needs to have the phrase "boot" in the name. Just need to add "boot" to the filename, for example: philz_touch_5.08.5-m7spr-boot.img.
Unfortunately, this limitation came about from beginners flashing incorrect files and overwriting their kernels so the device wouldn't boot. No real way around that issue other than silly filename limitations in an effort to education the users.
I test out the function real quick and the error message does come and go fairly quickly. I'll look at adjusting that so it the error message sticks around a bit longer to make it easier to read it.
Thanks for the feedback and hope that helps!

Thanks for the quick reply. This was definately worth the 99 cents. Since I can never get fastboot drivers to work on windows 8.

Myself, I prefer to adb .img's. But for a person who isnt as familiar with adb or someone who just doesnt want to, this is a great app, well worth the .99cnts. Thanks joey.
***Sent from my Super Groovy Hand Held Porno Machine***

Will this let us flash a firmware update instead of using adb? Thanks
Sent from my HTCONE using Xparent Blue Tapatalk 2

treIII said:
Will this let us flash a firmware update instead of using adb? Thanks
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, as far as I've seen HTC doesn't allow direct access to the firmware components from the standard booted Android mode. If you see any new information on how to access the firmware components directly, feel free to provide the links here and I'll research.
Thanks for the support!

[ROM] [JB][4.3.1][STABLE][UNOFFICIAL] CM10.2 build date - 02/06/2014

Built the CM 10.2 or JB4.3 ROM from CM sources.
Changelog:
The changes here are the regular updates that are made in the source and unlike custom ROMs, I do not cherry pick the changes. This is sort of a Nighlty build ROM. Building the ROM with Linaro 4.8 for Speed.
Here are the things you should do to flash this ROM
.
1. Take a Nandroid backup of your current ROM.
2. Do a factory/data reset.
3. Flash the Rom.
4. Flash Gapps.
5. Reboot.
The above is required if you are coming from JB4.2 or before.
For those with the JB 4.3 build of 09/18/2013,
1. Reboot into recovery.
2. Wipe Cache.
3. Wipe Dalvik cache.
4. Install New JB 4.3 ROM.
5. Install Gapps.
6. Reboot and enjoy.
BaseBand Unknown: If you get baseband unknown and no GSM connection,do the following:
If you have root explorer,
1. Open the RootExplorer.
2. Go to sdcard folder.
3. Go to backup folder.
4. go to efs folder.
5. copy nv_/data.bin and nv_data.bin.md5
6. go to root ("/")
7. click on "Mount R/W"
8. open efs folder.
9. paste the copied nv_data. bin files,
10 reboot.
Note: if you dont have Root explorer, download it from the playstore.
ScreenShots:
{
"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"
}
Build Date 02/06/2014
ROM
https://www.mediafire.com/?9z491koio3zh546
Build Date 01/02/2014
ROM
https://www.mediafire.com/?f468p2bifba626x
Build Date 12/30/2013
ROM
https://www.mediafire.com/?3o1bcr9yx14glzc
Build Date 12/20/.2013
ROM
https://www.mediafire.com/?pbssrae3bkg6bvk
Build Date 12/12/1013
ROM
https://www.mediafire.com/?oaoje5urrzhkad6
Build Date 12/04/2013
ROM
https://www.mediafire.com/?3iekdr9ol5f22b6
Build Date
ROM
https://www.mediafire.com/?phuc04ne1038p8m
Build Date 11/27/2013
ROM
https://www.mediafire.com/?9vca42qccgwgdui
Build Date 11/24/2013
ROM
http://www.mediafire.com/download/d60ju4orokua6fm/cm-10.2-20131124-SADANAND-vibrantmtd.zip
BuildDate 11/22/2013
ROM
http://www.mediafire.com/download/v9nto0cqmi2s5yg/cm-10.2-20131122-SADANAND-vibrantmtd.zip
Gapps
http://www.mediafire.com/?gw54qqpqw20lced
Super Su
This app seems to work better with android 4.3. Flash this from the recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=2390755&stc=1&d=1384388269
GPS:
If GPS does not work for you. Use FasterFix app to configure your location. You could you a customized gps.conf too.
Files for ODIN back to STOCK ROM.
TAR
http://www.mediafire.com/?h8hel72wrm6x487
PIT
http://www.mediafire.com/download/iqcguoi3bg39z64/s1_odin_20100512.pit
Disclaimer: Due to GPS files, that there could be intermittent E911 issues. Please be aware.
Enjoy.

The download link isn't working :/
Bugs?
Sent from my SGH-T959 using XDA Premium 4 mobile app

elfabio00 said:
The download link isn't working :/
Bugs?
Sent from my SGH-T959 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry about that.
I will upload the ROM once again and fix the link.

FIXED the ROM LINK.

Awesome do you have the modded repo?
Sent from my Nexus 4 using Tapatalk 4

jrongi1 said:
Awesome do you have the modded repo?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I don't have a repo. I can zip up the files needed to fix the gps.

jrongi1 said:
Awesome do you have the modded repo?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
sada23 said:
I don't have a repo. I can zip up the files needed to fix the gps.
Click to expand...
Click to collapse
That would be great.
Sent from my Nexus 4

jrongi1 said:
That would be great.
Sent from my Nexus 4
Click to expand...
Click to collapse
Attached a flashable zip file. This file could be flashed on any JB 4.3 ROM for VIBRANT only.
I hope the great, tireless and genius developers in this forum and others would make use of these files and develop much better JB 4.3 ROMs for us all.

Thanks man, a long awaiting 4.3 release. :thumbup:
Sent from my SGH-T959 using xda app-developers app

Installed following directions with resulting Installation Abort
Toggled verification- installed ROM following directions resulted in bootloop
Installed just the ROM resulting in bootloop.
Suggestions?

installed,
baseband unknown...
gsm is not working,tried to flash modem, still can't register on the network.

livbean said:
Installed following directions with resulting Installation Abort
Toggled verification- installed ROM following directions resulted in bootloop
Installed just the ROM resulting in bootloop.
Suggestions?
Click to expand...
Click to collapse
Try reinstating your previous ROM( non J?B 4.3). Boot up and then disable GPS. Reboot into recovery and install this ROM.
good luck.

maoten said:
installed,
baseband unknown...
gsm is not working,tried to flash modem, still can't register on the network.
Click to expand...
Click to collapse
If you have root explorer,
1. Open the RootExplorer.
2. Go to sdcard folder.
3. Go to backup folder.
4. go to efs folder.
5. copy nv_data.bin and nv_data.bin.md5
6. go to root ("/")
7. click on "Mount R/W"
8. open efs folder.
9. paste the copied nv_data. bin files,
10 reboot.
Note: if you dont have Root explorer, download it from the playstore.

sada23 said:
Try reinstating your previous ROM( non J?B 4.3). Boot up and then disable GPS. Reboot into recovery and install this ROM.
good luck.
Click to expand...
Click to collapse
Installed as suggested. Booted up fine, Everything appears to be working. I'll run it for a while and let you know.

sada23 said:
Attached a flashable zip file. This file could be flashed on any JB 4.3 ROM for VIBRANT only.
I hope the great, tireless and genius developers in this forum and others would make use of these files and develop much better JB 4.3 ROMs for us all.
Click to expand...
Click to collapse
Are you sure you uploaded the right file?
There are a few differences between the flashable fix and the rom.
Sent from my Nexus 4

jrongi1 said:
Are you sure you uploaded the right file?
There are a few differences between the flashable fix and the rom.
Sent from my Nexus 4
Click to expand...
Click to collapse
There could be some changes as I tried make a flashable zip. I think that files in zip should work. I have been testing several files and combinations. Hence the files in the ROM be different.
Let me know if the zip file does not work.
Thanks.

Feedback
he it is how I installed the rom.
1. Odin to default eclair from slimbean 4.2.2 Build 8. After boot, rooted it.
2. Flashed cm 7. 2.0 stable. And let it to settle for 5 minutes.
3. Flashed This 4.3 rom. it gave the error of wrong partition layout. flashed it again to solve it.
4. It rebooted into recovery automatically with new kernel, so I flashed 4.3 again. (if yours doesn't come to new recovery automatically then use 2 buttons combo to enter into recovery, make sure you have gingerbread bootloader).
5. Flashed GPS fix files and rebooted.
6. After 5 minutes of cyanogen logo boot animation, it successfully reached home screen.
7. Changed GPS.conf file in etc directory to my region and rebooted it. But Alas baseband disappeared. Changed kernel to Gearkernel for 4.3 and all things came to right path.
8. Used GPS status to check GPS functionality and wow it really worked. just make sure you have working internet connection.
9. Wi-Fi, Bluetooth, mobile data, everything works. except gesture typing of default keyboard. to solve this change keyboard to touchpal. you can use Swype or swift key. Battery timing seems good till now. haven't checked USB storage connection to PC yet. if anyone else have checked it please let me know.
10. overall stable and smoothly fast rom.

smokey155193 said:
he it is how I installed the rom.
1. Odin to default eclair from slimbean 4.2.2 Build 8. After boot, rooted it.
2. Flashed cm 7. 2.0 stable. And let it to settle for 5 minutes.
3. Flashed This 4.3 rom. it gave the error of wrong partition layout. flashed it again to solve it.
4. It rebooted into recovery automatically with new kernel, so I flashed 4.3 again. (if yours doesn't come to new recovery automatically then use 2 buttons combo to enter into recovery, make sure you have gingerbread bootloader).
5. Flashed GPS fix files and rebooted.
6. After 5 minutes of cyanogen logo boot animation, it successfully reached home screen.
7. Changed GPS.conf file in etc directory to my region and rebooted it. But Alas baseband disappeared. Changed kernel to Gearkernel for 4.3 and all things came to right path.
8. Used GPS status to check GPS functionality and wow it really worked. just make sure you have working internet connection.
9. Wi-Fi, Bluetooth, mobile data, everything works. except gesture typing of default keyboard. to solve this change keyboard to touchpal. you can use Swype or swift key. Battery timing seems good till now. haven't checked USB storage connection to PC yet. if anyone else have checked it please let me know.
10. overall stable and smoothly fast rom.
Click to expand...
Click to collapse
Thanks for the feedback. The change in partition does provide a warning and as you did you need to flash the rom once again. You don't need to flash the GPS zip files unless you are on s ROM that has GPS issues. This ROM doesn't have GPS issues. As you did, people have to change the GPS.conf to match their region or use faster fix app.
One again, thanks for the feedback.

Guys,
I got an email from Dropbox that my Public folder lnk has been suspended due to high volume of access and hence added a new link to download from mediafire. Hope this holds.

you are welcome.
following small problems annoy me very much.
1. enabling Ksm and zram in performance settings cause baseband unknown error. to solve it i have to uncheck them and change governor to ondemand in performance settings. then rebooting solves the problem.
2. as you know i changed kernel to gear kernel 1.0.8s, upon each boot i get annoying message of Android is upgrading, staring apps. i know it is for gear settings app builtin in this kernel being checked every time. is there any way to remove this message.
3. data of half of my user apps gets deleted upon reboot, i have to restore it from titanium backup. why this happens on every boot and only to half apps.
4. sometimes baseband changes to unknown upon boot even thoughihaven't changed any setting like zram etc.
5. you mentioned s roms have gps issue. what are s roms and how to solve their gps issue.
please take out some time to help.

OTA update for GPE 5.1 LMY47O.H9 to H10 -- TWRP

Not sure why the original GPE 5.1 thread got closed, but anyway I've created a TWRP flashable update for the LMY47O.H9 to LMY47O.H10 OTA that recently became available. It only works for clean H9 installs that are NOT rooted.
How-to and download: http://mostlyirrelevant.info/2015/10/07/lmy47o-h10-ota-update-htc-one-m8-gpe/
{
"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"
}

http://forum.xda-developers.com/showthread.php?t=2708589
Sent from my HTC6535LVW using Tapatalk

Getting an Error Executing updater binary in zip, error.
/system/bin/app_process32 has unexpected contents

/system/app/BasicDreams/BasicDreams.apk has unexpected contents
Please advise!
UPD1 Sorry, it was Philz recovery. Now I got TWRP and getting the same issue with app_process32
UPD2. It seems I have to unxpose and unroot first - but my M8 keeps rooting itself, cannot get into unrooted mode.

radeon_x said:
Not sure why the original GPE 5.1 thread got closed, but anyway I've created a TWRP flashable update for the LMY47O.H9 to LMY47O.H10 OTA that recently became available.
How-to and download: http://mostlyirrelevant.info/2015/10/07/lmy47o-h10-ota-update-htc-one-m8-gpe/
Click to expand...
Click to collapse
Thanks for the update, but it didn't work and causes an error like the post before this.
Unexpected error .... etc.

I got the same errors trying to sideload the original OTA zip through stock recovery, so it must be something in the zip itself.
Maybe a security measure to prevent installing on modded phones.

Would it be possible to post the entire H10 ROM .zip? I usually have problems updating just the OTA file. graffixnyc usually posted it but for some reason that thread got closed.
Thanks!

The issue with app_process32 seems to be related to rooted phones where /system/bin/app_process32 is a symlink to daemonsu. The question is how to unroot the phone. My one recovers rooted state itself...

sudaltsov said:
The issue with app_process32 seems to be related to rooted phones where /system/bin/app_process32 is a symlink to daemonsu. The question is how to unroot the phone. My one recovers rooted state itself...
Click to expand...
Click to collapse
Yeah sorry forgot to account for the app_process32 being modified when rooting.
I've modified the file (now v2) to support rooted LMY47O.H9 (download here: http://mostlyirrelevant.info/2015/10/07/download-update-ota-lmy47o-h9-to-h10-zip/)
Any other patch errors (i.e. not app_process32) are because you're not running a clean H9 install and there's nothing I can do about that.
EDIT: Also in case anyone missed it, there is a full H10 update zip posted here https://www.androidfilehost.com/?w=files&flid=39228, if this OTA patch doesn't work for you.

If you received the OTA notification for H10
Well, I have tried it twice (from H6 I believe to H9 and now from H9 to H10) and it worked and I did not loose any data files! I got the OTA notification and followed the following protocol (I am rooted and running TWRP):
1. Revert any app that had root access (i.e. Adblock... just revert and disable). If you have XPOSED framework you have to revert everything to stock!
2. Withing the SuperUser app (SU), fully "un-root" the phone.
3. Restart (probably not necessary)
4. Install H9 Recovery (I downloaded it from graffixnyc: http://forum.xda-developers.com/showthread.php?t=2708589) Do not forget to at least thank him!
5. Erase cache (Fastboot erase cache) just in case and Restart.
6. Install OTA :good:
7. Done! Now you have to install again TWRP via fastboot (erase cache once again, just in case...) for root access and re-install whatever you had before with root access. :laugh:
Long process but saves me a lot of headaches with data and any other errors may occur...

I uninstalled xposed. I installed v2. And... now I have kind of brick. The coloured dots moving endlessly. ((( Cleared the cache, of course.

sudaltsov said:
I uninstalled xposed. I installed v2. And... now I have kind of brick. The coloured dots moving endlessly. ((( Cleared the cache, of course.
Click to expand...
Click to collapse
Well the initial boot after clearing the cache takes a really long time of course.... But if it really and truly doesn't boot after several minutes just install the full H10 from that other thread.

Seems I have no choice but to sideload (thanks to TWRP) the full OTA H10..

radeon_x said:
Yeah sorry forgot to account for the app_process32 being modified when rooting.
I've modified the file (now v2) to support rooted LMY47O.H9 (download here: http://mostlyirrelevant.info/2015/10/07/download-update-ota-lmy47o-h9-to-h10-zip/)
Any other patch errors (i.e. not app_process32) are because you're not running a clean H9 install and there's nothing I can do about that.
EDIT: Also in case anyone missed it, there is a full H10 update zip posted here https://www.androidfilehost.com/?w=files&flid=39228, if this OTA patch doesn't work for you.
Click to expand...
Click to collapse
I updated succesfully!!
Follow those steps:
1st. Download the ROM : https://www.androidfilehost.com/?w=files&flid=39228
2nd. Copy the ".zip" to SDcard (Make sure to Backup all needed Apps and data.)
3rd. Wipe "Cache" and "Dalvik" !
4th. Install the ROM via Recovery, I used TWRP. In my case there is nothing wiped like internal SD, Data partition, BUT (Make sure to Backup all needed Apps and data.)
5th. Reboot to System
6th. If you are using Xposed you have to install the latest version (xposed-v75-sdk22-x86.zip) from this Tread: http://forum.xda-developers.com/showthread.php?t=3034811
Now enjoy!
cheers,
m_atze
But beware, all you do to your phone and it will be bricked etc. I am not responsible for. So use at your own risk!

m_atze said:
I updated succesfully!!
Follow those steps:
1st. Download the ROM : https://www.androidfilehost.com/?w=files&flid=39228
2nd. Copy the ".zip" to SDcard (Make sure to Backup all needed Apps and data.)
3rd. Wipe "Cache" and "Dalvik" !
4th. Install the ROM via Recovery, I used TWRP. In my case there is nothing wiped like internal SD, Data partition, BUT (Make sure to Backup all needed Apps and data.)
5th. Reboot to System
6th. If you are using Xposed you have to install the latest version (xposed-v75-sdk22-x86.zip) from this Tread: http://forum.xda-developers.com/showthread.php?t=3034811
Now enjoy!
cheers,
m_atze
But beware, all you do to your phone and it will be bricked etc. I am not responsible for. So use at your own risk!
Click to expand...
Click to collapse
Thanks, it's work for me.
btw the original thread is here http://forum.xda-developers.com/showthread.php?t=2706441

After multiple issues I just installed the H9 RUU unrooted from @graffxnyc, then installed the ota which popped up as soon as it rebooted.
For now I'm leaving it unrooted etc until marshmallow drops later this month.

Don't know whats the update for tho. But anyways installed. Maybe to prepare our system for Marshmallow update? Like what cyanogen did?

i'm not sure what's going on, but the update is a POS. Like sure it's a stagefright fix, but they've broken more than fixed it. Im having massive lag issues, the text windows are stuttering at times, unlocking the phone freezes it for a while and there are times where the notification sounds don't even sound off.

Sorry guys. I've had no problems at all.
This Version is woking like charm.

H10 update recovery
Could someone provide the recovery image from the H10 update?!

TWRP 3.2.0.0 Moto Z2 force [Nash]

{
"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"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10

Nice
Sent from my SM-N930F using XDA-Developers Legacy app

Woow, very nice present GREAT JOB!!!

Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!

In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.

Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.

jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.

Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:

jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.

joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it

Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good

joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)

How are you rooted

joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)

thread updated if any questions please pm me

Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!

Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk

Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?

Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly