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.
Related
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.
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.
Hello all,
Sorry to ask a "seemlingly" stupid question, but I'm having a very weird problem with my Nabi 2. It was working great until i decided to "re-hack" it. It had been rooted and Gapps installed, but I returned to stock for the OTA's last year. Now I want to go back to a rooted device.
Everything seemed to go well until the script pushed gapps to the already google friendly device. So, long story short, so many errors I decided to start over.
Using Nabilabs, I installed TWRP and installed the 1937 stock roms. Now here is where things go from bad to worse.
The system won't boot. I saw that there may be a TWRP version issue, so I used the TWRP from nabilabs (2.3.3.0) to make sure. At SOME point, not sure when or how, I lost all the mount points. I was able to get them back using TWRP 2.2.2.1but the Nabi is still soft bricked.
As of now, i am able to get any TWRP installed and can successfully restore any of the ROMS (1917 through 2127) but it won't boot. The NABI logo has no animation and it just sits there.
I have tried very permutation I can think of any nothing. Does anyone have any ideas?
Sorry for the long rambling.
mgd014 said:
Hello all,
Sorry to ask a "seemlingly" stupid question, but I'm having a very weird problem with my Nabi 2. It was working great until i decided to "re-hack" it. It had been rooted and Gapps installed, but I returned to stock for the OTA's last year. Now I want to go back to a rooted device.
Everything seemed to go well until the script pushed gapps to the already google friendly device. So, long story short, so many errors I decided to start over.
Using Nabilabs, I installed TWRP and installed the 1937 stock roms. Now here is where things go from bad to worse.
The system won't boot. I saw that there may be a TWRP version issue, so I used the TWRP from nabilabs (2.3.3.0) to make sure. At SOME point, not sure when or how, I lost all the mount points. I was able to get them back using TWRP 2.2.2.1but the Nabi is still soft bricked.
As of now, i am able to get any TWRP installed and can successfully restore any of the ROMS (1917 through 2127) but it won't boot. The NABI logo has no animation and it just sits there.
I have tried very permutation I can think of any nothing. Does anyone have any ideas?
Sorry for the long rambling.
Click to expand...
Click to collapse
Try this and also the link inside that link
http://forum.xda-developers.com/showpost.php?p=54871957&postcount=2342
I'm not sure if you should be starting with JB or ICS TWRP. You will have to figure that out. Just let TWRP do the rooting for you afterwards.
Awesome respone
aicjofs said:
Try this and also the link inside that link
http://forum.xda-developers.com/showpost.php?p=54871957&postcount=2342
I'm not sure if you should be starting with JB or ICS TWRP. You will have to figure that out. Just let TWRP do the rooting for you afterwards.
Click to expand...
Click to collapse
Man, that worked perfect. Thanks so much. You rock.
UPDATE:
So I tried the installer mn2ri-v1.5.0-beta2 without success. It would not detect the Nabi 2. I've been trying for 3 days straight and figured out that because it is Kitkat (Blue Morpho), it won't detect it. It just says waiting for device.
So I can't get into TWRP.
Ever since all the OTA updates, my screen would become unresponsive to touch, and freeze every few seconds. I also had WiFi problems but updated to Blue Morpho, and that fixed it.
I'm unable to do anything with the tablet because of the freezing.
How do I install the original OS, reverting it back to the original OS?
I'm not rooted or anything. I'm a noob.
I tried following some tutorials without success. I don't know how to install fastboot etc.
Please help.
Click to expand...
Click to collapse
okay guys, I've got pretty far.
I was able to get into TWRP
I used this tutorial HERE.
So I flashed the wifi fix.
I also pushed the backup into the correct folder. I even put it into the external just incase.
So when I choose restore, nothing is listed under external or internal drives. Even when I go to install, nothing is listed. I tried both the blue and red themed TWRPs.
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb