Database Develop

[Q] Rooting current Nexus One not easily possible?

Hi,
it's my first post here and I'm aware that I'm going to ask a typical newbie question... But after quite a long period of browsing the internet and this forum I concluded that I need help So I hope that I don't annoy anyone...
My intention is to prepare my Nexus One to use Cyanogenmod. To do that, I want to use a Linux PC instead of a Windows PC. I bought my Nexus from Vodefone in Germany. All current OTAs are installed. Some more specific information: Android 2.2.1, Build FRG83D.
I understood, that at first I have to root my Nexus and need to unlock my boot loader. But I'm a bit confused by the number of different approaches to root/unlock the Nexus One which can be found in this forum and via google. The most of the guides require a Windows PC. To me it was not possible to decide which approach I should follow in order to safely unlock and root my Nexus.
So far I've tried to root my device with the tool "ANDroot", but it won't work... I assume, that I need to follow a more complex approach via a USB-connected PC. I'm a quite experienced Linux (Ubuntu) user and want to use linux for rooting and unlocking my device.
I don't ask for someone to explain to me in detail how to do it! But it would be great if someone cold tell me whether it is easily possible to root and unlock my device from Linux and if so where I might find some comprehensive explanations.
Many thanks in advance and regards from Germany!

try here
http://ilikemygooglephone.com/2010/...-and-root-google-nexus-one-mac-windows-linux/

Look here, under root: http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
I say forget the one-button root and go the OG way, but I guess it just comes down to how comfortable you are with the process.

The process doesn't change very much regardless of what OS you are running.
All of the SDK adb commands are exactly the same - it's just ./adb rather than adb.exe.
Follow the instructions on the Android SDK download page for setting up the SDK on your system, and then follow instructions here for unlocking/rooting/flashing your device.
Just because you use Linux doesn't make you "special"

Thanks a lot for your replies!
Actually I just needed to realize that the Android SDK runs on Linux as well, and that with even less issues than on Win (no need for fancy USB drivers).
Very good for an overall overview: theunlockrDOTcom/2010/01/02/how-to-root-the-nexus-one/
One just has to realize that e.g. "fastboot-windows" has to be replaced by "fastboot_linux"...
A showstopper was the annoying "install-recovery.sh" script which kept me from loading into the new installed recovery image. But after consulting google the following saved me from freaking out:
Code:
./adb shell
$ su
# rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, Read-only file system
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/etc/install-recovery.sh
# exit
$ exit
After that is was straightforward to install CyanogenMod by following their specific update guide:
wiki.cyanogenmodDOTcom/index.php?title=Nexus_One:_Full_Update_Guide
And now I'm happily enjoying even a FM radio which I did not expect while thinking of installing CyanogenMod...!

shouldn't adb oem unlock do the trick?

Bloodflame said:
shouldn't adb oem unlock do the trick?
Click to expand...
Click to collapse
It's fastboot oem unlock ... but potato-patato.
To the OP...
I know you probably thought of this already but add
Code:
export PATH=~/android/tools/:$PATH
to your bash .rc script so you don't have to put up with ./adb each time you want to use the adb command.
sassafras

whoops. i should stop posting when tired
don't pay attention to me

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,

[Q] Why can't I run binaries from adb?

Sorry in advance if I'm missing something simple but I'm at my wits' end here...
For a while now I've been slowly researching and learning how a possible root exploit could work, and finally I managed to come up with an attack plan and set up a build toolchain, only to find that I can't even run a simple Hello World!
Now I'm only a bit familiar with linux environments and even less so with android ones, but I'm pretty sure something's not right here. Trying to run anything I put on the phone just spits back "not found". Also, any command that actually can't be found gives me "permission denied", from my searching online I couldn't find out whether this is the correct behavior.
Code:
$ ./hello
./hello
./hello: not found
$ hello
hello
hello: permission denied
$ ls -l
ls -l
drwxrwxrwx shell shell 2011-08-09 21:21 bin
drwxrwx--x mot_tcmd shell 2011-06-29 08:50 12m
-rwxrwxrwx shell shell 5585 2011-08-09 21:10 hello
drwxrwx--x mot_tcmd shell 2011-06-29 16:38 tmp
(Had to strip down the commands for the overzealous spam filter, this is running from /data/local)
From what I've seen in the other threads in this forum people have been able to run busybox and such from this location, so does anyone have a clue what's going on here?
Alternately, if there's anyone that's very familiar with native-code android development or the android kernel, particularly regarding network capabilities, please let me know here or via PM/e-mail so maybe I can figure out if my exploit is even possible.

/data/local ? I didn't realize adb had access there. I run busybox from /tmp there's about 2mb of space there for us to use.
Good luck to you.

