Related
Hey Guys at first sorry for my english i'm not good in it. And I'm a Android newbie I just gained a bit exerience with my Touch Diamond but it's broken now..okay but that's not the probleme....
If got a question:
After about 2 days of searching for an android 2.0 or 2.1 ROM I was a little bit confused of the diffrent news everybody was talking about. I'm root on my Hero. That was the first an last thing I made with my device.
1. Everybody is gonna talk about MoDaCo 3.0 but when I was trying to download his ROM my browser never got a request. Is the site down, where that ROM is hosted ?? Could someone give me a working link with this ROM ??
2. Is there a ROM with Android 2.0 or 2.1 outside or even not ??? And if yes are they working well ???
Would be nice if someone can help me =) thanks a lot.
Please answer soon if you know something about that =)
Greetz BassdoxXx
you can get modaco's roms at his website, www.modaco.com.
in the android development section there are some 2.0/1 roms, none of them works flawless, see for yourself if it fits your needs.
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
BassdoxXx said:
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
Click to expand...
Click to collapse
What? Does ISP's block that site? Lol, would never happened in Norway
there is a few 2.0+ roms out there for the hero.
most seem to be very usable now.
best sense ui would be lox/behnaam community release on 1.6.
http://htcpedia.com/forum/showthread.php?t=1448
there are two aosp roms worth looking at.
lox aosp ( im using that on a daily basis)
http://htcpedia.com/forum/showthread.php?t=1416
jnwhiteh aosp
http://htcpedia.com/forum/showthread.php?t=1528
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
sorry for the double posting. I've accidentally posted twice and I am unable to remove the post.
Hope anybody can help me please.
pvdeejay said:
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
Click to expand...
Click to collapse
i am on mcr3.0, i looked in the market, i can find 8 apps for eyesfree, tts is one of these. i didn't try to install one of these, but usually it works. the search for talkback returned nothing.
not that i want to be rude, but wouldn't you be better off with another phone if you are blind? i can not imagine a touchscreen only phone would be suitable for someone who is not able to see... especially because there are great devices out there that have a full qwerty keyboard, and come with android 2.0 out of the box... imho this would be a better solution.
again, the last thing i want to be is rude, but maybe this was your mistake: you posted in the htc hero section of this forum, the hero is a touch screen only device, including a virtual keyboard on the screen. it has only six buttons and a trackball, and two rocker buttons for the volume. just to make clear we are talking about the same device
if you are still up for the hero you could try the 2.1 rom from here: http://htcpedia.com/forum/showthread.php?p=30418&posted=1#post30418
best you try for yourself, it has some drawbacks, but maybe in areas you don't need (afaik syncing with exchange does not work for example, which wouldn't be a problem for me...). otherwise it might be worth to wait another week or two, we all are waiting unpatiently for the official eclair release from htc
keep asking if you need to know more, but maybe open a new thread, since your problems are very specific, and might drown between all the newbies question about "how to root my phone".
Hello,
Thanks for your reply and a great attitude.
Yes it may sound strange I have really got HTC Hero here. I know I'll be having problems with virtual keyboard but also I am afraid accessibility features of Android phones are not really such mastered one can use it daily. For example reading emails and content from the web browser is not yet possible. I just want to try how things work and I would also like to touch the virtual keyboard. If I can memorize computer keyboard and use it daily, typewriter keyboard, nokia mobile phone keyboard, then perhaps I might be able to make some use of this too.
I am sory but here are some more questions:
I haven't yet verified with some sighted friends but... is it possible my hero is running even older version of android like Android 1.5? I've based the assumption that it's most likelly running 1.5 because majority of the devices I was reading on the net are running it.
You've been triyng to locate eyes-free applications on the market but you were unable to find talkback. Are you sure you are running newer version of Android than 1.5?
Talkback is supposed to be installed with Android 1.6 andd 2.0 by default and you should be able to find it in the accessibility menu of your phone. I am not sure how well this applies to the custom roms.
Talkback requires google's accessibility api which is reported to be available on Android 1.6 upwards.
To tell you the full story first I've asked on the eyes-free google group whether some accessibility experts from there can help me but no one knowledgeable enough has replied to my query, so I'm trying my luck here then.
Oh I am really excited since I've got really well formed informative reply.
Thanks again
Edit:
Also, I've seen somewhere in the forums here this leaked HTC rom does not support the market. Has this been rectified already? You know if market does not work then most likelly I won't be able to install these applications I am tallking about.
Also you are mentioning possibility to wait a few weeks until HTC guys role out the official update for Hero. Wouldn't that break chances I will be able to root my device later?
Edit2:
Ooops, I should read better next time. Market works on this rom. The problem is paid apps can't be installed which is hopefully not a big issue for me since most of the accessibility enabled applications are free.
Which of the downloads from Hero 21 do I need?
63.18.55.06JU_6.35.09.26) or No Wipe Download. I will need a wipe I am sure but since this link says nowipe I am ehmmm. confused.
pvdeejay,
Unfortunately there is not an 'official' update for Android 1.6, 2.0 or 2.1 as of yet. There are rumours of one coming out soon, but nothing cast-iron yet.
You are correct in that the Hero runs 1.5. It does say it under Settings | About Phone (bottom item on list)| Firmware Version (bottom on list again), although without a working screen reader, there is probably little use in knowing how to find that.
If you did want to upgrade, I'm sure plenty of people could help find a ROM that would suit. The only issue with that is that you would need a rooted phone with a custom recovery image installed. Unfortunately, a lot of the procedures would not be easy for you, as the software that you might need to use to go through the procedure is probably not designed that well for accessibility tools. I don't know what kind of software you are using, but some of the instructions for making goldcards are quite complex, and involve editing some numbers in a 'table' which could be quite difficult for you, I would imagine.
I'm sure a friend would be able to help you out with making a goldcard/rooting if you did want to install a custom ROM (you'll probably be waiting a while otherwise ). They could even root their phone while doing yours (just share the goldcard between the devices).
Nonetheless, there is probably a ROM out there with little removed from it. I'll have a look just now, but you would need to have your phone rooted to do anything just now.
When it comes to rooting and installing custom recovery image. Do you thing the following instructions might work for me?
These instructions don't require a gold card:
- How to Root HTC Hero and Install Amon Ra Recovery Image
- How to install a custom rom on a HTC Hero
Hello,
Here are some numbers I've asked my friend to read from system -> about screen. The phone interface is in czech so I am unable to get some names translated to english, but I believe some of the geeks will understand these identifiers and might be able to help me what is best:
Code:
firmware: 1,5
63.118.55.O6U|6.35.04.25
2.6.27-a5504199
Build number: 1.76.405.6 146733 CL# 47214 release-keys
Software version: 1.0.0.A6288
pvdeejay,
to sum it up:
the hero definitly runs on android 1.5. there are no roms for older android versions, and a few homebrewn for newer versions, as we said already.
i searched for talkbalk on my 1.5 rom, so it is obvious that i couldn't find it...
about rooting of newer roms: it is just a matter of time, sooner or later there will be always methods of rooting a rom. what i meant by waiting is: wait until the official update is out, then wait a few more hours until the first rooted and customized rom is out
@pvdeejay,
I would have to agree with kendong2 that waiting for the official ROM is probably the best idea for you at the moment. There are no guarantees that an unofficial ROM would help, and it would be another user interface to try and learn.
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Sorry guys originally I believed I am slowly getting into the matter and am begining to understand how flashing / rooting / upgrading home brew firmwares works on these phones.
After these 2 posts I feel like a total noob again.
Now again some very concrete questions:
What about these 2 guides I've posted links to?
Can I somehow got [Recovery] [13-Dec-2009] RA-hero-v1.5.2 installed so I will be able to do nandroid backup and then possibly flash some new roms?
Can I really brick my phone by trying to install amon ra?
Originally I thought the process works as follows:
1) get the custom recovery image installed (that's the amon ra in this case),
2) do a nandroid backup which will dump everything usefull on to the memory card,
3) backup and reformat the card,
4) download a rom, rename it to update.zip, put it onto the root folder of the cart, reboot the hero in recovery mode, do the wipe of the data partition, and run update,
5) reboot again and believe it's good.
Also some very significant bit is the thing you are all calling the radio. I am afraid I've not identified this bit thus it's missing in this summary.
Which files will I need to download if I decide to try Android 2.1 community edition 1.8? Are these files I've copied links to a few posts earlier both needed?
Can you please check this list, identify the things I am missing, and make suggestions and corrections why this may not work on my device based off of those number I tried to put down here?
Even if I won't be able to do this right now I'd be happy to get corrections as I can learn something new.
Of course I won't be doing all this on my own. I will ask my bro to read all the stuff to me and we'll do it according to your advices.
To give some bits about me and my computer skills, I believe I am a Windows power user, Basically I do also understand unix, I know what's bash how the files are arranged in a file system, can use command-line tools, telnet, ssh. I am working as a network administrator here so some background is there really.
Hi pvdeejay,
Answers to your questions here.
You can actually use fastboot to 'temporarily' load up the AmonRA recovery image into memory and run it from there. I do that on my phone, for the simple reason that I can't be bothered ) ) to flash the recovery. Once you get AmonRA running, the first thing you should do is make a Nandroid backup. It will be saved to your SD card, so then get the nandroid directory of your card and save it to your PC (just in case!)
So, here's how you'd go about this.
(Make sure you have the android sdk installed, and that adb and fastboot commands are working). USB cable should be plugged in throughout.
Before you begin, put the ROM you want (ie. Android 2.1 community edition 1.8) into the root of the microSD card (a .zip file).
Code:
adb devices
Should list your phone's serial number
Now turn off the phone, and turn it on with the back key held down (the one at the very bottom right of the device).
You should enter fastboot mode. Now type
Code:
fastboot devices
and you should see the serial number again.
Now type
Code:
fastboot boot AmonRA.img
where AmonRA.img is a file in your present working directory that is the filename of the latest custom recovery image. This does NOT flash your phone, it merely runs the image (pretty much as close as you get to risk free, other than sitting there with a tinfoil hat on )
See screenshot of the recovery image here:
http://www.sizzledcore.com/wp-content/uploads/2009/12/RA-hero-recovery-image-500x375.jpg
Make the Nandroid backup by choosing 'Nandroid Vx.x Backup' and waiting a while.
If your ROM needs a wipe first (most new ones do), select Wipe data/factory reset. You will lose all your user data on the device (but you've got a nandroid backup just in case)
You're now good to go. So choose "Apply sdcard:choose zip"
Now select the custom ROM zip file you downloaded. It doesn't even need to be called update.zip! Choose it from the list and push trackball.
Wait for the update.zip to go in. Do NOT turn off the device or pull the battery. First boot can take a very long time (upto 30 minutes). Just keep it plugged in via USB and wait...
As for radios, see http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/ and look at the section titled radios. The latest one is in bold. It is a .zip file as well, that you use these exact same instructions for to install (don't do the wipe or anything like that. Just install the .zip file)
anon2122 said:
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Click to expand...
Click to collapse
this is correct so far, i did the same, except i installed the recovery. i play a lot with my phone, the installed recovery image with the nandroid backup is the best i have ever seen for a phone...
@pvdeejay
you always write so much...
i try to answer everything:
the two guides you posted are good for your situation. i never tried flashrec, but from what i read it is safe to use. i installed my recovery image through fastboot, the guide is here: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
i have no idea how this works out for you, but my honest suggestion would be that you have someone seeing assisting you, you CAN brick your phone, though it is not likely if you follow the instructions precisely. the process is not very time consuming at all, so you don't need to bother anyone for days of their time.
edit: and now i read your post to the end and saw that your brother will be helping you, so you are on the right track
once you have the recovery installed you can make nandroid backups, and i would suggest that you do this first thing after installing the recovery, better make a backup too much than one too less...
the 5 steps you described are correct, except there is no need to rename the zipfile anymore, you can select any .zip from your sdcard.
the radio part is the number that begins with 63.18.55.06, then comes two letters and then more numbers. as by now the version can be identified by the letters, with JU being the up-to-date one. in general you can say the newer the better, but you have to try for yourself. start with the newest one, if you have problems go back.
thanks this seems to be pretty doable plus I will easily be able to restore the current data backed using nandroid backup.
Which android SDK do I need the latest one?
The commands I need to type are supposed to be typed on the PC or on the phone? I assume on the PC but I just would like to ensure.
Hero21 1.8 community edition has a recommended radio listed in the first post. Is it necessary to install that one as well? What should I install first the actual rom or the radio? Do I need installing radio at all? Should i do the same with radio i.e. renaming it to update.zip and using amonra to install it?
Also will I be able to use this method even if I install another rom (running amonra without actually flashing it)?
Edit:
sorry guys did not realize renaming to update.zip is no longer needed.
Edit2:
is there an easy way on how to access sd card from windows? I can't just remove the card from phone and insert it into my laptop because I don't have the proper adapter. Previously my boss was using the hero and perhaps it would be nice to backup the sd card first.
Edit3:
uhmmm, installing android sdk is perhaps not as simple as it sounds.
I have just seen this article.
I am on a limited gprs internet connection, can you please suggest sdk features I won't need to save some download bandwith?
- you need only the adb binary (thats adb.exe for windows) from the sdk, the rest is not needed for this.
- install the radio from the 2.1community-rom-thread, it is the newest. install the radio first. DO NOT PULL THE BATTERY until the phone has rebooted completely. if you pull the battery during radio upgrade your phone will be dead. it takes a few minutes, do not panic!
- you can copy the contents of the sdcard via the usb-cable, plug it into your pc and pull down the notification bar...
Do I need to run SDK Setup.exe when I have downloaded android sdk for windows?
Or can I simply run that binary from the command-line without the installation?
Do I need any USB drivers so my phone can be recognized?
So, I used to run WinMo way back when, and I'm familiar with flashing, HardSPL, blah blah blah, whatevs. I haven't done the rooting process yet on my phone because I'm finding it hard to find a few key things that I need.
-What is the effect on my phone when I root, in regards to data? Do I need to backup? If so, can I backup on my SD card or is everything wiped? What program could I use to backup?
-Are there any crazy little tweaks or tips that anyone has to help guard against a brick?
-I've read the pros and cons list, but can I get more details from someone? Can this help with battery life, allow me to flash my radio, increase general connectivity, etc.
All help would be greatly appreciated, and I'll plan on doing a donation today. I've just been out of the loop (running WinMo 6.5 style out of the loop:/) so some advice to a rook would be great. My goal is to get out of school and come home and root and fiddle with things with little to no problems. Thanks a ton everyone.
Dig Life!
D
The process of actually rooting doesn't mess with any of your stuff.
I use Titanium Backup to restore apps after flashing roms.
In general, most of this stuff COULD help your battery life, here there are Devs that will help - with sprint you get their tech support.
Well, I DL'ed TB and it says that I have to root first? Am I missing something here? Is it ok to root or will it delete all of my apps and what not? I mean, if it does, it isn't really that big of a deal, considering I can just download them again, I'm just looking for input.
copsgottanks said:
Well, I DL'ed TB and it says that I have to root first? Am I missing something here? Is it ok to root or will it delete all of my apps and what not? I mean, if it does, it isn't really that big of a deal, considering I can just download them again, I'm just looking for input.
Click to expand...
Click to collapse
I'm pretty new, too, but I think I can answer your questions. Rooting (at least with the One Click Method I used on my Epic) doesn't destroy any data/apps on your phone. It simply gives your user root access to the underlying OS. Once that is achieved, you can modify things and tweak things. Titanium Backup will let you backup all system files and data, but only AFTER rooting.
This is not a ROM flash or anything like that from the WinMo days. I haven't gotten that far on Android, so I'm not sure what the flashing options are yet, but rooting is harmless on its own. It will let you royally screw things up though, so once it is done, be careful what you do.
Well, I tried to do a few things like listed in the One-Click root thread, but I guess I'm just not getting it. Now that I know the effects of the root, I'd like to be able to actually do it, but I don't have enough details. I haven't ever rooted before, and I'm finding it confusing. What was listed in the one-click thread wasn't specific enough for me, I don't know if I need to run from SD card, what the ADB thing is, nothing. I was a WinMo master and I'm finally coming to Android which is literally worlds away from my comfortable norm.
what os are you running? the one click comes with everything you need. theres an osx version the windows version that noobnl updates and the linux version i maintain
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
copsgottanks said:
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
Click to expand...
Click to collapse
I wouldn't exactly call root harmless..in itself it is ok..but if you give root access to a program that program has FULL access to your system..aka anything inputed on your phone or stored on your phone can be accessed by the program with root access. Though generally its not a problem..just careful which programs you allow to use root access.
Also, at what point are you getting stuck? did you install the drivers? are you getting any sort of errors or etc?
There is also some good reading over at SDX Developers.
I have hacked and rooted before, WinMo, Palm, HTC Hero, but this one was tough. It basically took me two days off and on, but it worked - finally.
Downloading drivers is a b--h, they are finicky and I needed all of them, kept
hanging on 2. They are slow, and kept looking for sources.
Search here, there is good info, then look there (above) I used OneClickExploit 2.2.4 which finally worked. It had some of the same files
in other methods, but this one worked.
I'm not changing roms, did on Hero to 2.2 because they weren't getting upgrade but I'm just going to hang and wait for Froyo.
Good luck
copsgottanks said:
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
Click to expand...
Click to collapse
Download and unzip the one-click archive in to a folder. Double-click the run.bat. I had some problems where it would start and then hang. I often had to kill it and rerun the batch file. Sometimes I had to end task on the adb.exe process. Eventually after rebooting the phone, etc, I was able to get it to work. Not sure what the exact problem was. I think part of it was connectivity to the phone via usb. Connect through a port on your computer, not a hub.
Also, the batch file is just a bunch of commands. You can open a command line in the folder where the batch file is and run each line in the batch file individually from the command line. That will give you some idea of what is happening and where it might be failing.
Like I said, I had to stop and restart a bunch of time before it finally got through to the end of the batch file correctly. When it did, it was fast. Not sure what was happening.
gTen said:
I wouldn't exactly call root harmless..in itself it is ok..but if you give root access to a program that program has FULL access to your system..aka anything inputed on your phone or stored on your phone can be accessed by the program with root access. Though generally its not a problem..just careful which programs you allow to use root access.
Also, at what point are you getting stuck? did you install the drivers? are you getting any sort of errors or etc?
Click to expand...
Click to collapse
When I try to install the drivers I get this message:
"The MSS InstallWizard was not Completed for SAMSUNG USB Driver for Mobile Phones V1.3.450.0
The MSS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones V1.3.450.0. Click Finish to exit the wizard.
And I'm basically stuck there. I've searched around and can't find any drivers that will work. Like I said, I'm on 64-bit Windows 7 with a clean OS and no previous negative install history. Not sure what the issue could be?
Found the drivers and everything that I needed and I'm rooted, but now I have one more question. I don't plan on flashing any roms, I'm alright with the stock rom, at least for now. I wanted to know what rooting will do in regards to over the air updates on my phone. Will I be able to OTA to FroYo when released? Any info would be great guys, thanks.
where did you find the drivers? I am having the exact same problem that you had where the installwizard cannot download finish installing the drivers for whatever reason
Hi guys!
I bought a Nexus 7 a few days ago, This is my first Android device, my first tablet and my first attempt at rooting anything. so I was hoping for some help from the experienced folks because frankly i don't know what I'm doing I was hoping you could help me with a sort of beginners guide for rooting, like what i should look out for, whats the safest and easiest toolkit, rom, kernel to use. I know i have so much to learn from you guys and I've been reading some of the threads and im starting to get a bit of it already just asking for a step by step of what i should do im mainly going to use my tablet for torrents, games, and some light photo editing and lots of comics! so how do i start? hope to hear from you guys soon THANKS IN ADVANCE!
For rooting the tablet ..its safe ,the important thing is to follow the instructions .so to root it you can use one of the toolkits in the development section,I preferred wugfresh toolkit more ..but its up to you the other one is also good ... Here's a video which explains the root procedure
https://www.youtube.com/watch?v=wI0_ylxyrWA&feature=youtube_gdata_player
btw update your phone before rooting it
And for flashing Roms there are a lots of guides on how to do it..just use Google
If you got stuck in any boot loops just use the toolkit you first used, to restore to stock or restore with a nandroid backup
Most important thing when you root. before touching a file ..do a nandroid backup in recovery to always stay safe ..
That's it enjoy the forums
Sent from my Nexus 7 using xda premium
BigJoey010 said:
For rooting the tablet ..its safe ,the important thing is to follow the instructions .so to root it you can use one of the toolkits in the development section,I preferred wugfresh toolkit more ..but its up to you the other one is also good ... Here's a video which explains the root procedure
https://www.youtube.com/watch?v=wI0_ylxyrWA&feature=youtube_gdata_player
btw update your phone before rooting it
And for flashing Roms there are a lots of guides on how to do it..just use Google
If you got stuck in any boot loops just use the toolkit you first used, to restore to stock or restore with a nandroid backup
Most important thing when you root. before touching a file ..do a nandroid backup in recovery to always stay safe ..
That's it enjoy the forums
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
well said, but here are some more tips: DO NOT PANIC!! when something goes wrong, which is likely, as you are a newbie to rooting, one thing you must not do is panic. calm down and troubleshoot, what did i do wrong? how do i fix it? and according to my experience, whenever a door slams shut behind you, a new window opens. if one method doesn't work, try another method.
also, read through the entire procedure list before start doing the steps. make sure you understand what is required and how to do it before accidentally doing something stupid. believe me, its happened to me b4, not a pleasant experience when you realise you dont actually meet the criteria to install something. btw, here is a list of common names given to the nexus 7: Nexus 7 (duh!), N7, grouper (wifi only) Tilapia (wifi+3g)
good luck rooting!
Read through the stickied threads and try to understand them. It won't happen right away though; your head will probably spin the first couple of times through.
There is really no "overnight" learning curve to this stuff - even if you are an old hand with Linux/Unix.
BTW, it is important to point something out: There should be no reason for you to feel like you should be in a hurry to root. The N7 is a fantastic device, even when used in a pure stock experience.. You are not going to be missing out by not rooting immediately. Spend some time with your device getting used to the Android way of doing things, and start reading XDA with a relaxed frame of mind. There is plenty of time. It would be different if you have lots of prior Android experience - but you said it - this is your first Android device.
OK, rooting. To try and keep you safe while you are a noob, I'll give this recommendation:
If you see the word "flash" (verb) near the word "bootloader", RUN AWAY!.
The most dangerous thing you can do to an N7 is mess around with the bootloader. You can turn your device into a useless object by getting things wrong, and it is a little bit rare that you need to flash a bootloader anyway. You have been warned.
So, make sure you know the difference between bootloader and "boot partition".
Most Android devices have a single flash memory chip in them which is divided up into a number of partitions. There are 5 principal partitions and about the same number of less frequently used partitions:
THE 5 PRINCIPAL ANDROID PARTITIONS:
(B) boot - a raw blob of binary data containing a "kernel" and a "ramdisk"
(B) recovery - another raw blob of binary data containing a "kernel" and a "ramdisk"
(F) system - The "ROM" part of Android - all the factory (or customized) software, used read-only
(F) data - User data and customizations. A "factory reset" simply erases all the files here
(F) cache - a scratch area used for downloading files and other maintenance operations
B = binary, bootable
F = Filesystem
Now, the two bootable partitions - boot and recovery - are very similar in structure, but extremely different in purpose. (In fact, in stock devices, they both use a private copy of the same kernel) The "boot" partition can produce a UI (User Interface) after it starts up only in conjunction with healthy /system and /data filesystems containing the Android software. But the "recovery" partition can produce a minimal UI even if the /data and /system filesystems are completely empty of files; so it (the recovery boot) is used to do all maintenance operations - including things like installing new /system software or erasing all user data.
So, and Android "rooter" will usually replace the very minimal (and locked-down-security) stock recovery partition with a "custom recovery" that is more friendly, and the vast amount of the "flashing" operations will take place using this custom recovery.
When people talk about "ROMs", they generally mean only TWO of those five partitions mentioned above: the "boot" partition and the "system" partition. When a "ROM" is flashed using the system partition, the usual procedure is:
- The rooter makes a full Nandroid backup.
- The rooter performs a "factory reset" procedure which erases the /data*** and /cache filesystems
- The rooter then "flashes a ROM", which puts in place a new boot partition, erases the /system partition, and then re-populates the /system partition with changed Android system software.
Upon booting an Android phone/tablet after this procedure, the device will behave as if it just came from the factory - but now with a different custom version of Android software. Note that this means that all the things you customized in the previous ROM - wallpapers, settings, home screen app icons, widgets, market apps downloaded, etc - will all be gone. So, folks that make a habit of hopping from ROM to ROM generally have some tricks up their sleeves for making the re-customization of a freshly-installed ROM a little less tedious. (Things like using custom launchers that allow you to save homescreen customizations, apps to restore previously-used market apps & their data, etc, etc, etc)
*** there is some funny business with Android devices that have no removable SDcard storage devices such as the Nexus 7 - the user's "SD card" is emulated, and the files that are stored there are actually stored in the /data filesystem. So, custom recoveries usually have a "factory reset" procedure which deletes all files in /data while scrupulously avoiding erasing things in this /sdcard area ( == /data/media ). This allows you to keep things safe from wiping (pictures, music, ROM files, backups) while still installing a fresh and un-initialized ROM. Note that the stock recovery in the N7 does not do this - when you use the "factory reset" of the stock recovery, EVERYTHING in /data gets erased - everything!
While you are reading about Android, here are some questions/searches to look up that concern rooting activities... have fun!
- What is the difference between grouper/tilapia (or nakasi/nakasig )?
- What does it mean to "install a new launcher" or "install a new home app"?
- What is Android fastboot used for?
- What is the Android ADB (Android Device Bridge) program used for?
- What is the difference between a boot image and a bootloader?
- How do I go about making a Nandroid Backup?
- What are the Carbon and Titanium Backup apps for? What can they do?
- What file browsers on the market are "root aware"?
- What Android settings can be saved by the Google Play Store, and automatically restored into a new ROM?
- Is there a difference between the "Superuser" and "SuperSU" root kits?
- What are the special Hardware Button Combinations used by the Nexus 7?
- What is the Google Android SDK?
- What custom recoveries are available for the Nexus 7?
- How many unique operating modes does the Nexus 7 bootloader display? What are they called?
- What is a MD5 signature? How can it help me stay out of trouble?
- What does soft-booting a bootable image with fastboot do?
- How many (Windows PC) drivers are needed to use ADB (with both the custom recovery and also the regular OS) and fastboot (with the bootloader), 2 or 3?
- Suppose I soft-brick my N7 - how will I transfer files to and from the N7 in this situation?
- What is the difference between adb push/pull and adb sideload?
- What does "sideloading an app" mean?
- Is an Android ".apk" file the same thing as a .zip file, or different?
- In what folder in /data are market apps (.apk files) found? Same question for /system and system apps (.apk files)?
- How do I enable the developer options on my N7 tablet?
- What are the limitations of MTP or PTP file transfer modes?
- Where does the custom recovery tool store backups?
- Are the Android tools "adb" and "fastboot" available for Mac or Linux?
- What are the limitations of the Google Factory Images for the Nexus 7? How are they installed?
- I have a problem using the recovery. Where is the log file stored?
- What is the big stumbling block involved in unlocking the N7 bootloader?
- What operations can you perform using fastboot and the bootloader which you can not do any other way?
OK, that's enough for now.
Thanks Everyone!
bftb0 said:
Read through the stickied threads and try to understand them. It won't happen right away though; your head will probably spin the first couple of times through.
There is really no "overnight" learning curve to this stuff - even if you are an old hand with Linux/Unix.
BTW, it is important to point something out: There should be no reason for you to feel like you should be in a hurry to root. The N7 is a fantastic device, even when used in a pure stock experience.. You are not going to be missing out by not rooting immediately. Spend some time with your device getting used to the Android way of doing things, and start reading XDA with a relaxed frame of mind. There is plenty of time. It would be different if you have lots of prior Android experience - but you said it - this is your first Android device..
Click to expand...
Click to collapse
I do appreciate everyones input! yeah i think ill make do with the stock for a couple weeks while i study up on rooting and firmwares. well the main reason i wanted to root was for the games, as much as i want to buy the games i like, i dont have the means to
This is great. Wish I had been fortunate enough to have such great help when I first started.
And the most important rule is the one about reading before you root or flash. This will save you some heartache down the road.
Sent from my Nexus 7 using XDA Premium HD app
How's rooting related to games ? You mean overclocking ?
Sent from my Nexus 7 using xda premium
BigJoey010 said:
How's rooting related to games ? You mean overclocking ?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
sad to say i will have to torrent my games as much as i wanna pay and support the game devs i already blew all my money on steam and buying the N7. ive read somewhere that if u are using the the stock version and you try to run a torrented game it automatically shuts down
No it doesn't ...i be downloaded tons of games(torrents) and I'm on stock and they are working normally
Sent from my Nexus 7 using xda premium
UrbabBear said:
sad to say i will have to torrent my games as much as i wanna pay and support the game devs i already blew all my money on steam and buying the N7. ive read somewhere that if u are using the the stock version and you try to run a torrented game it automatically shuts down
Click to expand...
Click to collapse
All the help you were given....then you bring this up.
I doubt further help will come your way as pirating software is very much frowned upon at xda.
Sent from my cell phone telephone....
kj2112 said:
All the help you were given....then you bring this up.
I doubt further help will come your way as pirating software is very much frowned upon at xda.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
i never really liked pirating software...believe me im a huge fan of steam and i practically buy alll my games legit for the pc.. since steam wallet codes are available at a local store here.. okay i promise i wont pirate and ill try to look for the means to buy from the google store , the thing is i dont have a credit card... and i dont know if google has have something equivalent to steam wallet cards for the google play store.. i could borrow a cc and pay for it.. but is the google play store a safe place to purchase ? i nkow some people disputing alot of charges from google play to everyone, i meant no disprespect.. i was thinking along the lines of test the game if there is no lite version, then when i can i will buy the game :< im still new to the whole tablet arena and im gonna need all the help that i can get
UrbabBear said:
i never really liked pirating software...believe me im a huge fan of steam and i practically buy alll my games legit for the pc.. since steam wallet codes are available at a local store here.. okay i promise i wont pirate and ill try to look for the means to buy from the google store , the thing is i dont have a credit card... and i dont know if google has have something equivalent to steam wallet cards for the google play store.. i could borrow a cc and pay for it.. but is the google play store a safe place to purchase ? i nkow some people disputing alot of charges from google play to everyone, i meant no disprespect.. i was thinking along the lines of test the game if there is no lite version, then when i can i will buy the game :< im still new to the whole tablet arena and im gonna need all the help that i can get
Click to expand...
Click to collapse
a good way to get started is to get yourself a prepaid credit card from 7eleven and use that for purchases from the play store.
Billchen0014 said:
a good way to get started is to get yourself a prepaid credit card from 7eleven and use that for purchases from the play store.
Click to expand...
Click to collapse
as much as that service would be convenient its not available in my country thanks! i hope somebody brings it here ... i found a workaround already now just a matter of saving up for the good apps! so in the mean time lite versions here i come!
UrbabBear said:
as much as that service would be convenient its not available in my country thanks! i hope somebody brings it here ... i found a workaround already now just a matter of saving up for the good apps! so in the mean time lite versions here i come!
Click to expand...
Click to collapse
http://play.google.com/about/giftcards/ use this to see if any retailers near you sell.
Sent from my Nexus 7 using xda premium
Hey guys, what do you think are the most basic and necessary apps that i should get ? running on stock
, ive checked some and go a file manager
If you think you are going to root down the road...
If you think there is a good chance that you are going to root down the road, I would suggest unlocking the bootloader in the near future. You'll need to do this and it wipes everything on the tablet. Even if you don't root, there's isn't any major downside to having the bootloader unlocked and you can always relock it later.
It's better to do that before you've put a lot of time into customizing your tablet to perfection and then have to redo it all.
In short, i deleted my photos by accident, and deeply desire to recover them.
Data Recovery programs wont work on my Google Nexus 4, for a combination of reasons. Namely, because it is not a usb mass storage device, it is internal memory, and because the phone has not ever been rooted. If it is possible to recover the photos without rooting the phone, this would be favorable. But i doubt this is possible.
Is there a way to root my phone without causing a "factory wipe/reset"? Perhaps by avoiding unlocking the bootloader?I am not even 100% sure if this can be achieved on 4.4.2. as of now. I am continuing to investigate, but if anyone has the know-how, please let me know.
this forum here, suggests something that might work, but at the end of the forum, it suggests that 4.4.2 is still impossible to root without wiping.
-There are methods of scanning the phone after it has been rooted, but i can't find the right kind of rooting i need.
-There are methods of copying the phone's hard drive -bit-by-bit- to my PC in .RAW format, and then converting this into something that can be mounted like a real drive, which could be scanned and from which photos could be recovered., but this method requires a rooted phone as well
-there is a possibility of trying to mount the phone on a linux OS, and then scan it possibly. but i don't know if this is impossible.
i am reading the basics in the meantime.
LG Google Nexus 4, 4.4.2
Build:KOT49H
kernel:
3.4.0-perf-g2cae413
[email protected] #1
wed Nov20 14:54:28 PST 2013
Desktop PC: Windows 7 Professional 64bit, service pack 1.
Laptop: mac...
you can read more about things i have tried and my other concerns, in greater detail below.
LOTS OF METHODS, LITTLE CLARITY
I just came back from visiting some dear friends in china and purchased an upgraded version of dropbox. Before I uploaded my photos, I accidentally deleted my entire album.
What is the safest and surest attempt for recovery?
1. i need to avoid installing anything on my phone as much as possible - (lest it overwrite the empty areas where the "deleted" photos reside.)
2. i need to keep my phone off as much as humanly possible (lest it overwrite the empty areas where the "deleted" photos reside.)
3. almost without saying - id like to avoid bricking my phone, (lest it destroy my "deleted" photos)
SOFTWARE RECOVERY SECTION
All known software recovery programs won't find any data on my phone because either they are made for scanning mountable drives, USB mass storage devices, or some simply cannot scan the device unless i root my phone (although I am not sure if rooting is directly correlated with successful scanning, or if rooting the phone simply allows me to carry on with other necessary steps prior to "successful scanning"- like allowing me to installing apps that allow me to mount the internal memory as a scannable drive). Enabling USB Debugging, or enabling/disabling MTP is not the same as enabling USB mass storage mode. Seeing the Nexus 4 as "portable Device" under my computer does not mean it is a mounted drive that i can scan with a recover program. No matter what, nothing seems to work with the Google Nexus 4 as it is now.
***I first tried installing the driver's through the ANDROID SDK, by unzipping the contents from the downloaded zip file and by double clicking the .exe file. Double-clicking the .exe file resulted in a cmd dos-style window popping up and immediately disappearing. Perhaps i needed to put the extracted folder on "C:\"?
REGARDLES....later, I have used WugFresh Nexus Root Toolkit v1.8.2 for ensuring proper driver installation for my phone. I have only used this software to install drivers. It walks you through bad-driver uninstallation/clean up, it retrieves the latest drivers, installs them, and then tests their workability for you and lets you know if the drivers were successfully installed.
I have not used Wug's toolkit to root or hack my phone... yet....
Below is a list of software I have used on my Windows machine and my mac. These simply will not work with the phone as it is right now.
Remo
TenorShare
Bycloud android data recovery
Android Data Recovery
Dr. Fone
Recuva
- i havent tried disk digger. but it requires a rooted phone.
SO simple methods will simply not work? Please correct me if I am wrong.
BIT BY BIT CLONE METHOD
This seems to be the most tedious (but thorough) method for actually preparing something that can be truly scanned for photo-recovery. This method seems to create a bit-by-bit copy of the phone to my computer, which can be converted and mounted and then scanned.
However, it requires rooting. Not to mention, it recommends non-destructive rooting. Which leads me to the next section ...
ROOTING section (and its problems)
In the fruitless sections listed above, it always seems to lead towards rooting as a requirement. Most people say you should root your phone when you first get it, because, i suppose rooting is "synonymous" with a wipe/reset. I believe this reset happens as a result of the bootloader being unlocked. According to MY limited understanding, this unlocking process essentially causes a "factory reset" which wipes the phone, and then catastrophically overwrites the precious space where the deleted photos currently reside. this is unacceptable. I imagine, this "reset" is for security reasons.
Most people seem to suggest that you make a back up before you root. This isn't helpful for my situation because we are talking about retrieving deleted data. I cannot make a back-up of deleted data.
Is it really possible to root without wiping the Google Nexus 4?
Is it even profitable to consider rooting a viable option? I don't imagine myself enjoying a rooted phone as much as others on this forum. I would hate to be creating a black hole for malicious software to breed. i am only concerned with data retrieval for this one time in my life. Is rooting the only viable option? If i root, won't that make the previously mentioned software-scanning section (e.g., Dr. fone), more viable than the BIT-BY-BIT section tedious and pointless by comparison?
All in all, I think it most likely that i will need to root my phone and do the bit by bit copy. If a rooting-first-step is the final conclusion, then I am looking for clear and careful advice for my specific phone on how to root it without jeopardizing the deleted photos (e.g., avoiding a "factory reset" from unlocking the bootloader, or perhaps avoiding unlocking the bootloader altogether) and how to hopefully carry on from there. I don't even know if avoiding "unlocking the bootloader" will virtually guarantee a non-destructive root method
Rooting gets crazy because it leads to necessary installations of SuperUser, busybox, kernels, roms, etc... There are so many unfamiliar vague terms for a beginner like me and it is taking tons of time to break through. I am uninterested in keeping my phone rooted, or maintaining a lifestyle with a rooted phone. if we can move expeditiously from point A to B and then back, (get in, get the photos, and get out,) that would be the most awesome plan.
LINUX METHOD?
is there another way to get to the deleted photos?.
I do not know if 'mounting' the phone is akin to 'mounting' a scannable drive. http://www.youtube.com/watch?v=fw2MKGIgyF4
maybe this is another wild goose chase?
IN SUMMARY
1. It would be helpful if there was a root-free photo-recovery software solution that actually works (this is unlikely to be in existence) with an unrooted nexus 4
2. It would be helpful if it is possible to root without destroying my chances of recovering my deleted photos, with the goal of allowing recovery software access (deeper access) to my phone, i.e. disk digger or if necessary... a bit-by-bit copy to my PC.
3. it would be interesting if the nexus 4 can be magically mounted and scanned on the linux operating system
4. It would be MOST HELPFUL if there was a clear consensus on what direction to take, because there is a lot of misinformation out there. One wrong step and i could end up shooting myself in the foot twice (if i inadvertently reset my phone), or three times (if i brick my phone).
5. can the phone be put back to normal (i.e. unroot) after rooting? or does this require that i make a full backup of the phone in its current state? ( i tried using WUGS toolkit to backup my media, but it wont do it unless i unlock the bootloader... back to that problem again )
I'm sorry for sounding like an idiot. I have been at this for a more than a few hours. I sincerely appreciate any help and consideration towards this specific situation in advance, and the hope that this forum has already offered me.
Impossible to root 4.4.2 without unlocking the boot loader and wiping the device.
DrFredPhD said:
Impossible to root 4.4.2 without unlocking the boot loader and wiping the device.
Click to expand...
Click to collapse
Same problem.... There isn't a solution yet? :crying:
fabrollo said:
Same problem.... There isn't a solution yet? :crying:
Click to expand...
Click to collapse
Nope, you have to unlock the bootloader and that wipes the device
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
Nope, you have to unlock the bootloader and that wipes the device
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
And after i should try to recover all the wiped files with diskdigger for example? Maybe the datas that we was searching will be found?
Thanks... if i must try this way to solve my problem i will bite the bullet...
fabrollo said:
And after i should try to recover all the wiped files with diskdigger for example? Maybe the datas that we was searching will be found?
Thanks... if i must try this way to solve my problem i will bite the bullet...
Click to expand...
Click to collapse
The chances of recovering anything is very small
Sent from my Nexus 5 using XDA Free mobile app
Want to try Nougat on your Nook HD+ or HD?
Installing Nougat has never been easier. Procedure described in post 239 of this thread.
Development for unofficial CM-12.1 for Nook HD and Nook HD+ has ceased.
The author @amaces has moved on to Marshmallow (Android 6), and the zip files for these progressive releases are what you now see at the collaboration link. If you wish to install CM-12.1 look instead through the pages of his "obsolete" folder for "cm-12.1-20151018" and "twrp-2.8.7.4" final releases. CWM should install these properly but later versions are likely to fail due to deficiencies in the CWM recovery utility.
Better yet try the latest Marshmallow and TWRP versions. For this you must create a new bootable microSD card using these files provided by @belfastraven and the downloaded zip files "cm_hummingbird-ota-MHC19Q.160407.zip" and "twrp-3.0.1-0-hummingbird.zip". These versions may advance by the time you happen to do this. The procedure is the same as described in the .pdf guide for CM-12.1, except with the new files.
And use a current GApps file for the ARM platform, Android 6.0 from http://opengapps.org/.
This is a detailed tutorial for beginners. Seasoned users may find it overly verbose.
My toy box contains some Nook HD and Nook HD+ tablets, and I recently became aware of CyanogenMod. I studied about it for a while and finally tried a CM-12.1 installation. It was successful, and I was so impressed by the improvements that I told some Nook-owning friends about it. They quickly decided to do likewise and asked for instructions.
My friends and I are all retirees, so we have seven Saturdays a week to spend as we wish. I decided to spend a few of mine re-writing my notes into an instruction manual. As of today, September 25, 2015, there are eleven formerly stock Nook tablets whose beginner-owners have followed the instruction and successfully installed CM-12.1. Several of these are being regularly updated as revisions are released. No bricks have been cast so far.
During the study period I spent a lot of time on xda developers pages, and it eventually occurred to me that there might be other beginners who could make good use of Nook-specific instructions. So I am pleased to offer this manual to anyone interested, and hope it will save you some time and trouble.
The procedure uses the technique and boot files by @leapinlar. The ROM and TWRP zip files used are those created by @amaces. Profound thanks to these experts for their diligent work and generosity.
Below is a synopsis of the instructions. The complete PDF document is attached to this post.
This document will guide you through the steps of installing a pure modern version of the Android operating system on your Nook HD or Nook HD+ tablet. The installation is done from a bootable microSD card using the ClockWorkMod recovery utility to install the contents of zip files. This straightforward method does not require ADB or rooting the Nook. The result is CM-12.1 installed with basic Google apps and your choice of TWRP or CWM for your resident recovery utility.
There's room for improvement.
If I could learn how to create a bootable microSD that would boot to TWRP instead of CWM the procedure could be reduced to four easy steps. I have found no help for this, and my own attempts have all failed. I would be most grateful for any help so I can update the instructions.
This is brilliant!
Where was this three days ago ? I really could have used this when I finally got around to fixing my dead Nook HD+ with spare parts from an ebayed broken on, and decided to finally go for broke on EMMC (after SD Boot killed the device twice on me while charging overnight.) Not a fun initial teardown to pull out that mainboard, but manageable with a good deal of care.
My own fumbling around led me to using verygreen's external recovery image here (Note, they are the Initial sdcard Images located at the very top) as recommended by amaces writing it to the SDcard using Win32DiskImager for a bootable sdcard (On Windows 10 here). Then using that, I went and installed amaces' TWRP and CM12.1 onto the Nook HD+ followed by finding a set of gapps to install as well.
I missed the backup/wipe parts of your guide, sadly. Though I do have a stock copy laying about, and my device has been out of warranty for a while by now. I just didn't think of doing the wipe (though looking back, the broken one I took the mainboard from and its EMMC already had that done). Further, I was lost seeing that "Root" fix note and ended up hitting yes. Fortunately, it doesn't appear to have done anything for my tablet.
In the end? I got my Nook HD+ up and running using amaces' CM12.1 ... even if in a manner that may make those more experience wince at my errors. Still, its nice to have my large tablet for reading and watching videos once more rather then needing to spend a couple hundred dollars on a decent large tablet. Gaming isn't up to par (older games still does decently), but its an old device and not exactly what I wanted it for anyways.
I just wish I held off a couple more days so I had this guide to help me through this. Still, for anyone that comes after I hope your efforts help them.
Thank you for taking your time and writing such a useful guide. I am currently on cm11 m12. Are there any noticeable difference between 12.1 and cm11? Is the update from cm11 to 12.1 the same as from stock to 12.1?
Holy crap that is awesome. Looks like I picked the perfect day to upgrade the kids YouTube machine from 4.4
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Thank you for taking the time to put together this extremely easy to follow guide! It helped me breath new life into my Nook!
Thanks so much for writing up a document us older folks can handle. (and say hello to Sequim for me!)
:good:
Cheers.
This looks like exactly what I need. I've finally reached the point of frustration with my Nook HD+ that I'm ready to go through with a reflash. Thanks so much for providing this great resource.
But, one question. You advise not modifying the user interface after flashing CM 12.1 to the device. This is because the ROM is still under development, and making chages of that sort will make upgrading to newer images more difficult. In principle, I understand this. But is this a permanent condition?
In other words, I suppose development on CM 12.1 will go on until interest in it is lost and the project goes moribund. No one can predict when that will happen, but if things go as they have for the past couple of decades, this project is likely to be abandoned sooner rather than later. So is there some projected point when the project reaches stability and when users can make interface changes without worry of having problems upgrading? Or is the inadvisability of making such personalization modifications a permanent condition?
i got it installed simple enough but cant seem to login to my google account, it just tells me something went wrong and wont sign in, any ideas what i can do?
I used this manual to put CM 12.1 on my Nook HD+ and it worked great. What a wonderful resource you've provided.
A couple of minor issues I encountered are as follows. The directions in step 5e call for rebooting the system, but the menu I encountered did not correspond precisely to the description, What is described in step 5e is a two-step process, first slecting "reboot," then "power off." However, when I tapped the "reboot" button, there was no subsequent option to power off; the device simply rebooted. That didn't prove to be much of an issue since, realizing the Nook would be trying to boot from the SD card, I simply quickly removed it in a very early stage of the boot process.
Another minor issue is that the file system is kind of strange, with the backed up data being located under /storage/emulated, with a couple of symlinks in other locations to that same directory. It's kind of puzzling to find my way around the system. That said, so far everything works and all my previous data seems to have been preserved.
As far as improvements to the guide, you might want to add the additional directive that developer options can be gained by going to Settings > About table and tapping on "build number" seven times. I wanted to change the hostname on the new installation, and I needed developer options to do that. I don't know how many retirees are going to want to do things like that but, age wise, I'm not too far away from that category, and I needed that. So, maybe something you could add at the end of your nice manual.
As to booting directly into TWRP, I found an img file at twrp.me under /devices/barnesnoblenookhdplus.html. It looks like directives there are for writing it to the internal recovery partition, but I don't see why it could not be written to an sd card by slightly adapting those same directives. I'm new enough to this to not quite understand whether the recovery image would answer to your issue, but it's something you might want to consider.
All in all, you've provided a nice resource with this guide. It worked well for me on a first try, so it's something I'd definitely recommend to others.
Question about step 3b from the manual (Backup the existing system and data to the microSD card). Let's say this is a brand new Nook HD+ that contains no data or configuration that the user wishes to preserve: can that step just be skipped in such a case?
I'm asking because my current Nook HD+ has a pretty badly cracked screen and I'm thinking of replacing the unit with another Nook HD+. Doing this upgrade to CycanogenMod has got me thinking more seriously about getting a unit with an intact screen. If I end up replacing the unit, there will be no data or configuration on the replacement unit that I'll be wanting to preserve.
wayover13 said:
Question about step 3b from the manual (Backup the existing system and data to the microSD card). Let's say this is a brand new Nook HD+ that contains no data or configuration that the user wishes to preserve: can that step just be skipped in such a case?
Click to expand...
Click to collapse
It wouldn't hurt to have a backup of Stock, imo. Further, its useful habit to get into as you upgrade to any new image that is released and not loose everything. If only to allow you to reset to the default state and try again.
wayover13 said:
But, one question. You advise not modifying the user interface after flashing CM 12.1 to the device. This is because the ROM is still under development, and making chages of that sort will make upgrading to newer images more difficult. In principle, I understand this. But is this a permanent condition?
Click to expand...
Click to collapse
I'm a bit lazy when it comes to installing incremental releases, so I prefer to do simple "dirty installs". This means re-flashing without wiping the old installation, which can be done in seconds with no consequences.
But a dirty install will probably fail if you have made user-interface changes, even if you try to reverse out those changes before flashing. You can still install revisions anytime you wish, but you must do the wipes first. This means you will have to go through the setup procedure all over again, which takes a lot longer than a dirty install.
CM-12.1 for our Nooks should eventually be offered among the official nightly releases, and hopefully a milestone release now and then. I might consider UI tweaks after installing one of these, then settle down for a long quite period of no more updates.
If a stable CM-12.1 ever happens, we'll all be installing CM-13 by then.
wayover13 said:
The directions in step 5e call for rebooting the system, but the menu I encountered did not correspond precisely to the description, What is described in step 5e is a two-step process, first slecting "reboot," then "power off." However, when I tapped the "reboot" button, there was no subsequent option to power off; the device simply rebooted.
Another minor issue is that the file system is kind of strange, with the backed up data being located under /storage/emulated, with a couple of symlinks in other locations to that same directory. It's kind of puzzling to find my way around the system. That said, so far everything works and all my previous data seems to have been preserved.
As far as improvements to the guide, you might want to add the additional directive that developer options can be gained by going to Settings > About table and tapping on "build number" seven times. I wanted to change the hostname on the new installation, and I needed developer options to do that.
As to booting directly into TWRP, I found an img file at twrp.me under /devices/barnesnoblenookhdplus.html. It looks like directives there are for writing it to the internal recovery partition, but I don't see why it could not be written to an sd card by slightly adapting those same directives. I'm new enough to this to not quite understand whether the recovery image would answer to your issue, but it's something you might want to consider.
All in all, you've provided a nice resource with this guide. It worked well for me on a first try, so it's something I'd definitely recommend to others.
Click to expand...
Click to collapse
I too was puzzled a few times. There are two "Reboot" buttons: One in the TWRP entry menu and the other is deeper in where the flash process ends. The one in the entry menu will present a Reboot menu with includes a Power Off button. Use the tablets move-back triangle below the screen to navigate back to the entry menu.
I think you refer to the stock backup made by CWM before flashing CM-12.1. My stock Nooks were under-used with no data worth recovering, so I never looked into this. If you'd care to share any details about your findings it might be helpful so some subsequent readers.
This one is covered on Page 15 (actually sheet 17 including cover page and Table of Contents) under the heading Reboot to Recovery.
Once TWRP is installed its pretty easy to use it to install a newer version of it. But getting the boot files prepared on a microSD to boot to this image turned out to be more complicated than my very limited experience could manage (I'm a retired orchardist). The CM-12.1 installation procedure would be greatly improved if I can make this work, but I really need some professional help to make this happen. I keep hoping for a knowledgeable person to come forward.
Thank you very much. There are so many helpful members on this forum, and it is gratifying that I've been able to make a tiny contribution.
zspeciman said:
Thank you for taking your time and writing such a useful guide. I am currently on cm11 m12. Are there any noticeable difference between 12.1 and cm11? Is the update from cm11 to 12.1 the same as from stock to 12.1?
Click to expand...
Click to collapse
I tried CM-11 briefly on one of my Nooks before I became aware of CM-12.1, so I can tell you there is a huge difference. The move is from Android 4.4 to Android 5.1. And in my opinion all of this huge difference is for the better.
If you use the instructions, you can follow them exactly to move from CM-11 to CM-12.1. You are going to wipe the existing installation entirely, so it matters not what it is.
siccoblue said:
i got it installed simple enough but cant seem to login to my google account, it just tells me something went wrong and wont sign in, any ideas what i can do?
Click to expand...
Click to collapse
I've been pondering this, but nothing has yet come to mind. I'm presuming you did the full wipe before starting the install.
Which GApps did you install? If, for example, you chose one of the more sophisticated packages (tk_gapps or open_gapps) you would have had to defer installing it until Step 5. If so, and if you were distracted for a while and forgot to install it, I suspect the setup process would not offer an opportunity to log in to your Google account. This is probably not your issue since you were able to attempt a login.
Were you replacing the stock Android? Any other clues you can offer?
I managed to fix it, I had to completely wipe everything as opposed to just a normal reformat and it fixed the issue, but I actually have another problem now, I'm trying to do this on my second nook and when I attempt to flash twrp, cwm recovery now throws me an error on both my tablets, along the lines of "cannot install recovery this was designed for ovation and you are on ." it says that the device is . and won't let me flash it, any ideas?
PeteInSequim said:
I'm a bit lazy when it comes to installing incremental releases, so I prefer to do simple "dirty installs". This means re-flashing without wiping the old installation, which can be done in seconds with no consequences.
Click to expand...
Click to collapse
I understand vaguely what you're talking about here, but I'm pretty new to flashing Android devices and find myself wanting to know more. Is there some link you can point me to that explains in greater detail about dirty versus other types of installations? What I'm most interested in learning is how much configuration is too much to permit a dirty install. For example, the tablet is of little use to me if I can't install certain apps on it; will installing apps, for example, obviate the possibility of the sort of dirty install you're speking of?
PeteInSequim said:
But a dirty install will probably fail if you have made user-interface changes, even if you try to reverse out those changes before flashing. You can still install revisions anytime you wish, but you must do the wipes first. This means you will have to go through the setup procedure all over again, which takes a lot longer than a dirty install.
Click to expand...
Click to collapse
For example, I want a battery percentage monitor in the taskbar. If I enable that, is that the sort of user interface change after which I will be unable to do a dirty install? How about deleting what I would call desktop icons and/or adding others from newly-installed apps? Is that the sort of user interface change that will cause me to be unable to do a dirty install? If so, it seems like I would need to become a sort of beta tester in order to retain the possibility of doing further dirty installs, rather than using my Nook for my everyday needs.
PeteInSequim said:
CM-12.1 for our Nooks should eventually be offered among the official nightly releases, and hopefully a milestone release now and then. I might consider UI tweaks after installing one of these, then settle down for a long quite period of no more updates.
If a stable CM-12.1 ever happens, we'll all be installing CM-13 by then.
Click to expand...
Click to collapse
I'm obviously not too well versed in CynaogenMod/Android development. I wasn't aware that CM-12.1 was at such an early stage of development. Let me see if I'm, understanding correctly: is the CM-12.x series tracking Lollipop, while the projected CM-13 will track Marshmallow (Marshmallow being, as I understand it, the next Android release)?
I've obvioulsy got a lot to learn on this front.
---------- Post added at 11:24 PM ---------- Previous post was at 10:55 PM ----------
PeteInSequim said:
I too was puzzled a few times. There are two "Reboot" buttons: One in the TWRP entry menu and the other is deeper in where the flash process ends. The one in the entry menu will present a Reboot menu with includes a Power Off button. Use the tablets move-back triangle below the screen to navigate back to the entry menu.
Click to expand...
Click to collapse
Yes, on a second attempt I realized I needed to hit the move-back trinagle to get to the reboot button to which the manual was referring. Thanks for the clarification.
PeteInSequim said:
This one is covered on Page 15 (actually sheet 17 including cover page and Table of Contents) under the heading Reboot to Recovery.
Click to expand...
Click to collapse
You're right. I should have kept reading
On my second try, I realized I'd noted another discrepancy in the manual, one that occurs between steps 5a and 5b. After step 5a (successfully booting to TWRP by holding the power and home buttons down for the correct interval) I actually get an "Unmodified System Partition" screen. There, I have the option of either keeping the system partition read-only, or swiping another option to allow modifications. It is only after either tapping the read-only item or swiping the allow modifications item that I get a subsequent screen where I can tap the Install button (step 5b).
PeteInSequim said:
Once TWRP is installed its pretty easy to use it to install a newer version of it. But getting the boot files prepared on a microSD to boot to this image turned out to be more complicated than my very limited experience could manage (I'm a retired orchardist). The CM-12.1 installation procedure would be greatly improved if I can make this work, but I really need some professional help to make this happen. I keep hoping for a knowledgeable person to come forward.
Click to expand...
Click to collapse
I have a fair amount of experience writing image files to disks/partitions. Does it seem like that's what's needed? I also know how to mount an image file as a looped file system in order to, for example, copy files from it. That's something like what was done with the unrar'ing of CWM and copying files over to the SD card. If any of that experience sounds helpful, I could probably conduct some experiments to see if I could succeed at this. I'm just not sure what the TWRP image file I found is: is it a bootable image? If so, I'm not sure copying files from it to a bootable partition, like you instructed to do for CWM, would work. Writing a bootable image to an SD card should, on the other hand, cause that SD card to become a bootable medium.
In any case, as I said, I could conduct some experiments if it seems like any of my suggestions would be helpful. I'm not really any kind of professional either, btw. I got into computing when I undertook, at a later stage of life, some graduate studies in the humanities, during which I developed the crazy notion that I could somehow gain the upper hand over the machines. That attempt ended in failure, but I have kept up my doomed insurgence and learned some things along the way.
siccoblue said:
I managed to fix it, I had to completely wipe everything as opposed to just a normal reformat and it fixed the issue, but I actually have another problem now, I'm trying to do this on my second nook and when I attempt to flash twrp, cwm recovery now throws me an error on both my tablets, along the lines of "cannot install recovery this was designed for ovation and you are on ." it says that the device is . and won't let me flash it, any ideas?
Click to expand...
Click to collapse
Well, sounds like the zip file you're attempting to flash is mismatched to your model Nook. "designed for ovation" means the zip file is intended for the 9-inch Nook HD+. Are you trying to install on hummingbird, which is the 7-inch Nook HD?
I understand vaguely what you're talking about here, but I'm pretty new to flashing Android devices and find myself wanting to know more. Is there some link you can point me to that explains in greater detail about dirty versus other types of installations? What I'm most interested in learning is how much configuration is too much to permit a dirty install. For example, the tablet is of little use to me if I can't install certain apps on it; will installing apps, for example, obviate the possibility of the sort of dirty install you're speking of?
Click to expand...
Click to collapse
The best explanation I can offer is on page 17 of the instructions. Basically if flashing an incremental CM-12.1 revision a dirty install is fine (no need to wipe the system partition) UNLESS you have altered the user interface with things like theme, colors, wallpaper, boot animation, sounds, etc. If you have, you must wipe both the Data and System partitions.
Or if you are installing an OS version for which the existing one is not a close relative. The most outrageous example of this would be re-installing the old stock Barnes & Noble Android in place of your CM-12.1. Review the information on pages 16 and 17, and I think you'll get a good handle on this.
I've been called to dinner; will address your other questions after that.