why buttons of android on mini still not work?which kernel is the correct one?and how should I do to make it works?please teach me step by step.thanks.
15131331231 said:
why buttons of android on mini still not work?which kernel is the correct one?and how should i do to make it works?please teach me step by step.thanks.
Click to expand...
Click to collapse
有没有!!!!!!! 有没有直接复制过来就能用的 到现在为止好用的功能的都有的??????下载一个一个补丁 自己折腾弄不来啊 我想要直接用的
15131331231 said:
why buttons of android on mini still not work?which kernel is the correct one?and how should I do to make it works?please teach me step by step.thanks.
Click to expand...
Click to collapse
1.because no one aligned them
2.who knows
3.learn step by step -> [Android Porting Guide][Step by Step][PREVIEW] http://www.neopeek.com/viewtopic.php?f=57&t=6208
last intrd.gz allow you to download from market and alignment seem to be good
http://forum.xda-developers.com/showpost.php?p=12646939&postcount=83
Still having alignment issue with that kernel. Market works
Afaik its a kernel and not a initrd thing.
if you tell me an app for android to test touchscreen i will fix the alignment
schlund said:
if you tell me an app for android to test touchscreen i will fix the alignment
Click to expand...
Click to collapse
here
..
I think you not read post about updates! If you see old post you will see aligment is fixed, sd card is fixed (android market works!). You need this:
- http://www.megaupload.com/?d=FD9D58ZR
- replace with this http://forum.xda-developers.com/attachment.php?attachmentid=560477&d=1301942854
- replace zImage with this, install keylayout http://forum.xda-developers.com/showpost.php?p=12532884&postcount=387
Reboot phone
Hm.. with the kernel you posted, my wifi no longer works. with the Kernel from your package it worked.
In settings it just shows "error".
Finaly I made new system image with proper linking, group & user permissions, totally rebuilded from begining. Some initrd fixes... and good news is:
- on first use you will see diference from previos image and this new image
- full working adb (previous image version is not ok becouse when you use win-adb, adb is not working correctly, some links was not found, some files was not found...etc)
- full root permisions (include popup window when you execute command su from android terminal emulator)
- installed busybox and linked to /system/xbin
- working android market
- auto created and activated 200mb swap
- internal phone storage 512mb
- working DHCP (now, you not need to enter static IP for wifi!!)
- auto detecting and installing (Asia-HK-CHT, Asia-TW-CHT, zh) carrier
All other i'm not tested, maybe we have other working previously not working!
Here is all you need (full installation) including all fixes, all drivers, keylayouts...etc (you must delete all previous instalations including all files and folders created by android!)
http://www.mediafire.com/?7a2697pywoj4fcr
cardsharing said:
Finaly I made new system image with proper linking, group & user permissions, totally rebuilded from begining. Some initrd fixes... and good news is:
- on first use you will see diference from previos image and this new image
- full working adb (previous image version is not ok becouse when you use win-adb, adb is not working correctly, some links was not found, some files was not found...etc)
- full root permisions (include popup window when you execute command su from android terminal emulator)
- installed busybox and linked to /system/xbin
- working android market
- auto created and activated 200mb swap
- internal phone storage 512mb
- working DHCP (now, you not need to enter static IP for wifi!!)
- auto detecting and installing (Asia-HK-CHT, Asia-TW-CHT, zh) carrier
All other i'm not tested, maybe we have other working previously not working!
Here is all you need (full installation) including all fixes, all drivers, keylayouts...etc (you must delete all previous instalations including all files and folders created by android!)
Click to expand...
Click to collapse
whether you can post a new post, and the latest and the most comprehensive publication on the ROM, which like this, to alter this post after being on the top or being renewed sometimes later.
Related
PLEASE READ THIS POST AND UNDERSTAND IT CLEARLY BEFORE USING THIS ROM!
Heyo,
This ROM is now a port of the Nexus S Gingerbread ROM leak for the HD2. I would like to make it clear that this ROM may be unstable and not for everyday use! Since we're using a version of Android designed for a different device, we may have issues. The leaked build I'm using is available here - some modding is required though.
Starting from 0.05, my builds come with a 96MB Data.img file to get you out of trouble. I will provide data.img files that are 128MB, 256MB, 512MB and 768MB in size. You can make your own image via a terminal on Linux like this (don't type the dollar sign or the stuff behind it)
Code:
[email protected]:~$ dd if=/dev/zero of=/path/to/Android/folder/data.img bs=1M count=128M
[email protected]:~$ mke2fs /path/to/Android/folder/data.img
(answer 'y' to the question when mke2fs says "data.img is not a special block device, proceed? [y,n]")
Installation
Extract the "Android" folder in the ZIP file below to your MicroSD Card, pop it into your HD2, open File Explorer from WinMo, find the Android folder, tap CLRCAD.exe and then Haret.exe and watch the sparks fly.
For patches, extract the files in the patch archive to your MicroSD Card, overwriting any existing files.
Downloads
You can download the ROM from my server below. Please don't use download accelators, they will make my VPS cry...
LATEST VERSION IS 0.5, PLEASE DO NOT USE OLDER VERSIONS AS YOU WILL BE ASKED TO UPGRADE IF YOU SAY SOMETHING IS NOT WORKING ON THOSE OLDER BUILDS!
Version 0.01 > Get the goodness here! <
Version 0.02 (Patch only, download v0.01 first!) > Get the goodness here! <
Version 0.03 (Only a data.img for people who are having boot problems) > Get the goodness here! <
Version 0.05 > Get the goodness here! <
Version 0.05 requires 7-Zip to extract
Disclaimer
If I used any of your works and I did not acknowledge you, I am not claiming your work as my own. That would be the wrong thing to do (and I am not intending to "kang" any sources). I am also not responsible if your device is bricked or broken by direct or indirect use of this ROM.
Credits
spbeeking - The person that dumped the gingerbread SDK build in the other thread, in which that got over 210 Posts.
dakluck - Found the fix for BSOD (temporary).
m-deejay - Used his kernel. They rock.
jubeh - Found the problem with the SDK Build's lagginess.
supercurio - For the Nexus S ROM Dump.
...last but not least, all HD2 Owners that have given up 250MB+ of their MicroSD Card space to test GingerHD2.
Credit will be given where due. Watch this space!
Changelog Key:
+ means addition/change
- means removal
[!] means danger/caution.
v0.0.6 - Changed over to m-deejay's Gingerbread, working with his base to make a "lite" ROM.
This version is currently under development and will be released when deemed finished!
v0.0.5 Release 1 - ??/12/10 - Coming very soon.
+ Switched to Nexus S ROM Base
+ Replaced Nexus S default GL drivers with the ones for the HD2
+ Working Radio - SMS & Texts should work...
v0.0.4 - 10/12/10 - R.I.P, I totally fudged up v0.04 SDK Sources. Stupid me!
v0.0.3 - 10/12/10 - Patch 2
+ Basic data.img only for people with boot problems. Only use with older releases, don't use it with v0.0.3+ builds.
v0.0.2 - 8/12/10 - Patch
+ Switched kernel to m-deejay's kernel for working 3G Connection, data should work.
+ Fast bootup speed.
[!] Black Screen of Death occurs if you allow the device to go to sleep.
NOTE: BSOD can be fixed temporarily, see below.
[!] Erratic behaviour occurs if you haven't PIN unlocked your SIM Card before booting this ROM.
[!] Can take a while to do things, ie. very laggy.
[!] Black screen after HTC logo, no android logo.
[!] Keyboard comes up as white space (?)
... Possible other things that are buggy or whatnot.
v0.0.1 - 8/12/10
+ First release. Boots somewhat and then has problems.
Temporary Fix for BSOD in sleep (present in v0.0.3 and below)
After pressing power button once, press and hold power button till vibrate, then press back button. May take a few attempts but persistance is key.
(Credit to dakluck)
Bug List
None as of yet for 0.05... (Currently in-dev)
(Outdated) Checklist
WiFi? Not yet working.
BlueTooth? Not tested.
SMS Sending? Seems so (according to m-deejay).
Calls? Working.
3G Data? Working - select APN before going on the 'net.
Sound? Not working, but I'm working on it.
Camera? Not working.
Camcorder? Not working.
Screen (blacklight, touch etc)? Working.
Lights (keypad): Working.
Accerometer/G-Sensor? Not working.
(..to finish..)
Having boot problems?
Download the 64MB Data.img which is v0.03 (it's just a zip with the data.img I use for this ROM) and extract it to the same folder (for example, if GingerHD2 is located in GingerROM on your MicroSD Card, extract it to that folder). Then you should get to the desktop.
IcedCube said:
Reserved for changelog and other stuff
Click to expand...
Click to collapse
that's pretty nice gingerbread , cooool i can't wait to see this fully working
WOW !
Keep up the amazing work !!!
much appreciated.
I will try the build now.
Cool thank you.
thanks
excellent work,at less we can have a try for 2.3,thanks.keep working on 2.3
As I've said, you won't get into the Android UI, but if you can confirm that the kernel is getting stuck at "init: untracked process X exited unexpectedly", that would be appreciated.
Nice work, thanks for sharing. The init.rc file you mention is linked to a pastebin link in the original dump thread. Should be easy to search.
phiredrop said:
Nice work, thanks for sharing. The init.rc file you mention is linked to a pastebin link in the original dump thread. Should be easy to search.
Click to expand...
Click to collapse
No worries. My eMac is being a pain, so I'll have to find the pastebin link manually.
Just a quick bump, I'm just fixing the bootup issue. Once done, I'll upload a patch for you guys (and girls).
Cool... I will give it a spin
Sent from my HTC bravo using XDA App
Keep up the good work. My pray from Indonesia
Sent from my Nexus One using XDA App
Thanks for the credit and all, but didn't you say that you used your own sdk dump?
Sent from my Decepticon using XDA App
spbeeking said:
Thanks for the credit and all, but didn't you say that you used your own sdk dump?
Sent from my Decepticon using XDA App
Click to expand...
Click to collapse
I just wanted to give you a shoutout because you did the dumping before I jumped into the fray and dumped the sources myself
And on that bombshell, the v0.02 patch is up! See the second post for changelog, and first post for downloads. Here's how to install the patch:
For patches, extract the files in the patch archive to your MicroSD Card, overwriting any existing files.
Click to expand...
Click to collapse
It couldn't get any harder. Or could it...?
thanks alot!
seems like the 0.02 patch is down.
mirror pls!
the patch is down
where is the patch? the broken patch link....
youngquazy said:
the patch is down
Click to expand...
Click to collapse
Patch is online; uploaded to wrong folder on VPS. Oops.
Version 0.02 download link Damage
File patch is missing in your server. Version 003 is imminent? thanks
Hi,
My brother's desperate to get a bluetooth keyboard working with his HTC Hero (UK). Currently runs the stock HTC 2.1-update1.
It's easy enough to pair them (we've tried two) but they remain paired but unconnected. With my Galaxy S (stock 2.2.1) they work fine. I gather this is because the Hero doesn't support the SPP or HID profiles.
We've also tried most of the apps we can think of: Keypro (sits on 'connecting'), Blueinput (force-closes when you click to select they keyboard), the JP one (sits on 'connecting'). Looking at the forum for keypro it looks like they're aware of this issue and haven't yet been able to correct it.
I've heard rumours that people running custom ROMs (eg based on Cyanogenmod) have been able to get keyboards working.
So - has anyone managed to get a bluetooth keyboard working with one of these devices, and if so how? Would prefer a solution that keeps Sense installed but he says he'll let me go to vanilla android.
Thanks in advance.
For the benefit of future users (and because the forum seems to be littered with questions like this!) we managed to get it working by installing FroydVillain 1.7.2.
Main problem was the lack of a flash_image binary to install the nandroid recovery image, but we copied over one we downloaded and it worked without issue.
Keyboard was recognised immediately and works fine as an HID device.
That's interesting! But could you detail, what were the steps of this successful installing? I also have an old bt keyboard, which I'm unable to use with the hero... Thank's if you can explain any more...
Mostly we used the instructions from http:##www|villainrom.co.uk/vBwiki/index.php/Installing_Custom_ROMs , though with a change for flashing the rom as the binary wasn't available on his phone.
More specifically - use the Froydvillain download mirrors at http:##www|villainrom.co.uk/forum/showthread.php?3698 and the wiki page above, and download:
Froydvillain 1.7.0
Froydvillain 1.7.1 upgrade
Froydvillain 1.7.2 upgrade
Universal Androot
AmonRA Recovery image
Stick everything onto the SD card - either using a USB cable and your phone, or we just used a USB card reader.
Install Universal Androot. We used HTC sync and just double-clicked on the .apk but you could also use a file manager (the wiki recommends Astro).
Install Android Terminal Emulator from the market.
Root the phone using Androot (he was running the latest 2.1 so we used the 2.0-2.2 root button).
The next bit is where we differed from the wiki instructions. They tell you to type:
Code:
su
flash_image recovery /sdcard/[I]<name of recovery image file>[/I]
reboot recovery
We found that there was no flash_image binary on my brother's phone (the error read 'flash_image: not found' so downloaded one - there's a copy at http:##cyanogen-files.carneeki.net/flash_image.zip ; I can't remember exactly where we got the one we used.
The instructions we found with the binary suggested something complicated involving remounting the system partition (it's normally read-only so you can't copy the binary there). Equally, you can't run it directly from the sd card without remounting as it's set not to allow executables. We just ran it from the data partition:
Copy the flash_image file to the sd card and use:
Code:
su
cp /sdcard/flash_image /data/flash_image
chmod 700 /data/flash_image
/data/flash_image recovery /sdcard/[i]<name of recovery image file>[/i]
sync
Then just power off the phone and turn it back on with the 'Home' button pressed. You should find yourself in recovery mode using your new recovery image.
We then used Backup/Restore > Nand backup to backup the current ROM to the SD card. Then from the Wipe menu we ran through each option in turn to ensure a fully fresh setup (I gather this isn't essential, but is advised). Lastly we used Flash zip and sequentially flashed 1.7.0, 1.7.1, then 1.7.2.
Then we rebooted, and waited... and waited... and waited... The VillainROM logo with the scary red-eyed android pulsated for about 30 minutes before I gave up and removed the battery. I took out the SD card and turned the phone back on; this time it was only a few minutes before we found ourselves with a fully functional (and factory-fresh) phone.
We put the sd card back in and set up the phone as normal; then turned on bluetooth and paired the phone with the keyboard (with ours it was a matter of typing a PIN on the keyboard and pressing enter, and duplicating the number on the phone) - it was instantly recognised as an HID device and worked perfectly!
Hope that's of some use - as I mentioned before it's essentially the same as the standard instructions except for the step involving the missing flash_image binary.
[edit: sorry, I'm not allowed to post links it seems! You'll have to cut and paste, and replace the '##' with '//', and the '|' with '.']
Thank you, you were very kind! But it seems basically only a normal fv installation on a rooted phone... Only I become a bit confused with all the /data/system operations... I can try installing fv 1.72, but at the moment I don't want to give back my floyo 1.20, which is more responsive (in my phone), but gives no sinal of accepting to connect the paired bt...
Yes - it was just a new ROM install which did the job - only the lack of flash_image and the lengthy bootup before we removed the sd card confused us so hopefully it's useful to someone trying the same.
I've not heard of Floyo - but the reason I decided to try FroydVillain was that it was CyanogenMod-based rather than HTC sense based as I heard that HTC don't include bluetooth HID support in their ROMs.
The CyanogenMod changelog http:##wiki.cyanogenmod.com/index.php?title=Changelog suggests that HID support has been included since 6.0.0 so I'd expect anything based on CyanogenMod since that should be fine. I chose FroydVillain simply because my brother's not very techy and I wanted a fairly mainstream ROM for him...
Not so simple...! Out of curiosity, I went to install froyd villain, but as I imagined the result was the same! "Paired but not connected"... It seems that when you rooted the hero, something remained in /system, no idea what was it! If a developer could read this, perhaps he could understand what happened... Floyo is simply another rom based on cm... the difference is all in the rooting process, seemingly...
Not for me
Hi Guys,
as I have been running Froyd Villain 1.7.2 for a rather long time now I thought I might give it a try. As there is an Apple Bluetooth keyboard dusting around here I had quite high hopes.
The pairing process worked well and it shows an Icon with the BT Symbol encased in Black and two arrows. In the BT settings it tells me that I am connected to a BT device, never the less, no matter what input field I choose, I cannot type on the BT keyboard. There is no other Input method I could choose from either so it's still not working for me.
Damn.
What keyboard where you using?
Hey guys!
I'm currently into scripts so I thought about creating something new. But I didn't know what...
But a friend was just looking for something to automatically synchronize all apps on the phone with the PC (copy them to PC and back to phone when needed).
So I decided to create something for him and share it with this great community.
Currently it's a really early version. The only option is currently to copy the apps and their data to PC. Nothing more.
Feedback is always welcome.
Note: I've made this for Linux, it may work for Mac also.
I won't make a Windows version! Don't ask for it!
How it works:
It will use adb to pull all apps and their data to PC.
You'll be asked for a folder to save to only once, it'll be saved in a config file.
It will wait for your device to connect and then start syncing.
When it's finished it'll tell you where everything have been saved.
Requirements:
-USB-Debugging on
-Enough free space on PC
-adb in the $PATH-variable (don't ask how to, use Google)
WIP:
-Music, image and video syncing with PC
-Restore saved apps from PC to phone with the script
-Some speed improvements (cause it runs really slow)
-Get a nice UI (last thing to do! Don't ask for it now!)
Download:
http://depositfiles.com/files/z26tkazxm
Source code:
http://pastebin.com/DWWVJat5
Tips:
To get it really automated put it in your Window Manager autostart folder.
How to do this: http://en.gentoo-wiki.com/wiki/Autostart_Programs
When script asks you for the path to save, don't use the format ~/something - this won't work.
Use /home/you/something instead.
Don't put a / at the end of the path.
I'll correct this in future versions.
Use option -h to get the help with all commands viewed.
Enjoy it and give me feedback!
Sent from my loved HTC Desire [email protected]
Tutorials
Tutorials will go here.
I will now create one for the cygwin method.
Addon package for the cygwin method: http://depositfiles.com/files/lipqqsv8t
Changelog
22.01.2012:
-initial release
28.01.2012:
-added restore option (beta) -> see the -h option for how to
-started the development for music, picture and video sync
Ditti4 said:
I won't make a Windows version! Don't ask for it!.
Click to expand...
Click to collapse
((((((((((((((
do3in said:
((((((((((((((
Click to expand...
Click to collapse
It's because I don't know how do batch code and the windows version would get updates later.
You can try to recode it for windows if you give me credits.
I got an idea. Gimme till tomorrow...
Hey dudes!
I think we can get the script working on Windows with Cygwin, but I don't know (yet) how to autostart scripts in the Cygwin environment.
So it would be good to have someone to test it with Cygwin.
BTW: restore function should work know. Will do some testing today and if everything is right I'll release an update.
Sent from my loved HTC Desire [email protected]
I got a uk glow worm on the 27th (2 days before release ) and one of the first things that I tried to do was to root with glownooter. Bad idea! I thought that I had bricked my device. I had to use a lot of trickery to recover from a loading screen lock-up and once I did the first thing that I did was backup my nook (Which i should have done before).
UPDATE!
Please try my new ROOT install pack HERE:
http://forum.xda-developers.com/showthread.php?p=34216660#post34216660
This can be used to root and install the most requested things of this thread in just one zip.
Here is a quick guide to most things you will need to do to get started. I will update this guide as I discover and build new modifications.
To Backup and Restore
Follow this guide. Please do this BEFORE any other tinkering!
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Its important to check your backup before proceeding! Please listen to roustabout and dont skip this step... He knows what he's talking about
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks roustabout
To Root!
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994 (Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593 (Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
To Add Apps
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Setup ADB over USB
OK I have taken the liberty of building a quick driver mod to support your nook through USB. It works for me. First you need to have the android SDK if you don't already (sure you do but just in case ).
http://developer.android.com/sdk/index.html
Make sure you tick to install the android USB driver when the SDK is installed.
Browse to extras\google\usb_driver in your SDK folder (wherever you put it) and replace android_winusb.inf with my file:
http://dl.dropbox.com/u/13673492/android_winusb.inf
Next go to C:\Users\your_user_account\.android and replace adb_usb.ini with my file:
http://dl.dropbox.com/u/13673492/adb_usb.ini
In device manager, point google ADB driver to this and hopefully that should get you set up!
To test type
Code:
adb devices
Its working if you get something like this:
Code:
* daemon not running. starting it now on port ____ *
* daemon started successfully *
List of devices attached
[YOUR NOOK] device
And then try
Code:
adb install app_of_your_choice.apk
UPDATE
Install Multitouch Kernel With Overclocking
Install the CWM zip using your clockworkmod SD card
http://forum.xda-developers.com/showthread.php?t=1906507
:good: Thanks to johnjtaylor for discovering that this kernel works works.
Hopefully this more comprehensive guide will get others with this software to start playing around.
If this helps, be polite and say thankyou
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
David0226 said:
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
Click to expand...
Click to collapse
Thanks for replying. I'm actually working setting up ADB now. As for books I only just got my nook so all of my titles are epub format on an sd card so i wouldn't think it would be that. As soon as I get ADB set up I will post back my results incase it helps anyone else with this new software version.
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
I set up ADB.
Plenty of space in all partitions including /data for the apps that I want. Managed to install through "adb install some_app_i_want.apk" so problem resides with the amazon app store. Not really an issue for me because I have a specific set of apps that I want and don't need to browse the app store.
I will try to work out what's wrong for others.
staylo said:
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
Click to expand...
Click to collapse
Thanks. I'm looking for it now
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
loney01843 said:
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
Click to expand...
Click to collapse
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
staylo said:
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
Click to expand...
Click to collapse
You're obviously not that lazy. Thanks for looking and gathering all of the extra info I need. I'll send B&N an e-mail and see what they say. I wouldn't be surprised if they didn't want to hand it out considering you can use it for an easy root setup and install the amazon and kobo stores which could financially damage their advance into new territories! What are we to do! Can't even subscribe to a newspaper or magazine through the nook store yet!
I'll let you know when / if I get a response
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
roustabout said:
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
Click to expand...
Click to collapse
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
UK tinynoot attempt failing
loney01843 said:
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
Click to expand...
Click to collapse
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
smerrett said:
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
Click to expand...
Click to collapse
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
loney01843 said:
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
Click to expand...
Click to collapse
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
smerrett said:
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
Click to expand...
Click to collapse
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
loney01843 said:
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
Click to expand...
Click to collapse
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
smerrett said:
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/13673492/n2T-Recovery_0.2.img
This is the file needed to force factory reset. However a quality backup like you have is far more important.
For anyone who wants to give this a go, here is a quick guide for root access and app installs using windows tools until I can make something more complete:
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994
(Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593
(Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
loney01843 said:
If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
Click to expand...
Click to collapse
Great - thanks to your more detailed instructions, I have persevered and the second attempt at installing the tinynoot zips worked. Your post gave me the confidence to try installing apks for the first time and for anyone else who is unfamiliar with the processes used, I found these two pages useful for:
navigating within a command prompt (how naive): pcstats.com/articleview.cfm?articleid=1723&page=3
Pasting text into a command prompt (ditto): megaleecher.net/Copy_Paste_Text_Dos_Window
Sorry, as a newb I'm not trusted to post outside links yet. It took a couple of attempts of pasting and pressing enter to work out how to install using the adb code but it's not as hard as I expected.
I have tried installing the 1 Mobile Market which works but it is unable to install apps itself (not enough space).
Also, I have just installed NoRefreshToggle and can't seem to get it to work. Any thoughts - is 1.2 to blame? Really want this to work as Business Calendar Free is just a series of blinks at the moment!
Great! I'm glad you pushed onward and have root.
I am going through possibilities of other ways to install apps and mods.
No refresh is something that I would like as well but I think that the framework may need editing for 1.2.0. For fast mode a new kernel will need to be made or existing one modified.
Be aware that installing kernels not designed for this firmware can give you some serious problems.
Once I can setup app markets, I will work on these other modifications.
Stay tuned :good:
Take a look at the overclock kernel - it's got a lot of the norefresh features baked in, and gives you a nice ability to control both clock and kernel tuning (via the governor control.)
You're right, you can flash the two zips back to back with no ill effect, I was mistaken about what the second zip was doing.
I mistyped when I typed "nook touch tools," I meant nook color tools.
I'm very interested that the amazon store is not working in 1.2. I will see if the software's available for my device, so I can try to see what's happened.
As of now, the us bn site does not mention an os 1.2 for the glowlight.
** DoPa5 v1.0 (AOSP v5.0.2_r1 - Lollipop) is now available for US/UK/AU users **
If you would like to upgrade from the stock ROM, see this post for downloads and installation details
Click to expand...
Click to collapse
DoPa v2.0 is an enhanced version of the stock ROM that features a custom-built kernel. It is based on Hisense's August, 2013 update (build P756.6.02.20) and is intended for US (8gb) versions of this tablet. It does not support the 32gb models sold in the UK and Australia. See Post 2 below for packages to root this tablet and install CWM Touch recovery.
This ROM de-bloats the original, roots it using SuperSU, and adds several useful apps, among them: Apex Launcher and ES File Explorer. It also includes several Xposed Installer modules to tweak your system, including GravityBox and my Phab7 UI switcher. For the hackers amongst us, ADB always runs as root.
The kernel is built from Hisense's source and offers enhancements and bug fixes. Most notably, it provides USB-OTG support so you can connect USB storage devices (e.g. thumb-drives) to your tablet using an OTG cable. It comes in two flavors, a non-overclocked version included in the main package, and a separate overclocked version that can be installed (and uninstalled) independently.
Installation
Having CWM installed is a prerequisite; if you haven't installed it yet, see Post 2. This ROM is intended to function as an update, preserving your apps and data. Unless you want to start from scratch, do NOT wipe or clear anything - the install script will do what's needed.
copy the file(s) to your internal or external SD card
reboot into CWM, then select "install zip"
I recommend you select "toggle signature verification"; enabling this will confirm the file hasn't gotten corrupted (if you get a verification error, stop, then copy the file to a different SD card)
choose the menu entry corresponding to where you put the file(s), then select "sero7pro-bld60220-dopa-v2.0.zip" from the list
after confirming your selection, the update will display what it's doing; you should NOT see any error messages
if you'd like to install the overclocked kernel, you can do so once the main package is in place, or at some later time
reboot
Notes
when you attach a drive using the USB-OTG feature, it is automatically mounted at '/usbdisk'. Be aware there is no easy way to unmount it - you may have to use adb or a terminal app to ensure a clean unmount. This should only be an issue if you write to the disk; if you're only reading, it may be safe to just pull the plug.
the overclocked version of the kernel runs the processor at 1.5ghz rather than the standard 1.3ghz. Using it may result in a significant loss of stability on some systems. You may want to install one of the many apps that let you control the maximum speed to regain stability and reduce power consumption.
much of the app-bloat this ROM tries to eliminate (such as Sams Club or Playstore Magazines) may still be present if you've ever gotten updates for any of these apps. To get rid of them permanently, uninstall them using Settings->Apps->Downloaded. For "system" apps like the Google stuff, select "Uninstall updates", then "OK" when it asks if you want to revert to the factory-installed version (which doesn't exist anymore). The apps will be gone for good.
to enable the many tweaks offered by GravityBox and Phab7, open the Xposed Installer app and enable it via the "Framework" option but don't reboot yet. Back out and choose "Modules", then tap directly on the checkbox to the left of each module's icon (not on the icon or text). Now, reboot to activate their features.
Note: GravityBox's Quick Settings tiles and statusbar mods only work with the Phone or Phablet UIs (i.e. not Tablet UI). To get the full effect from Tablet UI, open Apex Launcher's settings and select "Homescreen settings->Use tablet UI mode"
Geek Alert: with the addition of DriveDroid (not included), this kernel lets your tablet emulate a USB CD drive that can be used to boot your PC. See the app's description for details.
Credits
xboxexpert - for getting things going
randomblame - for many of the patches used in this kernel
Files
new and improved:
sero7pro-bld60220-dopa-v2.0.zip - the DoPa v2.0 ROM with the standard kernel
sero7pro-boot-dopa0oc-v2.0.zip - the overclocked kernel
sero7pro-boot-dopa0-v2.0.zip - the standard kernel (in case you want to reinstall it)
old and tired: (do not use with v2.0)
sero7pro-bld60220-dopa-v1.1.zip - the DoPa v1.1 ROM
sero7pro-usbotg-dopa-v1.1.zip - USB-OTG add-on
sero7pro-macfix-dopa-v1.1.zip - random MAC address fix
sero7pro-sysui-dopa-v1.1.zip - removes screenshot button
miscellaneous:
sero7pro-bld60220-removed.zip - files that were removed from the DoPa ROMS (note: unlike the other files here, this is not a flashable zip. Unzip it, copy the apps you want to your SD card, then install them from there)
stock-v60220-full-update.zip - the complete 6.02.20 update from Hisense - this is the closest you'll get to the original stock ROM
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
XDA:DevDB Information
Sero 7 Pro (US) - DoPa v2.0 Modified Stock ROM, ROM for the Android General
Contributors
dolorespark
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.1.x
Based On: Stock ROM
Version Information
Status: No Longer Updated
Current Stable Version: 2.0
Stable Release Date: 2014-01-22
Created 2015-01-26
Last Updated 2015-01-27
Root/CWM packages
These packages will root and install CWM Touch recovery on the US (8gb) model of the Sero 7 Pro. There are separate versions for Windows and Linux. They have been tested under Win XP, Win 8, and Ubuntu, and should avoid problems encountered with other root/recovery packages.
The packages are modular so that you can run some or all of the functions as-needed. They consist of 4 scripts:
step0-DoItAll - displays some setup info then runs all 3 of the following
step1-adb - enables ADB ("Android Debug Bridge") to locate the tablet
step2-root - roots the tablet and installs the SuperSU app
step3-cwm - installs CWM Touch Recovery v6.0.3.2
Versions of ADB for each OS are included, so no other packages or downloads are needed. Usage should be fairly simple: unzip the package into a convenient directory, doubleclick on step0-DoItAll, then follow the (minimal) instructions. Alternately (and better), open a command prompt/bash shell, change to the directory where you unzipped everything, then run the script(s) from there.
Avoiding Frustration
If you haven't rooted an Android device before, please read the following because there are a few "gotcha"s. If you have but things aren't going as expected, review the following in case you missed/forgot something.
Developer options must be visible in the Settings app. If they aren't, select "About tablet", then tap on "Build number" 7 times. A small popup will tell you that you're now a developer. Back out to the list of settings categories - you should now see "Developer options".
USB debugging must be enabled under "Developer options". Please be sure it is. If it isn't, select it then tap OK when a warning popup appears.
Both Windows and Linux require extra files to be in place before ADB can communicate with your tablet. Click on the button for your OS to see the ugly details.
Windows
Windows requires USB drivers to be installed. Drivers that will work with the Sero7Pro (and possibly any Android device) are included in the package.
After enabling "USB debugging" and connecting your tablet, a wizard may pop up to guide you through the steps. If not, force it to appear by opening Device Manager. Look under "Other devices" where you should see something like "Android phone". Doubleclick on it, then select the "Install driver" button on the window that appears.
When the wizard pops up, tell it you'll select the drivers, then choose the option that tells it where to look. Click the "Browse" button and navigate to the directory where you unzipped the package. Select the usb_driver folder, press "OK", then "Next" - the drivers should install without any problems.
Notes: On Windows XP, the first wizard to pop up may want to install drivers for "MTP" which XP doesn't support. If so, cancel out of that, then wait for the "Andoid Phone" wizard to appear. On later versions of Windows, you may get a popup warning that the drivers aren't signed properly; if so, select "Install driver anyway". On Win 8-64bit, driver installation will fail unless you started the current session with "Driver signature enforcement" disabled.
Linux
Linux (or at least Ubuntu) doesn't allow user programs to access USB devices directly without the appropriate permissions in place. This package includes a file named 99-android.rules which provides those permissions
If you've never provided access to other USB devices, just copy the file to /etc/udev/rules.d. Otherwise, you can either copy it or merge its contents with the .rules file containing your other USB entries.
Note: both the rules.d directory and its contents are owned by root. You will probably have to use the sudo command to gain access. For example, from a bash shell whose current directory is the one where you unzipped the package, you'd enter "sudo cp 99-android.rules /etc/udev/rules.d". Also, be sure the file's permissions match the others in that directory. If not, run "chmod 644 /etc/udev/rules.d/99-android.rules".
Notes
When you're done, open the SuperSU app to enable it. It will ask to update the su binary. After selecting OK, the app will be enabled and will popup warnings whenever an app requests root access for the first time.
The Linux script is actually designed for both Linux and Mac OS X. However, I haven't fully tested it yet so I don't want to make any incorrect claims of support. You may have to correct some file permissions and will almost certainly have to run it from the Terminal app.
Files
sero7pro-root-win-dopa.zip - Windows
sero7pro-root-unix-dopa.zip - Linux
[Obsolete] Remove Screenshot Button / Add Instant UI Switcher
The mod originally described in this posting is now obsolete with the release of the DoPa v2.0 ROM which has both features built in.
If you are running an older version of that ROM, or XBoxExpert's ROM, or even the stock ROM, you can still remove the screenshot button using this CWM-installable package: sero7pro-sysui-dopa-v1.1.zip.
If you'd like to try Phab7, an on-the-fly UI switcher that lets you select Phone, Phablet, or Tablet UI modes, see this thread. Note: you must install the SystemUI mod to switch to Phone UI - without it, SystemUI will force-close when you do.
Good work. Hope to see more devs and more Roms
Really good. I'm using it right now. Keep going with the good work
Good Job! Looking forward to more posts!
Thanks for the nice work and good instructions. I'm using your stock ((build P756.6.02.20) rooted now and plan to try the ROM soon without Link2SD operational to keep all my apps.
Thanks again, I have updated my Sero to this ROM. Everything seems to be working perfectly. I look forward to many updates!
Thank you. Your ROM runs smooth and fast.
Great work man, downloading it now! Thanks!
Antutu result for this ROM
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Installed and working. Thanks.
taba4real said:
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Click to expand...
Click to collapse
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
larryf said:
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Why am I getting 10500 on this ROM then?
Does this root and cwm change kernel like xbox's?
lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Cooter007 said:
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Click to expand...
Click to collapse
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
lordroy said:
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
Click to expand...
Click to collapse
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My HomeScreen ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Cooter007 said:
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My desktop ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Click to expand...
Click to collapse
Of course as soon as I mention something, my Sero decides to play nice.
Just got a score of 13861. I didnt change anything, it just decided to score better for some reason.
lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Sir i used to get this with Power Saving mode instead of Perfromance priority mode....... =):good: