Database Develop

Red Trackball of Death

Hello everyone,
Here is my issue :
http://forum.xda-developers.com/showthread.php?t=847499
I mostly did the same thing : a long time ago, tried 0.33 version of HBOOT, had the Black Screen, managed to fix it, but since then I have that dam RToD.
Someone I met on a forum with the same exact issue once found the solution : installing the CM, then modifying some values in the light detectors in the CM options. Eventually the RToD would stop, but the 4 softkeys would never light (as they usually do when it's quite dark in the place you are).
But that non-lighting issue was mostly nothing compared to the RToD so I always accepted it.
The point is, today I wanna try some other ROMs (like MIUI, and some French and very interesting ROMs as well) and that RToD came back to my mind as I flashed some ROM.
As the link above mentions, Amon_RA said that reflashing some LCD Nexus One misc partition would solve this problem.
First, I have a question :
You did follow the thread in your first post and flashed the Desire misc image (mtd0.img), right? I would try to :
1. unlock your bootloader so S=OFF (fastboot oem unlock)
2. get hold of an N1 mtd0.img dump with S=OFF and flash it
Click to expand...
Click to collapse
By saying S-OFF, did he do a mistake by just meaning unlocking the bootloader? Which I did a long time ago. But if he meant switching the Security to Off, well actually, I think that it's impossible on the Nexus One (some topics deal with that exploit on XDA) , so I do hope he just meant "unlock your bootloader"
Anyway, assuming that my bootloader is unlocked, here are the steps I followed :
- Since the link given by Amon_RA to download the misc.img is over, I asked to a french member of another forum who had a LCD Nexus One to do this :
Code:
su
cat /dev/mtd/mtd0 > /sdcard/misc.img
and to give me the file, which he did.
- Renamed it to mtd0.img (I think it's actually useless, but I did want to follow the exact advice of Amon_RA)
- Found a flash_image file from some forum (are there different flash_image files? May it be the issue?)
- Copied both flash_image and mtd0.img in C:\Android\platform-tools (where my adb.exe is)
- Went to that foled with the Windows CMD
- Did it with my phone on (not in Bootloader nor in Fastboot, otherwise the
Code:
adb devices
command would not return any phone ID :
Code:
adb push flash_image /data/flash_image
adb push mtd0.img /data/mtd0.img
adb shell
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Got that :
http://img825.imageshack.us/i/mtd0img.png/
But still, whatever ROM I flash, the RToD is still there. Only the CM allows me to "hide" the problem, not really to solve it.
What did I miss? Was my approach wrong?
Thanks if someone could help me with that 6 months remaining issue...

Hello,
Sorry, I don't like much to use that kind of means, but I'm doing a little "Up" cause I'm really surprised that none here could solve my issue, since we are a lot to encounter such a problem...

Hello,
Same problem.
Have tried the Amon_RA method without success.
I would appreciate any suggestions to solve the issue,
Thanks,

Root Nexus 7 from terminal, without replacing firmware or losing data

Even if you lose data, brick your device or/and throw it against the wall after reading this post
I am absolutely not responsible for anything you do to your android !
​
This procedure works on Linux (see NOTES below before).
1 - Ensure you have the latest android SDK installed on your computer, and that USB debugging is enabled on your device
2 - Backup your data with "adb backup":
adb backup -apk -shared -all -f backup.ab
(No warranty: You should also backup your sms (and paid application or application data) with something else.
Details and latest warnings here: http://forum.xda-developers.com/showthread.php?t=1420351)​
3 - Restart in bootloader:
adb reboot bootloader​
4 - Unlock the bootloader (everything will be erased, you need to confirm on your device)
fastboot oem unlock​
5 - Restart, skip configuration steps, enable USB debugging again
6 - Restore your data with adb restore:
adb restore backup.ab​
7 - Download the latest TWRP image on your computer, from the official TeamWin Recovery Project site: http://teamw.in/project/twrp2
8 - Download or push the latest CWM-superSU zipped package from eg http://download.chainfire.eu/282/SuperSU/
9 - Restart in bootloader:
adb reboot bootloader​
10 - Boot TWRP, eg;
fastboot boot openrecovery-twrp-2.3.1.0-grouper.img​
11 - Using TWRP, Install the CWM-superSU zipped package previously downloaded on your android.
12 - Reboot your device, you are set !
NOTES:
- If you need to re-root your system after a firmware update, restart at step 7 with USB debugging enabled.
- with Linux you need to:
* Run "sudo bash" first in the terminal window to enter administrator mode.
* Change to directory "android-sdk-linux/platform-tools" and prefix every command with ./
* If command "./adb devices" returns a "????? no permissions" error, restart adb server as root:
./adb kill-server
./adb start-server​

Is this not the wrong forum ?
Sent from my Galaxy Nexus using xda premium

danishprakash said:
Is this not the wrong forum ?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ditto.

Step 4 should read 'Unlock Bootloader.'

Is this not the injustice forum ?
Dispatched from my Collection Linkage using xda reward

this is good for those who have been holding out on root and don't want to lose everything. the first time i rooted i was hesistant because i lost everything. so nice post, and im sure it'll be useful to lots of people, who understand it

Um, so..
adb backup + Nexus 7 Rooting Guide
http://forum.xda-developers.com/showpost.php?p=29271179&postcount=218

on the walkthrough over in the gnex forums, users found out that you need to set a backup password in developer options, otherwise the backup would not work, does the n7 not need the password?

I just wanted to root, not problems...
My priority was to backup the stock partitions just in case - user data is a bonus i did not need..
Then I found out it was possible to start a recovery partition with "fastboot boot" while keeping every partitions untouched
Ideal to not mess up things with flashing an unsuitable or syphilitic version of a system partition downloaded I don't know where ...
I did not want to use any rootkit for the exact same reasons, plus i'm allergic to Windows...

Hi luc, don't bother he complaints - I reckon you're on the right sub-forum (Nexus 7 General : tips & tricks), and your tutorial is so clear, simple, and to the point. I got my Nexus 7 rooted pretty much straigh away.
I've sent my thanks to your posts. Much appreciated.
Just need a bit of editing - "fastboot oem unlock" should be "sudo fastboot oem unlock"
The same with "sudo fastboot boot openrecovery-twrp-2.3.1.0-grouper.img"
(without the sudo prefix, fastboot waits forever)
Now my Nexus 7 is rooted, and I can stick my 64 GB flashdisk to my Nexus 7, making its capacity 80 GB
Thanks again for sharing.

Unlocking the downloader wipes the device does it not?

sufehmi said:
Just need a bit of editing - "fastboot oem unlock" should be "sudo fastboot oem unlock"
The same with "sudo fastboot boot openrecovery-twrp-2.3.1.0-grouper.img"
(without the sudo prefix, fastboot waits forever)
Click to expand...
Click to collapse
I did not want to scare others users with linux stuff on top of page.
However linux users should read the NOTES for linux mentioned there and run "sudo bash"
Thanks for your return !

CJHolderUK said:
Unlocking the downloader wipes the device does it not?
Click to expand...
Click to collapse
You can backup before unlocking the bootloader, as described in step 2.

Would I be right in thinking this will only work using Linux? would it be possible if I ran Linux as a virtual machine in Microsoft Virtual PC? Sorry if it's a dumb question, I am rather new here.

OP - clean and nice write up, thanks.
shezzuk1 said:
Would I be right in thinking this will only work using Linux? would it be possible if I ran Linux as a virtual machine in Microsoft Virtual PC? Sorry if it's a dumb question, I am rather new here.
Click to expand...
Click to collapse
It will work from windows, just don't forget to install Android SDK. Start cmd as Admin and navigate to platform-tools
Code:
cd "c:\Program Files (x86)\Android\android-sdk\platform-tools"
All other commands will be the same and you don't need to care about Linux stuff at the end of OP post.

Don't forget that unlocking the bootloader wipes the internal SD card, too. That's part of the data partition. Read more here.

[Solved] Ubuntu / Nexus 4 / CF-Auto-Root #[email protected]&

BLUF (Bottom Line Up Front) Both the CF and SuperRoot auto-root's would give me "No such file or directory" errors in reference to fastboot when I knew damn well fastboot was present and working!
I don't have 10 posts and therefore I cannot post this in the actual CF-Auto-Root thread where this might help someone. However, If you happened to be having the same issue I had, I hope you find this.
I assume I cant post links to things either so, we'll skip that and hope people can google-along with me.
I should say that I am mostly to blame for my own issue since I read through several different rooting methods and I tried to quilt together pieces from each. Sometimes I think I'm smarter than I actually am when I should really just follow directions.
Here's how I went about it:
1. I pulled "adb" and "fastboot" from the webpud8 PPA (no issues)
2. I used "fastboot oem unlock" to unlock the bootloader (no issues)
3. I tried two separate auto-root methods and the Nexus-toolkit (NOTHING WORKED!)
My solution:
After pulling most of my hair out I began to realize the scripts were trying to reference a "fastboot-linux" file from the auto-rooter-specific files. In the case of CF-Auto-Root it was looking for "CF-Auto-Root-mako-occam-nexus4/tools/fastboot-linux". I don't know why the referenced "fastboot-linux" was throwing errors but I did know I had "fastboot" installed and that it was working fine.
I ran the two pieces of CF's "root-linux.sh" script manually, substituting "fastboot" in place of "tools/fastboot-linux".
They looked like this (It's important the CF-Auto-Root folder is extracted into the Home directory):
sudo fastboot oem unlock
sudo fastboot boot ~/CF-Auto-Root-mako-occam-nexus4/image/CF-Auto-Root-mako-occam-nexus4.img
I'm no expert (but I did stay in a Holiday Inn....once), and I can't claim this wont send you further in the wrong direction - but it finally ended hours of frustration for me!
-Jerry

[rom][android m][preview 2] nexus 5

For all those complaining insufficient information to flash Preview 2 of Android M to your nexus 5, here is the comprehensive guide to flashing the preview.
Install ADB and Fastboot to your computer
Follow this link http://forum.xda-developers.com/showthread.php?t=2588979&__utma=248941774.236267929.1403796127.1403796127.1403796127.1&__utmb=248941774.4.10.1403796127&__utmc=248941774&__utmx=-&__utmz=248941774.1403796127.1.1.utmcsr=google%7Cutmccn=%28organic%29%7Cutmcmd=organic%7Cutmctr=%28not%20provided%29&__utmv=-&__utmk=25906750
For MAC/linux
Follow this link
http://forum.xda-developers.com/showthread.php?t=2564453
Remember to head into settings > developer options and enable USB Debugging first.
download Android M Developer Preview from Google website for your specific device http://developer.android.com/preview/download.html
unzip these files to a folder you can access Desktop preferably
If your Nexus is not bootloader unlocked you should do that first.
Open a Terminal in the adb folder and type the command below then hit enter.
adb reboot bootloader
In Fastboot type:
fastboot oem unlock
Then hit enter. Follow the on-screen instructions and choose to erase the device. Wait a minute or so for it to unlock. This removes everything on your device.
If your bootloader is already unlocked, reember to wipe data before flashing. Do this by using these commands in cmd or terminal
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
How to Flash the Image
Now open the folder containing the unzipped Android M System Image file you downloaded. Type cmd in the address bar. Type the following commands posted below and hit enter. On a Mac you can open Terminal in the folder by enabling terminal shortcuts in settings. This is key for Mac users. Head to System Preferences and select Keyboard > Shortcuts > Services. Find “New Terminal at Folder” in the settings and click the box. Now when you’re in Finder, just right-click a folder and you’re shown the open to open Terminal.
Once in terminal simply copy and paste the commands below to install the Android M beta to your Nexus 5, Nexus 6, Nexus 9, or even the Nexus Player.
flash-all.bat
This will flash all of the needed files. If you are on a Mac or other computer you will need to type;
sudo ./flash-all.sh
This will push all of the files and update your device to the just released Android M developer preview beta. The files will start pushing and installing and your Nexus device may reboot and you will see an Android figure and then a moving Android logo. The logo screen may stay for a long time. Don’t unplug the device. This may last 10 minutes or longer.
It’s worth noting that some users may experience a “missing system.img” error and the installation will be aborted. This is because the way you’re trying to flash the update. Instructions on how to get around this can be found right here. Essentially users will need to unzip the update.zip folder and move all the images to the original folder we mentioned above, then manually flash them one by one, vs the flash-all command mentioned above. Only do this if you run into issues.
If you run into bootloop, follow this guide http://forum.xda-developers.com/google-nexus-5/help/bootloop-android-m-preview-2-t3154608/post61802470#post61802470
ENJOY!
Credits: Cory Gunther http://www.gottabemobile.com/2015/05/28/install-android-m-beta-download/

Thanks for the work for us.

I was able to install M2... but i am having trouble getting it rooted.. please help.. seems to be in bootloop.

Jaws4God said:
I was able to install M2... but i am having trouble getting it rooted.. please help.. seems to be in bootloop.
Click to expand...
Click to collapse
Manual here http://forum.xda-developers.com/google-nexus-5/development/rom-android-m-t3121186

@buildsaurabh
Thanks for the PM.
It is kinda convincing that this guide is more elaborate and a safe way to do this...even if it is the same result at the end.
I hope this helps others.
Thread open again

thanks for the guide, but this is not a rom just a tutorial hence the thread title should be changed accordingly.

Not to be that guy,
#1 do we really need another tutorial on how to flash your nexus?
#2 not a ROM its a tutorial
#3 the development section is not the place for this.
Plus there's already a dedicated android M thread.
Sent from my Nexus 5 using XDA Free mobile app

is anyone having issues with video playback? with despair 1.8 it would play audio with no video.. with elementalx.. it would play video but distorted.. anyone else having this issue?

buildsaurabh said:
[rom][android m][preview 2] nexus 5
Click to expand...
Click to collapse
This isn't a ROM, it's a guide so moved to General.
OP, please change the title to reflect this. Its misleading.

Looks like a "hit count" thread to me
Sent from my Nexus 5 xda-dev app

Simple explanation to fix ADB unauthorized device in 'M'

QUESTION: Can someone please explain in simple form how to fix the ADB unauthorized issue that has been present since the update to M? The option for removing any current rsa keys is gone from the developer settings. And when you plug your phone in to a new computer it used to pop up a notification that would let you accept the rsa key. None of this is working any more. I cant believe that it is not a bigger issue and I have spent a few hours over a few days looking for a solution so if I have missed it, I am sorry. I have read a few things that say that google has just removed the ability to use adb and one post even explaining that, what looked to me to be a prop file variable, needed to be changed from 0 to 1, or vise versa, but didnt explain where the variable was. I dont see anything that I am confident with in the build.prop. Thanks. Please explain so that anyone will be able to overcome this issue, or point to a link.

Are you talking about the option to "Revoke USB debugging authorisations" under Developer options? It's there, at least on my N6 running stock 6.0.1 MMB29V... And I just tried to ADB to my device and the popup for the authorisation came up on the phone, just as it should.
I think you have some other problem going on.

Are you running the latest adb/fastboot tools on your PC?

Article showing removal of ADB
stevemw said:
Are you running the latest adb/fastboot tools on your PC?
Click to expand...
Click to collapse
Yes I am, I always use the one directly from the 'platform-tools' directory in the SDK. Another thing is I have read multiple articles that actually state that Google has removed the adb functionality in marshmallow... I don't get it. I even went from stock G.E. to CM an its exact same problem. Not to mention now I am dealing bwith the fact that the nethunter kernel isn't compatible with the CM build for Nexus... What!? Anyone can enlighten me on that subject I would love to know that as well... LoL. Here is link to one of the ADB articles though.
Tekto-kodi.com/kodi-news/marshmallow-android-6-removes-adb/

I looked at your link and the links provided in that article. The only thing I can read from those is that the ability to run ADB from your phone, i.e. from the terminal emulator (not your PC) has been removed. Are you trying to run ADB from your phone or your PC (I was under the impression that you're using your PC, but I have to ask)?
As I stated before, ADB from my PC to my N6 works just fine with Marshmallow (6.0.1 MMB29V).
You say that you use ADB directly from "platform-tools", but you don't say if you've updated the tools from the SDK-manager.