Related
First, nothing in this post is my own work. I just wanted to compile the information for everyone else who is surely wanting to know if the 4g LTE tab can run Netflix.
Step 1 - Root:
1. Download the file from THIS THREAD POST to your Tab10.1 (anywhere should work, I went with the /sdcard folder on my tab)
2. Power Down Tab
3. Power On and when you see the Samsung Text Hold Power + Volume UP (From This Post)
4. Select the Android+Box (Volume up to switch, then volume down to select)
5. Chose "apply update from /sdcard" and select the .zip file you downloaded in step 1 (When finished, the tab will automatically reboot).
6. Verify Root - You should see SuperUser in your apps when your tab finishes rebooting.
Step 2 - Asus Transformer Patch
1. Download the Transformer Patch from THIS THREAD
2. Install Patch - I chose to use Root Explorer to manually move the libnvomx.so file into my /system/lib folder, but you could also reboot into recovery and apply the .zip file that way instead (steps 2-5 above).
3. Reboot - If you manually move the .so file you will need to reboot, using the recovery it should reboot for you when finished.
4. Watch Movies
If anyone has trouble with this Please Do Not Email Me
I am really not a pro at troubleshooting, I was just willing to take a shot at rooting and found out that it worked. Hopefully this will ease other people's minds about getting root and netflix on your Verizon Tab 10.1
Also it is worth mentioning that I did all of this without using ODIN or KIES or ADB Shell or any of those other scary things. I chose not to try to install Rom Manager of Flash Clockwork Recovery as I had heard they may cause troubles.
I noticed that you mentioned using an SD Card multiple times in this post, but the 4G LTE version doesn't support SD Cards (doesn't even have the slot).
Why the discrepancy?
dfxdeimos said:
I noticed that you mentioned using an SD Card multiple times in this post, but the 4G LTE version doesn't support SD Cards (doesn't even have the slot).
Why the discrepancy?
Click to expand...
Click to collapse
He probably meant place it on the root of the drive of the tab. When you plug in your tab to your computer, you should be able to view your files there. Add the zip file to the root of that drive. Hope that makes sense.
dfxdeimos said:
I noticed that you mentioned using an SD Card multiple times in this post, but the 4G LTE version doesn't support SD Cards (doesn't even have the slot).
Why the discrepancy?
Click to expand...
Click to collapse
True. I was torn with how to describe the location and decided to use SD Card to be in line with the "\sdcard" which is still in use in the file system for the tab
I guess I've been explaining the root / recovery process on the OG Droid for so long that I still toss references to "root of the sd card" and "install zip from sd".
I'll edit the original post for clarity.
Question (and thanks this is very helpful!). I'm going to do the same as you I think and stick with custom rom and no cwr. So if you need to unroot for warranty return or whatever, and we've only done the steps in this post, what do we have to do to unroot? Thanks!
This worked very well...it was almost too easy. Thank you for sharing the info.
Does it work on the wifi only model? P7510?
CSGirl said:
Question (and thanks this is very helpful!). I'm going to do the same as you I think and stick with custom rom and no cwr. So if you need to unroot for warranty return or whatever, and we've only done the steps in this post, what do we have to do to unroot? Thanks!
Click to expand...
Click to collapse
Not 100% sure CSGirl... in my experience, the person making the determination about warranty approvals would be the in-store rep. In that case you should be fine by just using root explorer and deleting the SuperUser app. The permissions would still be there I suppose, but the store guy wouldn't see the telltale app.
Someone else could probably give a better answer.
If you open up the .zip file for rooting and go into \meta-inf\com\google\android and open the updater-script file you can see everything that is getting changed, I guess you would just have to change that back.
Also, @wiibrewer, I have no idea
Well how about is there any reason it should not work on the wifi model?
wiibrewer said:
Well how about is there any reason it should not work on the wifi model?
Click to expand...
Click to collapse
None that I can think of...
I know that Droid-Life posted this file for the special edition wifi tab: Search "Galaxy Tab 10.1 Rooted" post from May 2011
You might try that too.
4g LTE Recovery Mode
Good Morning: Thank you for your postings. I have a new Verizon Galaxy Tab 10.1 4g LTE. I am not able to get the device into recovery mode. Is there a procedure for rooting that can eliminate that step or is there an alternate way to get in to recovery mode? Any assistance will be appreciated.
I found that the volume up button is the one closest to the power button and not the actual volume button if that solves your problem
Verizon 4g LTE Tab root
Hi there,
I just bought a samsung Galaxy 10.1 4G LTE tablet.
Model #SCH-I905 Running adroid version 3.1
And I cannot get to Step #5
My volume and power buttons are on the left side of the tablet.
I copied the the file Samsung_Galaxy_Tab_10.1_root zip file
onto the main root directory, but when I power down the tablet
and select the android box icon on the left - my screen goes blank
and cannot get to the next step witch is to apply the update from SD card and to choose the zip file.
Can someone please help me, it is driving me crazy! I have tried over and over too many times with no success.
My compter is running wondows 7 64bit
Thanks!
Did you rooted the tab because,mine runs just fine i rooted then i flashed the CMW recovery after
Sent from my SCH-I905 using XDA Premium App
Is this still working for anyone else? It was working fine for about a week but now I'm getting "connection failed" when starting Netflix. Poo it was nice while it lasted.
Sent from my Samsung Galaxy Tab 10.1 using Tapatalk
Edit: nevermind it must have been something on their end its working now.
i have another issue where i can get into recovery but when i go to apply the update i get the error e:unknown volume for path sd card and nothing is displayed in the file list even though i have the file on the root of it. Any help would be appreciated.
Link to exploit.zip is broken
The link to exploit.zip from the other post is broken. Anyone know of another link?
Same problem
lagqboy said:
Hi there,
I just bought a samsung Galaxy 10.1 4G LTE tablet.
Model #SCH-I905 Running adroid version 3.1
And I cannot get to Step #5
My volume and power buttons are on the left side of the tablet.
I copied the the file Samsung_Galaxy_Tab_10.1_root zip file
onto the main root directory, but when I power down the tablet
and select the android box icon on the left - my screen goes blank
and cannot get to the next step witch is to apply the update from SD card and to choose the zip file.
Can someone please help me, it is driving me crazy! I have tried over and over too many times with no success.
My compter is running wondows 7 64bit
Same problem here.
I can boot to Download mode and use Odin3 but can't boot to recovery mode... I get a blank screen with slight edge glow. So the older way to root won't work either, since you can't get to Recovery mode to finish the job.
Any suggestions? Would a Factory data reset work.
Click to expand...
Click to collapse
The link from step 1 is broken. Can you please upload a new copy?
dfxdeimos said:
The link from step 1 is broken. Can you please upload a new copy?
Click to expand...
Click to collapse
The link to the exploit file is now working in the linked post. Thanks.
I'm a complete noob and I've searched the forums and can't find an answer to my questions. (I'm sure there's some answer in Japanese on a Japanese forum somewhere, but my Japanese is not up to that level.)
I have a Toshiba Regza IS04 from AU (in Japan).
Running Android 2.2.2
Baseband Version 5014.1907.39
Kernel Version 2.6.32.9-rel [email protected] #1
Build Number FFK300
I have been researching rooting on and off for months since I first got the phone and have decided I would like to root it. My reasons for rooting:
1. I want to get rid of all the apps that were pre-installed that I don't use.
2. I would like to have the latest version of Android 4.0 Ice Cream Sandwich. (I doubt that another authorized upgrade from au is ever going to happen, since the 2.1 to 2.2 upgrade.)
It seems from reading forums that there are special builds of an OS depending on the phone?
My questions:
1. What is the best way to backup my phone before rooting?
2. What would be the best rooting method for my phone (SuperOneClick?)?
3. How can I (or even can I) upgrade my Android to 4.0?
Thanks for any help!!
Sam
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Thank you so much for this response!
I have the same phone, and I've been wanting to root it for a long time. There were so many pre-installed applications that are just hogging room, especially since I can't read Japanese well enough (yet).
-T
I hope it works for you too!
I spent probably the equivalent of 2-3 days searching over the last few weeks, but couldn't find anything that I was comfortable with trying.
This morning, I finally got the nerve up to try superoneclick and was really disappointed when it wouldn't work. Then I started trying all kinds of methods, and about 8 hours later finally came across the method that worked!
It's probably the only thing frustrating sometimes about having a Japanese phone: lack of English support!
Now I'm just hoping I don't break it! I'm backing up all the apps with Titanium backup before I start deleting them one by one. I would hate to delete something that is crucial to the system and not be able to restore it. I'm also looking into other ways to backup the system.
One word of warning. Your au one market will not work unless you do one more step. It's mentioned in English in the readme file. I didn't bother because I never download from it anyway. (Although, I probably should just so I'll keep getting updates on some of the J apps that I do have.)
Deleted
Deleted
the rootkit d/l has been removed. anyone know where to get it?
The File
I'm not sure if this is against the forum rules, but I have a copy of the zip file (well, a zipped up copy of the folder) from my computer. If you pm me, and I can send you it.
-T
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
link die;
anyone help me another link for that file & help me root this device step by step?
Thanks
The post above dissolution said they had one, but good luck getting a reply. I'm emailed twice and nothing.
私はローボーボブ。 Haro！！
Latest rootkit for FFK300
Here is the latest rootkit,
IS04 root toolkit ver 4.0.1
http://www1.axfc.net/uploader/Ne/so/131631
DL key ; is04
And other informations;
- Custom kernel(overclock, compcache, +others)
http://marijuana.ddo.jp/is01/index.php?moddir=downloads&action=visit&cid=9&lid=47
- Custom kernel(CWM on ramdisk, ported from Xperia, modUI)
http://www.mediafire.com/?jkz5nek59y3hpaf (reported kernel unstable)
# FFK301 stock ROM update - (rootkit does not work, still can be rooted.)
http://spf.fmworld.net/sw_update/kddi/is04/update/
- scroll to bottom and click on blue rectangle.
# kernel source code
http://spf.fmworld.net/oss/is04f/index.html
- some files are missing, extract them from T-01C(DoCoMo).
http://www.fmworld.net/product/phone/sp/android/develop/t-01c_froyo_oss/
help! rooting regza inquiry..
[/COLOR]
samkk75 said:
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Click to expand...
Click to collapse
hi!
I am a newbie here and like you all, I would also like to root my regza phone. Can someone give a working auto_rootkit because the link above is not working. I have searched it as well on the net but still all will lead me to dead hotfile link. Or someone could send me the file instead to my yahoo mail [email protected] tnx in advance
And also i have downloaded this rootkit instead from IS04 and downloaded. After dowloading, I click the adb file and it appears a command screen with commands running so fast. Next i did click the root file and there appeared a command screen with all sorts of command running so fast. My question is, i did not received any confirmation that the rooting process was succesfull. And also i have read to other forums that one thing you will notice that rooting was successfull is that 'superuser" will be automatically installed.
Please help me on this one. To be honest I started exploring this process since i have this phone and there are apps that i wanted to uninstall not unless i root the phone.
Thank you in advance
marvz,
Dissolution said:
I'm not sure if this is against the forum rules, but I have a copy of the zip file (well, a zipped up copy of the folder) from my computer. If you pm me, and I can send you it.
-T
Click to expand...
Click to collapse
hi there!
Can you send to my e-mail [email protected] the said file so that i could root my regza phone?
thank you for your help> ^_^
Question to get root on phone regza
samkk75 said:
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Click to expand...
Click to collapse
Hi
I have this phone too. And I try to get root, you can send for me the link of you downloaded and explain for me how you made it.
Other question, I can use this phone to call in brasil?
Thank you.
:good:
My phone just had this phone and I'm trying to update it before rooting. It came with 2.1-update 1 OS version and I'm trying to update the phone to it's latest official 2.2.2.
I've downloaded the necessary 256mb file update but it didn't work. Even tried using the recovery but is still not working.
Based on my research about this phone, There's no way to update without the phone downloading the app from the official website, using the SIM and au logins.
We've lost the sim (UIM) card that came with the phone. So I guess its stuck on its current OS. I'm having trouble installing apks (Gingerbreak and even normal apps) as it always gives me the error "parsing error" or something.
Is there anyone could help?
EDIT:
I have successfully updated the phone from Android 2.1-update1 to Android 2.2.2.
Download all the necessary files here:
http://www.fmworld.net/product/phone/is04/
I have used the method of updating from the least upgrade and up to the latest. I have managed to download 3 separate files for the upgrade, namely:
IS04_RC2_RC3RE_DL.zip
IS04_RC_4.zip
IS04_TO_SP_FYRC_4.zip <- froyo update
I have extracted all the files on the sd card. make sure that the ".enc" file is found on the root of the SD Card and on the "prg" folder.
I have updated it using the recovery mode (power + volume up + camera button).
I am now currently trying to Root the device using Gingerbreak and seems that it's taking too long to root.
Also. I have able to root the 2.1-update OS using z4root.
help me
hi.. i didn't my phone plz send me ...................................................auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
thnxx.. in advance..
Root
I rooted mine with http://unlockroot.com/
root_toolkit_is04_v4.3.zip
www1[dot]axfc[dot]net
/uploader/Ne/so/135399
Password is "is04".
suhax
www[dot]4shared[dot]com
/zip/pHLT8kqe/suhax.html
Sent from my IS04 using xda premium
more detail please
samkk75 said:
.....
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
.....
.....
I hope this can help someone else.
Click to expand...
Click to collapse
Thx so much for your posts.
I am so glad to finally find someone with the same phone, the same problem and intentions
I do, however, need more info:
Did you extract the files into any particular folder? You obviously hooked up in de-bug mode, but did you command prompt anything?
I tried your steps but get nothing to 'hit enter' on. I have also tried the other (different version) toolkit.
You can IM me or email or post or come around and root my phone yourself - I will sell you my car, house, wife...
... as you can tell I am a little frustrated ...
lets just IM/email for now
Thx in advance,
Kaz
---------- Post added at 12:34 PM ---------- Previous post was at 12:29 PM ----------
orgia82 said:
I rooted mine with http:!!unlockroot*com/
Click to expand...
Click to collapse
Didn't get to try it - was too tied down with all the additional ^%$&#$ I had to download to get to it.
help
as everyone can see that link isnt working anymore,so im here asking someone whos still have it to upload :fingers-crossed: again．．．．
First, you need to be sure you install the sdcard version of the recovery, otherwise you won't be able to do this. (You need to goto this thread to install the sdcard version and follow instructions.
First of all, make sure your drivers are setup properly as this is a windows script to fix everything since you can only fix it from a computer. (I CANNOT EMPHASIZE THAT ENOUGH!)
Then you just download this zip, it check's md5 sum on the image before flashing so no worries, and then it flashes. It will reboot when it's finished.
I am in NO way responsible should anything happen, it was your fault for not checking the app's md5 in the first place so if this works for you, openly admit that you could have been better with handling the app's flashing. <-- Required.
I'm having a seperate thread so I can actively update this with anything that may arise since it would make my app's thread cluttered.
Read the whole thread or enjoy a broken Ntab, it's your choice.
Just wanted to say thanks for the dedication to those of us not smart enough to figure things out on our own.
Sent from my BNTV250 using Tapatalk
is this for those nt cannot use sd card recovery or 8 times boot break to restore the originally rom?
Dumb Question
Total noob question. What do you mean by drivers set up properly? I want to try this, but I do not want to screw up again, and I just want to be totally sure I understand this properly. Thanks.
Benblanko81 said:
Total noob question. What do you mean by drivers set up properly? I want to try this, but I do not want to screw up again, and I just want to be totally sure I understand this properly. Thanks.
Click to expand...
Click to collapse
Means that you must have your nook drivers installed and working, if you ever rooted then you should have your drivers working properly.
~ Veronica
Can't get this to work
I have verified that I have the proper drivers (thanks Veronica). I unzip the fix and run the batch file, but the window closes almost instantly. I am using an XP machine, because of installing the drivers when I rooted. I can not for the life of me figure why it wont run. I am booted into the sd card version of CWM. Do I need to mount it some way or just at the home CWM recovery screen. I have been looking for help without asking and bothering, but can't figure it out. Not a noob but totally confused. Any help would be appreciated. Thanks.
Oops! I managed to set the wrong error levels on it, I meant to do 0 and 1, I instead did 1 and 2. Anyway, uploading now.
Still no go.
I got the batch file to run but it does not finish. It starts the Deamon successfully, and it just stays at Deamon Started Succesfully. It has been there for about 45 minutes. Should I wait or can I kill it and start over. Thanks again.
Kill it reboot your machine and start over
Sent from XDA premium using my Nook Tablet
No Go
Thanks Veronica, but the reboot still does the same thing. I just started the Nook&Zergy and the device shows up so I know the drivers are proper, it just stays stuck in Deamon Started Successfully for the fix. I am out of ideas, I fear I have just bricked my first device. I have doing this since the G1, this is sad.
No no, just do:
adb push cwm_internal.img /sdcard/cwm_internal.img
adb shell
then type:
dd if=/sdcard/cwm_internal.img of=/dev/block/mmcblk0p3
First off great work Indirect. This is exactly what I was hoping that image creator would be used for, just working on other things and got preoccupied. I think you might have to do some explaining though.
One thing to note though is that CWM should not be used for any other then rooting your device. As it stands right now there is no reason to flash it to an internal partition, you will only risk messing something up, as it has no gains.
Overview:In the Nook Tablet world there is a locked bootloader, which requires that there be a Secure Chain from u-boot, to the recovery. With the exploit that bauwks discovered and designed, we are able to flash custom recoveries on to the device. However a recovery must be packed.
Packing Structure:There are two ways that we have been able to go about getting around the boot loader, the internal method requires that we use the second U-Boot, with a 256k buffer and then attache the recovery after the buffer.
(0-m bytes) ------> (m-256k bytes) ------> (256k-n bytes)
Bauwks ntBoot Buffer nemiths CWM
The trick is that that 256kth byte must contain the header for the CWM, and this is vital. If that is lost, or something on Bauwks didnt get flashed right, you will enter a boot loop.
FAQ:
What Is a 'broken recovery' NT?
A broken recovery Nook Tablet is one where either the NT's internal recovery structure was not writen correctly or one where the NT's internal recovery structure is missing bauwks boot.
How can I tell if I have a 'broken recovery'?
Assuming you have not messed with any other partitions if you do either the N + pwr method, or the 8 false boots, you should see it open the BN recovery. If your device constantly turns on and off after one of these two methods, then you have a broken recovery partition.
My Nook just continues to boot into the recovery whats this?
Aha now that is not a 'broken recovery' and is actually quite fixable. In the nook Tablet there are two files that relate to the booting structure, aka the selection of where to boot from. These lie on a partition called bootdata, and are named BCB and BootCnt. If you are running stock on your internal partition, just let the stock recovery run, and it will solve your problem. If you are running CWM, you will have to use the following commands,
Code:
adb shell mount -t vfat /dev/block/mmcblk0p6 /data
adb shell dd if=/dev/zero of=/data/BCB bs=1 count=1088
adb shell dd if=/dev/zero of=/data/BootCnt bs=1 count=1
adb reboot
Aaa this is confusing can't I just put the stock recovery on my NT?
Sure. Hopefully indirect will make a script soon, or I will make one tonight that will put the default recovery img back. If you are feeling lucky you can do the following while on CMW.
NOTE: I AM NOT RESPONSIBLE FOR ANY DAMAGES YOU CAUSE TO YOUR DEVICE. One false move and you will brick your device. HIGHLY UNRECOMMENDED
Code:
adb push recovery.img /data (this is the recovery from the 1.4.0 or 1.4.1 update zip)
adb dd if=/data/recovery.img /dev/block/mmcblk0p3 (THIS LINE IS [COLOR="Red"]EXTREMELY DANGEROUS[/COLOR]. It should only be done as a last resort, and you should only do it if you are willing to take full responsibility.)
Dead End.
I am going to start from the beginning. I flashed CWM using this app and the hit reboot into recovery from the app as well. Went to the cardboard box. I can reboot into CWM using the sd card method but can get no further. I have been trying the fix for two days and cant get it to work. Indirect gave me some ADB commands but I cant get ADB to work either. I have been on this for 2 days and cannot get it going. I really do not know what else to do. I am not a Noob and i know I have the proper drivers, the fix gets stuck though, and with the tablet in CWM from the sd card I just cant get ADB to work. I do not know if maybe because of usb debugging not being checked off, but again I can not boot up to Android, just to recovery from sd card. If I take out the sd card with CWM it boots to the cardboard box, then to black screen, and there it stays. I checked the thread for the app and people are still having this problem. I really do not know what to do. I have followed every instruction I have found or has been given to me, to the t, nothing.
UPDATE - I deleted the sdk and everything that had to do with Android from my pc. Reinstalled drivers using the method in the root thread that is pinned. I ran NOOK&ZURGY just to see my device appear in list of adb devices, which it did. It gave me my serial and it said recovery. I then redownloaded the sdk and did not download the Drivers from SDK manager. I am not sure but that seems to be the key here, to get rid of google drivers that can be downloaded from SDK manager. I then opened a command prompt, adb devices and bam there it was. I used the commands posted by LogLud above my post under "My nook just continues to boot into the recovery, what is this?". ADB Reboot and ****ing worked. THANKS TO INDIRECT, LOGLUD, and LAVERO.BURGOS. Your patience and help is greatly appreciated. I have never really asked for this much help before on XDA, and you guys were on the money, Thank You, Thank You, Thank You. Please PM me so that I can get you guys and girls beers. I will try to figure out how on my own anyways, but you guys deserve a contribution for taking the time out of your day to help me and others. Anyone with this issue and is having problems fixing, please post here or shoot me a PM and I will gladly give you all I can. Thank you again to all and happy flashing.
Benblanko81 said:
I am going to start from the beginning. I flashed CWM using this app and the hit reboot into recovery from the app as well. Went to the cardboard box. I can reboot into CWM using the sd card method but can get no further. I have been trying the fix for two days and cant get it to work. Indirect gave me some ADB commands but I cant get ADB to work either. I have been on this for 2 days and cannot get it going. I really do not know what else to do. I am not a Noob and i know I have the proper drivers, the fix gets stuck though, and with the tablet in CWM from the sd card I just cant get ADB to work. I do not know if maybe because of usb debugging not being checked off, but again I can not boot up to Android, just to recovery from sd card. If I take out the sd card with CWM it boots to the cardboard box, then to black screen, and there it stays. I checked the thread for the app and people are still having this problem. I really do not know what to do. I have followed every instruction I have found or has been given to me, to the t, nothing.
UPDATE - I deleted the sdk and everything that had to do with Android from my pc. Reinstalled drivers using the method in the root thread that is pinned. I ran NOOK&ZURGY just to see my device appear in list of adb devices, which it did. It gave me my serial and it said recovery. I then redownloaded the sdk and did not download the Drivers from SDK manager. I am not sure but that seems to be the key here, to get rid of google drivers that can be downloaded from SDK manager. I then opened a command prompt, adb devices and bam there it was. I used the commands posted by LogLud above my post under "My nook just continues to boot into the recovery, what is this?". ADB Reboot and ****ing worked. THANKS TO INDIRECT, LOGLUD, and LAVERO.BURGOS. Your patience and help is greatly appreciated. I have never really asked for this much help before on XDA, and you guys were on the money, Thank You, Thank You, Thank You. Please PM me so that I can get you guys and girls beers. I will try to figure out how on my own anyways, but you guys deserve a contribution for taking the time out of your day to help me and others. Anyone with this issue and is having problems fixing, please post here or shoot me a PM and I will gladly give you all I can. Thank you again to all and happy flashing.
Click to expand...
Click to collapse
Oh well you should had started your first post by saying im using SDK and you will have it fixed faster. SDK is not needed in windows, leave that for devs all the necessary stuff that you needed to root is provided in indirects permanent root thread including drivers.
Glad it worked!
~ Veronica
Please help
I used Indirects app to install CWM, it seemed to work fine, but when I tried to boot into CWM it flashes the picture of the box, then shuts off. I tried using this method to fix it, but the same thing happens.
What am I doing wrong? Please help. I'd hate to have bricked my nook.
lehite said:
I used Indirects app to install CWM, it seemed to work fine, but when I tried to boot into CWM it flashes the picture of the box, then shuts off. I tried using this method to fix it, but the same thing happens.
What am I doing wrong? Please help. I'd hate to have bricked my nook.
Click to expand...
Click to collapse
Did you try the method posted in this thread? you don't mention that , also can you boot normal if you let it or you cant? provide more info.
~ Veronica
lavero.burgos said:
Did you try the method posted in this thread? you don't mention that , also can you boot normal if you let it or you cant? provide more info.
~ Veronica
Click to expand...
Click to collapse
Sorry if I was not clear. Here is the entire process:
1. I have a rooted Nook Tablet.
2. I installed Indirect's One Click App to install CWM
3. I used that app to install CWM.
4. I attempted to boot into CWM, but it flashes the box and then shuts off
5. I came to this thread and began following the instructions to fix it, but the fist set of instructions "First, you need to be sure you install the sdcard version of the recovery, otherwise you won't be able to do this.(You need to goto this thread to install the sdcard version and follow instructions.)
6. I followed those instructions, but I still get the box image then shut down.
7. I can't boot normally or into CWM.
Let me know if you need any other information and I greatly appreciate your help.
What I really need to know is how to create the CWM sdcard on a mac. i.e. I don't have a linux machine with gparted and I can't figure out how to get something like Disk Utility to enable boot and lda flags.
Thanks!
bootable sd card with osx
Lehite, I was having the same problem, i.e. disk utility in osx couldn't do the job for me. I ended up using this method.
Download the “size agnostic” CM7 SD card installer image (v1.3 in my case), then write it to your microSD following the instructions on the before mentioned page. The writing takes a little bit without terminal telling you the progress, after 1-2 minutes it should be done.
After succesfully writing the image to your SD card copy the files from Goncezilla's SD Boot thread (here) to your SD card overwriting files if necessary and follow his further instructions.
On a reboot with the boot SD inside your nook you should get to the CWM menu after seeing the cardboard box. good luck!
I myself am also stuck at the black screen after the box and need to figure out how to get the ADB working on osx to be able to do Loglud's commands...
UPDATE: to get ADB working on osx I used this method. Since I'm not a developer I didn't download the whole SDK package from google but rather just the ADB tools from here.
I then connected the Nook to the mac while in CWM, checked if it was properly recognized but typing adb devices, and applied Loglud's adb commands. BAM! worked! Am back in android Many thanks to all for directions, especially Loglud.
Now a question to Indirect, I downloaded your package just today, while using it it verified the MD5 positively and continued flashing. Why did I get the black screen, and not the CWM?
cheers
Hi anyone and everyone,
So let me start by saying I am really in need of help two months ago i had a flawless CM7 Nook Tablet 16GB that worked like a dream and now i have a useless brick and im about to through it away the problem i have can be viewed here............ http://www.youtube.com/watch?v=0BAZ...&playnext=1&list=PL05B917C134DF82A7........It gets stuck on the white screen everytime i was able to boot into CWM with a bootable sd card and I have tried to flash many roms from there and yet every time i get stuck at white screen please help help help help!
WOW!!!!!!!!!!!!!!!!!
Thanks in advance to all that reply!
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
ShinnAsuka said:
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
Click to expand...
Click to collapse
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
and as to where I am now......everytime I turn on my nook it gets stuck at the white screen with the cardboard box.....unless I use a bootable sd card which then I have tried to flash old roms new roms and I get nothing
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
Your partitions are : shot / corrupt / messed up. They "really" gotta be working okay . . . Will the near by B&N store put them back in good working order for you ?
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
With a bootable SD card are you able to.use ADB? If you are you might be able to push a normal build.prop to /system and be able to boot back into your rom. If not then like old fart said you may have messed up your partitions.
Sent from my Nook Tablet CM7 BETA using xda premium app
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Clksk8 said:
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Click to expand...
Click to collapse
assuming you have adb setup correctly the commands aren't too difficult. i believe the following should suffice. i only know windows commands so yeah..
open your start menu, type in cmd and then enter.
navigate to directory where you have adb installed. in my case it was -> cd C:/ntroot
then connect your NT to your computer, make sure usb debugging is enabled which it most likely is if you can get into cwm.
use adb devices, and there should a string of numbers which is your serial number. if you see it then that is a good sign.
then adb remount, which makes the file system writable.
next make sure you have the normal build.prop in that directory that you have adb installed in.
then do adb push build.prop /system
should be very quick, if all goes well you should be able to boot back into your rom. otherwise, your partitions are likely screwed up...
if your partitions are screwed up, there should be a couple of links in the android development section that tell you how to repartition so you can start anew.
good luck.
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
that serial number is normal, you should really learn to use the search function provided by this forum but here are two that i found...
http://forum.xda-developers.com/showthread.php?t=1562130
http://forum.xda-developers.com/showthread.php?t=1605664
those two are assuming you screwed up your partitions.
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
adb is hooked up correctly but when i put adb devices i get
0000000000 recovery instead of a serial number?
So I have bricked my Nook dozens of time but when I do I just download the acclaim_update.zip from one of these threads and go to a file in it.
Go to /META-INF/com/google/android/updater-script and then I just edit the first two lines. Edit both parts where it says "blaze" and change it to "acclaim". If you're on ubuntu then all you have to do is press saveand it will ask if you want to update the file (or something like that) and click yes. Then just make a CWM bootable sd card and flash that file Hope it helps!
Hello everyone, i recently purchased one of these from newegg at a reasonable price, but I can't seem to find rom's for them anywhere. Does anyone have any ideas on where to look, i've been hunting on google for hours. It's currently running 4.2.2
Kernel 3.0.36+
Firmware: CT9706_RK610
Im not sure what else to do. I would hate to have to stick with stock considering it's a little laggy with the junk that they piled onto it. Not to mention i know it has the chinese OS installed on it. Luckily i WAS able to root it, and even get cwm installed on it, but i have no rom to flash to it as of yet. Any help is appreciated, thanks!
Soft Bricked Taipad 10s
I have this tablet, and was able to root it, and all was fine until I realized that it was not utilizing the Nandflash. The internal storage was full, and the Nand was empty (ish). SO i decided (as a newb) to pull the boot.img, edit the init.rk3066.rc and attempt to re-route the emulated storage to /mnt/sdcard. Recreated the new_boot.img, and pushed it and cat to mtdblock2 as i got it..(correct base address) - and reboot takes it to recovery. over and over.
I am looking for a rom that will work, from what i find CWR and CWM are a no go due to stopped development, but im still searching. There must be a similar tablet somewhere.
Oh and b4 the softbrick i used to get adb shell cmd line "[email protected] #" or something like that - now i only get "#" - so i could not cat the original boot.img - yay fail.
Adulator12 said:
I have this tablet, and was able to root it, and all was fine until I realized that it was not utilizing the Nandflash. The internal storage was full, and the Nand was empty (ish). SO i decided (as a newb) to pull the boot.img, edit the init.rk3066.rc and attempt to re-route the emulated storage to /mnt/sdcard. Recreated the new_boot.img, and pushed it and cat to mtdblock2 as i got it..(correct base address) - and reboot takes it to recovery. over and over.
I am looking for a rom that will work, from what i find CWR and CWM are a no go due to stopped development, but im still searching. There must be a similar tablet somewhere.
Oh and b4 the softbrick i used to get adb shell cmd line "[email protected] #" or something like that - now i only get "#" - so i could not cat the original boot.img - yay fail.
Click to expand...
Click to collapse
hi... i have a taipd 9x- but i had a mistake.. and i dont have rom files and im stuck!!.. my android os does not work.. and i need the files to make it work the touch and wi fi hardware..can you help me how to do or find that rom file?
MAXIMAURO said:
hi... i have a taipd 9x- but i had a mistake.. and i dont have rom files and im stuck!!.. my android os does not work.. and i need the files to make it work the touch and wi fi hardware..can you help me how to do or find that rom file?
Click to expand...
Click to collapse
Do either of you still have the original firmware for the Taipad 9X? I've essentially bricked mine by loading an incompatible firmware and would love to get back to the original.
I'd be willing to pay a small fee to get it.