By now some of you are anticipating in getting one & have researched every known articles. But while reading all these wonderful articles, I kept asking myself, "how about dev'n these bad boys. Is it easy to root, load a new ROM & recover from a brick?"
Let me tell you it's ridiculous easy to root, install recovery & ROMs and recover from an unbootable device.
Here's the basics on recovering from an unbootable device by booting into fastboot & re-installing
Press "POWER" until you see the Google logo then press "VOL DOWN". If you did it correctly, you should be in bootloader.
Download the N7 Google Image then plug your device to a Mac/Linux & type "./flash-all.sh" & wait 5-10mins. It's that simple.
You can go into the Dev forum to learn how to root, install recovery & location of the Google N7 image.
I left out the screen, storage, & etc... because you can find it here or on the net.
EDIT:
will include the full instructions since I assume you had Android SDK installed on your system
1. Download & unrar Google's Android SDK
http://developer.android.com/sdk/index.html
2. use the SDK to download platform-tools
2. download Googles N7 image & unrar in the platform-tools folder
https://developers.google.com/android/nexus/images#nakasi
3. make sure N7 is in bootloader (hit power & hit vol down when you see the google logo)
4. plug to your Mac or linux box
5. open up terminal & CD into the folder that has the N7 image (.../.../platform-tools/N7 folder)
6. type ./flash-all.sh or sudo ./flash-all.sh
7. you are now back to stock
That concludes it, I'm just your typical geek, flash happy gadget dude.
Apps used in testing:
stock text/PDF reader, video & music player
MX Player w/ ARM7 neon plugin
Stick It player with plugin
Quick Office Pro
Root Explorer
Hardware used:
I/O Nexus 7
Belkin 2 Port USB powered hub
generic OTG
generic usb sdcard adapter
32gb microSD
Files used:
text & pdf file
MP3
MKV anime
AVI XVID
Formatting sdcard via
formatted FAT32 & NTFS using Win 7 pc
formatted EXT3 & EXT4 using G-Parted from linux (VMWare WS running Ubuntu)
1st testing:
FAT32 & NTFS: I copied the files from the PC to the sdcard.
EXT3 & EXT 4: I copied the files from linux (VMWare WS running Ubuntu) to the sdcard.
results from 1st testing:
FAT32 & NTFS: Unable to read PDF's & play the video files
EXT3 & EXT 4: Unable to read PDF's & play video files
2nd testing:
I copied the files from the PC to the tablet & will then transfer the files from the tablet to FAT32, EXT3 & EXT4 sdcards
results from 2nd testing:
FAT32: Unable to play music, video files & read PDF
EXT3: able to play the music, video files & read PDF
EXT4: able to play the music, video files & read PDF
3rd testing:
I used AirDroid to copy files from Linux to the tablet & will then transfer the files from the tablet to FAT32, EXT3 & EXT4 sdcards.
results from 3rd testing:
FAT32: Did not test
EXT3: able to play the music, video files & read PDF
EXT4: able to play the music, video files & read PDF
what about windows?
RMXO said:
Let me tell you it's ridiculous easy to root, install recovery & ROMs and recover from a brick device.
Here's the basics on recovering from a brick device.
Press "POWER" until you see the Google logo then press "VOL DOWN". If you did it correctly, you should be in bootloader.
Download the N7 Google Image then plug your device to a Mac/Linux & type "./flash-all.sh" & wait 5-10mins. It's that simple.
Click to expand...
Click to collapse
Good to know that it is that easy to recover from a bricking. Sorry you had to find out how, though
rcrd-pt said:
what about windows?
Click to expand...
Click to collapse
My advice for folks on Windows that don't have a Mac or linux box is to download & install Sun's VirtualBox & install Ubuntu. It's very easy to do & doesn't take up much space.
revmra said:
Good to know that it is that easy to recover from a bricking. Sorry you had to find out how, though
Click to expand...
Click to collapse
No need to apologize, I was wondering how long before I took me to brick & learn how to get it back to stock. I'm now more comfortable in messing around with the device since I know I can restore it back to stock within 5-10mins.
RMXO said:
reserved for my power hub & MHL testing later
Click to expand...
Click to collapse
yeah, that really begs the question of whether I can plug OTG into a powered usb hub to use peripherals and a mass storage device AND charge at the same time.
Will be interesting to see:highfive:.
@RMXO
You previously confirmed read write EXT3 EXT4 on OTG. Is that correct?
Hemidroids said:
@RMXO
You previously confirmed read write EXT3 EXT4 on OTG. Is that correct?
Click to expand...
Click to collapse
That is correct, I created a folder & moved files from the tablet using Root Explorer
I don't know if you have already stated this or not, but have you tried putting it into the tablet ui?
doctahjeph said:
I don't know if you have already stated this or not, but have you tried putting it into the tablet ui?
Click to expand...
Click to collapse
how do i put it in tablet UI? my current DPI is 213 but that shouldn't matter though. Correct me if I'm wrong here.
RMXO said:
how do i put it in tablet UI? my current DPI is 213 but that shouldn't matter though. Correct me if I'm wrong here.
Click to expand...
Click to collapse
It does in the build prop lower the density to 160 using root explorer
Are you able to read from an otg devices without a hub?
Sent from my PG86100 using Tapatalk 2
aaronpoweruser said:
It does in the build prop lower the density to 160 using root explorer
Are you able to read from an otg devices without a hub?
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
I need to redo my testing on EXT3 & EXT4 from an OTG cable only.
Man, I can barely read anything with 160 DPI.
RMXO said:
I need to redo my testing on EXT3 & EXT4 from an OTG cable only.
Man, I can barely read anything with 160 DPI.
Click to expand...
Click to collapse
Did the UI change when you put it to 160 or did it stay in the phone UI?
doctahjeph said:
Did the UI change when you put it to 160 or did it stay in the phone UI?
Click to expand...
Click to collapse
Sorry I have yet to test tablet mode & won't do it until later. I just want to finish up what I'm doing now & then redo testing in tablet UI. Plus, I'm probably going to redo my testing later, I've been up this for a while & now my brain is fried.
RMXO said:
Sorry I have yet to test tablet mode & won't do it until later. I just want to finish up what I'm doing now & then redo testing in tablet UI. Plus, I'm probably going to redo my testing later, I've been up this for a while & now my brain is fried.
Click to expand...
Click to collapse
Awesome! Thank you so much for this. Get some rest. Maybe you can do a seperate thread for tablet ui testing.
doctahjeph said:
Awesome! Thank you so much for this. Get some rest. Maybe you can do a seperate thread for tablet ui testing.
Click to expand...
Click to collapse
I'm completely redoing all my testing with hopefully less confusing test methods. Once, I get done with that, I will re-do everything in Tablet UI mode.
Thank you for going to such great depths with this testing RMXO - it's reassuring for all of us that don't yet have our hands on our ordered N7's that there is hope It's greatly appreciated.
Revised my testing methods & posted results in thread #2
Thank you for all the testing and for passing along what you learned.
If you would, could you lay out what downsides, if any, there are to rooting?
I ask because I discovered I could not play movies from Google on my rooted phone.
I don't regret rooting my phone because the benefits (CM9 !) exceed the inconvenience by a mile.
I might think twice about rooting my tablet, 'cause I want to be able to rent or buy protected content without jumping through hoops.
danny8 said:
Thank you for all the testing and for passing along what you learned.
If you would, could you lay out what downsides, if any, there are to rooting?
I ask because I discovered I could not play movies from Google on my rooted phone.
I don't regret rooting my phone because the benefits (CM9 !) exceed the inconvenience by a mile.
I might think twice about rooting my tablet, 'cause I want to be able to rent or buy protected content without jumping through hoops.
Click to expand...
Click to collapse
Yo're welcome & I honestly can't answer the downside of rooting because I love tinker & the only way to do that is to root. Actually, by rooting, you open yourself to bricking your device. That is the extreme case if you don't know what you are doing & can't follow directions properly. I've listed a way to recover from a bricked N7 device.
There is an app called "Voodoo OTA Rootkeeper" that allows you to unroot & go back to root when needed.
My tablet is unlocked, rooted & able to play movies from the Google Play Store.
Related
This thread is about installing Android natively on your Vogue so it completely replaces Windows Mobile.
[size +1]Important: This thread is now out of date, if you want to flash Android, use the new "norootfs" NBHs.[/size]
There are 2 installation methods:
If you are already running android from your sd card then use method 2, if you want a fresh install of android 1.5 from a windows machine use method 1.
For both methods, you must have a HardSPL installed, if you have flashed a custom wince rom before then you will, otherwise read one of the other threads on XDA about how to do this.
Method 1:
------------------------------------------------------------------
download the following:
http://www.mediafire.com/?zldjhfnkzk2
Unzip it and follow the instructions in README-ANDROID.txt.
All you have to do is copy the androidinstall.tar file to your sd card and run ROMUpdateUtility.exe on your PC.
Now Donate:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
You will also need a new rootfs:
http://it029000.massey.ac.nz/vogue/files/rootfs.zip
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
There are 3 ways to flash a rom.
1. Use ROMUpdateUtility under windows (this may not work on these roms, i haven't tried it). Rename the nbh file to RUU_signed.nbh.
2. Use HTCFlasher under Linux, this is what I have been doing and although a bit quirky, it does work. A binary that fixes a few things with HTCFlasher is on the website.
3. Rename the nbh file to VOGUIMG.NBH, put it on an SD card and boot the phone while holding down the power and camera keys.
When it starts, it should be running from nand. The tmp and cache dirs are still mounted from sd, so you do need the sd card in there but it's not really used much.
If something goes wrong or you haven't copied the correct files, press volume up while it is booting (after the two vibrates preferably). It will display a message saying that its in recovery mode. You should be able to plug the phone into a computer and the sd card will appear as a usb drive. You can also connect using adb.
There are a few limitations, rootfs must be less than 13M, system must be less than about 90M and data must be less than about 128M. This means unless you use a very stripped down system with apps2sd, hero probably won't work.
I've put a linux adb binary on the files page that fixes the annoying history 'feature' too.
Remember, this will completely wipe windows mobile and all your data from the phone. Run android from SD first to make sure you like it and don't want to be able to easily go back to windows mobile.
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Woot!
Doing this now =)
dzo said:
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Click to expand...
Click to collapse
I'm paypaling 5 bucks right now.... and I dont have a Vogue, I have a kaiser, but hey, $5 is long overdue for all the work you've done for the kernel... if NAND support hits the kaiser, I'll probably throw another $5-10 your way.
*paypaled - I normally dont do this kind of stuff, but its the holiday season, the MSM Android project has made SO much progress cause of DZO, if everyone just donated $5-10, it would at least be a nice gesture for all the work he's done*
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
If I understand correctly, theres "NO" build in here, you play with builds in your DS, and when you are ready and like one..you just use that system.sqsh data.img rootfs (provided) and..the nbh, all in the root of the sd card. And it will flash the nand with your files! So..thats it!
Nice one dzo, hoping for you to get to kaiser
Hey Martin, I can't even use these flashable images, but if it weren't for you I wouldn't even be running Android via haret, plus you've answered so many of my questions and I've never donated. So, since you're actually now, I'll donate $10.
flashing from windows
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
gswarriorfan said:
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
Click to expand...
Click to collapse
nothing that hasnt already worked works there is no change...
dj13241 said:
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Click to expand...
Click to collapse
yea camera + power + reset hole
Shidell said:
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
Click to expand...
Click to collapse
i can answer a few
1 nothing that wasnt already working this isnt a build!!!, this is a way for VOGUE users to be able to put a working build "data.img and system.sqsh" they already have working on their phone and to be able to get rid of android
2 this isnt a build
3 320x240 shows more on screen 320x428 and 320x480 show more on screen but it is a little blurry
4 you will require adb drivers located on http://code.google.com/p/vogue-android and as far as i know they work on vista 32 and win 7 32 bit and there are different ones also located at vogue-android for win 7 64b
there are adb drivers for linux in the android SDK located here http://developer.android.com/sdk/1.6_r1/index.html make sure you download 1.6r1 though! 1.5r3 doesnt work for our devices in linux
5 just reflash any wm rom (that works with vogue of course)
mrkite38 said:
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
Click to expand...
Click to collapse
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Ahhh ok I get it now. I'll still donate when I get it up and running. Thanks!
OMFG!!!! dzo you are something else!!!
I just got my Vogue a few weeks back and I am surprised on how well Android runs on this thing (I have a Raphael as well, but no comparison to this)
Having a flashable rom to a WM device... unbelievable...
Kudos for your work man!!!!
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Click to expand...
Click to collapse
I tried that and it came back in bootloader with 'RUUNBH' in the upper right corner. Then I added the task3 and it booted normally. Who knows, maybe I did something else funny.
I used htcflasher on my newly-reloaded ubuntu laptop, but I wasn't able to get it to work under windows. So I thought that maybe flashing from windows was ok, but it just needed a kick through mtty to get going.
What do those two bootloader commands do? Not that it really matters since dzo says the newest version should work from windows anyway...
egzthunder1 said:
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
Click to expand...
Click to collapse
Boot back to bootloader and flash it! Did that myself last night.
Also, how do we make a smaller data.img? I keep getting 256MB versions.
scizzle said:
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Click to expand...
Click to collapse
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Thanks you so much dzo. i got this working, now im going through all my android files on my computer to find a build that i like, and wanna keep as my main build, but one thing, does the data really have to be less than 128mb? because almost all my android builds are alot bigger which is annoying.
but other than that it worked like a charm. thanks so much.
p.s. once i get some $$ (the 15th of december [my payday]) and find a permanent build i'll send some donations for you hard work.
dzo said:
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Click to expand...
Click to collapse
Legend! Thank you. I will try it as soon as I can figure out the data.img haha.
scizzle said:
Also, how do we make a smaller data.img? I keep getting 256MB versions.
Click to expand...
Click to collapse
jamezelle said:
i used the following commands to make a new data img
Code:
dd if=/dev/zero of=~/data.img bs=1048576 count=128
mke2fs -F ~/data.img
to make a blank 128 mb data.img file in my home folder
Click to expand...
Click to collapse
- I can now confirm that flashing the nbh with the ruu works from Windows.
- dzo, I have a panel type 3 us sprint vogue. everything booted up fine, the buttons work, but the touchscreen isn't. Will post logcat / dmesg in a bit.
edit: uploaded zip w/ logcat and dmesg
Just wondering if anyone is working on a one-click root or custom ROM (obviously, for a donation!!!) for the NC? I am going to take the time to root this weekend, but would obviously love to just DL something and flash it.
Well, one click isn't really one click. There are lots of other clicks involved, turn on computer clicks, go to download page clicks, download clicks, then load on SD card clicks or Start - Run - cmd clicks, then the closing windows clicks.
What I believe you should have been asking, without the sugarcoating of the "one-click" phrase, is: "If it isn't too much trouble, can I use your third Genie wish after you've rubbed the lamp? I'll donate, of course, not that it would matter because I can only assume one of those first two wishes was an insane amount of money"
devis said:
Well, one click isn't really one click. There are lots of other clicks involved, turn on computer clicks, go to download page clicks, download clicks, then load on SD card clicks or Start - Run - cmd clicks, then the closing windows clicks.
What I believe you should have been asking, without the sugarcoating of the "one-click" phrase, is: "If it isn't too much trouble, can I use your third Genie wish after you've rubbed the lamp? I'll donate, of course, not that it would matter because I can only assume one of those first two wishes was an insane amount of money"
Click to expand...
Click to collapse
Precisely, what you said!!!! lol. Believe me, I try...
coldbeverage said:
Precisely, what you said!!!! lol. Believe me, I try...
Click to expand...
Click to collapse
Glad you enjoyed reading it as much as I did writing it
Now... that out of the way, and in all seriousness, can I use that third wish from someone?
devis said:
Glad you enjoyed reading it as much as I did writing it
Now... that out of the way, and in all seriousness, can I use that third wish from someone?
Click to expand...
Click to collapse
I'll have more time to mess with this after this week is over. On my todo list is trying the BN kernel's video console support so we can at least write a message to the screen when Nooter is done rooting, and copying over superuser.apk and su and maybe Astro for starting out.
With the above we could have an almost-1-click root if someone could make the card writing process easier. It would be nice if we had a Linux boot CD or boot USB image that can reformat the card (check that it's a USB device first and ask the user!) to make the boot partition the whole disk automatically. Or someone could verify the rumor that HP's USB bootdisk maker formats the drive correctly.
I'm not the guy to do a 1-click root; exploits aren't my thing, but my goal is to make Nooter easy enough that we don't need to go that route.
My apologies if this has been covered....but with my eken slate, we use an update.zip file....the device automatically does a restore with this file if its present on the sd card
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Thanks. I am just an IT lawyer who's only been at this android stuff since August so much to learn (for instance, figuring out what you wrote below.....I do try to learn and not constantly ask on here though)!!!!
johnopsec said:
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Click to expand...
Click to collapse
coldbeverage said:
Thanks. I am just an IT lawyer who's only been at this android stuff since August so much to learn (for instance, figuring out what you wrote below.....I do try to learn and not constantly ask on here though)!!!!
Click to expand...
Click to collapse
No problem. Just so nobody is confused about anything I posted above: I take absolutely no credit for anything (especially nooter) in my post. I simply wrote down the steps I took using OTHER PEOPLES ideas and code.
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
johnopsec said:
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Click to expand...
Click to collapse
jasoraso said:
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
Click to expand...
Click to collapse
^ This.
Thats the main reason I am holding out on rooting... That and I want to see how far it goes before the market place comes out unless an easy solution like this comes out. While I like the updates here, I am also not in a huge needs for a large phone... but still Great work so far!!!
johnopsec said:
No problem. Just so nobody is confused about anything I posted above: I take absolutely no credit for anything (especially nooter) in my post. I simply wrote down the steps I took using OTHER PEOPLES ideas and code.
Click to expand...
Click to collapse
Lol. I just meant that I try to help you guys, but I have so much to learn on actually doing the stuff you do. Everyone is sharing there stuff on here openly. All good.
I am going to try to teach myself how to use ADB. Kinda nervous though.
jasoraso said:
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
Click to expand...
Click to collapse
coldbeverage said:
I am going to try to teach myself how to use ADB. Kinda nervous though.
Click to expand...
Click to collapse
No kidding, that is whaat ij aam strugglliing with. Thhaatt and tthe stupid keyybboard!
pokey9000 said:
With the above we could have an almost-1-click root if someone could make the card writing process easier. It would be nice if we had a Linux boot CD or boot USB image that can reformat the card (check that it's a USB device first and ask the user!) to make the boot partition the whole disk automatically. Or someone could verify the rumor that HP's USB bootdisk maker formats the drive correctly.
Click to expand...
Click to collapse
I was messing around with UNetBootin, which is similar to the HP USB formatter. It is designed to take linux ISOs and format them as bootable. But I don't know what specialized format Nooter uses. I didn't get far on this front.
It seems windows users are having trouble with windows drivers needed to get USB ADB working. An alternative is to enable ADB over IP. Leaving this open persistantly is a security hole, but it may be appropriate for initial setup.
PHiZ said:
I was messing around with UNetBootin, which is similar to the HP USB formatter. It is designed to take linux ISOs and format them as bootable. But I don't know what specialized format Nooter uses. I didn't get far on this front.
It seems windows users are having trouble with windows drivers needed to get USB ADB working. An alternative is to enable ADB over IP. Leaving this open persistantly is a security hole, but it may be appropriate for initial setup.
Click to expand...
Click to collapse
Getting the OMAP to boot off of SD requires a few things:
-the OMAP wired to boot from SD
-an SD card with a specific disk geometry as reported by the partition table
-a FAT16 or 32 filesystem on the first partition
-a first and second stage bootloader (MLO and u-boot.bin) in the FAT filesystem
The hardest part of getting Nooter installed correctly is creating that special partition table, and so I released it as a raw dump of an SD formatted using that scheme to only a 40MB image. The theory I've heard is that for maximum BIOS compatibility the HP USB formatter tool generates this same sort of geometry, after which you just need to drag and drop the four Nooter files onto the drive. I haven't had a chance to try this yet though.
edit: I'll be damned, it does work! Just format using hpusbfw.exe (Google it) with "quick format" checked and "create a dos startup disk" unchecked. Then copy MLO, u-boot.bin, uImage, and uRamdisk over. That's it. Plus you wind up with a FAT32 partition that takes up your whole disk, not just 40MB.
pokey9000 said:
Getting the OMAP to boot off of SD requires a few things:
-the OMAP wired to boot from SD
-an SD card with a specific disk geometry as reported by the partition table
-a FAT16 or 32 filesystem on the first partition
-a first and second stage bootloader (MLO and u-boot.bin) in the FAT filesystem
The hardest part of getting Nooter installed correctly is creating that special partition table, and so I released it as a raw dump of an SD formatted using that scheme to only a 40MB image. The theory I've heard is that for maximum BIOS compatibility the HP USB formatter tool generates this same sort of geometry, after which you just need to drag and drop the four Nooter files onto the drive. I haven't had a chance to try this yet though.
edit: I'll be damned, it does work! Just format using hpusbfw.exe (Google it) with "quick format" checked and "create a dos startup disk" unchecked. Then copy MLO, u-boot.bin, uImage, and uRamdisk over. That's it. Plus you wind up with a FAT32 partition that takes up your whole disk, not just 40MB.
Click to expand...
Click to collapse
Sounds like we may be getting close to a custom rom....????
Is the uImage the ROM? or is it all 4 pieces
Sorry if I am misunderstanding this pokey since I am a total noob. I too have been holding out on rooting hoping for an easier solution (I do not even know how to navigate to directories in terminal) I believe you are implying that the NC can be rooted using this method and is in fact much easier to accomplish. You said that you had to copy over those 4 files once you format the card. Where can one obtain those files?
Thanks man for all your dedication and hard work!
sudermatt said:
Sounds like we may be getting close to a custom rom....????
Is the uImage the ROM? or is it all 4 pieces
Click to expand...
Click to collapse
MLO - first stage bootloader. The OMAP's built in ROM looks for this on the SD and runs it. MLO then looks for u-boot.bin and runs it if it can find it on the card. It's like the Nook's boot sector.
u-boot.bin - second stage bootloader. This is responsible for figuring out how to get Linux and the ramdisk in memory. This copy loads up uImage and uRamdisk from microsd and starts running the kernel. This is similar but not the exact same as the one on the internal flash.
uImage - The Linux kernel. This copy is built specifically for Nooter.
uRamdisk - a Linux filesystem that gets loaded into RAM. Contains the Nooter script, disk utilities for performing the root, and other bits and pieces that let you log in over USB and get a shell.
This really has nothing to do with a custom ROM, it's just an easier way to install Nooter.
th3c1am said:
Sorry if I am misunderstanding this pokey since I am a total noob. I too have been holding out on rooting hoping for an easier solution (I do not even know how to navigate to directories in terminal) I believe you are implying that the NC can be rooted using this method and is in fact much easier to accomplish. You said that you had to copy over those 4 files once you format the card. Where can one obtain those files?
Thanks man for all your dedication and hard work!
Click to expand...
Click to collapse
If you have a card with Nooter on it, you could mount it on a PC and pull all 4 files off. Using the HP utility is an easier option for people who want to root under Windows and are having trouble with the disk utilities. When I get a chance I'll post the files separately.
editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more
Hey guys. Sorry to bother you in the X98 section, but since there's no section for the X80 yet and maybe the devices have some similarities, I hope it's ok.
The tablet worked fine, but to remove any possible bloatware under Windows or Android, I reset Windows. Somehow the device must have crashed (low battery?) and now I can't boot to Windows anymore (black screen and / or boot loop). Of course I made no backup / recovery disk. Android still works fine and I still get into BIOS / UEFI.
I tried reinstalling Windows via OTG with USB stick. I got to the point where I can choose a partition. Problem is, there are lots of partitions (Android, recovery, System and so on). I located the Windows partition, formatted / deleted it and tried to reinstall Windows on this partition. Just the exact way I would do it on a PC. Somehow it won't install on this partition. The error message says something about "the partitions are not in the recommended order. Further information for installation on GPT-volumes..." (I don't know the exact English phrasing because everything is in German). I chose "continue anyway". Then I get the message that "the EFI-system is not formatted in NTFS. Format the partition to FAT32 and start install procedure again". I press ok and get back to Windows Setup (Install now).
I also tried different repair and recovery options. One time I got error code 0xC0000034. Funny thing is, Windows still seems to be there because while trying to repair / recover I tried to load some drivers and could see the hard drives and folders under Windows.
I tried downloading the original roms here: http://pan.baidu.com/s/1qYEa8gc
You need a Baidu account for the larger files and after days and days I gave up to create such an account as it seems to work only with a mainland China number. There's an option for oversea mobiles but that's not working. I tried a QQ-account, but Baidu wants to link with it and you need that telephone number again. So apparently there's no way to get the original files that way.
I found some stuff here: http://www.needrom.com/download/teclast-x80-pro-dualboot/ but that's only a tutorial file in Chinese and some flash programms / drivers (also got them from Baidu - smaller files are possible to download without an account).
Long story short: I guess recovering Windows 10 is too much effort, so I want to make the tablet Android only and of course want to use the whole capacity for Android. I found a thread on reddit about removing Windows on the X98: https://www.reddit.com/r/teclast/comments/479eua/teclast_x89_how_to_remove_windows_10/
But I have no idea which partitions are definitely needed for Android and which ones I can safely delete. I found a partition map here: http://wheresmykeyboard.com/2015/08/teclast-x98-air-64gb-dual-boot-default-partition-map/ but that doesn't help me that much because they look different.
Attached you will find a photo of all the partitions on my device. I guess there are some which were created during the failed Windows installation because I had about 20 GB free space and now only 17.7 GB.
So is there anybody out there who knows if it's possible to remove Windows completely and which partitions I have to delete?
Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.
Deathgazer said:
Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.
Click to expand...
Click to collapse
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Please do describe how you achieved Android-only with 32 GB memory
Cheers
metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Yes please tell us how metalaxi , it'll be much appreciated.:good:
Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!
metalaxi said:
Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!
Click to expand...
Click to collapse
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!
Do we have to change the gpt before doing what you said in your PDF? Or I have just to follow your PDF?
Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.
reycharlesconrad said:
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!
Click to expand...
Click to collapse
Sorry, I can't answer that sufficent enough. As far as I know, you can just delete all partitions except the ones from Windows. Then format the unallocated space and merge it with the one from Windows. No guarantee!
dirkzelf said:
Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.
Click to expand...
Click to collapse
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32
metalaxi said:
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32
Click to expand...
Click to collapse
it's too long ago, so I don't know what I exactly did there, but since there was no reply for a long time, I just took a shot and worked out well, now I have an Android only tablet.
I just got lucky I guess....
partition help
Hi, please help.
I have x80pro e3e8
I managed to erase a complete disk partition.
You are trying to revive again, fail.
installed here:
iSocUSB-Driver-Setup-1.2.0
IntelAndroidDrvSetup1.5.0
PhoneFlashTool_5.3.4.0_internal_win32
downloaded here:
Firmware (20161020_SZ)
Tablet joined and tried to flash.
* failed - failed loadet.efi
Please help. I can not download from Baidu
* If I use phoneFlasTool and flash a blank disc - Create Flash partition and dual boot and replace recovery?
What to do with an empty disc?
Thanks for any advice
It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.
theone0987654321 said:
It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.
Click to expand...
Click to collapse
Thank you for the advice. That's right, I did it was marked. I found a reason. rom file was saved on desktop, and had a long name (as I downloaded it) It must copy the file to C've renamed the firmware. Everything went alright. I downloaded and used the GPT files for resizing disk and now goes all right. Thank you for responding to my question.
hi, I have problem while flashing.
Phone flash tool always gives ERROR
Automatic reboot is not supported on this device, please reboot the device manually
ERROR : [Port 0/1/4] Failed to reboot the device
Click to expand...
Click to collapse
Any idea what to do? I followed all the steps, tried many times, still same problem. And it's not possible to reboot device manually, because then it lose connection with PC
Restock OS Without Android
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
---------- Post added at 04:03 PM ---------- Previous post was at 03:52 PM ----------
affe2000 said:
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
Click to expand...
Click to collapse
Ok, got it working... dnx fastboot mode is there
....
hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon
mike mike baby said:
hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon
Click to expand...
Click to collapse
Straightforward if you can obtain a USB stick capable of storing over 7GB (some 8GB sticks may not); USB hub (ideally a powered hub); USB keyboard; OTG cable.
1) Obtain the Windows files of the correct firmware. The procedure outlined here is for E6E9 firmware, but other firmware will be similar. Download the circa 6.5GB E6E9 firmware Windows files from https://yadi.sk/d/XEvRsoiD3Q4vKX or https://mega.nz/#F!I0AXGR5C!YiNFkZL9DIvzepH28qAjEQ (or from appropriate source for your firmware version).
Decompress the downloads as required to obtain six folders and two files.
2) Format the stick to FAT32.
3) Name the stick WINPE (five uppercase characters).
4) Copy the previously mentioned folders and files to the USB stick.
5) Plug USB stick and USB keyboard into hub; plug hub into OTG cable; plug OTG cable into tablet whilst the tablet is off.
6) Turn on tablet and immediately start tapping << Delete >> key on USB keyboard. This should open the UEFI config section prior to Android boot option. If the tablet displays the Android boot option, turn off the tablet, wait a few seconds, then turn on and start tapping << Delete >> key on USB keyboard again.
7) When in UEFI, touch the title menu option of << Save and Exit >> and look in the << Boot Override >> section for the name of your USB stick, then touch the name of your USB stick. The screen will immediately go blank as the tablet starts to boot from the USB stick.
8) After a few minutes, a numerically display of progress will be displayed in a CMD window.
9) After reaching 100% and nearing completion of the overall installation, the tablet will prompt for acceptance, so accept that prompt.
10) The setup will run a few final operations for a few seconds, then automatically reboot.
11) Done.
You will be prompted to complete the OOBE on each Windows boot until you complete OOBE.
Was wondering if it's easy to root or unlock the bootloader on the new chromecast with google tv
Sent from my A0001 using Tapatalk
We should wait for a custom recovery first. But you might loose all the DRM keys when the recovery partition is flashed. So choose wisely.
The 4gb storage is putting me off from buying it, if it was possible to root it to use apps2sd (or link2sd) to install entire apps on external storage, it would be a good upgrade to my fire tv stick 4k (vulkan support for emulators, slightly more powerful processor and better gpu drivers, as well as gapps installed from the start)
dictorclef said:
The 4gb storage is putting me off from buying it, if it was possible to root it to use apps2sd (or link2sd) to install entire apps on external storage, it would be a good upgrade to my fire tv stick 4k (vulkan support for emulators, slightly more powerful processor and better gpu drivers, as well as gapps installed from the start)
Click to expand...
Click to collapse
Isn't installing on external media a built in option? And forcing it for all apps in in the developer options.
xnamkcor said:
Isn't installing on external media a built in option? And forcing it for all apps in in the developer options.
Click to expand...
Click to collapse
Yeah you are right! This works without Problems.. you only need an USB C Hub with SD support.. look here: https://forum.xda-developers.com/android-tv/chromecast/chromecast-google-tv-ethernet-usb-hub-t4176725
I use an USB C Hub with Gigabit Ethernet and 128GB SD Card. It works nice!
airwolf1544 said:
Yeah you are right! This works without Problems.. you only need an USB C Hub with SD support.. look here: https://forum.xda-developers.com/an...hromecast-google-tv-ethernet-usb-hub-t4176725
I use an USB C Hub with Gigabit Ethernet and 128GB SD Card. It works nice!
Click to expand...
Click to collapse
How did you get the SD card working? I put in a 64GB in mine, but wasn't working until I discovered that the CCwGTV only supports FAT32 which has a max volume size of 32GB. I even tried creating two volumes of 32, but in the end the only thing that worked was just using 32GB of the 64GB as a single FAT32 volume.
EsotericCleric said:
How did you get the SD card working? I put in a 64GB in mine, but wasn't working until I discovered that the CCwGTV only supports FAT32 which has a max volume size of 32GB. I even tried creating two volumes of 32, but in the end the only thing that worked was just using 32GB of the 64GB as a single FAT32 volume.
Click to expand...
Click to collapse
I've succeeded to format large USB sticks (64GB) on FAT32 with Rufus portable (free software). SD card is working only in an USB stick adapter on my hub.
Hi,
Did anyone succeed to write files on a second USB stick?
I have the first USB stick formatted to extend the storage, and a second one as an external USB storage.
The second stick can be read or write on a PC, can also be (only) read on Chromecast with Google TV, but cannot write on it on chromecast. It's a write permission restriction there.
There is an ADB solution or similar?
Thanks,
Any sign of being able to root the Chromecast with Google TV yet?
@Twotoneeddy It sounds like we have to wait for TWRP to be ported to support Android11, once that is done then you can have full Recovery functionality and Root (unless someone wants to port fastbootd like what we did in OP8T). Atm A10 just got support recently from the TWRP Team (https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html).
**Edit**
Didn't realize device was A10, figured due to release time frame that it would have been released w/A11.
But the basics still stand, there is much more work to be done to get root (we can argue chicken or egg all we want but it doesn't change the end answer just the how you got to the answer).
card13 said:
@Twotoneeddy It sounds like we have to wait for TWRP to be ported to support Android11, once that is done then you can have full Recovery functionality and Root (unless someone wants to port fastbootd like what we did in OP8T). Atm A10 just got support recently from the TWRP Team (https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html).
Click to expand...
Click to collapse
Dude, you're putting the cart before the horse. If you don't have root or equivalent*, you can't boot a twrp, assuming you even wanted to.
Technically, you need the ability to boot an unsigned boot/recovery image, which includes the ability to feed that unsigned image into the device. If you can do that, then take the original boot image, install magisk on it, feed it in, and tell it to boot it. There's your root, no twrp required.
EDIT:
card13 said:
**Edit**
Didn't realize device was A10, figured due to release time frame that it would have been released w/A11.
But the basics still stand, there is much more work to be done to get root (we can argue chicken or egg all we want but it doesn't change the end answer just the how you got to the answer).
Click to expand...
Click to collapse
This isn't a chicken and egg problem AT ALL. twrp is just a custom recovery image. Without already having root or equivalent, there is NO WAY TO RUN IT.
Let me give you a simple example of the process as it works on a pixel phone;
1) Developer options --> OEM unlocking
2) adb reboot-bootloader
3) fastboot flashing unlock
4) fastboot [boot|flash boot] boot-magisk.img
* where boot-magisk.img is the boot.img found in the factory package, after being modified by magisk.
Steps 1-3 are the barrier for this device. twrp won't help you with them because you need to COMPLETE STEP 3 before you can install or boot twrp, and by the time you've completed STEP 3, you've already achieved the goal.
There are 2 ways to get there;
1) figure out how to accomplish steps 1-3.
2) figure out a privilege escalation exploit, either through Android, or through recovery, or whatever else you can come up with.
Here is a very simple question that could help start this process off; IS THERE ANY WAY TO BOOT INTO FASTBOOT?
Delete
has anyone tried to boot off sd card? possibly running emuelec?
The real reason to root this thing has to be to bring support for HD audio passthrough.
Apparently the Amlogic S905D3G used to have HD audio passthrough on older firmware. If someone could figure out how to reenable it it would be the perfect streamer.
You can find twrp builds for the S905 but they are for older versions of android
blaze2051 said:
has anyone tried to boot off sd card?
Click to expand...
Click to collapse
wanna know if you found the answer.
What's the answer
Stricted and I just wrote a bootloader unlock exploit - for those of you with compatible units, enjoy: https://www.xda-developers.com/chromecast-with-google-tv-bootloader-unlock-exploit/
npjohnson said:
Stricted and I just wrote a bootloader unlock exploit - for those of you with compatible units, enjoy: https://www.xda-developers.com/chromecast-with-google-tv-bootloader-unlock-exploit/
Click to expand...
Click to collapse
Not to necromorph an old thread, but I was curious to know by chance if it would be possible to apply your root method onto a Chromecast with Google TV that has been automatically updated to Android 12 even though it was manufacture 12/2020? After the update, some functionality I was used to that was present before the update occurred has been neutered and the OS sound effects are ruined and there's noticeable crackling/pop. Now I'm actively searching for a way to root my device so I can downgrade to either Android 11 or Android 10.
urbanman2004 said:
Not to necromorph an old thread, but I was curious to know by chance if it would be possible to apply your root method onto a Chromecast with Google TV that has been automatically updated to Android 12 even though it was manufacture 12/2020? After the update, some functionality I was used to that was present before the update occurred has been neutered and the OS sound effects are ruined and there's noticeable crackling/pop. Now I'm actively searching for a way to root my device so I can downgrade to either Android 11 or Android 10.
Click to expand...
Click to collapse
Nope. Locked up tight.