Related
TO GET TO THE POINT, AND TO AVOID MY *****ING, SCROLL DOWN​
OK, imma recent migrating bird from the sinking WinMo ship.
Just got this phone from LG, nice phone, but the flashing guides here aren't so easy to understand
I'll quote a 6 line instruction from the Prime/Megatron ROM thread which is
http://forum.xda-developers.com/showthread.php?t=870640
How to flash:
First, reboot into recovery via 3-button-combo, ADB, terminal, w/e.
Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
Wipe data (data,cache,dalvik-cache,ext).
Connect the device to PC, copy Megatron over to the SDcard, disconnect.
Flash it via "flash zip from sdcard"
Reboot
Read important notes below
That's it.
Click to expand...
Click to collapse
SERIOUS? THATS IT???????????
I have no idea what all that means, and so are millions of sad puppies who migrates from WinMo's or dreaded Dumb Phones like the ones they sell in 7-11
SO, the point is (you can stop scrolling now)
PLEASE PLEASE PLLLEEEEAAASE make a easy guide for flashing, possibily a video. Or you could make it easy enough for me to understand, and ill make the guide.
BTW, in the long term, it WILL educate FURTHER n00bs.
Thanks in advance. Sorry for the *****ing. Love u guys
OK, OK, OK, you have got me!! I will prepare some "dictionary" for all noobs. Maybe it will sounds crazy, but when I logged-in I had no idea what android is. OO is my first android phone. I have got everythink from whole this forum, but I was there since thread about P500 started so it wasn't too hard catch and read every post here. So, all informations are there, but sometimes is not possible find them.
So i just have to read everything? Optimus One Android Dev or General?
Great! Thanks a lot
But gonna go to sleep.. I'm sorry lol this is my last week of winter break and its midnight. Bye!
dongimin2 said:
So i just have to read everything? Optimus One Android Dev or General?
Click to expand...
Click to collapse
About 95% of posts it will be useless because there are also some question, helps, and another stuff. There is too much words and useless trash. You also need know basics of unix-like systems to understand what are guys (and you) trying to do in adb shell, what is root and for what it is, what # mean in command line, and so on.
custom ROM is mainly for experienced user. At least, experienced in unix-like system, because android is based on it. Tools like busybox bringing next tools known from unix and some programs needs it for running. And another and another words and name what is normal for advanced user, not for n00bs here.
Because that all stuff it takes some time that I will have some usable noob dictionary.
This is a good and pretty much complete guide.
forum.androidcentral.com/lg-optimus-s-roms-hacks/48543-idiots-guide-rooting-custom-roms-optimus-s-edition.html
Rooting is the same, you just have to change some commands for the custom recovery but once you get there you'll know. And I recommend rooting via Adb, its easier for later.
btw, don't know if its a problem posting the link, if it is, sorry.
One thread is enough!
Do not do this again or you will have an infraction for spam.
Cheers
***UPDATE***
I am removing this tutorial from general public view. if you read the warnings/disclaimers and are still interested you will need to read the links below and go about it yourself.
--------------------------------------------------------------------------------------
first off credit for this idea go to all the people/sites linked below. IF credit is missing where due please notify me and i will resolve. This is just a gathering of other posts and steps that worked for me.
This will wipe your device. backup anything and everything before proceeding.
If you are not willing to take it upon yourself to research any problems that arrise and fix them yourself DO NOT ATTEMPT.
If you are unwilling to wipe your stock Firmware DO NOT ATTEMPT.
If you are unwilling to start with a fresh nookie color SDcard NO NOT ATTEMPT.
If you are unable to fix your problems or want to revert to stock you can do so following the link at the bottom of the page
This is for advanced users. Make sure you read and reread everything before attempting anything! I take no responsibility and offer no promise of support if you make yourself a $250 B&N brand paperweight. keep in mind the nc is hard to brick (know from experience) but anything can happen, so be warned and proceed with caution.
if something below is not clear visit the links provided and look for your answers there. they are there and the more you read and learn the more sense this will make. if you are still unable to find help post here and i will try to get you going.
now on to the good stuff. I just wanted to gather the various posts and links that i used to gt a fully working froyo running on my nc from the internal memory (emmc) and present them in a step by step guide for others wanting to run NF from their internal memory and have no need for B&N stock. Flash is working if you install the proper apk. this is not installed out of the box. After installing to your EMMC you will be able to use any sdcard as you normally would in android. I am using a 16gb card with no problems.
***steps removed... see top of post***
helpful links:
http://forum.xda-developers.com/showpost.php?p=10254900&postcount=138
http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2
nookdevs steps for creating nookie froyo sdcard:
http://nookdevs.com/Nookie_FroYo:_Burning_a_bootable_SD_card
nookie froyo thread:
http://forum.xda-developers.com/showthread.php?t=883175
nookdevs nookie froyo tips:
http://nookdevs.com/NookColor:_Nookie_Froyo_Tips
wipe nc to stock: (download the images and run the commands from an adb shell.)
http://forum.xda-developers.com/showthread.php?t=919353
Flash back to clean stock ROM (nook devs) http://nookdevs.com/Flash_back_to_clean_stock_ROM
1. first you will want a fresh NF sd card. I tried to use my seasoned nf card and ended with a brick... if you have google apps installed you will not be able to get past the android screen and will have to reimage as stated above. create your fresh nf sdcard following the steps at nookdevs here
Click to expand...
Click to collapse
As we say in french, you must call a cat a cat. Your NC wasn't bricked at all. You simply needed to touch each corner of the screen one at a time when on "touch the android" screen, starting with the top left corner, then clockwise.
Would have saved you some time
If I were you (if I may..), I'd put all the links the bottom of the post. Would make reading easier. As for my code to copy sdcard content, go on and post it directly. Opening multiple pages only makes things more complicated. No problem. As for the Volume keys and gapps, it could be ambiguous, those add-ins aren't required at all. Simple leave a link to nookie tips on nook devs for those who want it?
But of course, this is your post..
Sam
samuelhalff said:
As we say in french, you must call a cat a cat. Your NC wasn't bricked at all. You simply needed to touch each corner of the screen one at a time when on "touch the android" screen, starting with the top left corner, then clockwise.
Would have saved you some time
If I were you (if I may..), I'd put all the links the bottom of the post. Would make reading easier. As for my code to copy sdcard content, go on and post it directly. Opening multiple pages only makes things more complicated. No problem. As for the Volume keys and gapps, it could be ambiguous, those add-ins aren't required at all. Simple leave a link to nookie tips on nook devs for those who want it?
But of course, this is your post..
Sam
Click to expand...
Click to collapse
I tried the touching four corners. no go. several roms required that back when i was using a D1... I couldnt for the life of me figure it out so just scrapped and started from scratch.
thanks for your input. i planned to clean this up a bit, was just in a rush writing the original. Thanks again for your help. couldnt have gotten this far without your steps to start off.
Eager to try this out ... but will it be able to see a non-NF SD card I enter in? Will it recognize it, and let me see it as mass storage when the Nook is plugged into my PC?
Very well written, just copy and paste the code into the console for the most part ... Runs nice and fast, I have a few FC's to clean up but that is due to me not factory resetting the NC prior to doing this as I am an impatient person! I must say it is very nice not to have the B&N notification bar at the bottom of the screen.
So if this is really 2.2, does it have flash?
theyownus said:
I used 0.5.9 and replaced the vold file with the one from 0.5.8 making sure to maintain executable permissions.
Click to expand...
Click to collapse
a) What vold file? Searching for "0.5.8 vold" on this board produces no hits.
b) Executable permissions on what? This "vold" file or something else?
Don't want to be "that guy" but date should read 1/20/2011.
Thanks gonna give this a shot.
What happens to the Media partition?
Also, slightly random: Why doesn't adb ever seem to work over USB with my Nook Color? 2.1 ROM, Nookie Froyo on SD 0.5.8 or 0.5.9, it never sees a device. By contrast, it works fine on my G2.
starkruzr said:
Also, slightly random: Why doesn't adb ever seem to work over USB with my Nook Color? 2.1 ROM, Nookie Froyo on SD 0.5.8 or 0.5.9, it never sees a device. By contrast, it works fine on my G2.
Click to expand...
Click to collapse
Re-run ADB configuration. Make sure id is 0x2080.
How do we fix the SD card error. I am unable to do anything with the SD card.
samuelhalff said:
Re-run ADB configuration. Make sure id is 0x2080.
Click to expand...
Click to collapse
Wow. This is INSANELY important and this is the first time I've ever seen mention of it. Every other post simply assumes your ADB "just works." I have been endlessly frustrated by the lack of working ADB on this thing such that every time I do something with my NC I have to find a way to first install ADBWireless.
http://fineoils.blogspot.com/2010/11/pokey9000-has-got-self-booting-image.html
The instructions to get it working are in here, folks. Can these instructions be put in a sticky somewhere? This is about the least-obvious thing I can think of.
Is there any improvement in speed and reliability running this from the emmc as opposed to a class 6 uSD?
"extract them to their respective folders"
Nothin but bootloop
theyownus said:
first off credit for this idea go to samuelhalff
links:
original steps from samuelhalff http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2
Click to expand...
Click to collapse
What a great idea. If only someone had talked about this weeks ago... Anyway now that it seems people are going to be trashing their nooks trying to do this, it's probably simpler for one to just boot into SD and...
[Replace the files in /system]
It would also be a good idea to clear out /data and /cache or there will likely be bootloops when froyo boots with the old data stuff still around.
That's off the top of my head and totally untested. Seriously. It probably doesn't work, and is totally unrecommended. Anyone who types "rm -rf *" in their emmc system is saying goodbye to their stock OS and will have to live with their decision. All GPL disclaimers apply.
Note also that IOMonster has a nice bootable clockwork SDcard that does all kinds of things, and automating this type of migration is only a matter of time now.
Update: Actually the steps aren't THAT different. /just sayin'.
fattire said:
What a great idea. If only someone had talked about this weeks ago... Anyway now that it seems people are going to be trashing their nooks trying to do this, it's probably simpler for one to just boot into SD and...
Somewhere in there it would be a good idea to clear out /data and /cache or there will likely be bootloops when froyo boots with the old data stuff still around.
That's off the top of my head and totally untested. Seriously. It probably doesn't work, and is totally unrecommended. Anyone who types "rm -rf *" in their emmc system is saying goodbye to their stock OS and will have to live with their decision. All GPL disclaimers apply.
Note also that IOMonster has a nice bootable clockwork SDcard that does all kinds of things, and automating this type of migration is only a matter of time now.
Update: Actually the steps aren't THAT different. /just sayin'.
Click to expand...
Click to collapse
I had the same reaction reading the post. Not only is it unfair to you, because I have read your post before attempting anything, but it's also unfair to me because it suggest that he did most of the practical work..
Anyway does it really matter? People who don't regularly read the forum often don't give a Jack of who's responsible for what. Those who do willl know you were first in line. Anyway, I understand your frustration I should have said something. I was just fed up. Sorry.
Please know that my original post recomanded doing dd's of all partition. That way reverting back to stock was easy. My post also mentionned emptying data.....
What do mean steps aren't that different?
Sent from my HTC Desire using XDA App
samuelhalff said:
I had the same reaction reading the post. Not only is it unfair to you, because I have read your post before attempting anything, but it's also unfair to me because it suggest that he did most the practical work..
Anyway does it really matter? People who don't regularly read the forum often don't give a Jack of who's responsible for what. Those who do willl know you were first in line. Anyway, I understand your frustration I should have said something. I was just fed up. Sorry.
What do mean steps aren't that different?
Click to expand...
Click to collapse
Ah, I just mean it's all the same idea-- out with the old, in with the new. Nothing particularly genius about it. In any event, it's not really a matter of credit. We all stand on the shoulders of giants. I was just amused is all... so let's just have fun, eat, drink, be merry, and dance in the rain.
It may turnout that English isn't the OP's native language. Although it isn't mine either..
Nothing really seems genius once you get to understanding it.. but as a newcomer, I still had a bit of trouble getting the sdcard to mount..
Sent from my HTC Desire using XDA App
So I've been doing this android flashing business a long time
And I've got a real mess on my hands. I'll be ****ing with this for the rest of the night! Thanks!
Hey guys,
I'm extremely nervous about rooting since I can't really afford to replace my phone with anything at the moment.
The reason I really want to root is for screenshots and a full hdmi mirroring without the dumb 60 dollar dock.
I've read all the threads about rooting on and etc, but I'm still confused.
If possible, can someone give me a simple answer of which way of rooting is best for me, possible side effects, and what I can do with it?
I'm pretty tech savvy, thing is, is that I've never had an android phone, and really want to make sure I don't kill such a nice phone
Sorry about this, I just REALLY don't want my phone to get bricked.
Phone Information: Bell Motorola Atrix
System Version: Blur_Version.0.37.23.MB860.BellMobility.en.CA
Model Number: MB860
Android Version: 2.2.2
Baseband version: n_01.77.15p
Motorola webtop version:OSHWT_U1_5.32.13
Kernel Version: 2.6.32.9
I think that's all that could matter.
I have not tried to mod the phone as of yet. Only things I've done is install snes and psx emulators
Any help is GREATLY appreciated.
shaimedio said:
Hey guys,
I'm extremely nervous about rooting since I can't really afford to replace my phone with anything at the moment.
The reason I really want to root is for screenshots and a full hdmi mirroring without the dumb 60 dollar dock.
I've read all the threads about rooting on and etc, but I'm still confused.
If possible, can someone give me a simple answer of which way of rooting is best for me, possible side effects, and what I can do with it?
I'm pretty tech savvy, thing is, is that I've never had an android phone, and really want to make sure I don't kill such a nice phone
Sorry about this, I just REALLY don't want my phone to get bricked.
Phone Information: Bell Motorola Atrix
System Version: Blur_Version.0.37.23.MB860.BellMobility.en.CA
Model Number: MB860
Android Version: 2.2.2
Baseband version: n_01.77.15p
Motorola webtop version:OSHWT_U1_5.32.13
Kernel Version: 2.6.32.9
I think that's all that could matter.
I have not tried to mod the phone as of yet. Only things I've done is install snes and psx emulators
Any help is GREATLY appreciated.
Click to expand...
Click to collapse
If you search for gingerbreak, its a downloadable apk file that you install on your phone. Make sure you have an sd card installed, and then just open the application and click root. It's very simple, i've used that program many times on my bell atrix. I will see if i can find the link
You can find the app here
Will I need to reformat my SD card?
Also, is there some sort of backup I can make just in case it fails or something?
Not entirely sure what my options are in case it fails.
Same situation as OP. Really new to this Android stuff! Been doing tons of reading on this forum before I attempt anything and I have to say all this weird naming convention and such is throwing me off lol (whats with pudding and fruitcakes??).
Anyways thanks nate for the link! I've read about Gingerbreak but there is also GladRoot. Any differences b/w the two? Pro's/Con's?
Also to OP or any new people to android just in case you haven't seen this thread: http://forum.xda-developers.com/showthread.php?t=1154600. Its really helpful. Answers your question about what root allows you to do briefly and some of the problems you may run into.
edit: Just re-read the GladRoot thread and it looks like that method is a no go for Bell users after the OTA (0.37.23).
@Bump: Can someone help me in regards to my second post?
Thanks again!
Best way is to download the Gingerbreak apk like the first guy said and just push that to your phone, or if you're a lazy bum (like me!) and you have a PC, then use this. Also, I've run this on my phone with no problems to any of my SD cards (both internal and external), but since it does touch that area, BACK UP BOTH. If anything, it's a bit more time but so much more worth it. Besides, don't you want a backup of those embarrassing videos you took of your friends? *cough cough* >.>
Also, know that if it doesn't work or something, pull the battery and try again. It took me a few tries, but i finally got it to work. =] Let me know how it goes.
Happy rooting!
~jojojohnson7410~
"When attempting this on my bell phone
(same stats as shaimedio) I get the error from gingerbreak "could not extract assets !" this is a freshly purchased phone.
I've followed steps from various threads on how to do this (being I've managed to use adb and get gingerbreak onto my phone i figured that was a start.) Any tips?"
Fixed my own problem
"adb shell rm /data/local/tmp/*
adb shell rmdir /data/local/tmp
adb shell mkdir /data/local/tmp"
Looks like the temp cache prevented access
+1 for the gingerbreak. I've used it a few times without any issues.
I always plug my phone in, mount my internal memory and copy it over to the computer, then take out my SD card. Install & run gingerbreak, then put the sd card back in and copy all my data back over to the phone from the computer.
Can't really say what your options are if it fails as I've never had that happen with mine the 3-4 times I've used it.
Hope that helps a bit.
I am at a loss, i am at a point where my phone is no longer bound by the laws of logic.
I was running Passion 13.1 ICS
two days ago for some reason i woke up and my phone was asking for a password to decrypt the phone, i though this was weird being that i didnt encrypt the phone.
so i setup ODIN and flashed back to Eugene's Froyo that doesn't brick pre rooted w/re-partition checked.
it passes and reboots after reboot i get
Code:
"E:Cant mount /dev/block/mmcblkop1 (or /dev/block/mmcblk0)
(no such file or directory)
but it will reboot into android
so i booted into android setup adb and copied over the fs tools (Parted, e2fsck, mke2fs, resize2fs tune2fs, and sdparted)
i found that in /dev/block/ the partition files were missing completely so i created them using
Code:
mknod /dev/block/mmcblk0 b 179 0
mknod /dev/block/mmcblk0p1 b 179 1
mknod /dev/block/mmcblk0p2 b 179 2
i can see them there but when i try to partition them using
Code:
parted /dev/block/mmcblk0 mkfs ext2
it returns
Code:
Error: Error opening /dev/block/mmcblk0: No such device or address
so i tried a shot in the dark i tried to write zero's to it
Code:
dd if=/dev/zero of=/dev/block/mmcblk0
it returns
Code:
/dev/block/mmcblk0: cannot open for write: No such device or address
so i rebooted my phone, when it came back up i opened an adb shell and to my surprise the fs tools and the files i created in /dev/block were gone it was like it factory reset it self on reboot.
were i am at now is hardware failure unless the collective minds here can see something that i missed?
i really really REALLY want to save her she has been an awesome phone.
any help would be appreciated
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Instead of the froyo build, you should try 2.1 jfd odin package
Woodrube said:
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Click to expand...
Click to collapse
I was thinking about doing this, but wouldn't it make my phone incredibly slow because of the sd latency?
Dougfresh said:
Instead of the froyo build, you should try 2.1 jfd odin package
Click to expand...
Click to collapse
i tried looking for this but i cant find it do you have a link or a copy of the files?
I'm sure it will slow down but it should boot up and you can load another ROM on there. You do lose your entire internal since it is essentially swapped out for the external. Can't hurt to try with a higher class card maybe.
It seems this is happening to everyone running ICS Passion.
Ya but on the Cappy threads it is happening to people on CM9 and Doc's too.
So I am wondering if anyone on AOKP builds are getting these. I posted in the other two threads about this (the one that you were helping that guy yesterday with and the other one) to see what ROMs/kernels they were running, JIC.
Might be a problem with the port of the AOSP code since it is essentially from NS and GNex, both Sammy products though. Anyone in your NS fora reporting this problem?
Nope, nobody. And I just flashed from 2.3.6 to 4.0.4 2 days ago
I flashed GBBOOT-T959UVJFD in an effort to fix my problem, but its just stuck in a boot loop now. is there a chance that the actual physical memory is damaged?
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Woodrube said:
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Click to expand...
Click to collapse
at this point i don't even care about recovering the internal partition i would like to just format it and start over clean.
It had a GB boot loader on it.
This is what is confusing me, in my mind if a partition is locked and i forget the key or in this case it encrypts itself shouldn't i be able to just fdisk or dd the partition back to cleanliness and format it?
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Big Dog KMc said:
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Click to expand...
Click to collapse
I thought the Nexus had ICS already, so i don't think that was what happened. plus i would think it would prompt the user to apply the update or restart the device.
at this point after reading this thread, i think its hardware failure in my case. otherwise why would it clear everything after a reboot?
TheGioDoodlesII said:
Flash the original stock rom , wipe cache and do a factory reset before and after flashing
Hope i helped :beer:
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
I tried that sans the beer LOL i think i am going to need something stronger.
Anythoughts on the SGS 2? HERE
or the NEXUS HERE
Hello everybody.
This is my first post, and while I am noob at XDA-Developers, I have spent more than 10 years writing and reading in forums, and I know what has to be done before writing on them. And I did. I have a couple of questions that I think they are not easy to answer. Indeed, I spent 8 hours yesterday searching through the interwebs and this forum to try to figure out the most thorough answer. And I think I figured out mine, but I don't know any people that can reinforce my toughts and tell me "Hey Gabriel: you are right, you did well, you are the man: go out for a beer, keep calm and carry on". I will ask the questions first, and later I will explain why I ask such questions, and finally what are the steps I did.
The questions are: How can I remove root from a custom rom, and how can I be sure that I properly did? I know that many of us think that "This is stupid / Why do you want to do such a thing / the power of your phone will... / go to stock / etc". But, any way, I have a deep concern on expanding concepts and knowledge, and I thing that root process, root means and rooted phone securing checklist are not as clear as I would like to find them. And more important: I *have* to remain in a custom rom but I *must not* be root.
So the why's are not the question but, just to add some reasonable context: I have a phone that does not fit my needs with the stock rom, because a hardware component is falling apart and I need a software workaround (YEAH, right LOL: a Nexus One with the power button falling apart and I need to be able to unlock / wake with the trackball; but this thread is Android-wide because it tries to find a deep insight into rooting itself). This software workaround does not work in stock rom when I configure the password / PIN / pattern. And the problem with custom roms is that they run into trouble with certain data-protection aware environments, which do not allow rooted terminals. And more important than all: I have no need at all to be root, at least by now.
So, I spent hours searching, and I figured out that I should remove "su" command and related APK's (ROM Manager, Superuser, ... and some others that I won't need). All by myself and with some posts (I don't remember if they were here or in "HTCMania", a good spanish smartphones board, either) that suggested it.
The exact process I did was to download CyanogenMod 7.2 RC1, check signature & md5 to make sure the zip was what it claimed to be (because later I found that I needed to shut down recovery signature check) open the .zip, remove "/system/xbin/su", install the rom, remove su-related ".apk" with adb, and try to check if it still had any sort of superuser permission scalation. It aparently does not have. I checked /data directory with Root Explorer, I downloaded and ran Root Checker Basic.
The results seem what I expected (and that's the question: they seem, and I don't know if they are): I am running on CyanogenMod, the workaround (wake on trackball) works, the PIN/password works fine with it, and it seems I am not able to gain root access.
But my question are deeper than that: is there any remaining technical mean that could be used to gain root access on my phone? Do I have to get rid of more su-companion tools to be sure and to be "non-root"-compliant? Is there any checklist we should follow to check both if our custom ROM is rooted-but-secure and if our ROM is properly un-rooted? And most important: did I miss / failed to find the correct resource in these forums?
Thanks to every body and congrats for this outrageous boards.