Well, I went and found a prebuilt busybox and that works, so I'm assuming there's something wrong with the binaries I'm making.
Right now I'm using the Code Sourcery GNU/Linux ARM toolchain as recommended by various sources online, since it seemed like the easiest option for someone with minimal experience with the GNU build tools. But unless I can get it working, seems like my only other option (without learning all the details of GNU development) is some "agcc" script somebody made a few years ago, which may not even work anymore, and would require me to do a full build of the android source in a linux VM.
So, anyone have any insights or experience on building native binaries fairly painlessly?

Try changing the permissions of the file.
chmod 755 /data/local/filename
Sent from my ADR6400L using Tapatalk

im pretty sure u are building a binary for another arch than arm...

[Q] extracting firmware

hello
is there any way to extract the whole firmware from a i9000?
a friend of mine just bought a i9000 from the same carrier that i have.. and i want the original rom. is there any way to get it untouched (vanilla)??

Not really untouched, you'd always need root to grab the firmware, so that's flashing a different kernel or trying other ways to get (temporary) root.
But don't let that stop you, the kernel probably won't be any different than the standard Samsung one, so you can put it back later.

the thing is... i cant find the original kernel around, i have searched all over, and there is no where to be found. so.. if i change the kernel, and take it in for warranty related stuff the carrier people will notice that i have changed it.. and they'll say.. sorry you void the warranty!!
so... is there any way to extract a vanilla rom??

Use check fus downloader. Google it or look around xda. You will be able to get your ROM direct from Samsung.
Sent from my GT-I9000 using Tapatalk

Is it me or are you confusing kernel and ROM ? The kernel is the stuff that makes it boot and talk to the hardware and stuff, like a bios from a pc. The rom is the operating system which does everything else.
Can you post the kernel version ?

EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
Bubble-be said:
Is it me or are you confusing kernel and ROM ? The kernel is the stuff that makes it boot and talk to the hardware and stuff, like a bios from a pc. The rom is the operating system which does everything else.
Can you post the kernel version ?
Click to expand...
Click to collapse
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Like I said, get the ROM and you get the kernel. The kernel is simple to extract, and you also have the added bonus of having the complete, unadulterated rom should you need it in the future.

