Related
Hi there,
I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.
1) download image from:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2
2) copy content of file to the microSD card
3) edit default txt and replace init=/linuxrc with init=/bin/sh
4) run haret and let it boot.
After a while you'll get to shell. No graphics.
Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)
and you will get usb0 interfece to start up.
Which IP to use to connect with OPAL I still must investigate.
Well ip connectivity now works:
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
Notas:/# ifconfig usb0 up 192.168.2.200 netmask 255.255.255.0
Listik:/usr/src/linux-2.6.27/Documentation# ping 192.168.2.202
PING 192.168.2.202 (192.168.2.202) 56(84) bytes of data.
64 bytes from 192.168.2.202: icmp_seq=1 ttl=64 time=2.95 ms
64 bytes from 192.168.2.202: icmp_seq=2 ttl=64 time=1.72 ms
And how to do it:
prolong "set CMDLINE" line with
ip=192.168.2.202:192.168.2.200:192.168.2.200pal:usb0
But in this image there doesn't seem to be any telnet/ssh server running. I will try cook image with ssh server support later
Download error
Were not able to re-upload
404 file not found error!!
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/
and open latest gizard-<date>.tar.bz2
or that I suppose.
The latest link should be http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20090703.tar.bz2
does this mean any chance of android working? anyone tried?
Hey,
I'm a new Opal user and I'm interested in getting *nix running on my device. I still haven't had the chance to mess around with this stuff but I'm excited to see this thread.
I was looking into the possibility of running Android on the Opal and it seems the closest thing is this thread bout running it on the Herald (it uses the same processor as the Opal).
I don't any experience in Linux porting so I thought I'd share this, in case anyone else is interested. And at the same time, I'll try to see if I can get something working based on what has been/is being done for other devices.
Sorry for the long post.
Hey Folks,
Any progress on getting Android on Opal? I am eagerly waiting to load one.
Kindly let me know, if this version of Linux when loaded, gives the UI.
Cheers'
Vijay
cijoml said:
Hi there
I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.
1) download image from:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2
2) copy content of file to the microSD card
3) edit default txt and replace init=/linuxrc with init=/bin/sh
4) run haret and let it boot.
After a while you'll get to shell. No graphics.
Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)
and you will get usb0 interfece to start up.
Which IP to use to connect with OPAL I still must investigate.
Click to expand...
Click to collapse
Android can boot on Opal
I have some good news, Android can boot on the Opal. This is just a proof of concept as it's missing tons of drivers and is completely useless.
Touchscreen and all keys except for the volume control (and obviously the reset button) are not working. So you basically can't do anything when you run it.
What I tried is the same as what's written in this thread about running Android on Gene. They're using the build made for the Herald/Wing (just as I was proposing in my last post) with customized initramfs and kernel.
You'll find all the necessary details in that thread. However, there's a newer build than the one mentioned there it's wing-linux-0.4pre2.cab. And the suitable kernel for that build is supposed to be the pre2 posted in this post but it didn't work on my Opal so I tried the older Gene kernel and it worked. The main difference between the two is bluetooth support, and that's obviously is of no use for us.
This doesn't effect the Windows rom, nor does it requires any special partitioning. Still it's best to have everything backed up before launching it, just in case.
This is the official site for the wing/herald build:
http://wing-linux.sf.net/
This thread on their forums about the Gene port will probably be of use to us:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=4
I'm reading about the next steps but as I said before, I don't have any previous experience or knowledge about this type of things. If someone can give me hand, I would be more than grateful. At any rate, once I have better understanding of the concept I'll contact the people behind the Wing and the Gene ports.
P.S: If you do try to run this, keep in mind that this will take lots of time, specially for the first launch. And when you get an error saying something like "android sh: can't access tty" just ignore it and keep waiting. After a while you'll have a flashing "android" on the screen, and after some more waiting you'll reach the main screen.
Is this just THE BEGINNING
Sooper Stuff..!! So is this just THE BEGINNING??
How do we port the drivers and other required information in the build?
Cheers'
Vijay
www.msigeek.com
A Lil' help
I'm going through the Gene port thread here and on the Wing-linux sourceforge forums but I'm still a bit overwhelmed.
I would appreciate any help as I'm completely new to porting. I have some programming and linux knowledge but never attempted this type of things.
Click to expand...
Click to collapse
So am I.
Hmmm...
Right. Lets do it the way I did it.
1. Get the touchscreen working. Through HaRET, you must have got the GPIO interrupt whenever you pressed the touchscreen. You must have got two numbers corresponding to each press - a smaller number and a bigger number. The smaller number is the GPIO, and the larger number is, well, lets say a special GPIO value for the same pin.
Now checkout the Gene branch through git.
Goto /wing-linux/kernel/arch/arm/mach-omap1/board-htcherald.c
Scroll down to a block of code where you'll see the touchscreen code. Enter the smaller number in the .dav_gpio statement, and the IRQ number in the OMAP_GPIO_IRQ() statement below.
2. Follow the Kernel build instructions on the development section of the wing-linux wiki (the two make commands)
Copy the zImage into the linux folder on your SD card
Boot into wing-linux. The touchscreen should start working.
3. Now, hopefully, after the touchscreen's working, You would essentially just require two more buttons - the home button and the back button for minimum functionality. Everything else can be worked on by the touchscreen.
Then follow the instructions on the wing-linux forum (Page 2) to get the KEY(row,col) values of the keys on your handset. Hopefully you should get atleast a couple. Note down the corresponding keys and their KEY(r,c) values output.
4. Fire up board-htcherald.c again and goto the place where you have the KEY(r,c,KEY_blah) thing and replace the codes as per your obtained KEY(r,c,KEY_blah) values (The Home button is the one commented as Left Button)
5. That's all I can help you with as of now. I'm also figuring out a stable way of getting the DPad and the center select key to work, but It'll take some time.
Thanks kshaurya!
(This guy right here is the one who fixed the kernel for Gene, I asked him for some pointers).
I don't want to take my device apart just yet (I usually do my best not take to dismantle anything that I haven't owned for at least 3 months unless absolutely necessary) and I couldn't find a place that states what touchscreen it uses. I'm just hoping that it's the same a tsc2046 as well. [Is there anyone without a warranty and/or willing to check for us?]
I'm gonna double check the values I got from the touchscreen as for some reason I seem to have to IRQ values, probably forgot to get rid of some spamming irq. And, at the same time, I'm currently setting up a VM as a building environment, my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines.
If anyone else have some experience and wants to try this, refer to: http://www.handhelds.org/moin/moin.cgi/HaRET_20Documentation (using haret to get the GPIO and IRQ values needed).
And to:
http://sourceforge.net/apps/trac/wing-linux/wiki/Development (acquiring the source code from Wing Linux and how to build it).
And a quick question for anyone that tried booting Android on the Opal, what screen did you get when Android finally finished booting?
I don't want to take my device apart just yet
Click to expand...
Click to collapse
Huh? where did that come from? Wing Linux will not touch your WM.
I seem to have to IRQ values
Click to expand...
Click to collapse
Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.
my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines
Click to expand...
Click to collapse
Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.
kshaurya said:
Huh? where did that come from? Wing Linux will not touch your WM.
Click to expand...
Click to collapse
I mean to check the screen, in case it turned out to be different that what you have.
kshaurya said:
Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.
Click to expand...
Click to collapse
Yeah, stupid typo.
I noticed now that one of them appears when I keep the screen 'touched' for a bit longer.
kshaurya said:
Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.
Click to expand...
Click to collapse
I'm not gonna build the complete thing. Seems like I got too exited and failed to notice that building the kernel only requires a cross-compile toolchain, te rest is for compiling the whole thing.
I'm not THIS stupid usually . Honestly!
Thanks again!
I'm not THIS stupid usually . Honestly!
Click to expand...
Click to collapse
Its pretty normal
Weird.
I've only changed the two touchscreen values and built the kenrel. It finished without any error but now it won't boot.
It gets stuck, even before the space allocation part, with this error: "sh: can't access tty; job control turned off". And then it displays a prompt.
I'll try modifying an older build, I'm pulling them from the repos at the moment.
After all, the pre2 kernel from Gene didn't boot on my device (although it got stuck later on).
Try doing a clean install - Remove the linux folder and try again.
Also, make sure that you're not forgetting to checkout the Gene branch.
Code:
git checkout Gene
Is your default.txt modified? And have you downloaded the modified initramfs.cpio?
check in the Gene forums for that.
Already tried the clean install, no dice. The default.txt is untouched and I'm using the modified intramfs. What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command. I could probably ssh via usb but I have no clue how that might help.
And I've already checked out the Gene branch from the beginning.
I've tried compiling the kernel for pre1 (after changing the screen values) from SVN and it did boot (both using the cabs for pre1 and pre2) but no touch screen yet. All in all, I'm guessing that there's too much hardware difference here.
And the button for lowering volumes didn't work either, it seems like whatever you changed for getting it to work on Gene is the same as what we need here, but I'll think about that later.
I only have two ideas left:
- Trying to go back to a more stable build (with lesser features and lesser possibilities for errors). Maybe 0.3.
- Trying to create some kind of hybrid kernel using this alongside the HTC Vogue build as it probably has closer hardware to the Opal (obviously, I'm talking about everything beside the MSM7500 400MHz processor that it has). I'm hoping it won't get to this cause I'm definitely under qualified for that at the time being.
What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command.
Click to expand...
Click to collapse
Could you post a screenshot?
I've tried compiling the kernel for pre1 (after changing the screen values)
Click to expand...
Click to collapse
I'm assuming you mean the touchscreen values? Try interchanging and see.
Trying to go back to a more stable build
Click to expand...
Click to collapse
I wouldn't recommend that. Defeats the whole purpose.
Why don't you try getting in touch with darkstar?
kshaurya said:
Could you post a screenshot?
Click to expand...
Click to collapse
A friend borrowed my digital camera, I tried my laptop's webcam but the text it too blurry. Couldn't fix it using gimp either. So here's exactly what's showing on the screen:
Code:
mdir: Cannot creat directory `/mnt' : File exists
modprbe: could not parse modules.dep
initramfs: Creating device nodes:
initramfs: Loading /initrd.d/10-initfs.sh module
initramfs: Loading /initrd.d/30-wingboot.sh module
Selected:
ROOT_DEVICE=/dev/
CMDLINE=debug quiet psplash=false loglevel=7 init=/sbin/init console=tty0 video=omapfb:accel fbcon=rotate:3 4 root=/dev/
initramfs: Loading /initrd.d/80-loopboot.sh module
initramfs: Loading /initrd.d/85-blockboot.sh module
booting from: /dev/
mount: Mounting /dev/ on /mnt failed: Invalid argument
Unable to mount rootfs device
sh: can't access tty; job control turned off
/ $
And after the prompt, on the same line, there's a flashing '_' waiting for input.
Using the original zImage (from the pre2 cab) it's right around here that the screen clears and the Wing Linux installation script kicks in.
kshaurya said:
I'm assuming you mean the touchscreen values? Try interchanging and see.
Click to expand...
Click to collapse
Will try that next.
kshaurya said:
I wouldn't recommend that. Defeats the whole purpose.
Click to expand...
Click to collapse
I meant it as just a temporary test to till the cause of the incompatibility is figured out. With less things that could go wrong, it'll be easier to locate the ones that are going wrong.
kshaurya said:
Why don't you try getting in touch with darkstar?
Click to expand...
Click to collapse
You're right. I should post a thread on the project's forums asking for his help.
Just figured I'd share.
First. All I wanted was an xterm on webtop + ssh client. I don't care about much else, that was my only goal. I already have a webtop dock ($80, well worth it, IMNSHO).
First I had to jailbreak. You can use virtually any method...I did the "moto-fastboot" with preinstall.img. I'm pretty sure all the downloads do mostly the same thing.
Once you have root...you need to install the superuser dohickie (just as the doco's profess). I renamed su to mysu, though 'cause some applications make the determination on if you are "rooted" based solely on the setuid existence of su.
Once there, you can install jaunty armel versions of lxterminal and openssh-client (a simple google search will give you a location for those deb downloads which you can install using dpkg. 4.5.91 (at least mine) does not have lxterminal. There are a lot of errors, but they work fine. I tried apt-get..yadda, but the sources.list includes resources in the 10. range. Don't know WTF that's about.
You need to have an android terminal app installed. In that, you need to change %admin to NOPASSSWD using the method described: http dev.toreishi.net/2011/03/hacking-the-atrix-step-3/
Then create the %gconf.xml as described at the end of the article.
The middle part is where I got screwed initially (broke my webtop entirely, and had to start over from factory reset). It has you going to specific line numbers which are version specific (a version that I didn't have). The things to note is that you want to change the policy for awn. First, make a backup copy of domain_policy.conf. In 4.5.91 is line is 1331. And use VI for christ sake: vi +1331 /etc/tomoyo/domain_policy.conf
The lines look like:
<kernel> /osh/usr/bin/awn
use_profile 3
Click to expand...
Click to collapse
Change the use_profile to 2
Then at the top of the file change the use_profile for lxterminal to 2.
(you made a backup, right)?
:wq!
Then reboot.
Happy xterm'ing.
This was a little messy to follow, but I got the gist from reading your notes and the notes from dev.toreishi.net/2011/03/hacking-the-atrix-step-3
Finally went and made the beginnings of a general flashing guide that should eventually cover the basics of everything streak related.
forum.xda-developers.com/wiki/index.php?title=Dell_Streak/Flashing_Guide
For the time being I ask that noone directly adds to the list and instead gives me the details to add myself. As it's a wiki I cannot force anyone to do this but i WILL edit it to match the phrasing or possibly remove it if it's redundant.
It is intentionally not excessively verbose/detailed as too much additional detail is only needed if you're completely new to flashing/messing with software.
It doesnt handhold your way though flashing stuff, if you dont know how to use the command line you should NOT be flashing roms as when you brick you only have your self to blame for not having the needed prereq ability pc wise.
It also only covers windows as I only work/dev on windows, if anyone on *nix/osx wants to give me the OS specific details i'll go ahead and add it
It's also missing most of the details on how to use QDL tool as i've never used it or needed it. I need someone to add/help me add the details in the same guide style without handholding users though using it
It's also very generic as installing most roms dont have specific requirements to them (excluding setting up SD's install.txt which is it's own thing)
it does NOT and will not cover using automated tools such as Gingerbreak or mutlirecovery flasher as automated tools ultimately mean that you do not wish to read the instructions on how to do it properly. (on the streak at least) (no offense to respective makers)
edit: it should also NEVER contain links to the forum and especially "read this post to do xxx" stuff, it should be more or less self contained except with regards to downloading files, which should either be direct links (preferably not on a filesharing site like multishare/etc) or links to another section of the wiki containing links
I know there's a couple users about with compiled guides but I cant recall who/which offhand as I dont need them myself. I'd like your input whoever you are
Great job!
Sent from my Inspire 4g using XDA Premium App
I have added some comments on the talk/discussion page on the wiki. If there is any specific topic you need help on in the wiki let me know.
TheManii said:
Finally went and made the beginnings of a general flashing guide that should eventually cover the basics of everything streak related.
forum.xda-developers.com/wiki/index.php?title=Dell_Streak/Flashing_Guide
For the time being I ask that noone directly adds to the list and instead gives me the details to add myself. As it's a wiki I cannot force anyone to do this but i WILL edit it to match the phrasing or possibly remove it if it's redundant.
It is intentionally not excessively verbose/detailed as too much additional detail is only needed if you're completely new to flashing/messing with software.
It doesnt handhold your way though flashing stuff, if you dont know how to use the command line you should NOT be flashing roms as when you brick you only have your self to blame for not having the needed prereq ability pc wise.
It also only covers windows as I only work/dev on windows, if anyone on *nix/osx wants to give me the OS specific details i'll go ahead and add it
It's also missing most of the details on how to use QDL tool as i've never used it or needed it. I need someone to add/help me add the details in the same guide style without handholding users though using it
It's also very generic as installing most roms dont have specific requirements to them (excluding setting up SD's install.txt which is it's own thing)
it does NOT and will not cover using automated tools such as Gingerbreak or mutlirecovery flasher as automated tools ultimately mean that you do not wish to read the instructions on how to do it properly. (on the streak at least) (no offense to respective makers)
edit: it should also NEVER contain links to the forum and especially "read this post to do xxx" stuff, it should be more or less self contained except with regards to downloading files, which should either be direct links (preferably not on a filesharing site like multishare/etc) or links to another section of the wiki containing links
I know there's a couple users about with compiled guides but I cant recall who/which offhand as I dont need them myself. I'd like your input whoever you are
Click to expand...
Click to collapse
Thanx!
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
There are at least two methods that work with the Glowworm.
You should not use any method until after you have
- made a noogie disk
- booted from it
- backed up your device
- restored that backup to a test disk (a 2 gig or larger microSD card, for instance) and confirmed that the test results in a disk that has 8 partitions.
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore seems to be only getting one partition restored and blowing out the other partitions.
I don't know if the stuff that eded is working on has come to fruition yet - he was looking at building a tool that could detect whether it was run on an NST or NSTG and root appropriately to the device.
The two routes I know work are:
- glownooter, the nooter project tool, includes Google apps and market support
- tinynoot, pasted together from various tools, gives you minimal root without google apps and with amazon appstore. Will work with either NST or NSTG because it's approach is so minimalist.
Thanks, roustabout! I will be sure to test the backups before I install anything else, then. Good to know!
In any case, what I am most concerned about is getting the right version of the rooting software for my device. I see that Nook devices have different firmware and that certain tools only work with certain firmware versions. I see no mention of my firmware version in any tools' websites, hence my apprehension.
hence the value of a backup
I saw your request on that and I think one of the issues here is that so many folks use Windows exclusively, and the backup process is so easy on linux that trying to tell people how to do it in Windows is like jabbing yourself in the eye with a stick, given that linux is free, vmware player is free, and linux can be installed and used for this job entirely in vmware player. On the other side of the coin, if you know nothing of linux, even using dd correctly will be a challenge since there's a pretty steep learning curve behind setting up a new OS successfully just to be able to get backups off an 80-130 dollar device.
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
I didn't mention it, but I also use Linux at home (Kubuntu, like Ubuntu but with a better UI). So many people are now using Ubuntu that I find it surprising that the instructions even bother mentioning the OSes for which the operation is as difficult as you say. I remember when doing things in Linux was hard and Windows was easy, and at that time Linux was hardly ever mentioned!
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
Click to expand...
Click to collapse
I did not realize that the 1.1.5 release is glowlight-only. Great, thanks, I'm on to hacking this thing!
ok, so for you the backup process is:
- make the noogie disk
- put it into your device
- power cycle your device
- when it boots to "rooted forever," connect the USB cable to your linux box
- once the linux box mounts the NSTG as storage, pay attention to which device it is mounting it at. Assuming it's sdX:
- backup with dd if=/dev/sdX of=backup.img bs=1M
When that's done, disconnect your NSTG, throw media of some sort, larger than 2G, onto your box and test your restore with
dd if=backup.img of=/dev/sdY bs=1M
Once that's done, do an
fdisk /dev/sdY
and a
p to print the partition table.
You should have 8 partitions (and your backup.img file should be just under 2 gig.)
Hack away; if you ever need to restore, you can just drop the virgin image back on.
I take a snapshot like this of my device every so often since remembering how I got to whatever config I liked is harder than just backing it up.
Thanks for the backup instructions, the idea of testing it on a DVD-ROM looks to save quite a bit of trouble with the actual device..
I rooted with this terrific guide:
http://forum.xda-developers.com/showthread.php?t=1675706
The process was simple. I do have an issue where I need to install a Hebrew font but ES File Manager doesn't seem to see the root folders. I'm having a hard time googling my way out of this one, bu all the other little issues were fairly simple.
One issue that I will mention that was hard to solve was the inability to perform searches in the Market. This page helped me resolve that issue:
blog.the-ebook-reader . com/2011/07/15/rooted-nook-touch-fixing-market-search-and-other-tips-and-tricks-video/
I just figured out that the file manager has to have Root permissions enabled. I've enabled it and added some fonts to /system/fonts but I still cannot get Hebrew text to display on this device. All I get are the typical rectangles instead of characters. Any ideas about how to proceed?
Thanks.
Restore Nook 1.1.2
roustabout said:
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore .
Click to expand...
Click to collapse
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
bubblewrapper said:
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Click to expand...
Click to collapse
Few people who will be knowledgeable will find your post buried here under this thread. i suggest that you simply start a new thread with a good descriptive title so that the gurus will find it.
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
roustabout said:
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
Click to expand...
Click to collapse
Actually, I think that I just need the fonts (or at least that would be a great first step). I put fonts with Hebrew glyphs in /system/fonts (using ES File Explorer in Root mode) but even after a restart it does not find the fonts (i.e. Hebrew text still shows as rectangles). I will fight with it some more in the coming days, if I don't succeed I will start a new, concise thread on the topic. There are plenty of Google posts on the subject, but all of the ones that I have seen (not Nook-specific) suggest that dropping the fonts is /system/fonts should be enough. Perhaps it is a permissions issue, I'll see if I can SSH into the device to see permissions.
dotancohen said:
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
Click to expand...
Click to collapse
Sorry that I am so slow to respond, but I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
ladykayaker said:
Sorry that I am so slow to respond,
Click to expand...
Click to collapse
Thank you! You don't need to apologize for taking time to respond, you are under no obligation! But I very much do appreciate your assistance and am happy to wait patiently! You will notice that I usually google issues first to try to save us both the time!
I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Click to expand...
Click to collapse
Thank you. It seems that those posts are Windows-centric summerizations of information found here at XDA-developers. The root is pretty much the process that I used, but from the guide right here which has Linux directions as well.
By the way, the-ebook-reader site is often not responding for me. Is it just for me, or does everyone have trouble with that site?
Thanks!
version 1.2.0
UK glowlight ships with 1.2.0. Use tinynooter to root this. You may have issues installing apps atm though but you will get the browser at least.
http://forum.xda-developers.com/showthread.php?t=1961835
Thanks, Loney. In fact, I got this Glowlight in the US, and it reports that it has software verion 1.1.5. But the information will be good for others who might google this thread!
Hello and thank you to anyone that can point me in the right direction.
I was recently given a Note 3 from a friend and for whatever reason it will not detect any SD card. The SD cards are fine and work in my other Android phones, Windows computers and anything else. So aside from that, is there any way to unlock the bootloader on this phone without the use of an SD card? All the methods I've come across mention one is needed. Thanks.
NM. I think I found what I was looking for here.
riotstarter said:
NM. I think I found what I was looking for here.
Click to expand...
Click to collapse
Possibly* a lesser-effort way - same thread, but here.
I say "possibly" because you didn't state which OS release was on the phone. (I can assume MI9->NC4, OB6, or OF1 as you must be rooted. NJ6, NK1, and PL1 are - as of this time - problematic for easy rooting).
There were some dependencies of the exploit code on OS version due to the location of the "CID" value moving around inside the kernel volatile filesystem /sys. You might have to take account of that in building/modding the code. (Either that or just get rid of the CID check if you know that you have a 0x15 eMMC chip device). Unfortunately, you need to thoroughly read about the first 350 posts in that thread to completely understand the discoveries that were made.
Anyway, some pointers to version compatibility are here.
* @beaups code is very straightforward. (@donc113 's mods of that code have the correct binary patching blob for the SM-N900V - beaups's github code was for the AT&T version of the phone) You probably will have more troubles setting up a toolchain than actually modding or compiling the code if you go that route.
good luck.
ps good to see someone in here that's not afraid of a compiler
bftb0 said:
Possibly* a lesser-effort way - same thread, but here.
I say "possibly" because you didn't state which OS release was on the phone. (I can assume MI9->NC4, OB6, or OF1 as you must be rooted. NJ6, NK1, and PL1 are - as of this time - problematic for easy rooting).
There were some dependencies of the exploit code on OS version due to the location of the "CID" value moving around inside the kernel volatile filesystem /sys. You might have to take account of that in building/modding the code. (Either that or just get rid of the CID check if you know that you have a 0x15 eMMC chip device). Unfortunately, you need to thoroughly read about the first 350 posts in that thread to completely understand the discoveries that were made.
Anyway, some pointers to version compatibility are here.
* @beaups code is very straightforward. (@donc113 's mods of that code have the correct binary patching blob for the SM-N900V - beaups's github code was for the AT&T version of the phone) You probably will have more troubles setting up a toolchain than actually modding or compiling the code if you go that route.
good luck.
ps good to see someone in here that's not afraid of a compiler
Click to expand...
Click to collapse
Thanks I appreciate the response. Yes I am on OF1 with a 0x15 chip. I've downloaded donc113's file and Android SDK/NDK. Does donc113's mod of the code already include what I'd be needing the SDK/NDK for? I'm definitely not afraid of trying something unfamiliar, I just want to ensure I'm doing it right. I'll do some more digging and see if I can figure things out a little more.
riotstarter said:
Does donc113's mod of the code already include what I'd be needing the SDK/NDK for?
Click to expand...
Click to collapse
Should be. Really the only thing you should check to see is if the path in /sys to the CID file on your OF1 phone is one of the paths that he is checking for. You can use the "strings" command for that.
OK, I just downloaded his code and did that ("strings" command). Here are the paths he is searching:
Code:
/sys/devices/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/cid
/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/cid
/sys/class/mmc_host/mmc0/mmc0:0001/cid
/sys/devices/msm_sdcc.1/mmc_host/mmc1/mmc1:0001/cid
If OF1 uses one of these, then you don't even need to compile anything, just run the binary.**
**there is a brutal form of "avoid compiling" hackery where you simply perform a binary edit of an executable file in order to change a constant value in the code such as a string. So long as the replacement string is shorter than the original, you can just replace the string and null-pad the unused length (as strings are assumed to be null-terminated in C). For example, if there was a pathname in a .bss or .rodata segment such as
Code:
/foo/original/path/filenameX
/bar/replacement/myname\0\0\0\0\0
this works so long as the replacement string's bytelength is less than or equal to the length of the original string. (And the code is not performing a signing or other integrity check of itself.)
Only to be used when you don't have the code to be compiled or emergencies such as when you are in a hurry LOL.
(Obviously you can not shorten or lengthen the file at all doing this: all the byte offsets in the file must remain unchanged).
https://forum.xda-developers.com/showthread.php?p=71448959
Sent from my SM-N900V using Tapatalk
Am on Sm-n900v (Rooted)
Android 5.0
0B6.
Want to unlock bootloader but need some strict instructions