Hi all,
I had rooted my nook tablet using snowball mod about a week ago and I loaded CWM on to the emmc using indirect's one-click recovery flash app. It was all working fine.
I wanted to return to stock and so put the 1.4.0 zip on my sdcard and rebooted. But it went straight to CWM. So I remembered i had to restore the stock recovery and rebooted and flashed stock recovery. only this time, I used the updated version of the one-click app (the updated version of 26th Jan) and hit reboot to recovery. This caused my NT to be in a boot loop ever since.
I have tried the 8 failed reboot method to initiate a factory reset but it didn't work. I also tried using the Nook Recovery Fix but i can't get to install the drivers since if I connect the NT to my computer, it keeps rebooting over and over again and I can't get to show for longer than 2 secs in device manager to install the drivers for Windows. (I was using it on Ubuntu till now).
My NT just turns on, the black screen n logo shows (The "With adobe reader" screen) however it doesn't go any farther than that. It just shuts down. The white nook screen does not even show. It's like it's going through multiple failed reboots without me holding down any buttons. Any help from you guys is greatly appreciated. Thanks.
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Data Injures said:
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Click to expand...
Click to collapse
Thanks a lot for your suggestion! I just spent a half hour on the phone with B&N customer service and they agreed to ship out a replacement device. The rep said it was a hardware failure that was causing it to act like that. I was a bit surprised at that. I'm not sure she knew what she was talking about. Anyway I had bought mine off craigslist. And now I'm getting a new device so I guess I can't complain. But I'll try later tonight to restore this one using the bootable CWM you linked to. Thanks again.
Follow Up
Just thought of posting a follow up. The bootable CWM method worked. I was able to fix the recovery. Most certainly not a HW problem like the tech claimed. It's working fine now.
I'm glad to hear that! Now if I have the same problem in the feature I can just follow my own advice. Lol
Sent from my DROIDX using XDA App
So I have basically the same problem. My girlfreinds nook was rooted but the OTA update stopped the root from being effective. I tried the sd card revert to 1.4.0 and I hade the problem with the "n" butting not working. When i tried the 8x reset the nook went into an endless boot loop where I see the back screen and the next white screen flashes for like 2 seconds and then reboots. I tried to make the CWM SD card but it still just reboots. My question is that since i never had the CWM mod installed am I pretty much hosed or am I doing something wrong?
What are you using to make the CWM SD card? I strongly recommend using GParted either from a Linux live image or there is a GParted live image you could use. When it works correctly, the bootable SD card that should stop the boot loop.
But why did the boot loop problem occur in the first place ?
sailerph said:
But why did the boot loop problem occur in the first place ?
Click to expand...
Click to collapse
From what I know of, if you install stock recovery and hit the reboot to recovery button, it initiates the stock recovery which then causes the error. Though I don't know the reason behind nor what's causing the problem, just relaying what I have read around the forums.
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Denmmurray said:
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Click to expand...
Click to collapse
Hm I actually unrooted my nook a couple of times to play with it. I reinstalled the stock recovery from the app on multiple occasions, but instead of clicking reboot to recovery, I ran the one click unroot and never ran into any trouble.
Related
So this time I'm going to be a little preemptive. I ordered a GTab like a week ago, spent the time waiting for it to get here doing a ton of reading so I could go ahead and get it flashed right away. It got here and I immediately ran into problems. I got CWM on there no problem and first flashed [ROM-AOSP]G-Harmony Gingerbread 2.3.3 with Honeycomb elements(UPDATED 4/17) with no problem. Didn't like it so tried to flash the CM7 nightly (which I have running on my evo and hero) and it kept getting stuck on the black screen with that just had "android" written on it really small. Since I hadn't anticipated running into something like that, I did even more reading. Decided to try some more roms and see if I had similar problems. Ran into similar problems with the vegan GB except it would hang on the powered by the "gtabdevs" screen or whatever it said. Vegan 5.1 or whatever the other Vegan one is I could get booted up fine though. So I read some mroe since I really wanted CM7. Discovered that I might need to re-partition, so went into CWM and repatitioned to what everyone was saying was the correct settings. Still a no go and got stuck on android screen. So after even more reading I kept seeing everyone saying NVFlash. So I found it, downloaded everything, read the sticky post on how to do it like 4 times before trying it, then gave it a shot. Put the tab into APX mode (vol- and power) and flashed everything and then when it was done, it was stuck in the APX mode. Very irritating considering I had only had it for about 6 hours. Anyways, sent it back and am getting a new one. It will be here tomorrow morning.
Sooooo, after that long winded explanation of everything, here is my question... How the **** can I get CM7 on my tab without wrecking it again? I did a ton of reading, and nothing I had seen helped at all. Everyone says wipe this and wipe that, or mount these then wipe those, or nvflash then do it and so basically I'm just not sure what to do. I WILL NOT use the nvflsh again and risk getting the APX loop, so any good advice would be most appreciated.
Thanks in advance
I just email walked my sister through installing CM7 on her new gtablet.
Have CM7harmony7.02.zip (or whatever.....7.02 is latest stable release....there is a newer nightly though if you prefer that), the gapps.zip on your computer.
install Clockworkmod recovery on your tablet like you did before.
Boot into CWM and partition sd card, 2048 for first partition and 0 for the second one.
attache via USB to your computer, mount usb option in CWM and copy the ROM.zip and the Gapps.zip to your tablet. Eject tablet from computer (USB eject) and unmount in CWM.
- wipe data/cache (factory reset)
- advanced, - wipe davlik cache
install .zip from sd card
(install the ROM, then choose to install .zip from sd card again and install gapps).
Reboot.
Make sure your tablet is NOT running OS 3991 (very unlikely) or 4349 (possible though unlikely) before doing any of this. (ie...boot tablet out of box and check it's OS version in settings).
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
ix3u said:
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Correct, downgrade and then proceed.
Even though I'm 100% sure that at some point of me trying last time that I did in fact do all of those steps, it was a no go.....But this time, I'm sitting here watching the CM7 boot screen
Thanks a ton
I have a rooted 8gb NT, all was working great until a few days ago. I turned it off one night while I was fixing my wifi router and didn't want anyting trying to conect to it and in the morning when I turned it back on it froze on "Bauwks box." The grey screen comes on, then the box comes up but when it looks like it tries to go into CWM the screen starts twiching and doesn't load. Before this it would boot happily with no issues. I have tried to get it to boot with a new SD root card and a recovery card to no avail. Any ideas?
So, what is Bauwks Box? Haha did you just now make that up?
I think it's the bootloader. Remember Bauwks, the one who broke the bootloader and helped us get ROMS on the Nook Tablet?
I know who Bauwks is. It's just funny that OP named it that.
But anyway, are you trying to boot into CWM when you see the box?
Solar.Plexus said:
I know who Bauwks is. It's just funny that OP named it that.
But anyway, are you trying to boot into CWM when you see the box?
Click to expand...
Click to collapse
Nope, not trying to get into CWM it is just doing it on it's own instead of a normal boot.
Not sure how, and more importantly, how to fix it. Previously, I unlocked with the Asus tool, did the sparky root method, installed the most current Prime version of CWM, then flashed JellyBro. Wanted to flash a new ROM last night. I booted into CWM and tried to do a backup, but got some kind of error about not being able to back up the boot image, or something like that. Not wanting to flash a new ROM without a backup, I just restarted, but now it just sits on the EEE Pad splash screen. If I hold down the power button, it restarts but still stays on the splash screen. I had to hold down the power and both volume buttons for a long time to get it to turn off and stay off without restarting. So, what do I do?
mrw1215 said:
Not sure how, and more importantly, how to fix it. Previously, I unlocked with the Asus tool, did the sparky root method, installed the most current Prime version of CWM, then flashed JellyBro. Wanted to flash a new ROM last night. I booted into CWM and tried to do a backup, but got some kind of error about not being able to back up the boot image, or something like that. Not wanting to flash a new ROM without a backup, I just restarted, but now it just sits on the EEE Pad splash screen. If I hold down the power button, it restarts but still stays on the splash screen. I had to hold down the power and both volume buttons for a long time to get it to turn off and stay off without restarting. So, what do I do?
Click to expand...
Click to collapse
Looks like this could help: http://forum.xda-developers.com/showthread.php?t=1662158
Next time I recommend using TWRP and not CWM.
qery said:
Looks like this could help:
Next time I recommend using TWRP and not CWM.
Click to expand...
Click to collapse
Yeah, people have been recommending ditching CWM for TWRP to me for a little while, now, and I continued sticking with it because I was so familiar with it and didn't want to bother with anything else. Didn't know there was a problem with the current version for the Prime. But yeah, I think I'm definitely going to make the jump to TWRP if/ when I get my Prime back up and running.
The biggest issue for me is, I'm not very familiar with actually using ADB/ command prompts for any of this stuff. Every device I've unlocked/ rooted, I used an automated script to do it, so I didn't have to bother with any of that. I also did read over the stuff about nvflash, but I couldn't really make heads or tails out of the instructions, so I thought it'd be best for me to not tamper with it. Figured I was playing safe with my Prime, so I wasn't concerned, anyway.
I believe I can still access fastboot on my Prime (I don't technically know what "fastboot" is or does, though); if I power it on holding down the power and volume down buttons, I get three options (wipe data, fastboot USB mode, and reboot), but I haven't tried connecting it to a computer yet. I'll take a look at your link.
Hm. So from what I gather, I need to get a new blob file; the one in the link you provided talks about getting it from the Virtuous Prime ROM, but the reason this concerns me is, VP seems like a stock ROM, and the unbricking thread notes that if you apply a stock blob file after installing CWM, you get an unrecoverable brick. So... not sure if I should use the Virtuous Prime blob file, or what? I don't want to permanently break my Transformer Prime. :/
mrw1215 said:
Hm. So from what I gather, I need to get a new blob file; the one in the link you provided talks about getting it from the Virtuous Prime ROM, but the reason this concerns me is, VP seems like a stock ROM, and the unbricking thread notes that if you apply a stock blob file after installing CWM, you get an unrecoverable brick. So... not sure if I should use the Virtuous Prime blob file, or what? I don't want to permanently break my Transformer Prime. :/
Click to expand...
Click to collapse
Gosh.... Stock blob = Asus blob downloaded from Support Center...
Just follow the instructions.
Striatum_bdr said:
Gosh.... Stock blob = Asus blob downloaded from Support Center...
Just follow the instructions.
Click to expand...
Click to collapse
Oh, okay, so the VP blob isn't "stock" then? I guess I'll give it a whirl then. Probably tomorrow, though, as I don't have much time today.
I'm not so sure I've set up fastboot on my computer correctly... I followed some instructions on a random site I googled, but I don't know if it worked. I put my Prime in fastboot mode, and when I connected it to my computer, Windows found and downloaded a "Fastboot" driver. But when I opened a command prompt and entered "fastboot devices", nothing happened.
Ok you sould use Universal Naked Drivers from developer forums.
VP is based on stock rom, but it is made for unlocked devices, so it does not hardbrick you (I think it doesn't flash bootloader).
You need to have files Android Platform Tools (from Android SDK) installed (or copied in folder). To this folder you copy files needed to be flashed (mine is c:\program files (x86)\android\android-sdk\platform-tools\). Then you open cmd from there (in explorer press Shift+Right click and select Open command window here).
Now reboot tablet while holding VolDown and select Fastboot (usb icon). Next connect to pc.
After that you should be able to use fastboot commands.
Sent from my Transformer Prime TF201 using Tapatalk 2
Okay, thanks everyone, looks like I'm back up and running!
Just a question; am I reading it right that with the newest version of TWRP, you can't do backups and restores without having done that nvflash thing?
Hm. This is probably unrelated, but... I'm not sure TWRP is working correctly. I installed it via GooManager after I got back up and running (I had tried to flash it via fastboot when unbricking, but for some reason, it didn't take, and I was still on CWM). Anyway, in TWRP, when I do my wipes, it doesn't appear to actually have any effect, even though it goes through the process and says they were successful. Also, when I try to install a ROM, the zips don't appear on the sdcard folder in TWRP, even though they are, in fact, on there.
Putting them on an external card allows TWRP to see them and flash them, but because TWRP apparently isn't actually doing the wipes (even though it says it is), I'm having trouble flashing other ROMs (because I'm basically "dirty flashing" from Virtuous). In particular, I'm trying to flash Blackbean; after the boot animation, it goes through the "Android is upgrading" thing for what I assume is still the Virtuous Prime stuff, then I get an error about system.media (something like that) not responding, and then it quickly goes back to the boot animation and continues to loop from the aforementioned error to the boot animation over and over until I force turn the tablet off.
Anyone know what the heck is going on? Why does it seem like TWRP isn't actually wiping the tablet, and why is it not recognizing the zips in the internal sdcard folder?
mrw1215 said:
Okay, thanks everyone, looks like I'm back up and running!
Just a question; am I reading it right that with the newest version of TWRP, you can't do backups and restores without having done that nvflash thing?
Click to expand...
Click to collapse
Yes. If you don't want nvflash, use older version - in OP it says that 2.2.1+ needs nvflash bootloader.
mrw1215 said:
Hm. This is probably unrelated, but... I'm not sure TWRP is working correctly. I installed it via GooManager after I got back up and running (I had tried to flash it via fastboot when unbricking, but for some reason, it didn't take, and I was still on CWM). Anyway, in TWRP, when I do my wipes, it doesn't appear to actually have any effect, even though it goes through the process and says they were successful. Also, when I try to install a ROM, the zips don't appear on the sdcard folder in TWRP, even though they are, in fact, on there.
Putting them on an external card allows TWRP to see them and flash them, but because TWRP apparently isn't actually doing the wipes (even though it says it is), I'm having trouble flashing other ROMs (because I'm basically "dirty flashing" from Virtuous). In particular, I'm trying to flash Blackbean; after the boot animation, it goes through the "Android is upgrading" thing for what I assume is still the Virtuous Prime stuff, then I get an error about system.media (something like that) not responding, and then it quickly goes back to the boot animation and continues to loop from the aforementioned error to the boot animation over and over until I force turn the tablet off.
Anyone know what the heck is going on? Why does it seem like TWRP isn't actually wiping the tablet, and why is it not recognizing the zips in the internal sdcard folder?
Click to expand...
Click to collapse
Try using older version of TWRP.
And in case of problems, report in twrp thread with a logcat.
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
JoeLansing said:
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
Click to expand...
Click to collapse
Flash this in twrp:
http://www.androidfiles.org/securekey.php?file=Nabi2/JmzNabi2Stock_OLD.zip
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Flash this in twrp:
http://www.androidfiles.org/securekey.php?file=Nabi2/JmzNabi2Stock_OLD.zip
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Ok, I got that. Having problems getting TWRP to see it. I tried from SD card, tried copying it into sd-ext, sdcard, external_sdcard, sdcard/twrp/backups. No luck. If I click Install from sdcard it shows me /sdcard/root.zip so I tried putting it in there but no luck when I click recovery. I tried setting permissions on the zip to 777. What on earth am I doing wrong. I spent about an hour with google searching before I came back here. I'm on TWRP v2.2.2.1
- Joe
JoeLansing said:
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
Click to expand...
Click to collapse
i hope ya wasnt using the mic hole on the bottom of the Unit
http://www.nabitablet.com/specs/nabi2
IF i were you i would Search the forum "nabi 2"
you will find a lot of post with downloads and things that people have done to help get their nabi 2 up and running.
HTH
I used the reset hole and I've already downloaded all the jmz files and a few more. I've read about Nabi here for hours. My last try was restoring JMZ_OLD to get back to factory. Still no WiFI. Then I tried installing the WiFI_Fix. Now it just shows a spinning Nabi logo. I rooted my 4th one today using the new Nabi Lab which I really like! My wife's is the only one that is a problem child. Funny thing is the other 3 were bought at Walmart, hers was bought at GameStop. I think from reading the Cannot Turn on WiFi is a version problem between the drivers and the kernel, but not sure. I really want to try Nabi Lab on it but I think it is old Nabi software at this point, and Nabi Lab says I should be fully updated to run it. But I can't update it without WiFi...grrrrrrrrr. Is there anything I can do to restore it to stock including stock kernel and drivers? Who knows, maybe the WiFI has a hardware problem? But I doubt it. If I use JMZ_Old, then the 2 OTA update files, then ??? I'm not sure I've tried that yet. I wipe everything between attempts. 3 more posts and I can go thank the gentelman that made Nabi Lab in that thread and tell him I tested it and it worked fine.
- Joe
I wonder if you have a Different Nabi 2 then i do ?
coz the only hole I have that looks like a reset hole is for the mic
http://forum.xda-developers.com/showthread.php?t=2050365&highlight=nabi
has a few different downloads like a striped rom a full untouched version and a full de-odexed version.
maybe try that one
.---UPDATE---
New Rom available.
Completely stock.
Not even De-Odexed.
Update 37.
SHOULD fix WiFi issues.
Flash using directions at top of post substituting this zip for the one used in the directions.
PureStockU37.zip
that is the updated 1.9.37 Current at the time of this post
Ok, I'm a moron. My reset hole is the mic, which is now pretty dead...:crying: The good news is Nabi Lab fixed my WiFi and soft brick problems. I had tried about every image out there including that one you suggested. Using Nabi Lab and flashing the hmm All Original - Won't Boot or something like that fixed it. Since I never use the mic I'm ok. I could probably replace it if I wanted to, but I'll give it a rest before I break it again.. I have 3 Nabi's, and 2 Uniden tablets. I killed one of the Unidens. The screen got worse and worse. I popped it apart and tried to reattach the 2 wires to the screen half. It started smoking and doesn't power on.. Now I might take the battery off it and see if I can solder it into the other Uniden to get longer life. I hope it doesn't get hot.
Eric Karz said:
I wonder if you have a Different Nabi 2 then i do ?
coz the only hole I have that looks like a reset hole is for the mic
http://forum.xda-developers.com/showthread.php?t=2050365&highlight=nabi
has a few different downloads like a striped rom a full untouched version and a full de-odexed version.
maybe try that one
.---UPDATE---
New Rom available.
Completely stock.
Not even De-Odexed.
Update 37.
SHOULD fix WiFi issues.
Flash using directions at top of post substituting this zip for the one used in the directions.
PureStockU37.zip
that is the updated 1.9.37 Current at the time of this post
Click to expand...
Click to collapse
that's good you got the nabi working
Now that nabi with the bad speaker ... i wonder if you can use the speakers from the dead Uniden in the nabi 2 ?
here is a thread where the nabi 2 was open up
http://forum.xda-developers.com/showthread.php?t=2024105&highlight=nabi
If you try the battery project or the speaker replacement - be neat to see pictres of it....lol
Speaker was a beer typo.. I meant the mic. I'm an old man and have no use for croaking at people over the interweb with a microphone so I'm ok.. I started a thread someplace about the Uniden tablets. I checked back and it's like 9 pages long with geeks installing Ubuntu and everything else on them. I was amazed! I'm going to get real and get an Onda V972 soon I hope. Now that I have enough posts here I will probably start a thread about buying one of them.
- Joe
Eric Karz said:
that's good you got the nabi working
Now that nabi with the bad speaker ... i wonder if you can use the speakers from the dead Uniden in the nabi 2 ?
here is a thread where the nabi 2 was open up
http://forum.xda-developers.com/showthread.php?t=2024105&highlight=nabi
If you try the battery project or the speaker replacement - be neat to see pictres of it....lol
Click to expand...
Click to collapse
Help brick
Sorry my english.
I was trying to install the GAPPS on nabi2 and messed up.
The kernel recovery screen appears with a exclamation android open.
In normal boot the screen is locked in logo nabi.
I do not have TWRP installed.
When I select fastboot protocol recognizes the PdaNet and appears as a device in windows mtp unknown.
Is there any chance to recover? Could guide me the way?
There is some recovery via APX?
RegisRicci said:
Sorry my english.
I was trying to install the GAPPS on nabi2 and messed up.
The kernel recovery screen appears with a exclamation android open.
In normal boot the screen is locked in logo nabi.
I do not have TWRP installed.
When I select fastboot protocol recognizes the PdaNet and appears as a device in windows mtp unknown.
Is there any chance to recover? Could guide me the way?
There is some recovery via APX?
Click to expand...
Click to collapse
Need to reinstall TWRP with fastboot.
Download a ROM image and restore it in TWRP.
There is an APX way but so far untested and not needed for where you are at.
Thanks for the help, after a snack could reconfigure.
I'm trying to install Freedom but is difficult. There is not enough system memory.
I updated to 2.1, but I think I'll go back to 2.05.