Related
No, I do not have a nook tablet so I can not offer any methods to bypass myself. This is just a thread where developers can talk about gaining the ability to flash roms and recoveries.
Developers, please use this thread to collaborate so we can have everyone working in the same space.
Users, please try to not post and if you do, don't make it a completely useless post like something that just says thanks and whatnot. Just use the button for that. The less clutter = more progress
edit: Someone is donating a nook tablet to me to try and bypass the bootloader! Here's hoping it doesn't get bricked.
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
chantman said:
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
Click to expand...
Click to collapse
Kernel is good enough to run CM7 (Gingerbread), but not sufficient for CM9 (ICS). Also it is not good enough for CM8 either (although the chance we see CM8 for any device is doubtful).
We need to find a way to keep a chat between developers. Add me on g+ and ill create a huddle for every dev
Sent by breaking the sound barrier
chantman said:
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
Click to expand...
Click to collapse
your pretty spot on, but i dont see cm7 being a problem, i see cm9 being a problem. with a 2nd init rom you have to build the OS around the kernel(which it is much harder than doing it the right way) and if the kernel isnt high enough or if drivers are outdated(like the nook color graphic drivers) than you can count that OS out of your list. cm7 since it is gingerbread and since gingerbread can be booted on a froyo kernel(moto droid proved that along with the droid x/2), i think it can be booted using 2nd init, ICS on the other hand needs a ICS kernel to boot and if your not using an ICS kernel than you need a custom kernel that can get ics booting properly
now i disagree with you about 2nd init being the best way to build a rom for the nook tablet, i believe kexec is the best way to go about building a rom for the nook tablet because it will allow for a custom kernel to be booted off the original kernel. from what i have read about kexec on android is that they cant get the 3g chip to get started again(but nook tablet doesnt have a 3g chip so who cares), but wifi and all the other key functions can get started up and running, so using kexec on a nook tablet seems the best logical solution to getting around the locked bootloader(but dont quote me on this cause i havent developed anything for the nook tablet yet, nor do i even own one).
---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------
Indirect said:
We need to find a way to keep a chat between developers. Add me on g+ and ill create a huddle for every dev
Sent by breaking the sound barrier
Click to expand...
Click to collapse
devs use irc to chat, its easier than any forum or chat program out there
Thats true but i cant always be on irc to keep up on info.
Sent by breaking the sound barrier
Also, ill look into getting kexec once i get my nook tab
Sent by breaking the sound barrier
Indirect said:
Thats true but i cant always be on irc to keep up on info.
Sent by breaking the sound barrier
Click to expand...
Click to collapse
There are most likely complete logs available somewhere to review, or someone could make them available for you. I don't have the link on this pc, but there is a site that keeps up-to-date logs #nookcolor available
Indirect said:
Also, ill look into getting kexec once i get my nook tab
Sent by breaking the sound barrier
Click to expand...
Click to collapse
I wouldn't spend too much time on this. Assuming that android_4430BN_defconfig from B&N's kernel sources is the defconfig used to compile the running kernel, kexec will not work as it has been disabled.
it doesn't really matter if kexec has been disabled in the kernel config. we can't really hope that they would leave a gaping hole that fricking big. honestly i'm kind of annoyed at the "omg they didn't configure their kernel specifically for us to hack the crap out of the device" posts. Seriously, even if they did this, as far as i've seen we have yet to disable OTA updates, so 3 seconds of a B&N developer time would wipe out any work depending on kexec being built into the kernel.
we can after all create modules neh? my linux kernel hacking experience is very close to non-existent, but i'll be starting by getting a module to load, followed by getting the kexec tools and a kexec module loading.
so far i'm having trouble finding any literature on kexec on ARM. it all says it's x86 only, but clearly everyone from motorola to sony communities are making use of kexec on arm. anyone know of any good points to find information on kexec for arm?
I've also seen something call splboot mentioned a few times, but am having trouble googling anything useful up. anyone familiar with that tech?
I suggest posting in the motorola dev section seeing if any of them would be interested in getting kexec up and running on the nook tab or could point us where to get information on it running with an ARM architecture device.
Indirect said:
I suggest posting in the motorola dev section seeing if any of them would be interested in getting kexec up and running on the nook tab or could point us where to get information on it running with an ARM architecture device.
Click to expand...
Click to collapse
Try Kabaldan. http://forum.xda-developers.com/member.php?u=2218140
He was a great developer when I owned a Motorola Milestone. Assuming he used 2ndInit to port CM6 and CM7
http://lists.infradead.org/pipermail/kexec/2008-February/001272.html<-- kexec on an ARM processor.
I just tried something to see where it would get me and if I could learn something new.
Using ROM Manager, I have been trying to flash different recoveries to see what results I would get or what I could break (or brick). After some research I found a device also running the OMAP 4430 processor and selected it (LG Optimus 3D). When I selected reboot into recovery, I did get some new screens I have not seen before. It made me reboot again, then another screen flashed very fast and it then rebooted and was normal from there. I think it may have replaced the recovery I flashed as it was flashing something but was very fast. I will try it again and see if I can determine what is happening. But I got it's attention and probably flashed the right thing in the wrong place, or the wrong thing in the right place.
I found a guide on a site for flashing a recovery to a device using flash_image binary, and two files were mentioned and deleted which allowed hijacking of the recovery process. Out NT has those two files as well:
/system/recovery-from-boot.p (encrypted, cannot view)
/system/etc/install-recovery.sh (can view code, and points to first file)
I wonder what the possibility is to hijack the install-recovery.sh file ? Or is there yet another file in the process? Very interesting though.
Ive actually been thinking of hijacking the install recovery script
Sent by breaking the sound barrier
To ellaborate further on my previous post, I believe this is the key to how we can get a bootloader bypass for a custom recovery as they have done for the Motorola Bionic and other Motorola phones. When a reboot occurs, the bootloader looks for a certain file in a certain place, if it exists then it reboots into recovery. If not, it boots like normal. The bootstraps for the Motorola devices mimic the logwrapper binary that the bootloader looks to and allows it to go into a custom recovery instead. A very simplified explanation.
What their bootstrap does is place the recovery indicator file in the proper place (somewhere in /data) and when the bootloader finds it, it goes to the logwrapper binary, which of course has been replaced with their hijacked version.
It appears the install-recovery.sh on our NT is looking for a "recovery" indicator, and if it exists, it is telling it to go to recovery-from-boot.p
If so, this is the very process we need to hijack to allow some type of custom recovery. It doesn't get us completely around the bootloader, but it would allow a recovery mode for flashing custom ROMs, just as the Motorola guys have done. I am probably way over simplifying this, but i have researched this quite a bit the past few days and it looks like for the short term, this is the path we need to look at.
If anyone has contact with Kousch or someone familiar with the bootstrap process, I think we could be in business to get something workable here.
Here is a link to one of the Motorola bootstraps, and the contents of the /system/etc/install-recovery.sh
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
#!/system/bin/sh
if ! applypatch -c IMG:/dev/block/platform/mmci-omap-hs.1/by-name/recovery:2048:70ef89e0497435e988819690aaabb35da6b7677f; then
log -t recovery "Installing new recovery image"
applypatch IMG:/dev/block/platform/mmci-omap-hs.1/by-name/boot:2850816:114706e7bbfa4c806323215a83d6ad4e9cd392f7 IMG:/dev/block/platform/mmci-omap-hs.1/by-name/recovery 532ad547febe82850924a52625132376514e3a8b 3203072 114706e7bbfa4c806323215a83d6ad4e9cd392f7:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Or all of this could be in place and not ever used !
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
Indirect said:
Ive actually been thinking of hijacking the install recovery script
Sent by breaking the sound barrier
Click to expand...
Click to collapse
The Motorola bootstraps are just one .apk file ! We could probably modify the process to fit ours. But these are paid for apps on the market so we would need permission, or even better help from the developer. For testing to see if it even works I don't think it would matter, if it doesn't work or is not the fix then we move on to something else. But if it works, I don't think we can just post the fix without the developer's permission on how he wants to handle it.
Let me see what I can find out
Alright that will be great. Thanks romified.
Sent by breaking the sound barrier
FYI, I know there is a free version of the Droid 2 bootstrapper floating around somewhere (I think the developer made it available on xda). I'll see if I can find the link.
ylexot said:
FYI, I know there is a free version of the Droid 2 bootstrapper floating around somewhere (I think the developer made it available on xda). I'll see if I can find the link.
Click to expand...
Click to collapse
Yes, I have the APK and have it decompiled...just not with me. I will dig into this afternoon and see what I can determine. If I can reach Kousch (the developer) he may be interested in helping do this and making it available since the NT is fairly popular. Then we could have help with a recovery as well.
Thanks for your help though ! If you find the link that is fine, it may help others who can look into this as well.
Found the link, but I guess it's not from Kousch:
http://www.mediafire.com/?fxvlw4wl2jade0o
It's in one of the Droid X stickies over at AndroidForums.
We have been discussing in another thread the possibility of getting a CM7 rom available for the NT.
Now that we have a functional recovery this should seriously help out with testing, if it goes wrong we can just restore to a working rom and start again debuging as we go.
***UPDATED 5TH Feb 2012***
I thought it was about time I updated this post with some up to date info on current state of development.
As many of you will know we got together last week and decided that we would like to build a CM7 rom for the Nook Tablet.
Goncezilla had already been making progress building firmware and a boot.img to get the thing booting up. Initially the system booted and you couldn't do a lot with it, but it prooved it could be done. Here's the vid showing the first boot:
After that it was down to work to make it useable. After a bit of investigation and a lot of man hours this is where we are at now
HARDWARE FUNCTIONS
Touchscreen FULLY WORKING
Orientation sensors FUNCTIONAL
Sound WORKING
SDCard WORKNING
WIFI Fully WORKING
Hardware video acceleration WORKING
SOFTWARE
Custom Kernel BUILT AND FUNCTIONING
Full tablet version on Cyanogen Mod WORKING
Root Access WORKING
Gapps WORKING
Sleep mode WORKING
Brightness control WORKING
BOOT FROM SD CARD SOLUTION AVAILABLE
and the one everyone seems to think is important
Angry Birds YES IT WORKS PERFECTLY lol
Another little video of current progress
Finally we have wifi working!
Sorry it's sideways, it's changing it now but it seems Google have slow computers!
So the main things we have left to fix are
1. Ermm... hmm... I'm sure we'll think of something
Thanks to Celtic for taking on the OP of this forum!
EDIT 2/5/2012Here are the source files used to create the first CM7 beta:
Internal
1. Kernel built from source - http://www.mediafire.com/?tu5lm7q8t5pbqpf
2. Nook Color CM7 Ramdisk (the one we want to modify) - http://www.mediafire.com/download.php?epv9n97evhnuaoi
3. Stock Nook Tablet Ramdisk (the one we need to borrow from) - http://www.mediafire.com/download.php?xms3aeztgupkjco
4. Buawk's Internal Boot.img 2ndboot (this gets appended to the front of a boot.img to get around the locked bootloader) - http://www.mediafire.com/download.php?9l8uxx7rhbqzund
5. Modified CM7 /system partition files (should be good to go for NT) - http://www.mediafire.com/download.php?il5ky2l51q48e8h
6. Modified Ramdisk - http://www.mediafire.com/download.php?9l8uxx7rhbqzund
7. Wifi Driver files (built from Kindle Fire source) - http://www.mediafire.com/?vogxuygrf84xsoe
8. Kernel Config File (settings used to build kernel above) - http://www.mediafire.com/?7vjvqctmlnd4enw
9. GFX Drivers (put in /system/lib/modules and insmod) - http://www.mediafire.com/?5uw4wgytb60n485
SDCard
1. SDRamdisk - http://www.mediafire.com/?4p3wq0u4p9j9mtd
All other files are same as internal.
EDIT 2/4/2012
My Plan for success:
1. Build a boot.img from CM7 NookColor Rom - Done!
3. Get a booting rom working from SDcard to verify steps 1 and 2 - Done! SDcard working great!
4. Port to internal boot partition (CWM) -Done!
5. Tweak to get everything working - Ongoing....
All other ideas welcome here!
I'll flash and test things for you all.
Sent from my Nexus S 4G using Tapatalk
LiuAnshan said:
I'll flash and test things for you all.
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Thanks
Just to let anybody interested know in advance, this may or may not turn into a working rom, even if it does become a fully functional rom please remember that during testing if your tablet does a nose dive and you can't recover for some obscure reason, we take no responsibility for any damage caused.
Other than that, as and when we have something testers will efinately be needed
Goncezilla said:
Reserved.
Ill post my current working files here soon. Thanks to Celtic!
My Plan for success:
1. Build a boot.img from CM7 NookColor Rom - Kernel built, working on ramdisk
2. Port /system partition -Mostly done but untested
3. Get a booting rom working from SDcard to verify steps 1 and 2
4. Port to internal boot partition (CWM) -2ndboot.img built and waiting
5. Tweak to get everything working
All other ideas welcome here!
Click to expand...
Click to collapse
So i'd thought id put in my two cents here...
First off, whom ever is testing this will want to have 2 sd cards, one of which is the update_acclaim boot disk, so they can "unbrick" their device. This device is nearly unbrickable, and whom ever ends up testing it, can make sure that they can always return it to stock.
Second off, I would HIGHLY recommend using the stock kernel, with the security keys stripped off. This would eliminate any problems that you would encounter with the kernel not causing a boot. I can get you guys a copy of the stock if you want, as it is easiest to just take the first 288 bytes off of the existing kernel, and ramdisk. I don't have an NC, but i'm not sure that the partitions are the same, I would think about building the ramdisk by combining the two ramdisks.
Lastly if someone has the inclination, they COULD eliminate the useless partitions, DO NOT TOUCH THE X-LOADER OR UBOOT PARTITIONS, MODIFYING THEM WILL BRICK YOUR DEVICE. However there is the useless BN and rom partitions that could be consolidated.
Ill be checking in from time to time, I would recommend that you join the CM7 IRC channel and make a new one so that you will not be bothered.
I've done little more than keep the port of miui updated for the Samsung infuse, but I'd be willing to help where I can. I'll probably only be useful for testing, but I'm more than willing to soft brick several times (or risk a hard brick )
Don't modify the rom partition, it forces a wipe of the device and without a proper recovery for that (stock) you're **** out of luck.
Sent from my Nexus S 4G using xda premium
Loglud said:
Second off, I would HIGHLY recommend using the stock kernel, with the security keys stripped off. This would eliminate any problems that you would encounter with the kernel not causing a boot. I can get you guys a copy of the stock if you want, as it is easiest to just take the first 288 bytes off of the existing kernel, and ramdisk. I don't have an NC, but i'm not sure that the partitions are the same, I would think about building the ramdisk by combining the two ramdisks.
Click to expand...
Click to collapse
Interesting about the first 288 bytes. Any specific reason for stripping them? Is this the kernel header or is it for the ramdisk too? The kernel Im using was built from the BN source.
The ramdisk Im putting together is a combo of the NC and NT. Im working on porting the .rc files and build.prop. There is a lot to look at and any help is appriciated. Ill post the files when I get home this weekend.
Lastly if someone has the inclination, they COULD eliminate the useless partitions, DO NOT TOUCH THE X-LOADER OR UBOOT PARTITIONS, MODIFYING THEM WILL BRICK YOUR DEVICE. However there is the useless BN and rom partitions that could be consolidated.
Click to expand...
Click to collapse
Good call here. I was thinking about mounting the 15GB B&N partition as rw and leaving it at that. If we get brave we can try and merge the partitions.
Thanks for the input.
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
Indirect said:
Don't modify the rom partition, it forces a wipe of the device and without a proper recovery for that (stock) you're **** out of luck.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Maybe this is the issue Im seeing. Does this mean we have to use 2ndboot to point to another partition? Is there a mdsum check being done at boot that triggers this?
EDIT: Nevermind was thinking boot partition instead of rom. Rookie mistake No plans to touch rom partition.
Guys, we won't need testers. We all have NT's. You all will get a build once it's in alpha.
Like Indirect said, as far as startup is concerned we'll be able to do the testing, we won't really need external testing until we have something semi stable.
Thanks for all your offers though. I'm sure when we get to alpha/beta stage you'll all get a shot at it
As agreed with OP i am going to move this to general. As soon as development is posted, it will be moved back to Development.
Thanks to the OP for his co-operation, He is a gentleman and exactly the type of member we want at XDA Developers!
Peace!
clock work mod
thanks to Albert I am beginning to understand the early stages of getting things like CM7 or 9 functional for the NT and his his recent video on youtube gives a good idea on the developments going on for the NT. I am trying to understand the possible uses of CWM for the nook other than it being a framework for installing custom roms. .. Thanks
Rafael863 said:
thanks to Albert I am beginning to understand the early stages of getting things like CM7 or 9 functional for the NT and his his recent video on youtube gives a good idea on the developments going on for the NT. I am trying to understand the possible uses of CWM for the nook other than it being a framework for installing custom roms. .. Thanks
Click to expand...
Click to collapse
Link to the video, per chance? Thanks in advance!
Just a quick update before I call it a night.
I've been having a lot of trouble getting a working boot.img built. When I cat the 2ndboot to my boot.img I see the flash screen on bootup but quickly get a black screen followed by a reboot of the system.
I can't even get the stock boot.img to boot after appending the 2ndboot.img file. I was, however, able to boot into CWM from the boot partition by attaching the 2ndboot.img. This tells me that the 2ndboot is working properly.
I'm continuing to deep dive on the boot.img files, but if any other devs want to play around with cat 2ndboot to a boot.img it might help.
All I've been doing to this point is taking the boot.img from a CWM recovery, adding the 2ndboot.img to the front of it, placing the modified boot.img back into a new CWM recovery folder (and rebuilding nandroid.md5), then flashing the boot back on using CWM Advance Recovery.
Well, I can report some partial success!
I was finally able to unpack a stock boot.img, modify the ramdisk (nothing major just a small tweak to test results), repack with another unsigned kernel, flash the new boot.img and get a good boot. I did this by using the kernel extracted from nemith's CWM image and not the custom kernel I've posted, so it seems like there is an issue with that kernel for now.
Anyway, I'll try and post some more files later but in the mean time I'm moving on with trying to get a CM7 ramdisk to boot.
I think this is now at a stage that it can be moved back to development.
Good work Guys!
Goncezilla said:
Well, I can report some partial success!
I was finally able to unpack a stock boot.img, modify the ramdisk (nothing major just a small tweak to test results), repack with another unsigned kernel, flash the new boot.img and get a good boot. I did this by using the kernel extracted from nemith's CWM image and not the custom kernel I've posted, so it seems like there is an issue with that kernel for now.
Anyway, I'll try and post some more files later but in the mean time I'm moving on with trying to get a CM7 ramdisk to boot.
Click to expand...
Click to collapse
Great to see you've made some decent progress. Sorry for my total lack of input, you're a good few steps ahead of me in developing. I'm still on a serious learning curve!
I'm getting there hopefully in time I catch up with you and give some decent worthwhile input!
CelticWebSolutions said:
Great to see you've made some decent progress. Sorry for my total lack of input, you're a good few steps ahead of me in developing. I'm still on a serious learning curve!
I'm getting there hopefully in time I catch up with you and give some decent worthwhile input!
Click to expand...
Click to collapse
Hey if you have any questions throw them out there. I'm learning some things as I go along but don't have all the answers either. Hoping we can start combining efforts to move forward.
---------- Post added at 10:31 PM ---------- Previous post was at 09:31 PM ----------
EDIT:More progress!
Was able to get the stock ramdisk to boot using the compiled kernel I posted. I think the issues were with my compilers. No guarantees they are fixed but we are getting close I can feel it!
I'm not sure but I think this kernel can be overclocked, so if nothing else this should allow you to overclock a rooted stock device for now. I'll do some testing and get back....
EDIT 2:
Well it looks like this kernel should be capable of overclocking, but there are a few other bugs with it (could not turn on wifi) that still need to be worked out so I am moving on for now. I will post the boot.img if anyone else wants to play around with the custom kernel on stock firmware in the meantime.
They had issue with wifi in the cm9 thread which they've now fixed. Perhaps some help from there thread will be available?[/QUOTE]
Good call, maybe we can leverage from them. I think I'm just missing a configuation setting in my kernel build but everything else seemed to be working so I'm not too worried about fixing it right away. Would rather get CM7 to boot
EDIT:
Well more progress to report this morning! I've finally got a CM7 boot screen! I'm stuck in a bootloop but we are really close now!
Turns out my permissions were all jacked up on my system partition and it was refusing to allow the kernel to load divers. I've jacked with files so trying to get a good boot that I'm not even sure what I have right now, so I'll go back to square one and hopefully see a full boot
Whenever you get a boot loop, I suggest that you get a logcat so you know what to look at.
Sent from my Nexus S 4G using xda premium
Okay, this thread is going to have A TON of info. I recommend that if you are new to Android you read this thread and any questions you have I will attempt to answer to the best of my knowledge or I'm sure someone else will.
It is, in my opinion, imperative that you understand the material of this post prior to playing around with your new Android device. Much of this topic is general purpose, i.e. it could apply to any Android device but I will be making specific references for the Nook Tablet.
Root: The Android OS is a linux based OS. Thus "root access" is a term that signifies full access to the file system of the OS. Consider root access similar to "administrative privileges" on Windows. An even more extreme analogy may be if you were to buy a Windows computer and find that you only had access to "My Documents;" the Android equivalent would be buying a device like the Nook Tablet (or pretty much any other android device) and not having root access.
Root for the Nook Tablet: We have various methods for rooting the Nook Tablet. The best method, IMO, is the sdcard method found here. This method will allow you to create an external microSD card that allows you to boot into a custom recovery (more on this later) and run a script which will get you "root access."
Why do I want root?: Root access allows you to do things you otherwise would not be able to do. Installing google apps is probably the biggest reason, but other reasons include making certain modifications to the device to allow you to do more "stuff." Another big reason is to install indirect's app which will allow you to flash (fancy word for install) a custom recovery to the internal memory of the Nook. He even has an app that will allow you to unroot the device and restore it to stock (I believe as of this post the unroot app only supports the 16GB model).
Custom Recovery? What's that?: A custom recovery is, IMO, the number 1 priority when tinkering with Android. The first instance of a custom recovery you may encounter is the one I mentioned previously, the sdcard version. I actually have a card that I keep imaged with the custom recovery (Clockworkmod Recovery) ready to go should I ever need it.
Within Clockworkmod Recovery or any other custom recovery, you will be able to do a few things: install zip files, make a backup of your current OS (and restore said backups), wipe data/cache. The key here, as with a lot of this stuff, is DO NOT START SELECTING THINGS YOU DO NOT FULLY UNDERSTAND. For some reason a lot of users have a habit of wiping system and other things within CWM thus resulting in broken partitions and other issues. Follow directions. If you are unsure of something, ask a question.
Custom ROM: ROM stands for Read Only Memory. It is the operating system of Android that is on your device. The stock ROM that comes with the device, a modified version of Android by B&N is very restricting. Getting root access on this rom will open up many options for users. However, as Android is open source, we have the ability to create custom ROMs that provide even more freedom and a "pure" Android experience.
These ROMs almost always come "rooted" as well. What I mean by this is that a developer could create a ROM that does not allow the user root access. In fact, the newest policy of Cyanogenmod (a very popular and hard working ROM development team) is that ROMs will no longer come "rooted" by default. Users will have to toggle root access in settings.
Custom roms are flashed (installed) via a custom recovery like Clockworkmod Recovery. Basically, if you have CWM on your external sdcard or flashed internally, you can store the ROM zip file on your internal memory (or the external card should you choose), boot into recovery, flash the ROM and voila you will be ready to boot into a new OS (you should probably wipe data/cache as well if its a new ROM). I must stress here that it is IMPERATIVE that you make a backup of your current OS prior to installing a new ROM. This way, you can restore your previous setup should you not like the new one or if there are any issues with the new one.
Boot from sdcard? Yes we are quite lucky with the Nook such that we can boot from the external sdcard. I have already mentioned booting into CWM from sdcard but we even have the benefit of booting into a custom ROM (CM7 only currently) from external sdcard. What this means is that you leave the internal OS completely intact. This would thus allow "dual booting" i.e. you can boot into internal or boot from external.
Back to stock: Getting back to stock is incredibly easy with the Nook Tablet. I've done it myself a few times on two devices for various reasons. Many people are afraid to root or flash custom ROMs because it voids the warranty. While true, if you are able to return the device to stock conditions, B&N has no way of knowing that the device has been tinkered with and thus the Warranty remains intact.
To wrap this up, I must stress how important it is that you read, read, read and read more when doing this stuff. Follow directions to the T. Ask questions if you aren't sure about something. I know this is a long post as well but I can't stress how important it is that users understand the information I have put forth here when rooting and/or flashing custom ROMs.
Also, if someone wants to add benefits to why rooting the stock OS is useful please feel free to do so (I admittedly have little experience with the B&N stock OS and thus am not 100% positive of the benefits of rooting the B&N stock OS).
Reserved.
The Download link for the Cyanogen Mod 7 Final Image is down?
I would like to download the latest Cyanogen Mod 7 Final Image, so I found this webpage containing the latest version of this Image =
http://forum.xda-developers.com/showthread.php?t=1481826
and tried to download the SD card for the Nook Tablet..
BUT the link to the SD Card for the Nook Tablet appears to be dead..at the very least, it's not working properly.
Please, can someone direct me to a proper link to download the correct Cyanogen Mod 7 Final Image for the 16 gig Nook Tablet ?
Thanks!
I'd check/ask in the thread for that rom.
I tried to make a similiar comment on that thread, however; I recieved a notice that since I was new here, I'm not allowed to post a comment on that development thread.
That is why I'm making a similiar request on this thread.
All I'm attempting to do at this point is simply download the correct Cyanogen Mod 7 Final Image, so, I'm requesting help in that regard.
Thanks again~
um, i have a request. could you please post your questions in the 'Q&A' section.
http://forum.xda-developers.com/forumdisplay.php?f=1508
thx.
.
now having 'asked nice' for that... i have another link. imho, @succulent has a better version of the cm7 internal for 16GB. it is here.
http://iamafanof.wordpress.com/2012/06/12/cm7-2-rc1-build-20120612/#more-739
thank you, "old fart"..
Please, accept my apologies for posting on an incorrect thread.. I honestly thought that I was posting on a thread that might be able to help.
Also, thank you for posting a webpage that contains the correct Cyanogen Mod 7 Image. In regard to this better Build of the Cyanogen Mod 7 for the Nook Tablet..I admit that I'm a real noobie, I'm simply asking because I don't know.
Is the Cyanogen Mod 7 Image in the Mediafire Folder listed on that webpage ?
If so, I've opened that Mediafire folder ..this folder contains a long list of various files.. which is the correct file that I should download, and write to my sd card ?
Thank you much for your help in answering my questions~
Please take it to another thread~
GENERAL CONDUCT REQUEST
@sinatrafan:
please refrain from using CAPS to get your point across, I'm sure people with be able to read a few sentances and respond without you needing to e-yell. Another suggestion, as a new member, maybe read some of the forum guidelines to better understand how we operate. In general, ask as many questions as you'd like, but do not expect an answer every time or on your time table, just hope that you get what you're looking for. Don't forget to search for yourself, I'm sure you could have found current links, just as the link was provided to you, I'm sure they foud that link by searching. Also, you'll likely receive better help if you are polite. Thank you.
I went to that link for you, here's the direct link for both (assuming the newest is the one to get).
ROM > http://www.mediafire.com/download.php?5gw47zw4xx108gc
GAPPS > http://goo.im/gapps/gapps-gb-20110828-signed.zip
@OP and other senior members:
please don't flame people with less than 10 posts, they're new here, remember when you were new? Just try to answer questions and be helpful, or don't post. If somebody is out of line, report the post and I'll get to it soonish. Thank you.
Installing/Flashing CWM on Rooted 1.4.0 NT w/ Blocked OTA Updates
Gents,
I stepped away from the world of the Nook Tablet over the last 5-6 months in order to focus on other Android devices.
Last time I was involved with the NT, I rooted my son's NT with Indirect's 'Full Root (v1.4.0) w/ Blocked OTAs w/ ZergRush exploit' Thread.
From what it seems, there have been a few changes, including obtaining root access for NT's that have 1.4.1+ through the SDCard boot method.
Quick question:
I want to load a custom recovery on my son's NT, such as Xionia or CWM. The root via SDCard method includes this as part of the overall root method.
Is there a preferred way that I can install/flash custom recovery on my son's NT, knowing that I have a rooted 1.4.0 NT Blocked OTA updates?
Just curious.
Thank you,
BJ.
Anyone?
b1ggjoe said:
Is there a preferred way that I can install/flash custom recovery on my son's NT, knowing that I have a rooted 1.4.0 NT Blocked OTA updates?
Click to expand...
Click to collapse
I have a preference for the internal method. Plug in things are sometimes troublesome for me.
LOL! Well that's not exactly what I was asking however. As I stated, I currently have a rooted Nook Tablet (1.4.0) with Blocked OTA Updates (I used the original method from November 2011).
I am not interested in loading any kind of Custom ROMs at this time, but I do wish to add CWM or some other kind of custom recovery to my son's Nook Tablet.
Is there a recommended method to do this, without going through a re-rooting process with the 'Boot from SDCard method'?
Thanks,
BJ.
Anyone?
Nook RecoveryFlasher.apk
Search on Nook Recovery Flasher.apk and see if that app will meet your need. I believe it was created by Indirect.
Aaah ok will do. Thank you!!!!
Nook won't boot with CWM on card
Guys, am I the only one having this problem or are there others?
I've read and clearly understand the procedure to root my Nook Tablet. The problem is that no matter what I do, any time an SD card with a bootable CWM is inserted, the Nook simply refuses to start. Removing the card or for that matter replacing it with any other card that does NOT have a bootable CWM fixes the problem. It'll even boot and run the pseudo-root ROM that runs off the SDCard without actually rooting the tablet.
I've tested this with many cards and with several different ways to prepare it, and the end result is always the same regardless of what mode the Nook is in. I'm thinking that if somehow I'm not preparing the card correctly, then wouldn't the tablet simply boot up normally as it does with any other card that has no bootable CWM in it?
Since I bought my tablet at about the end of August 2012, I'm thinking B&N put something in the stock ROM to detect any other recovery and stop cold if that's what it finds. I say this because the problem is only with bootable recoveries, any bootable non-recovery works OK.
Any ideas??
humb11 said:
Guys, am I the only one having this problem or are there others?
I've read and clearly understand the procedure to root my Nook Tablet. The problem is that no matter what I do, any time an SD card with a bootable CWM is inserted, the Nook simply refuses to start. Removing the card or for that matter replacing it with any other card that does NOT have a bootable CWM fixes the problem. It'll even boot and run the pseudo-root ROM that runs off the SDCard without actually rooting the tablet.
I've tested this with many cards and with several different ways to prepare it, and the end result is always the same regardless of what mode the Nook is in. I'm thinking that if somehow I'm not preparing the card correctly, then wouldn't the tablet simply boot up normally as it does with any other card that has no bootable CWM in it?
Since I bought my tablet at about the end of August 2012, I'm thinking B&N put something in the stock ROM to detect any other recovery and stop cold if that's what it finds. I say this because the problem is only with bootable recoveries, any bootable non-recovery works OK.
Any ideas??
Click to expand...
Click to collapse
Try powering off, inserting your bootable SD card in the tablet, then plugging the B&N USB cable into your tablet. Some tablets (and there doesn't seem to be any rhyme or reason to it) will only boot from the external card if they detect the USB cable.
Saludos,
Steve
Post to Q&A and someone will sort you out.
The OP mentioned that he only dual boot bootable Cyanogenmod image is CM7. Is there a reason why CM10 is not possible? It seems the N2A people are advertising that capability on their website. I would like to be able to do that myself if possible.
Ok so I'm what you guys would call a newbie with Android, I've been an iPhone user for years (switched from Verizon to AT&T to get the iPhone because at the time it was an AT&T exclusive). However I'm a really big Google enthusiasts so I have followed Android from inception. Growing tired of how bad AT&T's reception was in my house I recently switched back to Verizon and I purchased the GS4. I'm very happy that I can make calls without the use of a Micro Cell, truthfully reliable coverage was the biggest reason why I switched carriers. Else I would probably got the GS4 or HTC 1 on AT&T.
Being a newbie I made some noob mistakes, however I'm glad to report non of my mistakes bricked my phone. My phone works flawless it's only the stock recovery that is jacked up. So to start off I naively though all S4's were 100% open when rooted, by that I thought I could simply install any ROM I wanted to as long as I was rooted. However it appears that Verizon made Samsung lock the firmware with the OTA updates, from what I gather now after reading is the initial firmware was ok but the subsequent OTA downloads introduced the locked boot. Which sucks for me because I willingly took both updates which put the ME7 and now the MI1 builds on my device.
When I started to root process I had the MI1 build and I performed the De LaVega root method (thank you Tomsgt for your videos)! At the time of root and right after the root I was still not aware of the difference with builds. At that point I attempted to install TWRP via GooManager, since I had the MI1 build it did not work. GooManager kept telling me there was no file for my phone or something similar.
Now this should have been huge red flag for me but I was persistent and I looked on TWRP's website and found the file for my phone along with the manual install instructions. I'm familiar with using a Linux command line so followed the instructions to write TWRP into /dev/block/mmcblk0p21 on my device.
After reboot my device failed to get into stock recovery mode, instead it goes back into download mode but has an extra line of text that says "Could not do normal boot". Since I originally hosed my stock recovery I have read up on the different builds and I have also successfully installed the clockmod recovery option. That all works fine it's just factory recovery is still hosed up and it's annoying me!
I know that was a bit long winded but wanted to give a little background. Now I hope I'm not the only guy/girl who has jacked up the stock recovery section. I was hoping someone had some instructions to fix. Heck I think (but I'm not 100% sure) that if I can get someone who still has stock recovery to copy/export what they have in /dev/block/mmcblk0p21, then I can download that file put on my sd card and then write that back into my system using the same dd input/output command I did before.
May not be that easy but that's what I'm hoping for, or maybe some suggestions. :fingers-crossed:
Thx,
Joe
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
kennyglass123 said:
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
Click to expand...
Click to collapse
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
garzjoe said:
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
Click to expand...
Click to collapse
Bump....
Still hoping there is someone out there who can help me out.
garzjoe said:
Bump....
Still hoping there is someone out there who can help me out.
Click to expand...
Click to collapse
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
southpaw5271 said:
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
Click to expand...
Click to collapse
Hmm I can investigate that but my phone is not bricked. I'm using it now to reply to you. Stock recovery is hosed...so when I power off and then hold Vol+, Power, Home key and then let go of power and keep holding the other two buttons. That key sequence gets my phone into recovery mode. However I can't get into that with my phone anymore.
Thx,
Joe
Hello, I've got a bricked Wiko Ridge 4G. I tried everything so far to get it to work.
The problem is that Wiko original app doesn't finish the flashing.
I can flash with fastboot. I flashed all files except system, cache and data.
I booted TWRP, it shows that these partitions have 0 space.
Basically I can explore internal storage with file explorer in TWRP, but system folder is empty, as well as the other two.
I think I could fix this by flashing in fastboot mode.
I extracted the ROM from Wiko flasher, but the files for system, data and cache partition are sparsed.
Does anyone know how to flash this or compile it into one file?
They are all in .img format.
Every second file has only 8 kB, others are all around 128 MB, but are not exactly that much.
All partitions are detected in fastboot when you try to flash something.
I tried to do getvar for all partitions, but it never gives any output.
Other thing that might help my case (I think so) would be a nandroid backup. If someone has a working device, I would appreciate to get me some backups of these 3 partitions
Jovan Riparazioni said:
Hello, I've got a bricked Wiko Ridge 4G. I tried everything so far to get it to work...
Click to expand...
Click to collapse
I don't have this device but, the following thread may be helpful for what you need and don't be afraid to ask for some member guidance too.
https://forum.xda-developers.com/showthread.php?t=3586572
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen said:
I don't have this device but, the following thread may be helpful for what you need and don't be afraid to ask for some member guidance too.
https://forum.xda-developers.com/showthread.php?t=3586572
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Hey, thanks for a quick reply. I already flashed it a dozen of times in EDL. I tried with QFIL, Huiye Qualcomm flasher and even some other tools.
As it starts flashing those partitions, it stops getting readback from sectors.
Out of respect to you and hope I tried to flash it with those Blu firmwares.
Both end normally, but nothing is changed, not even the logo.
I think it's due to having encryption or Google Account removed at the time of rooting, but I'm not sure, because I can flash pretty much any partition other than those (which I can't cuz chunks...).
I can erase config, oem, there isn't even FRP partition.
I found supersu folder in the root directory with TWRP. When TWRP boots, it says something about failing to mount data partition due to wrong or missing encryption header.
As far as I understand, this could also be due to small incompatibilities of existing TWRP for L5510.
When I try to do anything with those partitions, it gives out an error 8.
Only copying files from internal to SD I know works for sure, I haven't tried other way.
I formated system, cache and userdata normally with fastboot format:ext4, but TWRP still reports 0 size with some subdirectories inside the main folders (partitions) in root directory.
Is there a way to compile the system from those system_x.img chunks?
I'm using Windows 10, so it's a bit more difficult to work with .ext4 fs images, I don't really know of a really 'smart' and universal tool which can do my work.
I had an idea to manually copy the content of system.img to system partition with twrp, as well with other partitions. I know it's a pain in the butt, but I don't really know what to do anymore.
I'm an ex repairman, I'm let's say "specialised" for software type of work. I'm quite familiar with deep flash, partitions, sectors, memory addressing and stuff. I at least understand how it works.
Only thing I haven't tried is the above mentioned: copying files manually (which might not work, no matter I can copy files without trouble), nandroid, or compiling/extracting those chunks into something I can actually work with. If you know something, please enlighten me. I bought this unit cheep for 30 euro while I was still in business, but now I need a new phone for myself, and I know Wiko isn't much comparing to my current HTC M7, but this M7 is dying literally, so I'm good as far as it's Qualcomm haha
i have the same problem as you with my ridge 4g
did you find any solutions ?????
plzzzz help me
_6ix._.9ine said:
i have the same problem as you with my ridge 4g
did you find any solutions ?????
plzzzz help me
Click to expand...
Click to collapse
Nope, seems like nobody will give us a nandroid
wiko ridge 4g
Jovan Riparazioni said:
Nope, seems like nobody will give us a nandroid
Click to expand...
Click to collapse
did u find q solution ???