since i`m new to everything here can you help me with smth that is bothering me
i got a i9000 2 months ago and since then i`ve been messing around with rooting and flashing around without understanding o lot but i've been doing exactly what others say step by step
i like this galnet miui rom (the only one i've tried so far) but i have battery drain issues
can you tell me a good combination of kernel and/or bootloader with this galnet so i would not have a battery drain
now i'm using official 2.3.5 and i have a full day battery usage
but i like some features that galnet has
thanks in advance
xxbeanxx said:
EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Like I said, get the ROM and you get the kernel. The kernel is simple to extract, and you also have the added bonus of having the complete, unadulterated rom should you need it in the future.
Click to expand...
Click to collapse

xxbeanxx said:
EDIT: Since you did not quote I am assuming you are replying to my post. If not please just ignore my bantering.
Click to expand...
Click to collapse
I did not quote, but was answering to the OP.
Sorry if that was confusing.
It's just you. I know what a kernel is, do you know what a rom is? The kernel is included with the rom. If you get the rom, you have the kernel.
Click to expand...
Click to collapse
Well yes, but I can't imagine a provider customizing the kernel. They do however customize the rom to include their own bootscreen, apps, theme. My previous phone was that way for example. I looked long and hard for the original firmware. But unless you're with one of the really big providers (Orange or the like), the rom is not available on the interwebs.
Showing up at a provider's service center with a bog standard rom can look suspicious that way.
Also, the kernel technically does not make your device boot. It is, however, used during the boot process to perform some hardware initialization (initializing IRQs, setting up the scheduler, starting the dynamic module loader).
It is nothing like a BOIS from a PC. This point is illustrated by the fact that a PC running linux requires both a BIOS and a kernel. They are mutually exclusive. The kernel is a part of the OS, the BIOS is a part of the device.
Click to expand...
Click to collapse
Thanks for clearing that up. I was aware of most things, but decided to paint a simpler picture for the OP.

enushi2002 said:
...can you tell me a good combination of kernel and/or bootloader with this galnet so i would not have a battery drain
...
Click to expand...
Click to collapse
The bootloader has no affect on your battery life.
Also don't assume the kernel is the biggest contributing factor to your battery drain. It very well may be, but there are a lot of other things that could also cause it. It would be better to try to investigate the cause of your battery drain rather than just switching kernels to try to fix it.
To directly answer your question, no I can't tell you a good kernel to use with MIUI. I am running CM7.1 currently with stock kernel and get decent battery life.
Are you on 3G data often? CM (and thus MIUI) has trouble with 3G, causing bad battery drain (so called RIL bug).
---------- Post added at 09:34 AM ---------- Previous post was at 09:27 AM ----------
Bubble-be said:
...the rom is not available on the interwebs.
Showing up at a provider's service center with a bog standard rom can look suspicious that way.
Click to expand...
Click to collapse
If you can update your phone via KIES you can get your ROM via check fus downloader. The rom you download using this tool will be what KIES uses to update your phone. So it is not "bog standard," it is what your provider puts on your phone, complete with provider customizations. It is impossible for a service center to tell the difference.
I had CyanogenMod on my phone when the touchscreen malfunctioned. I downloaded my provider's latest rom using check fus downloader, flashed it with odin, performed a factory reset, and brought it back and they replaced it no questions asked. As far as they knew I had only ever used the "proper channels" (ie: kies) to update my phone.

xxbeanxx said:
Use check fus downloader. Google it or look around xda. You will be able to get your ROM direct from Samsung.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks, but it did not found it..
in the result box says
Product Code: GT-I9000HKTVMT
no firmware info retrieved for given data
the firmware info would be:
Product code: GT-I9000HKTVMT
PDA: I9000TUBJPA
CSC: I9000TVMTJP6
Phone: I9000TUBJPA
Is a froyo 2.2.1 for a galaxy I9000T from movistar venezuela
I guess i'll keep looking for it

francescopp said:
I guess i'll keep looking for it
Click to expand...
Click to collapse
Wow that's strange. Well anyway, you could try this..it won't work without root but if you don't mind rooting first you can do this to get your kernel, then unroot.
Code:
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
If you want to backup your entire rom:
Code:
adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096"
adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096"
adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096"
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096"
To verify the dumps you can mount them in linux or use MagicISO in windows (the .rfs ones at least).
You can then turn these files into a full fledged rom with a bit of tinkering. This might be your only option.

Problem at the installation on my Huawei Ascend P7 L10

Hello everyone, I hope one of you can help me as I didn't really find any solution on the internet.
I got a Huawei Ascend P7 L10 and I absolutely love it, but I run into a problem every time that I try to install the Xposed framework on my device. The installer tells me that it "could not copy app_process to /system/bin"
I've looked a bit on the internet and found that it might be because of a permission problem within the /system folder but when I tried to change them my phone got stuck on the boot logo and I had to flash the ROM again to use my phone.
Does someone know how to solve that problem?
I'm of course on android 4.4.2 and tried different version of Xposed Installer 2.6 and 2.7) but nothing changed.
Thanks for the help.
Edit : I've also tried version 2.5 and both the automatic and manual flash of the installer, but couldn't get any of both working it always finished by a big "FAIL" written on the recovery screen.

Do you have root access?
I heard many problems with xposed on the p7 and personally think that it must be something with a whole device...

CCody said:
Do you have root access?
I heard many problems with xposed on the p7 and personally think that it must be something with a whole device...
Click to expand...
Click to collapse
Hello I do have root access (and I have all permissions on the /system/bin folder (at least I should have as I did chmod 777 /system/bin))

Can you post a logcat? You can try flashing it via the recovery first (you need to have a custom recovery, I'm guessing you do not, which is why the recovery installation failed when you tried it).

GermainZ said:
Can you post a logcat? You can try flashing it via the recovery first (you need to have a custom recovery, I'm guessing you do not, which is why the recovery installation failed when you tried it).
Click to expand...
Click to collapse
Oh i didn't know about the custom recovery, which one can I get (if there is any for my device of course)
Sorry about the newbie question but what is a catalog and how do I post it? (Never had to do/use that on iPhone :$)

PrimuSSaintS said:
Oh i didn't know about the custom recovery, which one can I get (if there is any for my device of course)
Click to expand...
Click to collapse
I don't know, check your device's forum.
PrimuSSaintS said:
Sorry about the newbie question but what is a catalog and how do I post it? (Never had to do/use that on iPhone :$)
Click to expand...
Click to collapse
Logcat*
There are many tutorials around such as this one. You can search for more if you don't prefer that method.

GermainZ said:
I don't know, check your device's forum.
Logcat*
There are many tutorials around such as this one. You can search for more if you don't prefer that method.
Click to expand...
Click to collapse
there it is
EDIT :
Problem solved, for the people that have the same problem than me, here is the solution :
Download BusyBox (playstore)
Download Terminal emulator
Then type this :
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
Click to expand...
Click to collapse
this will give you full access and you should be able to install Xposed framework (at least that worked for me) - Don't forget to disable the resource hooks in the settings panel as the numbers will be in green but it would still mark Xposed as uninstalled.
source :
http://forum.xda-developers.com/showpost.php?p=53291974&postcount=200&nocache=1&z=1143765179790447