Develop Bugs

Jade Remix OS ROM for NEXUS 10

Hi all,
i haven't a Nexus 10 but I want to let you know that Jade Remix OS ROM is now available for flashing on the Nexus 10:
Here is the link to download the ROM: https://drive.google.com/open?id=0B6QbFTXmsda3VDhCMUU3OVg1S2s
Here you'll find screenshots and videos: http://www.jide.com/en/remixos - https://www.youtube.com/channel/UC0U64-AHqJfeAnFJ5vQnM8w/feed
Here is the JIDE forum: https://forum.jide.com/index.php?p=/discussion/601/nexus-10-rom-available-here#Head
This is the greatest "fork" Android base ROM!!
P.S.: I don't want anything, just a Thank You
ROM Installation Instructions
Want to try to flash a Remix OS ROM to other android devices? Yes! We will soon put the Remix OS ROM on the Internet for users to download and flash onto their own device. To start, we will provide the guideline and support to flash the Remix OS ROM on Google Nexus 10.
Disclaimer
Flashing Remix OS ROM on Nexus 10 requires strong android knowledge. Flashing this ROM on Nexus 10 will be at your own risk. You will have to bear responsibility for all the resulting consequences. Jide will NOT be responsible for any damage caused.
Further Note:
Unfortunately, as a startup, we lack the resources to support installation Remix OS ROM on other android devices, thus, we will ONLY provide support for the Nexus 10 device. The Nexus 10 is a touchscreen tablet manufactured by Samsung with direct support from Google. It is the second Nexus tablet. Of course, we will look forward to the support of Remix fans to share with the world about their experience on flashing the ROM on other Android devices.
Installation Instructions
The followings are the steps to install Remix OS ROM: Unlocking the device & Installing image files using fastboot
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Connect the device to the computer through USB.
4. From a terminal on a computer, type the following to boot the device into fastboot mode:
- adb reboot bootloader
5. Once the device is in fastboot mode, verify your PC sees the device by typing
- fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", try running fastboot as root.
6. From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
7. A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
8. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing image files using fastboot
1. Make sure your computer has working fastboot and adb.
2. Download images
- you should have a download link from us in the email. The information of the image zip file:
- Images Zip File Name: images_Nexus_10-5.0.2-B2015070105-signed.zip
- md5: bdb08b6a0508dd1088f177a9e19c2875
- sha1: 9d6df824ef8c32af1a3a9d89e5f870133bcdebf6
3. Unzip the downloaded zip file ( images_Nexus_10-5.0.2-B2015070105-signed.zip ) and go to the folder
4. Connect the Nexus 10 to the computer via USB.
5. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command:
- fastboot -w
9. Flash images onto your device by entering the following three commands:
- fastboot flash system system.img
- fastboot flash recovery recovery.img
- fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
- fastboot reboot
Some of the external link of this documents will link to CM website. The installation process is referenced by http://wiki.cyanogenmod.org/w/Install_CM_for_manta

You are the man!

Yea that didn't work for me, no recovery on boot to recovery just blank screen. Also stuck on remix boot logo.

Works for me. You have to fastboot -w to wipe your device, then flash at least the system and boot image through fastboot.

I didn't wipe my device ,didn't wanna lose the sdcard content. I simply did a factory reset from twrp. Question, can it be rooted with cfautoroot like normal android 5.0?

its totally a new dev rom! the best out there! Love this rom!

How to add other languages, for example, russian?

So far I'm loving this rom. The only thing is that I wish there was a way to add widgets.

For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?

For some odd reason Tapatalk doesn't work on this ROM for me.

How do we root? Anyone know?

I've found this YOUTUBE link, but didn't test yet

EddyTeddy01 said:
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
Click to expand...
Click to collapse
I'm having the same problem, did you ever figure this out?

Corvidd said:
I'm having the same problem, did you ever figure this out?
Click to expand...
Click to collapse
Why is this always a problem with N10 roms?
Sent from my Nexus 5 using Tapatalk

I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?

blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.

drewski_1 said:
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
Click to expand...
Click to collapse
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.

blkhrt13 said:
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
Click to expand...
Click to collapse
Power + Vol Up/Down boots to bootloader.
If you have fastboot, then download the TWRP img file to your computer and issue the following command in the bootloader (forget the toolkit)
Code:
fastboot flash recovery <recovery img file name>
then you should be able to get into TWRP by using the Power Up/Down buttons until you see "Recovery" aligned with the Power Button.
press Power and you should be good to go.

blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
I'm in the EXACT same situation. Fastboot and adb not working for this, but all my other android devices are working fine. Luckily I have twrp installed so I'll just flash something else then start over on a diff rom.
Edit: and of course, just like that, I restart one more time and it actually works. very temperamental i guess.

This is a great ROM with fast clean I interface. I used official manta 5.1 from Jide. Unfortunately google device manager now sees my N10 as a Linux device, and google play services will not load properly so I cannot play cloud connected games which is really sad, I will have to back to an android custom ROM..... If you don't need play services give jide a try.. Its a pretty cool concept.

I have messed up, I don't know where to turn. HTC One M8 softbricked in Bootloop.

I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.

ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img

ckpv5 said:
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Thank you for reply!
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now. It does not appear under the devices list. If I can just get adb talking with my phone everything else should be easy, I just can't figure out why it's not recognizing it.

Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
Click to expand...
Click to collapse
Gitnerd said:
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now.
Click to expand...
Click to collapse
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
Gitnerd said:
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!!
Click to expand...
Click to collapse
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img

ckpv5 said:
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Oh.. My..God..
You just saved my life, this whole time I thought fastboot utility in AndroidSDK was just a stripped version of ADB. I'm a moron!
I have TWRP up and running holy crap thank you so so so so much, you are seriously a life saver.

try this
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
Click to expand...
Click to collapse
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears again (Should be around 10 seconds), press the volume down key.... Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
4) Once you are in the bootlader, select select fastboot by pressing power key.
5)you can flash either permanent or temporary a TWRP recovery once you are in fastboot.
6)Once you are in recovery mode, you can transfer any custom rom to memory or sd card, then install it from the place you chose.
7) you can flash RUU file at fatboot mode as well.

Nexus 7 - 2nd gen: update failed to Lollipop 5.1

HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks

Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img

k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img

Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072

Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.

i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.

ROOT Elephone S7 4gb on Windows 10x64 at last!

For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!

I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk

When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?

vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success

I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?

stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!

dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look

During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...

Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)

system destroyed, when in fastboot mode and plug to the pc (device not recognised)

So, a few months ago I rooted my device with twrp and then installed magisk manager... A few days later the manager stopped working and I got tired of not being able do do nothing so I tried to unroot. I used mi flash to flash the daisy rom and it didn't work so I tried to load to the twrp app and flash through there. Didn't work either. From then on every time I boot the device it shows the message "the system has been destroyed" and Bc of that I searched for solutions. I kinda found one. I boot to fastboot mode and with the platform tools I write on the command line ". /fastboot devices" and then it shows my device. After I write ". /fastboot boot continue" and it starts booting the device and it has worked for like 2 months but 2 days ago I had to reboot my device Bc it started to freeze but when I load to fastboot mode and plug it to the pc it show a prompt saying "the device is not recognized" and the device reboots to the message "system has been destroyed". Pls help, I've searched everywhere and didn't find any solution

Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.

Os_Herdz said:
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode

0flip3 said:
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
Click to expand...
Click to collapse
you are trying to get to edl mode by typing command "fastboot oem edl" when phone is in fastboot?